2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.5.11 - 2015-03-17
7 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
9 It backports several bugfixes from the 0.2.6 branch, including a
10 couple of medium-level security fixes for relays and exit nodes.
11 It also updates the list of directory authorities.
13 o Directory authority changes:
14 - Remove turtles as a directory authority.
15 - Add longclaw as a new (v3) directory authority. This implements
16 ticket 13296. This keeps the directory authority count at 9.
17 - The directory authority Faravahar has a new IP address. This
20 o Major bugfixes (crash, OSX, security):
21 - Fix a remote denial-of-service opportunity caused by a bug in
22 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
25 o Major bugfixes (relay, stability, possible security):
26 - Fix a bug that could lead to a relay crashing with an assertion
27 failure if a buffer of exactly the wrong layout was passed to
28 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
29 0.2.0.10-alpha. Patch from 'cypherpunks'.
30 - Do not assert if the 'data' pointer on a buffer is advanced to the
31 very end of the buffer; log a BUG message instead. Only assert if
32 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
34 o Major bugfixes (exit node stability):
35 - Fix an assertion failure that could occur under high DNS load.
36 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
37 diagnosed and fixed by "cypherpunks".
39 o Major bugfixes (Linux seccomp2 sandbox):
40 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
41 crash during attempts to call wait4. Fixes bug 15088; bugfix on
42 0.2.5.1-alpha. Patch from "sanic".
44 o Minor features (controller):
45 - New "GETINFO bw-event-cache" to get information about recent
46 bandwidth events. Closes ticket 14128. Useful for controllers to
47 get recent bandwidth history after the fix for ticket 13988.
49 o Minor features (geoip):
50 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
51 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
54 o Minor bugfixes (client, automapping):
55 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
56 no value follows the option. Fixes bug 14142; bugfix on
57 0.2.4.7-alpha. Patch by "teor".
58 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
59 14195; bugfix on 0.1.0.1-rc.
61 o Minor bugfixes (compilation):
62 - Build without warnings with the stock OpenSSL srtp.h header, which
63 has a duplicate declaration of SSL_get_selected_srtp_profile().
64 Fixes bug 14220; this is OpenSSL's bug, not ours.
66 o Minor bugfixes (directory authority):
67 - Allow directory authorities to fetch more data from one another if
68 they find themselves missing lots of votes. Previously, they had
69 been bumping against the 10 MB queued data limit. Fixes bug 14261;
70 bugfix on 0.1.2.5-alpha.
71 - Enlarge the buffer to read bwauth generated files to avoid an
72 issue when parsing the file in dirserv_read_measured_bandwidths().
73 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
75 o Minor bugfixes (statistics):
76 - Increase period over which bandwidth observations are aggregated
77 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
79 o Minor bugfixes (preventative security, C safety):
80 - When reading a hexadecimal, base-32, or base-64 encoded value from
81 a string, always overwrite the whole output buffer. This prevents
82 some bugs where we would look at (but fortunately, not reveal)
83 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
87 Changes in version 0.2.4.26 - 2015-03-17
88 Tor 0.2.4.26 includes an updated list of directory authorities. It
89 also backports a couple of stability and security bugfixes from 0.2.5
92 o Directory authority changes:
93 - Remove turtles as a directory authority.
94 - Add longclaw as a new (v3) directory authority. This implements
95 ticket 13296. This keeps the directory authority count at 9.
96 - The directory authority Faravahar has a new IP address. This
99 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
100 - Fix an assertion failure that could occur under high DNS load.
101 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
102 diagnosed and fixed by "cypherpunks".
104 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
105 - Fix a bug that could lead to a relay crashing with an assertion
106 failure if a buffer of exactly the wrong layout was passed to
107 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
108 0.2.0.10-alpha. Patch from 'cypherpunks'.
109 - Do not assert if the 'data' pointer on a buffer is advanced to the
110 very end of the buffer; log a BUG message instead. Only assert if
111 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
113 o Minor features (geoip):
114 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
115 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
118 Changes in version 0.2.5.10 - 2014-10-24
119 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
121 It adds several new security features, including improved
122 denial-of-service resistance for relays, new compiler hardening
123 options, and a system-call sandbox for hardened installations on Linux
124 (requires seccomp2). The controller protocol has several new features,
125 resolving IPv6 addresses should work better than before, and relays
126 should be a little more CPU-efficient. We've added support for more
127 OpenBSD and FreeBSD transparent proxy types. We've improved the build
128 system and testing infrastructure to allow unit testing of more parts
129 of the Tor codebase. Finally, we've addressed several nagging pluggable
130 transport usability issues, and included numerous other small bugfixes
131 and features mentioned below.
133 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
134 have accumulated many known flaws; everyone should upgrade.
136 o Major features (security):
137 - The ntor handshake is now on-by-default, no matter what the
138 directory authorities recommend. Implements ticket 8561.
139 - Make the "tor-gencert" tool used by directory authority operators
140 create 2048-bit signing keys by default (rather than 1024-bit, since
141 1024-bit is uncomfortably small these days). Addresses ticket 10324.
142 - Warn about attempts to run hidden services and relays in the same
143 process: that's probably not a good idea. Closes ticket 12908.
144 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
145 today support TLS 1.0 or later, so we can safely turn off support
146 for this old (and insecure) protocol. Fixes bug 13426.
148 o Major features (relay security, DoS-resistance):
149 - When deciding whether we have run out of memory and we need to
150 close circuits, also consider memory allocated in buffers for
151 streams attached to each circuit.
153 This change, which extends an anti-DoS feature introduced in
154 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
155 better resist more memory-based DoS attacks than before. Since the
156 MaxMemInCellQueues option now applies to all queues, it is renamed
157 to MaxMemInQueues. This feature fixes bug 10169.
158 - Avoid hash-flooding denial-of-service attacks by using the secure
159 SipHash-2-4 hash function for our hashtables. Without this
160 feature, an attacker could degrade performance of a targeted
161 client or server by flooding their data structures with a large
162 number of entries to be stored at the same hash table position,
163 thereby slowing down the Tor instance. With this feature, hash
164 table positions are derived from a randomized cryptographic key,
165 and an attacker cannot predict which entries will collide. Closes
167 - If you don't specify MaxMemInQueues yourself, Tor now tries to
168 pick a good value based on your total system memory. Previously,
169 the default was always 8 GB. You can still override the default by
170 setting MaxMemInQueues yourself. Resolves ticket 11396.
172 o Major features (bridges and pluggable transports):
173 - Add support for passing arguments to managed pluggable transport
174 proxies. Implements ticket 3594.
175 - Bridges now track GeoIP information and the number of their users
176 even when pluggable transports are in use, and report usage
177 statistics in their extra-info descriptors. Resolves tickets 4773
179 - Don't launch pluggable transport proxies if we don't have any
180 bridges configured that would use them. Now we can list many
181 pluggable transports, and Tor will dynamically start one when it
182 hears a bridge address that needs it. Resolves ticket 5018.
183 - The bridge directory authority now assigns status flags (Stable,
184 Guard, etc) to bridges based on thresholds calculated over all
185 Running bridges. Now bridgedb can finally make use of its features
186 to e.g. include at least one Stable bridge in its answers. Fixes
189 o Major features (controller):
190 - Extend ORCONN controller event to include an "ID" parameter,
191 and add four new controller event types CONN_BW, CIRC_BW,
192 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
193 The new events are emitted in private Tor networks only, with the
194 goal of being able to better track performance and load during
195 full-network simulations. Implements proposal 218 and ticket 7359.
197 o Major features (relay performance):
198 - Speed up server-side lookups of rendezvous and introduction point
199 circuits by using hashtables instead of linear searches. These
200 functions previously accounted between 3 and 7% of CPU usage on
201 some busy relays. Resolves ticket 9841.
202 - Avoid wasting CPU when extending a circuit over a channel that is
203 nearly out of circuit IDs. Previously, we would do a linear scan
204 over possible circuit IDs before finding one or deciding that we
205 had exhausted our possibilities. Now, we try at most 64 random
206 circuit IDs before deciding that we probably won't succeed. Fixes
207 a possible root cause of ticket 11553.
209 o Major features (seccomp2 sandbox, Linux only):
210 - Use the seccomp2 syscall filtering facility on Linux to limit
211 which system calls Tor can invoke. This is an experimental,
212 Linux-only feature to provide defense-in-depth against unknown
213 attacks. To try turning it on, set "Sandbox 1" in your torrc
214 file. Please be ready to report bugs. We hope to add support
215 for better sandboxing in the future, including more fine-grained
216 filters, better division of responsibility, and support for more
217 platforms. This work has been done by Cristian-Matei Toader for
218 Google Summer of Code. Resolves tickets 11351 and 11465.
220 o Major features (testing networks):
221 - Make testing Tor networks bootstrap better: lower directory fetch
222 retry schedules and maximum interval without directory requests,
223 and raise maximum download tries. Implements ticket 6752.
224 - Add make target 'test-network' to run tests on a Chutney network.
225 Implements ticket 8530.
227 o Major features (other):
228 - On some platforms (currently: recent OSX versions, glibc-based
229 platforms that support the ELF format, and a few other
230 Unix-like operating systems), Tor can now dump stack traces
231 when a crash occurs or an assertion fails. By default, traces
232 are dumped to stderr (if possible) and to any logs that are
233 reporting errors. Implements ticket 9299.
235 o Deprecated versions:
236 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
237 attention for some while.
239 o Major bugfixes (security, directory authorities):
240 - Directory authorities now include a digest of each relay's
241 identity key as a part of its microdescriptor.
243 This is a workaround for bug 11743 (reported by "cypherpunks"),
244 where Tor clients do not support receiving multiple
245 microdescriptors with the same SHA256 digest in the same
246 consensus. When clients receive a consensus like this, they only
247 use one of the relays. Without this fix, a hostile relay could
248 selectively disable some client use of target relays by
249 constructing a router descriptor with a different identity and the
250 same microdescriptor parameters and getting the authorities to
251 list it in a microdescriptor consensus. This fix prevents an
252 attacker from causing a microdescriptor collision, because the
253 router's identity is not forgeable.
255 o Major bugfixes (openssl bug workaround):
256 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
257 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
258 bug 13471. This is a workaround for an OpenSSL bug.
260 o Major bugfixes (client):
261 - Perform circuit cleanup operations even when circuit
262 construction operations are disabled (because the network is
263 disabled, or because there isn't enough directory information).
264 Previously, when we were not building predictive circuits, we
265 were not closing expired circuits either. Fixes bug 8387; bugfix on
266 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
267 became more strict about when we have "enough directory information
270 o Major bugfixes (client, pluggable transports):
271 - When managing pluggable transports, use OS notification facilities
272 to learn if they have crashed, and don't attempt to kill any
273 process that has already exited. Fixes bug 8746; bugfix
276 o Major bugfixes (relay denial of service):
277 - Instead of writing destroy cells directly to outgoing connection
278 buffers, queue them and intersperse them with other outgoing cells.
279 This can prevent a set of resource starvation conditions where too
280 many pending destroy cells prevent data cells from actually getting
281 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
282 bugfix on 0.2.0.1-alpha.
284 o Major bugfixes (relay):
285 - Avoid queuing or sending destroy cells for circuit ID zero when we
286 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
287 Found and fixed by "cypherpunks".
288 - Fix ORPort reachability detection on relays running behind a
289 proxy, by correctly updating the "local" mark on the controlling
290 channel when changing the address of an or_connection_t after the
291 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
292 - Use a direct dirport connection when uploading non-anonymous
293 descriptors to the directory authorities. Previously, relays would
294 incorrectly use tunnel connections under a fairly wide variety of
295 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
296 - When a circuit accidentally has the same circuit ID for its
297 forward and reverse direction, correctly detect the direction of
298 cells using that circuit. Previously, this bug made roughly one
299 circuit in a million non-functional. Fixes bug 12195; this is a
300 bugfix on every version of Tor.
302 o Minor features (security):
303 - New --enable-expensive-hardening option to enable security
304 hardening options that consume nontrivial amounts of CPU and
305 memory. Right now, this includes AddressSanitizer and UbSan, which
306 are supported in newer versions of GCC and Clang. Closes ticket
308 - Authorities now assign the Guard flag to the fastest 25% of the
309 network (it used to be the fastest 50%). Also raise the consensus
310 weight that guarantees the Guard flag from 250 to 2000. For the
311 current network, this results in about 1100 guards, down from 2500.
312 This step paves the way for moving the number of entry guards
313 down to 1 (proposal 236) while still providing reasonable expected
314 performance for most users. Implements ticket 12690.
316 o Minor features (security, memory management):
317 - Memory allocation tricks (mempools and buffer freelists) are now
318 disabled by default. You can turn them back on with
319 --enable-mempools and --enable-buf-freelists respectively. We're
320 disabling these features because malloc performance is good enough
321 on most platforms, and a similar feature in OpenSSL exacerbated
322 exploitation of the Heartbleed attack. Resolves ticket 11476.
324 o Minor features (bridge client):
325 - Report a more useful failure message when we can't connect to a
326 bridge because we don't have the right pluggable transport
327 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
329 o Minor features (bridge):
330 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
331 cookie file for the ExtORPort g+r by default.
333 o Minor features (bridges, pluggable transports):
334 - Bridges now write the SHA1 digest of their identity key
335 fingerprint (that is, a hash of a hash of their public key) to
336 notice-level logs, and to a new hashed-fingerprint file. This
337 information will help bridge operators look up their bridge in
338 Globe and similar tools. Resolves ticket 10884.
339 - Improve the message that Tor displays when running as a bridge
340 using pluggable transports without an Extended ORPort listener.
341 Also, log the message in the log file too. Resolves ticket 11043.
342 - Add threshold cutoffs to the networkstatus document created by
343 the Bridge Authority. Fixes bug 1117.
344 - On Windows, spawn background processes using the CREATE_NO_WINDOW
345 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
346 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
347 Vidalia set this option for us.) Implements ticket 10297.
349 o Minor features (build):
350 - The configure script has a --disable-seccomp option to turn off
351 support for libseccomp on systems that have it, in case it (or
352 Tor's use of it) is broken. Resolves ticket 11628.
353 - Assume that a user using ./configure --host wants to cross-compile,
354 and give an error if we cannot find a properly named
355 tool-chain. Add a --disable-tool-name-check option to proceed
356 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
357 - If we run ./configure and the compiler recognizes -fstack-protector
358 but the linker rejects it, warn the user about a potentially missing
359 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
360 - Add support for `--library-versions` flag. Implements ticket 6384.
361 - Return the "unexpected sendme" warnings to a warn severity, but make
362 them rate limited, to help diagnose ticket 8093.
363 - Detect a missing asciidoc, and warn the user about it, during
364 configure rather than at build time. Fixes issue 6506. Patch from
367 o Minor features (client):
368 - Add a new option, PredictedPortsRelevanceTime, to control how long
369 after having received a request to connect to a given port Tor
370 will try to keep circuits ready in anticipation of future requests
371 for that port. Patch from "unixninja92"; implements ticket 9176.
373 o Minor features (config options and command line):
374 - Add an --allow-missing-torrc commandline option that tells Tor to
375 run even if the configuration file specified by -f is not available.
376 Implements ticket 10060.
377 - Add support for the TPROXY transparent proxying facility on Linux.
378 See documentation for the new TransProxyType option for more
379 details. Implementation by "thomo". Closes ticket 10582.
381 o Minor features (config options):
382 - Config (torrc) lines now handle fingerprints which are missing
383 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
384 - Support a --dump-config option to print some or all of the
385 configured options. Mainly useful for debugging the command-line
386 option parsing code. Helps resolve ticket 4647.
387 - Raise awareness of safer logging: notify user of potentially
388 unsafe config options, like logging more verbosely than severity
389 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
390 - Add a new configuration option TestingV3AuthVotingStartOffset
391 that bootstraps a network faster by changing the timing for
392 consensus votes. Addresses ticket 8532.
393 - Add a new torrc option "ServerTransportOptions" that allows
394 bridge operators to pass configuration parameters to their
395 pluggable transports. Resolves ticket 8929.
396 - The config (torrc) file now accepts bandwidth and space limits in
397 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
398 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
401 o Minor features (controller):
402 - Make the entire exit policy available from the control port via
403 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
405 - Because of the fix for ticket 11396, the real limit for memory
406 usage may no longer match the configured MaxMemInQueues value. The
407 real limit is now exposed via GETINFO limits/max-mem-in-queues.
408 - Add a new "HS_DESC" controller event that reports activities
409 related to hidden service descriptors. Resolves ticket 8510.
410 - New "DROPGUARDS" controller command to forget all current entry
411 guards. Not recommended for ordinary use, since replacing guards
412 too frequently makes several attacks easier. Resolves ticket 9934;
414 - Implement the TRANSPORT_LAUNCHED control port event that
415 notifies controllers about new launched pluggable
416 transports. Resolves ticket 5609.
418 o Minor features (diagnostic):
419 - When logging a warning because of bug 7164, additionally check the
420 hash table for consistency (as proposed on ticket 11737). This may
421 help diagnose bug 7164.
422 - When we log a heartbeat, log how many one-hop circuits we have
423 that are at least 30 minutes old, and log status information about
424 a few of them. This is an attempt to track down bug 8387.
425 - When encountering an unexpected CR while writing text to a file on
426 Windows, log the name of the file. Should help diagnosing
428 - Give more specific warnings when a client notices that an onion
429 handshake has failed. Fixes ticket 9635.
430 - Add significant new logging code to attempt to diagnose bug 12184,
431 where relays seem to run out of available circuit IDs.
432 - Improve the diagnostic log message for bug 8387 even further to
433 try to improve our odds of figuring out why one-hop directory
434 circuits sometimes do not get closed.
435 - Add more log messages to diagnose bug 7164, which causes
436 intermittent "microdesc_free() called but md was still referenced"
437 warnings. We now include more information, to figure out why we
438 might be cleaning a microdescriptor for being too old if it's
439 still referenced by a live node_t object.
440 - Log current accounting state (bytes sent and received + remaining
441 time for the current accounting period) in the relay's heartbeat
442 message. Implements ticket 5526; patch from Peter Retzlaff.
444 o Minor features (geoip):
445 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
448 o Minor features (interface):
449 - Generate a warning if any ports are listed in the SocksPolicy,
450 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
451 AuthDirBadExit options. (These options only support address
452 ranges.) Fixes part of ticket 11108.
454 o Minor features (kernel API usage):
455 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
456 sockets in a single system call. Implements ticket 5129.
458 o Minor features (log messages):
459 - When ServerTransportPlugin is set on a bridge, Tor can write more
460 useful statistics about bridge use in its extrainfo descriptors,
461 but only if the Extended ORPort ("ExtORPort") is set too. Add a
462 log message to inform the user in this case. Resolves ticket 9651.
463 - When receiving a new controller connection, log the origin address.
464 Resolves ticket 9698; patch from "sigpipe".
465 - When logging OpenSSL engine status at startup, log the status of
466 more engines. Fixes ticket 10043; patch from Joshua Datko.
468 o Minor features (log verbosity):
469 - Demote the message that we give when a flushing connection times
470 out for too long from NOTICE to INFO. It was usually meaningless.
471 Resolves ticket 5286.
472 - Don't log so many notice-level bootstrapping messages at startup
473 about downloading descriptors. Previously, we'd log a notice
474 whenever we learned about more routers. Now, we only log a notice
475 at every 5% of progress. Fixes bug 9963.
476 - Warn less verbosely when receiving a malformed
477 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
479 o Minor features (performance):
480 - If we're using the pure-C 32-bit curve25519_donna implementation
481 of curve25519, build it with the -fomit-frame-pointer option to
482 make it go faster on register-starved hosts. This improves our
483 handshake performance by about 6% on i386 hosts without nacl.
486 o Minor features (relay):
487 - If a circuit timed out for at least 3 minutes, check if we have a
488 new external IP address, and publish a new descriptor with the new
489 IP address if it changed. Resolves ticket 2454.
491 o Minor features (testing):
492 - If Python is installed, "make check" now runs extra tests beyond
493 the unit test scripts.
494 - When bootstrapping a test network, sometimes very few relays get
495 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
496 specify a set of relays which should be voted Guard regardless of
497 their uptime or bandwidth. Addresses ticket 9206.
499 o Minor features (transparent proxy, *BSD):
500 - Support FreeBSD's ipfw firewall interface for TransPort ports on
501 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
502 10267; patch from "yurivict".
503 - Support OpenBSD's divert-to rules with the pf firewall for
504 transparent proxy ports. To enable it, set "TransProxyType
505 pf-divert". This allows Tor to run a TransPort transparent proxy
506 port on OpenBSD 4.4 or later without root privileges. See the
507 pf.conf(5) manual page for information on configuring pf to use
508 divert-to rules. Closes ticket 10896; patch from Dana Koch.
510 o Minor bugfixes (bridge client):
511 - Stop accepting bridge lines containing hostnames. Doing so would
512 cause clients to perform DNS requests on the hostnames, which was
513 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
515 o Minor bugfixes (bridges):
516 - Avoid potential crashes or bad behavior when launching a
517 server-side managed proxy with ORPort or ExtORPort temporarily
518 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
519 - Fix a bug where the first connection works to a bridge that uses a
520 pluggable transport with client-side parameters, but we don't send
521 the client-side parameters on subsequent connections. (We don't
522 use any pluggable transports with client-side parameters yet,
523 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
524 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
526 o Minor bugfixes (build, auxiliary programs):
527 - Stop preprocessing the "torify" script with autoconf, since
528 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
530 - The tor-fw-helper program now follows the standard convention and
531 exits with status code "0" on success. Fixes bug 9030; bugfix on
532 0.2.3.1-alpha. Patch by Arlo Breault.
533 - Corrected ./configure advice for what openssl dev package you should
534 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
536 o Minor bugfixes (client):
537 - Avoid "Tried to open a socket with DisableNetwork set" warnings
538 when starting a client with bridges configured and DisableNetwork
539 set. (Tor launcher starts Tor with DisableNetwork set the first
540 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
541 - Improve the log message when we can't connect to a hidden service
542 because all of the hidden service directory nodes hosting its
543 descriptor are excluded. Improves on our fix for bug 10722, which
544 was a bugfix on 0.2.0.10-alpha.
545 - Raise a control port warning when we fail to connect to all of
546 our bridges. Previously, we didn't inform the controller, and
547 the bootstrap process would stall. Fixes bug 11069; bugfix on
549 - Exit immediately when a process-owning controller exits.
550 Previously, tor relays would wait for a little while after their
551 controller exited, as if they had gotten an INT signal -- but this
552 was problematic, since there was no feedback for the user. To do a
553 clean shutdown, controllers should send an INT signal and give Tor
554 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
555 - Stop attempting to connect to bridges before our pluggable
556 transports are configured (harmless but resulted in some erroneous
557 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
558 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
559 generating incorrect SOCKS5 responses, and confusing client
560 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
562 o Minor bugfixes (client, DNSPort):
563 - When using DNSPort, try to respond to AAAA requests with AAAA
564 answers. Previously, we hadn't looked at the request type when
565 deciding which answer type to prefer. Fixes bug 10468; bugfix on
567 - When receiving a DNS query for an unsupported record type, reply
568 with no answer rather than with a NOTIMPL error. This behavior
569 isn't correct either, but it will break fewer client programs, we
570 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
573 o Minor bugfixes (client, logging during bootstrap):
574 - Only report the first fatal bootstrap error on a given OR
575 connection. This stops us from telling the controller bogus error
576 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
577 - Avoid generating spurious warnings when starting with
578 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
581 o Minor bugfixes (closing OR connections):
582 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
583 check if it's an or_connection_t and correctly call
584 connection_or_close_for_error() rather than
585 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
587 - When closing all connections on setting DisableNetwork to 1, use
588 connection_or_close_normally() rather than closing OR connections
589 out from under the channel layer. Fixes bug 11306; bugfix on
592 o Minor bugfixes (code correctness):
593 - Previously we used two temporary files when writing descriptors to
594 disk; now we only use one. Fixes bug 1376.
595 - Remove an erroneous (but impossible and thus harmless) pointer
596 comparison that would have allowed compilers to skip a bounds
597 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
598 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
599 - Fix an always-true assertion in pluggable transports code so it
600 actually checks what it was trying to check. Fixes bug 10046;
601 bugfix on 0.2.3.9-alpha. Found by "dcb".
603 o Minor bugfixes (command line):
604 - Use a single command-line parser for parsing torrc options on the
605 command line and for finding special command-line options to avoid
606 inconsistent behavior for torrc option arguments that have the same
607 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
609 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
610 9573; bugfix on 0.0.9pre5.
612 o Minor bugfixes (compilation):
613 - Compile correctly with builds and forks of OpenSSL (such as
614 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
615 0.2.1.1-alpha. Patch from "dhill".
616 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
617 turned off (that is, without support for v2 link handshakes). Fixes
618 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
619 - In routerlist_assert_ok(), don't take the address of a
620 routerinfo's cache_info member unless that routerinfo is non-NULL.
621 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
622 - Fix a large number of false positive warnings from the clang
623 analyzer static analysis tool. This should make real warnings
624 easier for clang analyzer to find. Patch from "teor". Closes
626 - Resolve GCC complaints on OpenBSD about discarding constness in
627 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
628 on 0.1.1.23. Patch from Dana Koch.
629 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
630 treatment of long and time_t as comparable types. Fixes part of
631 bug 11633. Patch from Dana Koch.
632 - When deciding whether to build the 64-bit curve25519
633 implementation, detect platforms where we can compile 128-bit
634 arithmetic but cannot link it. Fixes bug 11729; bugfix on
635 0.2.4.8-alpha. Patch from "conradev".
636 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
637 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
638 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
640 - Build and run correctly on systems like OpenBSD-current that have
641 patched OpenSSL to remove get_cipher_by_char and/or its
642 implementations. Fixes issue 13325.
644 o Minor bugfixes (controller and command-line):
645 - If changing a config option via "setconf" fails in a recoverable
646 way, we used to nonetheless write our new control ports to the
647 file described by the "ControlPortWriteToFile" option. Now we only
648 write out that file if we successfully switch to the new config
649 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
651 o Minor bugfixes (directory server):
652 - No longer accept malformed http headers when parsing urls from
653 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
655 - When sending a compressed set of descriptors or microdescriptors,
656 make sure to finalize the zlib stream. Previously, we would write
657 all the compressed data, but if the last descriptor we wanted to
658 send was missing or too old, we would not mark the stream as
659 finished. This caused problems for decompression tools. Fixes bug
660 11648; bugfix on 0.1.1.23.
662 o Minor bugfixes (hidden service):
663 - Only retry attempts to connect to a chosen rendezvous point 8
664 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
666 o Minor bugfixes (interface):
667 - Reject relative control socket paths and emit a warning. Previously,
668 single-component control socket paths would be rejected, but Tor
669 would not log why it could not validate the config. Fixes bug 9258;
670 bugfix on 0.2.3.16-alpha.
672 o Minor bugfixes (log messages):
673 - Fix a bug where clients using bridges would report themselves
674 as 50% bootstrapped even without a live consensus document.
675 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
676 - Suppress a warning where, if there's only one directory authority
677 in the network, we would complain that votes and signatures cannot
678 be uploaded to other directory authorities. Fixes bug 10842;
679 bugfix on 0.2.2.26-beta.
680 - Report bootstrapping progress correctly when we're downloading
681 microdescriptors. We had updated our "do we have enough microdescs
682 to begin building circuits?" logic most recently in 0.2.4.10-alpha
683 (see bug 5956), but we left the bootstrap status event logic at
684 "how far through getting 1/4 of them are we?" Fixes bug 9958;
685 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
687 o Minor bugfixes (logging):
688 - Downgrade "Unexpected onionskin length after decryption" warning
689 to a protocol-warn, since there's nothing relay operators can do
690 about a client that sends them a malformed create cell. Resolves
691 bug 12996; bugfix on 0.0.6rc1.
692 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
693 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
694 - When logging information about an EXTEND2 or EXTENDED2 cell, log
695 their names correctly. Fixes part of bug 12700; bugfix
697 - When logging information about a relay cell whose command we don't
698 recognize, log its command as an integer. Fixes part of bug 12700;
699 bugfix on 0.2.1.10-alpha.
700 - Escape all strings from the directory connection before logging
701 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
702 - Squelch a spurious LD_BUG message "No origin circuit for
703 successful SOCKS stream" in certain hidden service failure cases;
705 - Downgrade the severity of the 'unexpected sendme cell from client'
706 from 'warn' to 'protocol warning'. Closes ticket 8093.
708 o Minor bugfixes (misc code correctness):
709 - In munge_extrainfo_into_routerinfo(), check the return value of
710 memchr(). This would have been a serious issue if we ever passed
711 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
713 - On the chance that somebody manages to build Tor on a
714 platform where time_t is unsigned, correct the way that
715 microdesc_add_to_cache() handles negative time arguments.
716 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
717 - Fix various instances of undefined behavior in channeltls.c,
718 tor_memmem(), and eventdns.c that would cause us to construct
719 pointers to memory outside an allocated object. (These invalid
720 pointers were not accessed, but C does not even allow them to
721 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
722 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
723 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
724 fix some miscellaneous errors in our tests and codebase. Fixes bug
725 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
726 - Always check return values for unlink, munmap, UnmapViewOfFile;
727 check strftime return values more often. In some cases all we can
728 do is report a warning, but this may help prevent deeper bugs from
729 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
731 - Fix numerous warnings from the clang "scan-build" static analyzer.
732 Some of these are programming style issues; some of them are false
733 positives that indicated awkward code; some are undefined behavior
734 cases related to constructing (but not using) invalid pointers;
735 some are assumptions about API behavior; some are (harmlessly)
736 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
737 correct; and one or two are genuine bugs that weren't reachable
738 from the rest of the program. Fixes bug 8793; bugfixes on many,
741 o Minor bugfixes (node selection):
742 - If ExcludeNodes is set, consider non-excluded hidden service
743 directory servers before excluded ones. Do not consider excluded
744 hidden service directory servers at all if StrictNodes is
745 set. (Previously, we would sometimes decide to connect to those
746 servers, and then realize before we initiated a connection that
747 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
749 - If we set the ExitNodes option but it doesn't include any nodes
750 that have the Exit flag, we would choose not to bootstrap. Now we
751 bootstrap so long as ExitNodes includes nodes which can exit to
752 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
754 o Minor bugfixes (performance):
755 - Avoid a bug where every successful connection made us recompute
756 the flag telling us whether we have sufficient information to
757 build circuits. Previously, we would forget our cached value
758 whenever we successfully opened a channel (or marked a router as
759 running or not running for any other reason), regardless of
760 whether we had previously believed the router to be running. This
761 forced us to run an expensive update operation far too often.
762 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
763 - Avoid using tor_memeq() for checking relay cell integrity. This
764 removes a possible performance bottleneck. Fixes part of bug
765 12169; bugfix on 0.2.1.31.
767 o Minor bugfixes (platform-specific):
768 - When dumping a malformed directory object to disk, save it in
769 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
771 - Don't report failures from make_socket_reuseable() on incoming
772 sockets on OSX: this can happen when incoming connections close
773 early. Fixes bug 10081.
775 o Minor bugfixes (pluggable transports):
776 - Avoid another 60-second delay when starting Tor in a pluggable-
777 transport-using configuration when we already have cached
778 descriptors for our bridges. Fixes bug 11965; bugfix
781 o Minor bugfixes (protocol correctness):
782 - When receiving a VERSIONS cell with an odd number of bytes, close
783 the connection immediately since the cell is malformed. Fixes bug
784 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
787 o Minor bugfixes (relay, other):
788 - We now drop CREATE cells for already-existent circuit IDs and for
789 zero-valued circuit IDs, regardless of other factors that might
790 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
792 - When rejecting DATA cells for stream_id zero, still count them
793 against the circuit's deliver window so that we don't fail to send
794 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
796 o Minor bugfixes (relay, threading):
797 - Check return code on spawn_func() in cpuworker code, so that we
798 don't think we've spawned a nonworking cpuworker and write junk to
799 it forever. Fix related to bug 4345; bugfix on all released Tor
800 versions. Found by "skruffy".
801 - Use a pthread_attr to make sure that spawn_func() cannot return an
802 error while at the same time launching a thread. Fix related to
803 bug 4345; bugfix on all released Tor versions. Reported
806 o Minor bugfixes (relays and bridges):
807 - Avoid crashing on a malformed resolv.conf file when running a
808 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
809 - Non-exit relays no longer launch mock DNS requests to check for
810 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
811 non-exit relays stopped servicing DNS requests. Fixes bug 965;
812 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
813 - Bridges now report complete directory request statistics. Related
814 to bug 5824; bugfix on 0.2.2.1-alpha.
815 - Bridges now never collect statistics that were designed for
816 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
818 o Minor bugfixes (testing):
819 - Fix all valgrind warnings produced by the unit tests. There were
820 over a thousand memory leak warnings previously, mostly produced
821 by forgetting to free things in the unit test code. Fixes bug
822 11618, bugfixes on many versions of Tor.
824 o Minor bugfixes (tor-fw-helper):
825 - Give a correct log message when tor-fw-helper fails to launch.
826 (Previously, we would say something like "tor-fw-helper sent us a
827 string we could not parse".) Fixes bug 9781; bugfix
830 o Minor bugfixes (trivial memory leaks):
831 - Fix a small memory leak when signing a directory object. Fixes bug
832 11275; bugfix on 0.2.4.13-alpha.
833 - Resolve some memory leaks found by coverity in the unit tests, on
834 exit in tor-gencert, and on a failure to compute digests for our
835 own keys when generating a v3 networkstatus vote. These leaks
836 should never have affected anyone in practice.
838 o Code simplification and refactoring:
839 - Remove some old fallback code designed to keep Tor clients working
840 in a network with only two working relays. Elsewhere in the code we
841 have long since stopped supporting such networks, so there wasn't
842 much point in keeping it around. Addresses ticket 9926.
843 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
844 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
845 - Extract the common duplicated code for creating a subdirectory
846 of the data directory and writing to a file in it. Fixes ticket
847 4282; patch from Peter Retzlaff.
848 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
849 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
850 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
851 - Add a set of accessor functions for the circuit timeout data
852 structure. Fixes ticket 6153; patch from "piet".
853 - Clean up exit paths from connection_listener_new(). Closes ticket
854 8789. Patch from Arlo Breault.
855 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
856 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
857 - Use a doubly-linked list to implement the global circuit list.
858 Resolves ticket 9108. Patch from Marek Majkowski.
859 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
860 - Remove constants and tests for PKCS1 padding; it's insecure and
861 shouldn't be used for anything new. Fixes bug 8792; patch
863 - Remove instances of strcpy() from the unit tests. They weren't
864 hurting anything, since they were only in the unit tests, but it's
865 embarassing to have strcpy() in the code at all, and some analysis
866 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
867 0.2.3.8-alpha. Patch from Arlo Breault.
868 - Remove is_internal_IP() function. Resolves ticket 4645.
869 - Remove unused function circuit_dump_by_chan from circuitlist.c.
870 Closes issue 9107; patch from "marek".
871 - Change our use of the ENUM_BF macro to avoid declarations that
873 - Get rid of router->address, since in all cases it was just the
874 string representation of router->addr. Resolves ticket 5528.
877 - Adjust the URLs in the README to refer to the new locations of
878 several documents on the website. Fixes bug 12830. Patch from
880 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
882 - Update manpage to describe some of the files you can expect to
883 find in Tor's DataDirectory. Addresses ticket 9839.
884 - Clean up several option names in the manpage to match their real
885 names, add the missing documentation for a couple of testing and
886 directory authority options, remove the documentation for a
887 V2-directory fetching option that no longer exists. Resolves
889 - Correct the documenation so that it lists the correct directory
890 for the stats files. (They are in a subdirectory called "stats",
892 - In the manpage, move more authority-only options into the
893 directory authority section so that operators of regular directory
894 caches don't get confused.
895 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
896 11061; bugfix on 0.2.4.7-alpha.
897 - Resolve warnings from Doxygen.
898 - Document in the manpage that "KBytes" may also be written as
899 "kilobytes" or "KB", that "Kbits" may also be written as
900 "kilobits", and so forth. Closes ticket 9222.
901 - Document that the ClientOnly config option overrides ORPort.
902 Our old explanation made ClientOnly sound as though it did
903 nothing at all. Resolves bug 9059.
904 - Explain that SocksPolicy, DirPolicy, and similar options don't
905 take port arguments. Fixes the other part of ticket 11108.
906 - Fix a comment about the rend_server_descriptor_t.protocols field
907 to more accurately describe its range. Also, make that field
908 unsigned, to more accurately reflect its usage. Fixes bug 9099;
909 bugfix on 0.2.1.5-alpha.
910 - Fix the manpage's description of HiddenServiceAuthorizeClient:
911 the maximum client name length is 16, not 19. Fixes bug 11118;
912 bugfix on 0.2.1.6-alpha.
915 - The contrib directory has been sorted and tidied. Before, it was
916 an unsorted dumping ground for useful and not-so-useful things.
917 Now, it is divided based on functionality, and the items which
918 seemed to be nonfunctional or useless have been removed. Resolves
919 ticket 8966; based on patches from "rl1987".
921 o Removed code and features:
922 - Clients now reject any directory authority certificates lacking
923 a dir-key-crosscert element. These have been included since
924 0.2.1.9-alpha, so there's no real reason for them to be optional
925 any longer. Completes proposal 157. Resolves ticket 10162.
926 - Remove all code that existed to support the v2 directory system,
927 since there are no longer any v2 directory authorities. Resolves
929 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
930 options, which were used for designating authorities as "Hidden
931 service authorities". There has been no use of hidden service
932 authorities since 0.2.2.1-alpha, when we stopped uploading or
933 downloading v0 hidden service descriptors. Fixes bug 10881; also
934 part of a fix for bug 10841.
935 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
936 and MTBF calculations, but that nobody was using. Fixes bug 11742.
937 - The TunnelDirConns and PreferTunnelledDirConns options no longer
938 exist; tunneled directory connections have been available since
939 0.1.2.5-alpha, and turning them off is not a good idea. This is a
940 brute-force fix for 10849, where "TunnelDirConns 0" would break
942 - Remove all code for the long unused v1 directory protocol.
943 Resolves ticket 11070.
944 - Remove all remaining code related to version-0 hidden service
945 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
946 the rest of bug 10841.
947 - Remove migration code from when we renamed the "cached-routers"
948 file to "cached-descriptors" back in 0.2.0.8-alpha. This
949 incidentally resolves ticket 6502 by cleaning up the related code
950 a bit. Patch from Akshay Hebbar.
952 o Test infrastructure:
953 - Tor now builds each source file in two modes: a mode that avoids
954 exposing identifiers needlessly, and another mode that exposes
955 more identifiers for testing. This lets the compiler do better at
956 optimizing the production code, while enabling us to take more
957 radical measures to let the unit tests test things.
958 - The production builds no longer include functions used only in
959 the unit tests; all functions exposed from a module only for
960 unit-testing are now static in production builds.
961 - Add an --enable-coverage configuration option to make the unit
962 tests (and a new src/or/tor-cov target) to build with gcov test
964 - Update to the latest version of tinytest.
965 - Improve the tinytest implementation of string operation tests so
966 that comparisons with NULL strings no longer crash the tests; they
967 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
968 - New macros in test.h to simplify writing mock-functions for unit
969 tests. Part of ticket 11507. Patch from Dana Koch.
970 - We now have rudimentary function mocking support that our unit
971 tests can use to test functions in isolation. Function mocking
972 lets the tests temporarily replace a function's dependencies with
973 stub functions, so that the tests can check the function without
974 invoking the other functions it calls.
977 - Complete tests for the status.c module. Resolves ticket 11507.
978 Patch from Dana Koch.
979 - Add more unit tests for the <circid,channel>->circuit map, and
980 the destroy-cell-tracking code to fix bug 7912.
981 - Unit tests for failing cases of the TAP onion handshake.
982 - More unit tests for address-manipulation functions.
984 o Distribution (systemd):
985 - Include a tor.service file in contrib/dist for use with systemd.
986 Some distributions will be able to use this file unmodified;
987 others will need to tweak it, or write their own. Patch from Jamie
988 Nguyen; resolves ticket 8368.
989 - Verify configuration file via ExecStartPre in the systemd unit
990 file. Patch from intrigeri; resolves ticket 12730.
991 - Explicitly disable RunAsDaemon in the systemd unit file. Our
992 current systemd unit uses "Type = simple", so systemd does not
993 expect tor to fork. If the user has "RunAsDaemon 1" in their
994 torrc, then things won't work as expected. This is e.g. the case
995 on Debian (and derivatives), since there we pass "--defaults-torrc
996 /usr/share/tor/tor-service-defaults-torrc" (that contains
997 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1001 Changes in version 0.2.4.25 - 2014-10-20
1002 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1003 (even though POODLE does not affect Tor). It also works around a crash
1004 bug caused by some operating systems' response to the "POODLE" attack
1005 (which does affect Tor).
1007 o Major security fixes (also in 0.2.5.9-rc):
1008 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1009 today support TLS 1.0 or later, so we can safely turn off support
1010 for this old (and insecure) protocol. Fixes bug 13426.
1012 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1013 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1014 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1015 13471. This is a workaround for an OpenSSL bug.
1018 Changes in version 0.2.4.24 - 2014-09-22
1019 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1020 connecting to hidden services, and it updates the location of one of
1021 the directory authorities.
1024 - Clients now send the correct address for their chosen rendezvous
1025 point when trying to access a hidden service. They used to send
1026 the wrong address, which would still work some of the time because
1027 they also sent the identity digest of the rendezvous point, and if
1028 the hidden service happened to try connecting to the rendezvous
1029 point from a relay that already had a connection open to it,
1030 the relay would reuse that connection. Now connections to hidden
1031 services should be more robust and faster. Also, this bug meant
1032 that clients were leaking to the hidden service whether they were
1033 on a little-endian (common) or big-endian (rare) system, which for
1034 some users might have reduced their anonymity. Fixes bug 13151;
1035 bugfix on 0.2.1.5-alpha.
1037 o Directory authority changes:
1038 - Change IP address for gabelmoo (v3 directory authority).
1040 o Minor features (geoip):
1041 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1045 Changes in version 0.2.4.23 - 2014-07-28
1046 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1047 guard rotation, and also backports several important fixes from the
1048 Tor 0.2.5 alpha release series.
1051 - Clients now look at the "usecreatefast" consensus parameter to
1052 decide whether to use CREATE_FAST or CREATE cells for the first hop
1053 of their circuit. This approach can improve security on connections
1054 where Tor's circuit handshake is stronger than the available TLS
1055 connection security levels, but the tradeoff is more computational
1056 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1057 - Make the number of entry guards configurable via a new
1058 NumEntryGuards consensus parameter, and the number of directory
1059 guards configurable via a new NumDirectoryGuards consensus
1060 parameter. Implements ticket 12688.
1063 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1064 implementation that caused incorrect results on 32-bit
1065 implementations when certain malformed inputs were used along with
1066 a small class of private ntor keys. This bug does not currently
1067 appear to allow an attacker to learn private keys or impersonate a
1068 Tor server, but it could provide a means to distinguish 32-bit Tor
1069 implementations from 64-bit Tor implementations. Fixes bug 12694;
1070 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1074 - Warn and drop the circuit if we receive an inbound 'relay early'
1075 cell. Those used to be normal to receive on hidden service circuits
1076 due to bug 1038, but the buggy Tor versions are long gone from
1077 the network so we can afford to resume watching for them. Resolves
1078 the rest of bug 1038; bugfix on 0.2.1.19.
1079 - Correct a confusing error message when trying to extend a circuit
1080 via the control protocol but we don't know a descriptor or
1081 microdescriptor for one of the specified relays. Fixes bug 12718;
1082 bugfix on 0.2.3.1-alpha.
1083 - Avoid an illegal read from stack when initializing the TLS
1084 module using a version of OpenSSL without all of the ciphers
1085 used by the v2 link handshake. Fixes bug 12227; bugfix on
1086 0.2.4.8-alpha. Found by "starlight".
1089 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1093 Changes in version 0.2.4.22 - 2014-05-16
1094 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
1095 alpha release series. These include blocking all authority signing
1096 keys that may have been affected by the OpenSSL "heartbleed" bug,
1097 choosing a far more secure set of TLS ciphersuites by default, closing
1098 a couple of memory leaks that could be used to run a target relay out
1099 of RAM, and several others.
1101 o Major features (security, backport from 0.2.5.4-alpha):
1102 - Block authority signing keys that were used on authorities
1103 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1104 don't have any evidence that these keys _were_ compromised; we're
1105 doing this to be prudent.) Resolves ticket 11464.
1107 o Major bugfixes (security, OOM):
1108 - Fix a memory leak that could occur if a microdescriptor parse
1109 fails during the tokenizing step. This bug could enable a memory
1110 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1113 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
1114 - The relay ciphersuite list is now generated automatically based on
1115 uniform criteria, and includes all OpenSSL ciphersuites with
1116 acceptable strength and forward secrecy. Previously, we had left
1117 some perfectly fine ciphersuites unsupported due to omission or
1118 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1119 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1120 - Relays now trust themselves to have a better view than clients of
1121 which TLS ciphersuites are better than others. (Thanks to bug
1122 11513, the relay list is now well-considered, whereas the client
1123 list has been chosen mainly for anti-fingerprinting purposes.)
1124 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1125 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1126 AES128. Resolves ticket 11528.
1127 - Clients now try to advertise the same list of ciphersuites as
1128 Firefox 28. This change enables selection of (fast) GCM
1129 ciphersuites, disables some strange old ciphers, and stops
1130 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1131 Resolves ticket 11438.
1133 o Minor bugfixes (configuration, security):
1134 - When running a hidden service, do not allow TunneledDirConns 0:
1135 trying to set that option together with a hidden service would
1136 otherwise prevent the hidden service from running, and also make
1137 it publish its descriptors directly over HTTP. Fixes bug 10849;
1138 bugfix on 0.2.1.1-alpha.
1140 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1141 - Avoid sending a garbage value to the controller when a circuit is
1142 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1144 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1145 - Stop leaking memory when we successfully resolve a PTR record.
1146 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1148 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1149 - Avoid 60-second delays in the bootstrapping process when Tor is
1150 launching for a second time while using bridges. Fixes bug 9229;
1151 bugfix on 0.2.0.3-alpha.
1153 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
1154 - Give the correct URL in the warning message when trying to run a
1155 relay on an ancient version of Windows. Fixes bug 9393.
1157 o Minor bugfixes (compilation):
1158 - Fix a compilation error when compiling with --disable-curve25519.
1159 Fixes bug 9700; bugfix on 0.2.4.17-rc.
1162 - Downgrade the warning severity for the the "md was still
1163 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
1164 for trying to diagnose this bug, and the current warning in
1165 earlier versions of tor achieves nothing useful. Addresses warning
1168 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
1169 - When we run out of usable circuit IDs on a channel, log only one
1170 warning for the whole channel, and describe how many circuits
1171 there were on the channel. Fixes part of ticket 11553.
1173 o Minor features (security, backport from 0.2.5.4-alpha):
1174 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
1175 leave the default at 8GBytes), to better support Raspberry Pi
1176 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
1178 o Documentation (backport from 0.2.5.4-alpha):
1179 - Correctly document that we search for a system torrc file before
1180 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1184 Changes in version 0.2.4.21 - 2014-02-28
1185 Tor 0.2.4.21 further improves security against potential adversaries who
1186 find breaking 1024-bit crypto doable, and backports several stability
1187 and robustness patches from the 0.2.5 branch.
1189 o Major features (client security):
1190 - When we choose a path for a 3-hop circuit, make sure it contains
1191 at least one relay that supports the NTor circuit extension
1192 handshake. Otherwise, there is a chance that we're building
1193 a circuit that's worth attacking by an adversary who finds
1194 breaking 1024-bit crypto doable, and that chance changes the game
1195 theory. Implements ticket 9777.
1198 - Do not treat streams that fail with reason
1199 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1200 since it could also indicate an ENETUNREACH connection error. Fixes
1201 part of bug 10777; bugfix on 0.2.4.8-alpha.
1203 o Code simplification and refactoring:
1204 - Remove data structures which were introduced to implement the
1205 CellStatistics option: they are now redundant with the new timestamp
1206 field in the regular packed_cell_t data structure, which we did
1207 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
1210 - Always clear OpenSSL bignums before freeing them -- even bignums
1211 that don't contain secrets. Resolves ticket 10793. Patch by
1213 - Build without warnings under clang 3.4. (We have some macros that
1214 define static functions only some of which will get used later in
1215 the module. Starting with clang 3.4, these give a warning unless the
1216 unused attribute is set on them.) Resolves ticket 10904.
1217 - Update geoip and geoip6 files to the February 7 2014 Maxmind
1218 GeoLite2 Country database.
1221 - Set the listen() backlog limit to the largest actually supported
1222 on the system, not to the value in a header file. Fixes bug 9716;
1223 bugfix on every released Tor.
1224 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1225 exit node as a NOROUTE error, not an INTERNAL error, since they
1226 can apparently happen when trying to connect to the wrong sort
1227 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1228 - Fix build warnings about missing "a2x" comment when building the
1229 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1230 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1231 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1232 not entirely remove it from the connection lists. Fixes bug 9602;
1233 bugfix on 0.2.4.4-alpha.
1234 - Fix a segmentation fault in our benchmark code when running with
1235 Fedora's OpenSSL package, or any other OpenSSL that provides
1236 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1237 - Turn "circuit handshake stats since last time" log messages into a
1238 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1240 o Documentation fixes:
1241 - Document that all but one DirPort entry must have the NoAdvertise
1242 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1245 Changes in version 0.2.4.20 - 2013-12-22
1246 Tor 0.2.4.20 fixes potentially poor random number generation for users
1247 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
1248 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
1249 and 4) have no state file in their DataDirectory (as would happen on
1250 first start). Users who generated relay or hidden service identity
1251 keys in such a situation should discard them and generate new ones.
1253 This release also fixes a logic error that caused Tor clients to build
1254 many more preemptive circuits than they actually need.
1257 - Do not allow OpenSSL engines to replace the PRNG, even when
1258 HardwareAccel is set. The only default builtin PRNG engine uses
1259 the Intel RDRAND instruction to replace the entire PRNG, and
1260 ignores all attempts to seed it with more entropy. That's
1261 cryptographically stupid: the right response to a new alleged
1262 entropy source is never to discard all previously used entropy
1263 sources. Fixes bug 10402; works around behavior introduced in
1264 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1266 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1267 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1268 - Avoid launching spurious extra circuits when a stream is pending.
1269 This fixes a bug where any circuit that _wasn't_ unusable for new
1270 streams would be treated as if it were, causing extra circuits to
1271 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1274 - Avoid a crash bug when starting with a corrupted microdescriptor
1275 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1276 - If we fail to dump a previously cached microdescriptor to disk, avoid
1277 freeing duplicate data later on. Fixes bug 10423; bugfix on
1278 0.2.4.13-alpha. Spotted by "bobnomnom".
1281 Changes in version 0.2.4.19 - 2013-12-11
1282 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
1283 (1986-2013). Aaron worked on diverse projects including helping to guide
1284 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
1285 transparency to the U.S government's PACER documents, and contributing
1286 design and development for Tor and Tor2Web. Aaron was one of the latest
1287 martyrs in our collective fight for civil liberties and human rights,
1288 and his death is all the more painful because he was one of us.
1290 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
1291 a new circuit handshake and link encryption that use ECC to provide
1292 better security and efficiency; makes relays better manage circuit
1293 creation requests; uses "directory guards" to reduce client enumeration
1294 risks; makes bridges collect and report statistics about the pluggable
1295 transports they support; cleans up and improves our geoip database;
1296 gets much closer to IPv6 support for clients, bridges, and relays; makes
1297 directory authorities use measured bandwidths rather than advertised
1298 ones when computing flags and thresholds; disables client-side DNS
1299 caching to reduce tracking risks; and fixes a big bug in bridge
1300 reachability testing. This release introduces two new design
1301 abstractions in the code: a new "channel" abstraction between circuits
1302 and or_connections to allow for implementing alternate relay-to-relay
1303 transports, and a new "circuitmux" abstraction storing the queue of
1304 circuits for a channel. The release also includes many stability,
1305 security, and privacy fixes.
1307 o Major features (new circuit handshake):
1308 - Tor now supports a new circuit extension handshake designed by Ian
1309 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1310 circuit extension handshake, later called "TAP", was a bit slow
1311 (especially on the relay side), had a fragile security proof, and
1312 used weaker keys than we'd now prefer. The new circuit handshake
1313 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1314 function, making it significantly more secure than the older
1315 handshake, and significantly faster. Tor can use one of two built-in
1316 pure-C curve25519-donna implementations by Adam Langley, or it
1317 can link against the "nacl" library for a tuned version if present.
1319 The built-in version is very fast for 64-bit systems when building
1320 with GCC. The built-in 32-bit version is still faster than the
1321 old TAP protocol, but using libnacl is better on most such hosts.
1323 Implements proposal 216; closes ticket 7202.
1325 o Major features (better link encryption):
1326 - Relays can now enable the ECDHE TLS ciphersuites when available
1327 and appropriate. These ciphersuites let us negotiate forward-secure
1328 TLS secret keys more safely and more efficiently than with our
1329 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1330 public relays prefer the (faster) P224 group, and bridges prefer
1331 the (more common) P256 group; you can override this with the
1334 This feature requires clients running 0.2.3.17-beta or later,
1335 and requires both sides to be running OpenSSL 1.0.0 or later
1336 with ECC support. OpenSSL 1.0.1, with the compile-time option
1337 "enable-ec_nistp_64_gcc_128", is highly recommended.
1339 Implements the relay side of proposal 198; closes ticket 7200.
1341 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1342 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1343 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1344 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1345 them to solve bug 6033.)
1347 o Major features (relay performance):
1348 - Instead of limiting the number of queued onionskins (aka circuit
1349 create requests) to a fixed, hard-to-configure number, we limit
1350 the size of the queue based on how many we expect to be able to
1351 process in a given amount of time. We estimate the time it will
1352 take to process an onionskin based on average processing time
1353 of previous onionskins. Closes ticket 7291. You'll never have to
1354 configure MaxOnionsPending again.
1355 - Relays process the new "NTor" circuit-level handshake requests
1356 with higher priority than the old "TAP" circuit-level handshake
1357 requests. We still process some TAP requests to not totally starve
1358 0.2.3 clients when NTor becomes popular. A new consensus parameter
1359 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1360 Implements ticket 9574.
1362 o Major features (client bootstrapping resilience):
1363 - Add a new "FallbackDir" torrc option to use when we can't use
1364 a directory mirror from the consensus (either because we lack a
1365 consensus, or because they're all down). Currently, all authorities
1366 are fallbacks by default, and there are no other default fallbacks,
1367 but that will change. This option will allow us to give clients a
1368 longer list of servers to try to get a consensus from when first
1369 connecting to the Tor network, and thereby reduce load on the
1370 directory authorities. Implements proposal 206, "Preconfigured
1371 directory sources for bootstrapping". We also removed the old
1372 "FallbackNetworkstatus" option, since we never got it working well
1373 enough to use it. Closes bug 572.
1374 - If we have no circuits open, use a relaxed timeout (the
1375 95th-percentile cutoff) until a circuit succeeds. This heuristic
1376 should allow Tor to succeed at building circuits even when the
1377 network connection drastically changes. Should help with bug 3443.
1379 o Major features (use of guards):
1380 - Support directory guards (proposal 207): when possible, clients now
1381 use their entry guards for non-anonymous directory requests. This
1382 can help prevent client enumeration. Note that this behavior only
1383 works when we have a usable consensus directory, and when options
1384 about what to download are more or less standard. In the future we
1385 should re-bootstrap from our guards, rather than re-bootstrapping
1386 from the preconfigured list of directory sources that ships with
1387 Tor. Resolves ticket 6526.
1388 - Raise the default time that a client keeps an entry guard from
1389 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1390 2012 paper. (We would make it even longer, but we need better client
1391 load balancing first.) Also, make the guard lifetime controllable
1392 via a new GuardLifetime torrc option and a GuardLifetime consensus
1393 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1395 o Major features (bridges with pluggable transports):
1396 - Bridges now report the pluggable transports they support to the
1397 bridge authority, so it can pass the supported transports on to
1398 bridgedb and/or eventually do reachability testing. Implements
1400 - Automatically forward the TCP ports of pluggable transport
1401 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1404 o Major features (geoip database):
1405 - Maxmind began labelling Tor relays as being in country "A1",
1406 which breaks by-country node selection inside Tor. Now we use a
1407 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1408 file with real country codes. This script fixes about 90% of "A1"
1409 entries automatically and uses manual country code assignments to
1410 fix the remaining 10%. See src/config/README.geoip for details.
1412 - Add GeoIP database for IPv6 addresses. The new config option
1414 - Update to the October 2 2013 Maxmind GeoLite Country database.
1416 o Major features (IPv6):
1417 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1418 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1419 to happen. Implements ticket 5535.
1420 - All kind of relays, not just bridges, can now advertise an IPv6
1421 OR port. Implements ticket 6362.
1422 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1423 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1424 exit policy reads as you would like: the address * applies to all
1425 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1426 addresses only. On the client side, you'll need to wait for enough
1427 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
1428 and use Socks5. Closes ticket 5547, implements proposal 117 as
1429 revised in proposal 208.
1430 - Bridge authorities now accept IPv6 bridge addresses and include
1431 them in network status documents. Implements ticket 5534.
1432 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
1434 o Major features (directory authorities):
1435 - Directory authorities now prefer using measured bandwidths to
1436 advertised ones when computing flags and thresholds. Resolves
1438 - Directory authorities that vote measured bandwidths about more
1439 than a threshold number of relays now treat relays with
1440 unmeasured bandwidths as having bandwidth 0 when computing their
1441 flags. Resolves ticket 8435.
1442 - Directory authorities now support a new consensus method (17)
1443 where they cap the published bandwidth of relays for which
1444 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1445 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1446 serve any v2 directory information. Now we can test disabling the
1447 old deprecated v2 directory format, and see whether doing so has
1448 any effect on network load. Begins to fix bug 6783.
1450 o Major features (build and portability):
1451 - Switch to a nonrecursive Makefile structure. Now instead of each
1452 Makefile.am invoking other Makefile.am's, there is a master
1453 Makefile.am that includes the others. This change makes our build
1454 process slightly more maintainable, and improves parallelism for
1455 building with make -j. Original patch by Stewart Smith; various
1456 fixes by Jim Meyering.
1457 - Where available, we now use automake's "silent" make rules by
1458 default, so that warnings are easier to spot. You can get the old
1459 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1460 - Resume building correctly with MSVC and Makefile.nmake. This patch
1461 resolves numerous bugs and fixes reported by ultramage, including
1462 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1464 o Security features:
1465 - Switch to a completely time-invariant approach for picking nodes
1466 weighted by bandwidth. Our old approach would run through the
1467 part of the loop after it had made its choice slightly slower
1468 than it ran through the part of the loop before it had made its
1469 choice. Addresses ticket 6538.
1470 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1471 by tor2web clients allows hidden services to identify tor2web
1472 clients through their repeated selection of the same rendezvous
1473 and introduction point circuit endpoints (their guards). Resolves
1476 o Major bugfixes (relay denial of service):
1477 - When we have too much memory queued in circuits (according to a new
1478 MaxMemInCellQueues option), close the circuits that have the oldest
1479 queued cells, on the theory that those are most responsible for
1480 us running low on memory. This prevents us from running out of
1481 memory as a relay if circuits fill up faster than they can be
1482 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
1483 Tor. This bug is a further fix beyond bug 6252, whose fix was
1484 merged into 0.2.3.21-rc.
1485 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1486 ID: these could be used to create unexpected streams and circuits
1487 which would count as "present" to some parts of Tor but "absent"
1488 to others, leading to zombie circuits and streams or to a bandwidth
1489 denial-of-service. Fixes bug 7889; bugfix on every released version
1490 of Tor. Reported by "oftc_must_be_destroyed".
1491 - Avoid a bug where our response to TLS renegotiation under certain
1492 network conditions could lead to a busy-loop, with 100% CPU
1493 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1495 o Major bugfixes (asserts, crashes, leaks):
1496 - Prevent the get_freelists() function from running off the end of
1497 the list of freelists if it somehow gets an unrecognized
1498 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1500 - Avoid a memory leak where we would leak a consensus body when we
1501 find that a consensus which we couldn't previously verify due to
1502 missing certificates is now verifiable. Fixes bug 8719; bugfix
1504 - If we are unable to save a microdescriptor to the journal, do not
1505 drop it from memory and then reattempt downloading it. Fixes bug
1506 9645; bugfix on 0.2.2.6-alpha.
1507 - Fix an assertion failure that would occur when disabling the
1508 ORPort setting on a running Tor process while accounting was
1509 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1510 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1511 when an exit connection with optimistic data succeeds immediately
1512 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1514 - Fix a memory leak that would occur whenever a configuration
1515 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1517 o Major bugfixes (relay rate limiting):
1518 - When a TLS write is partially successful but incomplete, remember
1519 that the flushed part has been flushed, and notice that bytes were
1520 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
1521 bugfix on Tor 0.1.0.5-rc.
1522 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1523 to 1GB/1GB. The previous defaults were intended to be "basically
1524 infinite", but it turns out they're now limiting our 100mbit+
1525 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1526 last time we raised it).
1527 - No longer stop reading or writing on cpuworker connections when
1528 our rate limiting buckets go empty. Now we should handle circuit
1529 handshake requests more promptly. Resolves bug 9731.
1531 o Major bugfixes (client-side privacy):
1532 - When we mark a circuit as unusable for new circuits, have it
1533 continue to be unusable for new circuits even if MaxCircuitDirtiness
1534 is increased too much at the wrong time, or the system clock jumps
1535 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1536 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1537 which have resolved to internal addresses") is set, apply that
1538 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1539 - When an exit relay rejects a stream with reason "exit policy", but
1540 we only know an exit policy summary (e.g. from the microdesc
1541 consensus) for it, do not mark the relay as useless for all exiting.
1542 Instead, mark just the circuit as unsuitable for that particular
1543 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1545 o Major bugfixes (stream isolation):
1546 - Allow applications to get proper stream isolation with
1547 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1548 username/password authentication also offer "no authentication". Tor
1549 had previously preferred "no authentication", so the applications
1550 never actually sent Tor their auth details. Now Tor selects
1551 username/password authentication if it's offered. You can disable
1552 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1553 bug 8117; bugfix on 0.2.3.3-alpha.
1554 - Follow the socks5 protocol when offering username/password
1555 authentication. The fix for bug 8117 exposed this bug, and it
1556 turns out real-world applications like Pidgin do care. Bugfix on
1557 0.2.3.2-alpha; fixes bug 8879.
1559 o Major bugfixes (client circuit building):
1560 - Alter circuit build timeout measurement to start at the point
1561 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1562 initialization). This should make our timeout measurements more
1563 uniform. Previously, we were sometimes including ORconn setup time
1564 in our circuit build time measurements. Should resolve bug 3443.
1565 - If the circuit build timeout logic is disabled (via the consensus,
1566 or because we are an authority), then don't build testing circuits.
1567 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1569 o Major bugfixes (client-side DNS):
1570 - Turn off the client-side DNS cache by default. Updating and using
1571 the DNS cache is now configurable on a per-client-port
1572 level. SOCKSPort, DNSPort, etc lines may now contain
1573 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1574 cache these types of DNS answers when we receive them from an
1575 exit node in response to an application request on this port, and
1576 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1577 cached DNS answers of these types, we shouldn't use them. It's
1578 potentially risky to use cached DNS answers at the client, since
1579 doing so can indicate to one exit what answers we've gotten
1580 for DNS lookups in the past. With IPv6, this becomes especially
1581 problematic. Using cached DNS answers for requests on the same
1582 circuit would present less linkability risk, since all traffic
1583 on a circuit is already linkable, but it would also provide
1584 little performance benefit: the exit node caches DNS replies
1585 too. Implements a simplified version of Proposal 205. Implements
1588 o Major bugfixes (hidden service privacy):
1589 - Limit hidden service descriptors to at most ten introduction
1590 points, to slow one kind of guard enumeration. Fixes bug 9002;
1591 bugfix on 0.1.1.11-alpha.
1593 o Major bugfixes (directory fetching):
1594 - If the time to download the next old-style networkstatus is in
1595 the future, do not decline to consider whether to download the
1596 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1598 - We used to always request authority certificates by identity digest,
1599 meaning we'd get the newest one even when we wanted one with a
1600 different signing key. Then we would complain about being given
1601 a certificate we already had, and never get the one we really
1602 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1603 resource to request the one we want. Fixes bug 5595; bugfix on
1606 o Major bugfixes (bridge reachability):
1607 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1608 previously they did not, which prevented them from receiving
1609 successful connections from relays for self-test or bandwidth
1610 testing. Also, when a relay is extending a circuit to a bridge,
1611 it needs to send a NETINFO cell, even when the bridge hasn't sent
1612 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1614 o Major bugfixes (control interface):
1615 - When receiving a new configuration file via the control port's
1616 LOADCONF command, do not treat the defaults file as absent.
1617 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1619 o Major bugfixes (directory authorities):
1620 - Stop marking every relay as having been down for one hour every
1621 time we restart a directory authority. These artificial downtimes
1622 were messing with our Stable and Guard flag calculations. Fixes
1623 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1624 - When computing directory thresholds, ignore any rejected-as-sybil
1625 nodes during the computation so that they can't influence Fast,
1626 Guard, etc. (We should have done this for proposal 109.) Fixes
1628 - When marking a node as a likely sybil, reset its uptime metrics
1629 to zero, so that it cannot time towards getting marked as Guard,
1630 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1632 - Fix a bug in the voting algorithm that could yield incorrect results
1633 when a non-naming authority declared too many flags. Fixes bug 9200;
1634 bugfix on 0.2.0.3-alpha.
1636 o Internal abstraction features:
1637 - Introduce new channel_t abstraction between circuits and
1638 or_connection_t to allow for implementing alternate OR-to-OR
1639 transports. A channel_t is an abstract object which can either be a
1640 cell-bearing channel, which is responsible for authenticating and
1641 handshaking with the remote OR and transmitting cells to and from
1642 it, or a listening channel, which spawns new cell-bearing channels
1643 at the request of remote ORs. Implements part of ticket 6465.
1644 - Make a channel_tls_t subclass of channel_t, adapting it to the
1645 existing or_connection_t code. The V2/V3 protocol handshaking
1646 code which formerly resided in command.c has been moved below the
1647 channel_t abstraction layer and may be found in channeltls.c now.
1648 Implements the rest of ticket 6465.
1649 - Introduce new circuitmux_t storing the queue of circuits for
1650 a channel; this encapsulates and abstracts the queue logic and
1651 circuit selection policy, and allows the latter to be overridden
1652 easily by switching out a policy object. The existing EWMA behavior
1653 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1655 o New build requirements:
1656 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1657 strongly recommended.
1658 - Tor maintainers now require Automake version 1.9 or later to build
1659 Tor from the Git repository. (Automake is not required when building
1660 from a source distribution.)
1662 o Minor features (protocol):
1663 - No longer include the "opt" prefix when generating routerinfos
1664 or v2 directories: it has been needless since Tor 0.1.2. Closes
1666 - Reject EXTEND cells sent to nonexistent streams. According to the
1667 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1668 we were only checking for stream IDs that were currently in use.
1669 Found while hunting for more instances of bug 6271. Bugfix on
1670 0.0.2pre8, which introduced incremental circuit construction.
1671 - Tor relays and clients now support a better CREATE/EXTEND cell
1672 format, allowing the sender to specify multiple address, identity,
1673 and handshake types. Implements Robert Ransom's proposal 200;
1675 - Reject as invalid most directory objects containing a NUL.
1676 Belt-and-suspender fix for bug 8037.
1678 o Minor features (security):
1679 - Clear keys and key-derived material left on the stack in
1680 rendservice.c and rendclient.c. Check return value of
1681 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
1682 These fixes should make us more forward-secure against cold-boot
1683 attacks and the like. Fixes bug 2385.
1684 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1685 Irix's random() only return 15 bits; Solaris's random() returns more
1686 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1687 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1689 o Minor features (control protocol):
1690 - Add a "GETINFO signal/names" control port command. Implements
1692 - Provide default values for all options via "GETINFO config/defaults".
1693 Implements ticket 4971.
1694 - Allow an optional $ before the node identity digest in the
1695 controller command GETINFO ns/id/<identity>, for consistency with
1696 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1697 - Add CACHED keyword to ADDRMAP events in the control protocol
1698 to indicate whether a DNS result will be cached or not. Resolves
1700 - Generate bootstrapping status update events correctly when fetching
1701 microdescriptors. Fixes bug 9927.
1703 o Minor features (path selection):
1704 - When deciding whether we have enough descriptors to build circuits,
1705 instead of looking at raw relay counts, look at which fraction
1706 of (bandwidth-weighted) paths we're able to build. This approach
1707 keeps clients from building circuits if their paths are likely to
1708 stand out statistically. The default fraction of paths needed is
1709 taken from the consensus directory; you can override it with the
1710 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1711 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1712 and we have GeoIP information, also exclude all nodes with unknown
1713 countries "??" and "A1". This behavior is controlled by the
1714 new GeoIPExcludeUnknown option: you can make such nodes always
1715 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1716 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1717 gets you the default behavior. Implements feature 7706.
1719 o Minor features (hidden services):
1720 - Improve circuit build timeout handling for hidden services.
1721 In particular: adjust build timeouts more accurately depending
1722 upon the number of hop-RTTs that a particular circuit type
1723 undergoes. Additionally, launch intro circuits in parallel
1724 if they timeout, and take the first one to reply as valid.
1725 - The Tor client now ignores sub-domain components of a .onion
1726 address. This change makes HTTP "virtual" hosting
1727 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1728 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1729 hosted on the same hidden service. Implements proposal 204.
1730 - Enable Tor to read configuration, state, and key information from
1731 a FIFO. Previously Tor would only read from files with a positive
1732 stat.st_size. Code from meejah; fixes bug 6044.
1734 o Minor features (clients):
1735 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
1736 microdescriptor-related dir requests, and only fall back to normal
1737 descriptors if none of their bridges can handle microdescriptors
1738 (as opposed to the fix in ticket 4013, which caused them to fall
1739 back to normal descriptors if *any* of their bridges preferred
1740 them). Resolves ticket 4994.
1741 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1742 TCP ports to forward. In the past it only accepted two ports:
1743 the ORPort and the DirPort.
1745 o Minor features (protecting client timestamps):
1746 - Clients no longer send timestamps in their NETINFO cells. These were
1747 not used for anything, and they provided one small way for clients
1748 to be distinguished from each other as they moved from network to
1749 network or behind NAT. Implements part of proposal 222.
1750 - Clients now round timestamps in INTRODUCE cells down to the nearest
1751 10 minutes. If a new Support022HiddenServices option is set to 0, or
1752 if it's set to "auto" and the feature is disabled in the consensus,
1753 the timestamp is sent as 0 instead. Implements part of proposal 222.
1754 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1755 a big deal from a security point of view, but it achieves no actual
1756 good purpose, and isn't needed. Implements part of proposal 222.
1757 - Reduce down accuracy of timestamps in hidden service descriptors.
1758 Implements part of proposal 222.
1760 o Minor features (bridges):
1761 - Make bridge relays check once a minute for whether their IP
1762 address has changed, rather than only every 15 minutes. Resolves
1764 - Bridge statistics now count bridge clients connecting over IPv6:
1765 bridge statistics files now list "bridge-ip-versions" and
1766 extra-info documents list "geoip6-db-digest". The control protocol
1767 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1768 implementation by "shkoo", addressing ticket 5055.
1769 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1770 operators select the address where their pluggable transports will
1771 listen for connections. Resolves ticket 7013.
1772 - Randomize the lifetime of our SSL link certificate, so censors can't
1773 use the static value for filtering Tor flows. Resolves ticket 8443;
1774 related to ticket 4014 which was included in 0.2.2.33.
1776 o Minor features (relays):
1777 - Option OutboundBindAddress can be specified multiple times and
1778 accepts IPv6 addresses. Resolves ticket 6876.
1780 o Minor features (IPv6, client side):
1781 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1782 prefer to hand out virtual IPv6 addresses, since there are more of
1783 them and we can't run out. To override this behavior and make IPv4
1784 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1785 or DNSPort you're using for resolving. Implements ticket 7571.
1786 - AutomapHostsOnResolve responses are now randomized, to avoid
1787 annoying situations where Tor is restarted and applications
1788 connect to the wrong addresses.
1789 - Never try more than 1000 times to pick a new virtual address when
1790 AutomapHostsOnResolve is set. That's good enough so long as we
1791 aren't close to handing out our entire virtual address space;
1792 if you're getting there, it's best to switch to IPv6 virtual
1795 o Minor features (IPv6, relay/authority side):
1796 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1797 authorities should set if they have IPv6 connectivity and want to
1798 do reachability tests for IPv6 relays. Implements feature 5974.
1799 - A relay with an IPv6 OR port now sends that address in NETINFO
1800 cells (in addition to its other address). Implements ticket 6364.
1802 o Minor features (directory authorities):
1803 - Directory authorities no long accept descriptors for any version of
1804 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1805 These versions are insecure, unsupported, or both. Implements
1807 - When directory authorities are computing thresholds for flags,
1808 never let the threshold for the Fast flag fall below 4096
1809 bytes. Also, do not consider nodes with extremely low bandwidths
1810 when deciding thresholds for various directory flags. This change
1811 should raise our threshold for Fast relays, possibly in turn
1812 improving overall network performance; see ticket 1854. Resolves
1814 - Directory authorities now include inside each vote a statement of
1815 the performance thresholds they used when assigning flags.
1816 Implements ticket 8151.
1817 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1818 in directory authority votes to describe whether they have enough
1819 measured bandwidths to ignore advertised (relay descriptor)
1820 bandwidth claims. Resolves ticket 8711.
1822 o Minor features (path bias detection):
1823 - Path Use Bias: Perform separate accounting for successful circuit
1824 use. Keep separate statistics on stream attempt rates versus stream
1825 success rates for each guard. Provide configurable thresholds to
1826 determine when to emit log messages or disable use of guards that
1827 fail too many stream attempts. Resolves ticket 7802.
1828 - Create three levels of Path Bias log messages, as opposed to just
1829 two. These are configurable via consensus as well as via the torrc
1830 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1831 The default values are 0.70, 0.50, and 0.30 respectively.
1832 - Separate the log message levels from the decision to drop guards,
1833 which also is available via torrc option PathBiasDropGuards.
1834 PathBiasDropGuards still defaults to 0 (off).
1835 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1836 in combination with PathBiasExtremeRate.
1837 - Increase the default values for PathBiasScaleThreshold and
1838 PathBiasCircThreshold from (200, 20) to (300, 150).
1839 - Add in circuit usage accounting to path bias. If we try to use a
1840 built circuit but fail for any reason, it counts as path bias.
1841 Certain classes of circuits where the adversary gets to pick your
1842 destination node are exempt from this accounting. Usage accounting
1843 can be specifically disabled via consensus parameter or torrc.
1844 - Convert all internal path bias state to double-precision floating
1845 point, to avoid roundoff error and other issues.
1846 - Only record path bias information for circuits that have completed
1847 *two* hops. Assuming end-to-end tagging is the attack vector, this
1848 makes us more resilient to ambient circuit failure without any
1849 detection capability loss.
1851 o Minor features (build):
1852 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1853 dhill. Resolves ticket 6982.
1854 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1856 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1857 separate error codes; or at least, don't break for that reason.
1858 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1860 o Build improvements (autotools):
1861 - Warn if building on a platform with an unsigned time_t: there
1862 are too many places where Tor currently assumes that time_t can
1863 hold negative values. We'd like to fix them all, but probably
1865 - Do not report status verbosely from autogen.sh unless the -v flag
1866 is specified. Fixes issue 4664. Patch from Onizuka.
1867 - Detect and reject attempts to build Tor with threading support
1868 when OpenSSL has been compiled without threading support.
1870 - Try to detect if we are ever building on a platform where
1871 memset(...,0,...) does not set the value of a double to 0.0. Such
1872 platforms are permitted by the C standard, though in practice
1873 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1874 currently support them, but it's better to detect them and fail
1875 than to perform erroneously.
1876 - We no longer warn so much when generating manpages from their
1878 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1879 the signs of types during autoconf. This is better than our old
1880 approach, which didn't work when cross-compiling.
1882 o Minor features (log messages, warnings):
1883 - Detect when we're running with a version of OpenSSL other than the
1884 one we compiled with. This conflict has occasionally given people
1885 hard-to-track-down errors.
1886 - Warn users who run hidden services on a Tor client with
1887 UseEntryGuards disabled that their hidden services will be
1888 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1889 attack which motivated Tor to support entry guards in the first
1890 place). Resolves ticket 6889.
1891 - Warn when we are binding low ports when hibernation is enabled;
1892 previously we had warned when we were _advertising_ low ports with
1893 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1894 - Issue a warning when running with the bufferevents backend enabled.
1895 It's still not stable, and people should know that they're likely
1896 to hit unexpected problems. Closes ticket 9147.
1898 o Minor features (log messages, notices):
1899 - Refactor resolve_my_address() so it returns the method by which we
1900 decided our public IP address (explicitly configured, resolved from
1901 explicit hostname, guessed from interfaces, learned by gethostname).
1902 Now we can provide more helpful log messages when a relay guesses
1903 its IP address incorrectly (e.g. due to unexpected lines in
1904 /etc/hosts). Resolves ticket 2267.
1905 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1906 and how many we complete, and log it every hour to help relay
1907 operators follow trends in network load. Addresses ticket 9658.
1909 o Minor features (log messages, diagnostics):
1910 - If we fail to free a microdescriptor because of bug 7164, log
1911 the filename and line number from which we tried to free it.
1912 - We compute the overhead from passing onionskins back and forth to
1913 cpuworkers, and report it when dumping statistics in response to
1914 SIGUSR1. Supports ticket 7291.
1915 - Add another diagnostic to the heartbeat message: track and log
1916 overhead that TLS is adding to the data we write. If this is
1917 high, we are sending too little data to SSL_write at a time.
1918 Diagnostic for bug 7707.
1919 - Log packaged cell fullness as part of the heartbeat message.
1920 Diagnosis to try to determine the extent of bug 7743.
1921 - Add more detail to a log message about relaxed timeouts, to help
1923 - When learning a fingerprint for a bridge, log its corresponding
1924 transport type. Implements ticket 7896.
1925 - Warn more aggressively when flushing microdescriptors to a
1926 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1927 or at least make it more diagnosable.
1928 - Improve the log message when "Bug/attack: unexpected sendme cell
1929 from client" occurs, to help us track bug 8093.
1930 - Improve debugging output to help track down bug 8185 ("Bug:
1931 outgoing relay cell has n_chan==NULL. Dropping.")
1933 o Minor features (log messages, quieter bootstrapping):
1934 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1935 versions and capabilities when everything is going right. Resolves
1936 part of ticket 6736.
1937 - Omit the first heartbeat log message, because it never has anything
1938 useful to say, and it clutters up the bootstrapping messages.
1939 Resolves ticket 6758.
1940 - Don't log about reloading the microdescriptor cache at startup. Our
1941 bootstrap warnings are supposed to tell the user when there's a
1942 problem, and our bootstrap notices say when there isn't. Resolves
1943 ticket 6759; bugfix on 0.2.2.6-alpha.
1944 - Don't log "I learned some more directory information" when we're
1945 reading cached directory information. Reserve it for when new
1946 directory information arrives in response to a fetch. Resolves
1948 - Don't complain about bootstrapping problems while hibernating.
1949 These complaints reflect a general code problem, but not one
1950 with any problematic effects (no connections are actually
1951 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1953 o Minor features (testing):
1954 - In our testsuite, create temporary directories with a bit more
1955 entropy in their name to make name collisions less likely. Fixes
1957 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1958 (P-256) Diffie-Hellman handshakes to src/or/bench.
1959 - Add benchmark functions to test onion handshake performance.
1962 - The DirServer option is now DirAuthority, for consistency with
1963 current naming patterns. You can still use the old DirServer form.
1965 o Minor bugfixes (protocol):
1966 - Fix the handling of a TRUNCATE cell when it arrives while the
1967 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1968 - When a Tor client gets a "truncated" relay cell, the first byte of
1969 its payload specifies why the circuit was truncated. We were
1970 ignoring this 'reason' byte when tearing down the circuit, resulting
1971 in the controller not being told why the circuit closed. Now we
1972 pass the reason from the truncated cell to the controller. Bugfix
1973 on 0.1.2.3-alpha; fixes bug 7039.
1974 - Fix a misframing issue when reading the version numbers in a
1975 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1976 'version 1, version 2, and version 0x100', when it should have
1977 only included versions 1 and 2. Fixes bug 8059; bugfix on
1978 0.2.0.10-alpha. Reported pseudonymously.
1979 - Make the format and order of STREAM events for DNS lookups
1980 consistent among the various ways to launch DNS lookups. Fixes
1981 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
1983 o Minor bugfixes (syscalls and disk interaction):
1984 - Always check the return values of functions fcntl() and
1985 setsockopt(). We don't believe these are ever actually failing in
1986 practice, but better safe than sorry. Also, checking these return
1987 values should please analysis tools like Coverity. Patch from
1988 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1989 - Avoid double-closing the listener socket in our socketpair()
1990 replacement (used on Windows) in the case where the addresses on
1991 our opened sockets don't match what we expected. Fixes bug 9400;
1992 bugfix on 0.0.2pre7. Found by Coverity.
1993 - Correctly store microdescriptors and extrainfo descriptors that
1994 include an internal NUL byte. Fixes bug 8037; bugfix on
1995 0.2.0.1-alpha. Bug reported by "cypherpunks".
1996 - If for some reason we fail to write a microdescriptor while
1997 rebuilding the cache, do not let the annotations from that
1998 microdescriptor linger in the cache file, and do not let the
1999 microdescriptor stay recorded as present in its old location.
2000 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
2001 - Use direct writes rather than stdio when building microdescriptor
2002 caches, in an attempt to mitigate bug 8031, or at least make it
2005 o Minor fixes (config options):
2006 - Warn and fail if a server is configured not to advertise any
2007 ORPorts at all. (We need *something* to put in our descriptor,
2008 or we just won't work.)
2009 - Behave correctly when the user disables LearnCircuitBuildTimeout
2010 but doesn't tell us what they would like the timeout to be. Fixes
2011 bug 6304; bugfix on 0.2.2.14-alpha.
2012 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
2013 to start with a triple-underscore so the controller won't touch it.
2014 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
2015 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
2016 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
2017 - When autodetecting the number of CPUs, use the number of available
2018 CPUs in preference to the number of configured CPUs. Inform the
2019 user if this reduces the number of available CPUs. Fixes bug 8002;
2020 bugfix on 0.2.3.1-alpha.
2021 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2022 - Make it an error when you set EntryNodes but disable UseGuardNodes,
2023 since it will (surprisingly to some users) ignore EntryNodes. Fixes
2024 bug 8180; bugfix on 0.2.3.11-alpha.
2025 - Avoid overflows when the user sets MaxCircuitDirtiness to a
2026 ridiculously high value, by imposing a (ridiculously high) 30-day
2027 maximum on MaxCircuitDirtiness.
2029 o Minor bugfixes (control protocol):
2030 - Stop sending a stray "(null)" in some cases for the server status
2031 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
2033 - The ADDRMAP command can no longer generate an ill-formed error
2034 code on a failed MAPADDRESS. It now says "internal" rather than
2035 an English sentence fragment with spaces in the middle. Bugfix on
2038 o Minor bugfixes (clients / edges):
2039 - When we receive a RELAY_END cell with the reason DONE, or with no
2040 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
2041 status as "connection refused". Previously we reported these cases
2042 as success but then immediately closed the connection. Fixes bug
2043 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
2044 - If the guard we choose first doesn't answer, we would try the
2045 second guard, but once we connected to the second guard we would
2046 abandon it and retry the first one, slowing down bootstrapping.
2047 The fix is to treat all our initially chosen guards as acceptable
2048 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2049 - When choosing which stream on a formerly stalled circuit to wake
2050 first, make better use of the platform's weak RNG. Previously,
2051 we had been using the % ("modulo") operator to try to generate a
2052 1/N chance of picking each stream, but this behaves badly with
2053 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
2056 o Minor bugfixes (path bias detection):
2057 - If the state file's path bias counts are invalid (presumably from a
2058 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
2059 additional checks and log messages to the scaling of Path Bias
2060 counts, in case there still are remaining issues with scaling.
2061 Should help resolve bug 8235.
2062 - Prevent rounding error in path bias counts when scaling
2063 them down, and use the correct scale factor default. Also demote
2064 some path bias related log messages down a level and make others
2065 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
2066 - Remove a source of rounding error during path bias count scaling;
2067 don't count cannibalized circuits as used for path bias until we
2068 actually try to use them; and fix a circuit_package_relay_cell()
2069 warning message about n_chan==NULL. Fixes bug 7802.
2070 - Paste the description for PathBias parameters from the man
2071 page into or.h, so the code documents them too. Fixes bug 7982;
2072 bugfix on 0.2.3.17-beta.
2074 o Minor bugfixes (relays):
2075 - Stop trying to resolve our hostname so often (e.g. every time we
2076 think about doing a directory fetch). Now we reuse the cached
2077 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
2078 and 2410 (bugfix on 0.1.2.2-alpha).
2079 - When examining the list of network interfaces to find our address,
2080 do not consider non-running or disabled network interfaces. Fixes
2081 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2083 o Minor bugfixes (blocking resistance):
2084 - Only disable TLS session ticket support when running as a TLS
2085 server. Now clients will blend better with regular Firefox
2086 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
2088 o Minor bugfixes (IPv6):
2089 - Use square brackets around IPv6 addresses in numerous places
2090 that needed them, including log messages, HTTPS CONNECT proxy
2091 requests, TransportProxy statefile entries, and pluggable transport
2092 extra-info lines. Fixes bug 7011; patch by David Fifield.
2094 o Minor bugfixes (directory authorities):
2095 - Reject consensus votes with more than 64 known-flags. We aren't even
2096 close to that limit yet, and our code doesn't handle it correctly.
2097 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
2098 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
2099 bugfix on 0.2.0.3-alpha.
2101 o Minor bugfixes (memory leaks):
2102 - Avoid leaking memory if we fail to compute a consensus signature
2103 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
2104 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
2105 on 0.2.1.1-alpha; fixes bug 7816.
2106 - Fix a memory leak during safe-cookie controller authentication.
2107 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
2108 - Free some more still-in-use memory at exit, to make hunting for
2109 memory leaks easier. Resolves bug 7029.
2111 o Minor bugfixes (code correctness):
2112 - Increase the width of the field used to remember a connection's
2113 link protocol version to two bytes. Harmless for now, since the
2114 only currently recognized versions are one byte long. Reported
2115 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
2116 - Fix a crash when debugging unit tests on Windows: deallocate a
2117 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
2118 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
2119 - When detecting the largest possible file descriptor (in order to
2120 close all file descriptors when launching a new program), actually
2121 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
2122 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
2124 - Avoid a crash if we fail to generate an extrainfo descriptor.
2125 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
2127 - Avoid an off-by-one error when checking buffer boundaries when
2128 formatting the exit status of a pluggable transport helper.
2129 This is probably not an exploitable bug, but better safe than
2130 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2132 - Get rid of a couple of harmless clang warnings, where we compared
2133 enums to ints. These warnings are newly introduced in clang 3.2.
2135 o Minor bugfixes (code cleanliness):
2136 - Avoid use of reserved identifiers in our C code. The C standard
2137 doesn't like us declaring anything that starts with an
2138 underscore, so let's knock it off before we get in trouble. Fix
2139 for bug 1031; bugfix on the first Tor commit.
2140 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2141 with large values. This situation was untriggered, but nevertheless
2142 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2143 - Fix an impossible buffer overrun in the AES unit tests. Fixes
2144 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
2145 - Fix handling of rendezvous client authorization types over 8.
2146 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2147 - Remove a couple of extraneous semicolons that were upsetting the
2148 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
2149 bugfix on 0.2.2.1-alpha.
2150 - When complaining about a client port on a public address, log
2151 which address we're complaining about. Fixes bug 4020; bugfix on
2152 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2154 o Minor bugfixes (log messages, warnings):
2155 - If we encounter a write failure on a SOCKS connection before we
2156 finish our SOCKS handshake, don't warn that we closed the
2157 connection before we could send a SOCKS reply. Fixes bug 8427;
2158 bugfix on 0.1.0.1-rc.
2159 - Fix a directory authority warn caused when we have a large amount
2160 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
2161 - Downgrade "Failed to hand off onionskin" messages to "debug"
2162 severity, since they're typically redundant with the "Your computer
2163 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2164 - Avoid spurious warnings when configuring multiple client ports of
2165 which only some are nonlocal. Previously, we had claimed that some
2166 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2169 o Minor bugfixes (log messages, other):
2170 - Fix log messages and comments to avoid saying "GMT" when we mean
2171 "UTC". Fixes bug 6113.
2172 - When rejecting a configuration because we were unable to parse a
2173 quoted string, log an actual error message. Fixes bug 7950; bugfix
2175 - Correctly recognize that [::1] is a loopback address. Fixes
2176 bug 8377; bugfix on 0.2.1.3-alpha.
2177 - Don't log inappropriate heartbeat messages when hibernating: a
2178 hibernating node is _expected_ to drop out of the consensus,
2179 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
2180 bugfix on 0.2.3.1-alpha.
2181 - Eliminate several instances where we use "Nickname=ID" to refer to
2182 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2183 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2186 o Minor bugfixes (build):
2187 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2188 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2189 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2191 o Documentation fixes:
2192 - Make the torify manpage no longer refer to tsocks; torify hasn't
2193 supported tsocks since 0.2.3.14-alpha.
2194 - Make the tor manpage no longer reference tsocks.
2195 - Fix the GeoIPExcludeUnknown documentation to refer to
2196 ExcludeExitNodes rather than the currently nonexistent
2197 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
2198 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2200 - Say "KBytes" rather than "KB" in the man page (for various values
2201 of K), to further reduce confusion about whether Tor counts in
2202 units of memory or fractions of units of memory. Resolves ticket 7054.
2203 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
2204 names match. Fixes bug 7768.
2205 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
2206 message is logged at notice, not at info.
2207 - Clarify the usage and risks of setting the ContactInfo torrc line
2208 for your relay or bridge. Resolves ticket 9854.
2209 - Add anchors to the manpage so we can link to the html version of
2210 the documentation for specific options. Resolves ticket 9866.
2211 - Replace remaining references to DirServer in man page and
2212 log entries. Resolves ticket 10124.
2215 - Stop exporting estimates of v2 and v3 directory traffic shares
2216 in extrainfo documents. They were unneeded and sometimes inaccurate.
2217 Also stop exporting any v2 directory request statistics. Resolves
2219 - Drop support for detecting and warning about versions of Libevent
2220 before 1.3e. Nothing reasonable ships with them any longer; warning
2221 the user about them shouldn't be needed. Resolves ticket 6826.
2222 - Now that all versions before 0.2.2.x are disallowed, we no longer
2223 need to work around their missing features. Remove a bunch of
2227 - The tor-tsocks.conf is no longer distributed or installed. We
2228 recommend that tsocks users use torsocks instead. Resolves
2230 - Remove some of the older contents of doc/ as obsolete; move others
2231 to torspec.git. Fixes bug 8965.
2233 o Code simplification:
2234 - Avoid using character buffers when constructing most directory
2235 objects: this approach was unwieldy and error-prone. Instead,
2236 build smartlists of strings, and concatenate them when done.
2237 - Rename "isin" functions to "contains", for grammar. Resolves
2239 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2240 with the natural logarithm function from the system libm. Resolves
2242 - Start using OpenBSD's implementation of queue.h, so that we don't
2243 need to hand-roll our own pointer and list structures whenever we
2244 need them. (We can't rely on a sys/queue.h, since some operating
2245 systems don't have them, and the ones that do have them don't all
2246 present the same extensions.)
2247 - Start using OpenBSD's implementation of queue.h (originally by
2249 - Enhance our internal sscanf replacement so that we can eliminate
2250 the last remaining uses of the system sscanf. (Though those uses
2251 of sscanf were safe, sscanf itself is generally error prone, so
2252 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2254 - Replace all calls to snprintf() outside of src/ext with
2255 tor_snprintf(). Also remove the #define to replace snprintf with
2256 _snprintf on Windows; they have different semantics, and all of
2257 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2260 - Add a wrapper function for the common "log a message with a
2262 - Split the onion.c file into separate modules for the onion queue
2263 and the different handshakes it supports.
2264 - Move the client-side address-map/virtual-address/DNS-cache code
2265 out of connection_edge.c into a new addressmap.c module.
2266 - Move the entry node code from circuitbuild.c to its own file.
2267 - Move the circuit build timeout tracking code from circuitbuild.c
2269 - Source files taken from other packages now reside in src/ext;
2270 previously they were scattered around the rest of Tor.
2271 - Move the generic "config" code into a new file, and have "config.c"
2272 hold only torrc- and state-related code. Resolves ticket 6823.
2273 - Move the core of our "choose a weighted element at random" logic
2274 into its own function, and give it unit tests. Now the logic is
2275 testable, and a little less fragile too.
2276 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2277 - Move last_reachable and testing_since from routerinfo_t to node_t.
2278 Implements ticket 5529.
2279 - Add replaycache_t structure, functions and unit tests, then refactor
2280 rend_service_introduce() to be more clear to read, improve, debug,
2281 and test. Resolves bug 6177.
2284 - Remove some now-needless code that tried to aggressively flush
2285 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2286 cell queue logic has saved us from the failure mode that this code
2287 was supposed to prevent. Removing this code will limit the number
2288 of baroque control flow paths through Tor's network logic. Reported
2289 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2290 - Remove unused code for parsing v1 directories and "running routers"
2291 documents. Fixes bug 6887.
2292 - Remove the marshalling/unmarshalling code for sending requests to
2293 cpuworkers over a socket, and instead just send structs. The
2294 recipient will always be the same Tor binary as the sender, so
2295 any encoding is overkill.
2296 - Remove the testing_since field of node_t, which hasn't been used
2297 for anything since 0.2.0.9-alpha.
2298 - Finally remove support for malloc_good_size and malloc_usable_size.
2299 We had hoped that these functions would let us eke a little more
2300 memory out of our malloc implementation. Unfortunately, the only
2301 implementations that provided these functions are also ones that
2302 are already efficient about not overallocation: they never got us
2303 more than 7 or so bytes per allocation. Removing them saves us a
2304 little code complexity and a nontrivial amount of build complexity.
2307 Changes in version 0.2.3.25 - 2012-11-19
2308 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2309 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2310 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2311 programmer, and friend. Unstinting in his dedication to the cause of
2312 freedom, he inspired and helped many of us as we began our work on
2313 anonymity, and inspires us still. Please honor his memory by writing
2314 software to protect people's freedoms, and by helping others to do so.
2316 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2317 significantly reduced directory overhead (via microdescriptors),
2318 enormous crypto performance improvements for fast relays on new
2319 enough hardware, a new v3 TLS handshake protocol that can better
2320 resist fingerprinting, support for protocol obfuscation plugins (aka
2321 pluggable transports), better scalability for hidden services, IPv6
2322 support for bridges, performance improvements like allowing clients
2323 to skip the first round-trip on the circuit ("optimistic data") and
2324 refilling token buckets more often, a new "stream isolation" design
2325 to isolate different applications on different circuits, and many
2326 stability, security, and privacy fixes.
2328 Major features (v3 directory protocol):
2329 - Clients now use microdescriptors instead of regular descriptors
2330 to build circuits. Microdescriptors are authority-generated
2331 summaries of regular descriptors' contents, designed to change very
2332 rarely (see proposal 158 for details). This feature is designed
2333 to save bandwidth, especially for clients on slow internet
2334 connections. Use "UseMicrodescriptors 0" to disable it.
2335 - Caches now download, cache, and serve microdescriptors, as well
2336 as multiple "flavors" of the consensus, including a flavor that
2337 describes microdescriptors.
2339 o Major features (build hardening):
2340 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2342 o Major features (relay scaling):
2343 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2344 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2345 vectorized AES implementations as appropriate. These can be much,
2346 much faster than other AES implementations.
2347 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2348 implementation. It makes AES_CTR about 7% faster than our old one
2349 (which was about 10% faster than the one OpenSSL used to provide).
2350 Resolves ticket 4526.
2351 - Use OpenSSL's EVP interface for AES encryption, so that all AES
2352 operations can use hardware acceleration (if present). Resolves
2354 - Unconditionally use OpenSSL's AES implementation instead of our
2355 old built-in one. OpenSSL's AES has been better for a while, and
2356 relatively few servers should still be on any version of OpenSSL
2357 that doesn't have good optimized assembly AES.
2359 o Major features (blocking resistance):
2360 - Update TLS cipher list to match Firefox 8 and later. Resolves
2362 - Remove support for clients falsely claiming to support standard
2363 ciphersuites that they can actually provide. As of modern OpenSSL
2364 versions, it's not necessary to fake any standard ciphersuite,
2365 and doing so prevents us from using better ciphersuites in the
2366 future, since servers can't know whether an advertised ciphersuite
2367 is really supported or not. Some hosts -- notably, ones with very
2368 old versions of OpenSSL or where OpenSSL has been built with ECC
2369 disabled -- will stand out because of this change; TBB users should
2370 not be affected. Implements the client side of proposal 198.
2371 - Implement a new handshake protocol (v3) for authenticating Tors to
2372 each other over TLS. It should be more resistant to fingerprinting
2373 than previous protocols, and should require less TLS hacking for
2374 future Tor implementations. Implements proposal 176.
2375 - Allow variable-length padding cells, to disguise the length of
2376 Tor's TLS records. Implements part of proposal 184.
2377 - While we're trying to bootstrap, record how many TLS connections
2378 fail in each state, and report which states saw the most failures
2379 in response to any bootstrap failures. This feature may speed up
2380 diagnosis of censorship events. Implements ticket 3116.
2382 o Major features (pluggable transports):
2383 - Clients and bridges can now be configured to use a separate
2384 "transport" proxy. This approach makes the censorship arms race
2385 easier by allowing bridges to use protocol obfuscation plugins.
2386 Implements proposal 180 (tickets 2841 and 3472).
2388 o Major features (DoS resistance):
2389 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2390 part of "Proposal 110: Avoiding infinite length circuits" by
2391 refusing all circuit-extend requests that do not use a relay_early
2392 cell. This change helps Tor resist a class of denial-of-service
2393 attacks by limiting the maximum circuit length.
2394 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2395 could use this trick to make their circuits receive cells faster
2396 than our flow control would have allowed, or to gum up the network,
2397 or possibly to do targeted memory denial-of-service attacks on
2398 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2399 from July 2002, before the release of Tor 0.0.0.
2401 o Major features (hidden services):
2402 - Adjust the number of introduction points that a hidden service
2403 will try to maintain based on how long its introduction points
2404 remain in use and how many introductions they handle. Fixes
2406 - Add a "tor2web mode" for clients that want to connect to hidden
2407 services non-anonymously (and possibly more quickly). As a safety
2408 measure to try to keep users from turning this on without knowing
2409 what they are doing, tor2web mode must be explicitly enabled at
2410 compile time, and a copy of Tor compiled to run in tor2web mode
2411 cannot be used as a normal Tor client. Implements feature 2553.
2413 o Major features (IPv6):
2414 - Clients can now connect to private bridges over IPv6. Bridges
2415 still need at least one IPv4 address in order to connect to
2416 other relays. Note that we don't yet handle the case where the
2417 user has two bridge lines for the same bridge (one IPv4, one
2418 IPv6). Implements parts of proposal 186.
2420 o Major features (directory authorities):
2421 - Use a more secure consensus parameter voting algorithm. Now at
2422 least three directory authorities or a majority of them must
2423 vote on a given parameter before it will be included in the
2424 consensus. Implements proposal 178.
2425 - Remove the artificially low cutoff of 20KB to guarantee the Fast
2426 flag. In the past few years the average relay speed has picked
2427 up, and while the "top 7/8 of the network get the Fast flag" and
2428 "all relays with 20KB or more of capacity get the Fast flag" rules
2429 used to have the same result, now the top 7/8 of the network has
2430 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
2432 o Major features (performance):
2433 - Exit nodes now accept and queue data on not-yet-connected streams.
2434 Previously, the client wasn't allowed to send data until the
2435 stream was connected, which slowed down all connections. This
2436 change will enable clients to perform a "fast-start" on streams
2437 and send data without having to wait for a confirmation that the
2438 stream has opened. Patch from Ian Goldberg; implements the server
2439 side of Proposal 174.
2440 - When using an exit relay running 0.2.3.x, clients can now
2441 "optimistically" send data before the exit relay reports that
2442 the stream has opened. This saves a round trip when starting
2443 connections where the client speaks first (such as web browsing).
2444 This behavior is controlled by a consensus parameter (currently
2445 disabled). To turn it on or off manually, use the "OptimisticData"
2446 torrc option. Implements proposal 181; code by Ian Goldberg.
2447 - Add a new TokenBucketRefillInterval option to refill token buckets
2448 more frequently than once per second. This should improve network
2449 performance, alleviate queueing problems, and make traffic less
2450 bursty. Implements proposal 183; closes ticket 3630. Design by
2451 Florian Tschorsch and Björn Scheuermann; implementation by
2453 - Raise the threshold of server descriptors needed (75%) and exit
2454 server descriptors needed (50%) before we will declare ourselves
2455 bootstrapped. This will make clients start building circuits a
2456 little later, but makes the initially constructed circuits less
2457 skewed and less in conflict with further directory fetches. Fixes
2460 o Major features (relays):
2461 - Relays now try regenerating and uploading their descriptor more
2462 frequently if they are not listed in the consensus, or if the
2463 version of their descriptor listed in the consensus is too
2464 old. This fix should prevent situations where a server declines
2465 to re-publish itself because it has done so too recently, even
2466 though the authorities decided not to list its recent-enough
2467 descriptor. Fix for bug 3327.
2469 o Major features (stream isolation):
2470 - You can now configure Tor so that streams from different
2471 applications are isolated on different circuits, to prevent an
2472 attacker who sees your streams as they leave an exit node from
2473 linking your sessions to one another. To do this, choose some way
2474 to distinguish the applications: have them connect to different
2475 SocksPorts, or have one of them use SOCKS4 while the other uses
2476 SOCKS5, or have them pass different authentication strings to the
2477 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2478 degree of isolation you need. This implements Proposal 171.
2479 - There's a new syntax for specifying multiple client ports (such as
2480 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2481 multiple *Port entries with full addr:port syntax on each.
2482 The old *ListenAddress format is still supported, but you can't
2483 mix it with the new *Port syntax.
2485 o Major features (bufferevents):
2486 - Tor can now optionally build with the "bufferevents" buffered IO
2487 backend provided by Libevent 2. To use this feature, make sure you
2488 have the latest possible version of Libevent, and pass the
2489 --enable-bufferevents flag to configure when building Tor from
2490 source. This feature will make our networking code more flexible,
2491 let us stack layers on each other, and let us use more efficient
2492 zero-copy transports where available.
2493 - Add experimental support for running on Windows with IOCP and no
2494 kernel-space socket buffers. This feature is controlled by a new
2495 "UserspaceIOCPBuffers" config option (off by default), which has
2496 no effect unless Tor has been built with bufferevents enabled,
2497 you're running on Windows, and you've set "DisableIOCP 0". In the
2498 long run, this may help solve or mitigate bug 98.
2500 o Major features (path selection):
2501 - The EntryNodes option can now include country codes like {de} or IP
2502 addresses or network masks. Previously we had disallowed these
2503 options because we didn't have an efficient way to keep the list up
2504 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
2507 o Major features (port forwarding):
2508 - Add support for automatic port mapping on the many home routers
2509 that support NAT-PMP or UPnP. To build the support code, you'll
2510 need to have the libnatpnp library and/or the libminiupnpc library,
2511 and you'll need to enable the feature specifically by passing
2512 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
2513 it on, use the new PortForwarding option.
2515 o Major features (logging):
2516 - Add a new 'Heartbeat' log message type to periodically log a message
2517 describing Tor's status at level Notice. This feature is meant for
2518 operators who log at notice, and want to make sure that their Tor
2519 server is still working. Implementation by George Kadianakis.
2520 - Make logging resolution configurable with a new LogTimeGranularity
2521 option, and change the default from 1 millisecond to 1 second.
2522 Implements enhancement 1668.
2524 o Major features (other):
2525 - New "DisableNetwork" config option to prevent Tor from launching any
2526 connections or accepting any connections except on a control port.
2527 Bundles and controllers can set this option before letting Tor talk
2528 to the rest of the network, for example to prevent any connections
2529 to a non-bridge address. Packages like Orbot can also use this
2530 option to instruct Tor to save power when the network is off.
2531 - Try to use system facilities for enumerating local interface
2532 addresses, before falling back to our old approach (which was
2533 binding a UDP socket, and calling getsockname() on it). That
2534 approach was scaring OS X users whose draconian firewall
2535 software warned about binding to UDP sockets regardless of
2536 whether packets were sent. Now we try to use getifaddrs(),
2537 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2538 system supports. Resolves ticket 1827.
2539 - Add experimental support for a "defaults" torrc file to be parsed
2540 before the regular torrc. Torrc options override the defaults file's
2541 options in the same way that the command line overrides the torrc.
2542 The SAVECONF controller command saves only those options which
2543 differ between the current configuration and the defaults file. HUP
2544 reloads both files. Implements task 4552.
2546 o New directory authorities:
2547 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2548 authority. Closes ticket 5749.
2550 o Security/privacy fixes:
2551 - Avoid read-from-freed-memory and double-free bugs that could occur
2552 when a DNS request fails while launching it. Fixes bug 6480;
2553 bugfix on 0.2.0.1-alpha.
2554 - Reject any attempt to extend to an internal address. Without
2555 this fix, a router could be used to probe addresses on an internal
2556 network to see whether they were accepting connections. Fixes bug
2557 6710; bugfix on 0.0.8pre1.
2558 - Close any connection that sends unrecognized junk before the TLS
2559 handshake. Solves an issue noted in bug 4369.
2560 - The advertised platform of a relay now includes only its operating
2561 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
2562 its service pack level (for Windows) or its CPU architecture
2563 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
2564 can insert an extra string in the platform line by setting the
2565 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
2566 - Disable TLS session tickets. OpenSSL's implementation was giving
2567 our TLS session keys the lifetime of our TLS context objects, when
2568 perfect forward secrecy would want us to discard anything that
2569 could decrypt a link connection as soon as the link connection
2570 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2571 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2572 - Tor tries to wipe potentially sensitive data after using it, so
2573 that if some subsequent security failure exposes Tor's memory,
2574 the damage will be limited. But we had a bug where the compiler
2575 was eliminating these wipe operations when it decided that the
2576 memory was no longer visible to a (correctly running) program,
2577 hence defeating our attempt at defense in depth. We fix that
2578 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2579 is unlikely to optimize away. Future versions of Tor may use
2580 a less ridiculously heavy approach for this. Fixes bug 7352.
2581 Reported in an article by Andrey Karpov.
2583 o Major bugfixes (crashes and asserts):
2584 - Avoid a pair of double-free and use-after-mark bugs that can
2585 occur with certain timings in canceled and re-received DNS
2586 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2587 - Fix a denial of service attack by which any directory authority
2588 could crash all the others, or by which a single v2 directory
2589 authority could crash everybody downloading v2 directory
2590 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2591 - Fix an assert that directory authorities could trigger on sighup
2592 during some configuration state transitions. We now don't treat
2593 it as a fatal error when the new descriptor we just generated in
2594 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2595 - Avoid segfault when starting up having run with an extremely old
2596 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2599 o Major bugfixes (clients):
2600 - If we are unable to find any exit that supports our predicted ports,
2601 stop calling them predicted, so that we don't loop and build
2602 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2603 which introduced predicted ports.
2604 - Check at each new consensus whether our entry guards were picked
2605 long enough ago that we should rotate them. Previously, we only
2606 did this check at startup, which could lead to us holding a guard
2607 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2608 - When fetching a bridge descriptor from a bridge authority,
2609 always do so anonymously, whether we have been able to open
2610 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2611 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2612 but we'll need to wait for bug 6010 before it's actually usable.
2614 o Major bugfixes (directory voting):
2615 - Check more thoroughly to prevent a rogue authority from
2616 double-voting on any consensus directory parameter. Previously,
2617 authorities would crash in this case if the total number of
2618 votes for any parameter exceeded the number of active voters,
2619 but would let it pass otherwise. Partially fixes bug 5786; bugfix
2621 - When computing weight parameters, behave more robustly in the
2622 presence of a bad bwweightscale value. Previously, the authorities
2623 would crash if they agreed on a sufficiently broken weight_scale
2624 value; now, they use a reasonable default and carry on. Fixes the
2625 rest of bug 5786; bugfix on 0.2.2.17-alpha.
2626 - If authorities are unable to get a v2 consensus document from other
2627 directory authorities, they no longer fall back to fetching
2628 them from regular directory caches. Fixes bug 5635; bugfix on
2629 0.2.2.26-beta, where routers stopped downloading v2 consensus
2632 o Major bugfixes (relays):
2633 - Fix a bug handling SENDME cells on nonexistent streams that could
2634 result in bizarre window values. Report and patch contributed
2635 pseudonymously. Fixes part of bug 6271. This bug was introduced
2636 before the first Tor release, in svn commit r152.
2637 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2638 tor gets started. This prevents a wrong average bandwidth
2639 estimate, which would cause relays to always start a new accounting
2640 interval at the earliest possible moment. Fixes bug 2003; bugfix
2641 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
2642 immensely in tracking this bug down.
2643 - Fix a possible crash bug when checking for deactivated circuits
2644 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2645 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2646 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2647 connections. This change should allow busy exit relays to stop
2648 running out of available sockets as quickly. Fixes bug 4950;
2649 bugfix on 0.2.2.26-beta.
2651 o Major bugfixes (blocking resistance):
2652 - Bridges no longer include their address in NETINFO cells on outgoing
2653 OR connections, to allow them to blend in better with clients.
2654 Removes another avenue for enumerating bridges. Reported by
2655 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
2656 cells were introduced.
2657 - Warn the user when HTTPProxy, but no other proxy type, is
2658 configured. This can cause surprising behavior: it doesn't send
2659 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2660 directory traffic only. Resolves ticket 4663.
2662 o Major bugfixes (hidden services):
2663 - Improve hidden service robustness: when an attempt to connect to
2664 a hidden service ends, be willing to refetch its hidden service
2665 descriptors from each of the HSDir relays responsible for them
2666 immediately. Previously, we would not consider refetching the
2667 service's descriptors from each HSDir for 15 minutes after the last
2668 fetch, which was inconvenient if the hidden service was not running
2669 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
2670 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2671 They used to check that the timestamp was within 30 minutes
2672 of their system clock, so they could cap the size of their
2673 replay-detection cache, but that approach unnecessarily refused
2674 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2675 the v3 intro-point protocol (the first one which sent a timestamp
2676 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2677 - When one of a hidden service's introduction points appears to be
2678 unreachable, stop trying it. Previously, we would keep trying
2679 to build circuits to the introduction point until we lost the
2680 descriptor, usually because the user gave up and restarted Tor.
2681 Fixes part of bug 3825.
2683 o Changes to default torrc file:
2684 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2685 port on 9050 by default anyway, so this should not change anything
2687 - Stop mentioning the deprecated *ListenAddress options in
2688 torrc.sample. Fixes bug 5438.
2689 - Document unit of bandwidth-related options in sample torrc.
2691 - Fix broken URLs in the sample torrc file, and tell readers about
2692 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2693 PublishServerDescriptor options. Addresses bug 4652.
2695 o Minor features (directory authorities):
2696 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2697 change when the authority is deciding whether to accept a newly
2698 uploaded descriptor. Implements ticket 6423.
2699 - Directory authorities are now a little more lenient at accepting
2700 older router descriptors, or newer router descriptors that don't
2701 make big changes. This should help ameliorate past and future
2702 issues where routers think they have uploaded valid descriptors,
2703 but the authorities don't think so. Fix for ticket 2479.
2704 - Authority operators can now vote for all relays in a given
2705 set of countries to be BadDir/BadExit/Invalid/Rejected.
2706 - Provide two consensus parameters (FastFlagMinThreshold and
2707 FastFlagMaxThreshold) to control the range of allowable bandwidths
2708 for the Fast directory flag. These allow authorities to run
2709 experiments on appropriate requirements for being a "Fast" node.
2710 The AuthDirFastGuarantee config value still applies. Implements
2713 o Minor features (bridges / bridge authorities):
2714 - Make bridge SSL certificates a bit more stealthy by using random
2715 serial numbers, in the same fashion as OpenSSL when generating
2716 self-signed certificates. Implements ticket 4584.
2717 - Tag a bridge's descriptor as "never to be sent unencrypted".
2718 This shouldn't matter, since bridges don't open non-anonymous
2719 connections to the bridge authority and don't allow unencrypted
2720 directory connections from clients, but we might as well make
2721 sure. Closes bug 5139.
2722 - The Bridge Authority now writes statistics on how many bridge
2723 descriptors it gave out in total, and how many unique descriptors
2724 it gave out. It also lists how often the most and least commonly
2725 fetched descriptors were given out, as well as the median and
2726 25th/75th percentile. Implements tickets 4200 and 4294.
2728 o Minor features (IPv6):
2729 - Make the code that clients use to detect an address change be
2730 IPv6-aware, so that it won't fill clients' logs with error
2731 messages when trying to get the IPv4 address of an IPv6
2732 connection. Implements ticket 5537.
2733 - Relays now understand an IPv6 address when they get one from a
2734 directory server. Resolves ticket 4875.
2736 o Minor features (hidden services):
2737 - Expire old or over-used hidden service introduction points.
2738 Required by fix for bug 3460.
2739 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
2740 public key replay-detection cache from 60 minutes to 5 minutes. This
2741 replay-detection cache is now used only to detect multiple
2742 INTRODUCE2 cells specifying the same rendezvous point, so we can
2743 avoid launching multiple simultaneous attempts to connect to it.
2744 - When a hidden service's introduction point times out, consider
2745 trying it again during the next attempt to connect to the
2746 HS. Previously, we would not try it again unless a newly fetched
2747 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2749 o Minor features (relays):
2750 - Relays now include a reason for regenerating their descriptors
2751 in an HTTP header when uploading to the authorities. This will
2752 make it easier to debug descriptor-upload issues in the future.
2753 - Turn on directory request statistics by default and include them in
2754 extra-info descriptors. Don't break if we have no GeoIP database.
2755 - Replace files in stats/ rather than appending to them. Now that we
2756 include statistics in extra-info descriptors, it makes no sense to
2757 keep old statistics forever. Implements ticket 2930.
2758 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2759 bidirectional use of connections to disk every 24 hours.
2760 - Add a GeoIP file digest to the extra-info descriptor. Implements
2763 o Minor features (new config options):
2764 - New config option "DynamicDHGroups" (disabled by default) provides
2765 each bridge with a unique prime DH modulus to be used during
2766 SSL handshakes. This option attempts to help against censors
2767 who might use the Apache DH modulus as a static identifier for
2768 bridges. Addresses ticket 4548.
2769 - New config option "DisableDebuggerAttachment" (on by default)
2770 to prevent basic debugging attachment attempts by other processes.
2771 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
2772 - Ordinarily, Tor does not count traffic from private addresses (like
2773 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2774 There is now a new option, CountPrivateBandwidth, to disable this
2775 behavior. Patch from Daniel Cagara.
2777 o Minor features (different behavior for old config options):
2778 - Allow MapAddress directives to specify matches against super-domains,
2779 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
2780 Implements issue 933.
2781 - Don't disable the DirPort when we cannot exceed our AccountingMax
2782 limit during this interval because the effective bandwidthrate is
2783 low enough. This is useful in a situation where AccountMax is only
2784 used as an additional safeguard or to provide statistics.
2785 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2786 implements ticket 3439.
2787 - When configuring a large set of nodes in EntryNodes, and there are
2788 enough of them listed as Guard so that we don't need to consider
2789 the non-guard entries, prefer the ones listed with the Guard flag.
2790 - If you set the NumCPUs option to 0, Tor will now try to detect how
2791 many CPUs you have. This is the new default behavior.
2792 - The NodeFamily option -- which let you declare that you want to
2793 consider nodes to be part of a family whether they list themselves
2794 that way or not -- now allows IP address ranges and country codes.
2796 o Minor features (new command-line config behavior):
2797 - Slightly change behavior of "list" options (that is, config
2798 options that can appear more than once) when they appear both in
2799 torrc and on the command line. Previously, the command-line options
2800 would be appended to the ones from torrc. Now, the command-line
2801 options override the torrc options entirely. This new behavior
2802 allows the user to override list options (like exit policies and
2803 ports to listen on) from the command line, rather than simply
2804 appending to the list.
2805 - You can get the old (appending) command-line behavior for "list"
2806 options by prefixing the option name with a "+".
2807 - You can remove all the values for a "list" option from the command
2808 line without adding any new ones by prefixing the option name
2811 o Minor features (controller, new events):
2812 - Extend the control protocol to report flags that control a circuit's
2813 path selection in CIRC events and in replies to 'GETINFO
2814 circuit-status'. Implements part of ticket 2411.
2815 - Extend the control protocol to report the hidden service address
2816 and current state of a hidden-service-related circuit in CIRC
2817 events and in replies to 'GETINFO circuit-status'. Implements part
2819 - Include the creation time of a circuit in CIRC and CIRC2
2820 control-port events and the list produced by the 'GETINFO
2821 circuit-status' control-port command.
2822 - Add a new CONF_CHANGED event so that controllers can be notified
2823 of any configuration changes made by other controllers, or by the
2824 user. Implements ticket 1692.
2825 - Add a new SIGNAL event to the controller interface so that
2826 controllers can be notified when Tor handles a signal. Resolves
2827 issue 1955. Patch by John Brooks.
2829 o Minor features (controller, new getinfo options):
2830 - Expose our view of whether we have gone dormant to the controller,
2831 via a new "GETINFO dormant" value. Torbutton and other controllers
2832 can use this to avoid doing periodic requests through Tor while
2833 it's dormant (bug 4718). Resolves ticket 5954.
2834 - Add a new GETINFO option to get total bytes read and written. Patch
2835 from pipe, revised by atagar. Resolves ticket 2345.
2836 - Implement new GETINFO controller fields to provide information about
2837 the Tor process's pid, euid, username, and resource limits.
2839 o Minor features (controller, other):
2840 - Allow controllers to request an event notification whenever a
2841 circuit is cannibalized or its purpose is changed. Implements
2842 part of ticket 3457.
2843 - Use absolute path names when reporting the torrc filename in the
2844 control protocol, so a controller can more easily find the torrc
2845 file. Resolves bug 1101.
2846 - When reporting the path to the cookie file to the controller,
2847 give an absolute path. Resolves ticket 4881.
2849 o Minor features (log messages):
2850 - Add more information to a log statement that might help track down
2851 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2852 non-IP address" messages (or any Bug messages, for that matter!),
2853 please let us know about it.
2854 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2855 EntryNodes will have no effect. Resolves issue 2571.
2856 - Try to make the introductory warning message that Tor prints on
2857 startup more useful for actually finding help and information.
2858 Resolves ticket 2474.
2859 - When the system call to create a listener socket fails, log the
2860 error message explaining why. This may help diagnose bug 4027.
2862 o Minor features (other):
2863 - When we fail to initialize Libevent, retry with IOCP disabled so we
2864 don't need to turn on multi-threading support in Libevent, which in
2865 turn requires a working socketpair(). This is a workaround for bug
2866 4457, which affects Libevent versions from 2.0.1-alpha through
2868 - When starting as root and then changing our UID via the User
2869 control option, and we have a ControlSocket configured, make sure
2870 that the ControlSocket is owned by the same account that Tor will
2871 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2872 - Accept attempts to include a password authenticator in the
2873 handshake, as supported by SOCKS5. This handles SOCKS clients that
2874 don't know how to omit a password when authenticating. Resolves
2876 - Check for and recover from inconsistency in the microdescriptor
2877 cache. This will make it harder for us to accidentally free a
2878 microdescriptor without removing it from the appropriate data
2879 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2880 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2882 o Minor bugfixes (code security):
2883 - Prevent a null-pointer dereference when receiving a data cell
2884 for a nonexistent stream when the circuit in question has an
2885 empty deliver window. We don't believe this is triggerable,
2886 since we don't currently allow deliver windows to become empty,
2887 but the logic is tricky enough that it's better to make the code
2888 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2889 - Fix a (harmless) integer overflow in cell statistics reported by
2890 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2891 - Fix our implementation of crypto_random_hostname() so it can't
2892 overflow on ridiculously large inputs. (No Tor version has ever
2893 provided this kind of bad inputs, but let's be correct in depth.)
2894 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2895 - Add a (probably redundant) memory clear between iterations of
2896 the router status voting loop, to prevent future coding errors
2897 where data might leak between iterations of the loop. Resolves
2900 o Minor bugfixes (wrapper functions):
2901 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
2902 utility function used in the control-port code). This shouldn't
2903 ever happen unless Tor is completely out of memory, but if it did
2904 happen and Tor somehow recovered from it, Tor could have sent a log
2905 message to a control port in the middle of a reply to a controller
2906 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2907 - Fix some (not actually triggerable) buffer size checks in usage of
2908 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2910 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2911 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2912 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2913 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2914 - Make our replacement implementation of strtok_r() compatible with
2915 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2916 bugfix on 0.2.2.1-alpha.
2917 - Find more places in the code that should have been testing for
2918 invalid sockets using the SOCKET_OK macro. Required for a fix
2919 for bug 4533. Bugfix on 0.2.2.28-beta.
2921 o Minor bugfixes (code correctness):
2922 - Check return value of fputs() when writing authority certificate
2923 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2924 - When building Tor on Windows with -DUNICODE (not default), ensure
2925 that error messages, filenames, and DNS server names are always
2926 NUL-terminated when we convert them to a single-byte encoding.
2927 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2928 - Fix a memory leak when trying to launch a DNS request when the
2929 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
2931 - Correct file sizes when reading binary files on Cygwin, to avoid
2932 a bug where Tor would fail to read its state file. Fixes bug 6844;
2933 bugfix on 0.1.2.7-alpha.
2934 - Make sure to set *socket_error in all error cases in
2935 connection_connect(), so it can't produce a warning about
2936 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2937 0.2.1.1-alpha; resolves ticket 6028.
2938 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2939 bug 4532; found by "troll_un".
2941 o Minor bugfixes (clients):
2942 - Allow one-hop directory-fetching circuits the full "circuit build
2943 timeout" period, rather than just half of it, before failing them
2944 and marking the relay down. This fix should help reduce cases where
2945 clients declare relays (or worse, bridges) unreachable because
2946 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2947 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2949 - Ensure we don't cannibalize circuits that are longer than three hops
2950 already, so we don't end up making circuits with 5 or more
2951 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2952 0.1.0.1-rc which introduced cannibalization.
2954 o Minor bugfixes (relays):
2955 - Don't publish a new relay descriptor when we reload our onion key,
2956 unless the onion key has actually changed. Fixes bug 3263 and
2957 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2958 - When relays refuse a "create" cell because their queue of pending
2959 create cells is too big (typically because their cpu can't keep up
2960 with the arrival rate), send back reason "resource limit" rather
2961 than reason "internal", so network measurement scripts can get a
2962 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2963 - Exit nodes don't need to fetch certificates for authorities that
2964 they don't recognize; only directory authorities, bridges,
2965 and caches need to do that. Fixes part of bug 2297; bugfix on
2968 o Minor bugfixes (directory authority / mirrors):
2969 - Avoid O(n^2) performance characteristics when parsing a large
2970 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2971 - Authorities no longer include any router in their microdescriptor
2972 consensuses for which they couldn't generate or agree on a
2973 microdescriptor. Fixes the second piece of bug 6404; fix on
2975 - When checking for requested signatures on the latest consensus
2976 before serving it to a client, make sure to check the right
2977 consensus flavor. Bugfix on 0.2.2.6-alpha.
2978 - Fix an edge case where TestingTorNetwork is set but the authorities
2979 and relays all have an uptime of zero, so the private Tor network
2980 could briefly lack support for hidden services. Fixes bug 3886;
2981 bugfix on 0.2.2.18-alpha.
2982 - Directory caches no longer refuse to clean out descriptors because
2983 of missing v2 networkstatus documents, unless they're configured
2984 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2985 0.2.2.26-beta. Patch by Daniel Bryg.
2986 - Don't serve or accept v2 hidden service descriptors over a relay's
2987 DirPort. It's never correct to do so, and disabling it might
2988 make it more annoying to exploit any bugs that turn up in the
2989 descriptor-parsing code. Fixes bug 7149.
2991 o Minor bugfixes (hidden services, client-side):
2992 - Assert that hidden-service-related operations are not performed
2993 using single-hop circuits. Previously, Tor would assert that
2994 client-side streams are not attached to single-hop circuits,
2995 but not that other sensitive operations on the client and service
2996 side are not performed using single-hop circuits. Fixes bug 3332;
2998 - Avoid undefined behavior when parsing the list of supported
2999 rendezvous/introduction protocols in a hidden service descriptor.
3000 Previously, Tor would have confused (as-yet-unused) protocol version
3001 numbers greater than 32 with lower ones on many platforms. Fixes
3002 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3003 - Don't close hidden service client circuits which have almost
3004 finished connecting to their destination when they reach
3005 the normal circuit-build timeout. Previously, we would close
3006 introduction circuits which are waiting for an acknowledgement
3007 from the introduction point, and rendezvous circuits which have
3008 been specified in an INTRODUCE1 cell sent to a hidden service,
3009 after the normal CBT. Now, we mark them as 'timed out', and launch
3010 another rendezvous attempt in parallel. This behavior change can
3011 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3012 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3014 o Minor bugfixes (hidden services, service-side):
3015 - Don't close hidden-service-side rendezvous circuits when they
3016 reach the normal circuit-build timeout. This behavior change can
3017 be disabled using the new
3018 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3019 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3020 - Don't launch more than 10 service-side introduction-point circuits
3021 for a hidden service in five minutes. Previously, we would consider
3022 launching more introduction-point circuits if at least one second
3023 had passed without any introduction-point circuits failing. Fixes
3024 bug 4607; bugfix on 0.0.7pre1.
3026 o Minor bugfixes (config option behavior):
3027 - If the user tries to set MyFamily on a bridge, refuse to
3028 do so, and warn about the security implications. Fixes bug 4657;
3029 bugfix on 0.2.0.3-alpha.
3030 - The "--quiet" and "--hush" options now apply not only to Tor's
3031 behavior before logs are configured, but also to Tor's behavior in
3032 the absense of configured logs. Fixes bug 3550; bugfix on
3034 - Change the AllowDotExit rules so they should actually work.
3035 We now enforce AllowDotExit only immediately after receiving an
3036 address via SOCKS or DNSPort: other sources are free to provide
3037 .exit addresses after the resolution occurs. Fixes bug 3940;
3038 bugfix on 0.2.2.1-alpha.
3039 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
3040 don't depend on the consensus parameters or compute adaptive
3041 timeouts when it is disabled. Fixes bug 5049; bugfix on
3043 - After we pick a directory mirror, we would refuse to use it if
3044 it's in our ExcludeExitNodes list, resulting in mysterious failures
3045 to bootstrap for people who just wanted to avoid exiting from
3046 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
3047 - When told to add a bridge with the same digest as a preexisting
3048 bridge but a different addr:port, change the addr:port as
3049 requested. Previously we would not notice the change. Fixes half
3050 of bug 5603; fix on 0.2.2.26-beta.
3052 o Minor bugfixes (controller):
3053 - Allow manual 'authenticate' commands to the controller interface
3054 from netcat (nc) as well as telnet. We were rejecting them because
3055 they didn't come with the expected whitespace at the end of the
3056 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3057 - Report a real bootstrap problem to the controller on router
3058 identity mismatch. Previously we just said "foo", which probably
3059 made a lot of sense at the time. Fixes bug 4169; bugfix on
3061 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
3062 option is set to 0 (which Vidalia version 0.2.16 now does when
3063 a SAVECONF attempt fails), perform other actions that SIGHUP
3064 usually causes (like reopening the logs). Fixes bug 5095; bugfix
3066 - Correctly handle checking the permissions on the parent
3067 directory of a control socket in the root directory. Bug found
3068 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
3070 - End AUTHCHALLENGE error messages (in the control protocol) with
3071 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
3073 o Minor bugfixes (network reading/writing):
3074 - Disable writing on marked-for-close connections when they are
3075 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
3076 bug 5263; bugfix on 0.0.2pre13, where we first added a special
3077 case for flushing marked connections.
3078 - Make sure that there are no unhandled pending TLS errors before
3079 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
3080 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
3081 Bugfix on 0.1.0.5-rc; fixes bug 4528.
3082 - Detect SSL handshake even when the initial attempt to write the
3083 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
3084 - If the client fails to set a reasonable set of ciphersuites
3085 during its v2 handshake renegotiation, allow the renegotiation to
3086 continue nevertheless (i.e. send all the required certificates).
3087 Fixes bug 4591; bugfix on 0.2.0.20-rc.
3089 o Minor bugfixes (other):
3090 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
3091 resource exhaustion, so that clients can adjust their load to
3092 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
3093 started using END_STREAM_REASON_RESOURCELIMIT.
3094 - Don't check for whether the address we're using for outbound
3095 connections has changed until after the outbound connection has
3096 completed. On Windows, getsockname() doesn't succeed until the
3097 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
3098 - Don't hold a Windows file handle open for every file mapping;
3099 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
3101 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
3102 bugfix on 0.2.1.10-alpha.
3103 - If we fail to write a microdescriptor to the disk cache, do not
3104 continue replacing the old microdescriptor file. Fixes bug 2954;
3105 bugfix on 0.2.2.6-alpha.
3107 o Minor bugfixes (log messages, path selection):
3108 - Downgrade "set buildtimeout to low value" messages to "info"
3109 severity; they were never an actual problem, there was never
3110 anything reasonable to do about them, and they tended to spam logs
3111 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
3112 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
3113 more information to it, so that we can track it down in case it
3114 returns again. Mitigates bug 5235.
3115 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
3116 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
3117 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
3118 - Issue a log message if a guard completes less than 40% of your
3119 circuits. Threshold is configurable by torrc option
3120 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
3121 additional, off-by-default code to disable guards which fail too
3122 many circuits. Addresses ticket 5458.
3124 o Minor bugfixes (log messages, client):
3125 - Downgrade "Got a certificate, but we already have it" log messages
3126 from warning to info, except when we're a dirauth. Fixes bug 5238;
3127 bugfix on 0.2.1.7-alpha.
3128 - Fix the log message describing how we work around discovering
3129 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3130 4837; bugfix on 0.2.2.9-alpha.
3131 - When logging about a disallowed .exit name, do not also call it
3132 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3133 - Fix a log message suggesting that people contact a non-existent
3134 email address. Fixes bug 3448.
3135 - Rephrase the log message emitted if the TestSocks check is
3136 successful. Patch from Fabian Keil; fixes bug 4094.
3137 - Log (at debug level) whenever a circuit's purpose is changed.
3138 - Log SSL state transitions at log level DEBUG, log domain
3139 HANDSHAKE. This can be useful for debugging censorship events.
3140 Implements ticket 3264.
3141 - We now log which torrc file we're using on startup. Implements
3143 - Rate-limit log messages when asked to connect anonymously to
3144 a private address. When these hit, they tended to hit fast and
3145 often. Also, don't bother trying to connect to addresses that we
3146 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3147 reply makes us think we have been lied to, even when the address the
3148 client tried to connect to was "localhost." Resolves ticket 2822.
3150 o Minor bugfixes (log messages, non-client):
3151 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3152 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3153 - Don't log that we have "decided to publish new relay descriptor"
3154 unless we are actually publishing a descriptor. Fixes bug 3942;
3155 bugfix on 0.2.2.28-beta.
3156 - Log which authority we're missing votes from when we go to fetch
3157 them from the other auths.
3158 - Replace "Sending publish request" log messages with "Launching
3159 upload", so that they no longer confusingly imply that we're
3160 sending something to a directory we might not even be connected
3161 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3162 - Warn when Tor is configured to use accounting in a way that can
3163 link a hidden service to some other hidden service or public
3164 address. Resolves ticket 6490.
3165 - Fix a minor formatting issue in one of tor-gencert's error messages.
3169 - Update to the latest version of the tinytest unit testing framework.
3170 This includes a couple of bugfixes that can be relevant for
3171 running forked unit tests on Windows, and removes all reserved
3173 - Avoid a false positive in the util/threads unit test by increasing
3174 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3175 - Make it possible to set the TestingTorNetwork configuration
3176 option using AlternateDirAuthority and AlternateBridgeAuthority
3177 as an alternative to setting DirServer. Addresses ticket 6377.
3178 - Add a unit test for the environment_variable_names_equal() function.
3179 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3180 - Numerous new unit tests for functions in util.c and address.c by
3182 - The long-disabled benchmark tests are now split into their own
3183 ./src/test/bench binary.
3184 - The benchmark tests can now use more accurate timers than
3185 gettimeofday() when such timers are available.
3186 - Use tt_assert(), not tor_assert(), for checking for test failures.
3187 This makes the unit tests more able to go on in the event that
3190 o Build improvements:
3191 - Use the dead_strip option when building Tor on OS X. This reduces
3192 binary size by almost 19% when linking openssl and libevent
3193 statically, which we do for Tor Browser Bundle.
3194 - Provide a better error message about possible OSX Asciidoc failure
3195 reasons. Fixes bug 6436.
3196 - Detect attempts to build Tor on (as yet hypothetical) versions
3197 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3198 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3199 - On Windows, we now define the _WIN32_WINNT macros only if they
3200 are not already defined. This lets the person building Tor decide,
3201 if they want, to require a later version of Windows.
3202 - Our autogen.sh script now uses autoreconf to launch autoconf,
3203 automake, and so on. This is more robust against some of the failure
3204 modes associated with running the autotools pieces on their own.
3205 - Running "make version" now displays the version of Tor that
3206 we're about to build. Idea from katmagic; resolves issue 4400.
3207 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
3208 on 0.2.2.4-alpha; fixes bug 3427.
3209 - New --enable-static-tor configure option for building Tor as
3210 statically as possible. Idea, general hackery and thoughts from
3211 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3213 - Limited, experimental support for building with nmake and MSVC.
3215 o Build requirements:
3216 - Building Tor with bufferevent support now requires Libevent
3217 2.0.13-stable or later. Previous versions of Libevent had bugs in
3218 SSL-related bufferevents and related issues that would make Tor
3219 work badly with bufferevents. Requiring 2.0.13-stable also allows
3220 Tor with bufferevents to take advantage of Libevent APIs
3221 introduced after 2.0.8-rc.
3222 - Our build system requires automake 1.6 or later to create the
3223 Makefile.in files. Previously, you could have used 1.4.
3224 This only affects developers and people building Tor from git;
3225 people who build Tor from the source distribution without changing
3226 the Makefile.am files should be fine.
3227 - Detect when we try to build on a platform that doesn't define
3228 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3230 o Build fixes (compile/link):
3231 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3232 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3234 - When building with --enable-static-tor on OpenBSD, do not
3235 erroneously attempt to link -lrt. Fixes bug 5103.
3236 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3237 that IPv6 stuff will compile on MSVC, and compilation issues
3238 will be easier to track down. Fixes bug 5861.
3239 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
3240 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
3241 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3242 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3244 o Build fixes (other):
3245 - Use the _WIN32 macro throughout our code to detect Windows.
3246 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3248 - Properly handle the case where the build-tree is not the same
3249 as the source tree when generating src/common/common_sha1.i,
3250 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3251 bugfix on 0.2.0.1-alpha.
3252 - During configure, search for library containing cos function as
3253 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3254 against libm was hard-coded before. Fixes the first part of bug
3255 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3257 - Prevent a false positive from the check-spaces script, by disabling
3258 the "whitespace between function name and (" check for functions
3261 o Packaging (RPM) changes:
3262 - Update our default RPM spec files to work with mock and rpmbuild
3263 on RHEL/Fedora. They have an updated set of dependencies and
3264 conflicts, a fix for an ancient typo when creating the "_tor"
3265 user, and better instructions. Thanks to Ondrej Mikle for the
3266 patch series. Fixes bug 6043.
3267 - On OpenSUSE, create the /var/run/tor directory on startup if it
3268 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
3270 o Code refactoring (safety):
3271 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3272 10 lines. Also, don't nest them. Doing so in the past has
3273 led to hard-to-debug code. The new style is to use the
3274 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3275 - Use macros to indicate OpenSSL versions, so we don't need to worry
3276 about accidental hexadecimal bit shifts.
3277 - Use tor_sscanf() in place of scanf() in more places through the
3278 code. This makes us a little more locale-independent, and
3279 should help shut up code-analysis tools that can't tell
3280 a safe sscanf string from a dangerous one.
3281 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3282 - Use the smartlist_add_asprintf() alias more consistently.
3284 o Code refactoring (consolidate):
3285 - A major revision to our internal node-selecting and listing logic.
3286 Tor already had at least two major ways to look at the question of
3287 "which Tor servers do we know about": a list of router descriptors,
3288 and a list of entries in the current consensus. With
3289 microdescriptors, we're adding a third. Having so many systems
3290 without an abstraction layer over them was hurting the codebase.
3291 Now, we have a new "node_t" abstraction that presents a consistent
3292 interface to a client's view of a Tor node, and holds (nearly) all
3293 of the mutable state formerly in routerinfo_t and routerstatus_t.
3294 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3295 Libevent's notion of cached time when possible.
3296 - Remove duplicate code for invoking getrlimit() from control.c.
3297 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3298 own homebrewed ssl_state_to_string() replacement. Patch from
3299 Emile Snyder. Fixes bug 4653.
3300 - Change the symmetric cipher interface so that creating and
3301 initializing a stream cipher are no longer separate functions.
3303 o Code refactoring (separate):
3304 - Make a new "entry connection" struct as an internal subtype of "edge
3305 connection", to simplify the code and make exit connections smaller.
3306 - Split connection_about_to_close() into separate functions for each
3308 - Rewrite the listener-selection logic so that parsing which ports
3309 we want to listen on is now separate from binding to the ports
3312 o Code refactoring (name changes):
3313 - Rename a handful of old identifiers, mostly related to crypto
3314 structures and crypto functions. By convention, our "create an
3315 object" functions are called "type_new()", our "free an object"
3316 functions are called "type_free()", and our types indicate that
3317 they are types only with a final "_t". But a handful of older
3318 types and functions broke these rules, with function names like
3319 "type_create" or "subsystem_op_type", or with type names like
3321 - Rename Tor functions that turn strings into addresses, so that
3322 "parse" indicates that no hostname resolution occurs, and
3323 "lookup" indicates that hostname resolution may occur. This
3324 should help prevent mistakes in the future. Fixes bug 3512.
3325 - Use the name "CERTS" consistently to refer to the new cell type;
3326 we were calling it CERT in some places and CERTS in others.
3327 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3328 invalid value, rather than just -1.
3329 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3330 can pick them up when the tests aren't disabled. Bugfix on
3331 0.2.2.4-alpha which introduced tinytest.
3333 o Code refactoring (other):
3334 - Defensively refactor rend_mid_rendezvous() so that protocol
3335 violations and length checks happen in the beginning. Fixes
3337 - Remove the pure attribute from all functions that used it
3338 previously. In many cases we assigned it incorrectly, because the
3339 functions might assert or call impure functions, and we don't have
3340 evidence that keeping the pure attribute is worthwhile. Implements
3341 changes suggested in ticket 4421.
3342 - Move the replay-detection cache for the RSA-encrypted parts of
3343 INTRODUCE2 cells to the introduction point data structures.
3344 Previously, we would use one replay-detection cache per hidden
3345 service. Required by fix for bug 3460.
3346 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3347 no longer link against Libevent: they never used it, but
3348 our library structure used to force them to link it.
3350 o Removed features and files:
3351 - Remove all internal support for unpadded RSA. We never used it, and
3352 it would be a bad idea to start.
3353 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3355 - Remove some redundant #include directives throughout the code.
3356 Patch from Andrea Gelmini.
3357 - Remove some old code to remember statistics about which descriptors
3358 we've served as a directory mirror. The feature wasn't used and
3359 is outdated now that microdescriptors are around.
3360 - Remove some old code to work around even older versions of Tor that
3361 used forked processes to handle DNS requests. Such versions of Tor
3362 are no longer in use as relays.
3363 - The "torify" script no longer supports the "tsocks" socksifier
3364 tool, since tsocks doesn't support DNS and UDP right for Tor.
3365 Everyone should be using torsocks instead. Fixes bugs 3530 and
3366 5180. Based on a patch by "ugh".
3367 - Remove the torrc.bridge file: we don't use it for anything, and
3368 it had become badly desynchronized from torrc.sample. Resolves
3372 - Begin a doc/state-contents.txt file to explain the contents of
3373 the Tor state file. Fixes bug 2987.
3374 - Clarify the documentation for the Alternate*Authority options.
3376 - Document the --defaults-torrc option, and the new semantics for
3377 overriding, extending, and clearing lists of options. Closes
3379 - Add missing man page documentation for consensus and microdesc
3380 files. Resolves ticket 6732.
3381 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3383 o Documentation fixes:
3384 - Improve the manual's documentation for the NT Service command-line
3385 options. Addresses ticket 3964.
3386 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3387 - Document the changes to the ORPort and DirPort options, and the
3388 fact that {OR/Dir}ListenAddress is now unnecessary (and
3389 therefore deprecated). Resolves ticket 5597.
3390 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3391 - Clarify that hidden services are TCP only. Fixes bug 6024.
3394 Changes in version 0.2.2.39 - 2012-09-11
3395 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
3399 - Fix an assertion failure in tor_timegm() that could be triggered
3400 by a badly formatted directory object. Bug found by fuzzing with
3401 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3402 - Do not crash when comparing an address with port value 0 to an
3403 address policy. This bug could have been used to cause a remote
3404 assertion failure by or against directory authorities, or to
3405 allow some applications to crash clients. Fixes bug 6690; bugfix
3409 Changes in version 0.2.2.38 - 2012-08-12
3410 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3411 attack that could in theory leak path information.
3414 - Avoid an uninitialized memory read when reading a vote or consensus
3415 document that has an unrecognized flavor name. This read could
3416 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3417 - Try to leak less information about what relays a client is
3418 choosing to a side-channel attacker. Previously, a Tor client would
3419 stop iterating through the list of available relays as soon as it
3420 had chosen one, thus finishing a little earlier when it picked
3421 a router earlier in the list. If an attacker can recover this
3422 timing information (nontrivial but not proven to be impossible),
3423 they could learn some coarse-grained information about which relays
3424 a client was picking (middle nodes in particular are likelier to
3425 be affected than exits). The timing attack might be mitigated by
3426 other factors (see bug 6537 for some discussion), but it's best
3427 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3430 Changes in version 0.2.2.37 - 2012-06-06
3431 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3432 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3436 - Work around a bug in OpenSSL that broke renegotiation with TLS
3437 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3438 the v2 Tor connection protocol when both sides were using OpenSSL
3439 1.0.1 would fail. Resolves ticket 6033.
3440 - When waiting for a client to renegotiate, don't allow it to add
3441 any bytes to the input buffer. This fixes a potential DoS issue.
3442 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3443 - Fix an edge case where if we fetch or publish a hidden service
3444 descriptor, we might build a 4-hop circuit and then use that circuit
3445 for exiting afterwards -- even if the new last hop doesn't obey our
3446 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3449 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3450 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3453 - Tell GCC and Clang to check for any errors in format strings passed
3454 to the tor_v*(print|scan)f functions.
3457 Changes in version 0.2.2.36 - 2012-05-24
3458 Tor 0.2.2.36 updates the addresses for two of the eight directory
3459 authorities, fixes some potential anonymity and security issues,
3460 and fixes several crash bugs.
3462 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3463 known flaws, and nobody should be using them. You should upgrade. If
3464 you're using a Linux or BSD and its packages are obsolete, stop using
3465 those packages and upgrade anyway.
3467 o Directory authority changes:
3468 - Change IP address for maatuska (v3 directory authority).
3469 - Change IP address for ides (v3 directory authority), and rename
3473 - When building or running with any version of OpenSSL earlier
3474 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3475 versions have a bug (CVE-2011-4576) in which their block cipher
3476 padding includes uninitialized data, potentially leaking sensitive
3477 information to any peer with whom they make a SSLv3 connection. Tor
3478 does not use SSL v3 by default, but a hostile client or server
3479 could force an SSLv3 connection in order to gain information that
3480 they shouldn't have been able to get. The best solution here is to
3481 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3482 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3483 to make sure that the bug can't happen.
3484 - Never use a bridge or a controller-supplied node as an exit, even
3485 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3486 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3487 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3488 - Only build circuits if we have a sufficient threshold of the total
3489 descriptors that are marked in the consensus with the "Exit"
3490 flag. This mitigates an attack proposed by wanoskarnet, in which
3491 all of a client's bridges collude to restrict the exit nodes that
3492 the client knows about. Fixes bug 5343.
3493 - Provide controllers with a safer way to implement the cookie
3494 authentication mechanism. With the old method, if another locally
3495 running program could convince a controller that it was the Tor
3496 process, then that program could trick the controller into telling
3497 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3498 authentication method uses a challenge-response approach to prevent
3499 this attack. Fixes bug 5185; implements proposal 193.
3502 - Avoid logging uninitialized data when unable to decode a hidden
3503 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3504 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3505 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3507 - Fix builds when the path to sed, openssl, or sha1sum contains
3508 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3510 - Correct our replacements for the timeradd() and timersub() functions
3511 on platforms that lack them (for example, Windows). The timersub()
3512 function is used when expiring circuits, while timeradd() is
3513 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3514 bugfix on 0.2.2.24-alpha.
3515 - Fix the SOCKET_OK test that we use to tell when socket
3516 creation fails so that it works on Win64. Fixes part of bug 4533;
3517 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3520 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3521 Fixes bug 5346; bugfix on 0.0.8pre3.
3522 - Make our number-parsing functions always treat too-large values
3523 as an error, even when those values exceed the width of the
3524 underlying type. Previously, if the caller provided these
3525 functions with minima or maxima set to the extreme values of the
3526 underlying integer type, these functions would return those
3527 values on overflow rather than treating overflow as an error.
3528 Fixes part of bug 5786; bugfix on 0.0.9.
3529 - Older Linux kernels erroneously respond to strange nmap behavior
3530 by having accept() return successfully with a zero-length
3531 socket. When this happens, just close the connection. Previously,
3532 we would try harder to learn the remote address: but there was
3533 no such remote address to learn, and our method for trying to
3534 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3535 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3536 - Correct parsing of certain date types in parse_http_time().
3537 Without this patch, If-Modified-Since would behave
3538 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3539 Esteban Manchado Velázques.
3540 - Change the BridgePassword feature (part of the "bridge community"
3541 design, which is not yet implemented) to use a time-independent
3542 comparison. The old behavior might have allowed an adversary
3543 to use timing to guess the BridgePassword value. Fixes bug 5543;
3544 bugfix on 0.2.0.14-alpha.
3545 - Detect and reject certain misformed escape sequences in
3546 configuration values. Previously, these values would cause us
3547 to crash if received in a torrc file or over an authenticated
3548 control port. Bug found by Esteban Manchado Velázquez, and
3549 independently by Robert Connolly from Matta Consulting who further
3550 noted that it allows a post-authentication heap overflow. Patch
3551 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3552 bugfix on 0.2.0.16-alpha.
3553 - Fix a compile warning when using the --enable-openbsd-malloc
3554 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3555 - During configure, detect when we're building with clang version
3556 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3557 CFLAGS. clang doesn't support them yet.
3558 - When sending an HTTP/1.1 proxy request, include a Host header.
3559 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3560 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3561 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3562 - If we hit the error case where routerlist_insert() replaces an
3563 existing (old) server descriptor, make sure to remove that
3564 server descriptor from the old_routers list. Fix related to bug
3565 1776. Bugfix on 0.2.2.18-alpha.
3567 o Minor bugfixes (documentation and log messages):
3568 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3569 Fixes bug 4856; bugfix on Tor 0.0.6.
3570 - Update "ClientOnly" man page entry to explain that there isn't
3571 really any point to messing with it. Resolves ticket 5005.
3572 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3573 directory authority option (introduced in Tor 0.2.2.34).
3574 - Downgrade the "We're missing a certificate" message from notice
3575 to info: people kept mistaking it for a real problem, whereas it
3576 is seldom the problem even when we are failing to bootstrap. Fixes
3577 bug 5067; bugfix on 0.2.0.10-alpha.
3578 - Correctly spell "connect" in a log message on failure to create a
3579 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3580 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3581 circuits. Fixes issue 5259.
3584 - Directory authorities now reject versions of Tor older than
3585 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3586 inclusive. These versions accounted for only a small fraction of
3587 the Tor network, and have numerous known security issues. Resolves
3589 - Update to the May 1 2012 Maxmind GeoLite Country database.
3592 - When sending or relaying a RELAY_EARLY cell, we used to convert
3593 it to a RELAY cell if the connection was using the v1 link
3594 protocol. This was a workaround for older versions of Tor, which
3595 didn't handle RELAY_EARLY cells properly. Now that all supported
3596 versions can handle RELAY_EARLY cells, and now that we're enforcing
3597 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3598 remove this workaround. Addresses bug 4786.
3601 Changes in version 0.2.2.35 - 2011-12-16
3602 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3603 buffers code. Absolutely everybody should upgrade.
3605 The bug relied on an incorrect calculation when making data continuous
3606 in one of our IO buffers, if the first chunk of the buffer was
3607 misaligned by just the wrong amount. The miscalculation would allow an
3608 attacker to overflow a piece of heap-allocated memory. To mount this
3609 attack, the attacker would need to either open a SOCKS connection to
3610 Tor's SocksPort (usually restricted to localhost), or target a Tor
3611 instance configured to make its connections through a SOCKS proxy
3612 (which Tor does not do by default).
3614 Good security practice requires that all heap-overflow bugs should be
3615 presumed to be exploitable until proven otherwise, so we are treating
3616 this as a potential code execution attack. Please upgrade immediately!
3617 This bug does not affect bufferevents-based builds of Tor. Special
3618 thanks to "Vektor" for reporting this issue to us!
3620 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3621 crash bugs for unusual configurations, and a long-term bug that
3622 would prevent Tor from starting on Windows machines with draconian
3625 With this release, we remind everyone that 0.2.0.x has reached its
3626 formal end-of-life. Those Tor versions have many known flaws, and
3627 nobody should be using them. You should upgrade -- ideally to the
3628 0.2.2.x series. If you're using a Linux or BSD and its packages are
3629 obsolete, stop using those packages and upgrade anyway.
3631 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3632 longer receive support after some time in early 2012.
3635 - Fix a heap overflow bug that could occur when trying to pull
3636 data into the first chunk of a buffer, when that chunk had
3637 already had some data drained from it. Fixes CVE-2011-2778;
3638 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3639 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3640 that it doesn't attempt to allocate a socketpair. This could cause
3641 some problems on Windows systems with overzealous firewalls. Fix for
3642 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3644 - If we mark an OR connection for close based on a cell we process,
3645 don't process any further cells on it. We already avoid further
3646 reads on marked-for-close connections, but now we also discard the
3647 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3648 which was the first version where we might mark a connection for
3649 close based on processing a cell on it.
3650 - Correctly sanity-check that we don't underflow on a memory
3651 allocation (and then assert) for hidden service introduction
3652 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3653 bugfix on 0.2.1.5-alpha.
3654 - Fix a memory leak when we check whether a hidden service
3655 descriptor has any usable introduction points left. Fixes bug
3656 4424. Bugfix on 0.2.2.25-alpha.
3657 - Don't crash when we're running as a relay and don't have a GeoIP
3658 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3659 we've had in the 0.2.3.x branch already.
3660 - When running as a client, do not print a misleading (and plain
3661 wrong) log message that we're collecting "directory request"
3662 statistics: clients don't collect statistics. Also don't create a
3663 useless (because empty) stats file in the stats/ directory. Fixes
3664 bug 4353; bugfix on 0.2.2.34.
3667 - Detect failure to initialize Libevent. This fix provides better
3668 detection for future instances of bug 4457.
3669 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3670 function. This was eating up hideously large amounts of time on some
3671 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3672 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3673 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3675 - Don't warn about unused log_mutex in log.c when building with
3676 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3677 0.1.0.6-rc which introduced --disable-threads.
3678 - When configuring, starting, or stopping an NT service, stop
3679 immediately after the service configuration attempt has succeeded
3680 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3681 - When sending a NETINFO cell, include the original address
3682 received for the other side, not its canonical address. Found
3683 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3684 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3685 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3686 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3687 occurred when a client tried to fetch a descriptor for a bridge
3688 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3689 - Backport fixes for a pair of compilation warnings on Windows.
3690 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3691 - If we had ever tried to call tor_addr_to_str on an address of
3692 unknown type, we would have done a strdup on an uninitialized
3693 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3694 Reported by "troll_un".
3695 - Correctly detect and handle transient lookup failures from
3696 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3697 Reported by "troll_un".
3698 - Fix null-pointer access that could occur if TLS allocation failed.
3699 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3700 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3701 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3704 - Add two new config options for directory authorities:
3705 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3706 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3707 that is always sufficient to satisfy the bandwidth requirement for
3708 the Guard flag. Now it will be easier for researchers to simulate
3709 Tor networks with different values. Resolves ticket 4484.
3710 - When Tor ignores a hidden service specified in its configuration,
3711 include the hidden service's directory in the warning message.
3712 Previously, we would only tell the user that some hidden service
3713 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3714 - Update to the December 6 2011 Maxmind GeoLite Country database.
3716 o Packaging changes:
3717 - Make it easier to automate expert package builds on Windows,
3718 by removing an absolute path from makensis.exe command.
3721 Changes in version 0.2.1.32 - 2011-12-16
3722 Tor 0.2.1.32 backports important security and privacy fixes for
3723 oldstable. This release is intended only for package maintainers and
3724 others who cannot use the 0.2.2 stable series. All others should be
3725 using Tor 0.2.2.x or newer.
3727 The Tor 0.2.1.x series will reach formal end-of-life some time in
3728 early 2012; we will stop releasing patches for it then.
3730 o Major bugfixes (also included in 0.2.2.x):
3731 - Correctly sanity-check that we don't underflow on a memory
3732 allocation (and then assert) for hidden service introduction
3733 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3734 bugfix on 0.2.1.5-alpha.
3735 - Fix a heap overflow bug that could occur when trying to pull
3736 data into the first chunk of a buffer, when that chunk had
3737 already had some data drained from it. Fixes CVE-2011-2778;
3738 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3741 - Update to the December 6 2011 Maxmind GeoLite Country database.
3744 Changes in version 0.2.2.34 - 2011-10-26
3745 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3746 can deanonymize Tor users. Everybody should upgrade.
3748 The attack relies on four components: 1) Clients reuse their TLS cert
3749 when talking to different relays, so relays can recognize a user by
3750 the identity key in her cert. 2) An attacker who knows the client's
3751 identity key can probe each guard relay to see if that identity key
3752 is connected to that guard relay right now. 3) A variety of active
3753 attacks in the literature (starting from "Low-Cost Traffic Analysis
3754 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3755 discover the guard relays that a Tor user visiting the website is using.
3756 4) Clients typically pick three guards at random, so the set of guards
3757 for a given user could well be a unique fingerprint for her. This
3758 release fixes components #1 and #2, which is enough to block the attack;
3759 the other two remain as open research problems. Special thanks to
3760 "frosty_un" for reporting the issue to us!
3762 Clients should upgrade so they are no longer recognizable by the TLS
3763 certs they present. Relays should upgrade so they no longer allow a
3764 remote attacker to probe them to test whether unpatched clients are
3765 currently connected to them.
3767 This release also fixes several vulnerabilities that allow an attacker
3768 to enumerate bridge relays. Some bridge enumeration attacks still
3769 remain; see for example proposal 188.
3771 o Privacy/anonymity fixes (clients):
3772 - Clients and bridges no longer send TLS certificate chains on
3773 outgoing OR connections. Previously, each client or bridge would
3774 use the same cert chain for all outgoing OR connections until
3775 its IP address changes, which allowed any relay that the client
3776 or bridge contacted to determine which entry guards it is using.
3777 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3778 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3779 no longer considers that connection as suitable for satisfying a
3780 circuit EXTEND request. Now relays can protect clients from the
3781 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3782 - Directory authorities no longer assign the Guard flag to relays
3783 that haven't upgraded to the above "refuse EXTEND requests
3784 to client connections" fix. Now directory authorities can
3785 protect clients from the CVE-2011-2768 issue even if neither
3786 the clients nor the relays have upgraded yet. There's a new
3787 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3788 to let us transition smoothly, else tomorrow there would be no
3791 o Privacy/anonymity fixes (bridge enumeration):
3792 - Bridge relays now do their directory fetches inside Tor TLS
3793 connections, like all the other clients do, rather than connecting
3794 directly to the DirPort like public relays do. Removes another
3795 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3796 - Bridges relays now build circuits for themselves in a more similar
3797 way to how clients build them. Removes another avenue for
3798 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3799 when bridges were introduced.
3800 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3801 that they initiated. Relays could distinguish incoming bridge
3802 connections from client connections, creating another avenue for
3803 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3804 Found by "frosty_un".
3807 - Fix a crash bug when changing node restrictions while a DNS lookup
3808 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3810 - Don't launch a useless circuit after failing to use one of a
3811 hidden service's introduction points. Previously, we would
3812 launch a new introduction circuit, but not set the hidden service
3813 which that circuit was intended to connect to, so it would never
3814 actually be used. A different piece of code would then create a
3815 new introduction circuit correctly. Bug reported by katmagic and
3816 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3819 - Change an integer overflow check in the OpenBSD_Malloc code so
3820 that GCC is less likely to eliminate it as impossible. Patch
3821 from Mansour Moufid. Fixes bug 4059.
3822 - When a hidden service turns an extra service-side introduction
3823 circuit into a general-purpose circuit, free the rend_data and
3824 intro_key fields first, so we won't leak memory if the circuit
3825 is cannibalized for use as another service-side introduction
3826 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3827 - Bridges now skip DNS self-tests, to act a little more stealthily.
3828 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3829 bridges. Patch by "warms0x".
3830 - Fix internal bug-checking logic that was supposed to catch
3831 failures in digest generation so that it will fail more robustly
3832 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3833 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3834 - Report any failure in init_keys() calls launched because our
3835 IP address has changed. Spotted by Coverity Scan. Bugfix on
3836 0.1.1.4-alpha; fixes CID 484.
3838 o Minor bugfixes (log messages and documentation):
3839 - Remove a confusing dollar sign from the example fingerprint in the
3840 man page, and also make the example fingerprint a valid one. Fixes
3841 bug 4309; bugfix on 0.2.1.3-alpha.
3842 - The next version of Windows will be called Windows 8, and it has
3843 a major version of 6, minor version of 2. Correctly identify that
3844 version instead of calling it "Very recent version". Resolves
3845 ticket 4153; reported by funkstar.
3846 - Downgrade log messages about circuit timeout calibration from
3847 "notice" to "info": they don't require or suggest any human
3848 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3849 bugfix on 0.2.2.14-alpha.
3852 - Turn on directory request statistics by default and include them in
3853 extra-info descriptors. Don't break if we have no GeoIP database.
3854 Backported from 0.2.3.1-alpha; implements ticket 3951.
3855 - Update to the October 4 2011 Maxmind GeoLite Country database.
3858 Changes in version 0.2.1.31 - 2011-10-26
3859 Tor 0.2.1.31 backports important security and privacy fixes for
3860 oldstable. This release is intended only for package maintainers and
3861 others who cannot use the 0.2.2 stable series. All others should be
3862 using Tor 0.2.2.x or newer.
3864 o Security fixes (also included in 0.2.2.x):
3865 - Replace all potentially sensitive memory comparison operations
3866 with versions whose runtime does not depend on the data being
3867 compared. This will help resist a class of attacks where an
3868 adversary can use variations in timing information to learn
3869 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3870 implementation by Robert Ransom based partially on code by DJB.)
3871 - Fix an assert in parsing router descriptors containing IPv6
3872 addresses. This one took down the directory authorities when
3873 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3875 o Privacy/anonymity fixes (also included in 0.2.2.x):
3876 - Clients and bridges no longer send TLS certificate chains on
3877 outgoing OR connections. Previously, each client or bridge would
3878 use the same cert chain for all outgoing OR connections until
3879 its IP address changes, which allowed any relay that the client
3880 or bridge contacted to determine which entry guards it is using.
3881 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3882 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3883 no longer considers that connection as suitable for satisfying a
3884 circuit EXTEND request. Now relays can protect clients from the
3885 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3886 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3887 that they initiated. Relays could distinguish incoming bridge
3888 connections from client connections, creating another avenue for
3889 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3890 Found by "frosty_un".
3891 - When receiving a hidden service descriptor, check that it is for
3892 the hidden service we wanted. Previously, Tor would store any
3893 hidden service descriptors that a directory gave it, whether it
3894 wanted them or not. This wouldn't have let an attacker impersonate
3895 a hidden service, but it did let directories pre-seed a client
3896 with descriptors that it didn't want. Bugfix on 0.0.6.
3897 - Avoid linkability based on cached hidden service descriptors: forget
3898 all hidden service descriptors cached as a client when processing a
3899 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3900 - Make the bridge directory authority refuse to answer directory
3901 requests for "all" descriptors. It used to include bridge
3902 descriptors in its answer, which was a major information leak.
3903 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3904 - Don't attach new streams to old rendezvous circuits after SIGNAL
3905 NEWNYM. Previously, we would keep using an existing rendezvous
3906 circuit if it remained open (i.e. if it were kept open by a
3907 long-lived stream, or if a new stream were attached to it before
3908 Tor could notice that it was old and no longer in use). Bugfix on
3909 0.1.1.15-rc; fixes bug 3375.
3911 o Minor bugfixes (also included in 0.2.2.x):
3912 - When we restart our relay, we might get a successful connection
3913 from the outside before we've started our reachability tests,
3914 triggering a warning: "ORPort found reachable, but I have no
3915 routerinfo yet. Failing to inform controller of success." This
3916 bug was harmless unless Tor is running under a controller
3917 like Vidalia, in which case the controller would never get a
3918 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3920 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3921 enabled. Fixes bug 1526.
3922 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3923 anything since 0.2.1.16-rc.
3924 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3925 None of the cases where we did this before were wrong, but by making
3926 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3927 - Fix a rare crash bug that could occur when a client was configured
3928 with a large number of bridges. Fixes bug 2629; bugfix on
3929 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3930 - Correct the warning displayed when a rendezvous descriptor exceeds
3931 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3933 - Fix an uncommon assertion failure when running with DNSPort under
3934 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3935 - When warning about missing zlib development packages during compile,
3936 give the correct package names. Bugfix on 0.2.0.1-alpha.
3937 - Require that introduction point keys and onion keys have public
3938 exponent 65537. Bugfix on 0.2.0.10-alpha.
3939 - Do not crash when our configuration file becomes unreadable, for
3940 example due to a permissions change, between when we start up
3941 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3943 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3945 - Always NUL-terminate the sun_path field of a sockaddr_un before
3946 passing it to the kernel. (Not a security issue: kernels are
3947 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3948 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3949 - Don't stack-allocate the list of supplementary GIDs when we're
3950 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3951 could take up to 256K, which is way too much stack. Found by
3952 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3954 o Minor bugfixes (only in 0.2.1.x):
3955 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3956 rely on them. Bugfix on 0.2.1.30.
3957 - Use git revisions instead of svn revisions when generating our
3958 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3960 o Minor features (also included in 0.2.2.x):
3961 - Adjust the expiration time on our SSL session certificates to
3962 better match SSL certs seen in the wild. Resolves ticket 4014.
3963 - Allow nameservers with IPv6 address. Resolves bug 2574.
3964 - Update to the October 4 2011 Maxmind GeoLite Country database.
3967 Changes in version 0.2.2.33 - 2011-09-13
3968 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3969 TLS handshake that makes relays and bridges that run this new version
3970 reachable from Iran again.
3973 - Avoid an assertion failure when reloading a configuration with
3974 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3975 3923; bugfix on 0.2.2.25-alpha.
3977 o Minor features (security):
3978 - Check for replays of the public-key encrypted portion of an
3979 INTRODUCE1 cell, in addition to the current check for replays of
3980 the g^x value. This prevents a possible class of active attacks
3981 by an attacker who controls both an introduction point and a
3982 rendezvous point, and who uses the malleability of AES-CTR to
3983 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3984 that these attacks are infeasible (requiring the attacker to send
3985 on the order of zettabytes of altered cells in a short interval),
3986 but we'd rather block them off in case there are any classes of
3987 this attack that we missed. Reported by Willem Pinckaers.
3990 - Adjust the expiration time on our SSL session certificates to
3991 better match SSL certs seen in the wild. Resolves ticket 4014.
3992 - Change the default required uptime for a relay to be accepted as
3993 a HSDir (hidden service directory) from 24 hours to 25 hours.
3994 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3995 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3996 authorities to abstain from voting on assignment of the HSDir
3997 consensus flag. Related to bug 2649.
3998 - Update to the September 6 2011 Maxmind GeoLite Country database.
4000 o Minor bugfixes (documentation and log messages):
4001 - Correct the man page to explain that HashedControlPassword and
4002 CookieAuthentication can both be set, in which case either method
4003 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4004 when we decided to allow these config options to both be set. Issue
4006 - Demote the 'replay detected' log message emitted when a hidden
4007 service receives the same Diffie-Hellman public key in two different
4008 INTRODUCE2 cells to info level. A normal Tor client can cause that
4009 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4010 fixes part of bug 2442.
4011 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4012 level. There is nothing that a hidden service's operator can do
4013 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4015 - Clarify a log message specifying the characters permitted in
4016 HiddenServiceAuthorizeClient client names. Previously, the log
4017 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4018 given the impression that every ASCII character between "+" and "_"
4019 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4022 - Provide a substitute implementation of lround() for MSVC, which
4023 apparently lacks it. Patch from Gisle Vanem.
4024 - Clean up some code issues that prevented Tor from building on older
4025 BSDs. Fixes bug 3894; reported by "grarpamp".
4026 - Search for a platform-specific version of "ar" when cross-compiling.
4027 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4030 Changes in version 0.2.2.32 - 2011-08-27
4031 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4032 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4033 a founder of the PETS community, a leader in our field, a mentor,
4034 and a friend. He left us with these words: "I had the possibility
4035 to contribute to this world that is not as it should be. I hope I
4036 could help in some areas to make the world a better place, and that
4037 I could also encourage other people to be engaged in improving the
4038 world. Please, stay engaged. This world needs you, your love, your
4039 initiative -- now I cannot be part of that anymore."
4041 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4042 ready. More than two years in the making, this release features improved
4043 client performance and hidden service reliability, better compatibility
4044 for Android, correct behavior for bridges that listen on more than
4045 one address, more extensible and flexible directory object handling,
4046 better reporting of network statistics, improved code security, and
4047 many many other features and bugfixes.
4049 o Major features (client performance):
4050 - When choosing which cells to relay first, relays now favor circuits
4051 that have been quiet recently, to provide lower latency for
4052 low-volume circuits. By default, relays enable or disable this
4053 feature based on a setting in the consensus. They can override
4054 this default by using the new "CircuitPriorityHalflife" config
4055 option. Design and code by Ian Goldberg, Can Tang, and Chris
4057 - Directory authorities now compute consensus weightings that instruct
4058 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4059 and no flag. Clients use these weightings to distribute network load
4060 more evenly across these different relay types. The weightings are
4061 in the consensus so we can change them globally in the future. Extra
4062 thanks to "outofwords" for finding some nasty security bugs in
4063 the first implementation of this feature.
4065 o Major features (client performance, circuit build timeout):
4066 - Tor now tracks how long it takes to build client-side circuits
4067 over time, and adapts its timeout to local network performance.
4068 Since a circuit that takes a long time to build will also provide
4069 bad performance, we get significant latency improvements by
4070 discarding the slowest 20% of circuits. Specifically, Tor creates
4071 circuits more aggressively than usual until it has enough data
4072 points for a good timeout estimate. Implements proposal 151.
4073 - Circuit build timeout constants can be controlled by consensus
4074 parameters. We set good defaults for these parameters based on
4075 experimentation on broadband and simulated high-latency links.
4076 - Circuit build time learning can be disabled via consensus parameter
4077 or by the client via a LearnCircuitBuildTimeout config option. We
4078 also automatically disable circuit build time calculation if either
4079 AuthoritativeDirectory is set, or if we fail to write our state
4080 file. Implements ticket 1296.
4082 o Major features (relays use their capacity better):
4083 - Set SO_REUSEADDR socket option on all sockets, not just
4084 listeners. This should help busy exit nodes avoid running out of
4085 useable ports just because all the ports have been used in the
4086 near past. Resolves issue 2850.
4087 - Relays now save observed peak bandwidth throughput rates to their
4088 state file (along with total usage, which was already saved),
4089 so that they can determine their correct estimated bandwidth on
4090 restart. Resolves bug 1863, where Tor relays would reset their
4091 estimated bandwidth to 0 after restarting.
4092 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4093 should give us approximately 40-50% more Guard-flagged nodes,
4094 improving the anonymity the Tor network can provide and also
4095 decreasing the dropoff in throughput that relays experience when
4096 they first get the Guard flag.
4097 - Directory authorities now take changes in router IP address and
4098 ORPort into account when determining router stability. Previously,
4099 if a router changed its IP or ORPort, the authorities would not
4100 treat it as having any downtime for the purposes of stability
4101 calculation, whereas clients would experience downtime since the
4102 change would take a while to propagate to them. Resolves issue 1035.
4103 - New AccelName and AccelDir options add support for dynamic OpenSSL
4104 hardware crypto acceleration engines.
4106 o Major features (relays control their load better):
4107 - Exit relays now try harder to block exit attempts from unknown
4108 relays, to make it harder for people to use them as one-hop proxies
4109 a la tortunnel. Controlled by the refuseunknownexits consensus
4110 parameter (currently enabled), or you can override it on your
4111 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
4112 based on a variant of proposal 163.
4113 - Add separate per-conn write limiting to go with the per-conn read
4114 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4115 but never per-conn write limits.
4116 - New consensus params "bwconnrate" and "bwconnburst" to let us
4117 rate-limit client connections as they enter the network. It's
4118 controlled in the consensus so we can turn it on and off for
4119 experiments. It's starting out off. Based on proposal 163.
4121 o Major features (controllers):
4122 - Export GeoIP information on bridge usage to controllers even if we
4123 have not yet been running for 24 hours. Now Vidalia bridge operators
4124 can get more accurate and immediate feedback about their
4125 contributions to the network.
4126 - Add an __OwningControllerProcess configuration option and a
4127 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4128 that when it exits, Tor will shut down. Implements feature 3049.
4130 o Major features (directory authorities):
4131 - Directory authorities now create, vote on, and serve multiple
4132 parallel formats of directory data as part of their voting process.
4133 Partially implements Proposal 162: "Publish the consensus in
4135 - Directory authorities now agree on and publish small summaries
4136 of router information that clients can use in place of regular
4137 server descriptors. This transition will allow Tor 0.2.3 clients
4138 to use far less bandwidth for downloading information about the
4139 network. Begins the implementation of Proposal 158: "Clients
4140 download consensus + microdescriptors".
4141 - The directory voting system is now extensible to use multiple hash
4142 algorithms for signatures and resource selection. Newer formats
4143 are signed with SHA256, with a possibility for moving to a better
4144 hash algorithm in the future.
4145 - Directory authorities can now vote on arbitary integer values as
4146 part of the consensus process. This is designed to help set
4147 network-wide parameters. Implements proposal 167.
4149 o Major features and bugfixes (node selection):
4150 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4151 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
4152 options. Previously, we had been ambiguous in describing what
4153 counted as an "exit" node, and what operations exactly "StrictNodes
4154 0" would permit. This created confusion when people saw nodes built
4155 through unexpected circuits, and made it hard to tell real bugs from
4156 surprises. Now the intended behavior is:
4157 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4158 a node that delivers user traffic outside the Tor network.
4159 . "Entry", in the context of EntryNodes, means a node used as the
4160 first hop of a multihop circuit. It doesn't include direct
4161 connections to directory servers.
4162 . "ExcludeNodes" applies to all nodes.
4163 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4164 StrictNodes is set, Tor should avoid all nodes listed in
4165 ExcludeNodes, even when it will make user requests fail. When
4166 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4167 whenever it can, except when it must use an excluded node to
4168 perform self-tests, connect to a hidden service, provide a
4169 hidden service, fulfill a .exit request, upload directory
4170 information, or fetch directory information.
4171 Collectively, the changes to implement the behavior fix bug 1090.
4172 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4173 change during a config reload, mark and discard all our origin
4174 circuits. This fix should address edge cases where we change the
4175 config options and but then choose a circuit that we created before
4177 - Make EntryNodes config option much more aggressive even when
4178 StrictNodes is not set. Before it would prepend your requested
4179 entrynodes to your list of guard nodes, but feel free to use others
4180 after that. Now it chooses only from your EntryNodes if any of
4181 those are available, and only falls back to others if a) they're
4182 all down and b) StrictNodes is not set.
4183 - Now we refresh your entry guards from EntryNodes at each consensus
4184 fetch -- rather than just at startup and then they slowly rot as
4185 the network changes.
4186 - Add support for the country code "{??}" in torrc options like
4187 ExcludeNodes, to indicate all routers of unknown country. Closes
4189 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4190 a node is listed in both, it's treated as excluded.
4191 - ExcludeNodes now applies to directory nodes -- as a preference if
4192 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4193 Don't exclude all the directory authorities and set StrictNodes to 1
4194 unless you really want your Tor to break.
4195 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4196 - ExcludeExitNodes now overrides .exit requests.
4197 - We don't use bridges listed in ExcludeNodes.
4198 - When StrictNodes is 1:
4199 . We now apply ExcludeNodes to hidden service introduction points
4200 and to rendezvous points selected by hidden service users. This
4201 can make your hidden service less reliable: use it with caution!
4202 . If we have used ExcludeNodes on ourself, do not try relay
4203 reachability self-tests.
4204 . If we have excluded all the directory authorities, we will not
4205 even try to upload our descriptor if we're a relay.
4206 . Do not honor .exit requests to an excluded node.
4207 - When the set of permitted nodes changes, we now remove any mappings
4208 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4210 - We never cannibalize a circuit that had excluded nodes on it, even
4211 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4212 - Improve log messages related to excluded nodes.
4214 o Major features (misc):
4215 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4216 to help Tor build correctly for Android phones.
4217 - The options SocksPort, ControlPort, and so on now all accept a
4218 value "auto" that opens a socket on an OS-selected port. A
4219 new ControlPortWriteToFile option tells Tor to write its
4220 actual control port or ports to a chosen file. If the option
4221 ControlPortFileGroupReadable is set, the file is created as
4222 group-readable. Now users can run two Tor clients on the same
4223 system without needing to manually mess with parameters. Resolves
4224 part of ticket 3076.
4225 - Tor now supports tunneling all of its outgoing connections over
4226 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
4227 configuration options. Code by Christopher Davis.
4229 o Code security improvements:
4230 - Replace all potentially sensitive memory comparison operations
4231 with versions whose runtime does not depend on the data being
4232 compared. This will help resist a class of attacks where an
4233 adversary can use variations in timing information to learn
4234 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4235 implementation by Robert Ransom based partially on code by DJB.)
4236 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4237 Prevention (DEP) by default on Windows to make it harder for
4238 attackers to exploit vulnerabilities. Patch from John Brooks.
4239 - New "--enable-gcc-hardening" ./configure flag (off by default)
4240 to turn on gcc compile time hardening options. It ensures
4241 that signed ints have defined behavior (-fwrapv), enables
4242 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4243 with canaries (-fstack-protector-all), turns on ASLR protection if
4244 supported by the kernel (-fPIE, -pie), and adds additional security
4245 related warnings. Verified to work on Mac OS X and Debian Lenny.
4246 - New "--enable-linker-hardening" ./configure flag (off by default)
4247 to turn on ELF specific hardening features (relro, now). This does
4248 not work with Mac OS X or any other non-ELF binary format.
4249 - Always search the Windows system directory for system DLLs, and
4250 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4251 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4252 current and future memory pages via mlockall(). On supported
4253 platforms (modern Linux and probably BSD but not Windows or OS X),
4254 this should effectively disable any and all attempts to page out
4255 memory. This option requires that you start your Tor as root --
4256 if you use DisableAllSwap, please consider using the User option
4257 to properly reduce the privileges of your Tor.
4259 o Major bugfixes (crashes):
4260 - Fix crash bug on platforms where gmtime and localtime can return
4261 NULL. Windows 7 users were running into this one. Fixes part of bug
4262 2077. Bugfix on all versions of Tor. Found by boboper.
4263 - Introduce minimum/maximum values that clients will believe
4264 from the consensus. Now we'll have a better chance to avoid crashes
4265 or worse when a consensus param has a weird value.
4266 - Fix a rare crash bug that could occur when a client was configured
4267 with a large number of bridges. Fixes bug 2629; bugfix on
4268 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4269 - Do not crash when our configuration file becomes unreadable, for
4270 example due to a permissions change, between when we start up
4271 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4273 - If we're in the pathological case where there's no exit bandwidth
4274 but there is non-exit bandwidth, or no guard bandwidth but there
4275 is non-guard bandwidth, don't crash during path selection. Bugfix
4277 - Fix a crash bug when trying to initialize the evdns module in
4278 Libevent 2. Bugfix on 0.2.1.16-rc.
4280 o Major bugfixes (stability):
4281 - Fix an assert in parsing router descriptors containing IPv6
4282 addresses. This one took down the directory authorities when
4283 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4284 - Fix an uncommon assertion failure when running with DNSPort under
4285 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4286 - Treat an unset $HOME like an empty $HOME rather than triggering an
4287 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4288 - More gracefully handle corrupt state files, removing asserts
4289 in favor of saving a backup and resetting state.
4290 - Instead of giving an assertion failure on an internal mismatch
4291 on estimated freelist size, just log a BUG warning and try later.
4292 Mitigates but does not fix bug 1125.
4293 - Fix an assert that got triggered when using the TestingTorNetwork
4294 configuration option and then issuing a GETINFO config-text control
4295 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
4296 - If the cached cert file is unparseable, warn but don't exit.
4298 o Privacy fixes (relays/bridges):
4299 - Don't list Windows capabilities in relay descriptors. We never made
4300 use of them, and maybe it's a bad idea to publish them. Bugfix
4302 - If the Nickname configuration option isn't given, Tor would pick a
4303 nickname based on the local hostname as the nickname for a relay.
4304 Because nicknames are not very important in today's Tor and the
4305 "Unnamed" nickname has been implemented, this is now problematic
4306 behavior: It leaks information about the hostname without being
4307 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4308 introduced the Unnamed nickname. Reported by tagnaq.
4309 - Maintain separate TLS contexts and certificates for incoming and
4310 outgoing connections in bridge relays. Previously we would use the
4311 same TLS contexts and certs for incoming and outgoing connections.
4312 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4313 - Maintain separate identity keys for incoming and outgoing TLS
4314 contexts in bridge relays. Previously we would use the same
4315 identity keys for incoming and outgoing TLS contexts. Bugfix on
4316 0.2.0.3-alpha; addresses the other half of bug 988.
4317 - Make the bridge directory authority refuse to answer directory
4318 requests for "all descriptors". It used to include bridge
4319 descriptors in its answer, which was a major information leak.
4320 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4322 o Privacy fixes (clients):
4323 - When receiving a hidden service descriptor, check that it is for
4324 the hidden service we wanted. Previously, Tor would store any
4325 hidden service descriptors that a directory gave it, whether it
4326 wanted them or not. This wouldn't have let an attacker impersonate
4327 a hidden service, but it did let directories pre-seed a client
4328 with descriptors that it didn't want. Bugfix on 0.0.6.
4329 - Start the process of disabling ".exit" address notation, since it
4330 can be used for a variety of esoteric application-level attacks
4331 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
4333 - Reject attempts at the client side to open connections to private
4334 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
4335 a randomly chosen exit node. Attempts to do so are always
4336 ill-defined, generally prevented by exit policies, and usually
4337 in error. This will also help to detect loops in transparent
4338 proxy configurations. You can disable this feature by setting
4339 "ClientRejectInternalAddresses 0" in your torrc.
4340 - Log a notice when we get a new control connection. Now it's easier
4341 for security-conscious users to recognize when a local application
4342 is knocking on their controller door. Suggested by bug 1196.
4344 o Privacy fixes (newnym):
4345 - Avoid linkability based on cached hidden service descriptors: forget
4346 all hidden service descriptors cached as a client when processing a
4347 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4348 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4349 DNS cache entries, and virtual address mappings: that's what
4350 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4351 - Don't attach new streams to old rendezvous circuits after SIGNAL
4352 NEWNYM. Previously, we would keep using an existing rendezvous
4353 circuit if it remained open (i.e. if it were kept open by a
4354 long-lived stream, or if a new stream were attached to it before
4355 Tor could notice that it was old and no longer in use). Bugfix on
4356 0.1.1.15-rc; fixes bug 3375.
4358 o Major bugfixes (relay bandwidth accounting):
4359 - Fix a bug that could break accounting on 64-bit systems with large
4360 time_t values, making them hibernate for impossibly long intervals.
4361 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
4362 - Fix a bug in bandwidth accounting that could make us use twice
4363 the intended bandwidth when our interval start changes due to
4364 daylight saving time. Now we tolerate skew in stored vs computed
4365 interval starts: if the start of the period changes by no more than
4366 50% of the period's duration, we remember bytes that we transferred
4367 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4369 o Major bugfixes (bridges):
4370 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4371 on 0.2.0.3-alpha. Fixes bug 1113.
4372 - If you configure your bridge with a known identity fingerprint,
4373 and the bridge authority is unreachable (as it is in at least
4374 one country now), fall back to directly requesting the descriptor
4375 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4377 - Fix a bug where bridge users who configure the non-canonical
4378 address of a bridge automatically switch to its canonical
4379 address. If a bridge listens at more than one address, it
4380 should be able to advertise those addresses independently and
4381 any non-blocked addresses should continue to work. Bugfix on Tor
4382 0.2.0.3-alpha. Fixes bug 2510.
4383 - If you configure Tor to use bridge A, and then quit and
4384 configure Tor to use bridge B instead (or if you change Tor
4385 to use bridge B via the controller), it would happily continue
4386 to use bridge A if it's still reachable. While this behavior is
4387 a feature if your goal is connectivity, in some scenarios it's a
4388 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4389 - When the controller configures a new bridge, don't wait 10 to 60
4390 seconds before trying to fetch its descriptor. Bugfix on
4391 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4393 o Major bugfixes (directory authorities):
4394 - Many relays have been falling out of the consensus lately because
4395 not enough authorities know about their descriptor for them to get
4396 a majority of votes. When we deprecated the v2 directory protocol,
4397 we got rid of the only way that v3 authorities can hear from each
4398 other about other descriptors. Now authorities examine every v3
4399 vote for new descriptors, and fetch them from that authority. Bugfix
4401 - Authorities could be tricked into giving out the Exit flag to relays
4402 that didn't allow exiting to any ports. This bug could screw
4403 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4404 1238. Bug discovered by Martin Kowalczyk.
4405 - If all authorities restart at once right before a consensus vote,
4406 nobody will vote about "Running", and clients will get a consensus
4407 with no usable relays. Instead, authorities refuse to build a
4408 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4410 o Major bugfixes (stream-level fairness):
4411 - When receiving a circuit-level SENDME for a blocked circuit, try
4412 to package cells fairly from all the streams that had previously
4413 been blocked on that circuit. Previously, we had started with the
4414 oldest stream, and allowed each stream to potentially exhaust
4415 the circuit's package window. This gave older streams on any
4416 given circuit priority over newer ones. Fixes bug 1937. Detected
4417 originally by Camilo Viecco. This bug was introduced before the
4418 first Tor release, in svn commit r152: it is the new winner of
4419 the longest-lived bug prize.
4420 - Fix a stream fairness bug that would cause newer streams on a given
4421 circuit to get preference when reading bytes from the origin or
4422 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
4423 introduced before the first Tor release, in svn revision r152.
4424 - When the exit relay got a circuit-level sendme cell, it started
4425 reading on the exit streams, even if had 500 cells queued in the
4426 circuit queue already, so the circuit queue just grew and grew in
4427 some cases. We fix this by not re-enabling reading on receipt of a
4428 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4429 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4431 - Newly created streams were allowed to read cells onto circuits,
4432 even if the circuit's cell queue was blocked and waiting to drain.
4433 This created potential unfairness, as older streams would be
4434 blocked, but newer streams would gladly fill the queue completely.
4435 We add code to detect this situation and prevent any stream from
4436 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4439 o Major bugfixes (hidden services):
4440 - Apply circuit timeouts to opened hidden-service-related circuits
4441 based on the correct start time. Previously, we would apply the
4442 circuit build timeout based on time since the circuit's creation;
4443 it was supposed to be applied based on time since the circuit
4444 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4445 - Improve hidden service robustness: When we find that we have
4446 extended a hidden service's introduction circuit to a relay not
4447 listed as an introduction point in the HS descriptor we currently
4448 have, retry with an introduction point from the current
4449 descriptor. Previously we would just give up. Fixes bugs 1024 and
4450 1930; bugfix on 0.2.0.10-alpha.
4451 - Directory authorities now use data collected from their own
4452 uptime observations when choosing whether to assign the HSDir flag
4453 to relays, instead of trusting the uptime value the relay reports in
4454 its descriptor. This change helps prevent an attack where a small
4455 set of nodes with frequently-changing identity keys can blackhole
4456 a hidden service. (Only authorities need upgrade; others will be
4457 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4458 - Stop assigning the HSDir flag to relays that disable their
4459 DirPort (and thus will refuse to answer directory requests). This
4460 fix should dramatically improve the reachability of hidden services:
4461 hidden services and hidden service clients pick six HSDir relays
4462 to store and retrieve the hidden service descriptor, and currently
4463 about half of the HSDir relays will refuse to work. Bugfix on
4464 0.2.0.10-alpha; fixes part of bug 1693.
4466 o Major bugfixes (misc):
4467 - Clients now stop trying to use an exit node associated with a given
4468 destination by TrackHostExits if they fail to reach that exit node.
4469 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4470 - Fix a regression that caused Tor to rebind its ports if it receives
4471 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4472 - Remove an extra pair of quotation marks around the error
4473 message in control-port STATUS_GENERAL BUG events. Bugfix on
4474 0.1.2.6-alpha; fixes bug 3732.
4476 o Minor features (relays):
4477 - Ensure that no empty [dirreq-](read|write)-history lines are added
4478 to an extrainfo document. Implements ticket 2497.
4479 - When bandwidth accounting is enabled, be more generous with how
4480 much bandwidth we'll use up before entering "soft hibernation".
4481 Previously, we'd refuse new connections and circuits once we'd
4482 used up 95% of our allotment. Now, we use up 95% of our allotment,
4483 AND make sure that we have no more than 500MB (or 3 hours of
4484 expected traffic, whichever is lower) remaining before we enter
4486 - Relays now log the reason for publishing a new relay descriptor,
4487 so we have a better chance of hunting down instances of bug 1810.
4488 Resolves ticket 3252.
4489 - Log a little more clearly about the times at which we're no longer
4490 accepting new connections (e.g. due to hibernating). Resolves
4492 - When AllowSingleHopExits is set, print a warning to explain to the
4493 relay operator why most clients are avoiding her relay.
4494 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4495 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4496 clients are already deprecated because of security bugs.
4498 o Minor features (network statistics):
4499 - Directory mirrors that set "DirReqStatistics 1" write statistics
4500 about directory requests to disk every 24 hours. As compared to the
4501 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
4502 improvements: 1) stats are written to disk exactly every 24 hours;
4503 2) estimated shares of v2 and v3 requests are determined as mean
4504 values, not at the end of a measurement period; 3) unresolved
4505 requests are listed with country code '??'; 4) directories also
4506 measure download times.
4507 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
4508 number of exit streams and transferred bytes per port to disk every
4510 - Relays that set "CellStatistics 1" write statistics on how long
4511 cells spend in their circuit queues to disk every 24 hours.
4512 - Entry nodes that set "EntryStatistics 1" write statistics on the
4513 rough number and origins of connecting clients to disk every 24
4515 - Relays that write any of the above statistics to disk and set
4516 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
4517 their extra-info documents. Implements proposal 166.
4519 o Minor features (GeoIP and statistics):
4520 - Provide a log message stating which geoip file we're parsing
4521 instead of just stating that we're parsing the geoip file.
4522 Implements ticket 2432.
4523 - Make sure every relay writes a state file at least every 12 hours.
4524 Previously, a relay could go for weeks without writing its state
4525 file, and on a crash could lose its bandwidth history, capacity
4526 estimates, client country statistics, and so on. Addresses bug 3012.
4527 - Relays report the number of bytes spent on answering directory
4528 requests in extra-info descriptors similar to {read,write}-history.
4529 Implements enhancement 1790.
4530 - Report only the top 10 ports in exit-port stats in order not to
4531 exceed the maximum extra-info descriptor length of 50 KB. Implements
4533 - If writing the state file to disk fails, wait up to an hour before
4534 retrying again, rather than trying again each second. Fixes bug
4535 2346; bugfix on Tor 0.1.1.3-alpha.
4536 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4537 when we switch from being a public relay to a bridge. Otherwise
4538 there will still be clients that see the relay in their consensus,
4539 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
4541 - Update to the August 2 2011 Maxmind GeoLite Country database.
4543 o Minor features (clients):
4544 - When expiring circuits, use microsecond timers rather than
4545 one-second timers. This can avoid an unpleasant situation where a
4546 circuit is launched near the end of one second and expired right
4547 near the beginning of the next, and prevent fluctuations in circuit
4549 - If we've configured EntryNodes and our network goes away and/or all
4550 our entrynodes get marked down, optimistically retry them all when
4551 a new socks application request appears. Fixes bug 1882.
4552 - Always perform router selections using weighted relay bandwidth,
4553 even if we don't need a high capacity circuit at the time. Non-fast
4554 circuits now only differ from fast ones in that they can use relays
4555 not marked with the Fast flag. This "feature" could turn out to
4556 be a horrible bug; we should investigate more before it goes into
4558 - When we run out of directory information such that we can't build
4559 circuits, but then get enough that we can build circuits, log when
4560 we actually construct a circuit, so the user has a better chance of
4561 knowing what's going on. Fixes bug 1362.
4562 - Log SSL state transitions at debug level during handshake, and
4563 include SSL states in error messages. This may help debug future
4564 SSL handshake issues.
4566 o Minor features (directory authorities):
4567 - When a router changes IP address or port, authorities now launch
4568 a new reachability test for it. Implements ticket 1899.
4569 - Directory authorities now reject relays running any versions of
4570 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4571 known bugs that keep RELAY_EARLY cells from working on rendezvous
4572 circuits. Followup to fix for bug 2081.
4573 - Directory authorities now reject relays running any version of Tor
4574 older than 0.2.0.26-rc. That version is the earliest that fetches
4575 current directory information correctly. Fixes bug 2156.
4576 - Directory authorities now do an immediate reachability check as soon
4577 as they hear about a new relay. This change should slightly reduce
4578 the time between setting up a relay and getting listed as running
4579 in the consensus. It should also improve the time between setting
4580 up a bridge and seeing use by bridge users.
4581 - Directory authorities no longer launch a TLS connection to every
4582 relay as they startup. Now that we have 2k+ descriptors cached,
4583 the resulting network hiccup is becoming a burden. Besides,
4584 authorities already avoid voting about Running for the first half
4585 hour of their uptime.
4586 - Directory authorities now log the source of a rejected POSTed v3
4587 networkstatus vote, so we can track failures better.
4588 - Backport code from 0.2.3.x that allows directory authorities to
4589 clean their microdescriptor caches. Needed to resolve bug 2230.
4591 o Minor features (hidden services):
4592 - Use computed circuit-build timeouts to decide when to launch
4593 parallel introduction circuits for hidden services. (Previously,
4594 we would retry after 15 seconds.)
4595 - Don't allow v0 hidden service authorities to act as clients.
4596 Required by fix for bug 3000.
4597 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4598 by fix for bug 3000.
4599 - Make hidden services work better in private Tor networks by not
4600 requiring any uptime to join the hidden service descriptor
4601 DHT. Implements ticket 2088.
4602 - Log (at info level) when purging pieces of hidden-service-client
4603 state because of SIGNAL NEWNYM.
4605 o Minor features (controller interface):
4606 - New "GETINFO net/listeners/(type)" controller command to return
4607 a list of addresses and ports that are bound for listeners for a
4608 given connection type. This is useful when the user has configured
4609 "SocksPort auto" and the controller needs to know which port got
4610 chosen. Resolves another part of ticket 3076.
4611 - Have the controller interface give a more useful message than
4612 "Internal Error" in response to failed GETINFO requests.
4613 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4614 event, to give information on the current rate of circuit timeouts
4615 over our stored history.
4616 - The 'EXTENDCIRCUIT' control port command can now be used with
4617 a circ id of 0 and no path. This feature will cause Tor to build
4618 a new 'fast' general purpose circuit using its own path selection
4620 - Added a BUILDTIMEOUT_SET controller event to describe changes
4621 to the circuit build timeout.
4622 - New controller command "getinfo config-text". It returns the
4623 contents that Tor would write if you send it a SAVECONF command,
4624 so the controller can write the file to disk itself.
4626 o Minor features (controller protocol):
4627 - Add a new ControlSocketsGroupWritable configuration option: when
4628 it is turned on, ControlSockets are group-writeable by the default
4629 group of the current user. Patch by Jérémy Bobbio; implements
4631 - Tor now refuses to create a ControlSocket in a directory that is
4632 world-readable (or group-readable if ControlSocketsGroupWritable
4633 is 0). This is necessary because some operating systems do not
4634 enforce permissions on an AF_UNIX sockets. Permissions on the
4635 directory holding the socket, however, seems to work everywhere.
4636 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4637 not. This would lead to a cookie that is still not group readable.
4638 Closes bug 1843. Suggested by katmagic.
4639 - Future-proof the controller protocol a bit by ignoring keyword
4640 arguments we do not recognize.
4642 o Minor features (more useful logging):
4643 - Revise most log messages that refer to nodes by nickname to
4644 instead use the "$key=nickname at address" format. This should be
4645 more useful, especially since nicknames are less and less likely
4646 to be unique. Resolves ticket 3045.
4647 - When an HTTPS proxy reports "403 Forbidden", we now explain
4648 what it means rather than calling it an unexpected status code.
4649 Closes bug 2503. Patch from Michael Yakubovich.
4650 - Rate-limit a warning about failures to download v2 networkstatus
4651 documents. Resolves part of bug 1352.
4652 - Rate-limit the "your application is giving Tor only an IP address"
4653 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4654 - Rate-limit "Failed to hand off onionskin" warnings.
4655 - When logging a rate-limited warning, we now mention how many messages
4656 got suppressed since the last warning.
4657 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4658 2 no signature, 4 required" messages about consensus signatures
4659 easier to read, and make sure they get logged at the same severity
4660 as the messages explaining which keys are which. Fixes bug 1290.
4661 - Don't warn when we have a consensus that we can't verify because
4662 of missing certificates, unless those certificates are ones
4663 that we have been trying and failing to download. Fixes bug 1145.
4665 o Minor features (log domains):
4666 - Add documentation for configuring logging at different severities in
4667 different log domains. We've had this feature since 0.2.1.1-alpha,
4668 but for some reason it never made it into the manpage. Fixes
4670 - Make it simpler to specify "All log domains except for A and B".
4671 Previously you needed to say "[*,~A,~B]". Now you can just say
4673 - Add a "LogMessageDomains 1" option to include the domains of log
4674 messages along with the messages. Without this, there's no way
4675 to use log domains without reading the source or doing a lot
4677 - Add a new "Handshake" log domain for activities that happen
4678 during the TLS handshake.
4680 o Minor features (build process):
4681 - Make compilation with clang possible when using
4682 "--enable-gcc-warnings" by removing two warning options that clang
4683 hasn't implemented yet and by fixing a few warnings. Resolves
4685 - Detect platforms that brokenly use a signed size_t, and refuse to
4686 build there. Found and analyzed by doorss and rransom.
4687 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
4689 - Add support for statically linking zlib by specifying
4690 "--enable-static-zlib", to go with our support for statically
4691 linking openssl and libevent. Resolves bug 1358.
4692 - Instead of adding the svn revision to the Tor version string, report
4693 the git commit (when we're building from a git checkout).
4694 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4696 - New --digests command-line switch to output the digests of the
4697 source files Tor was built with.
4698 - Generate our manpage and HTML documentation using Asciidoc. This
4699 change should make it easier to maintain the documentation, and
4700 produce nicer HTML. The build process fails if asciidoc cannot
4701 be found and building with asciidoc isn't disabled (via the
4702 "--disable-asciidoc" argument to ./configure. Skipping the manpage
4703 speeds up the build considerably.
4705 o Minor features (options / torrc):
4706 - Warn when the same option is provided more than once in a torrc
4707 file, on the command line, or in a single SETCONF statement, and
4708 the option is one that only accepts a single line. Closes bug 1384.
4709 - Warn when the user configures two HiddenServiceDir lines that point
4710 to the same directory. Bugfix on 0.0.6 (the version introducing
4711 HiddenServiceDir); fixes bug 3289.
4712 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4713 do individual connection-level rate limiting of clients. The torrc
4714 config options with the same names trump the consensus params, if
4715 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4716 consensus params which were broken from 0.2.2.7-alpha through
4717 0.2.2.14-alpha. Closes bug 1947.
4718 - New config option "WarnUnsafeSocks 0" disables the warning that
4719 occurs whenever Tor receives a socks handshake using a version of
4720 the socks protocol that can only provide an IP address (rather
4721 than a hostname). Setups that do DNS locally over Tor are fine,
4722 and we shouldn't spam the logs in that case.
4723 - New config option "CircuitStreamTimeout" to override our internal
4724 timeout schedule for how many seconds until we detach a stream from
4725 a circuit and try a new circuit. If your network is particularly
4726 slow, you might want to set this to a number like 60.
4727 - New options for SafeLogging to allow scrubbing only log messages
4728 generated while acting as a relay. Specify "SafeLogging relay" if
4729 you want to ensure that only messages known to originate from
4730 client use of the Tor process will be logged unsafely.
4731 - Time and memory units in the configuration file can now be set to
4732 fractional units. For example, "2.5 GB" is now a valid value for
4734 - Support line continuations in the torrc config file. If a line
4735 ends with a single backslash character, the newline is ignored, and
4736 the configuration value is treated as continuing on the next line.
4739 o Minor features (unit tests):
4740 - Revise our unit tests to use the "tinytest" framework, so we
4741 can run tests in their own processes, have smarter setup/teardown
4742 code, and so on. The unit test code has moved to its own
4743 subdirectory, and has been split into multiple modules.
4744 - Add a unit test for cross-platform directory-listing code.
4745 - Add some forgotten return value checks during unit tests. Found
4747 - Use GetTempDir to find the proper temporary directory location on
4748 Windows when generating temporary files for the unit tests. Patch
4751 o Minor features (misc):
4752 - The "torify" script now uses torsocks where available.
4753 - Make Libevent log messages get delivered to controllers later,
4754 and not from inside the Libevent log handler. This prevents unsafe
4755 reentrant Libevent calls while still letting the log messages
4757 - Certain Tor clients (such as those behind check.torproject.org) may
4758 want to fetch the consensus in an extra early manner. To enable this
4759 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
4760 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
4761 as only certain clients who must have this information sooner should
4763 - Expand homedirs passed to tor-checkkey. This should silence a
4764 coverity complaint about passing a user-supplied string into
4765 open() without checking it.
4766 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4767 used on bridges, and it makes bridge scanning somewhat easier.
4768 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4769 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4771 o Minor bugfixes (relays):
4772 - When a relay decides that its DNS is too broken for it to serve
4773 as an exit server, it advertised itself as a non-exit, but
4774 continued to act as an exit. This could create accidental
4775 partitioning opportunities for users. Instead, if a relay is
4776 going to advertise reject *:* as its exit policy, it should
4777 really act with exit policy "reject *:*". Fixes bug 2366.
4778 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4779 - Publish a router descriptor even if generating an extra-info
4780 descriptor fails. Previously we would not publish a router
4781 descriptor without an extra-info descriptor; this can cause fast
4782 exit relays collecting exit-port statistics to drop from the
4783 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4784 - When we're trying to guess whether we know our IP address as
4785 a relay, we would log various ways that we failed to guess
4786 our address, but never log that we ended up guessing it
4787 successfully. Now add a log line to help confused and anxious
4788 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4789 - For bandwidth accounting, calculate our expected bandwidth rate
4790 based on the time during which we were active and not in
4791 soft-hibernation during the last interval. Previously, we were
4792 also considering the time spent in soft-hibernation. If this
4793 was a long time, we would wind up underestimating our bandwidth
4794 by a lot, and skewing our wakeup time towards the start of the
4795 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4796 - Demote a confusing TLS warning that relay operators might get when
4797 someone tries to talk to their ORPort. It is not the operator's
4798 fault, nor can they do anything about it. Fixes bug 1364; bugfix
4800 - Change "Application request when we're believed to be offline."
4801 notice to "Application request when we haven't used client
4802 functionality lately.", to clarify that it's not an error. Bugfix
4803 on 0.0.9.3; fixes bug 1222.
4805 o Minor bugfixes (bridges):
4806 - When a client starts or stops using bridges, never use a circuit
4807 that was built before the configuration change. This behavior could
4808 put at risk a user who uses bridges to ensure that her traffic
4809 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4811 - Do not reset the bridge descriptor download status every time we
4812 re-parse our configuration or get a configuration change. Fixes
4813 bug 3019; bugfix on 0.2.0.3-alpha.
4814 - Users couldn't configure a regular relay to be their bridge. It
4815 didn't work because when Tor fetched the bridge descriptor, it found
4816 that it already had it, and didn't realize that the purpose of the
4817 descriptor had changed. Now we replace routers with a purpose other
4818 than bridge with bridge descriptors when fetching them. Bugfix on
4819 0.1.1.9-alpha. Fixes bug 1776.
4820 - In the special case where you configure a public exit relay as your
4821 bridge, Tor would be willing to use that exit relay as the last
4822 hop in your circuit as well. Now we fail that circuit instead.
4823 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4825 o Minor bugfixes (clients):
4826 - We now ask the other side of a stream (the client or the exit)
4827 for more data on that stream when the amount of queued data on
4828 that stream dips low enough. Previously, we wouldn't ask the
4829 other side for more data until either it sent us more data (which
4830 it wasn't supposed to do if it had exhausted its window!) or we
4831 had completely flushed all our queued data. This flow control fix
4832 should improve throughput. Fixes bug 2756; bugfix on the earliest
4833 released versions of Tor (svn commit r152).
4834 - When a client finds that an origin circuit has run out of 16-bit
4835 stream IDs, we now mark it as unusable for new streams. Previously,
4836 we would try to close the entire circuit. Bugfix on 0.0.6.
4837 - Make it explicit that we don't cannibalize one-hop circuits. This
4838 happens in the wild, but doesn't turn out to be a problem because
4839 we fortunately don't use those circuits. Many thanks to outofwords
4840 for the initial analysis and to swissknife who confirmed that
4841 two-hop circuits are actually created.
4842 - Resolve an edge case in path weighting that could make us misweight
4843 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4844 - Make the DNSPort option work with libevent 2.x. Don't alter the
4845 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4847 o Minor bugfixes (directory authorities):
4848 - Make directory authorities more accurate at recording when
4849 relays that have failed several reachability tests became
4850 unreachable, so we can provide more accuracy at assigning Stable,
4851 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4852 - Directory authorities are now more robust to hops back in time
4853 when calculating router stability. Previously, if a run of uptime
4854 or downtime appeared to be negative, the calculation could give
4855 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4857 - Directory authorities will now attempt to download consensuses
4858 if their own efforts to make a live consensus have failed. This
4859 change means authorities that restart will fetch a valid
4860 consensus, and it means authorities that didn't agree with the
4861 current consensus will still fetch and serve it if it has enough
4862 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
4863 - Never vote for a server as "Running" if we have a descriptor for
4864 it claiming to be hibernating, and that descriptor was published
4865 more recently than our last contact with the server. Bugfix on
4866 0.2.0.3-alpha; fixes bug 911.
4867 - Directory authorities no longer change their opinion of, or vote on,
4868 whether a router is Running, unless they have themselves been
4869 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4872 o Minor bugfixes (hidden services):
4873 - Log malformed requests for rendezvous descriptors as protocol
4874 warnings, not warnings. Also, use a more informative log message
4875 in case someone sees it at log level warning without prior
4876 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
4877 - Accept hidden service descriptors if we think we might be a hidden
4878 service directory, regardless of what our consensus says. This
4879 helps robustness, since clients and hidden services can sometimes
4880 have a more up-to-date view of the network consensus than we do,
4881 and if they think that the directory authorities list us a HSDir,
4882 we might actually be one. Related to bug 2732; bugfix on
4884 - Correct the warning displayed when a rendezvous descriptor exceeds
4885 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4887 - Clients and hidden services now use HSDir-flagged relays for hidden
4888 service descriptor downloads and uploads even if the relays have no
4889 DirPort set and the client has disabled TunnelDirConns. This will
4890 eventually allow us to give the HSDir flag to relays with no
4891 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4892 - Only limit the lengths of single HS descriptors, even when multiple
4893 HS descriptors are published to an HSDir relay in a single POST
4894 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4896 o Minor bugfixes (controllers):
4897 - Allow GETINFO fingerprint to return a fingerprint even when
4898 we have not yet built a router descriptor. Fixes bug 3577;
4899 bugfix on 0.2.0.1-alpha.
4900 - Send a SUCCEEDED stream event to the controller when a reverse
4901 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4902 discovered by katmagic.
4903 - Remove a trailing asterisk from "exit-policy/default" in the
4904 output of the control port command "GETINFO info/names". Bugfix
4906 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
4907 2917. Bugfix on 0.1.1.1-alpha.
4908 - When we restart our relay, we might get a successful connection
4909 from the outside before we've started our reachability tests,
4910 triggering a warning: "ORPort found reachable, but I have no
4911 routerinfo yet. Failing to inform controller of success." This
4912 bug was harmless unless Tor is running under a controller
4913 like Vidalia, in which case the controller would never get a
4914 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4916 - When a controller changes TrackHostExits, remove mappings for
4917 hosts that should no longer have their exits tracked. Bugfix on
4919 - When a controller changes VirtualAddrNetwork, remove any mappings
4920 for hosts that were automapped to the old network. Bugfix on
4922 - When a controller changes one of the AutomapHosts* options, remove
4923 any mappings for hosts that should no longer be automapped. Bugfix
4925 - Fix an off-by-one error in calculating some controller command
4926 argument lengths. Fortunately, this mistake is harmless since
4927 the controller code does redundant NUL termination too. Found by
4928 boboper. Bugfix on 0.1.1.1-alpha.
4929 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4930 would return "551 Internal error" rather than "552 Unrecognized key
4931 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4932 - Don't spam the controller with events when we have no file
4933 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4934 for log messages was already solved from bug 748.)
4935 - Emit a GUARD DROPPED controller event for a case we missed.
4936 - Ensure DNS requests launched by "RESOLVE" commands from the
4937 controller respect the __LeaveStreamsUnattached setconf options. The
4938 same goes for requests launched via DNSPort or transparent
4939 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4941 o Minor bugfixes (config options):
4942 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4943 Change the limit to 512 characters by removing base64 newlines.
4944 Fixes bug 2752. Fix by Michael Yakubovich.
4945 - Complain if PublishServerDescriptor is given multiple arguments that
4946 include 0 or 1. This configuration will be rejected in the future.
4947 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4948 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4949 Bugfix on 0.2.0.13-alpha; closes bug 928.
4951 o Minor bugfixes (log subsystem fixes):
4952 - When unable to format an address as a string, report its value
4953 as "???" rather than reusing the last formatted address. Bugfix
4955 - Be more consistent in our treatment of file system paths. "~" should
4956 get expanded to the user's home directory in the Log config option.
4957 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4958 feature for the -f and --DataDirectory options.
4960 o Minor bugfixes (memory management):
4961 - Don't stack-allocate the list of supplementary GIDs when we're
4962 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4963 could take up to 256K, which is way too much stack. Found by
4964 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4965 - Save a couple bytes in memory allocation every time we escape
4966 certain characters in a string. Patch from Florian Zumbiehl.
4968 o Minor bugfixes (protocol correctness):
4969 - When checking for 1024-bit keys, check for 1024 bits, not 128
4970 bytes. This allows Tor to correctly discard keys of length 1017
4971 through 1023. Bugfix on 0.0.9pre5.
4972 - Require that introduction point keys and onion handshake keys
4973 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4975 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4976 than waiting forever for them to finish. Fixes bug 2330; bugfix
4977 on 0.2.0.16-alpha. Found by doorss.
4978 - Never relay a cell for a circuit we have already destroyed.
4979 Between marking a circuit as closeable and finally closing it,
4980 it may have been possible for a few queued cells to get relayed,
4981 even though they would have been immediately dropped by the next
4982 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4983 - Never queue a cell for a circuit that's already been marked
4985 - Fix a spec conformance issue: the network-status-version token
4986 must be the first token in a v3 consensus or vote. Discovered by
4987 "parakeep". Bugfix on 0.2.0.3-alpha.
4988 - A networkstatus vote must contain exactly one signature. Spec
4989 conformance issue. Bugfix on 0.2.0.3-alpha.
4990 - When asked about a DNS record type we don't support via a
4991 client DNSPort, reply with NOTIMPL rather than an empty
4992 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4993 - Make more fields in the controller protocol case-insensitive, since
4994 control-spec.txt said they were.
4996 o Minor bugfixes (log messages):
4997 - Fix a log message that said "bits" while displaying a value in
4998 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
5000 - Downgrade "no current certificates known for authority" message from
5001 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5002 - Correctly describe errors that occur when generating a TLS object.
5003 Previously we would attribute them to a failure while generating a
5004 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5006 - Fix an instance where a Tor directory mirror might accidentally
5007 log the IP address of a misbehaving Tor client. Bugfix on
5009 - Stop logging at severity 'warn' when some other Tor client tries
5010 to establish a circuit with us using weak DH keys. It's a protocol
5011 violation, but that doesn't mean ordinary users need to hear about
5012 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5013 - If your relay can't keep up with the number of incoming create
5014 cells, it would log one warning per failure into your logs. Limit
5015 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5017 o Minor bugfixes (build fixes):
5018 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5019 - When warning about missing zlib development packages during compile,
5020 give the correct package names. Bugfix on 0.2.0.1-alpha.
5021 - Fix warnings that newer versions of autoconf produce during
5022 ./autogen.sh. These warnings appear to be harmless in our case,
5023 but they were extremely verbose. Fixes bug 2020.
5024 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
5027 o Minor bugfixes (portability):
5028 - Write several files in text mode, on OSes that distinguish text
5029 mode from binary mode (namely, Windows). These files are:
5030 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5031 that collect those statistics; 'client_keys' and 'hostname' for
5032 hidden services that use authentication; and (in the tor-gencert
5033 utility) newly generated identity and signing keys. Previously,
5034 we wouldn't specify text mode or binary mode, leading to an
5035 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5036 the DirRecordUsageByCountry option which would have triggered
5037 the assertion failure was added), although this assertion failure
5038 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5039 - Selectively disable deprecation warnings on OS X because Lion
5040 started deprecating the shipped copy of openssl. Fixes bug 3643.
5041 - Use a wide type to hold sockets when built for 64-bit Windows.
5043 - Fix an issue that prevented static linking of libevent on
5044 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
5045 where we introduced the "--with-static-libevent" configure option.
5046 - Fix a bug with our locking implementation on Windows that couldn't
5047 correctly detect when a file was already locked. Fixes bug 2504,
5048 bugfix on 0.2.1.6-alpha.
5049 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5051 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5052 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5055 o Minor bugfixes (code correctness):
5056 - Always NUL-terminate the sun_path field of a sockaddr_un before
5057 passing it to the kernel. (Not a security issue: kernels are
5058 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5059 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5060 - Make connection_printf_to_buf()'s behavior sane. Its callers
5061 expect it to emit a CRLF iff the format string ends with CRLF;
5062 it actually emitted a CRLF iff (a) the format string ended with
5063 CRLF or (b) the resulting string was over 1023 characters long or
5064 (c) the format string did not end with CRLF *and* the resulting
5065 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
5066 fixes part of bug 3407.
5067 - Make send_control_event_impl()'s behavior sane. Its callers
5068 expect it to always emit a CRLF at the end of the string; it
5069 might have emitted extra control characters as well. Bugfix on
5070 0.1.1.9-alpha; fixes another part of bug 3407.
5071 - Make crypto_rand_int() check the value of its input correctly.
5072 Previously, it accepted values up to UINT_MAX, but could return a
5073 negative number if given a value above INT_MAX+1. Found by George
5074 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
5075 - Fix a potential null-pointer dereference while computing a
5076 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
5078 - If we fail to compute the identity digest of a v3 legacy keypair,
5079 warn, and don't use a buffer-full of junk instead. Bugfix on
5080 0.2.1.1-alpha; fixes bug 3106.
5081 - Resolve an untriggerable issue in smartlist_string_num_isin(),
5082 where if the function had ever in the future been used to check
5083 for the presence of a too-large number, it would have given an
5084 incorrect result. (Fortunately, we only used it for 16-bit
5085 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
5086 - Be more careful about reporting the correct error from a failed
5087 connect() system call. Under some circumstances, it was possible to
5088 look at an incorrect value for errno when sending the end reason.
5089 Bugfix on 0.1.0.1-rc.
5090 - Correctly handle an "impossible" overflow cases in connection byte
5091 counting, where we write or read more than 4GB on an edge connection
5092 in a single second. Bugfix on 0.1.2.8-beta.
5093 - Avoid a double mark-for-free warning when failing to attach a
5094 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5096 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5097 found by "cypherpunks". This bug was introduced before the first
5098 Tor release, in svn commit r110.
5099 - Fix a bug in bandwidth history state parsing that could have been
5100 triggered if a future version of Tor ever changed the timing
5101 granularity at which bandwidth history is measured. Bugfix on
5103 - Add assertions to check for overflow in arguments to
5104 base32_encode() and base32_decode(); fix a signed-unsigned
5105 comparison there too. These bugs are not actually reachable in Tor,
5106 but it's good to prevent future errors too. Found by doorss.
5107 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
5109 - Set target port in get_interface_address6() correctly. Bugfix
5110 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5111 - Fix an impossible-to-actually-trigger buffer overflow in relay
5112 descriptor generation. Bugfix on 0.1.0.15.
5113 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5115 o Minor bugfixes (code improvements):
5116 - After we free an internal connection structure, overwrite it
5117 with a different memory value than we use for overwriting a freed
5118 internal circuit structure. Should help with debugging. Suggested
5120 - If OpenSSL fails to make a duplicate of a private or public key, log
5121 an error message and try to exit cleanly. May help with debugging
5122 if bug 1209 ever remanifests.
5123 - Some options used different conventions for uppercasing of acronyms
5124 when comparing manpage and source. Fix those in favor of the
5125 manpage, as it makes sense to capitalize acronyms.
5126 - Take a first step towards making or.h smaller by splitting out
5127 function definitions for all source files in src/or/. Leave
5128 structures and defines in or.h for now.
5129 - Remove a few dead assignments during router parsing. Found by
5131 - Don't use 1-bit wide signed bit fields. Found by coverity.
5132 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5133 None of the cases where we did this before were wrong, but by making
5134 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5135 - The memarea code now uses a sentinel value at the end of each area
5136 to make sure nothing writes beyond the end of an area. This might
5137 help debug some conceivable causes of bug 930.
5138 - Always treat failure to allocate an RSA key as an unrecoverable
5140 - Add some more defensive programming for architectures that can't
5141 handle unaligned integer accesses. We don't know of any actual bugs
5142 right now, but that's the best time to fix them. Fixes bug 1943.
5144 o Minor bugfixes (misc):
5145 - Fix a rare bug in rend_fn unit tests: we would fail a test when
5146 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5147 on 0.2.0.10-alpha; fixes bug 1808.
5148 - Where available, use Libevent 2.0's periodic timers so that our
5149 once-per-second cleanup code gets called even more closely to
5150 once per second than it would otherwise. Fixes bug 943.
5151 - Ignore OutboundBindAddress when connecting to localhost.
5152 Connections to localhost need to come _from_ localhost, or else
5153 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5155 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5157 - If any of the v3 certs we download are unparseable, we should
5158 actually notice the failure so we don't retry indefinitely. Bugfix
5159 on 0.2.0.x; reported by "rotator".
5160 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5161 Might help diagnosing bug 1051.
5162 - Make our 'torify' script more portable; if we have only one of
5163 'torsocks' or 'tsocks' installed, don't complain to the user;
5164 and explain our warning about tsocks better.
5165 - Fix some urls in the exit notice file and make it XHTML1.1 strict
5166 compliant. Based on a patch from Christian Kujau.
5168 o Documentation changes:
5169 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5170 - Resolve all doxygen warnings except those for missing documentation.
5172 - Add doxygen documentation for more functions, fields, and types.
5173 - Convert the HACKING file to asciidoc, and add a few new sections
5174 to it, explaining how we use Git, how we make changelogs, and
5175 what should go in a patch.
5176 - Document the default socks host and port (127.0.0.1:9050) for
5178 - Removed some unnecessary files from the source distribution. The
5179 AUTHORS file has now been merged into the people page on the
5180 website. The roadmaps and design doc can now be found in the
5181 projects directory in svn.
5183 o Deprecated and removed features (config):
5184 - Remove the torrc.complete file. It hasn't been kept up to date
5185 and users will have better luck checking out the manpage.
5186 - Remove the HSAuthorityRecordStats option that version 0 hidden
5187 service authorities could use to track statistics of overall v0
5188 hidden service usage.
5189 - Remove the obsolete "NoPublish" option; it has been flagged
5190 as obsolete and has produced a warning since 0.1.1.18-rc.
5191 - Caches no longer download and serve v2 networkstatus documents
5192 unless FetchV2Networkstatus flag is set: these documents haven't
5193 haven't been used by clients or relays since 0.2.0.x. Resolves
5196 o Deprecated and removed features (controller):
5197 - The controller no longer accepts the old obsolete "addr-mappings/"
5198 or "unregistered-servers-" GETINFO values.
5199 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5200 always on; using them is necessary for correct forward-compatible
5203 o Deprecated and removed features (misc):
5204 - Hidden services no longer publish version 0 descriptors, and clients
5205 do not request or use version 0 descriptors. However, the old hidden
5206 service authorities still accept and serve version 0 descriptors
5207 when contacted by older hidden services/clients.
5208 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5209 anything since 0.2.1.16-rc.
5210 - Remove everything related to building the expert bundle for OS X.
5211 It has confused many users, doesn't work right on OS X 10.6,
5212 and is hard to get rid of once installed. Resolves bug 1274.
5213 - Remove support for .noconnect style addresses. Nobody was using
5214 them, and they provided another avenue for detecting Tor users
5215 via application-level web tricks.
5216 - When we fixed bug 1038 we had to put in a restriction not to send
5217 RELAY_EARLY cells on rend circuits. This was necessary as long
5218 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5219 active. Now remove this obsolete check. Resolves bug 2081.
5220 - Remove workaround code to handle directory responses from servers
5221 that had bug 539 (they would send HTTP status 503 responses _and_
5222 send a body too). Since only server versions before
5223 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5224 keep the workaround in place.
5225 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5226 handling calculations where we have a known amount of clock skew and
5227 an allowed amount of unknown skew. But we only used it in three
5228 places, and we never adjusted the known/unknown skew values. This is
5229 still something we might want to do someday, but if we do, we'll
5230 want to do it differently.
5231 - Remove the "--enable-iphone" option to ./configure. According to
5232 reports from Marco Bonetti, Tor builds fine without any special
5233 tweaking on recent iPhone SDK versions.
5236 Changes in version 0.2.1.30 - 2011-02-23
5237 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5238 change is a slight tweak to Tor's TLS handshake that makes relays
5239 and bridges that run this new version reachable from Iran again.
5240 We don't expect this tweak will win the arms race long-term, but it
5241 buys us time until we roll out a better solution.
5244 - Stop sending a CLOCK_SKEW controller status event whenever
5245 we fetch directory information from a relay that has a wrong clock.
5246 Instead, only inform the controller when it's a trusted authority
5247 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5248 the rest of bug 1074.
5249 - Fix a bounds-checking error that could allow an attacker to
5250 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5252 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5253 Tor would ignore their RelayBandwidthBurst setting,
5254 potentially using more bandwidth than expected. Bugfix on
5255 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5256 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5257 hidserv" in her torrc. The 'hidserv' argument never controlled
5258 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5261 - Adjust our TLS Diffie-Hellman parameters to match those used by
5263 - Update to the February 1 2011 Maxmind GeoLite Country database.
5266 - Check for and reject overly long directory certificates and
5267 directory tokens before they have a chance to hit any assertions.
5268 Bugfix on 0.2.1.28. Found by "doorss".
5269 - Bring the logic that gathers routerinfos and assesses the
5270 acceptability of circuits into line. This prevents a Tor OP from
5271 getting locked in a cycle of choosing its local OR as an exit for a
5272 path (due to a .exit request) and then rejecting the circuit because
5273 its OR is not listed yet. It also prevents Tor clients from using an
5274 OR running in the same instance as an exit (due to a .exit request)
5275 if the OR does not meet the same requirements expected of an OR
5276 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5278 o Packaging changes:
5279 - Stop shipping the Tor specs files and development proposal documents
5280 in the tarball. They are now in a separate git repository at
5281 git://git.torproject.org/torspec.git
5282 - Do not include Git version tags as though they are SVN tags when
5283 generating a tarball from inside a repository that has switched
5284 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5287 Changes in version 0.2.1.29 - 2011-01-15
5288 Tor 0.2.1.29 continues our recent code security audit work. The main
5289 fix resolves a remote heap overflow vulnerability that can allow remote
5290 code execution. Other fixes address a variety of assert and crash bugs,
5291 most of which we think are hard to exploit remotely.
5293 o Major bugfixes (security):
5294 - Fix a heap overflow bug where an adversary could cause heap
5295 corruption. This bug probably allows remote code execution
5296 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5298 - Prevent a denial-of-service attack by disallowing any
5299 zlib-compressed data whose compression factor is implausibly
5300 high. Fixes part of bug 2324; reported by "doorss".
5301 - Zero out a few more keys in memory before freeing them. Fixes
5302 bug 2384 and part of bug 2385. These key instances found by
5303 "cypherpunks", based on Andrew Case's report about being able
5304 to find sensitive data in Tor's memory space if you have enough
5305 permissions. Bugfix on 0.0.2pre9.
5307 o Major bugfixes (crashes):
5308 - Prevent calls to Libevent from inside Libevent log handlers.
5309 This had potential to cause a nasty set of crashes, especially
5310 if running Libevent with debug logging enabled, and running
5311 Tor with a controller watching for low-severity log messages.
5312 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5313 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5314 underflow errors there too. Fixes the other part of bug 2324.
5315 - Fix a bug where we would assert if we ever had a
5316 cached-descriptors.new file (or another file read directly into
5317 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5318 on 0.2.1.25. Found by doorss.
5319 - Fix some potential asserts and parsing issues with grossly
5320 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5323 o Minor bugfixes (other):
5324 - Fix a bug with handling misformed replies to reverse DNS lookup
5325 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5326 bug reported by doorss.
5327 - Fix compilation on mingw when a pthreads compatibility library
5328 has been installed. (We don't want to use it, so we shouldn't
5329 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5330 - Fix a bug where we would declare that we had run out of virtual
5331 addresses when the address space was only half-exhausted. Bugfix
5333 - Correctly handle the case where AutomapHostsOnResolve is set but
5334 no virtual addresses are available. Fixes bug 2328; bugfix on
5335 0.1.2.1-alpha. Bug found by doorss.
5336 - Correctly handle wrapping around when we run out of virtual
5337 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5340 - Update to the January 1 2011 Maxmind GeoLite Country database.
5341 - Introduce output size checks on all of our decryption functions.
5344 - Tor does not build packages correctly with Automake 1.6 and earlier;
5345 added a check to Makefile.am to make sure that we're building with
5346 Automake 1.7 or later.
5347 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5348 because we built it with a too-old version of automake. Thus that
5349 release broke ./configure --enable-openbsd-malloc, which is popular
5350 among really fast exit relays on Linux.
5353 Changes in version 0.2.1.28 - 2010-12-17
5354 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5355 exploitable bugs. We also took this opportunity to change the IP address
5356 for one of our directory authorities, and to update the geoip database
5360 - Fix a remotely exploitable bug that could be used to crash instances
5361 of Tor remotely by overflowing on the heap. Remote-code execution
5362 hasn't been confirmed, but can't be ruled out. Everyone should
5363 upgrade. Bugfix on the 0.1.1 series and later.
5365 o Directory authority changes:
5366 - Change IP address and ports for gabelmoo (v3 directory authority).
5369 - Update to the December 1 2010 Maxmind GeoLite Country database.
5372 Changes in version 0.2.1.27 - 2010-11-23
5373 Yet another OpenSSL security patch broke its compatibility with Tor:
5374 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5375 also took this opportunity to fix several crash bugs, integrate a new
5376 directory authority, and update the bundled GeoIP database.
5379 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5380 No longer set the tlsext_host_name extension on server SSL objects;
5381 but continue to set it on client SSL objects. Our goal in setting
5382 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5383 bugfix on 0.2.1.1-alpha.
5384 - Do not log messages to the controller while shrinking buffer
5385 freelists. Doing so would sometimes make the controller connection
5386 try to allocate a buffer chunk, which would mess up the internals
5387 of the freelist and cause an assertion failure. Fixes bug 1125;
5388 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5389 - Learn our external IP address when we're a relay or bridge, even if
5390 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5391 where we introduced bridge relays that don't need to publish to
5392 be useful. Fixes bug 2050.
5393 - Do even more to reject (and not just ignore) annotations on
5394 router descriptors received anywhere but from the cache. Previously
5395 we would ignore such annotations at first, but cache them to disk
5396 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5397 - When you're using bridges and your network goes away and your
5398 bridges get marked as down, recover when you attempt a new socks
5399 connection (if the network is back), rather than waiting up to an
5400 hour to try fetching new descriptors for your bridges. Bugfix on
5401 0.2.0.3-alpha; fixes bug 1981.
5404 - Move to the November 2010 Maxmind GeoLite country db (rather
5405 than the June 2009 ip-to-country GeoIP db) for our statistics that
5406 count how many users relays are seeing from each country. Now we'll
5407 have more accurate data, especially for many African countries.
5409 o New directory authorities:
5410 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5414 - Fix an assertion failure that could occur in directory caches or
5415 bridge users when using a very short voting interval on a testing
5416 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5418 - Enforce multiplicity rules when parsing annotations. Bugfix on
5419 0.2.0.8-alpha. Found by piebeer.
5420 - Allow handshaking OR connections to take a full KeepalivePeriod
5421 seconds to handshake. Previously, we would close them after
5422 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5423 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5425 - When building with --enable-gcc-warnings on OpenBSD, disable
5426 warnings in system headers. This makes --enable-gcc-warnings
5427 pass on OpenBSD 4.8.
5430 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5431 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5432 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5433 Servers can start sending this code when enough clients recognize
5434 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5435 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5436 Patch from mingw-san.
5439 - Remove the old debian/ directory from the main Tor distribution.
5440 The official Tor-for-debian git repository lives at the URL
5441 https://git.torproject.org/debian/tor.git
5442 - Stop shipping the old doc/website/ directory in the tarball. We
5443 changed the website format in late 2010, and what we shipped in
5444 0.2.1.26 really wasn't that useful anyway.
5447 Changes in version 0.2.1.26 - 2010-05-02
5448 Tor 0.2.1.26 addresses the recent connection and memory overload
5449 problems we've been seeing on relays, especially relays with their
5450 DirPort open. If your relay has been crashing, or you turned it off
5451 because it used too many resources, give this release a try.
5453 This release also fixes yet another instance of broken OpenSSL libraries
5454 that was causing some relays to drop out of the consensus.
5457 - Teach relays to defend themselves from connection overload. Relays
5458 now close idle circuits early if it looks like they were intended
5459 for directory fetches. Relays are also more aggressive about closing
5460 TLS connections that have no circuits on them. Such circuits are
5461 unlikely to be re-used, and tens of thousands of them were piling
5462 up at the fast relays, causing the relays to run out of sockets
5463 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5464 their directory fetches over TLS).
5465 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5466 that claim to be earlier than 0.9.8m, but which have in reality
5467 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5468 behavior. Possible fix for some cases of bug 1346.
5469 - Directory mirrors were fetching relay descriptors only from v2
5470 directory authorities, rather than v3 authorities like they should.
5471 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5472 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5475 - Finally get rid of the deprecated and now harmful notion of "clique
5476 mode", where directory authorities maintain TLS connections to
5480 - In the util/threads test, no longer free the test_mutex before all
5481 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5482 - The master thread could starve the worker threads quite badly on
5483 certain systems, causing them to run only partially in the allowed
5484 window. This resulted in test failures. Now the master thread sleeps
5485 occasionally for a few microseconds while the two worker-threads
5486 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5489 Changes in version 0.2.1.25 - 2010-03-16
5490 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5491 prevent relays from guessing their IP address correctly. It also fixes
5492 several minor potential security bugs.
5495 - Fix a regression from our patch for bug 1244 that caused relays
5496 to guess their IP address incorrectly if they didn't set Address
5497 in their torrc and/or their address fails to resolve. Bugfix on
5498 0.2.1.23; fixes bug 1269.
5499 - When freeing a session key, zero it out completely. We only zeroed
5500 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5501 patched by ekir. Fixes bug 1254.
5504 - Fix a dereference-then-NULL-check sequence when publishing
5505 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5507 - Fix another dereference-then-NULL-check sequence. Bugfix on
5508 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5509 - Make sure we treat potentially not NUL-terminated strings correctly.
5510 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5513 Changes in version 0.2.1.24 - 2010-02-21
5514 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5518 - Work correctly out-of-the-box with even more vendor-patched versions
5519 of OpenSSL. In particular, make it so Debian and OS X don't need
5520 customized patches to run/build.
5523 Changes in version 0.2.1.23 - 2010-02-13
5524 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5525 again on the latest OS X, and updates the location of a directory
5528 o Major bugfixes (performance):
5529 - We were selecting our guards uniformly at random, and then weighting
5530 which of our guards we'd use uniformly at random. This imbalance
5531 meant that Tor clients were severely limited on throughput (and
5532 probably latency too) by the first hop in their circuit. Now we
5533 select guards weighted by currently advertised bandwidth. We also
5534 automatically discard guards picked using the old algorithm. Fixes
5535 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5538 - Make Tor work again on the latest OS X: when deciding whether to
5539 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5540 version at run-time, not compile time. We need to do this because
5541 Apple doesn't update its dev-tools headers when it updates its
5542 libraries in a security patch.
5543 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5544 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5545 a memory leak when requesting a hidden service descriptor we've
5546 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5550 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5551 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5554 - Avoid a mad rush at the beginning of each month when each client
5555 rotates half of its guards. Instead we spread the rotation out
5556 throughout the month, but we still avoid leaving a precise timestamp
5557 in the state file about when we first picked the guard. Improves
5558 over the behavior introduced in 0.1.2.17.
5561 Changes in version 0.2.1.22 - 2010-01-19
5562 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5563 authorities -- it would tell you its whole history of bridge descriptors
5564 if you make the right directory request. This stable update also
5565 rotates two of the seven v3 directory authority keys and locations.
5567 o Directory authority changes:
5568 - Rotate keys (both v3 identity and relay identity) for moria1
5572 - Stop bridge directory authorities from answering dbg-stability.txt
5573 directory queries, which would let people fetch a list of all
5574 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5577 Changes in version 0.2.1.21 - 2009-12-21
5578 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5579 library. If you use Tor on Linux / Unix and you're getting SSL
5580 renegotiation errors, upgrading should help. We also recommend an
5581 upgrade if you're an exit relay.
5584 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5585 handshake from working unless we explicitly tell OpenSSL that we
5586 are using SSL renegotiation safely. We are, of course, but OpenSSL
5587 0.9.8l won't work unless we say we are.
5588 - Avoid crashing if the client is trying to upload many bytes and the
5589 circuit gets torn down at the same time, or if the flip side
5590 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5593 - Do not refuse to learn about authority certs and v2 networkstatus
5594 documents that are older than the latest consensus. This bug might
5595 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5596 Spotted and fixed by xmux.
5597 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5598 trigger platform-specific option misparsing case found by Coverity
5600 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5601 trigger assert. Fixes bug 1173.
5604 Changes in version 0.2.1.20 - 2009-10-15
5605 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5606 services at once, prepares for more performance improvements, and
5607 fixes a bunch of smaller bugs.
5609 The Windows and OS X bundles also include a more recent Vidalia,
5610 and switch from Privoxy to Polipo.
5612 The OS X installers are now drag and drop. It's best to un-install
5613 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5614 you want to upgrade, you'll need to update the paths for Tor and Polipo
5615 in the Vidalia Settings window.
5618 - Send circuit or stream sendme cells when our window has decreased
5619 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5620 by Karsten when testing the "reduce circuit window" performance
5621 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5622 before the release of Tor 0.0.0. This is the new winner of the
5624 - Fix a remotely triggerable memory leak when a consensus document
5625 contains more than one signature from the same voter. Bugfix on
5627 - Avoid segfault in rare cases when finishing an introduction circuit
5628 as a client and finding out that we don't have an introduction key
5629 for it. Fixes bug 1073. Reported by Aaron Swartz.
5632 - Tor now reads the "circwindow" parameter out of the consensus,
5633 and uses that value for its circuit package window rather than the
5634 default of 1000 cells. Begins the implementation of proposal 168.
5636 o New directory authorities:
5637 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5639 - Move moria1 and tonga to alternate IP addresses.
5642 - Fix a signed/unsigned compile warning in 0.2.1.19.
5643 - Fix possible segmentation fault on directory authorities. Bugfix on
5645 - Fix an extremely rare infinite recursion bug that could occur if
5646 we tried to log a message after shutting down the log subsystem.
5647 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5648 - Fix an obscure bug where hidden services on 64-bit big-endian
5649 systems might mis-read the timestamp in v3 introduce cells, and
5650 refuse to connect back to the client. Discovered by "rotor".
5651 Bugfix on 0.2.1.6-alpha.
5652 - We were triggering a CLOCK_SKEW controller status event whenever
5653 we connect via the v2 connection protocol to any relay that has
5654 a wrong clock. Instead, we should only inform the controller when
5655 it's a trusted authority that claims our clock is wrong. Bugfix
5656 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5657 - We were telling the controller about CHECKING_REACHABILITY and
5658 REACHABILITY_FAILED status events whenever we launch a testing
5659 circuit or notice that one has failed. Instead, only tell the
5660 controller when we want to inform the user of overall success or
5661 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5663 - Don't warn when we're using a circuit that ends with a node
5664 excluded in ExcludeExitNodes, but the circuit is not used to access
5665 the outside world. This should help fix bug 1090. Bugfix on
5667 - Work around a small memory leak in some versions of OpenSSL that
5668 stopped the memory used by the hostname TLS extension from being
5672 - Add a "getinfo status/accepted-server-descriptor" controller
5673 command, which is the recommended way for controllers to learn
5674 whether our server descriptor has been successfully received by at
5675 least on directory authority. Un-recommend good-server-descriptor
5676 getinfo and status events until we have a better design for them.
5679 Changes in version 0.2.1.19 - 2009-07-28
5680 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5684 - Make accessing hidden services on 0.2.1.x work right again.
5685 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5686 part of patch provided by "optimist".
5689 - When a relay/bridge is writing out its identity key fingerprint to
5690 the "fingerprint" file and to its logs, write it without spaces. Now
5691 it will look like the fingerprints in our bridges documentation,
5692 and confuse fewer users.
5695 - Relays no longer publish a new server descriptor if they change
5696 their MaxAdvertisedBandwidth config option but it doesn't end up
5697 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5698 fixes bug 1026. Patch from Sebastian.
5699 - Avoid leaking memory every time we get a create cell but we have
5700 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5701 fixes bug 1034. Reported by BarkerJr.
5704 Changes in version 0.2.1.18 - 2009-07-24
5705 Tor 0.2.1.18 lays the foundations for performance improvements,
5706 adds status events to help users diagnose bootstrap problems, adds
5707 optional authentication/authorization for hidden services, fixes a
5708 variety of potential anonymity problems, and includes a huge pile of
5709 other features and bug fixes.
5711 o Major features (clients):
5712 - Start sending "bootstrap phase" status events to the controller,
5713 so it can keep the user informed of progress fetching directory
5714 information and establishing circuits. Also inform the controller
5715 if we think we're stuck at a particular bootstrap phase. Implements
5717 - Clients replace entry guards that were chosen more than a few months
5718 ago. This change should significantly improve client performance,
5719 especially once more people upgrade, since relays that have been
5720 a guard for a long time are currently overloaded.
5721 - Network status consensus documents and votes now contain bandwidth
5722 information for each relay. Clients use the bandwidth values
5723 in the consensus, rather than the bandwidth values in each
5724 relay descriptor. This approach opens the door to more accurate
5725 bandwidth estimates once the directory authorities start doing
5726 active measurements. Implements part of proposal 141.
5728 o Major features (relays):
5729 - Disable and refactor some debugging checks that forced a linear scan
5730 over the whole server-side DNS cache. These accounted for over 50%
5731 of CPU time on a relatively busy exit node's gprof profile. Also,
5732 disable some debugging checks that appeared in exit node profile
5733 data. Found by Jacob.
5734 - New DirPortFrontPage option that takes an html file and publishes
5735 it as "/" on the DirPort. Now relay operators can provide a
5736 disclaimer without needing to set up a separate webserver. There's
5737 a sample disclaimer in contrib/tor-exit-notice.html.
5739 o Major features (hidden services):
5740 - Make it possible to build hidden services that only certain clients
5741 are allowed to connect to. This is enforced at several points,
5742 so that unauthorized clients are unable to send INTRODUCE cells
5743 to the service, or even (depending on the type of authentication)
5744 to learn introduction points. This feature raises the bar for
5745 certain kinds of active attacks against hidden services. Design
5746 and code by Karsten Loesing. Implements proposal 121.
5747 - Relays now store and serve v2 hidden service descriptors by default,
5748 i.e., the new default value for HidServDirectoryV2 is 1. This is
5749 the last step in proposal 114, which aims to make hidden service
5750 lookups more reliable.
5752 o Major features (path selection):
5753 - ExitNodes and Exclude*Nodes config options now allow you to restrict
5754 by country code ("{US}") or IP address or address pattern
5755 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
5756 refinement to decide what config options should take priority if
5757 you ask to both use a particular node and exclude it.
5759 o Major features (misc):
5760 - When building a consensus, do not include routers that are down.
5761 This cuts down 30% to 40% on consensus size. Implements proposal
5763 - New TestingTorNetwork config option to allow adjustment of
5764 previously constant values that could slow bootstrapping. Implements
5765 proposal 135. Patch from Karsten.
5766 - Convert many internal address representations to optionally hold
5767 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
5768 elements. Make resolver code handle nameservers located at IPv6
5770 - More work on making our TLS handshake blend in: modify the list
5771 of ciphers advertised by OpenSSL in client mode to even more
5772 closely resemble a common web browser. We cheat a little so that
5773 we can advertise ciphers that the locally installed OpenSSL doesn't
5775 - Use the TLS1 hostname extension to more closely resemble browser
5778 o Security fixes (anonymity/entropy):
5779 - Never use a connection with a mismatched address to extend a
5780 circuit, unless that connection is canonical. A canonical
5781 connection is one whose address is authenticated by the router's
5782 identity key, either in a NETINFO cell or in a router descriptor.
5783 - Implement most of proposal 110: The first K cells to be sent
5784 along a circuit are marked as special "early" cells; only K "early"
5785 cells will be allowed. Once this code is universal, we can block
5786 certain kinds of denial-of-service attack by requiring that EXTEND
5787 commands must be sent using an "early" cell.
5788 - Resume using OpenSSL's RAND_poll() for better (and more portable)
5789 cross-platform entropy collection again. We used to use it, then
5790 stopped using it because of a bug that could crash systems that
5791 called RAND_poll when they had a lot of fds open. It looks like the
5792 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
5793 at startup, and to call RAND_poll() when we reseed later only if
5794 we have a non-buggy OpenSSL version.
5795 - When the client is choosing entry guards, now it selects at most
5796 one guard from a given relay family. Otherwise we could end up with
5797 all of our entry points into the network run by the same operator.
5798 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5799 - Do not use or believe expired v3 authority certificates. Patch
5800 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
5801 - Drop begin cells to a hidden service if they come from the middle
5802 of a circuit. Patch from lark.
5803 - When we erroneously receive two EXTEND cells for the same circuit
5804 ID on the same connection, drop the second. Patch from lark.
5805 - Authorities now vote for the Stable flag for any router whose
5806 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5807 - Clients now never report any stream end reason except 'MISC'.
5808 Implements proposal 148.
5810 o Major bugfixes (crashes):
5811 - Parse dates and IPv4 addresses in a locale- and libc-independent
5812 manner, to avoid platform-dependent behavior on malformed input.
5813 - Fix a crash that occurs on exit nodes when a nameserver request
5814 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5815 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5817 - Do not assume that a stack-allocated character array will be
5818 64-bit aligned on platforms that demand that uint64_t access is
5819 aligned. Possible fix for bug 604.
5820 - Resolve a very rare crash bug that could occur when the user forced
5821 a nameserver reconfiguration during the middle of a nameserver
5822 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5823 - Avoid a "0 divided by 0" calculation when calculating router uptime
5824 at directory authorities. Bugfix on 0.2.0.8-alpha.
5825 - Fix an assertion bug in parsing policy-related options; possible fix
5827 - Rate-limit too-many-sockets messages: when they happen, they happen
5828 a lot and end up filling up the disk. Resolves bug 748.
5829 - Fix a race condition that could cause crashes or memory corruption
5830 when running as a server with a controller listening for log
5832 - Avoid crashing when we have a policy specified in a DirPolicy or
5833 SocksPolicy or ReachableAddresses option with ports set on it,
5834 and we re-load the policy. May fix bug 996.
5835 - Fix an assertion failure on 64-bit platforms when we allocated
5836 memory right up to the end of a memarea, then realigned the memory
5837 one step beyond the end. Fixes a possible cause of bug 930.
5838 - Protect the count of open sockets with a mutex, so we can't
5839 corrupt it when two threads are closing or opening sockets at once.
5840 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5842 o Major bugfixes (clients):
5843 - Discard router descriptors as we load them if they are more than
5844 five days old. Otherwise if Tor is off for a long time and then
5845 starts with cached descriptors, it will try to use the onion keys
5846 in those obsolete descriptors when building circuits. Fixes bug 887.
5847 - When we choose to abandon a new entry guard because we think our
5848 older ones might be better, close any circuits pending on that
5849 new entry guard connection. This fix should make us recover much
5850 faster when our network is down and then comes back. Bugfix on
5851 0.1.2.8-beta; found by lodger.
5852 - When Tor clients restart after 1-5 days, they discard all their
5853 cached descriptors as too old, but they still use the cached
5854 consensus document. This approach is good for robustness, but
5855 bad for performance: since they don't know any bandwidths, they
5856 end up choosing at random rather than weighting their choice by
5857 speed. Fixed by the above feature of putting bandwidths in the
5860 o Major bugfixes (relays):
5861 - Relays were falling out of the networkstatus consensus for
5862 part of a day if they changed their local config but the
5863 authorities discarded their new descriptor as "not sufficiently
5864 different". Now directory authorities accept a descriptor as changed
5865 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
5867 - Ensure that two circuits can never exist on the same connection
5868 with the same circuit ID, even if one is marked for close. This
5869 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
5870 - Directory authorities were neglecting to mark relays down in their
5871 internal histories if the relays fall off the routerlist without
5872 ever being found unreachable. So there were relays in the histories
5873 that haven't been seen for eight months, and are listed as being
5874 up for eight months. This wreaked havoc on the "median wfu" and
5875 "median mtbf" calculations, in turn making Guard and Stable flags
5876 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
5879 o Major bugfixes (hidden services):
5880 - When establishing a hidden service, introduction points that
5881 originate from cannibalized circuits were completely ignored
5882 and not included in rendezvous service descriptors. This might
5883 have been another reason for delay in making a hidden service
5884 available. Bugfix from long ago (0.0.9.x?)
5886 o Major bugfixes (memory and resource management):
5887 - Fixed some memory leaks -- some quite frequent, some almost
5888 impossible to trigger -- based on results from Coverity.
5889 - Speed up parsing and cut down on memory fragmentation by using
5890 stack-style allocations for parsing directory objects. Previously,
5891 this accounted for over 40% of allocations from within Tor's code
5892 on a typical directory cache.
5893 - Use a Bloom filter rather than a digest-based set to track which
5894 descriptors we need to keep around when we're cleaning out old
5895 router descriptors. This speeds up the computation significantly,
5896 and may reduce fragmentation.
5898 o New/changed config options:
5899 - Now NodeFamily and MyFamily config options allow spaces in
5900 identity fingerprints, so it's easier to paste them in.
5901 Suggested by Lucky Green.
5902 - Allow ports 465 and 587 in the default exit policy again. We had
5903 rejected them in 0.1.0.15, because back in 2005 they were commonly
5904 misconfigured and ended up as spam targets. We hear they are better
5905 locked down these days.
5906 - Make TrackHostExit mappings expire a while after their last use, not
5907 after their creation. Patch from Robert Hogan.
5908 - Add an ExcludeExitNodes option so users can list a set of nodes
5909 that should be be excluded from the exit node position, but
5910 allowed elsewhere. Implements proposal 151.
5911 - New --hush command-line option similar to --quiet. While --quiet
5912 disables all logging to the console on startup, --hush limits the
5913 output to messages of warning and error severity.
5914 - New configure/torrc options (--enable-geoip-stats,
5915 DirRecordUsageByCountry) to record how many IPs we've served
5916 directory info to in each country code, how many status documents
5917 total we've sent to each country code, and what share of the total
5918 directory requests we should expect to see.
5919 - Make outbound DNS packets respect the OutboundBindAddress setting.
5920 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5921 - Allow separate log levels to be configured for different logging
5922 domains. For example, this allows one to log all notices, warnings,
5923 or errors, plus all memory management messages of level debug or
5924 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
5925 - Update to the "June 3 2009" ip-to-country file.
5927 o Minor features (relays):
5928 - Raise the minimum rate limiting to be a relay from 20000 bytes
5929 to 20480 bytes (aka 20KB/s), to match our documentation. Also
5930 update directory authorities so they always assign the Fast flag
5931 to relays with 20KB/s of capacity. Now people running relays won't
5932 suddenly find themselves not seeing any use, if the network gets
5934 - If we're a relay and we change our IP address, be more verbose
5935 about the reason that made us change. Should help track down
5936 further bugs for relays on dynamic IP addresses.
5937 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5938 - Implement most of Proposal 152: allow specialized servers to permit
5939 single-hop circuits, and clients to use those servers to build
5940 single-hop circuits when using a specialized controller. Patch
5941 from Josh Albrecht. Resolves feature request 768.
5942 - When relays do their initial bandwidth measurement, don't limit
5943 to just our entry guards for the test circuits. Otherwise we tend
5944 to have multiple test circuits going through a single entry guard,
5945 which makes our bandwidth test less accurate. Fixes part of bug 654;
5946 patch contributed by Josh Albrecht.
5948 o Minor features (directory authorities):
5949 - Try not to open more than one descriptor-downloading connection
5950 to an authority at once. This should reduce load on directory
5951 authorities. Fixes bug 366.
5952 - Add cross-certification to newly generated certificates, so that
5953 a signing key is enough information to look up a certificate. Start
5954 serving certificates by <identity digest, signing key digest>
5955 pairs. Implements proposal 157.
5956 - When a directory authority downloads a descriptor that it then
5957 immediately rejects, do not retry downloading it right away. Should
5958 save some bandwidth on authorities. Fix for bug 888. Patch by
5960 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5961 help debug WFU and MTBF calculations.
5962 - In directory authorities' approved-routers files, allow
5963 fingerprints with or without space.
5965 o Minor features (directory mirrors):
5966 - When a download gets us zero good descriptors, do not notify
5967 Tor that new directory information has arrived.
5968 - Servers support a new URL scheme for consensus downloads that
5969 allows the client to specify which authorities are trusted.
5970 The server then only sends the consensus if the client will trust
5971 it. Otherwise a 404 error is sent back. Clients use this
5972 new scheme when the server supports it (meaning it's running
5973 0.2.1.1-alpha or later). Implements proposal 134.
5975 o Minor features (bridges):
5976 - If the bridge config line doesn't specify a port, assume 443.
5977 This makes bridge lines a bit smaller and easier for users to
5979 - If we're using bridges and our network goes away, be more willing
5980 to forgive our bridges and try again when we get an application
5983 o Minor features (hidden services):
5984 - When the client launches an introduction circuit, retry with a
5985 new circuit after 30 seconds rather than 60 seconds.
5986 - Launch a second client-side introduction circuit in parallel
5987 after a delay of 15 seconds (based on work by Christian Wilms).
5988 - Hidden services start out building five intro circuits rather
5989 than three, and when the first three finish they publish a service
5990 descriptor using those. Now we publish our service descriptor much
5991 faster after restart.
5992 - Drop the requirement to have an open dir port for storing and
5993 serving v2 hidden service descriptors.
5995 o Minor features (build and packaging):
5996 - On Linux, use the prctl call to re-enable core dumps when the User
5998 - Try to make sure that the version of Libevent we're running with
5999 is binary-compatible with the one we built with. May address bug
6001 - Add a new --enable-local-appdata configuration switch to change
6002 the default location of the datadir on win32 from APPDATA to
6003 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6004 entirely. Patch from coderman.
6005 - Build correctly against versions of OpenSSL 0.9.8 or later that
6006 are built without support for deprecated functions.
6007 - On platforms with a maximum syslog string length, truncate syslog
6008 messages to that length ourselves, rather than relying on the
6009 system to do it for us.
6010 - Automatically detect MacOSX versions earlier than 10.4.0, and
6011 disable kqueue from inside Tor when running with these versions.
6012 We previously did this from the startup script, but that was no
6013 help to people who didn't use the startup script. Resolves bug 863.
6014 - Build correctly when configured to build outside the main source
6015 path. Patch from Michael Gold.
6016 - Disable GCC's strict alias optimization by default, to avoid the
6017 likelihood of its introducing subtle bugs whenever our code violates
6018 the letter of C99's alias rules.
6019 - Change the contrib/tor.logrotate script so it makes the new
6020 logs as "_tor:_tor" rather than the default, which is generally
6021 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6022 - Change our header file guard macros to be less likely to conflict
6023 with system headers. Adam Langley noticed that we were conflicting
6024 with log.h on Android.
6025 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6026 and stop using a warning that had become unfixably verbose under
6028 - Use a lockfile to make sure that two Tor processes are not
6029 simultaneously running with the same datadir.
6030 - Allow OpenSSL to use dynamic locks if it wants.
6031 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
6033 o Minor features (controllers):
6034 - When generating circuit events with verbose nicknames for
6035 controllers, try harder to look up nicknames for routers on a
6036 circuit. (Previously, we would look in the router descriptors we had
6037 for nicknames, but not in the consensus.) Partial fix for bug 941.
6038 - New controller event NEWCONSENSUS that lists the networkstatus
6039 lines for every recommended relay. Now controllers like Torflow
6040 can keep up-to-date on which relays they should be using.
6041 - New controller event "clients_seen" to report a geoip-based summary
6042 of which countries we've seen clients from recently. Now controllers
6043 like Vidalia can show bridge operators that they're actually making
6045 - Add a 'getinfo status/clients-seen' controller command, in case
6046 controllers want to hear clients_seen events but connect late.
6047 - New CONSENSUS_ARRIVED event to note when a new consensus has
6048 been fetched and validated.
6049 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6050 controllers to prevent SIGHUP from reloading the configuration.
6052 - Return circuit purposes in response to GETINFO circuit-status.
6054 - Serve the latest v3 networkstatus consensus via the control
6055 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6056 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6057 controller can query our current bootstrap state in case it attaches
6058 partway through and wants to catch up.
6059 - Provide circuit purposes along with circuit events to the controller.
6061 o Minor features (tools):
6062 - Do not have tor-resolve automatically refuse all .onion addresses;
6063 if AutomapHostsOnResolve is set in your torrc, this will work fine.
6064 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6065 people find host:port too confusing.
6066 - Print the SOCKS5 error message string as well as the error code
6067 when a tor-resolve request fails. Patch from Jacob.
6069 o Minor bugfixes (memory and resource management):
6070 - Clients no longer cache certificates for authorities they do not
6071 recognize. Bugfix on 0.2.0.9-alpha.
6072 - Do not use C's stdio library for writing to log files. This will
6073 improve logging performance by a minute amount, and will stop
6074 leaking fds when our disk is full. Fixes bug 861.
6075 - Stop erroneous use of O_APPEND in cases where we did not in fact
6076 want to re-seek to the end of a file before every last write().
6077 - Fix a small alignment and memory-wasting bug on buffer chunks.
6079 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6080 to avoid unused RAM in buffer chunks and memory pools.
6081 - Reduce the default smartlist size from 32 to 16; it turns out that
6082 most smartlists hold around 8-12 elements tops.
6083 - Make dumpstats() log the fullness and size of openssl-internal
6085 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6086 patch to their OpenSSL, turn it on to save memory on servers. This
6087 patch will (with any luck) get included in a mainline distribution
6089 - Fix a memory leak when v3 directory authorities load their keys
6090 and cert from disk. Bugfix on 0.2.0.1-alpha.
6091 - Stop using malloc_usable_size() to use more area than we had
6092 actually allocated: it was safe, but made valgrind really unhappy.
6093 - Make the assert_circuit_ok() function work correctly on circuits that
6094 have already been marked for close.
6095 - Fix uninitialized size field for memory area allocation: may improve
6096 memory performance during directory parsing.
6098 o Minor bugfixes (clients):
6099 - Stop reloading the router list from disk for no reason when we
6100 run out of reachable directory mirrors. Once upon a time reloading
6101 it would set the 'is_running' flag back to 1 for them. It hasn't
6102 done that for a long time.
6103 - When we had picked an exit node for a connection, but marked it as
6104 "optional", and it turned out we had no onion key for the exit,
6105 stop wanting that exit and try again. This situation may not
6106 be possible now, but will probably become feasible with proposal
6107 158. Spotted by rovv. Fixes another case of bug 752.
6108 - Fix a bug in address parsing that was preventing bridges or hidden
6109 service targets from being at IPv6 addresses.
6110 - Do not remove routers as too old if we do not have any consensus
6111 document. Bugfix on 0.2.0.7-alpha.
6112 - When an exit relay resolves a stream address to a local IP address,
6113 do not just keep retrying that same exit relay over and
6114 over. Instead, just close the stream. Addresses bug 872. Bugfix
6115 on 0.2.0.32. Patch from rovv.
6116 - Made Tor a little less aggressive about deleting expired
6117 certificates. Partial fix for bug 854.
6118 - Treat duplicate certificate fetches as failures, so that we do
6119 not try to re-fetch an expired certificate over and over and over.
6120 - Do not say we're fetching a certificate when we'll in fact skip it
6121 because of a pending download.
6122 - If we have correct permissions on $datadir, we complain to stdout
6123 and fail to start. But dangerous permissions on
6124 $datadir/cached-status/ would cause us to open a log and complain
6125 there. Now complain to stdout and fail to start in both cases. Fixes
6126 bug 820, reported by seeess.
6128 o Minor bugfixes (bridges):
6129 - When we made bridge authorities stop serving bridge descriptors over
6130 unencrypted links, we also broke DirPort reachability testing for
6131 bridges. So bridges with a non-zero DirPort were printing spurious
6132 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6133 - Don't allow a bridge to publish its router descriptor to a
6134 non-bridge directory authority. Fixes part of bug 932.
6135 - When we change to or from being a bridge, reset our counts of
6136 client usage by country. Fixes bug 932.
6138 o Minor bugfixes (relays):
6139 - Log correct error messages for DNS-related network errors on
6141 - Actually return -1 in the error case for read_bandwidth_usage().
6142 Harmless bug, since we currently don't care about the return value
6143 anywhere. Bugfix on 0.2.0.9-alpha.
6144 - Provide a more useful log message if bug 977 (related to buffer
6145 freelists) ever reappears, and do not crash right away.
6146 - We were already rejecting relay begin cells with destination port
6147 of 0. Now also reject extend cells with destination port or address
6148 of 0. Suggested by lark.
6149 - When we can't transmit a DNS request due to a network error, retry
6150 it after a while, and eventually transmit a failing response to
6151 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
6152 - Solve a bug that kept hardware crypto acceleration from getting
6153 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6155 - When a canonical connection appears later in our internal list
6156 than a noncanonical one for a given OR ID, always use the
6157 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6159 - Avoid some nasty corner cases in the logic for marking connections
6160 as too old or obsolete or noncanonical for circuits. Partial
6162 - Fix another interesting corner-case of bug 891 spotted by rovv:
6163 Previously, if two hosts had different amounts of clock drift, and
6164 one of them created a new connection with just the wrong timing,
6165 the other might decide to deprecate the new connection erroneously.
6166 Bugfix on 0.1.1.13-alpha.
6167 - If one win32 nameserver fails to get added, continue adding the
6168 rest, and don't automatically fail.
6169 - Fix a bug where an unreachable relay would establish enough
6170 reachability testing circuits to do a bandwidth test -- if
6171 we already have a connection to the middle hop of the testing
6172 circuit, then it could establish the last hop by using the existing
6173 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6174 circuits no longer use entry guards in 0.2.1.3-alpha.
6176 o Minor bugfixes (directory authorities):
6177 - Limit uploaded directory documents to be 16M rather than 500K.
6178 The directory authorities were refusing v3 consensus votes from
6179 other authorities, since the votes are now 504K. Fixes bug 959;
6180 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
6181 - Directory authorities should never send a 503 "busy" response to
6182 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
6184 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6185 headers. Bugfix on 0.2.0.10-alpha.
6187 o Minor bugfixes (hidden services):
6188 - When we can't find an intro key for a v2 hidden service descriptor,
6189 fall back to the v0 hidden service descriptor and log a bug message.
6190 Workaround for bug 1024.
6191 - In very rare situations new hidden service descriptors were
6192 published earlier than 30 seconds after the last change to the
6193 service. (We currently think that a hidden service descriptor
6194 that's been stable for 30 seconds is worth publishing.)
6195 - If a hidden service sends us an END cell, do not consider
6196 retrying the connection; just close it. Patch from rovv.
6197 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6198 service directories if they have no advertised dir port. Bugfix
6201 o Minor bugfixes (tools):
6202 - In the torify(1) manpage, mention that tsocks will leak your
6205 o Minor bugfixes (controllers):
6206 - If the controller claimed responsibility for a stream, but that
6207 stream never finished making its connection, it would live
6208 forever in circuit_wait state. Now we close it after SocksTimeout
6209 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
6210 - Make DNS resolved controller events into "CLOSED", not
6211 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6213 - The control port would close the connection before flushing long
6214 replies, such as the network consensus, if a QUIT command was issued
6215 before the reply had completed. Now, the control port flushes all
6216 pending replies before closing the connection. Also fix a spurious
6217 warning when a QUIT command is issued after a malformed or rejected
6218 AUTHENTICATE command, but before the connection was closed. Patch
6219 by Marcus Griep. Fixes bugs 1015 and 1016.
6220 - Fix a bug that made stream bandwidth get misreported to the
6223 o Deprecated and removed features:
6224 - The old "tor --version --version" command, which would print out
6225 the subversion "Id" of most of the source files, is now removed. It
6226 turned out to be less useful than we'd expected, and harder to
6228 - RedirectExits has been removed. It was deprecated since
6230 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6231 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6232 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6233 - Directory mirrors no longer fetch the v1 directory or
6234 running-routers files. They are obsolete, and nobody asks for them
6235 anymore. This is the first step to making v1 authorities obsolete.
6236 - Take out the TestVia config option, since it was a workaround for
6237 a bug that was fixed in Tor 0.1.1.21.
6238 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6239 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6240 and nobody seems to be using them. Fixes bug 754. Bugfix on
6241 0.1.0.1-rc. Patch from Christian Wilms.
6242 - Remove all backward-compatibility code for relays running
6243 versions of Tor so old that they no longer work at all on the
6246 o Code simplifications and refactoring:
6247 - Tool-assisted documentation cleanup. Nearly every function or
6248 static variable in Tor should have its own documentation now.
6249 - Rename the confusing or_is_obsolete field to the more appropriate
6250 is_bad_for_new_circs, and move it to or_connection_t where it
6252 - Move edge-only flags from connection_t to edge_connection_t: not
6253 only is this better coding, but on machines of plausible alignment,
6254 it should save 4-8 bytes per connection_t. "Every little bit helps."
6255 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6256 for consistency; keep old option working for backward compatibility.
6257 - Simplify the code for finding connections to use for a circuit.
6258 - Revise the connection_new functions so that a more typesafe variant
6259 exists. This will work better with Coverity, and let us find any
6260 actual mistakes we're making here.
6261 - Refactor unit testing logic so that dmalloc can be used sensibly
6262 with unit tests to check for memory leaks.
6263 - Move all hidden-service related fields from connection and circuit
6264 structure to substructures: this way they won't eat so much memory.
6265 - Squeeze 2-5% out of client performance (according to oprofile) by
6266 improving the implementation of some policy-manipulation functions.
6267 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6268 be more efficient. Formerly it was quadratic in the number of
6269 servers; now it should be linear. Fixes bug 509.
6270 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6271 and n_conn_id_digest fields into a separate structure that's
6272 only needed when the circuit has not yet attached to an n_conn.
6273 - Optimize out calls to time(NULL) that occur for every IO operation,
6274 or for every cell. On systems like Windows where time() is a
6275 slow syscall, this fix will be slightly helpful.
6278 Changes in version 0.2.0.35 - 2009-06-24
6280 - Avoid crashing in the presence of certain malformed descriptors.
6281 Found by lark, and by automated fuzzing.
6282 - Fix an edge case where a malicious exit relay could convince a
6283 controller that the client's DNS question resolves to an internal IP
6284 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6287 - Finally fix the bug where dynamic-IP relays disappear when their
6288 IP address changes: directory mirrors were mistakenly telling
6289 them their old address if they asked via begin_dir, so they
6290 never got an accurate answer about their new address, so they
6291 just vanished after a day. For belt-and-suspenders, relays that
6292 don't set Address in their config now avoid using begin_dir for
6293 all direct connections. Should fix bugs 827, 883, and 900.
6294 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6295 that would occur on some exit nodes when DNS failures and timeouts
6296 occurred in certain patterns. Fix for bug 957.
6299 - When starting with a cache over a few days old, do not leak
6300 memory for the obsolete router descriptors in it. Bugfix on
6301 0.2.0.33; fixes bug 672.
6302 - Hidden service clients didn't use a cached service descriptor that
6303 was older than 15 minutes, but wouldn't fetch a new one either,
6304 because there was already one in the cache. Now, fetch a v2
6305 descriptor unless the same descriptor was added to the cache within
6306 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6309 Changes in version 0.2.0.34 - 2009-02-08
6310 Tor 0.2.0.34 features several more security-related fixes. You should
6311 upgrade, especially if you run an exit relay (remote crash) or a
6312 directory authority (remote infinite loop), or you're on an older
6313 (pre-XP) or not-recently-patched Windows (remote exploit).
6315 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6316 have many known flaws, and nobody should be using them. You should
6317 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6318 stop using those packages and upgrade anyway.
6321 - Fix an infinite-loop bug on handling corrupt votes under certain
6322 circumstances. Bugfix on 0.2.0.8-alpha.
6323 - Fix a temporary DoS vulnerability that could be performed by
6324 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6325 - Avoid a potential crash on exit nodes when processing malformed
6326 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6327 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6328 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6331 - Fix compilation on systems where time_t is a 64-bit integer.
6332 Patch from Matthias Drochner.
6333 - Don't consider expiring already-closed client connections. Fixes
6334 bug 893. Bugfix on 0.0.2pre20.
6337 Changes in version 0.2.0.33 - 2009-01-21
6338 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6339 useful to users. It also finally fixes a bug where a relay or client
6340 that's been off for many days would take a long time to bootstrap.
6342 This update also fixes an important security-related bug reported by
6343 Ilja van Sprundel. You should upgrade. (We'll send out more details
6344 about the bug once people have had some time to upgrade.)
6347 - Fix a heap-corruption bug that may be remotely triggerable on
6348 some platforms. Reported by Ilja van Sprundel.
6351 - When a stream at an exit relay is in state "resolving" or
6352 "connecting" and it receives an "end" relay cell, the exit relay
6353 would silently ignore the end cell and not close the stream. If
6354 the client never closes the circuit, then the exit relay never
6355 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6357 - When sending CREATED cells back for a given circuit, use a 64-bit
6358 connection ID to find the right connection, rather than an addr:port
6359 combination. Now that we can have multiple OR connections between
6360 the same ORs, it is no longer possible to use addr:port to uniquely
6361 identify a connection.
6362 - Bridge relays that had DirPort set to 0 would stop fetching
6363 descriptors shortly after startup, and then briefly resume
6364 after a new bandwidth test and/or after publishing a new bridge
6365 descriptor. Bridge users that try to bootstrap from them would
6366 get a recent networkstatus but would get descriptors from up to
6367 18 hours earlier, meaning most of the descriptors were obsolete
6368 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6369 - Prevent bridge relays from serving their 'extrainfo' document
6370 to anybody who asks, now that extrainfo docs include potentially
6371 sensitive aggregated client geoip summaries. Bugfix on
6373 - If the cached networkstatus consensus is more than five days old,
6374 discard it rather than trying to use it. In theory it could be
6375 useful because it lists alternate directory mirrors, but in practice
6376 it just means we spend many minutes trying directory mirrors that
6377 are long gone from the network. Also discard router descriptors as
6378 we load them if they are more than five days old, since the onion
6379 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6382 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6383 could make gcc generate non-functional binary search code. Bugfix
6385 - Build correctly on platforms without socklen_t.
6386 - Compile without warnings on solaris.
6387 - Avoid potential crash on internal error during signature collection.
6388 Fixes bug 864. Patch from rovv.
6389 - Correct handling of possible malformed authority signing key
6390 certificates with internal signature types. Fixes bug 880.
6391 Bugfix on 0.2.0.3-alpha.
6392 - Fix a hard-to-trigger resource leak when logging credential status.
6394 - When we can't initialize DNS because the network is down, do not
6395 automatically stop Tor from starting. Instead, we retry failed
6396 dns_init() every 10 minutes, and change the exit policy to reject
6397 *:* until one succeeds. Fixes bug 691.
6398 - Use 64 bits instead of 32 bits for connection identifiers used with
6399 the controller protocol, to greatly reduce risk of identifier reuse.
6400 - When we're choosing an exit node for a circuit, and we have
6401 no pending streams, choose a good general exit rather than one that
6402 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6403 - Fix another case of assuming, when a specific exit is requested,
6404 that we know more than the user about what hosts it allows.
6405 Fixes one case of bug 752. Patch from rovv.
6406 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6407 seconds. Warn the user if lower values are given in the
6408 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6409 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6410 user if lower values are given in the configuration. Bugfix on
6411 0.1.1.17-rc. Patch by Sebastian.
6412 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6413 the cache because we already had a v0 descriptor with the same ID.
6414 Bugfix on 0.2.0.18-alpha.
6415 - Fix a race condition when freeing keys shared between main thread
6416 and CPU workers that could result in a memory leak. Bugfix on
6417 0.1.0.1-rc. Fixes bug 889.
6418 - Send a valid END cell back when a client tries to connect to a
6419 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6420 840. Patch from rovv.
6421 - Check which hops rendezvous stream cells are associated with to
6422 prevent possible guess-the-streamid injection attacks from
6423 intermediate hops. Fixes another case of bug 446. Based on patch
6425 - If a broken client asks a non-exit router to connect somewhere,
6426 do not even do the DNS lookup before rejecting the connection.
6427 Fixes another case of bug 619. Patch from rovv.
6428 - When a relay gets a create cell it can't decrypt (e.g. because it's
6429 using the wrong onion key), we were dropping it and letting the
6430 client time out. Now actually answer with a destroy cell. Fixes
6431 bug 904. Bugfix on 0.0.2pre8.
6433 o Minor bugfixes (hidden services):
6434 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6435 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6438 - Report the case where all signatures in a detached set are rejected
6439 differently than the case where there is an error handling the
6441 - When we realize that another process has modified our cached
6442 descriptors, print out a more useful error message rather than
6443 triggering an assertion. Fixes bug 885. Patch from Karsten.
6444 - Implement the 0x20 hack to better resist DNS poisoning: set the
6445 case on outgoing DNS requests randomly, and reject responses that do
6446 not match the case correctly. This logic can be disabled with the
6447 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6448 of servers that do not reliably preserve case in replies. See
6449 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6451 - Check DNS replies for more matching fields to better resist DNS
6453 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6454 compress cells, which are basically all encrypted, compressed, or
6458 Changes in version 0.2.0.32 - 2008-11-20
6459 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6460 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6461 a smaller security flaw that might allow an attacker to access local
6462 services, further improves hidden service performance, and fixes a
6463 variety of other issues.
6466 - The "User" and "Group" config options did not clear the
6467 supplementary group entries for the Tor process. The "User" option
6468 is now more robust, and we now set the groups to the specified
6469 user's primary group. The "Group" option is now ignored. For more
6470 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6471 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6472 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6473 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6474 consistently obeyed: if an exit relay refuses a stream because its
6475 exit policy doesn't allow it, we would remember what IP address
6476 the relay said the destination address resolves to, even if it's
6477 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6480 - Fix a DOS opportunity during the voting signature collection process
6481 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6483 o Major bugfixes (hidden services):
6484 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6485 we were failing the whole hidden service request when the v0
6486 descriptor fetch fails, even if the v2 fetch is still pending and
6487 might succeed. Similarly, if the last v2 fetch fails, we were
6488 failing the whole hidden service request even if a v0 fetch is
6489 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6490 - When extending a circuit to a hidden service directory to upload a
6491 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6492 requests failed, because the router descriptor has not been
6493 downloaded yet. In these cases, do not attempt to upload the
6494 rendezvous descriptor, but wait until the router descriptor is
6495 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6496 descriptor from a hidden service directory for which the router
6497 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6501 - Fix several infrequent memory leaks spotted by Coverity.
6502 - When testing for libevent functions, set the LDFLAGS variable
6503 correctly. Found by Riastradh.
6504 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6505 bootstrapping with tunneled directory connections. Bugfix on
6506 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6507 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6508 and we know that server B rejects most-but-not all connections to
6509 port 80, we would previously reject the connection. Now, we assume
6510 the user knows what they were asking for. Fixes bug 752. Bugfix
6511 on 0.0.9rc5. Diagnosed by BarkerJr.
6512 - If we overrun our per-second write limits a little, count this as
6513 having used up our write allocation for the second, and choke
6514 outgoing directory writes. Previously, we had only counted this when
6515 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6516 Bugfix on 0.2.0.x (??).
6517 - Remove the old v2 directory authority 'lefkada' from the default
6518 list. It has been gone for many months.
6519 - Stop doing unaligned memory access that generated bus errors on
6520 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6521 - Make USR2 log-level switch take effect immediately. Bugfix on
6524 o Minor bugfixes (controller):
6525 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6526 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6529 Changes in version 0.2.0.31 - 2008-09-03
6530 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6531 a big bug we're seeing where in rare cases traffic from one Tor stream
6532 gets mixed into another stream, and fixes a variety of smaller issues.
6535 - Make sure that two circuits can never exist on the same connection
6536 with the same circuit ID, even if one is marked for close. This
6537 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6538 - Relays now reject risky extend cells: if the extend cell includes
6539 a digest of all zeroes, or asks to extend back to the relay that
6540 sent the extend cell, tear down the circuit. Ideas suggested
6542 - If not enough of our entry guards are available so we add a new
6543 one, we might use the new one even if it overlapped with the
6544 current circuit's exit relay (or its family). Anonymity bugfix
6545 pointed out by rovv.
6548 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6549 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6550 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6551 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6552 - Pick size of default geoip filename string correctly on windows.
6553 Fixes bug 806. Bugfix on 0.2.0.30.
6554 - Make the autoconf script accept the obsolete --with-ssl-dir
6555 option as an alias for the actually-working --with-openssl-dir
6556 option. Fix the help documentation to recommend --with-openssl-dir.
6557 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6558 - When using the TransPort option on OpenBSD, and using the User
6559 option to change UID and drop privileges, make sure to open
6560 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6561 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6562 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6563 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6564 on the client side when connecting to a hidden service. Bugfix
6565 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6566 - When closing an application-side connection because its circuit is
6567 getting torn down, generate the stream event correctly. Bugfix on
6568 0.1.2.x. Anonymous patch.
6571 Changes in version 0.2.0.30 - 2008-07-15
6572 This new stable release switches to a more efficient directory
6573 distribution design, adds features to make connections to the Tor
6574 network harder to block, allows Tor to act as a DNS proxy, adds separate
6575 rate limiting for relayed traffic to make it easier for clients to
6576 become relays, fixes a variety of potential anonymity problems, and
6577 includes the usual huge pile of other features and bug fixes.
6579 o New v3 directory design:
6580 - Tor now uses a new way to learn about and distribute information
6581 about the network: the directory authorities vote on a common
6582 network status document rather than each publishing their own
6583 opinion. Now clients and caches download only one networkstatus
6584 document to bootstrap, rather than downloading one for each
6585 authority. Clients only download router descriptors listed in
6586 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
6588 - Set up moria1, tor26, and dizum as v3 directory authorities
6589 in addition to being v2 authorities. Also add three new ones:
6590 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
6591 dannenberg (run by CCC).
6592 - Switch to multi-level keys for directory authorities: now their
6593 long-term identity key can be kept offline, and they periodically
6594 generate a new signing key. Clients fetch the "key certificates"
6595 to keep up to date on the right keys. Add a standalone tool
6596 "tor-gencert" to generate key certificates. Implements proposal 103.
6597 - Add a new V3AuthUseLegacyKey config option to make it easier for
6598 v3 authorities to change their identity keys if another bug like
6599 Debian's OpenSSL RNG flaw appears.
6600 - Authorities and caches fetch the v2 networkstatus documents
6601 less often, now that v3 is recommended.
6603 o Make Tor connections stand out less on the wire:
6604 - Use an improved TLS handshake designed by Steven Murdoch in proposal
6605 124, as revised in proposal 130. The new handshake is meant to
6606 be harder for censors to fingerprint, and it adds the ability
6607 to detect certain kinds of man-in-the-middle traffic analysis
6608 attacks. The new handshake format includes version negotiation for
6609 OR connections as described in proposal 105, which will allow us
6610 to improve Tor's link protocol more safely in the future.
6611 - Enable encrypted directory connections by default for non-relays,
6612 so censor tools that block Tor directory connections based on their
6613 plaintext patterns will no longer work. This means Tor works in
6614 certain censored countries by default again.
6615 - Stop including recognizeable strings in the commonname part of
6616 Tor's x509 certificates.
6618 o Implement bridge relays:
6619 - Bridge relays (or "bridges" for short) are Tor relays that aren't
6620 listed in the main Tor directory. Since there is no complete public
6621 list of them, even an ISP that is filtering connections to all the
6622 known Tor relays probably won't be able to block all the bridges.
6623 See doc/design-paper/blocking.pdf and proposal 125 for details.
6624 - New config option BridgeRelay that specifies you want to be a
6625 bridge relay rather than a normal relay. When BridgeRelay is set
6626 to 1, then a) you cache dir info even if your DirPort ins't on,
6627 and b) the default for PublishServerDescriptor is now "bridge"
6628 rather than "v2,v3".
6629 - New config option "UseBridges 1" for clients that want to use bridge
6630 relays instead of ordinary entry guards. Clients then specify
6631 bridge relays by adding "Bridge" lines to their config file. Users
6632 can learn about a bridge relay either manually through word of
6633 mouth, or by one of our rate-limited mechanisms for giving out
6634 bridge addresses without letting an attacker easily enumerate them
6635 all. See https://www.torproject.org/bridges for details.
6636 - Bridge relays behave like clients with respect to time intervals
6637 for downloading new v3 consensus documents -- otherwise they
6638 stand out. Bridge users now wait until the end of the interval,
6639 so their bridge relay will be sure to have a new consensus document.
6641 o Implement bridge directory authorities:
6642 - Bridge authorities are like normal directory authorities, except
6643 they don't serve a list of known bridges. Therefore users that know
6644 a bridge's fingerprint can fetch a relay descriptor for that bridge,
6645 including fetching updates e.g. if the bridge changes IP address,
6646 yet an attacker can't just fetch a list of all the bridges.
6647 - Set up Tonga as the default bridge directory authority.
6648 - Bridge authorities refuse to serve bridge descriptors or other
6649 bridge information over unencrypted connections (that is, when
6650 responding to direct DirPort requests rather than begin_dir cells.)
6651 - Bridge directory authorities do reachability testing on the
6652 bridges they know. They provide router status summaries to the
6653 controller via "getinfo ns/purpose/bridge", and also dump summaries
6654 to a file periodically, so we can keep internal stats about which
6655 bridges are functioning.
6656 - If bridge users set the UpdateBridgesFromAuthority config option,
6657 but the digest they ask for is a 404 on the bridge authority,
6658 they fall back to contacting the bridge directly.
6659 - Bridges always use begin_dir to publish their server descriptor to
6660 the bridge authority using an anonymous encrypted tunnel.
6661 - Early work on a "bridge community" design: if bridge authorities set
6662 the BridgePassword config option, they will serve a snapshot of
6663 known bridge routerstatuses from their DirPort to anybody who
6664 knows that password. Unset by default.
6665 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
6666 report sanitized aggregated summaries in their extra-info documents
6667 privately to the bridge authority, listing which countries are
6668 able to reach them. We hope this mechanism will let us learn when
6669 certain countries start trying to block bridges.
6670 - Bridge authorities write bridge descriptors to disk, so they can
6671 reload them after a reboot. They can also export the descriptors
6672 to other programs, so we can distribute them to blocked users via
6673 the BridgeDB interface, e.g. via https://bridges.torproject.org/
6674 and bridges@torproject.org.
6676 o Tor can be a DNS proxy:
6677 - The new client-side DNS proxy feature replaces the need for
6678 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
6679 for DNS requests on port 9999, use the Tor network to resolve them
6680 anonymously, and send the reply back like a regular DNS server.
6681 The code still only implements a subset of DNS.
6682 - Add a new AutomapHostsOnResolve option: when it is enabled, any
6683 resolve request for hosts matching a given pattern causes Tor to
6684 generate an internal virtual address mapping for that host. This
6685 allows DNSPort to work sensibly with hidden service users. By
6686 default, .exit and .onion addresses are remapped; the list of
6687 patterns can be reconfigured with AutomapHostsSuffixes.
6688 - Add an "-F" option to tor-resolve to force a resolve for a .onion
6689 address. Thanks to the AutomapHostsOnResolve option, this is no
6690 longer a completely silly thing to do.
6692 o Major features (relay usability):
6693 - New config options RelayBandwidthRate and RelayBandwidthBurst:
6694 a separate set of token buckets for relayed traffic. Right now
6695 relayed traffic is defined as answers to directory requests, and
6696 OR connections that don't have any local circuits on them. See
6697 proposal 111 for details.
6698 - Create listener connections before we setuid to the configured
6699 User and Group. Now non-Windows users can choose port values
6700 under 1024, start Tor as root, and have Tor bind those ports
6701 before it changes to another UID. (Windows users could already
6703 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6704 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6705 on "vserver" accounts. Patch from coderman.
6707 o Major features (directory authorities):
6708 - Directory authorities track weighted fractional uptime and weighted
6709 mean-time-between failures for relays. WFU is suitable for deciding
6710 whether a node is "usually up", while MTBF is suitable for deciding
6711 whether a node is "likely to stay up." We need both, because
6712 "usually up" is a good requirement for guards, while "likely to
6713 stay up" is a good requirement for long-lived connections.
6714 - Directory authorities use a new formula for selecting which relays
6715 to advertise as Guards: they must be in the top 7/8 in terms of
6716 how long we have known about them, and above the median of those
6717 nodes in terms of weighted fractional uptime.
6718 - Directory authorities use a new formula for selecting which relays
6719 to advertise as Stable: when we have 4 or more days of data, use
6720 median measured MTBF rather than median declared uptime. Implements
6722 - Directory authorities accept and serve "extra info" documents for
6723 routers. Routers now publish their bandwidth-history lines in the
6724 extra-info docs rather than the main descriptor. This step saves
6725 60% (!) on compressed router descriptor downloads. Servers upload
6726 extra-info docs to any authority that accepts them; directory
6727 authorities now allow multiple router descriptors and/or extra
6728 info documents to be uploaded in a single go. Authorities, and
6729 caches that have been configured to download extra-info documents,
6730 download them as needed. Implements proposal 104.
6731 - Authorities now list relays who have the same nickname as
6732 a different named relay, but list them with a new flag:
6733 "Unnamed". Now we can make use of relays that happen to pick the
6734 same nickname as a server that registered two years ago and then
6735 disappeared. Implements proposal 122.
6736 - Store routers in a file called cached-descriptors instead of in
6737 cached-routers. Initialize cached-descriptors from cached-routers
6738 if the old format is around. The new format allows us to store
6739 annotations along with descriptors, to record the time we received
6740 each descriptor, its source, and its purpose: currently one of
6741 general, controller, or bridge.
6743 o Major features (other):
6744 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
6745 Tor can warn and/or refuse connections to ports commonly used with
6746 vulnerable-plaintext protocols. Currently we warn on ports 23,
6747 109, 110, and 143, but we don't reject any. Based on proposal 129
6748 by Kevin Bauer and Damon McCoy.
6749 - Integrate Karsten Loesing's Google Summer of Code project to publish
6750 hidden service descriptors on a set of redundant relays that are a
6751 function of the hidden service address. Now we don't have to rely
6752 on three central hidden service authorities for publishing and
6753 fetching every hidden service descriptor. Implements proposal 114.
6754 - Allow tunnelled directory connections to ask for an encrypted
6755 "begin_dir" connection or an anonymized "uses a full Tor circuit"
6756 connection independently. Now we can make anonymized begin_dir
6757 connections for (e.g.) more secure hidden service posting and
6760 o Major bugfixes (crashes and assert failures):
6761 - Stop imposing an arbitrary maximum on the number of file descriptors
6762 used for busy servers. Bug reported by Olaf Selke; patch from
6764 - Avoid possible failures when generating a directory with routers
6765 with over-long versions strings, or too many flags set.
6766 - Fix a rare assert error when we're closing one of our threads:
6767 use a mutex to protect the list of logs, so we never write to the
6768 list as it's being freed. Fixes the very rare bug 575, which is
6769 kind of the revenge of bug 222.
6770 - Avoid segfault in the case where a badly behaved v2 versioning
6771 directory sends a signed networkstatus with missing client-versions.
6772 - When we hit an EOF on a log (probably because we're shutting down),
6773 don't try to remove the log from the list: just mark it as
6774 unusable. (Bulletproofs against bug 222.)
6776 o Major bugfixes (code security fixes):
6777 - Detect size overflow in zlib code. Reported by Justin Ferguson and
6779 - Rewrite directory tokenization code to never run off the end of
6780 a string. Fixes bug 455. Patch from croup.
6781 - Be more paranoid about overwriting sensitive memory on free(),
6782 as a defensive programming tactic to ensure forward secrecy.
6784 o Major bugfixes (anonymity fixes):
6785 - Reject requests for reverse-dns lookup of names that are in
6786 a private address space. Patch from lodger.
6787 - Never report that we've used more bandwidth than we're willing to
6788 relay: it leaks how much non-relay traffic we're using. Resolves
6790 - As a client, do not believe any server that tells us that an
6791 address maps to an internal address space.
6792 - Warn about unsafe ControlPort configurations.
6793 - Directory authorities now call routers Fast if their bandwidth is
6794 at least 100KB/s, and consider their bandwidth adequate to be a
6795 Guard if it is at least 250KB/s, no matter the medians. This fix
6796 complements proposal 107.
6797 - Directory authorities now never mark more than 2 servers per IP as
6798 Valid and Running (or 5 on addresses shared by authorities).
6799 Implements proposal 109, by Kevin Bauer and Damon McCoy.
6800 - If we're a relay, avoid picking ourselves as an introduction point,
6801 a rendezvous point, or as the final hop for internal circuits. Bug
6802 reported by taranis and lodger.
6803 - Exit relays that are used as a client can now reach themselves
6804 using the .exit notation, rather than just launching an infinite
6805 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
6806 - Fix a bug where, when we were choosing the 'end stream reason' to
6807 put in our relay end cell that we send to the exit relay, Tor
6808 clients on Windows were sometimes sending the wrong 'reason'. The
6809 anonymity problem is that exit relays may be able to guess whether
6810 the client is running Windows, thus helping partition the anonymity
6811 set. Down the road we should stop sending reasons to exit relays,
6812 or otherwise prevent future versions of this bug.
6813 - Only update guard status (usable / not usable) once we have
6814 enough directory information. This was causing us to discard all our
6815 guards on startup if we hadn't been running for a few weeks. Fixes
6817 - When our directory information has been expired for a while, stop
6818 being willing to build circuits using it. Fixes bug 401.
6820 o Major bugfixes (peace of mind for relay operators)
6821 - Non-exit relays no longer answer "resolve" relay cells, so they
6822 can't be induced to do arbitrary DNS requests. (Tor clients already
6823 avoid using non-exit relays for resolve cells, but now servers
6824 enforce this too.) Fixes bug 619. Patch from lodger.
6825 - When we setconf ClientOnly to 1, close any current OR and Dir
6826 listeners. Reported by mwenge.
6828 o Major bugfixes (other):
6829 - If we only ever used Tor for hidden service lookups or posts, we
6830 would stop building circuits and start refusing connections after
6831 24 hours, since we falsely believed that Tor was dormant. Reported
6833 - Add a new __HashedControlSessionPassword option for controllers
6834 to use for one-off session password hashes that shouldn't get
6835 saved to disk by SAVECONF --- Vidalia users were accumulating a
6836 pile of HashedControlPassword lines in their torrc files, one for
6837 each time they had restarted Tor and then clicked Save. Make Tor
6838 automatically convert "HashedControlPassword" to this new option but
6839 only when it's given on the command line. Partial fix for bug 586.
6840 - Patch from "Andrew S. Lists" to catch when we contact a directory
6841 mirror at IP address X and he says we look like we're coming from
6842 IP address X. Otherwise this would screw up our address detection.
6843 - Reject uploaded descriptors and extrainfo documents if they're
6844 huge. Otherwise we'll cache them all over the network and it'll
6845 clog everything up. Suggested by Aljosha Judmayer.
6846 - When a hidden service was trying to establish an introduction point,
6847 and Tor *did* manage to reuse one of the preemptively built
6848 circuits, it didn't correctly remember which one it used,
6849 so it asked for another one soon after, until there were no
6850 more preemptive circuits, at which point it launched one from
6851 scratch. Bugfix on 0.0.9.x.
6853 o Rate limiting and load balancing improvements:
6854 - When we add data to a write buffer in response to the data on that
6855 write buffer getting low because of a flush, do not consider the
6856 newly added data as a candidate for immediate flushing, but rather
6857 make it wait until the next round of writing. Otherwise, we flush
6858 and refill recursively, and a single greedy TLS connection can
6859 eat all of our bandwidth.
6860 - When counting the number of bytes written on a TLS connection,
6861 look at the BIO actually used for writing to the network, not
6862 at the BIO used (sometimes) to buffer data for the network.
6863 Looking at different BIOs could result in write counts on the
6864 order of ULONG_MAX. Fixes bug 614.
6865 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6866 Tor won't realize it should publish a new relay descriptor. Fixes
6867 bug 688, reported by mfr.
6868 - Avoid using too little bandwidth when our clock skips a few seconds.
6869 - Choose which bridge to use proportional to its advertised bandwidth,
6870 rather than uniformly at random. This should speed up Tor for
6871 bridge users. Also do this for people who set StrictEntryNodes.
6873 o Bootstrapping faster and building circuits more intelligently:
6874 - Fix bug 660 that was preventing us from knowing that we should
6875 preemptively build circuits to handle expected directory requests.
6876 - When we're checking if we have enough dir info for each relay
6877 to begin establishing circuits, make sure that we actually have
6878 the descriptor listed in the consensus, not just any descriptor.
6879 - Correctly notify one-hop connections when a circuit build has
6880 failed. Possible fix for bug 669. Found by lodger.
6881 - Clients now hold circuitless TLS connections open for 1.5 times
6882 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
6883 rebuild a new circuit over them within that timeframe. Previously,
6884 they held them open only for KeepalivePeriod (5 minutes).
6886 o Performance improvements (memory):
6887 - Add OpenBSD malloc code from "phk" as an optional malloc
6888 replacement on Linux: some glibc libraries do very poorly with
6889 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
6890 ./configure to get the replacement malloc code.
6891 - Switch our old ring buffer implementation for one more like that
6892 used by free Unix kernels. The wasted space in a buffer with 1mb
6893 of data will now be more like 8k than 1mb. The new implementation
6894 also avoids realloc();realloc(); patterns that can contribute to
6895 memory fragmentation.
6896 - Change the way that Tor buffers data that it is waiting to write.
6897 Instead of queueing data cells in an enormous ring buffer for each
6898 client->OR or OR->OR connection, we now queue cells on a separate
6899 queue for each circuit. This lets us use less slack memory, and
6900 will eventually let us be smarter about prioritizing different kinds
6902 - Reference-count and share copies of address policy entries; only 5%
6903 of them were actually distinct.
6904 - Tune parameters for cell pool allocation to minimize amount of
6906 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6907 for every single inactive connection_t. Free items from the
6908 4k/16k-buffer free lists when they haven't been used for a while.
6909 - Make memory debugging information describe more about history
6910 of cell allocation, so we can help reduce our memory use.
6911 - Be even more aggressive about releasing RAM from small
6912 empty buffers. Thanks to our free-list code, this shouldn't be too
6913 performance-intensive.
6914 - Log malloc statistics from mallinfo() on platforms where it exists.
6915 - Use memory pools to allocate cells with better speed and memory
6916 efficiency, especially on platforms where malloc() is inefficient.
6917 - Add a --with-tcmalloc option to the configure script to link
6918 against tcmalloc (if present). Does not yet search for non-system
6921 o Performance improvements (socket management):
6922 - Count the number of open sockets separately from the number of
6923 active connection_t objects. This will let us avoid underusing
6924 our allocated connection limit.
6925 - We no longer use socket pairs to link an edge connection to an
6926 anonymous directory connection or a DirPort test connection.
6927 Instead, we track the link internally and transfer the data
6928 in-process. This saves two sockets per "linked" connection (at the
6929 client and at the server), and avoids the nasty Windows socketpair()
6931 - We were leaking a file descriptor if Tor started with a zero-length
6932 cached-descriptors file. Patch by "freddy77".
6934 o Performance improvements (CPU use):
6935 - Never walk through the list of logs if we know that no log target
6936 is interested in a given message.
6937 - Call routerlist_remove_old_routers() much less often. This should
6938 speed startup, especially on directory caches.
6939 - Base64 decoding was actually showing up on our profile when parsing
6940 the initial descriptor file; switch to an in-process all-at-once
6941 implementation that's about 3.5x times faster than calling out to
6943 - Use a slightly simpler string hashing algorithm (copying Python's
6944 instead of Java's) and optimize our digest hashing algorithm to take
6945 advantage of 64-bit platforms and to remove some possibly-costly
6947 - When implementing AES counter mode, update only the portions of the
6948 counter buffer that need to change, and don't keep separate
6949 network-order and host-order counters on big-endian hosts (where
6951 - Add an in-place version of aes_crypt() so that we can avoid doing a
6952 needless memcpy() call on each cell payload.
6953 - Use Critical Sections rather than Mutexes for synchronizing threads
6954 on win32; Mutexes are heavier-weight, and designed for synchronizing
6957 o Performance improvements (bandwidth use):
6958 - Don't try to launch new descriptor downloads quite so often when we
6959 already have enough directory information to build circuits.
6960 - Version 1 directories are no longer generated in full. Instead,
6961 authorities generate and serve "stub" v1 directories that list
6962 no servers. This will stop Tor versions 0.1.0.x and earlier from
6963 working, but (for security reasons) nobody should be running those
6965 - Avoid going directly to the directory authorities even if you're a
6966 relay, if you haven't found yourself reachable yet or if you've
6967 decided not to advertise your dirport yet. Addresses bug 556.
6968 - If we've gone 12 hours since our last bandwidth check, and we
6969 estimate we have less than 50KB bandwidth capacity but we could
6970 handle more, do another bandwidth test.
6971 - Support "If-Modified-Since" when answering HTTP requests for
6972 directories, running-routers documents, and v2 and v3 networkstatus
6973 documents. (There's no need to support it for router descriptors,
6974 since those are downloaded by descriptor digest.)
6975 - Stop fetching directory info so aggressively if your DirPort is
6976 on but your ORPort is off; stop fetching v2 dir info entirely.
6977 You can override these choices with the new FetchDirInfoEarly
6980 o Changed config option behavior (features):
6981 - Configuration files now accept C-style strings as values. This
6982 helps encode characters not allowed in the current configuration
6983 file format, such as newline or #. Addresses bug 557.
6984 - Add hidden services and DNSPorts to the list of things that make
6985 Tor accept that it has running ports. Change starting Tor with no
6986 ports from a fatal error to a warning; we might change it back if
6987 this turns out to confuse anybody. Fixes bug 579.
6988 - Make PublishServerDescriptor default to 1, so the default doesn't
6989 have to change as we invent new directory protocol versions.
6990 - Allow people to say PreferTunnelledDirConns rather than
6991 PreferTunneledDirConns, for those alternate-spellers out there.
6992 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
6993 accommodate the growing number of servers that use the default
6994 and are reaching it.
6995 - Make it possible to enable HashedControlPassword and
6996 CookieAuthentication at the same time.
6997 - When a TrackHostExits-chosen exit fails too many times in a row,
6998 stop using it. Fixes bug 437.
7000 o Changed config option behavior (bugfixes):
7001 - Do not read the configuration file when we've only been told to
7002 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7003 based on patch from Sebastian Hahn.
7004 - Actually validate the options passed to AuthDirReject,
7005 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7006 - Make "ClientOnly 1" config option disable directory ports too.
7007 - Don't stop fetching descriptors when FetchUselessDescriptors is
7008 set, even if we stop asking for circuits. Bug reported by tup
7010 - Servers used to decline to publish their DirPort if their
7011 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
7012 they look only at BandwidthRate and RelayBandwidthRate.
7013 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
7014 minus 1 byte: the actual maximum declared bandwidth.
7015 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
7016 - Make the NodeFamilies config option work. (Reported by
7017 lodger -- it has never actually worked, even though we added it
7019 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
7020 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
7022 o New config options:
7023 - New configuration options AuthDirMaxServersPerAddr and
7024 AuthDirMaxServersperAuthAddr to override default maximum number
7025 of servers allowed on a single IP address. This is important for
7026 running a test network on a single host.
7027 - Three new config options (AlternateDirAuthority,
7028 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7029 user selectively replace the default directory authorities by type,
7030 rather than the all-or-nothing replacement that DirServer offers.
7031 - New config options AuthDirBadDir and AuthDirListBadDirs for
7032 authorities to mark certain relays as "bad directories" in the
7033 networkstatus documents. Also supports the "!baddir" directive in
7034 the approved-routers file.
7035 - New config option V2AuthoritativeDirectory that all v2 directory
7036 authorities must set. This lets v3 authorities choose not to serve
7037 v2 directory information.
7039 o Minor features (other):
7040 - When we're not serving v2 directory information, there is no reason
7041 to actually keep any around. Remove the obsolete files and directory
7042 on startup if they are very old and we aren't going to serve them.
7043 - When we negotiate a v2 link-layer connection (not yet implemented),
7044 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7045 negotiated a v1 connection for their next step. Initial steps for
7047 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7048 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7049 we can start out knowing some directory caches. We don't ship with
7050 a fallback consensus by default though, because it was making
7051 bootstrapping take too long while we tried many down relays.
7052 - Authorities send back an X-Descriptor-Not-New header in response to
7053 an accepted-but-discarded descriptor upload. Partially implements
7055 - If we find a cached-routers file that's been sitting around for more
7056 than 28 days unmodified, then most likely it's a leftover from
7057 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
7059 - When we (as a cache) download a descriptor because it was listed
7060 in a consensus, remember when the consensus was supposed to expire,
7061 and don't expire the descriptor until then.
7062 - Optionally (if built with -DEXPORTMALLINFO) export the output
7063 of mallinfo via http, as tor/mallinfo.txt. Only accessible
7065 - Tag every guard node in our state file with the version that
7066 we believe added it, or with our own version if we add it. This way,
7067 if a user temporarily runs an old version of Tor and then switches
7068 back to a new one, she doesn't automatically lose her guards.
7069 - When somebody requests a list of statuses or servers, and we have
7070 none of those, return a 404 rather than an empty 200.
7071 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
7073 - Add an HSAuthorityRecordStats option that hidden service authorities
7074 can use to track statistics of overall hidden service usage without
7075 logging information that would be as useful to an attacker.
7076 - Allow multiple HiddenServicePort directives with the same virtual
7077 port; when they occur, the user is sent round-robin to one
7078 of the target ports chosen at random. Partially fixes bug 393 by
7079 adding limited ad-hoc round-robining.
7080 - Revamp file-writing logic so we don't need to have the entire
7081 contents of a file in memory at once before we write to disk. Tor,
7084 o Minor bugfixes (other):
7085 - Alter the code that tries to recover from unhandled write
7086 errors, to not try to flush onto a socket that's given us
7088 - Directory mirrors no longer include a guess at the client's IP
7089 address if the connection appears to be coming from the same /24
7090 network; it was producing too many wrong guesses.
7091 - If we're trying to flush the last bytes on a connection (for
7092 example, when answering a directory request), reset the
7093 time-to-give-up timeout every time we manage to write something
7095 - Reject router descriptors with out-of-range bandwidthcapacity or
7096 bandwidthburst values.
7097 - If we can't expand our list of entry guards (e.g. because we're
7098 using bridges or we have StrictEntryNodes set), don't mark relays
7099 down when they fail a directory request. Otherwise we're too quick
7100 to mark all our entry points down.
7101 - Authorities no longer send back "400 you're unreachable please fix
7102 it" errors to Tor servers that aren't online all the time. We're
7103 supposed to tolerate these servers now.
7104 - Let directory authorities startup even when they can't generate
7105 a descriptor immediately, e.g. because they don't know their
7107 - Correctly enforce that elements of directory objects do not appear
7108 more often than they are allowed to appear.
7109 - Stop allowing hibernating servers to be "stable" or "fast".
7110 - On Windows, we were preventing other processes from reading
7111 cached-routers while Tor was running. (Reported by janbar)
7112 - Check return values from pthread_mutex functions.
7113 - When opening /dev/null in finish_daemonize(), do not pass the
7114 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
7115 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
7117 o Controller features:
7118 - The GETCONF command now escapes and quotes configuration values
7119 that don't otherwise fit into the torrc file.
7120 - The SETCONF command now handles quoted values correctly.
7121 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7122 ask about source, timestamp of arrival, purpose, etc. We need
7123 something like this to help Vidalia not do GeoIP lookups on bridge
7125 - Allow multiple HashedControlPassword config lines, to support
7126 multiple controller passwords.
7127 - Accept LF instead of CRLF on controller, since some software has a
7128 hard time generating real Internet newlines.
7129 - Add GETINFO values for the server status events
7130 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
7132 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
7133 GETINFO for Torstat to use until it can switch to using extrainfos.
7134 - New config option CookieAuthFile to choose a new location for the
7135 cookie authentication file, and config option
7136 CookieAuthFileGroupReadable to make it group-readable.
7137 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
7138 match requests to applications. Patch from Robert Hogan.
7139 - Add a RESOLVE command to launch hostname lookups. Original patch
7141 - Add GETINFO status/enough-dir-info to let controllers tell whether
7142 Tor has downloaded sufficient directory information. Patch from Tup.
7143 - You can now use the ControlSocket option to tell Tor to listen for
7144 controller connections on Unix domain sockets on systems that
7145 support them. Patch from Peter Palfrader.
7146 - New "GETINFO address-mappings/*" command to get address mappings
7147 with expiry information. "addr-mappings/*" is now deprecated.
7149 - Add a new config option __DisablePredictedCircuits designed for
7150 use by the controller, when we don't want Tor to build any circuits
7152 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
7153 so we can exit from the middle of the circuit.
7154 - Implement "getinfo status/circuit-established".
7155 - Implement "getinfo status/version/..." so a controller can tell
7156 whether the current version is recommended, and whether any versions
7157 are good, and how many authorities agree. Patch from "shibz".
7158 - Controllers should now specify cache=no or cache=yes when using
7159 the +POSTDESCRIPTOR command.
7160 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7161 Robert Hogan. Fixes the first part of bug 681.
7162 - When reporting clock skew, and we know that the clock is _at least
7163 as skewed_ as some value, but we don't know the actual value,
7164 report the value as a "minimum skew."
7166 o Controller bugfixes:
7167 - Generate "STATUS_SERVER" events rather than misspelled
7168 "STATUS_SEVER" events. Caught by mwenge.
7169 - Reject controller commands over 1MB in length, so rogue
7170 processes can't run us out of memory.
7171 - Change the behavior of "getinfo status/good-server-descriptor"
7172 so it doesn't return failure when any authority disappears.
7173 - Send NAMESERVER_STATUS messages for a single failed nameserver
7175 - When the DANGEROUS_VERSION controller status event told us we're
7176 running an obsolete version, it used the string "OLD" to describe
7177 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7178 "OBSOLETE" in both cases.
7179 - Respond to INT and TERM SIGNAL commands before we execute the
7180 signal, in case the signal shuts us down. We had a patch in
7181 0.1.2.1-alpha that tried to do this by queueing the response on
7182 the connection's buffer before shutting down, but that really
7183 isn't the same thing at all. Bug located by Matt Edman.
7184 - Provide DNS expiry times in GMT, not in local time. For backward
7185 compatibility, ADDRMAP events only provide GMT expiry in an extended
7186 field. "GETINFO address-mappings" always does the right thing.
7187 - Use CRLF line endings properly in NS events.
7188 - Make 'getinfo fingerprint' return a 551 error if we're not a
7189 server, so we match what the control spec claims we do. Reported
7191 - Fix a typo in an error message when extendcircuit fails that
7192 caused us to not follow the \r\n-based delimiter protocol. Reported
7194 - When tunneling an encrypted directory connection, and its first
7195 circuit fails, do not leave it unattached and ask the controller
7196 to deal. Fixes the second part of bug 681.
7197 - Treat some 403 responses from directory servers as INFO rather than
7198 WARN-severity events.
7200 o Portability / building / compiling:
7201 - When building with --enable-gcc-warnings, check for whether Apple's
7202 warning "-Wshorten-64-to-32" is available.
7203 - Support compilation to target iPhone; patch from cjacker huang.
7204 To build for iPhone, pass the --enable-iphone option to configure.
7205 - Port Tor to build and run correctly on Windows CE systems, using
7206 the wcecompat library. Contributed by Valerio Lupi.
7207 - Detect non-ASCII platforms (if any still exist) and refuse to
7208 build there: some of our code assumes that 'A' is 65 and so on.
7209 - Clear up some MIPSPro compiler warnings.
7210 - Make autoconf search for libevent, openssl, and zlib consistently.
7211 - Update deprecated macros in configure.in.
7212 - When warning about missing headers, tell the user to let us
7213 know if the compile succeeds anyway, so we can downgrade the
7215 - Include the current subversion revision as part of the version
7216 string: either fetch it directly if we're in an SVN checkout, do
7217 some magic to guess it if we're in an SVK checkout, or use
7218 the last-detected version if we're building from a .tar.gz.
7219 Use this version consistently in log messages.
7220 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
7221 - Read resolv.conf files correctly on platforms where read() returns
7222 partial results on small file reads.
7223 - Build without verbose warnings even on gcc 4.2 and 4.3.
7224 - On Windows, correctly detect errors when listing the contents of
7225 a directory. Fix from lodger.
7226 - Run 'make test' as part of 'make dist', so we stop releasing so
7227 many development snapshots that fail their unit tests.
7228 - Add support to detect Libevent versions in the 1.4.x series
7230 - Add command-line arguments to unit-test executable so that we can
7231 invoke any chosen test from the command line rather than having
7232 to run the whole test suite at once; and so that we can turn on
7233 logging for the unit tests.
7234 - Do not automatically run configure from autogen.sh. This
7235 non-standard behavior tended to annoy people who have built other
7237 - Fix a macro/CPP interaction that was confusing some compilers:
7238 some GCCs don't like #if/#endif pairs inside macro arguments.
7240 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7241 Fixes bug 704; fix from Steven Murdoch.
7242 - Correctly detect transparent proxy support on Linux hosts that
7243 require in.h to be included before netfilter_ipv4.h. Patch
7246 o Logging improvements:
7247 - When we haven't had any application requests lately, don't bother
7248 logging that we have expired a bunch of descriptors.
7249 - When attempting to open a logfile fails, tell us why.
7250 - Only log guard node status when guard node status has changed.
7251 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7252 make "INFO" 75% less verbose.
7253 - When SafeLogging is disabled, log addresses along with all TLS
7255 - Report TLS "zero return" case as a "clean close" and "IO error"
7256 as a "close". Stop calling closes "unexpected closes": existing
7257 Tors don't use SSL_close(), so having a connection close without
7258 the TLS shutdown handshake is hardly unexpected.
7259 - When we receive a consensus from the future, warn about skew.
7260 - Make "not enough dir info yet" warnings describe *why* Tor feels
7261 it doesn't have enough directory info yet.
7262 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7263 consumers. (We already do this on HUP.)
7264 - Give more descriptive well-formedness errors for out-of-range
7265 hidden service descriptor/protocol versions.
7266 - Stop recommending that every server operator send mail to tor-ops.
7267 Resolves bug 597. Bugfix on 0.1.2.x.
7268 - Improve skew reporting: try to give the user a better log message
7269 about how skewed they are, and how much this matters.
7270 - New --quiet command-line option to suppress the default console log.
7271 Good in combination with --hash-password.
7272 - Don't complain that "your server has not managed to confirm that its
7273 ports are reachable" if we haven't been able to build any circuits
7275 - Detect the reason for failing to mmap a descriptor file we just
7276 wrote, and give a more useful log message. Fixes bug 533.
7277 - Always prepend "Bug: " to any log message about a bug.
7278 - When dumping memory usage, list bytes used in buffer memory
7280 - When running with dmalloc, dump more stats on hup and on exit.
7281 - Put a platform string (e.g. "Linux i686") in the startup log
7282 message, so when people paste just their logs, we know if it's
7283 OpenBSD or Windows or what.
7284 - When logging memory usage, break down memory used in buffers by
7286 - When we are reporting the DirServer line we just parsed, we were
7287 logging the second stanza of the key fingerprint, not the first.
7288 - Even though Windows is equally happy with / and \ as path separators,
7289 try to use \ consistently on Windows and / consistently on Unix: it
7290 makes the log messages nicer.
7291 - On OSX, stop warning the user that kqueue support in libevent is
7292 "experimental", since it seems to have worked fine for ages.
7294 o Contributed scripts and tools:
7295 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7296 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7298 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
7299 Unix users an easy way to script their Tor process (e.g. by
7300 adjusting bandwidth based on the time of the day).
7301 - In the exitlist script, only consider the most recently published
7302 server descriptor for each server. Also, when the user requests
7303 a list of servers that _reject_ connections to a given address,
7304 explicitly exclude the IPs that also have servers that accept
7305 connections to that address. Resolves bug 405.
7306 - Include a new contrib/tor-exit-notice.html file that exit relay
7307 operators can put on their website to help reduce abuse queries.
7309 o Newly deprecated features:
7310 - The status/version/num-versioning and status/version/num-concurring
7311 GETINFO controller options are no longer useful in the v3 directory
7312 protocol: treat them as deprecated, and warn when they're used.
7313 - The RedirectExits config option is now deprecated.
7316 - Drop the old code to choke directory connections when the
7317 corresponding OR connections got full: thanks to the cell queue
7318 feature, OR conns don't get full any more.
7319 - Remove the old "dns worker" server DNS code: it hasn't been default
7320 since 0.1.2.2-alpha, and all the servers are using the new
7322 - Remove the code to generate the oldest (v1) directory format.
7323 - Remove support for the old bw_accounting file: we've been storing
7324 bandwidth accounting information in the state file since
7325 0.1.2.5-alpha. This may result in bandwidth accounting errors
7326 if you try to upgrade from 0.1.1.x or earlier, or if you try to
7327 downgrade to 0.1.1.x or earlier.
7328 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7329 it, it had no AES, and it hasn't seen any security patches since
7331 - Stop overloading the circuit_t.onionskin field for both "onionskin
7332 from a CREATE cell that we are waiting for a cpuworker to be
7333 assigned" and "onionskin from an EXTEND cell that we are going to
7334 send to an OR as soon as we are connected". Might help with bug 600.
7335 - Remove the tor_strpartition() function: its logic was confused,
7336 and it was only used for one thing that could be implemented far
7338 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
7339 and TorControl.py, as they use the old v0 controller protocol,
7340 and are obsoleted by TorFlow anyway.
7341 - Drop support for v1 rendezvous descriptors, since we never used
7342 them anyway, and the code has probably rotted by now. Based on
7343 patch from Karsten Loesing.
7344 - Stop allowing address masks that do not correspond to bit prefixes.
7345 We have warned about these for a really long time; now it's time
7346 to reject them. (Patch from croup.)
7347 - Remove an optimization in the AES counter-mode code that assumed
7348 that the counter never exceeded 2^68. When the counter can be set
7349 arbitrarily as an IV (as it is by Karsten's new hidden services
7350 code), this assumption no longer holds.
7351 - Disable the SETROUTERPURPOSE controller command: it is now
7355 Changes in version 0.1.2.19 - 2008-01-17
7356 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7357 exit policy a little bit more conservative so it's safer to run an
7358 exit relay on a home system, and fixes a variety of smaller issues.
7361 - Exit policies now reject connections that are addressed to a
7362 relay's public (external) IP address too, unless
7363 ExitPolicyRejectPrivate is turned off. We do this because too
7364 many relays are running nearby to services that trust them based
7368 - When the clock jumps forward a lot, do not allow the bandwidth
7369 buckets to become negative. Fixes bug 544.
7370 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7371 on every successful resolve. Reported by Mike Perry.
7372 - Purge old entries from the "rephist" database and the hidden
7373 service descriptor database even when DirPort is zero.
7374 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7375 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7376 crashing or mis-answering these requests.
7377 - When we decide to send a 503 response to a request for servers, do
7378 not then also send the server descriptors: this defeats the whole
7379 purpose. Fixes bug 539.
7382 - Changing the ExitPolicyRejectPrivate setting should cause us to
7383 rebuild our server descriptor.
7384 - Fix handling of hex nicknames when answering controller requests for
7385 networkstatus by name, or when deciding whether to warn about
7386 unknown routers in a config option. (Patch from mwenge.)
7387 - Fix a couple of hard-to-trigger autoconf problems that could result
7388 in really weird results on platforms whose sys/types.h files define
7389 nonstandard integer types.
7390 - Don't try to create the datadir when running --verify-config or
7391 --hash-password. Resolves bug 540.
7392 - If we were having problems getting a particular descriptor from the
7393 directory caches, and then we learned about a new descriptor for
7394 that router, we weren't resetting our failure count. Reported
7396 - Although we fixed bug 539 (where servers would send HTTP status 503
7397 responses _and_ send a body too), there are still servers out there
7398 that haven't upgraded. Therefore, make clients parse such bodies
7399 when they receive them.
7400 - Run correctly on systems where rlim_t is larger than unsigned long.
7401 This includes some 64-bit systems.
7402 - Run correctly on platforms (like some versions of OS X 10.5) where
7403 the real limit for number of open files is OPEN_FILES, not rlim_max
7404 from getrlimit(RLIMIT_NOFILES).
7405 - Avoid a spurious free on base64 failure.
7406 - Avoid segfaults on certain complex invocations of
7407 router_get_by_hexdigest().
7408 - Fix rare bug on REDIRECTSTREAM control command when called with no
7409 port set: it could erroneously report an error when none had
7413 Changes in version 0.1.2.18 - 2007-10-28
7414 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7415 hidden service introduction that were causing huge delays, and a big
7416 bug that was causing some servers to disappear from the network status
7417 lists for a few hours each day.
7419 o Major bugfixes (crashes):
7420 - If a connection is shut down abruptly because of something that
7421 happened inside connection_flushed_some(), do not call
7422 connection_finished_flushing(). Should fix bug 451:
7423 "connection_stop_writing: Assertion conn->write_event failed"
7424 Bugfix on 0.1.2.7-alpha.
7425 - Fix possible segfaults in functions called from
7426 rend_process_relay_cell().
7428 o Major bugfixes (hidden services):
7429 - Hidden services were choosing introduction points uniquely by
7430 hexdigest, but when constructing the hidden service descriptor
7431 they merely wrote the (potentially ambiguous) nickname.
7432 - Clients now use the v2 intro format for hidden service
7433 connections: they specify their chosen rendezvous point by identity
7434 digest rather than by (potentially ambiguous) nickname. These
7435 changes could speed up hidden service connections dramatically.
7437 o Major bugfixes (other):
7438 - Stop publishing a new server descriptor just because we get a
7439 HUP signal. This led (in a roundabout way) to some servers getting
7440 dropped from the networkstatus lists for a few hours each day.
7441 - When looking for a circuit to cannibalize, consider family as well
7442 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7443 circuit cannibalization).
7444 - When a router wasn't listed in a new networkstatus, we were leaving
7445 the flags for that router alone -- meaning it remained Named,
7446 Running, etc -- even though absence from the networkstatus means
7447 that it shouldn't be considered to exist at all anymore. Now we
7448 clear all the flags for routers that fall out of the networkstatus
7449 consensus. Fixes bug 529.
7452 - Don't try to access (or alter) the state file when running
7453 --list-fingerprint or --verify-config or --hash-password. Resolves
7455 - When generating information telling us how to extend to a given
7456 router, do not try to include the nickname if it is
7457 absent. Resolves bug 467.
7458 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7459 a way to trigger this remotely.)
7460 - When sending a status event to the controller telling it that an
7461 OR address is reachable, set the port correctly. (Previously we
7462 were reporting the dir port.)
7463 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7464 command. Bugfix on 0.1.2.17.
7465 - When loading bandwidth history, do not believe any information in
7466 the future. Fixes bug 434.
7467 - When loading entry guard information, do not believe any information
7469 - When we have our clock set far in the future and generate an
7470 onion key, then re-set our clock to be correct, we should not stop
7471 the onion key from getting rotated.
7472 - On some platforms, accept() can return a broken address. Detect
7473 this more quietly, and deal accordingly. Fixes bug 483.
7474 - It's not actually an error to find a non-pending entry in the DNS
7475 cache when canceling a pending resolve. Don't log unless stuff
7476 is fishy. Resolves bug 463.
7477 - Don't reset trusted dir server list when we set a configuration
7478 option. Patch from Robert Hogan.
7481 Changes in version 0.1.2.17 - 2007-08-30
7482 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
7483 X bundles. Vidalia 0.0.14 makes authentication required for the
7484 ControlPort in the default configuration, which addresses important
7485 security risks. Everybody who uses Vidalia (or another controller)
7488 In addition, this Tor update fixes major load balancing problems with
7489 path selection, which should speed things up a lot once many people
7492 o Major bugfixes (security):
7493 - We removed support for the old (v0) control protocol. It has been
7494 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
7495 become more of a headache than it's worth.
7497 o Major bugfixes (load balancing):
7498 - When choosing nodes for non-guard positions, weight guards
7499 proportionally less, since they already have enough load. Patch
7501 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7502 will allow fast Tor servers to get more attention.
7503 - When we're upgrading from an old Tor version, forget our current
7504 guards and pick new ones according to the new weightings. These
7505 three load balancing patches could raise effective network capacity
7506 by a factor of four. Thanks to Mike Perry for measurements.
7508 o Major bugfixes (stream expiration):
7509 - Expire not-yet-successful application streams in all cases if
7510 they've been around longer than SocksTimeout. Right now there are
7511 some cases where the stream will live forever, demanding a new
7512 circuit every 15 seconds. Fixes bug 454; reported by lodger.
7514 o Minor features (controller):
7515 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
7516 is valid before any authentication has been received. It tells
7517 a controller what kind of authentication is expected, and what
7518 protocol is spoken. Implements proposal 119.
7520 o Minor bugfixes (performance):
7521 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
7522 greatly speeding up loading cached-routers from disk on startup.
7523 - Disable sentinel-based debugging for buffer code: we squashed all
7524 the bugs that this was supposed to detect a long time ago, and now
7525 its only effect is to change our buffer sizes from nice powers of
7526 two (which platform mallocs tend to like) to values slightly over
7527 powers of two (which make some platform mallocs sad).
7529 o Minor bugfixes (misc):
7530 - If exit bandwidth ever exceeds one third of total bandwidth, then
7531 use the correct formula to weight exit nodes when choosing paths.
7532 Based on patch from Mike Perry.
7533 - Choose perfectly fairly among routers when choosing by bandwidth and
7534 weighting by fraction of bandwidth provided by exits. Previously, we
7535 would choose with only approximate fairness, and correct ourselves
7536 if we ran off the end of the list.
7537 - If we require CookieAuthentication but we fail to write the
7538 cookie file, we would warn but not exit, and end up in a state
7539 where no controller could authenticate. Now we exit.
7540 - If we require CookieAuthentication, stop generating a new cookie
7541 every time we change any piece of our config.
7542 - Refuse to start with certain directory authority keys, and
7543 encourage people using them to stop.
7544 - Terminate multi-line control events properly. Original patch
7546 - Fix a minor memory leak when we fail to find enough suitable
7547 servers to choose a circuit.
7548 - Stop leaking part of the descriptor when we run into a particularly
7549 unparseable piece of it.
7552 Changes in version 0.1.2.16 - 2007-08-01
7553 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
7554 remote attacker in certain situations to rewrite the user's torrc
7555 configuration file. This can completely compromise anonymity of users
7556 in most configurations, including those running the Vidalia bundles,
7557 TorK, etc. Or worse.
7559 o Major security fixes:
7560 - Close immediately after missing authentication on control port;
7561 do not allow multiple authentication attempts.
7564 Changes in version 0.1.2.15 - 2007-07-17
7565 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
7566 problems, fixes compilation on BSD, and fixes a variety of other
7567 bugs. Everybody should upgrade.
7569 o Major bugfixes (compilation):
7570 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
7572 o Major bugfixes (crashes):
7573 - Try even harder not to dereference the first character after
7574 an mmap(). Reported by lodger.
7575 - Fix a crash bug in directory authorities when we re-number the
7576 routerlist while inserting a new router.
7577 - When the cached-routers file is an even multiple of the page size,
7578 don't run off the end and crash. (Fixes bug 455; based on idea
7580 - Fix eventdns.c behavior on Solaris: It is critical to include
7581 orconfig.h _before_ sys/types.h, so that we can get the expected
7582 definition of _FILE_OFFSET_BITS.
7584 o Major bugfixes (security):
7585 - Fix a possible buffer overrun when using BSD natd support. Bug
7587 - When sending destroy cells from a circuit's origin, don't include
7588 the reason for tearing down the circuit. The spec says we didn't,
7589 and now we actually don't. Reported by lodger.
7590 - Keep streamids from different exits on a circuit separate. This
7591 bug may have allowed other routers on a given circuit to inject
7592 cells into streams. Reported by lodger; fixes bug 446.
7593 - If there's a never-before-connected-to guard node in our list,
7594 never choose any guards past it. This way we don't expand our
7595 guard list unless we need to.
7597 o Minor bugfixes (guard nodes):
7598 - Weight guard selection by bandwidth, so that low-bandwidth nodes
7599 don't get overused as guards.
7601 o Minor bugfixes (directory):
7602 - Correctly count the number of authorities that recommend each
7603 version. Previously, we were under-counting by 1.
7604 - Fix a potential crash bug when we load many server descriptors at
7605 once and some of them make others of them obsolete. Fixes bug 458.
7607 o Minor bugfixes (hidden services):
7608 - Stop tearing down the whole circuit when the user asks for a
7609 connection to a port that the hidden service didn't configure.
7612 o Minor bugfixes (misc):
7613 - On Windows, we were preventing other processes from reading
7614 cached-routers while Tor was running. Reported by janbar.
7615 - Fix a possible (but very unlikely) bug in picking routers by
7616 bandwidth. Add a log message to confirm that it is in fact
7617 unlikely. Patch from lodger.
7618 - Backport a couple of memory leak fixes.
7619 - Backport miscellaneous cosmetic bugfixes.
7622 Changes in version 0.1.2.14 - 2007-05-25
7623 Tor 0.1.2.14 changes the addresses of two directory authorities (this
7624 change especially affects those who serve or use hidden services),
7625 and fixes several other crash- and security-related bugs.
7627 o Directory authority changes:
7628 - Two directory authorities (moria1 and moria2) just moved to new
7629 IP addresses. This change will particularly affect those who serve
7630 or use hidden services.
7632 o Major bugfixes (crashes):
7633 - If a directory server runs out of space in the connection table
7634 as it's processing a begin_dir request, it will free the exit stream
7635 but leave it attached to the circuit, leading to unpredictable
7636 behavior. (Reported by seeess, fixes bug 425.)
7637 - Fix a bug in dirserv_remove_invalid() that would cause authorities
7638 to corrupt memory under some really unlikely scenarios.
7639 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
7640 - Avoid segfaults when reading from mmaped descriptor file. (Reported
7643 o Major bugfixes (security):
7644 - When choosing an entry guard for a circuit, avoid using guards
7645 that are in the same family as the chosen exit -- not just guards
7646 that are exactly the chosen exit. (Reported by lodger.)
7648 o Major bugfixes (resource management):
7649 - If a directory authority is down, skip it when deciding where to get
7650 networkstatus objects or descriptors. Otherwise we keep asking
7651 every 10 seconds forever. Fixes bug 384.
7652 - Count it as a failure if we fetch a valid network-status but we
7653 don't want to keep it. Otherwise we'll keep fetching it and keep
7654 not wanting to keep it. Fixes part of bug 422.
7655 - If all of our dirservers have given us bad or no networkstatuses
7656 lately, then stop hammering them once per minute even when we
7657 think they're failed. Fixes another part of bug 422.
7660 - Actually set the purpose correctly for descriptors inserted with
7662 - When we have k non-v2 authorities in our DirServer config,
7663 we ignored the last k authorities in the list when updating our
7665 - Correctly back-off from requesting router descriptors that we are
7666 having a hard time downloading.
7667 - Read resolv.conf files correctly on platforms where read() returns
7668 partial results on small file reads.
7669 - Don't rebuild the entire router store every time we get 32K of
7670 routers: rebuild it when the journal gets very large, or when
7671 the gaps in the store get very large.
7674 - When routers publish SVN revisions in their router descriptors,
7675 authorities now include those versions correctly in networkstatus
7677 - Warn when using a version of libevent before 1.3b to run a server on
7678 OSX or BSD: these versions interact badly with userspace threads.
7681 Changes in version 0.1.2.13 - 2007-04-24
7682 This release features some major anonymity fixes, such as safer path
7683 selection; better client performance; faster bootstrapping, better
7684 address detection, and better DNS support for servers; write limiting as
7685 well as read limiting to make servers easier to run; and a huge pile of
7686 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
7688 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
7689 of the Freenode IRC network, remembering his patience and vision for
7690 free speech on the Internet.
7692 o Major features, client performance:
7693 - Weight directory requests by advertised bandwidth. Now we can
7694 let servers enable write limiting but still allow most clients to
7695 succeed at their directory requests. (We still ignore weights when
7696 choosing a directory authority; I hope this is a feature.)
7697 - Stop overloading exit nodes -- avoid choosing them for entry or
7698 middle hops when the total bandwidth available from non-exit nodes
7699 is much higher than the total bandwidth available from exit nodes.
7700 - Rather than waiting a fixed amount of time between retrying
7701 application connections, we wait only 10 seconds for the first,
7702 10 seconds for the second, and 15 seconds for each retry after
7703 that. Hopefully this will improve the expected user experience.
7704 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7705 to open a stream fails; now we do in more cases. This should
7706 make clients able to find a good exit faster in some cases, since
7707 unhandleable requests will now get an error rather than timing out.
7709 o Major features, client functionality:
7710 - Implement BEGIN_DIR cells, so we can connect to a directory
7711 server via TLS to do encrypted directory requests rather than
7712 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
7713 config options if you like. For now, this feature only works if
7714 you already have a descriptor for the destination dirserver.
7715 - Add support for transparent application connections: this basically
7716 bundles the functionality of trans-proxy-tor into the Tor
7717 mainline. Now hosts with compliant pf/netfilter implementations
7718 can redirect TCP connections straight to Tor without diverting
7719 through SOCKS. (Based on patch from tup.)
7720 - Add support for using natd; this allows FreeBSDs earlier than
7721 5.1.2 to have ipfw send connections through Tor without using
7722 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7724 o Major features, servers:
7725 - Setting up a dyndns name for your server is now optional: servers
7726 with no hostname or IP address will learn their IP address by
7727 asking the directory authorities. This code only kicks in when you
7728 would normally have exited with a "no address" error. Nothing's
7729 authenticated, so use with care.
7730 - Directory servers now spool server descriptors, v1 directories,
7731 and v2 networkstatus objects to buffers as needed rather than en
7732 masse. They also mmap the cached-routers files. These steps save
7734 - Stop requiring clients to have well-formed certificates, and stop
7735 checking nicknames in certificates. (Clients have certificates so
7736 that they can look like Tor servers, but in the future we might want
7737 to allow them to look like regular TLS clients instead. Nicknames
7738 in certificates serve no purpose other than making our protocol
7739 easier to recognize on the wire.) Implements proposal 106.
7741 o Improvements on DNS support:
7742 - Add "eventdns" asynchronous dns library originally based on code
7743 from Adam Langley. Now we can discard the old rickety dnsworker
7744 concept, and support a wider variety of DNS functions. Allows
7745 multithreaded builds on NetBSD and OpenBSD again.
7746 - Add server-side support for "reverse" DNS lookups (using PTR
7747 records so clients can determine the canonical hostname for a given
7748 IPv4 address). Only supported by servers using eventdns; servers
7749 now announce in their descriptors if they don't support eventdns.
7750 - Workaround for name servers (like Earthlink's) that hijack failing
7751 DNS requests and replace the no-such-server answer with a "helpful"
7752 redirect to an advertising-driven search portal. Also work around
7753 DNS hijackers who "helpfully" decline to hijack known-invalid
7754 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
7755 lets you turn it off.
7756 - Servers now check for the case when common DNS requests are going to
7757 wildcarded addresses (i.e. all getting the same answer), and change
7758 their exit policy to reject *:* if it's happening.
7759 - When asked to resolve a hostname, don't use non-exit servers unless
7760 requested to do so. This allows servers with broken DNS to be
7761 useful to the network.
7762 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
7763 useless IPv6 DNS resolves.
7764 - Specify and implement client-side SOCKS5 interface for reverse DNS
7765 lookups (see doc/socks-extensions.txt). Also cache them.
7766 - When we change nameservers or IP addresses, reset and re-launch
7767 our tests for DNS hijacking.
7769 o Improvements on reachability testing:
7770 - Servers send out a burst of long-range padding cells once they've
7771 established that they're reachable. Spread them over 4 circuits,
7772 so hopefully a few will be fast. This exercises bandwidth and
7773 bootstraps them into the directory more quickly.
7774 - When we find our DirPort to be reachable, publish a new descriptor
7775 so we'll tell the world (reported by pnx).
7776 - Directory authorities now only decide that routers are reachable
7777 if their identity keys are as expected.
7778 - Do DirPort reachability tests less often, since a single test
7779 chews through many circuits before giving up.
7780 - Avoid some false positives during reachability testing: don't try
7781 to test via a server that's on the same /24 network as us.
7782 - Start publishing one minute or so after we find our ORPort
7783 to be reachable. This will help reduce the number of descriptors
7784 we have for ourselves floating around, since it's quite likely
7785 other things (e.g. DirPort) will change during that minute too.
7786 - Routers no longer try to rebuild long-term connections to directory
7787 authorities, and directory authorities no longer try to rebuild
7788 long-term connections to all servers. We still don't hang up
7789 connections in these two cases though -- we need to look at it
7790 more carefully to avoid flapping, and we likely need to wait til
7791 0.1.1.x is obsolete.
7793 o Improvements on rate limiting:
7794 - Enable write limiting as well as read limiting. Now we sacrifice
7795 capacity if we're pushing out lots of directory traffic, rather
7796 than overrunning the user's intended bandwidth limits.
7797 - Include TLS overhead when counting bandwidth usage; previously, we
7798 would count only the bytes sent over TLS, but not the bytes used
7800 - Servers decline directory requests much more aggressively when
7801 they're low on bandwidth. Otherwise they end up queueing more and
7802 more directory responses, which can't be good for latency.
7803 - But never refuse directory requests from local addresses.
7804 - Be willing to read or write on local connections (e.g. controller
7805 connections) even when the global rate limiting buckets are empty.
7806 - Flush local controller connection buffers periodically as we're
7807 writing to them, so we avoid queueing 4+ megabytes of data before
7809 - Revise and clean up the torrc.sample that we ship with; add
7810 a section for BandwidthRate and BandwidthBurst.
7812 o Major features, NT services:
7813 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
7814 command-line flag so that admins can override the default by saying
7815 "tor --service install --user "SomeUser"". This will not affect
7816 existing installed services. Also, warn the user that the service
7817 will look for its configuration file in the service user's
7818 %appdata% directory. (We can't do the "hardwire the user's appdata
7819 directory" trick any more, since we may not have read access to that
7821 - Support running the Tor service with a torrc not in the same
7822 directory as tor.exe and default to using the torrc located in
7823 the %appdata%\Tor\ of the user who installed the service. Patch
7825 - Add an --ignore-missing-torrc command-line option so that we can
7826 get the "use sensible defaults if the configuration file doesn't
7827 exist" behavior even when specifying a torrc location on the
7829 - When stopping an NT service, wait up to 10 sec for it to actually
7830 stop. (Patch from Matt Edman; resolves bug 295.)
7832 o Directory authority improvements:
7833 - Stop letting hibernating or obsolete servers affect uptime and
7835 - Stop listing hibernating servers in the v1 directory.
7836 - Authorities no longer recommend exits as guards if this would shift
7837 too much load to the exit nodes.
7838 - Authorities now specify server versions in networkstatus. This adds
7839 about 2% to the size of compressed networkstatus docs, and allows
7840 clients to tell which servers support BEGIN_DIR and which don't.
7841 The implementation is forward-compatible with a proposed future
7842 protocol version scheme not tied to Tor versions.
7843 - DirServer configuration lines now have an orport= option so
7844 clients can open encrypted tunnels to the authorities without
7845 having downloaded their descriptors yet. Enabled for moria1,
7846 moria2, tor26, and lefkada now in the default configuration.
7847 - Add a BadDirectory flag to network status docs so that authorities
7848 can (eventually) tell clients about caches they believe to be
7849 broken. Not used yet.
7850 - Allow authorities to list nodes as bad exits in their
7851 approved-routers file by fingerprint or by address. If most
7852 authorities set a BadExit flag for a server, clients don't think
7853 of it as a general-purpose exit. Clients only consider authorities
7854 that advertise themselves as listing bad exits.
7855 - Patch from Steve Hildrey: Generate network status correctly on
7856 non-versioning dirservers.
7857 - Have directory authorities allow larger amounts of drift in uptime
7858 without replacing the server descriptor: previously, a server that
7859 restarted every 30 minutes could have 48 "interesting" descriptors
7861 - Reserve the nickname "Unnamed" for routers that can't pick
7862 a hostname: any router can call itself Unnamed; directory
7863 authorities will never allocate Unnamed to any particular router;
7864 clients won't believe that any router is the canonical Unnamed.
7866 o Directory mirrors and clients:
7867 - Discard any v1 directory info that's over 1 month old (for
7868 directories) or over 1 week old (for running-routers lists).
7869 - Clients track responses with status 503 from dirservers. After a
7870 dirserver has given us a 503, we try not to use it until an hour has
7871 gone by, or until we have no dirservers that haven't given us a 503.
7872 - When we get a 503 from a directory, and we're not a server, we no
7873 longer count the failure against the total number of failures
7874 allowed for the object we're trying to download.
7875 - Prepare for servers to publish descriptors less often: never
7876 discard a descriptor simply for being too old until either it is
7877 recommended by no authorities, or until we get a better one for
7878 the same router. Make caches consider retaining old recommended
7879 routers for even longer.
7880 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7881 headers for content, so that we can work better in the presence of
7882 caching HTTP proxies.
7883 - Stop fetching descriptors if you're not a dir mirror and you
7884 haven't tried to establish any circuits lately. (This currently
7885 causes some dangerous behavior, because when you start up again
7886 you'll use your ancient server descriptors.)
7888 o Major fixes, crashes:
7889 - Stop crashing when the controller asks us to resetconf more than
7890 one config option at once. (Vidalia 0.0.11 does this.)
7891 - Fix a longstanding obscure crash bug that could occur when we run
7892 out of DNS worker processes, if we're not using eventdns. (Resolves
7894 - Fix an assert that could trigger if a controller quickly set then
7895 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
7896 - Avoid crash when telling controller about stream-status and a
7898 - Avoid sending junk to controllers or segfaulting when a controller
7899 uses EVENT_NEW_DESC with verbose nicknames.
7900 - Stop triggering asserts if the controller tries to extend hidden
7901 service circuits (reported by mwenge).
7902 - If we start a server with ClientOnly 1, then set ClientOnly to 0
7903 and hup, stop triggering an assert based on an empty onion_key.
7904 - Mask out all signals in sub-threads; only the libevent signal
7905 handler should be processing them. This should prevent some crashes
7906 on some machines using pthreads. (Patch from coderman.)
7907 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
7909 o Major fixes, anonymity/security:
7910 - Automatically avoid picking more than one node from the same
7911 /16 network when constructing a circuit. Add an
7912 "EnforceDistinctSubnets" option to let people disable it if they
7913 want to operate private test networks on a single subnet.
7914 - When generating bandwidth history, round down to the nearest
7915 1k. When storing accounting data, round up to the nearest 1k.
7916 - When we're running as a server, remember when we last rotated onion
7917 keys, so that we will rotate keys once they're a week old even if
7918 we never stay up for a week ourselves.
7919 - If a client asked for a server by name, and there's a named server
7920 in our network-status but we don't have its descriptor yet, we
7921 could return an unnamed server instead.
7922 - Reject (most) attempts to use Tor circuits with length one. (If
7923 many people start using Tor as a one-hop proxy, exit nodes become
7924 a more attractive target for compromise.)
7925 - Just because your DirPort is open doesn't mean people should be
7926 able to remotely teach you about hidden service descriptors. Now
7927 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7928 - Fix a potential race condition in the rpm installer. Found by
7930 - Do not log IPs with TLS failures for incoming TLS
7931 connections. (Fixes bug 382.)
7933 o Major fixes, other:
7934 - If our system clock jumps back in time, don't publish a negative
7935 uptime in the descriptor.
7936 - When we start during an accounting interval before it's time to wake
7937 up, remember to wake up at the correct time. (May fix bug 342.)
7938 - Previously, we would cache up to 16 old networkstatus documents
7939 indefinitely, if they came from nontrusted authorities. Now we
7940 discard them if they are more than 10 days old.
7941 - When we have a state file we cannot parse, tell the user and
7942 move it aside. Now we avoid situations where the user starts
7943 Tor in 1904, Tor writes a state file with that timestamp in it,
7944 the user fixes her clock, and Tor refuses to start.
7945 - Publish a new descriptor after we hup/reload. This is important
7946 if our config has changed such that we'll want to start advertising
7947 our DirPort now, etc.
7948 - If we are using an exit enclave and we can't connect, e.g. because
7949 its webserver is misconfigured to not listen on localhost, then
7950 back off and try connecting from somewhere else before we fail.
7952 o New config options or behaviors:
7953 - When EntryNodes are configured, rebuild the guard list to contain,
7954 in order: the EntryNodes that were guards before; the rest of the
7955 EntryNodes; the nodes that were guards before.
7956 - Do not warn when individual nodes in the configuration's EntryNodes,
7957 ExitNodes, etc are down: warn only when all possible nodes
7958 are down. (Fixes bug 348.)
7959 - Put a lower-bound on MaxAdvertisedBandwidth.
7960 - Start using the state file to store bandwidth accounting data:
7961 the bw_accounting file is now obsolete. We'll keep generating it
7962 for a while for people who are still using 0.1.2.4-alpha.
7963 - Try to batch changes to the state file so that we do as few
7964 disk writes as possible while still storing important things in
7966 - The state file and the bw_accounting file get saved less often when
7967 the AvoidDiskWrites config option is set.
7968 - Make PIDFile work on Windows.
7969 - Add internal descriptions for a bunch of configuration options:
7970 accessible via controller interface and in comments in saved
7972 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7973 NNTP by default, so this seems like a sensible addition.
7974 - Clients now reject hostnames with invalid characters. This should
7975 avoid some inadvertent info leaks. Add an option
7976 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7977 is running a private network with hosts called @, !, and #.
7978 - Check for addresses with invalid characters at the exit as well,
7979 and warn less verbosely when they fail. You can override this by
7980 setting ServerDNSAllowNonRFC953Addresses to 1.
7981 - Remove some options that have been deprecated since at least
7982 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7983 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7984 to set log options. Mark PathlenCoinWeight as obsolete.
7985 - Stop accepting certain malformed ports in configured exit policies.
7986 - When the user uses bad syntax in the Log config line, stop
7987 suggesting other bad syntax as a replacement.
7988 - Add new config option "ResolvConf" to let the server operator
7989 choose an alternate resolve.conf file when using eventdns.
7990 - If one of our entry guards is on the ExcludeNodes list, or the
7991 directory authorities don't think it's a good guard, treat it as
7992 if it were unlisted: stop using it as a guard, and throw it off
7993 the guards list if it stays that way for a long time.
7994 - Allow directory authorities to be marked separately as authorities
7995 for the v1 directory protocol, the v2 directory protocol, and
7996 as hidden service directories, to make it easier to retire old
7997 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7998 to continue being hidden service authorities too.
7999 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
8000 - Make TrackExitHosts case-insensitive, and fix the behavior of
8001 ".suffix" TrackExitHosts items to avoid matching in the middle of
8003 - New DirPort behavior: if you have your dirport set, you download
8004 descriptors aggressively like a directory mirror, whether or not
8008 - Create a new file ReleaseNotes which was the old ChangeLog. The
8009 new ChangeLog file now includes the notes for all development
8011 - Add a new address-spec.txt document to describe our special-case
8012 addresses: .exit, .onion, and .noconnnect.
8013 - Fork the v1 directory protocol into its own spec document,
8014 and mark dir-spec.txt as the currently correct (v2) spec.
8016 o Packaging, porting, and contrib
8017 - "tor --verify-config" now exits with -1(255) or 0 depending on
8018 whether the config options are bad or good.
8019 - The Debian package now uses --verify-config when (re)starting,
8020 to distinguish configuration errors from other errors.
8021 - Adapt a patch from goodell to let the contrib/exitlist script
8022 take arguments rather than require direct editing.
8023 - Prevent the contrib/exitlist script from printing the same
8024 result more than once.
8025 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
8026 - In the hidden service example in torrc.sample, stop recommending
8027 esoteric and discouraged hidden service options.
8028 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
8029 values before failing, and always enables eventdns.
8030 - Try to detect Windows correctly when cross-compiling.
8031 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
8032 Try to fix this in configure.in by checking for most functions
8033 before we check for libevent.
8034 - Update RPMs to require libevent 1.2.
8035 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
8036 or later. Log when we are doing this, so we can diagnose it when
8037 it fails. (Also, recommend libevent 1.1b for kqueue and
8038 win32 methods; deprecate libevent 1.0b harder; make libevent
8039 recommendation system saner.)
8040 - Build with recent (1.3+) libevents on platforms that do not
8041 define the nonstandard types "u_int8_t" and friends.
8042 - Remove architecture from OS X builds. The official builds are
8043 now universal binaries.
8044 - Run correctly on OS X platforms with case-sensitive filesystems.
8045 - Correctly set maximum connection limit on Cygwin. (This time
8047 - Start compiling on MinGW on Windows (patches from Mike Chiussi
8049 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
8050 - Finally fix the openssl warnings from newer gccs that believe that
8051 ignoring a return value is okay, but casting a return value and
8052 then ignoring it is a sign of madness.
8053 - On architectures where sizeof(int)>4, still clamp declarable
8054 bandwidth to INT32_MAX.
8056 o Minor features, controller:
8057 - Warn the user when an application uses the obsolete binary v0
8058 control protocol. We're planning to remove support for it during
8059 the next development series, so it's good to give people some
8061 - Add STREAM_BW events to report per-entry-stream bandwidth
8062 use. (Patch from Robert Hogan.)
8063 - Rate-limit SIGNEWNYM signals in response to controllers that
8064 impolitely generate them for every single stream. (Patch from
8065 mwenge; closes bug 394.)
8066 - Add a REMAP status to stream events to note that a stream's
8067 address has changed because of a cached address or a MapAddress
8069 - Make REMAP stream events have a SOURCE (cache or exit), and
8070 make them generated in every case where we get a successful
8071 connected or resolved cell.
8072 - Track reasons for OR connection failure; make these reasons
8073 available via the controller interface. (Patch from Mike Perry.)
8074 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
8075 can learn when clients are sending malformed hostnames to Tor.
8076 - Specify and implement some of the controller status events.
8077 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
8078 - Reimplement GETINFO so that info/names stays in sync with the
8080 - Implement "GETINFO fingerprint".
8081 - Implement "SETEVENTS GUARD" so controllers can get updates on
8082 entry guard status as it changes.
8083 - Make all connections to addresses of the form ".noconnect"
8084 immediately get closed. This lets application/controller combos
8085 successfully test whether they're talking to the same Tor by
8086 watching for STREAM events.
8087 - Add a REASON field to CIRC events; for backward compatibility, this
8088 field is sent only to controllers that have enabled the extended
8089 event format. Also, add additional reason codes to explain why
8090 a given circuit has been destroyed or truncated. (Patches from
8092 - Add a REMOTE_REASON field to extended CIRC events to tell the
8093 controller why a remote OR told us to close a circuit.
8094 - Stream events also now have REASON and REMOTE_REASON fields,
8095 working much like those for circuit events.
8096 - There's now a GETINFO ns/... field so that controllers can ask Tor
8097 about the current status of a router.
8098 - A new event type "NS" to inform a controller when our opinion of
8099 a router's status has changed.
8100 - Add a GETINFO events/names and GETINFO features/names so controllers
8101 can tell which events and features are supported.
8102 - A new CLEARDNSCACHE signal to allow controllers to clear the
8103 client-side DNS cache without expiring circuits.
8104 - Fix CIRC controller events so that controllers can learn the
8105 identity digests of non-Named servers used in circuit paths.
8106 - Let controllers ask for more useful identifiers for servers. Instead
8107 of learning identity digests for un-Named servers and nicknames
8108 for Named servers, the new identifiers include digest, nickname,
8109 and indication of Named status. Off by default; see control-spec.txt
8110 for more information.
8111 - Add a "getinfo address" controller command so it can display Tor's
8112 best guess to the user.
8113 - New controller event to alert the controller when our server
8114 descriptor has changed.
8115 - Give more meaningful errors on controller authentication failure.
8116 - Export the default exit policy via the control port, so controllers
8117 don't need to guess what it is / will be later.
8119 o Minor bugfixes, controller:
8120 - When creating a circuit via the controller, send a 'launched'
8121 event when we're done, so we follow the spec better.
8122 - Correct the control spec to match how the code actually responds
8123 to 'getinfo addr-mappings/*'. Reported by daejees.
8124 - The control spec described a GUARDS event, but the code
8125 implemented a GUARD event. Standardize on GUARD, but let people
8126 ask for GUARDS too. Reported by daejees.
8127 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
8128 clear the corresponding on_circuit variable, and remember later
8129 that we don't need to send a redundant CLOSED event. (Resolves part
8131 - Report events where a resolve succeeded or where we got a socks
8132 protocol error correctly, rather than calling both of them
8134 - Change reported stream target addresses to IP consistently when
8135 we finally get the IP from an exit node.
8136 - Send log messages to the controller even if they happen to be very
8138 - Flush ERR-level controller status events just like we currently
8139 flush ERR-level log events, so that a Tor shutdown doesn't prevent
8140 the controller from learning about current events.
8141 - Report the circuit number correctly in STREAM CLOSED events. Bug
8142 reported by Mike Perry.
8143 - Do not report bizarre values for results of accounting GETINFOs
8144 when the last second's write or read exceeds the allotted bandwidth.
8145 - Report "unrecognized key" rather than an empty string when the
8146 controller tries to fetch a networkstatus that doesn't exist.
8147 - When the controller does a "GETINFO network-status", tell it
8148 about even those routers whose descriptors are very old, and use
8149 long nicknames where appropriate.
8150 - Fix handling of verbose nicknames with ORCONN controller events:
8151 make them show up exactly when requested, rather than exactly when
8153 - Controller signals now work on non-Unix platforms that don't define
8154 SIGUSR1 and SIGUSR2 the way we expect.
8155 - Respond to SIGNAL command before we execute the signal, in case
8156 the signal shuts us down. Suggested by Karsten Loesing.
8157 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
8159 o Minor features, code performance:
8160 - Major performance improvement on inserting descriptors: change
8161 algorithm from O(n^2) to O(n).
8162 - Do not rotate onion key immediately after setting it for the first
8164 - Call router_have_min_dir_info half as often. (This is showing up in
8165 some profiles, but not others.)
8166 - When using GCC, make log_debug never get called at all, and its
8167 arguments never get evaluated, when no debug logs are configured.
8168 (This is showing up in some profiles, but not others.)
8169 - Statistics dumped by -USR2 now include a breakdown of public key
8170 operations, for profiling.
8171 - Make the common memory allocation path faster on machines where
8172 malloc(0) returns a pointer.
8173 - Split circuit_t into origin_circuit_t and or_circuit_t, and
8174 split connection_t into edge, or, dir, control, and base structs.
8175 These will save quite a bit of memory on busy servers, and they'll
8176 also help us track down bugs in the code and bugs in the spec.
8177 - Use OpenSSL's AES implementation on platforms where it's faster.
8178 This could save us as much as 10% CPU usage.
8180 o Minor features, descriptors and descriptor handling:
8181 - Avoid duplicate entries on MyFamily line in server descriptor.
8182 - When Tor receives a router descriptor that it asked for, but
8183 no longer wants (because it has received fresh networkstatuses
8184 in the meantime), do not warn the user. Cache the descriptor if
8185 we're a cache; drop it if we aren't.
8186 - Servers no longer ever list themselves in their "family" line,
8187 even if configured to do so. This makes it easier to configure
8188 family lists conveniently.
8190 o Minor fixes, confusing/misleading log messages:
8191 - Display correct results when reporting which versions are
8192 recommended, and how recommended they are. (Resolves bug 383.)
8193 - Inform the server operator when we decide not to advertise a
8194 DirPort due to AccountingMax enabled or a low BandwidthRate.
8195 - Only include function names in log messages for info/debug messages.
8196 For notice/warn/err, the content of the message should be clear on
8197 its own, and printing the function name only confuses users.
8198 - Remove even more protocol-related warnings from Tor server logs,
8199 such as bad TLS handshakes and malformed begin cells.
8200 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
8201 when the IP address is mapped through MapAddress to a hostname.
8202 - Fix misleading log messages: an entry guard that is "unlisted",
8203 as well as not known to be "down" (because we've never heard
8204 of it), is not therefore "up".
8206 o Minor fixes, old/obsolete behavior:
8207 - Start assuming we can use a create_fast cell if we don't know
8208 what version a router is running.
8209 - We no longer look for identity and onion keys in "identity.key" and
8210 "onion.key" -- these were replaced by secret_id_key and
8211 secret_onion_key in 0.0.8pre1.
8212 - We no longer require unrecognized directory entries to be
8214 - Drop compatibility with obsolete Tors that permit create cells
8215 to have the wrong circ_id_type.
8216 - Remove code to special-case "-cvs" ending, since it has not
8217 actually mattered since 0.0.9.
8218 - Don't re-write the fingerprint file every restart, unless it has
8221 o Minor fixes, misc client-side behavior:
8222 - Always remove expired routers and networkstatus docs before checking
8223 whether we have enough information to build circuits. (Fixes
8225 - When computing clock skew from directory HTTP headers, consider what
8226 time it was when we finished asking for the directory, not what
8228 - Make our socks5 handling more robust to broken socks clients:
8229 throw out everything waiting on the buffer in between socks
8230 handshake phases, since they can't possibly (so the theory
8231 goes) have predicted what we plan to respond to them.
8232 - Expire socks connections if they spend too long waiting for the
8233 handshake to finish. Previously we would let them sit around for
8234 days, if the connecting application didn't close them either.
8235 - And if the socks handshake hasn't started, don't send a
8236 "DNS resolve socks failed" handshake reply; just close it.
8237 - If the user asks to use invalid exit nodes, be willing to use
8239 - Track unreachable entry guards correctly: don't conflate
8240 'unreachable by us right now' with 'listed as down by the directory
8241 authorities'. With the old code, if a guard was unreachable by us
8242 but listed as running, it would clog our guard list forever.
8243 - Behave correctly in case we ever have a network with more than
8244 2GB/s total advertised capacity.
8245 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
8246 - Fix a memory leak when we ask for "all" networkstatuses and we
8247 get one we don't recognize.
8250 Changes in version 0.1.1.26 - 2006-12-14
8251 o Security bugfixes:
8252 - Stop sending the HttpProxyAuthenticator string to directory
8253 servers when directory connections are tunnelled through Tor.
8254 - Clients no longer store bandwidth history in the state file.
8255 - Do not log introduction points for hidden services if SafeLogging
8259 - Fix an assert failure when a directory authority sets
8260 AuthDirRejectUnlisted and then receives a descriptor from an
8261 unlisted router (reported by seeess).
8264 Changes in version 0.1.1.25 - 2006-11-04
8266 - When a client asks us to resolve (rather than connect to)
8267 an address, and we have a cached answer, give them the cached
8268 answer. Previously, we would give them no answer at all.
8269 - We were building exactly the wrong circuits when we predict
8270 hidden service requirements, meaning Tor would have to build all
8271 its circuits on demand.
8272 - If none of our live entry guards have a high uptime, but we
8273 require a guard with a high uptime, try adding a new guard before
8274 we give up on the requirement. This patch should make long-lived
8275 connections more stable on average.
8276 - When testing reachability of our DirPort, don't launch new
8277 tests when there's already one in progress -- unreachable
8278 servers were stacking up dozens of testing streams.
8280 o Security bugfixes:
8281 - When the user sends a NEWNYM signal, clear the client-side DNS
8282 cache too. Otherwise we continue to act on previous information.
8285 - Avoid a memory corruption bug when creating a hash table for
8287 - Avoid possibility of controller-triggered crash when misusing
8288 certain commands from a v0 controller on platforms that do not
8289 handle printf("%s",NULL) gracefully.
8290 - Avoid infinite loop on unexpected controller input.
8291 - Don't log spurious warnings when we see a circuit close reason we
8292 don't recognize; it's probably just from a newer version of Tor.
8293 - Add Vidalia to the OS X uninstaller script, so when we uninstall
8294 Tor/Privoxy we also uninstall Vidalia.
8297 Changes in version 0.1.1.24 - 2006-09-29
8299 - Allow really slow clients to not hang up five minutes into their
8300 directory downloads (suggested by Adam J. Richter).
8301 - Fix major performance regression from 0.1.0.x: instead of checking
8302 whether we have enough directory information every time we want to
8303 do something, only check when the directory information has changed.
8304 This should improve client CPU usage by 25-50%.
8305 - Don't crash if, after a server has been running for a while,
8306 it can't resolve its hostname.
8307 - When a client asks us to resolve (not connect to) an address,
8308 and we have a cached answer, give them the cached answer.
8309 Previously, we would give them no answer at all.
8312 - Allow Tor to start when RunAsDaemon is set but no logs are set.
8313 - Don't crash when the controller receives a third argument to an
8314 "extendcircuit" request.
8315 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
8316 response; fix error code when "getinfo dir/status/" fails.
8317 - Fix configure.in to not produce broken configure files with
8318 more recent versions of autoconf. Thanks to Clint for his auto*
8320 - Fix security bug on NetBSD that could allow someone to force
8321 uninitialized RAM to be sent to a server's DNS resolver. This
8322 only affects NetBSD and other platforms that do not bounds-check
8324 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
8325 methods: these are known to be buggy.
8326 - If we're a directory mirror and we ask for "all" network status
8327 documents, we would discard status documents from authorities
8331 Changes in version 0.1.1.23 - 2006-07-30
8333 - Fast Tor servers, especially exit nodes, were triggering asserts
8334 due to a bug in handling the list of pending DNS resolves. Some
8335 bugs still remain here; we're hunting them.
8336 - Entry guards could crash clients by sending unexpected input.
8337 - More fixes on reachability testing: if you find yourself reachable,
8338 then don't ever make any client requests (so you stop predicting
8339 circuits), then hup or have your clock jump, then later your IP
8340 changes, you won't think circuits are working, so you won't try to
8341 test reachability, so you won't publish.
8344 - Avoid a crash if the controller does a resetconf firewallports
8345 and then a setconf fascistfirewall=1.
8346 - Avoid an integer underflow when the dir authority decides whether
8347 a router is stable: we might wrongly label it stable, and compute
8348 a slightly wrong median stability, when a descriptor is published
8350 - Fix a place where we might trigger an assert if we can't build our
8351 own server descriptor yet.
8354 Changes in version 0.1.1.22 - 2006-07-05
8356 - Fix a big bug that was causing servers to not find themselves
8357 reachable if they changed IP addresses. Since only 0.1.1.22+
8358 servers can do reachability testing correctly, now we automatically
8359 make sure to test via one of these.
8360 - Fix to allow clients and mirrors to learn directory info from
8361 descriptor downloads that get cut off partway through.
8362 - Directory authorities had a bug in deciding if a newly published
8363 descriptor was novel enough to make everybody want a copy -- a few
8364 servers seem to be publishing new descriptors many times a minute.
8366 - Fix a rare bug that was causing some servers to complain about
8367 "closing wedged cpuworkers" and skip some circuit create requests.
8368 - Make the Exit flag in directory status documents actually work.
8371 Changes in version 0.1.1.21 - 2006-06-10
8372 o Crash and assert fixes from 0.1.1.20:
8373 - Fix a rare crash on Tor servers that have enabled hibernation.
8374 - Fix a seg fault on startup for Tor networks that use only one
8375 directory authority.
8376 - Fix an assert from a race condition that occurs on Tor servers
8377 while exiting, where various threads are trying to log that they're
8378 exiting, and delete the logs, at the same time.
8379 - Make our unit tests pass again on certain obscure platforms.
8382 - Add support for building SUSE RPM packages.
8383 - Speed up initial bootstrapping for clients: if we are making our
8384 first ever connection to any entry guard, then don't mark it down
8386 - When only one Tor server in the network is labelled as a guard,
8387 and we've already picked him, we would cycle endlessly picking him
8388 again, being unhappy about it, etc. Now we specifically exclude
8389 current guards when picking a new guard.
8390 - Servers send create cells more reliably after the TLS connection
8391 is established: we were sometimes forgetting to send half of them
8392 when we had more than one pending.
8393 - If we get a create cell that asks us to extend somewhere, but the
8394 Tor server there doesn't match the expected digest, we now send
8395 a destroy cell back, rather than silently doing nothing.
8396 - Make options->RedirectExit work again.
8397 - Make cookie authentication for the controller work again.
8398 - Stop being picky about unusual characters in the arguments to
8399 mapaddress. It's none of our business.
8400 - Add a new config option "TestVia" that lets you specify preferred
8401 middle hops to use for test circuits. Perhaps this will let me
8402 debug the reachability problems better.
8404 o Log / documentation fixes:
8405 - If we're a server and some peer has a broken TLS certificate, don't
8406 log about it unless ProtocolWarnings is set, i.e., we want to hear
8407 about protocol violations by others.
8408 - Fix spelling of VirtualAddrNetwork in man page.
8409 - Add a better explanation at the top of the autogenerated torrc file
8410 about what happened to our old torrc.
8413 Changes in version 0.1.1.20 - 2006-05-23
8414 o Crash and assert fixes from 0.1.0.17:
8415 - Fix assert bug in close_logs() on exit: when we close and delete
8416 logs, remove them all from the global "logfiles" list.
8417 - Fix an assert error when we're out of space in the connection_list
8418 and we try to post a hidden service descriptor (reported by Peter
8420 - Fix a rare assert error when we've tried all intro points for
8421 a hidden service and we try fetching the service descriptor again:
8422 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
8423 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
8424 out and refuse the setconf if it would fail.
8425 - If you specify a relative torrc path and you set RunAsDaemon in
8426 your torrc, then it chdir()'s to the new directory. If you then
8427 HUP, it tries to load the new torrc location, fails, and exits.
8428 The fix: no longer allow a relative path to torrc when using -f.
8429 - Check for integer overflows in more places, when adding elements
8430 to smartlists. This could possibly prevent a buffer overflow
8431 on malicious huge inputs.
8433 o Security fixes, major:
8434 - When we're printing strings from the network, don't try to print
8435 non-printable characters. Now we're safer against shell escape
8436 sequence exploits, and also against attacks to fool users into
8437 misreading their logs.
8438 - Implement entry guards: automatically choose a handful of entry
8439 nodes and stick with them for all circuits. Only pick new guards
8440 when the ones you have are unsuitable, and if the old guards
8441 become suitable again, switch back. This will increase security
8442 dramatically against certain end-point attacks. The EntryNodes
8443 config option now provides some hints about which entry guards you
8444 want to use most; and StrictEntryNodes means to only use those.
8445 Fixes CVE-2006-0414.
8446 - Implement exit enclaves: if we know an IP address for the
8447 destination, and there's a running Tor server at that address
8448 which allows exit to the destination, then extend the circuit to
8449 that exit first. This provides end-to-end encryption and end-to-end
8450 authentication. Also, if the user wants a .exit address or enclave,
8451 use 4 hops rather than 3, and cannibalize a general circ for it
8453 - Obey our firewall options more faithfully:
8454 . If we can't get to a dirserver directly, try going via Tor.
8455 . Don't ever try to connect (as a client) to a place our
8456 firewall options forbid.
8457 . If we specify a proxy and also firewall options, obey the
8458 firewall options even when we're using the proxy: some proxies
8459 can only proxy to certain destinations.
8460 - Make clients regenerate their keys when their IP address changes.
8461 - For the OS X package's modified privoxy config file, comment
8462 out the "logfile" line so we don't log everything passed
8464 - Our TLS handshakes were generating a single public/private
8465 keypair for the TLS context, rather than making a new one for
8466 each new connection. Oops. (But we were still rotating them
8467 periodically, so it's not so bad.)
8468 - When we were cannibalizing a circuit with a particular exit
8469 node in mind, we weren't checking to see if that exit node was
8470 already present earlier in the circuit. Now we are.
8471 - Require server descriptors to list IPv4 addresses -- hostnames
8472 are no longer allowed. This also fixes potential vulnerabilities
8473 to servers providing hostnames as their address and then
8474 preferentially resolving them so they can partition users.
8475 - Our logic to decide if the OR we connected to was the right guy
8476 was brittle and maybe open to a mitm for invalid routers.
8478 o Security fixes, minor:
8479 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
8480 Ian Goldberg can prove things about our handshake protocol more
8482 - Make directory authorities generate a separate "guard" flag to
8483 mean "would make a good entry guard". Clients now honor the
8484 is_guard flag rather than looking at is_fast or is_stable.
8485 - Try to list MyFamily elements by key, not by nickname, and warn
8486 if we've not heard of a server.
8487 - Start using RAND_bytes rather than RAND_pseudo_bytes from
8488 OpenSSL. Also, reseed our entropy every hour, not just at
8489 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
8490 - Refuse server descriptors where the fingerprint line doesn't match
8491 the included identity key. Tor doesn't care, but other apps (and
8492 humans) might actually be trusting the fingerprint line.
8493 - We used to kill the circuit when we receive a relay command we
8494 don't recognize. Now we just drop that cell.
8495 - Fix a bug found by Lasse Overlier: when we were making internal
8496 circuits (intended to be cannibalized later for rendezvous and
8497 introduction circuits), we were picking them so that they had
8498 useful exit nodes. There was no need for this, and it actually
8499 aids some statistical attacks.
8500 - Start treating internal circuits and exit circuits separately.
8501 It's important to keep them separate because internal circuits
8502 have their last hops picked like middle hops, rather than like
8503 exit hops. So exiting on them will break the user's expectations.
8504 - Fix a possible way to DoS dirservers.
8505 - When the client asked for a rendezvous port that the hidden
8506 service didn't want to provide, we were sending an IP address
8507 back along with the end cell. Fortunately, it was zero. But stop
8510 o Packaging improvements:
8511 - Implement --with-libevent-dir option to ./configure. Improve
8512 search techniques to find libevent, and use those for openssl too.
8513 - Fix a couple of bugs in OpenSSL detection. Deal better when
8514 there are multiple SSLs installed with different versions.
8515 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
8516 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
8518 - Make unit tests (and other invocations that aren't the real Tor)
8519 run without launching listeners, creating subdirectories, and so on.
8520 - The OS X installer was adding a symlink for tor_resolve but
8521 the binary was called tor-resolve (reported by Thomas Hardly).
8522 - Now we can target arch and OS in rpm builds (contributed by
8523 Phobos). Also make the resulting dist-rpm filename match the
8525 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8526 if you log to syslog and want something other than LOG_DAEMON.
8527 - Fix the torify (tsocks) config file to not use Tor for localhost
8529 - Start shipping socks-extensions.txt, tor-doc-unix.html,
8530 tor-doc-server.html, and stylesheet.css in the tarball.
8531 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
8532 They are useless now.
8533 - Add Peter Palfrader's contributed check-tor script. It lets you
8534 easily check whether a given server (referenced by nickname)
8535 is reachable by you.
8536 - Add BSD-style contributed startup script "rc.subr" from Peter
8539 o Directory improvements -- new directory protocol:
8540 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
8541 - Authorities and caches publish individual descriptors (by
8542 digest, by fingerprint, by "all", and by "tell me yours").
8543 - Clients don't download or use the old directory anymore. Now they
8544 download network-statuses from the directory authorities, and
8545 fetch individual server descriptors as needed from mirrors.
8546 - Clients don't download descriptors of non-running servers.
8547 - Download descriptors by digest, not by fingerprint. Caches try to
8548 download all listed digests from authorities; clients try to
8549 download "best" digests from caches. This avoids partitioning
8550 and isolating attacks better.
8551 - Only upload a new server descriptor when options change, 18
8552 hours have passed, uptime is reset, or bandwidth changes a lot.
8553 - Directory authorities silently throw away new descriptors that
8554 haven't changed much if the timestamps are similar. We do this to
8555 tolerate older Tor servers that upload a new descriptor every 15
8556 minutes. (It seemed like a good idea at the time.)
8557 - Clients choose directory servers from the network status lists,
8558 not from their internal list of router descriptors. Now they can
8559 go to caches directly rather than needing to go to authorities
8560 to bootstrap the first set of descriptors.
8561 - When picking a random directory, prefer non-authorities if any
8563 - Add a new flag to network-status indicating whether the server
8564 can answer v2 directory requests too.
8565 - Directory mirrors now cache up to 16 unrecognized network-status
8566 docs, so new directory authorities will be cached too.
8567 - Stop parsing, storing, or using running-routers output (but
8568 mirrors still cache and serve it).
8569 - Clients consider a threshold of "versioning" directory authorities
8570 before deciding whether to warn the user that he's obsolete.
8571 - Authorities publish separate sorted lists of recommended versions
8572 for clients and for servers.
8573 - Change DirServers config line to note which dirs are v1 authorities.
8574 - Put nicknames on the DirServer line, so we can refer to them
8575 without requiring all our users to memorize their IP addresses.
8576 - Remove option when getting directory cache to see whether they
8577 support running-routers; they all do now. Replace it with one
8578 to see whether caches support v2 stuff.
8579 - Stop listing down or invalid nodes in the v1 directory. This
8580 reduces its bulk by about 1/3, and reduces load on mirrors.
8581 - Mirrors no longer cache the v1 directory as often.
8582 - If we as a directory mirror don't know of any v1 directory
8583 authorities, then don't try to cache any v1 directories.
8585 o Other directory improvements:
8586 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
8587 fifth authoritative directory servers.
8588 - Directory authorities no longer require an open connection from
8589 a server to consider him "reachable". We need this change because
8590 when we add new directory authorities, old servers won't know not
8592 - Dir authorities now do their own external reachability testing
8593 of each server, and only list as running the ones they found to
8594 be reachable. We also send back warnings to the server's logs if
8595 it uploads a descriptor that we already believe is unreachable.
8596 - Spread the directory authorities' reachability testing over the
8597 entire testing interval, so we don't try to do 500 TLS's at once
8599 - Make the "stable" router flag in network-status be the median of
8600 the uptimes of running valid servers, and make clients pay
8601 attention to the network-status flags. Thus the cutoff adapts
8602 to the stability of the network as a whole, making IRC, IM, etc
8603 connections more reliable.
8604 - Make the v2 dir's "Fast" flag based on relative capacity, just
8605 like "Stable" is based on median uptime. Name everything in the
8606 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
8607 - Retry directory requests if we fail to get an answer we like
8608 from a given dirserver (we were retrying before, but only if
8609 we fail to connect).
8610 - Return a robots.txt on our dirport to discourage google indexing.
8612 o Controller protocol improvements:
8613 - Revised controller protocol (version 1) that uses ascii rather
8614 than binary: tor/doc/control-spec.txt. Add supporting libraries
8615 in python and java and c# so you can use the controller from your
8616 applications without caring how our protocol works.
8617 - Allow the DEBUG controller event to work again. Mark certain log
8618 entries as "don't tell this to controllers", so we avoid cycles.
8619 - New controller function "getinfo accounting", to ask how
8620 many bytes we've used in this time period.
8621 - Add a "resetconf" command so you can set config options like
8622 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
8623 a config option in the torrc with no value, then it clears it
8624 entirely (rather than setting it to its default).
8625 - Add a "getinfo config-file" to tell us where torrc is. Also
8626 expose guard nodes, config options/names.
8627 - Add a "quit" command (when when using the controller manually).
8628 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
8629 stop using any currently-dirty circuits for new streams, so we
8630 don't link new actions to old actions. This also occurs on HUP
8632 - If we would close a stream early (e.g. it asks for a .exit that
8633 we know would refuse it) but the LeaveStreamsUnattached config
8634 option is set by the controller, then don't close it.
8635 - Add a new controller event type "authdir_newdescs" that allows
8636 controllers to get all server descriptors that were uploaded to
8637 a router in its role as directory authority.
8638 - New controller option "getinfo desc/all-recent" to fetch the
8639 latest server descriptor for every router that Tor knows about.
8640 - Fix the controller's "attachstream 0" command to treat conn like
8641 it just connected, doing address remapping, handling .exit and
8642 .onion idioms, and so on. Now we're more uniform in making sure
8643 that the controller hears about new and closing connections.
8644 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
8645 the controller. Also, rotate dns and cpu workers if the controller
8646 changes options that will affect them; and initialize the dns
8647 worker cache tree whether or not we start out as a server.
8648 - Add a new circuit purpose 'controller' to let the controller ask
8649 for a circuit that Tor won't try to use. Extend the "extendcircuit"
8650 controller command to let you specify the purpose if you're starting
8651 a new circuit. Add a new "setcircuitpurpose" controller command to
8652 let you change a circuit's purpose after it's been created.
8653 - Let the controller ask for "getinfo dir/server/foo" so it can ask
8654 directly rather than connecting to the dir port. "getinfo
8655 dir/status/foo" also works, but currently only if your DirPort
8657 - Let the controller tell us about certain router descriptors
8658 that it doesn't want Tor to use in circuits. Implement
8659 "setrouterpurpose" and modify "+postdescriptor" to do this.
8660 - If the controller's *setconf commands fail, collect an error
8661 message in a string and hand it back to the controller -- don't
8662 just tell them to go read their logs.
8664 o Scalability, resource management, and performance:
8665 - Fix a major load balance bug: we were round-robin reading in 16 KB
8666 chunks, and servers with bandwidthrate of 20 KB, while downloading
8667 a 600 KB directory, would starve their other connections. Now we
8668 try to be a bit more fair.
8669 - Be more conservative about whether to advertise our DirPort.
8670 The main change is to not advertise if we're running at capacity
8671 and either a) we could hibernate ever or b) our capacity is low
8672 and we're using a default DirPort.
8673 - We weren't cannibalizing circuits correctly for
8674 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
8675 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
8676 build those from scratch. This should make hidden services faster.
8677 - Predict required circuits better, with an eye toward making hidden
8678 services faster on the service end.
8679 - Compress exit policies even more: look for duplicate lines and
8681 - Generate 18.0.0.0/8 address policy format in descs when we can;
8682 warn when the mask is not reducible to a bit-prefix.
8683 - There used to be two ways to specify your listening ports in a
8684 server descriptor: on the "router" line and with a separate "ports"
8685 line. Remove support for the "ports" line.
8686 - Reduce memory requirements in our structs by changing the order
8687 of fields. Replace balanced trees with hash tables. Inline
8688 bottleneck smartlist functions. Add a "Map from digest to void*"
8689 abstraction so we can do less hex encoding/decoding, and use it
8690 in router_get_by_digest(). Many other CPU and memory improvements.
8691 - Allow tor_gzip_uncompress to extract as much as possible from
8692 truncated compressed data. Try to extract as many
8693 descriptors as possible from truncated http responses (when
8694 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
8695 - Make circ->onionskin a pointer, not a static array. moria2 was using
8696 125000 circuit_t's after it had been up for a few weeks, which
8697 translates to 20+ megs of wasted space.
8698 - The private half of our EDH handshake keys are now chosen out
8699 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
8700 - Stop doing the complex voodoo overkill checking for insecure
8701 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8702 - Do round-robin writes for TLS of at most 16 kB per write. This
8703 might be more fair on loaded Tor servers.
8704 - Do not use unaligned memory access on alpha, mips, or mipsel.
8705 It *works*, but is very slow, so we treat them as if it doesn't.
8707 o Other bugfixes and improvements:
8708 - Start storing useful information to $DATADIR/state, so we can
8709 remember things across invocations of Tor. Retain unrecognized
8710 lines so we can be forward-compatible, and write a TorVersion line
8711 so we can be backward-compatible.
8712 - If ORPort is set, Address is not explicitly set, and our hostname
8713 resolves to a private IP address, try to use an interface address
8714 if it has a public address. Now Windows machines that think of
8715 themselves as localhost can guess their address.
8716 - Regenerate our local descriptor if it's dirty and we try to use
8717 it locally (e.g. if it changes during reachability detection).
8718 This was causing some Tor servers to keep publishing the same
8719 initial descriptor forever.
8720 - Tor servers with dynamic IP addresses were needing to wait 18
8721 hours before they could start doing reachability testing using
8722 the new IP address and ports. This is because they were using
8723 the internal descriptor to learn what to test, yet they were only
8724 rebuilding the descriptor once they decided they were reachable.
8725 - It turns out we couldn't bootstrap a network since we added
8726 reachability detection in 0.1.0.1-rc. Good thing the Tor network
8727 has never gone down. Add an AssumeReachable config option to let
8728 servers and authorities bootstrap. When we're trying to build a
8729 high-uptime or high-bandwidth circuit but there aren't enough
8730 suitable servers, try being less picky rather than simply failing.
8731 - Newly bootstrapped Tor networks couldn't establish hidden service
8732 circuits until they had nodes with high uptime. Be more tolerant.
8733 - Really busy servers were keeping enough circuits open on stable
8734 connections that they were wrapping around the circuit_id
8735 space. (It's only two bytes.) This exposed a bug where we would
8736 feel free to reuse a circuit_id even if it still exists but has
8737 been marked for close. Try to fix this bug. Some bug remains.
8738 - When we fail to bind or listen on an incoming or outgoing
8739 socket, we now close it before refusing, rather than just
8740 leaking it. (Thanks to Peter Palfrader for finding.)
8741 - Fix a file descriptor leak in start_daemon().
8742 - On Windows, you can't always reopen a port right after you've
8743 closed it. So change retry_listeners() to only close and re-open
8744 ports that have changed.
8745 - Workaround a problem with some http proxies that refuse GET
8746 requests that specify "Content-Length: 0". Reported by Adrian.
8747 - Recover better from TCP connections to Tor servers that are
8748 broken but don't tell you (it happens!); and rotate TLS
8749 connections once a week.
8750 - Fix a scary-looking but apparently harmless bug where circuits
8751 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
8752 servers, and never switch to state CIRCUIT_STATE_OPEN.
8753 - Check for even more Windows version flags when writing the platform
8754 string in server descriptors, and note any we don't recognize.
8755 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8756 get a better idea of why their circuits failed. Not used yet.
8757 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
8758 We don't use them yet, but maybe one day our DNS resolver will be
8759 able to discover them.
8760 - Let people type "tor --install" as well as "tor -install" when they
8761 want to make it an NT service.
8762 - Looks like we were never delivering deflated (i.e. compressed)
8763 running-routers lists, even when asked. Oops.
8764 - We were leaking some memory every time the client changed IPs.
8765 - Clean up more of the OpenSSL memory when exiting, so we can detect
8766 memory leaks better.
8767 - Never call free() on tor_malloc()d memory. This will help us
8768 use dmalloc to detect memory leaks.
8769 - Some Tor servers process billions of cells per day. These
8770 statistics are now uint64_t's.
8771 - Check [X-]Forwarded-For headers in HTTP requests when generating
8772 log messages. This lets people run dirservers (and caches) behind
8773 Apache but still know which IP addresses are causing warnings.
8774 - Fix minor integer overflow in calculating when we expect to use up
8775 our bandwidth allocation before hibernating.
8776 - Lower the minimum required number of file descriptors to 1000,
8777 so we can have some overhead for Valgrind on Linux, where the
8778 default ulimit -n is 1024.
8779 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
8780 and its existence is confusing some users.
8782 o Config option fixes:
8783 - Add a new config option ExitPolicyRejectPrivate which defaults
8784 to on. Now all exit policies will begin with rejecting private
8785 addresses, unless the server operator explicitly turns it off.
8786 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
8787 - Add new ReachableORAddresses and ReachableDirAddresses options
8788 that understand address policies. FascistFirewall is now a synonym
8789 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
8790 - Start calling it FooListenAddress rather than FooBindAddress,
8791 since few of our users know what it means to bind an address
8793 - If the user gave Tor an odd number of command-line arguments,
8794 we were silently ignoring the last one. Now we complain and fail.
8795 This wins the oldest-bug prize -- this bug has been present since
8796 November 2002, as released in Tor 0.0.0.
8797 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
8798 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
8799 it would silently ignore the 6668.
8800 - If we get a linelist or linelist_s config option from the torrc,
8801 e.g. ExitPolicy, and it has no value, warn and skip rather than
8802 silently resetting it to its default.
8803 - Setconf was appending items to linelists, not clearing them.
8804 - Add MyFamily to torrc.sample in the server section, so operators
8805 will be more likely to learn that it exists.
8806 - Make ContactInfo mandatory for authoritative directory servers.
8807 - MaxConn has been obsolete for a while now. Document the ConnLimit
8808 config option, which is a *minimum* number of file descriptors
8809 that must be available else Tor refuses to start.
8810 - Get rid of IgnoreVersion undocumented config option, and make us
8811 only warn, never exit, when we're running an obsolete version.
8812 - Make MonthlyAccountingStart config option truly obsolete now.
8813 - Correct the man page entry on TrackHostExitsExpire.
8814 - Let directory authorities start even if they don't specify an
8815 Address config option.
8816 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
8817 reflect the updated flags in our v2 dir protocol.
8819 o Config option features:
8820 - Add a new config option FastFirstHopPK (on by default) so clients
8821 do a trivial crypto handshake for their first hop, since TLS has
8822 already taken care of confidentiality and authentication.
8823 - Let the user set ControlListenAddress in the torrc. This can be
8824 dangerous, but there are some cases (like a secured LAN) where it
8826 - New config options to help controllers: FetchServerDescriptors
8827 and FetchHidServDescriptors for whether to fetch server
8828 info and hidserv info or let the controller do it, and
8829 PublishServerDescriptor and PublishHidServDescriptors.
8830 - Also let the controller set the __AllDirActionsPrivate config
8831 option if you want all directory fetches/publishes to happen via
8832 Tor (it assumes your controller bootstraps your circuits).
8833 - Add "HardwareAccel" config option: support for crypto hardware
8834 accelerators via OpenSSL. Off by default, until we find somebody
8835 smart who can test it for us. (It appears to produce seg faults
8836 in at least some cases.)
8837 - New config option "AuthDirRejectUnlisted" for directory authorities
8838 as a panic button: if we get flooded with unusable servers we can
8839 revert to only listing servers in the approved-routers file.
8840 - Directory authorities can now reject/invalidate by key and IP,
8841 with the config options "AuthDirInvalid" and "AuthDirReject", or
8842 by marking a fingerprint as "!reject" or "!invalid" (as its
8843 nickname) in the approved-routers file. This is useful since
8844 currently we automatically list servers as running and usable
8845 even if we know they're jerks.
8846 - Add a new config option TestSocks so people can see whether their
8847 applications are using socks4, socks4a, socks5-with-ip, or
8848 socks5-with-fqdn. This way they don't have to keep mucking
8849 with tcpdump and wondering if something got cached somewhere.
8850 - Add "private:*" as an alias in configuration for policies. Now
8851 you can simplify your exit policy rather than needing to list
8852 every single internal or nonroutable network space.
8853 - Accept "private:*" in routerdesc exit policies; not generated yet
8854 because older Tors do not understand it.
8855 - Add configuration option "V1AuthoritativeDirectory 1" which
8856 moria1, moria2, and tor26 have set.
8857 - Implement an option, VirtualAddrMask, to set which addresses
8858 get handed out in response to mapaddress requests. This works
8859 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8860 - Add a new config option FetchUselessDescriptors, off by default,
8861 for when you plan to run "exitlist" on your client and you want
8862 to know about even the non-running descriptors.
8863 - SocksTimeout: How long do we let a socks connection wait
8864 unattached before we fail it?
8865 - CircuitBuildTimeout: Cull non-open circuits that were born
8866 at least this many seconds ago.
8867 - CircuitIdleTimeout: Cull open clean circuits that were born
8868 at least this many seconds ago.
8869 - New config option SafeSocks to reject all application connections
8870 using unsafe socks protocols. Defaults to off.
8872 o Improved and clearer log messages:
8873 - Reduce clutter in server logs. We're going to try to make
8874 them actually usable now. New config option ProtocolWarnings that
8875 lets you hear about how _other Tors_ are breaking the protocol. Off
8877 - Divide log messages into logging domains. Once we put some sort
8878 of interface on this, it will let people looking at more verbose
8879 log levels specify the topics they want to hear more about.
8880 - Log server fingerprint on startup, so new server operators don't
8881 have to go hunting around their filesystem for it.
8882 - Provide dire warnings to any users who set DirServer manually;
8883 move it out of torrc.sample and into torrc.complete.
8884 - Make the log message less scary when all the dirservers are
8885 temporarily unreachable.
8886 - When tor_socketpair() fails in Windows, give a reasonable
8887 Windows-style errno back.
8888 - Improve tor_gettimeofday() granularity on windows.
8889 - We were printing the number of idle dns workers incorrectly when
8891 - Handle duplicate lines in approved-routers files without warning.
8892 - We were whining about using socks4 or socks5-with-local-lookup
8893 even when it's an IP address in the "virtual" range we designed
8894 exactly for this case.
8895 - Check for named servers when looking them up by nickname;
8896 warn when we're calling a non-named server by its nickname;
8897 don't warn twice about the same name.
8898 - Downgrade the dirserver log messages when whining about
8900 - Correct "your server is reachable" log entries to indicate that
8901 it was self-testing that told us so.
8902 - If we're trying to be a Tor server and running Windows 95/98/ME
8903 as a server, explain that we'll likely crash.
8904 - Provide a more useful warn message when our onion queue gets full:
8905 the CPU is too slow or the exit policy is too liberal.
8906 - Don't warn when we receive a 503 from a dirserver/cache -- this
8907 will pave the way for them being able to refuse if they're busy.
8908 - When we fail to bind a listener, try to provide a more useful
8909 log message: e.g., "Is Tor already running?"
8910 - Only start testing reachability once we've established a
8911 circuit. This will make startup on dir authorities less noisy.
8912 - Don't try to upload hidden service descriptors until we have
8913 established a circuit.
8914 - Tor didn't warn when it failed to open a log file.
8915 - Warn when listening on a public address for socks. We suspect a
8916 lot of people are setting themselves up as open socks proxies,
8917 and they have no idea that jerks on the Internet are using them,
8918 since they simply proxy the traffic into the Tor network.
8919 - Give a useful message when people run Tor as the wrong user,
8920 rather than telling them to start chowning random directories.
8921 - Fix a harmless bug that was causing Tor servers to log
8922 "Got an end because of misc error, but we're not an AP. Closing."
8923 - Fix wrong log message when you add a "HiddenServiceNodes" config
8924 line without any HiddenServiceDir line (reported by Chris Thomas).
8925 - Directory authorities now stop whining so loudly about bad
8926 descriptors that they fetch from other dirservers. So when there's
8927 a log complaint, it's for sure from a freshly uploaded descriptor.
8928 - When logging via syslog, include the pid whenever we provide
8929 a log entry. Suggested by Todd Fries.
8930 - When we're shutting down and we do something like try to post a
8931 server descriptor or rendezvous descriptor, don't complain that
8932 we seem to be unreachable. Of course we are, we're shutting down.
8933 - Change log line for unreachability to explicitly suggest /etc/hosts
8934 as the culprit. Also make it clearer what IP address and ports we're
8935 testing for reachability.
8936 - Put quotes around user-supplied strings when logging so users are
8937 more likely to realize if they add bad characters (like quotes)
8939 - NT service patch from Matt Edman to improve error messages on Win32.
8942 Changes in version 0.1.0.17 - 2006-02-17
8943 o Crash bugfixes on 0.1.0.x:
8944 - When servers with a non-zero DirPort came out of hibernation,
8945 sometimes they would trigger an assert.
8947 o Other important bugfixes:
8948 - On platforms that don't have getrlimit (like Windows), we were
8949 artificially constraining ourselves to a max of 1024
8950 connections. Now just assume that we can handle as many as 15000
8951 connections. Hopefully this won't cause other problems.
8953 o Backported features:
8954 - When we're a server, a client asks for an old-style directory,
8955 and our write bucket is empty, don't give it to him. This way
8956 small servers can continue to serve the directory *sometimes*,
8957 without getting overloaded.
8958 - Whenever you get a 503 in response to a directory fetch, try
8959 once more. This will become important once servers start sending
8960 503's whenever they feel busy.
8961 - Fetch a new directory every 120 minutes, not every 40 minutes.
8962 Now that we have hundreds of thousands of users running the old
8963 directory algorithm, it's starting to hurt a lot.
8964 - Bump up the period for forcing a hidden service descriptor upload
8965 from 20 minutes to 1 hour.
8968 Changes in version 0.1.0.16 - 2006-01-02
8969 o Crash bugfixes on 0.1.0.x:
8970 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8971 corrupting the heap, losing FDs, or crashing when we need to resize
8972 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8973 - It turns out sparc64 platforms crash on unaligned memory access
8974 too -- so detect and avoid this.
8975 - Handle truncated compressed data correctly (by detecting it and
8977 - Fix possible-but-unlikely free(NULL) in control.c.
8978 - When we were closing connections, there was a rare case that
8979 stomped on memory, triggering seg faults and asserts.
8980 - Avoid potential infinite recursion when building a descriptor. (We
8981 don't know that it ever happened, but better to fix it anyway.)
8982 - We were neglecting to unlink marked circuits from soon-to-close OR
8983 connections, which caused some rare scribbling on freed memory.
8984 - Fix a memory stomping race bug when closing the joining point of two
8985 rendezvous circuits.
8986 - Fix an assert in time parsing found by Steven Murdoch.
8988 o Other bugfixes on 0.1.0.x:
8989 - When we're doing reachability testing, provide more useful log
8990 messages so the operator knows what to expect.
8991 - Do not check whether DirPort is reachable when we are suppressing
8992 advertising it because of hibernation.
8993 - When building with -static or on Solaris, we sometimes needed -ldl.
8994 - One of the dirservers (tor26) changed its IP address.
8995 - When we're deciding whether a stream has enough circuits around
8996 that can handle it, count the freshly dirty ones and not the ones
8997 that are so dirty they won't be able to handle it.
8998 - When we're expiring old circuits, we had a logic error that caused
8999 us to close new rendezvous circuits rather than old ones.
9000 - Give a more helpful log message when you try to change ORPort via
9001 the controller: you should upgrade Tor if you want that to work.
9002 - We were failing to parse Tor versions that start with "Tor ".
9003 - Tolerate faulty streams better: when a stream fails for reason
9004 exitpolicy, stop assuming that the router is lying about his exit
9005 policy. When a stream fails for reason misc, allow it to retry just
9006 as if it was resolvefailed. When a stream has failed three times,
9007 reset its failure count so we can try again and get all three tries.
9010 Changes in version 0.1.0.15 - 2005-09-23
9011 o Bugfixes on 0.1.0.x:
9012 - Reject ports 465 and 587 (spam targets) in default exit policy.
9013 - Don't crash when we don't have any spare file descriptors and we
9014 try to spawn a dns or cpu worker.
9015 - Get rid of IgnoreVersion undocumented config option, and make us
9016 only warn, never exit, when we're running an obsolete version.
9017 - Don't try to print a null string when your server finds itself to
9018 be unreachable and the Address config option is empty.
9019 - Make the numbers in read-history and write-history into uint64s,
9020 so they don't overflow and publish negatives in the descriptor.
9021 - Fix a minor memory leak in smartlist_string_remove().
9022 - We were only allowing ourselves to upload a server descriptor at
9023 most every 20 minutes, even if it changed earlier than that.
9024 - Clean up log entries that pointed to old URLs.
9027 Changes in version 0.1.0.14 - 2005-08-08
9028 o Bugfixes on 0.1.0.x:
9029 - Fix the other half of the bug with crypto handshakes
9031 - Fix an assert trigger if you send a 'signal term' via the
9032 controller when it's listening for 'event info' messages.
9035 Changes in version 0.1.0.13 - 2005-08-04
9036 o Bugfixes on 0.1.0.x:
9037 - Fix a critical bug in the security of our crypto handshakes.
9038 - Fix a size_t underflow in smartlist_join_strings2() that made
9039 it do bad things when you hand it an empty smartlist.
9040 - Fix Windows installer to ship Tor license (thanks to Aphex for
9041 pointing out this oversight) and put a link to the doc directory
9043 - Explicitly set no-unaligned-access for sparc: it turns out the
9044 new gcc's let you compile broken code, but that doesn't make it
9048 Changes in version 0.1.0.12 - 2005-07-18
9049 o New directory servers:
9050 - tor26 has changed IP address.
9052 o Bugfixes on 0.1.0.x:
9053 - Fix a possible double-free in tor_gzip_uncompress().
9054 - When --disable-threads is set, do not search for or link against
9056 - Don't trigger an assert if an authoritative directory server
9057 claims its dirport is 0.
9058 - Fix bug with removing Tor as an NT service: some people were
9059 getting "The service did not return an error." Thanks to Matt
9063 Changes in version 0.1.0.11 - 2005-06-30
9064 o Bugfixes on 0.1.0.x:
9065 - Fix major security bug: servers were disregarding their
9066 exit policies if clients behaved unexpectedly.
9067 - Make OS X init script check for missing argument, so we don't
9068 confuse users who invoke it incorrectly.
9069 - Fix a seg fault in "tor --hash-password foo".
9070 - The MAPADDRESS control command was broken.
9073 Changes in version 0.1.0.10 - 2005-06-14
9075 - Make NT services work and start on startup on Win32 (based on
9076 patch by Matt Edman). See the FAQ entry for details.
9077 - Make 'platform' string in descriptor more accurate for Win32
9078 servers, so it's not just "unknown platform".
9079 - REUSEADDR on normal platforms means you can rebind to the port
9080 right after somebody else has let it go. But REUSEADDR on Win32
9081 means you can bind to the port _even when somebody else already
9082 has it bound_! So, don't do that on Win32.
9083 - Clean up the log messages when starting on Win32 with no config
9085 - Allow seeding the RNG on Win32 even when you're not running as
9086 Administrator. If seeding the RNG on Win32 fails, quit.
9088 o Assert / crash bugs:
9089 - Refuse relay cells that claim to have a length larger than the
9090 maximum allowed. This prevents a potential attack that could read
9091 arbitrary memory (e.g. keys) from an exit server's process
9093 - If unofficial Tor clients connect and send weird TLS certs, our
9094 Tor server triggers an assert. Stop asserting, and start handling
9095 TLS errors better in other situations too.
9096 - Fix a race condition that can trigger an assert when we have a
9097 pending create cell and an OR connection attempt fails.
9100 - Use pthreads for worker processes rather than forking. This was
9101 forced because when we forked, we ended up wasting a lot of
9102 duplicate ram over time.
9103 - Also switch to foo_r versions of some library calls to allow
9104 reentry and threadsafeness.
9105 - Implement --disable-threads configure option. Disable threads on
9106 netbsd and openbsd by default, because they have no reentrant
9107 resolver functions (!), and on solaris since it has other
9109 - Fix possible bug on threading platforms (e.g. win32) which was
9110 leaking a file descriptor whenever a cpuworker or dnsworker died.
9111 - Fix a minor memory leak when somebody establishes an introduction
9112 point at your Tor server.
9113 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
9115 - Add ./configure --with-dmalloc option, to track memory leaks.
9116 - And try to free all memory on closing, so we can detect what
9119 o Protocol correctness:
9120 - When we've connected to an OR and handshaked but didn't like
9121 the result, we were closing the conn without sending destroy
9122 cells back for pending circuits. Now send those destroys.
9123 - Start sending 'truncated' cells back rather than destroy cells
9124 if the circuit closes in front of you. This means we won't have
9125 to abandon partially built circuits.
9126 - Handle changed router status correctly when dirserver reloads
9127 fingerprint file. We used to be dropping all unverified descriptors
9128 right then. The bug was hidden because we would immediately
9129 fetch a directory from another dirserver, which would include the
9130 descriptors we just dropped.
9131 - Revise tor-spec to add more/better stream end reasons.
9132 - Revise all calls to connection_edge_end to avoid sending 'misc',
9133 and to take errno into account where possible.
9134 - Client now retries when streams end early for 'hibernating' or
9135 'resource limit' reasons, rather than failing them.
9136 - Try to be more zealous about calling connection_edge_end when
9137 things go bad with edge conns in connection.c.
9139 o Robustness improvements:
9140 - Better handling for heterogeneous / unreliable nodes:
9141 - Annotate circuits with whether they aim to contain high uptime
9142 nodes and/or high capacity nodes. When building circuits, choose
9144 - This means that every single node in an intro rend circuit,
9145 not just the last one, will have a minimum uptime.
9146 - New config option LongLivedPorts to indicate application streams
9147 that will want high uptime circuits.
9148 - Servers reset uptime when a dir fetch entirely fails. This
9149 hopefully reflects stability of the server's network connectivity.
9150 - If somebody starts his tor server in Jan 2004 and then fixes his
9151 clock, don't make his published uptime be a year.
9152 - Reset published uptime when we wake up from hibernation.
9153 - Introduce a notion of 'internal' circs, which are chosen without
9154 regard to the exit policy of the last hop. Intro and rendezvous
9155 circs must be internal circs, to avoid leaking information. Resolve
9156 and connect streams can use internal circs if they want.
9157 - New circuit pooling algorithm: keep track of what destination ports
9158 we've used recently (start out assuming we'll want to use 80), and
9159 make sure to have enough circs around to satisfy these ports. Also
9160 make sure to have 2 internal circs around if we've required internal
9161 circs lately (and with high uptime if we've seen that lately too).
9162 - Turn addr_policy_compare from a tristate to a quadstate; this should
9163 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
9164 for google.com" problem.
9165 - When a client asks us for a dir mirror and we don't have one,
9166 launch an attempt to get a fresh one.
9167 - First cut at support for "create-fast" cells. Clients can use
9168 these when extending to their first hop, since the TLS already
9169 provides forward secrecy and authentication. Not enabled on
9172 o Reachability testing.
9173 - Your Tor server will automatically try to see if its ORPort and
9174 DirPort are reachable from the outside, and it won't upload its
9175 descriptor until it decides at least ORPort is reachable (when
9176 DirPort is not yet found reachable, publish it as zero).
9177 - When building testing circs for ORPort testing, use only
9178 high-bandwidth nodes, so fewer circuits fail.
9179 - Notice when our IP changes, and reset stats/uptime/reachability.
9180 - Authdirservers don't do ORPort reachability detection, since
9181 they're in clique mode, so it will be rare to find a server not
9182 already connected to them.
9183 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
9187 - Now we allow two unverified servers with the same nickname
9188 but different keys. But if a nickname is verified, only that
9189 nickname+key are allowed.
9190 - If you're an authdirserver connecting to an address:port,
9191 and it's not the OR you were expecting, forget about that
9192 descriptor. If he *was* the one you were expecting, then forget
9193 about all other descriptors for that address:port.
9194 - Allow servers to publish descriptors from 12 hours in the future.
9195 Corollary: only whine about clock skew from the dirserver if
9196 he's a trusted dirserver (since now even verified servers could
9197 have quite wrong clocks).
9198 - Require servers that use the default dirservers to have public IP
9199 addresses. We have too many servers that are configured with private
9200 IPs and their admins never notice the log entries complaining that
9201 their descriptors are being rejected.
9203 o Efficiency improvements:
9204 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
9205 and /dev/poll), and hopefully work better on Windows too.
9206 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
9207 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
9208 - Find libevent even if it's hiding in /usr/local/ and your
9209 CFLAGS and LDFLAGS don't tell you to look there.
9210 - Be able to link with libevent as a shared library (the default
9211 after 1.0d), even if it's hiding in /usr/local/lib and even
9212 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
9213 assuming you're running gcc. Otherwise fail and give a useful
9215 - Switch to a new buffer management algorithm, which tries to avoid
9216 reallocing and copying quite as much. In first tests it looks like
9217 it uses *more* memory on average, but less cpu.
9218 - Switch our internal buffers implementation to use a ring buffer,
9219 to hopefully improve performance for fast servers a lot.
9220 - Reenable the part of the code that tries to flush as soon as an
9221 OR outbuf has a full TLS record available. Perhaps this will make
9222 OR outbufs not grow as huge except in rare cases, thus saving lots
9223 of CPU time plus memory.
9224 - Improve performance for dirservers: stop re-parsing the whole
9225 directory every time you regenerate it.
9226 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9227 it much faster to look up a circuit for each relay cell.
9228 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9229 since they're eating our cpu on exit nodes.
9230 - Stop wasting time doing a case insensitive comparison for every
9231 dns name every time we do any lookup. Canonicalize the names to
9232 lowercase when you first see them.
9235 - Handle unavailable hidden services better. Handle slow or busy
9236 hidden services better.
9237 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
9238 circ as necessary, if there are any completed ones lying around
9239 when we try to launch one.
9240 - Make hidden services try to establish a rendezvous for 30 seconds
9241 after fetching the descriptor, rather than for n (where n=3)
9242 attempts to build a circuit.
9243 - Adjust maximum skew and age for rendezvous descriptors: let skew
9244 be 48 hours rather than 90 minutes.
9245 - Reject malformed .onion addresses rather then passing them on as
9246 normal web requests.
9249 - More Tor controller support. See
9250 http://tor.eff.org/doc/control-spec.txt for all the new features,
9251 including signals to emulate unix signals from any platform;
9252 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9253 closestream; closecircuit; etc.
9254 - Encode hashed controller passwords in hex instead of base64,
9255 to make it easier to write controllers.
9256 - Revise control spec and implementation to allow all log messages to
9257 be sent to controller with their severities intact (suggested by
9258 Matt Edman). Disable debug-level logs while delivering a debug-level
9259 log to the controller, to prevent loop. Update TorControl to handle
9260 new log event types.
9262 o New config options/defaults:
9263 - Begin scrubbing sensitive strings from logs by default. Turn off
9264 the config option SafeLogging if you need to do debugging.
9265 - New exit policy: accept most low-numbered ports, rather than
9266 rejecting most low-numbered ports.
9267 - Put a note in the torrc about abuse potential with the default
9269 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9271 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
9272 based on patch from Adam Langley (basic auth only).
9273 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
9274 the fast servers that have been joining lately. (Clients are now
9275 willing to load balance over up to 2 MB of advertised bandwidth
9277 - New config option MaxAdvertisedBandwidth which lets you advertise
9278 a low bandwidthrate (to not attract as many circuits) while still
9279 allowing a higher bandwidthrate in reality.
9280 - Require BandwidthRate to be at least 20kB/s for servers.
9281 - Add a NoPublish config option, so you can be a server (e.g. for
9282 testing running Tor servers in other Tor networks) without
9283 publishing your descriptor to the primary dirservers.
9284 - Add a new AddressMap config directive to rewrite incoming socks
9285 addresses. This lets you, for example, declare an implicit
9286 required exit node for certain sites.
9287 - Add a new TrackHostExits config directive to trigger addressmaps
9288 for certain incoming socks addresses -- for sites that break when
9289 your exit keeps changing (based on patch from Mike Perry).
9290 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
9291 which describes how often we retry making new circuits if current
9292 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
9293 how long we're willing to make use of an already-dirty circuit.
9294 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
9295 a config option "ShutdownWaitLength" (when using kill -INT on
9297 - Fix an edge case in parsing config options: if they say "--"
9298 on the commandline, it's not a config option (thanks weasel).
9299 - New config option DirAllowPrivateAddresses for authdirservers.
9300 Now by default they refuse router descriptors that have non-IP or
9301 private-IP addresses.
9302 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
9303 smart" default value: low for servers and high for clients.
9304 - Some people were putting "Address " in their torrc, and they had
9305 a buggy resolver that resolved " " to 0.0.0.0. Oops.
9306 - If DataDir is ~/.tor, and that expands to /.tor, then default to
9307 LOCALSTATEDIR/tor instead.
9308 - Implement --verify-config command-line option to check if your torrc
9309 is valid without actually launching Tor.
9311 o Logging improvements:
9312 - When dirservers refuse a server descriptor, we now log its
9313 contactinfo, platform, and the poster's IP address.
9314 - Only warn once per nickname from add_nickname_list_to_smartlist()
9315 per failure, so an entrynode or exitnode choice that's down won't
9317 - When we're connecting to an OR and he's got a different nickname/key
9318 than we were expecting, only complain loudly if we're an OP or a
9319 dirserver. Complaining loudly to the OR admins just confuses them.
9320 - Whine at you if you're a server and you don't set your contactinfo.
9321 - Warn when exit policy implicitly allows local addresses.
9322 - Give a better warning when some other server advertises an
9323 ORPort that is actually an apache running ssl.
9324 - If we get an incredibly skewed timestamp from a dirserver mirror
9325 that isn't a verified OR, don't warn -- it's probably him that's
9327 - When a dirserver causes you to give a warn, mention which dirserver
9329 - Initialize libevent later in the startup process, so the logs are
9330 already established by the time we start logging libevent warns.
9331 - Use correct errno on win32 if libevent fails.
9332 - Check and warn about known-bad/slow libevent versions.
9333 - Stop warning about sigpipes in the logs. We're going to
9334 pretend that getting these occassionally is normal and fine.
9336 o New contrib scripts:
9337 - New experimental script tor/contrib/exitlist: a simple python
9338 script to parse directories and find Tor nodes that exit to listed
9340 - New experimental script tor/contrib/ExerciseServer.py (needs more
9341 work) that uses the controller interface to build circuits and
9342 fetch pages over them. This will help us bootstrap servers that
9343 have lots of capacity but haven't noticed it yet.
9344 - New experimental script tor/contrib/PathDemo.py (needs more work)
9345 that uses the controller interface to let you choose whole paths
9347 "<hostname>.<path,separated by dots>.<length of path>.path"
9348 - New contributed script "privoxy-tor-toggle" to toggle whether
9349 Privoxy uses Tor. Seems to be configured for Debian by default.
9350 - Have torctl.in/tor.sh.in check for location of su binary (needed
9354 - chdir() to your datadirectory at the *end* of the daemonize process,
9355 not the beginning. This was a problem because the first time you
9356 run tor, if your datadir isn't there, and you have runasdaemon set
9357 to 1, it will try to chdir to it before it tries to create it. Oops.
9358 - Fix several double-mark-for-close bugs, e.g. where we were finding
9359 a conn for a cell even if that conn is already marked for close.
9360 - Stop most cases of hanging up on a socks connection without sending
9362 - Fix a bug in the RPM package: set home directory for _tor to
9363 something more reasonable when first installing.
9364 - Stop putting nodename in the Platform string in server descriptors.
9365 It doesn't actually help, and it is confusing/upsetting some people.
9366 - When using preferred entry or exit nodes, ignore whether the
9367 circuit wants uptime or capacity. They asked for the nodes, they
9369 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9370 artificially capped at 500kB.
9371 - Cache local dns resolves correctly even when they're .exit
9373 - If we're hibernating and we get a SIGINT, exit immediately.
9374 - tor-resolve requests were ignoring .exit if there was a working circuit
9375 they could use instead.
9376 - Pay more attention to the ClientOnly config option.
9377 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
9378 installer screens; and don't put stuff into StartupItems unless
9379 the user asks you to.
9382 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
9383 rather than just rejecting it.
9384 - If our clock jumps forward by 100 seconds or more, assume something
9385 has gone wrong with our network and abandon all not-yet-used circs.
9386 - When an application is using socks5, give him the whole variety of
9387 potential socks5 responses (connect refused, host unreachable, etc),
9388 rather than just "success" or "failure".
9389 - A more sane version numbering system. See
9390 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9391 - Change version parsing logic: a version is "obsolete" if it is not
9392 recommended and (1) there is a newer recommended version in the
9393 same series, or (2) there are no recommended versions in the same
9394 series, but there are some recommended versions in a newer series.
9395 A version is "new" if it is newer than any recommended version in
9397 - Report HTTP reasons to client when getting a response from directory
9398 servers -- so you can actually know what went wrong.
9399 - Reject odd-looking addresses at the client (e.g. addresses that
9400 contain a colon), rather than having the server drop them because
9402 - Stop publishing socksport in the directory, since it's not
9403 actually meant to be public. For compatibility, publish a 0 there
9405 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
9406 cookies to disk and doesn't log each web request to disk. (Thanks
9407 to Brett Carrington for pointing this out.)
9408 - Add OSX uninstall instructions. An actual uninstall script will
9410 - Add "opt hibernating 1" to server descriptor to make it clearer
9411 whether the server is hibernating.
9414 Changes in version 0.0.9.10 - 2005-06-16
9415 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
9416 - Refuse relay cells that claim to have a length larger than the
9417 maximum allowed. This prevents a potential attack that could read
9418 arbitrary memory (e.g. keys) from an exit server's process
9422 Changes in version 0.0.9.9 - 2005-04-23
9423 o Bugfixes on 0.0.9.x:
9424 - If unofficial Tor clients connect and send weird TLS certs, our
9425 Tor server triggers an assert. This release contains a minimal
9426 backport from the broader fix that we put into 0.1.0.4-rc.
9429 Changes in version 0.0.9.8 - 2005-04-07
9430 o Bugfixes on 0.0.9.x:
9431 - We have a bug that I haven't found yet. Sometimes, very rarely,
9432 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9433 thinks of itself as idle. This meant that no new circuits ever got
9434 established. Here's a workaround to kill any cpuworker that's been
9435 busy for more than 100 seconds.
9438 Changes in version 0.0.9.7 - 2005-04-01
9439 o Bugfixes on 0.0.9.x:
9440 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9441 - Compare identity to identity, not to nickname, when extending to
9442 a router not already in the directory. This was preventing us from
9443 extending to unknown routers. Oops.
9444 - Make sure to create OS X Tor user in <500 range, so we aren't
9445 creating actual system users.
9446 - Note where connection-that-hasn't-sent-end was marked, and fix
9447 a few really loud instances of this harmless bug (it's fixed more
9451 Changes in version 0.0.9.6 - 2005-03-24
9452 o Bugfixes on 0.0.9.x (crashes and asserts):
9453 - Add new end stream reasons to maintainance branch. Fix bug where
9454 reason (8) could trigger an assert. Prevent bug from recurring.
9455 - Apparently win32 stat wants paths to not end with a slash.
9456 - Fix assert triggers in assert_cpath_layer_ok(), where we were
9457 blowing away the circuit that conn->cpath_layer points to, then
9458 checking to see if the circ is well-formed. Backport check to make
9459 sure we dont use the cpath on a closed connection.
9460 - Prevent circuit_resume_edge_reading_helper() from trying to package
9461 inbufs for marked-for-close streams.
9462 - Don't crash on hup if your options->address has become unresolvable.
9463 - Some systems (like OS X) sometimes accept() a connection and tell
9464 you the remote host is 0.0.0.0:0. If this happens, due to some
9465 other mis-features, we get confused; so refuse the conn for now.
9467 o Bugfixes on 0.0.9.x (other):
9468 - Fix harmless but scary "Unrecognized content encoding" warn message.
9469 - Add new stream error reason: TORPROTOCOL reason means "you are not
9470 speaking a version of Tor I understand; say bye-bye to your stream."
9471 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
9472 into the future, now that we are more tolerant of skew. This
9473 resolves a bug where a Tor server would refuse to cache a directory
9474 because all the directories it gets are too far in the future;
9475 yet the Tor server never logs any complaints about clock skew.
9476 - Mac packaging magic: make man pages useable, and do not overwrite
9477 existing torrc files.
9478 - Make OS X log happily to /var/log/tor/tor.log
9481 Changes in version 0.0.9.5 - 2005-02-22
9482 o Bugfixes on 0.0.9.x:
9483 - Fix an assert race at exit nodes when resolve requests fail.
9484 - Stop picking unverified dir mirrors--it only leads to misery.
9485 - Patch from Matt Edman to make NT services work better. Service
9486 support is still not compiled into the executable by default.
9487 - Patch from Dmitri Bely so the Tor service runs better under
9488 the win32 SYSTEM account.
9489 - Make tor-resolve actually work (?) on Win32.
9490 - Fix a sign bug when getrlimit claims to have 4+ billion
9491 file descriptors available.
9492 - Stop refusing to start when bandwidthburst == bandwidthrate.
9493 - When create cells have been on the onion queue more than five
9494 seconds, just send back a destroy and take them off the list.
9497 Changes in version 0.0.9.4 - 2005-02-03
9498 o Bugfixes on 0.0.9:
9499 - Fix an assert bug that took down most of our servers: when
9500 a server claims to have 1 GB of bandwidthburst, don't
9502 - Don't crash as badly if we have spawned the max allowed number
9503 of dnsworkers, or we're out of file descriptors.
9504 - Block more file-sharing ports in the default exit policy.
9505 - MaxConn is now automatically set to the hard limit of max
9506 file descriptors we're allowed (ulimit -n), minus a few for
9508 - Give a clearer message when servers need to raise their
9509 ulimit -n when they start running out of file descriptors.
9510 - SGI Compatibility patches from Jan Schaumann.
9511 - Tolerate a corrupt cached directory better.
9512 - When a dirserver hasn't approved your server, list which one.
9513 - Go into soft hibernation after 95% of the bandwidth is used,
9514 not 99%. This is especially important for daily hibernators who
9515 have a small accounting max. Hopefully it will result in fewer
9516 cut connections when the hard hibernation starts.
9517 - Load-balance better when using servers that claim more than
9518 800kB/s of capacity.
9519 - Make NT services work (experimental, only used if compiled in).
9522 Changes in version 0.0.9.3 - 2005-01-21
9523 o Bugfixes on 0.0.9:
9524 - Backport the cpu use fixes from main branch, so busy servers won't
9525 need as much processor time.
9526 - Work better when we go offline and then come back, or when we
9527 run Tor at boot before the network is up. We do this by
9528 optimistically trying to fetch a new directory whenever an
9529 application request comes in and we think we're offline -- the
9530 human is hopefully a good measure of when the network is back.
9531 - Backport some minimal hidserv bugfixes: keep rend circuits open as
9532 long as you keep using them; actually publish hidserv descriptors
9533 shortly after they change, rather than waiting 20-40 minutes.
9534 - Enable Mac startup script by default.
9535 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
9536 - When you update AllowUnverifiedNodes or FirewallPorts via the
9537 controller's setconf feature, we were always appending, never
9539 - When you update HiddenServiceDir via setconf, it was screwing up
9540 the order of reading the lines, making it fail.
9541 - Do not rewrite a cached directory back to the cache; otherwise we
9542 will think it is recent and not fetch a newer one on startup.
9543 - Workaround for webservers that lie about Content-Encoding: Tor
9544 now tries to autodetect compressed directories and compression
9545 itself. This lets us Proxypass dir fetches through apache.
9548 Changes in version 0.0.9.2 - 2005-01-04
9549 o Bugfixes on 0.0.9 (crashes and asserts):
9550 - Fix an assert on startup when the disk is full and you're logging
9552 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
9553 style address, then we'd crash.
9554 - Fix an assert trigger when the running-routers string we get from
9555 a dirserver is broken.
9556 - Make worker threads start and run on win32. Now win32 servers
9558 - Bandaid (not actually fix, but now it doesn't crash) an assert
9559 where the dns worker dies mysteriously and the main Tor process
9560 doesn't remember anything about the address it was resolving.
9562 o Bugfixes on 0.0.9 (Win32):
9563 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
9564 name out of the warning/assert messages.
9565 - Fix a superficial "unhandled error on read" bug on win32.
9566 - The win32 installer no longer requires a click-through for our
9567 license, since our Free Software license grants rights but does not
9569 - Win32: When connecting to a dirserver fails, try another one
9570 immediately. (This was already working for non-win32 Tors.)
9571 - Stop trying to parse $HOME on win32 when hunting for default
9573 - Make tor-resolve.c work on win32 by calling network_init().
9575 o Bugfixes on 0.0.9 (other):
9576 - Make 0.0.9.x build on Solaris again.
9577 - Due to a fencepost error, we were blowing away the \n when reporting
9578 confvalue items in the controller. So asking for multiple config
9579 values at once couldn't work.
9580 - When listing circuits that are pending on an opening OR connection,
9581 if we're an OR we were listing circuits that *end* at us as
9582 being pending on every listener, dns/cpu worker, etc. Stop that.
9583 - Dirservers were failing to create 'running-routers' or 'directory'
9584 strings if we had more than some threshold of routers. Fix them so
9585 they can handle any number of routers.
9586 - Fix a superficial "Duplicate mark for close" bug.
9587 - Stop checking for clock skew for OR connections, even for servers.
9588 - Fix a fencepost error that was chopping off the last letter of any
9589 nickname that is the maximum allowed nickname length.
9590 - Update URLs in log messages so they point to the new website.
9591 - Fix a potential problem in mangling server private keys while
9592 writing to disk (not triggered yet, as far as we know).
9593 - Include the licenses for other free software we include in Tor,
9594 now that we're shipping binary distributions more regularly.
9597 Changes in version 0.0.9.1 - 2004-12-15
9598 o Bugfixes on 0.0.9:
9599 - Make hibernation actually work.
9600 - Make HashedControlPassword config option work.
9601 - When we're reporting event circuit status to a controller,
9602 don't use the stream status code.
9605 Changes in version 0.0.9 - 2004-12-12
9606 o Bugfixes on 0.0.8.1 (Crashes and asserts):
9607 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
9608 write() call will fail and we handle it there.
9609 - When we run out of disk space, or other log writing error, don't
9610 crash. Just stop logging to that log and continue.
9611 - Fix isspace() and friends so they still make Solaris happy
9612 but also so they don't trigger asserts on win32.
9613 - Fix assert failure on malformed socks4a requests.
9614 - Fix an assert bug where a hidden service provider would fail if
9615 the first hop of his rendezvous circuit was down.
9616 - Better handling of size_t vs int, so we're more robust on 64
9619 o Bugfixes on 0.0.8.1 (Win32):
9620 - Make windows sockets actually non-blocking (oops), and handle
9621 win32 socket errors better.
9622 - Fix parse_iso_time on platforms without strptime (eg win32).
9623 - win32: when being multithreaded, leave parent fdarray open.
9624 - Better handling of winsock includes on non-MSV win32 compilers.
9625 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
9627 - Make unit tests work on win32.
9629 o Bugfixes on 0.0.8.1 (Path selection and streams):
9630 - Calculate timeout for waiting for a connected cell from the time
9631 we sent the begin cell, not from the time the stream started. If
9632 it took a long time to establish the circuit, we would time out
9633 right after sending the begin cell.
9634 - Fix router_compare_addr_to_addr_policy: it was not treating a port
9635 of * as always matching, so we were picking reject *:* nodes as
9636 exit nodes too. Oops.
9637 - When read() failed on a stream, we would close it without sending
9638 back an end. So 'connection refused' would simply be ignored and
9639 the user would get no response.
9640 - Stop a sigpipe: when an 'end' cell races with eof from the app,
9641 we shouldn't hold-open-until-flush if the eof arrived first.
9642 - Let resolve conns retry/expire also, rather than sticking around
9644 - Fix more dns related bugs: send back resolve_failed and end cells
9645 more reliably when the resolve fails, rather than closing the
9646 circuit and then trying to send the cell. Also attach dummy resolve
9647 connections to a circuit *before* calling dns_resolve(), to fix
9648 a bug where cached answers would never be sent in RESOLVED cells.
9650 o Bugfixes on 0.0.8.1 (Circuits):
9651 - Finally fix a bug that's been plaguing us for a year:
9652 With high load, circuit package window was reaching 0. Whenever
9653 we got a circuit-level sendme, we were reading a lot on each
9654 socket, but only writing out a bit. So we would eventually reach
9655 eof. This would be noticed and acted on even when there were still
9656 bytes sitting in the inbuf.
9657 - Use identity comparison, not nickname comparison, to choose which
9658 half of circuit-ID-space each side gets to use. This is needed
9659 because sometimes we think of a router as a nickname, and sometimes
9660 as a hex ID, and we can't predict what the other side will do.
9662 o Bugfixes on 0.0.8.1 (Other):
9663 - Fix a whole slew of memory leaks.
9664 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
9665 - If we are using select, make sure we stay within FD_SETSIZE.
9666 - When poll() is interrupted, we shouldn't believe the revents values.
9667 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
9668 and smartlist_len, which are two major profiling offenders.
9669 - If do_hup fails, actually notice.
9670 - Flush the log file descriptor after we print "Tor opening log file",
9671 so we don't see those messages days later.
9672 - Hidden service operators now correctly handle version 1 style
9673 INTRODUCE1 cells (nobody generates them still, so not a critical
9675 - Handle more errnos from accept() without closing the listener.
9676 Some OpenBSD machines were closing their listeners because
9677 they ran out of file descriptors.
9678 - Some people had wrapped their tor client/server in a script
9679 that would restart it whenever it died. This did not play well
9680 with our "shut down if your version is obsolete" code. Now people
9681 don't fetch a new directory if their local cached version is
9683 - Make our autogen.sh work on ksh as well as bash.
9684 - Better torrc example lines for dirbindaddress and orbindaddress.
9685 - Improved bounds checking on parsed ints (e.g. config options and
9686 the ones we find in directories.)
9687 - Stop using separate defaults for no-config-file and
9688 empty-config-file. Now you have to explicitly turn off SocksPort,
9689 if you don't want it open.
9690 - We were starting to daemonize before we opened our logs, so if
9691 there were any problems opening logs, we would complain to stderr,
9692 which wouldn't work, and then mysteriously exit.
9693 - If a verified OR connects to us before he's uploaded his descriptor,
9694 or we verify him and hup but he still has the original TLS
9695 connection, then conn->nickname is still set like he's unverified.
9697 o Code security improvements, inspired by Ilja:
9698 - tor_snprintf wrapper over snprintf with consistent (though not C99)
9700 - Replace sprintf with tor_snprintf. (I think they were all safe, but
9702 - Replace strcpy/strncpy with strlcpy in more places.
9703 - Avoid strcat; use tor_snprintf or strlcat instead.
9705 o Features (circuits and streams):
9706 - New circuit building strategy: keep a list of ports that we've
9707 used in the past 6 hours, and always try to have 2 circuits open
9708 or on the way that will handle each such port. Seed us with port
9709 80 so web users won't complain that Tor is "slow to start up".
9710 - Make kill -USR1 dump more useful stats about circuits.
9711 - When warning about retrying or giving up, print the address, so
9712 the user knows which one it's talking about.
9713 - If you haven't used a clean circuit in an hour, throw it away,
9714 just to be on the safe side. (This means after 6 hours a totally
9715 unused Tor client will have no circuits open.)
9716 - Support "foo.nickname.exit" addresses, to let Alice request the
9717 address "foo" as viewed by exit node "nickname". Based on a patch
9719 - If your requested entry or exit node has advertised bandwidth 0,
9721 - Be more greedy about filling up relay cells -- we try reading again
9722 once we've processed the stuff we read, in case enough has arrived
9723 to fill the last cell completely.
9724 - Refuse application socks connections to port 0.
9725 - Use only 0.0.9pre1 and later servers for resolve cells.
9727 o Features (bandwidth):
9728 - Hibernation: New config option "AccountingMax" lets you
9729 set how many bytes per month (in each direction) you want to
9730 allow your server to consume. Rather than spreading those
9731 bytes out evenly over the month, we instead hibernate for some
9732 of the month and pop up at a deterministic time, work until
9733 the bytes are consumed, then hibernate again. Config option
9734 "MonthlyAccountingStart" lets you specify which day of the month
9735 your billing cycle starts on.
9736 - Implement weekly/monthly/daily accounting: now you specify your
9737 hibernation properties by
9738 AccountingMax N bytes|KB|MB|GB|TB
9739 AccountingStart day|week|month [day] HH:MM
9740 Defaults to "month 1 0:00".
9741 - Let bandwidth and interval config options be specified as 5 bytes,
9742 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
9744 o Features (directories):
9745 - New "router-status" line in directory, to better bind each verified
9746 nickname to its identity key.
9747 - Clients can ask dirservers for /dir.z to get a compressed version
9748 of the directory. Only works for servers running 0.0.9, of course.
9749 - Make clients cache directories and use them to seed their router
9750 lists at startup. This means clients have a datadir again.
9751 - Respond to content-encoding headers by trying to uncompress as
9753 - Clients and servers now fetch running-routers; cache
9754 running-routers; compress running-routers; serve compressed
9756 - Make moria2 advertise a dirport of 80, so people behind firewalls
9757 will be able to get a directory.
9758 - Http proxy support
9759 - Dirservers translate requests for http://%s:%d/x to /x
9760 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
9761 be routed through this host.
9762 - Clients ask for /tor/x rather than /x for new enough dirservers.
9763 This way we can one day coexist peacefully with apache.
9764 - Clients specify a "Host: %s%d" http header, to be compatible
9765 with more proxies, and so running squid on an exit node can work.
9766 - Protect dirservers from overzealous descriptor uploading -- wait
9767 10 seconds after directory gets dirty, before regenerating.
9769 o Features (packages and install):
9770 - Add NSI installer contributed by J Doe.
9771 - Apply NT service patch from Osamu Fujino. Still needs more work.
9772 - Commit VC6 and VC7 workspace/project files.
9773 - Commit a tor.spec for making RPM files, with help from jbash.
9774 - Add contrib/torctl.in contributed by Glenn Fink.
9775 - Make expand_filename handle ~ and ~username.
9776 - Use autoconf to enable largefile support where necessary. Use
9777 ftello where available, since ftell can fail at 2GB.
9778 - Ship src/win32/ in the tarball, so people can use it to build.
9779 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
9782 o Features (ui controller):
9783 - Control interface: a separate program can now talk to your
9784 client/server over a socket, and get/set config options, receive
9785 notifications of circuits and streams starting/finishing/dying,
9786 bandwidth used, etc. The next step is to get some GUIs working.
9787 Let us know if you want to help out. See doc/control-spec.txt .
9788 - Ship a contrib/tor-control.py as an example script to interact
9789 with the control port.
9790 - "tor --hash-password zzyxz" will output a salted password for
9791 use in authenticating to the control interface.
9792 - Implement the control-spec's SAVECONF command, to write your
9793 configuration to torrc.
9794 - Get cookie authentication for the controller closer to working.
9795 - When set_conf changes our server descriptor, upload a new copy.
9796 But don't upload it too often if there are frequent changes.
9798 o Features (config and command-line):
9799 - Deprecate unofficial config option abbreviations, and abbreviations
9800 not on the command line.
9801 - Configuration infrastructure support for warning on obsolete
9803 - Give a slightly more useful output for "tor -h".
9804 - Break DirFetchPostPeriod into:
9805 - DirFetchPeriod for fetching full directory,
9806 - StatusFetchPeriod for fetching running-routers,
9807 - DirPostPeriod for posting server descriptor,
9808 - RendPostPeriod for posting hidden service descriptors.
9809 - New log format in config:
9810 "Log minsev[-maxsev] stdout|stderr|syslog" or
9811 "Log minsev[-maxsev] file /var/foo"
9812 - DirPolicy config option, to let people reject incoming addresses
9813 from their dirserver.
9814 - "tor --list-fingerprint" will list your identity key fingerprint
9816 - Make tor --version --version dump the cvs Id of every file.
9817 - New 'MyFamily nick1,...' config option for a server to
9818 specify other servers that shouldn't be used in the same circuit
9819 with it. Only believed if nick1 also specifies us.
9820 - New 'NodeFamily nick1,nick2,...' config option for a client to
9821 specify nodes that it doesn't want to use in the same circuit.
9822 - New 'Redirectexit pattern address:port' config option for a
9823 server to redirect exit connections, e.g. to a local squid.
9824 - Add "pass" target for RedirectExit, to make it easier to break
9825 out of a sequence of RedirectExit rules.
9826 - Make the dirservers file obsolete.
9827 - Include a dir-signing-key token in directories to tell the
9828 parsing entity which key is being used to sign.
9829 - Remove the built-in bulky default dirservers string.
9830 - New config option "Dirserver %s:%d [fingerprint]", which can be
9831 repeated as many times as needed. If no dirservers specified,
9832 default to moria1,moria2,tor26.
9833 - Make 'Routerfile' config option obsolete.
9834 - Discourage people from setting their dirfetchpostperiod more often
9835 than once per minute.
9838 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
9839 get back to normal.)
9840 - Accept *:706 (silc) in default exit policy.
9841 - Implement new versioning format for post 0.1.
9842 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
9843 log more informatively.
9844 - Check clock skew for verified servers, but allow unverified
9845 servers and clients to have any clock skew.
9846 - Make sure the hidden service descriptors are at a random offset
9847 from each other, to hinder linkability.
9848 - Clients now generate a TLS cert too, in preparation for having
9849 them act more like real nodes.
9850 - Add a pure-C tor-resolve implementation.
9851 - Use getrlimit and friends to ensure we can reach MaxConn (currently
9852 1024) file descriptors.
9853 - Raise the max dns workers from 50 to 100.
9856 Changes in version 0.0.8.1 - 2004-10-13
9858 - Fix a seg fault that can be triggered remotely for Tor
9859 clients/servers with an open dirport.
9860 - Fix a rare assert trigger, where routerinfos for entries in
9861 our cpath would expire while we're building the path.
9862 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9863 - Fix a rare seg fault for people running hidden services on
9864 intermittent connections.
9865 - Fix a bug in parsing opt keywords with objects.
9866 - Fix a stale pointer assert bug when a stream detaches and
9868 - Fix a string format vulnerability (probably not exploitable)
9869 in reporting stats locally.
9870 - Fix an assert trigger: sometimes launching circuits can fail
9871 immediately, e.g. because too many circuits have failed recently.
9872 - Fix a compile warning on 64 bit platforms.
9875 Changes in version 0.0.8 - 2004-08-25
9877 - Made our unit tests compile again on OpenBSD 3.5, and tor
9878 itself compile again on OpenBSD on a sparc64.
9879 - We were neglecting milliseconds when logging on win32, so
9880 everything appeared to happen at the beginning of each second.
9881 - Check directory signature _before_ you decide whether you're
9882 you're running an obsolete version and should exit.
9883 - Check directory signature _before_ you parse the running-routers
9884 list to decide who's running.
9885 - Check return value of fclose while writing to disk, so we don't
9886 end up with broken files when servers run out of disk space.
9887 - Port it to SunOS 5.9 / Athena
9888 - Fix two bugs in saving onion keys to disk when rotating, so
9889 hopefully we'll get fewer people using old onion keys.
9890 - Remove our mostly unused -- and broken -- hex_encode()
9891 function. Use base16_encode() instead. (Thanks to Timo Lindfors
9892 for pointing out this bug.)
9893 - Only pick and establish intro points after we've gotten a
9895 - Fix assert triggers: if the other side returns an address 0.0.0.0,
9896 don't put it into the client dns cache.
9897 - If a begin failed due to exit policy, but we believe the IP
9898 address should have been allowed, switch that router to exitpolicy
9899 reject *:* until we get our next directory.
9902 - 'Extend' relay cell payloads now include the digest of the
9903 intended next hop's identity key. Now we can verify that we're
9904 extending to the right router, and also extend to routers we
9905 hadn't heard of before.
9908 - Tor nodes can now act as relays (with an advertised ORPort)
9909 without being manually verified by the dirserver operators.
9910 - Uploaded descriptors of unverified routers are now accepted
9911 by the dirservers, and included in the directory.
9912 - Verified routers are listed by nickname in the running-routers
9913 list; unverified routers are listed as "$<fingerprint>".
9914 - We now use hash-of-identity-key in most places rather than
9915 nickname or addr:port, for improved security/flexibility.
9916 - AllowUnverifiedNodes config option to let circuits choose no-name
9917 routers in entry,middle,exit,introduction,rendezvous positions.
9918 Allow middle and rendezvous positions by default.
9919 - When picking unverified routers, skip those with low uptime and/or
9920 low bandwidth, depending on what properties you care about.
9921 - ClientOnly option for nodes that never want to become servers.
9922 - Directory caching.
9923 - "AuthoritativeDir 1" option for the official dirservers.
9924 - Now other nodes (clients and servers) will cache the latest
9925 directory they've pulled down.
9926 - They can enable their DirPort to serve it to others.
9927 - Clients will pull down a directory from any node with an open
9928 DirPort, and check the signature/timestamp correctly.
9929 - Authoritative dirservers now fetch directories from other
9930 authdirservers, to stay better synced.
9931 - Running-routers list tells who's down also, along with noting
9932 if they're verified (listed by nickname) or unverified (listed
9934 - Allow dirservers to serve running-router list separately.
9935 This isn't used yet.
9936 - You can now fetch $DIRURL/running-routers to get just the
9937 running-routers line, not the whole descriptor list. (But
9938 clients don't use this yet.)
9939 - Clients choose nodes proportional to advertised bandwidth.
9940 - Clients avoid using nodes with low uptime as introduction points.
9941 - Handle servers with dynamic IP addresses: don't just replace
9942 options->Address with the resolved one at startup, and
9943 detect our address right before we make a routerinfo each time.
9944 - 'FascistFirewall' option to pick dirservers and ORs on specific
9945 ports; plus 'FirewallPorts' config option to tell FascistFirewall
9946 which ports are open. (Defaults to 80,443)
9947 - Try other dirservers immediately if the one you try is down. This
9948 should tolerate down dirservers better now.
9949 - ORs connect-on-demand to other ORs
9950 - If you get an extend cell to an OR you're not connected to,
9951 connect, handshake, and forward the create cell.
9952 - The authoritative dirservers stay connected to everybody,
9953 and everybody stays connected to 0.0.7 servers, but otherwise
9954 clients/servers expire unused connections after 5 minutes.
9955 - When servers get a sigint, they delay 30 seconds (refusing new
9956 connections) then exit. A second sigint causes immediate exit.
9957 - File and name management:
9958 - Look for .torrc if no CONFDIR "torrc" is found.
9959 - If no datadir is defined, then choose, make, and secure ~/.tor
9961 - If torrc not found, exitpolicy reject *:*.
9962 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
9963 - If no nickname is defined, derive default from hostname.
9964 - Rename secret key files, e.g. identity.key -> secret_id_key,
9965 to discourage people from mailing their identity key to tor-ops.
9966 - Refuse to build a circuit before the directory has arrived --
9967 it won't work anyway, since you won't know the right onion keys
9969 - Parse tor version numbers so we can do an is-newer-than check
9970 rather than an is-in-the-list check.
9971 - New socks command 'resolve', to let us shim gethostbyname()
9973 - A 'tor_resolve' script to access the socks resolve functionality.
9974 - A new socks-extensions.txt doc file to describe our
9975 interpretation and extensions to the socks protocols.
9976 - Add a ContactInfo option, which gets published in descriptor.
9977 - Write tor version at the top of each log file
9978 - New docs in the tarball:
9980 - Document that you should proxy your SSL traffic too.
9981 - Log a warning if the user uses an unsafe socks variant, so people
9982 are more likely to learn about privoxy or socat.
9983 - Log a warning if you're running an unverified server, to let you
9984 know you might want to get it verified.
9985 - Change the default exit policy to reject the default edonkey,
9986 kazaa, gnutella ports.
9987 - Add replace_file() to util.[ch] to handle win32's rename().
9988 - Publish OR uptime in descriptor (and thus in directory) too.
9989 - Remember used bandwidth (both in and out), and publish 15-minute
9990 snapshots for the past day into our descriptor.
9991 - Be more aggressive about trying to make circuits when the network
9992 has changed (e.g. when you unsuspend your laptop).
9993 - Check for time skew on http headers; report date in response to
9995 - If the entrynode config line has only one node, don't pick it as
9997 - Add strict{entry|exit}nodes config options. If set to 1, then
9998 we refuse to build circuits that don't include the specified entry
10000 - OutboundBindAddress config option, to bind to a specific
10001 IP address for outgoing connect()s.
10002 - End truncated log entries (e.g. directories) with "[truncated]".
10005 Changes in version 0.0.7.3 - 2004-08-12
10006 o Stop dnsworkers from triggering an assert failure when you
10007 ask them to resolve the host "".
10010 Changes in version 0.0.7.2 - 2004-07-07
10011 o A better fix for the 0.0.0.0 problem, that will hopefully
10012 eliminate the remaining related assertion failures.
10015 Changes in version 0.0.7.1 - 2004-07-04
10016 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
10017 since internally we use 0.0.0.0 to signify "not yet resolved".
10020 Changes in version 0.0.7 - 2004-06-07
10021 o Fixes for crashes and other obnoxious bugs:
10022 - Fix an epipe bug: sometimes when directory connections failed
10023 to connect, we would give them a chance to flush before closing
10025 - When we detached from a circuit because of resolvefailed, we
10026 would immediately try the same circuit twice more, and then
10027 give up on the resolve thinking we'd tried three different
10029 - Limit the number of intro circuits we'll attempt to build for a
10030 hidden service per 15-minute period.
10031 - Check recommended-software string *early*, before actually parsing
10032 the directory. Thus we can detect an obsolete version and exit,
10033 even if the new directory format doesn't parse.
10034 o Fixes for security bugs:
10035 - Remember which nodes are dirservers when you startup, and if a
10036 random OR enables his dirport, don't automatically assume he's
10037 a trusted dirserver.
10039 - Directory connections were asking the wrong poll socket to
10040 start writing, and not asking themselves to start writing.
10041 - When we detached from a circuit because we sent a begin but
10042 didn't get a connected, we would use it again the first time;
10043 but after that we would correctly switch to a different one.
10044 - Stop warning when the first onion decrypt attempt fails; they
10045 will sometimes legitimately fail now that we rotate keys.
10046 - Override unaligned-access-ok check when $host_cpu is ia64 or
10047 arm. Apparently they allow it but the kernel whines.
10048 - Dirservers try to reconnect periodically too, in case connections
10050 - Fix some memory leaks in directory servers.
10051 - Allow backslash in Win32 filenames.
10052 - Made Tor build complain-free on FreeBSD, hopefully without
10053 breaking other BSD builds. We'll see.
10054 - Check directory signatures based on name of signer, not on whom
10055 we got the directory from. This will let us cache directories more
10057 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
10060 - Doxygen markup on all functions and global variables.
10061 - Make directory functions update routerlist, not replace it. So
10062 now directory disagreements are not so critical a problem.
10063 - Remove the upper limit on number of descriptors in a dirserver's
10064 directory (not that we were anywhere close).
10065 - Allow multiple logfiles at different severity ranges.
10066 - Allow *BindAddress to specify ":port" rather than setting *Port
10067 separately. Allow multiple instances of each BindAddress config
10068 option, so you can bind to multiple interfaces if you want.
10069 - Allow multiple exit policy lines, which are processed in order.
10070 Now we don't need that huge line with all the commas in it.
10071 - Enable accept/reject policies on SOCKS connections, so you can bind
10072 to 0.0.0.0 but still control who can use your OP.
10073 - Updated the man page to reflect these features.
10076 Changes in version 0.0.6.2 - 2004-05-16
10077 o Our integrity-checking digest was checking only the most recent cell,
10078 not the previous cells like we'd thought.
10079 Thanks to Stefan Mark for finding the flaw!
10082 Changes in version 0.0.6.1 - 2004-05-06
10083 o Fix two bugs in our AES counter-mode implementation (this affected
10084 onion-level stream encryption, but not TLS-level). It turns
10085 out we were doing something much more akin to a 16-character
10086 polyalphabetic cipher. Oops.
10087 Thanks to Stefan Mark for finding the flaw!
10088 o Retire moria3 as a directory server, and add tor26 as a directory
10092 Changes in version 0.0.6 - 2004-05-02
10094 - Hidden services and rendezvous points are implemented. Go to
10095 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
10096 hidden services. (This only works via a socks4a proxy such as
10097 Privoxy, and currently it's quite slow.)
10098 - We now rotate link (tls context) keys and onion keys.
10099 - CREATE cells now include oaep padding, so you can tell
10100 if you decrypted them correctly.
10101 - Retry stream correctly when we fail to connect because of
10102 exit-policy-reject (should try another) or can't-resolve-address.
10103 - When we hup a dirserver and we've *removed* a server from the
10104 approved-routers list, now we remove that server from the
10105 in-memory directories too.
10106 - Add bandwidthburst to server descriptor.
10107 - Directories now say which dirserver signed them.
10108 - Use a tor_assert macro that logs failed assertions too.
10109 - Since we don't support truncateds much, don't bother sending them;
10110 just close the circ.
10111 - Fetch randomness from /dev/urandom better (not via fopen/fread)
10112 - Better debugging for tls errors
10113 - Set Content-Type on the directory and hidserv descriptor.
10114 - Remove IVs from cipher code, since AES-ctr has none.
10116 - Fix an assert trigger for exit nodes that's been plaguing us since
10117 the days of 0.0.2prexx (thanks weasel!)
10118 - Fix a bug where we were closing tls connections intermittently.
10119 It turns out openssl keeps its errors around -- so if an error
10120 happens, and you don't ask about it, and then another openssl
10121 operation happens and succeeds, and you ask if there was an error,
10122 it tells you about the first error.
10123 - Fix a bug that's been lurking since 27 may 03 (!)
10124 When passing back a destroy cell, we would use the wrong circ id.
10125 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
10126 - Some versions of openssl have an SSL_pending function that erroneously
10127 returns bytes when there is a non-application record pending.
10128 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
10129 o We were using an array of length zero in a few places.
10130 o Win32's gethostbyname can't resolve an IP to an IP.
10131 o Win32's close can't close a socket.
10132 o Handle windows socket errors correctly.
10134 - check for <sys/limits.h> so we build on FreeBSD again, and
10135 <machine/limits.h> for NetBSD.
10138 Changes in version 0.0.5 - 2004-03-30
10139 o Install torrc as torrc.sample -- we no longer clobber your
10141 o Fix mangled-state bug in directory fetching (was causing sigpipes).
10142 o Only build circuits after we've fetched the directory: clients were
10143 using only the directory servers before they'd fetched a directory.
10144 This also means longer startup time; so it goes.
10145 o Fix an assert trigger where an OP would fail to handshake, and we'd
10146 expect it to have a nickname.
10147 o Work around a tsocks bug: do a socks reject when AP connection dies
10148 early, else tsocks goes into an infinite loop.
10149 o Hold socks connection open until reply is flushed (if possible)
10150 o Make exit nodes resolve IPs to IPs immediately, rather than asking
10151 the dns farm to do it.
10152 o Fix c99 aliasing warnings in rephist.c
10153 o Don't include server descriptors that are older than 24 hours in the
10155 o Give socks 'reject' replies their whole 15s to attempt to flush,
10156 rather than seeing the 60s timeout and assuming the flush had failed.
10157 o Clean automake droppings from the cvs repository
10158 o Add in a 'notice' log level for things the operator should hear
10159 but that aren't warnings
10162 Changes in version 0.0.4 - 2004-03-26
10163 o When connecting to a dirserver or OR and the network is down,
10167 Changes in version 0.0.3 - 2004-03-26
10168 o Warn and fail if server chose a nickname with illegal characters
10169 o Port to Solaris and Sparc:
10170 - include missing header fcntl.h
10171 - have autoconf find -lsocket -lnsl automatically
10172 - deal with hardware word alignment
10173 - make uname() work (solaris has a different return convention)
10174 - switch from using signal() to sigaction()
10175 o Preliminary work on reputation system:
10176 - Keep statistics on success/fail of connect attempts; they're published
10177 by kill -USR1 currently.
10178 - Add a RunTesting option to try to learn link state by creating test
10179 circuits, even when SocksPort is off.
10180 - Remove unused open circuits when there are too many.
10183 Changes in version 0.0.2 - 2004-03-19
10184 - Include strlcpy and strlcat for safer string ops
10185 - define INADDR_NONE so we compile (but still not run) on solaris
10188 Changes in version 0.0.2pre27 - 2004-03-14
10190 - Allow internal tor networks (we were rejecting internal IPs,
10191 now we allow them if they're set explicitly).
10192 - And fix a few endian issues.
10195 Changes in version 0.0.2pre26 - 2004-03-14
10197 - If a stream times out after 15s without a connected cell, don't
10198 try that circuit again: try a new one.
10199 - Retry streams at most 4 times. Then give up.
10200 - When a dirserver gets a descriptor from an unknown router, it
10201 logs its fingerprint (so the dirserver operator can choose to
10202 accept it even without mail from the server operator).
10203 - Inform unapproved servers when we reject their descriptors.
10204 - Make tor build on Windows again. It works as a client, who knows
10206 - Clearer instructions in the torrc for how to set up a server.
10207 - Be more efficient about reading fd's when our global token bucket
10208 (used for rate limiting) becomes empty.
10210 - Stop asserting that computers always go forward in time. It's
10212 - When we sent a cell (e.g. destroy) and then marked an OR connection
10213 expired, we might close it before finishing a flush if the other
10214 side isn't reading right then.
10215 - Don't allow dirservers to start if they haven't defined
10216 RecommendedVersions
10217 - We were caching transient dns failures. Oops.
10218 - Prevent servers from publishing an internal IP as their address.
10219 - Address a strcat vulnerability in circuit.c
10222 Changes in version 0.0.2pre25 - 2004-03-04
10224 - Put the OR's IP in its router descriptor, not its fqdn. That way
10225 we'll stop being stalled by gethostbyname for nodes with flaky dns,
10228 - If the user typed in an address that didn't resolve, the server
10232 Changes in version 0.0.2pre24 - 2004-03-03
10234 - Fix an assertion failure in dns.c, where we were trying to dequeue
10235 a pending dns resolve even if it wasn't pending
10236 - Fix a spurious socks5 warning about still trying to write after the
10237 connection is finished.
10238 - Hold certain marked_for_close connections open until they're finished
10239 flushing, rather than losing bytes by closing them too early.
10240 - Correctly report the reason for ending a stream
10241 - Remove some duplicate calls to connection_mark_for_close
10242 - Put switch_id and start_daemon earlier in the boot sequence, so it
10243 will actually try to chdir() to options.DataDirectory
10244 - Make 'make test' exit(1) if a test fails; fix some unit tests
10245 - Make tor fail when you use a config option it doesn't know about,
10246 rather than warn and continue.
10247 - Make --version work
10248 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
10251 Changes in version 0.0.2pre23 - 2004-02-29
10253 - Print a statement when the first circ is finished, so the user
10254 knows it's working.
10255 - If a relay cell is unrecognized at the end of the circuit,
10256 send back a destroy. (So attacks to mutate cells are more
10258 - New config option 'excludenodes' to avoid certain nodes for circuits.
10259 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
10260 so you can collect coredumps there.
10262 - Fix a bug in tls flushing where sometimes data got wedged and
10263 didn't flush until more data got sent. Hopefully this bug was
10264 a big factor in the random delays we were seeing.
10265 - Make 'connected' cells include the resolved IP, so the client
10266 dns cache actually gets populated.
10267 - Disallow changing from ORPort=0 to ORPort>0 on hup.
10268 - When we time-out on a stream and detach from the circuit, send an
10269 end cell down it first.
10270 - Only warn about an unknown router (in exitnodes, entrynodes,
10271 excludenodes) after we've fetched a directory.
10274 Changes in version 0.0.2pre22 - 2004-02-26
10276 - Servers publish less revealing uname information in descriptors.
10277 - More memory tracking and assertions, to crash more usefully when
10279 - If the default torrc isn't there, just use some default defaults.
10280 Plus provide an internal dirservers file if they don't have one.
10281 - When the user tries to use Tor as an http proxy, give them an http
10282 501 failure explaining that we're a socks proxy.
10283 - Dump a new router.desc on hup, to help confused people who change
10284 their exit policies and then wonder why router.desc doesn't reflect
10286 - Clean up the generic tor.sh init script that we ship with.
10288 - If the exit stream is pending on the resolve, and a destroy arrives,
10289 then the stream wasn't getting removed from the pending list. I
10290 think this was the one causing recent server crashes.
10291 - Use a more robust poll on OSX 10.3, since their poll is flaky.
10292 - When it couldn't resolve any dirservers, it was useless from then on.
10293 Now it reloads the RouterFile (or default dirservers) if it has no
10295 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
10296 many users don't even *have* a /usr/local/sbin/.
10299 Changes in version 0.0.2pre21 - 2004-02-18
10301 - There's a ChangeLog file that actually reflects the changelog.
10302 - There's a 'torify' wrapper script, with an accompanying
10303 tor-tsocks.conf, that simplifies the process of using tsocks for
10304 tor. It even has a man page.
10305 - The tor binary gets installed to sbin rather than bin now.
10306 - Retry streams where the connected cell hasn't arrived in 15 seconds
10307 - Clean up exit policy handling -- get the default out of the torrc,
10308 so we can update it without forcing each server operator to fix
10310 - Allow imaps and pop3s in default exit policy
10312 - Prevent picking middleman nodes as the last node in the circuit
10315 Changes in version 0.0.2pre20 - 2004-01-30
10317 - We now have a deb package, and it's in debian unstable. Go to
10318 it, apt-getters. :)
10319 - I've split the TotalBandwidth option into BandwidthRate (how many
10320 bytes per second you want to allow, long-term) and
10321 BandwidthBurst (how many bytes you will allow at once before the cap
10322 kicks in). This better token bucket approach lets you, say, set
10323 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
10324 performance while not exceeding your monthly bandwidth quota.
10325 - Push out a tls record's worth of data once you've got it, rather
10326 than waiting until you've read everything waiting to be read. This
10327 may improve performance by pipelining better. We'll see.
10328 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
10329 from failed circuits (if they haven't been connected yet) and attach
10331 - Expire old streams that haven't managed to connect. Some day we'll
10332 have them reattach to new circuits instead.
10335 - Fix several memory leaks that were causing servers to become bloated
10337 - Fix a few very rare assert triggers. A few more remain.
10338 - Setuid to User _before_ complaining about running as root.
10341 Changes in version 0.0.2pre19 - 2004-01-07
10343 - Fix deadlock condition in dns farm. We were telling a child to die by
10344 closing the parent's file descriptor to him. But newer children were
10345 inheriting the open file descriptor from the parent, and since they
10346 weren't closing it, the socket never closed, so the child never read
10347 eof, so he never knew to exit. Similarly, dns workers were holding
10348 open other sockets, leading to all sorts of chaos.
10349 - New cleaner daemon() code for forking and backgrounding.
10350 - If you log to a file, it now prints an entry at the top of the
10351 logfile so you know it's working.
10352 - The onionskin challenge length was 30 bytes longer than necessary.
10353 - Started to patch up the spec so it's not quite so out of date.
10356 Changes in version 0.0.2pre18 - 2004-01-02
10358 - Fix endian issues with the 'integrity' field in the relay header.
10359 - Fix a potential bug where connections in state
10360 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
10363 Changes in version 0.0.2pre17 - 2003-12-30
10365 - Made --debuglogfile (or any second log file, actually) work.
10366 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
10367 adversary could force us into an infinite loop.
10370 - Each onionskin handshake now includes a hash of the computed key,
10371 to prove the server's identity and help perfect forward secrecy.
10372 - Changed cell size from 256 to 512 bytes (working toward compatibility
10374 - Changed cell length to 2 bytes, and moved it to the relay header.
10375 - Implemented end-to-end integrity checking for the payloads of
10377 - Separated streamid from 'recognized' (otherwise circuits will get
10378 messed up when we try to have streams exit from the middle). We
10379 use the integrity-checking to confirm that a cell is addressed to
10381 - Randomize the initial circid and streamid values, so an adversary who
10382 breaks into a node can't learn how many circuits or streams have
10386 Changes in version 0.0.2pre16 - 2003-12-14
10388 - Fixed a bug that made HUP trigger an assert
10389 - Fixed a bug where a circuit that immediately failed wasn't being
10390 counted as a failed circuit in counting retries.
10393 - Now we close the circuit when we get a truncated cell: otherwise we're
10394 open to an anonymity attack where a bad node in the path truncates
10395 the circuit and then we open streams at him.
10396 - Add port ranges to exit policies
10397 - Add a conservative default exit policy
10398 - Warn if you're running tor as root
10399 - on HUP, retry OR connections and close/rebind listeners
10400 - options.EntryNodes: try these nodes first when picking the first node
10401 - options.ExitNodes: if your best choices happen to include any of
10402 your preferred exit nodes, you choose among just those preferred
10404 - options.ExcludedNodes: nodes that are never picked in path building
10407 Changes in version 0.0.2pre15 - 2003-12-03
10408 o Robustness and bugfixes:
10409 - Sometimes clients would cache incorrect DNS resolves, which would
10410 really screw things up.
10411 - An OP that goes offline would slowly leak all its sockets and stop
10413 - A wide variety of bugfixes in exit node selection, exit policy
10414 handling, and processing pending streams when a new circuit is
10416 - Pick nodes for a path only from those the directory says are up
10417 - Choose randomly from all running dirservers, not always the first one
10418 - Increase allowed http header size for directory fetch.
10419 - Stop writing to stderr (if we're daemonized it will be closed).
10420 - Enable -g always, so cores will be more useful to me.
10421 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
10424 - Wrote a man page. It lists commonly used options.
10427 - Change default loglevel to warn.
10428 - Make PidFile default to null rather than littering in your CWD.
10429 - OnionRouter config option is now obsolete. Instead it just checks
10431 - Moved to a single unified torrc file for both clients and servers.
10434 Changes in version 0.0.2pre14 - 2003-11-29
10435 o Robustness and bugfixes:
10436 - Force the admin to make the DataDirectory himself
10437 - to get ownership/permissions right
10438 - so clients no longer make a DataDirectory and then never use it
10439 - fix bug where a client who was offline for 45 minutes would never
10440 pull down a directory again
10441 - fix (or at least hide really well) the dns assert bug that was
10442 causing server crashes
10443 - warnings and improved robustness wrt clockskew for certs
10444 - use the native daemon(3) to daemonize, when available
10445 - exit if bind() fails
10446 - exit if neither socksport nor orport is defined
10447 - include our own tor_timegm (Win32 doesn't have its own)
10448 - bugfix for win32 with lots of connections
10449 - fix minor bias in PRNG
10450 - make dirserver more robust to corrupt cached directory
10453 - Wrote the design document (woo)
10455 o Circuit building and exit policies:
10456 - Circuits no longer try to use nodes that the directory has told them
10458 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
10459 bitcounts (18.0.0.0/8).
10460 - Make AP connections standby for a circuit if no suitable circuit
10461 exists, rather than failing
10462 - Circuits choose exit node based on addr/port, exit policies, and
10463 which AP connections are standing by
10464 - Bump min pathlen from 2 to 3
10465 - Relay end cells have a payload to describe why the stream ended.
10466 - If the stream failed because of exit policy, try again with a new
10468 - Clients have a dns cache to remember resolved addresses.
10469 - Notice more quickly when we have no working circuits
10472 - APPort is now called SocksPort
10473 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
10475 - RecommendedVersions is now a config variable rather than
10476 hardcoded (for dirservers)
10477 - Reloads config on HUP
10478 - Usage info on -h or --help
10479 - If you set User and Group config vars, it'll setu/gid to them.
10481 Changes in version 0.0.2pre13 - 2003-10-19
10482 o General stability:
10483 - SSL_write no longer fails when it returns WANTWRITE and the number
10484 of bytes in the buf has changed by the next SSL_write call.
10485 - Fix segfault fetching directory when network is down
10486 - Fix a variety of minor memory leaks
10487 - Dirservers reload the fingerprints file on HUP, so I don't have
10488 to take down the network when I approve a new router
10489 - Default server config file has explicit Address line to specify fqdn
10492 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
10493 - Make listener connections not ever alloc bufs
10495 o Autoconf improvements:
10496 - don't clobber an external CFLAGS in ./configure
10497 - Make install now works
10498 - create var/lib/tor on make install
10499 - autocreate a tor.sh initscript to help distribs
10500 - autocreate the torrc and sample-server-torrc with correct paths
10502 o Log files and Daemonizing now work:
10503 - If --DebugLogFile is specified, log to it at -l debug
10504 - If --LogFile is specified, use it instead of commandline
10505 - If --RunAsDaemon is set, tor forks and backgrounds on startup