1 This document summarizes new features and bugfixes in each stable release
2 of Tor. If you want to see more detailed descriptions of the changes in
3 each development snapshot, see the ChangeLog file.
5 Changes in version 0.2.5.xx - 2014-10-xx
7 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
8 attention for some while. Directory authorities no longer accept
9 descriptors from relays running any version of Tor prior to Tor
10 0.2.3.16-alpha. Resolves ticket 11149.
12 o Major features (client security):
13 - The ntor handshake is now on-by-default, no matter what the
14 directory authorities recommend. Implements ticket 8561.
16 o Major features (other security):
17 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18 today support TLS 1.0 or later, so we can safely turn off support
19 for this old (and insecure) protocol. Fixes bug 13426.
20 - Warn about attempts to run hidden services and relays in the same
21 process: that's probably not a good idea. Closes ticket 12908.
22 - Make the "tor-gencert" tool used by directory authority operators
23 create 2048-bit signing keys by default (rather than 1024-bit, since
24 1024-bit is uncomfortably small these days). Addresses ticket 10324.
26 o Major features (relay security, DoS-resistance):
27 - When deciding whether we have run out of memory and we need to
28 close circuits, also consider memory allocated in buffers for
29 streams attached to each circuit.
31 This change, which extends an anti-DoS feature introduced in
32 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
33 better resist more memory-based DoS attacks than before. Since the
34 MaxMemInCellQueues option now applies to all queues, it is renamed
35 to MaxMemInQueues. This feature fixes bug 10169.
36 - Avoid hash-flooding denial-of-service attacks by using the secure
37 SipHash-2-4 hash function for our hashtables. Without this
38 feature, an attacker could degrade performance of a targeted
39 client or server by flooding their data structures with a large
40 number of entries to be stored at the same hash table position,
41 thereby slowing down the Tor instance. With this feature, hash
42 table positions are derived from a randomized cryptographic key,
43 and an attacker cannot predict which entries will collide. Closes
45 - If you don't specify MaxMemInQueues yourself, Tor now tries to
46 pick a good value based on your total system memory. Previously,
47 the default was always 8 GB. You can still override the default by
48 setting MaxMemInQueues yourself. Resolves ticket 11396.
50 o Major features (bridges and pluggable transports):
51 - Add support for passing arguments to managed pluggable transport
52 proxies. Implements ticket 3594.
53 - Bridges now track GeoIP information and the number of their users
54 even when pluggable transports are in use, and report usage
55 statistics in their extra-info descriptors. Resolves tickets 4773
58 o Major features (bridges):
59 - Don't launch pluggable transport proxies if we don't have any
60 bridges configured that would use them. Now we can list many
61 pluggable transports, and Tor will dynamically start one when it
62 hears a bridge address that needs it. Resolves ticket 5018.
63 - The bridge directory authority now assigns status flags (Stable,
64 Guard, etc) to bridges based on thresholds calculated over all
65 Running bridges. Now bridgedb can finally make use of its features
66 to e.g. include at least one Stable bridge in its answers. Fixes
69 o Major features (controller):
70 - Extend ORCONN controller event to include an "ID" parameter,
71 and add four new controller event types CONN_BW, CIRC_BW,
72 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
73 The new events are emitted in private Tor networks only, with the
74 goal of being able to better track performance and load during
75 full-network simulations. Implements proposal 218 and ticket 7359.
77 o Major features (relay performance):
78 - Speed up server-side lookups of rendezvous and introduction point
79 circuits by using hashtables instead of linear searches. These
80 functions previously accounted between 3 and 7% of CPU usage on
81 some busy relays. Resolves ticket 9841.
82 - Avoid wasting CPU when extending a circuit over a channel that is
83 nearly out of circuit IDs. Previously, we would do a linear scan
84 over possible circuit IDs before finding one or deciding that we
85 had exhausted our possibilities. Now, we try at most 64 random
86 circuit IDs before deciding that we probably won't succeed. Fixes
87 a possible root cause of ticket 11553.
89 o Major features (seccomp2 sandbox, Linux only):
90 - Use the seccomp2 syscall filtering facility on Linux to limit
91 which system calls Tor can invoke. This is an experimental,
92 Linux-only feature to provide defense-in-depth against unknown
93 attacks. To try turning it on, set "Sandbox 1" in your torrc
94 file. Please be ready to report bugs. We hope to add support
95 for better sandboxing in the future, including more fine-grained
96 filters, better division of responsibility, and support for more
97 platforms. This work has been done by Cristian-Matei Toader for
98 Google Summer of Code. Resolves tickets 11351 and 11465.
100 o Major features (testing networks):
101 - Make testing Tor networks bootstrap better: lower directory fetch
102 retry schedules and maximum interval without directory requests,
103 and raise maximum download tries. Implements ticket 6752.
104 - Add make target 'test-network' to run tests on a Chutney network.
105 Implements ticket 8530.
107 o Major features (other):
108 - On some platforms (currently: recent OSX versions, glibc-based
109 platforms that support the ELF format, and a few other
110 Unix-like operating systems), Tor can now dump stack traces
111 when a crash occurs or an assertion fails. By default, traces
112 are dumped to stderr (if possible) and to any logs that are
113 reporting errors. Implements ticket 9299.
115 o Major bugfixes (security, directory authorities):
116 - Directory authorities now include a digest of each relay's
117 identity key as a part of its microdescriptor.
119 This is a workaround for bug 11743 (reported by "cypherpunks"),
120 where Tor clients do not support receiving multiple
121 microdescriptors with the same SHA256 digest in the same
122 consensus. When clients receive a consensus like this, they only
123 use one of the relays. Without this fix, a hostile relay could
124 selectively disable some client use of target relays by
125 constructing a router descriptor with a different identity and the
126 same microdescriptor parameters and getting the authorities to
127 list it in a microdescriptor consensus. This fix prevents an
128 attacker from causing a microdescriptor collision, because the
129 router's identity is not forgeable.
131 o Major bugfixes (client):
132 - Perform circuit cleanup operations even when circuit
133 construction operations are disabled (because the network is
134 disabled, or because there isn't enough directory information).
135 Previously, when we were not building predictive circuits, we
136 were not closing expired circuits either. Fixes bug 8387; bugfix on
137 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
138 became more strict about when we have "enough directory information
141 o Major bugfixes (client, pluggable transports):
142 - When managing pluggable transports, use OS notification facilities
143 to learn if they have crashed, and don't attempt to kill any
144 process that has already exited. Fixes bug 8746; bugfix
147 o Major bugfixes (relay denial of service):
148 - Instead of writing destroy cells directly to outgoing connection
149 buffers, queue them and intersperse them with other outgoing cells.
150 This can prevent a set of resource starvation conditions where too
151 many pending destroy cells prevent data cells from actually getting
152 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
153 bugfix on 0.2.0.1-alpha.
155 o Major bugfixes (relay):
156 - Avoid queuing or sending destroy cells for circuit ID zero when we
157 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
158 Found and fixed by "cypherpunks".
159 - Fix ORPort reachability detection on relays running behind a
160 proxy, by correctly updating the "local" mark on the controlling
161 channel when changing the address of an or_connection_t after the
162 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
163 - Use a direct dirport connection when uploading non-anonymous
164 descriptors to the directory authorities. Previously, relays would
165 incorrectly use tunnel connections under a fairly wide variety of
166 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
167 - When a circuit accidentally has the same circuit ID for its
168 forward and reverse direction, correctly detect the direction of
169 cells using that circuit. Previously, this bug made roughly one
170 circuit in a million non-functional. Fixes bug 12195; this is a
171 bugfix on every version of Tor.
173 o Minor features (security):
174 - New --enable-expensive-hardening option to enable security
175 hardening options that consume nontrivial amounts of CPU and
176 memory. Right now, this includes AddressSanitizer and UbSan, which
177 are supported in newer versions of GCC and Clang. Closes ticket
179 - Authorities now assign the Guard flag to the fastest 25% of the
180 network (it used to be the fastest 50%). Also raise the consensus
181 weight that guarantees the Guard flag from 250 to 2000. For the
182 current network, this results in about 1100 guards, down from 2500.
183 This step paves the way for moving the number of entry guards
184 down to 1 (proposal 236) while still providing reasonable expected
185 performance for most users. Implements ticket 12690.
187 o Minor features (security, memory management):
188 - Memory allocation tricks (mempools and buffer freelists) are now
189 disabled by default. You can turn them back on with
190 --enable-mempools and --enable-buf-freelists respectively. We're
191 disabling these features because malloc performance is good enough
192 on most platforms, and a similar feature in OpenSSL exacerbated
193 exploitation of the Heartbleed attack. Resolves ticket 11476.
195 o Minor features (bridge client):
196 - Report a more useful failure message when we can't connect to a
197 bridge because we don't have the right pluggable transport
198 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
200 o Minor features (bridge):
201 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
202 cookie file for the ExtORPort g+r by default.
204 o Minor features (bridges, pluggable transports):
205 - Bridges now write the SHA1 digest of their identity key
206 fingerprint (that is, a hash of a hash of their public key) to
207 notice-level logs, and to a new hashed-fingerprint file. This
208 information will help bridge operators look up their bridge in
209 Globe and similar tools. Resolves ticket 10884.
210 - Improve the message that Tor displays when running as a bridge
211 using pluggable transports without an Extended ORPort listener.
212 Also, log the message in the log file too. Resolves ticket 11043.
213 - Add threshold cutoffs to the networkstatus document created by
214 the Bridge Authority. Fixes bug 1117.
215 - On Windows, spawn background processes using the CREATE_NO_WINDOW
216 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
217 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
218 Vidalia set this option for us.) Implements ticket 10297.
220 o Minor features (build):
221 - The configure script has a --disable-seccomp option to turn off
222 support for libseccomp on systems that have it, in case it (or
223 Tor's use of it) is broken. Resolves ticket 11628.
224 - Assume that a user using ./configure --host wants to cross-compile,
225 and give an error if we cannot find a properly named
226 tool-chain. Add a --disable-tool-name-check option to proceed
227 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
228 - If we run ./configure and the compiler recognizes -fstack-protector
229 but the linker rejects it, warn the user about a potentially missing
230 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
231 - Add support for `--library-versions` flag. Implements ticket 6384.
232 - Return the "unexpected sendme" warnings to a warn severity, but make
233 them rate limited, to help diagnose ticket 8093.
234 - Detect a missing asciidoc, and warn the user about it, during
235 configure rather than at build time. Fixes issue 6506. Patch from
238 o Minor features (client):
239 - Add a new option, PredictedPortsRelevanceTime, to control how long
240 after having received a request to connect to a given port Tor
241 will try to keep circuits ready in anticipation of future requests
242 for that port. Patch from "unixninja92"; implements ticket 9176.
244 o Minor features (config options and command line):
245 - Add an --allow-missing-torrc commandline option that tells Tor to
246 run even if the configuration file specified by -f is not available.
247 Implements ticket 10060.
248 - Add support for the TPROXY transparent proxying facility on Linux.
249 See documentation for the new TransProxyType option for more
250 details. Implementation by "thomo". Closes ticket 10582.
252 o Minor features (config options):
253 - Config (torrc) lines now handle fingerprints which are missing
254 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
255 - Support a --dump-config option to print some or all of the
256 configured options. Mainly useful for debugging the command-line
257 option parsing code. Helps resolve ticket 4647.
258 - Raise awareness of safer logging: notify user of potentially
259 unsafe config options, like logging more verbosely than severity
260 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
261 - Add a new configuration option TestingV3AuthVotingStartOffset
262 that bootstraps a network faster by changing the timing for
263 consensus votes. Addresses ticket 8532.
264 - Add a new torrc option "ServerTransportOptions" that allows
265 bridge operators to pass configuration parameters to their
266 pluggable transports. Resolves ticket 8929.
267 - The config (torrc) file now accepts bandwidth and space limits in
268 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
269 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
272 o Minor features (controller):
273 - Make the entire exit policy available from the control port via
274 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
276 - Because of the fix for ticket 11396, the real limit for memory
277 usage may no longer match the configured MaxMemInQueues value. The
278 real limit is now exposed via GETINFO limits/max-mem-in-queues.
279 - Add a new "HS_DESC" controller event that reports activities
280 related to hidden service descriptors. Resolves ticket 8510.
281 - New "DROPGUARDS" controller command to forget all current entry
282 guards. Not recommended for ordinary use, since replacing guards
283 too frequently makes several attacks easier. Resolves ticket 9934;
285 - Implement the TRANSPORT_LAUNCHED control port event that
286 notifies controllers about new launched pluggable
287 transports. Resolves ticket 5609.
289 o Minor features (diagnostic):
290 - When logging a warning because of bug 7164, additionally check the
291 hash table for consistency (as proposed on ticket 11737). This may
292 help diagnose bug 7164.
293 - When we log a heartbeat, log how many one-hop circuits we have
294 that are at least 30 minutes old, and log status information about
295 a few of them. This is an attempt to track down bug 8387.
296 - When encountering an unexpected CR while writing text to a file on
297 Windows, log the name of the file. Should help diagnosing
299 - Give more specific warnings when a client notices that an onion
300 handshake has failed. Fixes ticket 9635.
301 - Add significant new logging code to attempt to diagnose bug 12184,
302 where relays seem to run out of available circuit IDs.
303 - Improve the diagnostic log message for bug 8387 even further to
304 try to improve our odds of figuring out why one-hop directory
305 circuits sometimes do not get closed.
306 - Add more log messages to diagnose bug 7164, which causes
307 intermittent "microdesc_free() called but md was still referenced"
308 warnings. We now include more information, to figure out why we
309 might be cleaning a microdescriptor for being too old if it's
310 still referenced by a live node_t object.
311 - Log current accounting state (bytes sent and received + remaining
312 time for the current accounting period) in the relay's heartbeat
313 message. Implements ticket 5526; patch from Peter Retzlaff.
315 o Minor features (geoip):
316 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
319 o Minor features (interface):
320 - Generate a warning if any ports are listed in the SocksPolicy,
321 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
322 AuthDirBadExit options. (These options only support address
323 ranges.) Fixes part of ticket 11108.
325 o Minor features (kernel API usage):
326 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
327 sockets in a single system call. Implements ticket 5129.
329 o Minor features (log messages):
330 - When ServerTransportPlugin is set on a bridge, Tor can write more
331 useful statistics about bridge use in its extrainfo descriptors,
332 but only if the Extended ORPort ("ExtORPort") is set too. Add a
333 log message to inform the user in this case. Resolves ticket 9651.
334 - When receiving a new controller connection, log the origin address.
335 Resolves ticket 9698; patch from "sigpipe".
336 - When logging OpenSSL engine status at startup, log the status of
337 more engines. Fixes ticket 10043; patch from Joshua Datko.
339 o Minor features (log verbosity):
340 - Demote the message that we give when a flushing connection times
341 out for too long from NOTICE to INFO. It was usually meaningless.
342 Resolves ticket 5286.
343 - Don't log so many notice-level bootstrapping messages at startup
344 about downloading descriptors. Previously, we'd log a notice
345 whenever we learned about more routers. Now, we only log a notice
346 at every 5% of progress. Fixes bug 9963.
347 - Warn less verbosely when receiving a malformed
348 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
350 o Minor features (performance):
351 - If we're using the pure-C 32-bit curve25519_donna implementation
352 of curve25519, build it with the -fomit-frame-pointer option to
353 make it go faster on register-starved hosts. This improves our
354 handshake performance by about 6% on i386 hosts without nacl.
357 o Minor features (relay):
358 - If a circuit timed out for at least 3 minutes, check if we have a
359 new external IP address, and publish a new descriptor with the new
360 IP address if it changed. Resolves ticket 2454.
362 o Minor features (testing):
363 - If Python is installed, "make check" now runs extra tests beyond
364 the unit test scripts.
365 - When bootstrapping a test network, sometimes very few relays get
366 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
367 specify a set of relays which should be voted Guard regardless of
368 their uptime or bandwidth. Addresses ticket 9206.
370 o Minor features (transparent proxy, *BSD):
371 - Support FreeBSD's ipfw firewall interface for TransPort ports on
372 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
373 10267; patch from "yurivict".
374 - Support OpenBSD's divert-to rules with the pf firewall for
375 transparent proxy ports. To enable it, set "TransProxyType
376 pf-divert". This allows Tor to run a TransPort transparent proxy
377 port on OpenBSD 4.4 or later without root privileges. See the
378 pf.conf(5) manual page for information on configuring pf to use
379 divert-to rules. Closes ticket 10896; patch from Dana Koch.
381 o Minor bugfixes (bridge client):
382 - Stop accepting bridge lines containing hostnames. Doing so would
383 cause clients to perform DNS requests on the hostnames, which was
384 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
386 o Minor bugfixes (bridges):
387 - Avoid potential crashes or bad behavior when launching a
388 server-side managed proxy with ORPort or ExtORPort temporarily
389 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
390 - Fix a bug where the first connection works to a bridge that uses a
391 pluggable transport with client-side parameters, but we don't send
392 the client-side parameters on subsequent connections. (We don't
393 use any pluggable transports with client-side parameters yet,
394 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
395 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
397 o Minor bugfixes (build, auxiliary programs):
398 - Stop preprocessing the "torify" script with autoconf, since
399 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
401 - The tor-fw-helper program now follows the standard convention and
402 exits with status code "0" on success. Fixes bug 9030; bugfix on
403 0.2.3.1-alpha. Patch by Arlo Breault.
404 - Corrected ./configure advice for what openssl dev package you should
405 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
407 o Minor bugfixes (client):
408 - Avoid "Tried to open a socket with DisableNetwork set" warnings
409 when starting a client with bridges configured and DisableNetwork
410 set. (Tor launcher starts Tor with DisableNetwork set the first
411 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
412 - Improve the log message when we can't connect to a hidden service
413 because all of the hidden service directory nodes hosting its
414 descriptor are excluded. Improves on our fix for bug 10722, which
415 was a bugfix on 0.2.0.10-alpha.
416 - Raise a control port warning when we fail to connect to all of
417 our bridges. Previously, we didn't inform the controller, and
418 the bootstrap process would stall. Fixes bug 11069; bugfix on
420 - Exit immediately when a process-owning controller exits.
421 Previously, tor relays would wait for a little while after their
422 controller exited, as if they had gotten an INT signal -- but this
423 was problematic, since there was no feedback for the user. To do a
424 clean shutdown, controllers should send an INT signal and give Tor
425 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
426 - Stop attempting to connect to bridges before our pluggable
427 transports are configured (harmless but resulted in some erroneous
428 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
429 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
430 generating incorrect SOCKS5 responses, and confusing client
431 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
433 o Minor bugfixes (client, DNSPort):
434 - When using DNSPort, try to respond to AAAA requests with AAAA
435 answers. Previously, we hadn't looked at the request type when
436 deciding which answer type to prefer. Fixes bug 10468; bugfix on
438 - When receiving a DNS query for an unsupported record type, reply
439 with no answer rather than with a NOTIMPL error. This behavior
440 isn't correct either, but it will break fewer client programs, we
441 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
444 o Minor bugfixes (client, logging during bootstrap):
445 - Only report the first fatal bootstrap error on a given OR
446 connection. This stops us from telling the controller bogus error
447 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
448 - Avoid generating spurious warnings when starting with
449 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
452 o Minor bugfixes (closing OR connections):
453 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
454 check if it's an or_connection_t and correctly call
455 connection_or_close_for_error() rather than
456 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
458 - When closing all connections on setting DisableNetwork to 1, use
459 connection_or_close_normally() rather than closing OR connections
460 out from under the channel layer. Fixes bug 11306; bugfix on
463 o Minor bugfixes (code correctness):
464 - Previously we used two temporary files when writing descriptors to
465 disk; now we only use one. Fixes bug 1376.
466 - Remove an erroneous (but impossible and thus harmless) pointer
467 comparison that would have allowed compilers to skip a bounds
468 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
469 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
470 - Fix an always-true assertion in pluggable transports code so it
471 actually checks what it was trying to check. Fixes bug 10046;
472 bugfix on 0.2.3.9-alpha. Found by "dcb".
474 o Minor bugfixes (command line):
475 - Use a single command-line parser for parsing torrc options on the
476 command line and for finding special command-line options to avoid
477 inconsistent behavior for torrc option arguments that have the same
478 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
480 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
481 9573; bugfix on 0.0.9pre5.
483 o Minor bugfixes (compilation):
484 - Compile correctly with builds and forks of OpenSSL (such as
485 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
486 0.2.1.1-alpha. Patch from "dhill".
487 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
488 turned off (that is, without support for v2 link handshakes). Fixes
489 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
490 - In routerlist_assert_ok(), don't take the address of a
491 routerinfo's cache_info member unless that routerinfo is non-NULL.
492 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
493 - Fix a large number of false positive warnings from the clang
494 analyzer static analysis tool. This should make real warnings
495 easier for clang analyzer to find. Patch from "teor". Closes
497 - Resolve GCC complaints on OpenBSD about discarding constness in
498 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
499 on 0.1.1.23. Patch from Dana Koch.
500 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
501 treatment of long and time_t as comparable types. Fixes part of
502 bug 11633. Patch from Dana Koch.
503 - When deciding whether to build the 64-bit curve25519
504 implementation, detect platforms where we can compile 128-bit
505 arithmetic but cannot link it. Fixes bug 11729; bugfix on
506 0.2.4.8-alpha. Patch from "conradev".
507 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
508 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
509 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
511 - Build and run correctly on systems like OpenBSD-current that have
512 patched OpenSSL to remove get_cipher_by_char and/or its
513 implementations. Fixes issue 13325.
515 o Minor bugfixes (controller and command-line):
516 - If changing a config option via "setconf" fails in a recoverable
517 way, we used to nonetheless write our new control ports to the
518 file described by the "ControlPortWriteToFile" option. Now we only
519 write out that file if we successfully switch to the new config
520 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
522 o Minor bugfixes (Directory server):
523 - No longer accept malformed http headers when parsing urls from
524 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
526 - When sending a compressed set of descriptors or microdescriptors,
527 make sure to finalize the zlib stream. Previously, we would write
528 all the compressed data, but if the last descriptor we wanted to
529 send was missing or too old, we would not mark the stream as
530 finished. This caused problems for decompression tools. Fixes bug
531 11648; bugfix on 0.1.1.23.
533 o Minor bugfixes (hidden service):
534 - Only retry attempts to connect to a chosen rendezvous point 8
535 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
537 o Minor bugfixes (interface):
538 - Reject relative control socket paths and emit a warning. Previously,
539 single-component control socket paths would be rejected, but Tor
540 would not log why it could not validate the config. Fixes bug 9258;
541 bugfix on 0.2.3.16-alpha.
543 o Minor bugfixes (log messages):
544 - Fix a bug where clients using bridges would report themselves
545 as 50% bootstrapped even without a live consensus document.
546 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
547 - Suppress a warning where, if there's only one directory authority
548 in the network, we would complain that votes and signatures cannot
549 be uploaded to other directory authorities. Fixes bug 10842;
550 bugfix on 0.2.2.26-beta.
551 - Report bootstrapping progress correctly when we're downloading
552 microdescriptors. We had updated our "do we have enough microdescs
553 to begin building circuits?" logic most recently in 0.2.4.10-alpha
554 (see bug 5956), but we left the bootstrap status event logic at
555 "how far through getting 1/4 of them are we?" Fixes bug 9958;
556 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
558 o Minor bugfixes (logging):
559 - Downgrade "Unexpected onionskin length after decryption" warning
560 to a protocol-warn, since there's nothing relay operators can do
561 about a client that sends them a malformed create cell. Resolves
562 bug 12996; bugfix on 0.0.6rc1.
563 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
564 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
565 - When logging information about an EXTEND2 or EXTENDED2 cell, log
566 their names correctly. Fixes part of bug 12700; bugfix
568 - When logging information about a relay cell whose command we don't
569 recognize, log its command as an integer. Fixes part of bug 12700;
570 bugfix on 0.2.1.10-alpha.
571 - Escape all strings from the directory connection before logging
572 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
573 - Squelch a spurious LD_BUG message "No origin circuit for
574 successful SOCKS stream" in certain hidden service failure cases;
576 - Downgrade the severity of the 'unexpected sendme cell from client'
577 from 'warn' to 'protocol warning'. Closes ticket 8093.
579 o Minor bugfixes (misc code correctness):
580 - In munge_extrainfo_into_routerinfo(), check the return value of
581 memchr(). This would have been a serious issue if we ever passed
582 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
584 - On the chance that somebody manages to build Tor on a
585 platform where time_t is unsigned, correct the way that
586 microdesc_add_to_cache() handles negative time arguments.
587 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
588 - Fix various instances of undefined behavior in channeltls.c,
589 tor_memmem(), and eventdns.c that would cause us to construct
590 pointers to memory outside an allocated object. (These invalid
591 pointers were not accessed, but C does not even allow them to
592 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
593 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
594 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
595 fix some miscellaneous errors in our tests and codebase. Fixes bug
596 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
597 - Always check return values for unlink, munmap, UnmapViewOfFile;
598 check strftime return values more often. In some cases all we can
599 do is report a warning, but this may help prevent deeper bugs from
600 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
602 - Fix numerous warnings from the clang "scan-build" static analyzer.
603 Some of these are programming style issues; some of them are false
604 positives that indicated awkward code; some are undefined behavior
605 cases related to constructing (but not using) invalid pointers;
606 some are assumptions about API behavior; some are (harmlessly)
607 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
608 correct; and one or two are genuine bugs that weren't reachable
609 from the rest of the program. Fixes bug 8793; bugfixes on many,
612 o Minor bugfixes (node selection):
613 - If ExcludeNodes is set, consider non-excluded hidden service
614 directory servers before excluded ones. Do not consider excluded
615 hidden service directory servers at all if StrictNodes is
616 set. (Previously, we would sometimes decide to connect to those
617 servers, and then realize before we initiated a connection that
618 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
620 - If we set the ExitNodes option but it doesn't include any nodes
621 that have the Exit flag, we would choose not to bootstrap. Now we
622 bootstrap so long as ExitNodes includes nodes which can exit to
623 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
625 o Minor bugfixes (performance):
626 - Avoid a bug where every successful connection made us recompute
627 the flag telling us whether we have sufficient information to
628 build circuits. Previously, we would forget our cached value
629 whenever we successfully opened a channel (or marked a router as
630 running or not running for any other reason), regardless of
631 whether we had previously believed the router to be running. This
632 forced us to run an expensive update operation far too often.
633 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
634 - Avoid using tor_memeq() for checking relay cell integrity. This
635 removes a possible performance bottleneck. Fixes part of bug
636 12169; bugfix on 0.2.1.31.
638 o Minor bugfixes (platform-specific):
639 - When dumping a malformed directory object to disk, save it in
640 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
642 - Don't report failures from make_socket_reuseable() on incoming
643 sockets on OSX: this can happen when incoming connections close
644 early. Fixes bug 10081.
646 o Minor bugfixes (pluggable transports):
647 - Avoid another 60-second delay when starting Tor in a pluggable-
648 transport-using configuration when we already have cached
649 descriptors for our bridges. Fixes bug 11965; bugfix
652 o Minor bugfixes (protocol correctness):
653 - When receiving a VERSIONS cell with an odd number of bytes, close
654 the connection immediately since the cell is malformed. Fixes bug
655 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
658 o Minor bugfixes (relay, other):
659 - We now drop CREATE cells for already-existent circuit IDs and for
660 zero-valued circuit IDs, regardless of other factors that might
661 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
663 - When rejecting DATA cells for stream_id zero, still count them
664 against the circuit's deliver window so that we don't fail to send
665 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
667 o Minor bugfixes (relay, threading):
668 - Check return code on spawn_func() in cpuworker code, so that we
669 don't think we've spawned a nonworking cpuworker and write junk to
670 it forever. Fix related to bug 4345; bugfix on all released Tor
671 versions. Found by "skruffy".
672 - Use a pthread_attr to make sure that spawn_func() cannot return an
673 error while at the same time launching a thread. Fix related to
674 bug 4345; bugfix on all released Tor versions. Reported
677 o Minor bugfixes (relays and bridges):
678 - Avoid crashing on a malformed resolv.conf file when running a
679 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
680 - Non-exit relays no longer launch mock DNS requests to check for
681 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
682 non-exit relays stopped servicing DNS requests. Fixes bug 965;
683 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
684 - Bridges now report complete directory request statistics. Related
685 to bug 5824; bugfix on 0.2.2.1-alpha.
686 - Bridges now never collect statistics that were designed for
687 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
689 o Minor bugfixes (testing):
690 - Fix all valgrind warnings produced by the unit tests. There were
691 over a thousand memory leak warnings previously, mostly produced
692 by forgetting to free things in the unit test code. Fixes bug
693 11618, bugfixes on many versions of Tor.
695 o Minor bugfixes (tools):
696 - Disable the sandbox name resolver cache when running tor-resolve:
697 tor-resolve doesn't use the sandbox code, and turning it on was
698 breaking attempts to do tor-resolve on a non-default server on
699 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
701 o Minor bugfixes (tor-fw-helper):
702 - Give a correct log message when tor-fw-helper fails to launch.
703 (Previously, we would say something like "tor-fw-helper sent us a
704 string we could not parse".) Fixes bug 9781; bugfix
707 o Minor bugfixes (trivial memory leaks):
708 - Fix a small memory leak when signing a directory object. Fixes bug
709 11275; bugfix on 0.2.4.13-alpha.
710 - Resolve some memory leaks found by coverity in the unit tests, on
711 exit in tor-gencert, and on a failure to compute digests for our
712 own keys when generating a v3 networkstatus vote. These leaks
713 should never have affected anyone in practice.
715 o Code simplification and refactoring:
716 - Remove some old fallback code designed to keep Tor clients working
717 in a network with only two working relays. Elsewhere in the code we
718 have long since stopped supporting such networks, so there wasn't
719 much point in keeping it around. Addresses ticket 9926.
720 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
721 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
722 - Extract the common duplicated code for creating a subdirectory
723 of the data directory and writing to a file in it. Fixes ticket
724 4282; patch from Peter Retzlaff.
725 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
726 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
727 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
728 - Add a set of accessor functions for the circuit timeout data
729 structure. Fixes ticket 6153; patch from "piet".
730 - Clean up exit paths from connection_listener_new(). Closes ticket
731 8789. Patch from Arlo Breault.
732 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
733 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
734 - Use a doubly-linked list to implement the global circuit list.
735 Resolves ticket 9108. Patch from Marek Majkowski.
736 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
737 - Remove constants and tests for PKCS1 padding; it's insecure and
738 shouldn't be used for anything new. Fixes bug 8792; patch
740 - Remove instances of strcpy() from the unit tests. They weren't
741 hurting anything, since they were only in the unit tests, but it's
742 embarassing to have strcpy() in the code at all, and some analysis
743 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
744 0.2.3.8-alpha. Patch from Arlo Breault.
745 - Remove is_internal_IP() function. Resolves ticket 4645.
746 - Remove unused function circuit_dump_by_chan from circuitlist.c.
747 Closes issue 9107; patch from "marek".
748 - Change our use of the ENUM_BF macro to avoid declarations that
750 - Get rid of router->address, since in all cases it was just the
751 string representation of router->addr. Resolves ticket 5528.
754 - Adjust the URLs in the README to refer to the new locations of
755 several documents on the website. Fixes bug 12830. Patch from
757 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
759 - Update manpage to describe some of the files you can expect to
760 find in Tor's DataDirectory. Addresses ticket 9839.
761 - Clean up several option names in the manpage to match their real
762 names, add the missing documentation for a couple of testing and
763 directory authority options, remove the documentation for a
764 V2-directory fetching option that no longer exists. Resolves
766 - Correct the documenation so that it lists the correct directory
767 for the stats files. (They are in a subdirectory called "stats",
769 - In the manpage, move more authority-only options into the
770 directory authority section so that operators of regular directory
771 caches don't get confused.
772 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
773 11061; bugfix on 0.2.4.7-alpha.
774 - Resolve warnings from Doxygen.
775 - Document in the manpage that "KBytes" may also be written as
776 "kilobytes" or "KB", that "Kbits" may also be written as
777 "kilobits", and so forth. Closes ticket 9222.
778 - Document that the ClientOnly config option overrides ORPort.
779 Our old explanation made ClientOnly sound as though it did
780 nothing at all. Resolves bug 9059.
781 - Explain that SocksPolicy, DirPolicy, and similar options don't
782 take port arguments. Fixes the other part of ticket 11108.
783 - Fix a comment about the rend_server_descriptor_t.protocols field
784 to more accurately describe its range. Also, make that field
785 unsigned, to more accurately reflect its usage. Fixes bug 9099;
786 bugfix on 0.2.1.5-alpha.
787 - Fix the manpage's description of HiddenServiceAuthorizeClient:
788 the maximum client name length is 16, not 19. Fixes bug 11118;
789 bugfix on 0.2.1.6-alpha.
792 - The contrib directory has been sorted and tidied. Before, it was
793 an unsorted dumping ground for useful and not-so-useful things.
794 Now, it is divided based on functionality, and the items which
795 seemed to be nonfunctional or useless have been removed. Resolves
796 ticket 8966; based on patches from "rl1987".
798 o Removed code and features:
799 - Clients now reject any directory authority certificates lacking
800 a dir-key-crosscert element. These have been included since
801 0.2.1.9-alpha, so there's no real reason for them to be optional
802 any longer. Completes proposal 157. Resolves ticket 10162.
803 - Remove all code that existed to support the v2 directory system,
804 since there are no longer any v2 directory authorities. Resolves
806 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
807 options, which were used for designating authorities as "Hidden
808 service authorities". There has been no use of hidden service
809 authorities since 0.2.2.1-alpha, when we stopped uploading or
810 downloading v0 hidden service descriptors. Fixes bug 10881; also
811 part of a fix for bug 10841.
812 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
813 and MTBF calculations, but that nobody was using. Fixes bug 11742.
814 - The TunnelDirConns and PreferTunnelledDirConns options no longer
815 exist; tunneled directory connections have been available since
816 0.1.2.5-alpha, and turning them off is not a good idea. This is a
817 brute-force fix for 10849, where "TunnelDirConns 0" would break
819 - Remove all code for the long unused v1 directory protocol.
820 Resolves ticket 11070.
821 - Remove all remaining code related to version-0 hidden service
822 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
823 the rest of bug 10841.
824 - Remove migration code from when we renamed the "cached-routers"
825 file to "cached-descriptors" back in 0.2.0.8-alpha. This
826 incidentally resolves ticket 6502 by cleaning up the related code
827 a bit. Patch from Akshay Hebbar.
829 o Test infrastructure:
830 - Tor now builds each source file in two modes: a mode that avoids
831 exposing identifiers needlessly, and another mode that exposes
832 more identifiers for testing. This lets the compiler do better at
833 optimizing the production code, while enabling us to take more
834 radical measures to let the unit tests test things.
835 - The production builds no longer include functions used only in
836 the unit tests; all functions exposed from a module only for
837 unit-testing are now static in production builds.
838 - Add an --enable-coverage configuration option to make the unit
839 tests (and a new src/or/tor-cov target) to build with gcov test
841 - Update to the latest version of tinytest.
842 - Improve the tinytest implementation of string operation tests so
843 that comparisons with NULL strings no longer crash the tests; they
844 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
845 - New macros in test.h to simplify writing mock-functions for unit
846 tests. Part of ticket 11507. Patch from Dana Koch.
847 - We now have rudimentary function mocking support that our unit
848 tests can use to test functions in isolation. Function mocking
849 lets the tests temporarily replace a function's dependencies with
850 stub functions, so that the tests can check the function without
851 invoking the other functions it calls.
854 - Complete tests for the status.c module. Resolves ticket 11507.
855 Patch from Dana Koch.
856 - Add more unit tests for the <circid,channel>->circuit map, and
857 the destroy-cell-tracking code to fix bug 7912.
858 - Unit tests for failing cases of the TAP onion handshake.
859 - More unit tests for address-manipulation functions.
861 o Distribution (systemd):
862 - Include a tor.service file in contrib/dist for use with systemd.
863 Some distributions will be able to use this file unmodified;
864 others will need to tweak it, or write their own. Patch from Jamie
865 Nguyen; resolves ticket 8368.
866 - Verify configuration file via ExecStartPre in the systemd unit
867 file. Patch from intrigeri; resolves ticket 12730.
868 - Explicitly disable RunAsDaemon in the systemd unit file. Our
869 current systemd unit uses "Type = simple", so systemd does not
870 expect tor to fork. If the user has "RunAsDaemon 1" in their
871 torrc, then things won't work as expected. This is e.g. the case
872 on Debian (and derivatives), since there we pass "--defaults-torrc
873 /usr/share/tor/tor-service-defaults-torrc" (that contains
874 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
878 Changes in version 0.2.4.24 - 2014-09-22
879 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
880 connecting to hidden services, and it updates the location of one of
881 the directory authorities.
884 - Clients now send the correct address for their chosen rendezvous
885 point when trying to access a hidden service. They used to send
886 the wrong address, which would still work some of the time because
887 they also sent the identity digest of the rendezvous point, and if
888 the hidden service happened to try connecting to the rendezvous
889 point from a relay that already had a connection open to it,
890 the relay would reuse that connection. Now connections to hidden
891 services should be more robust and faster. Also, this bug meant
892 that clients were leaking to the hidden service whether they were
893 on a little-endian (common) or big-endian (rare) system, which for
894 some users might have reduced their anonymity. Fixes bug 13151;
895 bugfix on 0.2.1.5-alpha.
897 o Directory authority changes:
898 - Change IP address for gabelmoo (v3 directory authority).
900 o Minor features (geoip):
901 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
905 Changes in version 0.2.4.23 - 2014-07-28
906 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
907 guard rotation, and also backports several important fixes from the
908 Tor 0.2.5 alpha release series.
911 - Clients now look at the "usecreatefast" consensus parameter to
912 decide whether to use CREATE_FAST or CREATE cells for the first hop
913 of their circuit. This approach can improve security on connections
914 where Tor's circuit handshake is stronger than the available TLS
915 connection security levels, but the tradeoff is more computational
916 load on guard relays. Implements proposal 221. Resolves ticket 9386.
917 - Make the number of entry guards configurable via a new
918 NumEntryGuards consensus parameter, and the number of directory
919 guards configurable via a new NumDirectoryGuards consensus
920 parameter. Implements ticket 12688.
923 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
924 implementation that caused incorrect results on 32-bit
925 implementations when certain malformed inputs were used along with
926 a small class of private ntor keys. This bug does not currently
927 appear to allow an attacker to learn private keys or impersonate a
928 Tor server, but it could provide a means to distinguish 32-bit Tor
929 implementations from 64-bit Tor implementations. Fixes bug 12694;
930 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
934 - Warn and drop the circuit if we receive an inbound 'relay early'
935 cell. Those used to be normal to receive on hidden service circuits
936 due to bug 1038, but the buggy Tor versions are long gone from
937 the network so we can afford to resume watching for them. Resolves
938 the rest of bug 1038; bugfix on 0.2.1.19.
939 - Correct a confusing error message when trying to extend a circuit
940 via the control protocol but we don't know a descriptor or
941 microdescriptor for one of the specified relays. Fixes bug 12718;
942 bugfix on 0.2.3.1-alpha.
943 - Avoid an illegal read from stack when initializing the TLS
944 module using a version of OpenSSL without all of the ciphers
945 used by the v2 link handshake. Fixes bug 12227; bugfix on
946 0.2.4.8-alpha. Found by "starlight".
949 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
953 Changes in version 0.2.4.22 - 2014-05-16
954 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
955 alpha release series. These include blocking all authority signing
956 keys that may have been affected by the OpenSSL "heartbleed" bug,
957 choosing a far more secure set of TLS ciphersuites by default, closing
958 a couple of memory leaks that could be used to run a target relay out
959 of RAM, and several others.
961 o Major features (security, backport from 0.2.5.4-alpha):
962 - Block authority signing keys that were used on authorities
963 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
964 don't have any evidence that these keys _were_ compromised; we're
965 doing this to be prudent.) Resolves ticket 11464.
967 o Major bugfixes (security, OOM):
968 - Fix a memory leak that could occur if a microdescriptor parse
969 fails during the tokenizing step. This bug could enable a memory
970 exhaustion attack by directory servers. Fixes bug 11649; bugfix
973 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
974 - The relay ciphersuite list is now generated automatically based on
975 uniform criteria, and includes all OpenSSL ciphersuites with
976 acceptable strength and forward secrecy. Previously, we had left
977 some perfectly fine ciphersuites unsupported due to omission or
978 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
979 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
980 - Relays now trust themselves to have a better view than clients of
981 which TLS ciphersuites are better than others. (Thanks to bug
982 11513, the relay list is now well-considered, whereas the client
983 list has been chosen mainly for anti-fingerprinting purposes.)
984 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
985 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
986 AES128. Resolves ticket 11528.
987 - Clients now try to advertise the same list of ciphersuites as
988 Firefox 28. This change enables selection of (fast) GCM
989 ciphersuites, disables some strange old ciphers, and stops
990 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
991 Resolves ticket 11438.
993 o Minor bugfixes (configuration, security):
994 - When running a hidden service, do not allow TunneledDirConns 0:
995 trying to set that option together with a hidden service would
996 otherwise prevent the hidden service from running, and also make
997 it publish its descriptors directly over HTTP. Fixes bug 10849;
998 bugfix on 0.2.1.1-alpha.
1000 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1001 - Avoid sending a garbage value to the controller when a circuit is
1002 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1004 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1005 - Stop leaking memory when we successfully resolve a PTR record.
1006 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1008 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1009 - Avoid 60-second delays in the bootstrapping process when Tor is
1010 launching for a second time while using bridges. Fixes bug 9229;
1011 bugfix on 0.2.0.3-alpha.
1013 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
1014 - Give the correct URL in the warning message when trying to run a
1015 relay on an ancient version of Windows. Fixes bug 9393.
1017 o Minor bugfixes (compilation):
1018 - Fix a compilation error when compiling with --disable-curve25519.
1019 Fixes bug 9700; bugfix on 0.2.4.17-rc.
1022 - Downgrade the warning severity for the the "md was still
1023 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
1024 for trying to diagnose this bug, and the current warning in
1025 earlier versions of tor achieves nothing useful. Addresses warning
1028 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
1029 - When we run out of usable circuit IDs on a channel, log only one
1030 warning for the whole channel, and describe how many circuits
1031 there were on the channel. Fixes part of ticket 11553.
1033 o Minor features (security, backport from 0.2.5.4-alpha):
1034 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
1035 leave the default at 8GBytes), to better support Raspberry Pi
1036 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
1038 o Documentation (backport from 0.2.5.4-alpha):
1039 - Correctly document that we search for a system torrc file before
1040 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1044 Changes in version 0.2.4.21 - 2014-02-28
1045 Tor 0.2.4.21 further improves security against potential adversaries who
1046 find breaking 1024-bit crypto doable, and backports several stability
1047 and robustness patches from the 0.2.5 branch.
1049 o Major features (client security):
1050 - When we choose a path for a 3-hop circuit, make sure it contains
1051 at least one relay that supports the NTor circuit extension
1052 handshake. Otherwise, there is a chance that we're building
1053 a circuit that's worth attacking by an adversary who finds
1054 breaking 1024-bit crypto doable, and that chance changes the game
1055 theory. Implements ticket 9777.
1058 - Do not treat streams that fail with reason
1059 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1060 since it could also indicate an ENETUNREACH connection error. Fixes
1061 part of bug 10777; bugfix on 0.2.4.8-alpha.
1063 o Code simplification and refactoring:
1064 - Remove data structures which were introduced to implement the
1065 CellStatistics option: they are now redundant with the new timestamp
1066 field in the regular packed_cell_t data structure, which we did
1067 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
1070 - Always clear OpenSSL bignums before freeing them -- even bignums
1071 that don't contain secrets. Resolves ticket 10793. Patch by
1073 - Build without warnings under clang 3.4. (We have some macros that
1074 define static functions only some of which will get used later in
1075 the module. Starting with clang 3.4, these give a warning unless the
1076 unused attribute is set on them.) Resolves ticket 10904.
1077 - Update geoip and geoip6 files to the February 7 2014 Maxmind
1078 GeoLite2 Country database.
1081 - Set the listen() backlog limit to the largest actually supported
1082 on the system, not to the value in a header file. Fixes bug 9716;
1083 bugfix on every released Tor.
1084 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1085 exit node as a NOROUTE error, not an INTERNAL error, since they
1086 can apparently happen when trying to connect to the wrong sort
1087 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1088 - Fix build warnings about missing "a2x" comment when building the
1089 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1090 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1091 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1092 not entirely remove it from the connection lists. Fixes bug 9602;
1093 bugfix on 0.2.4.4-alpha.
1094 - Fix a segmentation fault in our benchmark code when running with
1095 Fedora's OpenSSL package, or any other OpenSSL that provides
1096 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1097 - Turn "circuit handshake stats since last time" log messages into a
1098 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1100 o Documentation fixes:
1101 - Document that all but one DirPort entry must have the NoAdvertise
1102 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1105 Changes in version 0.2.4.20 - 2013-12-22
1106 Tor 0.2.4.20 fixes potentially poor random number generation for users
1107 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
1108 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
1109 and 4) have no state file in their DataDirectory (as would happen on
1110 first start). Users who generated relay or hidden service identity
1111 keys in such a situation should discard them and generate new ones.
1113 This release also fixes a logic error that caused Tor clients to build
1114 many more preemptive circuits than they actually need.
1117 - Do not allow OpenSSL engines to replace the PRNG, even when
1118 HardwareAccel is set. The only default builtin PRNG engine uses
1119 the Intel RDRAND instruction to replace the entire PRNG, and
1120 ignores all attempts to seed it with more entropy. That's
1121 cryptographically stupid: the right response to a new alleged
1122 entropy source is never to discard all previously used entropy
1123 sources. Fixes bug 10402; works around behavior introduced in
1124 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1126 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1127 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1128 - Avoid launching spurious extra circuits when a stream is pending.
1129 This fixes a bug where any circuit that _wasn't_ unusable for new
1130 streams would be treated as if it were, causing extra circuits to
1131 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1134 - Avoid a crash bug when starting with a corrupted microdescriptor
1135 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1136 - If we fail to dump a previously cached microdescriptor to disk, avoid
1137 freeing duplicate data later on. Fixes bug 10423; bugfix on
1138 0.2.4.13-alpha. Spotted by "bobnomnom".
1141 Changes in version 0.2.4.19 - 2013-12-11
1142 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
1143 (1986-2013). Aaron worked on diverse projects including helping to guide
1144 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
1145 transparency to the U.S government's PACER documents, and contributing
1146 design and development for Tor and Tor2Web. Aaron was one of the latest
1147 martyrs in our collective fight for civil liberties and human rights,
1148 and his death is all the more painful because he was one of us.
1150 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
1151 a new circuit handshake and link encryption that use ECC to provide
1152 better security and efficiency; makes relays better manage circuit
1153 creation requests; uses "directory guards" to reduce client enumeration
1154 risks; makes bridges collect and report statistics about the pluggable
1155 transports they support; cleans up and improves our geoip database;
1156 gets much closer to IPv6 support for clients, bridges, and relays; makes
1157 directory authorities use measured bandwidths rather than advertised
1158 ones when computing flags and thresholds; disables client-side DNS
1159 caching to reduce tracking risks; and fixes a big bug in bridge
1160 reachability testing. This release introduces two new design
1161 abstractions in the code: a new "channel" abstraction between circuits
1162 and or_connections to allow for implementing alternate relay-to-relay
1163 transports, and a new "circuitmux" abstraction storing the queue of
1164 circuits for a channel. The release also includes many stability,
1165 security, and privacy fixes.
1167 o Major features (new circuit handshake):
1168 - Tor now supports a new circuit extension handshake designed by Ian
1169 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
1170 circuit extension handshake, later called "TAP", was a bit slow
1171 (especially on the relay side), had a fragile security proof, and
1172 used weaker keys than we'd now prefer. The new circuit handshake
1173 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
1174 function, making it significantly more secure than the older
1175 handshake, and significantly faster. Tor can use one of two built-in
1176 pure-C curve25519-donna implementations by Adam Langley, or it
1177 can link against the "nacl" library for a tuned version if present.
1179 The built-in version is very fast for 64-bit systems when building
1180 with GCC. The built-in 32-bit version is still faster than the
1181 old TAP protocol, but using libnacl is better on most such hosts.
1183 Implements proposal 216; closes ticket 7202.
1185 o Major features (better link encryption):
1186 - Relays can now enable the ECDHE TLS ciphersuites when available
1187 and appropriate. These ciphersuites let us negotiate forward-secure
1188 TLS secret keys more safely and more efficiently than with our
1189 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1190 public relays prefer the (faster) P224 group, and bridges prefer
1191 the (more common) P256 group; you can override this with the
1194 This feature requires clients running 0.2.3.17-beta or later,
1195 and requires both sides to be running OpenSSL 1.0.0 or later
1196 with ECC support. OpenSSL 1.0.1, with the compile-time option
1197 "enable-ec_nistp_64_gcc_128", is highly recommended.
1199 Implements the relay side of proposal 198; closes ticket 7200.
1201 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1202 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1203 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1204 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1205 them to solve bug 6033.)
1207 o Major features (relay performance):
1208 - Instead of limiting the number of queued onionskins (aka circuit
1209 create requests) to a fixed, hard-to-configure number, we limit
1210 the size of the queue based on how many we expect to be able to
1211 process in a given amount of time. We estimate the time it will
1212 take to process an onionskin based on average processing time
1213 of previous onionskins. Closes ticket 7291. You'll never have to
1214 configure MaxOnionsPending again.
1215 - Relays process the new "NTor" circuit-level handshake requests
1216 with higher priority than the old "TAP" circuit-level handshake
1217 requests. We still process some TAP requests to not totally starve
1218 0.2.3 clients when NTor becomes popular. A new consensus parameter
1219 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1220 Implements ticket 9574.
1222 o Major features (client bootstrapping resilience):
1223 - Add a new "FallbackDir" torrc option to use when we can't use
1224 a directory mirror from the consensus (either because we lack a
1225 consensus, or because they're all down). Currently, all authorities
1226 are fallbacks by default, and there are no other default fallbacks,
1227 but that will change. This option will allow us to give clients a
1228 longer list of servers to try to get a consensus from when first
1229 connecting to the Tor network, and thereby reduce load on the
1230 directory authorities. Implements proposal 206, "Preconfigured
1231 directory sources for bootstrapping". We also removed the old
1232 "FallbackNetworkstatus" option, since we never got it working well
1233 enough to use it. Closes bug 572.
1234 - If we have no circuits open, use a relaxed timeout (the
1235 95th-percentile cutoff) until a circuit succeeds. This heuristic
1236 should allow Tor to succeed at building circuits even when the
1237 network connection drastically changes. Should help with bug 3443.
1239 o Major features (use of guards):
1240 - Support directory guards (proposal 207): when possible, clients now
1241 use their entry guards for non-anonymous directory requests. This
1242 can help prevent client enumeration. Note that this behavior only
1243 works when we have a usable consensus directory, and when options
1244 about what to download are more or less standard. In the future we
1245 should re-bootstrap from our guards, rather than re-bootstrapping
1246 from the preconfigured list of directory sources that ships with
1247 Tor. Resolves ticket 6526.
1248 - Raise the default time that a client keeps an entry guard from
1249 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1250 2012 paper. (We would make it even longer, but we need better client
1251 load balancing first.) Also, make the guard lifetime controllable
1252 via a new GuardLifetime torrc option and a GuardLifetime consensus
1253 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1255 o Major features (bridges with pluggable transports):
1256 - Bridges now report the pluggable transports they support to the
1257 bridge authority, so it can pass the supported transports on to
1258 bridgedb and/or eventually do reachability testing. Implements
1260 - Automatically forward the TCP ports of pluggable transport
1261 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1264 o Major features (geoip database):
1265 - Maxmind began labelling Tor relays as being in country "A1",
1266 which breaks by-country node selection inside Tor. Now we use a
1267 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1268 file with real country codes. This script fixes about 90% of "A1"
1269 entries automatically and uses manual country code assignments to
1270 fix the remaining 10%. See src/config/README.geoip for details.
1272 - Add GeoIP database for IPv6 addresses. The new config option
1274 - Update to the October 2 2013 Maxmind GeoLite Country database.
1276 o Major features (IPv6):
1277 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1278 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1279 to happen. Implements ticket 5535.
1280 - All kind of relays, not just bridges, can now advertise an IPv6
1281 OR port. Implements ticket 6362.
1282 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
1283 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1284 exit policy reads as you would like: the address * applies to all
1285 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1286 addresses only. On the client side, you'll need to wait for enough
1287 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
1288 and use Socks5. Closes ticket 5547, implements proposal 117 as
1289 revised in proposal 208.
1290 - Bridge authorities now accept IPv6 bridge addresses and include
1291 them in network status documents. Implements ticket 5534.
1292 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
1294 o Major features (directory authorities):
1295 - Directory authorities now prefer using measured bandwidths to
1296 advertised ones when computing flags and thresholds. Resolves
1298 - Directory authorities that vote measured bandwidths about more
1299 than a threshold number of relays now treat relays with
1300 unmeasured bandwidths as having bandwidth 0 when computing their
1301 flags. Resolves ticket 8435.
1302 - Directory authorities now support a new consensus method (17)
1303 where they cap the published bandwidth of relays for which
1304 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1305 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1306 serve any v2 directory information. Now we can test disabling the
1307 old deprecated v2 directory format, and see whether doing so has
1308 any effect on network load. Begins to fix bug 6783.
1310 o Major features (build and portability):
1311 - Switch to a nonrecursive Makefile structure. Now instead of each
1312 Makefile.am invoking other Makefile.am's, there is a master
1313 Makefile.am that includes the others. This change makes our build
1314 process slightly more maintainable, and improves parallelism for
1315 building with make -j. Original patch by Stewart Smith; various
1316 fixes by Jim Meyering.
1317 - Where available, we now use automake's "silent" make rules by
1318 default, so that warnings are easier to spot. You can get the old
1319 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1320 - Resume building correctly with MSVC and Makefile.nmake. This patch
1321 resolves numerous bugs and fixes reported by ultramage, including
1322 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1324 o Security features:
1325 - Switch to a completely time-invariant approach for picking nodes
1326 weighted by bandwidth. Our old approach would run through the
1327 part of the loop after it had made its choice slightly slower
1328 than it ran through the part of the loop before it had made its
1329 choice. Addresses ticket 6538.
1330 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1331 by tor2web clients allows hidden services to identify tor2web
1332 clients through their repeated selection of the same rendezvous
1333 and introduction point circuit endpoints (their guards). Resolves
1336 o Major bugfixes (relay denial of service):
1337 - When we have too much memory queued in circuits (according to a new
1338 MaxMemInCellQueues option), close the circuits that have the oldest
1339 queued cells, on the theory that those are most responsible for
1340 us running low on memory. This prevents us from running out of
1341 memory as a relay if circuits fill up faster than they can be
1342 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
1343 Tor. This bug is a further fix beyond bug 6252, whose fix was
1344 merged into 0.2.3.21-rc.
1345 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1346 ID: these could be used to create unexpected streams and circuits
1347 which would count as "present" to some parts of Tor but "absent"
1348 to others, leading to zombie circuits and streams or to a bandwidth
1349 denial-of-service. Fixes bug 7889; bugfix on every released version
1350 of Tor. Reported by "oftc_must_be_destroyed".
1351 - Avoid a bug where our response to TLS renegotiation under certain
1352 network conditions could lead to a busy-loop, with 100% CPU
1353 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1355 o Major bugfixes (asserts, crashes, leaks):
1356 - Prevent the get_freelists() function from running off the end of
1357 the list of freelists if it somehow gets an unrecognized
1358 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1360 - Avoid a memory leak where we would leak a consensus body when we
1361 find that a consensus which we couldn't previously verify due to
1362 missing certificates is now verifiable. Fixes bug 8719; bugfix
1364 - If we are unable to save a microdescriptor to the journal, do not
1365 drop it from memory and then reattempt downloading it. Fixes bug
1366 9645; bugfix on 0.2.2.6-alpha.
1367 - Fix an assertion failure that would occur when disabling the
1368 ORPort setting on a running Tor process while accounting was
1369 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1370 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1371 when an exit connection with optimistic data succeeds immediately
1372 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1374 - Fix a memory leak that would occur whenever a configuration
1375 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1377 o Major bugfixes (relay rate limiting):
1378 - When a TLS write is partially successful but incomplete, remember
1379 that the flushed part has been flushed, and notice that bytes were
1380 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
1381 bugfix on Tor 0.1.0.5-rc.
1382 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1383 to 1GB/1GB. The previous defaults were intended to be "basically
1384 infinite", but it turns out they're now limiting our 100mbit+
1385 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1386 last time we raised it).
1387 - No longer stop reading or writing on cpuworker connections when
1388 our rate limiting buckets go empty. Now we should handle circuit
1389 handshake requests more promptly. Resolves bug 9731.
1391 o Major bugfixes (client-side privacy):
1392 - When we mark a circuit as unusable for new circuits, have it
1393 continue to be unusable for new circuits even if MaxCircuitDirtiness
1394 is increased too much at the wrong time, or the system clock jumps
1395 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1396 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1397 which have resolved to internal addresses") is set, apply that
1398 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1399 - When an exit relay rejects a stream with reason "exit policy", but
1400 we only know an exit policy summary (e.g. from the microdesc
1401 consensus) for it, do not mark the relay as useless for all exiting.
1402 Instead, mark just the circuit as unsuitable for that particular
1403 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1405 o Major bugfixes (stream isolation):
1406 - Allow applications to get proper stream isolation with
1407 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1408 username/password authentication also offer "no authentication". Tor
1409 had previously preferred "no authentication", so the applications
1410 never actually sent Tor their auth details. Now Tor selects
1411 username/password authentication if it's offered. You can disable
1412 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1413 bug 8117; bugfix on 0.2.3.3-alpha.
1414 - Follow the socks5 protocol when offering username/password
1415 authentication. The fix for bug 8117 exposed this bug, and it
1416 turns out real-world applications like Pidgin do care. Bugfix on
1417 0.2.3.2-alpha; fixes bug 8879.
1419 o Major bugfixes (client circuit building):
1420 - Alter circuit build timeout measurement to start at the point
1421 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1422 initialization). This should make our timeout measurements more
1423 uniform. Previously, we were sometimes including ORconn setup time
1424 in our circuit build time measurements. Should resolve bug 3443.
1425 - If the circuit build timeout logic is disabled (via the consensus,
1426 or because we are an authority), then don't build testing circuits.
1427 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1429 o Major bugfixes (client-side DNS):
1430 - Turn off the client-side DNS cache by default. Updating and using
1431 the DNS cache is now configurable on a per-client-port
1432 level. SOCKSPort, DNSPort, etc lines may now contain
1433 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1434 cache these types of DNS answers when we receive them from an
1435 exit node in response to an application request on this port, and
1436 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1437 cached DNS answers of these types, we shouldn't use them. It's
1438 potentially risky to use cached DNS answers at the client, since
1439 doing so can indicate to one exit what answers we've gotten
1440 for DNS lookups in the past. With IPv6, this becomes especially
1441 problematic. Using cached DNS answers for requests on the same
1442 circuit would present less linkability risk, since all traffic
1443 on a circuit is already linkable, but it would also provide
1444 little performance benefit: the exit node caches DNS replies
1445 too. Implements a simplified version of Proposal 205. Implements
1448 o Major bugfixes (hidden service privacy):
1449 - Limit hidden service descriptors to at most ten introduction
1450 points, to slow one kind of guard enumeration. Fixes bug 9002;
1451 bugfix on 0.1.1.11-alpha.
1453 o Major bugfixes (directory fetching):
1454 - If the time to download the next old-style networkstatus is in
1455 the future, do not decline to consider whether to download the
1456 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1458 - We used to always request authority certificates by identity digest,
1459 meaning we'd get the newest one even when we wanted one with a
1460 different signing key. Then we would complain about being given
1461 a certificate we already had, and never get the one we really
1462 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1463 resource to request the one we want. Fixes bug 5595; bugfix on
1466 o Major bugfixes (bridge reachability):
1467 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1468 previously they did not, which prevented them from receiving
1469 successful connections from relays for self-test or bandwidth
1470 testing. Also, when a relay is extending a circuit to a bridge,
1471 it needs to send a NETINFO cell, even when the bridge hasn't sent
1472 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1474 o Major bugfixes (control interface):
1475 - When receiving a new configuration file via the control port's
1476 LOADCONF command, do not treat the defaults file as absent.
1477 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1479 o Major bugfixes (directory authorities):
1480 - Stop marking every relay as having been down for one hour every
1481 time we restart a directory authority. These artificial downtimes
1482 were messing with our Stable and Guard flag calculations. Fixes
1483 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1484 - When computing directory thresholds, ignore any rejected-as-sybil
1485 nodes during the computation so that they can't influence Fast,
1486 Guard, etc. (We should have done this for proposal 109.) Fixes
1488 - When marking a node as a likely sybil, reset its uptime metrics
1489 to zero, so that it cannot time towards getting marked as Guard,
1490 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1492 - Fix a bug in the voting algorithm that could yield incorrect results
1493 when a non-naming authority declared too many flags. Fixes bug 9200;
1494 bugfix on 0.2.0.3-alpha.
1496 o Internal abstraction features:
1497 - Introduce new channel_t abstraction between circuits and
1498 or_connection_t to allow for implementing alternate OR-to-OR
1499 transports. A channel_t is an abstract object which can either be a
1500 cell-bearing channel, which is responsible for authenticating and
1501 handshaking with the remote OR and transmitting cells to and from
1502 it, or a listening channel, which spawns new cell-bearing channels
1503 at the request of remote ORs. Implements part of ticket 6465.
1504 - Make a channel_tls_t subclass of channel_t, adapting it to the
1505 existing or_connection_t code. The V2/V3 protocol handshaking
1506 code which formerly resided in command.c has been moved below the
1507 channel_t abstraction layer and may be found in channeltls.c now.
1508 Implements the rest of ticket 6465.
1509 - Introduce new circuitmux_t storing the queue of circuits for
1510 a channel; this encapsulates and abstracts the queue logic and
1511 circuit selection policy, and allows the latter to be overridden
1512 easily by switching out a policy object. The existing EWMA behavior
1513 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1515 o New build requirements:
1516 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1517 strongly recommended.
1518 - Tor maintainers now require Automake version 1.9 or later to build
1519 Tor from the Git repository. (Automake is not required when building
1520 from a source distribution.)
1522 o Minor features (protocol):
1523 - No longer include the "opt" prefix when generating routerinfos
1524 or v2 directories: it has been needless since Tor 0.1.2. Closes
1526 - Reject EXTEND cells sent to nonexistent streams. According to the
1527 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1528 we were only checking for stream IDs that were currently in use.
1529 Found while hunting for more instances of bug 6271. Bugfix on
1530 0.0.2pre8, which introduced incremental circuit construction.
1531 - Tor relays and clients now support a better CREATE/EXTEND cell
1532 format, allowing the sender to specify multiple address, identity,
1533 and handshake types. Implements Robert Ransom's proposal 200;
1535 - Reject as invalid most directory objects containing a NUL.
1536 Belt-and-suspender fix for bug 8037.
1538 o Minor features (security):
1539 - Clear keys and key-derived material left on the stack in
1540 rendservice.c and rendclient.c. Check return value of
1541 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
1542 These fixes should make us more forward-secure against cold-boot
1543 attacks and the like. Fixes bug 2385.
1544 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1545 Irix's random() only return 15 bits; Solaris's random() returns more
1546 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1547 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1549 o Minor features (control protocol):
1550 - Add a "GETINFO signal/names" control port command. Implements
1552 - Provide default values for all options via "GETINFO config/defaults".
1553 Implements ticket 4971.
1554 - Allow an optional $ before the node identity digest in the
1555 controller command GETINFO ns/id/<identity>, for consistency with
1556 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1557 - Add CACHED keyword to ADDRMAP events in the control protocol
1558 to indicate whether a DNS result will be cached or not. Resolves
1560 - Generate bootstrapping status update events correctly when fetching
1561 microdescriptors. Fixes bug 9927.
1563 o Minor features (path selection):
1564 - When deciding whether we have enough descriptors to build circuits,
1565 instead of looking at raw relay counts, look at which fraction
1566 of (bandwidth-weighted) paths we're able to build. This approach
1567 keeps clients from building circuits if their paths are likely to
1568 stand out statistically. The default fraction of paths needed is
1569 taken from the consensus directory; you can override it with the
1570 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1571 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1572 and we have GeoIP information, also exclude all nodes with unknown
1573 countries "??" and "A1". This behavior is controlled by the
1574 new GeoIPExcludeUnknown option: you can make such nodes always
1575 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1576 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1577 gets you the default behavior. Implements feature 7706.
1579 o Minor features (hidden services):
1580 - Improve circuit build timeout handling for hidden services.
1581 In particular: adjust build timeouts more accurately depending
1582 upon the number of hop-RTTs that a particular circuit type
1583 undergoes. Additionally, launch intro circuits in parallel
1584 if they timeout, and take the first one to reply as valid.
1585 - The Tor client now ignores sub-domain components of a .onion
1586 address. This change makes HTTP "virtual" hosting
1587 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1588 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1589 hosted on the same hidden service. Implements proposal 204.
1590 - Enable Tor to read configuration, state, and key information from
1591 a FIFO. Previously Tor would only read from files with a positive
1592 stat.st_size. Code from meejah; fixes bug 6044.
1594 o Minor features (clients):
1595 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
1596 microdescriptor-related dir requests, and only fall back to normal
1597 descriptors if none of their bridges can handle microdescriptors
1598 (as opposed to the fix in ticket 4013, which caused them to fall
1599 back to normal descriptors if *any* of their bridges preferred
1600 them). Resolves ticket 4994.
1601 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1602 TCP ports to forward. In the past it only accepted two ports:
1603 the ORPort and the DirPort.
1605 o Minor features (protecting client timestamps):
1606 - Clients no longer send timestamps in their NETINFO cells. These were
1607 not used for anything, and they provided one small way for clients
1608 to be distinguished from each other as they moved from network to
1609 network or behind NAT. Implements part of proposal 222.
1610 - Clients now round timestamps in INTRODUCE cells down to the nearest
1611 10 minutes. If a new Support022HiddenServices option is set to 0, or
1612 if it's set to "auto" and the feature is disabled in the consensus,
1613 the timestamp is sent as 0 instead. Implements part of proposal 222.
1614 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1615 a big deal from a security point of view, but it achieves no actual
1616 good purpose, and isn't needed. Implements part of proposal 222.
1617 - Reduce down accuracy of timestamps in hidden service descriptors.
1618 Implements part of proposal 222.
1620 o Minor features (bridges):
1621 - Make bridge relays check once a minute for whether their IP
1622 address has changed, rather than only every 15 minutes. Resolves
1624 - Bridge statistics now count bridge clients connecting over IPv6:
1625 bridge statistics files now list "bridge-ip-versions" and
1626 extra-info documents list "geoip6-db-digest". The control protocol
1627 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1628 implementation by "shkoo", addressing ticket 5055.
1629 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1630 operators select the address where their pluggable transports will
1631 listen for connections. Resolves ticket 7013.
1632 - Randomize the lifetime of our SSL link certificate, so censors can't
1633 use the static value for filtering Tor flows. Resolves ticket 8443;
1634 related to ticket 4014 which was included in 0.2.2.33.
1636 o Minor features (relays):
1637 - Option OutboundBindAddress can be specified multiple times and
1638 accepts IPv6 addresses. Resolves ticket 6876.
1640 o Minor features (IPv6, client side):
1641 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1642 prefer to hand out virtual IPv6 addresses, since there are more of
1643 them and we can't run out. To override this behavior and make IPv4
1644 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1645 or DNSPort you're using for resolving. Implements ticket 7571.
1646 - AutomapHostsOnResolve responses are now randomized, to avoid
1647 annoying situations where Tor is restarted and applications
1648 connect to the wrong addresses.
1649 - Never try more than 1000 times to pick a new virtual address when
1650 AutomapHostsOnResolve is set. That's good enough so long as we
1651 aren't close to handing out our entire virtual address space;
1652 if you're getting there, it's best to switch to IPv6 virtual
1655 o Minor features (IPv6, relay/authority side):
1656 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1657 authorities should set if they have IPv6 connectivity and want to
1658 do reachability tests for IPv6 relays. Implements feature 5974.
1659 - A relay with an IPv6 OR port now sends that address in NETINFO
1660 cells (in addition to its other address). Implements ticket 6364.
1662 o Minor features (directory authorities):
1663 - Directory authorities no long accept descriptors for any version of
1664 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1665 These versions are insecure, unsupported, or both. Implements
1667 - When directory authorities are computing thresholds for flags,
1668 never let the threshold for the Fast flag fall below 4096
1669 bytes. Also, do not consider nodes with extremely low bandwidths
1670 when deciding thresholds for various directory flags. This change
1671 should raise our threshold for Fast relays, possibly in turn
1672 improving overall network performance; see ticket 1854. Resolves
1674 - Directory authorities now include inside each vote a statement of
1675 the performance thresholds they used when assigning flags.
1676 Implements ticket 8151.
1677 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1678 in directory authority votes to describe whether they have enough
1679 measured bandwidths to ignore advertised (relay descriptor)
1680 bandwidth claims. Resolves ticket 8711.
1682 o Minor features (path bias detection):
1683 - Path Use Bias: Perform separate accounting for successful circuit
1684 use. Keep separate statistics on stream attempt rates versus stream
1685 success rates for each guard. Provide configurable thresholds to
1686 determine when to emit log messages or disable use of guards that
1687 fail too many stream attempts. Resolves ticket 7802.
1688 - Create three levels of Path Bias log messages, as opposed to just
1689 two. These are configurable via consensus as well as via the torrc
1690 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1691 The default values are 0.70, 0.50, and 0.30 respectively.
1692 - Separate the log message levels from the decision to drop guards,
1693 which also is available via torrc option PathBiasDropGuards.
1694 PathBiasDropGuards still defaults to 0 (off).
1695 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1696 in combination with PathBiasExtremeRate.
1697 - Increase the default values for PathBiasScaleThreshold and
1698 PathBiasCircThreshold from (200, 20) to (300, 150).
1699 - Add in circuit usage accounting to path bias. If we try to use a
1700 built circuit but fail for any reason, it counts as path bias.
1701 Certain classes of circuits where the adversary gets to pick your
1702 destination node are exempt from this accounting. Usage accounting
1703 can be specifically disabled via consensus parameter or torrc.
1704 - Convert all internal path bias state to double-precision floating
1705 point, to avoid roundoff error and other issues.
1706 - Only record path bias information for circuits that have completed
1707 *two* hops. Assuming end-to-end tagging is the attack vector, this
1708 makes us more resilient to ambient circuit failure without any
1709 detection capability loss.
1711 o Minor features (build):
1712 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1713 dhill. Resolves ticket 6982.
1714 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1716 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1717 separate error codes; or at least, don't break for that reason.
1718 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1720 o Build improvements (autotools):
1721 - Warn if building on a platform with an unsigned time_t: there
1722 are too many places where Tor currently assumes that time_t can
1723 hold negative values. We'd like to fix them all, but probably
1725 - Do not report status verbosely from autogen.sh unless the -v flag
1726 is specified. Fixes issue 4664. Patch from Onizuka.
1727 - Detect and reject attempts to build Tor with threading support
1728 when OpenSSL has been compiled without threading support.
1730 - Try to detect if we are ever building on a platform where
1731 memset(...,0,...) does not set the value of a double to 0.0. Such
1732 platforms are permitted by the C standard, though in practice
1733 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
1734 currently support them, but it's better to detect them and fail
1735 than to perform erroneously.
1736 - We no longer warn so much when generating manpages from their
1738 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1739 the signs of types during autoconf. This is better than our old
1740 approach, which didn't work when cross-compiling.
1742 o Minor features (log messages, warnings):
1743 - Detect when we're running with a version of OpenSSL other than the
1744 one we compiled with. This conflict has occasionally given people
1745 hard-to-track-down errors.
1746 - Warn users who run hidden services on a Tor client with
1747 UseEntryGuards disabled that their hidden services will be
1748 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1749 attack which motivated Tor to support entry guards in the first
1750 place). Resolves ticket 6889.
1751 - Warn when we are binding low ports when hibernation is enabled;
1752 previously we had warned when we were _advertising_ low ports with
1753 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1754 - Issue a warning when running with the bufferevents backend enabled.
1755 It's still not stable, and people should know that they're likely
1756 to hit unexpected problems. Closes ticket 9147.
1758 o Minor features (log messages, notices):
1759 - Refactor resolve_my_address() so it returns the method by which we
1760 decided our public IP address (explicitly configured, resolved from
1761 explicit hostname, guessed from interfaces, learned by gethostname).
1762 Now we can provide more helpful log messages when a relay guesses
1763 its IP address incorrectly (e.g. due to unexpected lines in
1764 /etc/hosts). Resolves ticket 2267.
1765 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1766 and how many we complete, and log it every hour to help relay
1767 operators follow trends in network load. Addresses ticket 9658.
1769 o Minor features (log messages, diagnostics):
1770 - If we fail to free a microdescriptor because of bug 7164, log
1771 the filename and line number from which we tried to free it.
1772 - We compute the overhead from passing onionskins back and forth to
1773 cpuworkers, and report it when dumping statistics in response to
1774 SIGUSR1. Supports ticket 7291.
1775 - Add another diagnostic to the heartbeat message: track and log
1776 overhead that TLS is adding to the data we write. If this is
1777 high, we are sending too little data to SSL_write at a time.
1778 Diagnostic for bug 7707.
1779 - Log packaged cell fullness as part of the heartbeat message.
1780 Diagnosis to try to determine the extent of bug 7743.
1781 - Add more detail to a log message about relaxed timeouts, to help
1783 - When learning a fingerprint for a bridge, log its corresponding
1784 transport type. Implements ticket 7896.
1785 - Warn more aggressively when flushing microdescriptors to a
1786 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1787 or at least make it more diagnosable.
1788 - Improve the log message when "Bug/attack: unexpected sendme cell
1789 from client" occurs, to help us track bug 8093.
1790 - Improve debugging output to help track down bug 8185 ("Bug:
1791 outgoing relay cell has n_chan==NULL. Dropping.")
1793 o Minor features (log messages, quieter bootstrapping):
1794 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1795 versions and capabilities when everything is going right. Resolves
1796 part of ticket 6736.
1797 - Omit the first heartbeat log message, because it never has anything
1798 useful to say, and it clutters up the bootstrapping messages.
1799 Resolves ticket 6758.
1800 - Don't log about reloading the microdescriptor cache at startup. Our
1801 bootstrap warnings are supposed to tell the user when there's a
1802 problem, and our bootstrap notices say when there isn't. Resolves
1803 ticket 6759; bugfix on 0.2.2.6-alpha.
1804 - Don't log "I learned some more directory information" when we're
1805 reading cached directory information. Reserve it for when new
1806 directory information arrives in response to a fetch. Resolves
1808 - Don't complain about bootstrapping problems while hibernating.
1809 These complaints reflect a general code problem, but not one
1810 with any problematic effects (no connections are actually
1811 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1813 o Minor features (testing):
1814 - In our testsuite, create temporary directories with a bit more
1815 entropy in their name to make name collisions less likely. Fixes
1817 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1818 (P-256) Diffie-Hellman handshakes to src/or/bench.
1819 - Add benchmark functions to test onion handshake performance.
1822 - The DirServer option is now DirAuthority, for consistency with
1823 current naming patterns. You can still use the old DirServer form.
1825 o Minor bugfixes (protocol):
1826 - Fix the handling of a TRUNCATE cell when it arrives while the
1827 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1828 - When a Tor client gets a "truncated" relay cell, the first byte of
1829 its payload specifies why the circuit was truncated. We were
1830 ignoring this 'reason' byte when tearing down the circuit, resulting
1831 in the controller not being told why the circuit closed. Now we
1832 pass the reason from the truncated cell to the controller. Bugfix
1833 on 0.1.2.3-alpha; fixes bug 7039.
1834 - Fix a misframing issue when reading the version numbers in a
1835 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1836 'version 1, version 2, and version 0x100', when it should have
1837 only included versions 1 and 2. Fixes bug 8059; bugfix on
1838 0.2.0.10-alpha. Reported pseudonymously.
1839 - Make the format and order of STREAM events for DNS lookups
1840 consistent among the various ways to launch DNS lookups. Fixes
1841 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
1843 o Minor bugfixes (syscalls and disk interaction):
1844 - Always check the return values of functions fcntl() and
1845 setsockopt(). We don't believe these are ever actually failing in
1846 practice, but better safe than sorry. Also, checking these return
1847 values should please analysis tools like Coverity. Patch from
1848 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1849 - Avoid double-closing the listener socket in our socketpair()
1850 replacement (used on Windows) in the case where the addresses on
1851 our opened sockets don't match what we expected. Fixes bug 9400;
1852 bugfix on 0.0.2pre7. Found by Coverity.
1853 - Correctly store microdescriptors and extrainfo descriptors that
1854 include an internal NUL byte. Fixes bug 8037; bugfix on
1855 0.2.0.1-alpha. Bug reported by "cypherpunks".
1856 - If for some reason we fail to write a microdescriptor while
1857 rebuilding the cache, do not let the annotations from that
1858 microdescriptor linger in the cache file, and do not let the
1859 microdescriptor stay recorded as present in its old location.
1860 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1861 - Use direct writes rather than stdio when building microdescriptor
1862 caches, in an attempt to mitigate bug 8031, or at least make it
1865 o Minor fixes (config options):
1866 - Warn and fail if a server is configured not to advertise any
1867 ORPorts at all. (We need *something* to put in our descriptor,
1868 or we just won't work.)
1869 - Behave correctly when the user disables LearnCircuitBuildTimeout
1870 but doesn't tell us what they would like the timeout to be. Fixes
1871 bug 6304; bugfix on 0.2.2.14-alpha.
1872 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1873 to start with a triple-underscore so the controller won't touch it.
1874 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1875 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1876 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1877 - When autodetecting the number of CPUs, use the number of available
1878 CPUs in preference to the number of configured CPUs. Inform the
1879 user if this reduces the number of available CPUs. Fixes bug 8002;
1880 bugfix on 0.2.3.1-alpha.
1881 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1882 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1883 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1884 bug 8180; bugfix on 0.2.3.11-alpha.
1885 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1886 ridiculously high value, by imposing a (ridiculously high) 30-day
1887 maximum on MaxCircuitDirtiness.
1889 o Minor bugfixes (control protocol):
1890 - Stop sending a stray "(null)" in some cases for the server status
1891 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1893 - The ADDRMAP command can no longer generate an ill-formed error
1894 code on a failed MAPADDRESS. It now says "internal" rather than
1895 an English sentence fragment with spaces in the middle. Bugfix on
1898 o Minor bugfixes (clients / edges):
1899 - When we receive a RELAY_END cell with the reason DONE, or with no
1900 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1901 status as "connection refused". Previously we reported these cases
1902 as success but then immediately closed the connection. Fixes bug
1903 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1904 - If the guard we choose first doesn't answer, we would try the
1905 second guard, but once we connected to the second guard we would
1906 abandon it and retry the first one, slowing down bootstrapping.
1907 The fix is to treat all our initially chosen guards as acceptable
1908 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1909 - When choosing which stream on a formerly stalled circuit to wake
1910 first, make better use of the platform's weak RNG. Previously,
1911 we had been using the % ("modulo") operator to try to generate a
1912 1/N chance of picking each stream, but this behaves badly with
1913 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1916 o Minor bugfixes (path bias detection):
1917 - If the state file's path bias counts are invalid (presumably from a
1918 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1919 additional checks and log messages to the scaling of Path Bias
1920 counts, in case there still are remaining issues with scaling.
1921 Should help resolve bug 8235.
1922 - Prevent rounding error in path bias counts when scaling
1923 them down, and use the correct scale factor default. Also demote
1924 some path bias related log messages down a level and make others
1925 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
1926 - Remove a source of rounding error during path bias count scaling;
1927 don't count cannibalized circuits as used for path bias until we
1928 actually try to use them; and fix a circuit_package_relay_cell()
1929 warning message about n_chan==NULL. Fixes bug 7802.
1930 - Paste the description for PathBias parameters from the man
1931 page into or.h, so the code documents them too. Fixes bug 7982;
1932 bugfix on 0.2.3.17-beta.
1934 o Minor bugfixes (relays):
1935 - Stop trying to resolve our hostname so often (e.g. every time we
1936 think about doing a directory fetch). Now we reuse the cached
1937 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1938 and 2410 (bugfix on 0.1.2.2-alpha).
1939 - When examining the list of network interfaces to find our address,
1940 do not consider non-running or disabled network interfaces. Fixes
1941 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1943 o Minor bugfixes (blocking resistance):
1944 - Only disable TLS session ticket support when running as a TLS
1945 server. Now clients will blend better with regular Firefox
1946 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1948 o Minor bugfixes (IPv6):
1949 - Use square brackets around IPv6 addresses in numerous places
1950 that needed them, including log messages, HTTPS CONNECT proxy
1951 requests, TransportProxy statefile entries, and pluggable transport
1952 extra-info lines. Fixes bug 7011; patch by David Fifield.
1954 o Minor bugfixes (directory authorities):
1955 - Reject consensus votes with more than 64 known-flags. We aren't even
1956 close to that limit yet, and our code doesn't handle it correctly.
1957 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1958 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1959 bugfix on 0.2.0.3-alpha.
1961 o Minor bugfixes (memory leaks):
1962 - Avoid leaking memory if we fail to compute a consensus signature
1963 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1964 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1965 on 0.2.1.1-alpha; fixes bug 7816.
1966 - Fix a memory leak during safe-cookie controller authentication.
1967 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
1968 - Free some more still-in-use memory at exit, to make hunting for
1969 memory leaks easier. Resolves bug 7029.
1971 o Minor bugfixes (code correctness):
1972 - Increase the width of the field used to remember a connection's
1973 link protocol version to two bytes. Harmless for now, since the
1974 only currently recognized versions are one byte long. Reported
1975 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1976 - Fix a crash when debugging unit tests on Windows: deallocate a
1977 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1978 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1979 - When detecting the largest possible file descriptor (in order to
1980 close all file descriptors when launching a new program), actually
1981 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1982 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1984 - Avoid a crash if we fail to generate an extrainfo descriptor.
1985 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1987 - Avoid an off-by-one error when checking buffer boundaries when
1988 formatting the exit status of a pluggable transport helper.
1989 This is probably not an exploitable bug, but better safe than
1990 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1992 - Get rid of a couple of harmless clang warnings, where we compared
1993 enums to ints. These warnings are newly introduced in clang 3.2.
1995 o Minor bugfixes (code cleanliness):
1996 - Avoid use of reserved identifiers in our C code. The C standard
1997 doesn't like us declaring anything that starts with an
1998 underscore, so let's knock it off before we get in trouble. Fix
1999 for bug 1031; bugfix on the first Tor commit.
2000 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2001 with large values. This situation was untriggered, but nevertheless
2002 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2003 - Fix an impossible buffer overrun in the AES unit tests. Fixes
2004 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
2005 - Fix handling of rendezvous client authorization types over 8.
2006 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2007 - Remove a couple of extraneous semicolons that were upsetting the
2008 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
2009 bugfix on 0.2.2.1-alpha.
2010 - When complaining about a client port on a public address, log
2011 which address we're complaining about. Fixes bug 4020; bugfix on
2012 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2014 o Minor bugfixes (log messages, warnings):
2015 - If we encounter a write failure on a SOCKS connection before we
2016 finish our SOCKS handshake, don't warn that we closed the
2017 connection before we could send a SOCKS reply. Fixes bug 8427;
2018 bugfix on 0.1.0.1-rc.
2019 - Fix a directory authority warn caused when we have a large amount
2020 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
2021 - Downgrade "Failed to hand off onionskin" messages to "debug"
2022 severity, since they're typically redundant with the "Your computer
2023 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2024 - Avoid spurious warnings when configuring multiple client ports of
2025 which only some are nonlocal. Previously, we had claimed that some
2026 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2029 o Minor bugfixes (log messages, other):
2030 - Fix log messages and comments to avoid saying "GMT" when we mean
2031 "UTC". Fixes bug 6113.
2032 - When rejecting a configuration because we were unable to parse a
2033 quoted string, log an actual error message. Fixes bug 7950; bugfix
2035 - Correctly recognize that [::1] is a loopback address. Fixes
2036 bug 8377; bugfix on 0.2.1.3-alpha.
2037 - Don't log inappropriate heartbeat messages when hibernating: a
2038 hibernating node is _expected_ to drop out of the consensus,
2039 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
2040 bugfix on 0.2.3.1-alpha.
2041 - Eliminate several instances where we use "Nickname=ID" to refer to
2042 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2043 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2046 o Minor bugfixes (build):
2047 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2048 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2049 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2051 o Documentation fixes:
2052 - Make the torify manpage no longer refer to tsocks; torify hasn't
2053 supported tsocks since 0.2.3.14-alpha.
2054 - Make the tor manpage no longer reference tsocks.
2055 - Fix the GeoIPExcludeUnknown documentation to refer to
2056 ExcludeExitNodes rather than the currently nonexistent
2057 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
2058 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2060 - Say "KBytes" rather than "KB" in the man page (for various values
2061 of K), to further reduce confusion about whether Tor counts in
2062 units of memory or fractions of units of memory. Resolves ticket 7054.
2063 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
2064 names match. Fixes bug 7768.
2065 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
2066 message is logged at notice, not at info.
2067 - Clarify the usage and risks of setting the ContactInfo torrc line
2068 for your relay or bridge. Resolves ticket 9854.
2069 - Add anchors to the manpage so we can link to the html version of
2070 the documentation for specific options. Resolves ticket 9866.
2071 - Replace remaining references to DirServer in man page and
2072 log entries. Resolves ticket 10124.
2075 - Stop exporting estimates of v2 and v3 directory traffic shares
2076 in extrainfo documents. They were unneeded and sometimes inaccurate.
2077 Also stop exporting any v2 directory request statistics. Resolves
2079 - Drop support for detecting and warning about versions of Libevent
2080 before 1.3e. Nothing reasonable ships with them any longer; warning
2081 the user about them shouldn't be needed. Resolves ticket 6826.
2082 - Now that all versions before 0.2.2.x are disallowed, we no longer
2083 need to work around their missing features. Remove a bunch of
2087 - The tor-tsocks.conf is no longer distributed or installed. We
2088 recommend that tsocks users use torsocks instead. Resolves
2090 - Remove some of the older contents of doc/ as obsolete; move others
2091 to torspec.git. Fixes bug 8965.
2093 o Code simplification:
2094 - Avoid using character buffers when constructing most directory
2095 objects: this approach was unwieldy and error-prone. Instead,
2096 build smartlists of strings, and concatenate them when done.
2097 - Rename "isin" functions to "contains", for grammar. Resolves
2099 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2100 with the natural logarithm function from the system libm. Resolves
2102 - Start using OpenBSD's implementation of queue.h, so that we don't
2103 need to hand-roll our own pointer and list structures whenever we
2104 need them. (We can't rely on a sys/queue.h, since some operating
2105 systems don't have them, and the ones that do have them don't all
2106 present the same extensions.)
2107 - Start using OpenBSD's implementation of queue.h (originally by
2109 - Enhance our internal sscanf replacement so that we can eliminate
2110 the last remaining uses of the system sscanf. (Though those uses
2111 of sscanf were safe, sscanf itself is generally error prone, so
2112 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2114 - Replace all calls to snprintf() outside of src/ext with
2115 tor_snprintf(). Also remove the #define to replace snprintf with
2116 _snprintf on Windows; they have different semantics, and all of
2117 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2120 - Add a wrapper function for the common "log a message with a
2122 - Split the onion.c file into separate modules for the onion queue
2123 and the different handshakes it supports.
2124 - Move the client-side address-map/virtual-address/DNS-cache code
2125 out of connection_edge.c into a new addressmap.c module.
2126 - Move the entry node code from circuitbuild.c to its own file.
2127 - Move the circuit build timeout tracking code from circuitbuild.c
2129 - Source files taken from other packages now reside in src/ext;
2130 previously they were scattered around the rest of Tor.
2131 - Move the generic "config" code into a new file, and have "config.c"
2132 hold only torrc- and state-related code. Resolves ticket 6823.
2133 - Move the core of our "choose a weighted element at random" logic
2134 into its own function, and give it unit tests. Now the logic is
2135 testable, and a little less fragile too.
2136 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2137 - Move last_reachable and testing_since from routerinfo_t to node_t.
2138 Implements ticket 5529.
2139 - Add replaycache_t structure, functions and unit tests, then refactor
2140 rend_service_introduce() to be more clear to read, improve, debug,
2141 and test. Resolves bug 6177.
2144 - Remove some now-needless code that tried to aggressively flush
2145 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2146 cell queue logic has saved us from the failure mode that this code
2147 was supposed to prevent. Removing this code will limit the number
2148 of baroque control flow paths through Tor's network logic. Reported
2149 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2150 - Remove unused code for parsing v1 directories and "running routers"
2151 documents. Fixes bug 6887.
2152 - Remove the marshalling/unmarshalling code for sending requests to
2153 cpuworkers over a socket, and instead just send structs. The
2154 recipient will always be the same Tor binary as the sender, so
2155 any encoding is overkill.
2156 - Remove the testing_since field of node_t, which hasn't been used
2157 for anything since 0.2.0.9-alpha.
2158 - Finally remove support for malloc_good_size and malloc_usable_size.
2159 We had hoped that these functions would let us eke a little more
2160 memory out of our malloc implementation. Unfortunately, the only
2161 implementations that provided these functions are also ones that
2162 are already efficient about not overallocation: they never got us
2163 more than 7 or so bytes per allocation. Removing them saves us a
2164 little code complexity and a nontrivial amount of build complexity.
2167 Changes in version 0.2.3.25 - 2012-11-19
2168 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2169 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2170 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2171 programmer, and friend. Unstinting in his dedication to the cause of
2172 freedom, he inspired and helped many of us as we began our work on
2173 anonymity, and inspires us still. Please honor his memory by writing
2174 software to protect people's freedoms, and by helping others to do so.
2176 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2177 significantly reduced directory overhead (via microdescriptors),
2178 enormous crypto performance improvements for fast relays on new
2179 enough hardware, a new v3 TLS handshake protocol that can better
2180 resist fingerprinting, support for protocol obfuscation plugins (aka
2181 pluggable transports), better scalability for hidden services, IPv6
2182 support for bridges, performance improvements like allowing clients
2183 to skip the first round-trip on the circuit ("optimistic data") and
2184 refilling token buckets more often, a new "stream isolation" design
2185 to isolate different applications on different circuits, and many
2186 stability, security, and privacy fixes.
2188 Major features (v3 directory protocol):
2189 - Clients now use microdescriptors instead of regular descriptors
2190 to build circuits. Microdescriptors are authority-generated
2191 summaries of regular descriptors' contents, designed to change very
2192 rarely (see proposal 158 for details). This feature is designed
2193 to save bandwidth, especially for clients on slow internet
2194 connections. Use "UseMicrodescriptors 0" to disable it.
2195 - Caches now download, cache, and serve microdescriptors, as well
2196 as multiple "flavors" of the consensus, including a flavor that
2197 describes microdescriptors.
2199 o Major features (build hardening):
2200 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2202 o Major features (relay scaling):
2203 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2204 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2205 vectorized AES implementations as appropriate. These can be much,
2206 much faster than other AES implementations.
2207 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2208 implementation. It makes AES_CTR about 7% faster than our old one
2209 (which was about 10% faster than the one OpenSSL used to provide).
2210 Resolves ticket 4526.
2211 - Use OpenSSL's EVP interface for AES encryption, so that all AES
2212 operations can use hardware acceleration (if present). Resolves
2214 - Unconditionally use OpenSSL's AES implementation instead of our
2215 old built-in one. OpenSSL's AES has been better for a while, and
2216 relatively few servers should still be on any version of OpenSSL
2217 that doesn't have good optimized assembly AES.
2219 o Major features (blocking resistance):
2220 - Update TLS cipher list to match Firefox 8 and later. Resolves
2222 - Remove support for clients falsely claiming to support standard
2223 ciphersuites that they can actually provide. As of modern OpenSSL
2224 versions, it's not necessary to fake any standard ciphersuite,
2225 and doing so prevents us from using better ciphersuites in the
2226 future, since servers can't know whether an advertised ciphersuite
2227 is really supported or not. Some hosts -- notably, ones with very
2228 old versions of OpenSSL or where OpenSSL has been built with ECC
2229 disabled -- will stand out because of this change; TBB users should
2230 not be affected. Implements the client side of proposal 198.
2231 - Implement a new handshake protocol (v3) for authenticating Tors to
2232 each other over TLS. It should be more resistant to fingerprinting
2233 than previous protocols, and should require less TLS hacking for
2234 future Tor implementations. Implements proposal 176.
2235 - Allow variable-length padding cells, to disguise the length of
2236 Tor's TLS records. Implements part of proposal 184.
2237 - While we're trying to bootstrap, record how many TLS connections
2238 fail in each state, and report which states saw the most failures
2239 in response to any bootstrap failures. This feature may speed up
2240 diagnosis of censorship events. Implements ticket 3116.
2242 o Major features (pluggable transports):
2243 - Clients and bridges can now be configured to use a separate
2244 "transport" proxy. This approach makes the censorship arms race
2245 easier by allowing bridges to use protocol obfuscation plugins.
2246 Implements proposal 180 (tickets 2841 and 3472).
2248 o Major features (DoS resistance):
2249 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2250 part of "Proposal 110: Avoiding infinite length circuits" by
2251 refusing all circuit-extend requests that do not use a relay_early
2252 cell. This change helps Tor resist a class of denial-of-service
2253 attacks by limiting the maximum circuit length.
2254 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2255 could use this trick to make their circuits receive cells faster
2256 than our flow control would have allowed, or to gum up the network,
2257 or possibly to do targeted memory denial-of-service attacks on
2258 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2259 from July 2002, before the release of Tor 0.0.0.
2261 o Major features (hidden services):
2262 - Adjust the number of introduction points that a hidden service
2263 will try to maintain based on how long its introduction points
2264 remain in use and how many introductions they handle. Fixes
2266 - Add a "tor2web mode" for clients that want to connect to hidden
2267 services non-anonymously (and possibly more quickly). As a safety
2268 measure to try to keep users from turning this on without knowing
2269 what they are doing, tor2web mode must be explicitly enabled at
2270 compile time, and a copy of Tor compiled to run in tor2web mode
2271 cannot be used as a normal Tor client. Implements feature 2553.
2273 o Major features (IPv6):
2274 - Clients can now connect to private bridges over IPv6. Bridges
2275 still need at least one IPv4 address in order to connect to
2276 other relays. Note that we don't yet handle the case where the
2277 user has two bridge lines for the same bridge (one IPv4, one
2278 IPv6). Implements parts of proposal 186.
2280 o Major features (directory authorities):
2281 - Use a more secure consensus parameter voting algorithm. Now at
2282 least three directory authorities or a majority of them must
2283 vote on a given parameter before it will be included in the
2284 consensus. Implements proposal 178.
2285 - Remove the artificially low cutoff of 20KB to guarantee the Fast
2286 flag. In the past few years the average relay speed has picked
2287 up, and while the "top 7/8 of the network get the Fast flag" and
2288 "all relays with 20KB or more of capacity get the Fast flag" rules
2289 used to have the same result, now the top 7/8 of the network has
2290 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
2292 o Major features (performance):
2293 - Exit nodes now accept and queue data on not-yet-connected streams.
2294 Previously, the client wasn't allowed to send data until the
2295 stream was connected, which slowed down all connections. This
2296 change will enable clients to perform a "fast-start" on streams
2297 and send data without having to wait for a confirmation that the
2298 stream has opened. Patch from Ian Goldberg; implements the server
2299 side of Proposal 174.
2300 - When using an exit relay running 0.2.3.x, clients can now
2301 "optimistically" send data before the exit relay reports that
2302 the stream has opened. This saves a round trip when starting
2303 connections where the client speaks first (such as web browsing).
2304 This behavior is controlled by a consensus parameter (currently
2305 disabled). To turn it on or off manually, use the "OptimisticData"
2306 torrc option. Implements proposal 181; code by Ian Goldberg.
2307 - Add a new TokenBucketRefillInterval option to refill token buckets
2308 more frequently than once per second. This should improve network
2309 performance, alleviate queueing problems, and make traffic less
2310 bursty. Implements proposal 183; closes ticket 3630. Design by
2311 Florian Tschorsch and Björn Scheuermann; implementation by
2313 - Raise the threshold of server descriptors needed (75%) and exit
2314 server descriptors needed (50%) before we will declare ourselves
2315 bootstrapped. This will make clients start building circuits a
2316 little later, but makes the initially constructed circuits less
2317 skewed and less in conflict with further directory fetches. Fixes
2320 o Major features (relays):
2321 - Relays now try regenerating and uploading their descriptor more
2322 frequently if they are not listed in the consensus, or if the
2323 version of their descriptor listed in the consensus is too
2324 old. This fix should prevent situations where a server declines
2325 to re-publish itself because it has done so too recently, even
2326 though the authorities decided not to list its recent-enough
2327 descriptor. Fix for bug 3327.
2329 o Major features (stream isolation):
2330 - You can now configure Tor so that streams from different
2331 applications are isolated on different circuits, to prevent an
2332 attacker who sees your streams as they leave an exit node from
2333 linking your sessions to one another. To do this, choose some way
2334 to distinguish the applications: have them connect to different
2335 SocksPorts, or have one of them use SOCKS4 while the other uses
2336 SOCKS5, or have them pass different authentication strings to the
2337 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2338 degree of isolation you need. This implements Proposal 171.
2339 - There's a new syntax for specifying multiple client ports (such as
2340 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2341 multiple *Port entries with full addr:port syntax on each.
2342 The old *ListenAddress format is still supported, but you can't
2343 mix it with the new *Port syntax.
2345 o Major features (bufferevents):
2346 - Tor can now optionally build with the "bufferevents" buffered IO
2347 backend provided by Libevent 2. To use this feature, make sure you
2348 have the latest possible version of Libevent, and pass the
2349 --enable-bufferevents flag to configure when building Tor from
2350 source. This feature will make our networking code more flexible,
2351 let us stack layers on each other, and let us use more efficient
2352 zero-copy transports where available.
2353 - Add experimental support for running on Windows with IOCP and no
2354 kernel-space socket buffers. This feature is controlled by a new
2355 "UserspaceIOCPBuffers" config option (off by default), which has
2356 no effect unless Tor has been built with bufferevents enabled,
2357 you're running on Windows, and you've set "DisableIOCP 0". In the
2358 long run, this may help solve or mitigate bug 98.
2360 o Major features (path selection):
2361 - The EntryNodes option can now include country codes like {de} or IP
2362 addresses or network masks. Previously we had disallowed these
2363 options because we didn't have an efficient way to keep the list up
2364 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
2367 o Major features (port forwarding):
2368 - Add support for automatic port mapping on the many home routers
2369 that support NAT-PMP or UPnP. To build the support code, you'll
2370 need to have the libnatpnp library and/or the libminiupnpc library,
2371 and you'll need to enable the feature specifically by passing
2372 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
2373 it on, use the new PortForwarding option.
2375 o Major features (logging):
2376 - Add a new 'Heartbeat' log message type to periodically log a message
2377 describing Tor's status at level Notice. This feature is meant for
2378 operators who log at notice, and want to make sure that their Tor
2379 server is still working. Implementation by George Kadianakis.
2380 - Make logging resolution configurable with a new LogTimeGranularity
2381 option, and change the default from 1 millisecond to 1 second.
2382 Implements enhancement 1668.
2384 o Major features (other):
2385 - New "DisableNetwork" config option to prevent Tor from launching any
2386 connections or accepting any connections except on a control port.
2387 Bundles and controllers can set this option before letting Tor talk
2388 to the rest of the network, for example to prevent any connections
2389 to a non-bridge address. Packages like Orbot can also use this
2390 option to instruct Tor to save power when the network is off.
2391 - Try to use system facilities for enumerating local interface
2392 addresses, before falling back to our old approach (which was
2393 binding a UDP socket, and calling getsockname() on it). That
2394 approach was scaring OS X users whose draconian firewall
2395 software warned about binding to UDP sockets regardless of
2396 whether packets were sent. Now we try to use getifaddrs(),
2397 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2398 system supports. Resolves ticket 1827.
2399 - Add experimental support for a "defaults" torrc file to be parsed
2400 before the regular torrc. Torrc options override the defaults file's
2401 options in the same way that the command line overrides the torrc.
2402 The SAVECONF controller command saves only those options which
2403 differ between the current configuration and the defaults file. HUP
2404 reloads both files. Implements task 4552.
2406 o New directory authorities:
2407 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2408 authority. Closes ticket 5749.
2410 o Security/privacy fixes:
2411 - Avoid read-from-freed-memory and double-free bugs that could occur
2412 when a DNS request fails while launching it. Fixes bug 6480;
2413 bugfix on 0.2.0.1-alpha.
2414 - Reject any attempt to extend to an internal address. Without
2415 this fix, a router could be used to probe addresses on an internal
2416 network to see whether they were accepting connections. Fixes bug
2417 6710; bugfix on 0.0.8pre1.
2418 - Close any connection that sends unrecognized junk before the TLS
2419 handshake. Solves an issue noted in bug 4369.
2420 - The advertised platform of a relay now includes only its operating
2421 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
2422 its service pack level (for Windows) or its CPU architecture
2423 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
2424 can insert an extra string in the platform line by setting the
2425 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
2426 - Disable TLS session tickets. OpenSSL's implementation was giving
2427 our TLS session keys the lifetime of our TLS context objects, when
2428 perfect forward secrecy would want us to discard anything that
2429 could decrypt a link connection as soon as the link connection
2430 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2431 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2432 - Tor tries to wipe potentially sensitive data after using it, so
2433 that if some subsequent security failure exposes Tor's memory,
2434 the damage will be limited. But we had a bug where the compiler
2435 was eliminating these wipe operations when it decided that the
2436 memory was no longer visible to a (correctly running) program,
2437 hence defeating our attempt at defense in depth. We fix that
2438 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2439 is unlikely to optimize away. Future versions of Tor may use
2440 a less ridiculously heavy approach for this. Fixes bug 7352.
2441 Reported in an article by Andrey Karpov.
2443 o Major bugfixes (crashes and asserts):
2444 - Avoid a pair of double-free and use-after-mark bugs that can
2445 occur with certain timings in canceled and re-received DNS
2446 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2447 - Fix a denial of service attack by which any directory authority
2448 could crash all the others, or by which a single v2 directory
2449 authority could crash everybody downloading v2 directory
2450 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2451 - Fix an assert that directory authorities could trigger on sighup
2452 during some configuration state transitions. We now don't treat
2453 it as a fatal error when the new descriptor we just generated in
2454 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2455 - Avoid segfault when starting up having run with an extremely old
2456 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2459 o Major bugfixes (clients):
2460 - If we are unable to find any exit that supports our predicted ports,
2461 stop calling them predicted, so that we don't loop and build
2462 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2463 which introduced predicted ports.
2464 - Check at each new consensus whether our entry guards were picked
2465 long enough ago that we should rotate them. Previously, we only
2466 did this check at startup, which could lead to us holding a guard
2467 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2468 - When fetching a bridge descriptor from a bridge authority,
2469 always do so anonymously, whether we have been able to open
2470 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2471 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2472 but we'll need to wait for bug 6010 before it's actually usable.
2474 o Major bugfixes (directory voting):
2475 - Check more thoroughly to prevent a rogue authority from
2476 double-voting on any consensus directory parameter. Previously,
2477 authorities would crash in this case if the total number of
2478 votes for any parameter exceeded the number of active voters,
2479 but would let it pass otherwise. Partially fixes bug 5786; bugfix
2481 - When computing weight parameters, behave more robustly in the
2482 presence of a bad bwweightscale value. Previously, the authorities
2483 would crash if they agreed on a sufficiently broken weight_scale
2484 value; now, they use a reasonable default and carry on. Fixes the
2485 rest of bug 5786; bugfix on 0.2.2.17-alpha.
2486 - If authorities are unable to get a v2 consensus document from other
2487 directory authorities, they no longer fall back to fetching
2488 them from regular directory caches. Fixes bug 5635; bugfix on
2489 0.2.2.26-beta, where routers stopped downloading v2 consensus
2492 o Major bugfixes (relays):
2493 - Fix a bug handling SENDME cells on nonexistent streams that could
2494 result in bizarre window values. Report and patch contributed
2495 pseudonymously. Fixes part of bug 6271. This bug was introduced
2496 before the first Tor release, in svn commit r152.
2497 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2498 tor gets started. This prevents a wrong average bandwidth
2499 estimate, which would cause relays to always start a new accounting
2500 interval at the earliest possible moment. Fixes bug 2003; bugfix
2501 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
2502 immensely in tracking this bug down.
2503 - Fix a possible crash bug when checking for deactivated circuits
2504 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2505 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2506 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2507 connections. This change should allow busy exit relays to stop
2508 running out of available sockets as quickly. Fixes bug 4950;
2509 bugfix on 0.2.2.26-beta.
2511 o Major bugfixes (blocking resistance):
2512 - Bridges no longer include their address in NETINFO cells on outgoing
2513 OR connections, to allow them to blend in better with clients.
2514 Removes another avenue for enumerating bridges. Reported by
2515 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
2516 cells were introduced.
2517 - Warn the user when HTTPProxy, but no other proxy type, is
2518 configured. This can cause surprising behavior: it doesn't send
2519 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2520 directory traffic only. Resolves ticket 4663.
2522 o Major bugfixes (hidden services):
2523 - Improve hidden service robustness: when an attempt to connect to
2524 a hidden service ends, be willing to refetch its hidden service
2525 descriptors from each of the HSDir relays responsible for them
2526 immediately. Previously, we would not consider refetching the
2527 service's descriptors from each HSDir for 15 minutes after the last
2528 fetch, which was inconvenient if the hidden service was not running
2529 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
2530 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2531 They used to check that the timestamp was within 30 minutes
2532 of their system clock, so they could cap the size of their
2533 replay-detection cache, but that approach unnecessarily refused
2534 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2535 the v3 intro-point protocol (the first one which sent a timestamp
2536 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2537 - When one of a hidden service's introduction points appears to be
2538 unreachable, stop trying it. Previously, we would keep trying
2539 to build circuits to the introduction point until we lost the
2540 descriptor, usually because the user gave up and restarted Tor.
2541 Fixes part of bug 3825.
2543 o Changes to default torrc file:
2544 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2545 port on 9050 by default anyway, so this should not change anything
2547 - Stop mentioning the deprecated *ListenAddress options in
2548 torrc.sample. Fixes bug 5438.
2549 - Document unit of bandwidth-related options in sample torrc.
2551 - Fix broken URLs in the sample torrc file, and tell readers about
2552 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2553 PublishServerDescriptor options. Addresses bug 4652.
2555 o Minor features (directory authorities):
2556 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
2557 change when the authority is deciding whether to accept a newly
2558 uploaded descriptor. Implements ticket 6423.
2559 - Directory authorities are now a little more lenient at accepting
2560 older router descriptors, or newer router descriptors that don't
2561 make big changes. This should help ameliorate past and future
2562 issues where routers think they have uploaded valid descriptors,
2563 but the authorities don't think so. Fix for ticket 2479.
2564 - Authority operators can now vote for all relays in a given
2565 set of countries to be BadDir/BadExit/Invalid/Rejected.
2566 - Provide two consensus parameters (FastFlagMinThreshold and
2567 FastFlagMaxThreshold) to control the range of allowable bandwidths
2568 for the Fast directory flag. These allow authorities to run
2569 experiments on appropriate requirements for being a "Fast" node.
2570 The AuthDirFastGuarantee config value still applies. Implements
2573 o Minor features (bridges / bridge authorities):
2574 - Make bridge SSL certificates a bit more stealthy by using random
2575 serial numbers, in the same fashion as OpenSSL when generating
2576 self-signed certificates. Implements ticket 4584.
2577 - Tag a bridge's descriptor as "never to be sent unencrypted".
2578 This shouldn't matter, since bridges don't open non-anonymous
2579 connections to the bridge authority and don't allow unencrypted
2580 directory connections from clients, but we might as well make
2581 sure. Closes bug 5139.
2582 - The Bridge Authority now writes statistics on how many bridge
2583 descriptors it gave out in total, and how many unique descriptors
2584 it gave out. It also lists how often the most and least commonly
2585 fetched descriptors were given out, as well as the median and
2586 25th/75th percentile. Implements tickets 4200 and 4294.
2588 o Minor features (IPv6):
2589 - Make the code that clients use to detect an address change be
2590 IPv6-aware, so that it won't fill clients' logs with error
2591 messages when trying to get the IPv4 address of an IPv6
2592 connection. Implements ticket 5537.
2593 - Relays now understand an IPv6 address when they get one from a
2594 directory server. Resolves ticket 4875.
2596 o Minor features (hidden services):
2597 - Expire old or over-used hidden service introduction points.
2598 Required by fix for bug 3460.
2599 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
2600 public key replay-detection cache from 60 minutes to 5 minutes. This
2601 replay-detection cache is now used only to detect multiple
2602 INTRODUCE2 cells specifying the same rendezvous point, so we can
2603 avoid launching multiple simultaneous attempts to connect to it.
2604 - When a hidden service's introduction point times out, consider
2605 trying it again during the next attempt to connect to the
2606 HS. Previously, we would not try it again unless a newly fetched
2607 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2609 o Minor features (relays):
2610 - Relays now include a reason for regenerating their descriptors
2611 in an HTTP header when uploading to the authorities. This will
2612 make it easier to debug descriptor-upload issues in the future.
2613 - Turn on directory request statistics by default and include them in
2614 extra-info descriptors. Don't break if we have no GeoIP database.
2615 - Replace files in stats/ rather than appending to them. Now that we
2616 include statistics in extra-info descriptors, it makes no sense to
2617 keep old statistics forever. Implements ticket 2930.
2618 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2619 bidirectional use of connections to disk every 24 hours.
2620 - Add a GeoIP file digest to the extra-info descriptor. Implements
2623 o Minor features (new config options):
2624 - New config option "DynamicDHGroups" (disabled by default) provides
2625 each bridge with a unique prime DH modulus to be used during
2626 SSL handshakes. This option attempts to help against censors
2627 who might use the Apache DH modulus as a static identifier for
2628 bridges. Addresses ticket 4548.
2629 - New config option "DisableDebuggerAttachment" (on by default)
2630 to prevent basic debugging attachment attempts by other processes.
2631 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
2632 - Ordinarily, Tor does not count traffic from private addresses (like
2633 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2634 There is now a new option, CountPrivateBandwidth, to disable this
2635 behavior. Patch from Daniel Cagara.
2637 o Minor features (different behavior for old config options):
2638 - Allow MapAddress directives to specify matches against super-domains,
2639 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
2640 Implements issue 933.
2641 - Don't disable the DirPort when we cannot exceed our AccountingMax
2642 limit during this interval because the effective bandwidthrate is
2643 low enough. This is useful in a situation where AccountMax is only
2644 used as an additional safeguard or to provide statistics.
2645 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2646 implements ticket 3439.
2647 - When configuring a large set of nodes in EntryNodes, and there are
2648 enough of them listed as Guard so that we don't need to consider
2649 the non-guard entries, prefer the ones listed with the Guard flag.
2650 - If you set the NumCPUs option to 0, Tor will now try to detect how
2651 many CPUs you have. This is the new default behavior.
2652 - The NodeFamily option -- which let you declare that you want to
2653 consider nodes to be part of a family whether they list themselves
2654 that way or not -- now allows IP address ranges and country codes.
2656 o Minor features (new command-line config behavior):
2657 - Slightly change behavior of "list" options (that is, config
2658 options that can appear more than once) when they appear both in
2659 torrc and on the command line. Previously, the command-line options
2660 would be appended to the ones from torrc. Now, the command-line
2661 options override the torrc options entirely. This new behavior
2662 allows the user to override list options (like exit policies and
2663 ports to listen on) from the command line, rather than simply
2664 appending to the list.
2665 - You can get the old (appending) command-line behavior for "list"
2666 options by prefixing the option name with a "+".
2667 - You can remove all the values for a "list" option from the command
2668 line without adding any new ones by prefixing the option name
2671 o Minor features (controller, new events):
2672 - Extend the control protocol to report flags that control a circuit's
2673 path selection in CIRC events and in replies to 'GETINFO
2674 circuit-status'. Implements part of ticket 2411.
2675 - Extend the control protocol to report the hidden service address
2676 and current state of a hidden-service-related circuit in CIRC
2677 events and in replies to 'GETINFO circuit-status'. Implements part
2679 - Include the creation time of a circuit in CIRC and CIRC2
2680 control-port events and the list produced by the 'GETINFO
2681 circuit-status' control-port command.
2682 - Add a new CONF_CHANGED event so that controllers can be notified
2683 of any configuration changes made by other controllers, or by the
2684 user. Implements ticket 1692.
2685 - Add a new SIGNAL event to the controller interface so that
2686 controllers can be notified when Tor handles a signal. Resolves
2687 issue 1955. Patch by John Brooks.
2689 o Minor features (controller, new getinfo options):
2690 - Expose our view of whether we have gone dormant to the controller,
2691 via a new "GETINFO dormant" value. Torbutton and other controllers
2692 can use this to avoid doing periodic requests through Tor while
2693 it's dormant (bug 4718). Resolves ticket 5954.
2694 - Add a new GETINFO option to get total bytes read and written. Patch
2695 from pipe, revised by atagar. Resolves ticket 2345.
2696 - Implement new GETINFO controller fields to provide information about
2697 the Tor process's pid, euid, username, and resource limits.
2699 o Minor features (controller, other):
2700 - Allow controllers to request an event notification whenever a
2701 circuit is cannibalized or its purpose is changed. Implements
2702 part of ticket 3457.
2703 - Use absolute path names when reporting the torrc filename in the
2704 control protocol, so a controller can more easily find the torrc
2705 file. Resolves bug 1101.
2706 - When reporting the path to the cookie file to the controller,
2707 give an absolute path. Resolves ticket 4881.
2709 o Minor features (log messages):
2710 - Add more information to a log statement that might help track down
2711 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2712 non-IP address" messages (or any Bug messages, for that matter!),
2713 please let us know about it.
2714 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2715 EntryNodes will have no effect. Resolves issue 2571.
2716 - Try to make the introductory warning message that Tor prints on
2717 startup more useful for actually finding help and information.
2718 Resolves ticket 2474.
2719 - When the system call to create a listener socket fails, log the
2720 error message explaining why. This may help diagnose bug 4027.
2722 o Minor features (other):
2723 - When we fail to initialize Libevent, retry with IOCP disabled so we
2724 don't need to turn on multi-threading support in Libevent, which in
2725 turn requires a working socketpair(). This is a workaround for bug
2726 4457, which affects Libevent versions from 2.0.1-alpha through
2728 - When starting as root and then changing our UID via the User
2729 control option, and we have a ControlSocket configured, make sure
2730 that the ControlSocket is owned by the same account that Tor will
2731 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2732 - Accept attempts to include a password authenticator in the
2733 handshake, as supported by SOCKS5. This handles SOCKS clients that
2734 don't know how to omit a password when authenticating. Resolves
2736 - Check for and recover from inconsistency in the microdescriptor
2737 cache. This will make it harder for us to accidentally free a
2738 microdescriptor without removing it from the appropriate data
2739 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2740 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2742 o Minor bugfixes (code security):
2743 - Prevent a null-pointer dereference when receiving a data cell
2744 for a nonexistent stream when the circuit in question has an
2745 empty deliver window. We don't believe this is triggerable,
2746 since we don't currently allow deliver windows to become empty,
2747 but the logic is tricky enough that it's better to make the code
2748 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2749 - Fix a (harmless) integer overflow in cell statistics reported by
2750 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2751 - Fix our implementation of crypto_random_hostname() so it can't
2752 overflow on ridiculously large inputs. (No Tor version has ever
2753 provided this kind of bad inputs, but let's be correct in depth.)
2754 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2755 - Add a (probably redundant) memory clear between iterations of
2756 the router status voting loop, to prevent future coding errors
2757 where data might leak between iterations of the loop. Resolves
2760 o Minor bugfixes (wrapper functions):
2761 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
2762 utility function used in the control-port code). This shouldn't
2763 ever happen unless Tor is completely out of memory, but if it did
2764 happen and Tor somehow recovered from it, Tor could have sent a log
2765 message to a control port in the middle of a reply to a controller
2766 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2767 - Fix some (not actually triggerable) buffer size checks in usage of
2768 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2770 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2771 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2772 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2773 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2774 - Make our replacement implementation of strtok_r() compatible with
2775 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2776 bugfix on 0.2.2.1-alpha.
2777 - Find more places in the code that should have been testing for
2778 invalid sockets using the SOCKET_OK macro. Required for a fix
2779 for bug 4533. Bugfix on 0.2.2.28-beta.
2781 o Minor bugfixes (code correctness):
2782 - Check return value of fputs() when writing authority certificate
2783 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2784 - When building Tor on Windows with -DUNICODE (not default), ensure
2785 that error messages, filenames, and DNS server names are always
2786 NUL-terminated when we convert them to a single-byte encoding.
2787 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2788 - Fix a memory leak when trying to launch a DNS request when the
2789 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
2791 - Correct file sizes when reading binary files on Cygwin, to avoid
2792 a bug where Tor would fail to read its state file. Fixes bug 6844;
2793 bugfix on 0.1.2.7-alpha.
2794 - Make sure to set *socket_error in all error cases in
2795 connection_connect(), so it can't produce a warning about
2796 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2797 0.2.1.1-alpha; resolves ticket 6028.
2798 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2799 bug 4532; found by "troll_un".
2801 o Minor bugfixes (clients):
2802 - Allow one-hop directory-fetching circuits the full "circuit build
2803 timeout" period, rather than just half of it, before failing them
2804 and marking the relay down. This fix should help reduce cases where
2805 clients declare relays (or worse, bridges) unreachable because
2806 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
2807 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
2809 - Ensure we don't cannibalize circuits that are longer than three hops
2810 already, so we don't end up making circuits with 5 or more
2811 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2812 0.1.0.1-rc which introduced cannibalization.
2814 o Minor bugfixes (relays):
2815 - Don't publish a new relay descriptor when we reload our onion key,
2816 unless the onion key has actually changed. Fixes bug 3263 and
2817 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2818 - When relays refuse a "create" cell because their queue of pending
2819 create cells is too big (typically because their cpu can't keep up
2820 with the arrival rate), send back reason "resource limit" rather
2821 than reason "internal", so network measurement scripts can get a
2822 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2823 - Exit nodes don't need to fetch certificates for authorities that
2824 they don't recognize; only directory authorities, bridges,
2825 and caches need to do that. Fixes part of bug 2297; bugfix on
2828 o Minor bugfixes (directory authority / mirrors):
2829 - Avoid O(n^2) performance characteristics when parsing a large
2830 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2831 - Authorities no longer include any router in their microdescriptor
2832 consensuses for which they couldn't generate or agree on a
2833 microdescriptor. Fixes the second piece of bug 6404; fix on
2835 - When checking for requested signatures on the latest consensus
2836 before serving it to a client, make sure to check the right
2837 consensus flavor. Bugfix on 0.2.2.6-alpha.
2838 - Fix an edge case where TestingTorNetwork is set but the authorities
2839 and relays all have an uptime of zero, so the private Tor network
2840 could briefly lack support for hidden services. Fixes bug 3886;
2841 bugfix on 0.2.2.18-alpha.
2842 - Directory caches no longer refuse to clean out descriptors because
2843 of missing v2 networkstatus documents, unless they're configured
2844 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2845 0.2.2.26-beta. Patch by Daniel Bryg.
2846 - Don't serve or accept v2 hidden service descriptors over a relay's
2847 DirPort. It's never correct to do so, and disabling it might
2848 make it more annoying to exploit any bugs that turn up in the
2849 descriptor-parsing code. Fixes bug 7149.
2851 o Minor bugfixes (hidden services, client-side):
2852 - Assert that hidden-service-related operations are not performed
2853 using single-hop circuits. Previously, Tor would assert that
2854 client-side streams are not attached to single-hop circuits,
2855 but not that other sensitive operations on the client and service
2856 side are not performed using single-hop circuits. Fixes bug 3332;
2858 - Avoid undefined behaviour when parsing the list of supported
2859 rendezvous/introduction protocols in a hidden service descriptor.
2860 Previously, Tor would have confused (as-yet-unused) protocol version
2861 numbers greater than 32 with lower ones on many platforms. Fixes
2862 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2863 - Don't close hidden service client circuits which have almost
2864 finished connecting to their destination when they reach
2865 the normal circuit-build timeout. Previously, we would close
2866 introduction circuits which are waiting for an acknowledgement
2867 from the introduction point, and rendezvous circuits which have
2868 been specified in an INTRODUCE1 cell sent to a hidden service,
2869 after the normal CBT. Now, we mark them as 'timed out', and launch
2870 another rendezvous attempt in parallel. This behavior change can
2871 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2872 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2874 o Minor bugfixes (hidden services, service-side):
2875 - Don't close hidden-service-side rendezvous circuits when they
2876 reach the normal circuit-build timeout. This behaviour change can
2877 be disabled using the new
2878 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2879 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2880 - Don't launch more than 10 service-side introduction-point circuits
2881 for a hidden service in five minutes. Previously, we would consider
2882 launching more introduction-point circuits if at least one second
2883 had passed without any introduction-point circuits failing. Fixes
2884 bug 4607; bugfix on 0.0.7pre1.
2886 o Minor bugfixes (config option behavior):
2887 - If the user tries to set MyFamily on a bridge, refuse to
2888 do so, and warn about the security implications. Fixes bug 4657;
2889 bugfix on 0.2.0.3-alpha.
2890 - The "--quiet" and "--hush" options now apply not only to Tor's
2891 behavior before logs are configured, but also to Tor's behavior in
2892 the absense of configured logs. Fixes bug 3550; bugfix on
2894 - Change the AllowDotExit rules so they should actually work.
2895 We now enforce AllowDotExit only immediately after receiving an
2896 address via SOCKS or DNSPort: other sources are free to provide
2897 .exit addresses after the resolution occurs. Fixes bug 3940;
2898 bugfix on 0.2.2.1-alpha.
2899 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
2900 don't depend on the consensus parameters or compute adaptive
2901 timeouts when it is disabled. Fixes bug 5049; bugfix on
2903 - After we pick a directory mirror, we would refuse to use it if
2904 it's in our ExcludeExitNodes list, resulting in mysterious failures
2905 to bootstrap for people who just wanted to avoid exiting from
2906 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2907 - When told to add a bridge with the same digest as a preexisting
2908 bridge but a different addr:port, change the addr:port as
2909 requested. Previously we would not notice the change. Fixes half
2910 of bug 5603; fix on 0.2.2.26-beta.
2912 o Minor bugfixes (controller):
2913 - Allow manual 'authenticate' commands to the controller interface
2914 from netcat (nc) as well as telnet. We were rejecting them because
2915 they didn't come with the expected whitespace at the end of the
2916 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2917 - Report a real bootstrap problem to the controller on router
2918 identity mismatch. Previously we just said "foo", which probably
2919 made a lot of sense at the time. Fixes bug 4169; bugfix on
2921 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2922 option is set to 0 (which Vidalia version 0.2.16 now does when
2923 a SAVECONF attempt fails), perform other actions that SIGHUP
2924 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2926 - Correctly handle checking the permissions on the parent
2927 directory of a control socket in the root directory. Bug found
2928 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2930 - End AUTHCHALLENGE error messages (in the control protocol) with
2931 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
2933 o Minor bugfixes (network reading/writing):
2934 - Disable writing on marked-for-close connections when they are
2935 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2936 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2937 case for flushing marked connections.
2938 - Make sure that there are no unhandled pending TLS errors before
2939 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2940 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2941 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2942 - Detect SSL handshake even when the initial attempt to write the
2943 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2944 - If the client fails to set a reasonable set of ciphersuites
2945 during its v2 handshake renegotiation, allow the renegotiation to
2946 continue nevertheless (i.e. send all the required certificates).
2947 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2949 o Minor bugfixes (other):
2950 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2951 resource exhaustion, so that clients can adjust their load to
2952 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2953 started using END_STREAM_REASON_RESOURCELIMIT.
2954 - Don't check for whether the address we're using for outbound
2955 connections has changed until after the outbound connection has
2956 completed. On Windows, getsockname() doesn't succeed until the
2957 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2958 - Don't hold a Windows file handle open for every file mapping;
2959 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2961 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2962 bugfix on 0.2.1.10-alpha.
2963 - If we fail to write a microdescriptor to the disk cache, do not
2964 continue replacing the old microdescriptor file. Fixes bug 2954;
2965 bugfix on 0.2.2.6-alpha.
2967 o Minor bugfixes (log messages, path selection):
2968 - Downgrade "set buildtimeout to low value" messages to "info"
2969 severity; they were never an actual problem, there was never
2970 anything reasonable to do about them, and they tended to spam logs
2971 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
2972 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2973 more information to it, so that we can track it down in case it
2974 returns again. Mitigates bug 5235.
2975 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2976 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2977 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2978 - Issue a log message if a guard completes less than 40% of your
2979 circuits. Threshold is configurable by torrc option
2980 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
2981 additional, off-by-default code to disable guards which fail too
2982 many circuits. Addresses ticket 5458.
2984 o Minor bugfixes (log messages, client):
2985 - Downgrade "Got a certificate, but we already have it" log messages
2986 from warning to info, except when we're a dirauth. Fixes bug 5238;
2987 bugfix on 0.2.1.7-alpha.
2988 - Fix the log message describing how we work around discovering
2989 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2990 4837; bugfix on 0.2.2.9-alpha.
2991 - When logging about a disallowed .exit name, do not also call it
2992 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2993 - Fix a log message suggesting that people contact a non-existent
2994 email address. Fixes bug 3448.
2995 - Rephrase the log message emitted if the TestSocks check is
2996 successful. Patch from Fabian Keil; fixes bug 4094.
2997 - Log (at debug level) whenever a circuit's purpose is changed.
2998 - Log SSL state transitions at log level DEBUG, log domain
2999 HANDSHAKE. This can be useful for debugging censorship events.
3000 Implements ticket 3264.
3001 - We now log which torrc file we're using on startup. Implements
3003 - Rate-limit log messages when asked to connect anonymously to
3004 a private address. When these hit, they tended to hit fast and
3005 often. Also, don't bother trying to connect to addresses that we
3006 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3007 reply makes us think we have been lied to, even when the address the
3008 client tried to connect to was "localhost." Resolves ticket 2822.
3010 o Minor bugfixes (log messages, non-client):
3011 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3012 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3013 - Don't log that we have "decided to publish new relay descriptor"
3014 unless we are actually publishing a descriptor. Fixes bug 3942;
3015 bugfix on 0.2.2.28-beta.
3016 - Log which authority we're missing votes from when we go to fetch
3017 them from the other auths.
3018 - Replace "Sending publish request" log messages with "Launching
3019 upload", so that they no longer confusingly imply that we're
3020 sending something to a directory we might not even be connected
3021 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3022 - Warn when Tor is configured to use accounting in a way that can
3023 link a hidden service to some other hidden service or public
3024 address. Resolves ticket 6490.
3025 - Fix a minor formatting issue in one of tor-gencert's error messages.
3029 - Update to the latest version of the tinytest unit testing framework.
3030 This includes a couple of bugfixes that can be relevant for
3031 running forked unit tests on Windows, and removes all reserved
3033 - Avoid a false positive in the util/threads unit test by increasing
3034 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3035 - Make it possible to set the TestingTorNetwork configuration
3036 option using AlternateDirAuthority and AlternateBridgeAuthority
3037 as an alternative to setting DirServer. Addresses ticket 6377.
3038 - Add a unit test for the environment_variable_names_equal() function.
3039 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3040 - Numerous new unit tests for functions in util.c and address.c by
3042 - The long-disabled benchmark tests are now split into their own
3043 ./src/test/bench binary.
3044 - The benchmark tests can now use more accurate timers than
3045 gettimeofday() when such timers are available.
3046 - Use tt_assert(), not tor_assert(), for checking for test failures.
3047 This makes the unit tests more able to go on in the event that
3050 o Build improvements:
3051 - Use the dead_strip option when building Tor on OS X. This reduces
3052 binary size by almost 19% when linking openssl and libevent
3053 statically, which we do for Tor Browser Bundle.
3054 - Provide a better error message about possible OSX Asciidoc failure
3055 reasons. Fixes bug 6436.
3056 - Detect attempts to build Tor on (as yet hypothetical) versions
3057 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3058 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3059 - On Windows, we now define the _WIN32_WINNT macros only if they
3060 are not already defined. This lets the person building Tor decide,
3061 if they want, to require a later version of Windows.
3062 - Our autogen.sh script now uses autoreconf to launch autoconf,
3063 automake, and so on. This is more robust against some of the failure
3064 modes associated with running the autotools pieces on their own.
3065 - Running "make version" now displays the version of Tor that
3066 we're about to build. Idea from katmagic; resolves issue 4400.
3067 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
3068 on 0.2.2.4-alpha; fixes bug 3427.
3069 - New --enable-static-tor configure option for building Tor as
3070 statically as possible. Idea, general hackery and thoughts from
3071 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3073 - Limited, experimental support for building with nmake and MSVC.
3075 o Build requirements:
3076 - Building Tor with bufferevent support now requires Libevent
3077 2.0.13-stable or later. Previous versions of Libevent had bugs in
3078 SSL-related bufferevents and related issues that would make Tor
3079 work badly with bufferevents. Requiring 2.0.13-stable also allows
3080 Tor with bufferevents to take advantage of Libevent APIs
3081 introduced after 2.0.8-rc.
3082 - Our build system requires automake 1.6 or later to create the
3083 Makefile.in files. Previously, you could have used 1.4.
3084 This only affects developers and people building Tor from git;
3085 people who build Tor from the source distribution without changing
3086 the Makefile.am files should be fine.
3087 - Detect when we try to build on a platform that doesn't define
3088 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3090 o Build fixes (compile/link):
3091 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3092 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3094 - When building with --enable-static-tor on OpenBSD, do not
3095 erroneously attempt to link -lrt. Fixes bug 5103.
3096 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3097 that IPv6 stuff will compile on MSVC, and compilation issues
3098 will be easier to track down. Fixes bug 5861.
3099 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
3100 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
3101 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3102 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3104 o Build fixes (other):
3105 - Use the _WIN32 macro throughout our code to detect Windows.
3106 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
3108 - Properly handle the case where the build-tree is not the same
3109 as the source tree when generating src/common/common_sha1.i,
3110 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3111 bugfix on 0.2.0.1-alpha.
3112 - During configure, search for library containing cos function as
3113 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3114 against libm was hard-coded before. Fixes the first part of bug
3115 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3117 - Prevent a false positive from the check-spaces script, by disabling
3118 the "whitespace between function name and (" check for functions
3121 o Packaging (RPM) changes:
3122 - Update our default RPM spec files to work with mock and rpmbuild
3123 on RHEL/Fedora. They have an updated set of dependencies and
3124 conflicts, a fix for an ancient typo when creating the "_tor"
3125 user, and better instructions. Thanks to Ondrej Mikle for the
3126 patch series. Fixes bug 6043.
3127 - On OpenSUSE, create the /var/run/tor directory on startup if it
3128 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
3130 o Code refactoring (safety):
3131 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3132 10 lines. Also, don't nest them. Doing so in the past has
3133 led to hard-to-debug code. The new style is to use the
3134 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3135 - Use macros to indicate OpenSSL versions, so we don't need to worry
3136 about accidental hexadecimal bit shifts.
3137 - Use tor_sscanf() in place of scanf() in more places through the
3138 code. This makes us a little more locale-independent, and
3139 should help shut up code-analysis tools that can't tell
3140 a safe sscanf string from a dangerous one.
3141 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3142 - Use the smartlist_add_asprintf() alias more consistently.
3144 o Code refactoring (consolidate):
3145 - A major revision to our internal node-selecting and listing logic.
3146 Tor already had at least two major ways to look at the question of
3147 "which Tor servers do we know about": a list of router descriptors,
3148 and a list of entries in the current consensus. With
3149 microdescriptors, we're adding a third. Having so many systems
3150 without an abstraction layer over them was hurting the codebase.
3151 Now, we have a new "node_t" abstraction that presents a consistent
3152 interface to a client's view of a Tor node, and holds (nearly) all
3153 of the mutable state formerly in routerinfo_t and routerstatus_t.
3154 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3155 Libevent's notion of cached time when possible.
3156 - Remove duplicate code for invoking getrlimit() from control.c.
3157 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3158 own homebrewed ssl_state_to_string() replacement. Patch from
3159 Emile Snyder. Fixes bug 4653.
3160 - Change the symmetric cipher interface so that creating and
3161 initializing a stream cipher are no longer separate functions.
3163 o Code refactoring (separate):
3164 - Make a new "entry connection" struct as an internal subtype of "edge
3165 connection", to simplify the code and make exit connections smaller.
3166 - Split connection_about_to_close() into separate functions for each
3168 - Rewrite the listener-selection logic so that parsing which ports
3169 we want to listen on is now separate from binding to the ports
3172 o Code refactoring (name changes):
3173 - Rename a handful of old identifiers, mostly related to crypto
3174 structures and crypto functions. By convention, our "create an
3175 object" functions are called "type_new()", our "free an object"
3176 functions are called "type_free()", and our types indicate that
3177 they are types only with a final "_t". But a handful of older
3178 types and functions broke these rules, with function names like
3179 "type_create" or "subsystem_op_type", or with type names like
3181 - Rename Tor functions that turn strings into addresses, so that
3182 "parse" indicates that no hostname resolution occurs, and
3183 "lookup" indicates that hostname resolution may occur. This
3184 should help prevent mistakes in the future. Fixes bug 3512.
3185 - Use the name "CERTS" consistently to refer to the new cell type;
3186 we were calling it CERT in some places and CERTS in others.
3187 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3188 invalid value, rather than just -1.
3189 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3190 can pick them up when the tests aren't disabled. Bugfix on
3191 0.2.2.4-alpha which introduced tinytest.
3193 o Code refactoring (other):
3194 - Defensively refactor rend_mid_rendezvous() so that protocol
3195 violations and length checks happen in the beginning. Fixes
3197 - Remove the pure attribute from all functions that used it
3198 previously. In many cases we assigned it incorrectly, because the
3199 functions might assert or call impure functions, and we don't have
3200 evidence that keeping the pure attribute is worthwhile. Implements
3201 changes suggested in ticket 4421.
3202 - Move the replay-detection cache for the RSA-encrypted parts of
3203 INTRODUCE2 cells to the introduction point data structures.
3204 Previously, we would use one replay-detection cache per hidden
3205 service. Required by fix for bug 3460.
3206 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3207 no longer link against Libevent: they never used it, but
3208 our library structure used to force them to link it.
3210 o Removed features and files:
3211 - Remove all internal support for unpadded RSA. We never used it, and
3212 it would be a bad idea to start.
3213 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3215 - Remove some redundant #include directives throughout the code.
3216 Patch from Andrea Gelmini.
3217 - Remove some old code to remember statistics about which descriptors
3218 we've served as a directory mirror. The feature wasn't used and
3219 is outdated now that microdescriptors are around.
3220 - Remove some old code to work around even older versions of Tor that
3221 used forked processes to handle DNS requests. Such versions of Tor
3222 are no longer in use as relays.
3223 - The "torify" script no longer supports the "tsocks" socksifier
3224 tool, since tsocks doesn't support DNS and UDP right for Tor.
3225 Everyone should be using torsocks instead. Fixes bugs 3530 and
3226 5180. Based on a patch by "ugh".
3227 - Remove the torrc.bridge file: we don't use it for anything, and
3228 it had become badly desynchronized from torrc.sample. Resolves
3232 - Begin a doc/state-contents.txt file to explain the contents of
3233 the Tor state file. Fixes bug 2987.
3234 - Clarify the documentation for the Alternate*Authority options.
3236 - Document the --defaults-torrc option, and the new semantics for
3237 overriding, extending, and clearing lists of options. Closes
3239 - Add missing man page documentation for consensus and microdesc
3240 files. Resolves ticket 6732.
3241 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3243 o Documentation fixes:
3244 - Improve the manual's documentation for the NT Service command-line
3245 options. Addresses ticket 3964.
3246 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3247 - Document the changes to the ORPort and DirPort options, and the
3248 fact that {OR/Dir}ListenAddress is now unnecessary (and
3249 therefore deprecated). Resolves ticket 5597.
3250 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3251 - Clarify that hidden services are TCP only. Fixes bug 6024.
3254 Changes in version 0.2.2.39 - 2012-09-11
3255 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
3259 - Fix an assertion failure in tor_timegm() that could be triggered
3260 by a badly formatted directory object. Bug found by fuzzing with
3261 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3262 - Do not crash when comparing an address with port value 0 to an
3263 address policy. This bug could have been used to cause a remote
3264 assertion failure by or against directory authorities, or to
3265 allow some applications to crash clients. Fixes bug 6690; bugfix
3269 Changes in version 0.2.2.38 - 2012-08-12
3270 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3271 attack that could in theory leak path information.
3274 - Avoid an uninitialized memory read when reading a vote or consensus
3275 document that has an unrecognized flavor name. This read could
3276 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3277 - Try to leak less information about what relays a client is
3278 choosing to a side-channel attacker. Previously, a Tor client would
3279 stop iterating through the list of available relays as soon as it
3280 had chosen one, thus finishing a little earlier when it picked
3281 a router earlier in the list. If an attacker can recover this
3282 timing information (nontrivial but not proven to be impossible),
3283 they could learn some coarse-grained information about which relays
3284 a client was picking (middle nodes in particular are likelier to
3285 be affected than exits). The timing attack might be mitigated by
3286 other factors (see bug 6537 for some discussion), but it's best
3287 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3290 Changes in version 0.2.2.37 - 2012-06-06
3291 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3292 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3296 - Work around a bug in OpenSSL that broke renegotiation with TLS
3297 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3298 the v2 Tor connection protocol when both sides were using OpenSSL
3299 1.0.1 would fail. Resolves ticket 6033.
3300 - When waiting for a client to renegotiate, don't allow it to add
3301 any bytes to the input buffer. This fixes a potential DoS issue.
3302 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3303 - Fix an edge case where if we fetch or publish a hidden service
3304 descriptor, we might build a 4-hop circuit and then use that circuit
3305 for exiting afterwards -- even if the new last hop doesn't obey our
3306 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3309 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3310 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3313 - Tell GCC and Clang to check for any errors in format strings passed
3314 to the tor_v*(print|scan)f functions.
3317 Changes in version 0.2.2.36 - 2012-05-24
3318 Tor 0.2.2.36 updates the addresses for two of the eight directory
3319 authorities, fixes some potential anonymity and security issues,
3320 and fixes several crash bugs.
3322 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3323 known flaws, and nobody should be using them. You should upgrade. If
3324 you're using a Linux or BSD and its packages are obsolete, stop using
3325 those packages and upgrade anyway.
3327 o Directory authority changes:
3328 - Change IP address for maatuska (v3 directory authority).
3329 - Change IP address for ides (v3 directory authority), and rename
3333 - When building or running with any version of OpenSSL earlier
3334 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3335 versions have a bug (CVE-2011-4576) in which their block cipher
3336 padding includes uninitialized data, potentially leaking sensitive
3337 information to any peer with whom they make a SSLv3 connection. Tor
3338 does not use SSL v3 by default, but a hostile client or server
3339 could force an SSLv3 connection in order to gain information that
3340 they shouldn't have been able to get. The best solution here is to
3341 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3342 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3343 to make sure that the bug can't happen.
3344 - Never use a bridge or a controller-supplied node as an exit, even
3345 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3346 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3347 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3348 - Only build circuits if we have a sufficient threshold of the total
3349 descriptors that are marked in the consensus with the "Exit"
3350 flag. This mitigates an attack proposed by wanoskarnet, in which
3351 all of a client's bridges collude to restrict the exit nodes that
3352 the client knows about. Fixes bug 5343.
3353 - Provide controllers with a safer way to implement the cookie
3354 authentication mechanism. With the old method, if another locally
3355 running program could convince a controller that it was the Tor
3356 process, then that program could trick the controller into telling
3357 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3358 authentication method uses a challenge-response approach to prevent
3359 this attack. Fixes bug 5185; implements proposal 193.
3362 - Avoid logging uninitialized data when unable to decode a hidden
3363 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3364 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3365 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3367 - Fix builds when the path to sed, openssl, or sha1sum contains
3368 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3370 - Correct our replacements for the timeradd() and timersub() functions
3371 on platforms that lack them (for example, Windows). The timersub()
3372 function is used when expiring circuits, while timeradd() is
3373 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3374 bugfix on 0.2.2.24-alpha.
3375 - Fix the SOCKET_OK test that we use to tell when socket
3376 creation fails so that it works on Win64. Fixes part of bug 4533;
3377 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3380 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3381 Fixes bug 5346; bugfix on 0.0.8pre3.
3382 - Make our number-parsing functions always treat too-large values
3383 as an error, even when those values exceed the width of the
3384 underlying type. Previously, if the caller provided these
3385 functions with minima or maxima set to the extreme values of the
3386 underlying integer type, these functions would return those
3387 values on overflow rather than treating overflow as an error.
3388 Fixes part of bug 5786; bugfix on 0.0.9.
3389 - Older Linux kernels erroneously respond to strange nmap behavior
3390 by having accept() return successfully with a zero-length
3391 socket. When this happens, just close the connection. Previously,
3392 we would try harder to learn the remote address: but there was
3393 no such remote address to learn, and our method for trying to
3394 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3395 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3396 - Correct parsing of certain date types in parse_http_time().
3397 Without this patch, If-Modified-Since would behave
3398 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3399 Esteban Manchado Velázques.
3400 - Change the BridgePassword feature (part of the "bridge community"
3401 design, which is not yet implemented) to use a time-independent
3402 comparison. The old behavior might have allowed an adversary
3403 to use timing to guess the BridgePassword value. Fixes bug 5543;
3404 bugfix on 0.2.0.14-alpha.
3405 - Detect and reject certain misformed escape sequences in
3406 configuration values. Previously, these values would cause us
3407 to crash if received in a torrc file or over an authenticated
3408 control port. Bug found by Esteban Manchado Velázquez, and
3409 independently by Robert Connolly from Matta Consulting who further
3410 noted that it allows a post-authentication heap overflow. Patch
3411 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3412 bugfix on 0.2.0.16-alpha.
3413 - Fix a compile warning when using the --enable-openbsd-malloc
3414 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3415 - During configure, detect when we're building with clang version
3416 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3417 CFLAGS. clang doesn't support them yet.
3418 - When sending an HTTP/1.1 proxy request, include a Host header.
3419 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3420 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3421 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3422 - If we hit the error case where routerlist_insert() replaces an
3423 existing (old) server descriptor, make sure to remove that
3424 server descriptor from the old_routers list. Fix related to bug
3425 1776. Bugfix on 0.2.2.18-alpha.
3427 o Minor bugfixes (documentation and log messages):
3428 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3429 Fixes bug 4856; bugfix on Tor 0.0.6.
3430 - Update "ClientOnly" man page entry to explain that there isn't
3431 really any point to messing with it. Resolves ticket 5005.
3432 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3433 directory authority option (introduced in Tor 0.2.2.34).
3434 - Downgrade the "We're missing a certificate" message from notice
3435 to info: people kept mistaking it for a real problem, whereas it
3436 is seldom the problem even when we are failing to bootstrap. Fixes
3437 bug 5067; bugfix on 0.2.0.10-alpha.
3438 - Correctly spell "connect" in a log message on failure to create a
3439 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3440 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3441 circuits. Fixes issue 5259.
3444 - Directory authorities now reject versions of Tor older than
3445 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3446 inclusive. These versions accounted for only a small fraction of
3447 the Tor network, and have numerous known security issues. Resolves
3449 - Update to the May 1 2012 Maxmind GeoLite Country database.
3452 - When sending or relaying a RELAY_EARLY cell, we used to convert
3453 it to a RELAY cell if the connection was using the v1 link
3454 protocol. This was a workaround for older versions of Tor, which
3455 didn't handle RELAY_EARLY cells properly. Now that all supported
3456 versions can handle RELAY_EARLY cells, and now that we're enforcing
3457 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3458 remove this workaround. Addresses bug 4786.
3461 Changes in version 0.2.2.35 - 2011-12-16
3462 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3463 buffers code. Absolutely everybody should upgrade.
3465 The bug relied on an incorrect calculation when making data continuous
3466 in one of our IO buffers, if the first chunk of the buffer was
3467 misaligned by just the wrong amount. The miscalculation would allow an
3468 attacker to overflow a piece of heap-allocated memory. To mount this
3469 attack, the attacker would need to either open a SOCKS connection to
3470 Tor's SocksPort (usually restricted to localhost), or target a Tor
3471 instance configured to make its connections through a SOCKS proxy
3472 (which Tor does not do by default).
3474 Good security practice requires that all heap-overflow bugs should be
3475 presumed to be exploitable until proven otherwise, so we are treating
3476 this as a potential code execution attack. Please upgrade immediately!
3477 This bug does not affect bufferevents-based builds of Tor. Special
3478 thanks to "Vektor" for reporting this issue to us!
3480 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3481 crash bugs for unusual configurations, and a long-term bug that
3482 would prevent Tor from starting on Windows machines with draconian
3485 With this release, we remind everyone that 0.2.0.x has reached its
3486 formal end-of-life. Those Tor versions have many known flaws, and
3487 nobody should be using them. You should upgrade -- ideally to the
3488 0.2.2.x series. If you're using a Linux or BSD and its packages are
3489 obsolete, stop using those packages and upgrade anyway.
3491 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3492 longer receive support after some time in early 2012.
3495 - Fix a heap overflow bug that could occur when trying to pull
3496 data into the first chunk of a buffer, when that chunk had
3497 already had some data drained from it. Fixes CVE-2011-2778;
3498 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3499 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3500 that it doesn't attempt to allocate a socketpair. This could cause
3501 some problems on Windows systems with overzealous firewalls. Fix for
3502 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3504 - If we mark an OR connection for close based on a cell we process,
3505 don't process any further cells on it. We already avoid further
3506 reads on marked-for-close connections, but now we also discard the
3507 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3508 which was the first version where we might mark a connection for
3509 close based on processing a cell on it.
3510 - Correctly sanity-check that we don't underflow on a memory
3511 allocation (and then assert) for hidden service introduction
3512 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3513 bugfix on 0.2.1.5-alpha.
3514 - Fix a memory leak when we check whether a hidden service
3515 descriptor has any usable introduction points left. Fixes bug
3516 4424. Bugfix on 0.2.2.25-alpha.
3517 - Don't crash when we're running as a relay and don't have a GeoIP
3518 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3519 we've had in the 0.2.3.x branch already.
3520 - When running as a client, do not print a misleading (and plain
3521 wrong) log message that we're collecting "directory request"
3522 statistics: clients don't collect statistics. Also don't create a
3523 useless (because empty) stats file in the stats/ directory. Fixes
3524 bug 4353; bugfix on 0.2.2.34.
3527 - Detect failure to initialize Libevent. This fix provides better
3528 detection for future instances of bug 4457.
3529 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3530 function. This was eating up hideously large amounts of time on some
3531 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3532 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3533 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3535 - Don't warn about unused log_mutex in log.c when building with
3536 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3537 0.1.0.6-rc which introduced --disable-threads.
3538 - When configuring, starting, or stopping an NT service, stop
3539 immediately after the service configuration attempt has succeeded
3540 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3541 - When sending a NETINFO cell, include the original address
3542 received for the other side, not its canonical address. Found
3543 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3544 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3545 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3546 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3547 occurred when a client tried to fetch a descriptor for a bridge
3548 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3549 - Backport fixes for a pair of compilation warnings on Windows.
3550 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3551 - If we had ever tried to call tor_addr_to_str on an address of
3552 unknown type, we would have done a strdup on an uninitialized
3553 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3554 Reported by "troll_un".
3555 - Correctly detect and handle transient lookup failures from
3556 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3557 Reported by "troll_un".
3558 - Fix null-pointer access that could occur if TLS allocation failed.
3559 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3560 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3561 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3564 - Add two new config options for directory authorities:
3565 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3566 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3567 that is always sufficient to satisfy the bandwidth requirement for
3568 the Guard flag. Now it will be easier for researchers to simulate
3569 Tor networks with different values. Resolves ticket 4484.
3570 - When Tor ignores a hidden service specified in its configuration,
3571 include the hidden service's directory in the warning message.
3572 Previously, we would only tell the user that some hidden service
3573 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3574 - Update to the December 6 2011 Maxmind GeoLite Country database.
3576 o Packaging changes:
3577 - Make it easier to automate expert package builds on Windows,
3578 by removing an absolute path from makensis.exe command.
3581 Changes in version 0.2.1.32 - 2011-12-16
3582 Tor 0.2.1.32 backports important security and privacy fixes for
3583 oldstable. This release is intended only for package maintainers and
3584 others who cannot use the 0.2.2 stable series. All others should be
3585 using Tor 0.2.2.x or newer.
3587 The Tor 0.2.1.x series will reach formal end-of-life some time in
3588 early 2012; we will stop releasing patches for it then.
3590 o Major bugfixes (also included in 0.2.2.x):
3591 - Correctly sanity-check that we don't underflow on a memory
3592 allocation (and then assert) for hidden service introduction
3593 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3594 bugfix on 0.2.1.5-alpha.
3595 - Fix a heap overflow bug that could occur when trying to pull
3596 data into the first chunk of a buffer, when that chunk had
3597 already had some data drained from it. Fixes CVE-2011-2778;
3598 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3601 - Update to the December 6 2011 Maxmind GeoLite Country database.
3604 Changes in version 0.2.2.34 - 2011-10-26
3605 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3606 can deanonymize Tor users. Everybody should upgrade.
3608 The attack relies on four components: 1) Clients reuse their TLS cert
3609 when talking to different relays, so relays can recognize a user by
3610 the identity key in her cert. 2) An attacker who knows the client's
3611 identity key can probe each guard relay to see if that identity key
3612 is connected to that guard relay right now. 3) A variety of active
3613 attacks in the literature (starting from "Low-Cost Traffic Analysis
3614 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3615 discover the guard relays that a Tor user visiting the website is using.
3616 4) Clients typically pick three guards at random, so the set of guards
3617 for a given user could well be a unique fingerprint for her. This
3618 release fixes components #1 and #2, which is enough to block the attack;
3619 the other two remain as open research problems. Special thanks to
3620 "frosty_un" for reporting the issue to us!
3622 Clients should upgrade so they are no longer recognizable by the TLS
3623 certs they present. Relays should upgrade so they no longer allow a
3624 remote attacker to probe them to test whether unpatched clients are
3625 currently connected to them.
3627 This release also fixes several vulnerabilities that allow an attacker
3628 to enumerate bridge relays. Some bridge enumeration attacks still
3629 remain; see for example proposal 188.
3631 o Privacy/anonymity fixes (clients):
3632 - Clients and bridges no longer send TLS certificate chains on
3633 outgoing OR connections. Previously, each client or bridge would
3634 use the same cert chain for all outgoing OR connections until
3635 its IP address changes, which allowed any relay that the client
3636 or bridge contacted to determine which entry guards it is using.
3637 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3638 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3639 no longer considers that connection as suitable for satisfying a
3640 circuit EXTEND request. Now relays can protect clients from the
3641 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3642 - Directory authorities no longer assign the Guard flag to relays
3643 that haven't upgraded to the above "refuse EXTEND requests
3644 to client connections" fix. Now directory authorities can
3645 protect clients from the CVE-2011-2768 issue even if neither
3646 the clients nor the relays have upgraded yet. There's a new
3647 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3648 to let us transition smoothly, else tomorrow there would be no
3651 o Privacy/anonymity fixes (bridge enumeration):
3652 - Bridge relays now do their directory fetches inside Tor TLS
3653 connections, like all the other clients do, rather than connecting
3654 directly to the DirPort like public relays do. Removes another
3655 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3656 - Bridges relays now build circuits for themselves in a more similar
3657 way to how clients build them. Removes another avenue for
3658 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3659 when bridges were introduced.
3660 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3661 that they initiated. Relays could distinguish incoming bridge
3662 connections from client connections, creating another avenue for
3663 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3664 Found by "frosty_un".
3667 - Fix a crash bug when changing node restrictions while a DNS lookup
3668 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3670 - Don't launch a useless circuit after failing to use one of a
3671 hidden service's introduction points. Previously, we would
3672 launch a new introduction circuit, but not set the hidden service
3673 which that circuit was intended to connect to, so it would never
3674 actually be used. A different piece of code would then create a
3675 new introduction circuit correctly. Bug reported by katmagic and
3676 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3679 - Change an integer overflow check in the OpenBSD_Malloc code so
3680 that GCC is less likely to eliminate it as impossible. Patch
3681 from Mansour Moufid. Fixes bug 4059.
3682 - When a hidden service turns an extra service-side introduction
3683 circuit into a general-purpose circuit, free the rend_data and
3684 intro_key fields first, so we won't leak memory if the circuit
3685 is cannibalized for use as another service-side introduction
3686 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3687 - Bridges now skip DNS self-tests, to act a little more stealthily.
3688 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3689 bridges. Patch by "warms0x".
3690 - Fix internal bug-checking logic that was supposed to catch
3691 failures in digest generation so that it will fail more robustly
3692 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3693 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3694 - Report any failure in init_keys() calls launched because our
3695 IP address has changed. Spotted by Coverity Scan. Bugfix on
3696 0.1.1.4-alpha; fixes CID 484.
3698 o Minor bugfixes (log messages and documentation):
3699 - Remove a confusing dollar sign from the example fingerprint in the
3700 man page, and also make the example fingerprint a valid one. Fixes
3701 bug 4309; bugfix on 0.2.1.3-alpha.
3702 - The next version of Windows will be called Windows 8, and it has
3703 a major version of 6, minor version of 2. Correctly identify that
3704 version instead of calling it "Very recent version". Resolves
3705 ticket 4153; reported by funkstar.
3706 - Downgrade log messages about circuit timeout calibration from
3707 "notice" to "info": they don't require or suggest any human
3708 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3709 bugfix on 0.2.2.14-alpha.
3712 - Turn on directory request statistics by default and include them in
3713 extra-info descriptors. Don't break if we have no GeoIP database.
3714 Backported from 0.2.3.1-alpha; implements ticket 3951.
3715 - Update to the October 4 2011 Maxmind GeoLite Country database.
3718 Changes in version 0.2.1.31 - 2011-10-26
3719 Tor 0.2.1.31 backports important security and privacy fixes for
3720 oldstable. This release is intended only for package maintainers and
3721 others who cannot use the 0.2.2 stable series. All others should be
3722 using Tor 0.2.2.x or newer.
3724 o Security fixes (also included in 0.2.2.x):
3725 - Replace all potentially sensitive memory comparison operations
3726 with versions whose runtime does not depend on the data being
3727 compared. This will help resist a class of attacks where an
3728 adversary can use variations in timing information to learn
3729 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3730 implementation by Robert Ransom based partially on code by DJB.)
3731 - Fix an assert in parsing router descriptors containing IPv6
3732 addresses. This one took down the directory authorities when
3733 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3735 o Privacy/anonymity fixes (also included in 0.2.2.x):
3736 - Clients and bridges no longer send TLS certificate chains on
3737 outgoing OR connections. Previously, each client or bridge would
3738 use the same cert chain for all outgoing OR connections until
3739 its IP address changes, which allowed any relay that the client
3740 or bridge contacted to determine which entry guards it is using.
3741 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3742 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3743 no longer considers that connection as suitable for satisfying a
3744 circuit EXTEND request. Now relays can protect clients from the
3745 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3746 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3747 that they initiated. Relays could distinguish incoming bridge
3748 connections from client connections, creating another avenue for
3749 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3750 Found by "frosty_un".
3751 - When receiving a hidden service descriptor, check that it is for
3752 the hidden service we wanted. Previously, Tor would store any
3753 hidden service descriptors that a directory gave it, whether it
3754 wanted them or not. This wouldn't have let an attacker impersonate
3755 a hidden service, but it did let directories pre-seed a client
3756 with descriptors that it didn't want. Bugfix on 0.0.6.
3757 - Avoid linkability based on cached hidden service descriptors: forget
3758 all hidden service descriptors cached as a client when processing a
3759 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3760 - Make the bridge directory authority refuse to answer directory
3761 requests for "all" descriptors. It used to include bridge
3762 descriptors in its answer, which was a major information leak.
3763 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3764 - Don't attach new streams to old rendezvous circuits after SIGNAL
3765 NEWNYM. Previously, we would keep using an existing rendezvous
3766 circuit if it remained open (i.e. if it were kept open by a
3767 long-lived stream, or if a new stream were attached to it before
3768 Tor could notice that it was old and no longer in use). Bugfix on
3769 0.1.1.15-rc; fixes bug 3375.
3771 o Minor bugfixes (also included in 0.2.2.x):
3772 - When we restart our relay, we might get a successful connection
3773 from the outside before we've started our reachability tests,
3774 triggering a warning: "ORPort found reachable, but I have no
3775 routerinfo yet. Failing to inform controller of success." This
3776 bug was harmless unless Tor is running under a controller
3777 like Vidalia, in which case the controller would never get a
3778 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3780 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3781 enabled. Fixes bug 1526.
3782 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3783 anything since 0.2.1.16-rc.
3784 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3785 None of the cases where we did this before were wrong, but by making
3786 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3787 - Fix a rare crash bug that could occur when a client was configured
3788 with a large number of bridges. Fixes bug 2629; bugfix on
3789 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3790 - Correct the warning displayed when a rendezvous descriptor exceeds
3791 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3793 - Fix an uncommon assertion failure when running with DNSPort under
3794 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3795 - When warning about missing zlib development packages during compile,
3796 give the correct package names. Bugfix on 0.2.0.1-alpha.
3797 - Require that introduction point keys and onion keys have public
3798 exponent 65537. Bugfix on 0.2.0.10-alpha.
3799 - Do not crash when our configuration file becomes unreadable, for
3800 example due to a permissions change, between when we start up
3801 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3803 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3805 - Always NUL-terminate the sun_path field of a sockaddr_un before
3806 passing it to the kernel. (Not a security issue: kernels are
3807 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3808 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3809 - Don't stack-allocate the list of supplementary GIDs when we're
3810 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3811 could take up to 256K, which is way too much stack. Found by
3812 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3814 o Minor bugfixes (only in 0.2.1.x):
3815 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3816 rely on them. Bugfix on 0.2.1.30.
3817 - Use git revisions instead of svn revisions when generating our
3818 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3820 o Minor features (also included in 0.2.2.x):
3821 - Adjust the expiration time on our SSL session certificates to
3822 better match SSL certs seen in the wild. Resolves ticket 4014.
3823 - Allow nameservers with IPv6 address. Resolves bug 2574.
3824 - Update to the October 4 2011 Maxmind GeoLite Country database.
3827 Changes in version 0.2.2.33 - 2011-09-13
3828 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3829 TLS handshake that makes relays and bridges that run this new version
3830 reachable from Iran again.
3833 - Avoid an assertion failure when reloading a configuration with
3834 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3835 3923; bugfix on 0.2.2.25-alpha.
3837 o Minor features (security):
3838 - Check for replays of the public-key encrypted portion of an
3839 INTRODUCE1 cell, in addition to the current check for replays of
3840 the g^x value. This prevents a possible class of active attacks
3841 by an attacker who controls both an introduction point and a
3842 rendezvous point, and who uses the malleability of AES-CTR to
3843 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3844 that these attacks are infeasible (requiring the attacker to send
3845 on the order of zettabytes of altered cells in a short interval),
3846 but we'd rather block them off in case there are any classes of
3847 this attack that we missed. Reported by Willem Pinckaers.
3850 - Adjust the expiration time on our SSL session certificates to
3851 better match SSL certs seen in the wild. Resolves ticket 4014.
3852 - Change the default required uptime for a relay to be accepted as
3853 a HSDir (hidden service directory) from 24 hours to 25 hours.
3854 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3855 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3856 authorities to abstain from voting on assignment of the HSDir
3857 consensus flag. Related to bug 2649.
3858 - Update to the September 6 2011 Maxmind GeoLite Country database.
3860 o Minor bugfixes (documentation and log messages):
3861 - Correct the man page to explain that HashedControlPassword and
3862 CookieAuthentication can both be set, in which case either method
3863 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3864 when we decided to allow these config options to both be set. Issue
3866 - Demote the 'replay detected' log message emitted when a hidden
3867 service receives the same Diffie-Hellman public key in two different
3868 INTRODUCE2 cells to info level. A normal Tor client can cause that
3869 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3870 fixes part of bug 2442.
3871 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3872 level. There is nothing that a hidden service's operator can do
3873 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3875 - Clarify a log message specifying the characters permitted in
3876 HiddenServiceAuthorizeClient client names. Previously, the log
3877 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3878 given the impression that every ASCII character between "+" and "_"
3879 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3882 - Provide a substitute implementation of lround() for MSVC, which
3883 apparently lacks it. Patch from Gisle Vanem.
3884 - Clean up some code issues that prevented Tor from building on older
3885 BSDs. Fixes bug 3894; reported by "grarpamp".
3886 - Search for a platform-specific version of "ar" when cross-compiling.
3887 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3890 Changes in version 0.2.2.32 - 2011-08-27
3891 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3892 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3893 a founder of the PETS community, a leader in our field, a mentor,
3894 and a friend. He left us with these words: "I had the possibility
3895 to contribute to this world that is not as it should be. I hope I
3896 could help in some areas to make the world a better place, and that
3897 I could also encourage other people to be engaged in improving the
3898 world. Please, stay engaged. This world needs you, your love, your
3899 initiative -- now I cannot be part of that anymore."
3901 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3902 ready. More than two years in the making, this release features improved
3903 client performance and hidden service reliability, better compatibility
3904 for Android, correct behavior for bridges that listen on more than
3905 one address, more extensible and flexible directory object handling,
3906 better reporting of network statistics, improved code security, and
3907 many many other features and bugfixes.
3909 o Major features (client performance):
3910 - When choosing which cells to relay first, relays now favor circuits
3911 that have been quiet recently, to provide lower latency for
3912 low-volume circuits. By default, relays enable or disable this
3913 feature based on a setting in the consensus. They can override
3914 this default by using the new "CircuitPriorityHalflife" config
3915 option. Design and code by Ian Goldberg, Can Tang, and Chris
3917 - Directory authorities now compute consensus weightings that instruct
3918 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
3919 and no flag. Clients use these weightings to distribute network load
3920 more evenly across these different relay types. The weightings are
3921 in the consensus so we can change them globally in the future. Extra
3922 thanks to "outofwords" for finding some nasty security bugs in
3923 the first implementation of this feature.
3925 o Major features (client performance, circuit build timeout):
3926 - Tor now tracks how long it takes to build client-side circuits
3927 over time, and adapts its timeout to local network performance.
3928 Since a circuit that takes a long time to build will also provide
3929 bad performance, we get significant latency improvements by
3930 discarding the slowest 20% of circuits. Specifically, Tor creates
3931 circuits more aggressively than usual until it has enough data
3932 points for a good timeout estimate. Implements proposal 151.
3933 - Circuit build timeout constants can be controlled by consensus
3934 parameters. We set good defaults for these parameters based on
3935 experimentation on broadband and simulated high-latency links.
3936 - Circuit build time learning can be disabled via consensus parameter
3937 or by the client via a LearnCircuitBuildTimeout config option. We
3938 also automatically disable circuit build time calculation if either
3939 AuthoritativeDirectory is set, or if we fail to write our state
3940 file. Implements ticket 1296.
3942 o Major features (relays use their capacity better):
3943 - Set SO_REUSEADDR socket option on all sockets, not just
3944 listeners. This should help busy exit nodes avoid running out of
3945 useable ports just because all the ports have been used in the
3946 near past. Resolves issue 2850.
3947 - Relays now save observed peak bandwidth throughput rates to their
3948 state file (along with total usage, which was already saved),
3949 so that they can determine their correct estimated bandwidth on
3950 restart. Resolves bug 1863, where Tor relays would reset their
3951 estimated bandwidth to 0 after restarting.
3952 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3953 should give us approximately 40-50% more Guard-flagged nodes,
3954 improving the anonymity the Tor network can provide and also
3955 decreasing the dropoff in throughput that relays experience when
3956 they first get the Guard flag.
3957 - Directory authorities now take changes in router IP address and
3958 ORPort into account when determining router stability. Previously,
3959 if a router changed its IP or ORPort, the authorities would not
3960 treat it as having any downtime for the purposes of stability
3961 calculation, whereas clients would experience downtime since the
3962 change would take a while to propagate to them. Resolves issue 1035.
3963 - New AccelName and AccelDir options add support for dynamic OpenSSL
3964 hardware crypto acceleration engines.
3966 o Major features (relays control their load better):
3967 - Exit relays now try harder to block exit attempts from unknown
3968 relays, to make it harder for people to use them as one-hop proxies
3969 a la tortunnel. Controlled by the refuseunknownexits consensus
3970 parameter (currently enabled), or you can override it on your
3971 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
3972 based on a variant of proposal 163.
3973 - Add separate per-conn write limiting to go with the per-conn read
3974 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
3975 but never per-conn write limits.
3976 - New consensus params "bwconnrate" and "bwconnburst" to let us
3977 rate-limit client connections as they enter the network. It's
3978 controlled in the consensus so we can turn it on and off for
3979 experiments. It's starting out off. Based on proposal 163.
3981 o Major features (controllers):
3982 - Export GeoIP information on bridge usage to controllers even if we
3983 have not yet been running for 24 hours. Now Vidalia bridge operators
3984 can get more accurate and immediate feedback about their
3985 contributions to the network.
3986 - Add an __OwningControllerProcess configuration option and a
3987 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
3988 that when it exits, Tor will shut down. Implements feature 3049.
3990 o Major features (directory authorities):
3991 - Directory authorities now create, vote on, and serve multiple
3992 parallel formats of directory data as part of their voting process.
3993 Partially implements Proposal 162: "Publish the consensus in
3995 - Directory authorities now agree on and publish small summaries
3996 of router information that clients can use in place of regular
3997 server descriptors. This transition will allow Tor 0.2.3 clients
3998 to use far less bandwidth for downloading information about the
3999 network. Begins the implementation of Proposal 158: "Clients
4000 download consensus + microdescriptors".
4001 - The directory voting system is now extensible to use multiple hash
4002 algorithms for signatures and resource selection. Newer formats
4003 are signed with SHA256, with a possibility for moving to a better
4004 hash algorithm in the future.
4005 - Directory authorities can now vote on arbitary integer values as
4006 part of the consensus process. This is designed to help set
4007 network-wide parameters. Implements proposal 167.
4009 o Major features and bugfixes (node selection):
4010 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4011 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
4012 options. Previously, we had been ambiguous in describing what
4013 counted as an "exit" node, and what operations exactly "StrictNodes
4014 0" would permit. This created confusion when people saw nodes built
4015 through unexpected circuits, and made it hard to tell real bugs from
4016 surprises. Now the intended behavior is:
4017 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4018 a node that delivers user traffic outside the Tor network.
4019 . "Entry", in the context of EntryNodes, means a node used as the
4020 first hop of a multihop circuit. It doesn't include direct
4021 connections to directory servers.
4022 . "ExcludeNodes" applies to all nodes.
4023 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4024 StrictNodes is set, Tor should avoid all nodes listed in
4025 ExcludeNodes, even when it will make user requests fail. When
4026 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4027 whenever it can, except when it must use an excluded node to
4028 perform self-tests, connect to a hidden service, provide a
4029 hidden service, fulfill a .exit request, upload directory
4030 information, or fetch directory information.
4031 Collectively, the changes to implement the behavior fix bug 1090.
4032 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4033 change during a config reload, mark and discard all our origin
4034 circuits. This fix should address edge cases where we change the
4035 config options and but then choose a circuit that we created before
4037 - Make EntryNodes config option much more aggressive even when
4038 StrictNodes is not set. Before it would prepend your requested
4039 entrynodes to your list of guard nodes, but feel free to use others
4040 after that. Now it chooses only from your EntryNodes if any of
4041 those are available, and only falls back to others if a) they're
4042 all down and b) StrictNodes is not set.
4043 - Now we refresh your entry guards from EntryNodes at each consensus
4044 fetch -- rather than just at startup and then they slowly rot as
4045 the network changes.
4046 - Add support for the country code "{??}" in torrc options like
4047 ExcludeNodes, to indicate all routers of unknown country. Closes
4049 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4050 a node is listed in both, it's treated as excluded.
4051 - ExcludeNodes now applies to directory nodes -- as a preference if
4052 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4053 Don't exclude all the directory authorities and set StrictNodes to 1
4054 unless you really want your Tor to break.
4055 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4056 - ExcludeExitNodes now overrides .exit requests.
4057 - We don't use bridges listed in ExcludeNodes.
4058 - When StrictNodes is 1:
4059 . We now apply ExcludeNodes to hidden service introduction points
4060 and to rendezvous points selected by hidden service users. This
4061 can make your hidden service less reliable: use it with caution!
4062 . If we have used ExcludeNodes on ourself, do not try relay
4063 reachability self-tests.
4064 . If we have excluded all the directory authorities, we will not
4065 even try to upload our descriptor if we're a relay.
4066 . Do not honor .exit requests to an excluded node.
4067 - When the set of permitted nodes changes, we now remove any mappings
4068 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4070 - We never cannibalize a circuit that had excluded nodes on it, even
4071 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4072 - Improve log messages related to excluded nodes.
4074 o Major features (misc):
4075 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4076 to help Tor build correctly for Android phones.
4077 - The options SocksPort, ControlPort, and so on now all accept a
4078 value "auto" that opens a socket on an OS-selected port. A
4079 new ControlPortWriteToFile option tells Tor to write its
4080 actual control port or ports to a chosen file. If the option
4081 ControlPortFileGroupReadable is set, the file is created as
4082 group-readable. Now users can run two Tor clients on the same
4083 system without needing to manually mess with parameters. Resolves
4084 part of ticket 3076.
4085 - Tor now supports tunneling all of its outgoing connections over
4086 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
4087 configuration options. Code by Christopher Davis.
4089 o Code security improvements:
4090 - Replace all potentially sensitive memory comparison operations
4091 with versions whose runtime does not depend on the data being
4092 compared. This will help resist a class of attacks where an
4093 adversary can use variations in timing information to learn
4094 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4095 implementation by Robert Ransom based partially on code by DJB.)
4096 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4097 Prevention (DEP) by default on Windows to make it harder for
4098 attackers to exploit vulnerabilities. Patch from John Brooks.
4099 - New "--enable-gcc-hardening" ./configure flag (off by default)
4100 to turn on gcc compile time hardening options. It ensures
4101 that signed ints have defined behavior (-fwrapv), enables
4102 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4103 with canaries (-fstack-protector-all), turns on ASLR protection if
4104 supported by the kernel (-fPIE, -pie), and adds additional security
4105 related warnings. Verified to work on Mac OS X and Debian Lenny.
4106 - New "--enable-linker-hardening" ./configure flag (off by default)
4107 to turn on ELF specific hardening features (relro, now). This does
4108 not work with Mac OS X or any other non-ELF binary format.
4109 - Always search the Windows system directory for system DLLs, and
4110 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4111 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4112 current and future memory pages via mlockall(). On supported
4113 platforms (modern Linux and probably BSD but not Windows or OS X),
4114 this should effectively disable any and all attempts to page out
4115 memory. This option requires that you start your Tor as root --
4116 if you use DisableAllSwap, please consider using the User option
4117 to properly reduce the privileges of your Tor.
4119 o Major bugfixes (crashes):
4120 - Fix crash bug on platforms where gmtime and localtime can return
4121 NULL. Windows 7 users were running into this one. Fixes part of bug
4122 2077. Bugfix on all versions of Tor. Found by boboper.
4123 - Introduce minimum/maximum values that clients will believe
4124 from the consensus. Now we'll have a better chance to avoid crashes
4125 or worse when a consensus param has a weird value.
4126 - Fix a rare crash bug that could occur when a client was configured
4127 with a large number of bridges. Fixes bug 2629; bugfix on
4128 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4129 - Do not crash when our configuration file becomes unreadable, for
4130 example due to a permissions change, between when we start up
4131 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4133 - If we're in the pathological case where there's no exit bandwidth
4134 but there is non-exit bandwidth, or no guard bandwidth but there
4135 is non-guard bandwidth, don't crash during path selection. Bugfix
4137 - Fix a crash bug when trying to initialize the evdns module in
4138 Libevent 2. Bugfix on 0.2.1.16-rc.
4140 o Major bugfixes (stability):
4141 - Fix an assert in parsing router descriptors containing IPv6
4142 addresses. This one took down the directory authorities when
4143 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4144 - Fix an uncommon assertion failure when running with DNSPort under
4145 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4146 - Treat an unset $HOME like an empty $HOME rather than triggering an
4147 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4148 - More gracefully handle corrupt state files, removing asserts
4149 in favor of saving a backup and resetting state.
4150 - Instead of giving an assertion failure on an internal mismatch
4151 on estimated freelist size, just log a BUG warning and try later.
4152 Mitigates but does not fix bug 1125.
4153 - Fix an assert that got triggered when using the TestingTorNetwork
4154 configuration option and then issuing a GETINFO config-text control
4155 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
4156 - If the cached cert file is unparseable, warn but don't exit.
4158 o Privacy fixes (relays/bridges):
4159 - Don't list Windows capabilities in relay descriptors. We never made
4160 use of them, and maybe it's a bad idea to publish them. Bugfix
4162 - If the Nickname configuration option isn't given, Tor would pick a
4163 nickname based on the local hostname as the nickname for a relay.
4164 Because nicknames are not very important in today's Tor and the
4165 "Unnamed" nickname has been implemented, this is now problematic
4166 behavior: It leaks information about the hostname without being
4167 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4168 introduced the Unnamed nickname. Reported by tagnaq.
4169 - Maintain separate TLS contexts and certificates for incoming and
4170 outgoing connections in bridge relays. Previously we would use the
4171 same TLS contexts and certs for incoming and outgoing connections.
4172 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4173 - Maintain separate identity keys for incoming and outgoing TLS
4174 contexts in bridge relays. Previously we would use the same
4175 identity keys for incoming and outgoing TLS contexts. Bugfix on
4176 0.2.0.3-alpha; addresses the other half of bug 988.
4177 - Make the bridge directory authority refuse to answer directory
4178 requests for "all descriptors". It used to include bridge
4179 descriptors in its answer, which was a major information leak.
4180 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4182 o Privacy fixes (clients):
4183 - When receiving a hidden service descriptor, check that it is for
4184 the hidden service we wanted. Previously, Tor would store any
4185 hidden service descriptors that a directory gave it, whether it
4186 wanted them or not. This wouldn't have let an attacker impersonate
4187 a hidden service, but it did let directories pre-seed a client
4188 with descriptors that it didn't want. Bugfix on 0.0.6.
4189 - Start the process of disabling ".exit" address notation, since it
4190 can be used for a variety of esoteric application-level attacks
4191 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
4193 - Reject attempts at the client side to open connections to private
4194 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
4195 a randomly chosen exit node. Attempts to do so are always
4196 ill-defined, generally prevented by exit policies, and usually
4197 in error. This will also help to detect loops in transparent
4198 proxy configurations. You can disable this feature by setting
4199 "ClientRejectInternalAddresses 0" in your torrc.
4200 - Log a notice when we get a new control connection. Now it's easier
4201 for security-conscious users to recognize when a local application
4202 is knocking on their controller door. Suggested by bug 1196.
4204 o Privacy fixes (newnym):
4205 - Avoid linkability based on cached hidden service descriptors: forget
4206 all hidden service descriptors cached as a client when processing a
4207 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4208 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4209 DNS cache entries, and virtual address mappings: that's what
4210 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4211 - Don't attach new streams to old rendezvous circuits after SIGNAL
4212 NEWNYM. Previously, we would keep using an existing rendezvous
4213 circuit if it remained open (i.e. if it were kept open by a
4214 long-lived stream, or if a new stream were attached to it before
4215 Tor could notice that it was old and no longer in use). Bugfix on
4216 0.1.1.15-rc; fixes bug 3375.
4218 o Major bugfixes (relay bandwidth accounting):
4219 - Fix a bug that could break accounting on 64-bit systems with large
4220 time_t values, making them hibernate for impossibly long intervals.
4221 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
4222 - Fix a bug in bandwidth accounting that could make us use twice
4223 the intended bandwidth when our interval start changes due to
4224 daylight saving time. Now we tolerate skew in stored vs computed
4225 interval starts: if the start of the period changes by no more than
4226 50% of the period's duration, we remember bytes that we transferred
4227 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4229 o Major bugfixes (bridges):
4230 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4231 on 0.2.0.3-alpha. Fixes bug 1113.
4232 - If you configure your bridge with a known identity fingerprint,
4233 and the bridge authority is unreachable (as it is in at least
4234 one country now), fall back to directly requesting the descriptor
4235 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4237 - Fix a bug where bridge users who configure the non-canonical
4238 address of a bridge automatically switch to its canonical
4239 address. If a bridge listens at more than one address, it
4240 should be able to advertise those addresses independently and
4241 any non-blocked addresses should continue to work. Bugfix on Tor
4242 0.2.0.3-alpha. Fixes bug 2510.
4243 - If you configure Tor to use bridge A, and then quit and
4244 configure Tor to use bridge B instead (or if you change Tor
4245 to use bridge B via the controller), it would happily continue
4246 to use bridge A if it's still reachable. While this behavior is
4247 a feature if your goal is connectivity, in some scenarios it's a
4248 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4249 - When the controller configures a new bridge, don't wait 10 to 60
4250 seconds before trying to fetch its descriptor. Bugfix on
4251 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4253 o Major bugfixes (directory authorities):
4254 - Many relays have been falling out of the consensus lately because
4255 not enough authorities know about their descriptor for them to get
4256 a majority of votes. When we deprecated the v2 directory protocol,
4257 we got rid of the only way that v3 authorities can hear from each
4258 other about other descriptors. Now authorities examine every v3
4259 vote for new descriptors, and fetch them from that authority. Bugfix
4261 - Authorities could be tricked into giving out the Exit flag to relays
4262 that didn't allow exiting to any ports. This bug could screw
4263 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4264 1238. Bug discovered by Martin Kowalczyk.
4265 - If all authorities restart at once right before a consensus vote,
4266 nobody will vote about "Running", and clients will get a consensus
4267 with no usable relays. Instead, authorities refuse to build a
4268 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4270 o Major bugfixes (stream-level fairness):
4271 - When receiving a circuit-level SENDME for a blocked circuit, try
4272 to package cells fairly from all the streams that had previously
4273 been blocked on that circuit. Previously, we had started with the
4274 oldest stream, and allowed each stream to potentially exhaust
4275 the circuit's package window. This gave older streams on any
4276 given circuit priority over newer ones. Fixes bug 1937. Detected
4277 originally by Camilo Viecco. This bug was introduced before the
4278 first Tor release, in svn commit r152: it is the new winner of
4279 the longest-lived bug prize.
4280 - Fix a stream fairness bug that would cause newer streams on a given
4281 circuit to get preference when reading bytes from the origin or
4282 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
4283 introduced before the first Tor release, in svn revision r152.
4284 - When the exit relay got a circuit-level sendme cell, it started
4285 reading on the exit streams, even if had 500 cells queued in the
4286 circuit queue already, so the circuit queue just grew and grew in
4287 some cases. We fix this by not re-enabling reading on receipt of a
4288 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4289 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4291 - Newly created streams were allowed to read cells onto circuits,
4292 even if the circuit's cell queue was blocked and waiting to drain.
4293 This created potential unfairness, as older streams would be
4294 blocked, but newer streams would gladly fill the queue completely.
4295 We add code to detect this situation and prevent any stream from
4296 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4299 o Major bugfixes (hidden services):
4300 - Apply circuit timeouts to opened hidden-service-related circuits
4301 based on the correct start time. Previously, we would apply the
4302 circuit build timeout based on time since the circuit's creation;
4303 it was supposed to be applied based on time since the circuit
4304 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4305 - Improve hidden service robustness: When we find that we have
4306 extended a hidden service's introduction circuit to a relay not
4307 listed as an introduction point in the HS descriptor we currently
4308 have, retry with an introduction point from the current
4309 descriptor. Previously we would just give up. Fixes bugs 1024 and
4310 1930; bugfix on 0.2.0.10-alpha.
4311 - Directory authorities now use data collected from their own
4312 uptime observations when choosing whether to assign the HSDir flag
4313 to relays, instead of trusting the uptime value the relay reports in
4314 its descriptor. This change helps prevent an attack where a small
4315 set of nodes with frequently-changing identity keys can blackhole
4316 a hidden service. (Only authorities need upgrade; others will be
4317 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4318 - Stop assigning the HSDir flag to relays that disable their
4319 DirPort (and thus will refuse to answer directory requests). This
4320 fix should dramatically improve the reachability of hidden services:
4321 hidden services and hidden service clients pick six HSDir relays
4322 to store and retrieve the hidden service descriptor, and currently
4323 about half of the HSDir relays will refuse to work. Bugfix on
4324 0.2.0.10-alpha; fixes part of bug 1693.
4326 o Major bugfixes (misc):
4327 - Clients now stop trying to use an exit node associated with a given
4328 destination by TrackHostExits if they fail to reach that exit node.
4329 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4330 - Fix a regression that caused Tor to rebind its ports if it receives
4331 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4332 - Remove an extra pair of quotation marks around the error
4333 message in control-port STATUS_GENERAL BUG events. Bugfix on
4334 0.1.2.6-alpha; fixes bug 3732.
4336 o Minor features (relays):
4337 - Ensure that no empty [dirreq-](read|write)-history lines are added
4338 to an extrainfo document. Implements ticket 2497.
4339 - When bandwidth accounting is enabled, be more generous with how
4340 much bandwidth we'll use up before entering "soft hibernation".
4341 Previously, we'd refuse new connections and circuits once we'd
4342 used up 95% of our allotment. Now, we use up 95% of our allotment,
4343 AND make sure that we have no more than 500MB (or 3 hours of
4344 expected traffic, whichever is lower) remaining before we enter
4346 - Relays now log the reason for publishing a new relay descriptor,
4347 so we have a better chance of hunting down instances of bug 1810.
4348 Resolves ticket 3252.
4349 - Log a little more clearly about the times at which we're no longer
4350 accepting new connections (e.g. due to hibernating). Resolves
4352 - When AllowSingleHopExits is set, print a warning to explain to the
4353 relay operator why most clients are avoiding her relay.
4354 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4355 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4356 clients are already deprecated because of security bugs.
4358 o Minor features (network statistics):
4359 - Directory mirrors that set "DirReqStatistics 1" write statistics
4360 about directory requests to disk every 24 hours. As compared to the
4361 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
4362 improvements: 1) stats are written to disk exactly every 24 hours;
4363 2) estimated shares of v2 and v3 requests are determined as mean
4364 values, not at the end of a measurement period; 3) unresolved
4365 requests are listed with country code '??'; 4) directories also
4366 measure download times.
4367 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
4368 number of exit streams and transferred bytes per port to disk every
4370 - Relays that set "CellStatistics 1" write statistics on how long
4371 cells spend in their circuit queues to disk every 24 hours.
4372 - Entry nodes that set "EntryStatistics 1" write statistics on the
4373 rough number and origins of connecting clients to disk every 24
4375 - Relays that write any of the above statistics to disk and set
4376 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
4377 their extra-info documents. Implements proposal 166.
4379 o Minor features (GeoIP and statistics):
4380 - Provide a log message stating which geoip file we're parsing
4381 instead of just stating that we're parsing the geoip file.
4382 Implements ticket 2432.
4383 - Make sure every relay writes a state file at least every 12 hours.
4384 Previously, a relay could go for weeks without writing its state
4385 file, and on a crash could lose its bandwidth history, capacity
4386 estimates, client country statistics, and so on. Addresses bug 3012.
4387 - Relays report the number of bytes spent on answering directory
4388 requests in extra-info descriptors similar to {read,write}-history.
4389 Implements enhancement 1790.
4390 - Report only the top 10 ports in exit-port stats in order not to
4391 exceed the maximum extra-info descriptor length of 50 KB. Implements
4393 - If writing the state file to disk fails, wait up to an hour before
4394 retrying again, rather than trying again each second. Fixes bug
4395 2346; bugfix on Tor 0.1.1.3-alpha.
4396 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4397 when we switch from being a public relay to a bridge. Otherwise
4398 there will still be clients that see the relay in their consensus,
4399 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
4401 - Update to the August 2 2011 Maxmind GeoLite Country database.
4403 o Minor features (clients):
4404 - When expiring circuits, use microsecond timers rather than
4405 one-second timers. This can avoid an unpleasant situation where a
4406 circuit is launched near the end of one second and expired right
4407 near the beginning of the next, and prevent fluctuations in circuit
4409 - If we've configured EntryNodes and our network goes away and/or all
4410 our entrynodes get marked down, optimistically retry them all when
4411 a new socks application request appears. Fixes bug 1882.
4412 - Always perform router selections using weighted relay bandwidth,
4413 even if we don't need a high capacity circuit at the time. Non-fast
4414 circuits now only differ from fast ones in that they can use relays
4415 not marked with the Fast flag. This "feature" could turn out to
4416 be a horrible bug; we should investigate more before it goes into
4418 - When we run out of directory information such that we can't build
4419 circuits, but then get enough that we can build circuits, log when
4420 we actually construct a circuit, so the user has a better chance of
4421 knowing what's going on. Fixes bug 1362.
4422 - Log SSL state transitions at debug level during handshake, and
4423 include SSL states in error messages. This may help debug future
4424 SSL handshake issues.
4426 o Minor features (directory authorities):
4427 - When a router changes IP address or port, authorities now launch
4428 a new reachability test for it. Implements ticket 1899.
4429 - Directory authorities now reject relays running any versions of
4430 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4431 known bugs that keep RELAY_EARLY cells from working on rendezvous
4432 circuits. Followup to fix for bug 2081.
4433 - Directory authorities now reject relays running any version of Tor
4434 older than 0.2.0.26-rc. That version is the earliest that fetches
4435 current directory information correctly. Fixes bug 2156.
4436 - Directory authorities now do an immediate reachability check as soon
4437 as they hear about a new relay. This change should slightly reduce
4438 the time between setting up a relay and getting listed as running
4439 in the consensus. It should also improve the time between setting
4440 up a bridge and seeing use by bridge users.
4441 - Directory authorities no longer launch a TLS connection to every
4442 relay as they startup. Now that we have 2k+ descriptors cached,
4443 the resulting network hiccup is becoming a burden. Besides,
4444 authorities already avoid voting about Running for the first half
4445 hour of their uptime.
4446 - Directory authorities now log the source of a rejected POSTed v3
4447 networkstatus vote, so we can track failures better.
4448 - Backport code from 0.2.3.x that allows directory authorities to
4449 clean their microdescriptor caches. Needed to resolve bug 2230.
4451 o Minor features (hidden services):
4452 - Use computed circuit-build timeouts to decide when to launch
4453 parallel introduction circuits for hidden services. (Previously,
4454 we would retry after 15 seconds.)
4455 - Don't allow v0 hidden service authorities to act as clients.
4456 Required by fix for bug 3000.
4457 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4458 by fix for bug 3000.
4459 - Make hidden services work better in private Tor networks by not
4460 requiring any uptime to join the hidden service descriptor
4461 DHT. Implements ticket 2088.
4462 - Log (at info level) when purging pieces of hidden-service-client
4463 state because of SIGNAL NEWNYM.
4465 o Minor features (controller interface):
4466 - New "GETINFO net/listeners/(type)" controller command to return
4467 a list of addresses and ports that are bound for listeners for a
4468 given connection type. This is useful when the user has configured
4469 "SocksPort auto" and the controller needs to know which port got
4470 chosen. Resolves another part of ticket 3076.
4471 - Have the controller interface give a more useful message than
4472 "Internal Error" in response to failed GETINFO requests.
4473 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4474 event, to give information on the current rate of circuit timeouts
4475 over our stored history.
4476 - The 'EXTENDCIRCUIT' control port command can now be used with
4477 a circ id of 0 and no path. This feature will cause Tor to build
4478 a new 'fast' general purpose circuit using its own path selection
4480 - Added a BUILDTIMEOUT_SET controller event to describe changes
4481 to the circuit build timeout.
4482 - New controller command "getinfo config-text". It returns the
4483 contents that Tor would write if you send it a SAVECONF command,
4484 so the controller can write the file to disk itself.
4486 o Minor features (controller protocol):
4487 - Add a new ControlSocketsGroupWritable configuration option: when
4488 it is turned on, ControlSockets are group-writeable by the default
4489 group of the current user. Patch by Jérémy Bobbio; implements
4491 - Tor now refuses to create a ControlSocket in a directory that is
4492 world-readable (or group-readable if ControlSocketsGroupWritable
4493 is 0). This is necessary because some operating systems do not
4494 enforce permissions on an AF_UNIX sockets. Permissions on the
4495 directory holding the socket, however, seems to work everywhere.
4496 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4497 not. This would lead to a cookie that is still not group readable.
4498 Closes bug 1843. Suggested by katmagic.
4499 - Future-proof the controller protocol a bit by ignoring keyword
4500 arguments we do not recognize.
4502 o Minor features (more useful logging):
4503 - Revise most log messages that refer to nodes by nickname to
4504 instead use the "$key=nickname at address" format. This should be
4505 more useful, especially since nicknames are less and less likely
4506 to be unique. Resolves ticket 3045.
4507 - When an HTTPS proxy reports "403 Forbidden", we now explain
4508 what it means rather than calling it an unexpected status code.
4509 Closes bug 2503. Patch from Michael Yakubovich.
4510 - Rate-limit a warning about failures to download v2 networkstatus
4511 documents. Resolves part of bug 1352.
4512 - Rate-limit the "your application is giving Tor only an IP address"
4513 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4514 - Rate-limit "Failed to hand off onionskin" warnings.
4515 - When logging a rate-limited warning, we now mention how many messages
4516 got suppressed since the last warning.
4517 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4518 2 no signature, 4 required" messages about consensus signatures
4519 easier to read, and make sure they get logged at the same severity
4520 as the messages explaining which keys are which. Fixes bug 1290.
4521 - Don't warn when we have a consensus that we can't verify because
4522 of missing certificates, unless those certificates are ones
4523 that we have been trying and failing to download. Fixes bug 1145.
4525 o Minor features (log domains):
4526 - Add documentation for configuring logging at different severities in
4527 different log domains. We've had this feature since 0.2.1.1-alpha,
4528 but for some reason it never made it into the manpage. Fixes
4530 - Make it simpler to specify "All log domains except for A and B".
4531 Previously you needed to say "[*,~A,~B]". Now you can just say
4533 - Add a "LogMessageDomains 1" option to include the domains of log
4534 messages along with the messages. Without this, there's no way
4535 to use log domains without reading the source or doing a lot
4537 - Add a new "Handshake" log domain for activities that happen
4538 during the TLS handshake.
4540 o Minor features (build process):
4541 - Make compilation with clang possible when using
4542 "--enable-gcc-warnings" by removing two warning options that clang
4543 hasn't implemented yet and by fixing a few warnings. Resolves
4545 - Detect platforms that brokenly use a signed size_t, and refuse to
4546 build there. Found and analyzed by doorss and rransom.
4547 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
4549 - Add support for statically linking zlib by specifying
4550 "--enable-static-zlib", to go with our support for statically
4551 linking openssl and libevent. Resolves bug 1358.
4552 - Instead of adding the svn revision to the Tor version string, report
4553 the git commit (when we're building from a git checkout).
4554 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4556 - New --digests command-line switch to output the digests of the
4557 source files Tor was built with.
4558 - Generate our manpage and HTML documentation using Asciidoc. This
4559 change should make it easier to maintain the documentation, and
4560 produce nicer HTML. The build process fails if asciidoc cannot
4561 be found and building with asciidoc isn't disabled (via the
4562 "--disable-asciidoc" argument to ./configure. Skipping the manpage
4563 speeds up the build considerably.
4565 o Minor features (options / torrc):
4566 - Warn when the same option is provided more than once in a torrc
4567 file, on the command line, or in a single SETCONF statement, and
4568 the option is one that only accepts a single line. Closes bug 1384.
4569 - Warn when the user configures two HiddenServiceDir lines that point
4570 to the same directory. Bugfix on 0.0.6 (the version introducing
4571 HiddenServiceDir); fixes bug 3289.
4572 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4573 do individual connection-level rate limiting of clients. The torrc
4574 config options with the same names trump the consensus params, if
4575 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4576 consensus params which were broken from 0.2.2.7-alpha through
4577 0.2.2.14-alpha. Closes bug 1947.
4578 - New config option "WarnUnsafeSocks 0" disables the warning that
4579 occurs whenever Tor receives a socks handshake using a version of
4580 the socks protocol that can only provide an IP address (rather
4581 than a hostname). Setups that do DNS locally over Tor are fine,
4582 and we shouldn't spam the logs in that case.
4583 - New config option "CircuitStreamTimeout" to override our internal
4584 timeout schedule for how many seconds until we detach a stream from
4585 a circuit and try a new circuit. If your network is particularly
4586 slow, you might want to set this to a number like 60.
4587 - New options for SafeLogging to allow scrubbing only log messages
4588 generated while acting as a relay. Specify "SafeLogging relay" if
4589 you want to ensure that only messages known to originate from
4590 client use of the Tor process will be logged unsafely.
4591 - Time and memory units in the configuration file can now be set to
4592 fractional units. For example, "2.5 GB" is now a valid value for
4594 - Support line continuations in the torrc config file. If a line
4595 ends with a single backslash character, the newline is ignored, and
4596 the configuration value is treated as continuing on the next line.
4599 o Minor features (unit tests):
4600 - Revise our unit tests to use the "tinytest" framework, so we
4601 can run tests in their own processes, have smarter setup/teardown
4602 code, and so on. The unit test code has moved to its own
4603 subdirectory, and has been split into multiple modules.
4604 - Add a unit test for cross-platform directory-listing code.
4605 - Add some forgotten return value checks during unit tests. Found
4607 - Use GetTempDir to find the proper temporary directory location on
4608 Windows when generating temporary files for the unit tests. Patch
4611 o Minor features (misc):
4612 - The "torify" script now uses torsocks where available.
4613 - Make Libevent log messages get delivered to controllers later,
4614 and not from inside the Libevent log handler. This prevents unsafe
4615 reentrant Libevent calls while still letting the log messages
4617 - Certain Tor clients (such as those behind check.torproject.org) may
4618 want to fetch the consensus in an extra early manner. To enable this
4619 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
4620 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
4621 as only certain clients who must have this information sooner should
4623 - Expand homedirs passed to tor-checkkey. This should silence a
4624 coverity complaint about passing a user-supplied string into
4625 open() without checking it.
4626 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4627 used on bridges, and it makes bridge scanning somewhat easier.
4628 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4629 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4631 o Minor bugfixes (relays):
4632 - When a relay decides that its DNS is too broken for it to serve
4633 as an exit server, it advertised itself as a non-exit, but
4634 continued to act as an exit. This could create accidental
4635 partitioning opportunities for users. Instead, if a relay is
4636 going to advertise reject *:* as its exit policy, it should
4637 really act with exit policy "reject *:*". Fixes bug 2366.
4638 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4639 - Publish a router descriptor even if generating an extra-info
4640 descriptor fails. Previously we would not publish a router
4641 descriptor without an extra-info descriptor; this can cause fast
4642 exit relays collecting exit-port statistics to drop from the
4643 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4644 - When we're trying to guess whether we know our IP address as
4645 a relay, we would log various ways that we failed to guess
4646 our address, but never log that we ended up guessing it
4647 successfully. Now add a log line to help confused and anxious
4648 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4649 - For bandwidth accounting, calculate our expected bandwidth rate
4650 based on the time during which we were active and not in
4651 soft-hibernation during the last interval. Previously, we were
4652 also considering the time spent in soft-hibernation. If this
4653 was a long time, we would wind up underestimating our bandwidth
4654 by a lot, and skewing our wakeup time towards the start of the
4655 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4656 - Demote a confusing TLS warning that relay operators might get when
4657 someone tries to talk to their ORPort. It is not the operator's
4658 fault, nor can they do anything about it. Fixes bug 1364; bugfix
4660 - Change "Application request when we're believed to be offline."
4661 notice to "Application request when we haven't used client
4662 functionality lately.", to clarify that it's not an error. Bugfix
4663 on 0.0.9.3; fixes bug 1222.
4665 o Minor bugfixes (bridges):
4666 - When a client starts or stops using bridges, never use a circuit
4667 that was built before the configuration change. This behavior could
4668 put at risk a user who uses bridges to ensure that her traffic
4669 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4671 - Do not reset the bridge descriptor download status every time we
4672 re-parse our configuration or get a configuration change. Fixes
4673 bug 3019; bugfix on 0.2.0.3-alpha.
4674 - Users couldn't configure a regular relay to be their bridge. It
4675 didn't work because when Tor fetched the bridge descriptor, it found
4676 that it already had it, and didn't realize that the purpose of the
4677 descriptor had changed. Now we replace routers with a purpose other
4678 than bridge with bridge descriptors when fetching them. Bugfix on
4679 0.1.1.9-alpha. Fixes bug 1776.
4680 - In the special case where you configure a public exit relay as your
4681 bridge, Tor would be willing to use that exit relay as the last
4682 hop in your circuit as well. Now we fail that circuit instead.
4683 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4685 o Minor bugfixes (clients):
4686 - We now ask the other side of a stream (the client or the exit)
4687 for more data on that stream when the amount of queued data on
4688 that stream dips low enough. Previously, we wouldn't ask the
4689 other side for more data until either it sent us more data (which
4690 it wasn't supposed to do if it had exhausted its window!) or we
4691 had completely flushed all our queued data. This flow control fix
4692 should improve throughput. Fixes bug 2756; bugfix on the earliest
4693 released versions of Tor (svn commit r152).
4694 - When a client finds that an origin circuit has run out of 16-bit
4695 stream IDs, we now mark it as unusable for new streams. Previously,
4696 we would try to close the entire circuit. Bugfix on 0.0.6.
4697 - Make it explicit that we don't cannibalize one-hop circuits. This
4698 happens in the wild, but doesn't turn out to be a problem because
4699 we fortunately don't use those circuits. Many thanks to outofwords
4700 for the initial analysis and to swissknife who confirmed that
4701 two-hop circuits are actually created.
4702 - Resolve an edge case in path weighting that could make us misweight
4703 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4704 - Make the DNSPort option work with libevent 2.x. Don't alter the
4705 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4707 o Minor bugfixes (directory authorities):
4708 - Make directory authorities more accurate at recording when
4709 relays that have failed several reachability tests became
4710 unreachable, so we can provide more accuracy at assigning Stable,
4711 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4712 - Directory authorities are now more robust to hops back in time
4713 when calculating router stability. Previously, if a run of uptime
4714 or downtime appeared to be negative, the calculation could give
4715 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4717 - Directory authorities will now attempt to download consensuses
4718 if their own efforts to make a live consensus have failed. This
4719 change means authorities that restart will fetch a valid
4720 consensus, and it means authorities that didn't agree with the
4721 current consensus will still fetch and serve it if it has enough
4722 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
4723 - Never vote for a server as "Running" if we have a descriptor for
4724 it claiming to be hibernating, and that descriptor was published
4725 more recently than our last contact with the server. Bugfix on
4726 0.2.0.3-alpha; fixes bug 911.
4727 - Directory authorities no longer change their opinion of, or vote on,
4728 whether a router is Running, unless they have themselves been
4729 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4732 o Minor bugfixes (hidden services):
4733 - Log malformed requests for rendezvous descriptors as protocol
4734 warnings, not warnings. Also, use a more informative log message
4735 in case someone sees it at log level warning without prior
4736 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
4737 - Accept hidden service descriptors if we think we might be a hidden
4738 service directory, regardless of what our consensus says. This
4739 helps robustness, since clients and hidden services can sometimes
4740 have a more up-to-date view of the network consensus than we do,
4741 and if they think that the directory authorities list us a HSDir,
4742 we might actually be one. Related to bug 2732; bugfix on
4744 - Correct the warning displayed when a rendezvous descriptor exceeds
4745 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4747 - Clients and hidden services now use HSDir-flagged relays for hidden
4748 service descriptor downloads and uploads even if the relays have no
4749 DirPort set and the client has disabled TunnelDirConns. This will
4750 eventually allow us to give the HSDir flag to relays with no
4751 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4752 - Only limit the lengths of single HS descriptors, even when multiple
4753 HS descriptors are published to an HSDir relay in a single POST
4754 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4756 o Minor bugfixes (controllers):
4757 - Allow GETINFO fingerprint to return a fingerprint even when
4758 we have not yet built a router descriptor. Fixes bug 3577;
4759 bugfix on 0.2.0.1-alpha.
4760 - Send a SUCCEEDED stream event to the controller when a reverse
4761 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4762 discovered by katmagic.
4763 - Remove a trailing asterisk from "exit-policy/default" in the
4764 output of the control port command "GETINFO info/names". Bugfix
4766 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
4767 2917. Bugfix on 0.1.1.1-alpha.
4768 - When we restart our relay, we might get a successful connection
4769 from the outside before we've started our reachability tests,
4770 triggering a warning: "ORPort found reachable, but I have no
4771 routerinfo yet. Failing to inform controller of success." This
4772 bug was harmless unless Tor is running under a controller
4773 like Vidalia, in which case the controller would never get a
4774 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4776 - When a controller changes TrackHostExits, remove mappings for
4777 hosts that should no longer have their exits tracked. Bugfix on
4779 - When a controller changes VirtualAddrNetwork, remove any mappings
4780 for hosts that were automapped to the old network. Bugfix on
4782 - When a controller changes one of the AutomapHosts* options, remove
4783 any mappings for hosts that should no longer be automapped. Bugfix
4785 - Fix an off-by-one error in calculating some controller command
4786 argument lengths. Fortunately, this mistake is harmless since
4787 the controller code does redundant NUL termination too. Found by
4788 boboper. Bugfix on 0.1.1.1-alpha.
4789 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4790 would return "551 Internal error" rather than "552 Unrecognized key
4791 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4792 - Don't spam the controller with events when we have no file
4793 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4794 for log messages was already solved from bug 748.)
4795 - Emit a GUARD DROPPED controller event for a case we missed.
4796 - Ensure DNS requests launched by "RESOLVE" commands from the
4797 controller respect the __LeaveStreamsUnattached setconf options. The
4798 same goes for requests launched via DNSPort or transparent
4799 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4801 o Minor bugfixes (config options):
4802 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4803 Change the limit to 512 characters by removing base64 newlines.
4804 Fixes bug 2752. Fix by Michael Yakubovich.
4805 - Complain if PublishServerDescriptor is given multiple arguments that
4806 include 0 or 1. This configuration will be rejected in the future.
4807 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4808 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4809 Bugfix on 0.2.0.13-alpha; closes bug 928.
4811 o Minor bugfixes (log subsystem fixes):
4812 - When unable to format an address as a string, report its value
4813 as "???" rather than reusing the last formatted address. Bugfix
4815 - Be more consistent in our treatment of file system paths. "~" should
4816 get expanded to the user's home directory in the Log config option.
4817 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4818 feature for the -f and --DataDirectory options.
4820 o Minor bugfixes (memory management):
4821 - Don't stack-allocate the list of supplementary GIDs when we're
4822 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4823 could take up to 256K, which is way too much stack. Found by
4824 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4825 - Save a couple bytes in memory allocation every time we escape
4826 certain characters in a string. Patch from Florian Zumbiehl.
4828 o Minor bugfixes (protocol correctness):
4829 - When checking for 1024-bit keys, check for 1024 bits, not 128
4830 bytes. This allows Tor to correctly discard keys of length 1017
4831 through 1023. Bugfix on 0.0.9pre5.
4832 - Require that introduction point keys and onion handshake keys
4833 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4835 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4836 than waiting forever for them to finish. Fixes bug 2330; bugfix
4837 on 0.2.0.16-alpha. Found by doorss.
4838 - Never relay a cell for a circuit we have already destroyed.
4839 Between marking a circuit as closeable and finally closing it,
4840 it may have been possible for a few queued cells to get relayed,
4841 even though they would have been immediately dropped by the next
4842 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4843 - Never queue a cell for a circuit that's already been marked
4845 - Fix a spec conformance issue: the network-status-version token
4846 must be the first token in a v3 consensus or vote. Discovered by
4847 "parakeep". Bugfix on 0.2.0.3-alpha.
4848 - A networkstatus vote must contain exactly one signature. Spec
4849 conformance issue. Bugfix on 0.2.0.3-alpha.
4850 - When asked about a DNS record type we don't support via a
4851 client DNSPort, reply with NOTIMPL rather than an empty
4852 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4853 - Make more fields in the controller protocol case-insensitive, since
4854 control-spec.txt said they were.
4856 o Minor bugfixes (log messages):
4857 - Fix a log message that said "bits" while displaying a value in
4858 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4860 - Downgrade "no current certificates known for authority" message from
4861 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
4862 - Correctly describe errors that occur when generating a TLS object.
4863 Previously we would attribute them to a failure while generating a
4864 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4866 - Fix an instance where a Tor directory mirror might accidentally
4867 log the IP address of a misbehaving Tor client. Bugfix on
4869 - Stop logging at severity 'warn' when some other Tor client tries
4870 to establish a circuit with us using weak DH keys. It's a protocol
4871 violation, but that doesn't mean ordinary users need to hear about
4872 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4873 - If your relay can't keep up with the number of incoming create
4874 cells, it would log one warning per failure into your logs. Limit
4875 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4877 o Minor bugfixes (build fixes):
4878 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4879 - When warning about missing zlib development packages during compile,
4880 give the correct package names. Bugfix on 0.2.0.1-alpha.
4881 - Fix warnings that newer versions of autoconf produce during
4882 ./autogen.sh. These warnings appear to be harmless in our case,
4883 but they were extremely verbose. Fixes bug 2020.
4884 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4887 o Minor bugfixes (portability):
4888 - Write several files in text mode, on OSes that distinguish text
4889 mode from binary mode (namely, Windows). These files are:
4890 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4891 that collect those statistics; 'client_keys' and 'hostname' for
4892 hidden services that use authentication; and (in the tor-gencert
4893 utility) newly generated identity and signing keys. Previously,
4894 we wouldn't specify text mode or binary mode, leading to an
4895 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4896 the DirRecordUsageByCountry option which would have triggered
4897 the assertion failure was added), although this assertion failure
4898 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4899 - Selectively disable deprecation warnings on OS X because Lion
4900 started deprecating the shipped copy of openssl. Fixes bug 3643.
4901 - Use a wide type to hold sockets when built for 64-bit Windows.
4903 - Fix an issue that prevented static linking of libevent on
4904 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
4905 where we introduced the "--with-static-libevent" configure option.
4906 - Fix a bug with our locking implementation on Windows that couldn't
4907 correctly detect when a file was already locked. Fixes bug 2504,
4908 bugfix on 0.2.1.6-alpha.
4909 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4911 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4912 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
4915 o Minor bugfixes (code correctness):
4916 - Always NUL-terminate the sun_path field of a sockaddr_un before
4917 passing it to the kernel. (Not a security issue: kernels are
4918 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4919 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4920 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4921 expect it to emit a CRLF iff the format string ends with CRLF;
4922 it actually emitted a CRLF iff (a) the format string ended with
4923 CRLF or (b) the resulting string was over 1023 characters long or
4924 (c) the format string did not end with CRLF *and* the resulting
4925 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4926 fixes part of bug 3407.
4927 - Make send_control_event_impl()'s behaviour sane. Its callers
4928 expect it to always emit a CRLF at the end of the string; it
4929 might have emitted extra control characters as well. Bugfix on
4930 0.1.1.9-alpha; fixes another part of bug 3407.
4931 - Make crypto_rand_int() check the value of its input correctly.
4932 Previously, it accepted values up to UINT_MAX, but could return a
4933 negative number if given a value above INT_MAX+1. Found by George
4934 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4935 - Fix a potential null-pointer dereference while computing a
4936 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4938 - If we fail to compute the identity digest of a v3 legacy keypair,
4939 warn, and don't use a buffer-full of junk instead. Bugfix on
4940 0.2.1.1-alpha; fixes bug 3106.
4941 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4942 where if the function had ever in the future been used to check
4943 for the presence of a too-large number, it would have given an
4944 incorrect result. (Fortunately, we only used it for 16-bit
4945 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4946 - Be more careful about reporting the correct error from a failed
4947 connect() system call. Under some circumstances, it was possible to
4948 look at an incorrect value for errno when sending the end reason.
4949 Bugfix on 0.1.0.1-rc.
4950 - Correctly handle an "impossible" overflow cases in connection byte
4951 counting, where we write or read more than 4GB on an edge connection
4952 in a single second. Bugfix on 0.1.2.8-beta.
4953 - Avoid a double mark-for-free warning when failing to attach a
4954 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4956 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4957 found by "cypherpunks". This bug was introduced before the first
4958 Tor release, in svn commit r110.
4959 - Fix a bug in bandwidth history state parsing that could have been
4960 triggered if a future version of Tor ever changed the timing
4961 granularity at which bandwidth history is measured. Bugfix on
4963 - Add assertions to check for overflow in arguments to
4964 base32_encode() and base32_decode(); fix a signed-unsigned
4965 comparison there too. These bugs are not actually reachable in Tor,
4966 but it's good to prevent future errors too. Found by doorss.
4967 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4969 - Set target port in get_interface_address6() correctly. Bugfix
4970 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
4971 - Fix an impossible-to-actually-trigger buffer overflow in relay
4972 descriptor generation. Bugfix on 0.1.0.15.
4973 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4975 o Minor bugfixes (code improvements):
4976 - After we free an internal connection structure, overwrite it
4977 with a different memory value than we use for overwriting a freed
4978 internal circuit structure. Should help with debugging. Suggested
4980 - If OpenSSL fails to make a duplicate of a private or public key, log
4981 an error message and try to exit cleanly. May help with debugging
4982 if bug 1209 ever remanifests.
4983 - Some options used different conventions for uppercasing of acronyms
4984 when comparing manpage and source. Fix those in favor of the
4985 manpage, as it makes sense to capitalize acronyms.
4986 - Take a first step towards making or.h smaller by splitting out
4987 function definitions for all source files in src/or/. Leave
4988 structures and defines in or.h for now.
4989 - Remove a few dead assignments during router parsing. Found by
4991 - Don't use 1-bit wide signed bit fields. Found by coverity.
4992 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4993 None of the cases where we did this before were wrong, but by making
4994 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4995 - The memarea code now uses a sentinel value at the end of each area
4996 to make sure nothing writes beyond the end of an area. This might
4997 help debug some conceivable causes of bug 930.
4998 - Always treat failure to allocate an RSA key as an unrecoverable
5000 - Add some more defensive programming for architectures that can't
5001 handle unaligned integer accesses. We don't know of any actual bugs
5002 right now, but that's the best time to fix them. Fixes bug 1943.
5004 o Minor bugfixes (misc):
5005 - Fix a rare bug in rend_fn unit tests: we would fail a test when
5006 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5007 on 0.2.0.10-alpha; fixes bug 1808.
5008 - Where available, use Libevent 2.0's periodic timers so that our
5009 once-per-second cleanup code gets called even more closely to
5010 once per second than it would otherwise. Fixes bug 943.
5011 - Ignore OutboundBindAddress when connecting to localhost.
5012 Connections to localhost need to come _from_ localhost, or else
5013 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5015 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5017 - If any of the v3 certs we download are unparseable, we should
5018 actually notice the failure so we don't retry indefinitely. Bugfix
5019 on 0.2.0.x; reported by "rotator".
5020 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5021 Might help diagnosing bug 1051.
5022 - Make our 'torify' script more portable; if we have only one of
5023 'torsocks' or 'tsocks' installed, don't complain to the user;
5024 and explain our warning about tsocks better.
5025 - Fix some urls in the exit notice file and make it XHTML1.1 strict
5026 compliant. Based on a patch from Christian Kujau.
5028 o Documentation changes:
5029 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5030 - Resolve all doxygen warnings except those for missing documentation.
5032 - Add doxygen documentation for more functions, fields, and types.
5033 - Convert the HACKING file to asciidoc, and add a few new sections
5034 to it, explaining how we use Git, how we make changelogs, and
5035 what should go in a patch.
5036 - Document the default socks host and port (127.0.0.1:9050) for
5038 - Removed some unnecessary files from the source distribution. The
5039 AUTHORS file has now been merged into the people page on the
5040 website. The roadmaps and design doc can now be found in the
5041 projects directory in svn.
5043 o Deprecated and removed features (config):
5044 - Remove the torrc.complete file. It hasn't been kept up to date
5045 and users will have better luck checking out the manpage.
5046 - Remove the HSAuthorityRecordStats option that version 0 hidden
5047 service authorities could use to track statistics of overall v0
5048 hidden service usage.
5049 - Remove the obsolete "NoPublish" option; it has been flagged
5050 as obsolete and has produced a warning since 0.1.1.18-rc.
5051 - Caches no longer download and serve v2 networkstatus documents
5052 unless FetchV2Networkstatus flag is set: these documents haven't
5053 haven't been used by clients or relays since 0.2.0.x. Resolves
5056 o Deprecated and removed features (controller):
5057 - The controller no longer accepts the old obsolete "addr-mappings/"
5058 or "unregistered-servers-" GETINFO values.
5059 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5060 always on; using them is necessary for correct forward-compatible
5063 o Deprecated and removed features (misc):
5064 - Hidden services no longer publish version 0 descriptors, and clients
5065 do not request or use version 0 descriptors. However, the old hidden
5066 service authorities still accept and serve version 0 descriptors
5067 when contacted by older hidden services/clients.
5068 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5069 anything since 0.2.1.16-rc.
5070 - Remove everything related to building the expert bundle for OS X.
5071 It has confused many users, doesn't work right on OS X 10.6,
5072 and is hard to get rid of once installed. Resolves bug 1274.
5073 - Remove support for .noconnect style addresses. Nobody was using
5074 them, and they provided another avenue for detecting Tor users
5075 via application-level web tricks.
5076 - When we fixed bug 1038 we had to put in a restriction not to send
5077 RELAY_EARLY cells on rend circuits. This was necessary as long
5078 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5079 active. Now remove this obsolete check. Resolves bug 2081.
5080 - Remove workaround code to handle directory responses from servers
5081 that had bug 539 (they would send HTTP status 503 responses _and_
5082 send a body too). Since only server versions before
5083 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5084 keep the workaround in place.
5085 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5086 handling calculations where we have a known amount of clock skew and
5087 an allowed amount of unknown skew. But we only used it in three
5088 places, and we never adjusted the known/unknown skew values. This is
5089 still something we might want to do someday, but if we do, we'll
5090 want to do it differently.
5091 - Remove the "--enable-iphone" option to ./configure. According to
5092 reports from Marco Bonetti, Tor builds fine without any special
5093 tweaking on recent iPhone SDK versions.
5096 Changes in version 0.2.1.30 - 2011-02-23
5097 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5098 change is a slight tweak to Tor's TLS handshake that makes relays
5099 and bridges that run this new version reachable from Iran again.
5100 We don't expect this tweak will win the arms race long-term, but it
5101 buys us time until we roll out a better solution.
5104 - Stop sending a CLOCK_SKEW controller status event whenever
5105 we fetch directory information from a relay that has a wrong clock.
5106 Instead, only inform the controller when it's a trusted authority
5107 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5108 the rest of bug 1074.
5109 - Fix a bounds-checking error that could allow an attacker to
5110 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5112 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5113 Tor would ignore their RelayBandwidthBurst setting,
5114 potentially using more bandwidth than expected. Bugfix on
5115 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5116 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5117 hidserv" in her torrc. The 'hidserv' argument never controlled
5118 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5121 - Adjust our TLS Diffie-Hellman parameters to match those used by
5123 - Update to the February 1 2011 Maxmind GeoLite Country database.
5126 - Check for and reject overly long directory certificates and
5127 directory tokens before they have a chance to hit any assertions.
5128 Bugfix on 0.2.1.28. Found by "doorss".
5129 - Bring the logic that gathers routerinfos and assesses the
5130 acceptability of circuits into line. This prevents a Tor OP from
5131 getting locked in a cycle of choosing its local OR as an exit for a
5132 path (due to a .exit request) and then rejecting the circuit because
5133 its OR is not listed yet. It also prevents Tor clients from using an
5134 OR running in the same instance as an exit (due to a .exit request)
5135 if the OR does not meet the same requirements expected of an OR
5136 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5138 o Packaging changes:
5139 - Stop shipping the Tor specs files and development proposal documents
5140 in the tarball. They are now in a separate git repository at
5141 git://git.torproject.org/torspec.git
5142 - Do not include Git version tags as though they are SVN tags when
5143 generating a tarball from inside a repository that has switched
5144 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5147 Changes in version 0.2.1.29 - 2011-01-15
5148 Tor 0.2.1.29 continues our recent code security audit work. The main
5149 fix resolves a remote heap overflow vulnerability that can allow remote
5150 code execution. Other fixes address a variety of assert and crash bugs,
5151 most of which we think are hard to exploit remotely.
5153 o Major bugfixes (security):
5154 - Fix a heap overflow bug where an adversary could cause heap
5155 corruption. This bug probably allows remote code execution
5156 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5158 - Prevent a denial-of-service attack by disallowing any
5159 zlib-compressed data whose compression factor is implausibly
5160 high. Fixes part of bug 2324; reported by "doorss".
5161 - Zero out a few more keys in memory before freeing them. Fixes
5162 bug 2384 and part of bug 2385. These key instances found by
5163 "cypherpunks", based on Andrew Case's report about being able
5164 to find sensitive data in Tor's memory space if you have enough
5165 permissions. Bugfix on 0.0.2pre9.
5167 o Major bugfixes (crashes):
5168 - Prevent calls to Libevent from inside Libevent log handlers.
5169 This had potential to cause a nasty set of crashes, especially
5170 if running Libevent with debug logging enabled, and running
5171 Tor with a controller watching for low-severity log messages.
5172 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5173 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5174 underflow errors there too. Fixes the other part of bug 2324.
5175 - Fix a bug where we would assert if we ever had a
5176 cached-descriptors.new file (or another file read directly into
5177 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5178 on 0.2.1.25. Found by doorss.
5179 - Fix some potential asserts and parsing issues with grossly
5180 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5183 o Minor bugfixes (other):
5184 - Fix a bug with handling misformed replies to reverse DNS lookup
5185 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5186 bug reported by doorss.
5187 - Fix compilation on mingw when a pthreads compatibility library
5188 has been installed. (We don't want to use it, so we shouldn't
5189 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5190 - Fix a bug where we would declare that we had run out of virtual
5191 addresses when the address space was only half-exhausted. Bugfix
5193 - Correctly handle the case where AutomapHostsOnResolve is set but
5194 no virtual addresses are available. Fixes bug 2328; bugfix on
5195 0.1.2.1-alpha. Bug found by doorss.
5196 - Correctly handle wrapping around when we run out of virtual
5197 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5200 - Update to the January 1 2011 Maxmind GeoLite Country database.
5201 - Introduce output size checks on all of our decryption functions.
5204 - Tor does not build packages correctly with Automake 1.6 and earlier;
5205 added a check to Makefile.am to make sure that we're building with
5206 Automake 1.7 or later.
5207 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5208 because we built it with a too-old version of automake. Thus that
5209 release broke ./configure --enable-openbsd-malloc, which is popular
5210 among really fast exit relays on Linux.
5213 Changes in version 0.2.1.28 - 2010-12-17
5214 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5215 exploitable bugs. We also took this opportunity to change the IP address
5216 for one of our directory authorities, and to update the geoip database
5220 - Fix a remotely exploitable bug that could be used to crash instances
5221 of Tor remotely by overflowing on the heap. Remote-code execution
5222 hasn't been confirmed, but can't be ruled out. Everyone should
5223 upgrade. Bugfix on the 0.1.1 series and later.
5225 o Directory authority changes:
5226 - Change IP address and ports for gabelmoo (v3 directory authority).
5229 - Update to the December 1 2010 Maxmind GeoLite Country database.
5232 Changes in version 0.2.1.27 - 2010-11-23
5233 Yet another OpenSSL security patch broke its compatibility with Tor:
5234 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5235 also took this opportunity to fix several crash bugs, integrate a new
5236 directory authority, and update the bundled GeoIP database.
5239 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5240 No longer set the tlsext_host_name extension on server SSL objects;
5241 but continue to set it on client SSL objects. Our goal in setting
5242 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5243 bugfix on 0.2.1.1-alpha.
5244 - Do not log messages to the controller while shrinking buffer
5245 freelists. Doing so would sometimes make the controller connection
5246 try to allocate a buffer chunk, which would mess up the internals
5247 of the freelist and cause an assertion failure. Fixes bug 1125;
5248 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5249 - Learn our external IP address when we're a relay or bridge, even if
5250 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5251 where we introduced bridge relays that don't need to publish to
5252 be useful. Fixes bug 2050.
5253 - Do even more to reject (and not just ignore) annotations on
5254 router descriptors received anywhere but from the cache. Previously
5255 we would ignore such annotations at first, but cache them to disk
5256 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5257 - When you're using bridges and your network goes away and your
5258 bridges get marked as down, recover when you attempt a new socks
5259 connection (if the network is back), rather than waiting up to an
5260 hour to try fetching new descriptors for your bridges. Bugfix on
5261 0.2.0.3-alpha; fixes bug 1981.
5264 - Move to the November 2010 Maxmind GeoLite country db (rather
5265 than the June 2009 ip-to-country GeoIP db) for our statistics that
5266 count how many users relays are seeing from each country. Now we'll
5267 have more accurate data, especially for many African countries.
5269 o New directory authorities:
5270 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5274 - Fix an assertion failure that could occur in directory caches or
5275 bridge users when using a very short voting interval on a testing
5276 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5278 - Enforce multiplicity rules when parsing annotations. Bugfix on
5279 0.2.0.8-alpha. Found by piebeer.
5280 - Allow handshaking OR connections to take a full KeepalivePeriod
5281 seconds to handshake. Previously, we would close them after
5282 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5283 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5285 - When building with --enable-gcc-warnings on OpenBSD, disable
5286 warnings in system headers. This makes --enable-gcc-warnings
5287 pass on OpenBSD 4.8.
5290 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5291 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5292 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5293 Servers can start sending this code when enough clients recognize
5294 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5295 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5296 Patch from mingw-san.
5299 - Remove the old debian/ directory from the main Tor distribution.
5300 The official Tor-for-debian git repository lives at the URL
5301 https://git.torproject.org/debian/tor.git
5302 - Stop shipping the old doc/website/ directory in the tarball. We
5303 changed the website format in late 2010, and what we shipped in
5304 0.2.1.26 really wasn't that useful anyway.
5307 Changes in version 0.2.1.26 - 2010-05-02
5308 Tor 0.2.1.26 addresses the recent connection and memory overload
5309 problems we've been seeing on relays, especially relays with their
5310 DirPort open. If your relay has been crashing, or you turned it off
5311 because it used too many resources, give this release a try.
5313 This release also fixes yet another instance of broken OpenSSL libraries
5314 that was causing some relays to drop out of the consensus.
5317 - Teach relays to defend themselves from connection overload. Relays
5318 now close idle circuits early if it looks like they were intended
5319 for directory fetches. Relays are also more aggressive about closing
5320 TLS connections that have no circuits on them. Such circuits are
5321 unlikely to be re-used, and tens of thousands of them were piling
5322 up at the fast relays, causing the relays to run out of sockets
5323 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5324 their directory fetches over TLS).
5325 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5326 that claim to be earlier than 0.9.8m, but which have in reality
5327 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5328 behavior. Possible fix for some cases of bug 1346.
5329 - Directory mirrors were fetching relay descriptors only from v2
5330 directory authorities, rather than v3 authorities like they should.
5331 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5332 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5335 - Finally get rid of the deprecated and now harmful notion of "clique
5336 mode", where directory authorities maintain TLS connections to
5340 - In the util/threads test, no longer free the test_mutex before all
5341 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5342 - The master thread could starve the worker threads quite badly on
5343 certain systems, causing them to run only partially in the allowed
5344 window. This resulted in test failures. Now the master thread sleeps
5345 occasionally for a few microseconds while the two worker-threads
5346 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5349 Changes in version 0.2.1.25 - 2010-03-16
5350 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5351 prevent relays from guessing their IP address correctly. It also fixes
5352 several minor potential security bugs.
5355 - Fix a regression from our patch for bug 1244 that caused relays
5356 to guess their IP address incorrectly if they didn't set Address
5357 in their torrc and/or their address fails to resolve. Bugfix on
5358 0.2.1.23; fixes bug 1269.
5359 - When freeing a session key, zero it out completely. We only zeroed
5360 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5361 patched by ekir. Fixes bug 1254.
5364 - Fix a dereference-then-NULL-check sequence when publishing
5365 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5367 - Fix another dereference-then-NULL-check sequence. Bugfix on
5368 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5369 - Make sure we treat potentially not NUL-terminated strings correctly.
5370 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5373 Changes in version 0.2.1.24 - 2010-02-21
5374 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5378 - Work correctly out-of-the-box with even more vendor-patched versions
5379 of OpenSSL. In particular, make it so Debian and OS X don't need
5380 customized patches to run/build.
5383 Changes in version 0.2.1.23 - 2010-02-13
5384 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5385 again on the latest OS X, and updates the location of a directory
5388 o Major bugfixes (performance):
5389 - We were selecting our guards uniformly at random, and then weighting
5390 which of our guards we'd use uniformly at random. This imbalance
5391 meant that Tor clients were severely limited on throughput (and
5392 probably latency too) by the first hop in their circuit. Now we
5393 select guards weighted by currently advertised bandwidth. We also
5394 automatically discard guards picked using the old algorithm. Fixes
5395 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5398 - Make Tor work again on the latest OS X: when deciding whether to
5399 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5400 version at run-time, not compile time. We need to do this because
5401 Apple doesn't update its dev-tools headers when it updates its
5402 libraries in a security patch.
5403 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5404 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5405 a memory leak when requesting a hidden service descriptor we've
5406 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5410 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5411 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5414 - Avoid a mad rush at the beginning of each month when each client
5415 rotates half of its guards. Instead we spread the rotation out
5416 throughout the month, but we still avoid leaving a precise timestamp
5417 in the state file about when we first picked the guard. Improves
5418 over the behavior introduced in 0.1.2.17.
5421 Changes in version 0.2.1.22 - 2010-01-19
5422 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5423 authorities -- it would tell you its whole history of bridge descriptors
5424 if you make the right directory request. This stable update also
5425 rotates two of the seven v3 directory authority keys and locations.
5427 o Directory authority changes:
5428 - Rotate keys (both v3 identity and relay identity) for moria1
5432 - Stop bridge directory authorities from answering dbg-stability.txt
5433 directory queries, which would let people fetch a list of all
5434 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5437 Changes in version 0.2.1.21 - 2009-12-21
5438 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5439 library. If you use Tor on Linux / Unix and you're getting SSL
5440 renegotiation errors, upgrading should help. We also recommend an
5441 upgrade if you're an exit relay.
5444 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5445 handshake from working unless we explicitly tell OpenSSL that we
5446 are using SSL renegotiation safely. We are, of course, but OpenSSL
5447 0.9.8l won't work unless we say we are.
5448 - Avoid crashing if the client is trying to upload many bytes and the
5449 circuit gets torn down at the same time, or if the flip side
5450 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5453 - Do not refuse to learn about authority certs and v2 networkstatus
5454 documents that are older than the latest consensus. This bug might
5455 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5456 Spotted and fixed by xmux.
5457 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5458 trigger platform-specific option misparsing case found by Coverity
5460 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5461 trigger assert. Fixes bug 1173.
5464 Changes in version 0.2.1.20 - 2009-10-15
5465 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5466 services at once, prepares for more performance improvements, and
5467 fixes a bunch of smaller bugs.
5469 The Windows and OS X bundles also include a more recent Vidalia,
5470 and switch from Privoxy to Polipo.
5472 The OS X installers are now drag and drop. It's best to un-install
5473 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5474 you want to upgrade, you'll need to update the paths for Tor and Polipo
5475 in the Vidalia Settings window.
5478 - Send circuit or stream sendme cells when our window has decreased
5479 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5480 by Karsten when testing the "reduce circuit window" performance
5481 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5482 before the release of Tor 0.0.0. This is the new winner of the
5484 - Fix a remotely triggerable memory leak when a consensus document
5485 contains more than one signature from the same voter. Bugfix on
5487 - Avoid segfault in rare cases when finishing an introduction circuit
5488 as a client and finding out that we don't have an introduction key
5489 for it. Fixes bug 1073. Reported by Aaron Swartz.
5492 - Tor now reads the "circwindow" parameter out of the consensus,
5493 and uses that value for its circuit package window rather than the
5494 default of 1000 cells. Begins the implementation of proposal 168.
5496 o New directory authorities:
5497 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5499 - Move moria1 and tonga to alternate IP addresses.
5502 - Fix a signed/unsigned compile warning in 0.2.1.19.
5503 - Fix possible segmentation fault on directory authorities. Bugfix on
5505 - Fix an extremely rare infinite recursion bug that could occur if
5506 we tried to log a message after shutting down the log subsystem.
5507 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5508 - Fix an obscure bug where hidden services on 64-bit big-endian
5509 systems might mis-read the timestamp in v3 introduce cells, and
5510 refuse to connect back to the client. Discovered by "rotor".
5511 Bugfix on 0.2.1.6-alpha.
5512 - We were triggering a CLOCK_SKEW controller status event whenever
5513 we connect via the v2 connection protocol to any relay that has
5514 a wrong clock. Instead, we should only inform the controller when
5515 it's a trusted authority that claims our clock is wrong. Bugfix
5516 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5517 - We were telling the controller about CHECKING_REACHABILITY and
5518 REACHABILITY_FAILED status events whenever we launch a testing
5519 circuit or notice that one has failed. Instead, only tell the
5520 controller when we want to inform the user of overall success or
5521 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5523 - Don't warn when we're using a circuit that ends with a node
5524 excluded in ExcludeExitNodes, but the circuit is not used to access
5525 the outside world. This should help fix bug 1090. Bugfix on
5527 - Work around a small memory leak in some versions of OpenSSL that
5528 stopped the memory used by the hostname TLS extension from being
5532 - Add a "getinfo status/accepted-server-descriptor" controller
5533 command, which is the recommended way for controllers to learn
5534 whether our server descriptor has been successfully received by at
5535 least on directory authority. Un-recommend good-server-descriptor
5536 getinfo and status events until we have a better design for them.
5539 Changes in version 0.2.1.19 - 2009-07-28
5540 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5544 - Make accessing hidden services on 0.2.1.x work right again.
5545 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5546 part of patch provided by "optimist".
5549 - When a relay/bridge is writing out its identity key fingerprint to
5550 the "fingerprint" file and to its logs, write it without spaces. Now
5551 it will look like the fingerprints in our bridges documentation,
5552 and confuse fewer users.
5555 - Relays no longer publish a new server descriptor if they change
5556 their MaxAdvertisedBandwidth config option but it doesn't end up
5557 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5558 fixes bug 1026. Patch from Sebastian.
5559 - Avoid leaking memory every time we get a create cell but we have
5560 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5561 fixes bug 1034. Reported by BarkerJr.
5564 Changes in version 0.2.1.18 - 2009-07-24
5565 Tor 0.2.1.18 lays the foundations for performance improvements,
5566 adds status events to help users diagnose bootstrap problems, adds
5567 optional authentication/authorization for hidden services, fixes a
5568 variety of potential anonymity problems, and includes a huge pile of
5569 other features and bug fixes.
5571 o Major features (clients):
5572 - Start sending "bootstrap phase" status events to the controller,
5573 so it can keep the user informed of progress fetching directory
5574 information and establishing circuits. Also inform the controller
5575 if we think we're stuck at a particular bootstrap phase. Implements
5577 - Clients replace entry guards that were chosen more than a few months
5578 ago. This change should significantly improve client performance,
5579 especially once more people upgrade, since relays that have been
5580 a guard for a long time are currently overloaded.
5581 - Network status consensus documents and votes now contain bandwidth
5582 information for each relay. Clients use the bandwidth values
5583 in the consensus, rather than the bandwidth values in each
5584 relay descriptor. This approach opens the door to more accurate
5585 bandwidth estimates once the directory authorities start doing
5586 active measurements. Implements part of proposal 141.
5588 o Major features (relays):
5589 - Disable and refactor some debugging checks that forced a linear scan
5590 over the whole server-side DNS cache. These accounted for over 50%
5591 of CPU time on a relatively busy exit node's gprof profile. Also,
5592 disable some debugging checks that appeared in exit node profile
5593 data. Found by Jacob.
5594 - New DirPortFrontPage option that takes an html file and publishes
5595 it as "/" on the DirPort. Now relay operators can provide a
5596 disclaimer without needing to set up a separate webserver. There's
5597 a sample disclaimer in contrib/tor-exit-notice.html.
5599 o Major features (hidden services):
5600 - Make it possible to build hidden services that only certain clients
5601 are allowed to connect to. This is enforced at several points,
5602 so that unauthorized clients are unable to send INTRODUCE cells
5603 to the service, or even (depending on the type of authentication)
5604 to learn introduction points. This feature raises the bar for
5605 certain kinds of active attacks against hidden services. Design
5606 and code by Karsten Loesing. Implements proposal 121.
5607 - Relays now store and serve v2 hidden service descriptors by default,
5608 i.e., the new default value for HidServDirectoryV2 is 1. This is
5609 the last step in proposal 114, which aims to make hidden service
5610 lookups more reliable.
5612 o Major features (path selection):
5613 - ExitNodes and Exclude*Nodes config options now allow you to restrict
5614 by country code ("{US}") or IP address or address pattern
5615 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
5616 refinement to decide what config options should take priority if
5617 you ask to both use a particular node and exclude it.
5619 o Major features (misc):
5620 - When building a consensus, do not include routers that are down.
5621 This cuts down 30% to 40% on consensus size. Implements proposal
5623 - New TestingTorNetwork config option to allow adjustment of
5624 previously constant values that could slow bootstrapping. Implements
5625 proposal 135. Patch from Karsten.
5626 - Convert many internal address representations to optionally hold
5627 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
5628 elements. Make resolver code handle nameservers located at IPv6
5630 - More work on making our TLS handshake blend in: modify the list
5631 of ciphers advertised by OpenSSL in client mode to even more
5632 closely resemble a common web browser. We cheat a little so that
5633 we can advertise ciphers that the locally installed OpenSSL doesn't
5635 - Use the TLS1 hostname extension to more closely resemble browser
5638 o Security fixes (anonymity/entropy):
5639 - Never use a connection with a mismatched address to extend a
5640 circuit, unless that connection is canonical. A canonical
5641 connection is one whose address is authenticated by the router's
5642 identity key, either in a NETINFO cell or in a router descriptor.
5643 - Implement most of proposal 110: The first K cells to be sent
5644 along a circuit are marked as special "early" cells; only K "early"
5645 cells will be allowed. Once this code is universal, we can block
5646 certain kinds of denial-of-service attack by requiring that EXTEND
5647 commands must be sent using an "early" cell.
5648 - Resume using OpenSSL's RAND_poll() for better (and more portable)
5649 cross-platform entropy collection again. We used to use it, then
5650 stopped using it because of a bug that could crash systems that
5651 called RAND_poll when they had a lot of fds open. It looks like the
5652 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
5653 at startup, and to call RAND_poll() when we reseed later only if
5654 we have a non-buggy OpenSSL version.
5655 - When the client is choosing entry guards, now it selects at most
5656 one guard from a given relay family. Otherwise we could end up with
5657 all of our entry points into the network run by the same operator.
5658 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5659 - Do not use or believe expired v3 authority certificates. Patch
5660 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
5661 - Drop begin cells to a hidden service if they come from the middle
5662 of a circuit. Patch from lark.
5663 - When we erroneously receive two EXTEND cells for the same circuit
5664 ID on the same connection, drop the second. Patch from lark.
5665 - Authorities now vote for the Stable flag for any router whose
5666 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5667 - Clients now never report any stream end reason except 'MISC'.
5668 Implements proposal 148.
5670 o Major bugfixes (crashes):
5671 - Parse dates and IPv4 addresses in a locale- and libc-independent
5672 manner, to avoid platform-dependent behavior on malformed input.
5673 - Fix a crash that occurs on exit nodes when a nameserver request
5674 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5675 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5677 - Do not assume that a stack-allocated character array will be
5678 64-bit aligned on platforms that demand that uint64_t access is
5679 aligned. Possible fix for bug 604.
5680 - Resolve a very rare crash bug that could occur when the user forced
5681 a nameserver reconfiguration during the middle of a nameserver
5682 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5683 - Avoid a "0 divided by 0" calculation when calculating router uptime
5684 at directory authorities. Bugfix on 0.2.0.8-alpha.
5685 - Fix an assertion bug in parsing policy-related options; possible fix
5687 - Rate-limit too-many-sockets messages: when they happen, they happen
5688 a lot and end up filling up the disk. Resolves bug 748.
5689 - Fix a race condition that could cause crashes or memory corruption
5690 when running as a server with a controller listening for log
5692 - Avoid crashing when we have a policy specified in a DirPolicy or
5693 SocksPolicy or ReachableAddresses option with ports set on it,
5694 and we re-load the policy. May fix bug 996.
5695 - Fix an assertion failure on 64-bit platforms when we allocated
5696 memory right up to the end of a memarea, then realigned the memory
5697 one step beyond the end. Fixes a possible cause of bug 930.
5698 - Protect the count of open sockets with a mutex, so we can't
5699 corrupt it when two threads are closing or opening sockets at once.
5700 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5702 o Major bugfixes (clients):
5703 - Discard router descriptors as we load them if they are more than
5704 five days old. Otherwise if Tor is off for a long time and then
5705 starts with cached descriptors, it will try to use the onion keys
5706 in those obsolete descriptors when building circuits. Fixes bug 887.
5707 - When we choose to abandon a new entry guard because we think our
5708 older ones might be better, close any circuits pending on that
5709 new entry guard connection. This fix should make us recover much
5710 faster when our network is down and then comes back. Bugfix on
5711 0.1.2.8-beta; found by lodger.
5712 - When Tor clients restart after 1-5 days, they discard all their
5713 cached descriptors as too old, but they still use the cached
5714 consensus document. This approach is good for robustness, but
5715 bad for performance: since they don't know any bandwidths, they
5716 end up choosing at random rather than weighting their choice by
5717 speed. Fixed by the above feature of putting bandwidths in the
5720 o Major bugfixes (relays):
5721 - Relays were falling out of the networkstatus consensus for
5722 part of a day if they changed their local config but the
5723 authorities discarded their new descriptor as "not sufficiently
5724 different". Now directory authorities accept a descriptor as changed
5725 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
5727 - Ensure that two circuits can never exist on the same connection
5728 with the same circuit ID, even if one is marked for close. This
5729 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
5730 - Directory authorities were neglecting to mark relays down in their
5731 internal histories if the relays fall off the routerlist without
5732 ever being found unreachable. So there were relays in the histories
5733 that haven't been seen for eight months, and are listed as being
5734 up for eight months. This wreaked havoc on the "median wfu" and
5735 "median mtbf" calculations, in turn making Guard and Stable flags
5736 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
5739 o Major bugfixes (hidden services):
5740 - When establishing a hidden service, introduction points that
5741 originate from cannibalized circuits were completely ignored
5742 and not included in rendezvous service descriptors. This might
5743 have been another reason for delay in making a hidden service
5744 available. Bugfix from long ago (0.0.9.x?)
5746 o Major bugfixes (memory and resource management):
5747 - Fixed some memory leaks -- some quite frequent, some almost
5748 impossible to trigger -- based on results from Coverity.
5749 - Speed up parsing and cut down on memory fragmentation by using
5750 stack-style allocations for parsing directory objects. Previously,
5751 this accounted for over 40% of allocations from within Tor's code
5752 on a typical directory cache.
5753 - Use a Bloom filter rather than a digest-based set to track which
5754 descriptors we need to keep around when we're cleaning out old
5755 router descriptors. This speeds up the computation significantly,
5756 and may reduce fragmentation.
5758 o New/changed config options:
5759 - Now NodeFamily and MyFamily config options allow spaces in
5760 identity fingerprints, so it's easier to paste them in.
5761 Suggested by Lucky Green.
5762 - Allow ports 465 and 587 in the default exit policy again. We had
5763 rejected them in 0.1.0.15, because back in 2005 they were commonly
5764 misconfigured and ended up as spam targets. We hear they are better
5765 locked down these days.
5766 - Make TrackHostExit mappings expire a while after their last use, not
5767 after their creation. Patch from Robert Hogan.
5768 - Add an ExcludeExitNodes option so users can list a set of nodes
5769 that should be be excluded from the exit node position, but
5770 allowed elsewhere. Implements proposal 151.
5771 - New --hush command-line option similar to --quiet. While --quiet
5772 disables all logging to the console on startup, --hush limits the
5773 output to messages of warning and error severity.
5774 - New configure/torrc options (--enable-geoip-stats,
5775 DirRecordUsageByCountry) to record how many IPs we've served
5776 directory info to in each country code, how many status documents
5777 total we've sent to each country code, and what share of the total
5778 directory requests we should expect to see.
5779 - Make outbound DNS packets respect the OutboundBindAddress setting.
5780 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5781 - Allow separate log levels to be configured for different logging
5782 domains. For example, this allows one to log all notices, warnings,
5783 or errors, plus all memory management messages of level debug or
5784 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
5785 - Update to the "June 3 2009" ip-to-country file.
5787 o Minor features (relays):
5788 - Raise the minimum rate limiting to be a relay from 20000 bytes
5789 to 20480 bytes (aka 20KB/s), to match our documentation. Also
5790 update directory authorities so they always assign the Fast flag
5791 to relays with 20KB/s of capacity. Now people running relays won't
5792 suddenly find themselves not seeing any use, if the network gets
5794 - If we're a relay and we change our IP address, be more verbose
5795 about the reason that made us change. Should help track down
5796 further bugs for relays on dynamic IP addresses.
5797 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5798 - Implement most of Proposal 152: allow specialized servers to permit
5799 single-hop circuits, and clients to use those servers to build
5800 single-hop circuits when using a specialized controller. Patch
5801 from Josh Albrecht. Resolves feature request 768.
5802 - When relays do their initial bandwidth measurement, don't limit
5803 to just our entry guards for the test circuits. Otherwise we tend
5804 to have multiple test circuits going through a single entry guard,
5805 which makes our bandwidth test less accurate. Fixes part of bug 654;
5806 patch contributed by Josh Albrecht.
5808 o Minor features (directory authorities):
5809 - Try not to open more than one descriptor-downloading connection
5810 to an authority at once. This should reduce load on directory
5811 authorities. Fixes bug 366.
5812 - Add cross-certification to newly generated certificates, so that
5813 a signing key is enough information to look up a certificate. Start
5814 serving certificates by <identity digest, signing key digest>
5815 pairs. Implements proposal 157.
5816 - When a directory authority downloads a descriptor that it then
5817 immediately rejects, do not retry downloading it right away. Should
5818 save some bandwidth on authorities. Fix for bug 888. Patch by
5820 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5821 help debug WFU and MTBF calculations.
5822 - In directory authorities' approved-routers files, allow
5823 fingerprints with or without space.
5825 o Minor features (directory mirrors):
5826 - When a download gets us zero good descriptors, do not notify
5827 Tor that new directory information has arrived.
5828 - Servers support a new URL scheme for consensus downloads that
5829 allows the client to specify which authorities are trusted.
5830 The server then only sends the consensus if the client will trust
5831 it. Otherwise a 404 error is sent back. Clients use this
5832 new scheme when the server supports it (meaning it's running
5833 0.2.1.1-alpha or later). Implements proposal 134.
5835 o Minor features (bridges):
5836 - If the bridge config line doesn't specify a port, assume 443.
5837 This makes bridge lines a bit smaller and easier for users to
5839 - If we're using bridges and our network goes away, be more willing
5840 to forgive our bridges and try again when we get an application
5843 o Minor features (hidden services):
5844 - When the client launches an introduction circuit, retry with a
5845 new circuit after 30 seconds rather than 60 seconds.
5846 - Launch a second client-side introduction circuit in parallel
5847 after a delay of 15 seconds (based on work by Christian Wilms).
5848 - Hidden services start out building five intro circuits rather
5849 than three, and when the first three finish they publish a service
5850 descriptor using those. Now we publish our service descriptor much
5851 faster after restart.
5852 - Drop the requirement to have an open dir port for storing and
5853 serving v2 hidden service descriptors.
5855 o Minor features (build and packaging):
5856 - On Linux, use the prctl call to re-enable core dumps when the User
5858 - Try to make sure that the version of Libevent we're running with
5859 is binary-compatible with the one we built with. May address bug
5861 - Add a new --enable-local-appdata configuration switch to change
5862 the default location of the datadir on win32 from APPDATA to
5863 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5864 entirely. Patch from coderman.
5865 - Build correctly against versions of OpenSSL 0.9.8 or later that
5866 are built without support for deprecated functions.
5867 - On platforms with a maximum syslog string length, truncate syslog
5868 messages to that length ourselves, rather than relying on the
5869 system to do it for us.
5870 - Automatically detect MacOSX versions earlier than 10.4.0, and
5871 disable kqueue from inside Tor when running with these versions.
5872 We previously did this from the startup script, but that was no
5873 help to people who didn't use the startup script. Resolves bug 863.
5874 - Build correctly when configured to build outside the main source
5875 path. Patch from Michael Gold.
5876 - Disable GCC's strict alias optimization by default, to avoid the
5877 likelihood of its introducing subtle bugs whenever our code violates
5878 the letter of C99's alias rules.
5879 - Change the contrib/tor.logrotate script so it makes the new
5880 logs as "_tor:_tor" rather than the default, which is generally
5881 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
5882 - Change our header file guard macros to be less likely to conflict
5883 with system headers. Adam Langley noticed that we were conflicting
5884 with log.h on Android.
5885 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
5886 and stop using a warning that had become unfixably verbose under
5888 - Use a lockfile to make sure that two Tor processes are not
5889 simultaneously running with the same datadir.
5890 - Allow OpenSSL to use dynamic locks if it wants.
5891 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5893 o Minor features (controllers):
5894 - When generating circuit events with verbose nicknames for
5895 controllers, try harder to look up nicknames for routers on a
5896 circuit. (Previously, we would look in the router descriptors we had
5897 for nicknames, but not in the consensus.) Partial fix for bug 941.
5898 - New controller event NEWCONSENSUS that lists the networkstatus
5899 lines for every recommended relay. Now controllers like Torflow
5900 can keep up-to-date on which relays they should be using.
5901 - New controller event "clients_seen" to report a geoip-based summary
5902 of which countries we've seen clients from recently. Now controllers
5903 like Vidalia can show bridge operators that they're actually making
5905 - Add a 'getinfo status/clients-seen' controller command, in case
5906 controllers want to hear clients_seen events but connect late.
5907 - New CONSENSUS_ARRIVED event to note when a new consensus has
5908 been fetched and validated.
5909 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5910 controllers to prevent SIGHUP from reloading the configuration.
5912 - Return circuit purposes in response to GETINFO circuit-status.
5914 - Serve the latest v3 networkstatus consensus via the control
5915 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
5916 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
5917 controller can query our current bootstrap state in case it attaches
5918 partway through and wants to catch up.
5919 - Provide circuit purposes along with circuit events to the controller.
5921 o Minor features (tools):
5922 - Do not have tor-resolve automatically refuse all .onion addresses;
5923 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5924 - Add a -p option to tor-resolve for specifying the SOCKS port: some
5925 people find host:port too confusing.
5926 - Print the SOCKS5 error message string as well as the error code
5927 when a tor-resolve request fails. Patch from Jacob.
5929 o Minor bugfixes (memory and resource management):
5930 - Clients no longer cache certificates for authorities they do not
5931 recognize. Bugfix on 0.2.0.9-alpha.
5932 - Do not use C's stdio library for writing to log files. This will
5933 improve logging performance by a minute amount, and will stop
5934 leaking fds when our disk is full. Fixes bug 861.
5935 - Stop erroneous use of O_APPEND in cases where we did not in fact
5936 want to re-seek to the end of a file before every last write().
5937 - Fix a small alignment and memory-wasting bug on buffer chunks.
5939 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
5940 to avoid unused RAM in buffer chunks and memory pools.
5941 - Reduce the default smartlist size from 32 to 16; it turns out that
5942 most smartlists hold around 8-12 elements tops.
5943 - Make dumpstats() log the fullness and size of openssl-internal
5945 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
5946 patch to their OpenSSL, turn it on to save memory on servers. This
5947 patch will (with any luck) get included in a mainline distribution
5949 - Fix a memory leak when v3 directory authorities load their keys
5950 and cert from disk. Bugfix on 0.2.0.1-alpha.
5951 - Stop using malloc_usable_size() to use more area than we had
5952 actually allocated: it was safe, but made valgrind really unhappy.
5953 - Make the assert_circuit_ok() function work correctly on circuits that
5954 have already been marked for close.
5955 - Fix uninitialized size field for memory area allocation: may improve
5956 memory performance during directory parsing.
5958 o Minor bugfixes (clients):
5959 - Stop reloading the router list from disk for no reason when we
5960 run out of reachable directory mirrors. Once upon a time reloading
5961 it would set the 'is_running' flag back to 1 for them. It hasn't
5962 done that for a long time.
5963 - When we had picked an exit node for a connection, but marked it as
5964 "optional", and it turned out we had no onion key for the exit,
5965 stop wanting that exit and try again. This situation may not
5966 be possible now, but will probably become feasible with proposal
5967 158. Spotted by rovv. Fixes another case of bug 752.
5968 - Fix a bug in address parsing that was preventing bridges or hidden
5969 service targets from being at IPv6 addresses.
5970 - Do not remove routers as too old if we do not have any consensus
5971 document. Bugfix on 0.2.0.7-alpha.
5972 - When an exit relay resolves a stream address to a local IP address,
5973 do not just keep retrying that same exit relay over and
5974 over. Instead, just close the stream. Addresses bug 872. Bugfix
5975 on 0.2.0.32. Patch from rovv.
5976 - Made Tor a little less aggressive about deleting expired
5977 certificates. Partial fix for bug 854.
5978 - Treat duplicate certificate fetches as failures, so that we do
5979 not try to re-fetch an expired certificate over and over and over.
5980 - Do not say we're fetching a certificate when we'll in fact skip it
5981 because of a pending download.
5982 - If we have correct permissions on $datadir, we complain to stdout
5983 and fail to start. But dangerous permissions on
5984 $datadir/cached-status/ would cause us to open a log and complain
5985 there. Now complain to stdout and fail to start in both cases. Fixes
5986 bug 820, reported by seeess.
5988 o Minor bugfixes (bridges):
5989 - When we made bridge authorities stop serving bridge descriptors over
5990 unencrypted links, we also broke DirPort reachability testing for
5991 bridges. So bridges with a non-zero DirPort were printing spurious
5992 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5993 - Don't allow a bridge to publish its router descriptor to a
5994 non-bridge directory authority. Fixes part of bug 932.
5995 - When we change to or from being a bridge, reset our counts of
5996 client usage by country. Fixes bug 932.
5998 o Minor bugfixes (relays):
5999 - Log correct error messages for DNS-related network errors on
6001 - Actually return -1 in the error case for read_bandwidth_usage().
6002 Harmless bug, since we currently don't care about the return value
6003 anywhere. Bugfix on 0.2.0.9-alpha.
6004 - Provide a more useful log message if bug 977 (related to buffer
6005 freelists) ever reappears, and do not crash right away.
6006 - We were already rejecting relay begin cells with destination port
6007 of 0. Now also reject extend cells with destination port or address
6008 of 0. Suggested by lark.
6009 - When we can't transmit a DNS request due to a network error, retry
6010 it after a while, and eventually transmit a failing response to
6011 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
6012 - Solve a bug that kept hardware crypto acceleration from getting
6013 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6015 - When a canonical connection appears later in our internal list
6016 than a noncanonical one for a given OR ID, always use the
6017 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6019 - Avoid some nasty corner cases in the logic for marking connections
6020 as too old or obsolete or noncanonical for circuits. Partial
6022 - Fix another interesting corner-case of bug 891 spotted by rovv:
6023 Previously, if two hosts had different amounts of clock drift, and
6024 one of them created a new connection with just the wrong timing,
6025 the other might decide to deprecate the new connection erroneously.
6026 Bugfix on 0.1.1.13-alpha.
6027 - If one win32 nameserver fails to get added, continue adding the
6028 rest, and don't automatically fail.
6029 - Fix a bug where an unreachable relay would establish enough
6030 reachability testing circuits to do a bandwidth test -- if
6031 we already have a connection to the middle hop of the testing
6032 circuit, then it could establish the last hop by using the existing
6033 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6034 circuits no longer use entry guards in 0.2.1.3-alpha.
6036 o Minor bugfixes (directory authorities):
6037 - Limit uploaded directory documents to be 16M rather than 500K.
6038 The directory authorities were refusing v3 consensus votes from
6039 other authorities, since the votes are now 504K. Fixes bug 959;
6040 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
6041 - Directory authorities should never send a 503 "busy" response to
6042 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
6044 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6045 headers. Bugfix on 0.2.0.10-alpha.
6047 o Minor bugfixes (hidden services):
6048 - When we can't find an intro key for a v2 hidden service descriptor,
6049 fall back to the v0 hidden service descriptor and log a bug message.
6050 Workaround for bug 1024.
6051 - In very rare situations new hidden service descriptors were
6052 published earlier than 30 seconds after the last change to the
6053 service. (We currently think that a hidden service descriptor
6054 that's been stable for 30 seconds is worth publishing.)
6055 - If a hidden service sends us an END cell, do not consider
6056 retrying the connection; just close it. Patch from rovv.
6057 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6058 service directories if they have no advertised dir port. Bugfix
6061 o Minor bugfixes (tools):
6062 - In the torify(1) manpage, mention that tsocks will leak your
6065 o Minor bugfixes (controllers):
6066 - If the controller claimed responsibility for a stream, but that
6067 stream never finished making its connection, it would live
6068 forever in circuit_wait state. Now we close it after SocksTimeout
6069 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
6070 - Make DNS resolved controller events into "CLOSED", not
6071 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6073 - The control port would close the connection before flushing long
6074 replies, such as the network consensus, if a QUIT command was issued
6075 before the reply had completed. Now, the control port flushes all
6076 pending replies before closing the connection. Also fix a spurious
6077 warning when a QUIT command is issued after a malformed or rejected
6078 AUTHENTICATE command, but before the connection was closed. Patch
6079 by Marcus Griep. Fixes bugs 1015 and 1016.
6080 - Fix a bug that made stream bandwidth get misreported to the
6083 o Deprecated and removed features:
6084 - The old "tor --version --version" command, which would print out
6085 the subversion "Id" of most of the source files, is now removed. It
6086 turned out to be less useful than we'd expected, and harder to
6088 - RedirectExits has been removed. It was deprecated since
6090 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6091 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6092 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6093 - Directory mirrors no longer fetch the v1 directory or
6094 running-routers files. They are obsolete, and nobody asks for them
6095 anymore. This is the first step to making v1 authorities obsolete.
6096 - Take out the TestVia config option, since it was a workaround for
6097 a bug that was fixed in Tor 0.1.1.21.
6098 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6099 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6100 and nobody seems to be using them. Fixes bug 754. Bugfix on
6101 0.1.0.1-rc. Patch from Christian Wilms.
6102 - Remove all backward-compatibility code for relays running
6103 versions of Tor so old that they no longer work at all on the
6106 o Code simplifications and refactoring:
6107 - Tool-assisted documentation cleanup. Nearly every function or
6108 static variable in Tor should have its own documentation now.
6109 - Rename the confusing or_is_obsolete field to the more appropriate
6110 is_bad_for_new_circs, and move it to or_connection_t where it
6112 - Move edge-only flags from connection_t to edge_connection_t: not
6113 only is this better coding, but on machines of plausible alignment,
6114 it should save 4-8 bytes per connection_t. "Every little bit helps."
6115 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6116 for consistency; keep old option working for backward compatibility.
6117 - Simplify the code for finding connections to use for a circuit.
6118 - Revise the connection_new functions so that a more typesafe variant
6119 exists. This will work better with Coverity, and let us find any
6120 actual mistakes we're making here.
6121 - Refactor unit testing logic so that dmalloc can be used sensibly
6122 with unit tests to check for memory leaks.
6123 - Move all hidden-service related fields from connection and circuit
6124 structure to substructures: this way they won't eat so much memory.
6125 - Squeeze 2-5% out of client performance (according to oprofile) by
6126 improving the implementation of some policy-manipulation functions.
6127 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6128 be more efficient. Formerly it was quadratic in the number of
6129 servers; now it should be linear. Fixes bug 509.
6130 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6131 and n_conn_id_digest fields into a separate structure that's
6132 only needed when the circuit has not yet attached to an n_conn.
6133 - Optimize out calls to time(NULL) that occur for every IO operation,
6134 or for every cell. On systems like Windows where time() is a
6135 slow syscall, this fix will be slightly helpful.
6138 Changes in version 0.2.0.35 - 2009-06-24
6140 - Avoid crashing in the presence of certain malformed descriptors.
6141 Found by lark, and by automated fuzzing.
6142 - Fix an edge case where a malicious exit relay could convince a
6143 controller that the client's DNS question resolves to an internal IP
6144 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6147 - Finally fix the bug where dynamic-IP relays disappear when their
6148 IP address changes: directory mirrors were mistakenly telling
6149 them their old address if they asked via begin_dir, so they
6150 never got an accurate answer about their new address, so they
6151 just vanished after a day. For belt-and-suspenders, relays that
6152 don't set Address in their config now avoid using begin_dir for
6153 all direct connections. Should fix bugs 827, 883, and 900.
6154 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6155 that would occur on some exit nodes when DNS failures and timeouts
6156 occurred in certain patterns. Fix for bug 957.
6159 - When starting with a cache over a few days old, do not leak
6160 memory for the obsolete router descriptors in it. Bugfix on
6161 0.2.0.33; fixes bug 672.
6162 - Hidden service clients didn't use a cached service descriptor that
6163 was older than 15 minutes, but wouldn't fetch a new one either,
6164 because there was already one in the cache. Now, fetch a v2
6165 descriptor unless the same descriptor was added to the cache within
6166 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6169 Changes in version 0.2.0.34 - 2009-02-08
6170 Tor 0.2.0.34 features several more security-related fixes. You should
6171 upgrade, especially if you run an exit relay (remote crash) or a
6172 directory authority (remote infinite loop), or you're on an older
6173 (pre-XP) or not-recently-patched Windows (remote exploit).
6175 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6176 have many known flaws, and nobody should be using them. You should
6177 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6178 stop using those packages and upgrade anyway.
6181 - Fix an infinite-loop bug on handling corrupt votes under certain
6182 circumstances. Bugfix on 0.2.0.8-alpha.
6183 - Fix a temporary DoS vulnerability that could be performed by
6184 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6185 - Avoid a potential crash on exit nodes when processing malformed
6186 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6187 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6188 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6191 - Fix compilation on systems where time_t is a 64-bit integer.
6192 Patch from Matthias Drochner.
6193 - Don't consider expiring already-closed client connections. Fixes
6194 bug 893. Bugfix on 0.0.2pre20.
6197 Changes in version 0.2.0.33 - 2009-01-21
6198 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6199 useful to users. It also finally fixes a bug where a relay or client
6200 that's been off for many days would take a long time to bootstrap.
6202 This update also fixes an important security-related bug reported by
6203 Ilja van Sprundel. You should upgrade. (We'll send out more details
6204 about the bug once people have had some time to upgrade.)
6207 - Fix a heap-corruption bug that may be remotely triggerable on
6208 some platforms. Reported by Ilja van Sprundel.
6211 - When a stream at an exit relay is in state "resolving" or
6212 "connecting" and it receives an "end" relay cell, the exit relay
6213 would silently ignore the end cell and not close the stream. If
6214 the client never closes the circuit, then the exit relay never
6215 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6217 - When sending CREATED cells back for a given circuit, use a 64-bit
6218 connection ID to find the right connection, rather than an addr:port
6219 combination. Now that we can have multiple OR connections between
6220 the same ORs, it is no longer possible to use addr:port to uniquely
6221 identify a connection.
6222 - Bridge relays that had DirPort set to 0 would stop fetching
6223 descriptors shortly after startup, and then briefly resume
6224 after a new bandwidth test and/or after publishing a new bridge
6225 descriptor. Bridge users that try to bootstrap from them would
6226 get a recent networkstatus but would get descriptors from up to
6227 18 hours earlier, meaning most of the descriptors were obsolete
6228 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6229 - Prevent bridge relays from serving their 'extrainfo' document
6230 to anybody who asks, now that extrainfo docs include potentially
6231 sensitive aggregated client geoip summaries. Bugfix on
6233 - If the cached networkstatus consensus is more than five days old,
6234 discard it rather than trying to use it. In theory it could be
6235 useful because it lists alternate directory mirrors, but in practice
6236 it just means we spend many minutes trying directory mirrors that
6237 are long gone from the network. Also discard router descriptors as
6238 we load them if they are more than five days old, since the onion
6239 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6242 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6243 could make gcc generate non-functional binary search code. Bugfix
6245 - Build correctly on platforms without socklen_t.
6246 - Compile without warnings on solaris.
6247 - Avoid potential crash on internal error during signature collection.
6248 Fixes bug 864. Patch from rovv.
6249 - Correct handling of possible malformed authority signing key
6250 certificates with internal signature types. Fixes bug 880.
6251 Bugfix on 0.2.0.3-alpha.
6252 - Fix a hard-to-trigger resource leak when logging credential status.
6254 - When we can't initialize DNS because the network is down, do not
6255 automatically stop Tor from starting. Instead, we retry failed
6256 dns_init() every 10 minutes, and change the exit policy to reject
6257 *:* until one succeeds. Fixes bug 691.
6258 - Use 64 bits instead of 32 bits for connection identifiers used with
6259 the controller protocol, to greatly reduce risk of identifier reuse.
6260 - When we're choosing an exit node for a circuit, and we have
6261 no pending streams, choose a good general exit rather than one that
6262 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6263 - Fix another case of assuming, when a specific exit is requested,
6264 that we know more than the user about what hosts it allows.
6265 Fixes one case of bug 752. Patch from rovv.
6266 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6267 seconds. Warn the user if lower values are given in the
6268 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6269 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6270 user if lower values are given in the configuration. Bugfix on
6271 0.1.1.17-rc. Patch by Sebastian.
6272 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6273 the cache because we already had a v0 descriptor with the same ID.
6274 Bugfix on 0.2.0.18-alpha.
6275 - Fix a race condition when freeing keys shared between main thread
6276 and CPU workers that could result in a memory leak. Bugfix on
6277 0.1.0.1-rc. Fixes bug 889.
6278 - Send a valid END cell back when a client tries to connect to a
6279 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6280 840. Patch from rovv.
6281 - Check which hops rendezvous stream cells are associated with to
6282 prevent possible guess-the-streamid injection attacks from
6283 intermediate hops. Fixes another case of bug 446. Based on patch
6285 - If a broken client asks a non-exit router to connect somewhere,
6286 do not even do the DNS lookup before rejecting the connection.
6287 Fixes another case of bug 619. Patch from rovv.
6288 - When a relay gets a create cell it can't decrypt (e.g. because it's
6289 using the wrong onion key), we were dropping it and letting the
6290 client time out. Now actually answer with a destroy cell. Fixes
6291 bug 904. Bugfix on 0.0.2pre8.
6293 o Minor bugfixes (hidden services):
6294 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6295 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6298 - Report the case where all signatures in a detached set are rejected
6299 differently than the case where there is an error handling the
6301 - When we realize that another process has modified our cached
6302 descriptors, print out a more useful error message rather than
6303 triggering an assertion. Fixes bug 885. Patch from Karsten.
6304 - Implement the 0x20 hack to better resist DNS poisoning: set the
6305 case on outgoing DNS requests randomly, and reject responses that do
6306 not match the case correctly. This logic can be disabled with the
6307 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6308 of servers that do not reliably preserve case in replies. See
6309 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6311 - Check DNS replies for more matching fields to better resist DNS
6313 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6314 compress cells, which are basically all encrypted, compressed, or
6318 Changes in version 0.2.0.32 - 2008-11-20
6319 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6320 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6321 a smaller security flaw that might allow an attacker to access local
6322 services, further improves hidden service performance, and fixes a
6323 variety of other issues.
6326 - The "User" and "Group" config options did not clear the
6327 supplementary group entries for the Tor process. The "User" option
6328 is now more robust, and we now set the groups to the specified
6329 user's primary group. The "Group" option is now ignored. For more
6330 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6331 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6332 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6333 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6334 consistently obeyed: if an exit relay refuses a stream because its
6335 exit policy doesn't allow it, we would remember what IP address
6336 the relay said the destination address resolves to, even if it's
6337 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6340 - Fix a DOS opportunity during the voting signature collection process
6341 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6343 o Major bugfixes (hidden services):
6344 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6345 we were failing the whole hidden service request when the v0
6346 descriptor fetch fails, even if the v2 fetch is still pending and
6347 might succeed. Similarly, if the last v2 fetch fails, we were
6348 failing the whole hidden service request even if a v0 fetch is
6349 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6350 - When extending a circuit to a hidden service directory to upload a
6351 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6352 requests failed, because the router descriptor has not been
6353 downloaded yet. In these cases, do not attempt to upload the
6354 rendezvous descriptor, but wait until the router descriptor is
6355 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6356 descriptor from a hidden service directory for which the router
6357 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6361 - Fix several infrequent memory leaks spotted by Coverity.
6362 - When testing for libevent functions, set the LDFLAGS variable
6363 correctly. Found by Riastradh.
6364 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6365 bootstrapping with tunneled directory connections. Bugfix on
6366 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6367 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6368 and we know that server B rejects most-but-not all connections to
6369 port 80, we would previously reject the connection. Now, we assume
6370 the user knows what they were asking for. Fixes bug 752. Bugfix
6371 on 0.0.9rc5. Diagnosed by BarkerJr.
6372 - If we overrun our per-second write limits a little, count this as
6373 having used up our write allocation for the second, and choke
6374 outgoing directory writes. Previously, we had only counted this when
6375 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6376 Bugfix on 0.2.0.x (??).
6377 - Remove the old v2 directory authority 'lefkada' from the default
6378 list. It has been gone for many months.
6379 - Stop doing unaligned memory access that generated bus errors on
6380 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6381 - Make USR2 log-level switch take effect immediately. Bugfix on
6384 o Minor bugfixes (controller):
6385 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6386 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6389 Changes in version 0.2.0.31 - 2008-09-03
6390 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6391 a big bug we're seeing where in rare cases traffic from one Tor stream
6392 gets mixed into another stream, and fixes a variety of smaller issues.
6395 - Make sure that two circuits can never exist on the same connection
6396 with the same circuit ID, even if one is marked for close. This
6397 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6398 - Relays now reject risky extend cells: if the extend cell includes
6399 a digest of all zeroes, or asks to extend back to the relay that
6400 sent the extend cell, tear down the circuit. Ideas suggested
6402 - If not enough of our entry guards are available so we add a new
6403 one, we might use the new one even if it overlapped with the
6404 current circuit's exit relay (or its family). Anonymity bugfix
6405 pointed out by rovv.
6408 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6409 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6410 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6411 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6412 - Pick size of default geoip filename string correctly on windows.
6413 Fixes bug 806. Bugfix on 0.2.0.30.
6414 - Make the autoconf script accept the obsolete --with-ssl-dir
6415 option as an alias for the actually-working --with-openssl-dir
6416 option. Fix the help documentation to recommend --with-openssl-dir.
6417 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6418 - When using the TransPort option on OpenBSD, and using the User
6419 option to change UID and drop privileges, make sure to open
6420 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6421 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6422 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6423 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6424 on the client side when connecting to a hidden service. Bugfix
6425 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6426 - When closing an application-side connection because its circuit is
6427 getting torn down, generate the stream event correctly. Bugfix on
6428 0.1.2.x. Anonymous patch.
6431 Changes in version 0.2.0.30 - 2008-07-15
6432 This new stable release switches to a more efficient directory
6433 distribution design, adds features to make connections to the Tor
6434 network harder to block, allows Tor to act as a DNS proxy, adds separate
6435 rate limiting for relayed traffic to make it easier for clients to
6436 become relays, fixes a variety of potential anonymity problems, and
6437 includes the usual huge pile of other features and bug fixes.
6439 o New v3 directory design:
6440 - Tor now uses a new way to learn about and distribute information
6441 about the network: the directory authorities vote on a common
6442 network status document rather than each publishing their own
6443 opinion. Now clients and caches download only one networkstatus
6444 document to bootstrap, rather than downloading one for each
6445 authority. Clients only download router descriptors listed in
6446 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
6448 - Set up moria1, tor26, and dizum as v3 directory authorities
6449 in addition to being v2 authorities. Also add three new ones:
6450 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
6451 dannenberg (run by CCC).
6452 - Switch to multi-level keys for directory authorities: now their
6453 long-term identity key can be kept offline, and they periodically
6454 generate a new signing key. Clients fetch the "key certificates"
6455 to keep up to date on the right keys. Add a standalone tool
6456 "tor-gencert" to generate key certificates. Implements proposal 103.
6457 - Add a new V3AuthUseLegacyKey config option to make it easier for
6458 v3 authorities to change their identity keys if another bug like
6459 Debian's OpenSSL RNG flaw appears.
6460 - Authorities and caches fetch the v2 networkstatus documents
6461 less often, now that v3 is recommended.
6463 o Make Tor connections stand out less on the wire:
6464 - Use an improved TLS handshake designed by Steven Murdoch in proposal
6465 124, as revised in proposal 130. The new handshake is meant to
6466 be harder for censors to fingerprint, and it adds the ability
6467 to detect certain kinds of man-in-the-middle traffic analysis
6468 attacks. The new handshake format includes version negotiation for
6469 OR connections as described in proposal 105, which will allow us
6470 to improve Tor's link protocol more safely in the future.
6471 - Enable encrypted directory connections by default for non-relays,
6472 so censor tools that block Tor directory connections based on their
6473 plaintext patterns will no longer work. This means Tor works in
6474 certain censored countries by default again.
6475 - Stop including recognizeable strings in the commonname part of
6476 Tor's x509 certificates.
6478 o Implement bridge relays:
6479 - Bridge relays (or "bridges" for short) are Tor relays that aren't
6480 listed in the main Tor directory. Since there is no complete public
6481 list of them, even an ISP that is filtering connections to all the
6482 known Tor relays probably won't be able to block all the bridges.
6483 See doc/design-paper/blocking.pdf and proposal 125 for details.
6484 - New config option BridgeRelay that specifies you want to be a
6485 bridge relay rather than a normal relay. When BridgeRelay is set
6486 to 1, then a) you cache dir info even if your DirPort ins't on,
6487 and b) the default for PublishServerDescriptor is now "bridge"
6488 rather than "v2,v3".
6489 - New config option "UseBridges 1" for clients that want to use bridge
6490 relays instead of ordinary entry guards. Clients then specify
6491 bridge relays by adding "Bridge" lines to their config file. Users
6492 can learn about a bridge relay either manually through word of
6493 mouth, or by one of our rate-limited mechanisms for giving out
6494 bridge addresses without letting an attacker easily enumerate them
6495 all. See https://www.torproject.org/bridges for details.
6496 - Bridge relays behave like clients with respect to time intervals
6497 for downloading new v3 consensus documents -- otherwise they
6498 stand out. Bridge users now wait until the end of the interval,
6499 so their bridge relay will be sure to have a new consensus document.
6501 o Implement bridge directory authorities:
6502 - Bridge authorities are like normal directory authorities, except
6503 they don't serve a list of known bridges. Therefore users that know
6504 a bridge's fingerprint can fetch a relay descriptor for that bridge,
6505 including fetching updates e.g. if the bridge changes IP address,
6506 yet an attacker can't just fetch a list of all the bridges.
6507 - Set up Tonga as the default bridge directory authority.
6508 - Bridge authorities refuse to serve bridge descriptors or other
6509 bridge information over unencrypted connections (that is, when
6510 responding to direct DirPort requests rather than begin_dir cells.)
6511 - Bridge directory authorities do reachability testing on the
6512 bridges they know. They provide router status summaries to the
6513 controller via "getinfo ns/purpose/bridge", and also dump summaries
6514 to a file periodically, so we can keep internal stats about which
6515 bridges are functioning.
6516 - If bridge users set the UpdateBridgesFromAuthority config option,
6517 but the digest they ask for is a 404 on the bridge authority,
6518 they fall back to contacting the bridge directly.
6519 - Bridges always use begin_dir to publish their server descriptor to
6520 the bridge authority using an anonymous encrypted tunnel.
6521 - Early work on a "bridge community" design: if bridge authorities set
6522 the BridgePassword config option, they will serve a snapshot of
6523 known bridge routerstatuses from their DirPort to anybody who
6524 knows that password. Unset by default.
6525 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
6526 report sanitized aggregated summaries in their extra-info documents
6527 privately to the bridge authority, listing which countries are
6528 able to reach them. We hope this mechanism will let us learn when
6529 certain countries start trying to block bridges.
6530 - Bridge authorities write bridge descriptors to disk, so they can
6531 reload them after a reboot. They can also export the descriptors
6532 to other programs, so we can distribute them to blocked users via
6533 the BridgeDB interface, e.g. via https://bridges.torproject.org/
6534 and bridges@torproject.org.
6536 o Tor can be a DNS proxy:
6537 - The new client-side DNS proxy feature replaces the need for
6538 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
6539 for DNS requests on port 9999, use the Tor network to resolve them
6540 anonymously, and send the reply back like a regular DNS server.
6541 The code still only implements a subset of DNS.
6542 - Add a new AutomapHostsOnResolve option: when it is enabled, any
6543 resolve request for hosts matching a given pattern causes Tor to
6544 generate an internal virtual address mapping for that host. This
6545 allows DNSPort to work sensibly with hidden service users. By
6546 default, .exit and .onion addresses are remapped; the list of
6547 patterns can be reconfigured with AutomapHostsSuffixes.
6548 - Add an "-F" option to tor-resolve to force a resolve for a .onion
6549 address. Thanks to the AutomapHostsOnResolve option, this is no
6550 longer a completely silly thing to do.
6552 o Major features (relay usability):
6553 - New config options RelayBandwidthRate and RelayBandwidthBurst:
6554 a separate set of token buckets for relayed traffic. Right now
6555 relayed traffic is defined as answers to directory requests, and
6556 OR connections that don't have any local circuits on them. See
6557 proposal 111 for details.
6558 - Create listener connections before we setuid to the configured
6559 User and Group. Now non-Windows users can choose port values
6560 under 1024, start Tor as root, and have Tor bind those ports
6561 before it changes to another UID. (Windows users could already
6563 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
6564 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
6565 on "vserver" accounts. Patch from coderman.
6567 o Major features (directory authorities):
6568 - Directory authorities track weighted fractional uptime and weighted
6569 mean-time-between failures for relays. WFU is suitable for deciding
6570 whether a node is "usually up", while MTBF is suitable for deciding
6571 whether a node is "likely to stay up." We need both, because
6572 "usually up" is a good requirement for guards, while "likely to
6573 stay up" is a good requirement for long-lived connections.
6574 - Directory authorities use a new formula for selecting which relays
6575 to advertise as Guards: they must be in the top 7/8 in terms of
6576 how long we have known about them, and above the median of those
6577 nodes in terms of weighted fractional uptime.
6578 - Directory authorities use a new formula for selecting which relays
6579 to advertise as Stable: when we have 4 or more days of data, use
6580 median measured MTBF rather than median declared uptime. Implements
6582 - Directory authorities accept and serve "extra info" documents for
6583 routers. Routers now publish their bandwidth-history lines in the
6584 extra-info docs rather than the main descriptor. This step saves
6585 60% (!) on compressed router descriptor downloads. Servers upload
6586 extra-info docs to any authority that accepts them; directory
6587 authorities now allow multiple router descriptors and/or extra
6588 info documents to be uploaded in a single go. Authorities, and
6589 caches that have been configured to download extra-info documents,
6590 download them as needed. Implements proposal 104.
6591 - Authorities now list relays who have the same nickname as
6592 a different named relay, but list them with a new flag:
6593 "Unnamed". Now we can make use of relays that happen to pick the
6594 same nickname as a server that registered two years ago and then
6595 disappeared. Implements proposal 122.
6596 - Store routers in a file called cached-descriptors instead of in
6597 cached-routers. Initialize cached-descriptors from cached-routers
6598 if the old format is around. The new format allows us to store
6599 annotations along with descriptors, to record the time we received
6600 each descriptor, its source, and its purpose: currently one of
6601 general, controller, or bridge.
6603 o Major features (other):
6604 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
6605 Tor can warn and/or refuse connections to ports commonly used with
6606 vulnerable-plaintext protocols. Currently we warn on ports 23,
6607 109, 110, and 143, but we don't reject any. Based on proposal 129
6608 by Kevin Bauer and Damon McCoy.
6609 - Integrate Karsten Loesing's Google Summer of Code project to publish
6610 hidden service descriptors on a set of redundant relays that are a
6611 function of the hidden service address. Now we don't have to rely
6612 on three central hidden service authorities for publishing and
6613 fetching every hidden service descriptor. Implements proposal 114.
6614 - Allow tunnelled directory connections to ask for an encrypted
6615 "begin_dir" connection or an anonymized "uses a full Tor circuit"
6616 connection independently. Now we can make anonymized begin_dir
6617 connections for (e.g.) more secure hidden service posting and
6620 o Major bugfixes (crashes and assert failures):
6621 - Stop imposing an arbitrary maximum on the number of file descriptors
6622 used for busy servers. Bug reported by Olaf Selke; patch from
6624 - Avoid possible failures when generating a directory with routers
6625 with over-long versions strings, or too many flags set.
6626 - Fix a rare assert error when we're closing one of our threads:
6627 use a mutex to protect the list of logs, so we never write to the
6628 list as it's being freed. Fixes the very rare bug 575, which is
6629 kind of the revenge of bug 222.
6630 - Avoid segfault in the case where a badly behaved v2 versioning
6631 directory sends a signed networkstatus with missing client-versions.
6632 - When we hit an EOF on a log (probably because we're shutting down),
6633 don't try to remove the log from the list: just mark it as
6634 unusable. (Bulletproofs against bug 222.)
6636 o Major bugfixes (code security fixes):
6637 - Detect size overflow in zlib code. Reported by Justin Ferguson and
6639 - Rewrite directory tokenization code to never run off the end of
6640 a string. Fixes bug 455. Patch from croup.
6641 - Be more paranoid about overwriting sensitive memory on free(),
6642 as a defensive programming tactic to ensure forward secrecy.
6644 o Major bugfixes (anonymity fixes):
6645 - Reject requests for reverse-dns lookup of names that are in
6646 a private address space. Patch from lodger.
6647 - Never report that we've used more bandwidth than we're willing to
6648 relay: it leaks how much non-relay traffic we're using. Resolves
6650 - As a client, do not believe any server that tells us that an
6651 address maps to an internal address space.
6652 - Warn about unsafe ControlPort configurations.
6653 - Directory authorities now call routers Fast if their bandwidth is
6654 at least 100KB/s, and consider their bandwidth adequate to be a
6655 Guard if it is at least 250KB/s, no matter the medians. This fix
6656 complements proposal 107.
6657 - Directory authorities now never mark more than 2 servers per IP as
6658 Valid and Running (or 5 on addresses shared by authorities).
6659 Implements proposal 109, by Kevin Bauer and Damon McCoy.
6660 - If we're a relay, avoid picking ourselves as an introduction point,
6661 a rendezvous point, or as the final hop for internal circuits. Bug
6662 reported by taranis and lodger.
6663 - Exit relays that are used as a client can now reach themselves
6664 using the .exit notation, rather than just launching an infinite
6665 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
6666 - Fix a bug where, when we were choosing the 'end stream reason' to
6667 put in our relay end cell that we send to the exit relay, Tor
6668 clients on Windows were sometimes sending the wrong 'reason'. The
6669 anonymity problem is that exit relays may be able to guess whether
6670 the client is running Windows, thus helping partition the anonymity
6671 set. Down the road we should stop sending reasons to exit relays,
6672 or otherwise prevent future versions of this bug.
6673 - Only update guard status (usable / not usable) once we have
6674 enough directory information. This was causing us to discard all our
6675 guards on startup if we hadn't been running for a few weeks. Fixes
6677 - When our directory information has been expired for a while, stop
6678 being willing to build circuits using it. Fixes bug 401.
6680 o Major bugfixes (peace of mind for relay operators)
6681 - Non-exit relays no longer answer "resolve" relay cells, so they
6682 can't be induced to do arbitrary DNS requests. (Tor clients already
6683 avoid using non-exit relays for resolve cells, but now servers
6684 enforce this too.) Fixes bug 619. Patch from lodger.
6685 - When we setconf ClientOnly to 1, close any current OR and Dir
6686 listeners. Reported by mwenge.
6688 o Major bugfixes (other):
6689 - If we only ever used Tor for hidden service lookups or posts, we
6690 would stop building circuits and start refusing connections after
6691 24 hours, since we falsely believed that Tor was dormant. Reported
6693 - Add a new __HashedControlSessionPassword option for controllers
6694 to use for one-off session password hashes that shouldn't get
6695 saved to disk by SAVECONF --- Vidalia users were accumulating a
6696 pile of HashedControlPassword lines in their torrc files, one for
6697 each time they had restarted Tor and then clicked Save. Make Tor
6698 automatically convert "HashedControlPassword" to this new option but
6699 only when it's given on the command line. Partial fix for bug 586.
6700 - Patch from "Andrew S. Lists" to catch when we contact a directory
6701 mirror at IP address X and he says we look like we're coming from
6702 IP address X. Otherwise this would screw up our address detection.
6703 - Reject uploaded descriptors and extrainfo documents if they're
6704 huge. Otherwise we'll cache them all over the network and it'll
6705 clog everything up. Suggested by Aljosha Judmayer.
6706 - When a hidden service was trying to establish an introduction point,
6707 and Tor *did* manage to reuse one of the preemptively built
6708 circuits, it didn't correctly remember which one it used,
6709 so it asked for another one soon after, until there were no
6710 more preemptive circuits, at which point it launched one from
6711 scratch. Bugfix on 0.0.9.x.
6713 o Rate limiting and load balancing improvements:
6714 - When we add data to a write buffer in response to the data on that
6715 write buffer getting low because of a flush, do not consider the
6716 newly added data as a candidate for immediate flushing, but rather
6717 make it wait until the next round of writing. Otherwise, we flush
6718 and refill recursively, and a single greedy TLS connection can
6719 eat all of our bandwidth.
6720 - When counting the number of bytes written on a TLS connection,
6721 look at the BIO actually used for writing to the network, not
6722 at the BIO used (sometimes) to buffer data for the network.
6723 Looking at different BIOs could result in write counts on the
6724 order of ULONG_MAX. Fixes bug 614.
6725 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6726 Tor won't realize it should publish a new relay descriptor. Fixes
6727 bug 688, reported by mfr.
6728 - Avoid using too little bandwidth when our clock skips a few seconds.
6729 - Choose which bridge to use proportional to its advertised bandwidth,
6730 rather than uniformly at random. This should speed up Tor for
6731 bridge users. Also do this for people who set StrictEntryNodes.
6733 o Bootstrapping faster and building circuits more intelligently:
6734 - Fix bug 660 that was preventing us from knowing that we should
6735 preemptively build circuits to handle expected directory requests.
6736 - When we're checking if we have enough dir info for each relay
6737 to begin establishing circuits, make sure that we actually have
6738 the descriptor listed in the consensus, not just any descriptor.
6739 - Correctly notify one-hop connections when a circuit build has
6740 failed. Possible fix for bug 669. Found by lodger.
6741 - Clients now hold circuitless TLS connections open for 1.5 times
6742 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
6743 rebuild a new circuit over them within that timeframe. Previously,
6744 they held them open only for KeepalivePeriod (5 minutes).
6746 o Performance improvements (memory):
6747 - Add OpenBSD malloc code from "phk" as an optional malloc
6748 replacement on Linux: some glibc libraries do very poorly with
6749 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
6750 ./configure to get the replacement malloc code.
6751 - Switch our old ring buffer implementation for one more like that
6752 used by free Unix kernels. The wasted space in a buffer with 1mb
6753 of data will now be more like 8k than 1mb. The new implementation
6754 also avoids realloc();realloc(); patterns that can contribute to
6755 memory fragmentation.
6756 - Change the way that Tor buffers data that it is waiting to write.
6757 Instead of queueing data cells in an enormous ring buffer for each
6758 client->OR or OR->OR connection, we now queue cells on a separate
6759 queue for each circuit. This lets us use less slack memory, and
6760 will eventually let us be smarter about prioritizing different kinds
6762 - Reference-count and share copies of address policy entries; only 5%
6763 of them were actually distinct.
6764 - Tune parameters for cell pool allocation to minimize amount of
6766 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
6767 for every single inactive connection_t. Free items from the
6768 4k/16k-buffer free lists when they haven't been used for a while.
6769 - Make memory debugging information describe more about history
6770 of cell allocation, so we can help reduce our memory use.
6771 - Be even more aggressive about releasing RAM from small
6772 empty buffers. Thanks to our free-list code, this shouldn't be too
6773 performance-intensive.
6774 - Log malloc statistics from mallinfo() on platforms where it exists.
6775 - Use memory pools to allocate cells with better speed and memory
6776 efficiency, especially on platforms where malloc() is inefficient.
6777 - Add a --with-tcmalloc option to the configure script to link
6778 against tcmalloc (if present). Does not yet search for non-system
6781 o Performance improvements (socket management):
6782 - Count the number of open sockets separately from the number of
6783 active connection_t objects. This will let us avoid underusing
6784 our allocated connection limit.
6785 - We no longer use socket pairs to link an edge connection to an
6786 anonymous directory connection or a DirPort test connection.
6787 Instead, we track the link internally and transfer the data
6788 in-process. This saves two sockets per "linked" connection (at the
6789 client and at the server), and avoids the nasty Windows socketpair()
6791 - We were leaking a file descriptor if Tor started with a zero-length
6792 cached-descriptors file. Patch by "freddy77".
6794 o Performance improvements (CPU use):
6795 - Never walk through the list of logs if we know that no log target
6796 is interested in a given message.
6797 - Call routerlist_remove_old_routers() much less often. This should
6798 speed startup, especially on directory caches.
6799 - Base64 decoding was actually showing up on our profile when parsing
6800 the initial descriptor file; switch to an in-process all-at-once
6801 implementation that's about 3.5x times faster than calling out to
6803 - Use a slightly simpler string hashing algorithm (copying Python's
6804 instead of Java's) and optimize our digest hashing algorithm to take
6805 advantage of 64-bit platforms and to remove some possibly-costly
6807 - When implementing AES counter mode, update only the portions of the
6808 counter buffer that need to change, and don't keep separate
6809 network-order and host-order counters on big-endian hosts (where
6811 - Add an in-place version of aes_crypt() so that we can avoid doing a
6812 needless memcpy() call on each cell payload.
6813 - Use Critical Sections rather than Mutexes for synchronizing threads
6814 on win32; Mutexes are heavier-weight, and designed for synchronizing
6817 o Performance improvements (bandwidth use):
6818 - Don't try to launch new descriptor downloads quite so often when we
6819 already have enough directory information to build circuits.
6820 - Version 1 directories are no longer generated in full. Instead,
6821 authorities generate and serve "stub" v1 directories that list
6822 no servers. This will stop Tor versions 0.1.0.x and earlier from
6823 working, but (for security reasons) nobody should be running those
6825 - Avoid going directly to the directory authorities even if you're a
6826 relay, if you haven't found yourself reachable yet or if you've
6827 decided not to advertise your dirport yet. Addresses bug 556.
6828 - If we've gone 12 hours since our last bandwidth check, and we
6829 estimate we have less than 50KB bandwidth capacity but we could
6830 handle more, do another bandwidth test.
6831 - Support "If-Modified-Since" when answering HTTP requests for
6832 directories, running-routers documents, and v2 and v3 networkstatus
6833 documents. (There's no need to support it for router descriptors,
6834 since those are downloaded by descriptor digest.)
6835 - Stop fetching directory info so aggressively if your DirPort is
6836 on but your ORPort is off; stop fetching v2 dir info entirely.
6837 You can override these choices with the new FetchDirInfoEarly
6840 o Changed config option behavior (features):
6841 - Configuration files now accept C-style strings as values. This
6842 helps encode characters not allowed in the current configuration
6843 file format, such as newline or #. Addresses bug 557.
6844 - Add hidden services and DNSPorts to the list of things that make
6845 Tor accept that it has running ports. Change starting Tor with no
6846 ports from a fatal error to a warning; we might change it back if
6847 this turns out to confuse anybody. Fixes bug 579.
6848 - Make PublishServerDescriptor default to 1, so the default doesn't
6849 have to change as we invent new directory protocol versions.
6850 - Allow people to say PreferTunnelledDirConns rather than
6851 PreferTunneledDirConns, for those alternate-spellers out there.
6852 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
6853 accommodate the growing number of servers that use the default
6854 and are reaching it.
6855 - Make it possible to enable HashedControlPassword and
6856 CookieAuthentication at the same time.
6857 - When a TrackHostExits-chosen exit fails too many times in a row,
6858 stop using it. Fixes bug 437.
6860 o Changed config option behavior (bugfixes):
6861 - Do not read the configuration file when we've only been told to
6862 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
6863 based on patch from Sebastian Hahn.
6864 - Actually validate the options passed to AuthDirReject,
6865 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
6866 - Make "ClientOnly 1" config option disable directory ports too.
6867 - Don't stop fetching descriptors when FetchUselessDescriptors is
6868 set, even if we stop asking for circuits. Bug reported by tup
6870 - Servers used to decline to publish their DirPort if their
6871 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
6872 they look only at BandwidthRate and RelayBandwidthRate.
6873 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
6874 minus 1 byte: the actual maximum declared bandwidth.
6875 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
6876 - Make the NodeFamilies config option work. (Reported by
6877 lodger -- it has never actually worked, even though we added it
6879 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
6880 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
6882 o New config options:
6883 - New configuration options AuthDirMaxServersPerAddr and
6884 AuthDirMaxServersperAuthAddr to override default maximum number
6885 of servers allowed on a single IP address. This is important for
6886 running a test network on a single host.
6887 - Three new config options (AlternateDirAuthority,
6888 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
6889 user selectively replace the default directory authorities by type,
6890 rather than the all-or-nothing replacement that DirServer offers.
6891 - New config options AuthDirBadDir and AuthDirListBadDirs for
6892 authorities to mark certain relays as "bad directories" in the
6893 networkstatus documents. Also supports the "!baddir" directive in
6894 the approved-routers file.
6895 - New config option V2AuthoritativeDirectory that all v2 directory
6896 authorities must set. This lets v3 authorities choose not to serve
6897 v2 directory information.
6899 o Minor features (other):
6900 - When we're not serving v2 directory information, there is no reason
6901 to actually keep any around. Remove the obsolete files and directory
6902 on startup if they are very old and we aren't going to serve them.
6903 - When we negotiate a v2 link-layer connection (not yet implemented),
6904 accept RELAY_EARLY cells and turn them into RELAY cells if we've
6905 negotiated a v1 connection for their next step. Initial steps for
6907 - When we have no consensus, check FallbackNetworkstatusFile (defaults
6908 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
6909 we can start out knowing some directory caches. We don't ship with
6910 a fallback consensus by default though, because it was making
6911 bootstrapping take too long while we tried many down relays.
6912 - Authorities send back an X-Descriptor-Not-New header in response to
6913 an accepted-but-discarded descriptor upload. Partially implements
6915 - If we find a cached-routers file that's been sitting around for more
6916 than 28 days unmodified, then most likely it's a leftover from
6917 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
6919 - When we (as a cache) download a descriptor because it was listed
6920 in a consensus, remember when the consensus was supposed to expire,
6921 and don't expire the descriptor until then.
6922 - Optionally (if built with -DEXPORTMALLINFO) export the output
6923 of mallinfo via http, as tor/mallinfo.txt. Only accessible
6925 - Tag every guard node in our state file with the version that
6926 we believe added it, or with our own version if we add it. This way,
6927 if a user temporarily runs an old version of Tor and then switches
6928 back to a new one, she doesn't automatically lose her guards.
6929 - When somebody requests a list of statuses or servers, and we have
6930 none of those, return a 404 rather than an empty 200.
6931 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
6933 - Add an HSAuthorityRecordStats option that hidden service authorities
6934 can use to track statistics of overall hidden service usage without
6935 logging information that would be as useful to an attacker.
6936 - Allow multiple HiddenServicePort directives with the same virtual
6937 port; when they occur, the user is sent round-robin to one
6938 of the target ports chosen at random. Partially fixes bug 393 by
6939 adding limited ad-hoc round-robining.
6940 - Revamp file-writing logic so we don't need to have the entire
6941 contents of a file in memory at once before we write to disk. Tor,
6944 o Minor bugfixes (other):
6945 - Alter the code that tries to recover from unhandled write
6946 errors, to not try to flush onto a socket that's given us
6948 - Directory mirrors no longer include a guess at the client's IP
6949 address if the connection appears to be coming from the same /24
6950 network; it was producing too many wrong guesses.
6951 - If we're trying to flush the last bytes on a connection (for
6952 example, when answering a directory request), reset the
6953 time-to-give-up timeout every time we manage to write something
6955 - Reject router descriptors with out-of-range bandwidthcapacity or
6956 bandwidthburst values.
6957 - If we can't expand our list of entry guards (e.g. because we're
6958 using bridges or we have StrictEntryNodes set), don't mark relays
6959 down when they fail a directory request. Otherwise we're too quick
6960 to mark all our entry points down.
6961 - Authorities no longer send back "400 you're unreachable please fix
6962 it" errors to Tor servers that aren't online all the time. We're
6963 supposed to tolerate these servers now.
6964 - Let directory authorities startup even when they can't generate
6965 a descriptor immediately, e.g. because they don't know their
6967 - Correctly enforce that elements of directory objects do not appear
6968 more often than they are allowed to appear.
6969 - Stop allowing hibernating servers to be "stable" or "fast".
6970 - On Windows, we were preventing other processes from reading
6971 cached-routers while Tor was running. (Reported by janbar)
6972 - Check return values from pthread_mutex functions.
6973 - When opening /dev/null in finish_daemonize(), do not pass the
6974 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6975 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6977 o Controller features:
6978 - The GETCONF command now escapes and quotes configuration values
6979 that don't otherwise fit into the torrc file.
6980 - The SETCONF command now handles quoted values correctly.
6981 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
6982 ask about source, timestamp of arrival, purpose, etc. We need
6983 something like this to help Vidalia not do GeoIP lookups on bridge
6985 - Allow multiple HashedControlPassword config lines, to support
6986 multiple controller passwords.
6987 - Accept LF instead of CRLF on controller, since some software has a
6988 hard time generating real Internet newlines.
6989 - Add GETINFO values for the server status events
6990 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
6992 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
6993 GETINFO for Torstat to use until it can switch to using extrainfos.
6994 - New config option CookieAuthFile to choose a new location for the
6995 cookie authentication file, and config option
6996 CookieAuthFileGroupReadable to make it group-readable.
6997 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
6998 match requests to applications. Patch from Robert Hogan.
6999 - Add a RESOLVE command to launch hostname lookups. Original patch
7001 - Add GETINFO status/enough-dir-info to let controllers tell whether
7002 Tor has downloaded sufficient directory information. Patch from Tup.
7003 - You can now use the ControlSocket option to tell Tor to listen for
7004 controller connections on Unix domain sockets on systems that
7005 support them. Patch from Peter Palfrader.
7006 - New "GETINFO address-mappings/*" command to get address mappings
7007 with expiry information. "addr-mappings/*" is now deprecated.
7009 - Add a new config option __DisablePredictedCircuits designed for
7010 use by the controller, when we don't want Tor to build any circuits
7012 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
7013 so we can exit from the middle of the circuit.
7014 - Implement "getinfo status/circuit-established".
7015 - Implement "getinfo status/version/..." so a controller can tell
7016 whether the current version is recommended, and whether any versions
7017 are good, and how many authorities agree. Patch from "shibz".
7018 - Controllers should now specify cache=no or cache=yes when using
7019 the +POSTDESCRIPTOR command.
7020 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7021 Robert Hogan. Fixes the first part of bug 681.
7022 - When reporting clock skew, and we know that the clock is _at least
7023 as skewed_ as some value, but we don't know the actual value,
7024 report the value as a "minimum skew."
7026 o Controller bugfixes:
7027 - Generate "STATUS_SERVER" events rather than misspelled
7028 "STATUS_SEVER" events. Caught by mwenge.
7029 - Reject controller commands over 1MB in length, so rogue
7030 processes can't run us out of memory.
7031 - Change the behavior of "getinfo status/good-server-descriptor"
7032 so it doesn't return failure when any authority disappears.
7033 - Send NAMESERVER_STATUS messages for a single failed nameserver
7035 - When the DANGEROUS_VERSION controller status event told us we're
7036 running an obsolete version, it used the string "OLD" to describe
7037 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7038 "OBSOLETE" in both cases.
7039 - Respond to INT and TERM SIGNAL commands before we execute the
7040 signal, in case the signal shuts us down. We had a patch in
7041 0.1.2.1-alpha that tried to do this by queueing the response on
7042 the connection's buffer before shutting down, but that really
7043 isn't the same thing at all. Bug located by Matt Edman.
7044 - Provide DNS expiry times in GMT, not in local time. For backward
7045 compatibility, ADDRMAP events only provide GMT expiry in an extended
7046 field. "GETINFO address-mappings" always does the right thing.
7047 - Use CRLF line endings properly in NS events.
7048 - Make 'getinfo fingerprint' return a 551 error if we're not a
7049 server, so we match what the control spec claims we do. Reported
7051 - Fix a typo in an error message when extendcircuit fails that
7052 caused us to not follow the \r\n-based delimiter protocol. Reported
7054 - When tunneling an encrypted directory connection, and its first
7055 circuit fails, do not leave it unattached and ask the controller
7056 to deal. Fixes the second part of bug 681.
7057 - Treat some 403 responses from directory servers as INFO rather than
7058 WARN-severity events.
7060 o Portability / building / compiling:
7061 - When building with --enable-gcc-warnings, check for whether Apple's
7062 warning "-Wshorten-64-to-32" is available.
7063 - Support compilation to target iPhone; patch from cjacker huang.
7064 To build for iPhone, pass the --enable-iphone option to configure.
7065 - Port Tor to build and run correctly on Windows CE systems, using
7066 the wcecompat library. Contributed by Valerio Lupi.
7067 - Detect non-ASCII platforms (if any still exist) and refuse to
7068 build there: some of our code assumes that 'A' is 65 and so on.
7069 - Clear up some MIPSPro compiler warnings.
7070 - Make autoconf search for libevent, openssl, and zlib consistently.
7071 - Update deprecated macros in configure.in.
7072 - When warning about missing headers, tell the user to let us
7073 know if the compile succeeds anyway, so we can downgrade the
7075 - Include the current subversion revision as part of the version
7076 string: either fetch it directly if we're in an SVN checkout, do
7077 some magic to guess it if we're in an SVK checkout, or use
7078 the last-detected version if we're building from a .tar.gz.
7079 Use this version consistently in log messages.
7080 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
7081 - Read resolv.conf files correctly on platforms where read() returns
7082 partial results on small file reads.
7083 - Build without verbose warnings even on gcc 4.2 and 4.3.
7084 - On Windows, correctly detect errors when listing the contents of
7085 a directory. Fix from lodger.
7086 - Run 'make test' as part of 'make dist', so we stop releasing so
7087 many development snapshots that fail their unit tests.
7088 - Add support to detect Libevent versions in the 1.4.x series
7090 - Add command-line arguments to unit-test executable so that we can
7091 invoke any chosen test from the command line rather than having
7092 to run the whole test suite at once; and so that we can turn on
7093 logging for the unit tests.
7094 - Do not automatically run configure from autogen.sh. This
7095 non-standard behavior tended to annoy people who have built other
7097 - Fix a macro/CPP interaction that was confusing some compilers:
7098 some GCCs don't like #if/#endif pairs inside macro arguments.
7100 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7101 Fixes bug 704; fix from Steven Murdoch.
7102 - Correctly detect transparent proxy support on Linux hosts that
7103 require in.h to be included before netfilter_ipv4.h. Patch
7106 o Logging improvements:
7107 - When we haven't had any application requests lately, don't bother
7108 logging that we have expired a bunch of descriptors.
7109 - When attempting to open a logfile fails, tell us why.
7110 - Only log guard node status when guard node status has changed.
7111 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7112 make "INFO" 75% less verbose.
7113 - When SafeLogging is disabled, log addresses along with all TLS
7115 - Report TLS "zero return" case as a "clean close" and "IO error"
7116 as a "close". Stop calling closes "unexpected closes": existing
7117 Tors don't use SSL_close(), so having a connection close without
7118 the TLS shutdown handshake is hardly unexpected.
7119 - When we receive a consensus from the future, warn about skew.
7120 - Make "not enough dir info yet" warnings describe *why* Tor feels
7121 it doesn't have enough directory info yet.
7122 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7123 consumers. (We already do this on HUP.)
7124 - Give more descriptive well-formedness errors for out-of-range
7125 hidden service descriptor/protocol versions.
7126 - Stop recommending that every server operator send mail to tor-ops.
7127 Resolves bug 597. Bugfix on 0.1.2.x.
7128 - Improve skew reporting: try to give the user a better log message
7129 about how skewed they are, and how much this matters.
7130 - New --quiet command-line option to suppress the default console log.
7131 Good in combination with --hash-password.
7132 - Don't complain that "your server has not managed to confirm that its
7133 ports are reachable" if we haven't been able to build any circuits
7135 - Detect the reason for failing to mmap a descriptor file we just
7136 wrote, and give a more useful log message. Fixes bug 533.
7137 - Always prepend "Bug: " to any log message about a bug.
7138 - When dumping memory usage, list bytes used in buffer memory
7140 - When running with dmalloc, dump more stats on hup and on exit.
7141 - Put a platform string (e.g. "Linux i686") in the startup log
7142 message, so when people paste just their logs, we know if it's
7143 OpenBSD or Windows or what.
7144 - When logging memory usage, break down memory used in buffers by
7146 - When we are reporting the DirServer line we just parsed, we were
7147 logging the second stanza of the key fingerprint, not the first.
7148 - Even though Windows is equally happy with / and \ as path separators,
7149 try to use \ consistently on Windows and / consistently on Unix: it
7150 makes the log messages nicer.
7151 - On OSX, stop warning the user that kqueue support in libevent is
7152 "experimental", since it seems to have worked fine for ages.
7154 o Contributed scripts and tools:
7155 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7156 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7158 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
7159 Unix users an easy way to script their Tor process (e.g. by
7160 adjusting bandwidth based on the time of the day).
7161 - In the exitlist script, only consider the most recently published
7162 server descriptor for each server. Also, when the user requests
7163 a list of servers that _reject_ connections to a given address,
7164 explicitly exclude the IPs that also have servers that accept
7165 connections to that address. Resolves bug 405.
7166 - Include a new contrib/tor-exit-notice.html file that exit relay
7167 operators can put on their website to help reduce abuse queries.
7169 o Newly deprecated features:
7170 - The status/version/num-versioning and status/version/num-concurring
7171 GETINFO controller options are no longer useful in the v3 directory
7172 protocol: treat them as deprecated, and warn when they're used.
7173 - The RedirectExits config option is now deprecated.
7176 - Drop the old code to choke directory connections when the
7177 corresponding OR connections got full: thanks to the cell queue
7178 feature, OR conns don't get full any more.
7179 - Remove the old "dns worker" server DNS code: it hasn't been default
7180 since 0.1.2.2-alpha, and all the servers are using the new
7182 - Remove the code to generate the oldest (v1) directory format.
7183 - Remove support for the old bw_accounting file: we've been storing
7184 bandwidth accounting information in the state file since
7185 0.1.2.5-alpha. This may result in bandwidth accounting errors
7186 if you try to upgrade from 0.1.1.x or earlier, or if you try to
7187 downgrade to 0.1.1.x or earlier.
7188 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7189 it, it had no AES, and it hasn't seen any security patches since
7191 - Stop overloading the circuit_t.onionskin field for both "onionskin
7192 from a CREATE cell that we are waiting for a cpuworker to be
7193 assigned" and "onionskin from an EXTEND cell that we are going to
7194 send to an OR as soon as we are connected". Might help with bug 600.
7195 - Remove the tor_strpartition() function: its logic was confused,
7196 and it was only used for one thing that could be implemented far
7198 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
7199 and TorControl.py, as they use the old v0 controller protocol,
7200 and are obsoleted by TorFlow anyway.
7201 - Drop support for v1 rendezvous descriptors, since we never used
7202 them anyway, and the code has probably rotted by now. Based on
7203 patch from Karsten Loesing.
7204 - Stop allowing address masks that do not correspond to bit prefixes.
7205 We have warned about these for a really long time; now it's time
7206 to reject them. (Patch from croup.)
7207 - Remove an optimization in the AES counter-mode code that assumed
7208 that the counter never exceeded 2^68. When the counter can be set
7209 arbitrarily as an IV (as it is by Karsten's new hidden services
7210 code), this assumption no longer holds.
7211 - Disable the SETROUTERPURPOSE controller command: it is now
7215 Changes in version 0.1.2.19 - 2008-01-17
7216 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7217 exit policy a little bit more conservative so it's safer to run an
7218 exit relay on a home system, and fixes a variety of smaller issues.
7221 - Exit policies now reject connections that are addressed to a
7222 relay's public (external) IP address too, unless
7223 ExitPolicyRejectPrivate is turned off. We do this because too
7224 many relays are running nearby to services that trust them based
7228 - When the clock jumps forward a lot, do not allow the bandwidth
7229 buckets to become negative. Fixes bug 544.
7230 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7231 on every successful resolve. Reported by Mike Perry.
7232 - Purge old entries from the "rephist" database and the hidden
7233 service descriptor database even when DirPort is zero.
7234 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7235 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7236 crashing or mis-answering these requests.
7237 - When we decide to send a 503 response to a request for servers, do
7238 not then also send the server descriptors: this defeats the whole
7239 purpose. Fixes bug 539.
7242 - Changing the ExitPolicyRejectPrivate setting should cause us to
7243 rebuild our server descriptor.
7244 - Fix handling of hex nicknames when answering controller requests for
7245 networkstatus by name, or when deciding whether to warn about
7246 unknown routers in a config option. (Patch from mwenge.)
7247 - Fix a couple of hard-to-trigger autoconf problems that could result
7248 in really weird results on platforms whose sys/types.h files define
7249 nonstandard integer types.
7250 - Don't try to create the datadir when running --verify-config or
7251 --hash-password. Resolves bug 540.
7252 - If we were having problems getting a particular descriptor from the
7253 directory caches, and then we learned about a new descriptor for
7254 that router, we weren't resetting our failure count. Reported
7256 - Although we fixed bug 539 (where servers would send HTTP status 503
7257 responses _and_ send a body too), there are still servers out there
7258 that haven't upgraded. Therefore, make clients parse such bodies
7259 when they receive them.
7260 - Run correctly on systems where rlim_t is larger than unsigned long.
7261 This includes some 64-bit systems.
7262 - Run correctly on platforms (like some versions of OS X 10.5) where
7263 the real limit for number of open files is OPEN_FILES, not rlim_max
7264 from getrlimit(RLIMIT_NOFILES).
7265 - Avoid a spurious free on base64 failure.
7266 - Avoid segfaults on certain complex invocations of
7267 router_get_by_hexdigest().
7268 - Fix rare bug on REDIRECTSTREAM control command when called with no
7269 port set: it could erroneously report an error when none had
7273 Changes in version 0.1.2.18 - 2007-10-28
7274 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7275 hidden service introduction that were causing huge delays, and a big
7276 bug that was causing some servers to disappear from the network status
7277 lists for a few hours each day.
7279 o Major bugfixes (crashes):
7280 - If a connection is shut down abruptly because of something that
7281 happened inside connection_flushed_some(), do not call
7282 connection_finished_flushing(). Should fix bug 451:
7283 "connection_stop_writing: Assertion conn->write_event failed"
7284 Bugfix on 0.1.2.7-alpha.
7285 - Fix possible segfaults in functions called from
7286 rend_process_relay_cell().
7288 o Major bugfixes (hidden services):
7289 - Hidden services were choosing introduction points uniquely by
7290 hexdigest, but when constructing the hidden service descriptor
7291 they merely wrote the (potentially ambiguous) nickname.
7292 - Clients now use the v2 intro format for hidden service
7293 connections: they specify their chosen rendezvous point by identity
7294 digest rather than by (potentially ambiguous) nickname. These
7295 changes could speed up hidden service connections dramatically.
7297 o Major bugfixes (other):
7298 - Stop publishing a new server descriptor just because we get a
7299 HUP signal. This led (in a roundabout way) to some servers getting
7300 dropped from the networkstatus lists for a few hours each day.
7301 - When looking for a circuit to cannibalize, consider family as well
7302 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7303 circuit cannibalization).
7304 - When a router wasn't listed in a new networkstatus, we were leaving
7305 the flags for that router alone -- meaning it remained Named,
7306 Running, etc -- even though absence from the networkstatus means
7307 that it shouldn't be considered to exist at all anymore. Now we
7308 clear all the flags for routers that fall out of the networkstatus
7309 consensus. Fixes bug 529.
7312 - Don't try to access (or alter) the state file when running
7313 --list-fingerprint or --verify-config or --hash-password. Resolves
7315 - When generating information telling us how to extend to a given
7316 router, do not try to include the nickname if it is
7317 absent. Resolves bug 467.
7318 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7319 a way to trigger this remotely.)
7320 - When sending a status event to the controller telling it that an
7321 OR address is reachable, set the port correctly. (Previously we
7322 were reporting the dir port.)
7323 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7324 command. Bugfix on 0.1.2.17.
7325 - When loading bandwidth history, do not believe any information in
7326 the future. Fixes bug 434.
7327 - When loading entry guard information, do not believe any information
7329 - When we have our clock set far in the future and generate an
7330 onion key, then re-set our clock to be correct, we should not stop
7331 the onion key from getting rotated.
7332 - On some platforms, accept() can return a broken address. Detect
7333 this more quietly, and deal accordingly. Fixes bug 483.
7334 - It's not actually an error to find a non-pending entry in the DNS
7335 cache when canceling a pending resolve. Don't log unless stuff
7336 is fishy. Resolves bug 463.
7337 - Don't reset trusted dir server list when we set a configuration
7338 option. Patch from Robert Hogan.
7341 Changes in version 0.1.2.17 - 2007-08-30
7342 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
7343 X bundles. Vidalia 0.0.14 makes authentication required for the
7344 ControlPort in the default configuration, which addresses important
7345 security risks. Everybody who uses Vidalia (or another controller)
7348 In addition, this Tor update fixes major load balancing problems with
7349 path selection, which should speed things up a lot once many people
7352 o Major bugfixes (security):
7353 - We removed support for the old (v0) control protocol. It has been
7354 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
7355 become more of a headache than it's worth.
7357 o Major bugfixes (load balancing):
7358 - When choosing nodes for non-guard positions, weight guards
7359 proportionally less, since they already have enough load. Patch
7361 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7362 will allow fast Tor servers to get more attention.
7363 - When we're upgrading from an old Tor version, forget our current
7364 guards and pick new ones according to the new weightings. These
7365 three load balancing patches could raise effective network capacity
7366 by a factor of four. Thanks to Mike Perry for measurements.
7368 o Major bugfixes (stream expiration):
7369 - Expire not-yet-successful application streams in all cases if
7370 they've been around longer than SocksTimeout. Right now there are
7371 some cases where the stream will live forever, demanding a new
7372 circuit every 15 seconds. Fixes bug 454; reported by lodger.
7374 o Minor features (controller):
7375 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
7376 is valid before any authentication has been received. It tells
7377 a controller what kind of authentication is expected, and what
7378 protocol is spoken. Implements proposal 119.
7380 o Minor bugfixes (performance):
7381 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
7382 greatly speeding up loading cached-routers from disk on startup.
7383 - Disable sentinel-based debugging for buffer code: we squashed all
7384 the bugs that this was supposed to detect a long time ago, and now
7385 its only effect is to change our buffer sizes from nice powers of
7386 two (which platform mallocs tend to like) to values slightly over
7387 powers of two (which make some platform mallocs sad).
7389 o Minor bugfixes (misc):
7390 - If exit bandwidth ever exceeds one third of total bandwidth, then
7391 use the correct formula to weight exit nodes when choosing paths.
7392 Based on patch from Mike Perry.
7393 - Choose perfectly fairly among routers when choosing by bandwidth and
7394 weighting by fraction of bandwidth provided by exits. Previously, we
7395 would choose with only approximate fairness, and correct ourselves
7396 if we ran off the end of the list.
7397 - If we require CookieAuthentication but we fail to write the
7398 cookie file, we would warn but not exit, and end up in a state
7399 where no controller could authenticate. Now we exit.
7400 - If we require CookieAuthentication, stop generating a new cookie
7401 every time we change any piece of our config.
7402 - Refuse to start with certain directory authority keys, and
7403 encourage people using them to stop.
7404 - Terminate multi-line control events properly. Original patch
7406 - Fix a minor memory leak when we fail to find enough suitable
7407 servers to choose a circuit.
7408 - Stop leaking part of the descriptor when we run into a particularly
7409 unparseable piece of it.
7412 Changes in version 0.1.2.16 - 2007-08-01
7413 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
7414 remote attacker in certain situations to rewrite the user's torrc
7415 configuration file. This can completely compromise anonymity of users
7416 in most configurations, including those running the Vidalia bundles,
7417 TorK, etc. Or worse.
7419 o Major security fixes:
7420 - Close immediately after missing authentication on control port;
7421 do not allow multiple authentication attempts.
7424 Changes in version 0.1.2.15 - 2007-07-17
7425 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
7426 problems, fixes compilation on BSD, and fixes a variety of other
7427 bugs. Everybody should upgrade.
7429 o Major bugfixes (compilation):
7430 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
7432 o Major bugfixes (crashes):
7433 - Try even harder not to dereference the first character after
7434 an mmap(). Reported by lodger.
7435 - Fix a crash bug in directory authorities when we re-number the
7436 routerlist while inserting a new router.
7437 - When the cached-routers file is an even multiple of the page size,
7438 don't run off the end and crash. (Fixes bug 455; based on idea
7440 - Fix eventdns.c behavior on Solaris: It is critical to include
7441 orconfig.h _before_ sys/types.h, so that we can get the expected
7442 definition of _FILE_OFFSET_BITS.
7444 o Major bugfixes (security):
7445 - Fix a possible buffer overrun when using BSD natd support. Bug
7447 - When sending destroy cells from a circuit's origin, don't include
7448 the reason for tearing down the circuit. The spec says we didn't,
7449 and now we actually don't. Reported by lodger.
7450 - Keep streamids from different exits on a circuit separate. This
7451 bug may have allowed other routers on a given circuit to inject
7452 cells into streams. Reported by lodger; fixes bug 446.
7453 - If there's a never-before-connected-to guard node in our list,
7454 never choose any guards past it. This way we don't expand our
7455 guard list unless we need to.
7457 o Minor bugfixes (guard nodes):
7458 - Weight guard selection by bandwidth, so that low-bandwidth nodes
7459 don't get overused as guards.
7461 o Minor bugfixes (directory):
7462 - Correctly count the number of authorities that recommend each
7463 version. Previously, we were under-counting by 1.
7464 - Fix a potential crash bug when we load many server descriptors at
7465 once and some of them make others of them obsolete. Fixes bug 458.
7467 o Minor bugfixes (hidden services):
7468 - Stop tearing down the whole circuit when the user asks for a
7469 connection to a port that the hidden service didn't configure.
7472 o Minor bugfixes (misc):
7473 - On Windows, we were preventing other processes from reading
7474 cached-routers while Tor was running. Reported by janbar.
7475 - Fix a possible (but very unlikely) bug in picking routers by
7476 bandwidth. Add a log message to confirm that it is in fact
7477 unlikely. Patch from lodger.
7478 - Backport a couple of memory leak fixes.
7479 - Backport miscellaneous cosmetic bugfixes.
7482 Changes in version 0.1.2.14 - 2007-05-25
7483 Tor 0.1.2.14 changes the addresses of two directory authorities (this
7484 change especially affects those who serve or use hidden services),
7485 and fixes several other crash- and security-related bugs.
7487 o Directory authority changes:
7488 - Two directory authorities (moria1 and moria2) just moved to new
7489 IP addresses. This change will particularly affect those who serve
7490 or use hidden services.
7492 o Major bugfixes (crashes):
7493 - If a directory server runs out of space in the connection table
7494 as it's processing a begin_dir request, it will free the exit stream
7495 but leave it attached to the circuit, leading to unpredictable
7496 behavior. (Reported by seeess, fixes bug 425.)
7497 - Fix a bug in dirserv_remove_invalid() that would cause authorities
7498 to corrupt memory under some really unlikely scenarios.
7499 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
7500 - Avoid segfaults when reading from mmaped descriptor file. (Reported
7503 o Major bugfixes (security):
7504 - When choosing an entry guard for a circuit, avoid using guards
7505 that are in the same family as the chosen exit -- not just guards
7506 that are exactly the chosen exit. (Reported by lodger.)
7508 o Major bugfixes (resource management):
7509 - If a directory authority is down, skip it when deciding where to get
7510 networkstatus objects or descriptors. Otherwise we keep asking
7511 every 10 seconds forever. Fixes bug 384.
7512 - Count it as a failure if we fetch a valid network-status but we
7513 don't want to keep it. Otherwise we'll keep fetching it and keep
7514 not wanting to keep it. Fixes part of bug 422.
7515 - If all of our dirservers have given us bad or no networkstatuses
7516 lately, then stop hammering them once per minute even when we
7517 think they're failed. Fixes another part of bug 422.
7520 - Actually set the purpose correctly for descriptors inserted with
7522 - When we have k non-v2 authorities in our DirServer config,
7523 we ignored the last k authorities in the list when updating our
7525 - Correctly back-off from requesting router descriptors that we are
7526 having a hard time downloading.
7527 - Read resolv.conf files correctly on platforms where read() returns
7528 partial results on small file reads.
7529 - Don't rebuild the entire router store every time we get 32K of
7530 routers: rebuild it when the journal gets very large, or when
7531 the gaps in the store get very large.
7534 - When routers publish SVN revisions in their router descriptors,
7535 authorities now include those versions correctly in networkstatus
7537 - Warn when using a version of libevent before 1.3b to run a server on
7538 OSX or BSD: these versions interact badly with userspace threads.
7541 Changes in version 0.1.2.13 - 2007-04-24
7542 This release features some major anonymity fixes, such as safer path
7543 selection; better client performance; faster bootstrapping, better
7544 address detection, and better DNS support for servers; write limiting as
7545 well as read limiting to make servers easier to run; and a huge pile of
7546 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
7548 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
7549 of the Freenode IRC network, remembering his patience and vision for
7550 free speech on the Internet.
7552 o Major features, client performance:
7553 - Weight directory requests by advertised bandwidth. Now we can
7554 let servers enable write limiting but still allow most clients to
7555 succeed at their directory requests. (We still ignore weights when
7556 choosing a directory authority; I hope this is a feature.)
7557 - Stop overloading exit nodes -- avoid choosing them for entry or
7558 middle hops when the total bandwidth available from non-exit nodes
7559 is much higher than the total bandwidth available from exit nodes.
7560 - Rather than waiting a fixed amount of time between retrying
7561 application connections, we wait only 10 seconds for the first,
7562 10 seconds for the second, and 15 seconds for each retry after
7563 that. Hopefully this will improve the expected user experience.
7564 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
7565 to open a stream fails; now we do in more cases. This should
7566 make clients able to find a good exit faster in some cases, since
7567 unhandleable requests will now get an error rather than timing out.
7569 o Major features, client functionality:
7570 - Implement BEGIN_DIR cells, so we can connect to a directory
7571 server via TLS to do encrypted directory requests rather than
7572 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
7573 config options if you like. For now, this feature only works if
7574 you already have a descriptor for the destination dirserver.
7575 - Add support for transparent application connections: this basically
7576 bundles the functionality of trans-proxy-tor into the Tor
7577 mainline. Now hosts with compliant pf/netfilter implementations
7578 can redirect TCP connections straight to Tor without diverting
7579 through SOCKS. (Based on patch from tup.)
7580 - Add support for using natd; this allows FreeBSDs earlier than
7581 5.1.2 to have ipfw send connections through Tor without using
7582 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
7584 o Major features, servers:
7585 - Setting up a dyndns name for your server is now optional: servers
7586 with no hostname or IP address will learn their IP address by
7587 asking the directory authorities. This code only kicks in when you
7588 would normally have exited with a "no address" error. Nothing's
7589 authenticated, so use with care.
7590 - Directory servers now spool server descriptors, v1 directories,
7591 and v2 networkstatus objects to buffers as needed rather than en
7592 masse. They also mmap the cached-routers files. These steps save
7594 - Stop requiring clients to have well-formed certificates, and stop
7595 checking nicknames in certificates. (Clients have certificates so
7596 that they can look like Tor servers, but in the future we might want
7597 to allow them to look like regular TLS clients instead. Nicknames
7598 in certificates serve no purpose other than making our protocol
7599 easier to recognize on the wire.) Implements proposal 106.
7601 o Improvements on DNS support:
7602 - Add "eventdns" asynchronous dns library originally based on code
7603 from Adam Langley. Now we can discard the old rickety dnsworker
7604 concept, and support a wider variety of DNS functions. Allows
7605 multithreaded builds on NetBSD and OpenBSD again.
7606 - Add server-side support for "reverse" DNS lookups (using PTR
7607 records so clients can determine the canonical hostname for a given
7608 IPv4 address). Only supported by servers using eventdns; servers
7609 now announce in their descriptors if they don't support eventdns.
7610 - Workaround for name servers (like Earthlink's) that hijack failing
7611 DNS requests and replace the no-such-server answer with a "helpful"
7612 redirect to an advertising-driven search portal. Also work around
7613 DNS hijackers who "helpfully" decline to hijack known-invalid
7614 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
7615 lets you turn it off.
7616 - Servers now check for the case when common DNS requests are going to
7617 wildcarded addresses (i.e. all getting the same answer), and change
7618 their exit policy to reject *:* if it's happening.
7619 - When asked to resolve a hostname, don't use non-exit servers unless
7620 requested to do so. This allows servers with broken DNS to be
7621 useful to the network.
7622 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
7623 useless IPv6 DNS resolves.
7624 - Specify and implement client-side SOCKS5 interface for reverse DNS
7625 lookups (see doc/socks-extensions.txt). Also cache them.
7626 - When we change nameservers or IP addresses, reset and re-launch
7627 our tests for DNS hijacking.
7629 o Improvements on reachability testing:
7630 - Servers send out a burst of long-range padding cells once they've
7631 established that they're reachable. Spread them over 4 circuits,
7632 so hopefully a few will be fast. This exercises bandwidth and
7633 bootstraps them into the directory more quickly.
7634 - When we find our DirPort to be reachable, publish a new descriptor
7635 so we'll tell the world (reported by pnx).
7636 - Directory authorities now only decide that routers are reachable
7637 if their identity keys are as expected.
7638 - Do DirPort reachability tests less often, since a single test
7639 chews through many circuits before giving up.
7640 - Avoid some false positives during reachability testing: don't try
7641 to test via a server that's on the same /24 network as us.
7642 - Start publishing one minute or so after we find our ORPort
7643 to be reachable. This will help reduce the number of descriptors
7644 we have for ourselves floating around, since it's quite likely
7645 other things (e.g. DirPort) will change during that minute too.
7646 - Routers no longer try to rebuild long-term connections to directory
7647 authorities, and directory authorities no longer try to rebuild
7648 long-term connections to all servers. We still don't hang up
7649 connections in these two cases though -- we need to look at it
7650 more carefully to avoid flapping, and we likely need to wait til
7651 0.1.1.x is obsolete.
7653 o Improvements on rate limiting:
7654 - Enable write limiting as well as read limiting. Now we sacrifice
7655 capacity if we're pushing out lots of directory traffic, rather
7656 than overrunning the user's intended bandwidth limits.
7657 - Include TLS overhead when counting bandwidth usage; previously, we
7658 would count only the bytes sent over TLS, but not the bytes used
7660 - Servers decline directory requests much more aggressively when
7661 they're low on bandwidth. Otherwise they end up queueing more and
7662 more directory responses, which can't be good for latency.
7663 - But never refuse directory requests from local addresses.
7664 - Be willing to read or write on local connections (e.g. controller
7665 connections) even when the global rate limiting buckets are empty.
7666 - Flush local controller connection buffers periodically as we're
7667 writing to them, so we avoid queueing 4+ megabytes of data before
7669 - Revise and clean up the torrc.sample that we ship with; add
7670 a section for BandwidthRate and BandwidthBurst.
7672 o Major features, NT services:
7673 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
7674 command-line flag so that admins can override the default by saying
7675 "tor --service install --user "SomeUser"". This will not affect
7676 existing installed services. Also, warn the user that the service
7677 will look for its configuration file in the service user's
7678 %appdata% directory. (We can't do the "hardwire the user's appdata
7679 directory" trick any more, since we may not have read access to that
7681 - Support running the Tor service with a torrc not in the same
7682 directory as tor.exe and default to using the torrc located in
7683 the %appdata%\Tor\ of the user who installed the service. Patch
7685 - Add an --ignore-missing-torrc command-line option so that we can
7686 get the "use sensible defaults if the configuration file doesn't
7687 exist" behavior even when specifying a torrc location on the
7689 - When stopping an NT service, wait up to 10 sec for it to actually
7690 stop. (Patch from Matt Edman; resolves bug 295.)
7692 o Directory authority improvements:
7693 - Stop letting hibernating or obsolete servers affect uptime and
7695 - Stop listing hibernating servers in the v1 directory.
7696 - Authorities no longer recommend exits as guards if this would shift
7697 too much load to the exit nodes.
7698 - Authorities now specify server versions in networkstatus. This adds
7699 about 2% to the size of compressed networkstatus docs, and allows
7700 clients to tell which servers support BEGIN_DIR and which don't.
7701 The implementation is forward-compatible with a proposed future
7702 protocol version scheme not tied to Tor versions.
7703 - DirServer configuration lines now have an orport= option so
7704 clients can open encrypted tunnels to the authorities without
7705 having downloaded their descriptors yet. Enabled for moria1,
7706 moria2, tor26, and lefkada now in the default configuration.
7707 - Add a BadDirectory flag to network status docs so that authorities
7708 can (eventually) tell clients about caches they believe to be
7709 broken. Not used yet.
7710 - Allow authorities to list nodes as bad exits in their
7711 approved-routers file by fingerprint or by address. If most
7712 authorities set a BadExit flag for a server, clients don't think
7713 of it as a general-purpose exit. Clients only consider authorities
7714 that advertise themselves as listing bad exits.
7715 - Patch from Steve Hildrey: Generate network status correctly on
7716 non-versioning dirservers.
7717 - Have directory authorities allow larger amounts of drift in uptime
7718 without replacing the server descriptor: previously, a server that
7719 restarted every 30 minutes could have 48 "interesting" descriptors
7721 - Reserve the nickname "Unnamed" for routers that can't pick
7722 a hostname: any router can call itself Unnamed; directory
7723 authorities will never allocate Unnamed to any particular router;
7724 clients won't believe that any router is the canonical Unnamed.
7726 o Directory mirrors and clients:
7727 - Discard any v1 directory info that's over 1 month old (for
7728 directories) or over 1 week old (for running-routers lists).
7729 - Clients track responses with status 503 from dirservers. After a
7730 dirserver has given us a 503, we try not to use it until an hour has
7731 gone by, or until we have no dirservers that haven't given us a 503.
7732 - When we get a 503 from a directory, and we're not a server, we no
7733 longer count the failure against the total number of failures
7734 allowed for the object we're trying to download.
7735 - Prepare for servers to publish descriptors less often: never
7736 discard a descriptor simply for being too old until either it is
7737 recommended by no authorities, or until we get a better one for
7738 the same router. Make caches consider retaining old recommended
7739 routers for even longer.
7740 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
7741 headers for content, so that we can work better in the presence of
7742 caching HTTP proxies.
7743 - Stop fetching descriptors if you're not a dir mirror and you
7744 haven't tried to establish any circuits lately. (This currently
7745 causes some dangerous behavior, because when you start up again
7746 you'll use your ancient server descriptors.)
7748 o Major fixes, crashes:
7749 - Stop crashing when the controller asks us to resetconf more than
7750 one config option at once. (Vidalia 0.0.11 does this.)
7751 - Fix a longstanding obscure crash bug that could occur when we run
7752 out of DNS worker processes, if we're not using eventdns. (Resolves
7754 - Fix an assert that could trigger if a controller quickly set then
7755 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
7756 - Avoid crash when telling controller about stream-status and a
7758 - Avoid sending junk to controllers or segfaulting when a controller
7759 uses EVENT_NEW_DESC with verbose nicknames.
7760 - Stop triggering asserts if the controller tries to extend hidden
7761 service circuits (reported by mwenge).
7762 - If we start a server with ClientOnly 1, then set ClientOnly to 0
7763 and hup, stop triggering an assert based on an empty onion_key.
7764 - Mask out all signals in sub-threads; only the libevent signal
7765 handler should be processing them. This should prevent some crashes
7766 on some machines using pthreads. (Patch from coderman.)
7767 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
7769 o Major fixes, anonymity/security:
7770 - Automatically avoid picking more than one node from the same
7771 /16 network when constructing a circuit. Add an
7772 "EnforceDistinctSubnets" option to let people disable it if they
7773 want to operate private test networks on a single subnet.
7774 - When generating bandwidth history, round down to the nearest
7775 1k. When storing accounting data, round up to the nearest 1k.
7776 - When we're running as a server, remember when we last rotated onion
7777 keys, so that we will rotate keys once they're a week old even if
7778 we never stay up for a week ourselves.
7779 - If a client asked for a server by name, and there's a named server
7780 in our network-status but we don't have its descriptor yet, we
7781 could return an unnamed server instead.
7782 - Reject (most) attempts to use Tor circuits with length one. (If
7783 many people start using Tor as a one-hop proxy, exit nodes become
7784 a more attractive target for compromise.)
7785 - Just because your DirPort is open doesn't mean people should be
7786 able to remotely teach you about hidden service descriptors. Now
7787 only accept rendezvous posts if you've got HSAuthoritativeDir set.
7788 - Fix a potential race condition in the rpm installer. Found by
7790 - Do not log IPs with TLS failures for incoming TLS
7791 connections. (Fixes bug 382.)
7793 o Major fixes, other:
7794 - If our system clock jumps back in time, don't publish a negative
7795 uptime in the descriptor.
7796 - When we start during an accounting interval before it's time to wake
7797 up, remember to wake up at the correct time. (May fix bug 342.)
7798 - Previously, we would cache up to 16 old networkstatus documents
7799 indefinitely, if they came from nontrusted authorities. Now we
7800 discard them if they are more than 10 days old.
7801 - When we have a state file we cannot parse, tell the user and
7802 move it aside. Now we avoid situations where the user starts
7803 Tor in 1904, Tor writes a state file with that timestamp in it,
7804 the user fixes her clock, and Tor refuses to start.
7805 - Publish a new descriptor after we hup/reload. This is important
7806 if our config has changed such that we'll want to start advertising
7807 our DirPort now, etc.
7808 - If we are using an exit enclave and we can't connect, e.g. because
7809 its webserver is misconfigured to not listen on localhost, then
7810 back off and try connecting from somewhere else before we fail.
7812 o New config options or behaviors:
7813 - When EntryNodes are configured, rebuild the guard list to contain,
7814 in order: the EntryNodes that were guards before; the rest of the
7815 EntryNodes; the nodes that were guards before.
7816 - Do not warn when individual nodes in the configuration's EntryNodes,
7817 ExitNodes, etc are down: warn only when all possible nodes
7818 are down. (Fixes bug 348.)
7819 - Put a lower-bound on MaxAdvertisedBandwidth.
7820 - Start using the state file to store bandwidth accounting data:
7821 the bw_accounting file is now obsolete. We'll keep generating it
7822 for a while for people who are still using 0.1.2.4-alpha.
7823 - Try to batch changes to the state file so that we do as few
7824 disk writes as possible while still storing important things in
7826 - The state file and the bw_accounting file get saved less often when
7827 the AvoidDiskWrites config option is set.
7828 - Make PIDFile work on Windows.
7829 - Add internal descriptions for a bunch of configuration options:
7830 accessible via controller interface and in comments in saved
7832 - Reject *:563 (NNTPS) in the default exit policy. We already reject
7833 NNTP by default, so this seems like a sensible addition.
7834 - Clients now reject hostnames with invalid characters. This should
7835 avoid some inadvertent info leaks. Add an option
7836 AllowNonRFC953Hostnames to disable this behavior, in case somebody
7837 is running a private network with hosts called @, !, and #.
7838 - Check for addresses with invalid characters at the exit as well,
7839 and warn less verbosely when they fail. You can override this by
7840 setting ServerDNSAllowNonRFC953Addresses to 1.
7841 - Remove some options that have been deprecated since at least
7842 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
7843 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
7844 to set log options. Mark PathlenCoinWeight as obsolete.
7845 - Stop accepting certain malformed ports in configured exit policies.
7846 - When the user uses bad syntax in the Log config line, stop
7847 suggesting other bad syntax as a replacement.
7848 - Add new config option "ResolvConf" to let the server operator
7849 choose an alternate resolve.conf file when using eventdns.
7850 - If one of our entry guards is on the ExcludeNodes list, or the
7851 directory authorities don't think it's a good guard, treat it as
7852 if it were unlisted: stop using it as a guard, and throw it off
7853 the guards list if it stays that way for a long time.
7854 - Allow directory authorities to be marked separately as authorities
7855 for the v1 directory protocol, the v2 directory protocol, and
7856 as hidden service directories, to make it easier to retire old
7857 authorities. V1 authorities should set "HSAuthoritativeDir 1"
7858 to continue being hidden service authorities too.
7859 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
7860 - Make TrackExitHosts case-insensitive, and fix the behavior of
7861 ".suffix" TrackExitHosts items to avoid matching in the middle of
7863 - New DirPort behavior: if you have your dirport set, you download
7864 descriptors aggressively like a directory mirror, whether or not
7868 - Create a new file ReleaseNotes which was the old ChangeLog. The
7869 new ChangeLog file now includes the notes for all development
7871 - Add a new address-spec.txt document to describe our special-case
7872 addresses: .exit, .onion, and .noconnnect.
7873 - Fork the v1 directory protocol into its own spec document,
7874 and mark dir-spec.txt as the currently correct (v2) spec.
7876 o Packaging, porting, and contrib
7877 - "tor --verify-config" now exits with -1(255) or 0 depending on
7878 whether the config options are bad or good.
7879 - The Debian package now uses --verify-config when (re)starting,
7880 to distinguish configuration errors from other errors.
7881 - Adapt a patch from goodell to let the contrib/exitlist script
7882 take arguments rather than require direct editing.
7883 - Prevent the contrib/exitlist script from printing the same
7884 result more than once.
7885 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
7886 - In the hidden service example in torrc.sample, stop recommending
7887 esoteric and discouraged hidden service options.
7888 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
7889 values before failing, and always enables eventdns.
7890 - Try to detect Windows correctly when cross-compiling.
7891 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
7892 Try to fix this in configure.in by checking for most functions
7893 before we check for libevent.
7894 - Update RPMs to require libevent 1.2.
7895 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
7896 or later. Log when we are doing this, so we can diagnose it when
7897 it fails. (Also, recommend libevent 1.1b for kqueue and
7898 win32 methods; deprecate libevent 1.0b harder; make libevent
7899 recommendation system saner.)
7900 - Build with recent (1.3+) libevents on platforms that do not
7901 define the nonstandard types "u_int8_t" and friends.
7902 - Remove architecture from OS X builds. The official builds are
7903 now universal binaries.
7904 - Run correctly on OS X platforms with case-sensitive filesystems.
7905 - Correctly set maximum connection limit on Cygwin. (This time
7907 - Start compiling on MinGW on Windows (patches from Mike Chiussi
7909 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
7910 - Finally fix the openssl warnings from newer gccs that believe that
7911 ignoring a return value is okay, but casting a return value and
7912 then ignoring it is a sign of madness.
7913 - On architectures where sizeof(int)>4, still clamp declarable
7914 bandwidth to INT32_MAX.
7916 o Minor features, controller:
7917 - Warn the user when an application uses the obsolete binary v0
7918 control protocol. We're planning to remove support for it during
7919 the next development series, so it's good to give people some
7921 - Add STREAM_BW events to report per-entry-stream bandwidth
7922 use. (Patch from Robert Hogan.)
7923 - Rate-limit SIGNEWNYM signals in response to controllers that
7924 impolitely generate them for every single stream. (Patch from
7925 mwenge; closes bug 394.)
7926 - Add a REMAP status to stream events to note that a stream's
7927 address has changed because of a cached address or a MapAddress
7929 - Make REMAP stream events have a SOURCE (cache or exit), and
7930 make them generated in every case where we get a successful
7931 connected or resolved cell.
7932 - Track reasons for OR connection failure; make these reasons
7933 available via the controller interface. (Patch from Mike Perry.)
7934 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
7935 can learn when clients are sending malformed hostnames to Tor.
7936 - Specify and implement some of the controller status events.
7937 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
7938 - Reimplement GETINFO so that info/names stays in sync with the
7940 - Implement "GETINFO fingerprint".
7941 - Implement "SETEVENTS GUARD" so controllers can get updates on
7942 entry guard status as it changes.
7943 - Make all connections to addresses of the form ".noconnect"
7944 immediately get closed. This lets application/controller combos
7945 successfully test whether they're talking to the same Tor by
7946 watching for STREAM events.
7947 - Add a REASON field to CIRC events; for backward compatibility, this
7948 field is sent only to controllers that have enabled the extended
7949 event format. Also, add additional reason codes to explain why
7950 a given circuit has been destroyed or truncated. (Patches from
7952 - Add a REMOTE_REASON field to extended CIRC events to tell the
7953 controller why a remote OR told us to close a circuit.
7954 - Stream events also now have REASON and REMOTE_REASON fields,
7955 working much like those for circuit events.
7956 - There's now a GETINFO ns/... field so that controllers can ask Tor
7957 about the current status of a router.
7958 - A new event type "NS" to inform a controller when our opinion of
7959 a router's status has changed.
7960 - Add a GETINFO events/names and GETINFO features/names so controllers
7961 can tell which events and features are supported.
7962 - A new CLEARDNSCACHE signal to allow controllers to clear the
7963 client-side DNS cache without expiring circuits.
7964 - Fix CIRC controller events so that controllers can learn the
7965 identity digests of non-Named servers used in circuit paths.
7966 - Let controllers ask for more useful identifiers for servers. Instead
7967 of learning identity digests for un-Named servers and nicknames
7968 for Named servers, the new identifiers include digest, nickname,
7969 and indication of Named status. Off by default; see control-spec.txt
7970 for more information.
7971 - Add a "getinfo address" controller command so it can display Tor's
7972 best guess to the user.
7973 - New controller event to alert the controller when our server
7974 descriptor has changed.
7975 - Give more meaningful errors on controller authentication failure.
7976 - Export the default exit policy via the control port, so controllers
7977 don't need to guess what it is / will be later.
7979 o Minor bugfixes, controller:
7980 - When creating a circuit via the controller, send a 'launched'
7981 event when we're done, so we follow the spec better.
7982 - Correct the control spec to match how the code actually responds
7983 to 'getinfo addr-mappings/*'. Reported by daejees.
7984 - The control spec described a GUARDS event, but the code
7985 implemented a GUARD event. Standardize on GUARD, but let people
7986 ask for GUARDS too. Reported by daejees.
7987 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
7988 clear the corresponding on_circuit variable, and remember later
7989 that we don't need to send a redundant CLOSED event. (Resolves part
7991 - Report events where a resolve succeeded or where we got a socks
7992 protocol error correctly, rather than calling both of them
7994 - Change reported stream target addresses to IP consistently when
7995 we finally get the IP from an exit node.
7996 - Send log messages to the controller even if they happen to be very
7998 - Flush ERR-level controller status events just like we currently
7999 flush ERR-level log events, so that a Tor shutdown doesn't prevent
8000 the controller from learning about current events.
8001 - Report the circuit number correctly in STREAM CLOSED events. Bug
8002 reported by Mike Perry.
8003 - Do not report bizarre values for results of accounting GETINFOs
8004 when the last second's write or read exceeds the allotted bandwidth.
8005 - Report "unrecognized key" rather than an empty string when the
8006 controller tries to fetch a networkstatus that doesn't exist.
8007 - When the controller does a "GETINFO network-status", tell it
8008 about even those routers whose descriptors are very old, and use
8009 long nicknames where appropriate.
8010 - Fix handling of verbose nicknames with ORCONN controller events:
8011 make them show up exactly when requested, rather than exactly when
8013 - Controller signals now work on non-Unix platforms that don't define
8014 SIGUSR1 and SIGUSR2 the way we expect.
8015 - Respond to SIGNAL command before we execute the signal, in case
8016 the signal shuts us down. Suggested by Karsten Loesing.
8017 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
8019 o Minor features, code performance:
8020 - Major performance improvement on inserting descriptors: change
8021 algorithm from O(n^2) to O(n).
8022 - Do not rotate onion key immediately after setting it for the first
8024 - Call router_have_min_dir_info half as often. (This is showing up in
8025 some profiles, but not others.)
8026 - When using GCC, make log_debug never get called at all, and its
8027 arguments never get evaluated, when no debug logs are configured.
8028 (This is showing up in some profiles, but not others.)
8029 - Statistics dumped by -USR2 now include a breakdown of public key
8030 operations, for profiling.
8031 - Make the common memory allocation path faster on machines where
8032 malloc(0) returns a pointer.
8033 - Split circuit_t into origin_circuit_t and or_circuit_t, and
8034 split connection_t into edge, or, dir, control, and base structs.
8035 These will save quite a bit of memory on busy servers, and they'll
8036 also help us track down bugs in the code and bugs in the spec.
8037 - Use OpenSSL's AES implementation on platforms where it's faster.
8038 This could save us as much as 10% CPU usage.
8040 o Minor features, descriptors and descriptor handling:
8041 - Avoid duplicate entries on MyFamily line in server descriptor.
8042 - When Tor receives a router descriptor that it asked for, but
8043 no longer wants (because it has received fresh networkstatuses
8044 in the meantime), do not warn the user. Cache the descriptor if
8045 we're a cache; drop it if we aren't.
8046 - Servers no longer ever list themselves in their "family" line,
8047 even if configured to do so. This makes it easier to configure
8048 family lists conveniently.
8050 o Minor fixes, confusing/misleading log messages:
8051 - Display correct results when reporting which versions are
8052 recommended, and how recommended they are. (Resolves bug 383.)
8053 - Inform the server operator when we decide not to advertise a
8054 DirPort due to AccountingMax enabled or a low BandwidthRate.
8055 - Only include function names in log messages for info/debug messages.
8056 For notice/warn/err, the content of the message should be clear on
8057 its own, and printing the function name only confuses users.
8058 - Remove even more protocol-related warnings from Tor server logs,
8059 such as bad TLS handshakes and malformed begin cells.
8060 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
8061 when the IP address is mapped through MapAddress to a hostname.
8062 - Fix misleading log messages: an entry guard that is "unlisted",
8063 as well as not known to be "down" (because we've never heard
8064 of it), is not therefore "up".
8066 o Minor fixes, old/obsolete behavior:
8067 - Start assuming we can use a create_fast cell if we don't know
8068 what version a router is running.
8069 - We no longer look for identity and onion keys in "identity.key" and
8070 "onion.key" -- these were replaced by secret_id_key and
8071 secret_onion_key in 0.0.8pre1.
8072 - We no longer require unrecognized directory entries to be
8074 - Drop compatibility with obsolete Tors that permit create cells
8075 to have the wrong circ_id_type.
8076 - Remove code to special-case "-cvs" ending, since it has not
8077 actually mattered since 0.0.9.
8078 - Don't re-write the fingerprint file every restart, unless it has
8081 o Minor fixes, misc client-side behavior:
8082 - Always remove expired routers and networkstatus docs before checking
8083 whether we have enough information to build circuits. (Fixes
8085 - When computing clock skew from directory HTTP headers, consider what
8086 time it was when we finished asking for the directory, not what
8088 - Make our socks5 handling more robust to broken socks clients:
8089 throw out everything waiting on the buffer in between socks
8090 handshake phases, since they can't possibly (so the theory
8091 goes) have predicted what we plan to respond to them.
8092 - Expire socks connections if they spend too long waiting for the
8093 handshake to finish. Previously we would let them sit around for
8094 days, if the connecting application didn't close them either.
8095 - And if the socks handshake hasn't started, don't send a
8096 "DNS resolve socks failed" handshake reply; just close it.
8097 - If the user asks to use invalid exit nodes, be willing to use
8099 - Track unreachable entry guards correctly: don't conflate
8100 'unreachable by us right now' with 'listed as down by the directory
8101 authorities'. With the old code, if a guard was unreachable by us
8102 but listed as running, it would clog our guard list forever.
8103 - Behave correctly in case we ever have a network with more than
8104 2GB/s total advertised capacity.
8105 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
8106 - Fix a memory leak when we ask for "all" networkstatuses and we
8107 get one we don't recognize.
8110 Changes in version 0.1.1.26 - 2006-12-14
8111 o Security bugfixes:
8112 - Stop sending the HttpProxyAuthenticator string to directory
8113 servers when directory connections are tunnelled through Tor.
8114 - Clients no longer store bandwidth history in the state file.
8115 - Do not log introduction points for hidden services if SafeLogging
8119 - Fix an assert failure when a directory authority sets
8120 AuthDirRejectUnlisted and then receives a descriptor from an
8121 unlisted router (reported by seeess).
8124 Changes in version 0.1.1.25 - 2006-11-04
8126 - When a client asks us to resolve (rather than connect to)
8127 an address, and we have a cached answer, give them the cached
8128 answer. Previously, we would give them no answer at all.
8129 - We were building exactly the wrong circuits when we predict
8130 hidden service requirements, meaning Tor would have to build all
8131 its circuits on demand.
8132 - If none of our live entry guards have a high uptime, but we
8133 require a guard with a high uptime, try adding a new guard before
8134 we give up on the requirement. This patch should make long-lived
8135 connections more stable on average.
8136 - When testing reachability of our DirPort, don't launch new
8137 tests when there's already one in progress -- unreachable
8138 servers were stacking up dozens of testing streams.
8140 o Security bugfixes:
8141 - When the user sends a NEWNYM signal, clear the client-side DNS
8142 cache too. Otherwise we continue to act on previous information.
8145 - Avoid a memory corruption bug when creating a hash table for
8147 - Avoid possibility of controller-triggered crash when misusing
8148 certain commands from a v0 controller on platforms that do not
8149 handle printf("%s",NULL) gracefully.
8150 - Avoid infinite loop on unexpected controller input.
8151 - Don't log spurious warnings when we see a circuit close reason we
8152 don't recognize; it's probably just from a newer version of Tor.
8153 - Add Vidalia to the OS X uninstaller script, so when we uninstall
8154 Tor/Privoxy we also uninstall Vidalia.
8157 Changes in version 0.1.1.24 - 2006-09-29
8159 - Allow really slow clients to not hang up five minutes into their
8160 directory downloads (suggested by Adam J. Richter).
8161 - Fix major performance regression from 0.1.0.x: instead of checking
8162 whether we have enough directory information every time we want to
8163 do something, only check when the directory information has changed.
8164 This should improve client CPU usage by 25-50%.
8165 - Don't crash if, after a server has been running for a while,
8166 it can't resolve its hostname.
8167 - When a client asks us to resolve (not connect to) an address,
8168 and we have a cached answer, give them the cached answer.
8169 Previously, we would give them no answer at all.
8172 - Allow Tor to start when RunAsDaemon is set but no logs are set.
8173 - Don't crash when the controller receives a third argument to an
8174 "extendcircuit" request.
8175 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
8176 response; fix error code when "getinfo dir/status/" fails.
8177 - Fix configure.in to not produce broken configure files with
8178 more recent versions of autoconf. Thanks to Clint for his auto*
8180 - Fix security bug on NetBSD that could allow someone to force
8181 uninitialized RAM to be sent to a server's DNS resolver. This
8182 only affects NetBSD and other platforms that do not bounds-check
8184 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
8185 methods: these are known to be buggy.
8186 - If we're a directory mirror and we ask for "all" network status
8187 documents, we would discard status documents from authorities
8191 Changes in version 0.1.1.23 - 2006-07-30
8193 - Fast Tor servers, especially exit nodes, were triggering asserts
8194 due to a bug in handling the list of pending DNS resolves. Some
8195 bugs still remain here; we're hunting them.
8196 - Entry guards could crash clients by sending unexpected input.
8197 - More fixes on reachability testing: if you find yourself reachable,
8198 then don't ever make any client requests (so you stop predicting
8199 circuits), then hup or have your clock jump, then later your IP
8200 changes, you won't think circuits are working, so you won't try to
8201 test reachability, so you won't publish.
8204 - Avoid a crash if the controller does a resetconf firewallports
8205 and then a setconf fascistfirewall=1.
8206 - Avoid an integer underflow when the dir authority decides whether
8207 a router is stable: we might wrongly label it stable, and compute
8208 a slightly wrong median stability, when a descriptor is published
8210 - Fix a place where we might trigger an assert if we can't build our
8211 own server descriptor yet.
8214 Changes in version 0.1.1.22 - 2006-07-05
8216 - Fix a big bug that was causing servers to not find themselves
8217 reachable if they changed IP addresses. Since only 0.1.1.22+
8218 servers can do reachability testing correctly, now we automatically
8219 make sure to test via one of these.
8220 - Fix to allow clients and mirrors to learn directory info from
8221 descriptor downloads that get cut off partway through.
8222 - Directory authorities had a bug in deciding if a newly published
8223 descriptor was novel enough to make everybody want a copy -- a few
8224 servers seem to be publishing new descriptors many times a minute.
8226 - Fix a rare bug that was causing some servers to complain about
8227 "closing wedged cpuworkers" and skip some circuit create requests.
8228 - Make the Exit flag in directory status documents actually work.
8231 Changes in version 0.1.1.21 - 2006-06-10
8232 o Crash and assert fixes from 0.1.1.20:
8233 - Fix a rare crash on Tor servers that have enabled hibernation.
8234 - Fix a seg fault on startup for Tor networks that use only one
8235 directory authority.
8236 - Fix an assert from a race condition that occurs on Tor servers
8237 while exiting, where various threads are trying to log that they're
8238 exiting, and delete the logs, at the same time.
8239 - Make our unit tests pass again on certain obscure platforms.
8242 - Add support for building SUSE RPM packages.
8243 - Speed up initial bootstrapping for clients: if we are making our
8244 first ever connection to any entry guard, then don't mark it down
8246 - When only one Tor server in the network is labelled as a guard,
8247 and we've already picked him, we would cycle endlessly picking him
8248 again, being unhappy about it, etc. Now we specifically exclude
8249 current guards when picking a new guard.
8250 - Servers send create cells more reliably after the TLS connection
8251 is established: we were sometimes forgetting to send half of them
8252 when we had more than one pending.
8253 - If we get a create cell that asks us to extend somewhere, but the
8254 Tor server there doesn't match the expected digest, we now send
8255 a destroy cell back, rather than silently doing nothing.
8256 - Make options->RedirectExit work again.
8257 - Make cookie authentication for the controller work again.
8258 - Stop being picky about unusual characters in the arguments to
8259 mapaddress. It's none of our business.
8260 - Add a new config option "TestVia" that lets you specify preferred
8261 middle hops to use for test circuits. Perhaps this will let me
8262 debug the reachability problems better.
8264 o Log / documentation fixes:
8265 - If we're a server and some peer has a broken TLS certificate, don't
8266 log about it unless ProtocolWarnings is set, i.e., we want to hear
8267 about protocol violations by others.
8268 - Fix spelling of VirtualAddrNetwork in man page.
8269 - Add a better explanation at the top of the autogenerated torrc file
8270 about what happened to our old torrc.
8273 Changes in version 0.1.1.20 - 2006-05-23
8274 o Crash and assert fixes from 0.1.0.17:
8275 - Fix assert bug in close_logs() on exit: when we close and delete
8276 logs, remove them all from the global "logfiles" list.
8277 - Fix an assert error when we're out of space in the connection_list
8278 and we try to post a hidden service descriptor (reported by Peter
8280 - Fix a rare assert error when we've tried all intro points for
8281 a hidden service and we try fetching the service descriptor again:
8282 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
8283 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
8284 out and refuse the setconf if it would fail.
8285 - If you specify a relative torrc path and you set RunAsDaemon in
8286 your torrc, then it chdir()'s to the new directory. If you then
8287 HUP, it tries to load the new torrc location, fails, and exits.
8288 The fix: no longer allow a relative path to torrc when using -f.
8289 - Check for integer overflows in more places, when adding elements
8290 to smartlists. This could possibly prevent a buffer overflow
8291 on malicious huge inputs.
8293 o Security fixes, major:
8294 - When we're printing strings from the network, don't try to print
8295 non-printable characters. Now we're safer against shell escape
8296 sequence exploits, and also against attacks to fool users into
8297 misreading their logs.
8298 - Implement entry guards: automatically choose a handful of entry
8299 nodes and stick with them for all circuits. Only pick new guards
8300 when the ones you have are unsuitable, and if the old guards
8301 become suitable again, switch back. This will increase security
8302 dramatically against certain end-point attacks. The EntryNodes
8303 config option now provides some hints about which entry guards you
8304 want to use most; and StrictEntryNodes means to only use those.
8305 Fixes CVE-2006-0414.
8306 - Implement exit enclaves: if we know an IP address for the
8307 destination, and there's a running Tor server at that address
8308 which allows exit to the destination, then extend the circuit to
8309 that exit first. This provides end-to-end encryption and end-to-end
8310 authentication. Also, if the user wants a .exit address or enclave,
8311 use 4 hops rather than 3, and cannibalize a general circ for it
8313 - Obey our firewall options more faithfully:
8314 . If we can't get to a dirserver directly, try going via Tor.
8315 . Don't ever try to connect (as a client) to a place our
8316 firewall options forbid.
8317 . If we specify a proxy and also firewall options, obey the
8318 firewall options even when we're using the proxy: some proxies
8319 can only proxy to certain destinations.
8320 - Make clients regenerate their keys when their IP address changes.
8321 - For the OS X package's modified privoxy config file, comment
8322 out the "logfile" line so we don't log everything passed
8324 - Our TLS handshakes were generating a single public/private
8325 keypair for the TLS context, rather than making a new one for
8326 each new connection. Oops. (But we were still rotating them
8327 periodically, so it's not so bad.)
8328 - When we were cannibalizing a circuit with a particular exit
8329 node in mind, we weren't checking to see if that exit node was
8330 already present earlier in the circuit. Now we are.
8331 - Require server descriptors to list IPv4 addresses -- hostnames
8332 are no longer allowed. This also fixes potential vulnerabilities
8333 to servers providing hostnames as their address and then
8334 preferentially resolving them so they can partition users.
8335 - Our logic to decide if the OR we connected to was the right guy
8336 was brittle and maybe open to a mitm for invalid routers.
8338 o Security fixes, minor:
8339 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
8340 Ian Goldberg can prove things about our handshake protocol more
8342 - Make directory authorities generate a separate "guard" flag to
8343 mean "would make a good entry guard". Clients now honor the
8344 is_guard flag rather than looking at is_fast or is_stable.
8345 - Try to list MyFamily elements by key, not by nickname, and warn
8346 if we've not heard of a server.
8347 - Start using RAND_bytes rather than RAND_pseudo_bytes from
8348 OpenSSL. Also, reseed our entropy every hour, not just at
8349 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
8350 - Refuse server descriptors where the fingerprint line doesn't match
8351 the included identity key. Tor doesn't care, but other apps (and
8352 humans) might actually be trusting the fingerprint line.
8353 - We used to kill the circuit when we receive a relay command we
8354 don't recognize. Now we just drop that cell.
8355 - Fix a bug found by Lasse Overlier: when we were making internal
8356 circuits (intended to be cannibalized later for rendezvous and
8357 introduction circuits), we were picking them so that they had
8358 useful exit nodes. There was no need for this, and it actually
8359 aids some statistical attacks.
8360 - Start treating internal circuits and exit circuits separately.
8361 It's important to keep them separate because internal circuits
8362 have their last hops picked like middle hops, rather than like
8363 exit hops. So exiting on them will break the user's expectations.
8364 - Fix a possible way to DoS dirservers.
8365 - When the client asked for a rendezvous port that the hidden
8366 service didn't want to provide, we were sending an IP address
8367 back along with the end cell. Fortunately, it was zero. But stop
8370 o Packaging improvements:
8371 - Implement --with-libevent-dir option to ./configure. Improve
8372 search techniques to find libevent, and use those for openssl too.
8373 - Fix a couple of bugs in OpenSSL detection. Deal better when
8374 there are multiple SSLs installed with different versions.
8375 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
8376 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
8378 - Make unit tests (and other invocations that aren't the real Tor)
8379 run without launching listeners, creating subdirectories, and so on.
8380 - The OS X installer was adding a symlink for tor_resolve but
8381 the binary was called tor-resolve (reported by Thomas Hardly).
8382 - Now we can target arch and OS in rpm builds (contributed by
8383 Phobos). Also make the resulting dist-rpm filename match the
8385 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
8386 if you log to syslog and want something other than LOG_DAEMON.
8387 - Fix the torify (tsocks) config file to not use Tor for localhost
8389 - Start shipping socks-extensions.txt, tor-doc-unix.html,
8390 tor-doc-server.html, and stylesheet.css in the tarball.
8391 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
8392 They are useless now.
8393 - Add Peter Palfrader's contributed check-tor script. It lets you
8394 easily check whether a given server (referenced by nickname)
8395 is reachable by you.
8396 - Add BSD-style contributed startup script "rc.subr" from Peter
8399 o Directory improvements -- new directory protocol:
8400 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
8401 - Authorities and caches publish individual descriptors (by
8402 digest, by fingerprint, by "all", and by "tell me yours").
8403 - Clients don't download or use the old directory anymore. Now they
8404 download network-statuses from the directory authorities, and
8405 fetch individual server descriptors as needed from mirrors.
8406 - Clients don't download descriptors of non-running servers.
8407 - Download descriptors by digest, not by fingerprint. Caches try to
8408 download all listed digests from authorities; clients try to
8409 download "best" digests from caches. This avoids partitioning
8410 and isolating attacks better.
8411 - Only upload a new server descriptor when options change, 18
8412 hours have passed, uptime is reset, or bandwidth changes a lot.
8413 - Directory authorities silently throw away new descriptors that
8414 haven't changed much if the timestamps are similar. We do this to
8415 tolerate older Tor servers that upload a new descriptor every 15
8416 minutes. (It seemed like a good idea at the time.)
8417 - Clients choose directory servers from the network status lists,
8418 not from their internal list of router descriptors. Now they can
8419 go to caches directly rather than needing to go to authorities
8420 to bootstrap the first set of descriptors.
8421 - When picking a random directory, prefer non-authorities if any
8423 - Add a new flag to network-status indicating whether the server
8424 can answer v2 directory requests too.
8425 - Directory mirrors now cache up to 16 unrecognized network-status
8426 docs, so new directory authorities will be cached too.
8427 - Stop parsing, storing, or using running-routers output (but
8428 mirrors still cache and serve it).
8429 - Clients consider a threshold of "versioning" directory authorities
8430 before deciding whether to warn the user that he's obsolete.
8431 - Authorities publish separate sorted lists of recommended versions
8432 for clients and for servers.
8433 - Change DirServers config line to note which dirs are v1 authorities.
8434 - Put nicknames on the DirServer line, so we can refer to them
8435 without requiring all our users to memorize their IP addresses.
8436 - Remove option when getting directory cache to see whether they
8437 support running-routers; they all do now. Replace it with one
8438 to see whether caches support v2 stuff.
8439 - Stop listing down or invalid nodes in the v1 directory. This
8440 reduces its bulk by about 1/3, and reduces load on mirrors.
8441 - Mirrors no longer cache the v1 directory as often.
8442 - If we as a directory mirror don't know of any v1 directory
8443 authorities, then don't try to cache any v1 directories.
8445 o Other directory improvements:
8446 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
8447 fifth authoritative directory servers.
8448 - Directory authorities no longer require an open connection from
8449 a server to consider him "reachable". We need this change because
8450 when we add new directory authorities, old servers won't know not
8452 - Dir authorities now do their own external reachability testing
8453 of each server, and only list as running the ones they found to
8454 be reachable. We also send back warnings to the server's logs if
8455 it uploads a descriptor that we already believe is unreachable.
8456 - Spread the directory authorities' reachability testing over the
8457 entire testing interval, so we don't try to do 500 TLS's at once
8459 - Make the "stable" router flag in network-status be the median of
8460 the uptimes of running valid servers, and make clients pay
8461 attention to the network-status flags. Thus the cutoff adapts
8462 to the stability of the network as a whole, making IRC, IM, etc
8463 connections more reliable.
8464 - Make the v2 dir's "Fast" flag based on relative capacity, just
8465 like "Stable" is based on median uptime. Name everything in the
8466 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
8467 - Retry directory requests if we fail to get an answer we like
8468 from a given dirserver (we were retrying before, but only if
8469 we fail to connect).
8470 - Return a robots.txt on our dirport to discourage google indexing.
8472 o Controller protocol improvements:
8473 - Revised controller protocol (version 1) that uses ascii rather
8474 than binary: tor/doc/control-spec.txt. Add supporting libraries
8475 in python and java and c# so you can use the controller from your
8476 applications without caring how our protocol works.
8477 - Allow the DEBUG controller event to work again. Mark certain log
8478 entries as "don't tell this to controllers", so we avoid cycles.
8479 - New controller function "getinfo accounting", to ask how
8480 many bytes we've used in this time period.
8481 - Add a "resetconf" command so you can set config options like
8482 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
8483 a config option in the torrc with no value, then it clears it
8484 entirely (rather than setting it to its default).
8485 - Add a "getinfo config-file" to tell us where torrc is. Also
8486 expose guard nodes, config options/names.
8487 - Add a "quit" command (when when using the controller manually).
8488 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
8489 stop using any currently-dirty circuits for new streams, so we
8490 don't link new actions to old actions. This also occurs on HUP
8492 - If we would close a stream early (e.g. it asks for a .exit that
8493 we know would refuse it) but the LeaveStreamsUnattached config
8494 option is set by the controller, then don't close it.
8495 - Add a new controller event type "authdir_newdescs" that allows
8496 controllers to get all server descriptors that were uploaded to
8497 a router in its role as directory authority.
8498 - New controller option "getinfo desc/all-recent" to fetch the
8499 latest server descriptor for every router that Tor knows about.
8500 - Fix the controller's "attachstream 0" command to treat conn like
8501 it just connected, doing address remapping, handling .exit and
8502 .onion idioms, and so on. Now we're more uniform in making sure
8503 that the controller hears about new and closing connections.
8504 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
8505 the controller. Also, rotate dns and cpu workers if the controller
8506 changes options that will affect them; and initialize the dns
8507 worker cache tree whether or not we start out as a server.
8508 - Add a new circuit purpose 'controller' to let the controller ask
8509 for a circuit that Tor won't try to use. Extend the "extendcircuit"
8510 controller command to let you specify the purpose if you're starting
8511 a new circuit. Add a new "setcircuitpurpose" controller command to
8512 let you change a circuit's purpose after it's been created.
8513 - Let the controller ask for "getinfo dir/server/foo" so it can ask
8514 directly rather than connecting to the dir port. "getinfo
8515 dir/status/foo" also works, but currently only if your DirPort
8517 - Let the controller tell us about certain router descriptors
8518 that it doesn't want Tor to use in circuits. Implement
8519 "setrouterpurpose" and modify "+postdescriptor" to do this.
8520 - If the controller's *setconf commands fail, collect an error
8521 message in a string and hand it back to the controller -- don't
8522 just tell them to go read their logs.
8524 o Scalability, resource management, and performance:
8525 - Fix a major load balance bug: we were round-robin reading in 16 KB
8526 chunks, and servers with bandwidthrate of 20 KB, while downloading
8527 a 600 KB directory, would starve their other connections. Now we
8528 try to be a bit more fair.
8529 - Be more conservative about whether to advertise our DirPort.
8530 The main change is to not advertise if we're running at capacity
8531 and either a) we could hibernate ever or b) our capacity is low
8532 and we're using a default DirPort.
8533 - We weren't cannibalizing circuits correctly for
8534 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
8535 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
8536 build those from scratch. This should make hidden services faster.
8537 - Predict required circuits better, with an eye toward making hidden
8538 services faster on the service end.
8539 - Compress exit policies even more: look for duplicate lines and
8541 - Generate 18.0.0.0/8 address policy format in descs when we can;
8542 warn when the mask is not reducible to a bit-prefix.
8543 - There used to be two ways to specify your listening ports in a
8544 server descriptor: on the "router" line and with a separate "ports"
8545 line. Remove support for the "ports" line.
8546 - Reduce memory requirements in our structs by changing the order
8547 of fields. Replace balanced trees with hash tables. Inline
8548 bottleneck smartlist functions. Add a "Map from digest to void*"
8549 abstraction so we can do less hex encoding/decoding, and use it
8550 in router_get_by_digest(). Many other CPU and memory improvements.
8551 - Allow tor_gzip_uncompress to extract as much as possible from
8552 truncated compressed data. Try to extract as many
8553 descriptors as possible from truncated http responses (when
8554 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
8555 - Make circ->onionskin a pointer, not a static array. moria2 was using
8556 125000 circuit_t's after it had been up for a few weeks, which
8557 translates to 20+ megs of wasted space.
8558 - The private half of our EDH handshake keys are now chosen out
8559 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
8560 - Stop doing the complex voodoo overkill checking for insecure
8561 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
8562 - Do round-robin writes for TLS of at most 16 kB per write. This
8563 might be more fair on loaded Tor servers.
8564 - Do not use unaligned memory access on alpha, mips, or mipsel.
8565 It *works*, but is very slow, so we treat them as if it doesn't.
8567 o Other bugfixes and improvements:
8568 - Start storing useful information to $DATADIR/state, so we can
8569 remember things across invocations of Tor. Retain unrecognized
8570 lines so we can be forward-compatible, and write a TorVersion line
8571 so we can be backward-compatible.
8572 - If ORPort is set, Address is not explicitly set, and our hostname
8573 resolves to a private IP address, try to use an interface address
8574 if it has a public address. Now Windows machines that think of
8575 themselves as localhost can guess their address.
8576 - Regenerate our local descriptor if it's dirty and we try to use
8577 it locally (e.g. if it changes during reachability detection).
8578 This was causing some Tor servers to keep publishing the same
8579 initial descriptor forever.
8580 - Tor servers with dynamic IP addresses were needing to wait 18
8581 hours before they could start doing reachability testing using
8582 the new IP address and ports. This is because they were using
8583 the internal descriptor to learn what to test, yet they were only
8584 rebuilding the descriptor once they decided they were reachable.
8585 - It turns out we couldn't bootstrap a network since we added
8586 reachability detection in 0.1.0.1-rc. Good thing the Tor network
8587 has never gone down. Add an AssumeReachable config option to let
8588 servers and authorities bootstrap. When we're trying to build a
8589 high-uptime or high-bandwidth circuit but there aren't enough
8590 suitable servers, try being less picky rather than simply failing.
8591 - Newly bootstrapped Tor networks couldn't establish hidden service
8592 circuits until they had nodes with high uptime. Be more tolerant.
8593 - Really busy servers were keeping enough circuits open on stable
8594 connections that they were wrapping around the circuit_id
8595 space. (It's only two bytes.) This exposed a bug where we would
8596 feel free to reuse a circuit_id even if it still exists but has
8597 been marked for close. Try to fix this bug. Some bug remains.
8598 - When we fail to bind or listen on an incoming or outgoing
8599 socket, we now close it before refusing, rather than just
8600 leaking it. (Thanks to Peter Palfrader for finding.)
8601 - Fix a file descriptor leak in start_daemon().
8602 - On Windows, you can't always reopen a port right after you've
8603 closed it. So change retry_listeners() to only close and re-open
8604 ports that have changed.
8605 - Workaround a problem with some http proxies that refuse GET
8606 requests that specify "Content-Length: 0". Reported by Adrian.
8607 - Recover better from TCP connections to Tor servers that are
8608 broken but don't tell you (it happens!); and rotate TLS
8609 connections once a week.
8610 - Fix a scary-looking but apparently harmless bug where circuits
8611 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
8612 servers, and never switch to state CIRCUIT_STATE_OPEN.
8613 - Check for even more Windows version flags when writing the platform
8614 string in server descriptors, and note any we don't recognize.
8615 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
8616 get a better idea of why their circuits failed. Not used yet.
8617 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
8618 We don't use them yet, but maybe one day our DNS resolver will be
8619 able to discover them.
8620 - Let people type "tor --install" as well as "tor -install" when they
8621 want to make it an NT service.
8622 - Looks like we were never delivering deflated (i.e. compressed)
8623 running-routers lists, even when asked. Oops.
8624 - We were leaking some memory every time the client changed IPs.
8625 - Clean up more of the OpenSSL memory when exiting, so we can detect
8626 memory leaks better.
8627 - Never call free() on tor_malloc()d memory. This will help us
8628 use dmalloc to detect memory leaks.
8629 - Some Tor servers process billions of cells per day. These
8630 statistics are now uint64_t's.
8631 - Check [X-]Forwarded-For headers in HTTP requests when generating
8632 log messages. This lets people run dirservers (and caches) behind
8633 Apache but still know which IP addresses are causing warnings.
8634 - Fix minor integer overflow in calculating when we expect to use up
8635 our bandwidth allocation before hibernating.
8636 - Lower the minimum required number of file descriptors to 1000,
8637 so we can have some overhead for Valgrind on Linux, where the
8638 default ulimit -n is 1024.
8639 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
8640 and its existence is confusing some users.
8642 o Config option fixes:
8643 - Add a new config option ExitPolicyRejectPrivate which defaults
8644 to on. Now all exit policies will begin with rejecting private
8645 addresses, unless the server operator explicitly turns it off.
8646 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
8647 - Add new ReachableORAddresses and ReachableDirAddresses options
8648 that understand address policies. FascistFirewall is now a synonym
8649 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
8650 - Start calling it FooListenAddress rather than FooBindAddress,
8651 since few of our users know what it means to bind an address
8653 - If the user gave Tor an odd number of command-line arguments,
8654 we were silently ignoring the last one. Now we complain and fail.
8655 This wins the oldest-bug prize -- this bug has been present since
8656 November 2002, as released in Tor 0.0.0.
8657 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
8658 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
8659 it would silently ignore the 6668.
8660 - If we get a linelist or linelist_s config option from the torrc,
8661 e.g. ExitPolicy, and it has no value, warn and skip rather than
8662 silently resetting it to its default.
8663 - Setconf was appending items to linelists, not clearing them.
8664 - Add MyFamily to torrc.sample in the server section, so operators
8665 will be more likely to learn that it exists.
8666 - Make ContactInfo mandatory for authoritative directory servers.
8667 - MaxConn has been obsolete for a while now. Document the ConnLimit
8668 config option, which is a *minimum* number of file descriptors
8669 that must be available else Tor refuses to start.
8670 - Get rid of IgnoreVersion undocumented config option, and make us
8671 only warn, never exit, when we're running an obsolete version.
8672 - Make MonthlyAccountingStart config option truly obsolete now.
8673 - Correct the man page entry on TrackHostExitsExpire.
8674 - Let directory authorities start even if they don't specify an
8675 Address config option.
8676 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
8677 reflect the updated flags in our v2 dir protocol.
8679 o Config option features:
8680 - Add a new config option FastFirstHopPK (on by default) so clients
8681 do a trivial crypto handshake for their first hop, since TLS has
8682 already taken care of confidentiality and authentication.
8683 - Let the user set ControlListenAddress in the torrc. This can be
8684 dangerous, but there are some cases (like a secured LAN) where it
8686 - New config options to help controllers: FetchServerDescriptors
8687 and FetchHidServDescriptors for whether to fetch server
8688 info and hidserv info or let the controller do it, and
8689 PublishServerDescriptor and PublishHidServDescriptors.
8690 - Also let the controller set the __AllDirActionsPrivate config
8691 option if you want all directory fetches/publishes to happen via
8692 Tor (it assumes your controller bootstraps your circuits).
8693 - Add "HardwareAccel" config option: support for crypto hardware
8694 accelerators via OpenSSL. Off by default, until we find somebody
8695 smart who can test it for us. (It appears to produce seg faults
8696 in at least some cases.)
8697 - New config option "AuthDirRejectUnlisted" for directory authorities
8698 as a panic button: if we get flooded with unusable servers we can
8699 revert to only listing servers in the approved-routers file.
8700 - Directory authorities can now reject/invalidate by key and IP,
8701 with the config options "AuthDirInvalid" and "AuthDirReject", or
8702 by marking a fingerprint as "!reject" or "!invalid" (as its
8703 nickname) in the approved-routers file. This is useful since
8704 currently we automatically list servers as running and usable
8705 even if we know they're jerks.
8706 - Add a new config option TestSocks so people can see whether their
8707 applications are using socks4, socks4a, socks5-with-ip, or
8708 socks5-with-fqdn. This way they don't have to keep mucking
8709 with tcpdump and wondering if something got cached somewhere.
8710 - Add "private:*" as an alias in configuration for policies. Now
8711 you can simplify your exit policy rather than needing to list
8712 every single internal or nonroutable network space.
8713 - Accept "private:*" in routerdesc exit policies; not generated yet
8714 because older Tors do not understand it.
8715 - Add configuration option "V1AuthoritativeDirectory 1" which
8716 moria1, moria2, and tor26 have set.
8717 - Implement an option, VirtualAddrMask, to set which addresses
8718 get handed out in response to mapaddress requests. This works
8719 around a bug in tsocks where 127.0.0.0/8 is never socksified.
8720 - Add a new config option FetchUselessDescriptors, off by default,
8721 for when you plan to run "exitlist" on your client and you want
8722 to know about even the non-running descriptors.
8723 - SocksTimeout: How long do we let a socks connection wait
8724 unattached before we fail it?
8725 - CircuitBuildTimeout: Cull non-open circuits that were born
8726 at least this many seconds ago.
8727 - CircuitIdleTimeout: Cull open clean circuits that were born
8728 at least this many seconds ago.
8729 - New config option SafeSocks to reject all application connections
8730 using unsafe socks protocols. Defaults to off.
8732 o Improved and clearer log messages:
8733 - Reduce clutter in server logs. We're going to try to make
8734 them actually usable now. New config option ProtocolWarnings that
8735 lets you hear about how _other Tors_ are breaking the protocol. Off
8737 - Divide log messages into logging domains. Once we put some sort
8738 of interface on this, it will let people looking at more verbose
8739 log levels specify the topics they want to hear more about.
8740 - Log server fingerprint on startup, so new server operators don't
8741 have to go hunting around their filesystem for it.
8742 - Provide dire warnings to any users who set DirServer manually;
8743 move it out of torrc.sample and into torrc.complete.
8744 - Make the log message less scary when all the dirservers are
8745 temporarily unreachable.
8746 - When tor_socketpair() fails in Windows, give a reasonable
8747 Windows-style errno back.
8748 - Improve tor_gettimeofday() granularity on windows.
8749 - We were printing the number of idle dns workers incorrectly when
8751 - Handle duplicate lines in approved-routers files without warning.
8752 - We were whining about using socks4 or socks5-with-local-lookup
8753 even when it's an IP address in the "virtual" range we designed
8754 exactly for this case.
8755 - Check for named servers when looking them up by nickname;
8756 warn when we're calling a non-named server by its nickname;
8757 don't warn twice about the same name.
8758 - Downgrade the dirserver log messages when whining about
8760 - Correct "your server is reachable" log entries to indicate that
8761 it was self-testing that told us so.
8762 - If we're trying to be a Tor server and running Windows 95/98/ME
8763 as a server, explain that we'll likely crash.
8764 - Provide a more useful warn message when our onion queue gets full:
8765 the CPU is too slow or the exit policy is too liberal.
8766 - Don't warn when we receive a 503 from a dirserver/cache -- this
8767 will pave the way for them being able to refuse if they're busy.
8768 - When we fail to bind a listener, try to provide a more useful
8769 log message: e.g., "Is Tor already running?"
8770 - Only start testing reachability once we've established a
8771 circuit. This will make startup on dir authorities less noisy.
8772 - Don't try to upload hidden service descriptors until we have
8773 established a circuit.
8774 - Tor didn't warn when it failed to open a log file.
8775 - Warn when listening on a public address for socks. We suspect a
8776 lot of people are setting themselves up as open socks proxies,
8777 and they have no idea that jerks on the Internet are using them,
8778 since they simply proxy the traffic into the Tor network.
8779 - Give a useful message when people run Tor as the wrong user,
8780 rather than telling them to start chowning random directories.
8781 - Fix a harmless bug that was causing Tor servers to log
8782 "Got an end because of misc error, but we're not an AP. Closing."
8783 - Fix wrong log message when you add a "HiddenServiceNodes" config
8784 line without any HiddenServiceDir line (reported by Chris Thomas).
8785 - Directory authorities now stop whining so loudly about bad
8786 descriptors that they fetch from other dirservers. So when there's
8787 a log complaint, it's for sure from a freshly uploaded descriptor.
8788 - When logging via syslog, include the pid whenever we provide
8789 a log entry. Suggested by Todd Fries.
8790 - When we're shutting down and we do something like try to post a
8791 server descriptor or rendezvous descriptor, don't complain that
8792 we seem to be unreachable. Of course we are, we're shutting down.
8793 - Change log line for unreachability to explicitly suggest /etc/hosts
8794 as the culprit. Also make it clearer what IP address and ports we're
8795 testing for reachability.
8796 - Put quotes around user-supplied strings when logging so users are
8797 more likely to realize if they add bad characters (like quotes)
8799 - NT service patch from Matt Edman to improve error messages on Win32.
8802 Changes in version 0.1.0.17 - 2006-02-17
8803 o Crash bugfixes on 0.1.0.x:
8804 - When servers with a non-zero DirPort came out of hibernation,
8805 sometimes they would trigger an assert.
8807 o Other important bugfixes:
8808 - On platforms that don't have getrlimit (like Windows), we were
8809 artificially constraining ourselves to a max of 1024
8810 connections. Now just assume that we can handle as many as 15000
8811 connections. Hopefully this won't cause other problems.
8813 o Backported features:
8814 - When we're a server, a client asks for an old-style directory,
8815 and our write bucket is empty, don't give it to him. This way
8816 small servers can continue to serve the directory *sometimes*,
8817 without getting overloaded.
8818 - Whenever you get a 503 in response to a directory fetch, try
8819 once more. This will become important once servers start sending
8820 503's whenever they feel busy.
8821 - Fetch a new directory every 120 minutes, not every 40 minutes.
8822 Now that we have hundreds of thousands of users running the old
8823 directory algorithm, it's starting to hurt a lot.
8824 - Bump up the period for forcing a hidden service descriptor upload
8825 from 20 minutes to 1 hour.
8828 Changes in version 0.1.0.16 - 2006-01-02
8829 o Crash bugfixes on 0.1.0.x:
8830 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
8831 corrupting the heap, losing FDs, or crashing when we need to resize
8832 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
8833 - It turns out sparc64 platforms crash on unaligned memory access
8834 too -- so detect and avoid this.
8835 - Handle truncated compressed data correctly (by detecting it and
8837 - Fix possible-but-unlikely free(NULL) in control.c.
8838 - When we were closing connections, there was a rare case that
8839 stomped on memory, triggering seg faults and asserts.
8840 - Avoid potential infinite recursion when building a descriptor. (We
8841 don't know that it ever happened, but better to fix it anyway.)
8842 - We were neglecting to unlink marked circuits from soon-to-close OR
8843 connections, which caused some rare scribbling on freed memory.
8844 - Fix a memory stomping race bug when closing the joining point of two
8845 rendezvous circuits.
8846 - Fix an assert in time parsing found by Steven Murdoch.
8848 o Other bugfixes on 0.1.0.x:
8849 - When we're doing reachability testing, provide more useful log
8850 messages so the operator knows what to expect.
8851 - Do not check whether DirPort is reachable when we are suppressing
8852 advertising it because of hibernation.
8853 - When building with -static or on Solaris, we sometimes needed -ldl.
8854 - One of the dirservers (tor26) changed its IP address.
8855 - When we're deciding whether a stream has enough circuits around
8856 that can handle it, count the freshly dirty ones and not the ones
8857 that are so dirty they won't be able to handle it.
8858 - When we're expiring old circuits, we had a logic error that caused
8859 us to close new rendezvous circuits rather than old ones.
8860 - Give a more helpful log message when you try to change ORPort via
8861 the controller: you should upgrade Tor if you want that to work.
8862 - We were failing to parse Tor versions that start with "Tor ".
8863 - Tolerate faulty streams better: when a stream fails for reason
8864 exitpolicy, stop assuming that the router is lying about his exit
8865 policy. When a stream fails for reason misc, allow it to retry just
8866 as if it was resolvefailed. When a stream has failed three times,
8867 reset its failure count so we can try again and get all three tries.
8870 Changes in version 0.1.0.15 - 2005-09-23
8871 o Bugfixes on 0.1.0.x:
8872 - Reject ports 465 and 587 (spam targets) in default exit policy.
8873 - Don't crash when we don't have any spare file descriptors and we
8874 try to spawn a dns or cpu worker.
8875 - Get rid of IgnoreVersion undocumented config option, and make us
8876 only warn, never exit, when we're running an obsolete version.
8877 - Don't try to print a null string when your server finds itself to
8878 be unreachable and the Address config option is empty.
8879 - Make the numbers in read-history and write-history into uint64s,
8880 so they don't overflow and publish negatives in the descriptor.
8881 - Fix a minor memory leak in smartlist_string_remove().
8882 - We were only allowing ourselves to upload a server descriptor at
8883 most every 20 minutes, even if it changed earlier than that.
8884 - Clean up log entries that pointed to old URLs.
8887 Changes in version 0.1.0.14 - 2005-08-08
8888 o Bugfixes on 0.1.0.x:
8889 - Fix the other half of the bug with crypto handshakes
8891 - Fix an assert trigger if you send a 'signal term' via the
8892 controller when it's listening for 'event info' messages.
8895 Changes in version 0.1.0.13 - 2005-08-04
8896 o Bugfixes on 0.1.0.x:
8897 - Fix a critical bug in the security of our crypto handshakes.
8898 - Fix a size_t underflow in smartlist_join_strings2() that made
8899 it do bad things when you hand it an empty smartlist.
8900 - Fix Windows installer to ship Tor license (thanks to Aphex for
8901 pointing out this oversight) and put a link to the doc directory
8903 - Explicitly set no-unaligned-access for sparc: it turns out the
8904 new gcc's let you compile broken code, but that doesn't make it
8908 Changes in version 0.1.0.12 - 2005-07-18
8909 o New directory servers:
8910 - tor26 has changed IP address.
8912 o Bugfixes on 0.1.0.x:
8913 - Fix a possible double-free in tor_gzip_uncompress().
8914 - When --disable-threads is set, do not search for or link against
8916 - Don't trigger an assert if an authoritative directory server
8917 claims its dirport is 0.
8918 - Fix bug with removing Tor as an NT service: some people were
8919 getting "The service did not return an error." Thanks to Matt
8923 Changes in version 0.1.0.11 - 2005-06-30
8924 o Bugfixes on 0.1.0.x:
8925 - Fix major security bug: servers were disregarding their
8926 exit policies if clients behaved unexpectedly.
8927 - Make OS X init script check for missing argument, so we don't
8928 confuse users who invoke it incorrectly.
8929 - Fix a seg fault in "tor --hash-password foo".
8930 - The MAPADDRESS control command was broken.
8933 Changes in version 0.1.0.10 - 2005-06-14
8935 - Make NT services work and start on startup on Win32 (based on
8936 patch by Matt Edman). See the FAQ entry for details.
8937 - Make 'platform' string in descriptor more accurate for Win32
8938 servers, so it's not just "unknown platform".
8939 - REUSEADDR on normal platforms means you can rebind to the port
8940 right after somebody else has let it go. But REUSEADDR on Win32
8941 means you can bind to the port _even when somebody else already
8942 has it bound_! So, don't do that on Win32.
8943 - Clean up the log messages when starting on Win32 with no config
8945 - Allow seeding the RNG on Win32 even when you're not running as
8946 Administrator. If seeding the RNG on Win32 fails, quit.
8948 o Assert / crash bugs:
8949 - Refuse relay cells that claim to have a length larger than the
8950 maximum allowed. This prevents a potential attack that could read
8951 arbitrary memory (e.g. keys) from an exit server's process
8953 - If unofficial Tor clients connect and send weird TLS certs, our
8954 Tor server triggers an assert. Stop asserting, and start handling
8955 TLS errors better in other situations too.
8956 - Fix a race condition that can trigger an assert when we have a
8957 pending create cell and an OR connection attempt fails.
8960 - Use pthreads for worker processes rather than forking. This was
8961 forced because when we forked, we ended up wasting a lot of
8962 duplicate ram over time.
8963 - Also switch to foo_r versions of some library calls to allow
8964 reentry and threadsafeness.
8965 - Implement --disable-threads configure option. Disable threads on
8966 netbsd and openbsd by default, because they have no reentrant
8967 resolver functions (!), and on solaris since it has other
8969 - Fix possible bug on threading platforms (e.g. win32) which was
8970 leaking a file descriptor whenever a cpuworker or dnsworker died.
8971 - Fix a minor memory leak when somebody establishes an introduction
8972 point at your Tor server.
8973 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
8975 - Add ./configure --with-dmalloc option, to track memory leaks.
8976 - And try to free all memory on closing, so we can detect what
8979 o Protocol correctness:
8980 - When we've connected to an OR and handshaked but didn't like
8981 the result, we were closing the conn without sending destroy
8982 cells back for pending circuits. Now send those destroys.
8983 - Start sending 'truncated' cells back rather than destroy cells
8984 if the circuit closes in front of you. This means we won't have
8985 to abandon partially built circuits.
8986 - Handle changed router status correctly when dirserver reloads
8987 fingerprint file. We used to be dropping all unverified descriptors
8988 right then. The bug was hidden because we would immediately
8989 fetch a directory from another dirserver, which would include the
8990 descriptors we just dropped.
8991 - Revise tor-spec to add more/better stream end reasons.
8992 - Revise all calls to connection_edge_end to avoid sending 'misc',
8993 and to take errno into account where possible.
8994 - Client now retries when streams end early for 'hibernating' or
8995 'resource limit' reasons, rather than failing them.
8996 - Try to be more zealous about calling connection_edge_end when
8997 things go bad with edge conns in connection.c.
8999 o Robustness improvements:
9000 - Better handling for heterogeneous / unreliable nodes:
9001 - Annotate circuits with whether they aim to contain high uptime
9002 nodes and/or high capacity nodes. When building circuits, choose
9004 - This means that every single node in an intro rend circuit,
9005 not just the last one, will have a minimum uptime.
9006 - New config option LongLivedPorts to indicate application streams
9007 that will want high uptime circuits.
9008 - Servers reset uptime when a dir fetch entirely fails. This
9009 hopefully reflects stability of the server's network connectivity.
9010 - If somebody starts his tor server in Jan 2004 and then fixes his
9011 clock, don't make his published uptime be a year.
9012 - Reset published uptime when we wake up from hibernation.
9013 - Introduce a notion of 'internal' circs, which are chosen without
9014 regard to the exit policy of the last hop. Intro and rendezvous
9015 circs must be internal circs, to avoid leaking information. Resolve
9016 and connect streams can use internal circs if they want.
9017 - New circuit pooling algorithm: keep track of what destination ports
9018 we've used recently (start out assuming we'll want to use 80), and
9019 make sure to have enough circs around to satisfy these ports. Also
9020 make sure to have 2 internal circs around if we've required internal
9021 circs lately (and with high uptime if we've seen that lately too).
9022 - Turn addr_policy_compare from a tristate to a quadstate; this should
9023 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
9024 for google.com" problem.
9025 - When a client asks us for a dir mirror and we don't have one,
9026 launch an attempt to get a fresh one.
9027 - First cut at support for "create-fast" cells. Clients can use
9028 these when extending to their first hop, since the TLS already
9029 provides forward secrecy and authentication. Not enabled on
9032 o Reachability testing.
9033 - Your Tor server will automatically try to see if its ORPort and
9034 DirPort are reachable from the outside, and it won't upload its
9035 descriptor until it decides at least ORPort is reachable (when
9036 DirPort is not yet found reachable, publish it as zero).
9037 - When building testing circs for ORPort testing, use only
9038 high-bandwidth nodes, so fewer circuits fail.
9039 - Notice when our IP changes, and reset stats/uptime/reachability.
9040 - Authdirservers don't do ORPort reachability detection, since
9041 they're in clique mode, so it will be rare to find a server not
9042 already connected to them.
9043 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
9047 - Now we allow two unverified servers with the same nickname
9048 but different keys. But if a nickname is verified, only that
9049 nickname+key are allowed.
9050 - If you're an authdirserver connecting to an address:port,
9051 and it's not the OR you were expecting, forget about that
9052 descriptor. If he *was* the one you were expecting, then forget
9053 about all other descriptors for that address:port.
9054 - Allow servers to publish descriptors from 12 hours in the future.
9055 Corollary: only whine about clock skew from the dirserver if
9056 he's a trusted dirserver (since now even verified servers could
9057 have quite wrong clocks).
9058 - Require servers that use the default dirservers to have public IP
9059 addresses. We have too many servers that are configured with private
9060 IPs and their admins never notice the log entries complaining that
9061 their descriptors are being rejected.
9063 o Efficiency improvements:
9064 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
9065 and /dev/poll), and hopefully work better on Windows too.
9066 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
9067 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
9068 - Find libevent even if it's hiding in /usr/local/ and your
9069 CFLAGS and LDFLAGS don't tell you to look there.
9070 - Be able to link with libevent as a shared library (the default
9071 after 1.0d), even if it's hiding in /usr/local/lib and even
9072 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
9073 assuming you're running gcc. Otherwise fail and give a useful
9075 - Switch to a new buffer management algorithm, which tries to avoid
9076 reallocing and copying quite as much. In first tests it looks like
9077 it uses *more* memory on average, but less cpu.
9078 - Switch our internal buffers implementation to use a ring buffer,
9079 to hopefully improve performance for fast servers a lot.
9080 - Reenable the part of the code that tries to flush as soon as an
9081 OR outbuf has a full TLS record available. Perhaps this will make
9082 OR outbufs not grow as huge except in rare cases, thus saving lots
9083 of CPU time plus memory.
9084 - Improve performance for dirservers: stop re-parsing the whole
9085 directory every time you regenerate it.
9086 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
9087 it much faster to look up a circuit for each relay cell.
9088 - Remove most calls to assert_all_pending_dns_resolves_ok(),
9089 since they're eating our cpu on exit nodes.
9090 - Stop wasting time doing a case insensitive comparison for every
9091 dns name every time we do any lookup. Canonicalize the names to
9092 lowercase when you first see them.
9095 - Handle unavailable hidden services better. Handle slow or busy
9096 hidden services better.
9097 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
9098 circ as necessary, if there are any completed ones lying around
9099 when we try to launch one.
9100 - Make hidden services try to establish a rendezvous for 30 seconds
9101 after fetching the descriptor, rather than for n (where n=3)
9102 attempts to build a circuit.
9103 - Adjust maximum skew and age for rendezvous descriptors: let skew
9104 be 48 hours rather than 90 minutes.
9105 - Reject malformed .onion addresses rather then passing them on as
9106 normal web requests.
9109 - More Tor controller support. See
9110 http://tor.eff.org/doc/control-spec.txt for all the new features,
9111 including signals to emulate unix signals from any platform;
9112 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
9113 closestream; closecircuit; etc.
9114 - Encode hashed controller passwords in hex instead of base64,
9115 to make it easier to write controllers.
9116 - Revise control spec and implementation to allow all log messages to
9117 be sent to controller with their severities intact (suggested by
9118 Matt Edman). Disable debug-level logs while delivering a debug-level
9119 log to the controller, to prevent loop. Update TorControl to handle
9120 new log event types.
9122 o New config options/defaults:
9123 - Begin scrubbing sensitive strings from logs by default. Turn off
9124 the config option SafeLogging if you need to do debugging.
9125 - New exit policy: accept most low-numbered ports, rather than
9126 rejecting most low-numbered ports.
9127 - Put a note in the torrc about abuse potential with the default
9129 - Add support for CONNECTing through https proxies, with "HttpsProxy"
9131 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
9132 based on patch from Adam Langley (basic auth only).
9133 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
9134 the fast servers that have been joining lately. (Clients are now
9135 willing to load balance over up to 2 MB of advertised bandwidth
9137 - New config option MaxAdvertisedBandwidth which lets you advertise
9138 a low bandwidthrate (to not attract as many circuits) while still
9139 allowing a higher bandwidthrate in reality.
9140 - Require BandwidthRate to be at least 20kB/s for servers.
9141 - Add a NoPublish config option, so you can be a server (e.g. for
9142 testing running Tor servers in other Tor networks) without
9143 publishing your descriptor to the primary dirservers.
9144 - Add a new AddressMap config directive to rewrite incoming socks
9145 addresses. This lets you, for example, declare an implicit
9146 required exit node for certain sites.
9147 - Add a new TrackHostExits config directive to trigger addressmaps
9148 for certain incoming socks addresses -- for sites that break when
9149 your exit keeps changing (based on patch from Mike Perry).
9150 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
9151 which describes how often we retry making new circuits if current
9152 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
9153 how long we're willing to make use of an already-dirty circuit.
9154 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
9155 a config option "ShutdownWaitLength" (when using kill -INT on
9157 - Fix an edge case in parsing config options: if they say "--"
9158 on the commandline, it's not a config option (thanks weasel).
9159 - New config option DirAllowPrivateAddresses for authdirservers.
9160 Now by default they refuse router descriptors that have non-IP or
9161 private-IP addresses.
9162 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
9163 smart" default value: low for servers and high for clients.
9164 - Some people were putting "Address " in their torrc, and they had
9165 a buggy resolver that resolved " " to 0.0.0.0. Oops.
9166 - If DataDir is ~/.tor, and that expands to /.tor, then default to
9167 LOCALSTATEDIR/tor instead.
9168 - Implement --verify-config command-line option to check if your torrc
9169 is valid without actually launching Tor.
9171 o Logging improvements:
9172 - When dirservers refuse a server descriptor, we now log its
9173 contactinfo, platform, and the poster's IP address.
9174 - Only warn once per nickname from add_nickname_list_to_smartlist()
9175 per failure, so an entrynode or exitnode choice that's down won't
9177 - When we're connecting to an OR and he's got a different nickname/key
9178 than we were expecting, only complain loudly if we're an OP or a
9179 dirserver. Complaining loudly to the OR admins just confuses them.
9180 - Whine at you if you're a server and you don't set your contactinfo.
9181 - Warn when exit policy implicitly allows local addresses.
9182 - Give a better warning when some other server advertises an
9183 ORPort that is actually an apache running ssl.
9184 - If we get an incredibly skewed timestamp from a dirserver mirror
9185 that isn't a verified OR, don't warn -- it's probably him that's
9187 - When a dirserver causes you to give a warn, mention which dirserver
9189 - Initialize libevent later in the startup process, so the logs are
9190 already established by the time we start logging libevent warns.
9191 - Use correct errno on win32 if libevent fails.
9192 - Check and warn about known-bad/slow libevent versions.
9193 - Stop warning about sigpipes in the logs. We're going to
9194 pretend that getting these occassionally is normal and fine.
9196 o New contrib scripts:
9197 - New experimental script tor/contrib/exitlist: a simple python
9198 script to parse directories and find Tor nodes that exit to listed
9200 - New experimental script tor/contrib/ExerciseServer.py (needs more
9201 work) that uses the controller interface to build circuits and
9202 fetch pages over them. This will help us bootstrap servers that
9203 have lots of capacity but haven't noticed it yet.
9204 - New experimental script tor/contrib/PathDemo.py (needs more work)
9205 that uses the controller interface to let you choose whole paths
9207 "<hostname>.<path,separated by dots>.<length of path>.path"
9208 - New contributed script "privoxy-tor-toggle" to toggle whether
9209 Privoxy uses Tor. Seems to be configured for Debian by default.
9210 - Have torctl.in/tor.sh.in check for location of su binary (needed
9214 - chdir() to your datadirectory at the *end* of the daemonize process,
9215 not the beginning. This was a problem because the first time you
9216 run tor, if your datadir isn't there, and you have runasdaemon set
9217 to 1, it will try to chdir to it before it tries to create it. Oops.
9218 - Fix several double-mark-for-close bugs, e.g. where we were finding
9219 a conn for a cell even if that conn is already marked for close.
9220 - Stop most cases of hanging up on a socks connection without sending
9222 - Fix a bug in the RPM package: set home directory for _tor to
9223 something more reasonable when first installing.
9224 - Stop putting nodename in the Platform string in server descriptors.
9225 It doesn't actually help, and it is confusing/upsetting some people.
9226 - When using preferred entry or exit nodes, ignore whether the
9227 circuit wants uptime or capacity. They asked for the nodes, they
9229 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
9230 artificially capped at 500kB.
9231 - Cache local dns resolves correctly even when they're .exit
9233 - If we're hibernating and we get a SIGINT, exit immediately.
9234 - tor-resolve requests were ignoring .exit if there was a working circuit
9235 they could use instead.
9236 - Pay more attention to the ClientOnly config option.
9237 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
9238 installer screens; and don't put stuff into StartupItems unless
9239 the user asks you to.
9242 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
9243 rather than just rejecting it.
9244 - If our clock jumps forward by 100 seconds or more, assume something
9245 has gone wrong with our network and abandon all not-yet-used circs.
9246 - When an application is using socks5, give him the whole variety of
9247 potential socks5 responses (connect refused, host unreachable, etc),
9248 rather than just "success" or "failure".
9249 - A more sane version numbering system. See
9250 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
9251 - Change version parsing logic: a version is "obsolete" if it is not
9252 recommended and (1) there is a newer recommended version in the
9253 same series, or (2) there are no recommended versions in the same
9254 series, but there are some recommended versions in a newer series.
9255 A version is "new" if it is newer than any recommended version in
9257 - Report HTTP reasons to client when getting a response from directory
9258 servers -- so you can actually know what went wrong.
9259 - Reject odd-looking addresses at the client (e.g. addresses that
9260 contain a colon), rather than having the server drop them because
9262 - Stop publishing socksport in the directory, since it's not
9263 actually meant to be public. For compatibility, publish a 0 there
9265 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
9266 cookies to disk and doesn't log each web request to disk. (Thanks
9267 to Brett Carrington for pointing this out.)
9268 - Add OSX uninstall instructions. An actual uninstall script will
9270 - Add "opt hibernating 1" to server descriptor to make it clearer
9271 whether the server is hibernating.
9274 Changes in version 0.0.9.10 - 2005-06-16
9275 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
9276 - Refuse relay cells that claim to have a length larger than the
9277 maximum allowed. This prevents a potential attack that could read
9278 arbitrary memory (e.g. keys) from an exit server's process
9282 Changes in version 0.0.9.9 - 2005-04-23
9283 o Bugfixes on 0.0.9.x:
9284 - If unofficial Tor clients connect and send weird TLS certs, our
9285 Tor server triggers an assert. This release contains a minimal
9286 backport from the broader fix that we put into 0.1.0.4-rc.
9289 Changes in version 0.0.9.8 - 2005-04-07
9290 o Bugfixes on 0.0.9.x:
9291 - We have a bug that I haven't found yet. Sometimes, very rarely,
9292 cpuworkers get stuck in the 'busy' state, even though the cpuworker
9293 thinks of itself as idle. This meant that no new circuits ever got
9294 established. Here's a workaround to kill any cpuworker that's been
9295 busy for more than 100 seconds.
9298 Changes in version 0.0.9.7 - 2005-04-01
9299 o Bugfixes on 0.0.9.x:
9300 - Fix another race crash bug (thanks to Glenn Fink for reporting).
9301 - Compare identity to identity, not to nickname, when extending to
9302 a router not already in the directory. This was preventing us from
9303 extending to unknown routers. Oops.
9304 - Make sure to create OS X Tor user in <500 range, so we aren't
9305 creating actual system users.
9306 - Note where connection-that-hasn't-sent-end was marked, and fix
9307 a few really loud instances of this harmless bug (it's fixed more
9311 Changes in version 0.0.9.6 - 2005-03-24
9312 o Bugfixes on 0.0.9.x (crashes and asserts):
9313 - Add new end stream reasons to maintainance branch. Fix bug where
9314 reason (8) could trigger an assert. Prevent bug from recurring.
9315 - Apparently win32 stat wants paths to not end with a slash.
9316 - Fix assert triggers in assert_cpath_layer_ok(), where we were
9317 blowing away the circuit that conn->cpath_layer points to, then
9318 checking to see if the circ is well-formed. Backport check to make
9319 sure we dont use the cpath on a closed connection.
9320 - Prevent circuit_resume_edge_reading_helper() from trying to package
9321 inbufs for marked-for-close streams.
9322 - Don't crash on hup if your options->address has become unresolvable.
9323 - Some systems (like OS X) sometimes accept() a connection and tell
9324 you the remote host is 0.0.0.0:0. If this happens, due to some
9325 other mis-features, we get confused; so refuse the conn for now.
9327 o Bugfixes on 0.0.9.x (other):
9328 - Fix harmless but scary "Unrecognized content encoding" warn message.
9329 - Add new stream error reason: TORPROTOCOL reason means "you are not
9330 speaking a version of Tor I understand; say bye-bye to your stream."
9331 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
9332 into the future, now that we are more tolerant of skew. This
9333 resolves a bug where a Tor server would refuse to cache a directory
9334 because all the directories it gets are too far in the future;
9335 yet the Tor server never logs any complaints about clock skew.
9336 - Mac packaging magic: make man pages useable, and do not overwrite
9337 existing torrc files.
9338 - Make OS X log happily to /var/log/tor/tor.log
9341 Changes in version 0.0.9.5 - 2005-02-22
9342 o Bugfixes on 0.0.9.x:
9343 - Fix an assert race at exit nodes when resolve requests fail.
9344 - Stop picking unverified dir mirrors--it only leads to misery.
9345 - Patch from Matt Edman to make NT services work better. Service
9346 support is still not compiled into the executable by default.
9347 - Patch from Dmitri Bely so the Tor service runs better under
9348 the win32 SYSTEM account.
9349 - Make tor-resolve actually work (?) on Win32.
9350 - Fix a sign bug when getrlimit claims to have 4+ billion
9351 file descriptors available.
9352 - Stop refusing to start when bandwidthburst == bandwidthrate.
9353 - When create cells have been on the onion queue more than five
9354 seconds, just send back a destroy and take them off the list.
9357 Changes in version 0.0.9.4 - 2005-02-03
9358 o Bugfixes on 0.0.9:
9359 - Fix an assert bug that took down most of our servers: when
9360 a server claims to have 1 GB of bandwidthburst, don't
9362 - Don't crash as badly if we have spawned the max allowed number
9363 of dnsworkers, or we're out of file descriptors.
9364 - Block more file-sharing ports in the default exit policy.
9365 - MaxConn is now automatically set to the hard limit of max
9366 file descriptors we're allowed (ulimit -n), minus a few for
9368 - Give a clearer message when servers need to raise their
9369 ulimit -n when they start running out of file descriptors.
9370 - SGI Compatibility patches from Jan Schaumann.
9371 - Tolerate a corrupt cached directory better.
9372 - When a dirserver hasn't approved your server, list which one.
9373 - Go into soft hibernation after 95% of the bandwidth is used,
9374 not 99%. This is especially important for daily hibernators who
9375 have a small accounting max. Hopefully it will result in fewer
9376 cut connections when the hard hibernation starts.
9377 - Load-balance better when using servers that claim more than
9378 800kB/s of capacity.
9379 - Make NT services work (experimental, only used if compiled in).
9382 Changes in version 0.0.9.3 - 2005-01-21
9383 o Bugfixes on 0.0.9:
9384 - Backport the cpu use fixes from main branch, so busy servers won't
9385 need as much processor time.
9386 - Work better when we go offline and then come back, or when we
9387 run Tor at boot before the network is up. We do this by
9388 optimistically trying to fetch a new directory whenever an
9389 application request comes in and we think we're offline -- the
9390 human is hopefully a good measure of when the network is back.
9391 - Backport some minimal hidserv bugfixes: keep rend circuits open as
9392 long as you keep using them; actually publish hidserv descriptors
9393 shortly after they change, rather than waiting 20-40 minutes.
9394 - Enable Mac startup script by default.
9395 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
9396 - When you update AllowUnverifiedNodes or FirewallPorts via the
9397 controller's setconf feature, we were always appending, never
9399 - When you update HiddenServiceDir via setconf, it was screwing up
9400 the order of reading the lines, making it fail.
9401 - Do not rewrite a cached directory back to the cache; otherwise we
9402 will think it is recent and not fetch a newer one on startup.
9403 - Workaround for webservers that lie about Content-Encoding: Tor
9404 now tries to autodetect compressed directories and compression
9405 itself. This lets us Proxypass dir fetches through apache.
9408 Changes in version 0.0.9.2 - 2005-01-04
9409 o Bugfixes on 0.0.9 (crashes and asserts):
9410 - Fix an assert on startup when the disk is full and you're logging
9412 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
9413 style address, then we'd crash.
9414 - Fix an assert trigger when the running-routers string we get from
9415 a dirserver is broken.
9416 - Make worker threads start and run on win32. Now win32 servers
9418 - Bandaid (not actually fix, but now it doesn't crash) an assert
9419 where the dns worker dies mysteriously and the main Tor process
9420 doesn't remember anything about the address it was resolving.
9422 o Bugfixes on 0.0.9 (Win32):
9423 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
9424 name out of the warning/assert messages.
9425 - Fix a superficial "unhandled error on read" bug on win32.
9426 - The win32 installer no longer requires a click-through for our
9427 license, since our Free Software license grants rights but does not
9429 - Win32: When connecting to a dirserver fails, try another one
9430 immediately. (This was already working for non-win32 Tors.)
9431 - Stop trying to parse $HOME on win32 when hunting for default
9433 - Make tor-resolve.c work on win32 by calling network_init().
9435 o Bugfixes on 0.0.9 (other):
9436 - Make 0.0.9.x build on Solaris again.
9437 - Due to a fencepost error, we were blowing away the \n when reporting
9438 confvalue items in the controller. So asking for multiple config
9439 values at once couldn't work.
9440 - When listing circuits that are pending on an opening OR connection,
9441 if we're an OR we were listing circuits that *end* at us as
9442 being pending on every listener, dns/cpu worker, etc. Stop that.
9443 - Dirservers were failing to create 'running-routers' or 'directory'
9444 strings if we had more than some threshold of routers. Fix them so
9445 they can handle any number of routers.
9446 - Fix a superficial "Duplicate mark for close" bug.
9447 - Stop checking for clock skew for OR connections, even for servers.
9448 - Fix a fencepost error that was chopping off the last letter of any
9449 nickname that is the maximum allowed nickname length.
9450 - Update URLs in log messages so they point to the new website.
9451 - Fix a potential problem in mangling server private keys while
9452 writing to disk (not triggered yet, as far as we know).
9453 - Include the licenses for other free software we include in Tor,
9454 now that we're shipping binary distributions more regularly.
9457 Changes in version 0.0.9.1 - 2004-12-15
9458 o Bugfixes on 0.0.9:
9459 - Make hibernation actually work.
9460 - Make HashedControlPassword config option work.
9461 - When we're reporting event circuit status to a controller,
9462 don't use the stream status code.
9465 Changes in version 0.0.9 - 2004-12-12
9466 o Bugfixes on 0.0.8.1 (Crashes and asserts):
9467 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
9468 write() call will fail and we handle it there.
9469 - When we run out of disk space, or other log writing error, don't
9470 crash. Just stop logging to that log and continue.
9471 - Fix isspace() and friends so they still make Solaris happy
9472 but also so they don't trigger asserts on win32.
9473 - Fix assert failure on malformed socks4a requests.
9474 - Fix an assert bug where a hidden service provider would fail if
9475 the first hop of his rendezvous circuit was down.
9476 - Better handling of size_t vs int, so we're more robust on 64
9479 o Bugfixes on 0.0.8.1 (Win32):
9480 - Make windows sockets actually non-blocking (oops), and handle
9481 win32 socket errors better.
9482 - Fix parse_iso_time on platforms without strptime (eg win32).
9483 - win32: when being multithreaded, leave parent fdarray open.
9484 - Better handling of winsock includes on non-MSV win32 compilers.
9485 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
9487 - Make unit tests work on win32.
9489 o Bugfixes on 0.0.8.1 (Path selection and streams):
9490 - Calculate timeout for waiting for a connected cell from the time
9491 we sent the begin cell, not from the time the stream started. If
9492 it took a long time to establish the circuit, we would time out
9493 right after sending the begin cell.
9494 - Fix router_compare_addr_to_addr_policy: it was not treating a port
9495 of * as always matching, so we were picking reject *:* nodes as
9496 exit nodes too. Oops.
9497 - When read() failed on a stream, we would close it without sending
9498 back an end. So 'connection refused' would simply be ignored and
9499 the user would get no response.
9500 - Stop a sigpipe: when an 'end' cell races with eof from the app,
9501 we shouldn't hold-open-until-flush if the eof arrived first.
9502 - Let resolve conns retry/expire also, rather than sticking around
9504 - Fix more dns related bugs: send back resolve_failed and end cells
9505 more reliably when the resolve fails, rather than closing the
9506 circuit and then trying to send the cell. Also attach dummy resolve
9507 connections to a circuit *before* calling dns_resolve(), to fix
9508 a bug where cached answers would never be sent in RESOLVED cells.
9510 o Bugfixes on 0.0.8.1 (Circuits):
9511 - Finally fix a bug that's been plaguing us for a year:
9512 With high load, circuit package window was reaching 0. Whenever
9513 we got a circuit-level sendme, we were reading a lot on each
9514 socket, but only writing out a bit. So we would eventually reach
9515 eof. This would be noticed and acted on even when there were still
9516 bytes sitting in the inbuf.
9517 - Use identity comparison, not nickname comparison, to choose which
9518 half of circuit-ID-space each side gets to use. This is needed
9519 because sometimes we think of a router as a nickname, and sometimes
9520 as a hex ID, and we can't predict what the other side will do.
9522 o Bugfixes on 0.0.8.1 (Other):
9523 - Fix a whole slew of memory leaks.
9524 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
9525 - If we are using select, make sure we stay within FD_SETSIZE.
9526 - When poll() is interrupted, we shouldn't believe the revents values.
9527 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
9528 and smartlist_len, which are two major profiling offenders.
9529 - If do_hup fails, actually notice.
9530 - Flush the log file descriptor after we print "Tor opening log file",
9531 so we don't see those messages days later.
9532 - Hidden service operators now correctly handle version 1 style
9533 INTRODUCE1 cells (nobody generates them still, so not a critical
9535 - Handle more errnos from accept() without closing the listener.
9536 Some OpenBSD machines were closing their listeners because
9537 they ran out of file descriptors.
9538 - Some people had wrapped their tor client/server in a script
9539 that would restart it whenever it died. This did not play well
9540 with our "shut down if your version is obsolete" code. Now people
9541 don't fetch a new directory if their local cached version is
9543 - Make our autogen.sh work on ksh as well as bash.
9544 - Better torrc example lines for dirbindaddress and orbindaddress.
9545 - Improved bounds checking on parsed ints (e.g. config options and
9546 the ones we find in directories.)
9547 - Stop using separate defaults for no-config-file and
9548 empty-config-file. Now you have to explicitly turn off SocksPort,
9549 if you don't want it open.
9550 - We were starting to daemonize before we opened our logs, so if
9551 there were any problems opening logs, we would complain to stderr,
9552 which wouldn't work, and then mysteriously exit.
9553 - If a verified OR connects to us before he's uploaded his descriptor,
9554 or we verify him and hup but he still has the original TLS
9555 connection, then conn->nickname is still set like he's unverified.
9557 o Code security improvements, inspired by Ilja:
9558 - tor_snprintf wrapper over snprintf with consistent (though not C99)
9560 - Replace sprintf with tor_snprintf. (I think they were all safe, but
9562 - Replace strcpy/strncpy with strlcpy in more places.
9563 - Avoid strcat; use tor_snprintf or strlcat instead.
9565 o Features (circuits and streams):
9566 - New circuit building strategy: keep a list of ports that we've
9567 used in the past 6 hours, and always try to have 2 circuits open
9568 or on the way that will handle each such port. Seed us with port
9569 80 so web users won't complain that Tor is "slow to start up".
9570 - Make kill -USR1 dump more useful stats about circuits.
9571 - When warning about retrying or giving up, print the address, so
9572 the user knows which one it's talking about.
9573 - If you haven't used a clean circuit in an hour, throw it away,
9574 just to be on the safe side. (This means after 6 hours a totally
9575 unused Tor client will have no circuits open.)
9576 - Support "foo.nickname.exit" addresses, to let Alice request the
9577 address "foo" as viewed by exit node "nickname". Based on a patch
9579 - If your requested entry or exit node has advertised bandwidth 0,
9581 - Be more greedy about filling up relay cells -- we try reading again
9582 once we've processed the stuff we read, in case enough has arrived
9583 to fill the last cell completely.
9584 - Refuse application socks connections to port 0.
9585 - Use only 0.0.9pre1 and later servers for resolve cells.
9587 o Features (bandwidth):
9588 - Hibernation: New config option "AccountingMax" lets you
9589 set how many bytes per month (in each direction) you want to
9590 allow your server to consume. Rather than spreading those
9591 bytes out evenly over the month, we instead hibernate for some
9592 of the month and pop up at a deterministic time, work until
9593 the bytes are consumed, then hibernate again. Config option
9594 "MonthlyAccountingStart" lets you specify which day of the month
9595 your billing cycle starts on.
9596 - Implement weekly/monthly/daily accounting: now you specify your
9597 hibernation properties by
9598 AccountingMax N bytes|KB|MB|GB|TB
9599 AccountingStart day|week|month [day] HH:MM
9600 Defaults to "month 1 0:00".
9601 - Let bandwidth and interval config options be specified as 5 bytes,
9602 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
9604 o Features (directories):
9605 - New "router-status" line in directory, to better bind each verified
9606 nickname to its identity key.
9607 - Clients can ask dirservers for /dir.z to get a compressed version
9608 of the directory. Only works for servers running 0.0.9, of course.
9609 - Make clients cache directories and use them to seed their router
9610 lists at startup. This means clients have a datadir again.
9611 - Respond to content-encoding headers by trying to uncompress as
9613 - Clients and servers now fetch running-routers; cache
9614 running-routers; compress running-routers; serve compressed
9616 - Make moria2 advertise a dirport of 80, so people behind firewalls
9617 will be able to get a directory.
9618 - Http proxy support
9619 - Dirservers translate requests for http://%s:%d/x to /x
9620 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
9621 be routed through this host.
9622 - Clients ask for /tor/x rather than /x for new enough dirservers.
9623 This way we can one day coexist peacefully with apache.
9624 - Clients specify a "Host: %s%d" http header, to be compatible
9625 with more proxies, and so running squid on an exit node can work.
9626 - Protect dirservers from overzealous descriptor uploading -- wait
9627 10 seconds after directory gets dirty, before regenerating.
9629 o Features (packages and install):
9630 - Add NSI installer contributed by J Doe.
9631 - Apply NT service patch from Osamu Fujino. Still needs more work.
9632 - Commit VC6 and VC7 workspace/project files.
9633 - Commit a tor.spec for making RPM files, with help from jbash.
9634 - Add contrib/torctl.in contributed by Glenn Fink.
9635 - Make expand_filename handle ~ and ~username.
9636 - Use autoconf to enable largefile support where necessary. Use
9637 ftello where available, since ftell can fail at 2GB.
9638 - Ship src/win32/ in the tarball, so people can use it to build.
9639 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
9642 o Features (ui controller):
9643 - Control interface: a separate program can now talk to your
9644 client/server over a socket, and get/set config options, receive
9645 notifications of circuits and streams starting/finishing/dying,
9646 bandwidth used, etc. The next step is to get some GUIs working.
9647 Let us know if you want to help out. See doc/control-spec.txt .
9648 - Ship a contrib/tor-control.py as an example script to interact
9649 with the control port.
9650 - "tor --hash-password zzyxz" will output a salted password for
9651 use in authenticating to the control interface.
9652 - Implement the control-spec's SAVECONF command, to write your
9653 configuration to torrc.
9654 - Get cookie authentication for the controller closer to working.
9655 - When set_conf changes our server descriptor, upload a new copy.
9656 But don't upload it too often if there are frequent changes.
9658 o Features (config and command-line):
9659 - Deprecate unofficial config option abbreviations, and abbreviations
9660 not on the command line.
9661 - Configuration infrastructure support for warning on obsolete
9663 - Give a slightly more useful output for "tor -h".
9664 - Break DirFetchPostPeriod into:
9665 - DirFetchPeriod for fetching full directory,
9666 - StatusFetchPeriod for fetching running-routers,
9667 - DirPostPeriod for posting server descriptor,
9668 - RendPostPeriod for posting hidden service descriptors.
9669 - New log format in config:
9670 "Log minsev[-maxsev] stdout|stderr|syslog" or
9671 "Log minsev[-maxsev] file /var/foo"
9672 - DirPolicy config option, to let people reject incoming addresses
9673 from their dirserver.
9674 - "tor --list-fingerprint" will list your identity key fingerprint
9676 - Make tor --version --version dump the cvs Id of every file.
9677 - New 'MyFamily nick1,...' config option for a server to
9678 specify other servers that shouldn't be used in the same circuit
9679 with it. Only believed if nick1 also specifies us.
9680 - New 'NodeFamily nick1,nick2,...' config option for a client to
9681 specify nodes that it doesn't want to use in the same circuit.
9682 - New 'Redirectexit pattern address:port' config option for a
9683 server to redirect exit connections, e.g. to a local squid.
9684 - Add "pass" target for RedirectExit, to make it easier to break
9685 out of a sequence of RedirectExit rules.
9686 - Make the dirservers file obsolete.
9687 - Include a dir-signing-key token in directories to tell the
9688 parsing entity which key is being used to sign.
9689 - Remove the built-in bulky default dirservers string.
9690 - New config option "Dirserver %s:%d [fingerprint]", which can be
9691 repeated as many times as needed. If no dirservers specified,
9692 default to moria1,moria2,tor26.
9693 - Make 'Routerfile' config option obsolete.
9694 - Discourage people from setting their dirfetchpostperiod more often
9695 than once per minute.
9698 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
9699 get back to normal.)
9700 - Accept *:706 (silc) in default exit policy.
9701 - Implement new versioning format for post 0.1.
9702 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
9703 log more informatively.
9704 - Check clock skew for verified servers, but allow unverified
9705 servers and clients to have any clock skew.
9706 - Make sure the hidden service descriptors are at a random offset
9707 from each other, to hinder linkability.
9708 - Clients now generate a TLS cert too, in preparation for having
9709 them act more like real nodes.
9710 - Add a pure-C tor-resolve implementation.
9711 - Use getrlimit and friends to ensure we can reach MaxConn (currently
9712 1024) file descriptors.
9713 - Raise the max dns workers from 50 to 100.
9716 Changes in version 0.0.8.1 - 2004-10-13
9718 - Fix a seg fault that can be triggered remotely for Tor
9719 clients/servers with an open dirport.
9720 - Fix a rare assert trigger, where routerinfos for entries in
9721 our cpath would expire while we're building the path.
9722 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9723 - Fix a rare seg fault for people running hidden services on
9724 intermittent connections.
9725 - Fix a bug in parsing opt keywords with objects.
9726 - Fix a stale pointer assert bug when a stream detaches and
9728 - Fix a string format vulnerability (probably not exploitable)
9729 in reporting stats locally.
9730 - Fix an assert trigger: sometimes launching circuits can fail
9731 immediately, e.g. because too many circuits have failed recently.
9732 - Fix a compile warning on 64 bit platforms.
9735 Changes in version 0.0.8 - 2004-08-25
9737 - Made our unit tests compile again on OpenBSD 3.5, and tor
9738 itself compile again on OpenBSD on a sparc64.
9739 - We were neglecting milliseconds when logging on win32, so
9740 everything appeared to happen at the beginning of each second.
9741 - Check directory signature _before_ you decide whether you're
9742 you're running an obsolete version and should exit.
9743 - Check directory signature _before_ you parse the running-routers
9744 list to decide who's running.
9745 - Check return value of fclose while writing to disk, so we don't
9746 end up with broken files when servers run out of disk space.
9747 - Port it to SunOS 5.9 / Athena
9748 - Fix two bugs in saving onion keys to disk when rotating, so
9749 hopefully we'll get fewer people using old onion keys.
9750 - Remove our mostly unused -- and broken -- hex_encode()
9751 function. Use base16_encode() instead. (Thanks to Timo Lindfors
9752 for pointing out this bug.)
9753 - Only pick and establish intro points after we've gotten a
9755 - Fix assert triggers: if the other side returns an address 0.0.0.0,
9756 don't put it into the client dns cache.
9757 - If a begin failed due to exit policy, but we believe the IP
9758 address should have been allowed, switch that router to exitpolicy
9759 reject *:* until we get our next directory.
9762 - 'Extend' relay cell payloads now include the digest of the
9763 intended next hop's identity key. Now we can verify that we're
9764 extending to the right router, and also extend to routers we
9765 hadn't heard of before.
9768 - Tor nodes can now act as relays (with an advertised ORPort)
9769 without being manually verified by the dirserver operators.
9770 - Uploaded descriptors of unverified routers are now accepted
9771 by the dirservers, and included in the directory.
9772 - Verified routers are listed by nickname in the running-routers
9773 list; unverified routers are listed as "$<fingerprint>".
9774 - We now use hash-of-identity-key in most places rather than
9775 nickname or addr:port, for improved security/flexibility.
9776 - AllowUnverifiedNodes config option to let circuits choose no-name
9777 routers in entry,middle,exit,introduction,rendezvous positions.
9778 Allow middle and rendezvous positions by default.
9779 - When picking unverified routers, skip those with low uptime and/or
9780 low bandwidth, depending on what properties you care about.
9781 - ClientOnly option for nodes that never want to become servers.
9782 - Directory caching.
9783 - "AuthoritativeDir 1" option for the official dirservers.
9784 - Now other nodes (clients and servers) will cache the latest
9785 directory they've pulled down.
9786 - They can enable their DirPort to serve it to others.
9787 - Clients will pull down a directory from any node with an open
9788 DirPort, and check the signature/timestamp correctly.
9789 - Authoritative dirservers now fetch directories from other
9790 authdirservers, to stay better synced.
9791 - Running-routers list tells who's down also, along with noting
9792 if they're verified (listed by nickname) or unverified (listed
9794 - Allow dirservers to serve running-router list separately.
9795 This isn't used yet.
9796 - You can now fetch $DIRURL/running-routers to get just the
9797 running-routers line, not the whole descriptor list. (But
9798 clients don't use this yet.)
9799 - Clients choose nodes proportional to advertised bandwidth.
9800 - Clients avoid using nodes with low uptime as introduction points.
9801 - Handle servers with dynamic IP addresses: don't just replace
9802 options->Address with the resolved one at startup, and
9803 detect our address right before we make a routerinfo each time.
9804 - 'FascistFirewall' option to pick dirservers and ORs on specific
9805 ports; plus 'FirewallPorts' config option to tell FascistFirewall
9806 which ports are open. (Defaults to 80,443)
9807 - Try other dirservers immediately if the one you try is down. This
9808 should tolerate down dirservers better now.
9809 - ORs connect-on-demand to other ORs
9810 - If you get an extend cell to an OR you're not connected to,
9811 connect, handshake, and forward the create cell.
9812 - The authoritative dirservers stay connected to everybody,
9813 and everybody stays connected to 0.0.7 servers, but otherwise
9814 clients/servers expire unused connections after 5 minutes.
9815 - When servers get a sigint, they delay 30 seconds (refusing new
9816 connections) then exit. A second sigint causes immediate exit.
9817 - File and name management:
9818 - Look for .torrc if no CONFDIR "torrc" is found.
9819 - If no datadir is defined, then choose, make, and secure ~/.tor
9821 - If torrc not found, exitpolicy reject *:*.
9822 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
9823 - If no nickname is defined, derive default from hostname.
9824 - Rename secret key files, e.g. identity.key -> secret_id_key,
9825 to discourage people from mailing their identity key to tor-ops.
9826 - Refuse to build a circuit before the directory has arrived --
9827 it won't work anyway, since you won't know the right onion keys
9829 - Parse tor version numbers so we can do an is-newer-than check
9830 rather than an is-in-the-list check.
9831 - New socks command 'resolve', to let us shim gethostbyname()
9833 - A 'tor_resolve' script to access the socks resolve functionality.
9834 - A new socks-extensions.txt doc file to describe our
9835 interpretation and extensions to the socks protocols.
9836 - Add a ContactInfo option, which gets published in descriptor.
9837 - Write tor version at the top of each log file
9838 - New docs in the tarball:
9840 - Document that you should proxy your SSL traffic too.
9841 - Log a warning if the user uses an unsafe socks variant, so people
9842 are more likely to learn about privoxy or socat.
9843 - Log a warning if you're running an unverified server, to let you
9844 know you might want to get it verified.
9845 - Change the default exit policy to reject the default edonkey,
9846 kazaa, gnutella ports.
9847 - Add replace_file() to util.[ch] to handle win32's rename().
9848 - Publish OR uptime in descriptor (and thus in directory) too.
9849 - Remember used bandwidth (both in and out), and publish 15-minute
9850 snapshots for the past day into our descriptor.
9851 - Be more aggressive about trying to make circuits when the network
9852 has changed (e.g. when you unsuspend your laptop).
9853 - Check for time skew on http headers; report date in response to
9855 - If the entrynode config line has only one node, don't pick it as
9857 - Add strict{entry|exit}nodes config options. If set to 1, then
9858 we refuse to build circuits that don't include the specified entry
9860 - OutboundBindAddress config option, to bind to a specific
9861 IP address for outgoing connect()s.
9862 - End truncated log entries (e.g. directories) with "[truncated]".
9865 Changes in version 0.0.7.3 - 2004-08-12
9866 o Stop dnsworkers from triggering an assert failure when you
9867 ask them to resolve the host "".
9870 Changes in version 0.0.7.2 - 2004-07-07
9871 o A better fix for the 0.0.0.0 problem, that will hopefully
9872 eliminate the remaining related assertion failures.
9875 Changes in version 0.0.7.1 - 2004-07-04
9876 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
9877 since internally we use 0.0.0.0 to signify "not yet resolved".
9880 Changes in version 0.0.7 - 2004-06-07
9881 o Fixes for crashes and other obnoxious bugs:
9882 - Fix an epipe bug: sometimes when directory connections failed
9883 to connect, we would give them a chance to flush before closing
9885 - When we detached from a circuit because of resolvefailed, we
9886 would immediately try the same circuit twice more, and then
9887 give up on the resolve thinking we'd tried three different
9889 - Limit the number of intro circuits we'll attempt to build for a
9890 hidden service per 15-minute period.
9891 - Check recommended-software string *early*, before actually parsing
9892 the directory. Thus we can detect an obsolete version and exit,
9893 even if the new directory format doesn't parse.
9894 o Fixes for security bugs:
9895 - Remember which nodes are dirservers when you startup, and if a
9896 random OR enables his dirport, don't automatically assume he's
9897 a trusted dirserver.
9899 - Directory connections were asking the wrong poll socket to
9900 start writing, and not asking themselves to start writing.
9901 - When we detached from a circuit because we sent a begin but
9902 didn't get a connected, we would use it again the first time;
9903 but after that we would correctly switch to a different one.
9904 - Stop warning when the first onion decrypt attempt fails; they
9905 will sometimes legitimately fail now that we rotate keys.
9906 - Override unaligned-access-ok check when $host_cpu is ia64 or
9907 arm. Apparently they allow it but the kernel whines.
9908 - Dirservers try to reconnect periodically too, in case connections
9910 - Fix some memory leaks in directory servers.
9911 - Allow backslash in Win32 filenames.
9912 - Made Tor build complain-free on FreeBSD, hopefully without
9913 breaking other BSD builds. We'll see.
9914 - Check directory signatures based on name of signer, not on whom
9915 we got the directory from. This will let us cache directories more
9917 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
9920 - Doxygen markup on all functions and global variables.
9921 - Make directory functions update routerlist, not replace it. So
9922 now directory disagreements are not so critical a problem.
9923 - Remove the upper limit on number of descriptors in a dirserver's
9924 directory (not that we were anywhere close).
9925 - Allow multiple logfiles at different severity ranges.
9926 - Allow *BindAddress to specify ":port" rather than setting *Port
9927 separately. Allow multiple instances of each BindAddress config
9928 option, so you can bind to multiple interfaces if you want.
9929 - Allow multiple exit policy lines, which are processed in order.
9930 Now we don't need that huge line with all the commas in it.
9931 - Enable accept/reject policies on SOCKS connections, so you can bind
9932 to 0.0.0.0 but still control who can use your OP.
9933 - Updated the man page to reflect these features.
9936 Changes in version 0.0.6.2 - 2004-05-16
9937 o Our integrity-checking digest was checking only the most recent cell,
9938 not the previous cells like we'd thought.
9939 Thanks to Stefan Mark for finding the flaw!
9942 Changes in version 0.0.6.1 - 2004-05-06
9943 o Fix two bugs in our AES counter-mode implementation (this affected
9944 onion-level stream encryption, but not TLS-level). It turns
9945 out we were doing something much more akin to a 16-character
9946 polyalphabetic cipher. Oops.
9947 Thanks to Stefan Mark for finding the flaw!
9948 o Retire moria3 as a directory server, and add tor26 as a directory
9952 Changes in version 0.0.6 - 2004-05-02
9954 - Hidden services and rendezvous points are implemented. Go to
9955 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
9956 hidden services. (This only works via a socks4a proxy such as
9957 Privoxy, and currently it's quite slow.)
9958 - We now rotate link (tls context) keys and onion keys.
9959 - CREATE cells now include oaep padding, so you can tell
9960 if you decrypted them correctly.
9961 - Retry stream correctly when we fail to connect because of
9962 exit-policy-reject (should try another) or can't-resolve-address.
9963 - When we hup a dirserver and we've *removed* a server from the
9964 approved-routers list, now we remove that server from the
9965 in-memory directories too.
9966 - Add bandwidthburst to server descriptor.
9967 - Directories now say which dirserver signed them.
9968 - Use a tor_assert macro that logs failed assertions too.
9969 - Since we don't support truncateds much, don't bother sending them;
9970 just close the circ.
9971 - Fetch randomness from /dev/urandom better (not via fopen/fread)
9972 - Better debugging for tls errors
9973 - Set Content-Type on the directory and hidserv descriptor.
9974 - Remove IVs from cipher code, since AES-ctr has none.
9976 - Fix an assert trigger for exit nodes that's been plaguing us since
9977 the days of 0.0.2prexx (thanks weasel!)
9978 - Fix a bug where we were closing tls connections intermittently.
9979 It turns out openssl keeps its errors around -- so if an error
9980 happens, and you don't ask about it, and then another openssl
9981 operation happens and succeeds, and you ask if there was an error,
9982 it tells you about the first error.
9983 - Fix a bug that's been lurking since 27 may 03 (!)
9984 When passing back a destroy cell, we would use the wrong circ id.
9985 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
9986 - Some versions of openssl have an SSL_pending function that erroneously
9987 returns bytes when there is a non-application record pending.
9988 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
9989 o We were using an array of length zero in a few places.
9990 o Win32's gethostbyname can't resolve an IP to an IP.
9991 o Win32's close can't close a socket.
9992 o Handle windows socket errors correctly.
9994 - check for <sys/limits.h> so we build on FreeBSD again, and
9995 <machine/limits.h> for NetBSD.
9998 Changes in version 0.0.5 - 2004-03-30
9999 o Install torrc as torrc.sample -- we no longer clobber your
10001 o Fix mangled-state bug in directory fetching (was causing sigpipes).
10002 o Only build circuits after we've fetched the directory: clients were
10003 using only the directory servers before they'd fetched a directory.
10004 This also means longer startup time; so it goes.
10005 o Fix an assert trigger where an OP would fail to handshake, and we'd
10006 expect it to have a nickname.
10007 o Work around a tsocks bug: do a socks reject when AP connection dies
10008 early, else tsocks goes into an infinite loop.
10009 o Hold socks connection open until reply is flushed (if possible)
10010 o Make exit nodes resolve IPs to IPs immediately, rather than asking
10011 the dns farm to do it.
10012 o Fix c99 aliasing warnings in rephist.c
10013 o Don't include server descriptors that are older than 24 hours in the
10015 o Give socks 'reject' replies their whole 15s to attempt to flush,
10016 rather than seeing the 60s timeout and assuming the flush had failed.
10017 o Clean automake droppings from the cvs repository
10018 o Add in a 'notice' log level for things the operator should hear
10019 but that aren't warnings
10022 Changes in version 0.0.4 - 2004-03-26
10023 o When connecting to a dirserver or OR and the network is down,
10027 Changes in version 0.0.3 - 2004-03-26
10028 o Warn and fail if server chose a nickname with illegal characters
10029 o Port to Solaris and Sparc:
10030 - include missing header fcntl.h
10031 - have autoconf find -lsocket -lnsl automatically
10032 - deal with hardware word alignment
10033 - make uname() work (solaris has a different return convention)
10034 - switch from using signal() to sigaction()
10035 o Preliminary work on reputation system:
10036 - Keep statistics on success/fail of connect attempts; they're published
10037 by kill -USR1 currently.
10038 - Add a RunTesting option to try to learn link state by creating test
10039 circuits, even when SocksPort is off.
10040 - Remove unused open circuits when there are too many.
10043 Changes in version 0.0.2 - 2004-03-19
10044 - Include strlcpy and strlcat for safer string ops
10045 - define INADDR_NONE so we compile (but still not run) on solaris
10048 Changes in version 0.0.2pre27 - 2004-03-14
10050 - Allow internal tor networks (we were rejecting internal IPs,
10051 now we allow them if they're set explicitly).
10052 - And fix a few endian issues.
10055 Changes in version 0.0.2pre26 - 2004-03-14
10057 - If a stream times out after 15s without a connected cell, don't
10058 try that circuit again: try a new one.
10059 - Retry streams at most 4 times. Then give up.
10060 - When a dirserver gets a descriptor from an unknown router, it
10061 logs its fingerprint (so the dirserver operator can choose to
10062 accept it even without mail from the server operator).
10063 - Inform unapproved servers when we reject their descriptors.
10064 - Make tor build on Windows again. It works as a client, who knows
10066 - Clearer instructions in the torrc for how to set up a server.
10067 - Be more efficient about reading fd's when our global token bucket
10068 (used for rate limiting) becomes empty.
10070 - Stop asserting that computers always go forward in time. It's
10072 - When we sent a cell (e.g. destroy) and then marked an OR connection
10073 expired, we might close it before finishing a flush if the other
10074 side isn't reading right then.
10075 - Don't allow dirservers to start if they haven't defined
10076 RecommendedVersions
10077 - We were caching transient dns failures. Oops.
10078 - Prevent servers from publishing an internal IP as their address.
10079 - Address a strcat vulnerability in circuit.c
10082 Changes in version 0.0.2pre25 - 2004-03-04
10084 - Put the OR's IP in its router descriptor, not its fqdn. That way
10085 we'll stop being stalled by gethostbyname for nodes with flaky dns,
10088 - If the user typed in an address that didn't resolve, the server
10092 Changes in version 0.0.2pre24 - 2004-03-03
10094 - Fix an assertion failure in dns.c, where we were trying to dequeue
10095 a pending dns resolve even if it wasn't pending
10096 - Fix a spurious socks5 warning about still trying to write after the
10097 connection is finished.
10098 - Hold certain marked_for_close connections open until they're finished
10099 flushing, rather than losing bytes by closing them too early.
10100 - Correctly report the reason for ending a stream
10101 - Remove some duplicate calls to connection_mark_for_close
10102 - Put switch_id and start_daemon earlier in the boot sequence, so it
10103 will actually try to chdir() to options.DataDirectory
10104 - Make 'make test' exit(1) if a test fails; fix some unit tests
10105 - Make tor fail when you use a config option it doesn't know about,
10106 rather than warn and continue.
10107 - Make --version work
10108 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
10111 Changes in version 0.0.2pre23 - 2004-02-29
10113 - Print a statement when the first circ is finished, so the user
10114 knows it's working.
10115 - If a relay cell is unrecognized at the end of the circuit,
10116 send back a destroy. (So attacks to mutate cells are more
10118 - New config option 'excludenodes' to avoid certain nodes for circuits.
10119 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
10120 so you can collect coredumps there.
10122 - Fix a bug in tls flushing where sometimes data got wedged and
10123 didn't flush until more data got sent. Hopefully this bug was
10124 a big factor in the random delays we were seeing.
10125 - Make 'connected' cells include the resolved IP, so the client
10126 dns cache actually gets populated.
10127 - Disallow changing from ORPort=0 to ORPort>0 on hup.
10128 - When we time-out on a stream and detach from the circuit, send an
10129 end cell down it first.
10130 - Only warn about an unknown router (in exitnodes, entrynodes,
10131 excludenodes) after we've fetched a directory.
10134 Changes in version 0.0.2pre22 - 2004-02-26
10136 - Servers publish less revealing uname information in descriptors.
10137 - More memory tracking and assertions, to crash more usefully when
10139 - If the default torrc isn't there, just use some default defaults.
10140 Plus provide an internal dirservers file if they don't have one.
10141 - When the user tries to use Tor as an http proxy, give them an http
10142 501 failure explaining that we're a socks proxy.
10143 - Dump a new router.desc on hup, to help confused people who change
10144 their exit policies and then wonder why router.desc doesn't reflect
10146 - Clean up the generic tor.sh init script that we ship with.
10148 - If the exit stream is pending on the resolve, and a destroy arrives,
10149 then the stream wasn't getting removed from the pending list. I
10150 think this was the one causing recent server crashes.
10151 - Use a more robust poll on OSX 10.3, since their poll is flaky.
10152 - When it couldn't resolve any dirservers, it was useless from then on.
10153 Now it reloads the RouterFile (or default dirservers) if it has no
10155 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
10156 many users don't even *have* a /usr/local/sbin/.
10159 Changes in version 0.0.2pre21 - 2004-02-18
10161 - There's a ChangeLog file that actually reflects the changelog.
10162 - There's a 'torify' wrapper script, with an accompanying
10163 tor-tsocks.conf, that simplifies the process of using tsocks for
10164 tor. It even has a man page.
10165 - The tor binary gets installed to sbin rather than bin now.
10166 - Retry streams where the connected cell hasn't arrived in 15 seconds
10167 - Clean up exit policy handling -- get the default out of the torrc,
10168 so we can update it without forcing each server operator to fix
10170 - Allow imaps and pop3s in default exit policy
10172 - Prevent picking middleman nodes as the last node in the circuit
10175 Changes in version 0.0.2pre20 - 2004-01-30
10177 - We now have a deb package, and it's in debian unstable. Go to
10178 it, apt-getters. :)
10179 - I've split the TotalBandwidth option into BandwidthRate (how many
10180 bytes per second you want to allow, long-term) and
10181 BandwidthBurst (how many bytes you will allow at once before the cap
10182 kicks in). This better token bucket approach lets you, say, set
10183 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
10184 performance while not exceeding your monthly bandwidth quota.
10185 - Push out a tls record's worth of data once you've got it, rather
10186 than waiting until you've read everything waiting to be read. This
10187 may improve performance by pipelining better. We'll see.
10188 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
10189 from failed circuits (if they haven't been connected yet) and attach
10191 - Expire old streams that haven't managed to connect. Some day we'll
10192 have them reattach to new circuits instead.
10195 - Fix several memory leaks that were causing servers to become bloated
10197 - Fix a few very rare assert triggers. A few more remain.
10198 - Setuid to User _before_ complaining about running as root.
10201 Changes in version 0.0.2pre19 - 2004-01-07
10203 - Fix deadlock condition in dns farm. We were telling a child to die by
10204 closing the parent's file descriptor to him. But newer children were
10205 inheriting the open file descriptor from the parent, and since they
10206 weren't closing it, the socket never closed, so the child never read
10207 eof, so he never knew to exit. Similarly, dns workers were holding
10208 open other sockets, leading to all sorts of chaos.
10209 - New cleaner daemon() code for forking and backgrounding.
10210 - If you log to a file, it now prints an entry at the top of the
10211 logfile so you know it's working.
10212 - The onionskin challenge length was 30 bytes longer than necessary.
10213 - Started to patch up the spec so it's not quite so out of date.
10216 Changes in version 0.0.2pre18 - 2004-01-02
10218 - Fix endian issues with the 'integrity' field in the relay header.
10219 - Fix a potential bug where connections in state
10220 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
10223 Changes in version 0.0.2pre17 - 2003-12-30
10225 - Made --debuglogfile (or any second log file, actually) work.
10226 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
10227 adversary could force us into an infinite loop.
10230 - Each onionskin handshake now includes a hash of the computed key,
10231 to prove the server's identity and help perfect forward secrecy.
10232 - Changed cell size from 256 to 512 bytes (working toward compatibility
10234 - Changed cell length to 2 bytes, and moved it to the relay header.
10235 - Implemented end-to-end integrity checking for the payloads of
10237 - Separated streamid from 'recognized' (otherwise circuits will get
10238 messed up when we try to have streams exit from the middle). We
10239 use the integrity-checking to confirm that a cell is addressed to
10241 - Randomize the initial circid and streamid values, so an adversary who
10242 breaks into a node can't learn how many circuits or streams have
10246 Changes in version 0.0.2pre16 - 2003-12-14
10248 - Fixed a bug that made HUP trigger an assert
10249 - Fixed a bug where a circuit that immediately failed wasn't being
10250 counted as a failed circuit in counting retries.
10253 - Now we close the circuit when we get a truncated cell: otherwise we're
10254 open to an anonymity attack where a bad node in the path truncates
10255 the circuit and then we open streams at him.
10256 - Add port ranges to exit policies
10257 - Add a conservative default exit policy
10258 - Warn if you're running tor as root
10259 - on HUP, retry OR connections and close/rebind listeners
10260 - options.EntryNodes: try these nodes first when picking the first node
10261 - options.ExitNodes: if your best choices happen to include any of
10262 your preferred exit nodes, you choose among just those preferred
10264 - options.ExcludedNodes: nodes that are never picked in path building
10267 Changes in version 0.0.2pre15 - 2003-12-03
10268 o Robustness and bugfixes:
10269 - Sometimes clients would cache incorrect DNS resolves, which would
10270 really screw things up.
10271 - An OP that goes offline would slowly leak all its sockets and stop
10273 - A wide variety of bugfixes in exit node selection, exit policy
10274 handling, and processing pending streams when a new circuit is
10276 - Pick nodes for a path only from those the directory says are up
10277 - Choose randomly from all running dirservers, not always the first one
10278 - Increase allowed http header size for directory fetch.
10279 - Stop writing to stderr (if we're daemonized it will be closed).
10280 - Enable -g always, so cores will be more useful to me.
10281 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
10284 - Wrote a man page. It lists commonly used options.
10287 - Change default loglevel to warn.
10288 - Make PidFile default to null rather than littering in your CWD.
10289 - OnionRouter config option is now obsolete. Instead it just checks
10291 - Moved to a single unified torrc file for both clients and servers.
10294 Changes in version 0.0.2pre14 - 2003-11-29
10295 o Robustness and bugfixes:
10296 - Force the admin to make the DataDirectory himself
10297 - to get ownership/permissions right
10298 - so clients no longer make a DataDirectory and then never use it
10299 - fix bug where a client who was offline for 45 minutes would never
10300 pull down a directory again
10301 - fix (or at least hide really well) the dns assert bug that was
10302 causing server crashes
10303 - warnings and improved robustness wrt clockskew for certs
10304 - use the native daemon(3) to daemonize, when available
10305 - exit if bind() fails
10306 - exit if neither socksport nor orport is defined
10307 - include our own tor_timegm (Win32 doesn't have its own)
10308 - bugfix for win32 with lots of connections
10309 - fix minor bias in PRNG
10310 - make dirserver more robust to corrupt cached directory
10313 - Wrote the design document (woo)
10315 o Circuit building and exit policies:
10316 - Circuits no longer try to use nodes that the directory has told them
10318 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
10319 bitcounts (18.0.0.0/8).
10320 - Make AP connections standby for a circuit if no suitable circuit
10321 exists, rather than failing
10322 - Circuits choose exit node based on addr/port, exit policies, and
10323 which AP connections are standing by
10324 - Bump min pathlen from 2 to 3
10325 - Relay end cells have a payload to describe why the stream ended.
10326 - If the stream failed because of exit policy, try again with a new
10328 - Clients have a dns cache to remember resolved addresses.
10329 - Notice more quickly when we have no working circuits
10332 - APPort is now called SocksPort
10333 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
10335 - RecommendedVersions is now a config variable rather than
10336 hardcoded (for dirservers)
10337 - Reloads config on HUP
10338 - Usage info on -h or --help
10339 - If you set User and Group config vars, it'll setu/gid to them.
10341 Changes in version 0.0.2pre13 - 2003-10-19
10342 o General stability:
10343 - SSL_write no longer fails when it returns WANTWRITE and the number
10344 of bytes in the buf has changed by the next SSL_write call.
10345 - Fix segfault fetching directory when network is down
10346 - Fix a variety of minor memory leaks
10347 - Dirservers reload the fingerprints file on HUP, so I don't have
10348 to take down the network when I approve a new router
10349 - Default server config file has explicit Address line to specify fqdn
10352 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
10353 - Make listener connections not ever alloc bufs
10355 o Autoconf improvements:
10356 - don't clobber an external CFLAGS in ./configure
10357 - Make install now works
10358 - create var/lib/tor on make install
10359 - autocreate a tor.sh initscript to help distribs
10360 - autocreate the torrc and sample-server-torrc with correct paths
10362 o Log files and Daemonizing now work:
10363 - If --DebugLogFile is specified, log to it at -l debug
10364 - If --LogFile is specified, use it instead of commandline
10365 - If --RunAsDaemon is set, tor forks and backgrounds on startup