1 Changes in version 0.2.5.5-alpha - 2014-05-??
4 Changes in version 0.2.4.22 - 2014-05-16
5 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
6 alpha release series. These include blocking all authority signing
7 keys that may have been affected by the OpenSSL "heartbleed" bug,
8 choosing a far more secure set of TLS ciphersuites by default, closing
9 a couple of memory leaks that could be used to run a target relay out
10 of RAM, and several others.
12 o Major features (security, backport from 0.2.5.4-alpha):
13 - Block authority signing keys that were used on authorities
14 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15 don't have any evidence that these keys _were_ compromised; we're
16 doing this to be prudent.) Resolves ticket 11464.
18 o Major bugfixes (security, OOM):
19 - Fix a memory leak that could occur if a microdescriptor parse
20 fails during the tokenizing step. This bug could enable a memory
21 exhaustion attack by directory servers. Fixes bug 11649; bugfix
24 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
25 - The relay ciphersuite list is now generated automatically based on
26 uniform criteria, and includes all OpenSSL ciphersuites with
27 acceptable strength and forward secrecy. Previously, we had left
28 some perfectly fine ciphersuites unsupported due to omission or
29 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
30 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
31 - Relays now trust themselves to have a better view than clients of
32 which TLS ciphersuites are better than others. (Thanks to bug
33 11513, the relay list is now well-considered, whereas the client
34 list has been chosen mainly for anti-fingerprinting purposes.)
35 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
36 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
37 AES128. Resolves ticket 11528.
38 - Clients now try to advertise the same list of ciphersuites as
39 Firefox 28. This change enables selection of (fast) GCM
40 ciphersuites, disables some strange old ciphers, and stops
41 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
42 Resolves ticket 11438.
44 o Minor bugfixes (configuration, security):
45 - When running a hidden service, do not allow TunneledDirConns 0:
46 trying to set that option together with a hidden service would
47 otherwise prevent the hidden service from running, and also make
48 it publish its descriptors directly over HTTP. Fixes bug 10849;
49 bugfix on 0.2.1.1-alpha.
51 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
52 - Avoid sending a garbage value to the controller when a circuit is
53 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
55 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
56 - Stop leaking memory when we successfully resolve a PTR record.
57 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
59 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
60 - Avoid 60-second delays in the bootstrapping process when Tor is
61 launching for a second time while using bridges. Fixes bug 9229;
62 bugfix on 0.2.0.3-alpha.
64 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
65 - Give the correct URL in the warning message when trying to run a
66 relay on an ancient version of Windows. Fixes bug 9393.
68 o Minor bugfixes (compilation):
69 - Fix a compilation error when compiling with --disable-curve25519.
70 Fixes bug 9700; bugfix on 0.2.4.17-rc.
73 - Downgrade the warning severity for the the "md was still
74 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
75 for trying to diagnose this bug, and the current warning in
76 earlier versions of tor achieves nothing useful. Addresses warning
79 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
80 - When we run out of usable circuit IDs on a channel, log only one
81 warning for the whole channel, and describe how many circuits
82 there were on the channel. Fixes part of ticket 11553.
84 o Minor features (security, backport from 0.2.5.4-alpha):
85 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
86 leave the default at 8GBytes), to better support Raspberry Pi
87 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
89 o Documentation (backport from 0.2.5.4-alpha):
90 - Correctly document that we search for a system torrc file before
91 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
95 Changes in version 0.2.5.4-alpha - 2014-04-25
96 Tor 0.2.5.4-alpha includes several security and performance
97 improvements for clients and relays, including blacklisting authority
98 signing keys that were used while susceptible to the OpenSSL
99 "heartbleed" bug, fixing two expensive functions on busy relays,
100 improved TLS ciphersuite preference lists, support for run-time
101 hardening on compilers that support AddressSanitizer, and more work on
102 the Linux sandbox code.
104 There are also several usability fixes for clients (especially clients
105 that use bridges), two new TransPort protocols supported (one on
106 OpenBSD, one on FreeBSD), and various other bugfixes.
108 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
109 have accumulated many known flaws; everyone should upgrade.
111 o Major features (security):
112 - If you don't specify MaxMemInQueues yourself, Tor now tries to
113 pick a good value based on your total system memory. Previously,
114 the default was always 8 GB. You can still override the default by
115 setting MaxMemInQueues yourself. Resolves ticket 11396.
116 - Block authority signing keys that were used on authorities
117 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
118 don't have any evidence that these keys _were_ compromised; we're
119 doing this to be prudent.) Resolves ticket 11464.
121 o Major features (relay performance):
122 - Speed up server-side lookups of rendezvous and introduction point
123 circuits by using hashtables instead of linear searches. These
124 functions previously accounted between 3 and 7% of CPU usage on
125 some busy relays. Resolves ticket 9841.
126 - Avoid wasting CPU when extending a circuit over a channel that is
127 nearly out of circuit IDs. Previously, we would do a linear scan
128 over possible circuit IDs before finding one or deciding that we
129 had exhausted our possibilities. Now, we try at most 64 random
130 circuit IDs before deciding that we probably won't succeed. Fixes
131 a possible root cause of ticket 11553.
133 o Major features (seccomp2 sandbox, Linux only):
134 - The seccomp2 sandbox can now run a test network for multiple hours
135 without crashing. The sandbox is still experimental, and more bugs
136 will probably turn up. To try it, enable "Sandbox 1" on a Linux
137 host. Resolves ticket 11351.
138 - Strengthen sandbox code: the sandbox can now test the arguments
139 for rename(), and blocks _sysctl() entirely. Resolves another part
141 - When the sandbox blocks a system call, it now tries to log a stack
142 trace before exiting. Resolves ticket 11465.
144 o Major bugfixes (TLS cipher selection):
145 - The relay ciphersuite list is now generated automatically based on
146 uniform criteria, and includes all OpenSSL ciphersuites with
147 acceptable strength and forward secrecy. Previously, we had left
148 some perfectly fine ciphersuites unsupported due to omission or
149 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
150 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
151 - Relays now trust themselves to have a better view than clients of
152 which TLS ciphersuites are better than others. (Thanks to bug
153 11513, the relay list is now well-considered, whereas the client
154 list has been chosen mainly for anti-fingerprinting purposes.)
155 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
156 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
157 AES128. Resolves ticket 11528.
158 - Clients now try to advertise the same list of ciphersuites as
159 Firefox 28. This change enables selection of (fast) GCM
160 ciphersuites, disables some strange old ciphers, and stops
161 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
162 Resolves ticket 11438.
164 o Major bugfixes (bridge client):
165 - Avoid 60-second delays in the bootstrapping process when Tor is
166 launching for a second time while using bridges. Fixes bug 9229;
167 bugfix on 0.2.0.3-alpha.
169 o Minor features (transparent proxy, *BSD):
170 - Support FreeBSD's ipfw firewall interface for TransPort ports on
171 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
172 10267; patch from "yurivict".
173 - Support OpenBSD's divert-to rules with the pf firewall for
174 transparent proxy ports. To enable it, set "TransProxyType
175 pf-divert". This allows Tor to run a TransPort transparent proxy
176 port on OpenBSD 4.4 or later without root privileges. See the
177 pf.conf(5) manual page for information on configuring pf to use
178 divert-to rules. Closes ticket 10896; patch from Dana Koch.
180 o Minor features (security):
181 - New --enable-expensive-hardening option to enable security
182 hardening options that consume nontrivial amounts of CPU and
183 memory. Right now, this includes AddressSanitizer and UbSan, which
184 are supported in newer versions of GCC and Clang. Closes ticket
187 o Minor features (log verbosity):
188 - Demote the message that we give when a flushing connection times
189 out for too long from NOTICE to INFO. It was usually meaningless.
190 Resolves ticket 5286.
191 - Don't log so many notice-level bootstrapping messages at startup
192 about downloading descriptors. Previously, we'd log a notice
193 whenever we learned about more routers. Now, we only log a notice
194 at every 5% of progress. Fixes bug 9963.
195 - Warn less verbosely when receiving a malformed
196 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
197 - When we run out of usable circuit IDs on a channel, log only one
198 warning for the whole channel, and describe how many circuits
199 there were on the channel. Fixes part of ticket 11553.
201 o Minor features (relay):
202 - If a circuit timed out for at least 3 minutes, check if we have a
203 new external IP address, and publish a new descriptor with the new
204 IP address if it changed. Resolves ticket 2454.
206 o Minor features (controller):
207 - Make the entire exit policy available from the control port via
208 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
210 - Because of the fix for ticket 11396, the real limit for memory
211 usage may no longer match the configured MaxMemInQueues value. The
212 real limit is now exposed via GETINFO limits/max-mem-in-queues.
214 o Minor features (bridge client):
215 - Report a more useful failure message when we can't connect to a
216 bridge because we don't have the right pluggable transport
217 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
219 o Minor features (diagnostic):
220 - Add more log messages to diagnose bug 7164, which causes
221 intermittent "microdesc_free() called but md was still referenced"
222 warnings. We now include more information, to figure out why we
223 might be cleaning a microdescriptor for being too old if it's
224 still referenced by a live node_t object.
226 o Minor bugfixes (client, DNSPort):
227 - When using DNSPort, try to respond to AAAA requests with AAAA
228 answers. Previously, we hadn't looked at the request type when
229 deciding which answer type to prefer. Fixes bug 10468; bugfix on
231 - When receiving a DNS query for an unsupported record type, reply
232 with no answer rather than with a NOTIMPL error. This behavior
233 isn't correct either, but it will break fewer client programs, we
234 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
237 o Minor bugfixes (exit relay):
238 - Stop leaking memory when we successfully resolve a PTR record.
239 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
241 o Minor bugfixes (bridge client):
242 - Stop accepting bridge lines containing hostnames. Doing so would
243 cause clients to perform DNS requests on the hostnames, which was
244 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
245 - Avoid a 60-second delay in the bootstrapping process when a Tor
246 client with pluggable transports re-reads its configuration at
247 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
249 o Minor bugfixes (client, logging during bootstrap):
250 - Warn only once if we start logging in an unsafe way. Previously,
251 we complain as many times as we had problems. Fixes bug 9870;
252 bugfix on 0.2.5.1-alpha.
253 - Only report the first fatal bootstrap error on a given OR
254 connection. This stops us from telling the controller bogus error
255 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
256 - Be more helpful when trying to run sandboxed on Linux without
257 libseccomp. Instead of saying "Sandbox is not implemented on this
258 platform", we now explain that we need to be built with
259 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
260 - Avoid generating spurious warnings when starting with
261 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
264 o Minor bugfixes (closing OR connections):
265 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
266 check if it's an or_connection_t and correctly call
267 connection_or_close_for_error() rather than
268 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
270 - When closing all connections on setting DisableNetwork to 1, use
271 connection_or_close_normally() rather than closing OR connections
272 out from under the channel layer. Fixes bug 11306; bugfix on
275 o Minor bugfixes (controller):
276 - Avoid sending a garbage value to the controller when a circuit is
277 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
279 o Minor bugfixes (tor-fw-helper):
280 - Allow tor-fw-helper to build again by adding src/ext to its
281 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
283 o Minor bugfixes (bridges):
284 - Avoid potential crashes or bad behavior when launching a
285 server-side managed proxy with ORPort or ExtORPort temporarily
286 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
288 o Minor bugfixes (platform-specific):
289 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
290 bug 11426; bugfix on 0.2.5.3-alpha.
291 - When dumping a malformed directory object to disk, save it in
292 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
294 - Don't report failures from make_socket_reuseable() on incoming
295 sockets on OSX: this can happen when incoming connections close
296 early. Fixes bug 10081.
298 o Minor bugfixes (trivial memory leaks):
299 - Fix a small memory leak when signing a directory object. Fixes bug
300 11275; bugfix on 0.2.4.13-alpha.
301 - Free placeholder entries in our circuit table at exit; fixes a
302 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
303 - Don't re-initialize a second set of OpenSSL mutexes when starting
304 up. Previously, we'd make one set of mutexes, and then immediately
305 replace them with another. Fixes bug 11726; bugfix on
307 - Resolve some memory leaks found by coverity in the unit tests, on
308 exit in tor-gencert, and on a failure to compute digests for our
309 own keys when generating a v3 networkstatus vote. These leaks
310 should never have affected anyone in practice.
312 o Minor bugfixes (hidden service):
313 - Only retry attempts to connect to a chosen rendezvous point 8
314 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
316 o Minor bugfixes (misc code correctness):
317 - Fix various instances of undefined behavior in channeltls.c,
318 tor_memmem(), and eventdns.c that would cause us to construct
319 pointers to memory outside an allocated object. (These invalid
320 pointers were not accessed, but C does not even allow them to
321 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
322 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
323 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
324 fix some miscellaneous errors in our tests and codebase. Fixes bug
325 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
326 - Always check return values for unlink, munmap, UnmapViewOfFile;
327 check strftime return values more often. In some cases all we can
328 do is report a warning, but this may help prevent deeper bugs from
329 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
331 - Fix numerous warnings from the clang "scan-build" static analyzer.
332 Some of these are programming style issues; some of them are false
333 positives that indicated awkward code; some are undefined behavior
334 cases related to constructing (but not using) invalid pointers;
335 some are assumptions about API behavior; some are (harmlessly)
336 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
337 correct; and one or two are genuine bugs that weren't reachable
338 from the rest of the program. Fixes bug 8793; bugfixes on many,
342 - Build the torify.1 manpage again. Previously, we were only trying
343 to build it when also building tor-fw-helper. That's why we didn't
344 notice that we'd broken the ability to build it. Fixes bug 11321;
345 bugfix on 0.2.5.1-alpha.
346 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
347 11061; bugfix on 0.2.4.7-alpha.
348 - Correctly document that we search for a system torrc file before
349 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
351 - Resolve warnings from Doxygen.
353 o Code simplifications and refactoring:
354 - Remove is_internal_IP() function. Resolves ticket 4645.
355 - Remove unused function circuit_dump_by_chan from circuitlist.c.
356 Closes issue 9107; patch from "marek".
357 - Change our use of the ENUM_BF macro to avoid declarations that
360 o Deprecated versions:
361 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
362 attention for some while. Directory authorities no longer accept
363 descriptors from relays running any version of Tor prior to Tor
364 0.2.3.16-alpha. Resolves ticket 11149.
367 - New macros in test.h to simplify writing mock-functions for unit
368 tests. Part of ticket 11507. Patch from Dana Koch.
369 - Complete tests for the status.c module. Resolves ticket 11507.
370 Patch from Dana Koch.
373 - Remove all code for the long unused v1 directory protocol.
374 Resolves ticket 11070.
377 Changes in version 0.2.5.3-alpha - 2014-03-22
378 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
379 two new anti-DoS features for Tor relays, resolves a bug that kept
380 SOCKS5 support for IPv6 from working, fixes several annoying usability
381 issues for bridge users, and removes more old code for unused
384 The Tor 0.2.5.x release series is now in patch-freeze: no feature
385 patches not already written will be considered for inclusion in 0.2.5.x.
387 o Major features (relay security, DoS-resistance):
388 - When deciding whether we have run out of memory and we need to
389 close circuits, also consider memory allocated in buffers for
390 streams attached to each circuit.
392 This change, which extends an anti-DoS feature introduced in
393 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
394 better resist more memory-based DoS attacks than before. Since the
395 MaxMemInCellQueues option now applies to all queues, it is renamed
396 to MaxMemInQueues. This feature fixes bug 10169.
397 - Avoid hash-flooding denial-of-service attacks by using the secure
398 SipHash-2-4 hash function for our hashtables. Without this
399 feature, an attacker could degrade performance of a targeted
400 client or server by flooding their data structures with a large
401 number of entries to be stored at the same hash table position,
402 thereby slowing down the Tor instance. With this feature, hash
403 table positions are derived from a randomized cryptographic key,
404 and an attacker cannot predict which entries will collide. Closes
406 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
407 the default at 8GBytes), to better support Raspberry Pi users. Fixes
408 bug 9686; bugfix on 0.2.4.14-alpha.
410 o Minor features (bridges, pluggable transports):
411 - Bridges now write the SHA1 digest of their identity key
412 fingerprint (that is, a hash of a hash of their public key) to
413 notice-level logs, and to a new hashed-fingerprint file. This
414 information will help bridge operators look up their bridge in
415 Globe and similar tools. Resolves ticket 10884.
416 - Improve the message that Tor displays when running as a bridge
417 using pluggable transports without an Extended ORPort listener.
418 Also, log the message in the log file too. Resolves ticket 11043.
420 o Minor features (other):
421 - Add a new option, PredictedPortsRelevanceTime, to control how long
422 after having received a request to connect to a given port Tor
423 will try to keep circuits ready in anticipation of future requests
424 for that port. Patch from "unixninja92"; implements ticket 9176.
425 - Generate a warning if any ports are listed in the SocksPolicy,
426 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
427 AuthDirBadExit options. (These options only support address
428 ranges.) Fixes part of ticket 11108.
429 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
432 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
433 - Build without warnings under clang 3.4. (We have some macros that
434 define static functions only some of which will get used later in
435 the module. Starting with clang 3.4, these give a warning unless the
436 unused attribute is set on them.) Resolves ticket 10904.
437 - Fix build warnings about missing "a2x" comment when building the
438 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
439 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
441 o Minor bugfixes (client):
442 - Improve the log message when we can't connect to a hidden service
443 because all of the hidden service directory nodes hosting its
444 descriptor are excluded. Improves on our fix for bug 10722, which
445 was a bugfix on 0.2.0.10-alpha.
446 - Raise a control port warning when we fail to connect to all of
447 our bridges. Previously, we didn't inform the controller, and
448 the bootstrap process would stall. Fixes bug 11069; bugfix on
450 - Exit immediately when a process-owning controller exits.
451 Previously, tor relays would wait for a little while after their
452 controller exited, as if they had gotten an INT signal -- but this
453 was problematic, since there was no feedback for the user. To do a
454 clean shutdown, controllers should send an INT signal and give Tor
455 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
456 - Stop attempting to connect to bridges before our pluggable
457 transports are configured (harmless but resulted in some erroneous
458 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
459 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
460 generating incorrect SOCKS5 responses, and confusing client
461 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
463 o Minor bugfixes (relays and bridges):
464 - Avoid crashing on a malformed resolv.conf file when running a
465 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
466 - Non-exit relays no longer launch mock DNS requests to check for
467 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
468 non-exit relays stopped servicing DNS requests. Fixes bug 965;
469 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
470 - Bridges now report complete directory request statistics. Related
471 to bug 5824; bugfix on 0.2.2.1-alpha.
472 - Bridges now never collect statistics that were designed for
473 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
474 - Stop giving annoying warning messages when we decide not to launch
475 a pluggable transport proxy that we don't need (because there are
476 no bridges configured to use it). Resolves ticket 5018; bugfix
478 - Give the correct URL in the warning message when trying to run a
479 relay on an ancient version of Windows. Fixes bug 9393.
481 o Minor bugfixes (backtrace support):
482 - Support automatic backtraces on more platforms by using the
483 "-fasynchronous-unwind-tables" compiler option. This option is
484 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
485 is on by default and table generation is not. This doesn't yet
486 add Windows support; only Linux, OSX, and some BSDs are affected.
487 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
488 - Avoid strange behavior if two threads hit failed assertions at the
489 same time and both try to log backtraces at once. (Previously, if
490 this had happened, both threads would have stored their intermediate
491 results in the same buffer, and generated junk outputs.) Reported by
492 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
493 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
494 0.2.5.2-alpha; patch from Nick Hopper.
496 o Minor bugfixes (unit tests):
497 - Fix a small bug in the unit tests that might have made the tests
498 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
499 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
502 - Remove all remaining code related to version-0 hidden service
503 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
504 the rest of bug 10841.
507 - Document in the manpage that "KBytes" may also be written as
508 "kilobytes" or "KB", that "Kbits" may also be written as
509 "kilobits", and so forth. Closes ticket 9222.
510 - Document that the ClientOnly config option overrides ORPort.
511 Our old explanation made ClientOnly sound as though it did
512 nothing at all. Resolves bug 9059.
513 - Explain that SocksPolicy, DirPolicy, and similar options don't
514 take port arguments. Fixes the other part of ticket 11108.
515 - Fix a comment about the rend_server_descriptor_t.protocols field
516 to more accurately describe its range. Also, make that field
517 unsigned, to more accurately reflect its usage. Fixes bug 9099;
518 bugfix on 0.2.1.5-alpha.
519 - Fix the manpage's description of HiddenServiceAuthorizeClient:
520 the maximum client name length is 16, not 19. Fixes bug 11118;
521 bugfix on 0.2.1.6-alpha.
523 o Code simplifications and refactoring:
524 - Get rid of router->address, since in all cases it was just the
525 string representation of router->addr. Resolves ticket 5528.
527 o Test infrastructure:
528 - Update to the latest version of tinytest.
529 - Improve the tinytest implementation of string operation tests so
530 that comparisons with NULL strings no longer crash the tests; they
531 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
534 Changes in version 0.2.4.21 - 2014-02-28
535 Tor 0.2.4.21 further improves security against potential adversaries who
536 find breaking 1024-bit crypto doable, and backports several stability
537 and robustness patches from the 0.2.5 branch.
539 o Major features (client security):
540 - When we choose a path for a 3-hop circuit, make sure it contains
541 at least one relay that supports the NTor circuit extension
542 handshake. Otherwise, there is a chance that we're building
543 a circuit that's worth attacking by an adversary who finds
544 breaking 1024-bit crypto doable, and that chance changes the game
545 theory. Implements ticket 9777.
548 - Do not treat streams that fail with reason
549 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
550 since it could also indicate an ENETUNREACH connection error. Fixes
551 part of bug 10777; bugfix on 0.2.4.8-alpha.
553 o Code simplification and refactoring:
554 - Remove data structures which were introduced to implement the
555 CellStatistics option: they are now redundant with the new timestamp
556 field in the regular packed_cell_t data structure, which we did
557 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
560 - Always clear OpenSSL bignums before freeing them -- even bignums
561 that don't contain secrets. Resolves ticket 10793. Patch by
563 - Build without warnings under clang 3.4. (We have some macros that
564 define static functions only some of which will get used later in
565 the module. Starting with clang 3.4, these give a warning unless the
566 unused attribute is set on them.) Resolves ticket 10904.
567 - Update geoip and geoip6 files to the February 7 2014 Maxmind
568 GeoLite2 Country database.
571 - Set the listen() backlog limit to the largest actually supported
572 on the system, not to the value in a header file. Fixes bug 9716;
573 bugfix on every released Tor.
574 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
575 exit node as a NOROUTE error, not an INTERNAL error, since they
576 can apparently happen when trying to connect to the wrong sort
577 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
578 - Fix build warnings about missing "a2x" comment when building the
579 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
580 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
581 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
582 not entirely remove it from the connection lists. Fixes bug 9602;
583 bugfix on 0.2.4.4-alpha.
584 - Fix a segmentation fault in our benchmark code when running with
585 Fedora's OpenSSL package, or any other OpenSSL that provides
586 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
587 - Turn "circuit handshake stats since last time" log messages into a
588 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
590 o Documentation fixes:
591 - Document that all but one DirPort entry must have the NoAdvertise
592 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
595 Changes in version 0.2.5.2-alpha - 2014-02-13
596 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
597 like the "poor random number generation" fix and the "building too many
598 circuits" fix. It also further improves security against potential
599 adversaries who find breaking 1024-bit crypto doable, and launches
600 pluggable transports on demand (which gets us closer to integrating
601 pluggable transport support by default -- not to be confused with Tor
602 bundles enabling pluggable transports and bridges by default).
604 o Major features (client security):
605 - When we choose a path for a 3-hop circuit, make sure it contains
606 at least one relay that supports the NTor circuit extension
607 handshake. Otherwise, there is a chance that we're building
608 a circuit that's worth attacking by an adversary who finds
609 breaking 1024-bit crypto doable, and that chance changes the game
610 theory. Implements ticket 9777.
611 - Clients now look at the "usecreatefast" consensus parameter to
612 decide whether to use CREATE_FAST or CREATE cells for the first hop
613 of their circuit. This approach can improve security on connections
614 where Tor's circuit handshake is stronger than the available TLS
615 connection security levels, but the tradeoff is more computational
616 load on guard relays. Implements proposal 221. Resolves ticket 9386.
618 o Major features (bridges):
619 - Don't launch pluggable transport proxies if we don't have any
620 bridges configured that would use them. Now we can list many
621 pluggable transports, and Tor will dynamically start one when it
622 hears a bridge address that needs it. Resolves ticket 5018.
623 - The bridge directory authority now assigns status flags (Stable,
624 Guard, etc) to bridges based on thresholds calculated over all
625 Running bridges. Now bridgedb can finally make use of its features
626 to e.g. include at least one Stable bridge in its answers. Fixes
629 o Major features (other):
630 - Extend ORCONN controller event to include an "ID" parameter,
631 and add four new controller event types CONN_BW, CIRC_BW,
632 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
633 The new events are emitted in private Tor networks only, with the
634 goal of being able to better track performance and load during
635 full-network simulations. Implements proposal 218 and ticket 7359.
636 - On some platforms (currently: recent OSX versions, glibc-based
637 platforms that support the ELF format, and a few other
638 Unix-like operating systems), Tor can now dump stack traces
639 when a crash occurs or an assertion fails. By default, traces
640 are dumped to stderr (if possible) and to any logs that are
641 reporting errors. Implements ticket 9299.
644 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
645 not entirely remove it from the connection lists. Fixes bug 9602;
646 bugfix on 0.2.4.4-alpha.
647 - Do not treat streams that fail with reason
648 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
649 since it could also indicate an ENETUNREACH connection error. Fixes
650 part of bug 10777; bugfix on 0.2.4.8-alpha.
652 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
653 - Do not allow OpenSSL engines to replace the PRNG, even when
654 HardwareAccel is set. The only default builtin PRNG engine uses
655 the Intel RDRAND instruction to replace the entire PRNG, and
656 ignores all attempts to seed it with more entropy. That's
657 cryptographically stupid: the right response to a new alleged
658 entropy source is never to discard all previously used entropy
659 sources. Fixes bug 10402; works around behavior introduced in
660 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
662 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
663 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
664 - Avoid launching spurious extra circuits when a stream is pending.
665 This fixes a bug where any circuit that _wasn't_ unusable for new
666 streams would be treated as if it were, causing extra circuits to
667 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
669 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
670 - No longer stop reading or writing on cpuworker connections when
671 our rate limiting buckets go empty. Now we should handle circuit
672 handshake requests more promptly. Resolves bug 9731.
673 - Stop trying to bootstrap all our directory information from
674 only our first guard. Discovered while fixing bug 9946; bugfix
677 o Minor features (bridges, pluggable transports):
678 - Add threshold cutoffs to the networkstatus document created by
679 the Bridge Authority. Fixes bug 1117.
680 - On Windows, spawn background processes using the CREATE_NO_WINDOW
681 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
682 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
683 Vidalia set this option for us.) Implements ticket 10297.
685 o Minor features (security):
686 - Always clear OpenSSL bignums before freeing them -- even bignums
687 that don't contain secrets. Resolves ticket 10793. Patch by
690 o Minor features (config options and command line):
691 - Add an --allow-missing-torrc commandline option that tells Tor to
692 run even if the configuration file specified by -f is not available.
693 Implements ticket 10060.
694 - Add support for the TPROXY transparent proxying facility on Linux.
695 See documentation for the new TransProxyType option for more
696 details. Implementation by "thomo". Closes ticket 10582.
698 o Minor features (controller):
699 - Add a new "HS_DESC" controller event that reports activities
700 related to hidden service descriptors. Resolves ticket 8510.
701 - New "DROPGUARDS" controller command to forget all current entry
702 guards. Not recommended for ordinary use, since replacing guards
703 too frequently makes several attacks easier. Resolves ticket 9934;
706 o Minor features (build):
707 - Assume that a user using ./configure --host wants to cross-compile,
708 and give an error if we cannot find a properly named
709 tool-chain. Add a --disable-tool-name-check option to proceed
710 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
711 - If we run ./configure and the compiler recognizes -fstack-protector
712 but the linker rejects it, warn the user about a potentially missing
713 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
715 o Minor features (testing):
716 - If Python is installed, "make check" now runs extra tests beyond
717 the unit test scripts.
718 - When bootstrapping a test network, sometimes very few relays get
719 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
720 specify a set of relays which should be voted Guard regardless of
721 their uptime or bandwidth. Addresses ticket 9206.
723 o Minor features (log messages):
724 - When ServerTransportPlugin is set on a bridge, Tor can write more
725 useful statistics about bridge use in its extrainfo descriptors,
726 but only if the Extended ORPort ("ExtORPort") is set too. Add a
727 log message to inform the user in this case. Resolves ticket 9651.
728 - When receiving a new controller connection, log the origin address.
729 Resolves ticket 9698; patch from "sigpipe".
730 - When logging OpenSSL engine status at startup, log the status of
731 more engines. Fixes ticket 10043; patch from Joshua Datko.
732 - Turn "circuit handshake stats since last time" log messages into a
733 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
735 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
736 - Improve the circuit queue out-of-memory handler. Previously, when
737 we ran low on memory, we'd close whichever circuits had the most
738 queued cells. Now, we close those that have the *oldest* queued
739 cells, on the theory that those are most responsible for us
740 running low on memory. Based on analysis from a forthcoming paper
741 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
742 - Generate bootstrapping status update events correctly when fetching
743 microdescriptors. Fixes bug 9927.
744 - Update to the October 2 2013 Maxmind GeoLite Country database.
746 o Minor bugfixes (clients):
747 - When closing a channel that has already been open, do not close
748 pending circuits that were waiting to connect to the same relay.
749 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
752 o Minor bugfixes (relays):
753 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
754 exit node as a NOROUTE error, not an INTERNAL error, since they
755 can apparently happen when trying to connect to the wrong sort
756 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
758 o Minor bugfixes (bridges):
759 - Fix a bug where the first connection works to a bridge that uses a
760 pluggable transport with client-side parameters, but we don't send
761 the client-side parameters on subsequent connections. (We don't
762 use any pluggable transports with client-side parameters yet,
763 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
764 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
766 o Minor bugfixes (node selection):
767 - If ExcludeNodes is set, consider non-excluded hidden service
768 directory servers before excluded ones. Do not consider excluded
769 hidden service directory servers at all if StrictNodes is
770 set. (Previously, we would sometimes decide to connect to those
771 servers, and then realize before we initiated a connection that
772 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
774 - If we set the ExitNodes option but it doesn't include any nodes
775 that have the Exit flag, we would choose not to bootstrap. Now we
776 bootstrap so long as ExitNodes includes nodes which can exit to
777 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
779 o Minor bugfixes (controller and command-line):
780 - If changing a config option via "setconf" fails in a recoverable
781 way, we used to nonetheless write our new control ports to the
782 file described by the "ControlPortWriteToFile" option. Now we only
783 write out that file if we successfully switch to the new config
784 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
785 - When a command-line option such as --version or --help that
786 ordinarily implies --hush appears on the command line along with
787 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
788 only if it appeared later on the command line. Fixes bug 9578;
789 bugfix on 0.2.5.1-alpha.
791 o Minor bugfixes (code correctness):
792 - Previously we used two temporary files when writing descriptors to
793 disk; now we only use one. Fixes bug 1376.
794 - Remove an erroneous (but impossible and thus harmless) pointer
795 comparison that would have allowed compilers to skip a bounds
796 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
797 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
798 - Fix an always-true assertion in pluggable transports code so it
799 actually checks what it was trying to check. Fixes bug 10046;
800 bugfix on 0.2.3.9-alpha. Found by "dcb".
802 o Minor bugfixes (protocol correctness):
803 - When receiving a VERSIONS cell with an odd number of bytes, close
804 the connection immediately since the cell is malformed. Fixes bug
805 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
808 o Minor bugfixes (build):
809 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
810 turned off (that is, without support for v2 link handshakes). Fixes
811 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
812 - Fix compilation warnings and startup issues when running with
813 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
815 - Fix compilation on Solaris 9, which didn't like us having an
816 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
818 o Minor bugfixes (testing):
819 - Fix a segmentation fault in our benchmark code when running with
820 Fedora's OpenSSL package, or any other OpenSSL that provides
821 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
823 o Minor bugfixes (log messages):
824 - Fix a bug where clients using bridges would report themselves
825 as 50% bootstrapped even without a live consensus document.
826 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
827 - Suppress a warning where, if there's only one directory authority
828 in the network, we would complain that votes and signatures cannot
829 be uploaded to other directory authorities. Fixes bug 10842;
830 bugfix on 0.2.2.26-beta.
831 - Report bootstrapping progress correctly when we're downloading
832 microdescriptors. We had updated our "do we have enough microdescs
833 to begin building circuits?" logic most recently in 0.2.4.10-alpha
834 (see bug 5956), but we left the bootstrap status event logic at
835 "how far through getting 1/4 of them are we?" Fixes bug 9958;
836 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
838 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
839 - Avoid a crash bug when starting with a corrupted microdescriptor
840 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
841 - If we fail to dump a previously cached microdescriptor to disk, avoid
842 freeing duplicate data later on. Fixes bug 10423; bugfix on
843 0.2.4.13-alpha. Spotted by "bobnomnom".
845 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
846 - Correctly log long IPv6 exit policies, instead of truncating them
847 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
848 - Our default TLS ecdhe groups were backwards: we meant to be using
849 P224 for relays (for performance win) and P256 for bridges (since
850 it is more common in the wild). Instead we had it backwards. After
851 reconsideration, we decided that the default should be P256 on all
852 hosts, since its security is probably better, and since P224 is
853 reportedly used quite little in the wild. Found by "skruffy" on
854 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
855 - Free directory authority certificate download statuses on exit
856 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
858 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
859 - If the guard we choose first doesn't answer, we would try the
860 second guard, but once we connected to the second guard we would
861 abandon it and retry the first one, slowing down bootstrapping.
862 The fix is to treat all our initially chosen guards as acceptable
863 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
864 - Fix an assertion failure that would occur when disabling the
865 ORPort setting on a running Tor process while accounting was
866 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
867 - When examining the list of network interfaces to find our address,
868 do not consider non-running or disabled network interfaces. Fixes
869 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
870 - Avoid an off-by-one error when checking buffer boundaries when
871 formatting the exit status of a pluggable transport helper.
872 This is probably not an exploitable bug, but better safe than
873 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
876 o Removed code and features:
877 - Clients now reject any directory authority certificates lacking
878 a dir-key-crosscert element. These have been included since
879 0.2.1.9-alpha, so there's no real reason for them to be optional
880 any longer. Completes proposal 157. Resolves ticket 10162.
881 - Remove all code that existed to support the v2 directory system,
882 since there are no longer any v2 directory authorities. Resolves
884 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
885 options, which were used for designating authorities as "Hidden
886 service authorities". There has been no use of hidden service
887 authorities since 0.2.2.1-alpha, when we stopped uploading or
888 downloading v0 hidden service descriptors. Fixes bug 10881; also
889 part of a fix for bug 10841.
891 o Code simplification and refactoring:
892 - Remove some old fallback code designed to keep Tor clients working
893 in a network with only two working relays. Elsewhere in the code we
894 have long since stopped supporting such networks, so there wasn't
895 much point in keeping it around. Addresses ticket 9926.
896 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
897 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
898 - Remove data structures which were introduced to implement the
899 CellStatistics option: they are now redundant with the addition
900 of a timestamp to the regular packed_cell_t data structure, which
901 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
904 o Documentation (man page) fixes:
905 - Update manpage to describe some of the files you can expect to
906 find in Tor's DataDirectory. Addresses ticket 9839.
907 - Document that all but one DirPort entry must have the NoAdvertise
908 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
910 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
911 - Clarify the usage and risks of setting the ContactInfo torrc line
912 for your relay or bridge. Resolves ticket 9854.
913 - Add anchors to the manpage so we can link to the html version of
914 the documentation for specific options. Resolves ticket 9866.
915 - Replace remaining references to DirServer in man page and
916 log entries. Resolves ticket 10124.
919 - Make the "tor-gencert" tool used by directory authority operators
920 create 2048-bit signing keys by default (rather than 1024-bit, since
921 1024-bit is uncomfortably small these days). Addresses ticket 10324.
924 Changes in version 0.2.4.20 - 2013-12-22
925 Tor 0.2.4.20 fixes potentially poor random number generation for users
926 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
927 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
928 and 4) have no state file in their DataDirectory (as would happen on
929 first start). Users who generated relay or hidden service identity
930 keys in such a situation should discard them and generate new ones.
932 This release also fixes a logic error that caused Tor clients to build
933 many more preemptive circuits than they actually need.
936 - Do not allow OpenSSL engines to replace the PRNG, even when
937 HardwareAccel is set. The only default builtin PRNG engine uses
938 the Intel RDRAND instruction to replace the entire PRNG, and
939 ignores all attempts to seed it with more entropy. That's
940 cryptographically stupid: the right response to a new alleged
941 entropy source is never to discard all previously used entropy
942 sources. Fixes bug 10402; works around behavior introduced in
943 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
945 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
946 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
947 - Avoid launching spurious extra circuits when a stream is pending.
948 This fixes a bug where any circuit that _wasn't_ unusable for new
949 streams would be treated as if it were, causing extra circuits to
950 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
953 - Avoid a crash bug when starting with a corrupted microdescriptor
954 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
955 - If we fail to dump a previously cached microdescriptor to disk, avoid
956 freeing duplicate data later on. Fixes bug 10423; bugfix on
957 0.2.4.13-alpha. Spotted by "bobnomnom".
960 Changes in version 0.2.4.19 - 2013-12-11
961 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
962 (1986-2013). Aaron worked on diverse projects including helping to guide
963 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
964 transparency to the U.S government's PACER documents, and contributing
965 design and development for Tor and Tor2Web. Aaron was one of the latest
966 martyrs in our collective fight for civil liberties and human rights,
967 and his death is all the more painful because he was one of us.
969 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
970 a new circuit handshake and link encryption that use ECC to provide
971 better security and efficiency; makes relays better manage circuit
972 creation requests; uses "directory guards" to reduce client enumeration
973 risks; makes bridges collect and report statistics about the pluggable
974 transports they support; cleans up and improves our geoip database;
975 gets much closer to IPv6 support for clients, bridges, and relays; makes
976 directory authorities use measured bandwidths rather than advertised
977 ones when computing flags and thresholds; disables client-side DNS
978 caching to reduce tracking risks; and fixes a big bug in bridge
979 reachability testing. This release introduces two new design
980 abstractions in the code: a new "channel" abstraction between circuits
981 and or_connections to allow for implementing alternate relay-to-relay
982 transports, and a new "circuitmux" abstraction storing the queue of
983 circuits for a channel. The release also includes many stability,
984 security, and privacy fixes.
987 Changes in version 0.2.4.18-rc - 2013-11-16
988 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
989 series. It takes a variety of fixes from the 0.2.5.x branch to improve
990 stability, performance, and better handling of edge cases.
993 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
994 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
995 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
996 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
997 them to solve bug 6033.)
1000 - No longer stop reading or writing on cpuworker connections when
1001 our rate limiting buckets go empty. Now we should handle circuit
1002 handshake requests more promptly. Resolves bug 9731.
1003 - If we are unable to save a microdescriptor to the journal, do not
1004 drop it from memory and then reattempt downloading it. Fixes bug
1005 9645; bugfix on 0.2.2.6-alpha.
1006 - Stop trying to bootstrap all our directory information from
1007 only our first guard. Discovered while fixing bug 9946; bugfix
1009 - The new channel code sometimes lost track of in-progress circuits,
1010 causing long-running clients to stop building new circuits. The
1011 fix is to always call circuit_n_chan_done(chan, 0) from
1012 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1014 o Minor bugfixes (on 0.2.4.x):
1015 - Correctly log long IPv6 exit policies, instead of truncating them
1016 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1017 - Our default TLS ecdhe groups were backwards: we meant to be using
1018 P224 for relays (for performance win) and P256 for bridges (since
1019 it is more common in the wild). Instead we had it backwards. After
1020 reconsideration, we decided that the default should be P256 on all
1021 hosts, since its security is probably better, and since P224 is
1022 reportedly used quite little in the wild. Found by "skruffy" on
1023 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1024 - Free directory authority certificate download statuses on exit
1025 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1027 o Minor bugfixes (on 0.2.3.x and earlier):
1028 - If the guard we choose first doesn't answer, we would try the
1029 second guard, but once we connected to the second guard we would
1030 abandon it and retry the first one, slowing down bootstrapping.
1031 The fix is to treat all our initially chosen guards as acceptable
1032 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1033 - Fix an assertion failure that would occur when disabling the
1034 ORPort setting on a running Tor process while accounting was
1035 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1036 - When examining the list of network interfaces to find our address,
1037 do not consider non-running or disabled network interfaces. Fixes
1038 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1039 - Avoid an off-by-one error when checking buffer boundaries when
1040 formatting the exit status of a pluggable transport helper.
1041 This is probably not an exploitable bug, but better safe than
1042 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1045 o Minor features (protecting client timestamps):
1046 - Clients no longer send timestamps in their NETINFO cells. These were
1047 not used for anything, and they provided one small way for clients
1048 to be distinguished from each other as they moved from network to
1049 network or behind NAT. Implements part of proposal 222.
1050 - Clients now round timestamps in INTRODUCE cells down to the nearest
1051 10 minutes. If a new Support022HiddenServices option is set to 0, or
1052 if it's set to "auto" and the feature is disabled in the consensus,
1053 the timestamp is sent as 0 instead. Implements part of proposal 222.
1054 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1055 a big deal from a security point of view, but it achieves no actual
1056 good purpose, and isn't needed. Implements part of proposal 222.
1057 - Reduce down accuracy of timestamps in hidden service descriptors.
1058 Implements part of proposal 222.
1060 o Minor features (other):
1061 - Improve the circuit queue out-of-memory handler. Previously, when
1062 we ran low on memory, we'd close whichever circuits had the most
1063 queued cells. Now, we close those that have the *oldest* queued
1064 cells, on the theory that those are most responsible for us
1065 running low on memory. Based on analysis from a forthcoming paper
1066 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1067 - Generate bootstrapping status update events correctly when fetching
1068 microdescriptors. Fixes bug 9927.
1069 - Update to the October 2 2013 Maxmind GeoLite Country database.
1071 o Documentation fixes:
1072 - Clarify the usage and risks of setting the ContactInfo torrc line
1073 for your relay or bridge. Resolves ticket 9854.
1074 - Add anchors to the manpage so we can link to the html version of
1075 the documentation for specific options. Resolves ticket 9866.
1076 - Replace remaining references to DirServer in man page and
1077 log entries. Resolves ticket 10124.
1080 Changes in version 0.2.5.1-alpha - 2013-10-02
1081 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
1082 on Linux, allows bridges that offer pluggable transports to report usage
1083 statistics, fixes many issues to make testing easier, and provides
1084 a pile of minor features and bugfixes that have been waiting for a
1085 release of the new branch.
1087 This is the first alpha release in a new series, so expect there to
1088 be bugs. Users who would rather test out a more stable branch should
1089 stay with 0.2.4.x for now.
1091 o Major features (security):
1092 - Use the seccomp2 syscall filtering facility on Linux to limit
1093 which system calls Tor can invoke. This is an experimental,
1094 Linux-only feature to provide defense-in-depth against unknown
1095 attacks. To try turning it on, set "Sandbox 1" in your torrc
1096 file. Please be ready to report bugs. We hope to add support
1097 for better sandboxing in the future, including more fine-grained
1098 filters, better division of responsibility, and support for more
1099 platforms. This work has been done by Cristian-Matei Toader for
1100 Google Summer of Code.
1101 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1102 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1103 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1104 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1105 them to solve bug 6033.)
1107 o Major features (other):
1108 - Add support for passing arguments to managed pluggable transport
1109 proxies. Implements ticket 3594.
1110 - Bridges now track GeoIP information and the number of their users
1111 even when pluggable transports are in use, and report usage
1112 statistics in their extra-info descriptors. Resolves tickets 4773
1114 - Make testing Tor networks bootstrap better: lower directory fetch
1115 retry schedules and maximum interval without directory requests,
1116 and raise maximum download tries. Implements ticket 6752.
1117 - Add make target 'test-network' to run tests on a Chutney network.
1118 Implements ticket 8530.
1119 - The ntor handshake is now on-by-default, no matter what the
1120 directory authorities recommend. Implements ticket 8561.
1123 - Instead of writing destroy cells directly to outgoing connection
1124 buffers, queue them and intersperse them with other outgoing cells.
1125 This can prevent a set of resource starvation conditions where too
1126 many pending destroy cells prevent data cells from actually getting
1127 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
1128 bugfix on 0.2.0.1-alpha.
1129 - If we are unable to save a microdescriptor to the journal, do not
1130 drop it from memory and then reattempt downloading it. Fixes bug
1131 9645; bugfix on 0.2.2.6-alpha.
1132 - The new channel code sometimes lost track of in-progress circuits,
1133 causing long-running clients to stop building new circuits. The
1134 fix is to always call circuit_n_chan_done(chan, 0) from
1135 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1138 - Tor now builds each source file in two modes: a mode that avoids
1139 exposing identifiers needlessly, and another mode that exposes
1140 more identifiers for testing. This lets the compiler do better at
1141 optimizing the production code, while enabling us to take more
1142 radical measures to let the unit tests test things.
1143 - The production builds no longer include functions used only in
1144 the unit tests; all functions exposed from a module only for
1145 unit-testing are now static in production builds.
1146 - Add an --enable-coverage configuration option to make the unit
1147 tests (and a new src/or/tor-cov target) to build with gcov test
1151 - We now have rudimentary function mocking support that our unit
1152 tests can use to test functions in isolation. Function mocking
1153 lets the tests temporarily replace a function's dependencies with
1154 stub functions, so that the tests can check the function without
1155 invoking the other functions it calls.
1156 - Add more unit tests for the <circid,channel>->circuit map, and
1157 the destroy-cell-tracking code to fix bug 7912.
1158 - Unit tests for failing cases of the TAP onion handshake.
1159 - More unit tests for address-manipulation functions.
1161 o Minor features (protecting client timestamps):
1162 - Clients no longer send timestamps in their NETINFO cells. These were
1163 not used for anything, and they provided one small way for clients
1164 to be distinguished from each other as they moved from network to
1165 network or behind NAT. Implements part of proposal 222.
1166 - Clients now round timestamps in INTRODUCE cells down to the nearest
1167 10 minutes. If a new Support022HiddenServices option is set to 0, or
1168 if it's set to "auto" and the feature is disabled in the consensus,
1169 the timestamp is sent as 0 instead. Implements part of proposal 222.
1170 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1171 a big deal from a security point of view, but it achieves no actual
1172 good purpose, and isn't needed. Implements part of proposal 222.
1173 - Reduce down accuracy of timestamps in hidden service descriptors.
1174 Implements part of proposal 222.
1176 o Minor features (config options):
1177 - Config (torrc) lines now handle fingerprints which are missing
1178 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
1179 - Support a --dump-config option to print some or all of the
1180 configured options. Mainly useful for debugging the command-line
1181 option parsing code. Helps resolve ticket 4647.
1182 - Raise awareness of safer logging: notify user of potentially
1183 unsafe config options, like logging more verbosely than severity
1184 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
1185 - Add a new configuration option TestingV3AuthVotingStartOffset
1186 that bootstraps a network faster by changing the timing for
1187 consensus votes. Addresses ticket 8532.
1188 - Add a new torrc option "ServerTransportOptions" that allows
1189 bridge operators to pass configuration parameters to their
1190 pluggable transports. Resolves ticket 8929.
1191 - The config (torrc) file now accepts bandwidth and space limits in
1192 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
1193 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
1196 o Minor features (build):
1197 - Add support for `--library-versions` flag. Implements ticket 6384.
1198 - Return the "unexpected sendme" warnings to a warn severity, but make
1199 them rate limited, to help diagnose ticket 8093.
1200 - Detect a missing asciidoc, and warn the user about it, during
1201 configure rather than at build time. Fixes issue 6506. Patch from
1204 o Minor features (other):
1205 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
1206 sockets in a single system call. Implements ticket 5129.
1207 - Log current accounting state (bytes sent and received + remaining
1208 time for the current accounting period) in the relay's heartbeat
1209 message. Implements ticket 5526; patch from Peter Retzlaff.
1210 - Implement the TRANSPORT_LAUNCHED control port event that
1211 notifies controllers about new launched pluggable
1212 transports. Resolves ticket 5609.
1213 - If we're using the pure-C 32-bit curve25519_donna implementation
1214 of curve25519, build it with the -fomit-frame-pointer option to
1215 make it go faster on register-starved hosts. This improves our
1216 handshake performance by about 6% on i386 hosts without nacl.
1218 - Update to the September 4 2013 Maxmind GeoLite Country database.
1221 - Set the listen() backlog limit to the largest actually supported
1222 on the system, not to the value in a header file. Fixes bug 9716;
1223 bugfix on every released Tor.
1224 - No longer accept malformed http headers when parsing urls from
1225 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
1226 bugfix on 0.0.6pre1.
1227 - In munge_extrainfo_into_routerinfo(), check the return value of
1228 memchr(). This would have been a serious issue if we ever passed
1229 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
1231 - On the chance that somebody manages to build Tor on a
1232 platform where time_t is unsigned, correct the way that
1233 microdesc_add_to_cache() handles negative time arguments.
1234 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
1235 - Reject relative control socket paths and emit a warning. Previously,
1236 single-component control socket paths would be rejected, but Tor
1237 would not log why it could not validate the config. Fixes bug 9258;
1238 bugfix on 0.2.3.16-alpha.
1240 o Minor bugfixes (command line):
1241 - Use a single command-line parser for parsing torrc options on the
1242 command line and for finding special command-line options to avoid
1243 inconsistent behavior for torrc option arguments that have the same
1244 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
1246 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
1247 9573; bugfix on 0.0.9pre5.
1249 o Minor fixes (build, auxiliary programs):
1250 - Stop preprocessing the "torify" script with autoconf, since
1251 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
1253 - The tor-fw-helper program now follows the standard convention and
1254 exits with status code "0" on success. Fixes bug 9030; bugfix on
1255 0.2.3.1-alpha. Patch by Arlo Breault.
1256 - Corrected ./configure advice for what openssl dev package you should
1257 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
1259 o Minor code improvements:
1260 - Remove constants and tests for PKCS1 padding; it's insecure and
1261 shouldn't be used for anything new. Fixes bug 8792; patch
1263 - Remove instances of strcpy() from the unit tests. They weren't
1264 hurting anything, since they were only in the unit tests, but it's
1265 embarassing to have strcpy() in the code at all, and some analysis
1266 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
1267 0.2.3.8-alpha. Patch from Arlo Breault.
1270 - Remove migration code from when we renamed the "cached-routers"
1271 file to "cached-descriptors" back in 0.2.0.8-alpha. This
1272 incidentally resolves ticket 6502 by cleaning up the related code
1273 a bit. Patch from Akshay Hebbar.
1275 o Code simplification and refactoring:
1276 - Extract the common duplicated code for creating a subdirectory
1277 of the data directory and writing to a file in it. Fixes ticket
1278 4282; patch from Peter Retzlaff.
1279 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
1280 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
1281 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
1282 - Add a set of accessor functions for the circuit timeout data
1283 structure. Fixes ticket 6153; patch from "piet".
1284 - Clean up exit paths from connection_listener_new(). Closes ticket
1285 8789. Patch from Arlo Breault.
1286 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
1287 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
1288 - Use a doubly-linked list to implement the global circuit list.
1289 Resolves ticket 9108. Patch from Marek Majkowski.
1290 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
1293 Changes in version 0.2.4.17-rc - 2013-09-05
1294 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
1295 series. It adds an emergency step to help us tolerate the massive
1296 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
1297 circuit-level handshakes now effectively jump the queue compared to
1298 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
1299 big bug hindering bridge reachability tests.
1302 - Relays now process the new "NTor" circuit-level handshake requests
1303 with higher priority than the old "TAP" circuit-level handshake
1304 requests. We still process some TAP requests to not totally starve
1305 0.2.3 clients when NTor becomes popular. A new consensus parameter
1306 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1307 Implements ticket 9574.
1310 - If the circuit build timeout logic is disabled (via the consensus,
1311 or because we are an authority), then don't build testing circuits.
1312 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1313 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1314 previously they did not, which prevented them from receiving
1315 successful connections from relays for self-test or bandwidth
1316 testing. Also, when a relay is extending a circuit to a bridge,
1317 it needs to send a NETINFO cell, even when the bridge hasn't sent
1318 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1319 - If the time to download the next old-style networkstatus is in
1320 the future, do not decline to consider whether to download the
1321 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1325 - Avoid double-closing the listener socket in our socketpair()
1326 replacement (used on Windows) in the case where the addresses on
1327 our opened sockets don't match what we expected. Fixes bug 9400;
1328 bugfix on 0.0.2pre7. Found by Coverity.
1330 o Minor fixes (config options):
1331 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1332 ridiculously high value, by imposing a (ridiculously high) 30-day
1333 maximum on MaxCircuitDirtiness.
1334 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
1335 message is logged at notice, not at info.
1336 - Warn and fail if a server is configured not to advertise any
1337 ORPorts at all. (We need *something* to put in our descriptor,
1338 or we just won't work.)
1341 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1342 and how many we complete, and log it every hour to help relay
1343 operators follow trends in network load. Addresses ticket 9658.
1344 - Update to the August 7 2013 Maxmind GeoLite Country database.
1347 Changes in version 0.2.4.16-rc - 2013-08-10
1348 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
1349 series. It fixes several crash bugs in the 0.2.4 branch.
1352 - Fix a bug in the voting algorithm that could yield incorrect results
1353 when a non-naming authority declared too many flags. Fixes bug 9200;
1354 bugfix on 0.2.0.3-alpha.
1355 - Fix an uninitialized read that could in some cases lead to a remote
1356 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
1357 Anybody running a hidden service on the experimental 0.2.4.x
1358 branch should upgrade. (This is, so far as we know, unrelated to
1360 - Avoid an assertion failure when processing DNS replies without the
1361 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
1362 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
1363 0.2.4.15-rc. Found by stem integration tests.
1366 - Fix an invalid memory read that occured when a pluggable
1367 transport proxy failed its configuration protocol.
1368 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
1369 - When evaluating whether to use a connection that we haven't
1370 decided is canonical using a recent link protocol version,
1371 decide that it's canonical only if it used address _does_
1372 match the desired address. Fixes bug 9309; bugfix on
1373 0.2.4.4-alpha. Reported by skruffy.
1374 - Make the default behavior of NumDirectoryGuards be to track
1375 NumEntryGuards. Now a user who changes only NumEntryGuards will get
1376 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
1377 - Fix a spurious compilation warning with some older versions of
1378 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1381 - Update to the July 3 2013 Maxmind GeoLite Country database.
1384 Changes in version 0.2.4.15-rc - 2013-07-01
1385 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
1386 series. It fixes a few smaller bugs, but generally appears stable.
1387 Please test it and let us know whether it is!
1390 - When receiving a new configuration file via the control port's
1391 LOADCONF command, do not treat the defaults file as absent.
1392 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1395 - Issue a warning when running with the bufferevents backend enabled.
1396 It's still not stable, and people should know that they're likely
1397 to hit unexpected problems. Closes ticket 9147.
1400 Changes in version 0.2.4.14-alpha - 2013-06-18
1401 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
1402 present in 0.2.4.13-alpha.
1405 - When we have too much memory queued in circuits (according to a new
1406 MaxMemInCellQueues option), close the circuits consuming the most
1407 memory. This prevents us from running out of memory as a relay if
1408 circuits fill up faster than they can be drained. Fixes bug 9063;
1409 bugfix on the 54th commit of Tor. This bug is a further fix beyond
1410 bug 6252, whose fix was merged into 0.2.3.21-rc.
1412 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
1413 where we tried to solve this issue simply by imposing an upper limit
1414 on the number of queued cells for a single circuit. That approach
1415 proved to be problematic, since there are ways to provoke clients to
1416 send a number of cells in excess of any such reasonable limit. Fixes
1417 bug 9072; bugfix on 0.2.4.13-alpha.
1419 - Limit hidden service descriptors to at most ten introduction
1420 points, to slow one kind of guard enumeration. Fixes bug 9002;
1421 bugfix on 0.1.1.11-alpha.
1424 Changes in version 0.2.4.13-alpha - 2013-06-14
1425 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
1426 vulnerabilities, makes socks5 username/password circuit isolation
1427 actually actually work (this time for sure!), and cleans up a bunch
1428 of other issues in preparation for a release candidate.
1430 o Major bugfixes (robustness):
1431 - Close any circuit that has too many cells queued on it. Fixes
1432 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
1433 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
1434 - Prevent the get_freelists() function from running off the end of
1435 the list of freelists if it somehow gets an unrecognized
1436 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1438 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1439 when an exit connection with optimistic data succeeds immediately
1440 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1442 - Fix a directory authority crash bug when building a consensus
1443 using an older consensus as its basis. Fixes bug 8833. Bugfix
1447 - Avoid a memory leak where we would leak a consensus body when we
1448 find that a consensus which we couldn't previously verify due to
1449 missing certificates is now verifiable. Fixes bug 8719; bugfix
1451 - We used to always request authority certificates by identity digest,
1452 meaning we'd get the newest one even when we wanted one with a
1453 different signing key. Then we would complain about being given
1454 a certificate we already had, and never get the one we really
1455 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1456 resource to request the one we want. Fixes bug 5595; bugfix on
1458 - Follow the socks5 protocol when offering username/password
1459 authentication. The fix for bug 8117 exposed this bug, and it
1460 turns out real-world applications like Pidgin do care. Bugfix on
1461 0.2.3.2-alpha; fixes bug 8879.
1462 - Prevent failures on Windows Vista and later when rebuilding the
1463 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
1464 bugfix on 0.2.4.12-alpha.
1467 - Fix an impossible buffer overrun in the AES unit tests. Fixes
1468 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
1469 - If for some reason we fail to write a microdescriptor while
1470 rebuilding the cache, do not let the annotations from that
1471 microdescriptor linger in the cache file, and do not let the
1472 microdescriptor stay recorded as present in its old location.
1473 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1474 - Fix a memory leak that would occur whenever a configuration
1475 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1476 - Paste the description for PathBias parameters from the man
1477 page into or.h, so the code documents them too. Fixes bug 7982;
1478 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
1479 - Relays now treat a changed IPv6 ORPort as sufficient reason to
1480 publish an updated descriptor. Fixes bug 6026; bugfix on
1482 - When launching a resolve request on behalf of an AF_UNIX control
1483 socket, omit the address field of the new entry connection, used in
1484 subsequent controller events, rather than letting tor_dup_addr()
1485 set it to "<unknown address type>". Fixes bug 8639; bugfix on
1488 o Minor bugfixes (log messages):
1489 - Fix a scaling issue in the path bias accounting code that
1490 resulted in "Bug:" log messages from either
1491 pathbias_scale_close_rates() or pathbias_count_build_success().
1492 This represents a bugfix on a previous bugfix: the original fix
1493 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
1495 - Give a less useless error message when the user asks for an IPv4
1496 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
1500 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
1501 to tolerate bug 8093 for now.
1502 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1503 in directory authority votes to describe whether they have enough
1504 measured bandwidths to ignore advertised (relay descriptor)
1505 bandwidth claims. Resolves ticket 8711.
1506 - Update to the June 5 2013 Maxmind GeoLite Country database.
1508 o Removed documentation:
1509 - Remove some of the older contents of doc/ as obsolete; move others
1510 to torspec.git. Fixes bug 8965.
1512 o Code simplification and refactoring:
1513 - Avoid using character buffers when constructing most directory
1514 objects: this approach was unwieldy and error-prone. Instead,
1515 build smartlists of strings, and concatenate them when done.
1518 Changes in version 0.2.4.12-alpha - 2013-04-18
1519 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
1520 process for lengthening the guard rotation period, makes directory
1521 authority opinions in the consensus a bit less gameable, makes socks5
1522 username/password circuit isolation actually work, and fixes a wide
1523 variety of other issues.
1526 - Raise the default time that a client keeps an entry guard from
1527 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1528 2012 paper. (We would make it even longer, but we need better client
1529 load balancing first.) Also, make the guard lifetime controllable
1530 via a new GuardLifetime torrc option and a GuardLifetime consensus
1531 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1532 - Directory authorities now prefer using measured bandwidths to
1533 advertised ones when computing flags and thresholds. Resolves
1535 - Directory authorities that have more than a threshold number
1536 of relays with measured bandwidths now treat relays with unmeasured
1537 bandwidths as having bandwidth 0. Resolves ticket 8435.
1539 o Major bugfixes (assert / resource use):
1540 - Avoid a bug where our response to TLS renegotiation under certain
1541 network conditions could lead to a busy-loop, with 100% CPU
1542 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1543 - Avoid an assertion when we discover that we'd like to write a cell
1544 onto a closing connection: just discard the cell. Fixes another
1545 case of bug 7350; bugfix on 0.2.4.4-alpha.
1547 o Major bugfixes (client-side privacy):
1548 - When we mark a circuit as unusable for new circuits, have it
1549 continue to be unusable for new circuits even if MaxCircuitDirtiness
1550 is increased too much at the wrong time, or the system clock jumps
1551 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1552 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1553 which have resolved to internal addresses") is set, apply that
1554 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1555 - When an exit relay rejects a stream with reason "exit policy", but
1556 we only know an exit policy summary (e.g. from the microdesc
1557 consensus) for it, do not mark the relay as useless for all exiting.
1558 Instead, mark just the circuit as unsuitable for that particular
1559 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1560 - Allow applications to get proper stream isolation with
1561 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1562 username/password authentication also offer "no authentication". Tor
1563 had previously preferred "no authentication", so the applications
1564 never actually sent Tor their auth details. Now Tor selects
1565 username/password authentication if it's offered. You can disable
1566 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1567 bug 8117; bugfix on 0.2.3.3-alpha.
1569 o Major bugfixes (other):
1570 - When unable to find any working directory nodes to use as a
1571 directory guard, give up rather than adding the same non-working
1572 nodes to the directory guard list over and over. Fixes bug 8231;
1573 bugfix on 0.2.4.8-alpha.
1576 - Reject as invalid most directory objects containing a NUL.
1577 Belt-and-suspender fix for bug 8037.
1578 - In our testsuite, create temporary directories with a bit more
1579 entropy in their name to make name collisions less likely. Fixes
1581 - Add CACHED keyword to ADDRMAP events in the control protocol
1582 to indicate whether a DNS result will be cached or not. Resolves
1584 - Update to the April 3 2013 Maxmind GeoLite Country database.
1586 o Minor features (build):
1587 - Detect and reject attempts to build Tor with threading support
1588 when OpenSSL has been compiled without threading support.
1590 - Clarify that when autoconf is checking for nacl, it is checking
1591 specifically for nacl with a fast curve25519 implementation.
1593 - Warn if building on a platform with an unsigned time_t: there
1594 are too many places where Tor currently assumes that time_t can
1595 hold negative values. We'd like to fix them all, but probably
1598 o Minor bugfixes (build):
1599 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
1600 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
1601 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
1602 - Add the old src/or/micro-revision.i filename to CLEANFILES.
1603 On the off chance that somebody has one, it will go away as soon
1604 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
1605 - Build Tor correctly on 32-bit platforms where the compiler can build
1606 but not run code using the "uint128_t" construction. Fixes bug 8587;
1607 bugfix on 0.2.4.8-alpha.
1608 - Fix compilation warning with some versions of clang that would
1609 prefer the -Wswitch-enum compiler flag to warn about switch
1610 statements with missing enum values, even if those switch
1611 statements have a "default:" statement. Fixes bug 8598; bugfix
1614 o Minor bugfixes (protocol):
1615 - Fix the handling of a TRUNCATE cell when it arrives while the
1616 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
1617 - Fix a misframing issue when reading the version numbers in a
1618 VERSIONS cell. Previously we would recognize [00 01 00 02] as
1619 'version 1, version 2, and version 0x100', when it should have
1620 only included versions 1 and 2. Fixes bug 8059; bugfix on
1621 0.2.0.10-alpha. Reported pseudonymously.
1622 - Make the format and order of STREAM events for DNS lookups
1623 consistent among the various ways to launch DNS lookups. Fixes
1624 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
1625 - Correct our check for which versions of Tor support the EXTEND2
1626 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
1627 later, when support was really added in version 0.2.4.8-alpha.
1628 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
1630 o Minor bugfixes (other):
1631 - Correctly store microdescriptors and extrainfo descriptors with
1632 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
1633 Bug reported by "cypherpunks".
1634 - Increase the width of the field used to remember a connection's
1635 link protocol version to two bytes. Harmless for now, since the
1636 only currently recognized versions are one byte long. Reported
1637 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
1638 - If the state file's path bias counts are invalid (presumably from a
1639 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
1640 additional checks and log messages to the scaling of Path Bias
1641 counts, in case there still are remaining issues with scaling.
1642 Should help resolve bug 8235.
1643 - Eliminate several instances where we use "Nickname=ID" to refer to
1644 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
1645 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
1646 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
1648 o Minor bugfixes (syscalls):
1649 - Always check the return values of functions fcntl() and
1650 setsockopt(). We don't believe these are ever actually failing in
1651 practice, but better safe than sorry. Also, checking these return
1652 values should please analysis tools like Coverity. Patch from
1653 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
1654 - Use direct writes rather than stdio when building microdescriptor
1655 caches, in an attempt to mitigate bug 8031, or at least make it
1658 o Minor bugfixes (config):
1659 - When rejecting a configuration because we were unable to parse a
1660 quoted string, log an actual error message. Fixes bug 7950; bugfix
1662 - Behave correctly when the user disables LearnCircuitBuildTimeout
1663 but doesn't tell us what they would like the timeout to be. Fixes
1664 bug 6304; bugfix on 0.2.2.14-alpha.
1665 - When autodetecting the number of CPUs, use the number of available
1666 CPUs in preference to the number of configured CPUs. Inform the
1667 user if this reduces the number of available CPUs. Fixes bug 8002;
1668 bugfix on 0.2.3.1-alpha.
1669 - Make it an error when you set EntryNodes but disable UseGuardNodes,
1670 since it will (surprisingly to some users) ignore EntryNodes. Fixes
1671 bug 8180; bugfix on 0.2.3.11-alpha.
1672 - Allow TestingTorNetworks to override the 4096-byte minimum for
1673 the Fast threshold. Otherwise they can't bootstrap until they've
1674 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
1675 - Fix some logic errors when the user manually overrides the
1676 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
1679 o Minor bugfixes (log messages to help diagnose bugs):
1680 - If we fail to free a microdescriptor because of bug 7164, log
1681 the filename and line number from which we tried to free it.
1682 - Add another diagnostic to the heartbeat message: track and log
1683 overhead that TLS is adding to the data we write. If this is
1684 high, we are sending too little data to SSL_write at a time.
1685 Diagnostic for bug 7707.
1686 - Add more detail to a log message about relaxed timeouts, to help
1688 - Warn more aggressively when flushing microdescriptors to a
1689 microdescriptor cache fails, in an attempt to mitigate bug 8031,
1690 or at least make it more diagnosable.
1691 - Improve debugging output to help track down bug 8185 ("Bug:
1692 outgoing relay cell has n_chan==NULL. Dropping.")
1693 - Log the purpose of a path-bias testing circuit correctly.
1694 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
1696 o Minor bugfixes (0.2.4.x log messages that were too noisy):
1697 - Don't attempt to relax the timeout of already opened 1-hop circuits.
1698 They might never timeout. This should eliminate some/all cases of
1699 the relaxed timeout log message.
1700 - Use circuit creation time for network liveness evaluation. This
1701 should eliminate warning log messages about liveness caused
1702 by changes in timeout evaluation. Fixes bug 6572; bugfix on
1704 - Reduce a path bias length check from notice to info. The message
1705 is triggered when creating controller circuits. Fixes bug 8196;
1706 bugfix on 0.2.4.8-alpha.
1707 - Fix a path state issue that triggered a notice during relay startup.
1708 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
1709 - Reduce occurrences of warns about circuit purpose in
1710 connection_ap_expire_building(). Fixes bug 8477; bugfix on
1713 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
1714 - If we encounter a write failure on a SOCKS connection before we
1715 finish our SOCKS handshake, don't warn that we closed the
1716 connection before we could send a SOCKS reply. Fixes bug 8427;
1717 bugfix on 0.1.0.1-rc.
1718 - Correctly recognize that [::1] is a loopback address. Fixes
1719 bug 8377; bugfix on 0.2.1.3-alpha.
1720 - Fix a directory authority warn caused when we have a large amount
1721 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
1722 - Don't log inappropriate heartbeat messages when hibernating: a
1723 hibernating node is _expected_ to drop out of the consensus,
1724 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
1725 bugfix on 0.2.3.1-alpha.
1726 - Don't complain about bootstrapping problems while hibernating.
1727 These complaints reflect a general code problem, but not one
1728 with any problematic effects (no connections are actually
1729 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
1731 o Documentation fixes:
1732 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
1733 names match. Fixes bug 7768.
1734 - Make the torify manpage no longer refer to tsocks; torify hasn't
1735 supported tsocks since 0.2.3.14-alpha.
1736 - Make the tor manpage no longer reference tsocks.
1737 - Fix the GeoIPExcludeUnknown documentation to refer to
1738 ExcludeExitNodes rather than the currently nonexistent
1739 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
1742 - The tor-tsocks.conf is no longer distributed or installed. We
1743 recommend that tsocks users use torsocks instead. Resolves
1747 Changes in version 0.2.4.11-alpha - 2013-03-11
1748 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
1749 more robust, makes hidden service authentication work again, and
1750 resolves a DPI fingerprint for Tor's SSL transport.
1752 o Major features (directory authorities):
1753 - Directory authorities now support a new consensus method (17)
1754 where they cap the published bandwidth of servers for which
1755 insufficient bandwidth measurements exist. Fixes part of bug 2286.
1756 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
1757 serve any v2 directory information. Now we can test disabling the
1758 old deprecated v2 directory format, and see whether doing so has
1759 any effect on network load. Begins to fix bug 6783.
1760 - Directory authorities now include inside each vote a statement of
1761 the performance thresholds they used when assigning flags.
1762 Implements ticket 8151.
1764 o Major bugfixes (directory authorities):
1765 - Stop marking every relay as having been down for one hour every
1766 time we restart a directory authority. These artificial downtimes
1767 were messing with our Stable and Guard flag calculations. Fixes
1768 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
1770 o Major bugfixes (hidden services):
1771 - Allow hidden service authentication to succeed again. When we
1772 refactored the hidden service introduction code back
1773 in 0.2.4.1-alpha, we didn't update the code that checks
1774 whether authentication information is present, causing all
1775 authentication checks to return "false". Fix for bug 8207; bugfix
1776 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
1778 o Minor features (relays, bridges):
1779 - Make bridge relays check once a minute for whether their IP
1780 address has changed, rather than only every 15 minutes. Resolves
1782 - Refactor resolve_my_address() so it returns the method by which we
1783 decided our public IP address (explicitly configured, resolved from
1784 explicit hostname, guessed from interfaces, learned by gethostname).
1785 Now we can provide more helpful log messages when a relay guesses
1786 its IP address incorrectly (e.g. due to unexpected lines in
1787 /etc/hosts). Resolves ticket 2267.
1788 - Teach bridge-using clients to avoid 0.2.2 bridges when making
1789 microdescriptor-related dir requests, and only fall back to normal
1790 descriptors if none of their bridges can handle microdescriptors
1791 (as opposed to the fix in ticket 4013, which caused them to fall
1792 back to normal descriptors if *any* of their bridges preferred
1793 them). Resolves ticket 4994.
1794 - Randomize the lifetime of our SSL link certificate, so censors can't
1795 use the static value for filtering Tor flows. Resolves ticket 8443;
1796 related to ticket 4014 which was included in 0.2.2.33.
1797 - Support a new version of the link protocol that allows 4-byte circuit
1798 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
1799 a possible resource exhaustion issue. Closes ticket 7351; implements
1802 o Minor features (portability):
1803 - Tweak the curve25519-donna*.c implementations to tolerate systems
1804 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
1805 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
1806 the signs of types during autoconf. This is better than our old
1807 approach, which didn't work when cross-compiling.
1808 - Detect the sign of enum values, rather than assuming that MSC is the
1809 only compiler where enum types are all signed. Fixes bug 7727;
1810 bugfix on 0.2.4.10-alpha.
1812 o Minor features (other):
1813 - Say "KBytes" rather than "KB" in the man page (for various values
1814 of K), to further reduce confusion about whether Tor counts in
1815 units of memory or fractions of units of memory. Resolves ticket 7054.
1816 - Clear the high bit on curve25519 public keys before passing them to
1817 our backend, in case we ever wind up using a backend that doesn't do
1818 so itself. If we used such a backend, and *didn't* clear the high bit,
1819 we could wind up in a situation where users with such backends would
1820 be distinguishable from users without. Fixes bug 8121; bugfix on
1822 - Update to the March 6 2013 Maxmind GeoLite Country database.
1824 o Minor bugfixes (clients):
1825 - When we receive a RELAY_END cell with the reason DONE, or with no
1826 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
1827 status as "connection refused". Previously we reported these cases
1828 as success but then immediately closed the connection. Fixes bug
1829 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
1830 - Downgrade an assertion in connection_ap_expire_beginning to an
1831 LD_BUG message. The fix for bug 8024 should prevent this message
1832 from displaying, but just in case, a warn that we can diagnose
1833 is better than more assert crashes. Fixes bug 8065; bugfix on
1835 - Lower path use bias thresholds to .80 for notice and .60 for warn.
1836 Also make the rate limiting flags for the path use bias log messages
1837 independent from the original path bias flags. Fixes bug 8161;
1838 bugfix on 0.2.4.10-alpha.
1840 o Minor bugfixes (relays):
1841 - Stop trying to resolve our hostname so often (e.g. every time we
1842 think about doing a directory fetch). Now we reuse the cached
1843 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
1844 and 2410 (bugfix on 0.1.2.2-alpha).
1845 - Stop sending a stray "(null)" in some cases for the server status
1846 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
1848 - When choosing which stream on a formerly stalled circuit to wake
1849 first, make better use of the platform's weak RNG. Previously,
1850 we had been using the % ("modulo") operator to try to generate a
1851 1/N chance of picking each stream, but this behaves badly with
1852 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
1854 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
1855 Irix's random() only return 15 bits; Solaris's random() returns more
1856 bits but its RAND_MAX says it only returns 15, and so on. Motivated
1857 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
1859 o Minor bugfixes (directory authorities):
1860 - Directory authorities now use less space when formatting identical
1861 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
1864 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
1865 - Avoid leaking memory if we fail to compute a consensus signature
1866 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
1867 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
1869 - Fix a memory leak during safe-cookie controller authentication.
1870 Bugfix on 0.2.3.13-alpha.
1871 - Avoid memory leak of IPv6 policy content if we fail to format it into
1872 a router descriptor. Bugfix on 0.2.4.7-alpha.
1874 o Minor bugfixes (other code correctness issues):
1875 - Avoid a crash if we fail to generate an extrainfo descriptor.
1876 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
1878 - When detecting the largest possible file descriptor (in order to
1879 close all file descriptors when launching a new program), actually
1880 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
1881 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
1883 - Fix a copy-and-paste error when adding a missing A1 to a routerset
1884 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
1885 Bugfix on 0.2.4.10-alpha.
1886 - Fix an impossible-to-trigger integer overflow when estimating how
1887 long our onionskin queue would take. (This overflow would require us
1888 to accept 4 million onionskins before processing 100 of them.) Fixes
1889 bug 8210; bugfix on 0.2.4.10-alpha.
1891 o Code simplification and refactoring:
1892 - Add a wrapper function for the common "log a message with a
1896 Changes in version 0.2.4.10-alpha - 2013-02-04
1897 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
1898 certain attacks that flood the network with relays; changes the queue
1899 for circuit create requests from a sized-based limit to a time-based
1900 limit; resumes building with MSVC on Windows; and fixes a wide variety
1903 o Major bugfixes (directory authority):
1904 - When computing directory thresholds, ignore any rejected-as-sybil
1905 nodes during the computation so that they can't influence Fast,
1906 Guard, etc. (We should have done this for proposal 109.) Fixes
1908 - When marking a node as a likely sybil, reset its uptime metrics
1909 to zero, so that it cannot time towards getting marked as Guard,
1910 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
1914 - When a TLS write is partially successful but incomplete, remember
1915 that the flushed part has been flushed, and notice that bytes were
1916 actually written. Reported and fixed pseudonymously. Fixes bug
1917 7708; bugfix on Tor 0.1.0.5-rc.
1918 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
1919 ID: these could be used to create unexpected streams and circuits
1920 which would count as "present" to some parts of Tor but "absent"
1921 to others, leading to zombie circuits and streams or to a bandwidth
1922 denial-of-service. Fixes bug 7889; bugfix on every released version
1923 of Tor. Reported by "oftc_must_be_destroyed".
1924 - Rename all macros in our local copy of queue.h to begin with "TOR_".
1925 This change seems the only good way to permanently prevent conflicts
1926 with queue.h on various operating systems. Fixes bug 8107; bugfix
1929 o Major features (relay):
1930 - Instead of limiting the number of queued onionskins (aka circuit
1931 create requests) to a fixed, hard-to-configure number, we limit
1932 the size of the queue based on how many we expect to be able to
1933 process in a given amount of time. We estimate the time it will
1934 take to process an onionskin based on average processing time
1935 of previous onionskins. Closes ticket 7291. You'll never have to
1936 configure MaxOnionsPending again.
1938 o Major features (portability):
1939 - Resume building correctly with MSVC and Makefile.nmake. This patch
1940 resolves numerous bugs and fixes reported by ultramage, including
1941 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
1942 - Make the ntor and curve25519 code build correctly with MSVC.
1943 Fix on 0.2.4.8-alpha.
1946 - When directory authorities are computing thresholds for flags,
1947 never let the threshold for the Fast flag fall below 4096
1948 bytes. Also, do not consider nodes with extremely low bandwidths
1949 when deciding thresholds for various directory flags. This change
1950 should raise our threshold for Fast relays, possibly in turn
1951 improving overall network performance; see ticket 1854. Resolves
1953 - The Tor client now ignores sub-domain components of a .onion
1954 address. This change makes HTTP "virtual" hosting
1955 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
1956 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
1957 hosted on the same hidden service. Implements proposal 204.
1958 - We compute the overhead from passing onionskins back and forth to
1959 cpuworkers, and report it when dumping statistics in response to
1960 SIGUSR1. Supports ticket 7291.
1962 o Minor features (path selection):
1963 - When deciding whether we have enough descriptors to build circuits,
1964 instead of looking at raw relay counts, look at which fraction
1965 of (bandwidth-weighted) paths we're able to build. This approach
1966 keeps clients from building circuits if their paths are likely to
1967 stand out statistically. The default fraction of paths needed is
1968 taken from the consensus directory; you can override it with the
1969 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
1970 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
1971 and we have GeoIP information, also exclude all nodes with unknown
1972 countries "??" and "A1". This behavior is controlled by the
1973 new GeoIPExcludeUnknown option: you can make such nodes always
1974 excluded with "GeoIPExcludeUnknown 1", and disable the feature
1975 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
1976 gets you the default behavior. Implements feature 7706.
1977 - Path Use Bias: Perform separate accounting for successful circuit
1978 use. Keep separate statistics on stream attempt rates versus stream
1979 success rates for each guard. Provide configurable thresholds to
1980 determine when to emit log messages or disable use of guards that
1981 fail too many stream attempts. Resolves ticket 7802.
1983 o Minor features (log messages):
1984 - When learning a fingerprint for a bridge, log its corresponding
1985 transport type. Implements ticket 7896.
1986 - Improve the log message when "Bug/attack: unexpected sendme cell
1987 from client" occurs, to help us track bug 8093.
1990 - Remove a couple of extraneous semicolons that were upsetting the
1991 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
1992 bugfix on 0.2.2.1-alpha.
1993 - Remove a source of rounding error during path bias count scaling;
1994 don't count cannibalized circuits as used for path bias until we
1995 actually try to use them; and fix a circuit_package_relay_cell()
1996 warning message about n_chan==NULL. Fixes bug 7802.
1997 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
1998 actually link against nacl when we're configured to use it. Fixes
1999 bug 7972; bugfix on 0.2.4.8-alpha.
2000 - Compile correctly with the --disable-curve25519 option. Fixes
2001 bug 8153; bugfix on 0.2.4.8-alpha.
2003 o Build improvements:
2004 - Do not report status verbosely from autogen.sh unless the -v flag
2005 is specified. Fixes issue 4664. Patch from Onizuka.
2006 - Replace all calls to snprintf() outside of src/ext with
2007 tor_snprintf(). Also remove the #define to replace snprintf with
2008 _snprintf on Windows; they have different semantics, and all of
2009 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2010 - Try to detect if we are ever building on a platform where
2011 memset(...,0,...) does not set the value of a double to 0.0. Such
2012 platforms are permitted by the C standard, though in practice
2013 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
2014 currently support them, but it's better to detect them and fail
2015 than to perform erroneously.
2018 - Stop exporting estimates of v2 and v3 directory traffic shares
2019 in extrainfo documents. They were unneeded and sometimes inaccurate.
2020 Also stop exporting any v2 directory request statistics. Resolves
2022 - Drop support for detecting and warning about versions of Libevent
2023 before 1.3e. Nothing reasonable ships with them any longer;
2024 warning the user about them shouldn't be needed. Resolves ticket
2027 o Code simplifications and refactoring:
2028 - Rename "isin" functions to "contains", for grammar. Resolves
2030 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2031 with the natural logarithm function from the system libm. Resolves
2035 Changes in version 0.2.4.9-alpha - 2013-01-15
2036 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
2040 - Fix backward compatibility logic when receiving an embedded ntor
2041 handshake tunneled in a CREATE cell. This clears up the "Bug:
2042 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
2046 Changes in version 0.2.4.8-alpha - 2013-01-14
2047 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
2048 risks, adds a new stronger and faster circuit handshake, and offers
2049 stronger and faster link encryption when both sides support it.
2052 - Preliminary support for directory guards (proposal 207): when
2053 possible, clients now use their entry guards for non-anonymous
2054 directory requests. This can help prevent client enumeration. Note
2055 that this behavior only works when we have a usable consensus
2056 directory, and when options about what to download are more or less
2057 standard. In the future we should re-bootstrap from our guards,
2058 rather than re-bootstrapping from the preconfigured list of
2059 directory sources that ships with Tor. Resolves ticket 6526.
2060 - Tor relays and clients now support a better CREATE/EXTEND cell
2061 format, allowing the sender to specify multiple address, identity,
2062 and handshake types. Implements Robert Ransom's proposal 200;
2065 o Major features (new circuit handshake):
2066 - Tor now supports a new circuit extension handshake designed by Ian
2067 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
2068 circuit extension handshake, later called "TAP", was a bit slow
2069 (especially on the relay side), had a fragile security proof, and
2070 used weaker keys than we'd now prefer. The new circuit handshake
2071 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
2072 function, making it significantly more secure than the older
2073 handshake, and significantly faster. Tor can use one of two built-in
2074 pure-C curve25519-donna implementations by Adam Langley, or it
2075 can link against the "nacl" library for a tuned version if present.
2077 The built-in version is very fast for 64-bit systems when building
2078 with GCC. The built-in 32-bit version is still faster than the
2079 old TAP protocol, but using libnacl is better on most such hosts.
2081 Clients don't currently use this protocol by default, since
2082 comparatively few clients support it so far. To try it, set
2083 UseNTorHandshake to 1.
2085 Implements proposal 216; closes ticket 7202.
2087 o Major features (better link encryption):
2088 - Relays can now enable the ECDHE TLS ciphersuites when available
2089 and appropriate. These ciphersuites let us negotiate forward-secure
2090 TLS secret keys more safely and more efficiently than with our
2091 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
2092 public relays prefer the (faster) P224 group, and bridges prefer
2093 the (more common) P256 group; you can override this with the
2096 Enabling these ciphers was a little tricky, since for a long time,
2097 clients had been claiming to support them without actually doing
2098 so, in order to foil fingerprinting. But with the client-side
2099 implementation of proposal 198 in 0.2.3.17-beta, clients can now
2100 match the ciphers from recent Firefox versions *and* list the
2101 ciphers they actually mean, so relays can believe such clients
2102 when they advertise ECDHE support in their TLS ClientHello messages.
2104 This feature requires clients running 0.2.3.17-beta or later,
2105 and requires both sides to be running OpenSSL 1.0.0 or later
2106 with ECC support. OpenSSL 1.0.1, with the compile-time option
2107 "enable-ec_nistp_64_gcc_128", is highly recommended.
2109 Implements the relay side of proposal 198; closes ticket 7200.
2112 - Avoid crashing when, as a relay without IPv6-exit support, a
2113 client insists on getting an IPv6 address or nothing. Fixes bug
2114 7814; bugfix on 0.2.4.7-alpha.
2117 - Improve circuit build timeout handling for hidden services.
2118 In particular: adjust build timeouts more accurately depending
2119 upon the number of hop-RTTs that a particular circuit type
2120 undergoes. Additionally, launch intro circuits in parallel
2121 if they timeout, and take the first one to reply as valid.
2122 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
2123 separate error codes; or at least, don't break for that reason.
2124 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
2125 - Update to the January 2 2013 Maxmind GeoLite Country database.
2127 o Minor features (testing):
2128 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
2129 (P-256) Diffie-Hellman handshakes to src/or/bench.
2130 - Add benchmark functions to test onion handshake performance.
2132 o Minor features (path bias detection):
2133 - Alter the Path Bias log messages to be more descriptive in terms
2134 of reporting timeouts and other statistics.
2135 - Create three levels of Path Bias log messages, as opposed to just
2136 two. These are configurable via consensus as well as via the torrc
2137 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
2138 The default values are 0.70, 0.50, and 0.30 respectively.
2139 - Separate the log message levels from the decision to drop guards,
2140 which also is available via torrc option PathBiasDropGuards.
2141 PathBiasDropGuards still defaults to 0 (off).
2142 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
2143 in combination with PathBiasExtremeRate.
2144 - Increase the default values for PathBiasScaleThreshold and
2145 PathBiasCircThreshold from (200, 20) to (300, 150).
2146 - Add in circuit usage accounting to path bias. If we try to use a
2147 built circuit but fail for any reason, it counts as path bias.
2148 Certain classes of circuits where the adversary gets to pick your
2149 destination node are exempt from this accounting. Usage accounting
2150 can be specifically disabled via consensus parameter or torrc.
2151 - Convert all internal path bias state to double-precision floating
2152 point, to avoid roundoff error and other issues.
2153 - Only record path bias information for circuits that have completed
2154 *two* hops. Assuming end-to-end tagging is the attack vector, this
2155 makes us more resilient to ambient circuit failure without any
2156 detection capability loss.
2158 o Minor bugfixes (log messages):
2159 - Rate-limit the "No circuits are opened. Relaxed timeout for a
2160 circuit with channel state open..." message to once per hour to
2161 keep it from filling the notice logs. Mitigates bug 7799 but does
2162 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
2163 - Avoid spurious warnings when configuring multiple client ports of
2164 which only some are nonlocal. Previously, we had claimed that some
2165 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2168 o Code simplifications and refactoring:
2169 - Get rid of a couple of harmless clang warnings, where we compared
2170 enums to ints. These warnings are newly introduced in clang 3.2.
2171 - Split the onion.c file into separate modules for the onion queue
2172 and the different handshakes it supports.
2173 - Remove the marshalling/unmarshalling code for sending requests to
2174 cpuworkers over a socket, and instead just send structs. The
2175 recipient will always be the same Tor binary as the sender, so
2176 any encoding is overkill.
2179 Changes in version 0.2.4.7-alpha - 2012-12-24
2180 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
2181 directory mirrors for more robust bootstrapping; fixes more issues where
2182 clients with changing network conditions refuse to make any circuits;
2183 adds initial support for exiting to IPv6 addresses; resumes being able
2184 to update our GeoIP database, and includes the geoip6 file this time;
2185 turns off the client-side DNS cache by default due to privacy risks;
2186 and fixes a variety of other issues.
2188 o Major features (client resilience):
2189 - Add a new "FallbackDir" torrc option to use when we can't use
2190 a directory mirror from the consensus (either because we lack a
2191 consensus, or because they're all down). Currently, all authorities
2192 are fallbacks by default, and there are no other default fallbacks,
2193 but that will change. This option will allow us to give clients a
2194 longer list of servers to try to get a consensus from when first
2195 connecting to the Tor network, and thereby reduce load on the
2196 directory authorities. Implements proposal 206, "Preconfigured
2197 directory sources for bootstrapping". We also removed the old
2198 "FallbackNetworkstatus" option, since we never got it working well
2199 enough to use it. Closes bug 572.
2200 - If we have no circuits open, use a relaxed timeout (the
2201 95-percentile cutoff) until a circuit succeeds. This heuristic
2202 should allow Tor to succeed at building circuits even when the
2203 network connection drastically changes. Should help with bug 3443.
2205 o Major features (IPv6):
2206 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
2207 connectivity, then set the IPv6Exit flag to 1. Also make sure your
2208 exit policy reads as you would like: the address * applies to all
2209 address families, whereas *4 is IPv4 address only, and *6 is IPv6
2210 addresses only. On the client side, you'll need to wait until the
2211 authorities have upgraded, wait for enough exits to support IPv6,
2212 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
2213 ticket 5547, implements proposal 117 as revised in proposal 208.
2215 We DO NOT recommend that clients with actual anonymity needs start
2216 using IPv6 over Tor yet, since not enough exits support it yet.
2218 o Major features (geoip database):
2219 - Maxmind began labelling Tor relays as being in country "A1",
2220 which breaks by-country node selection inside Tor. Now we use a
2221 script to replace "A1" ("Anonymous Proxy") entries in our geoip
2222 file with real country codes. This script fixes about 90% of "A1"
2223 entries automatically and uses manual country code assignments to
2224 fix the remaining 10%. See src/config/README.geoip for details.
2225 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
2226 Country database, as modified above.
2228 o Major bugfixes (client-side DNS):
2229 - Turn off the client-side DNS cache by default. Updating and using
2230 the DNS cache is now configurable on a per-client-port
2231 level. SOCKSPort, DNSPort, etc lines may now contain
2232 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
2233 cache these types of DNS answers when we receive them from an
2234 exit node in response to an application request on this port, and
2235 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
2236 cached DNS answers of these types, we shouldn't use them. It's
2237 potentially risky to use cached DNS answers at the client, since
2238 doing so can indicate to one exit what answers we've gotten
2239 for DNS lookups in the past. With IPv6, this becomes especially
2240 problematic. Using cached DNS answers for requests on the same
2241 circuit would present less linkability risk, since all traffic
2242 on a circuit is already linkable, but it would also provide
2243 little performance benefit: the exit node caches DNS replies
2244 too. Implements a simplified version of Proposal 205. Implements
2247 o Major bugfixes (other):
2248 - Alter circuit build timeout measurement to start at the point
2249 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
2250 initialization). This should make our timeout measurements more
2251 uniform. Previously, we were sometimes including ORconn setup time
2252 in our circuit build time measurements. Should resolve bug 3443.
2253 - Fix an assertion that could trigger in hibernate_go_dormant() when
2254 closing an or_connection_t: call channel_mark_for_close() rather
2255 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
2257 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
2258 7655; bugfix on 0.2.4.6-alpha.
2261 - Add a new torrc option "ServerTransportListenAddr" to let bridge
2262 operators select the address where their pluggable transports will
2263 listen for connections. Resolves ticket 7013.
2264 - Allow an optional $ before the node identity digest in the
2265 controller command GETINFO ns/id/<identity>, for consistency with
2266 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
2267 - Log packaged cell fullness as part of the heartbeat message.
2268 Diagnosis to try to determine the extent of bug 7743.
2270 o Minor features (IPv6):
2271 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
2272 prefer to hand out virtual IPv6 addresses, since there are more of
2273 them and we can't run out. To override this behavior and make IPv4
2274 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
2275 or DNSPort you're using for resolving. Implements ticket 7571.
2276 - AutomapHostsOnResolve responses are now randomized, to avoid
2277 annoying situations where Tor is restarted and applications
2278 connect to the wrong addresses.
2279 - Never try more than 1000 times to pick a new virtual address when
2280 AutomapHostsOnResolve is set. That's good enough so long as we
2281 aren't close to handing out our entire virtual address space;
2282 if you're getting there, it's best to switch to IPv6 virtual
2286 - The ADDRMAP command can no longer generate an ill-formed error
2287 code on a failed MAPADDRESS. It now says "internal" rather than
2288 an English sentence fragment with spaces in the middle. Bugfix on
2290 - Fix log messages and comments to avoid saying "GMT" when we mean
2291 "UTC". Fixes bug 6113.
2292 - Compile on win64 using mingw64. Fixes bug 7260; patches from
2294 - Fix a crash when debugging unit tests on Windows: deallocate a
2295 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
2296 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
2299 - The DirServer option is now DirAuthority, for consistency with
2300 current naming patterns. You can still use the old DirServer form.
2302 o Code simplification and refactoring:
2303 - Move the client-side address-map/virtual-address/DNS-cache code
2304 out of connection_edge.c into a new addressmap.c module.
2305 - Remove unused code for parsing v1 directories and "running routers"
2306 documents. Fixes bug 6887.
2309 Changes in version 0.2.3.25 - 2012-11-19
2310 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2311 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2312 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2313 programmer, and friend. Unstinting in his dedication to the cause of
2314 freedom, he inspired and helped many of us as we began our work on
2315 anonymity, and inspires us still. Please honor his memory by writing
2316 software to protect people's freedoms, and by helping others to do so.
2318 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2319 significantly reduced directory overhead (via microdescriptors),
2320 enormous crypto performance improvements for fast relays on new
2321 enough hardware, a new v3 TLS handshake protocol that can better
2322 resist fingerprinting, support for protocol obfuscation plugins (aka
2323 pluggable transports), better scalability for hidden services, IPv6
2324 support for bridges, performance improvements like allowing clients
2325 to skip the first round-trip on the circuit ("optimistic data") and
2326 refilling token buckets more often, a new "stream isolation" design
2327 to isolate different applications on different circuits, and many
2328 stability, security, and privacy fixes.
2331 - Tor tries to wipe potentially sensitive data after using it, so
2332 that if some subsequent security failure exposes Tor's memory,
2333 the damage will be limited. But we had a bug where the compiler
2334 was eliminating these wipe operations when it decided that the
2335 memory was no longer visible to a (correctly running) program,
2336 hence defeating our attempt at defense in depth. We fix that
2337 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2338 is unlikely to optimize away. Future versions of Tor may use
2339 a less ridiculously heavy approach for this. Fixes bug 7352.
2340 Reported in an article by Andrey Karpov.
2343 - Fix a harmless bug when opting against publishing a relay descriptor
2344 because DisableNetwork is set. Fixes bug 7464; bugfix on
2348 Changes in version 0.2.4.6-alpha - 2012-11-13
2349 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
2350 makes our defense-in-depth memory wiping more reliable, and begins to
2351 count IPv6 addresses in bridge statistics,
2354 - Fix an assertion failure that could occur when closing a connection
2355 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
2357 - Tor tries to wipe potentially sensitive data after using it, so
2358 that if some subsequent security failure exposes Tor's memory,
2359 the damage will be limited. But we had a bug where the compiler
2360 was eliminating these wipe operations when it decided that the
2361 memory was no longer visible to a (correctly running) program,
2362 hence defeating our attempt at defense in depth. We fix that
2363 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2364 is unlikely to optimize away. Future versions of Tor may use
2365 a less ridiculously heavy approach for this. Fixes bug 7352.
2366 Reported in an article by Andrey Karpov.
2369 - Add GeoIP database for IPv6 addresses. The new config option
2371 - Bridge statistics now count bridge clients connecting over IPv6:
2372 bridge statistics files now list "bridge-ip-versions" and
2373 extra-info documents list "geoip6-db-digest". The control protocol
2374 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
2375 implementation by "shkoo", addressing ticket 5055.
2378 - Warn when we are binding low ports when hibernation is enabled;
2379 previously we had warned when we were _advertising_ low ports with
2380 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2381 - Fix a harmless bug when opting against publishing a relay descriptor
2382 because DisableNetwork is set. Fixes bug 7464; bugfix on
2384 - Add warning message when a managed proxy dies during configuration.
2385 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
2386 - Fix a linking error when building tor-fw-helper without miniupnp.
2387 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
2388 - Check for closing an or_connection_t without going through correct
2389 channel functions; emit a warning and then call
2390 connection_or_close_for_error() so we don't assert as in bugs 7212
2392 - Compile correctly on compilers without C99 designated initializer
2393 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
2394 - Avoid a possible assert that can occur when channel_send_destroy() is
2395 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
2396 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
2397 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
2398 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
2399 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
2401 o Code simplification and refactoring:
2402 - Start using OpenBSD's implementation of queue.h, so that we don't
2403 need to hand-roll our own pointer and list structures whenever we
2404 need them. (We can't rely on a sys/queue.h, since some operating
2405 systems don't have them, and the ones that do have them don't all
2406 present the same extensions.)
2409 Changes in version 0.2.4.5-alpha - 2012-10-25
2410 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
2411 two important security vulnerabilities that could lead to remotely
2412 triggerable relay crashes, fix a major bug that was preventing clients
2413 from choosing suitable exit nodes, and refactor some of our code.
2415 o Major bugfixes (security, also in 0.2.3.24-rc):
2416 - Fix a group of remotely triggerable assertion failures related to
2417 incorrect link protocol negotiation. Found, diagnosed, and fixed
2418 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2420 - Fix a denial of service attack by which any directory authority
2421 could crash all the others, or by which a single v2 directory
2422 authority could crash everybody downloading v2 directory
2423 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2425 o Major bugfixes (also in 0.2.3.24-rc):
2426 - When parsing exit policy summaries from microdescriptors, we had
2427 previously been ignoring the last character in each one, so that
2428 "accept 80,443,8080" would be treated by clients as indicating
2429 a node that allows access to ports 80, 443, and 808. That would
2430 lead to clients attempting connections that could never work,
2431 and ignoring exit nodes that would support their connections. Now
2432 clients parse these exit policy summaries correctly. Fixes bug 7192;
2433 bugfix on 0.2.3.1-alpha.
2435 o Minor bugfixes (also in 0.2.3.24-rc):
2436 - Clients now consider the ClientRejectInternalAddresses config option
2437 when using a microdescriptor consensus stanza to decide whether
2438 an exit relay would allow exiting to an internal address. Fixes
2439 bug 7190; bugfix on 0.2.3.1-alpha.
2442 - Only disable TLS session ticket support when running as a TLS
2443 server. Now clients will blend better with regular Firefox
2444 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
2446 o Code simplification and refactoring:
2447 - Start using OpenBSD's implementation of queue.h (originally by
2449 - Move the entry node code from circuitbuild.c to its own file.
2450 - Move the circuit build timeout tracking code from circuitbuild.c
2454 Changes in version 0.2.3.24-rc - 2012-10-25
2455 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
2456 could lead to remotely triggerable relay crashes, and fixes
2457 a major bug that was preventing clients from choosing suitable exit
2460 o Major bugfixes (security):
2461 - Fix a group of remotely triggerable assertion failures related to
2462 incorrect link protocol negotiation. Found, diagnosed, and fixed
2463 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2465 - Fix a denial of service attack by which any directory authority
2466 could crash all the others, or by which a single v2 directory
2467 authority could crash everybody downloading v2 directory
2468 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2471 - When parsing exit policy summaries from microdescriptors, we had
2472 previously been ignoring the last character in each one, so that
2473 "accept 80,443,8080" would be treated by clients as indicating
2474 a node that allows access to ports 80, 443, and 808. That would
2475 lead to clients attempting connections that could never work,
2476 and ignoring exit nodes that would support their connections. Now
2477 clients parse these exit policy summaries correctly. Fixes bug 7192;
2478 bugfix on 0.2.3.1-alpha.
2481 - Clients now consider the ClientRejectInternalAddresses config option
2482 when using a microdescriptor consensus stanza to decide whether
2483 an exit relay would allow exiting to an internal address. Fixes
2484 bug 7190; bugfix on 0.2.3.1-alpha.
2487 Changes in version 0.2.4.4-alpha - 2012-10-20
2488 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
2489 vulnerability introduced by a change in OpenSSL, fixes a remotely
2490 triggerable assert, and adds new channel_t and circuitmux_t abstractions
2491 that will make it easier to test new connection transport and cell
2492 scheduling algorithms.
2494 o New directory authorities (also in 0.2.3.23-rc):
2495 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2496 authority. Closes ticket 5749.
2498 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
2499 - Disable TLS session tickets. OpenSSL's implementation was giving
2500 our TLS session keys the lifetime of our TLS context objects, when
2501 perfect forward secrecy would want us to discard anything that
2502 could decrypt a link connection as soon as the link connection
2503 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2504 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2505 - Discard extraneous renegotiation attempts once the V3 link
2506 protocol has been initiated. Failure to do so left us open to
2507 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2508 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2510 o Internal abstraction features:
2511 - Introduce new channel_t abstraction between circuits and
2512 or_connection_t to allow for implementing alternate OR-to-OR
2513 transports. A channel_t is an abstract object which can either be a
2514 cell-bearing channel, which is responsible for authenticating and
2515 handshaking with the remote OR and transmitting cells to and from
2516 it, or a listening channel, which spawns new cell-bearing channels
2517 at the request of remote ORs. Implements part of ticket 6465.
2518 - Also new is the channel_tls_t subclass of channel_t, adapting it
2519 to the existing or_connection_t code. The V2/V3 protocol handshaking
2520 code which formerly resided in command.c has been moved below the
2521 channel_t abstraction layer and may be found in channeltls.c now.
2522 Implements the rest of ticket 6465.
2523 - Introduce new circuitmux_t storing the queue of circuits for
2524 a channel; this encapsulates and abstracts the queue logic and
2525 circuit selection policy, and allows the latter to be overridden
2526 easily by switching out a policy object. The existing EWMA behavior
2527 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
2529 o Required libraries:
2530 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
2531 strongly recommended.
2534 - Warn users who run hidden services on a Tor client with
2535 UseEntryGuards disabled that their hidden services will be
2536 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2537 attack which motivated Tor to support entry guards in the first
2538 place). Resolves ticket 6889.
2539 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2540 dhill. Resolves ticket 6982.
2541 - Option OutboundBindAddress can be specified multiple times and
2542 accepts IPv6 addresses. Resolves ticket 6876.
2544 o Minor bugfixes (also in 0.2.3.23-rc):
2545 - Don't serve or accept v2 hidden service descriptors over a
2546 relay's DirPort. It's never correct to do so, and disabling it
2547 might make it more annoying to exploit any bugs that turn up in the
2548 descriptor-parsing code. Fixes bug 7149.
2549 - Fix two cases in src/or/transports.c where we were calling
2550 fmt_addr() twice in a parameter list. Bug found by David
2551 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2552 - Fix memory leaks whenever we logged any message about the "path
2553 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2554 - When relays refuse a "create" cell because their queue of pending
2555 create cells is too big (typically because their cpu can't keep up
2556 with the arrival rate), send back reason "resource limit" rather
2557 than reason "internal", so network measurement scripts can get a
2558 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
2561 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2562 - Free some more still-in-use memory at exit, to make hunting for
2563 memory leaks easier. Resolves bug 7029.
2564 - When a Tor client gets a "truncated" relay cell, the first byte of
2565 its payload specifies why the circuit was truncated. We were
2566 ignoring this 'reason' byte when tearing down the circuit, resulting
2567 in the controller not being told why the circuit closed. Now we
2568 pass the reason from the truncated cell to the controller. Bugfix
2569 on 0.1.2.3-alpha; fixes bug 7039.
2570 - Downgrade "Failed to hand off onionskin" messages to "debug"
2571 severity, since they're typically redundant with the "Your computer
2572 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2573 - Make clients running with IPv6 bridges connect over IPv6 again,
2574 even without setting new config options ClientUseIPv6 and
2575 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
2576 - Use square brackets around IPv6 addresses in numerous places
2577 that needed them, including log messages, HTTPS CONNECT proxy
2578 requests, TransportProxy statefile entries, and pluggable transport
2579 extra-info lines. Fixes bug 7011; patch by David Fifield.
2581 o Code refactoring and cleanup:
2582 - Source files taken from other packages now reside in src/ext;
2583 previously they were scattered around the rest of Tor.
2584 - Avoid use of reserved identifiers in our C code. The C standard
2585 doesn't like us declaring anything that starts with an
2586 underscore, so let's knock it off before we get in trouble. Fix
2587 for bug 1031; bugfix on the first Tor commit.
2590 Changes in version 0.2.3.23-rc - 2012-10-20
2591 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
2592 vulnerability introduced by a change in OpenSSL, and fixes a variety
2593 of smaller bugs in preparation for the release.
2595 o New directory authorities:
2596 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2597 authority. Closes ticket 5749.
2599 o Major bugfixes (security/privacy):
2600 - Disable TLS session tickets. OpenSSL's implementation was giving
2601 our TLS session keys the lifetime of our TLS context objects, when
2602 perfect forward secrecy would want us to discard anything that
2603 could decrypt a link connection as soon as the link connection
2604 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2605 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2606 - Discard extraneous renegotiation attempts once the V3 link
2607 protocol has been initiated. Failure to do so left us open to
2608 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2609 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2612 - Fix a possible crash bug when checking for deactivated circuits
2613 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2614 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2616 o Minor bugfixes (on 0.2.3.x):
2617 - Fix two cases in src/or/transports.c where we were calling
2618 fmt_addr() twice in a parameter list. Bug found by David
2619 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2620 - Convert an assert in the pathbias code to a log message. The assert
2621 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2622 bugfix on 0.2.3.17-beta.
2623 - Fix memory leaks whenever we logged any message about the "path
2624 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2626 o Minor bugfixes (on 0.2.2.x and earlier):
2627 - Don't serve or accept v2 hidden service descriptors over a relay's
2628 DirPort. It's never correct to do so, and disabling it might
2629 make it more annoying to exploit any bugs that turn up in the
2630 descriptor-parsing code. Fixes bug 7149.
2631 - When relays refuse a "create" cell because their queue of pending
2632 create cells is too big (typically because their cpu can't keep up
2633 with the arrival rate), send back reason "resource limit" rather
2634 than reason "internal", so network measurement scripts can get a
2635 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
2636 - Correct file sizes when reading binary files on Cygwin, to avoid
2637 a bug where Tor would fail to read its state file. Fixes bug 6844;
2638 bugfix on 0.1.2.7-alpha.
2639 - Avoid undefined behaviour when parsing the list of supported
2640 rendezvous/introduction protocols in a hidden service descriptor.
2641 Previously, Tor would have confused (as-yet-unused) protocol version
2642 numbers greater than 32 with lower ones on many platforms. Fixes
2643 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2645 o Documentation fixes:
2646 - Clarify that hidden services are TCP only. Fixes bug 6024.
2649 Changes in version 0.2.4.3-alpha - 2012-09-22
2650 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
2651 assertion, resumes letting relays test reachability of their DirPort,
2652 and cleans up a bunch of smaller bugs.
2655 - Fix an assertion failure in tor_timegm() that could be triggered
2656 by a badly formatted directory object. Bug found by fuzzing with
2657 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2660 - Fix a possible crash bug when checking for deactivated circuits
2661 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
2662 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
2663 - Allow routers to detect that their own DirPorts are running. When
2664 we removed support for versions_supports_begindir, we also
2665 accidentally removed the mechanism we used to self-test our
2666 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
2667 bugfix on 0.2.4.2-alpha.
2669 o Security features:
2670 - Switch to a completely time-invariant approach for picking nodes
2671 weighted by bandwidth. Our old approach would run through the
2672 part of the loop after it had made its choice slightly slower
2673 than it ran through the part of the loop before it had made its
2674 choice. Addresses ticket 6538.
2675 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
2676 by tor2web clients allows hidden services to identify tor2web
2677 clients through their repeated selection of the same rendezvous
2678 and introduction point circuit endpoints (their guards). Resolves
2682 - Enable Tor to read configuration, state, and key information from
2683 a FIFO. Previously Tor would only read from files with a positive
2684 stat.st_size. Code from meejah; fixes bug 6044.
2687 - Correct file sizes when reading binary files on Cygwin, to avoid
2688 a bug where Tor would fail to read its state file. Fixes bug 6844;
2689 bugfix on 0.1.2.7-alpha.
2690 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
2691 bugfix on 0.2.0.3-alpha.
2692 - When complaining about a client port on a public address, log
2693 which address we're complaining about. Fixes bug 4020; bugfix on
2694 0.2.3.3-alpha. Patch by Tom Fitzhenry.
2695 - Convert an assert in the pathbias code to a log message. The assert
2696 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
2697 bugfix on 0.2.3.17-beta.
2698 - Our new buildsystem was overzealous about rebuilding manpages: it
2699 would rebuild them all whenever any one of them changed. Now our
2700 dependency checking should be correct. Fixes bug 6843; bugfix on
2702 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
2703 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
2704 - Correct log printout about which address family is preferred
2705 when connecting to a bridge with both an IPv4 and IPv6 OR port.
2706 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
2708 o Minor bugfixes (code cleanliness):
2709 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
2710 with large values. This situation was untriggered, but nevertheless
2711 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
2712 - Reject consensus votes with more than 64 known-flags. We aren't even
2713 close to that limit yet, and our code doesn't handle it correctly.
2714 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
2715 - Avoid undefined behaviour when parsing the list of supported
2716 rendezvous/introduction protocols in a hidden service descriptor.
2717 Previously, Tor would have confused (as-yet-unused) protocol version
2718 numbers greater than 32 with lower ones on many platforms. Fixes
2719 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
2720 - Fix handling of rendezvous client authorization types over 8.
2721 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
2722 - Fix building with older versions of GCC (2.95, for one) that don't
2723 like preprocessor directives inside macro arguments. Found by
2724 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
2725 - Switch weighted node selection rule from using a list of doubles
2726 to using a list of int64_t. This change should make the process
2727 slightly easier to debug and maintain. Needed to finish ticket 6538.
2729 o Code simplification and refactoring:
2730 - Move the generic "config" code into a new file, and have "config.c"
2731 hold only torrc- and state-related code. Resolves ticket 6823.
2732 - Move the core of our "choose a weighted element at random" logic
2733 into its own function, and give it unit tests. Now the logic is
2734 testable, and a little less fragile too.
2735 - Removed the testing_since field of node_t, which hasn't been used
2736 for anything since 0.2.0.9-alpha.
2738 o Documentation fixes:
2739 - Clarify that hidden services are TCP only. Fixes bug 6024.
2740 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
2744 Changes in version 0.2.3.22-rc - 2012-09-11
2745 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
2749 - Fix an assertion failure in tor_timegm() that could be triggered
2750 by a badly formatted directory object. Bug found by fuzzing with
2751 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2754 - Avoid segfault when starting up having run with an extremely old
2755 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2759 Changes in version 0.2.2.39 - 2012-09-11
2760 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2764 - Fix an assertion failure in tor_timegm() that could be triggered
2765 by a badly formatted directory object. Bug found by fuzzing with
2766 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2767 - Do not crash when comparing an address with port value 0 to an
2768 address policy. This bug could have been used to cause a remote
2769 assertion failure by or against directory authorities, or to
2770 allow some applications to crash clients. Fixes bug 6690; bugfix
2774 Changes in version 0.2.4.2-alpha - 2012-09-10
2775 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
2776 raises the default rate limiting even more, and makes the bootstrapping
2777 log messages less noisy.
2780 - Automatically forward the TCP ports of pluggable transport
2781 proxies using tor-fw-helper if PortForwarding is enabled. Implements
2785 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
2786 to 1GB/1GB. The previous defaults were intended to be "basically
2787 infinite", but it turns out they're now limiting our 100mbit+
2788 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
2789 last time we raised it).
2792 - Detect when we're running with a version of OpenSSL other than the
2793 one we compiled with. This has occasionally given people hard-to-
2795 - Log fewer lines at level "notice" about our OpenSSL and Libevent
2796 versions and capabilities when everything is going right. Resolves
2797 part of ticket 6736.
2798 - Directory authorities no long accept descriptors for any version of
2799 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
2800 These versions are insecure, unsupported, or both. Implements
2804 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
2805 to start with a triple-underscore so the controller won't touch it.
2806 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
2807 - Avoid segfault when starting up having run with an extremely old
2808 version of Tor and parsing its state file. Fixes bug 6801; bugfix
2810 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
2811 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
2812 - Don't follow the NULL pointer if microdescriptor generation fails.
2813 (This does not appear to be triggerable, but it's best to be safe.)
2814 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
2815 - Fix mis-declared dependencies on src/common/crypto.c and
2816 src/or/tor_main.c that could break out-of-tree builds under some
2817 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
2818 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
2819 6778; bugfix on 0.2.4.1-alpha.
2820 - Fix a harmless (in this case) build warning for implicitly
2821 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
2824 - Now that all versions before 0.2.2.x are disallowed, we no longer
2825 need to work around their missing features. Thus we can remove a
2826 bunch of compatibility code.
2829 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
2830 TCP ports to forward. In the past it only accepted two ports:
2831 the ORPort and the DirPort.
2834 Changes in version 0.2.4.1-alpha - 2012-09-05
2835 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
2836 bridgedb; lets relays use IPv6 addresses and directory authorities
2837 advertise them; and switches to a cleaner build interface.
2839 This is the first alpha release in a new series, so expect there to
2840 be bugs. Users who would rather test out a more stable branch should
2841 stay with 0.2.3.x for now.
2843 o Major features (bridges):
2844 - Bridges now report the pluggable transports they support to the
2845 bridge authority, so it can pass the supported transports on to
2846 bridgedb and/or eventually do reachability testing. Implements
2849 o Major features (IPv6):
2850 - Bridge authorities now accept IPv6 bridge addresses and include
2851 them in network status documents. Implements ticket 5534.
2852 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
2853 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
2854 to happen. Implements ticket 5535.
2855 - All kind of relays, not just bridges, can now advertise an IPv6
2856 OR port. Implements ticket 6362.
2857 - Directory authorities vote on IPv6 OR ports using the new consensus
2858 method 14. Implements ticket 6363.
2860 o Major features (build):
2861 - Switch to a nonrecursive Makefile structure. Now instead of each
2862 Makefile.am invoking other Makefile.am's, there is a master
2863 Makefile.am that includes the others. This change makes our build
2864 process slightly more maintainable, and improves parallelism for
2865 building with make -j. Original patch by Stewart Smith; various
2866 fixes by Jim Meyering.
2867 - Where available, we now use automake's "silent" make rules by
2868 default, so that warnings are easier to spot. You can get the old
2869 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
2871 o Minor features (code security and spec conformance):
2872 - Clear keys and key-derived material left on the stack in
2873 rendservice.c and rendclient.c. Check return value of
2874 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
2875 These fixes should make us more forward-secure against cold-boot
2876 attacks and the like. Fixes bug 2385.
2877 - Reject EXTEND cells sent to nonexistent streams. According to the
2878 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
2879 we were only checking for stream IDs that were currently in use.
2880 Found while hunting for more instances of bug 6271. Bugfix on
2881 0.0.2pre8, which introduced incremental circuit construction.
2883 o Minor features (streamlining);
2884 - No longer include the "opt" prefix when generating routerinfos
2885 or v2 directories: it has been needless since Tor 0.1.2. Closes
2887 - Remove some now-needless code that tried to aggressively flush
2888 OR connections as data was added to them. Since 0.2.0.1-alpha, our
2889 cell queue logic has saved us from the failure mode that this code
2890 was supposed to prevent. Removing this code will limit the number
2891 of baroque control flow paths through Tor's network logic. Reported
2892 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
2894 o Minor features (controller):
2895 - Add a "GETINFO signal/names" control port command. Implements
2897 - Provide default values for all options via "GETINFO config/defaults".
2898 Implements ticket 4971.
2900 o Minor features (IPv6):
2901 - New config option "AuthDirHasIPv6Connectivity 1" that directory
2902 authorities should set if they have IPv6 connectivity and want to
2903 do reachability tests for IPv6 relays. Implements feature 5974.
2904 - A relay with an IPv6 OR port now sends that address in NETINFO
2905 cells (in addition to its other address). Implements ticket 6364.
2907 o Minor features (log messages):
2908 - Omit the first heartbeat log message, because it never has anything
2909 useful to say, and it clutters up the bootstrapping messages.
2910 Resolves ticket 6758.
2911 - Don't log about reloading the microdescriptor cache at startup. Our
2912 bootstrap warnings are supposed to tell the user when there's a
2913 problem, and our bootstrap notices say when there isn't. Resolves
2914 ticket 6759; bugfix on 0.2.2.6-alpha.
2915 - Don't log "I learned some more directory information" when we're
2916 reading cached directory information. Reserve it for when new
2917 directory information arrives in response to a fetch. Resolves
2919 - Prevent rounding error in path bias counts when scaling
2920 them down, and use the correct scale factor default. Also demote
2921 some path bias related log messages down a level and make others
2922 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
2923 - We no longer warn so much when generating manpages from their
2926 o Code simplifications and refactoring:
2927 - Enhance our internal sscanf replacement so that we can eliminate
2928 the last remaining uses of the system sscanf. (Though those uses
2929 of sscanf were safe, sscanf itself is generally error prone, so
2930 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
2932 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
2933 - Move last_reachable and testing_since from routerinfo_t to node_t.
2934 Implements ticket 5529.
2935 - Add replaycache_t structure, functions and unit tests, then refactor
2936 rend_service_introduce() to be more clear to read, improve, debug,
2937 and test. Resolves bug 6177.
2938 - Finally remove support for malloc_good_size and malloc_usable_size.
2939 We had hoped that these functions would let us eke a little more
2940 memory out of our malloc implementation. Unfortunately, the only
2941 implementations that provided these functions are also ones that
2942 are already efficient about not overallocation: they never got us
2943 more than 7 or so bytes per allocation. Removing them saves us a
2944 little code complexity and a nontrivial amount of build complexity.
2947 - Tor maintainers now require Automake version 1.9 or later to build
2948 Tor from the Git repository. (Automake is not required when building
2949 from a source distribution.)
2952 Changes in version 0.2.3.21-rc - 2012-09-05
2953 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
2954 series. It fixes a trio of potential security bugs, fixes a bug where
2955 we were leaving some of the fast relays out of the microdescriptor
2956 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
2957 and cleans up other smaller issues.
2959 o Major bugfixes (security):
2960 - Tear down the circuit if we get an unexpected SENDME cell. Clients
2961 could use this trick to make their circuits receive cells faster
2962 than our flow control would have allowed, or to gum up the network,
2963 or possibly to do targeted memory denial-of-service attacks on
2964 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
2965 from July 2002, before the release of Tor 0.0.0. We had committed
2966 this patch previously, but we had to revert it because of bug 6271.
2967 Now that 6271 is fixed, this patch appears to work.
2968 - Reject any attempt to extend to an internal address. Without
2969 this fix, a router could be used to probe addresses on an internal
2970 network to see whether they were accepting connections. Fixes bug
2971 6710; bugfix on 0.0.8pre1.
2972 - Do not crash when comparing an address with port value 0 to an
2973 address policy. This bug could have been used to cause a remote
2974 assertion failure by or against directory authorities, or to
2975 allow some applications to crash clients. Fixes bug 6690; bugfix
2979 - Remove the upper bound on microdescriptor length. We were hitting
2980 the limit for routers with complex exit policies or family
2981 declarations, causing clients to not use them. Fixes the first
2982 piece of bug 6404; fix on 0.2.2.6-alpha.
2983 - Detect "ORPort 0" as meaning, uniformly, that we're not running
2984 as a relay. Previously, some of our code would treat the presence
2985 of any ORPort line as meaning that we should act like a relay,
2986 even though our new listener code would correctly not open any
2987 ORPorts for ORPort 0. Similar bugs in other Port options are also
2988 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
2991 - Avoid a pair of double-free and use-after-mark bugs that can
2992 occur with certain timings in canceled and re-received DNS
2993 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
2994 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
2995 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
2996 - Allow one-hop directory fetching circuits the full "circuit build
2997 timeout" period, rather than just half of it, before failing them
2998 and marking the relay down. This fix should help reduce cases where
2999 clients declare relays (or worse, bridges) unreachable because
3000 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
3001 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
3003 - Authorities no longer include any router in their microdescriptor
3004 consensuses for which they couldn't generate or agree on a
3005 microdescriptor. Fixes the second piece of bug 6404; fix on
3007 - Detect and reject attempts to specify both "FooPort" and
3008 "FooPort 0" in the same configuration domain. (It's still okay
3009 to have a FooPort in your configuration file, and use "FooPort 0"
3010 on the command line to disable it.) Fixes the second half of bug
3011 6507; bugfix on 0.2.3.3-alpha.
3012 - Make wildcarded addresses (that is, ones beginning with "*.") work
3013 when provided via the controller's MapAddress command. Previously,
3014 they were accepted, but we never actually noticed that they were
3015 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
3016 - Avoid crashing on a malformed state file where EntryGuardPathBias
3017 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
3018 - Add a (probably redundant) memory clear between iterations of
3019 the router status voting loop, to prevent future coding errors
3020 where data might leak between iterations of the loop. Resolves
3023 o Minor bugfixes (log messages):
3024 - Downgrade "set buildtimeout to low value" messages to "info"
3025 severity; they were never an actual problem, there was never
3026 anything reasonable to do about them, and they tended to spam logs
3027 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
3028 - Downgrade path-bias warning messages to "info". We'll try to get
3029 them working better in 0.2.4. Add internal circuit construction
3030 state to protect against the noisy warn message "Unexpectedly high
3031 circuit_successes". Also add some additional rate-limited notice
3032 messages to help determine the root cause of the warn. Fixes bug
3033 6475. Bugfix against 0.2.3.17-beta.
3034 - Move log message when unable to find a microdesc in a routerstatus
3035 entry to parse time. Previously we'd spam this warning every time
3036 we tried to figure out which microdescriptors to download. Fixes
3037 the third piece of bug 6404; fix on 0.2.3.18-rc.
3040 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
3041 change when the authority is deciding whether to accept a newly
3042 uploaded descriptor. Implements ticket 6423.
3043 - Add missing documentation for consensus and microdesc files.
3044 Resolves ticket 6732.
3047 Changes in version 0.2.2.38 - 2012-08-12
3048 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3049 attack that could in theory leak path information.
3052 - Avoid an uninitialized memory read when reading a vote or consensus
3053 document that has an unrecognized flavor name. This read could
3054 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3055 - Try to leak less information about what relays a client is
3056 choosing to a side-channel attacker. Previously, a Tor client would
3057 stop iterating through the list of available relays as soon as it
3058 had chosen one, thus finishing a little earlier when it picked
3059 a router earlier in the list. If an attacker can recover this
3060 timing information (nontrivial but not proven to be impossible),
3061 they could learn some coarse-grained information about which relays
3062 a client was picking (middle nodes in particular are likelier to
3063 be affected than exits). The timing attack might be mitigated by
3064 other factors (see bug 6537 for some discussion), but it's best
3065 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3068 Changes in version 0.2.3.20-rc - 2012-08-05
3069 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
3070 series. It fixes a pair of code security bugs and a potential anonymity
3071 issue, updates our RPM spec files, and cleans up other smaller issues.
3074 - Avoid read-from-freed-memory and double-free bugs that could occur
3075 when a DNS request fails while launching it. Fixes bug 6480;
3076 bugfix on 0.2.0.1-alpha.
3077 - Avoid an uninitialized memory read when reading a vote or consensus
3078 document that has an unrecognized flavor name. This read could
3079 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3080 - Try to leak less information about what relays a client is
3081 choosing to a side-channel attacker. Previously, a Tor client would
3082 stop iterating through the list of available relays as soon as it
3083 had chosen one, thus finishing a little earlier when it picked
3084 a router earlier in the list. If an attacker can recover this
3085 timing information (nontrivial but not proven to be impossible),
3086 they could learn some coarse-grained information about which relays
3087 a client was picking (middle nodes in particular are likelier to
3088 be affected than exits). The timing attack might be mitigated by
3089 other factors (see bug 6537 for some discussion), but it's best
3090 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3093 - Try to make the warning when giving an obsolete SOCKSListenAddress
3094 a little more useful.
3095 - Terminate active server managed proxies if Tor stops being a
3096 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
3097 - Provide a better error message about possible OSX Asciidoc failure
3098 reasons. Fixes bug 6436.
3099 - Warn when Tor is configured to use accounting in a way that can
3100 link a hidden service to some other hidden service or public
3101 address. Resolves ticket 6490.
3104 - Check return value of fputs() when writing authority certificate
3105 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
3106 - Ignore ServerTransportPlugin lines when Tor is not configured as
3107 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
3108 - When disabling guards for having too high a proportion of failed
3109 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
3113 - Update our default RPM spec files to work with mock and rpmbuild
3114 on RHEL/Fedora. They have an updated set of dependencies and
3115 conflicts, a fix for an ancient typo when creating the "_tor"
3116 user, and better instructions. Thanks to Ondrej Mikle for the
3117 patch series. Fixes bug 6043.
3120 - Make it possible to set the TestingTorNetwork configuration
3121 option using AlternateDirAuthority and AlternateBridgeAuthority
3122 as an alternative to setting DirServer. Addresses ticket 6377.
3125 - Clarify the documentation for the Alternate*Authority options.
3127 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3129 o Code simplification and refactoring:
3130 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3131 10 lines. Also, don't nest them. Doing so in the past has
3132 led to hard-to-debug code. The new style is to use the
3133 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3136 Changes in version 0.2.3.19-rc - 2012-07-06
3137 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
3138 series. It fixes the compile on Windows, reverts to a GeoIP database
3139 that isn't as broken, and fixes a flow control bug that has been around
3140 since the beginning of Tor.
3143 - Fix a bug handling SENDME cells on nonexistent streams that could
3144 result in bizarre window values. Report and patch contributed
3145 pseudonymously. Fixes part of bug 6271. This bug was introduced
3146 before the first Tor release, in svn commit r152.
3147 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
3148 June 2012 database, Maxmind marked many Tor relays as country "A1",
3149 which will cause risky behavior for clients that set EntryNodes
3150 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
3151 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
3152 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
3155 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
3156 bugfix on 0.2.1.10-alpha.
3159 Changes in version 0.2.3.18-rc - 2012-06-28
3160 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
3161 series. It fixes a few smaller bugs, but generally appears stable.
3162 Please test it and let us know whether it is!
3165 - Allow wildcarded mapaddress targets to be specified on the
3166 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
3167 - Make our linker option detection code more robust against linkers
3168 such as on FreeBSD 8, where a bad combination of options completes
3169 successfully but makes an unrunnable binary. Fixes bug 6173;
3170 bugfix on 0.2.3.17-beta.
3172 o Minor bugfixes (on 0.2.2.x and earlier):
3173 - Avoid a false positive in the util/threads unit test by increasing
3174 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3175 - Replace "Sending publish request" log messages with "Launching
3176 upload", so that they no longer confusingly imply that we're
3177 sending something to a directory we might not even be connected
3178 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3179 - Make sure to set *socket_error in all error cases in
3180 connection_connect(), so it can't produce a warning about
3181 errno being zero from errno_to_orconn_end_reason(). Bugfix on
3182 0.2.1.1-alpha; resolves ticket 6028.
3183 - Downgrade "Got a certificate, but we already have it" log messages
3184 from warning to info, except when we're a dirauth. Fixes bug 5238;
3185 bugfix on 0.2.1.7-alpha.
3186 - When checking for requested signatures on the latest consensus
3187 before serving it to a client, make sure to check the right
3188 consensus flavor. Bugfix on 0.2.2.6-alpha.
3189 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3190 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3192 o Minor bugfixes (on 0.2.3.x):
3193 - Make format_helper_exit_status() avoid unnecessary space padding
3194 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
3196 - Downgrade a message about cleaning the microdescriptor cache to
3197 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
3198 - Log a BUG message at severity INFO if we have a networkstatus with
3199 a missing entry for some microdescriptor. Continues on a patch
3201 - Improve the log message when a managed proxy fails to launch. Fixes
3202 bug 5099; bugfix on 0.2.3.6-alpha.
3203 - Don't do DNS lookups when parsing corrupted managed proxy protocol
3204 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
3205 - When formatting wildcarded address mappings for the controller,
3206 be sure to include "*." as appropriate. Partially fixes bug 6244;
3207 bugfix on 0.2.3.9-alpha.
3208 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
3209 Bugfix on 0.2.3.13-alpha.
3210 - Stop logging messages about running with circuit timeout learning
3211 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
3212 - Disable a spurious warning about reading on a marked and flushing
3213 connection. We shouldn't be doing that, but apparently we
3214 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
3215 - Fix a bug that stopped AllowDotExit from working on addresses
3216 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
3219 o Code simplification, refactoring, unit tests:
3220 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3221 Libevent's notion of cached time when possible.
3222 - Remove duplicate code for invoking getrlimit() from control.c.
3223 - Add a unit test for the environment_variable_names_equal function.
3226 - Document the --defaults-torrc option, and the new (in 0.2.3)
3227 semantics for overriding, extending, and clearing lists of
3228 options. Closes bug 4748.
3231 Changes in version 0.2.3.17-beta - 2012-06-15
3232 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
3233 gets our TLS handshake back on track for being able to blend in with
3234 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
3235 with Vidalia, and otherwise continues to get us closer to a release
3239 - Enable gcc and ld hardening by default. Resolves ticket 5210.
3240 - Update TLS cipher list to match Firefox 8 and later. Resolves
3242 - Implement the client side of proposal 198: remove support for
3243 clients falsely claiming to support standard ciphersuites that
3244 they can actually provide. As of modern OpenSSL versions, it's not
3245 necessary to fake any standard ciphersuite, and doing so prevents
3246 us from using better ciphersuites in the future, since servers
3247 can't know whether an advertised ciphersuite is really supported or
3248 not. Some hosts -- notably, ones with very old versions of OpenSSL
3249 or where OpenSSL has been built with ECC disabled -- will stand
3250 out because of this change; TBB users should not be affected.
3253 - Change the default value for DynamicDHGroups (introduced in
3254 0.2.3.9-alpha) to 0. This feature can make Tor relays less
3255 identifiable by their use of the mod_ssl DH group, but at
3256 the cost of some usability (#4721) and bridge tracing (#6087)
3257 regressions. Resolves ticket 5598.
3258 - Send a CRLF at the end of each STATUS_* control protocol event. This
3259 bug tickled a bug in Vidalia which would make it freeze. Fixes
3260 bug 6094; bugfix on 0.2.3.16-alpha.
3263 - Disable writing on marked-for-close connections when they are
3264 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
3265 bug 5263; bugfix on 0.0.2pre13, where we first added a special
3266 case for flushing marked connections.
3267 - Detect SSL handshake even when the initial attempt to write the
3268 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
3269 - Change the AllowDotExit rules so they should actually work.
3270 We now enforce AllowDotExit only immediately after receiving an
3271 address via SOCKS or DNSPort: other sources are free to provide
3272 .exit addresses after the resolution occurs. Fixes bug 3940;
3273 bugfix on 0.2.2.1-alpha.
3274 - Fix a (harmless) integer overflow in cell statistics reported by
3275 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
3276 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
3277 right places and never depends on the consensus parameters or
3278 computes adaptive timeouts when it is disabled. Fixes bug 5049;
3279 bugfix on 0.2.2.14-alpha.
3280 - When building Tor on Windows with -DUNICODE (not default), ensure
3281 that error messages, filenames, and DNS server names are always
3282 NUL-terminated when we convert them to a single-byte encoding.
3283 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
3284 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3285 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3286 - Fix an edge case where TestingTorNetwork is set but the authorities
3287 and relays all have an uptime of zero, where the private Tor network
3288 could briefly lack support for hidden services. Fixes bug 3886;
3289 bugfix on 0.2.2.18-alpha.
3290 - Correct the manpage's descriptions for the default values of
3291 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
3293 - Fix the documentation for the --hush and --quiet command line
3294 options, which changed their behavior back in 0.2.3.3-alpha.
3295 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
3299 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
3300 more information to it, so that we can track it down in case it
3301 returns again. Mitigates bug 5235.
3302 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
3303 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
3304 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
3305 - Warn the user when HTTPProxy, but no other proxy type, is
3306 configured. This can cause surprising behavior: it doesn't send
3307 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
3308 directory traffic only. Resolves ticket 4663.
3309 - Issue a notice if a guard completes less than 40% of your circuits.
3310 Threshold is configurable by torrc option PathBiasNoticeRate and
3311 consensus parameter pb_noticepct. There is additional, off-by-
3312 default code to disable guards which fail too many circuits.
3313 Addresses ticket 5458.
3314 - Update to the June 6 2012 Maxmind GeoLite Country database.
3316 o Code simplifications and refactoring:
3317 - Remove validate_pluggable_transports_config(): its warning
3318 message is now handled by connection_or_connect().
3321 Changes in version 0.2.2.37 - 2012-06-06
3322 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3323 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3327 - Work around a bug in OpenSSL that broke renegotiation with TLS
3328 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3329 the v2 Tor connection protocol when both sides were using OpenSSL
3330 1.0.1 would fail. Resolves ticket 6033.
3331 - When waiting for a client to renegotiate, don't allow it to add
3332 any bytes to the input buffer. This fixes a potential DoS issue.
3333 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3334 - Fix an edge case where if we fetch or publish a hidden service
3335 descriptor, we might build a 4-hop circuit and then use that circuit
3336 for exiting afterwards -- even if the new last hop doesn't obey our
3337 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3340 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3341 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3344 - Tell GCC and Clang to check for any errors in format strings passed
3345 to the tor_v*(print|scan)f functions.
3348 Changes in version 0.2.3.16-alpha - 2012-06-05
3349 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
3350 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3351 currently). It also fixes a variety of smaller bugs and other cleanups
3352 that get us closer to a release candidate.
3354 o Major bugfixes (general):
3355 - Work around a bug in OpenSSL that broke renegotiation with TLS
3356 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3357 the v2 Tor connection protocol when both sides were using OpenSSL
3358 1.0.1 would fail. Resolves ticket 6033.
3359 - When waiting for a client to renegotiate, don't allow it to add
3360 any bytes to the input buffer. This fixes a potential DoS issue.
3361 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3362 - Pass correct OR address to managed proxies (like obfsproxy),
3363 even when ORListenAddress is used. Fixes bug 4865; bugfix on
3365 - The advertised platform of a router now includes only its operating
3366 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
3367 service pack level (for Windows) or its CPU architecture (for Unix).
3368 We also no longer include the "git-XYZ" tag in the version. Resolves
3371 o Major bugfixes (clients):
3372 - If we are unable to find any exit that supports our predicted ports,
3373 stop calling them predicted, so that we don't loop and build
3374 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
3375 which introduced predicted ports.
3376 - Fix an edge case where if we fetch or publish a hidden service
3377 descriptor, we might build a 4-hop circuit and then use that circuit
3378 for exiting afterwards -- even if the new last hop doesn't obey our
3379 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3380 - Check at each new consensus whether our entry guards were picked
3381 long enough ago that we should rotate them. Previously, we only
3382 did this check at startup, which could lead to us holding a guard
3383 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3384 - When fetching a bridge descriptor from a bridge authority,
3385 always do so anonymously, whether we have been able to open
3386 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3387 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3388 but we'll need to wait for bug 6010 before it's actually usable.
3390 o Major bugfixes (directory authorities):
3391 - When computing weight parameters, behave more robustly in the
3392 presence of a bad bwweightscale value. Previously, the authorities
3393 would crash if they agreed on a sufficiently broken weight_scale
3394 value: now, they use a reasonable default and carry on. Partial
3395 fix for 5786; bugfix on 0.2.2.17-alpha.
3396 - Check more thoroughly to prevent a rogue authority from
3397 double-voting on any consensus directory parameter. Previously,
3398 authorities would crash in this case if the total number of
3399 votes for any parameter exceeded the number of active voters,
3400 but would let it pass otherwise. Partial fix for bug 5786; bugfix
3404 - Rate-limit log messages when asked to connect anonymously to
3405 a private address. When these hit, they tended to hit fast and
3406 often. Also, don't bother trying to connect to addresses that we
3407 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3408 reply makes us think we have been lied to, even when the address the
3409 client tried to connect to was "localhost." Resolves ticket 2822.
3410 - Allow packagers to insert an extra string in server descriptor
3411 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
3412 Resolves the rest of ticket 2988.
3413 - Raise the threshold of server descriptors needed (75%) and exit
3414 server descriptors needed (50%) before we will declare ourselves
3415 bootstrapped. This will make clients start building circuits a
3416 little later, but makes the initially constructed circuits less
3417 skewed and less in conflict with further directory fetches. Fixes
3419 - Close any connection that sends unrecognized junk before the
3420 handshake. Solves an issue noted in bug 4369.
3421 - Improve log messages about managed transports. Resolves ticket 5070.
3422 - Tag a bridge's descriptor as "never to be sent unencrypted".
3423 This shouldn't matter, since bridges don't open non-anonymous
3424 connections to the bridge authority and don't allow unencrypted
3425 directory connections from clients, but we might as well make
3426 sure. Closes bug 5139.
3427 - Expose our view of whether we have gone dormant to the controller,
3428 via a new "GETINFO dormant" value. Torbutton and other controllers
3429 can use this to avoid doing periodic requests through Tor while
3430 it's dormant (bug 4718). Fixes bug 5954.
3431 - Tell GCC and Clang to check for any errors in format strings passed
3432 to the tor_v*(print|scan)f functions.
3433 - Update to the May 1 2012 Maxmind GeoLite Country database.
3435 o Minor bugfixes (already included in 0.2.2.36):
3436 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3437 Fixes bug 5346; bugfix on 0.0.8pre3.
3438 - Correct parsing of certain date types in parse_http_time().
3439 Without this patch, If-Modified-Since would behave
3440 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3441 Esteban Manchado Velázques.
3442 - Make our number-parsing functions always treat too-large values
3443 as an error, even when those values exceed the width of the
3444 underlying type. Previously, if the caller provided these
3445 functions with minima or maxima set to the extreme values of the
3446 underlying integer type, these functions would return those
3447 values on overflow rather than treating overflow as an error.
3448 Fixes part of bug 5786; bugfix on 0.0.9.
3449 - If we hit the error case where routerlist_insert() replaces an
3450 existing (old) server descriptor, make sure to remove that
3451 server descriptor from the old_routers list. Fix related to bug
3452 1776. Bugfix on 0.2.2.18-alpha.
3453 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3454 circuits. Fixes issue 5259.
3456 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
3457 - Prevent a null-pointer dereference when receiving a data cell
3458 for a nonexistent stream when the circuit in question has an
3459 empty deliver window. We don't believe this is triggerable,
3460 since we don't currently allow deliver windows to become empty,
3461 but the logic is tricky enough that it's better to make the code
3462 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
3463 - Fix a memory leak when trying to launch a DNS request when the
3464 network is disabled or the nameservers are unconfigurable. Fixes
3465 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
3466 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
3467 - Don't hold a Windows file handle open for every file mapping;
3468 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
3470 - Avoid O(n^2) performance characteristics when parsing a large
3471 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
3472 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3473 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3475 - Make our replacement implementation of strtok_r() compatible with
3476 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
3477 bugfix on 0.2.2.1-alpha.
3478 - Fix a NULL-pointer dereference on a badly formed
3479 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
3480 bugfix on 0.2.2.9-alpha.
3481 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3482 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3483 - Defensively refactor rend_mid_rendezvous() so that protocol
3484 violations and length checks happen in the beginning. Fixes
3486 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3487 that IPv6 stuff will compile on MSVC, and compilation issues
3488 will be easier to track down. Fixes bug 5861.
3490 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
3491 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
3492 resource exhaustion, so that clients can adjust their load to
3493 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
3494 started using END_STREAM_REASON_RESOURCELIMIT.
3495 - Don't check for whether the address we're using for outbound
3496 connections has changed until after the outbound connection has
3497 completed. On Windows, getsockname() doesn't succeed until the
3498 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
3499 - If the configuration tries to set MyFamily on a bridge, refuse to
3500 do so, and warn about the security implications. Fixes bug 4657;
3501 bugfix on 0.2.0.3-alpha.
3502 - If the client fails to set a reasonable set of ciphersuites
3503 during its v2 handshake renegotiation, allow the renegotiation to
3504 continue nevertheless (i.e. send all the required certificates).
3505 Fixes bug 4591; bugfix on 0.2.0.20-rc.
3506 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
3507 option is set to 0 (which Vidalia version 0.2.16 now does when
3508 a SAVECONF attempt fails), perform other actions that SIGHUP
3509 usually causes (like reopening the logs). Fixes bug 5095; bugfix
3511 - If we fail to write a microdescriptor to the disk cache, do not
3512 continue replacing the old microdescriptor file. Fixes bug 2954;
3513 bugfix on 0.2.2.6-alpha.
3514 - Exit nodes don't need to fetch certificates for authorities that
3515 they don't recognize; only directory authorities, bridges,
3516 and caches need to do that. Fixes part of bug 2297; bugfix on
3518 - Correctly handle checking the permissions on the parent
3519 directory of a control socket in the root directory. Bug found
3520 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
3522 - When told to add a bridge with the same digest as a preexisting
3523 bridge but a different addr:port, change the addr:port as
3524 requested. Previously we would not notice the change. Fixes half
3525 of bug 5603; fix on 0.2.2.26-beta.
3526 - End AUTHCHALLENGE error messages (in the control protocol) with
3527 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
3529 o Minor bugfixes (on 0.2.3.x):
3530 - Turn an assertion (that the number of handshakes received as a
3531 server is not < 1) into a warning. Fixes bug 4873; bugfix on
3533 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
3534 we had reversed them when the answer was cached.) Fixes bug
3535 5723; bugfix on 0.2.3.1-alpha.
3536 - Work correctly on Linux systems with accept4 support advertised in
3537 their headers, but without accept4 support in the kernel. Fix
3538 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
3539 - When told to add a bridge with the same addr:port as a preexisting
3540 bridge but a different transport, change the transport as
3541 requested. Previously we would not notice the change. Fixes half
3542 of bug 5603; fix on 0.2.3.2-alpha.
3543 - Avoid a "double-reply" warning when replying to a SOCKS request
3544 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
3545 bugfix on 0.2.3.4-alpha.
3546 - Fix a bug where a bridge authority crashes if it has seen no
3547 directory requests when it's time to write statistics to disk.
3548 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
3550 - Don't try to open non-control listeners when DisableNetwork is set.
3551 Previously, we'd open all listeners, then immediately close them.
3552 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
3553 - Don't abort the managed proxy protocol if the managed proxy
3554 sends us an unrecognized line; ignore it instead. Fixes bug
3555 5910; bugfix on 0.2.3.9-alpha.
3556 - Fix a compile warning in crypto.c when compiling with clang 3.1.
3557 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
3558 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
3559 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
3560 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
3561 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
3562 - Resolve numerous small warnings and build issues with MSVC. Resolves
3565 o Documentation fixes:
3566 - Improve the manual's documentation for the NT Service command-line
3567 options. Addresses ticket 3964.
3568 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3569 - Document the changes to the ORPort and DirPort options, and the
3570 fact that {OR/Dir}ListenAddress is now unnecessary (and
3571 therefore deprecated). Resolves ticket 5597.
3574 - Remove the torrc.bridge file: we don't use it for anything, and
3575 it had become badly desynchronized from torrc.sample. Resolves
3579 Changes in version 0.2.2.36 - 2012-05-24
3580 Tor 0.2.2.36 updates the addresses for two of the eight directory
3581 authorities, fixes some potential anonymity and security issues,
3582 and fixes several crash bugs.
3584 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
3585 known flaws, and nobody should be using them. You should upgrade. If
3586 you're using a Linux or BSD and its packages are obsolete, stop using
3587 those packages and upgrade anyway.
3589 o Directory authority changes:
3590 - Change IP address for maatuska (v3 directory authority).
3591 - Change IP address for ides (v3 directory authority), and rename
3595 - When building or running with any version of OpenSSL earlier
3596 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
3597 versions have a bug (CVE-2011-4576) in which their block cipher
3598 padding includes uninitialized data, potentially leaking sensitive
3599 information to any peer with whom they make a SSLv3 connection. Tor
3600 does not use SSL v3 by default, but a hostile client or server
3601 could force an SSLv3 connection in order to gain information that
3602 they shouldn't have been able to get. The best solution here is to
3603 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
3604 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
3605 to make sure that the bug can't happen.
3606 - Never use a bridge or a controller-supplied node as an exit, even
3607 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3608 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3609 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3610 - Only build circuits if we have a sufficient threshold of the total
3611 descriptors that are marked in the consensus with the "Exit"
3612 flag. This mitigates an attack proposed by wanoskarnet, in which
3613 all of a client's bridges collude to restrict the exit nodes that
3614 the client knows about. Fixes bug 5343.
3615 - Provide controllers with a safer way to implement the cookie
3616 authentication mechanism. With the old method, if another locally
3617 running program could convince a controller that it was the Tor
3618 process, then that program could trick the controller into telling
3619 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3620 authentication method uses a challenge-response approach to prevent
3621 this attack. Fixes bug 5185; implements proposal 193.
3624 - Avoid logging uninitialized data when unable to decode a hidden
3625 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3626 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3627 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3629 - Fix builds when the path to sed, openssl, or sha1sum contains
3630 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3632 - Correct our replacements for the timeradd() and timersub() functions
3633 on platforms that lack them (for example, Windows). The timersub()
3634 function is used when expiring circuits, while timeradd() is
3635 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
3636 bugfix on 0.2.2.24-alpha.
3637 - Fix the SOCKET_OK test that we use to tell when socket
3638 creation fails so that it works on Win64. Fixes part of bug 4533;
3639 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
3642 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3643 Fixes bug 5346; bugfix on 0.0.8pre3.
3644 - Make our number-parsing functions always treat too-large values
3645 as an error, even when those values exceed the width of the
3646 underlying type. Previously, if the caller provided these
3647 functions with minima or maxima set to the extreme values of the
3648 underlying integer type, these functions would return those
3649 values on overflow rather than treating overflow as an error.
3650 Fixes part of bug 5786; bugfix on 0.0.9.
3651 - Older Linux kernels erroneously respond to strange nmap behavior
3652 by having accept() return successfully with a zero-length
3653 socket. When this happens, just close the connection. Previously,
3654 we would try harder to learn the remote address: but there was
3655 no such remote address to learn, and our method for trying to
3656 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3657 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3658 - Correct parsing of certain date types in parse_http_time().
3659 Without this patch, If-Modified-Since would behave
3660 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3661 Esteban Manchado Velázques.
3662 - Change the BridgePassword feature (part of the "bridge community"
3663 design, which is not yet implemented) to use a time-independent
3664 comparison. The old behavior might have allowed an adversary
3665 to use timing to guess the BridgePassword value. Fixes bug 5543;
3666 bugfix on 0.2.0.14-alpha.
3667 - Detect and reject certain misformed escape sequences in
3668 configuration values. Previously, these values would cause us
3669 to crash if received in a torrc file or over an authenticated
3670 control port. Bug found by Esteban Manchado Velázquez, and
3671 independently by Robert Connolly from Matta Consulting who further
3672 noted that it allows a post-authentication heap overflow. Patch
3673 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3674 bugfix on 0.2.0.16-alpha.
3675 - Fix a compile warning when using the --enable-openbsd-malloc
3676 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3677 - During configure, detect when we're building with clang version
3678 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3679 CFLAGS. clang doesn't support them yet.
3680 - When sending an HTTP/1.1 proxy request, include a Host header.
3681 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3682 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
3683 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
3684 - If we hit the error case where routerlist_insert() replaces an
3685 existing (old) server descriptor, make sure to remove that
3686 server descriptor from the old_routers list. Fix related to bug
3687 1776. Bugfix on 0.2.2.18-alpha.
3689 o Minor bugfixes (documentation and log messages):
3690 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3691 Fixes bug 4856; bugfix on Tor 0.0.6.
3692 - Update "ClientOnly" man page entry to explain that there isn't
3693 really any point to messing with it. Resolves ticket 5005.
3694 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3695 directory authority option (introduced in Tor 0.2.2.34).
3696 - Downgrade the "We're missing a certificate" message from notice
3697 to info: people kept mistaking it for a real problem, whereas it
3698 is seldom the problem even when we are failing to bootstrap. Fixes
3699 bug 5067; bugfix on 0.2.0.10-alpha.
3700 - Correctly spell "connect" in a log message on failure to create a
3701 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
3702 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3703 circuits. Fixes issue 5259.
3706 - Directory authorities now reject versions of Tor older than
3707 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3708 inclusive. These versions accounted for only a small fraction of
3709 the Tor network, and have numerous known security issues. Resolves
3711 - Update to the May 1 2012 Maxmind GeoLite Country database.
3714 - When sending or relaying a RELAY_EARLY cell, we used to convert
3715 it to a RELAY cell if the connection was using the v1 link
3716 protocol. This was a workaround for older versions of Tor, which
3717 didn't handle RELAY_EARLY cells properly. Now that all supported
3718 versions can handle RELAY_EARLY cells, and now that we're enforcing
3719 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3720 remove this workaround. Addresses bug 4786.
3723 Changes in version 0.2.3.15-alpha - 2012-04-30
3724 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
3725 the development branch build on Windows again.
3727 o Minor bugfixes (on 0.2.2.x and earlier):
3728 - Make sure that there are no unhandled pending TLS errors before
3729 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
3730 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
3731 Bugfix on 0.1.0.5-rc; fixes bug 4528.
3732 - Fix an assert that directory authorities could trigger on sighup
3733 during some configuration state transitions. We now don't treat
3734 it as a fatal error when the new descriptor we just generated in
3735 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
3736 - After we pick a directory mirror, we would refuse to use it if
3737 it's in our ExcludeExitNodes list, resulting in mysterious failures
3738 to bootstrap for people who just wanted to avoid exiting from
3739 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
3740 - When building with --enable-static-tor on OpenBSD, do not
3741 erroneously attempt to link -lrt. Fixes bug 5103.
3743 o Minor bugfixes (on 0.2.3.x):
3744 - When Tor is built with kernel headers from a recent (last few
3745 years) Linux kernel, do not fail to run on older (pre-2.6.28
3746 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
3747 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
3749 - Fix compilation with miniupnpc version 1.6; patch from
3750 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
3751 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
3752 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
3753 - Fix compilation on platforms without unistd.h, or where environ
3754 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
3757 - Directory authorities are now a little more lenient at accepting
3758 older router descriptors, or newer router descriptors that don't
3759 make big changes. This should help ameliorate past and future
3760 issues where routers think they have uploaded valid descriptors,
3761 but the authorities don't think so. Fix for ticket 2479.
3762 - Make the code that clients use to detect an address change be
3763 IPv6-aware, so that it won't fill clients' logs with error
3764 messages when trying to get the IPv4 address of an IPv6
3765 connection. Implements ticket 5537.
3768 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
3769 authorities needed to use it for a while to keep the network working
3770 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
3771 that was six months ago. As of now, it should no longer be needed
3775 Changes in version 0.2.3.14-alpha - 2012-04-23
3776 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
3777 candidate. It also dramatically speeds up AES: fast relays should
3778 consider switching to the newer OpenSSL library.
3780 o Directory authority changes:
3781 - Change IP address for ides (v3 directory authority), and rename
3785 - Avoid logging uninitialized data when unable to decode a hidden
3786 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
3787 - Avoid a client-side assertion failure when receiving an INTRODUCE2
3788 cell on a general purpose circuit. Fixes bug 5644; bugfix on
3790 - If authorities are unable to get a v2 consensus document from other
3791 directory authorities, they no longer fall back to fetching
3792 them from regular directory caches. Fixes bug 5635; bugfix on
3793 0.2.2.26-beta, where routers stopped downloading v2 consensus
3795 - When we start a Tor client with a normal consensus already cached,
3796 be willing to download a microdescriptor consensus. Fixes bug 4011;
3797 fix on 0.2.3.1-alpha.
3799 o Major features (performance):
3800 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
3801 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
3802 vectorized AES implementations as appropriate. These can be much,
3803 much faster than other AES implementations.
3805 o Minor bugfixes (0.2.2.x and earlier):
3806 - Don't launch more than 10 service-side introduction-point circuits
3807 for a hidden service in five minutes. Previously, we would consider
3808 launching more introduction-point circuits if at least one second
3809 had passed without any introduction-point circuits failing. Fixes
3810 bug 4607; bugfix on 0.0.7pre1.
3811 - Change the BridgePassword feature (part of the "bridge community"
3812 design, which is not yet implemented) to use a time-independent
3813 comparison. The old behavior might have allowed an adversary
3814 to use timing to guess the BridgePassword value. Fixes bug 5543;
3815 bugfix on 0.2.0.14-alpha.
3816 - Enforce correct return behavior of tor_vsscanf() when the '%%'
3817 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
3818 - When sending an HTTP/1.1 proxy request, include a Host header.
3819 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
3820 - Don't log that we have "decided to publish new relay descriptor"
3821 unless we are actually publishing a descriptor. Fixes bug 3942;
3822 bugfix on 0.2.2.28-beta.
3824 o Minor bugfixes (0.2.3.x):
3825 - Fix a bug where a bridge authority crashes (on a failed assert)
3826 if it has seen no directory requests when it's time to write
3827 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
3828 - Fix bug stomping on ORPort option NoListen and ignoring option
3829 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
3830 - In the testsuite, provide a large enough buffer in the tor_sscanf
3831 unit test. Otherwise we'd overrun that buffer and crash during
3832 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
3834 - Make sure we create the keys directory if it doesn't exist and we're
3835 about to store the dynamic Diffie-Hellman parameters. Fixes bug
3836 5572; bugfix on 0.2.3.13-alpha.
3837 - Fix a small memory leak when trying to decode incorrect base16
3838 authenticator during SAFECOOKIE authentication. Found by
3839 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
3842 - Add more information to a log statement that might help track down
3843 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
3844 non-IP address" messages (or any Bug messages, for that matter!),
3845 please let us know about it.
3846 - Relays now understand an IPv6 address when they get one from a
3847 directory server. Resolves ticket 4875.
3848 - Resolve IPv6 addresses in bridge and entry statistics to country
3849 code "??" which means we at least count them. Resolves ticket 5053;
3850 improves on 0.2.3.9-alpha.
3851 - Update to the April 3 2012 Maxmind GeoLite Country database.
3852 - Begin a doc/state-contents.txt file to explain the contents of
3853 the Tor state file. Fixes bug 2987.
3855 o Default torrc changes:
3856 - Stop listing "socksport 9050" in torrc.sample. We open a socks
3857 port on 9050 by default anyway, so this should not change anything
3859 - Stop mentioning the deprecated *ListenAddress options in
3860 torrc.sample. Fixes bug 5438.
3861 - Document unit of bandwidth related options in sample torrc.
3865 - The "torify" script no longer supports the "tsocks" socksifier
3866 tool, since tsocks doesn't support DNS and UDP right for Tor.
3867 Everyone should be using torsocks instead. Fixes bugs 3530 and
3868 5180. Based on a patch by "ugh".
3871 - Change the symmetric cipher interface so that creating and
3872 initializing a stream cipher are no longer separate functions.
3873 - Remove all internal support for unpadded RSA. We never used it, and
3874 it would be a bad idea to start.
3877 Changes in version 0.2.3.13-alpha - 2012-03-26
3878 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
3879 in managed pluggable transports, as well as providing other cleanups
3880 that get us closer to a release candidate.
3882 o Directory authority changes:
3883 - Change IP address for maatuska (v3 directory authority).
3886 - Provide controllers with a safer way to implement the cookie
3887 authentication mechanism. With the old method, if another locally
3888 running program could convince a controller that it was the Tor
3889 process, then that program could trick the controller into telling
3890 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
3891 authentication method uses a challenge-response approach to prevent
3892 this attack. Fixes bug 5185, implements proposal 193.
3893 - Never use a bridge or a controller-supplied node as an exit, even
3894 if its exit policy allows it. Found by wanoskarnet. Fixes bug
3895 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
3896 and 0.2.0.3-alpha (for bridge-purpose descriptors).
3897 - Only build circuits if we have a sufficient threshold of the total
3898 descriptors that are marked in the consensus with the "Exit"
3899 flag. This mitigates an attack proposed by wanoskarnet, in which
3900 all of a client's bridges collude to restrict the exit nodes that
3901 the client knows about. Fixes bug 5343.
3903 o Major bugfixes (on Tor 0.2.3.x):
3904 - Avoid an assert when managed proxies like obfsproxy are configured,
3905 and we receive HUP signals or setconf attempts too rapidly. This
3906 situation happens most commonly when Vidalia tries to attach to
3907 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
3908 bugfix on 0.2.3.6-alpha.
3909 - Fix a relay-side pluggable transports bug where managed proxies were
3910 unreachable from the Internet, because Tor asked them to bind on
3911 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
3912 - Stop discarding command-line arguments when TestingTorNetwork
3913 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
3914 0.2.3.9-alpha, where task 4552 added support for two layers of
3916 - Resume allowing the unit tests to run in gdb. This was accidentally
3917 made impossible when the DisableDebuggerAttachment option was
3918 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
3919 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
3920 0.2.3.11-alpha. Reported by Anthony G. Basile.
3922 o Minor bugfixes (on 0.2.2.x and earlier):
3923 - Ensure we don't cannibalize circuits that are longer than three hops
3924 already, so we don't end up making circuits with 5 or more
3925 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
3926 0.1.0.1-rc which introduced cannibalization.
3927 - Detect and reject certain misformed escape sequences in
3928 configuration values. Previously, these values would cause us
3929 to crash if received in a torrc file or over an authenticated
3930 control port. Bug found by Esteban Manchado Velázquez, and
3931 independently by Robert Connolly from Matta Consulting who further
3932 noted that it allows a post-authentication heap overflow. Patch
3933 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
3934 bugfix on 0.2.0.16-alpha.
3935 - Fix a compile warning when using the --enable-openbsd-malloc
3936 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
3937 - Directory caches no longer refuse to clean out descriptors because
3938 of missing v2 networkstatus documents, unless they're configured
3939 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
3940 0.2.2.26-beta. Patch by Daniel Bryg.
3941 - Update to the latest version of the tinytest unit testing framework.
3942 This includes a couple of bugfixes that can be relevant for
3943 running forked unit tests on Windows, and removes all reserved
3946 o Minor bugfixes (on 0.2.3.x):
3947 - On a failed pipe() call, don't leak file descriptors. Fixes bug
3948 4296; bugfix on 0.2.3.1-alpha.
3949 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
3950 until after we have received a CERTS cell. Fixes bug 4361; bugfix
3951 on 0.2.3.6-alpha. Patch by "frosty".
3952 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
3953 option, so that the IP stack doesn't decide to use it for IPv4
3954 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
3955 - Ensure that variables set in Tor's environment cannot override
3956 environment variables that Tor passes to a managed
3957 pluggable-transport proxy. Previously, Tor would pass every
3958 variable in its environment to managed proxies along with the new
3959 ones, in such a way that on many operating systems, the inherited
3960 environment variables would override those which Tor tried to
3961 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
3962 bugfix on 0.2.3.9-alpha for Windows.
3965 - A wide variety of new unit tests by Esteban Manchado Velázquez.
3966 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
3967 - Update to the March 6 2012 Maxmind GeoLite Country database.
3970 Changes in version 0.2.3.12-alpha - 2012-02-13
3971 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
3972 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
3973 when Tor is configured to use a pluggable transport like obfsproxy.
3976 - Fix builds when the path to sed, openssl, or sha1sum contains
3977 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
3979 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
3980 connections. This change should allow busy exit relays to stop
3981 running out of available sockets as quickly. Fixes bug 4950;
3982 bugfix on 0.2.2.26-beta.
3983 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
3984 would ask the bridge for microdescriptors, which are only supported
3985 in 0.2.3.x, and then fail to bootstrap when it didn't get the
3986 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
3987 - Properly set up obfsproxy's environment when in managed mode. The
3988 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
3989 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
3990 5076 and 5082; bugfix on 0.2.3.6-alpha.
3993 - Use the dead_strip option when building Tor on OS X. This reduces
3994 binary size by almost 19% when linking openssl and libevent
3995 statically, which we do for Tor Browser Bundle.
3996 - Fix broken URLs in the sample torrc file, and tell readers about
3997 the OutboundBindAddress, ExitPolicyRejectPrivate, and
3998 PublishServerDescriptor options. Addresses bug 4652.
3999 - Update to the February 7 2012 Maxmind GeoLite Country database.
4002 - Downgrade the "We're missing a certificate" message from notice
4003 to info: people kept mistaking it for a real problem, whereas it
4004 is seldom the problem even when we are failing to bootstrap. Fixes
4005 bug 5067; bugfix on 0.2.0.10-alpha.
4006 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
4007 managed pluggable transport server proxy's environment.
4008 Previously, we would put it there, even though Tor doesn't
4009 implement an 'extended server port' yet, and even though Tor
4010 almost certainly isn't listening at that address. For now, we set
4011 it to an empty string to avoid crashing older obfsproxies. Bugfix
4013 - Log the heartbeat message every HeartbeatPeriod seconds, not every
4014 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
4015 0.2.3.1-alpha. Bug reported by Scott Bennett.
4016 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
4017 bugfix on 0.2.3.11-alpha.
4018 - Update "ClientOnly" man page entry to explain that there isn't
4019 really any point to messing with it. Resolves ticket 5005.
4020 - Use the correct CVE number for CVE-2011-4576 in our comments and
4021 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
4024 o Code simplifications and refactoring:
4025 - Use the _WIN32 macro throughout our code to detect Windows.
4026 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
4030 Changes in version 0.2.3.11-alpha - 2012-01-22
4031 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
4032 the last step of the plan to limit maximum circuit length, includes
4033 a wide variety of hidden service performance and correctness fixes,
4034 works around an OpenSSL security flaw if your distro is too stubborn
4035 to upgrade, and fixes a bunch of smaller issues.
4038 - Now that Tor 0.2.0.x is completely deprecated, enable the final
4039 part of "Proposal 110: Avoiding infinite length circuits" by
4040 refusing all circuit-extend requests that do not use a relay_early
4041 cell. This change helps Tor resist a class of denial-of-service
4042 attacks by limiting the maximum circuit length.
4043 - Adjust the number of introduction points that a hidden service
4044 will try to maintain based on how long its introduction points
4045 remain in use and how many introductions they handle. Fixes
4047 - Try to use system facilities for enumerating local interface
4048 addresses, before falling back to our old approach (which was
4049 binding a UDP socket, and calling getsockname() on it). That
4050 approach was scaring OS X users whose draconian firewall
4051 software warned about binding to UDP sockets, regardless of
4052 whether packets were sent. Now we try to use getifaddrs(),
4053 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
4054 system supports. Resolves ticket 1827.
4056 o Major security workaround:
4057 - When building or running with any version of OpenSSL earlier
4058 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4059 versions have a bug (CVE-2011-4576) in which their block cipher
4060 padding includes uninitialized data, potentially leaking sensitive
4061 information to any peer with whom they make a SSLv3 connection. Tor
4062 does not use SSL v3 by default, but a hostile client or server
4063 could force an SSLv3 connection in order to gain information that
4064 they shouldn't have been able to get. The best solution here is to
4065 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4066 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4067 to make sure that the bug can't happen.
4070 - Fix the SOCKET_OK test that we use to tell when socket
4071 creation fails so that it works on Win64. Fixes part of bug 4533;
4072 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4073 - Correct our replacements for the timeradd() and timersub() functions
4074 on platforms that lack them (for example, Windows). The timersub()
4075 function is used when expiring circuits, while timeradd() is
4076 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4077 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
4078 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
4079 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
4080 bug at runtime, not compile time, because some distributions hack
4081 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
4082 on 0.2.3.9-alpha. Found by Pascal.
4084 o Minor features (controller):
4085 - Use absolute path names when reporting the torrc filename in the
4086 control protocol, so a controller can more easily find the torrc
4087 file. Resolves bug 1101.
4088 - Extend the control protocol to report flags that control a circuit's
4089 path selection in CIRC events and in replies to 'GETINFO
4090 circuit-status'. Implements part of ticket 2411.
4091 - Extend the control protocol to report the hidden service address
4092 and current state of a hidden-service-related circuit in CIRC
4093 events and in replies to 'GETINFO circuit-status'. Implements part
4095 - When reporting the path to the cookie file to the controller,
4096 give an absolute path. Resolves ticket 4881.
4097 - Allow controllers to request an event notification whenever a
4098 circuit is cannibalized or its purpose is changed. Implements
4099 part of ticket 3457.
4100 - Include the creation time of a circuit in CIRC and CIRC2
4101 control-port events and the list produced by the 'GETINFO
4102 circuit-status' control-port command.
4104 o Minor features (directory authorities):
4105 - Directory authorities now reject versions of Tor older than
4106 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4107 inclusive. These versions accounted for only a small fraction of
4108 the Tor network, and have numerous known security issues. Resolves
4110 - Authority operators can now vote for all relays in a given
4111 set of countries to be BadDir/BadExit/Invalid/Rejected.
4112 - Provide two consensus parameters (FastFlagMinThreshold and
4113 FastFlagMaxThreshold) to control the range of allowable bandwidths
4114 for the Fast directory flag. These allow authorities to run
4115 experiments on appropriate requirements for being a "Fast" node.
4116 The AuthDirFastGuarantee config value still applies. Implements
4118 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4119 directory authority option (introduced in Tor 0.2.2.34).
4121 o Minor features (other):
4122 - Don't disable the DirPort when we cannot exceed our AccountingMax
4123 limit during this interval because the effective bandwidthrate is
4124 low enough. This is useful in a situation where AccountMax is only
4125 used as an additional safeguard or to provide statistics.
4126 - Prepend an informative header to generated dynamic_dh_params files.
4127 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
4128 EntryNodes will have no effect. Resolves issue 2571.
4129 - Log more useful messages when we fail to disable debugger
4131 - Log which authority we're missing votes from when we go to fetch
4132 them from the other auths.
4133 - Log (at debug level) whenever a circuit's purpose is changed.
4134 - Add missing documentation for the MaxClientCircuitsPending,
4135 UseMicrodescriptors, UserspaceIOCPBuffers, and
4136 _UseFilteringSSLBufferevents options, all introduced during
4138 - Update to the January 3 2012 Maxmind GeoLite Country database.
4140 o Minor bugfixes (hidden services):
4141 - Don't close hidden service client circuits which have almost
4142 finished connecting to their destination when they reach
4143 the normal circuit-build timeout. Previously, we would close
4144 introduction circuits which are waiting for an acknowledgement
4145 from the introduction point, and rendezvous circuits which have
4146 been specified in an INTRODUCE1 cell sent to a hidden service,
4147 after the normal CBT. Now, we mark them as 'timed out', and launch
4148 another rendezvous attempt in parallel. This behavior change can
4149 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4150 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4151 - Don't close hidden-service-side rendezvous circuits when they
4152 reach the normal circuit-build timeout. This behaviour change can
4153 be disabled using the new
4154 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4155 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4156 - Make sure we never mark the wrong rendezvous circuit as having
4157 had its introduction cell acknowleged by the introduction-point
4158 relay. Previously, when we received an INTRODUCE_ACK cell on a
4159 client-side hidden-service introduction circuit, we might have
4160 marked a rendezvous circuit other than the one we specified in
4161 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
4162 a warning message and interfered with the hidden service
4163 connection-establishment process. Fixes bug 4759; bugfix on
4164 0.2.3.3-alpha, when we added the stream-isolation feature which
4165 might cause Tor to open multiple rendezvous circuits for the same
4167 - Don't trigger an assertion failure when we mark a new client-side
4168 hidden-service introduction circuit for close during the process
4169 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
4172 o Minor bugfixes (log messages):
4173 - Correctly spell "connect" in a log message on failure to create a
4174 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
4176 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4177 Fixes bug 4856; bugfix on Tor 0.0.6.
4178 - Fix the log message describing how we work around discovering
4179 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
4180 4837; bugfix on 0.2.2.9-alpha.
4181 - When logging about a disallowed .exit name, do not also call it
4182 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
4184 o Minor bugfixes (build fixes):
4185 - During configure, detect when we're building with clang version
4186 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4187 CFLAGS. clang doesn't support them yet.
4188 - During configure, search for library containing cos function as
4189 libm lives in libcore on some platforms (BeOS/Haiku). Linking
4190 against libm was hard-coded before. Fixes the first part of bug
4191 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
4193 - Detect attempts to build Tor on (as yet hypothetical) versions
4194 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
4195 fix for bug 4533. Bugfix on 0.2.2.28-beta.
4196 - Preprocessor directives should not be put inside the arguments
4197 of a macro. This would break compilation with GCC releases prior
4198 to version 3.3. We would never recommend such an old GCC version,
4199 but it is apparently required for binary compatibility on some
4200 platforms (namely, certain builds of Haiku). Fixes the other part
4201 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
4204 o Minor bugfixes (other):
4205 - Older Linux kernels erroneously respond to strange nmap behavior
4206 by having accept() return successfully with a zero-length
4207 socket. When this happens, just close the connection. Previously,
4208 we would try harder to learn the remote address: but there was
4209 no such remote address to learn, and our method for trying to
4210 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4211 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4212 - Fix null-pointer access that could occur if TLS allocation failed.
4213 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
4214 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
4215 accidentally been reverted.
4216 - Fix our implementation of crypto_random_hostname() so it can't
4217 overflow on ridiculously large inputs. (No Tor version has ever
4218 provided this kind of bad inputs, but let's be correct in depth.)
4219 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
4220 - Find more places in the code that should have been testing for
4221 invalid sockets using the SOCKET_OK macro. Required for a fix
4222 for bug 4533. Bugfix on 0.2.2.28-beta.
4223 - Fix an assertion failure when, while running with bufferevents, a
4224 connection finishes connecting after it is marked for close, but
4225 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
4226 - test_util_spawn_background_ok() hardcoded the expected value
4227 for ENOENT to 2. This isn't portable as error numbers are
4228 platform specific, and particularly the hurd has ENOENT at
4229 0x40000002. Construct expected string at runtime, using the correct
4230 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
4231 - Reject attempts to disable DisableDebuggerAttachment while Tor is
4232 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
4233 - Use an appropriate-width type for sockets in tor-fw-helper on
4234 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
4237 - When sending or relaying a RELAY_EARLY cell, we used to convert
4238 it to a RELAY cell if the connection was using the v1 link
4239 protocol. This was a workaround for older versions of Tor, which
4240 didn't handle RELAY_EARLY cells properly. Now that all supported
4241 versions can handle RELAY_EARLY cells, and now that we're enforcing
4242 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4243 remove this workaround. Addresses bug 4786.
4245 o Code simplifications and refactoring:
4246 - Use OpenSSL's built-in SSL_state_string_long() instead of our
4247 own homebrewed ssl_state_to_string() replacement. Patch from
4248 Emile Snyder. Fixes bug 4653.
4249 - Use macros to indicate OpenSSL versions, so we don't need to worry
4250 about accidental hexadecimal bit shifts.
4251 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
4253 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
4254 - Use the smartlist_add_asprintf() alias more consistently.
4255 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
4256 invalid value, rather than just -1.
4257 - Rename a handful of old identifiers, mostly related to crypto
4258 structures and crypto functions. By convention, our "create an
4259 object" functions are called "type_new()", our "free an object"
4260 functions are called "type_free()", and our types indicate that
4261 they are types only with a final "_t". But a handful of older
4262 types and functions broke these rules, with function names like
4263 "type_create" or "subsystem_op_type", or with type names like
4267 Changes in version 0.2.3.10-alpha - 2011-12-16
4268 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
4269 Tor's buffers code. Absolutely everybody should upgrade.
4271 The bug relied on an incorrect calculation when making data continuous
4272 in one of our IO buffers, if the first chunk of the buffer was
4273 misaligned by just the wrong amount. The miscalculation would allow an
4274 attacker to overflow a piece of heap-allocated memory. To mount this
4275 attack, the attacker would need to either open a SOCKS connection to
4276 Tor's SocksPort (usually restricted to localhost), or target a Tor
4277 instance configured to make its connections through a SOCKS proxy
4278 (which Tor does not do by default).
4280 Good security practice requires that all heap-overflow bugs should be
4281 presumed to be exploitable until proven otherwise, so we are treating
4282 this as a potential code execution attack. Please upgrade immediately!
4283 This bug does not affect bufferevents-based builds of Tor. Special
4284 thanks to "Vektor" for reporting this issue to us!
4286 This release also contains a few minor bugfixes for issues discovered
4290 - Fix a heap overflow bug that could occur when trying to pull
4291 data into the first chunk of a buffer, when that chunk had
4292 already had some data drained from it. Fixes CVE-2011-2778;
4293 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4296 - If we can't attach streams to a rendezvous circuit when we
4297 finish connecting to a hidden service, clear the rendezvous
4298 circuit's stream-isolation state and try to attach streams
4299 again. Previously, we cleared rendezvous circuits' isolation
4300 state either too early (if they were freshly built) or not at all
4301 (if they had been built earlier and were cannibalized). Bugfix on
4302 0.2.3.3-alpha; fixes bug 4655.
4303 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
4304 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
4305 - Fix an assertion failure when a relay with accounting enabled
4306 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
4309 - Update to the December 6 2011 Maxmind GeoLite Country database.
4312 Changes in version 0.2.2.35 - 2011-12-16
4313 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
4314 buffers code. Absolutely everybody should upgrade.
4316 The bug relied on an incorrect calculation when making data continuous
4317 in one of our IO buffers, if the first chunk of the buffer was
4318 misaligned by just the wrong amount. The miscalculation would allow an
4319 attacker to overflow a piece of heap-allocated memory. To mount this
4320 attack, the attacker would need to either open a SOCKS connection to
4321 Tor's SocksPort (usually restricted to localhost), or target a Tor
4322 instance configured to make its connections through a SOCKS proxy
4323 (which Tor does not do by default).
4325 Good security practice requires that all heap-overflow bugs should be
4326 presumed to be exploitable until proven otherwise, so we are treating
4327 this as a potential code execution attack. Please upgrade immediately!
4328 This bug does not affect bufferevents-based builds of Tor. Special
4329 thanks to "Vektor" for reporting this issue to us!
4331 Tor 0.2.2.35 also fixes several bugs in previous versions, including
4332 crash bugs for unusual configurations, and a long-term bug that
4333 would prevent Tor from starting on Windows machines with draconian
4336 With this release, we remind everyone that 0.2.0.x has reached its
4337 formal end-of-life. Those Tor versions have many known flaws, and
4338 nobody should be using them. You should upgrade -- ideally to the
4339 0.2.2.x series. If you're using a Linux or BSD and its packages are
4340 obsolete, stop using those packages and upgrade anyway.
4342 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
4343 longer receive support after some time in early 2012.
4346 - Fix a heap overflow bug that could occur when trying to pull
4347 data into the first chunk of a buffer, when that chunk had
4348 already had some data drained from it. Fixes CVE-2011-2778;
4349 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4350 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4351 that it doesn't attempt to allocate a socketpair. This could cause
4352 some problems on Windows systems with overzealous firewalls. Fix for
4353 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4355 - If we mark an OR connection for close based on a cell we process,
4356 don't process any further cells on it. We already avoid further
4357 reads on marked-for-close connections, but now we also discard the
4358 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4359 which was the first version where we might mark a connection for
4360 close based on processing a cell on it.
4361 - Correctly sanity-check that we don't underflow on a memory
4362 allocation (and then assert) for hidden service introduction
4363 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4364 bugfix on 0.2.1.5-alpha.
4365 - Fix a memory leak when we check whether a hidden service
4366 descriptor has any usable introduction points left. Fixes bug
4367 4424. Bugfix on 0.2.2.25-alpha.
4368 - Don't crash when we're running as a relay and don't have a GeoIP
4369 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
4370 we've had in the 0.2.3.x branch already.
4371 - When running as a client, do not print a misleading (and plain
4372 wrong) log message that we're collecting "directory request"
4373 statistics: clients don't collect statistics. Also don't create a
4374 useless (because empty) stats file in the stats/ directory. Fixes
4375 bug 4353; bugfix on 0.2.2.34.
4378 - Detect failure to initialize Libevent. This fix provides better
4379 detection for future instances of bug 4457.
4380 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4381 function. This was eating up hideously large amounts of time on some
4382 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4383 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4384 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4386 - Don't warn about unused log_mutex in log.c when building with
4387 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4388 0.1.0.6-rc which introduced --disable-threads.
4389 - When configuring, starting, or stopping an NT service, stop
4390 immediately after the service configuration attempt has succeeded
4391 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4392 - When sending a NETINFO cell, include the original address
4393 received for the other side, not its canonical address. Found
4394 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4395 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4396 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4397 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4398 occurred when a client tried to fetch a descriptor for a bridge
4399 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4400 - Backport fixes for a pair of compilation warnings on Windows.
4401 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
4402 - If we had ever tried to call tor_addr_to_str on an address of
4403 unknown type, we would have done a strdup on an uninitialized
4404 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4405 Reported by "troll_un".
4406 - Correctly detect and handle transient lookup failures from
4407 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4408 Reported by "troll_un".
4409 - Fix null-pointer access that could occur if TLS allocation failed.
4410 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4411 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4412 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4415 - Add two new config options for directory authorities:
4416 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4417 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4418 that is always sufficient to satisfy the bandwidth requirement for
4419 the Guard flag. Now it will be easier for researchers to simulate
4420 Tor networks with different values. Resolves ticket 4484.
4421 - When Tor ignores a hidden service specified in its configuration,
4422 include the hidden service's directory in the warning message.
4423 Previously, we would only tell the user that some hidden service
4424 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4425 - Update to the December 6 2011 Maxmind GeoLite Country database.
4427 o Packaging changes:
4428 - Make it easier to automate expert package builds on Windows,
4429 by removing an absolute path from makensis.exe command.
4432 Changes in version 0.2.1.32 - 2011-12-16
4433 Tor 0.2.1.32 backports important security and privacy fixes for
4434 oldstable. This release is intended only for package maintainers and
4435 others who cannot use the 0.2.2 stable series. All others should be
4436 using Tor 0.2.2.x or newer.
4438 The Tor 0.2.1.x series will reach formal end-of-life some time in
4439 early 2012; we will stop releasing patches for it then.
4441 o Major bugfixes (also included in 0.2.2.x):
4442 - Correctly sanity-check that we don't underflow on a memory
4443 allocation (and then assert) for hidden service introduction
4444 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4445 bugfix on 0.2.1.5-alpha.
4446 - Fix a heap overflow bug that could occur when trying to pull
4447 data into the first chunk of a buffer, when that chunk had
4448 already had some data drained from it. Fixes CVE-2011-2778;
4449 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4452 - Update to the December 6 2011 Maxmind GeoLite Country database.
4455 Changes in version 0.2.3.9-alpha - 2011-12-08
4456 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
4457 a "DisableNetwork" security feature that bundles can use to avoid
4458 touching the network until bridges are configured, moves forward on
4459 the pluggable transport design, fixes a flaw in the hidden service
4460 design that unnecessarily prevented clients with wrong clocks from
4461 reaching hidden services, and fixes a wide variety of other issues.
4464 - Clients can now connect to private bridges over IPv6. Bridges
4465 still need at least one IPv4 address in order to connect to
4466 other relays. Note that we don't yet handle the case where the
4467 user has two bridge lines for the same bridge (one IPv4, one
4468 IPv6). Implements parts of proposal 186.
4469 - New "DisableNetwork" config option to prevent Tor from launching any
4470 connections or accepting any connections except on a control port.
4471 Bundles and controllers can set this option before letting Tor talk
4472 to the rest of the network, for example to prevent any connections
4473 to a non-bridge address. Packages like Orbot can also use this
4474 option to instruct Tor to save power when the network is off.
4475 - Clients and bridges can now be configured to use a separate
4476 "transport" proxy. This approach makes the censorship arms race
4477 easier by allowing bridges to use protocol obfuscation plugins. It
4478 implements the "managed proxy" part of proposal 180 (ticket 3472).
4479 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
4480 implementation. It makes AES_CTR about 7% faster than our old one
4481 (which was about 10% faster than the one OpenSSL used to provide).
4482 Resolves ticket 4526.
4483 - Add a "tor2web mode" for clients that want to connect to hidden
4484 services non-anonymously (and possibly more quickly). As a safety
4485 measure to try to keep users from turning this on without knowing
4486 what they are doing, tor2web mode must be explicitly enabled at
4487 compile time, and a copy of Tor compiled to run in tor2web mode
4488 cannot be used as a normal Tor client. Implements feature 2553.
4489 - Add experimental support for running on Windows with IOCP and no
4490 kernel-space socket buffers. This feature is controlled by a new
4491 "UserspaceIOCPBuffers" config option (off by default), which has
4492 no effect unless Tor has been built with support for bufferevents,
4493 is running on Windows, and has enabled IOCP. This may, in the long
4494 run, help solve or mitigate bug 98.
4495 - Use a more secure consensus parameter voting algorithm. Now at
4496 least three directory authorities or a majority of them must
4497 vote on a given parameter before it will be included in the
4498 consensus. Implements proposal 178.
4501 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
4502 They used to check that the timestamp was within 30 minutes
4503 of their system clock, so they could cap the size of their
4504 replay-detection cache, but that approach unnecessarily refused
4505 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
4506 the v3 intro-point protocol (the first one which sent a timestamp
4507 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
4508 - Only use the EVP interface when AES acceleration is enabled,
4509 to avoid a 5-7% performance regression. Resolves issue 4525;
4510 bugfix on 0.2.3.8-alpha.
4512 o Privacy/anonymity features (bridge detection):
4513 - Make bridge SSL certificates a bit more stealthy by using random
4514 serial numbers, in the same fashion as OpenSSL when generating
4515 self-signed certificates. Implements ticket 4584.
4516 - Introduce a new config option "DynamicDHGroups", enabled by
4517 default, which provides each bridge with a unique prime DH modulus
4518 to be used during SSL handshakes. This option attempts to help
4519 against censors who might use the Apache DH modulus as a static
4520 identifier for bridges. Addresses ticket 4548.
4522 o Minor features (new/different config options):
4523 - New configuration option "DisableDebuggerAttachment" (on by default)
4524 to prevent basic debugging attachment attempts by other processes.
4525 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
4526 - Allow MapAddress directives to specify matches against super-domains,
4527 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
4528 Implements issue 933.
4529 - Slightly change behavior of "list" options (that is, config
4530 options that can appear more than once) when they appear both in
4531 torrc and on the command line. Previously, the command-line options
4532 would be appended to the ones from torrc. Now, the command-line
4533 options override the torrc options entirely. This new behavior
4534 allows the user to override list options (like exit policies and
4535 ports to listen on) from the command line, rather than simply
4536 appending to the list.
4537 - You can get the old (appending) command-line behavior for "list"
4538 options by prefixing the option name with a "+".
4539 - You can remove all the values for a "list" option from the command
4540 line without adding any new ones by prefixing the option name
4542 - Add experimental support for a "defaults" torrc file to be parsed
4543 before the regular torrc. Torrc options override the defaults file's
4544 options in the same way that the command line overrides the torrc.
4545 The SAVECONF controller command saves only those options which
4546 differ between the current configuration and the defaults file. HUP
4547 reloads both files. (Note: This is an experimental feature; its
4548 behavior will probably be refined in future 0.2.3.x-alpha versions
4549 to better meet packagers' needs.) Implements task 4552.
4552 - Try to make the introductory warning message that Tor prints on
4553 startup more useful for actually finding help and information.
4554 Resolves ticket 2474.
4555 - Running "make version" now displays the version of Tor that
4556 we're about to build. Idea from katmagic; resolves issue 4400.
4557 - Expire old or over-used hidden service introduction points.
4558 Required by fix for bug 3460.
4559 - Move the replay-detection cache for the RSA-encrypted parts of
4560 INTRODUCE2 cells to the introduction point data structures.
4561 Previously, we would use one replay-detection cache per hidden
4562 service. Required by fix for bug 3460.
4563 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4564 public key replay-detection cache from 60 minutes to 5 minutes. This
4565 replay-detection cache is now used only to detect multiple
4566 INTRODUCE2 cells specifying the same rendezvous point, so we can
4567 avoid launching multiple simultaneous attempts to connect to it.
4569 o Minor bugfixes (on Tor 0.2.2.x and earlier):
4570 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4571 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4573 - Fix a minor formatting issue in one of tor-gencert's error messages.
4575 - Prevent a false positive from the check-spaces script, by disabling
4576 the "whitespace between function name and (" check for functions
4578 - Fix a log message suggesting that people contact a non-existent
4579 email address. Fixes bug 3448.
4580 - Fix null-pointer access that could occur if TLS allocation failed.
4581 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4582 - Report a real bootstrap problem to the controller on router
4583 identity mismatch. Previously we just said "foo", which probably
4584 made a lot of sense at the time. Fixes bug 4169; bugfix on
4586 - If we had ever tried to call tor_addr_to_str() on an address of
4587 unknown type, we would have done a strdup() on an uninitialized
4588 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4589 Reported by "troll_un".
4590 - Correctly detect and handle transient lookup failures from
4591 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4592 Reported by "troll_un".
4593 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4594 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4595 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
4596 bug 4532; found by "troll_un".
4598 o Minor bugfixes (on Tor 0.2.3.x):
4599 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
4601 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
4602 circuit for use as a hidden service client's rendezvous point.
4603 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
4604 with help from wanoskarnet.
4605 - Restore behavior of overriding SocksPort, ORPort, and similar
4606 options from the command line. Bugfix on 0.2.3.3-alpha.
4609 - Properly handle the case where the build-tree is not the same
4610 as the source tree when generating src/common/common_sha1.i,
4611 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
4612 bugfix on 0.2.0.1-alpha.
4614 o Code simplifications, cleanups, and refactorings:
4615 - Remove the pure attribute from all functions that used it
4616 previously. In many cases we assigned it incorrectly, because the
4617 functions might assert or call impure functions, and we don't have
4618 evidence that keeping the pure attribute is worthwhile. Implements
4619 changes suggested in ticket 4421.
4620 - Remove some dead code spotted by coverity. Fixes cid 432.
4621 Bugfix on 0.2.3.1-alpha, closes bug 4637.
4624 Changes in version 0.2.3.8-alpha - 2011-11-22
4625 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
4626 socketpair-related bug that has been bothering Windows users. It adds
4627 support to serve microdescriptors to controllers, so Vidalia's network
4628 map can resume listing relays (once Vidalia implements its side),
4629 and adds better support for hardware AES acceleration. Finally, it
4630 starts the process of adjusting the bandwidth cutoff for getting the
4631 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
4632 that tiny relays harm performance more than they help network capacity.
4635 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4636 that it doesn't attempt to allocate a socketpair. This could cause
4637 some problems on Windows systems with overzealous firewalls. Fix for
4638 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4640 - Correctly sanity-check that we don't underflow on a memory
4641 allocation (and then assert) for hidden service introduction
4642 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4643 bugfix on 0.2.1.5-alpha.
4644 - Remove the artificially low cutoff of 20KB to guarantee the Fast
4645 flag. In the past few years the average relay speed has picked
4646 up, and while the "top 7/8 of the network get the Fast flag" and
4647 "all relays with 20KB or more of capacity get the Fast flag" rules
4648 used to have the same result, now the top 7/8 of the network has
4649 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
4650 - Fix a rare assertion failure when checking whether a v0 hidden
4651 service descriptor has any usable introduction points left, and
4652 we don't have enough information to build a circuit to the first
4653 intro point named in the descriptor. The HS client code in
4654 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
4655 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
4656 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
4657 - Make bridge authorities not crash when they are asked for their own
4658 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
4659 - When running as a client, do not print a misleading (and plain
4660 wrong) log message that we're collecting "directory request"
4661 statistics: clients don't collect statistics. Also don't create a
4662 useless (because empty) stats file in the stats/ directory. Fixes
4663 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
4666 - Allow Tor controllers like Vidalia to obtain the microdescriptor
4667 for a relay by identity digest or nickname. Previously,
4668 microdescriptors were only available by their own digests, so a
4669 controller would have to ask for and parse the whole microdescriptor
4670 consensus in order to look up a single relay's microdesc. Fixes
4671 bug 3832; bugfix on 0.2.3.1-alpha.
4672 - Use OpenSSL's EVP interface for AES encryption, so that all AES
4673 operations can use hardware acceleration (if present). Resolves
4676 o Minor bugfixes (on 0.2.2.x and earlier):
4677 - Detect failure to initialize Libevent. This fix provides better
4678 detection for future instances of bug 4457.
4679 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4680 function. This was eating up hideously large amounts of time on some
4681 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4682 - Don't warn about unused log_mutex in log.c when building with
4683 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4684 0.1.0.6-rc which introduced --disable-threads.
4685 - Allow manual 'authenticate' commands to the controller interface
4686 from netcat (nc) as well as telnet. We were rejecting them because
4687 they didn't come with the expected whitespace at the end of the
4688 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
4689 - Fix some (not actually triggerable) buffer size checks in usage of
4690 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
4692 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
4693 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
4694 - When configuring, starting, or stopping an NT service, stop
4695 immediately after the service configuration attempt has succeeded
4696 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4697 - When sending a NETINFO cell, include the original address
4698 received for the other side, not its canonical address. Found
4699 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4700 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
4701 can pick them up when the tests aren't disabled. Bugfix on
4702 0.2.2.4-alpha which introduced tinytest.
4703 - Fix a memory leak when we check whether a hidden service
4704 descriptor has any usable introduction points left. Fixes bug
4705 4424. Bugfix on 0.2.2.25-alpha.
4706 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4707 occurred when a client tried to fetch a descriptor for a bridge
4708 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4710 o Minor bugfixes (on 0.2.3.x):
4711 - Make util unit tests build correctly with MSVC. Bugfix on
4712 0.2.3.3-alpha. Patch by Gisle Vanem.
4713 - Successfully detect AUTH_CHALLENGE cells with no recognized
4714 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
4716 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
4717 it should still send a NETINFO cell to allow the connection to
4718 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
4720 - Log less loudly when we get an invalid authentication certificate
4721 from a source other than a directory authority: it's not unusual
4722 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
4724 - Tolerate servers with more clock skew in their authentication
4725 certificates than previously. Fixes bug 4371; bugfix on
4727 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
4728 on 0.2.3.4-alpha and 0.2.3.6-alpha.
4731 - Add two new config options for directory authorities:
4732 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4733 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4734 that is always sufficient to satisfy the bandwidth requirement for
4735 the Guard flag. Now it will be easier for researchers to simulate
4736 Tor networks with different values. Resolves ticket 4484.
4737 - When Tor ignores a hidden service specified in its configuration,
4738 include the hidden service's directory in the warning message.
4739 Previously, we would only tell the user that some hidden service
4740 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4741 - When we fail to initialize Libevent, retry with IOCP disabled so we
4742 don't need to turn on multi-threading support in Libevent, which in
4743 turn requires a working socketpair(). This is a workaround for bug
4744 4457, which affects Libevent versions from 2.0.1-alpha through
4746 - Detect when we try to build on a platform that doesn't define
4747 AF_UNSPEC to 0. We don't work there, so refuse to compile.
4748 - Update to the November 1 2011 Maxmind GeoLite Country database.
4750 o Packaging changes:
4751 - Make it easier to automate expert package builds on Windows,
4752 by removing an absolute path from makensis.exe command.
4754 o Code simplifications and refactoring:
4755 - Remove some redundant #include directives throughout the code.
4756 Patch from Andrea Gelmini.
4757 - Unconditionally use OpenSSL's AES implementation instead of our
4758 old built-in one. OpenSSL's AES has been better for a while, and
4759 relatively few servers should still be on any version of OpenSSL
4760 that doesn't have good optimized assembly AES.
4761 - Use the name "CERTS" consistently to refer to the new cell type;
4762 we were calling it CERT in some places and CERTS in others.
4765 - Numerous new unit tests for functions in util.c and address.c by
4767 - The long-disabled benchmark tests are now split into their own
4768 ./src/test/bench binary.
4769 - The benchmark tests can now use more accurate timers than
4770 gettimeofday() when such timers are available.
4773 Changes in version 0.2.3.7-alpha - 2011-10-30
4774 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
4775 the new v3 handshake. It also resolves yet another bridge address
4779 - If we mark an OR connection for close based on a cell we process,
4780 don't process any further cells on it. We already avoid further
4781 reads on marked-for-close connections, but now we also discard the
4782 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4783 which was the first version where we might mark a connection for
4784 close based on processing a cell on it.
4785 - Fix a double-free bug that would occur when we received an invalid
4786 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
4787 bugfix on 0.2.3.6-alpha.
4788 - Bridges no longer include their address in NETINFO cells on outgoing
4789 OR connections, to allow them to blend in better with clients.
4790 Removes another avenue for enumerating bridges. Reported by
4791 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
4792 cells were introduced.
4795 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
4796 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4799 Changes in version 0.2.3.6-alpha - 2011-10-26
4800 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
4801 anonymity vulnerability where an attacker can deanonymize Tor
4802 users. Everybody should upgrade.
4804 This release also features support for a new v3 connection handshake
4805 protocol, and fixes to make hidden service connections more robust.
4808 - Implement a new handshake protocol (v3) for authenticating Tors to
4809 each other over TLS. It should be more resistant to fingerprinting
4810 than previous protocols, and should require less TLS hacking for
4811 future Tor implementations. Implements proposal 176.
4812 - Allow variable-length padding cells to disguise the length of
4813 Tor's TLS records. Implements part of proposal 184.
4815 o Privacy/anonymity fixes (clients):
4816 - Clients and bridges no longer send TLS certificate chains on
4817 outgoing OR connections. Previously, each client or bridge would
4818 use the same cert chain for all outgoing OR connections until
4819 its IP address changes, which allowed any relay that the client
4820 or bridge contacted to determine which entry guards it is using.
4821 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4822 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4823 no longer considers that connection as suitable for satisfying a
4824 circuit EXTEND request. Now relays can protect clients from the
4825 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4826 - Directory authorities no longer assign the Guard flag to relays
4827 that haven't upgraded to the above "refuse EXTEND requests
4828 to client connections" fix. Now directory authorities can
4829 protect clients from the CVE-2011-2768 issue even if neither
4830 the clients nor the relays have upgraded yet. There's a new
4831 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4832 to let us transition smoothly, else tomorrow there would be no
4835 o Major bugfixes (hidden services):
4836 - Improve hidden service robustness: when an attempt to connect to
4837 a hidden service ends, be willing to refetch its hidden service
4838 descriptors from each of the HSDir relays responsible for them
4839 immediately. Previously, we would not consider refetching the
4840 service's descriptors from each HSDir for 15 minutes after the last
4841 fetch, which was inconvenient if the hidden service was not running
4842 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
4843 - When one of a hidden service's introduction points appears to be
4844 unreachable, stop trying it. Previously, we would keep trying
4845 to build circuits to the introduction point until we lost the
4846 descriptor, usually because the user gave up and restarted Tor.
4847 Partly fixes bug 3825.
4848 - Don't launch a useless circuit after failing to use one of a
4849 hidden service's introduction points. Previously, we would
4850 launch a new introduction circuit, but not set the hidden service
4851 which that circuit was intended to connect to, so it would never
4852 actually be used. A different piece of code would then create a
4853 new introduction circuit correctly. Bug reported by katmagic and
4854 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
4856 o Major bugfixes (other):
4857 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4858 that they initiated. Relays could distinguish incoming bridge
4859 connections from client connections, creating another avenue for
4860 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4861 Found by "frosty_un".
4862 - Don't update the AccountingSoftLimitHitAt state file entry whenever
4863 tor gets started. This prevents a wrong average bandwidth
4864 estimate, which would cause relays to always start a new accounting
4865 interval at the earliest possible moment. Fixes bug 2003; bugfix
4866 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
4867 immensely in tracking this bug down.
4868 - Fix a crash bug when changing node restrictions while a DNS lookup
4869 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4872 o Minor bugfixes (on 0.2.2.x and earlier):
4873 - When a hidden service turns an extra service-side introduction
4874 circuit into a general-purpose circuit, free the rend_data and
4875 intro_key fields first, so we won't leak memory if the circuit
4876 is cannibalized for use as another service-side introduction
4877 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
4878 - Rephrase the log message emitted if the TestSocks check is
4879 successful. Patch from Fabian Keil; fixes bug 4094.
4880 - Bridges now skip DNS self-tests, to act a little more stealthily.
4881 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
4882 bridges. Patch by "warms0x".
4883 - Remove a confusing dollar sign from the example fingerprint in the
4884 man page, and also make the example fingerprint a valid one. Fixes
4885 bug 4309; bugfix on 0.2.1.3-alpha.
4886 - Fix internal bug-checking logic that was supposed to catch
4887 failures in digest generation so that it will fail more robustly
4888 if we ask for a nonexistent algorithm. Found by Coverity Scan.
4889 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
4890 - Report any failure in init_keys() calls launched because our
4891 IP address has changed. Spotted by Coverity Scan. Bugfix on
4892 0.1.1.4-alpha; fixes CID 484.
4894 o Minor bugfixes (on 0.2.3.x):
4895 - Fix a bug in configure.in that kept it from building a configure
4896 script with autoconf versions earlier than 2.61. Fixes bug 2430;
4897 bugfix on 0.2.3.1-alpha.
4898 - Don't warn users that they are exposing a client port to the
4899 Internet if they have specified an RFC1918 address. Previously,
4900 we would warn if the user had specified any non-loopback
4901 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
4902 - Fix memory leaks in the failing cases of the new SocksPort and
4903 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
4904 fixes coverity CIDs 485, 486, and 487.
4907 - When a hidden service's introduction point times out, consider
4908 trying it again during the next attempt to connect to the
4909 HS. Previously, we would not try it again unless a newly fetched
4910 descriptor contained it. Required by fixes for bugs 1297 and 3825.
4911 - The next version of Windows will be called Windows 8, and it has
4912 a major version of 6, minor version of 2. Correctly identify that
4913 version instead of calling it "Very recent version". Resolves
4914 ticket 4153; reported by funkstar.
4915 - The Bridge Authority now writes statistics on how many bridge
4916 descriptors it gave out in total, and how many unique descriptors
4917 it gave out. It also lists how often the most and least commonly
4918 fetched descriptors were given out, as well as the median and
4919 25th/75th percentile. Implements tickets 4200 and 4294.
4920 - Update to the October 4 2011 Maxmind GeoLite Country database.
4922 o Code simplifications and refactoring:
4923 - Remove some old code to remember statistics about which descriptors
4924 we've served as a directory mirror. The feature wasn't used and
4925 is outdated now that microdescriptors are around.
4926 - Rename Tor functions that turn strings into addresses, so that
4927 "parse" indicates that no hostname resolution occurs, and
4928 "lookup" indicates that hostname resolution may occur. This
4929 should help prevent mistakes in the future. Fixes bug 3512.
4932 Changes in version 0.2.2.34 - 2011-10-26
4933 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
4934 can deanonymize Tor users. Everybody should upgrade.
4936 The attack relies on four components: 1) Clients reuse their TLS cert
4937 when talking to different relays, so relays can recognize a user by
4938 the identity key in her cert. 2) An attacker who knows the client's
4939 identity key can probe each guard relay to see if that identity key
4940 is connected to that guard relay right now. 3) A variety of active
4941 attacks in the literature (starting from "Low-Cost Traffic Analysis
4942 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
4943 discover the guard relays that a Tor user visiting the website is using.
4944 4) Clients typically pick three guards at random, so the set of guards
4945 for a given user could well be a unique fingerprint for her. This
4946 release fixes components #1 and #2, which is enough to block the attack;
4947 the other two remain as open research problems. Special thanks to
4948 "frosty_un" for reporting the issue to us!
4950 Clients should upgrade so they are no longer recognizable by the TLS
4951 certs they present. Relays should upgrade so they no longer allow a
4952 remote attacker to probe them to test whether unpatched clients are
4953 currently connected to them.
4955 This release also fixes several vulnerabilities that allow an attacker
4956 to enumerate bridge relays. Some bridge enumeration attacks still
4957 remain; see for example proposal 188.
4959 o Privacy/anonymity fixes (clients):
4960 - Clients and bridges no longer send TLS certificate chains on
4961 outgoing OR connections. Previously, each client or bridge would
4962 use the same cert chain for all outgoing OR connections until
4963 its IP address changes, which allowed any relay that the client
4964 or bridge contacted to determine which entry guards it is using.
4965 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
4966 - If a relay receives a CREATE_FAST cell on a TLS connection, it
4967 no longer considers that connection as suitable for satisfying a
4968 circuit EXTEND request. Now relays can protect clients from the
4969 CVE-2011-2768 issue even if the clients haven't upgraded yet.
4970 - Directory authorities no longer assign the Guard flag to relays
4971 that haven't upgraded to the above "refuse EXTEND requests
4972 to client connections" fix. Now directory authorities can
4973 protect clients from the CVE-2011-2768 issue even if neither
4974 the clients nor the relays have upgraded yet. There's a new
4975 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
4976 to let us transition smoothly, else tomorrow there would be no
4979 o Privacy/anonymity fixes (bridge enumeration):
4980 - Bridge relays now do their directory fetches inside Tor TLS
4981 connections, like all the other clients do, rather than connecting
4982 directly to the DirPort like public relays do. Removes another
4983 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4984 - Bridges relays now build circuits for themselves in a more similar
4985 way to how clients build them. Removes another avenue for
4986 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4987 when bridges were introduced.
4988 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
4989 that they initiated. Relays could distinguish incoming bridge
4990 connections from client connections, creating another avenue for
4991 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
4992 Found by "frosty_un".
4995 - Fix a crash bug when changing node restrictions while a DNS lookup
4996 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
4998 - Don't launch a useless circuit after failing to use one of a
4999 hidden service's introduction points. Previously, we would
5000 launch a new introduction circuit, but not set the hidden service
5001 which that circuit was intended to connect to, so it would never
5002 actually be used. A different piece of code would then create a
5003 new introduction circuit correctly. Bug reported by katmagic and
5004 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5007 - Change an integer overflow check in the OpenBSD_Malloc code so
5008 that GCC is less likely to eliminate it as impossible. Patch
5009 from Mansour Moufid. Fixes bug 4059.
5010 - When a hidden service turns an extra service-side introduction
5011 circuit into a general-purpose circuit, free the rend_data and
5012 intro_key fields first, so we won't leak memory if the circuit
5013 is cannibalized for use as another service-side introduction
5014 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5015 - Bridges now skip DNS self-tests, to act a little more stealthily.
5016 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5017 bridges. Patch by "warms0x".
5018 - Fix internal bug-checking logic that was supposed to catch
5019 failures in digest generation so that it will fail more robustly
5020 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5021 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5022 - Report any failure in init_keys() calls launched because our
5023 IP address has changed. Spotted by Coverity Scan. Bugfix on
5024 0.1.1.4-alpha; fixes CID 484.
5026 o Minor bugfixes (log messages and documentation):
5027 - Remove a confusing dollar sign from the example fingerprint in the
5028 man page, and also make the example fingerprint a valid one. Fixes
5029 bug 4309; bugfix on 0.2.1.3-alpha.
5030 - The next version of Windows will be called Windows 8, and it has
5031 a major version of 6, minor version of 2. Correctly identify that
5032 version instead of calling it "Very recent version". Resolves
5033 ticket 4153; reported by funkstar.
5034 - Downgrade log messages about circuit timeout calibration from
5035 "notice" to "info": they don't require or suggest any human
5036 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5037 bugfix on 0.2.2.14-alpha.
5040 - Turn on directory request statistics by default and include them in
5041 extra-info descriptors. Don't break if we have no GeoIP database.
5042 Backported from 0.2.3.1-alpha; implements ticket 3951.
5043 - Update to the October 4 2011 Maxmind GeoLite Country database.
5046 Changes in version 0.2.1.31 - 2011-10-26
5047 Tor 0.2.1.31 backports important security and privacy fixes for
5048 oldstable. This release is intended only for package maintainers and
5049 others who cannot use the 0.2.2 stable series. All others should be
5050 using Tor 0.2.2.x or newer.
5052 o Security fixes (also included in 0.2.2.x):
5053 - Replace all potentially sensitive memory comparison operations
5054 with versions whose runtime does not depend on the data being
5055 compared. This will help resist a class of attacks where an
5056 adversary can use variations in timing information to learn
5057 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5058 implementation by Robert Ransom based partially on code by DJB.)
5059 - Fix an assert in parsing router descriptors containing IPv6
5060 addresses. This one took down the directory authorities when
5061 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5063 o Privacy/anonymity fixes (also included in 0.2.2.x):
5064 - Clients and bridges no longer send TLS certificate chains on
5065 outgoing OR connections. Previously, each client or bridge would
5066 use the same cert chain for all outgoing OR connections until
5067 its IP address changes, which allowed any relay that the client
5068 or bridge contacted to determine which entry guards it is using.
5069 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5070 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5071 no longer considers that connection as suitable for satisfying a
5072 circuit EXTEND request. Now relays can protect clients from the
5073 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5074 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5075 that they initiated. Relays could distinguish incoming bridge
5076 connections from client connections, creating another avenue for
5077 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5078 Found by "frosty_un".
5079 - When receiving a hidden service descriptor, check that it is for
5080 the hidden service we wanted. Previously, Tor would store any
5081 hidden service descriptors that a directory gave it, whether it
5082 wanted them or not. This wouldn't have let an attacker impersonate
5083 a hidden service, but it did let directories pre-seed a client
5084 with descriptors that it didn't want. Bugfix on 0.0.6.
5085 - Avoid linkability based on cached hidden service descriptors: forget
5086 all hidden service descriptors cached as a client when processing a
5087 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5088 - Make the bridge directory authority refuse to answer directory
5089 requests for "all" descriptors. It used to include bridge
5090 descriptors in its answer, which was a major information leak.
5091 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5092 - Don't attach new streams to old rendezvous circuits after SIGNAL
5093 NEWNYM. Previously, we would keep using an existing rendezvous
5094 circuit if it remained open (i.e. if it were kept open by a
5095 long-lived stream, or if a new stream were attached to it before
5096 Tor could notice that it was old and no longer in use). Bugfix on
5097 0.1.1.15-rc; fixes bug 3375.
5099 o Minor bugfixes (also included in 0.2.2.x):
5100 - When we restart our relay, we might get a successful connection
5101 from the outside before we've started our reachability tests,
5102 triggering a warning: "ORPort found reachable, but I have no
5103 routerinfo yet. Failing to inform controller of success." This
5104 bug was harmless unless Tor is running under a controller
5105 like Vidalia, in which case the controller would never get a
5106 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5108 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5109 enabled. Fixes bug 1526.
5110 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5111 anything since 0.2.1.16-rc.
5112 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5113 None of the cases where we did this before were wrong, but by making
5114 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5115 - Fix a rare crash bug that could occur when a client was configured
5116 with a large number of bridges. Fixes bug 2629; bugfix on
5117 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5118 - Correct the warning displayed when a rendezvous descriptor exceeds
5119 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5121 - Fix an uncommon assertion failure when running with DNSPort under
5122 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5123 - When warning about missing zlib development packages during compile,
5124 give the correct package names. Bugfix on 0.2.0.1-alpha.
5125 - Require that introduction point keys and onion keys have public
5126 exponent 65537. Bugfix on 0.2.0.10-alpha.
5127 - Do not crash when our configuration file becomes unreadable, for
5128 example due to a permissions change, between when we start up
5129 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5131 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5133 - Always NUL-terminate the sun_path field of a sockaddr_un before
5134 passing it to the kernel. (Not a security issue: kernels are
5135 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5136 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5137 - Don't stack-allocate the list of supplementary GIDs when we're
5138 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5139 could take up to 256K, which is way too much stack. Found by
5140 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5142 o Minor bugfixes (only in 0.2.1.x):
5143 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5144 rely on them. Bugfix on 0.2.1.30.
5145 - Use git revisions instead of svn revisions when generating our
5146 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5148 o Minor features (also included in 0.2.2.x):
5149 - Adjust the expiration time on our SSL session certificates to
5150 better match SSL certs seen in the wild. Resolves ticket 4014.
5151 - Allow nameservers with IPv6 address. Resolves bug 2574.
5152 - Update to the October 4 2011 Maxmind GeoLite Country database.
5155 Changes in version 0.2.3.5-alpha - 2011-09-28
5156 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
5157 bridge relays; fixes an assertion error that many users started hitting
5158 today; and adds the ability to refill token buckets more often than
5159 once per second, allowing significant performance improvements.
5162 - Bridge relays now do their directory fetches inside Tor TLS
5163 connections, like all the other clients do, rather than connecting
5164 directly to the DirPort like public relays do. Removes another
5165 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5166 - Bridges relays now build circuits for themselves in a more similar
5167 way to how clients build them. Removes another avenue for
5168 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5169 when bridges were introduced.
5172 - Fix an "Assertion md->held_by_node == 1 failed" error that could
5173 occur when the same microdescriptor was referenced by two node_t
5174 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
5176 o Major features (networking):
5177 - Add a new TokenBucketRefillInterval option to refill token buckets
5178 more frequently than once per second. This should improve network
5179 performance, alleviate queueing problems, and make traffic less
5180 bursty. Implements proposal 183; closes ticket 3630. Design by
5181 Florian Tschorsch and Björn Scheuermann; implementation by
5185 - Change an integer overflow check in the OpenBSD_Malloc code so
5186 that GCC is less likely to eliminate it as impossible. Patch
5187 from Mansour Moufid. Fixes bug 4059.
5189 o Minor bugfixes (usability):
5190 - Downgrade log messages about circuit timeout calibration from
5191 "notice" to "info": they don't require or suggest any human
5192 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5193 bugfix on 0.2.2.14-alpha.
5195 o Minor features (diagnostics):
5196 - When the system call to create a listener socket fails, log the
5197 error message explaining why. This may help diagnose bug 4027.
5200 Changes in version 0.2.3.4-alpha - 2011-09-13
5201 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
5202 tweak to Tor's TLS handshake that makes relays and bridges that run
5203 this new version reachable from Iran again. It also fixes a few new
5204 bugs in 0.2.3.x, and teaches relays to recognize when they're not
5205 listed in the network consensus and republish.
5207 o Major bugfixes (also part of 0.2.2.33):
5208 - Avoid an assertion failure when reloading a configuration with
5209 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5210 3923; bugfix on 0.2.2.25-alpha.
5212 o Minor features (security, also part of 0.2.2.33):
5213 - Check for replays of the public-key encrypted portion of an
5214 INTRODUCE1 cell, in addition to the current check for replays of
5215 the g^x value. This prevents a possible class of active attacks
5216 by an attacker who controls both an introduction point and a
5217 rendezvous point, and who uses the malleability of AES-CTR to
5218 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5219 that these attacks are infeasible (requiring the attacker to send
5220 on the order of zettabytes of altered cells in a short interval),
5221 but we'd rather block them off in case there are any classes of
5222 this attack that we missed. Reported by Willem Pinckaers.
5224 o Minor features (also part of 0.2.2.33):
5225 - Adjust the expiration time on our SSL session certificates to
5226 better match SSL certs seen in the wild. Resolves ticket 4014.
5227 - Change the default required uptime for a relay to be accepted as
5228 a HSDir (hidden service directory) from 24 hours to 25 hours.
5229 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5230 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5231 authorities to abstain from voting on assignment of the HSDir
5232 consensus flag. Related to bug 2649.
5233 - Update to the September 6 2011 Maxmind GeoLite Country database.
5235 o Minor bugfixes (also part of 0.2.2.33):
5236 - Demote the 'replay detected' log message emitted when a hidden
5237 service receives the same Diffie-Hellman public key in two different
5238 INTRODUCE2 cells to info level. A normal Tor client can cause that
5239 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5240 fixes part of bug 2442.
5241 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5242 level. There is nothing that a hidden service's operator can do
5243 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5245 - Clarify a log message specifying the characters permitted in
5246 HiddenServiceAuthorizeClient client names. Previously, the log
5247 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5248 given the impression that every ASCII character between "+" and "_"
5249 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5251 o Build fixes (also part of 0.2.2.33):
5252 - Clean up some code issues that prevented Tor from building on older
5253 BSDs. Fixes bug 3894; reported by "grarpamp".
5254 - Search for a platform-specific version of "ar" when cross-compiling.
5255 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5258 - Fix a bug where the SocksPort option (for example) would get
5259 ignored and replaced by the default if a SocksListenAddress
5260 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
5264 - Relays now try regenerating and uploading their descriptor more
5265 frequently if they are not listed in the consensus, or if the
5266 version of their descriptor listed in the consensus is too
5267 old. This fix should prevent situations where a server declines
5268 to re-publish itself because it has done so too recently, even
5269 though the authorities decided not to list its recent-enough
5270 descriptor. Fix for bug 3327.
5273 - Relays now include a reason for regenerating their descriptors
5274 in an HTTP header when uploading to the authorities. This will
5275 make it easier to debug descriptor-upload issues in the future.
5276 - When starting as root and then changing our UID via the User
5277 control option, and we have a ControlSocket configured, make sure
5278 that the ControlSocket is owned by the same account that Tor will
5279 run under. Implements ticket 3421; fix by Jérémy Bobbio.
5282 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
5283 utility function used in the control-port code). This shouldn't
5284 ever happen unless Tor is completely out of memory, but if it did
5285 happen and Tor somehow recovered from it, Tor could have sent a log
5286 message to a control port in the middle of a reply to a controller
5287 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
5288 - Make 'FetchUselessDescriptors' cause all descriptor types and
5289 all consensus types (including microdescriptors) to get fetched.
5290 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
5293 - Make a new "entry connection" struct as an internal subtype of "edge
5294 connection", to simplify the code and make exit connections smaller.
5297 Changes in version 0.2.2.33 - 2011-09-13
5298 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5299 TLS handshake that makes relays and bridges that run this new version
5300 reachable from Iran again.
5303 - Avoid an assertion failure when reloading a configuration with
5304 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5305 3923; bugfix on 0.2.2.25-alpha.
5307 o Minor features (security):
5308 - Check for replays of the public-key encrypted portion of an
5309 INTRODUCE1 cell, in addition to the current check for replays of
5310 the g^x value. This prevents a possible class of active attacks
5311 by an attacker who controls both an introduction point and a
5312 rendezvous point, and who uses the malleability of AES-CTR to
5313 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5314 that these attacks are infeasible (requiring the attacker to send
5315 on the order of zettabytes of altered cells in a short interval),
5316 but we'd rather block them off in case there are any classes of
5317 this attack that we missed. Reported by Willem Pinckaers.
5320 - Adjust the expiration time on our SSL session certificates to
5321 better match SSL certs seen in the wild. Resolves ticket 4014.
5322 - Change the default required uptime for a relay to be accepted as
5323 a HSDir (hidden service directory) from 24 hours to 25 hours.
5324 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5325 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5326 authorities to abstain from voting on assignment of the HSDir
5327 consensus flag. Related to bug 2649.
5328 - Update to the September 6 2011 Maxmind GeoLite Country database.
5330 o Minor bugfixes (documentation and log messages):
5331 - Correct the man page to explain that HashedControlPassword and
5332 CookieAuthentication can both be set, in which case either method
5333 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5334 when we decided to allow these config options to both be set. Issue
5336 - Demote the 'replay detected' log message emitted when a hidden
5337 service receives the same Diffie-Hellman public key in two different
5338 INTRODUCE2 cells to info level. A normal Tor client can cause that
5339 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5340 fixes part of bug 2442.
5341 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5342 level. There is nothing that a hidden service's operator can do
5343 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5345 - Clarify a log message specifying the characters permitted in
5346 HiddenServiceAuthorizeClient client names. Previously, the log
5347 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5348 given the impression that every ASCII character between "+" and "_"
5349 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5352 - Provide a substitute implementation of lround() for MSVC, which
5353 apparently lacks it. Patch from Gisle Vanem.
5354 - Clean up some code issues that prevented Tor from building on older
5355 BSDs. Fixes bug 3894; reported by "grarpamp".
5356 - Search for a platform-specific version of "ar" when cross-compiling.
5357 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5360 Changes in version 0.2.3.3-alpha - 2011-09-01
5361 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
5362 security, and provides client-side support for the microdescriptor
5363 and optimistic data features introduced earlier in the 0.2.3.x
5364 series. It also includes numerous critical bugfixes in the (optional)
5365 bufferevent-based networking backend.
5367 o Major features (stream isolation):
5368 - You can now configure Tor so that streams from different
5369 applications are isolated on different circuits, to prevent an
5370 attacker who sees your streams as they leave an exit node from
5371 linking your sessions to one another. To do this, choose some way
5372 to distinguish the applications: have them connect to different
5373 SocksPorts, or have one of them use SOCKS4 while the other uses
5374 SOCKS5, or have them pass different authentication strings to the
5375 SOCKS proxy. Then, use the new SocksPort syntax to configure the
5376 degree of isolation you need. This implements Proposal 171.
5377 - There's a new syntax for specifying multiple client ports (such as
5378 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
5379 multiple *Port entries with full addr:port syntax on each.
5380 The old *ListenAddress format is still supported, but you can't
5381 mix it with the new *Port syntax.
5383 o Major features (other):
5384 - Enable microdescriptor fetching by default for clients. This allows
5385 clients to download a much smaller amount of directory information.
5386 To disable it (and go back to the old-style consensus and
5387 descriptors), set "UseMicrodescriptors 0" in your torrc file.
5388 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
5389 "PortForwarding" config option), now supports Windows.
5390 - When using an exit relay running 0.2.3.x, clients can now
5391 "optimistically" send data before the exit relay reports that
5392 the stream has opened. This saves a round trip when starting
5393 connections where the client speaks first (such as web browsing).
5394 This behavior is controlled by a consensus parameter (currently
5395 disabled). To turn it on or off manually, use the "OptimisticData"
5396 torrc option. Implements proposal 181; code by Ian Goldberg.
5398 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
5399 - When using IOCP on Windows, we need to enable Libevent windows
5401 - The IOCP backend now works even when the user has not specified
5402 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
5403 Fixes part of bug 3752.
5404 - Correctly record the bytes we've read and written when using
5405 bufferevents, so that we can include them in our bandwidth history
5406 and advertised bandwidth. Fixes bug 3803.
5407 - Apply rate-limiting only at the bottom of a chain of filtering
5408 bufferevents. This prevents us from filling up internal read
5409 buffers and violating rate-limits when filtering bufferevents
5410 are enabled. Fixes part of bug 3804.
5411 - Add high-watermarks to the output buffers for filtered
5412 bufferevents. This prevents us from filling up internal write
5413 buffers and wasting CPU cycles when filtering bufferevents are
5414 enabled. Fixes part of bug 3804.
5415 - Correctly notice when data has been written from a bufferevent
5416 without flushing it completely. Fixes bug 3805.
5417 - Fix a bug where server-side tunneled bufferevent-based directory
5418 streams would get closed prematurely. Fixes bug 3814.
5419 - Fix a use-after-free error with per-connection rate-limiting
5420 buckets. Fixes bug 3888.
5422 o Major bugfixes (also part of 0.2.2.31-rc):
5423 - If we're configured to write our ControlPorts to disk, only write
5424 them after switching UID and creating the data directory. This way,
5425 we don't fail when starting up with a nonexistent DataDirectory
5426 and a ControlPortWriteToFile setting based on that directory. Fixes
5427 bug 3747; bugfix on Tor 0.2.2.26-beta.
5430 - Added a new CONF_CHANGED event so that controllers can be notified
5431 of any configuration changes made by other controllers, or by the
5432 user. Implements ticket 1692.
5433 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
5434 leak when using bufferevents, and lets Libevent worry about how to
5435 best copy data out of a buffer.
5436 - Replace files in stats/ rather than appending to them. Now that we
5437 include statistics in extra-info descriptors, it makes no sense to
5438 keep old statistics forever. Implements ticket 2930.
5440 o Minor features (build compatibility):
5441 - Limited, experimental support for building with nmake and MSVC.
5442 - Provide a substitute implementation of lround() for MSVC, which
5443 apparently lacks it. Patch from Gisle Vanem.
5445 o Minor features (also part of 0.2.2.31-rc):
5446 - Update to the August 2 2011 Maxmind GeoLite Country database.
5448 o Minor bugfixes (on 0.2.3.x-alpha):
5449 - Fix a spurious warning when parsing SOCKS requests with
5450 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
5451 - Get rid of a harmless warning that could happen on relays running
5452 with bufferevents. The warning was caused by someone doing an http
5453 request to a relay's orport. Also don't warn for a few related
5454 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
5456 o Minor bugfixes (on 2.2.x and earlier):
5457 - Correct the man page to explain that HashedControlPassword and
5458 CookieAuthentication can both be set, in which case either method
5459 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5460 when we decided to allow these config options to both be set. Issue
5462 - The "--quiet" and "--hush" options now apply not only to Tor's
5463 behavior before logs are configured, but also to Tor's behavior in
5464 the absense of configured logs. Fixes bug 3550; bugfix on
5467 o Minor bugfixes (also part of 0.2.2.31-rc):
5468 - Write several files in text mode, on OSes that distinguish text
5469 mode from binary mode (namely, Windows). These files are:
5470 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5471 that collect those statistics; 'client_keys' and 'hostname' for
5472 hidden services that use authentication; and (in the tor-gencert
5473 utility) newly generated identity and signing keys. Previously,
5474 we wouldn't specify text mode or binary mode, leading to an
5475 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5476 the DirRecordUsageByCountry option which would have triggered
5477 the assertion failure was added), although this assertion failure
5478 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5479 - Selectively disable deprecation warnings on OS X because Lion
5480 started deprecating the shipped copy of openssl. Fixes bug 3643.
5481 - Remove an extra pair of quotation marks around the error
5482 message in control-port STATUS_GENERAL BUG events. Bugfix on
5483 0.1.2.6-alpha; fixes bug 3732.
5484 - When unable to format an address as a string, report its value
5485 as "???" rather than reusing the last formatted address. Bugfix
5488 o Code simplifications and refactoring:
5489 - Rewrite the listener-selection logic so that parsing which ports
5490 we want to listen on is now separate from binding to the ports
5494 - Building Tor with bufferevent support now requires Libevent
5495 2.0.13-stable or later. Previous versions of Libevent had bugs in
5496 SSL-related bufferevents and related issues that would make Tor
5497 work badly with bufferevents. Requiring 2.0.13-stable also allows
5498 Tor with bufferevents to take advantage of Libevent APIs
5499 introduced after 2.0.8-rc.
5502 Changes in version 0.2.2.32 - 2011-08-27
5503 The Tor 0.2.2 release series is dedicated to the memory of Andreas
5504 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
5505 a founder of the PETS community, a leader in our field, a mentor,
5506 and a friend. He left us with these words: "I had the possibility
5507 to contribute to this world that is not as it should be. I hope I
5508 could help in some areas to make the world a better place, and that
5509 I could also encourage other people to be engaged in improving the
5510 world. Please, stay engaged. This world needs you, your love, your
5511 initiative -- now I cannot be part of that anymore."
5513 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
5514 ready. More than two years in the making, this release features improved
5515 client performance and hidden service reliability, better compatibility
5516 for Android, correct behavior for bridges that listen on more than
5517 one address, more extensible and flexible directory object handling,
5518 better reporting of network statistics, improved code security, and
5519 many many other features and bugfixes.
5522 Changes in version 0.2.2.31-rc - 2011-08-17
5523 Tor 0.2.2.31-rc is the second and hopefully final release candidate
5524 for the Tor 0.2.2.x series.
5527 - Remove an extra pair of quotation marks around the error
5528 message in control-port STATUS_GENERAL BUG events. Bugfix on
5529 0.1.2.6-alpha; fixes bug 3732.
5530 - If we're configured to write our ControlPorts to disk, only write
5531 them after switching UID and creating the data directory. This way,
5532 we don't fail when starting up with a nonexistent DataDirectory
5533 and a ControlPortWriteToFile setting based on that directory. Fixes
5534 bug 3747; bugfix on Tor 0.2.2.26-beta.
5537 - Update to the August 2 2011 Maxmind GeoLite Country database.
5540 - Allow GETINFO fingerprint to return a fingerprint even when
5541 we have not yet built a router descriptor. Fixes bug 3577;
5542 bugfix on 0.2.0.1-alpha.
5543 - Write several files in text mode, on OSes that distinguish text
5544 mode from binary mode (namely, Windows). These files are:
5545 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5546 that collect those statistics; 'client_keys' and 'hostname' for
5547 hidden services that use authentication; and (in the tor-gencert
5548 utility) newly generated identity and signing keys. Previously,
5549 we wouldn't specify text mode or binary mode, leading to an
5550 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5551 the DirRecordUsageByCountry option which would have triggered
5552 the assertion failure was added), although this assertion failure
5553 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5554 - Selectively disable deprecation warnings on OS X because Lion
5555 started deprecating the shipped copy of openssl. Fixes bug 3643.
5556 - When unable to format an address as a string, report its value
5557 as "???" rather than reusing the last formatted address. Bugfix
5561 Changes in version 0.2.3.2-alpha - 2011-07-18
5562 Tor 0.2.3.2-alpha introduces two new experimental features:
5563 microdescriptors and pluggable transports. It also continues cleaning
5564 up a variety of recently introduced features.
5567 - Clients can now use microdescriptors instead of regular descriptors
5568 to build circuits. Microdescriptors are authority-generated
5569 summaries of regular descriptors' contents, designed to change
5570 very rarely (see proposal 158 for details). This feature is
5571 designed to save bandwidth, especially for clients on slow internet
5572 connections. It's off by default for now, since nearly no caches
5573 support it, but it will be on-by-default for clients in a future
5574 version. You can use the UseMicrodescriptors option to turn it on.
5575 - Tor clients using bridges can now be configured to use a separate
5576 'transport' proxy for each bridge. This approach helps to resist
5577 censorship by allowing bridges to use protocol obfuscation
5578 plugins. It implements part of proposal 180. Implements ticket 2841.
5579 - While we're trying to bootstrap, record how many TLS connections
5580 fail in each state, and report which states saw the most failures
5581 in response to any bootstrap failures. This feature may speed up
5582 diagnosis of censorship events. Implements ticket 3116.
5584 o Major bugfixes (on 0.2.3.1-alpha):
5585 - When configuring a large set of nodes in EntryNodes (as with
5586 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
5587 random subset to be guards, and choose them in random
5588 order. Fixes bug 2798.
5589 - Tor could crash when remembering a consensus in a non-used consensus
5590 flavor without having a current consensus set. Fixes bug 3361.
5591 - Comparing an unknown address to a microdescriptor's shortened exit
5592 policy would always give a "rejected" result. Fixes bug 3599.
5593 - Using microdescriptors as a client no longer prevents Tor from
5594 uploading and downloading hidden service descriptors. Fixes
5598 - Allow nameservers with IPv6 address. Resolves bug 2574.
5599 - Accept attempts to include a password authenticator in the
5600 handshake, as supported by SOCKS5. This handles SOCKS clients that
5601 don't know how to omit a password when authenticating. Resolves
5603 - When configuring a large set of nodes in EntryNodes, and there are
5604 enough of them listed as Guard so that we don't need to consider
5605 the non-guard entries, prefer the ones listed with the Guard flag.
5606 - Check for and recover from inconsistency in the microdescriptor
5607 cache. This will make it harder for us to accidentally free a
5608 microdescriptor without removing it from the appropriate data
5609 structures. Fixes issue 3135; issue noted by "wanoskarnet".
5610 - Log SSL state transitions at log level DEBUG, log domain
5611 HANDSHAKE. This can be useful for debugging censorship events.
5612 Implements ticket 3264.
5613 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
5614 implements ticket 3439.
5616 o Minor bugfixes (on 0.2.3.1-alpha):
5617 - Do not free all general-purpose regular descriptors just
5618 because microdescriptor use is enabled. Fixes bug 3113.
5619 - Correctly link libevent_openssl when --enable-static-libevent
5620 is passed to configure. Fixes bug 3118.
5621 - Bridges should not complain during their heartbeat log messages that
5622 they are unlisted in the consensus: that's more or less the point
5623 of being a bridge. Fixes bug 3183.
5624 - Report a SIGNAL event to controllers when acting on a delayed
5625 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
5626 event to the controller if we acted on a SIGNAL NEWNYM command
5627 immediately, and otherwise not report a SIGNAL event for the
5628 command at all. Fixes bug 3349.
5629 - Fix a crash when handling the SIGNAL controller command or
5630 reporting ERR-level status events with bufferevents enabled. Found
5631 by Robert Ransom. Fixes bug 3367.
5632 - Always ship the tor-fw-helper manpage in our release tarballs.
5633 Fixes bug 3389. Reported by Stephen Walker.
5634 - Fix a class of double-mark-for-close bugs when bufferevents
5635 are enabled. Fixes bug 3403.
5636 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
5637 - Add SIGNAL to the list returned by the 'GETINFO events/names'
5638 control-port command. Fixes part of bug 3465.
5639 - Prevent using negative indices during unit test runs when read_all()
5640 fails. Spotted by coverity.
5641 - Fix a rare memory leak when checking the nodelist without it being
5642 present. Found by coverity.
5643 - Only try to download a microdescriptor-flavored consensus from
5644 a directory cache that provides them.
5646 o Minor bugfixes (on 0.2.2.x and earlier):
5647 - Assert that hidden-service-related operations are not performed
5648 using single-hop circuits. Previously, Tor would assert that
5649 client-side streams are not attached to single-hop circuits,
5650 but not that other sensitive operations on the client and service
5651 side are not performed using single-hop circuits. Fixes bug 3332;
5653 - Don't publish a new relay descriptor when we reload our onion key,
5654 unless the onion key has actually changed. Fixes bug 3263 and
5655 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
5656 - Allow GETINFO fingerprint to return a fingerprint even when
5657 we have not yet built a router descriptor. Fixes bug 3577;
5658 bugfix on 0.2.0.1-alpha.
5659 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
5660 on 0.2.2.4-alpha; fixes bug 3427.
5662 o Code simplification and refactoring:
5663 - Use tor_sscanf() in place of scanf() in more places through the
5664 code. This makes us a little more locale-independent, and
5665 should help shut up code-analysis tools that can't tell
5666 a safe sscanf string from a dangerous one.
5667 - Use tt_assert(), not tor_assert(), for checking for test failures.
5668 This makes the unit tests more able to go on in the event that
5670 - Split connection_about_to_close() into separate functions for each
5674 - On Windows, we now define the _WIN32_WINNT macros only if they
5675 are not already defined. This lets the person building Tor decide,
5676 if they want, to require a later version of Windows.
5679 Changes in version 0.2.2.30-rc - 2011-07-07
5680 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
5681 series. It fixes a few smaller bugs, but generally appears stable.
5682 Please test it and let us know whether it is!
5685 - Send a SUCCEEDED stream event to the controller when a reverse
5686 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
5687 discovered by katmagic.
5688 - Always NUL-terminate the sun_path field of a sockaddr_un before
5689 passing it to the kernel. (Not a security issue: kernels are
5690 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5691 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5692 - Don't stack-allocate the list of supplementary GIDs when we're
5693 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5694 could take up to 256K, which is way too much stack. Found by
5695 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5696 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
5697 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
5698 fixes part of bug 3465.
5699 - Fix a memory leak when receiving a descriptor for a hidden
5700 service we didn't ask for. Found by Coverity; CID #30. Bugfix
5704 - Update to the July 1 2011 Maxmind GeoLite Country database.
5707 Changes in version 0.2.2.29-beta - 2011-06-20
5708 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
5709 have bridge lines in their torrc but don't want to use them; gets
5710 us closer to having the control socket feature working on Debian;
5711 and fixes a variety of smaller bugs.
5714 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
5715 When we changed the default behavior to "use bridges if any
5716 are listed in the torrc", we surprised users who had bridges
5717 in their torrc files but who didn't actually want to use them.
5718 Partial resolution for bug 3354.
5721 - Don't attach new streams to old rendezvous circuits after SIGNAL
5722 NEWNYM. Previously, we would keep using an existing rendezvous
5723 circuit if it remained open (i.e. if it were kept open by a
5724 long-lived stream, or if a new stream were attached to it before
5725 Tor could notice that it was old and no longer in use). Bugfix on
5726 0.1.1.15-rc; fixes bug 3375.
5729 - Fix a bug when using ControlSocketsGroupWritable with User. The
5730 directory's group would be checked against the current group, not
5731 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
5732 bugfix on 0.2.2.26-beta.
5733 - Make connection_printf_to_buf()'s behaviour sane. Its callers
5734 expect it to emit a CRLF iff the format string ends with CRLF;
5735 it actually emitted a CRLF iff (a) the format string ended with
5736 CRLF or (b) the resulting string was over 1023 characters long or
5737 (c) the format string did not end with CRLF *and* the resulting
5738 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
5739 fixes part of bug 3407.
5740 - Make send_control_event_impl()'s behaviour sane. Its callers
5741 expect it to always emit a CRLF at the end of the string; it
5742 might have emitted extra control characters as well. Bugfix on
5743 0.1.1.9-alpha; fixes another part of bug 3407.
5744 - Make crypto_rand_int() check the value of its input correctly.
5745 Previously, it accepted values up to UINT_MAX, but could return a
5746 negative number if given a value above INT_MAX+1. Found by George
5747 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
5748 - Avoid a segfault when reading a malformed circuit build state
5749 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
5751 - When asked about a DNS record type we don't support via a
5752 client DNSPort, reply with NOTIMPL rather than an empty
5753 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
5754 - Fix a rare memory leak during stats writing. Found by coverity.
5757 - Update to the June 1 2011 Maxmind GeoLite Country database.
5759 o Code simplifications and refactoring:
5760 - Remove some dead code as indicated by coverity.
5761 - Remove a few dead assignments during router parsing. Found by
5763 - Add some forgotten return value checks during unit tests. Found
5765 - Don't use 1-bit wide signed bit fields. Found by coverity.
5768 Changes in version 0.2.2.28-beta - 2011-06-04
5769 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
5770 fixed a big bug in whether relays stay in the consensus consistently,
5771 we moved closer to handling bridges and hidden services correctly,
5772 and we started the process of better handling the dreaded "my Vidalia
5773 died, and now my Tor demands a password when I try to reconnect to it"
5777 - Don't decide to make a new descriptor when receiving a HUP signal.
5778 This bug has caused a lot of 0.2.2.x relays to disappear from the
5779 consensus periodically. Fixes the most common case of triggering
5780 bug 1810; bugfix on 0.2.2.7-alpha.
5781 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
5782 - Don't try to build descriptors if "ORPort auto" is set and we
5783 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
5785 - Resolve a crash that occurred when setting BridgeRelay to 1 with
5786 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
5787 - Apply circuit timeouts to opened hidden-service-related circuits
5788 based on the correct start time. Previously, we would apply the
5789 circuit build timeout based on time since the circuit's creation;
5790 it was supposed to be applied based on time since the circuit
5791 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
5792 - Use the same circuit timeout for client-side introduction
5793 circuits as for other four-hop circuits, rather than the timeout
5794 for single-hop directory-fetch circuits; the shorter timeout may
5795 have been appropriate with the static circuit build timeout in
5796 0.2.1.x and earlier, but caused many hidden service access attempts
5797 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
5798 on 0.2.2.2-alpha; fixes another part of bug 1297.
5799 - In ticket 2511 we fixed a case where you could use an unconfigured
5800 bridge if you had configured it as a bridge the last time you ran
5801 Tor. Now fix another edge case: if you had configured it as a bridge
5802 but then switched to a different bridge via the controller, you
5803 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
5807 - Add an __OwningControllerProcess configuration option and a
5808 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
5809 that when it exits, Tor will shut down. Implements feature 3049.
5810 - If "UseBridges 1" is set and no bridges are configured, Tor will
5811 now refuse to build any circuits until some bridges are set.
5812 If "UseBridges auto" is set, Tor will use bridges if they are
5813 configured and we are not running as a server, but otherwise will
5814 make circuits as usual. The new default is "auto". Patch by anonym,
5815 so the Tails LiveCD can stop automatically revealing you as a Tor
5819 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5820 - Remove a trailing asterisk from "exit-policy/default" in the
5821 output of the control port command "GETINFO info/names". Bugfix
5823 - Use a wide type to hold sockets when built for 64-bit Windows builds.
5825 - Warn when the user configures two HiddenServiceDir lines that point
5826 to the same directory. Bugfix on 0.0.6 (the version introducing
5827 HiddenServiceDir); fixes bug 3289.
5828 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
5829 part of bug 2748; bugfix on 0.2.0.10-alpha.
5830 - Log malformed requests for rendezvous descriptors as protocol
5831 warnings, not warnings. Also, use a more informative log message
5832 in case someone sees it at log level warning without prior
5833 info-level messages. Fixes the other part of bug 2748; bugfix
5835 - Clear the table recording the time of the last request for each
5836 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
5837 Previously, we would clear our HS descriptor cache on SIGNAL
5838 NEWNYM, but if we had previously retrieved a descriptor (or tried
5839 to) from every directory responsible for it, we would refuse to
5840 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
5842 - Fix a log message that said "bits" while displaying a value in
5843 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
5845 - When checking for 1024-bit keys, check for 1024 bits, not 128
5846 bytes. This allows Tor to correctly discard keys of length 1017
5847 through 1023. Bugfix on 0.0.9pre5.
5850 - Relays now log the reason for publishing a new relay descriptor,
5851 so we have a better chance of hunting down instances of bug 1810.
5852 Resolves ticket 3252.
5853 - Revise most log messages that refer to nodes by nickname to
5854 instead use the "$key=nickname at address" format. This should be
5855 more useful, especially since nicknames are less and less likely
5856 to be unique. Resolves ticket 3045.
5857 - Log (at info level) when purging pieces of hidden-service-client
5858 state because of SIGNAL NEWNYM.
5861 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5862 anything since 0.2.1.16-rc.
5865 Changes in version 0.2.2.27-beta - 2011-05-18
5866 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
5867 release, and also adds a few more general bugfixes.
5870 - Fix a crash bug when changing bridges in a running Tor process.
5871 Fixes bug 3213; bugfix on 0.2.2.26-beta.
5872 - When the controller configures a new bridge, don't wait 10 to 60
5873 seconds before trying to fetch its descriptor. Bugfix on
5874 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
5877 - Require that onion keys have exponent 65537 in microdescriptors too.
5878 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
5879 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
5880 Changed the limit to 512 characters by removing base64 newlines.
5881 Fixes bug 2752. Fix by Michael Yakubovich.
5882 - When a client starts or stops using bridges, never use a circuit
5883 that was built before the configuration change. This behavior could
5884 put at risk a user who uses bridges to ensure that her traffic
5885 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
5889 Changes in version 0.2.2.26-beta - 2011-05-17
5890 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
5891 also introduces a new "socksport auto" approach that should make it
5892 easier to run multiple Tors on the same system, and does a lot of
5893 cleanup to get us closer to a release candidate.
5895 o Security/privacy fixes:
5896 - Replace all potentially sensitive memory comparison operations
5897 with versions whose runtime does not depend on the data being
5898 compared. This will help resist a class of attacks where an
5899 adversary can use variations in timing information to learn
5900 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5901 implementation by Robert Ransom based partially on code by DJB.)
5902 - When receiving a hidden service descriptor, check that it is for
5903 the hidden service we wanted. Previously, Tor would store any
5904 hidden service descriptors that a directory gave it, whether it
5905 wanted them or not. This wouldn't have let an attacker impersonate
5906 a hidden service, but it did let directories pre-seed a client
5907 with descriptors that it didn't want. Bugfix on 0.0.6.
5908 - On SIGHUP, do not clear out all TrackHostExits mappings, client
5909 DNS cache entries, and virtual address mappings: that's what
5910 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
5913 - The options SocksPort, ControlPort, and so on now all accept a
5914 value "auto" that opens a socket on an OS-selected port. A
5915 new ControlPortWriteToFile option tells Tor to write its
5916 actual control port or ports to a chosen file. If the option
5917 ControlPortFileGroupReadable is set, the file is created as
5918 group-readable. Now users can run two Tor clients on the same
5919 system without needing to manually mess with parameters. Resolves
5920 part of ticket 3076.
5921 - Set SO_REUSEADDR on all sockets, not just listeners. This should
5922 help busy exit nodes avoid running out of useable ports just
5923 because all the ports have been used in the near past. Resolves
5927 - New "GETINFO net/listeners/(type)" controller command to return
5928 a list of addresses and ports that are bound for listeners for a
5929 given connection type. This is useful when the user has configured
5930 "SocksPort auto" and the controller needs to know which port got
5931 chosen. Resolves another part of ticket 3076.
5932 - Add a new ControlSocketsGroupWritable configuration option: when
5933 it is turned on, ControlSockets are group-writeable by the default
5934 group of the current user. Patch by Jérémy Bobbio; implements
5936 - Tor now refuses to create a ControlSocket in a directory that is
5937 world-readable (or group-readable if ControlSocketsGroupWritable
5938 is 0). This is necessary because some operating systems do not
5939 enforce permissions on an AF_UNIX sockets. Permissions on the
5940 directory holding the socket, however, seems to work everywhere.
5941 - Rate-limit a warning about failures to download v2 networkstatus
5942 documents. Resolves part of bug 1352.
5943 - Backport code from 0.2.3.x that allows directory authorities to
5944 clean their microdescriptor caches. Needed to resolve bug 2230.
5945 - When an HTTPS proxy reports "403 Forbidden", we now explain
5946 what it means rather than calling it an unexpected status code.
5947 Closes bug 2503. Patch from Michael Yakubovich.
5948 - Update to the May 1 2011 Maxmind GeoLite Country database.
5951 - Authorities now clean their microdesc cache periodically and when
5952 reading from disk initially, not only when adding new descriptors.
5953 This prevents a bug where we could lose microdescriptors. Bugfix
5954 on 0.2.2.6-alpha. Fixes bug 2230.
5955 - Do not crash when our configuration file becomes unreadable, for
5956 example due to a permissions change, between when we start up
5957 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5959 - Avoid a bug that would keep us from replacing a microdescriptor
5960 cache on Windows. (We would try to replace the file while still
5961 holding it open. That's fine on Unix, but Windows doesn't let us
5962 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
5963 - Add missing explanations for the authority-related torrc options
5964 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
5965 man page. Resolves issue 2379.
5966 - As an authority, do not upload our own vote or signature set to
5967 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
5968 it would get flagged as a duplicate. Resolves bug 3026.
5969 - Accept hidden service descriptors if we think we might be a hidden
5970 service directory, regardless of what our consensus says. This
5971 helps robustness, since clients and hidden services can sometimes
5972 have a more up-to-date view of the network consensus than we do,
5973 and if they think that the directory authorities list us a HSDir,
5974 we might actually be one. Related to bug 2732; bugfix on
5976 - When a controller changes TrackHostExits, remove mappings for
5977 hosts that should no longer have their exits tracked. Bugfix on
5979 - When a controller changes VirtualAddrNetwork, remove any mappings
5980 for hosts that were automapped to the old network. Bugfix on
5982 - When a controller changes one of the AutomapHosts* options, remove
5983 any mappings for hosts that should no longer be automapped. Bugfix
5985 - Do not reset the bridge descriptor download status every time we
5986 re-parse our configuration or get a configuration change. Fixes
5987 bug 3019; bugfix on 0.2.0.3-alpha.
5989 o Minor bugfixes (code cleanup):
5990 - When loading the microdesc journal, remember its current size.
5991 In 0.2.2, this helps prevent the microdesc journal from growing
5992 without limit on authorities (who are the only ones to use it in
5993 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5994 Fix posted by "cypherpunks."
5995 - The microdesc journal is supposed to get rebuilt only if it is
5996 at least _half_ the length of the store, not _twice_ the length
5997 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5998 - Fix a potential null-pointer dereference while computing a
5999 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
6001 - Avoid a possible null-pointer dereference when rebuilding the mdesc
6002 cache without actually having any descriptors to cache. Bugfix on
6003 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
6004 - If we fail to compute the identity digest of a v3 legacy keypair,
6005 warn, and don't use a buffer-full of junk instead. Bugfix on
6006 0.2.1.1-alpha; fixes bug 3106.
6007 - Resolve an untriggerable issue in smartlist_string_num_isin(),
6008 where if the function had ever in the future been used to check
6009 for the presence of a too-large number, it would have given an
6010 incorrect result. (Fortunately, we only used it for 16-bit
6011 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
6012 - Require that introduction point keys and onion handshake keys
6013 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6017 - Caches no longer download and serve v2 networkstatus documents
6018 unless FetchV2Networkstatus flag is set: these documents haven't
6019 haven't been used by clients or relays since 0.2.0.x. Resolves
6023 Changes in version 0.2.3.1-alpha - 2011-05-05
6024 Tor 0.2.3.1-alpha adds some new experimental features, including support
6025 for an improved network IO backend, IOCP networking on Windows,
6026 microdescriptor caching, "fast-start" support for streams, and automatic
6027 home router configuration. There are also numerous internal improvements
6028 to try to make the code easier for developers to work with.
6030 This is the first alpha release in a new series, so expect there to be
6031 bugs. Users who would rather test out a more stable branch should
6032 stay with 0.2.2.x for now.
6035 - Tor can now optionally build with the "bufferevents" buffered IO
6036 backend provided by Libevent 2. To use this feature, make sure you
6037 have the latest possible version of Libevent, and pass the
6038 --enable-bufferevents flag to configure when building Tor from
6039 source. This feature will make our networking code more flexible,
6040 let us stack layers on each other, and let us use more efficient
6041 zero-copy transports where available.
6042 - As an experimental feature, Tor can use IOCP for networking on Windows.
6043 Once this code is tuned and optimized, it promises much better
6044 performance than the select-based backend we've used in the past. To
6045 try this feature, you must build Tor with Libevent 2, configure Tor
6046 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
6047 your torrc. There are known bugs here: only try this if you can help
6048 debug it as it breaks.
6049 - The EntryNodes option can now include country codes like {de} or IP
6050 addresses or network masks. Previously we had disallowed these options
6051 because we didn't have an efficient way to keep the list up to
6052 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
6053 - Exit nodes now accept and queue data on not-yet-connected streams.
6054 Previously, the client wasn't allowed to send data until the stream was
6055 connected, which slowed down all connections. This change will enable
6056 clients to perform a "fast-start" on streams and send data without
6057 having to wait for a confirmation that the stream has opened. (Patch
6058 from Ian Goldberg; implements the server side of Proposal 174.)
6059 - Tor now has initial support for automatic port mapping on the many
6060 home routers that support NAT-PMP or UPnP. (Not yet supported on
6061 Windows). To build the support code, you'll need to have libnatpnp
6062 library and/or the libminiupnpc library, and you'll need to enable the
6063 feature specifically by passing "--enable-upnp" and/or
6064 "--enable-natpnp" to configure. To turn it on, use the new
6065 PortForwarding option.
6066 - Caches now download, cache, and serve multiple "flavors" of the
6067 consensus, including a flavor that describes microdescriptors.
6068 - Caches now download, cache, and serve microdescriptors -- small
6069 summaries of router descriptors that are authenticated by all of the
6070 directory authorities. Once enough caches are running this code,
6071 clients will be able to save significant amounts of directory bandwidth
6072 by downloading microdescriptors instead of router descriptors.
6075 - Make logging resolution configurable with a new LogTimeGranularity
6076 option, and change the default from 1 millisecond to 1 second.
6077 Implements enhancement 1668.
6078 - We log which torrc file we're using on startup. Implements ticket
6080 - Ordinarily, Tor does not count traffic from private addresses (like
6081 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6082 There is now a new option, CountPrivateBandwidth, to disable this
6083 behavior. Patch from Daniel Cagara.
6084 - New --enable-static-tor configure option for building Tor as
6085 statically as possible. Idea, general hackery and thoughts from
6086 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
6088 - If you set the NumCPUs option to 0, Tor will now try to detect how
6089 many CPUs you have. This is the new default behavior.
6090 - Turn on directory request statistics by default and include them in
6091 extra-info descriptors. Don't break if we have no GeoIP database.
6092 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6093 bidirectional use of connections to disk every 24 hours.
6094 - Add a GeoIP file digest to the extra-info descriptor. Implements
6096 - The NodeFamily option -- which let you declare that you want to
6097 consider nodes to be part of a family whether they list themselves
6098 that way or not -- now allows IP address ranges and country codes.
6099 - Add a new 'Heartbeat' log message type to periodically log a message
6100 describing Tor's status at level Notice. This feature is meant for
6101 operators who log at notice, and want to make sure that their Tor
6102 server is still working. Implementation by George Kadianakis.
6104 o Minor bugfixes (on 0.2.2.25-alpha):
6105 - When loading the microdesc journal, remember its current size.
6106 In 0.2.2, this helps prevent the microdesc journal from growing
6107 without limit on authorities (who are the only ones to use it in
6108 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6109 Fix posted by "cypherpunks."
6110 - The microdesc journal is supposed to get rebuilt only if it is
6111 at least _half_ the length of the store, not _twice_ the length
6112 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6113 - If as an authority we fail to compute the identity digest of a v3
6114 legacy keypair, warn, and don't use a buffer-full of junk instead.
6115 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
6116 - Authorities now clean their microdesc cache periodically and when
6117 reading from disk initially, not only when adding new descriptors.
6118 This prevents a bug where we could lose microdescriptors. Bugfix
6121 o Minor features (controller):
6122 - Add a new SIGNAL event to the controller interface so that
6123 controllers can be notified when Tor handles a signal. Resolves
6124 issue 1955. Patch by John Brooks.
6125 - Add a new GETINFO option to get total bytes read and written. Patch
6126 from pipe, revised by atagar. Resolves ticket 2345.
6127 - Implement some GETINFO controller fields to provide information about
6128 the Tor process's pid, euid, username, and resource limits.
6131 - Our build system requires automake 1.6 or later to create the
6132 Makefile.in files. Previously, you could have used 1.4.
6133 This only affects developers and people building Tor from git;
6134 people who build Tor from the source distribution without changing
6135 the Makefile.am files should be fine.
6136 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
6137 so on. This is more robust against some of the failure modes
6138 associated with running the autotools pieces on their own.
6140 o Minor packaging issues:
6141 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
6142 already created. Patch from Andreas Stieger. Fixes bug 2573.
6144 o Code simplifications and refactoring:
6145 - A major revision to our internal node-selecting and listing logic.
6146 Tor already had at least two major ways to look at the question of
6147 "which Tor servers do we know about": a list of router descriptors,
6148 and a list of entries in the current consensus. With
6149 microdescriptors, we're adding a third. Having so many systems
6150 without an abstraction layer over them was hurting the codebase.
6151 Now, we have a new "node_t" abstraction that presents a consistent
6152 interface to a client's view of a Tor node, and holds (nearly) all
6153 of the mutable state formerly in routerinfo_t and routerstatus_t.
6154 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
6155 no longer link against Libevent: they never used it, but
6156 our library structure used to force them to link it.
6159 - Remove some old code to work around even older versions of Tor that
6160 used forked processes to handle DNS requests. Such versions of Tor
6161 are no longer in use as servers.
6163 o Documentation fixes:
6164 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
6165 - Add missing documentation for the authority-related torrc options
6166 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
6170 Changes in version 0.2.2.25-alpha - 2011-04-29
6171 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
6172 robust, routers no longer overreport their bandwidth, Win7 should crash
6173 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
6174 now prevents hidden service-related activity from being linkable. It
6175 provides more information to Vidalia so you can see if your bridge is
6176 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
6177 StrictNodes configuration options to make them more reliable, more
6178 understandable, and more regularly applied. If you use those options,
6179 please see the revised documentation for them in the manual page.
6182 - Relays were publishing grossly inflated bandwidth values because
6183 they were writing their state files wrong--now they write the
6184 correct value. Also, resume reading bandwidth history from the
6185 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
6186 - Improve hidden service robustness: When we find that we have
6187 extended a hidden service's introduction circuit to a relay not
6188 listed as an introduction point in the HS descriptor we currently
6189 have, retry with an introduction point from the current
6190 descriptor. Previously we would just give up. Fixes bugs 1024 and
6191 1930; bugfix on 0.2.0.10-alpha.
6192 - Clients now stop trying to use an exit node associated with a given
6193 destination by TrackHostExits if they fail to reach that exit node.
6194 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
6195 - Fix crash bug on platforms where gmtime and localtime can return
6196 NULL. Windows 7 users were running into this one. Fixes part of bug
6197 2077. Bugfix on all versions of Tor. Found by boboper.
6199 o Security and stability fixes:
6200 - Don't double-free a parsable, but invalid, microdescriptor, even if
6201 it is followed in the blob we're parsing by an unparsable
6202 microdescriptor. Fixes an issue reported in a comment on bug 2954.
6203 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
6204 - If the Nickname configuration option isn't given, Tor would pick a
6205 nickname based on the local hostname as the nickname for a relay.
6206 Because nicknames are not very important in today's Tor and the
6207 "Unnamed" nickname has been implemented, this is now problematic
6208 behavior: It leaks information about the hostname without being
6209 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
6210 introduced the Unnamed nickname. Reported by tagnaq.
6211 - Fix an uncommon assertion failure when running with DNSPort under
6212 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6213 - Avoid linkability based on cached hidden service descriptors: forget
6214 all hidden service descriptors cached as a client when processing a
6215 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6218 - Export GeoIP information on bridge usage to controllers even if we
6219 have not yet been running for 24 hours. Now Vidalia bridge operators
6220 can get more accurate and immediate feedback about their
6221 contributions to the network.
6223 o Major features and bugfixes (node selection):
6224 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
6225 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
6226 options. Previously, we had been ambiguous in describing what
6227 counted as an "exit" node, and what operations exactly "StrictNodes
6228 0" would permit. This created confusion when people saw nodes built
6229 through unexpected circuits, and made it hard to tell real bugs from
6230 surprises. Now the intended behavior is:
6231 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
6232 a node that delivers user traffic outside the Tor network.
6233 . "Entry", in the context of EntryNodes, means a node used as the
6234 first hop of a multihop circuit. It doesn't include direct
6235 connections to directory servers.
6236 . "ExcludeNodes" applies to all nodes.
6237 . "StrictNodes" changes the behavior of ExcludeNodes only. When
6238 StrictNodes is set, Tor should avoid all nodes listed in
6239 ExcludeNodes, even when it will make user requests fail. When
6240 StrictNodes is *not* set, then Tor should follow ExcludeNodes
6241 whenever it can, except when it must use an excluded node to
6242 perform self-tests, connect to a hidden service, provide a
6243 hidden service, fulfill a .exit request, upload directory
6244 information, or fetch directory information.
6245 Collectively, the changes to implement the behavior fix bug 1090.
6246 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
6247 a node is listed in both, it's treated as excluded.
6248 - ExcludeNodes now applies to directory nodes -- as a preference if
6249 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
6250 Don't exclude all the directory authorities and set StrictNodes to 1
6251 unless you really want your Tor to break.
6252 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
6253 - ExcludeExitNodes now overrides .exit requests.
6254 - We don't use bridges listed in ExcludeNodes.
6255 - When StrictNodes is 1:
6256 . We now apply ExcludeNodes to hidden service introduction points
6257 and to rendezvous points selected by hidden service users. This
6258 can make your hidden service less reliable: use it with caution!
6259 . If we have used ExcludeNodes on ourself, do not try relay
6260 reachability self-tests.
6261 . If we have excluded all the directory authorities, we will not
6262 even try to upload our descriptor if we're a relay.
6263 . Do not honor .exit requests to an excluded node.
6264 - Remove a misfeature that caused us to ignore the Fast/Stable flags
6265 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
6266 - When the set of permitted nodes changes, we now remove any mappings
6267 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
6269 - We never cannibalize a circuit that had excluded nodes on it, even
6270 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
6271 - Revert a change where we would be laxer about attaching streams to
6272 circuits than when building the circuits. This was meant to prevent
6273 a set of bugs where streams were never attachable, but our improved
6274 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
6275 - Keep track of how many times we launch a new circuit to handle a
6276 given stream. Too many launches could indicate an inconsistency
6277 between our "launch a circuit to handle this stream" logic and our
6278 "attach this stream to one of the available circuits" logic.
6279 - Improve log messages related to excluded nodes.
6282 - Fix a spurious warning when moving from a short month to a long
6283 month on relays with month-based BandwidthAccounting. Bugfix on
6284 0.2.2.17-alpha; fixes bug 3020.
6285 - When a client finds that an origin circuit has run out of 16-bit
6286 stream IDs, we now mark it as unusable for new streams. Previously,
6287 we would try to close the entire circuit. Bugfix on 0.0.6.
6288 - Add a forgotten cast that caused a compile warning on OS X 10.6.
6289 Bugfix on 0.2.2.24-alpha.
6290 - Be more careful about reporting the correct error from a failed
6291 connect() system call. Under some circumstances, it was possible to
6292 look at an incorrect value for errno when sending the end reason.
6293 Bugfix on 0.1.0.1-rc.
6294 - Correctly handle an "impossible" overflow cases in connection byte
6295 counting, where we write or read more than 4GB on an edge connection
6296 in a single second. Bugfix on 0.1.2.8-beta.
6297 - Correct the warning displayed when a rendezvous descriptor exceeds
6298 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6300 - Clients and hidden services now use HSDir-flagged relays for hidden
6301 service descriptor downloads and uploads even if the relays have no
6302 DirPort set and the client has disabled TunnelDirConns. This will
6303 eventually allow us to give the HSDir flag to relays with no
6304 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
6305 - Downgrade "no current certificates known for authority" message from
6306 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6307 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
6308 2917. Bugfix on 0.1.1.1-alpha.
6309 - Only limit the lengths of single HS descriptors, even when multiple
6310 HS descriptors are published to an HSDir relay in a single POST
6311 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
6312 - Write the current time into the LastWritten line in our state file,
6313 rather than the time from the previous write attempt. Also, stop
6314 trying to use a time of -1 in our log statements. Fixes bug 3039;
6315 bugfix on 0.2.2.14-alpha.
6316 - Be more consistent in our treatment of file system paths. "~" should
6317 get expanded to the user's home directory in the Log config option.
6318 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6319 feature for the -f and --DataDirectory options.
6322 - Make sure every relay writes a state file at least every 12 hours.
6323 Previously, a relay could go for weeks without writing its state
6324 file, and on a crash could lose its bandwidth history, capacity
6325 estimates, client country statistics, and so on. Addresses bug 3012.
6326 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
6327 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
6328 clients are already deprecated because of security bugs.
6329 - Don't allow v0 hidden service authorities to act as clients.
6330 Required by fix for bug 3000.
6331 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
6332 by fix for bug 3000.
6333 - Ensure that no empty [dirreq-](read|write)-history lines are added
6334 to an extrainfo document. Implements ticket 2497.
6336 o Code simplification and refactoring:
6337 - Remove workaround code to handle directory responses from servers
6338 that had bug 539 (they would send HTTP status 503 responses _and_
6339 send a body too). Since only server versions before
6340 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
6341 keep the workaround in place.
6342 - Remove the old 'fuzzy time' logic. It was supposed to be used for
6343 handling calculations where we have a known amount of clock skew and
6344 an allowed amount of unknown skew. But we only used it in three
6345 places, and we never adjusted the known/unknown skew values. This is
6346 still something we might want to do someday, but if we do, we'll
6347 want to do it differently.
6348 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6349 None of the cases where we did this before were wrong, but by making
6350 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6351 - Use GetTempDir to find the proper temporary directory location on
6352 Windows when generating temporary files for the unit tests. Patch by
6356 Changes in version 0.2.2.24-alpha - 2011-04-08
6357 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
6358 prevented Tor clients from effectively using "multihomed" bridges,
6359 that is, bridges that listen on multiple ports or IP addresses so users
6360 can continue to use some of their addresses even if others get blocked.
6363 - Fix a bug where bridge users who configure the non-canonical
6364 address of a bridge automatically switch to its canonical
6365 address. If a bridge listens at more than one address, it should be
6366 able to advertise those addresses independently and any non-blocked
6367 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
6369 - If you configured Tor to use bridge A, and then quit and
6370 configured Tor to use bridge B instead, it would happily continue
6371 to use bridge A if it's still reachable. While this behavior is
6372 a feature if your goal is connectivity, in some scenarios it's a
6373 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
6374 - Directory authorities now use data collected from their own
6375 uptime observations when choosing whether to assign the HSDir flag
6376 to relays, instead of trusting the uptime value the relay reports in
6377 its descriptor. This change helps prevent an attack where a small
6378 set of nodes with frequently-changing identity keys can blackhole
6379 a hidden service. (Only authorities need upgrade; others will be
6380 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6383 - When we restart our relay, we might get a successful connection
6384 from the outside before we've started our reachability tests,
6385 triggering a warning: "ORPort found reachable, but I have no
6386 routerinfo yet. Failing to inform controller of success." This
6387 bug was harmless unless Tor is running under a controller
6388 like Vidalia, in which case the controller would never get a
6389 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6391 - Make directory authorities more accurate at recording when
6392 relays that have failed several reachability tests became
6393 unreachable, so we can provide more accuracy at assigning Stable,
6394 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6395 - Fix an issue that prevented static linking of libevent on
6396 some platforms (notably Linux). Fixes bug 2698; bugfix on
6397 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
6398 the --with-static-libevent configure option).
6399 - We now ask the other side of a stream (the client or the exit)
6400 for more data on that stream when the amount of queued data on
6401 that stream dips low enough. Previously, we wouldn't ask the
6402 other side for more data until either it sent us more data (which
6403 it wasn't supposed to do if it had exhausted its window!) or we
6404 had completely flushed all our queued data. This flow control fix
6405 should improve throughput. Fixes bug 2756; bugfix on the earliest
6406 released versions of Tor (svn commit r152).
6407 - Avoid a double-mark-for-free warning when failing to attach a
6408 transparent proxy connection. (We thought we had fixed this in
6409 0.2.2.23-alpha, but it turns out our fix was checking the wrong
6410 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
6411 bug) and 0.2.2.23-alpha (the incorrect fix).
6412 - When warning about missing zlib development packages during compile,
6413 give the correct package names. Bugfix on 0.2.0.1-alpha.
6416 - Directory authorities now log the source of a rejected POSTed v3
6418 - Make compilation with clang possible when using
6419 --enable-gcc-warnings by removing two warning options that clang
6420 hasn't implemented yet and by fixing a few warnings. Implements
6422 - When expiring circuits, use microsecond timers rather than
6423 one-second timers. This can avoid an unpleasant situation where a
6424 circuit is launched near the end of one second and expired right
6425 near the beginning of the next, and prevent fluctuations in circuit
6427 - Use computed circuit-build timeouts to decide when to launch
6428 parallel introduction circuits for hidden services. (Previously,
6429 we would retry after 15 seconds.)
6430 - Update to the April 1 2011 Maxmind GeoLite Country database.
6433 - Create the /var/run/tor directory on startup on OpenSUSE if it is
6434 not already created. Patch from Andreas Stieger. Fixes bug 2573.
6436 o Documentation changes:
6437 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
6438 - Resolve all doxygen warnings except those for missing documentation.
6440 - Add doxygen documentation for more functions, fields, and types.
6443 Changes in version 0.2.2.23-alpha - 2011-03-08
6444 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
6445 they restart they don't lose their bandwidth capacity estimate. This
6446 release also fixes a diverse set of user-facing bugs, ranging from
6447 relays overrunning their rate limiting to clients falsely warning about
6448 clock skew to bridge descriptor leaks by our bridge directory authority.
6451 - Stop sending a CLOCK_SKEW controller status event whenever
6452 we fetch directory information from a relay that has a wrong clock.
6453 Instead, only inform the controller when it's a trusted authority
6454 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6455 the rest of bug 1074.
6456 - Fix an assert in parsing router descriptors containing IPv6
6457 addresses. This one took down the directory authorities when
6458 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6459 - Make the bridge directory authority refuse to answer directory
6460 requests for "all" descriptors. It used to include bridge
6461 descriptors in its answer, which was a major information leak.
6462 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6463 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6464 Tor would ignore their RelayBandwidthBurst setting,
6465 potentially using more bandwidth than expected. Bugfix on
6466 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6467 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6468 hidserv" in her torrc. The 'hidserv' argument never controlled
6469 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6472 - Relays now save observed peak bandwidth throughput rates to their
6473 state file (along with total usage, which was already saved)
6474 so that they can determine their correct estimated bandwidth on
6475 restart. Resolves bug 1863, where Tor relays would reset their
6476 estimated bandwidth to 0 after restarting.
6477 - Directory authorities now take changes in router IP address and
6478 ORPort into account when determining router stability. Previously,
6479 if a router changed its IP or ORPort, the authorities would not
6480 treat it as having any downtime for the purposes of stability
6481 calculation, whereas clients would experience downtime since the
6482 change could take a while to propagate to them. Resolves issue 1035.
6483 - Enable Address Space Layout Randomization (ASLR) and Data Execution
6484 Prevention (DEP) by default on Windows to make it harder for
6485 attackers to exploit vulnerabilities. Patch from John Brooks.
6487 o Minor bugfixes (on 0.2.1.x and earlier):
6488 - Fix a rare crash bug that could occur when a client was configured
6489 with a large number of bridges. Fixes bug 2629; bugfix on
6490 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6491 - Avoid a double mark-for-free warning when failing to attach a
6492 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
6494 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
6495 found by "cypherpunks". This bug was introduced before the first
6496 Tor release, in svn commit r110.
6497 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
6498 don't mention them in the manpage. Fixes bug 2450; issue
6499 spotted by keb and G-Lo.
6500 - Fix a bug in bandwidth history state parsing that could have been
6501 triggered if a future version of Tor ever changed the timing
6502 granularity at which bandwidth history is measured. Bugfix on
6504 - When a relay decides that its DNS is too broken for it to serve
6505 as an exit server, it advertised itself as a non-exit, but
6506 continued to act as an exit. This could create accidental
6507 partitioning opportunities for users. Instead, if a relay is
6508 going to advertise reject *:* as its exit policy, it should
6509 really act with exit policy "reject *:*". Fixes bug 2366.
6510 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
6511 - In the special case where you configure a public exit relay as your
6512 bridge, Tor would be willing to use that exit relay as the last
6513 hop in your circuit as well. Now we fail that circuit instead.
6514 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
6515 - Fix a bug with our locking implementation on Windows that couldn't
6516 correctly detect when a file was already locked. Fixes bug 2504,
6517 bugfix on 0.2.1.6-alpha.
6518 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
6519 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
6521 - Set target port in get_interface_address6() correctly. Bugfix
6522 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
6523 - Directory authorities are now more robust to hops back in time
6524 when calculating router stability. Previously, if a run of uptime
6525 or downtime appeared to be negative, the calculation could give
6526 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
6528 - Fix an assert that got triggered when using the TestingTorNetwork
6529 configuration option and then issuing a GETINFO config-text control
6530 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
6532 o Minor bugfixes (on 0.2.2.x):
6533 - Clients should not weight BadExit nodes as Exits in their node
6534 selection. Similarly, directory authorities should not count BadExit
6535 bandwidth as Exit bandwidth when computing bandwidth-weights.
6536 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
6537 - Correctly clear our dir_read/dir_write history when there is an
6538 error parsing any bw history value from the state file. Bugfix on
6540 - Resolve a bug in verifying signatures of directory objects
6541 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
6542 Fixes bug 2409. Found by "piebeer".
6543 - Bridge authorities no longer crash on SIGHUP when they try to
6544 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
6548 - Log less aggressively about circuit timeout changes, and improve
6549 some other circuit timeout messages. Resolves bug 2004.
6550 - Log a little more clearly about the times at which we're no longer
6551 accepting new connections. Resolves bug 2181.
6552 - Reject attempts at the client side to open connections to private
6553 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6554 a randomly chosen exit node. Attempts to do so are always
6555 ill-defined, generally prevented by exit policies, and usually
6556 in error. This will also help to detect loops in transparent
6557 proxy configurations. You can disable this feature by setting
6558 "ClientRejectInternalAddresses 0" in your torrc.
6559 - Always treat failure to allocate an RSA key as an unrecoverable
6561 - Update to the March 1 2011 Maxmind GeoLite Country database.
6563 o Minor features (log subsystem):
6564 - Add documentation for configuring logging at different severities in
6565 different log domains. We've had this feature since 0.2.1.1-alpha,
6566 but for some reason it never made it into the manpage. Fixes
6568 - Make it simpler to specify "All log domains except for A and B".
6569 Previously you needed to say "[*,~A,~B]". Now you can just say
6571 - Add a "LogMessageDomains 1" option to include the domains of log
6572 messages along with the messages. Without this, there's no way
6573 to use log domains without reading the source or doing a lot
6576 o Packaging changes:
6577 - Stop shipping the Tor specs files and development proposal documents
6578 in the tarball. They are now in a separate git repository at
6579 git://git.torproject.org/torspec.git
6582 Changes in version 0.2.1.30 - 2011-02-23
6583 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
6584 change is a slight tweak to Tor's TLS handshake that makes relays
6585 and bridges that run this new version reachable from Iran again.
6586 We don't expect this tweak will win the arms race long-term, but it
6587 buys us time until we roll out a better solution.
6590 - Stop sending a CLOCK_SKEW controller status event whenever
6591 we fetch directory information from a relay that has a wrong clock.
6592 Instead, only inform the controller when it's a trusted authority
6593 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6594 the rest of bug 1074.
6595 - Fix a bounds-checking error that could allow an attacker to
6596 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6598 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6599 Tor would ignore their RelayBandwidthBurst setting,
6600 potentially using more bandwidth than expected. Bugfix on
6601 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6602 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6603 hidserv" in her torrc. The 'hidserv' argument never controlled
6604 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6607 - Adjust our TLS Diffie-Hellman parameters to match those used by
6609 - Update to the February 1 2011 Maxmind GeoLite Country database.
6612 - Check for and reject overly long directory certificates and
6613 directory tokens before they have a chance to hit any assertions.
6614 Bugfix on 0.2.1.28. Found by "doorss".
6615 - Bring the logic that gathers routerinfos and assesses the
6616 acceptability of circuits into line. This prevents a Tor OP from
6617 getting locked in a cycle of choosing its local OR as an exit for a
6618 path (due to a .exit request) and then rejecting the circuit because
6619 its OR is not listed yet. It also prevents Tor clients from using an
6620 OR running in the same instance as an exit (due to a .exit request)
6621 if the OR does not meet the same requirements expected of an OR
6622 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
6624 o Packaging changes:
6625 - Stop shipping the Tor specs files and development proposal documents
6626 in the tarball. They are now in a separate git repository at
6627 git://git.torproject.org/torspec.git
6628 - Do not include Git version tags as though they are SVN tags when
6629 generating a tarball from inside a repository that has switched
6630 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6633 Changes in version 0.2.2.22-alpha - 2011-01-25
6634 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
6635 main other change is a slight tweak to Tor's TLS handshake that makes
6636 relays and bridges that run this new version reachable from Iran again.
6637 We don't expect this tweak will win the arms race long-term, but it
6638 will buy us a bit more time until we roll out a better solution.
6641 - Fix a bounds-checking error that could allow an attacker to
6642 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
6644 - Don't assert when changing from bridge to relay or vice versa
6645 via the controller. The assert happened because we didn't properly
6646 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
6647 bug 2433. Reported by bastik.
6650 - Adjust our TLS Diffie-Hellman parameters to match those used by
6652 - Provide a log message stating which geoip file we're parsing
6653 instead of just stating that we're parsing the geoip file.
6654 Implements ticket 2432.
6657 - Check for and reject overly long directory certificates and
6658 directory tokens before they have a chance to hit any assertions.
6659 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
6662 Changes in version 0.2.2.21-alpha - 2011-01-15
6663 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
6664 continues our recent code security audit work. The main fix resolves
6665 a remote heap overflow vulnerability that can allow remote code
6666 execution (CVE-2011-0427). Other fixes address a variety of assert
6667 and crash bugs, most of which we think are hard to exploit remotely.
6669 o Major bugfixes (security), also included in 0.2.1.29:
6670 - Fix a heap overflow bug where an adversary could cause heap
6671 corruption. This bug probably allows remote code execution
6672 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6674 - Prevent a denial-of-service attack by disallowing any
6675 zlib-compressed data whose compression factor is implausibly
6676 high. Fixes part of bug 2324; reported by "doorss".
6677 - Zero out a few more keys in memory before freeing them. Fixes
6678 bug 2384 and part of bug 2385. These key instances found by
6679 "cypherpunks", based on Andrew Case's report about being able
6680 to find sensitive data in Tor's memory space if you have enough
6681 permissions. Bugfix on 0.0.2pre9.
6683 o Major bugfixes (crashes), also included in 0.2.1.29:
6684 - Prevent calls to Libevent from inside Libevent log handlers.
6685 This had potential to cause a nasty set of crashes, especially
6686 if running Libevent with debug logging enabled, and running
6687 Tor with a controller watching for low-severity log messages.
6688 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6689 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6690 underflow errors there too. Fixes the other part of bug 2324.
6691 - Fix a bug where we would assert if we ever had a
6692 cached-descriptors.new file (or another file read directly into
6693 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6694 on 0.2.1.25. Found by doorss.
6695 - Fix some potential asserts and parsing issues with grossly
6696 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6699 o Minor bugfixes (other), also included in 0.2.1.29:
6700 - Fix a bug with handling misformed replies to reverse DNS lookup
6701 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6702 bug reported by doorss.
6703 - Fix compilation on mingw when a pthreads compatibility library
6704 has been installed. (We don't want to use it, so we shouldn't
6705 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6706 - Fix a bug where we would declare that we had run out of virtual
6707 addresses when the address space was only half-exhausted. Bugfix
6709 - Correctly handle the case where AutomapHostsOnResolve is set but
6710 no virtual addresses are available. Fixes bug 2328; bugfix on
6711 0.1.2.1-alpha. Bug found by doorss.
6712 - Correctly handle wrapping around when we run out of virtual
6713 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
6715 o Minor features, also included in 0.2.1.29:
6716 - Update to the January 1 2011 Maxmind GeoLite Country database.
6717 - Introduce output size checks on all of our decryption functions.
6719 o Build changes, also included in 0.2.1.29:
6720 - Tor does not build packages correctly with Automake 1.6 and earlier;
6721 added a check to Makefile.am to make sure that we're building with
6722 Automake 1.7 or later.
6723 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6724 because we built it with a too-old version of automake. Thus that
6725 release broke ./configure --enable-openbsd-malloc, which is popular
6726 among really fast exit relays on Linux.
6728 o Major bugfixes, new in 0.2.2.21-alpha:
6729 - Prevent crash/heap corruption when the cbtnummodes consensus
6730 parameter is set to 0 or large values. Fixes bug 2317; bugfix
6733 o Major features, new in 0.2.2.21-alpha:
6734 - Introduce minimum/maximum values that clients will believe
6735 from the consensus. Now we'll have a better chance to avoid crashes
6736 or worse when a consensus param has a weird value.
6738 o Minor features, new in 0.2.2.21-alpha:
6739 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
6740 used on bridges, and it makes bridge scanning somewhat easier.
6741 - If writing the state file to disk fails, wait up to an hour before
6742 retrying again, rather than trying again each second. Fixes bug
6743 2346; bugfix on Tor 0.1.1.3-alpha.
6744 - Make Libevent log messages get delivered to controllers later,
6745 and not from inside the Libevent log handler. This prevents unsafe
6746 reentrant Libevent calls while still letting the log messages
6748 - Detect platforms that brokenly use a signed size_t, and refuse to
6749 build there. Found and analyzed by doorss and rransom.
6750 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
6753 o Minor bugfixes, new in 0.2.2.21-alpha:
6754 - Handle SOCKS messages longer than 128 bytes long correctly, rather
6755 than waiting forever for them to finish. Fixes bug 2330; bugfix
6756 on 0.2.0.16-alpha. Found by doorss.
6757 - Add assertions to check for overflow in arguments to
6758 base32_encode() and base32_decode(); fix a signed-unsigned
6759 comparison there too. These bugs are not actually reachable in Tor,
6760 but it's good to prevent future errors too. Found by doorss.
6761 - Correctly detect failures to create DNS requests when using Libevent
6762 versions before v2. (Before Libevent 2, we used our own evdns
6763 implementation. Its return values for Libevent's evdns_resolve_*()
6764 functions are not consistent with those from Libevent.) Fixes bug
6765 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
6767 o Documentation, new in 0.2.2.21-alpha:
6768 - Document the default socks host and port (127.0.0.1:9050) for
6772 Changes in version 0.2.1.29 - 2011-01-15
6773 Tor 0.2.1.29 continues our recent code security audit work. The main
6774 fix resolves a remote heap overflow vulnerability that can allow remote
6775 code execution. Other fixes address a variety of assert and crash bugs,
6776 most of which we think are hard to exploit remotely.
6778 o Major bugfixes (security):
6779 - Fix a heap overflow bug where an adversary could cause heap
6780 corruption. This bug probably allows remote code execution
6781 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
6783 - Prevent a denial-of-service attack by disallowing any
6784 zlib-compressed data whose compression factor is implausibly
6785 high. Fixes part of bug 2324; reported by "doorss".
6786 - Zero out a few more keys in memory before freeing them. Fixes
6787 bug 2384 and part of bug 2385. These key instances found by
6788 "cypherpunks", based on Andrew Case's report about being able
6789 to find sensitive data in Tor's memory space if you have enough
6790 permissions. Bugfix on 0.0.2pre9.
6792 o Major bugfixes (crashes):
6793 - Prevent calls to Libevent from inside Libevent log handlers.
6794 This had potential to cause a nasty set of crashes, especially
6795 if running Libevent with debug logging enabled, and running
6796 Tor with a controller watching for low-severity log messages.
6797 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
6798 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
6799 underflow errors there too. Fixes the other part of bug 2324.
6800 - Fix a bug where we would assert if we ever had a
6801 cached-descriptors.new file (or another file read directly into
6802 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
6803 on 0.2.1.25. Found by doorss.
6804 - Fix some potential asserts and parsing issues with grossly
6805 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
6808 o Minor bugfixes (other):
6809 - Fix a bug with handling misformed replies to reverse DNS lookup
6810 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
6811 bug reported by doorss.
6812 - Fix compilation on mingw when a pthreads compatibility library
6813 has been installed. (We don't want to use it, so we shouldn't
6814 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
6815 - Fix a bug where we would declare that we had run out of virtual
6816 addresses when the address space was only half-exhausted. Bugfix
6818 - Correctly handle the case where AutomapHostsOnResolve is set but
6819 no virtual addresses are available. Fixes bug 2328; bugfix on
6820 0.1.2.1-alpha. Bug found by doorss.
6821 - Correctly handle wrapping around to when we run out of virtual
6822 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
6823 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
6824 because we built it with a too-old version of automake. Thus that
6825 release broke ./configure --enable-openbsd-malloc, which is popular
6826 among really fast exit relays on Linux.
6829 - Update to the January 1 2011 Maxmind GeoLite Country database.
6830 - Introduce output size checks on all of our decryption functions.
6833 - Tor does not build packages correctly with Automake 1.6 and earlier;
6834 added a check to Makefile.am to make sure that we're building with
6835 Automake 1.7 or later.
6838 Changes in version 0.2.2.20-alpha - 2010-12-17
6839 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
6840 exploitable bugs. We also fix a variety of other significant bugs,
6841 change the IP address for one of our directory authorities, and update
6842 the minimum version that Tor relays must run to join the network.
6845 - Fix a remotely exploitable bug that could be used to crash instances
6846 of Tor remotely by overflowing on the heap. Remote-code execution
6847 hasn't been confirmed, but can't be ruled out. Everyone should
6848 upgrade. Bugfix on the 0.1.1 series and later.
6849 - Fix a bug that could break accounting on 64-bit systems with large
6850 time_t values, making them hibernate for impossibly long intervals.
6851 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
6852 - Fix a logic error in directory_fetches_from_authorities() that
6853 would cause all _non_-exits refusing single-hop-like circuits
6854 to fetch from authorities, when we wanted to have _exits_ fetch
6855 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
6857 - Fix a stream fairness bug that would cause newer streams on a given
6858 circuit to get preference when reading bytes from the origin or
6859 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
6860 introduced before the first Tor release, in svn revision r152.
6862 o Directory authority changes:
6863 - Change IP address and ports for gabelmoo (v3 directory authority).
6866 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
6867 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
6868 - Fix an off-by-one error in calculating some controller command
6869 argument lengths. Fortunately, this mistake is harmless since
6870 the controller code does redundant NUL termination too. Found by
6871 boboper. Bugfix on 0.1.1.1-alpha.
6872 - Do not dereference NULL if a bridge fails to build its
6873 extra-info descriptor. Found by an anonymous commenter on
6874 Trac. Bugfix on 0.2.2.19-alpha.
6877 - Update to the December 1 2010 Maxmind GeoLite Country database.
6878 - Directory authorities now reject relays running any versions of
6879 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
6880 known bugs that keep RELAY_EARLY cells from working on rendezvous
6881 circuits. Followup to fix for bug 2081.
6882 - Directory authorities now reject relays running any version of Tor
6883 older than 0.2.0.26-rc. That version is the earliest that fetches
6884 current directory information correctly. Fixes bug 2156.
6885 - Report only the top 10 ports in exit-port stats in order not to
6886 exceed the maximum extra-info descriptor length of 50 KB. Implements
6890 Changes in version 0.2.1.28 - 2010-12-17
6891 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
6892 exploitable bugs. We also took this opportunity to change the IP address
6893 for one of our directory authorities, and to update the geoip database
6897 - Fix a remotely exploitable bug that could be used to crash instances
6898 of Tor remotely by overflowing on the heap. Remote-code execution
6899 hasn't been confirmed, but can't be ruled out. Everyone should
6900 upgrade. Bugfix on the 0.1.1 series and later.
6902 o Directory authority changes:
6903 - Change IP address and ports for gabelmoo (v3 directory authority).
6906 - Update to the December 1 2010 Maxmind GeoLite Country database.
6909 Changes in version 0.2.1.27 - 2010-11-23
6910 Yet another OpenSSL security patch broke its compatibility with Tor:
6911 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
6912 also took this opportunity to fix several crash bugs, integrate a new
6913 directory authority, and update the bundled GeoIP database.
6916 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6917 No longer set the tlsext_host_name extension on server SSL objects;
6918 but continue to set it on client SSL objects. Our goal in setting
6919 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6920 bugfix on 0.2.1.1-alpha.
6921 - Do not log messages to the controller while shrinking buffer
6922 freelists. Doing so would sometimes make the controller connection
6923 try to allocate a buffer chunk, which would mess up the internals
6924 of the freelist and cause an assertion failure. Fixes bug 1125;
6925 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
6926 - Learn our external IP address when we're a relay or bridge, even if
6927 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
6928 where we introduced bridge relays that don't need to publish to
6929 be useful. Fixes bug 2050.
6930 - Do even more to reject (and not just ignore) annotations on
6931 router descriptors received anywhere but from the cache. Previously
6932 we would ignore such annotations at first, but cache them to disk
6933 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
6934 - When you're using bridges and your network goes away and your
6935 bridges get marked as down, recover when you attempt a new socks
6936 connection (if the network is back), rather than waiting up to an
6937 hour to try fetching new descriptors for your bridges. Bugfix on
6938 0.2.0.3-alpha; fixes bug 1981.
6941 - Move to the November 2010 Maxmind GeoLite country db (rather
6942 than the June 2009 ip-to-country GeoIP db) for our statistics that
6943 count how many users relays are seeing from each country. Now we'll
6944 have more accurate data, especially for many African countries.
6946 o New directory authorities:
6947 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6951 - Fix an assertion failure that could occur in directory caches or
6952 bridge users when using a very short voting interval on a testing
6953 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
6955 - Enforce multiplicity rules when parsing annotations. Bugfix on
6956 0.2.0.8-alpha. Found by piebeer.
6957 - Allow handshaking OR connections to take a full KeepalivePeriod
6958 seconds to handshake. Previously, we would close them after
6959 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6960 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6962 - When building with --enable-gcc-warnings on OpenBSD, disable
6963 warnings in system headers. This makes --enable-gcc-warnings
6964 pass on OpenBSD 4.8.
6967 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6968 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6969 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6970 Servers can start sending this code when enough clients recognize
6971 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
6972 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6973 Patch from mingw-san.
6976 - Remove the old debian/ directory from the main Tor distribution.
6977 The official Tor-for-debian git repository lives at the URL
6978 https://git.torproject.org/debian/tor.git
6979 - Stop shipping the old doc/website/ directory in the tarball. We
6980 changed the website format in late 2010, and what we shipped in
6981 0.2.1.26 really wasn't that useful anyway.
6984 Changes in version 0.2.2.19-alpha - 2010-11-22
6985 Yet another OpenSSL security patch broke its compatibility with Tor:
6986 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
6989 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
6990 No longer set the tlsext_host_name extension on server SSL objects;
6991 but continue to set it on client SSL objects. Our goal in setting
6992 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
6993 bugfix on 0.2.1.1-alpha.
6996 - Try harder not to exceed the maximum length of 50 KB when writing
6997 statistics to extra-info descriptors. This bug was triggered by very
6998 fast relays reporting exit-port, entry, and dirreq statistics.
6999 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
7000 - Publish a router descriptor even if generating an extra-info
7001 descriptor fails. Previously we would not publish a router
7002 descriptor without an extra-info descriptor; this can cause fast
7003 exit relays collecting exit-port statistics to drop from the
7004 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
7007 Changes in version 0.2.2.18-alpha - 2010-11-16
7008 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
7009 us lately, makes unpublished bridge relays able to detect their IP
7010 address, and fixes a wide variety of other bugs to get us much closer
7011 to a stable release.
7014 - Do even more to reject (and not just ignore) annotations on
7015 router descriptors received anywhere but from the cache. Previously
7016 we would ignore such annotations at first, but cache them to disk
7017 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7018 - Do not log messages to the controller while shrinking buffer
7019 freelists. Doing so would sometimes make the controller connection
7020 try to allocate a buffer chunk, which would mess up the internals
7021 of the freelist and cause an assertion failure. Fixes bug 1125;
7022 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7023 - Learn our external IP address when we're a relay or bridge, even if
7024 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7025 where we introduced bridge relays that don't need to publish to
7026 be useful. Fixes bug 2050.
7027 - Maintain separate TLS contexts and certificates for incoming and
7028 outgoing connections in bridge relays. Previously we would use the
7029 same TLS contexts and certs for incoming and outgoing connections.
7030 Bugfix on 0.2.0.3-alpha; addresses bug 988.
7031 - Maintain separate identity keys for incoming and outgoing TLS
7032 contexts in bridge relays. Previously we would use the same
7033 identity keys for incoming and outgoing TLS contexts. Bugfix on
7034 0.2.0.3-alpha; addresses the other half of bug 988.
7035 - Avoid an assertion failure when we as an authority receive a
7036 duplicate upload of a router descriptor that we already have,
7037 but which we previously considered an obsolete descriptor.
7038 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
7039 - Avoid a crash bug triggered by looking at a dangling pointer while
7040 setting the network status consensus. Found by Robert Ransom.
7041 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
7042 - Fix a logic error where servers that _didn't_ act as exits would
7043 try to keep their server lists more aggressively up to date than
7044 exits, when it was supposed to be the other way around. Bugfix
7047 o Minor bugfixes (on Tor 0.2.1.x and earlier):
7048 - When we're trying to guess whether we know our IP address as
7049 a relay, we would log various ways that we failed to guess
7050 our address, but never log that we ended up guessing it
7051 successfully. Now add a log line to help confused and anxious
7052 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
7053 - Bring the logic that gathers routerinfos and assesses the
7054 acceptability of circuits into line. This prevents a Tor OP from
7055 getting locked in a cycle of choosing its local OR as an exit for a
7056 path (due to a .exit request) and then rejecting the circuit because
7057 its OR is not listed yet. It also prevents Tor clients from using an
7058 OR running in the same instance as an exit (due to a .exit request)
7059 if the OR does not meet the same requirements expected of an OR
7060 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7061 - Correctly describe errors that occur when generating a TLS object.
7062 Previously we would attribute them to a failure while generating a
7063 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
7065 - Enforce multiplicity rules when parsing annotations. Bugfix on
7066 0.2.0.8-alpha. Found by piebeer.
7067 - Fix warnings that newer versions of autoconf produced during
7068 ./autogen.sh. These warnings appear to be harmless in our case,
7069 but they were extremely verbose. Fixes bug 2020.
7071 o Minor bugfixes (on Tor 0.2.2.x):
7072 - Enable protection of small arrays whenever we build with gcc
7073 hardening features, not only when also building with warnings
7074 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
7077 - Make hidden services work better in private Tor networks by not
7078 requiring any uptime to join the hidden service descriptor
7079 DHT. Implements ticket 2088.
7080 - Rate-limit the "your application is giving Tor only an IP address"
7081 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
7082 - When AllowSingleHopExits is set, print a warning to explain to the
7083 relay operator why most clients are avoiding her relay.
7084 - Update to the November 1 2010 Maxmind GeoLite Country database.
7086 o Code simplifications and refactoring:
7087 - When we fixed bug 1038 we had to put in a restriction not to send
7088 RELAY_EARLY cells on rend circuits. This was necessary as long
7089 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
7090 active. Now remove this obsolete check. Resolves bug 2081.
7091 - Some options used different conventions for uppercasing of acronyms
7092 when comparing manpage and source. Fix those in favor of the
7093 manpage, as it makes sense to capitalize acronyms.
7094 - Remove the torrc.complete file. It hasn't been kept up to date
7095 and users will have better luck checking out the manpage.
7096 - Remove the obsolete "NoPublish" option; it has been flagged
7097 as obsolete and has produced a warning since 0.1.1.18-rc.
7098 - Remove everything related to building the expert bundle for OS X.
7099 It has confused many users, doesn't work right on OS X 10.6,
7100 and is hard to get rid of once installed. Resolves bug 1274.
7103 Changes in version 0.2.2.17-alpha - 2010-09-30
7104 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
7105 to use one-hop circuits (which can put the exit relays at higher risk,
7106 plus unbalance the network); fixes a big bug in bandwidth accounting
7107 for relays that want to limit their monthly bandwidth use; fixes a
7108 big pile of bugs in how clients tolerate temporary network failure;
7109 and makes our adaptive circuit build timeout feature (which improves
7110 client performance if your network is fast while not breaking things
7111 if your network is slow) better handle bad networks.
7114 - Exit relays now try harder to block exit attempts from unknown
7115 relays, to make it harder for people to use them as one-hop proxies
7116 a la tortunnel. Controlled by the refuseunknownexits consensus
7117 parameter (currently enabled), or you can override it on your
7118 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
7120 o Major bugfixes (0.2.1.x and earlier):
7121 - Fix a bug in bandwidth accounting that could make us use twice
7122 the intended bandwidth when our interval start changes due to
7123 daylight saving time. Now we tolerate skew in stored vs computed
7124 interval starts: if the start of the period changes by no more than
7125 50% of the period's duration, we remember bytes that we transferred
7126 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
7127 - Always search the Windows system directory for system DLLs, and
7128 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
7129 - When you're using bridges and your network goes away and your
7130 bridges get marked as down, recover when you attempt a new socks
7131 connection (if the network is back), rather than waiting up to an
7132 hour to try fetching new descriptors for your bridges. Bugfix on
7133 0.2.0.3-alpha; fixes bug 1981.
7135 o Major bugfixes (on 0.2.2.x):
7136 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
7138 - Fix a segfault that could happen when operating a bridge relay with
7139 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
7140 - The consensus bandwidth-weights (used by clients to choose fast
7141 relays) entered an unexpected edge case in September where
7142 Exits were much scarcer than Guards, resulting in bad weight
7143 recommendations. Now we compute them using new constraints that
7144 should succeed in all cases. Also alter directory authorities to
7145 not include the bandwidth-weights line if they fail to produce
7146 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
7147 - When weighting bridges during path selection, we used to trust
7148 the bandwidths they provided in their descriptor, only capping them
7149 at 10MB/s. This turned out to be problematic for two reasons:
7150 Bridges could claim to handle a lot more traffic then they
7151 actually would, thus making more clients pick them and have a
7152 pretty effective DoS attack. The other issue is that new bridges
7153 that might not have a good estimate for their bw capacity yet
7154 would not get used at all unless no other bridges are available
7155 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
7157 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
7158 - Ignore cannibalized circuits when recording circuit build times.
7159 This should provide for a minor performance improvement for hidden
7160 service users using 0.2.2.14-alpha, and should remove two spurious
7161 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
7162 - Simplify the logic that causes us to decide if the network is
7163 unavailable for purposes of recording circuit build times. If we
7164 receive no cells whatsoever for the entire duration of a circuit's
7165 full measured lifetime, the network is probably down. Also ignore
7166 one-hop directory fetching circuit timeouts when calculating our
7167 circuit build times. These changes should hopefully reduce the
7168 cases where we see ridiculous circuit build timeouts for people
7169 with spotty wireless connections. Fixes part of bug 1772; bugfix
7171 - Prevent the circuit build timeout from becoming larger than
7172 the maximum build time we have ever seen. Also, prevent the time
7173 period for measurement circuits from becoming larger than twice that
7174 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
7177 - When we run out of directory information such that we can't build
7178 circuits, but then get enough that we can build circuits, log when
7179 we actually construct a circuit, so the user has a better chance of
7180 knowing what's going on. Fixes bug 1362.
7181 - Be more generous with how much bandwidth we'd use up (with
7182 accounting enabled) before entering "soft hibernation". Previously,
7183 we'd refuse new connections and circuits once we'd used up 95% of
7184 our allotment. Now, we use up 95% of our allotment, AND make sure
7185 that we have no more than 500MB (or 3 hours of expected traffic,
7186 whichever is lower) remaining before we enter soft hibernation.
7187 - If we've configured EntryNodes and our network goes away and/or all
7188 our entrynodes get marked down, optimistically retry them all when
7189 a new socks application request appears. Fixes bug 1882.
7190 - Add some more defensive programming for architectures that can't
7191 handle unaligned integer accesses. We don't know of any actual bugs
7192 right now, but that's the best time to fix them. Fixes bug 1943.
7193 - Support line continuations in the torrc config file. If a line
7194 ends with a single backslash character, the newline is ignored, and
7195 the configuration value is treated as continuing on the next line.
7198 o Minor bugfixes (on 0.2.1.x and earlier):
7199 - For bandwidth accounting, calculate our expected bandwidth rate
7200 based on the time during which we were active and not in
7201 soft-hibernation during the last interval. Previously, we were
7202 also considering the time spent in soft-hibernation. If this
7203 was a long time, we would wind up underestimating our bandwidth
7204 by a lot, and skewing our wakeup time towards the start of the
7205 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
7207 o Minor bugfixes (on 0.2.2.x):
7208 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
7209 which were disabled by the circuit build timeout changes in
7210 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
7211 - Make sure we don't warn about missing bandwidth weights when
7212 choosing bridges or other relays not in the consensus. Bugfix on
7213 0.2.2.10-alpha; fixes bug 1805.
7214 - In our logs, do not double-report signatures from unrecognized
7215 authorities both as "from unknown authority" and "not
7216 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
7219 Changes in version 0.2.2.16-alpha - 2010-09-17
7220 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
7221 evident at exit relays), and also continues to resolve all the little
7222 bugs that have been filling up trac lately.
7224 o Major bugfixes (stream-level fairness):
7225 - When receiving a circuit-level SENDME for a blocked circuit, try
7226 to package cells fairly from all the streams that had previously
7227 been blocked on that circuit. Previously, we had started with the
7228 oldest stream, and allowed each stream to potentially exhaust
7229 the circuit's package window. This gave older streams on any
7230 given circuit priority over newer ones. Fixes bug 1937. Detected
7231 originally by Camilo Viecco. This bug was introduced before the
7232 first Tor release, in svn commit r152: it is the new winner of
7233 the longest-lived bug prize.
7234 - When the exit relay got a circuit-level sendme cell, it started
7235 reading on the exit streams, even if had 500 cells queued in the
7236 circuit queue already, so the circuit queue just grew and grew in
7237 some cases. We fix this by not re-enabling reading on receipt of a
7238 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
7239 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
7241 - Newly created streams were allowed to read cells onto circuits,
7242 even if the circuit's cell queue was blocked and waiting to drain.
7243 This created potential unfairness, as older streams would be
7244 blocked, but newer streams would gladly fill the queue completely.
7245 We add code to detect this situation and prevent any stream from
7246 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
7250 - Update to the September 1 2010 Maxmind GeoLite Country database.
7251 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
7252 not. This would lead to a cookie that is still not group readable.
7253 Closes bug 1843. Suggested by katmagic.
7254 - When logging a rate-limited warning, we now mention how many messages
7255 got suppressed since the last warning.
7256 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
7257 do individual connection-level rate limiting of clients. The torrc
7258 config options with the same names trump the consensus params, if
7259 both are present. Replaces the old "bwconnrate" and "bwconnburst"
7260 consensus params which were broken from 0.2.2.7-alpha through
7261 0.2.2.14-alpha. Closes bug 1947.
7262 - When a router changes IP address or port, authorities now launch
7263 a new reachability test for it. Implements ticket 1899.
7264 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
7265 2 no signature, 4 required" messages about consensus signatures
7266 easier to read, and make sure they get logged at the same severity
7267 as the messages explaining which keys are which. Fixes bug 1290.
7268 - Don't warn when we have a consensus that we can't verify because
7269 of missing certificates, unless those certificates are ones
7270 that we have been trying and failing to download. Fixes bug 1145.
7271 - If you configure your bridge with a known identity fingerprint,
7272 and the bridge authority is unreachable (as it is in at least
7273 one country now), fall back to directly requesting the descriptor
7274 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
7276 - When building with --enable-gcc-warnings on OpenBSD, disable
7277 warnings in system headers. This makes --enable-gcc-warnings
7278 pass on OpenBSD 4.8.
7280 o Minor bugfixes (on 0.2.1.x and earlier):
7281 - Authorities will now attempt to download consensuses if their
7282 own efforts to make a live consensus have failed. This change
7283 means authorities that restart will fetch a valid consensus, and
7284 it means authorities that didn't agree with the current consensus
7285 will still fetch and serve it if it has enough signatures. Bugfix
7286 on 0.2.0.9-alpha; fixes bug 1300.
7287 - Ensure DNS requests launched by "RESOLVE" commands from the
7288 controller respect the __LeaveStreamsUnattached setconf options. The
7289 same goes for requests launched via DNSPort or transparent
7290 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
7291 - Allow handshaking OR connections to take a full KeepalivePeriod
7292 seconds to handshake. Previously, we would close them after
7293 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7294 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7296 - Rate-limit "Failed to hand off onionskin" warnings.
7297 - Never relay a cell for a circuit we have already destroyed.
7298 Between marking a circuit as closeable and finally closing it,
7299 it may have been possible for a few queued cells to get relayed,
7300 even though they would have been immediately dropped by the next
7301 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
7302 - Never queue a cell for a circuit that's already been marked
7304 - Never vote for a server as "Running" if we have a descriptor for
7305 it claiming to be hibernating, and that descriptor was published
7306 more recently than our last contact with the server. Bugfix on
7307 0.2.0.3-alpha; fixes bug 911.
7308 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
7311 o Minor bugfixes (on 0.2.2.x):
7312 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
7313 down if a directory fetch fails and you've configured either
7314 bridges or EntryNodes. The intent was to mark the relay as down
7315 _unless_ you're using bridges or EntryNodes, since if you are
7316 then you could quickly run out of entry points.
7317 - Fix the Windows directory-listing code. A bug introduced in
7318 0.2.2.14-alpha could make Windows directory servers forget to load
7319 some of their cached v2 networkstatus files.
7320 - Really allow clients to use relays as bridges. Fixes bug 1776;
7321 bugfix on 0.2.2.15-alpha.
7322 - Demote a warn to info that happens when the CellStatistics option
7323 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
7324 Reported by Moritz Bartl.
7325 - On Windows, build correctly either with or without Unicode support.
7326 This is necessary so that Tor can support fringe platforms like
7327 Windows 98 (which has no Unicode), or Windows CE (which has no
7328 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
7331 - Add a unit test for cross-platform directory-listing code.
7334 Changes in version 0.2.2.15-alpha - 2010-08-18
7335 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
7336 fixes a variety of other bugs that were preventing performance
7337 experiments from moving forward, fixes several bothersome memory leaks,
7338 and generally closes a lot of smaller bugs that have been filling up
7342 - Stop assigning the HSDir flag to relays that disable their
7343 DirPort (and thus will refuse to answer directory requests). This
7344 fix should dramatically improve the reachability of hidden services:
7345 hidden services and hidden service clients pick six HSDir relays
7346 to store and retrieve the hidden service descriptor, and currently
7347 about half of the HSDir relays will refuse to work. Bugfix on
7348 0.2.0.10-alpha; fixes part of bug 1693.
7349 - The PerConnBWRate and Burst config options, along with the
7350 bwconnrate and bwconnburst consensus params, initialized each conn's
7351 token bucket values only when the connection is established. Now we
7352 update them if the config options change, and update them every time
7353 we get a new consensus. Otherwise we can encounter an ugly edge
7354 case where we initialize an OR conn to client-level bandwidth,
7355 but then later the relay joins the consensus and we leave it
7356 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
7357 - Fix a regression that caused Tor to rebind its ports if it receives
7358 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
7361 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
7362 should give us approximately 40-50% more Guard-flagged nodes,
7363 improving the anonymity the Tor network can provide and also
7364 decreasing the dropoff in throughput that relays experience when
7365 they first get the Guard flag.
7366 - Allow enabling or disabling the *Statistics config options while
7370 - Update to the August 1 2010 Maxmind GeoLite Country database.
7371 - Have the controller interface give a more useful message than
7372 "Internal Error" in response to failed GETINFO requests.
7373 - Warn when the same option is provided more than once in a torrc
7374 file, on the command line, or in a single SETCONF statement, and
7375 the option is one that only accepts a single line. Closes bug 1384.
7376 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7377 Patch from mingw-san.
7378 - Add support for the country code "{??}" in torrc options like
7379 ExcludeNodes, to indicate all routers of unknown country. Closes
7381 - Relays report the number of bytes spent on answering directory
7382 requests in extra-info descriptors similar to {read,write}-history.
7383 Implements enhancement 1790.
7385 o Minor bugfixes (on 0.2.1.x and earlier):
7386 - Complain if PublishServerDescriptor is given multiple arguments that
7387 include 0 or 1. This configuration will be rejected in the future.
7388 Bugfix on 0.2.0.1-alpha; closes bug 1107.
7389 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
7390 Bugfix on 0.2.0.13-alpha; closes bug 928.
7391 - Change "Application request when we're believed to be offline."
7392 notice to "Application request when we haven't used client
7393 functionality lately.", to clarify that it's not an error. Bugfix
7394 on 0.0.9.3; fixes bug 1222.
7395 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
7396 would return "551 Internal error" rather than "552 Unrecognized key
7397 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
7398 - Users can't configure a regular relay to be their bridge. It didn't
7399 work because when Tor fetched the bridge descriptor, it found
7400 that it already had it, and didn't realize that the purpose of the
7401 descriptor had changed. Now we replace routers with a purpose other
7402 than bridge with bridge descriptors when fetching them. Bugfix on
7403 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
7404 refetch the descriptor with router purpose 'general', disabling
7406 - Fix a rare bug in rend_fn unit tests: we would fail a test when
7407 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
7408 on 0.2.0.10-alpha; fixes bug 1808.
7409 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7410 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7411 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7412 Servers can start sending this code when enough clients recognize
7413 it. Also update the spec to reflect this new reason. Bugfix on
7414 0.1.0.1-rc; fixes part of bug 1793.
7415 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
7416 when we switch from being a public relay to a bridge. Otherwise
7417 there will still be clients that see the relay in their consensus,
7418 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
7420 - Instead of giving an assertion failure on an internal mismatch
7421 on estimated freelist size, just log a BUG warning and try later.
7422 Mitigates but does not fix bug 1125.
7423 - Fix an assertion failure that could occur in caches or bridge users
7424 when using a very short voting interval on a testing network.
7425 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
7427 o Minor bugfixes (on 0.2.2.x):
7428 - Alter directory authorities to always consider Exit-flagged nodes
7429 as potential Guard nodes in their votes. The actual decision to
7430 use Exits as Guards is done in the consensus bandwidth weights.
7431 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
7432 - When the controller is reporting the purpose of circuits that
7433 didn't finish building before the circuit build timeout, it was
7434 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
7435 - Our libevent version parsing code couldn't handle versions like
7436 1.4.14b-stable and incorrectly warned the user about using an
7437 old and broken version of libevent. Treat 1.4.14b-stable like
7438 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
7440 - Don't use substitution references like $(VAR:MOD) when
7441 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
7442 '$(:x)' to 'x' rather than the empty string. This bites us in
7443 doc/ when configured with --disable-asciidoc. Bugfix on
7444 0.2.2.9-alpha; fixes bug 1773.
7445 - Remove a spurious hidden service server-side log notice about
7446 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
7448 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
7450 - Correctly report written bytes on linked connections. Found while
7451 implementing 1790. Bugfix on 0.2.2.4-alpha.
7452 - Fix three memory leaks: one in circuit_build_times_parse_state(),
7453 one in dirvote_add_signatures_to_pending_consensus(), and one every
7454 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
7455 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
7457 o Code simplifications and refactoring:
7458 - Take a first step towards making or.h smaller by splitting out
7459 function definitions for all source files in src/or/. Leave
7460 structures and defines in or.h for now.
7461 - Remove a bunch of unused function declarations as well as a block of
7462 #if 0'd code from the unit tests. Closes bug 1824.
7463 - New unit tests for exit-port history statistics; refactored exit
7464 statistics code to be more easily tested.
7465 - Remove the old debian/ directory from the main Tor distribution.
7466 The official Tor-for-debian git repository lives at the URL
7467 https://git.torproject.org/debian/tor.git
7470 Changes in version 0.2.2.14-alpha - 2010-07-12
7471 Tor 0.2.2.14-alpha greatly improves client-side handling of
7472 circuit build timeouts, which are used to estimate speed and improve
7473 performance. We also move to a much better GeoIP database, port Tor to
7474 Windows CE, introduce new compile flags that improve code security,
7475 add an eighth v3 directory authority, and address a lot of more
7479 - Tor directory authorities no longer crash when started with a
7480 cached-microdesc-consensus file in their data directory. Bugfix
7481 on 0.2.2.6-alpha; fixes bug 1532.
7482 - Treat an unset $HOME like an empty $HOME rather than triggering an
7483 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
7484 - Ignore negative and large circuit build timeout values that can
7485 happen during a suspend or hibernate. These values caused various
7486 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
7487 - Alter calculation of Pareto distribution parameter 'Xm' for
7488 Circuit Build Timeout learning to use the weighted average of the
7489 top N=3 modes (because we have three entry guards). Considering
7490 multiple modes should improve the timeout calculation in some cases,
7491 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
7493 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
7494 right censored distribution model. This approach improves over the
7495 synthetic timeout generation approach that was producing insanely
7496 high timeout values. Now we calculate build timeouts using truncated
7497 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
7498 - Do not close circuits that are under construction when they reach
7499 the circuit build timeout. Instead, leave them building (but do not
7500 use them) for up until the time corresponding to the 95th percentile
7501 on the Pareto CDF or 60 seconds, whichever is greater. This is done
7502 to provide better data for the new Pareto model. This percentile
7503 can be controlled by the consensus.
7506 - Move to the June 2010 Maxmind GeoLite country db (rather than the
7507 June 2009 ip-to-country GeoIP db) for our statistics that count
7508 how many users relays are seeing from each country. Now we have
7509 more accurate data for many African countries.
7510 - Port Tor to build and run correctly on Windows CE systems, using
7511 the wcecompat library. Contributed by Valerio Lupi.
7512 - New "--enable-gcc-hardening" ./configure flag (off by default)
7513 to turn on gcc compile time hardening options. It ensures
7514 that signed ints have defined behavior (-fwrapv), enables
7515 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
7516 with canaries (-fstack-protector-all), turns on ASLR protection if
7517 supported by the kernel (-fPIE, -pie), and adds additional security
7518 related warnings. Verified to work on Mac OS X and Debian Lenny.
7519 - New "--enable-linker-hardening" ./configure flag (off by default)
7520 to turn on ELF specific hardening features (relro, now). This does
7521 not work with Mac OS X or any other non-ELF binary format.
7523 o New directory authorities:
7524 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7528 - New config option "WarnUnsafeSocks 0" disables the warning that
7529 occurs whenever Tor receives a socks handshake using a version of
7530 the socks protocol that can only provide an IP address (rather
7531 than a hostname). Setups that do DNS locally over Tor are fine,
7532 and we shouldn't spam the logs in that case.
7533 - Convert the HACKING file to asciidoc, and add a few new sections
7534 to it, explaining how we use Git, how we make changelogs, and
7535 what should go in a patch.
7536 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
7537 event, to give information on the current rate of circuit timeouts
7538 over our stored history.
7539 - Add ability to disable circuit build time learning via consensus
7540 parameter and via a LearnCircuitBuildTimeout config option. Also
7541 automatically disable circuit build time calculation if we are
7542 either a AuthoritativeDirectory, or if we fail to write our state
7543 file. Fixes bug 1296.
7544 - More gracefully handle corrupt state files, removing asserts
7545 in favor of saving a backup and resetting state.
7546 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
7550 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7552 - When a2x fails, mention that the user could disable manpages instead
7553 of trying to fix their asciidoc installation.
7554 - Where available, use Libevent 2.0's periodic timers so that our
7555 once-per-second cleanup code gets called even more closely to
7556 once per second than it would otherwise. Fixes bug 943.
7557 - If you run a bridge that listens on multiple IP addresses, and
7558 some user configures a bridge address that uses a different IP
7559 address than your bridge writes in its router descriptor, and the
7560 user doesn't specify an identity key, their Tor would discard the
7561 descriptor because "it isn't one of our configured bridges", and
7562 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
7563 Bugfix on 0.2.0.3-alpha.
7564 - If OpenSSL fails to make a duplicate of a private or public key, log
7565 an error message and try to exit cleanly. May help with debugging
7566 if bug 1209 ever remanifests.
7567 - Save a couple bytes in memory allocation every time we escape
7568 certain characters in a string. Patch from Florian Zumbiehl.
7569 - Make it explicit that we don't cannibalize one-hop circuits. This
7570 happens in the wild, but doesn't turn out to be a problem because
7571 we fortunately don't use those circuits. Many thanks to outofwords
7572 for the initial analysis and to swissknife who confirmed that
7573 two-hop circuits are actually created.
7574 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
7575 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
7576 - Eliminate a case where a circuit build time warning was displayed
7577 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
7580 Changes in version 0.2.1.26 - 2010-05-02
7581 Tor 0.2.1.26 addresses the recent connection and memory overload
7582 problems we've been seeing on relays, especially relays with their
7583 DirPort open. If your relay has been crashing, or you turned it off
7584 because it used too many resources, give this release a try.
7586 This release also fixes yet another instance of broken OpenSSL libraries
7587 that was causing some relays to drop out of the consensus.
7590 - Teach relays to defend themselves from connection overload. Relays
7591 now close idle circuits early if it looks like they were intended
7592 for directory fetches. Relays are also more aggressive about closing
7593 TLS connections that have no circuits on them. Such circuits are
7594 unlikely to be re-used, and tens of thousands of them were piling
7595 up at the fast relays, causing the relays to run out of sockets
7596 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7597 their directory fetches over TLS).
7598 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7599 that claim to be earlier than 0.9.8m, but which have in reality
7600 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7601 behavior. Possible fix for some cases of bug 1346.
7602 - Directory mirrors were fetching relay descriptors only from v2
7603 directory authorities, rather than v3 authorities like they should.
7604 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7605 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7608 - Finally get rid of the deprecated and now harmful notion of "clique
7609 mode", where directory authorities maintain TLS connections to
7613 - In the util/threads test, no longer free the test_mutex before all
7614 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7615 - The master thread could starve the worker threads quite badly on
7616 certain systems, causing them to run only partially in the allowed
7617 window. This resulted in test failures. Now the master thread sleeps
7618 occasionally for a few microseconds while the two worker-threads
7619 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7622 Changes in version 0.2.2.13-alpha - 2010-04-24
7623 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
7624 problems we've been seeing on relays, especially relays with their
7625 DirPort open. If your relay has been crashing, or you turned it off
7626 because it used too many resources, give this release a try.
7629 - Teach relays to defend themselves from connection overload. Relays
7630 now close idle circuits early if it looks like they were intended
7631 for directory fetches. Relays are also more aggressive about closing
7632 TLS connections that have no circuits on them. Such circuits are
7633 unlikely to be re-used, and tens of thousands of them were piling
7634 up at the fast relays, causing the relays to run out of sockets
7635 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
7636 their directory fetches over TLS).
7639 - Finally get rid of the deprecated and now harmful notion of "clique
7640 mode", where directory authorities maintain TLS connections to
7642 - Directory authorities now do an immediate reachability check as soon
7643 as they hear about a new relay. This change should slightly reduce
7644 the time between setting up a relay and getting listed as running
7645 in the consensus. It should also improve the time between setting
7646 up a bridge and seeing use by bridge users.
7647 - Directory authorities no longer launch a TLS connection to every
7648 relay as they startup. Now that we have 2k+ descriptors cached,
7649 the resulting network hiccup is becoming a burden. Besides,
7650 authorities already avoid voting about Running for the first half
7651 hour of their uptime.
7654 Changes in version 0.2.2.12-alpha - 2010-04-20
7655 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
7656 handle and vote on descriptors. It was causing relays to drop out of
7660 - Many relays have been falling out of the consensus lately because
7661 not enough authorities know about their descriptor for them to get
7662 a majority of votes. When we deprecated the v2 directory protocol,
7663 we got rid of the only way that v3 authorities can hear from each
7664 other about other descriptors. Now authorities examine every v3
7665 vote for new descriptors, and fetch them from that authority. Bugfix
7667 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
7668 and a warning in or.h related to bandwidth_weight_rule_t that
7669 prevented clean compile on OS X. Fixes bug 1363; bugfix on
7671 - Fix a segfault on relays when DirReqStatistics is enabled
7672 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
7676 - Demote a confusing TLS warning that relay operators might get when
7677 someone tries to talk to their OrPort. It is neither the operator's
7678 fault nor can they do anything about it. Fixes bug 1364; bugfix
7682 Changes in version 0.2.2.11-alpha - 2010-04-15
7683 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
7684 libraries that was causing some relays to drop out of the consensus.
7687 - Directory mirrors were fetching relay descriptors only from v2
7688 directory authorities, rather than v3 authorities like they should.
7689 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
7690 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
7691 - Fix a parsing error that made every possible value of
7692 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
7693 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
7694 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
7695 about the option without breaking older ones.
7696 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
7697 that claim to be earlier than 0.9.8m, but which have in reality
7698 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
7699 behavior. Possible fix for some cases of bug 1346.
7702 - Experiment with a more aggressive approach to preventing clients
7703 from making one-hop exit streams. Exit relays who want to try it
7704 out can set "RefuseUnknownExits 1" in their torrc, and then look
7705 for "Attempt by %s to open a stream" log messages. Let us know
7707 - Add support for statically linking zlib by specifying
7708 --enable-static-zlib, to go with our support for statically linking
7709 openssl and libevent. Resolves bug 1358.
7712 - Fix a segfault that happens whenever a Tor client that is using
7713 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
7715 - When we cleaned up the contrib/tor-exit-notice.html file, we left
7716 out the first line. Fixes bug 1295.
7717 - When building the manpage from a tarball, we required asciidoc, but
7718 the asciidoc -> roff/html conversion was already done for the
7719 tarball. Make 'make' complain only when we need asciidoc (either
7720 because we're compiling directly from git, or because we altered
7721 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
7722 - When none of the directory authorities vote on any params, Tor
7723 segfaulted when trying to make the consensus from the votes. We
7724 didn't trigger the bug in practice, because authorities do include
7725 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
7728 - In the util/threads test, no longer free the test_mutex before all
7729 worker threads have finished. Bugfix on 0.2.1.6-alpha.
7730 - The master thread could starve the worker threads quite badly on
7731 certain systems, causing them to run only partially in the allowed
7732 window. This resulted in test failures. Now the master thread sleeps
7733 occasionally for a few microseconds while the two worker-threads
7734 compete for the mutex. Bugfix on 0.2.0.1-alpha.
7737 Changes in version 0.2.2.10-alpha - 2010-03-07
7738 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
7739 could prevent relays from guessing their IP address correctly. It also
7740 starts the groundwork for another client-side performance boost, since
7741 currently we're not making efficient use of relays that have both the
7742 Guard flag and the Exit flag.
7745 - Fix a regression from our patch for bug 1244 that caused relays
7746 to guess their IP address incorrectly if they didn't set Address
7747 in their torrc and/or their address fails to resolve. Bugfix on
7748 0.2.2.9-alpha; fixes bug 1269.
7750 o Major features (performance):
7751 - Directory authorities now compute consensus weightings that instruct
7752 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
7753 and no flag. Clients that use these weightings will distribute
7754 network load more evenly across these different relay types. The
7755 weightings are in the consensus so we can change them globally in
7756 the future. Extra thanks to "outofwords" for finding some nasty
7757 security bugs in the first implementation of this feature.
7759 o Minor features (performance):
7760 - Always perform router selections using weighted relay bandwidth,
7761 even if we don't need a high capacity circuit at the time. Non-fast
7762 circuits now only differ from fast ones in that they can use relays
7763 not marked with the Fast flag. This "feature" could turn out to
7764 be a horrible bug; we should investigate more before it goes into
7768 - Allow disabling building of the manpages. Skipping the manpage
7769 speeds up the build considerably.
7771 o Minor bugfixes (on 0.2.2.x):
7772 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
7773 Bugfix on 0.2.2.9-alpha.
7774 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
7775 config option. Bugfix on 0.2.2.7-alpha.
7776 - Ship the asciidoc-helper file in the tarball, so that people can
7777 build from source if they want to, and touching the .1.txt files
7778 doesn't break the build. Bugfix on 0.2.2.9-alpha.
7780 o Minor bugfixes (on 0.2.1.x or earlier):
7781 - Fix a dereference-then-NULL-check sequence when publishing
7782 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7784 - Fix another dereference-then-NULL-check sequence. Bugfix on
7785 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7786 - Make sure we treat potentially not NUL-terminated strings correctly.
7787 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7789 o Code simplifications and refactoring:
7790 - Fix some urls in the exit notice file and make it XHTML1.1 strict
7791 compliant. Based on a patch from Christian Kujau.
7792 - Don't use sed in asciidoc-helper anymore.
7793 - Make the build process fail if asciidoc cannot be found and
7794 building with asciidoc isn't disabled.
7797 Changes in version 0.2.2.9-alpha - 2010-02-22
7798 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
7799 location of a directory authority, and cleans up a bunch of small bugs.
7801 o Directory authority changes:
7802 - Change IP address for dannenberg (v3 directory authority), and
7803 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7804 service directory authority) from the list.
7807 - Make Tor work again on the latest OS X: when deciding whether to
7808 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7809 version at run-time, not compile time. We need to do this because
7810 Apple doesn't update its dev-tools headers when it updates its
7811 libraries in a security patch.
7812 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7813 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7814 a memory leak when requesting a hidden service descriptor we've
7815 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7817 - Authorities could be tricked into giving out the Exit flag to relays
7818 that didn't allow exiting to any ports. This bug could screw
7819 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
7820 1238. Bug discovered by Martin Kowalczyk.
7821 - When freeing a session key, zero it out completely. We only zeroed
7822 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7823 patched by ekir. Fixes bug 1254.
7826 - Fix static compilation by listing the openssl libraries in the right
7827 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
7828 - Resume handling .exit hostnames in a special way: originally we
7829 stripped the .exit part and used the requested exit relay. In
7830 0.2.2.1-alpha we stopped treating them in any special way, meaning
7831 if you use a .exit address then Tor will pass it on to the exit
7832 relay. Now we reject the .exit stream outright, since that behavior
7833 might be more expected by the user. Found and diagnosed by Scott
7834 Bennett and Downie on or-talk.
7835 - Don't spam the controller with events when we have no file
7836 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
7837 for log messages was already solved from bug 748.)
7838 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
7840 - Make the DNSPort option work with libevent 2.x. Don't alter the
7841 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
7842 - Emit a GUARD DROPPED controller event for a case we missed.
7843 - Make more fields in the controller protocol case-insensitive, since
7844 control-spec.txt said they were.
7845 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7846 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7847 - Fix a spec conformance issue: the network-status-version token
7848 must be the first token in a v3 consensus or vote. Discovered by
7849 parakeep. Bugfix on 0.2.0.3-alpha.
7851 o Code simplifications and refactoring:
7852 - Generate our manpage and HTML documentation using Asciidoc. This
7853 change should make it easier to maintain the documentation, and
7855 - Remove the --enable-iphone option. According to reports from Marco
7856 Bonetti, Tor builds fine without any special tweaking on recent
7857 iPhone SDK versions.
7858 - Removed some unnecessary files from the source distribution. The
7859 AUTHORS file has now been merged into the people page on the
7860 website. The roadmaps and design doc can now be found in the
7861 projects directory in svn.
7862 - Enabled various circuit build timeout constants to be controlled
7863 by consensus parameters. Also set better defaults for these
7864 parameters based on experimentation on broadband and simulated
7868 - The 'EXTENDCIRCUIT' control port command can now be used with
7869 a circ id of 0 and no path. This feature will cause Tor to build
7870 a new 'fast' general purpose circuit using its own path selection
7872 - Added a BUILDTIMEOUT_SET controller event to describe changes
7873 to the circuit build timeout.
7874 - Future-proof the controller protocol a bit by ignoring keyword
7875 arguments we do not recognize.
7876 - Expand homedirs passed to tor-checkkey. This should silence a
7877 coverity complaint about passing a user-supplied string into
7878 open() without checking it.
7881 Changes in version 0.2.1.25 - 2010-03-16
7882 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
7883 prevent relays from guessing their IP address correctly. It also fixes
7884 several minor potential security bugs.
7887 - Fix a regression from our patch for bug 1244 that caused relays
7888 to guess their IP address incorrectly if they didn't set Address
7889 in their torrc and/or their address fails to resolve. Bugfix on
7890 0.2.1.23; fixes bug 1269.
7891 - When freeing a session key, zero it out completely. We only zeroed
7892 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
7893 patched by ekir. Fixes bug 1254.
7896 - Fix a dereference-then-NULL-check sequence when publishing
7897 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
7899 - Fix another dereference-then-NULL-check sequence. Bugfix on
7900 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
7901 - Make sure we treat potentially not NUL-terminated strings correctly.
7902 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
7906 Changes in version 0.2.1.24 - 2010-02-21
7907 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
7911 - Work correctly out-of-the-box with even more vendor-patched versions
7912 of OpenSSL. In particular, make it so Debian and OS X don't need
7913 customized patches to run/build.
7916 Changes in version 0.2.1.23 - 2010-02-13
7917 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
7918 again on the latest OS X, and updates the location of a directory
7921 o Major bugfixes (performance):
7922 - We were selecting our guards uniformly at random, and then weighting
7923 which of our guards we'd use uniformly at random. This imbalance
7924 meant that Tor clients were severely limited on throughput (and
7925 probably latency too) by the first hop in their circuit. Now we
7926 select guards weighted by currently advertised bandwidth. We also
7927 automatically discard guards picked using the old algorithm. Fixes
7928 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7931 - Make Tor work again on the latest OS X: when deciding whether to
7932 use strange flags to turn TLS renegotiation on, detect the OpenSSL
7933 version at run-time, not compile time. We need to do this because
7934 Apple doesn't update its dev-tools headers when it updates its
7935 libraries in a security patch.
7936 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
7937 that could happen on 32-bit platforms with 64-bit time_t. Also fix
7938 a memory leak when requesting a hidden service descriptor we've
7939 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
7942 o Directory authority changes:
7943 - Change IP address for dannenberg (v3 directory authority), and
7944 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
7945 service directory authority) from the list.
7948 - Refactor resolve_my_address() to not use gethostbyname() anymore.
7949 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
7952 - Avoid a mad rush at the beginning of each month when each client
7953 rotates half of its guards. Instead we spread the rotation out
7954 throughout the month, but we still avoid leaving a precise timestamp
7955 in the state file about when we first picked the guard. Improves
7956 over the behavior introduced in 0.1.2.17.
7959 Changes in version 0.2.2.8-alpha - 2010-01-26
7960 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
7961 causing bridge relays to disappear. If you're running a bridge,
7965 - Fix a memory corruption bug on bridges that occured during the
7966 inclusion of stats data in extra-info descriptors. Also fix the
7967 interface for geoip_get_bridge_stats* to prevent similar bugs in
7968 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
7969 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
7972 - Ignore OutboundBindAddress when connecting to localhost.
7973 Connections to localhost need to come _from_ localhost, or else
7974 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
7978 Changes in version 0.2.2.7-alpha - 2010-01-19
7979 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
7980 as laying the groundwork for further relay-side performance fixes. It
7981 also starts cleaning up client behavior with respect to the EntryNodes,
7982 ExitNodes, and StrictNodes config options.
7984 This release also rotates two directory authority keys, due to a
7985 security breach of some of the Torproject servers.
7987 o Directory authority changes:
7988 - Rotate keys (both v3 identity and relay identity) for moria1
7991 o Major features (performance):
7992 - We were selecting our guards uniformly at random, and then weighting
7993 which of our guards we'd use uniformly at random. This imbalance
7994 meant that Tor clients were severely limited on throughput (and
7995 probably latency too) by the first hop in their circuit. Now we
7996 select guards weighted by currently advertised bandwidth. We also
7997 automatically discard guards picked using the old algorithm. Fixes
7998 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
7999 - When choosing which cells to relay first, relays can now favor
8000 circuits that have been quiet recently, to provide lower latency
8001 for low-volume circuits. By default, relays enable or disable this
8002 feature based on a setting in the consensus. You can override
8003 this default by using the new "CircuitPriorityHalflife" config
8004 option. Design and code by Ian Goldberg, Can Tang, and Chris
8006 - Add separate per-conn write limiting to go with the per-conn read
8007 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8008 but never per-conn write limits.
8009 - New consensus params "bwconnrate" and "bwconnburst" to let us
8010 rate-limit client connections as they enter the network. It's
8011 controlled in the consensus so we can turn it on and off for
8012 experiments. It's starting out off. Based on proposal 163.
8014 o Major features (relay selection options):
8015 - Switch to a StrictNodes config option, rather than the previous
8016 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
8017 "StrictExcludeNodes" option.
8018 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8019 change during a config reload, mark and discard all our origin
8020 circuits. This fix should address edge cases where we change the
8021 config options and but then choose a circuit that we created before
8023 - If EntryNodes or ExitNodes are set, be more willing to use an
8024 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
8026 - Make EntryNodes config option much more aggressive even when
8027 StrictNodes is not set. Before it would prepend your requested
8028 entrynodes to your list of guard nodes, but feel free to use others
8029 after that. Now it chooses only from your EntryNodes if any of
8030 those are available, and only falls back to others if a) they're
8031 all down and b) StrictNodes is not set.
8032 - Now we refresh your entry guards from EntryNodes at each consensus
8033 fetch -- rather than just at startup and then they slowly rot as
8034 the network changes.
8037 - Stop bridge directory authorities from answering dbg-stability.txt
8038 directory queries, which would let people fetch a list of all
8039 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8042 - Log a notice when we get a new control connection. Now it's easier
8043 for security-conscious users to recognize when a local application
8044 is knocking on their controller door. Suggested by bug 1196.
8045 - New config option "CircuitStreamTimeout" to override our internal
8046 timeout schedule for how many seconds until we detach a stream from
8047 a circuit and try a new circuit. If your network is particularly
8048 slow, you might want to set this to a number like 60.
8049 - New controller command "getinfo config-text". It returns the
8050 contents that Tor would write if you send it a SAVECONF command,
8051 so the controller can write the file to disk itself.
8052 - New options for SafeLogging to allow scrubbing only log messages
8053 generated while acting as a relay.
8054 - Ship the bridges spec file in the tarball too.
8055 - Avoid a mad rush at the beginning of each month when each client
8056 rotates half of its guards. Instead we spread the rotation out
8057 throughout the month, but we still avoid leaving a precise timestamp
8058 in the state file about when we first picked the guard. Improves
8059 over the behavior introduced in 0.1.2.17.
8061 o Minor bugfixes (compiling):
8062 - Fix compilation on OS X 10.3, which has a stub mlockall() but
8063 hides it. Bugfix on 0.2.2.6-alpha.
8064 - Fix compilation on Solaris by removing support for the
8065 DisableAllSwap config option. Solaris doesn't have an rlimit for
8066 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
8069 o Minor bugfixes (crashes):
8070 - Do not segfault when writing buffer stats when we haven't observed
8071 a single circuit to report about. Found by Fabian Lanze. Bugfix on
8073 - If we're in the pathological case where there's no exit bandwidth
8074 but there is non-exit bandwidth, or no guard bandwidth but there
8075 is non-guard bandwidth, don't crash during path selection. Bugfix
8077 - Fix an impossible-to-actually-trigger buffer overflow in relay
8078 descriptor generation. Bugfix on 0.1.0.15.
8080 o Minor bugfixes (privacy):
8081 - Fix an instance where a Tor directory mirror might accidentally
8082 log the IP address of a misbehaving Tor client. Bugfix on
8084 - Don't list Windows capabilities in relay descriptors. We never made
8085 use of them, and maybe it's a bad idea to publish them. Bugfix
8088 o Minor bugfixes (other):
8089 - Resolve an edge case in path weighting that could make us misweight
8090 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8091 - Fix statistics on client numbers by country as seen by bridges that
8092 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
8093 intervals instead of variable 12-to-48-hour intervals.
8094 - After we free an internal connection structure, overwrite it
8095 with a different memory value than we use for overwriting a freed
8096 internal circuit structure. Should help with debugging. Suggested
8098 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
8102 - Remove the HSAuthorityRecordStats option that version 0 hidden
8103 service authorities could have used to track statistics of overall
8104 hidden service usage.
8107 Changes in version 0.2.1.22 - 2010-01-19
8108 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
8109 authorities -- it would tell you its whole history of bridge descriptors
8110 if you make the right directory request. This stable update also
8111 rotates two of the seven v3 directory authority keys and locations.
8113 o Directory authority changes:
8114 - Rotate keys (both v3 identity and relay identity) for moria1
8118 - Stop bridge directory authorities from answering dbg-stability.txt
8119 directory queries, which would let people fetch a list of all
8120 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8123 Changes in version 0.2.1.21 - 2009-12-21
8124 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
8125 library. If you use Tor on Linux / Unix and you're getting SSL
8126 renegotiation errors, upgrading should help. We also recommend an
8127 upgrade if you're an exit relay.
8130 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8131 handshake from working unless we explicitly tell OpenSSL that we
8132 are using SSL renegotiation safely. We are, of course, but OpenSSL
8133 0.9.8l won't work unless we say we are.
8134 - Avoid crashing if the client is trying to upload many bytes and the
8135 circuit gets torn down at the same time, or if the flip side
8136 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
8139 - Do not refuse to learn about authority certs and v2 networkstatus
8140 documents that are older than the latest consensus. This bug might
8141 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8142 Spotted and fixed by xmux.
8143 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
8144 trigger platform-specific option misparsing case found by Coverity
8146 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
8147 trigger assert. Fixes bug 1173.
8150 Changes in version 0.2.2.6-alpha - 2009-11-19
8151 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
8152 support for the new lower-footprint "microdescriptor" directory design,
8153 future-proofing our consensus format against new hash functions or
8154 other changes, and an Android port. It also makes Tor compatible with
8155 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
8158 - Directory authorities can now create, vote on, and serve multiple
8159 parallel formats of directory data as part of their voting process.
8160 Partially implements Proposal 162: "Publish the consensus in
8162 - Directory authorities can now agree on and publish small summaries
8163 of router information that clients can use in place of regular
8164 server descriptors. This transition will eventually allow clients
8165 to use far less bandwidth for downloading information about the
8166 network. Begins the implementation of Proposal 158: "Clients
8167 download consensus + microdescriptors".
8168 - The directory voting system is now extensible to use multiple hash
8169 algorithms for signatures and resource selection. Newer formats
8170 are signed with SHA256, with a possibility for moving to a better
8171 hash algorithm in the future.
8172 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8173 current and future memory pages via mlockall(). On supported
8174 platforms (modern Linux and probably BSD but not Windows or OS X),
8175 this should effectively disable any and all attempts to page out
8176 memory. This option requires that you start your Tor as root --
8177 if you use DisableAllSwap, please consider using the User option
8178 to properly reduce the privileges of your Tor.
8179 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8180 to help Tor build correctly for Android phones.
8183 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8184 handshake from working unless we explicitly tell OpenSSL that we
8185 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
8186 won't work unless we say we are.
8189 - Fix a crash bug when trying to initialize the evdns module in
8190 Libevent 2. Bugfix on 0.2.1.16-rc.
8191 - Stop logging at severity 'warn' when some other Tor client tries
8192 to establish a circuit with us using weak DH keys. It's a protocol
8193 violation, but that doesn't mean ordinary users need to hear about
8194 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
8195 - Do not refuse to learn about authority certs and v2 networkstatus
8196 documents that are older than the latest consensus. This bug might
8197 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8198 Spotted and fixed by xmux.
8199 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
8200 - If all authorities restart at once right before a consensus vote,
8201 nobody will vote about "Running", and clients will get a consensus
8202 with no usable relays. Instead, authorities refuse to build a
8203 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8204 - If your relay can't keep up with the number of incoming create
8205 cells, it would log one warning per failure into your logs. Limit
8206 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
8207 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8208 on 0.2.0.3-alpha; fixes bug 1113.
8209 - Fix a memory leak on directory authorities during voting that was
8210 introduced in 0.2.2.1-alpha. Found via valgrind.
8213 Changes in version 0.2.1.20 - 2009-10-15
8214 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
8215 services at once, prepares for more performance improvements, and
8216 fixes a bunch of smaller bugs.
8218 The Windows and OS X bundles also include a more recent Vidalia,
8219 and switch from Privoxy to Polipo.
8221 The OS X installers are now drag and drop. It's best to un-install
8222 Tor/Vidalia and then install this new bundle, rather than upgrade. If
8223 you want to upgrade, you'll need to update the paths for Tor and Polipo
8224 in the Vidalia Settings window.
8227 - Send circuit or stream sendme cells when our window has decreased
8228 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8229 by Karsten when testing the "reduce circuit window" performance
8230 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8231 before the release of Tor 0.0.0. This is the new winner of the
8233 - Fix a remotely triggerable memory leak when a consensus document
8234 contains more than one signature from the same voter. Bugfix on
8236 - Avoid segfault in rare cases when finishing an introduction circuit
8237 as a client and finding out that we don't have an introduction key
8238 for it. Fixes bug 1073. Reported by Aaron Swartz.
8241 - Tor now reads the "circwindow" parameter out of the consensus,
8242 and uses that value for its circuit package window rather than the
8243 default of 1000 cells. Begins the implementation of proposal 168.
8245 o New directory authorities:
8246 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8248 - Move moria1 and tonga to alternate IP addresses.
8251 - Fix a signed/unsigned compile warning in 0.2.1.19.
8252 - Fix possible segmentation fault on directory authorities. Bugfix on
8254 - Fix an extremely rare infinite recursion bug that could occur if
8255 we tried to log a message after shutting down the log subsystem.
8256 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8257 - Fix an obscure bug where hidden services on 64-bit big-endian
8258 systems might mis-read the timestamp in v3 introduce cells, and
8259 refuse to connect back to the client. Discovered by "rotor".
8260 Bugfix on 0.2.1.6-alpha.
8261 - We were triggering a CLOCK_SKEW controller status event whenever
8262 we connect via the v2 connection protocol to any relay that has
8263 a wrong clock. Instead, we should only inform the controller when
8264 it's a trusted authority that claims our clock is wrong. Bugfix
8265 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8266 - We were telling the controller about CHECKING_REACHABILITY and
8267 REACHABILITY_FAILED status events whenever we launch a testing
8268 circuit or notice that one has failed. Instead, only tell the
8269 controller when we want to inform the user of overall success or
8270 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8272 - Don't warn when we're using a circuit that ends with a node
8273 excluded in ExcludeExitNodes, but the circuit is not used to access
8274 the outside world. This should help fix bug 1090. Bugfix on
8276 - Work around a small memory leak in some versions of OpenSSL that
8277 stopped the memory used by the hostname TLS extension from being
8281 - Add a "getinfo status/accepted-server-descriptor" controller
8282 command, which is the recommended way for controllers to learn
8283 whether our server descriptor has been successfully received by at
8284 least on directory authority. Un-recommend good-server-descriptor
8285 getinfo and status events until we have a better design for them.
8288 Changes in version 0.2.2.5-alpha - 2009-10-11
8289 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
8292 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
8294 o Directory authorities:
8295 - Temporarily (just for this release) move dizum to an alternate
8299 Changes in version 0.2.2.4-alpha - 2009-10-10
8300 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
8301 introduces a new unit test framework, shifts directry authority
8302 addresses around to reduce the impact from recent blocking events,
8303 and fixes a few smaller bugs.
8306 - Fix several more asserts in the circuit_build_times code, for
8307 example one that causes Tor to fail to start once we have
8308 accumulated 5000 build times in the state file. Bugfixes on
8309 0.2.2.2-alpha; fixes bug 1108.
8311 o New directory authorities:
8312 - Move moria1 and Tonga to alternate IP addresses.
8315 - Log SSL state transitions at debug level during handshake, and
8316 include SSL states in error messages. This may help debug future
8317 SSL handshake issues.
8318 - Add a new "Handshake" log domain for activities that happen
8319 during the TLS handshake.
8320 - Revert to the "June 3 2009" ip-to-country file. The September one
8321 seems to have removed most US IP addresses.
8322 - Directory authorities now reject Tor relays with versions less than
8323 0.1.2.14. This step cuts out four relays from the current network,
8324 none of which are very big.
8327 - Fix a couple of smaller issues with gathering statistics. Bugfixes
8329 - Fix two memory leaks in the error case of
8330 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
8331 - Don't count one-hop circuits when we're estimating how long it
8332 takes circuits to build on average. Otherwise we'll set our circuit
8333 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
8334 - Directory authorities no longer change their opinion of, or vote on,
8335 whether a router is Running, unless they have themselves been
8336 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8339 o Code simplifications and refactoring:
8340 - Revise our unit tests to use the "tinytest" framework, so we
8341 can run tests in their own processes, have smarter setup/teardown
8342 code, and so on. The unit test code has moved to its own
8343 subdirectory, and has been split into multiple modules.
8346 Changes in version 0.2.2.3-alpha - 2009-09-23
8347 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
8350 - Fix an overzealous assert in our new circuit build timeout code.
8351 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
8354 - If the networkstatus consensus tells us that we should use a
8355 negative circuit package window, ignore it. Otherwise we'll
8356 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
8359 Changes in version 0.2.2.2-alpha - 2009-09-21
8360 Tor 0.2.2.2-alpha introduces our latest performance improvement for
8361 clients: Tor tracks the average time it takes to build a circuit, and
8362 avoids using circuits that take too long to build. For fast connections,
8363 this feature can cut your expected latency in half. For slow or flaky
8364 connections, it could ruin your Tor experience. Let us know if it does!
8367 - Tor now tracks how long it takes to build client-side circuits
8368 over time, and adapts its timeout to local network performance.
8369 Since a circuit that takes a long time to build will also provide
8370 bad performance, we get significant latency improvements by
8371 discarding the slowest 20% of circuits. Specifically, Tor creates
8372 circuits more aggressively than usual until it has enough data
8373 points for a good timeout estimate. Implements proposal 151.
8374 We are especially looking for reports (good and bad) from users with
8375 both EDGE and broadband connections that can move from broadband
8376 to EDGE and find out if the build-time data in the .tor/state gets
8377 reset without loss of Tor usability. You should also see a notice
8378 log message telling you that Tor has reset its timeout.
8379 - Directory authorities can now vote on arbitary integer values as
8380 part of the consensus process. This is designed to help set
8381 network-wide parameters. Implements proposal 167.
8382 - Tor now reads the "circwindow" parameter out of the consensus,
8383 and uses that value for its circuit package window rather than the
8384 default of 1000 cells. Begins the implementation of proposal 168.
8387 - Fix a remotely triggerable memory leak when a consensus document
8388 contains more than one signature from the same voter. Bugfix on
8392 - Fix an extremely rare infinite recursion bug that could occur if
8393 we tried to log a message after shutting down the log subsystem.
8394 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8395 - Fix parsing for memory or time units given without a space between
8396 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
8397 - A networkstatus vote must contain exactly one signature. Spec
8398 conformance issue. Bugfix on 0.2.0.3-alpha.
8399 - Fix an obscure bug where hidden services on 64-bit big-endian
8400 systems might mis-read the timestamp in v3 introduce cells, and
8401 refuse to connect back to the client. Discovered by "rotor".
8402 Bugfix on 0.2.1.6-alpha.
8403 - We were triggering a CLOCK_SKEW controller status event whenever
8404 we connect via the v2 connection protocol to any relay that has
8405 a wrong clock. Instead, we should only inform the controller when
8406 it's a trusted authority that claims our clock is wrong. Bugfix
8407 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8408 - We were telling the controller about CHECKING_REACHABILITY and
8409 REACHABILITY_FAILED status events whenever we launch a testing
8410 circuit or notice that one has failed. Instead, only tell the
8411 controller when we want to inform the user of overall success or
8412 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8414 - Don't warn when we're using a circuit that ends with a node
8415 excluded in ExcludeExitNodes, but the circuit is not used to access
8416 the outside world. This should help fix bug 1090, but more problems
8417 remain. Bugfix on 0.2.1.6-alpha.
8418 - Work around a small memory leak in some versions of OpenSSL that
8419 stopped the memory used by the hostname TLS extension from being
8421 - Make our 'torify' script more portable; if we have only one of
8422 'torsocks' or 'tsocks' installed, don't complain to the user;
8423 and explain our warning about tsocks better.
8426 - Add a "getinfo status/accepted-server-descriptor" controller
8427 command, which is the recommended way for controllers to learn
8428 whether our server descriptor has been successfully received by at
8429 least on directory authority. Un-recommend good-server-descriptor
8430 getinfo and status events until we have a better design for them.
8431 - Update to the "September 4 2009" ip-to-country file.
8434 Changes in version 0.2.2.1-alpha - 2009-08-26
8435 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
8436 Tor clients to bootstrap on networks where only port 80 is reachable,
8437 makes it more straightforward to support hardware crypto accelerators,
8438 and starts the groundwork for gathering stats safely at relays.
8441 - Start the process of disabling ".exit" address notation, since it
8442 can be used for a variety of esoteric application-level attacks
8443 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8446 o New directory authorities:
8447 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8451 - New AccelName and AccelDir options add support for dynamic OpenSSL
8452 hardware crypto acceleration engines.
8453 - Tor now supports tunneling all of its outgoing connections over
8454 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8455 configuration options. Code by Christopher Davis.
8458 - Send circuit or stream sendme cells when our window has decreased
8459 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8460 by Karsten when testing the "reduce circuit window" performance
8461 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8462 before the release of Tor 0.0.0. This is the new winner of the
8465 o New options for gathering stats safely:
8466 - Directory mirrors that set "DirReqStatistics 1" write statistics
8467 about directory requests to disk every 24 hours. As compared to the
8468 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
8469 1) stats are written to disk exactly every 24 hours; 2) estimated
8470 shares of v2 and v3 requests are determined as mean values, not at
8471 the end of a measurement period; 3) unresolved requests are listed
8472 with country code '??'; 4) directories also measure download times.
8473 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8474 number of exit streams and transferred bytes per port to disk every
8476 - Relays that set "CellStatistics 1" write statistics on how long
8477 cells spend in their circuit queues to disk every 24 hours.
8478 - Entry nodes that set "EntryStatistics 1" write statistics on the
8479 rough number and origins of connecting clients to disk every 24
8481 - Relays that write any of the above statistics to disk and set
8482 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8483 their extra-info documents.
8486 - New --digests command-line switch to output the digests of the
8487 source files Tor was built with.
8488 - The "torify" script now uses torsocks where available.
8489 - The memarea code now uses a sentinel value at the end of each area
8490 to make sure nothing writes beyond the end of an area. This might
8491 help debug some conceivable causes of bug 930.
8492 - Time and memory units in the configuration file can now be set to
8493 fractional units. For example, "2.5 GB" is now a valid value for
8495 - Certain Tor clients (such as those behind check.torproject.org) may
8496 want to fetch the consensus in an extra early manner. To enable this
8497 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8498 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8499 as only certain clients who must have this information sooner should
8501 - Instead of adding the svn revision to the Tor version string, report
8502 the git commit (when we're building from a git checkout).
8505 - If any of the v3 certs we download are unparseable, we should
8506 actually notice the failure so we don't retry indefinitely. Bugfix
8507 on 0.2.0.x; reported by "rotator".
8508 - If the cached cert file is unparseable, warn but don't exit.
8509 - Fix possible segmentation fault on directory authorities. Bugfix on
8511 - When Tor fails to parse a descriptor of any kind, dump it to disk.
8512 Might help diagnosing bug 1051.
8514 o Deprecated and removed features:
8515 - The controller no longer accepts the old obsolete "addr-mappings/"
8516 or "unregistered-servers-" GETINFO values.
8517 - Hidden services no longer publish version 0 descriptors, and clients
8518 do not request or use version 0 descriptors. However, the old hidden
8519 service authorities still accept and serve version 0 descriptors
8520 when contacted by older hidden services/clients.
8521 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
8522 always on; using them is necessary for correct forward-compatible
8524 - Remove support for .noconnect style addresses. Nobody was using
8525 them, and they provided another avenue for detecting Tor users
8526 via application-level web tricks.
8528 o Packaging changes:
8529 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
8530 installer bundles. See
8531 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
8532 for details of what's new in Vidalia 0.2.3.
8533 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
8534 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
8535 configuration file, rather than the old Privoxy.
8536 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
8537 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
8538 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
8539 better compatibility with OS X 10.6, aka Snow Leopard.
8540 - OS X Vidalia Bundle: The multi-package installer is now replaced
8541 by a simple drag and drop to the /Applications folder. This change
8542 occurred with the upgrade to Vidalia 0.2.3.
8545 Changes in version 0.2.1.19 - 2009-07-28
8546 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
8547 services on Tor 0.2.1.3-alpha through 0.2.1.18.
8550 - Make accessing hidden services on 0.2.1.x work right again.
8551 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
8552 part of patch provided by "optimist".
8555 - When a relay/bridge is writing out its identity key fingerprint to
8556 the "fingerprint" file and to its logs, write it without spaces. Now
8557 it will look like the fingerprints in our bridges documentation,
8558 and confuse fewer users.
8561 - Relays no longer publish a new server descriptor if they change
8562 their MaxAdvertisedBandwidth config option but it doesn't end up
8563 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
8564 fixes bug 1026. Patch from Sebastian.
8565 - Avoid leaking memory every time we get a create cell but we have
8566 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
8567 fixes bug 1034. Reported by BarkerJr.
8570 Changes in version 0.2.1.18 - 2009-07-24
8571 Tor 0.2.1.18 lays the foundations for performance improvements,
8572 adds status events to help users diagnose bootstrap problems, adds
8573 optional authentication/authorization for hidden services, fixes a
8574 variety of potential anonymity problems, and includes a huge pile of
8575 other features and bug fixes.
8578 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8581 Changes in version 0.2.1.17-rc - 2009-07-07
8582 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
8583 candidate for the 0.2.1.x series. It lays the groundwork for further
8584 client performance improvements, and also fixes a big bug with directory
8585 authorities that were causing them to assign Guard and Stable flags
8588 The Windows bundles also finally include the geoip database that we
8589 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
8590 should actually install Torbutton rather than giving you a cryptic
8591 failure message (oops).
8594 - Clients now use the bandwidth values in the consensus, rather than
8595 the bandwidth values in each relay descriptor. This approach opens
8596 the door to more accurate bandwidth estimates once the directory
8597 authorities start doing active measurements. Implements more of
8601 - When Tor clients restart after 1-5 days, they discard all their
8602 cached descriptors as too old, but they still use the cached
8603 consensus document. This approach is good for robustness, but
8604 bad for performance: since they don't know any bandwidths, they
8605 end up choosing at random rather than weighting their choice by
8606 speed. Fixed by the above feature of putting bandwidths in the
8607 consensus. Bugfix on 0.2.0.x.
8608 - Directory authorities were neglecting to mark relays down in their
8609 internal histories if the relays fall off the routerlist without
8610 ever being found unreachable. So there were relays in the histories
8611 that haven't been seen for eight months, and are listed as being
8612 up for eight months. This wreaked havoc on the "median wfu"
8613 and "median mtbf" calculations, in turn making Guard and Stable
8614 flags very wrong, hurting network performance. Fixes bugs 696 and
8615 969. Bugfix on 0.2.0.6-alpha.
8618 - Serve the DirPortFrontPage page even when we have been approaching
8619 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
8620 - The control port would close the connection before flushing long
8621 replies, such as the network consensus, if a QUIT command was issued
8622 before the reply had completed. Now, the control port flushes all
8623 pending replies before closing the connection. Also fixed a spurious
8624 warning when a QUIT command is issued after a malformed or rejected
8625 AUTHENTICATE command, but before the connection was closed. Patch
8626 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
8627 - When we can't find an intro key for a v2 hidden service descriptor,
8628 fall back to the v0 hidden service descriptor and log a bug message.
8629 Workaround for bug 1024.
8630 - Fix a log message that did not respect the SafeLogging option.
8634 - If we're a relay and we change our IP address, be more verbose
8635 about the reason that made us change. Should help track down
8636 further bugs for relays on dynamic IP addresses.
8639 Changes in version 0.2.0.35 - 2009-06-24
8641 - Avoid crashing in the presence of certain malformed descriptors.
8642 Found by lark, and by automated fuzzing.
8643 - Fix an edge case where a malicious exit relay could convince a
8644 controller that the client's DNS question resolves to an internal IP
8645 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8648 - Finally fix the bug where dynamic-IP relays disappear when their
8649 IP address changes: directory mirrors were mistakenly telling
8650 them their old address if they asked via begin_dir, so they
8651 never got an accurate answer about their new address, so they
8652 just vanished after a day. For belt-and-suspenders, relays that
8653 don't set Address in their config now avoid using begin_dir for
8654 all direct connections. Should fix bugs 827, 883, and 900.
8655 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8656 that would occur on some exit nodes when DNS failures and timeouts
8657 occurred in certain patterns. Fix for bug 957.
8660 - When starting with a cache over a few days old, do not leak
8661 memory for the obsolete router descriptors in it. Bugfix on
8662 0.2.0.33; fixes bug 672.
8663 - Hidden service clients didn't use a cached service descriptor that
8664 was older than 15 minutes, but wouldn't fetch a new one either,
8665 because there was already one in the cache. Now, fetch a v2
8666 descriptor unless the same descriptor was added to the cache within
8667 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8670 Changes in version 0.2.1.16-rc - 2009-06-20
8671 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
8672 a bunch of minor bugs.
8675 - Fix an edge case where a malicious exit relay could convince a
8676 controller that the client's DNS question resolves to an internal IP
8677 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
8679 o Major performance improvements (on 0.2.0.x):
8680 - Disable and refactor some debugging checks that forced a linear scan
8681 over the whole server-side DNS cache. These accounted for over 50%
8682 of CPU time on a relatively busy exit node's gprof profile. Found
8684 - Disable some debugging checks that appeared in exit node profile
8688 - Update to the "June 3 2009" ip-to-country file.
8689 - Do not have tor-resolve automatically refuse all .onion addresses;
8690 if AutomapHostsOnResolve is set in your torrc, this will work fine.
8692 o Minor bugfixes (on 0.2.0.x):
8693 - Log correct error messages for DNS-related network errors on
8695 - Fix a race condition that could cause crashes or memory corruption
8696 when running as a server with a controller listening for log
8698 - Avoid crashing when we have a policy specified in a DirPolicy or
8699 SocksPolicy or ReachableAddresses option with ports set on it,
8700 and we re-load the policy. May fix bug 996.
8701 - Hidden service clients didn't use a cached service descriptor that
8702 was older than 15 minutes, but wouldn't fetch a new one either,
8703 because there was already one in the cache. Now, fetch a v2
8704 descriptor unless the same descriptor was added to the cache within
8705 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
8707 o Minor bugfixes (on 0.2.1.x):
8708 - Don't warn users about low port and hibernation mix when they
8709 provide a *ListenAddress directive to fix that. Bugfix on
8711 - When switching back and forth between bridge mode, do not start
8712 gathering GeoIP data until two hours have passed.
8713 - Do not complain that the user has requested an excluded node as
8714 an exit when the node is not really an exit. This could happen
8715 because the circuit was for testing, or an introduction point.
8719 Changes in version 0.2.1.15-rc - 2009-05-25
8720 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
8721 series. It fixes a major bug on fast exit relays, as well as a variety
8724 o Major bugfixes (on 0.2.0.x):
8725 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
8726 that would occur on some exit nodes when DNS failures and timeouts
8727 occurred in certain patterns. Fix for bug 957.
8729 o Minor bugfixes (on 0.2.0.x):
8730 - Actually return -1 in the error case for read_bandwidth_usage().
8731 Harmless bug, since we currently don't care about the return value
8732 anywhere. Bugfix on 0.2.0.9-alpha.
8733 - Provide a more useful log message if bug 977 (related to buffer
8734 freelists) ever reappears, and do not crash right away.
8735 - Fix an assertion failure on 64-bit platforms when we allocated
8736 memory right up to the end of a memarea, then realigned the memory
8737 one step beyond the end. Fixes a possible cause of bug 930.
8738 - Protect the count of open sockets with a mutex, so we can't
8739 corrupt it when two threads are closing or opening sockets at once.
8740 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
8741 - Don't allow a bridge to publish its router descriptor to a
8742 non-bridge directory authority. Fixes part of bug 932.
8743 - When we change to or from being a bridge, reset our counts of
8744 client usage by country. Fixes bug 932.
8745 - Fix a bug that made stream bandwidth get misreported to the
8747 - Stop using malloc_usable_size() to use more area than we had
8748 actually allocated: it was safe, but made valgrind really unhappy.
8749 - Fix a memory leak when v3 directory authorities load their keys
8750 and cert from disk. Bugfix on 0.2.0.1-alpha.
8752 o Minor bugfixes (on 0.2.1.x):
8753 - Fix use of freed memory when deciding to mark a non-addable
8754 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
8757 Changes in version 0.2.1.14-rc - 2009-04-12
8758 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
8759 series. It begins fixing some major performance problems, and also
8760 finally addresses the bug that was causing relays on dynamic IP
8761 addresses to fall out of the directory.
8764 - Clients replace entry guards that were chosen more than a few months
8765 ago. This change should significantly improve client performance,
8766 especially once more people upgrade, since relays that have been
8767 a guard for a long time are currently overloaded.
8769 o Major bugfixes (on 0.2.0):
8770 - Finally fix the bug where dynamic-IP relays disappear when their
8771 IP address changes: directory mirrors were mistakenly telling
8772 them their old address if they asked via begin_dir, so they
8773 never got an accurate answer about their new address, so they
8774 just vanished after a day. For belt-and-suspenders, relays that
8775 don't set Address in their config now avoid using begin_dir for
8776 all direct connections. Should fix bugs 827, 883, and 900.
8777 - Relays were falling out of the networkstatus consensus for
8778 part of a day if they changed their local config but the
8779 authorities discarded their new descriptor as "not sufficiently
8780 different". Now directory authorities accept a descriptor as changed
8781 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
8783 - Avoid crashing in the presence of certain malformed descriptors.
8784 Found by lark, and by automated fuzzing.
8787 - When generating circuit events with verbose nicknames for
8788 controllers, try harder to look up nicknames for routers on a
8789 circuit. (Previously, we would look in the router descriptors we had
8790 for nicknames, but not in the consensus.) Partial fix for bug 941.
8791 - If the bridge config line doesn't specify a port, assume 443.
8792 This makes bridge lines a bit smaller and easier for users to
8794 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
8795 bytes (aka 20KB/s), to match our documentation. Also update
8796 directory authorities so they always assign the Fast flag to relays
8797 with 20KB/s of capacity. Now people running relays won't suddenly
8798 find themselves not seeing any use, if the network gets faster
8800 - Update to the "April 3 2009" ip-to-country file.
8803 - Avoid trying to print raw memory to the logs when we decide to
8804 give up on downloading a given relay descriptor. Bugfix on
8806 - In tor-resolve, when the Tor client to use is specified by
8807 <hostname>:<port>, actually use the specified port rather than
8808 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
8809 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
8810 - When starting with a cache over a few days old, do not leak
8811 memory for the obsolete router descriptors in it. Bugfix on
8813 - Avoid double-free on list of successfully uploaded hidden
8814 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
8815 - Change memarea_strndup() implementation to work even when
8816 duplicating a string at the end of a page. This bug was
8817 harmless for now, but could have meant crashes later. Fix by
8818 lark. Bugfix on 0.2.1.1-alpha.
8819 - Limit uploaded directory documents to be 16M rather than 500K.
8820 The directory authorities were refusing v3 consensus votes from
8821 other authorities, since the votes are now 504K. Fixes bug 959;
8822 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
8823 - Directory authorities should never send a 503 "busy" response to
8824 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
8828 Changes in version 0.2.1.13-alpha - 2009-03-09
8829 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
8830 cleanups. We're finally getting close to a release candidate.
8833 - Correctly update the list of which countries we exclude as
8834 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
8835 lark. Bugfix on 0.2.1.6-alpha.
8837 o Minor bugfixes (on 0.2.0.x and earlier):
8838 - Automatically detect MacOSX versions earlier than 10.4.0, and
8839 disable kqueue from inside Tor when running with these versions.
8840 We previously did this from the startup script, but that was no
8841 help to people who didn't use the startup script. Resolves bug 863.
8842 - When we had picked an exit node for a connection, but marked it as
8843 "optional", and it turned out we had no onion key for the exit,
8844 stop wanting that exit and try again. This situation may not
8845 be possible now, but will probably become feasible with proposal
8846 158. Spotted by rovv. Fixes another case of bug 752.
8847 - Clients no longer cache certificates for authorities they do not
8848 recognize. Bugfix on 0.2.0.9-alpha.
8849 - When we can't transmit a DNS request due to a network error, retry
8850 it after a while, and eventually transmit a failing response to
8851 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
8852 - If the controller claimed responsibility for a stream, but that
8853 stream never finished making its connection, it would live
8854 forever in circuit_wait state. Now we close it after SocksTimeout
8855 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
8856 - Drop begin cells to a hidden service if they come from the middle
8857 of a circuit. Patch from lark.
8858 - When we erroneously receive two EXTEND cells for the same circuit
8859 ID on the same connection, drop the second. Patch from lark.
8860 - Fix a crash that occurs on exit nodes when a nameserver request
8861 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
8862 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
8864 - Do not assume that a stack-allocated character array will be
8865 64-bit aligned on platforms that demand that uint64_t access is
8866 aligned. Possible fix for bug 604.
8867 - Parse dates and IPv4 addresses in a locale- and libc-independent
8868 manner, to avoid platform-dependent behavior on malformed input.
8869 - Build correctly when configured to build outside the main source
8870 path. Patch from Michael Gold.
8871 - We were already rejecting relay begin cells with destination port
8872 of 0. Now also reject extend cells with destination port or address
8873 of 0. Suggested by lark.
8875 o Minor bugfixes (on 0.2.1.x):
8876 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
8877 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
8878 - If we're an exit node, scrub the IP address to which we are exiting
8879 in the logs. Bugfix on 0.2.1.8-alpha.
8882 - On Linux, use the prctl call to re-enable core dumps when the user
8884 - New controller event NEWCONSENSUS that lists the networkstatus
8885 lines for every recommended relay. Now controllers like Torflow
8886 can keep up-to-date on which relays they should be using.
8887 - Update to the "February 26 2009" ip-to-country file.
8890 Changes in version 0.2.0.34 - 2009-02-08
8891 Tor 0.2.0.34 features several more security-related fixes. You should
8892 upgrade, especially if you run an exit relay (remote crash) or a
8893 directory authority (remote infinite loop), or you're on an older
8894 (pre-XP) or not-recently-patched Windows (remote exploit).
8896 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
8897 have many known flaws, and nobody should be using them. You should
8898 upgrade. If you're using a Linux or BSD and its packages are obsolete,
8899 stop using those packages and upgrade anyway.
8902 - Fix an infinite-loop bug on handling corrupt votes under certain
8903 circumstances. Bugfix on 0.2.0.8-alpha.
8904 - Fix a temporary DoS vulnerability that could be performed by
8905 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8906 - Avoid a potential crash on exit nodes when processing malformed
8907 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
8908 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8909 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8912 - Fix compilation on systems where time_t is a 64-bit integer.
8913 Patch from Matthias Drochner.
8914 - Don't consider expiring already-closed client connections. Fixes
8915 bug 893. Bugfix on 0.0.2pre20.
8918 Changes in version 0.2.1.12-alpha - 2009-02-08
8919 Tor 0.2.1.12-alpha features several more security-related fixes. You
8920 should upgrade, especially if you run an exit relay (remote crash) or
8921 a directory authority (remote infinite loop), or you're on an older
8922 (pre-XP) or not-recently-patched Windows (remote exploit). It also
8923 includes a big pile of minor bugfixes and cleanups.
8926 - Fix an infinite-loop bug on handling corrupt votes under certain
8927 circumstances. Bugfix on 0.2.0.8-alpha.
8928 - Fix a temporary DoS vulnerability that could be performed by
8929 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
8930 - Avoid a potential crash on exit nodes when processing malformed
8931 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
8934 - Let controllers actually ask for the "clients_seen" event for
8935 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
8936 reported by Matt Edman.
8937 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
8939 - Fix a bug in address parsing that was preventing bridges or hidden
8940 service targets from being at IPv6 addresses.
8941 - Solve a bug that kept hardware crypto acceleration from getting
8942 enabled when accounting was turned on. Fixes bug 907. Bugfix on
8944 - Remove a bash-ism from configure.in to build properly on non-Linux
8945 platforms. Bugfix on 0.2.1.1-alpha.
8946 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
8947 headers. Bugfix on 0.2.0.10-alpha.
8948 - Don't consider expiring already-closed client connections. Fixes
8949 bug 893. Bugfix on 0.0.2pre20.
8950 - Fix another interesting corner-case of bug 891 spotted by rovv:
8951 Previously, if two hosts had different amounts of clock drift, and
8952 one of them created a new connection with just the wrong timing,
8953 the other might decide to deprecate the new connection erroneously.
8954 Bugfix on 0.1.1.13-alpha.
8955 - Resolve a very rare crash bug that could occur when the user forced
8956 a nameserver reconfiguration during the middle of a nameserver
8957 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
8958 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
8959 Bugfix on 0.2.1.7-alpha.
8960 - If we're using bridges and our network goes away, be more willing
8961 to forgive our bridges and try again when we get an application
8962 request. Bugfix on 0.2.0.x.
8965 - Support platforms where time_t is 64 bits long. (Congratulations,
8966 NetBSD!) Patch from Matthias Drochner.
8967 - Add a 'getinfo status/clients-seen' controller command, in case
8968 controllers want to hear clients_seen events but connect late.
8971 - Disable GCC's strict alias optimization by default, to avoid the
8972 likelihood of its introducing subtle bugs whenever our code violates
8973 the letter of C99's alias rules.
8976 Changes in version 0.2.0.33 - 2009-01-21
8977 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8978 useful to users. It also finally fixes a bug where a relay or client
8979 that's been off for many days would take a long time to bootstrap.
8981 This update also fixes an important security-related bug reported by
8982 Ilja van Sprundel. You should upgrade. (We'll send out more details
8983 about the bug once people have had some time to upgrade.)
8986 - Fix a heap-corruption bug that may be remotely triggerable on
8987 some platforms. Reported by Ilja van Sprundel.
8990 - When a stream at an exit relay is in state "resolving" or
8991 "connecting" and it receives an "end" relay cell, the exit relay
8992 would silently ignore the end cell and not close the stream. If
8993 the client never closes the circuit, then the exit relay never
8994 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
8996 - When sending CREATED cells back for a given circuit, use a 64-bit
8997 connection ID to find the right connection, rather than an addr:port
8998 combination. Now that we can have multiple OR connections between
8999 the same ORs, it is no longer possible to use addr:port to uniquely
9000 identify a connection.
9001 - Bridge relays that had DirPort set to 0 would stop fetching
9002 descriptors shortly after startup, and then briefly resume
9003 after a new bandwidth test and/or after publishing a new bridge
9004 descriptor. Bridge users that try to bootstrap from them would
9005 get a recent networkstatus but would get descriptors from up to
9006 18 hours earlier, meaning most of the descriptors were obsolete
9007 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9008 - Prevent bridge relays from serving their 'extrainfo' document
9009 to anybody who asks, now that extrainfo docs include potentially
9010 sensitive aggregated client geoip summaries. Bugfix on
9012 - If the cached networkstatus consensus is more than five days old,
9013 discard it rather than trying to use it. In theory it could be
9014 useful because it lists alternate directory mirrors, but in practice
9015 it just means we spend many minutes trying directory mirrors that
9016 are long gone from the network. Also discard router descriptors as
9017 we load them if they are more than five days old, since the onion
9018 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
9021 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9022 could make gcc generate non-functional binary search code. Bugfix
9024 - Build correctly on platforms without socklen_t.
9025 - Compile without warnings on solaris.
9026 - Avoid potential crash on internal error during signature collection.
9027 Fixes bug 864. Patch from rovv.
9028 - Correct handling of possible malformed authority signing key
9029 certificates with internal signature types. Fixes bug 880.
9030 Bugfix on 0.2.0.3-alpha.
9031 - Fix a hard-to-trigger resource leak when logging credential status.
9033 - When we can't initialize DNS because the network is down, do not
9034 automatically stop Tor from starting. Instead, we retry failed
9035 dns_init() every 10 minutes, and change the exit policy to reject
9036 *:* until one succeeds. Fixes bug 691.
9037 - Use 64 bits instead of 32 bits for connection identifiers used with
9038 the controller protocol, to greatly reduce risk of identifier reuse.
9039 - When we're choosing an exit node for a circuit, and we have
9040 no pending streams, choose a good general exit rather than one that
9041 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9042 - Fix another case of assuming, when a specific exit is requested,
9043 that we know more than the user about what hosts it allows.
9044 Fixes one case of bug 752. Patch from rovv.
9045 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9046 seconds. Warn the user if lower values are given in the
9047 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9048 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9049 user if lower values are given in the configuration. Bugfix on
9050 0.1.1.17-rc. Patch by Sebastian.
9051 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
9052 the cache because we already had a v0 descriptor with the same ID.
9053 Bugfix on 0.2.0.18-alpha.
9054 - Fix a race condition when freeing keys shared between main thread
9055 and CPU workers that could result in a memory leak. Bugfix on
9056 0.1.0.1-rc. Fixes bug 889.
9057 - Send a valid END cell back when a client tries to connect to a
9058 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9059 840. Patch from rovv.
9060 - Check which hops rendezvous stream cells are associated with to
9061 prevent possible guess-the-streamid injection attacks from
9062 intermediate hops. Fixes another case of bug 446. Based on patch
9064 - If a broken client asks a non-exit router to connect somewhere,
9065 do not even do the DNS lookup before rejecting the connection.
9066 Fixes another case of bug 619. Patch from rovv.
9067 - When a relay gets a create cell it can't decrypt (e.g. because it's
9068 using the wrong onion key), we were dropping it and letting the
9069 client time out. Now actually answer with a destroy cell. Fixes
9070 bug 904. Bugfix on 0.0.2pre8.
9072 o Minor bugfixes (hidden services):
9073 - Do not throw away existing introduction points on SIGHUP. Bugfix on
9074 0.0.6pre1. Patch by Karsten. Fixes bug 874.
9077 - Report the case where all signatures in a detached set are rejected
9078 differently than the case where there is an error handling the
9080 - When we realize that another process has modified our cached
9081 descriptors, print out a more useful error message rather than
9082 triggering an assertion. Fixes bug 885. Patch from Karsten.
9083 - Implement the 0x20 hack to better resist DNS poisoning: set the
9084 case on outgoing DNS requests randomly, and reject responses that do
9085 not match the case correctly. This logic can be disabled with the
9086 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
9087 of servers that do not reliably preserve case in replies. See
9088 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9090 - Check DNS replies for more matching fields to better resist DNS
9092 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9093 compress cells, which are basically all encrypted, compressed, or
9097 Changes in version 0.2.1.11-alpha - 2009-01-20
9098 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
9099 week it will take a long time to bootstrap again" bug. It also fixes
9100 an important security-related bug reported by Ilja van Sprundel. You
9101 should upgrade. (We'll send out more details about the bug once people
9102 have had some time to upgrade.)
9105 - Fix a heap-corruption bug that may be remotely triggerable on
9106 some platforms. Reported by Ilja van Sprundel.
9109 - Discard router descriptors as we load them if they are more than
9110 five days old. Otherwise if Tor is off for a long time and then
9111 starts with cached descriptors, it will try to use the onion
9112 keys in those obsolete descriptors when building circuits. Bugfix
9113 on 0.2.0.x. Fixes bug 887.
9116 - Try to make sure that the version of Libevent we're running with
9117 is binary-compatible with the one we built with. May address bug
9119 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
9120 for bug 905. Bugfix on 0.2.1.7-alpha.
9121 - Add a new --enable-local-appdata configuration switch to change
9122 the default location of the datadir on win32 from APPDATA to
9123 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
9124 entirely. Patch from coderman.
9127 - Make outbound DNS packets respect the OutboundBindAddress setting.
9128 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9129 - When our circuit fails at the first hop (e.g. we get a destroy
9130 cell back), avoid using that OR connection anymore, and also
9131 tell all the one-hop directory requests waiting for it that they
9132 should fail. Bugfix on 0.2.1.3-alpha.
9133 - In the torify(1) manpage, mention that tsocks will leak your
9137 Changes in version 0.2.1.10-alpha - 2009-01-06
9138 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
9139 would make the bridge relay not so useful if it had DirPort set to 0,
9140 and one that could let an attacker learn a little bit of information
9141 about the bridge's users), and a bug that would cause your Tor relay
9142 to ignore a circuit create request it can't decrypt (rather than reply
9143 with an error). It also fixes a wide variety of other bugs.
9146 - If the cached networkstatus consensus is more than five days old,
9147 discard it rather than trying to use it. In theory it could
9148 be useful because it lists alternate directory mirrors, but in
9149 practice it just means we spend many minutes trying directory
9150 mirrors that are long gone from the network. Helps bug 887 a bit;
9152 - Bridge relays that had DirPort set to 0 would stop fetching
9153 descriptors shortly after startup, and then briefly resume
9154 after a new bandwidth test and/or after publishing a new bridge
9155 descriptor. Bridge users that try to bootstrap from them would
9156 get a recent networkstatus but would get descriptors from up to
9157 18 hours earlier, meaning most of the descriptors were obsolete
9158 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9159 - Prevent bridge relays from serving their 'extrainfo' document
9160 to anybody who asks, now that extrainfo docs include potentially
9161 sensitive aggregated client geoip summaries. Bugfix on
9165 - New controller event "clients_seen" to report a geoip-based summary
9166 of which countries we've seen clients from recently. Now controllers
9167 like Vidalia can show bridge operators that they're actually making
9169 - Build correctly against versions of OpenSSL 0.9.8 or later built
9170 without support for deprecated functions.
9171 - Update to the "December 19 2008" ip-to-country file.
9173 o Minor bugfixes (on 0.2.0.x):
9174 - Authorities now vote for the Stable flag for any router whose
9175 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9176 - Do not remove routers as too old if we do not have any consensus
9177 document. Bugfix on 0.2.0.7-alpha.
9178 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9179 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9180 - When an exit relay resolves a stream address to a local IP address,
9181 do not just keep retrying that same exit relay over and
9182 over. Instead, just close the stream. Addresses bug 872. Bugfix
9183 on 0.2.0.32. Patch from rovv.
9184 - If a hidden service sends us an END cell, do not consider
9185 retrying the connection; just close it. Patch from rovv.
9186 - When we made bridge authorities stop serving bridge descriptors over
9187 unencrypted links, we also broke DirPort reachability testing for
9188 bridges. So bridges with a non-zero DirPort were printing spurious
9189 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
9190 - When a relay gets a create cell it can't decrypt (e.g. because it's
9191 using the wrong onion key), we were dropping it and letting the
9192 client time out. Now actually answer with a destroy cell. Fixes
9193 bug 904. Bugfix on 0.0.2pre8.
9194 - Squeeze 2-5% out of client performance (according to oprofile) by
9195 improving the implementation of some policy-manipulation functions.
9197 o Minor bugfixes (on 0.2.1.x):
9198 - Make get_interface_address() function work properly again; stop
9199 guessing the wrong parts of our address as our address.
9200 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
9201 send on that circuit. Otherwise we might violate the proposal-110
9202 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
9204 - When we're sending non-EXTEND cells to the first hop in a circuit,
9205 for example to use an encrypted directory connection, we don't need
9206 to use RELAY_EARLY cells: the first hop knows what kind of cell
9207 it is, and nobody else can even see the cell type. Conserving
9208 RELAY_EARLY cells makes it easier to cannibalize circuits like
9210 - Stop logging nameserver addresses in reverse order.
9211 - If we are retrying a directory download slowly over and over, do
9212 not automatically give up after the 254th failure. Bugfix on
9214 - Resume reporting accurate "stream end" reasons to the local control
9215 port. They were lost in the changes for Proposal 148. Bugfix on
9218 o Deprecated and removed features:
9219 - The old "tor --version --version" command, which would print out
9220 the subversion "Id" of most of the source files, is now removed. It
9221 turned out to be less useful than we'd expected, and harder to
9224 o Code simplifications and refactoring:
9225 - Change our header file guard macros to be less likely to conflict
9226 with system headers. Adam Langley noticed that we were conflicting
9227 with log.h on Android.
9228 - Tool-assisted documentation cleanup. Nearly every function or
9229 static variable in Tor should have its own documentation now.
9232 Changes in version 0.2.1.9-alpha - 2008-12-25
9233 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
9235 o New directory authorities:
9236 - gabelmoo (the authority run by Karsten Loesing) now has a new
9240 - Never use a connection with a mismatched address to extend a
9241 circuit, unless that connection is canonical. A canonical
9242 connection is one whose address is authenticated by the router's
9243 identity key, either in a NETINFO cell or in a router descriptor.
9244 - Avoid a possible memory corruption bug when receiving hidden service
9245 descriptors. Bugfix on 0.2.1.6-alpha.
9248 - Fix a logic error that would automatically reject all but the first
9249 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
9250 part of bug 813/868. Bug spotted by coderman.
9251 - When a stream at an exit relay is in state "resolving" or
9252 "connecting" and it receives an "end" relay cell, the exit relay
9253 would silently ignore the end cell and not close the stream. If
9254 the client never closes the circuit, then the exit relay never
9255 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
9257 - When we can't initialize DNS because the network is down, do not
9258 automatically stop Tor from starting. Instead, retry failed
9259 dns_init() every 10 minutes, and change the exit policy to reject
9260 *:* until one succeeds. Fixes bug 691.
9263 - Give a better error message when an overzealous init script says
9264 "sudo -u username tor --user username". Makes Bug 882 easier for
9266 - When a directory authority gives us a new guess for our IP address,
9267 log which authority we used. Hopefully this will help us debug
9268 the recent complaints about bad IP address guesses.
9269 - Detect svn revision properly when we're using git-svn.
9270 - Try not to open more than one descriptor-downloading connection
9271 to an authority at once. This should reduce load on directory
9272 authorities. Fixes bug 366.
9273 - Add cross-certification to newly generated certificates, so that
9274 a signing key is enough information to look up a certificate.
9275 Partial implementation of proposal 157.
9276 - Start serving certificates by <identity digest, signing key digest>
9277 pairs. Partial implementation of proposal 157.
9278 - Clients now never report any stream end reason except 'MISC'.
9279 Implements proposal 148.
9280 - On platforms with a maximum syslog string length, truncate syslog
9281 messages to that length ourselves, rather than relying on the
9282 system to do it for us.
9283 - Optimize out calls to time(NULL) that occur for every IO operation,
9284 or for every cell. On systems where time() is a slow syscall,
9285 this fix will be slightly helpful.
9286 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9287 - When we download a descriptor that we then immediately (as
9288 a directory authority) reject, do not retry downloading it right
9289 away. Should save some bandwidth on authorities. Fix for bug
9290 888. Patch by Sebastian Hahn.
9291 - When a download gets us zero good descriptors, do not notify
9292 Tor that new directory information has arrived.
9293 - Avoid some nasty corner cases in the logic for marking connections
9294 as too old or obsolete or noncanonical for circuits. Partial
9297 o Minor features (controller):
9298 - New CONSENSUS_ARRIVED event to note when a new consensus has
9299 been fetched and validated.
9300 - When we realize that another process has modified our cached
9301 descriptors file, print out a more useful error message rather
9302 than triggering an assertion. Fixes bug 885. Patch from Karsten.
9303 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
9304 controllers to prevent SIGHUP from reloading the
9305 configuration. Fixes bug 856.
9308 - Resume using the correct "REASON=" stream when telling the
9309 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
9310 - When a canonical connection appears later in our internal list
9311 than a noncanonical one for a given OR ID, always use the
9312 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
9314 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9315 seconds. Warn the user if lower values are given in the
9316 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9317 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9318 user if lower values are given in the configuration. Bugfix on
9319 0.1.1.17-rc. Patch by Sebastian.
9320 - Fix a race condition when freeing keys shared between main thread
9321 and CPU workers that could result in a memory leak. Bugfix on
9322 0.1.0.1-rc. Fixes bug 889.
9324 o Minor bugfixes (hidden services):
9325 - Do not throw away existing introduction points on SIGHUP (bugfix on
9326 0.0.6pre1); also, do not stall hidden services because we're
9327 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
9328 by John Brooks. Patch by Karsten. Fixes bug 874.
9329 - Fix a memory leak when we decline to add a v2 rendezvous
9330 descriptor to the cache because we already had a v0 descriptor
9331 with the same ID. Bugfix on 0.2.0.18-alpha.
9333 o Deprecated and removed features:
9334 - RedirectExits has been removed. It was deprecated since
9336 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
9337 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
9338 - Cell pools are now always enabled; --disable-cell-pools is ignored.
9340 o Code simplifications and refactoring:
9341 - Rename the confusing or_is_obsolete field to the more appropriate
9342 is_bad_for_new_circs, and move it to or_connection_t where it
9344 - Move edge-only flags from connection_t to edge_connection_t: not
9345 only is this better coding, but on machines of plausible alignment,
9346 it should save 4-8 bytes per connection_t. "Every little bit helps."
9347 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
9348 for consistency; keep old option working for backward compatibility.
9349 - Simplify the code for finding connections to use for a circuit.
9352 Changes in version 0.2.1.8-alpha - 2008-12-08
9353 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
9354 builds better on unusual platforms like Solaris and old OS X, and
9355 fixes a variety of other issues.
9358 - New DirPortFrontPage option that takes an html file and publishes
9359 it as "/" on the DirPort. Now relay operators can provide a
9360 disclaimer without needing to set up a separate webserver. There's
9361 a sample disclaimer in contrib/tor-exit-notice.html.
9364 - When the client is choosing entry guards, now it selects at most
9365 one guard from a given relay family. Otherwise we could end up with
9366 all of our entry points into the network run by the same operator.
9367 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9370 - Fix a DOS opportunity during the voting signature collection process
9371 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9372 - Fix a possible segfault when establishing an exit connection. Bugfix
9376 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
9378 - Made Tor a little less aggressive about deleting expired
9379 certificates. Partial fix for bug 854.
9380 - Stop doing unaligned memory access that generated bus errors on
9381 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9382 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
9383 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
9384 - Make USR2 log-level switch take effect immediately. Bugfix on
9386 - If one win32 nameserver fails to get added, continue adding the
9387 rest, and don't automatically fail.
9388 - Use fcntl() for locking when flock() is not available. Should fix
9389 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
9390 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9391 could make gcc generate non-functional binary search code. Bugfix
9393 - Build correctly on platforms without socklen_t.
9394 - Avoid potential crash on internal error during signature collection.
9395 Fixes bug 864. Patch from rovv.
9396 - Do not use C's stdio library for writing to log files. This will
9397 improve logging performance by a minute amount, and will stop
9398 leaking fds when our disk is full. Fixes bug 861.
9399 - Stop erroneous use of O_APPEND in cases where we did not in fact
9400 want to re-seek to the end of a file before every last write().
9401 - Correct handling of possible malformed authority signing key
9402 certificates with internal signature types. Fixes bug 880. Bugfix
9404 - Fix a hard-to-trigger resource leak when logging credential status.
9408 - Directory mirrors no longer fetch the v1 directory or
9409 running-routers files. They are obsolete, and nobody asks for them
9410 anymore. This is the first step to making v1 authorities obsolete.
9412 o Minor features (controller):
9413 - Return circuit purposes in response to GETINFO circuit-status. Fixes
9417 Changes in version 0.2.0.32 - 2008-11-20
9418 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
9419 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9420 a smaller security flaw that might allow an attacker to access local
9421 services, further improves hidden service performance, and fixes a
9422 variety of other issues.
9425 - The "User" and "Group" config options did not clear the
9426 supplementary group entries for the Tor process. The "User" option
9427 is now more robust, and we now set the groups to the specified
9428 user's primary group. The "Group" option is now ignored. For more
9429 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9430 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9431 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
9432 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9433 consistently obeyed: if an exit relay refuses a stream because its
9434 exit policy doesn't allow it, we would remember what IP address
9435 the relay said the destination address resolves to, even if it's
9436 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9439 - Fix a DOS opportunity during the voting signature collection process
9440 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9442 o Major bugfixes (hidden services):
9443 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9444 we were failing the whole hidden service request when the v0
9445 descriptor fetch fails, even if the v2 fetch is still pending and
9446 might succeed. Similarly, if the last v2 fetch fails, we were
9447 failing the whole hidden service request even if a v0 fetch is
9448 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9449 - When extending a circuit to a hidden service directory to upload a
9450 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9451 requests failed, because the router descriptor has not been
9452 downloaded yet. In these cases, do not attempt to upload the
9453 rendezvous descriptor, but wait until the router descriptor is
9454 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
9455 descriptor from a hidden service directory for which the router
9456 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
9460 - Fix several infrequent memory leaks spotted by Coverity.
9461 - When testing for libevent functions, set the LDFLAGS variable
9462 correctly. Found by Riastradh.
9463 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9464 bootstrapping with tunneled directory connections. Bugfix on
9465 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9466 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9467 and we know that server B rejects most-but-not all connections to
9468 port 80, we would previously reject the connection. Now, we assume
9469 the user knows what they were asking for. Fixes bug 752. Bugfix
9470 on 0.0.9rc5. Diagnosed by BarkerJr.
9471 - If we overrun our per-second write limits a little, count this as
9472 having used up our write allocation for the second, and choke
9473 outgoing directory writes. Previously, we had only counted this when
9474 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
9475 Bugfix on 0.2.0.x (??).
9476 - Remove the old v2 directory authority 'lefkada' from the default
9477 list. It has been gone for many months.
9478 - Stop doing unaligned memory access that generated bus errors on
9479 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
9480 - Make USR2 log-level switch take effect immediately. Bugfix on
9483 o Minor bugfixes (controller):
9484 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
9485 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
9488 Changes in version 0.2.1.7-alpha - 2008-11-08
9489 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
9490 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9491 a smaller security flaw that might allow an attacker to access local
9492 services, adds better defense against DNS poisoning attacks on exit
9493 relays, further improves hidden service performance, and fixes a
9494 variety of other issues.
9497 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9498 consistently obeyed: if an exit relay refuses a stream because its
9499 exit policy doesn't allow it, we would remember what IP address
9500 the relay said the destination address resolves to, even if it's
9501 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9502 - The "User" and "Group" config options did not clear the
9503 supplementary group entries for the Tor process. The "User" option
9504 is now more robust, and we now set the groups to the specified
9505 user's primary group. The "Group" option is now ignored. For more
9506 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9507 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9508 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
9509 - Do not use or believe expired v3 authority certificates. Patch
9510 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9513 - Now NodeFamily and MyFamily config options allow spaces in
9514 identity fingerprints, so it's easier to paste them in.
9515 Suggested by Lucky Green.
9516 - Implement the 0x20 hack to better resist DNS poisoning: set the
9517 case on outgoing DNS requests randomly, and reject responses that do
9518 not match the case correctly. This logic can be disabled with the
9519 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
9520 of servers that do not reliably preserve case in replies. See
9521 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9523 - Preserve case in replies to DNSPort requests in order to support
9524 the 0x20 hack for resisting DNS poisoning attacks.
9526 o Hidden service performance improvements:
9527 - When the client launches an introduction circuit, retry with a
9528 new circuit after 30 seconds rather than 60 seconds.
9529 - Launch a second client-side introduction circuit in parallel
9530 after a delay of 15 seconds (based on work by Christian Wilms).
9531 - Hidden services start out building five intro circuits rather
9532 than three, and when the first three finish they publish a service
9533 descriptor using those. Now we publish our service descriptor much
9534 faster after restart.
9537 - Minor fix in the warning messages when you're having problems
9538 bootstrapping; also, be more forgiving of bootstrap problems when
9539 we're still making incremental progress on a given bootstrap phase.
9540 - When we're choosing an exit node for a circuit, and we have
9541 no pending streams, choose a good general exit rather than one that
9542 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9543 - Send a valid END cell back when a client tries to connect to a
9544 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9545 840. Patch from rovv.
9546 - If a broken client asks a non-exit router to connect somewhere,
9547 do not even do the DNS lookup before rejecting the connection.
9548 Fixes another case of bug 619. Patch from rovv.
9549 - Fix another case of assuming, when a specific exit is requested,
9550 that we know more than the user about what hosts it allows.
9551 Fixes another case of bug 752. Patch from rovv.
9552 - Check which hops rendezvous stream cells are associated with to
9553 prevent possible guess-the-streamid injection attacks from
9554 intermediate hops. Fixes another case of bug 446. Based on patch
9556 - Avoid using a negative right-shift when comparing 32-bit
9557 addresses. Possible fix for bug 845 and bug 811.
9558 - Make the assert_circuit_ok() function work correctly on circuits that
9559 have already been marked for close.
9560 - Fix read-off-the-end-of-string error in unit tests when decoding
9561 introduction points.
9562 - Fix uninitialized size field for memory area allocation: may improve
9563 memory performance during directory parsing.
9564 - Treat duplicate certificate fetches as failures, so that we do
9565 not try to re-fetch an expired certificate over and over and over.
9566 - Do not say we're fetching a certificate when we'll in fact skip it
9567 because of a pending download.
9570 Changes in version 0.2.1.6-alpha - 2008-09-30
9571 Tor 0.2.1.6-alpha further improves performance and robustness of
9572 hidden services, starts work on supporting per-country relay selection,
9573 and fixes a variety of smaller issues.
9576 - Implement proposal 121: make it possible to build hidden services
9577 that only certain clients are allowed to connect to. This is
9578 enforced at several points, so that unauthorized clients are unable
9579 to send INTRODUCE cells to the service, or even (depending on the
9580 type of authentication) to learn introduction points. This feature
9581 raises the bar for certain kinds of active attacks against hidden
9582 services. Code by Karsten Loesing.
9583 - Relays now store and serve v2 hidden service descriptors by default,
9584 i.e., the new default value for HidServDirectoryV2 is 1. This is
9585 the last step in proposal 114, which aims to make hidden service
9586 lookups more reliable.
9587 - Start work to allow node restrictions to include country codes. The
9588 syntax to exclude nodes in a country with country code XX is
9589 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
9590 refinement to decide what config options should take priority if
9591 you ask to both use a particular node and exclude it.
9592 - Allow ExitNodes list to include IP ranges and country codes, just
9593 like the Exclude*Nodes lists. Patch from Robert Hogan.
9596 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
9597 Tor to fail to start if you had it configured to use a bridge
9598 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
9599 - When extending a circuit to a hidden service directory to upload a
9600 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9601 requests failed, because the router descriptor had not been
9602 downloaded yet. In these cases, we now wait until the router
9603 descriptor is downloaded, and then retry. Likewise, clients
9604 now skip over a hidden service directory if they don't yet have
9605 its router descriptor, rather than futilely requesting it and
9606 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
9608 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9609 we were failing the whole hidden service request when the v0
9610 descriptor fetch fails, even if the v2 fetch is still pending and
9611 might succeed. Similarly, if the last v2 fetch fails, we were
9612 failing the whole hidden service request even if a v0 fetch is
9613 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9614 - DNS replies need to have names matching their requests, but
9615 these names should be in the questions section, not necessarily
9616 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
9619 - Update to the "September 1 2008" ip-to-country file.
9620 - Allow ports 465 and 587 in the default exit policy again. We had
9621 rejected them in 0.1.0.15, because back in 2005 they were commonly
9622 misconfigured and ended up as spam targets. We hear they are better
9623 locked down these days.
9624 - Use a lockfile to make sure that two Tor processes are not
9625 simultaneously running with the same datadir.
9626 - Serve the latest v3 networkstatus consensus via the control
9627 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
9628 - Better logging about stability/reliability calculations on directory
9630 - Drop the requirement to have an open dir port for storing and
9631 serving v2 hidden service descriptors.
9632 - Directory authorities now serve a /tor/dbg-stability.txt URL to
9633 help debug WFU and MTBF calculations.
9634 - Implement most of Proposal 152: allow specialized servers to permit
9635 single-hop circuits, and clients to use those servers to build
9636 single-hop circuits when using a specialized controller. Patch
9637 from Josh Albrecht. Resolves feature request 768.
9638 - Add a -p option to tor-resolve for specifying the SOCKS port: some
9639 people find host:port too confusing.
9640 - Make TrackHostExit mappings expire a while after their last use, not
9641 after their creation. Patch from Robert Hogan.
9642 - Provide circuit purposes along with circuit events to the controller.
9645 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
9647 - Fixed some memory leaks -- some quite frequent, some almost
9648 impossible to trigger -- based on results from Coverity.
9649 - When testing for libevent functions, set the LDFLAGS variable
9650 correctly. Found by Riastradh.
9651 - Fix an assertion bug in parsing policy-related options; possible fix
9653 - Catch and report a few more bootstrapping failure cases when Tor
9654 fails to establish a TCP connection. Cleanup on 0.2.1.x.
9655 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9656 bootstrapping with tunneled directory connections. Bugfix on
9657 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9658 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9659 and we know that server B rejects most-but-not all connections to
9660 port 80, we would previously reject the connection. Now, we assume
9661 the user knows what they were asking for. Fixes bug 752. Bugfix
9662 on 0.0.9rc5. Diagnosed by BarkerJr.
9663 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
9664 service directories if they have no advertised dir port. Bugfix
9666 - If we overrun our per-second write limits a little, count this as
9667 having used up our write allocation for the second, and choke
9668 outgoing directory writes. Previously, we had only counted this when
9669 we had met our limits precisely. Fixes bug 824. Patch by rovv.
9670 Bugfix on 0.2.0.x (??).
9671 - Avoid a "0 divided by 0" calculation when calculating router uptime
9672 at directory authorities. Bugfix on 0.2.0.8-alpha.
9673 - Make DNS resolved controller events into "CLOSED", not
9674 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
9676 - Fix a bug where an unreachable relay would establish enough
9677 reachability testing circuits to do a bandwidth test -- if
9678 we already have a connection to the middle hop of the testing
9679 circuit, then it could establish the last hop by using the existing
9680 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
9681 circuits no longer use entry guards in 0.2.1.3-alpha.
9682 - If we have correct permissions on $datadir, we complain to stdout
9683 and fail to start. But dangerous permissions on
9684 $datadir/cached-status/ would cause us to open a log and complain
9685 there. Now complain to stdout and fail to start in both cases. Fixes
9686 bug 820, reported by seeess.
9687 - Remove the old v2 directory authority 'lefkada' from the default
9688 list. It has been gone for many months.
9690 o Code simplifications and refactoring:
9691 - Revise the connection_new functions so that a more typesafe variant
9692 exists. This will work better with Coverity, and let us find any
9693 actual mistakes we're making here.
9694 - Refactor unit testing logic so that dmalloc can be used sensibly
9695 with unit tests to check for memory leaks.
9696 - Move all hidden-service related fields from connection and circuit
9697 structure to substructures: this way they won't eat so much memory.
9700 Changes in version 0.2.0.31 - 2008-09-03
9701 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
9702 a big bug we're seeing where in rare cases traffic from one Tor stream
9703 gets mixed into another stream, and fixes a variety of smaller issues.
9706 - Make sure that two circuits can never exist on the same connection
9707 with the same circuit ID, even if one is marked for close. This
9708 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
9709 - Relays now reject risky extend cells: if the extend cell includes
9710 a digest of all zeroes, or asks to extend back to the relay that
9711 sent the extend cell, tear down the circuit. Ideas suggested
9713 - If not enough of our entry guards are available so we add a new
9714 one, we might use the new one even if it overlapped with the
9715 current circuit's exit relay (or its family). Anonymity bugfix
9716 pointed out by rovv.
9719 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9720 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9721 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9722 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9723 - Pick size of default geoip filename string correctly on windows.
9724 Fixes bug 806. Bugfix on 0.2.0.30.
9725 - Make the autoconf script accept the obsolete --with-ssl-dir
9726 option as an alias for the actually-working --with-openssl-dir
9727 option. Fix the help documentation to recommend --with-openssl-dir.
9728 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9729 - When using the TransPort option on OpenBSD, and using the User
9730 option to change UID and drop privileges, make sure to open
9731 /dev/pf before dropping privileges. Fixes bug 782. Patch from
9732 Christopher Davis. Bugfix on 0.1.2.1-alpha.
9733 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9734 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9735 on the client side when connecting to a hidden service. Bugfix
9736 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9737 - When closing an application-side connection because its circuit is
9738 getting torn down, generate the stream event correctly. Bugfix on
9739 0.1.2.x. Anonymous patch.
9742 Changes in version 0.2.1.5-alpha - 2008-08-31
9743 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
9744 in a lot of the infrastructure for adding authorization to hidden
9745 services, lays the groundwork for having clients read their load
9746 balancing information out of the networkstatus consensus rather than
9747 the individual router descriptors, addresses two potential anonymity
9748 issues, and fixes a variety of smaller issues.
9751 - Convert many internal address representations to optionally hold
9753 - Generate and accept IPv6 addresses in many protocol elements.
9754 - Make resolver code handle nameservers located at ipv6 addresses.
9755 - Begin implementation of proposal 121 ("Client authorization for
9756 hidden services"): configure hidden services with client
9757 authorization, publish descriptors for them, and configure
9758 authorization data for hidden services at clients. The next
9759 step is to actually access hidden services that perform client
9761 - More progress toward proposal 141: Network status consensus
9762 documents and votes now contain bandwidth information for each
9763 router and a summary of that router's exit policy. Eventually this
9764 will be used by clients so that they do not have to download every
9765 known descriptor before building circuits.
9767 o Major bugfixes (on 0.2.0.x and before):
9768 - When sending CREATED cells back for a given circuit, use a 64-bit
9769 connection ID to find the right connection, rather than an addr:port
9770 combination. Now that we can have multiple OR connections between
9771 the same ORs, it is no longer possible to use addr:port to uniquely
9772 identify a connection.
9773 - Relays now reject risky extend cells: if the extend cell includes
9774 a digest of all zeroes, or asks to extend back to the relay that
9775 sent the extend cell, tear down the circuit. Ideas suggested
9777 - If not enough of our entry guards are available so we add a new
9778 one, we might use the new one even if it overlapped with the
9779 current circuit's exit relay (or its family). Anonymity bugfix
9780 pointed out by rovv.
9783 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
9784 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
9785 - When using the TransPort option on OpenBSD, and using the User
9786 option to change UID and drop privileges, make sure to open /dev/pf
9787 before dropping privileges. Fixes bug 782. Patch from Christopher
9788 Davis. Bugfix on 0.1.2.1-alpha.
9789 - Correctly detect the presence of the linux/netfilter_ipv4.h header
9790 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
9791 - Add a missing safe_str() call for a debug log message.
9792 - Use 64 bits instead of 32 bits for connection identifiers used with
9793 the controller protocol, to greatly reduce risk of identifier reuse.
9794 - Make the autoconf script accept the obsolete --with-ssl-dir
9795 option as an alias for the actually-working --with-openssl-dir
9796 option. Fix the help documentation to recommend --with-openssl-dir.
9797 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
9800 - Rate-limit too-many-sockets messages: when they happen, they happen
9801 a lot. Resolves bug 748.
9802 - Resist DNS poisoning a little better by making sure that names in
9803 answer sections match.
9804 - Print the SOCKS5 error message string as well as the error code
9805 when a tor-resolve request fails. Patch from Jacob.
9808 Changes in version 0.2.1.4-alpha - 2008-08-04
9809 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
9812 - The address part of exit policies was not correctly written
9813 to router descriptors. This generated router descriptors that failed
9814 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
9816 - Tor triggered a false assert when extending a circuit to a relay
9817 but we already have a connection open to that relay. Noticed by
9818 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
9821 - Fix a hidden service logging bug: in some edge cases, the router
9822 descriptor of a previously picked introduction point becomes
9823 obsolete and we need to give up on it rather than continually
9824 complaining that it has become obsolete. Observed by xiando. Bugfix
9828 - Take out the TestVia config option, since it was a workaround for
9829 a bug that was fixed in Tor 0.1.1.21.
9832 Changes in version 0.2.1.3-alpha - 2008-08-03
9833 Tor 0.2.1.3-alpha implements most of the pieces to prevent
9834 infinite-length circuit attacks (see proposal 110); fixes a bug that
9835 might cause exit relays to corrupt streams they send back; allows
9836 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
9837 ExcludeExitNodes config options; and fixes a big pile of bugs.
9839 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
9840 - Send a bootstrap problem "warn" event on the first problem if the
9841 reason is NO_ROUTE (that is, our network is down).
9844 - Implement most of proposal 110: The first K cells to be sent
9845 along a circuit are marked as special "early" cells; only K "early"
9846 cells will be allowed. Once this code is universal, we can block
9847 certain kinds of DOS attack by requiring that EXTEND commands must
9848 be sent using an "early" cell.
9851 - Try to attach connections immediately upon receiving a RENDEZVOUS2
9852 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
9853 on the client side when connecting to a hidden service. Bugfix
9854 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
9855 - Ensure that two circuits can never exist on the same connection
9856 with the same circuit ID, even if one is marked for close. This
9857 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
9860 - When relays do their initial bandwidth measurement, don't limit
9861 to just our entry guards for the test circuits. Otherwise we tend
9862 to have multiple test circuits going through a single entry guard,
9863 which makes our bandwidth test less accurate. Fixes part of bug 654;
9864 patch contributed by Josh Albrecht.
9865 - Add an ExcludeExitNodes option so users can list a set of nodes
9866 that should be be excluded from the exit node position, but
9867 allowed elsewhere. Implements proposal 151.
9868 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
9869 ExcludeNodes and ExcludeExitNodes lists.
9870 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
9871 be more efficient. Formerly it was quadratic in the number of
9872 servers; now it should be linear. Fixes bug 509.
9873 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
9874 and n_conn_id_digest fields into a separate structure that's
9875 only needed when the circuit has not yet attached to an n_conn.
9878 - Change the contrib/tor.logrotate script so it makes the new
9879 logs as "_tor:_tor" rather than the default, which is generally
9880 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
9881 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9882 warnings (occasionally), but it can also cause the compiler to
9883 eliminate error-checking code. Suggested by Peter Gutmann.
9884 - When a hidden service is giving up on an introduction point candidate
9885 that was not included in the last published rendezvous descriptor,
9886 don't reschedule publication of the next descriptor. Fixes bug 763.
9888 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
9889 HiddenServiceExcludeNodes as obsolete: they never worked properly,
9890 and nobody claims to be using them. Fixes bug 754. Bugfix on
9891 0.1.0.1-rc. Patch from Christian Wilms.
9892 - Fix a small alignment and memory-wasting bug on buffer chunks.
9895 o Minor bugfixes (controller):
9896 - When closing an application-side connection because its circuit
9897 is getting torn down, generate the stream event correctly.
9898 Bugfix on 0.1.2.x. Anonymous patch.
9901 - Remove all backward-compatibility code to support relays running
9902 versions of Tor so old that they no longer work at all on the
9906 Changes in version 0.2.0.30 - 2008-07-15
9908 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
9909 warnings (occasionally), but it can also cause the compiler to
9910 eliminate error-checking code. Suggested by Peter Gutmann.
9913 Changes in version 0.2.0.29-rc - 2008-07-08
9914 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
9915 hidden-service performance bugs, and fixes a bunch of smaller bugs.
9918 - If you have more than one bridge but don't know their keys,
9919 you would only launch a request for the descriptor of the first one
9920 on your list. (Tor considered launching requests for the others, but
9921 found that it already had a connection on the way for $0000...0000
9922 so it didn't open another.) Bugfix on 0.2.0.x.
9923 - If you have more than one bridge but don't know their keys, and the
9924 connection to one of the bridges failed, you would cancel all
9925 pending bridge connections. (After all, they all have the same
9926 digest.) Bugfix on 0.2.0.x.
9927 - When a hidden service was trying to establish an introduction point,
9928 and Tor had built circuits preemptively for such purposes, we
9929 were ignoring all the preemptive circuits and launching a new one
9930 instead. Bugfix on 0.2.0.14-alpha.
9931 - When a hidden service was trying to establish an introduction point,
9932 and Tor *did* manage to reuse one of the preemptively built
9933 circuits, it didn't correctly remember which one it used,
9934 so it asked for another one soon after, until there were no
9935 more preemptive circuits, at which point it launched one from
9936 scratch. Bugfix on 0.0.9.x.
9937 - Make directory servers include the X-Your-Address-Is: http header in
9938 their responses even for begin_dir conns. Now clients who only
9939 ever use begin_dir connections still have a way to learn their IP
9940 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
9943 - Fix a macro/CPP interaction that was confusing some compilers:
9944 some GCCs don't like #if/#endif pairs inside macro arguments.
9946 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
9947 Fixes bug 704; fix from Steven Murdoch.
9948 - When opening /dev/null in finish_daemonize(), do not pass the
9949 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
9950 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
9951 - Correctly detect transparent proxy support on Linux hosts that
9952 require in.h to be included before netfilter_ipv4.h. Patch
9954 - Disallow session resumption attempts during the renegotiation
9955 stage of the v2 handshake protocol. Clients should never be trying
9956 session resumption at this point, but apparently some did, in
9957 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
9958 found by Geoff Goodell.
9961 Changes in version 0.2.1.2-alpha - 2008-06-20
9962 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
9963 make it easier to set up your own private Tor network; fixes several
9964 big bugs with using more than one bridge relay; fixes a big bug with
9965 offering hidden services quickly after Tor starts; and uses a better
9966 API for reporting potential bootstrapping problems to the controller.
9969 - New TestingTorNetwork config option to allow adjustment of
9970 previously constant values that, while reasonable, could slow
9971 bootstrapping. Implements proposal 135. Patch from Karsten.
9974 - If you have more than one bridge but don't know their digests,
9975 you would only learn a request for the descriptor of the first one
9976 on your list. (Tor considered launching requests for the others, but
9977 found that it already had a connection on the way for $0000...0000
9978 so it didn't open another.) Bugfix on 0.2.0.x.
9979 - If you have more than one bridge but don't know their digests,
9980 and the connection to one of the bridges failed, you would cancel
9981 all pending bridge connections. (After all, they all have the
9982 same digest.) Bugfix on 0.2.0.x.
9983 - When establishing a hidden service, introduction points that
9984 originate from cannibalized circuits are completely ignored and not
9985 included in rendezvous service descriptors. This might be another
9986 reason for delay in making a hidden service available. Bugfix
9987 from long ago (0.0.9.x?)
9990 - Allow OpenSSL to use dynamic locks if it wants.
9991 - When building a consensus, do not include routers that are down.
9992 This will cut down 30% to 40% on consensus size. Implements
9994 - In directory authorities' approved-routers files, allow
9995 fingerprints with or without space.
9996 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
9997 controller can query our current bootstrap state in case it attaches
9998 partway through and wants to catch up.
9999 - Send an initial "Starting" bootstrap status event, so we have a
10000 state to start out in.
10003 - Asking for a conditional consensus at .../consensus/<fingerprints>
10004 would crash a dirserver if it did not already have a
10005 consensus. Bugfix on 0.2.1.1-alpha.
10006 - Clean up some macro/CPP interactions: some GCC versions don't like
10007 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
10010 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
10011 - Directory authorities shouldn't complain about bootstrapping
10012 problems just because they do a lot of reachability testing and
10013 some of the connection attempts fail.
10014 - Start sending "count" and "recommendation" key/value pairs in
10015 bootstrap problem status events, so the controller can hear about
10016 problems even before Tor decides they're worth reporting for sure.
10017 - If you're using bridges, generate "bootstrap problem" warnings
10018 as soon as you run out of working bridges, rather than waiting
10019 for ten failures -- which will never happen if you have less than
10021 - If we close our OR connection because there's been a circuit
10022 pending on it for too long, we were telling our bootstrap status
10023 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
10026 Changes in version 0.2.1.1-alpha - 2008-06-13
10027 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
10028 were making the Tor process bloat especially on Linux; makes our TLS
10029 handshake blend in better; sends "bootstrap phase" status events to
10030 the controller, so it can keep the user informed of progress (and
10031 problems) fetching directory information and establishing circuits;
10032 and adds a variety of smaller features.
10035 - More work on making our TLS handshake blend in: modify the list
10036 of ciphers advertised by OpenSSL in client mode to even more
10037 closely resemble a common web browser. We cheat a little so that
10038 we can advertise ciphers that the locally installed OpenSSL doesn't
10040 - Start sending "bootstrap phase" status events to the controller,
10041 so it can keep the user informed of progress fetching directory
10042 information and establishing circuits. Also inform the controller
10043 if we think we're stuck at a particular bootstrap phase. Implements
10045 - Resume using OpenSSL's RAND_poll() for better (and more portable)
10046 cross-platform entropy collection again. We used to use it, then
10047 stopped using it because of a bug that could crash systems that
10048 called RAND_poll when they had a lot of fds open. It looks like the
10049 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
10050 at startup, and to call RAND_poll() when we reseed later only if
10051 we have a non-buggy OpenSSL version.
10054 - When we choose to abandon a new entry guard because we think our
10055 older ones might be better, close any circuits pending on that
10056 new entry guard connection. This fix should make us recover much
10057 faster when our network is down and then comes back. Bugfix on
10058 0.1.2.8-beta; found by lodger.
10060 o Memory fixes and improvements:
10061 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10062 to avoid unused RAM in buffer chunks and memory pools.
10063 - Speed up parsing and cut down on memory fragmentation by using
10064 stack-style allocations for parsing directory objects. Previously,
10065 this accounted for over 40% of allocations from within Tor's code
10066 on a typical directory cache.
10067 - Use a Bloom filter rather than a digest-based set to track which
10068 descriptors we need to keep around when we're cleaning out old
10069 router descriptors. This speeds up the computation significantly,
10070 and may reduce fragmentation.
10071 - Reduce the default smartlist size from 32 to 16; it turns out that
10072 most smartlists hold around 8-12 elements tops.
10073 - Make dumpstats() log the fullness and size of openssl-internal
10075 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10076 patch to their OpenSSL, turn it on to save memory on servers. This
10077 patch will (with any luck) get included in a mainline distribution
10079 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10080 compress cells, which are basically all encrypted, compressed,
10084 - Stop reloading the router list from disk for no reason when we
10085 run out of reachable directory mirrors. Once upon a time reloading
10086 it would set the 'is_running' flag back to 1 for them. It hasn't
10087 done that for a long time.
10088 - In very rare situations new hidden service descriptors were
10089 published earlier than 30 seconds after the last change to the
10090 service. (We currently think that a hidden service descriptor
10091 that's been stable for 30 seconds is worth publishing.)
10094 - Allow separate log levels to be configured for different logging
10095 domains. For example, this allows one to log all notices, warnings,
10096 or errors, plus all memory management messages of level debug or
10097 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
10098 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10099 and stop using a warning that had become unfixably verbose under
10101 - New --hush command-line option similar to --quiet. While --quiet
10102 disables all logging to the console on startup, --hush limits the
10103 output to messages of warning and error severity.
10104 - Servers support a new URL scheme for consensus downloads that
10105 allows the client to specify which authorities are trusted.
10106 The server then only sends the consensus if the client will trust
10107 it. Otherwise a 404 error is sent back. Clients use this
10108 new scheme when the server supports it (meaning it's running
10109 0.2.1.1-alpha or later). Implements proposal 134.
10110 - New configure/torrc options (--enable-geoip-stats,
10111 DirRecordUsageByCountry) to record how many IPs we've served
10112 directory info to in each country code, how many status documents
10113 total we've sent to each country code, and what share of the total
10114 directory requests we should expect to see.
10115 - Use the TLS1 hostname extension to more closely resemble browser
10117 - Lots of new unit tests.
10118 - Add a macro to implement the common pattern of iterating through
10119 two parallel lists in lockstep.
10122 Changes in version 0.2.0.28-rc - 2008-06-13
10123 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
10124 performance bug, and fixes a bunch of smaller bugs.
10127 - Fix a bug where, when we were choosing the 'end stream reason' to
10128 put in our relay end cell that we send to the exit relay, Tor
10129 clients on Windows were sometimes sending the wrong 'reason'. The
10130 anonymity problem is that exit relays may be able to guess whether
10131 the client is running Windows, thus helping partition the anonymity
10132 set. Down the road we should stop sending reasons to exit relays,
10133 or otherwise prevent future versions of this bug.
10136 - While setting up a hidden service, some valid introduction circuits
10137 were overlooked and abandoned. This might be the reason for
10138 the long delay in making a hidden service available. Bugfix on
10142 - Update to the "June 9 2008" ip-to-country file.
10143 - Run 'make test' as part of 'make dist', so we stop releasing so
10144 many development snapshots that fail their unit tests.
10147 - When we're checking if we have enough dir info for each relay
10148 to begin establishing circuits, make sure that we actually have
10149 the descriptor listed in the consensus, not just any descriptor.
10151 - Bridge relays no longer print "xx=0" in their extrainfo document
10152 for every single country code in the geoip db. Bugfix on
10154 - Only warn when we fail to load the geoip file if we were planning to
10155 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
10156 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10157 Tor won't realize it should publish a new relay descriptor. Fixes
10158 bug 688, reported by mfr. Bugfix on 0.1.2.x.
10159 - When we haven't had any application requests lately, don't bother
10160 logging that we have expired a bunch of descriptors. Bugfix
10162 - Make relay cells written on a connection count as non-padding when
10163 tracking how long a connection has been in use. Bugfix on
10164 0.2.0.1-alpha. Spotted by lodger.
10165 - Fix unit tests in 0.2.0.27-rc.
10166 - Fix compile on Windows.
10169 Changes in version 0.2.0.27-rc - 2008-06-03
10170 Tor 0.2.0.27-rc adds a few features we left out of the earlier
10171 release candidates. In particular, we now include an IP-to-country
10172 GeoIP database, so controllers can easily look up what country a
10173 given relay is in, and so bridge relays can give us some sanitized
10174 summaries about which countries are making use of bridges. (See proposal
10175 126-geoip-fetching.txt for details.)
10178 - Include an IP-to-country GeoIP file in the tarball, so bridge
10179 relays can report sanitized summaries of the usage they're seeing.
10182 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
10183 Robert Hogan. Fixes the first part of bug 681.
10184 - Make bridge authorities never serve extrainfo docs.
10185 - Add support to detect Libevent versions in the 1.4.x series
10187 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
10188 - Include a new contrib/tor-exit-notice.html file that exit relay
10189 operators can put on their website to help reduce abuse queries.
10192 - When tunneling an encrypted directory connection, and its first
10193 circuit fails, do not leave it unattached and ask the controller
10194 to deal. Fixes the second part of bug 681.
10195 - Make bridge authorities correctly expire old extrainfo documents
10199 Changes in version 0.2.0.26-rc - 2008-05-13
10200 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
10201 in Debian's OpenSSL packages. All users running any 0.2.0.x version
10202 should upgrade, whether they're running Debian or not.
10204 o Major security fixes:
10205 - Use new V3 directory authority keys on the tor26, gabelmoo, and
10206 moria1 V3 directory authorities. The old keys were generated with
10207 a vulnerable version of Debian's OpenSSL package, and must be
10208 considered compromised. Other authorities' keys were not generated
10209 with an affected version of OpenSSL.
10212 - List authority signatures as "unrecognized" based on DirServer
10213 lines, not on cert cache. Bugfix on 0.2.0.x.
10216 - Add a new V3AuthUseLegacyKey option to make it easier for
10217 authorities to change their identity keys if they have to.
10220 Changes in version 0.2.0.25-rc - 2008-04-23
10221 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
10224 - Remember to initialize threading before initializing logging.
10225 Otherwise, many BSD-family implementations will crash hard on
10226 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
10229 - Authorities correctly free policies on bad servers on
10230 exit. Fixes bug 672. Bugfix on 0.2.0.x.
10233 Changes in version 0.2.0.24-rc - 2008-04-22
10234 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
10235 v3 directory authority, makes relays with dynamic IP addresses and no
10236 DirPort notice more quickly when their IP address changes, fixes a few
10237 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
10239 o New directory authorities:
10240 - Take lefkada out of the list of v3 directory authorities, since
10241 it has been down for months.
10242 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
10246 - Detect address changes more quickly on non-directory mirror
10247 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
10249 o Minor features (security):
10250 - Reject requests for reverse-dns lookup of names that are in
10251 a private address space. Patch from lodger.
10252 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
10255 o Minor bugfixes (crashes):
10256 - Avoid a rare assert that can trigger when Tor doesn't have much
10257 directory information yet and it tries to fetch a v2 hidden
10258 service descriptor. Fixes bug 651, reported by nwf.
10259 - Initialize log mutex before initializing dmalloc. Otherwise,
10260 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
10261 - Use recursive pthread mutexes in order to avoid deadlock when
10262 logging debug-level messages to a controller. Bug spotted by nwf,
10263 bugfix on 0.2.0.16-alpha.
10265 o Minor bugfixes (resource management):
10266 - Keep address policies from leaking memory: start their refcount
10267 at 1, not 2. Bugfix on 0.2.0.16-alpha.
10268 - Free authority certificates on exit, so they don't look like memory
10269 leaks. Bugfix on 0.2.0.19-alpha.
10270 - Free static hashtables for policy maps and for TLS connections on
10271 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
10272 - Avoid allocating extra space when computing consensuses on 64-bit
10273 platforms. Bug spotted by aakova.
10275 o Minor bugfixes (misc):
10276 - Do not read the configuration file when we've only been told to
10277 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
10278 based on patch from Sebastian Hahn.
10279 - Exit relays that are used as a client can now reach themselves
10280 using the .exit notation, rather than just launching an infinite
10281 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10282 - When attempting to open a logfile fails, tell us why.
10283 - Fix a dumb bug that was preventing us from knowing that we should
10284 preemptively build circuits to handle expected directory requests.
10285 Fixes bug 660. Bugfix on 0.1.2.x.
10286 - Warn less verbosely about clock skew from netinfo cells from
10287 untrusted sources. Fixes bug 663.
10288 - Make controller stream events for DNS requests more consistent,
10289 by adding "new stream" events for DNS requests, and removing
10290 spurious "stream closed" events" for cached reverse resolves.
10291 Patch from mwenge. Fixes bug 646.
10292 - Correctly notify one-hop connections when a circuit build has
10293 failed. Possible fix for bug 669. Found by lodger.
10296 Changes in version 0.2.0.23-rc - 2008-03-24
10297 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
10298 makes bootstrapping faster if the first directory mirror you contact
10299 is down. The bundles also include the new Vidalia 0.1.2 release.
10302 - When a tunneled directory request is made to a directory server
10303 that's down, notice after 30 seconds rather than 120 seconds. Also,
10304 fail any begindir streams that are pending on it, so they can
10305 retry elsewhere. This was causing multi-minute delays on bootstrap.
10308 Changes in version 0.2.0.22-rc - 2008-03-18
10309 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
10310 enables encrypted directory connections by default for non-relays, fixes
10311 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
10312 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
10315 - Enable encrypted directory connections by default for non-relays,
10316 so censor tools that block Tor directory connections based on their
10317 plaintext patterns will no longer work. This means Tor works in
10318 certain censored countries by default again.
10321 - Make sure servers always request certificates from clients during
10322 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
10323 - Do not enter a CPU-eating loop when a connection is closed in
10324 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
10325 diagnosed by lodger; bugfix on 0.2.0.20-rc.
10326 - Fix assertion failure that could occur when a blocked circuit
10327 became unblocked, and it had pending client DNS requests. Bugfix
10328 on 0.2.0.1-alpha. Fixes bug 632.
10330 o Minor bugfixes (on 0.1.2.x):
10331 - Generate "STATUS_SERVER" events rather than misspelled
10332 "STATUS_SEVER" events. Caught by mwenge.
10333 - When counting the number of bytes written on a TLS connection,
10334 look at the BIO actually used for writing to the network, not
10335 at the BIO used (sometimes) to buffer data for the network.
10336 Looking at different BIOs could result in write counts on the
10337 order of ULONG_MAX. Fixes bug 614.
10338 - On Windows, correctly detect errors when listing the contents of
10339 a directory. Fix from lodger.
10341 o Minor bugfixes (on 0.2.0.x):
10342 - Downgrade "sslv3 alert handshake failure" message to INFO.
10343 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
10344 left BandwidthRate and BandwidthBurst at the default, we would be
10345 silently limited by those defaults. Now raise them to match the
10346 RelayBandwidth* values.
10347 - Fix the SVK version detection logic to work correctly on a branch.
10348 - Make --enable-openbsd-malloc work correctly on Linux with alpha
10349 CPUs. Fixes bug 625.
10350 - Logging functions now check that the passed severity is sane.
10351 - Use proper log levels in the testsuite call of
10352 get_interface_address6().
10353 - When using a nonstandard malloc, do not use the platform values for
10354 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
10355 - Make the openbsd malloc code use 8k pages on alpha CPUs and
10357 - Detect mismatched page sizes when using --enable-openbsd-malloc.
10358 - Avoid double-marked-for-close warning when certain kinds of invalid
10359 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
10360 for bug 617. Bugfix on 0.2.0.1-alpha.
10361 - Make sure that the "NULL-means-reject *:*" convention is followed by
10362 all the policy manipulation functions, avoiding some possible crash
10363 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
10364 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
10365 actually works, and doesn't warn about every single reverse lookup.
10366 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
10369 - Only log guard node status when guard node status has changed.
10370 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
10371 make "INFO" 75% less verbose.
10374 Changes in version 0.2.0.21-rc - 2008-03-02
10375 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
10376 makes Tor work well with Vidalia again, fixes a rare assert bug,
10377 and fixes a pair of more minor bugs. The bundles also include Vidalia
10378 0.1.0 and Torbutton 1.1.16.
10381 - The control port should declare that it requires password auth
10382 when HashedControlSessionPassword is set too. Patch from Matt Edman;
10383 bugfix on 0.2.0.20-rc. Fixes bug 615.
10384 - Downgrade assert in connection_buckets_decrement() to a log message.
10385 This may help us solve bug 614, and in any case will make its
10386 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
10387 - We were sometimes miscounting the number of bytes read from the
10388 network, causing our rate limiting to not be followed exactly.
10389 Bugfix on 0.2.0.16-alpha. Reported by lodger.
10392 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
10393 OpenSSL versions should have been working fine. Diagnosis and patch
10394 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
10395 Bugfix on 0.2.0.20-rc.
10398 Changes in version 0.2.0.20-rc - 2008-02-24
10399 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
10400 makes more progress towards normalizing Tor's TLS handshake, makes
10401 hidden services work better again, helps relays bootstrap if they don't
10402 know their IP address, adds optional support for linking in openbsd's
10403 allocator or tcmalloc, allows really fast relays to scale past 15000
10404 sockets, and fixes a bunch of minor bugs reported by Veracode.
10407 - Enable the revised TLS handshake based on the one designed by
10408 Steven Murdoch in proposal 124, as revised in proposal 130. It
10409 includes version negotiation for OR connections as described in
10410 proposal 105. The new handshake is meant to be harder for censors
10411 to fingerprint, and it adds the ability to detect certain kinds of
10412 man-in-the-middle traffic analysis attacks. The version negotiation
10413 feature will allow us to improve Tor's link protocol more safely
10415 - Choose which bridge to use proportional to its advertised bandwidth,
10416 rather than uniformly at random. This should speed up Tor for
10417 bridge users. Also do this for people who set StrictEntryNodes.
10418 - When a TrackHostExits-chosen exit fails too many times in a row,
10419 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
10422 - Resolved problems with (re-)fetching hidden service descriptors.
10423 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
10424 and 0.2.0.19-alpha.
10425 - If we only ever used Tor for hidden service lookups or posts, we
10426 would stop building circuits and start refusing connections after
10427 24 hours, since we falsely believed that Tor was dormant. Reported
10428 by nwf; bugfix on 0.1.2.x.
10429 - Servers that don't know their own IP address should go to the
10430 authorities for their first directory fetch, even if their DirPort
10431 is off or if they don't know they're reachable yet. This will help
10432 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
10433 - When counting the number of open sockets, count not only the number
10434 of sockets we have received from the socket() call, but also
10435 the number we've gotten from accept() and socketpair(). This bug
10436 made us fail to count all sockets that we were using for incoming
10437 connections. Bugfix on 0.2.0.x.
10438 - Fix code used to find strings within buffers, when those strings
10439 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
10440 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
10441 - Add a new __HashedControlSessionPassword option for controllers
10442 to use for one-off session password hashes that shouldn't get
10443 saved to disk by SAVECONF --- Vidalia users were accumulating a
10444 pile of HashedControlPassword lines in their torrc files, one for
10445 each time they had restarted Tor and then clicked Save. Make Tor
10446 automatically convert "HashedControlPassword" to this new option but
10447 only when it's given on the command line. Partial fix for bug 586.
10449 o Minor features (performance):
10450 - Tune parameters for cell pool allocation to minimize amount of
10452 - Add OpenBSD malloc code from phk as an optional malloc
10453 replacement on Linux: some glibc libraries do very poorly
10454 with Tor's memory allocation patterns. Pass
10455 --enable-openbsd-malloc to get the replacement malloc code.
10456 - Add a --with-tcmalloc option to the configure script to link
10457 against tcmalloc (if present). Does not yet search for
10458 non-system include paths.
10459 - Stop imposing an arbitrary maximum on the number of file descriptors
10460 used for busy servers. Bug reported by Olaf Selke; patch from
10463 o Minor features (other):
10464 - When SafeLogging is disabled, log addresses along with all TLS
10466 - When building with --enable-gcc-warnings, check for whether Apple's
10467 warning "-Wshorten-64-to-32" is available.
10468 - Add a --passphrase-fd argument to the tor-gencert command for
10471 o Minor bugfixes (memory leaks and code problems):
10472 - We were leaking a file descriptor if Tor started with a zero-length
10473 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
10474 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10476 - We were comparing the raw BridgePassword entry with a base64'ed
10477 version of it, when handling a "/tor/networkstatus-bridges"
10478 directory request. Now compare correctly. Noticed by Veracode.
10479 - Recover from bad tracked-since value in MTBF-history file.
10480 Should fix bug 537.
10481 - Alter the code that tries to recover from unhandled write
10482 errors, to not try to flush onto a socket that's given us
10483 unhandled errors. Bugfix on 0.1.2.x.
10484 - Make Unix controlsockets work correctly on OpenBSD. Patch from
10485 tup. Bugfix on 0.2.0.3-alpha.
10487 o Minor bugfixes (other):
10488 - If we have an extra-info document for our server, always make
10489 it available on the control port, even if we haven't gotten
10490 a copy of it from an authority yet. Patch from mwenge.
10491 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
10492 - Directory mirrors no longer include a guess at the client's IP
10493 address if the connection appears to be coming from the same /24
10494 network; it was producing too many wrong guesses.
10495 - Make the new hidden service code respect the SafeLogging setting.
10496 Bugfix on 0.2.0.x. Patch from Karsten.
10497 - When starting as an authority, do not overwrite all certificates
10498 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
10499 - If we're trying to flush the last bytes on a connection (for
10500 example, when answering a directory request), reset the
10501 time-to-give-up timeout every time we manage to write something
10502 on the socket. Bugfix on 0.1.2.x.
10503 - Change the behavior of "getinfo status/good-server-descriptor"
10504 so it doesn't return failure when any authority disappears.
10505 - Even though the man page said that "TrackHostExits ." should
10506 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
10507 - Report TLS "zero return" case as a "clean close" and "IO error"
10508 as a "close". Stop calling closes "unexpected closes": existing
10509 Tors don't use SSL_close(), so having a connection close without
10510 the TLS shutdown handshake is hardly unexpected.
10511 - Send NAMESERVER_STATUS messages for a single failed nameserver
10514 o Code simplifications and refactoring:
10515 - Remove the tor_strpartition function: its logic was confused,
10516 and it was only used for one thing that could be implemented far
10520 Changes in version 0.2.0.19-alpha - 2008-02-09
10521 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
10522 handshake, makes path selection for relays more secure and IP address
10523 guessing more robust, and generally fixes a lot of bugs in preparation
10524 for calling the 0.2.0 branch stable.
10527 - Do not include recognizeable strings in the commonname part of
10528 Tor's x509 certificates.
10531 - If we're a relay, avoid picking ourselves as an introduction point,
10532 a rendezvous point, or as the final hop for internal circuits. Bug
10533 reported by taranis and lodger. Bugfix on 0.1.2.x.
10534 - Patch from "Andrew S. Lists" to catch when we contact a directory
10535 mirror at IP address X and he says we look like we're coming from
10536 IP address X. Bugfix on 0.1.2.x.
10538 o Minor features (security):
10539 - Be more paranoid about overwriting sensitive memory on free(),
10540 as a defensive programming tactic to ensure forward secrecy.
10542 o Minor features (directory authority):
10543 - Actually validate the options passed to AuthDirReject,
10544 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10545 - Reject router descriptors with out-of-range bandwidthcapacity or
10546 bandwidthburst values.
10548 o Minor features (controller):
10549 - Reject controller commands over 1MB in length. This keeps rogue
10550 processes from running us out of memory.
10552 o Minor features (misc):
10553 - Give more descriptive well-formedness errors for out-of-range
10554 hidden service descriptor/protocol versions.
10555 - Make memory debugging information describe more about history
10556 of cell allocation, so we can help reduce our memory use.
10558 o Deprecated features (controller):
10559 - The status/version/num-versioning and status/version/num-concurring
10560 GETINFO options are no longer useful in the v3 directory protocol:
10561 treat them as deprecated, and warn when they're used.
10564 - When our consensus networkstatus has been expired for a while, stop
10565 being willing to build circuits using it. Fixes bug 401. Bugfix
10567 - Directory caches now fetch certificates from all authorities
10568 listed in a networkstatus consensus, even when they do not
10569 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
10570 - When connecting to a bridge without specifying its key, insert
10571 the connection into the identity-to-connection map as soon as
10572 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
10573 - Detect versions of OS X where malloc_good_size() is present in the
10574 library but never actually declared. Resolves bug 587. Bugfix
10576 - Stop incorrectly truncating zlib responses to directory authority
10577 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
10578 - Stop recommending that every server operator send mail to tor-ops.
10579 Resolves bug 597. Bugfix on 0.1.2.x.
10580 - Don't trigger an assert if we start a directory authority with a
10581 private IP address (like 127.0.0.1).
10582 - Avoid possible failures when generating a directory with routers
10583 with over-long versions strings, or too many flags set. Bugfix
10585 - If an attempt to launch a DNS resolve request over the control
10586 port fails because we have overrun the limit on the number of
10587 connections, tell the controller that the request has failed.
10588 - Avoid using too little bandwidth when our clock skips a few
10589 seconds. Bugfix on 0.1.2.x.
10590 - Fix shell error when warning about missing packages in configure
10591 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
10592 - Do not become confused when receiving a spurious VERSIONS-like
10593 cell from a confused v1 client. Bugfix on 0.2.0.x.
10594 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
10595 introduction points for a hidden service have failed. Patch from
10596 Karsten Loesing. Bugfix on 0.2.0.x.
10598 o Code simplifications and refactoring:
10599 - Remove some needless generality from cpuworker code, for improved
10601 - Stop overloading the circuit_t.onionskin field for both "onionskin
10602 from a CREATE cell that we are waiting for a cpuworker to be
10603 assigned" and "onionskin from an EXTEND cell that we are going to
10604 send to an OR as soon as we are connected". Might help with bug 600.
10605 - Add an in-place version of aes_crypt() so that we can avoid doing a
10606 needless memcpy() call on each cell payload.
10609 Changes in version 0.2.0.18-alpha - 2008-01-25
10610 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
10611 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
10612 that can warn or reject connections to ports generally associated with
10613 vulnerable-plaintext protocols.
10615 o New directory authorities:
10616 - Set up dannenberg (run by CCC) as the sixth v3 directory
10620 - Fix a major memory leak when attempting to use the v2 TLS
10621 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
10622 - We accidentally enabled the under-development v2 TLS handshake
10623 code, which was causing log entries like "TLS error while
10624 renegotiating handshake". Disable it again. Resolves bug 590.
10625 - We were computing the wrong Content-Length: header for directory
10626 responses that need to be compressed on the fly, causing clients
10627 asking for those items to always fail. Bugfix on 0.2.0.x; partially
10631 - Avoid going directly to the directory authorities even if you're a
10632 relay, if you haven't found yourself reachable yet or if you've
10633 decided not to advertise your dirport yet. Addresses bug 556.
10634 - If we've gone 12 hours since our last bandwidth check, and we
10635 estimate we have less than 50KB bandwidth capacity but we could
10636 handle more, do another bandwidth test.
10637 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
10638 Tor can warn and/or refuse connections to ports commonly used with
10639 vulnerable-plaintext protocols. Currently we warn on ports 23,
10640 109, 110, and 143, but we don't reject any.
10643 - When we setconf ClientOnly to 1, close any current OR and Dir
10644 listeners. Reported by mwenge.
10645 - When we get a consensus that's been signed by more people than
10646 we expect, don't log about it; it's not a big deal. Reported
10650 - Don't answer "/tor/networkstatus-bridges" directory requests if
10651 the request isn't encrypted.
10652 - Make "ClientOnly 1" config option disable directory ports too.
10653 - Patches from Karsten Loesing to make v2 hidden services more
10654 robust: work even when there aren't enough HSDir relays available;
10655 retry when a v2 rend desc fetch fails; but don't retry if we
10656 already have a usable v0 rend desc.
10659 Changes in version 0.2.0.17-alpha - 2008-01-17
10660 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
10663 - Make the tor-gencert man page get included correctly in the tarball.
10666 Changes in version 0.2.0.16-alpha - 2008-01-17
10667 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
10668 Loesing, and generally cleans up a lot of features and minor bugs.
10670 o New directory authorities:
10671 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
10674 o Major performance improvements:
10675 - Switch our old ring buffer implementation for one more like that
10676 used by free Unix kernels. The wasted space in a buffer with 1mb
10677 of data will now be more like 8k than 1mb. The new implementation
10678 also avoids realloc();realloc(); patterns that can contribute to
10679 memory fragmentation.
10682 - Configuration files now accept C-style strings as values. This
10683 helps encode characters not allowed in the current configuration
10684 file format, such as newline or #. Addresses bug 557.
10685 - Although we fixed bug 539 (where servers would send HTTP status 503
10686 responses _and_ send a body too), there are still servers out
10687 there that haven't upgraded. Therefore, make clients parse such
10688 bodies when they receive them.
10689 - When we're not serving v2 directory information, there is no reason
10690 to actually keep any around. Remove the obsolete files and directory
10691 on startup if they are very old and we aren't going to serve them.
10693 o Minor performance improvements:
10694 - Reference-count and share copies of address policy entries; only 5%
10695 of them were actually distinct.
10696 - Never walk through the list of logs if we know that no log is
10697 interested in a given message.
10700 - When an authority has not signed a consensus, do not try to
10701 download a nonexistent "certificate with key 00000000". Bugfix
10702 on 0.2.0.x. Fixes bug 569.
10703 - Fix a rare assert error when we're closing one of our threads:
10704 use a mutex to protect the list of logs, so we never write to the
10705 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
10706 bug 575, which is kind of the revenge of bug 222.
10707 - Patch from Karsten Loesing to complain less at both the client
10708 and the relay when a relay used to have the HSDir flag but doesn't
10709 anymore, and we try to upload a hidden service descriptor.
10710 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
10712 - Do not try to download missing certificates until we have tried
10713 to check our fallback consensus. Fixes bug 583.
10714 - Make bridges round reported GeoIP stats info up to the nearest
10715 estimate, not down. Now we can distinguish between "0 people from
10716 this country" and "1 person from this country".
10717 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
10718 - Avoid possible segfault if key generation fails in
10719 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
10720 - Avoid segfault in the case where a badly behaved v2 versioning
10721 directory sends a signed networkstatus with missing client-versions.
10723 - Avoid segfaults on certain complex invocations of
10724 router_get_by_hexdigest(). Bugfix on 0.1.2.
10725 - Correct bad index on array access in parse_http_time(). Bugfix
10727 - Fix possible bug in vote generation when server versions are present
10728 but client versions are not.
10729 - Fix rare bug on REDIRECTSTREAM control command when called with no
10730 port set: it could erroneously report an error when none had
10732 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
10733 compressing large objects and find ourselves with more than 4k
10734 left over. Bugfix on 0.2.0.
10735 - Fix a small memory leak when setting up a hidden service.
10736 - Fix a few memory leaks that could in theory happen under bizarre
10738 - Fix an assert if we post a general-purpose descriptor via the
10739 control port but that descriptor isn't mentioned in our current
10740 network consensus. Bug reported by Jon McLachlan; bugfix on
10743 o Minor features (controller):
10744 - Get NS events working again. Patch from tup.
10745 - The GETCONF command now escapes and quotes configuration values
10746 that don't otherwise fit into the torrc file.
10747 - The SETCONF command now handles quoted values correctly.
10749 o Minor features (directory authorities):
10750 - New configuration options to override default maximum number of
10751 servers allowed on a single IP address. This is important for
10752 running a test network on a single host.
10753 - Actually implement the -s option to tor-gencert.
10754 - Add a manual page for tor-gencert.
10756 o Minor features (bridges):
10757 - Bridge authorities no longer serve bridge descriptors over
10758 unencrypted connections.
10760 o Minor features (other):
10761 - Add hidden services and DNSPorts to the list of things that make
10762 Tor accept that it has running ports. Change starting Tor with no
10763 ports from a fatal error to a warning; we might change it back if
10764 this turns out to confuse anybody. Fixes bug 579.
10767 Changes in version 0.1.2.19 - 2008-01-17
10768 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
10769 exit policy a little bit more conservative so it's safer to run an
10770 exit relay on a home system, and fixes a variety of smaller issues.
10773 - Exit policies now reject connections that are addressed to a
10774 relay's public (external) IP address too, unless
10775 ExitPolicyRejectPrivate is turned off. We do this because too
10776 many relays are running nearby to services that trust them based
10777 on network address.
10780 - When the clock jumps forward a lot, do not allow the bandwidth
10781 buckets to become negative. Fixes bug 544.
10782 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
10783 on every successful resolve. Reported by Mike Perry.
10784 - Purge old entries from the "rephist" database and the hidden
10785 service descriptor database even when DirPort is zero.
10786 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10787 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10788 crashing or mis-answering these requests.
10789 - When we decide to send a 503 response to a request for servers, do
10790 not then also send the server descriptors: this defeats the whole
10791 purpose. Fixes bug 539.
10794 - Changing the ExitPolicyRejectPrivate setting should cause us to
10795 rebuild our server descriptor.
10796 - Fix handling of hex nicknames when answering controller requests for
10797 networkstatus by name, or when deciding whether to warn about
10798 unknown routers in a config option. (Patch from mwenge.)
10799 - Fix a couple of hard-to-trigger autoconf problems that could result
10800 in really weird results on platforms whose sys/types.h files define
10801 nonstandard integer types.
10802 - Don't try to create the datadir when running --verify-config or
10803 --hash-password. Resolves bug 540.
10804 - If we were having problems getting a particular descriptor from the
10805 directory caches, and then we learned about a new descriptor for
10806 that router, we weren't resetting our failure count. Reported
10808 - Although we fixed bug 539 (where servers would send HTTP status 503
10809 responses _and_ send a body too), there are still servers out there
10810 that haven't upgraded. Therefore, make clients parse such bodies
10811 when they receive them.
10812 - Run correctly on systems where rlim_t is larger than unsigned long.
10813 This includes some 64-bit systems.
10814 - Run correctly on platforms (like some versions of OS X 10.5) where
10815 the real limit for number of open files is OPEN_FILES, not rlim_max
10816 from getrlimit(RLIMIT_NOFILES).
10817 - Avoid a spurious free on base64 failure.
10818 - Avoid segfaults on certain complex invocations of
10819 router_get_by_hexdigest().
10820 - Fix rare bug on REDIRECTSTREAM control command when called with no
10821 port set: it could erroneously report an error when none had
10825 Changes in version 0.2.0.15-alpha - 2007-12-25
10826 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
10827 features added in 0.2.0.13-alpha.
10830 - Fix several remotely triggerable asserts based on DirPort requests
10831 for a v2 or v3 networkstatus object before we were prepared. This
10832 was particularly bad for 0.2.0.13 and later bridge relays, who
10833 would never have a v2 networkstatus and would thus always crash
10834 when used. Bugfixes on 0.2.0.x.
10835 - Estimate the v3 networkstatus size more accurately, rather than
10836 estimating it at zero bytes and giving it artificially high priority
10837 compared to other directory requests. Bugfix on 0.2.0.x.
10840 - Fix configure.in logic for cross-compilation.
10841 - When we load a bridge descriptor from the cache, and it was
10842 previously unreachable, mark it as retriable so we won't just
10843 ignore it. Also, try fetching a new copy immediately. Bugfixes
10845 - The bridge GeoIP stats were counting other relays, for example
10846 self-reachability and authority-reachability tests.
10849 - Support compilation to target iPhone; patch from cjacker huang.
10850 To build for iPhone, pass the --enable-iphone option to configure.
10853 Changes in version 0.2.0.14-alpha - 2007-12-23
10855 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
10856 without a datadirectory from a previous Tor install. Reported
10858 - Fix a crash when we fetch a descriptor that turns out to be
10859 unexpected (it used to be in our networkstatus when we started
10860 fetching it, but it isn't in our current networkstatus), and we
10861 aren't using bridges. Bugfix on 0.2.0.x.
10862 - Fix a crash when accessing hidden services: it would work the first
10863 time you use a given introduction point for your service, but
10864 on subsequent requests we'd be using garbage memory. Fixed by
10865 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
10866 - Fix a crash when we load a bridge descriptor from disk but we don't
10867 currently have a Bridge line for it in our torrc. Bugfix on
10871 - If bridge authorities set BridgePassword, they will serve a
10872 snapshot of known bridge routerstatuses from their DirPort to
10873 anybody who knows that password. Unset by default.
10876 - Make the unit tests build again.
10877 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
10878 - Make PublishServerDescriptor default to 1, so the default doesn't
10879 have to change as we invent new directory protocol versions.
10880 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
10881 be included unless sys/time.h is already included. Fixes
10882 bug 553. Bugfix on 0.2.0.x.
10883 - If we receive a general-purpose descriptor and then receive an
10884 identical bridge-purpose descriptor soon after, don't discard
10885 the next one as a duplicate.
10888 - If BridgeRelay is set to 1, then the default for
10889 PublishServerDescriptor is now "bridge" rather than "v2,v3".
10890 - If the user sets RelayBandwidthRate but doesn't set
10891 RelayBandwidthBurst, then make them equal rather than erroring out.
10894 Changes in version 0.2.0.13-alpha - 2007-12-21
10895 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
10896 Goodell, fixes many more bugs, and adds a lot of infrastructure for
10899 o New directory authorities:
10900 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
10904 - Only update guard status (usable / not usable) once we have
10905 enough directory information. This was causing us to always pick
10906 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
10907 causing us to discard all our guards on startup if we hadn't been
10908 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
10909 - Purge old entries from the "rephist" database and the hidden
10910 service descriptor databases even when DirPort is zero. Bugfix
10912 - We were ignoring our RelayBandwidthRate for the first 30 seconds
10913 after opening a circuit -- even a relayed circuit. Bugfix on
10915 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
10916 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
10917 crashing or mis-answering these types of requests.
10918 - Relays were publishing their server descriptor to v1 and v2
10919 directory authorities, but they didn't try publishing to v3-only
10920 authorities. Fix this; and also stop publishing to v1 authorities.
10922 - When we were reading router descriptors from cache, we were ignoring
10923 the annotations -- so for example we were reading in bridge-purpose
10924 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
10925 - When we decided to send a 503 response to a request for servers, we
10926 were then also sending the server descriptors: this defeats the
10927 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
10930 - Bridge relays now behave like clients with respect to time
10931 intervals for downloading new consensus documents -- otherwise they
10932 stand out. Bridge users now wait until the end of the interval,
10933 so their bridge relay will be sure to have a new consensus document.
10934 - Three new config options (AlternateDirAuthority,
10935 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
10936 user selectively replace the default directory authorities by type,
10937 rather than the all-or-nothing replacement that DirServer offers.
10938 - Tor can now be configured to read a GeoIP file from disk in one
10939 of two formats. This can be used by controllers to map IP addresses
10940 to countries. Eventually, it may support exit-by-country.
10941 - When possible, bridge relays remember which countries users
10942 are coming from, and report aggregate information in their
10943 extra-info documents, so that the bridge authorities can learn
10944 where Tor is blocked.
10945 - Bridge directory authorities now do reachability testing on the
10946 bridges they know. They provide router status summaries to the
10947 controller via "getinfo ns/purpose/bridge", and also dump summaries
10948 to a file periodically.
10949 - Stop fetching directory info so aggressively if your DirPort is
10950 on but your ORPort is off; stop fetching v2 dir info entirely.
10951 You can override these choices with the new FetchDirInfoEarly
10955 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
10956 consensus documents when there are too many relays at a single
10957 IP address. Now clear it in v2 network status documents too, and
10958 also clear it in routerinfo_t when the relay is no longer listed
10959 in the relevant networkstatus document.
10960 - Don't crash if we get an unexpected value for the
10961 PublishServerDescriptor config option. Reported by Matt Edman;
10962 bugfix on 0.2.0.9-alpha.
10963 - Our new v2 hidden service descriptor format allows descriptors
10964 that have no introduction points. But Tor crashed when we tried
10965 to build a descriptor with no intro points (and it would have
10966 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
10967 by Karsten Loesing.
10968 - Fix building with dmalloc 5.5.2 with glibc.
10969 - Reject uploaded descriptors and extrainfo documents if they're
10970 huge. Otherwise we'll cache them all over the network and it'll
10971 clog everything up. Reported by Aljosha Judmayer.
10972 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
10973 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
10974 - When the DANGEROUS_VERSION controller status event told us we're
10975 running an obsolete version, it used the string "OLD" to describe
10976 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
10977 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
10978 - If we can't expand our list of entry guards (e.g. because we're
10979 using bridges or we have StrictEntryNodes set), don't mark relays
10980 down when they fail a directory request. Otherwise we're too quick
10981 to mark all our entry points down. Bugfix on 0.1.2.x.
10982 - Fix handling of hex nicknames when answering controller requests for
10983 networkstatus by name, or when deciding whether to warn about unknown
10984 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
10985 - Fix a couple of hard-to-trigger autoconf problems that could result
10986 in really weird results on platforms whose sys/types.h files define
10987 nonstandard integer types. Bugfix on 0.1.2.x.
10988 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
10989 - Don't crash on name lookup when we have no current consensus. Fixes
10990 bug 538; bugfix on 0.2.0.x.
10991 - Only Tors that want to mirror the v2 directory info should
10992 create the "cached-status" directory in their datadir. (All Tors
10993 used to create it.) Bugfix on 0.2.0.9-alpha.
10994 - Directory authorities should only automatically download Extra Info
10995 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
10998 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
10999 consumers. (We already do this on HUP.)
11000 - Authorities and caches fetch the v2 networkstatus documents
11001 less often, now that v3 is encouraged.
11002 - Add a new config option BridgeRelay that specifies you want to
11003 be a bridge relay. Right now the only difference is that it makes
11004 you answer begin_dir requests, and it makes you cache dir info,
11005 even if your DirPort isn't on.
11006 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11007 ask about source, timestamp of arrival, purpose, etc. We need
11008 something like this to help Vidalia not do GeoIP lookups on bridge
11010 - Allow multiple HashedControlPassword config lines, to support
11011 multiple controller passwords.
11012 - Authorities now decide whether they're authoritative for a given
11013 router based on the router's purpose.
11014 - New config options AuthDirBadDir and AuthDirListBadDirs for
11015 authorities to mark certain relays as "bad directories" in the
11016 networkstatus documents. Also supports the "!baddir" directive in
11017 the approved-routers file.
11020 Changes in version 0.2.0.12-alpha - 2007-11-16
11021 This twelfth development snapshot fixes some more build problems as
11022 well as a few minor bugs.
11025 - Make it build on OpenBSD again. Patch from tup.
11026 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
11027 package-building for Red Hat, OS X, etc.
11029 o Minor bugfixes (on 0.1.2.x):
11030 - Changing the ExitPolicyRejectPrivate setting should cause us to
11031 rebuild our server descriptor.
11033 o Minor bugfixes (on 0.2.0.x):
11034 - When we're lacking a consensus, don't try to perform rendezvous
11035 operations. Reported by Karsten Loesing.
11036 - Fix a small memory leak whenever we decide against using a
11037 newly picked entry guard. Reported by Mike Perry.
11038 - When authorities detected more than two relays running on the same
11039 IP address, they were clearing all the status flags but forgetting
11040 to clear the "hsdir" flag. So clients were being told that a
11041 given relay was the right choice for a v2 hsdir lookup, yet they
11042 never had its descriptor because it was marked as 'not running'
11044 - If we're trying to fetch a bridge descriptor and there's no way
11045 the bridge authority could help us (for example, we don't know
11046 a digest, or there is no bridge authority), don't be so eager to
11047 fall back to asking the bridge authority.
11048 - If we're using bridges or have strictentrynodes set, and our
11049 chosen exit is in the same family as all our bridges/entry guards,
11050 then be flexible about families.
11053 - When we negotiate a v2 link-layer connection (not yet implemented),
11054 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11055 negotiated a v1 connection for their next step. Initial code for
11059 Changes in version 0.2.0.11-alpha - 2007-11-12
11060 This eleventh development snapshot fixes some build problems with
11061 the previous snapshot. It also includes a more secure-by-default exit
11062 policy for relays, fixes an enormous memory leak for exit relays, and
11063 fixes another bug where servers were falling out of the directory list.
11066 - Exit policies now reject connections that are addressed to a
11067 relay's public (external) IP address too, unless
11068 ExitPolicyRejectPrivate is turned off. We do this because too
11069 many relays are running nearby to services that trust them based
11070 on network address. Bugfix on 0.1.2.x.
11073 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11074 on every successful resolve. Reported by Mike Perry; bugfix
11076 - On authorities, never downgrade to old router descriptors simply
11077 because they're listed in the consensus. This created a catch-22
11078 where we wouldn't list a new descriptor because there was an
11079 old one in the consensus, and we couldn't get the new one in the
11080 consensus because we wouldn't list it. Possible fix for bug 548.
11081 Also, this might cause bug 543 to appear on authorities; if so,
11082 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
11084 o Packaging fixes on 0.2.0.10-alpha:
11085 - We were including instructions about what to do with the
11086 src/config/fallback-consensus file, but we weren't actually
11087 including it in the tarball. Disable all of that for now.
11090 - Allow people to say PreferTunnelledDirConns rather than
11091 PreferTunneledDirConns, for those alternate-spellers out there.
11094 - Don't reevaluate all the information from our consensus document
11095 just because we've downloaded a v2 networkstatus that we intend
11096 to cache. Fixes bug 545; bugfix on 0.2.0.x.
11099 Changes in version 0.2.0.10-alpha - 2007-11-10
11100 This tenth development snapshot adds a third v3 directory authority
11101 run by Mike Perry, adds most of Karsten Loesing's new hidden service
11102 descriptor format, fixes a bad crash bug and new bridge bugs introduced
11103 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
11104 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
11105 addresses many more minor issues.
11107 o New directory authorities:
11108 - Set up ides (run by Mike Perry) as the third v3 directory authority.
11111 - Allow tunnelled directory connections to ask for an encrypted
11112 "begin_dir" connection or an anonymized "uses a full Tor circuit"
11113 connection independently. Now we can make anonymized begin_dir
11114 connections for (e.g.) more secure hidden service posting and
11116 - More progress on proposal 114: code from Karsten Loesing to
11117 implement new hidden service descriptor format.
11118 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
11119 accommodate the growing number of servers that use the default
11120 and are reaching it.
11121 - Directory authorities use a new formula for selecting which nodes
11122 to advertise as Guards: they must be in the top 7/8 in terms of
11123 how long we have known about them, and above the median of those
11124 nodes in terms of weighted fractional uptime.
11125 - Make "not enough dir info yet" warnings describe *why* Tor feels
11126 it doesn't have enough directory info yet.
11129 - Stop servers from crashing if they set a Family option (or
11130 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
11132 - Make bridge users work again -- the move to v3 directories in
11133 0.2.0.9-alpha had introduced a number of bugs that made bridges
11134 no longer work for clients.
11135 - When the clock jumps forward a lot, do not allow the bandwidth
11136 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
11138 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
11139 - When the consensus lists a router descriptor that we previously were
11140 mirroring, but that we considered non-canonical, reload the
11141 descriptor as canonical. This fixes bug 543 where Tor servers
11142 would start complaining after a few days that they don't have
11143 enough directory information to build a circuit.
11144 - Consider replacing the current consensus when certificates arrive
11145 that make the pending consensus valid. Previously, we were only
11146 considering replacement when the new certs _didn't_ help.
11147 - Fix an assert error on startup if we didn't already have the
11148 consensus and certs cached in our datadirectory: we were caching
11149 the consensus in consensus_waiting_for_certs but then free'ing it
11151 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
11152 Request) if we need more v3 certs but we've already got pending
11153 requests for all of them.
11154 - Correctly back off from failing certificate downloads. Fixes
11156 - Authorities don't vote on the Running flag if they have been running
11157 for less than 30 minutes themselves. Fixes bug 547, where a newly
11158 started authority would vote that everyone was down.
11160 o New requirements:
11161 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11162 it, it had no AES, and it hasn't seen any security patches since
11166 - Clients now hold circuitless TLS connections open for 1.5 times
11167 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
11168 rebuild a new circuit over them within that timeframe. Previously,
11169 they held them open only for KeepalivePeriod (5 minutes).
11170 - Use "If-Modified-Since" to avoid retrieving consensus
11171 networkstatuses that we already have.
11172 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11173 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11174 we start knowing some directory caches.
11175 - When we receive a consensus from the future, warn about skew.
11176 - Improve skew reporting: try to give the user a better log message
11177 about how skewed they are, and how much this matters.
11178 - When we have a certificate for an authority, believe that
11179 certificate's claims about the authority's IP address.
11180 - New --quiet command-line option to suppress the default console log.
11181 Good in combination with --hash-password.
11182 - Authorities send back an X-Descriptor-Not-New header in response to
11183 an accepted-but-discarded descriptor upload. Partially implements
11185 - Make the log message for "tls error. breaking." more useful.
11186 - Better log messages about certificate downloads, to attempt to
11187 track down the second incarnation of bug 546.
11189 o Minor features (bridges):
11190 - If bridge users set UpdateBridgesFromAuthority, but the digest
11191 they ask for is a 404 from the bridge authority, they now fall
11192 back to trying the bridge directly.
11193 - Bridges now use begin_dir to publish their server descriptor to
11194 the bridge authority, even when they haven't set TunnelDirConns.
11196 o Minor features (controller):
11197 - When reporting clock skew, and we know that the clock is _at least
11198 as skewed_ as some value, but we don't know the actual value,
11199 report the value as a "minimum skew."
11202 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11203 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11207 - Refuse to start if both ORPort and UseBridges are set. Bugfix
11208 on 0.2.0.x, suggested by Matt Edman.
11209 - Don't stop fetching descriptors when FetchUselessDescriptors is
11210 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
11211 reported by tup and ioerror.
11212 - Better log message on vote from unknown authority.
11213 - Don't log "Launching 0 request for 0 router" message.
11215 o Minor bugfixes (memory leaks):
11216 - Stop leaking memory every time we parse a v3 certificate. Bugfix
11218 - Stop leaking memory every time we load a v3 certificate. Bugfix
11219 on 0.2.0.1-alpha. Fixes bug 536.
11220 - Stop leaking a cached networkstatus on exit. Bugfix on
11222 - Stop leaking voter information every time we free a consensus.
11223 Bugfix on 0.2.0.3-alpha.
11224 - Stop leaking signed data every time we check a voter signature.
11225 Bugfix on 0.2.0.3-alpha.
11226 - Stop leaking a signature every time we fail to parse a consensus or
11227 a vote. Bugfix on 0.2.0.3-alpha.
11228 - Stop leaking v2_download_status_map on shutdown. Bugfix on
11230 - Stop leaking conn->nickname every time we make a connection to a
11231 Tor relay without knowing its expected identity digest (e.g. when
11232 using bridges). Bugfix on 0.2.0.3-alpha.
11234 - Minor bugfixes (portability):
11235 - Run correctly on platforms where rlim_t is larger than unsigned
11236 long, and/or where the real limit for number of open files is
11237 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
11238 particular, these may be needed for OS X 10.5.
11241 Changes in version 0.1.2.18 - 2007-10-28
11242 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11243 hidden service introduction that were causing huge delays, and a big
11244 bug that was causing some servers to disappear from the network status
11245 lists for a few hours each day.
11247 o Major bugfixes (crashes):
11248 - If a connection is shut down abruptly because of something that
11249 happened inside connection_flushed_some(), do not call
11250 connection_finished_flushing(). Should fix bug 451:
11251 "connection_stop_writing: Assertion conn->write_event failed"
11252 Bugfix on 0.1.2.7-alpha.
11253 - Fix possible segfaults in functions called from
11254 rend_process_relay_cell().
11256 o Major bugfixes (hidden services):
11257 - Hidden services were choosing introduction points uniquely by
11258 hexdigest, but when constructing the hidden service descriptor
11259 they merely wrote the (potentially ambiguous) nickname.
11260 - Clients now use the v2 intro format for hidden service
11261 connections: they specify their chosen rendezvous point by identity
11262 digest rather than by (potentially ambiguous) nickname. These
11263 changes could speed up hidden service connections dramatically.
11265 o Major bugfixes (other):
11266 - Stop publishing a new server descriptor just because we get a
11267 HUP signal. This led (in a roundabout way) to some servers getting
11268 dropped from the networkstatus lists for a few hours each day.
11269 - When looking for a circuit to cannibalize, consider family as well
11270 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11271 circuit cannibalization).
11272 - When a router wasn't listed in a new networkstatus, we were leaving
11273 the flags for that router alone -- meaning it remained Named,
11274 Running, etc -- even though absence from the networkstatus means
11275 that it shouldn't be considered to exist at all anymore. Now we
11276 clear all the flags for routers that fall out of the networkstatus
11277 consensus. Fixes bug 529.
11280 - Don't try to access (or alter) the state file when running
11281 --list-fingerprint or --verify-config or --hash-password. Resolves
11283 - When generating information telling us how to extend to a given
11284 router, do not try to include the nickname if it is
11285 absent. Resolves bug 467.
11286 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11287 a way to trigger this remotely.)
11288 - When sending a status event to the controller telling it that an
11289 OR address is reachable, set the port correctly. (Previously we
11290 were reporting the dir port.)
11291 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11292 command. Bugfix on 0.1.2.17.
11293 - When loading bandwidth history, do not believe any information in
11294 the future. Fixes bug 434.
11295 - When loading entry guard information, do not believe any information
11297 - When we have our clock set far in the future and generate an
11298 onion key, then re-set our clock to be correct, we should not stop
11299 the onion key from getting rotated.
11300 - On some platforms, accept() can return a broken address. Detect
11301 this more quietly, and deal accordingly. Fixes bug 483.
11302 - It's not actually an error to find a non-pending entry in the DNS
11303 cache when canceling a pending resolve. Don't log unless stuff
11304 is fishy. Resolves bug 463.
11305 - Don't reset trusted dir server list when we set a configuration
11306 option. Patch from Robert Hogan.
11307 - Don't try to create the datadir when running --verify-config or
11308 --hash-password. Resolves bug 540.
11311 Changes in version 0.2.0.9-alpha - 2007-10-24
11312 This ninth development snapshot switches clients to the new v3 directory
11313 system; allows servers to be listed in the network status even when they
11314 have the same nickname as a registered server; and fixes many other
11315 bugs including a big one that was causing some servers to disappear
11316 from the network status lists for a few hours each day.
11318 o Major features (directory system):
11319 - Clients now download v3 consensus networkstatus documents instead
11320 of v2 networkstatus documents. Clients and caches now base their
11321 opinions about routers on these consensus documents. Clients only
11322 download router descriptors listed in the consensus.
11323 - Authorities now list servers who have the same nickname as
11324 a different named server, but list them with a new flag,
11325 "Unnamed". Now we can list servers that happen to pick the same
11326 nickname as a server that registered two years ago and then
11327 disappeared. Partially implements proposal 122.
11328 - If the consensus lists a router as "Unnamed", the name is assigned
11329 to a different router: do not identify the router by that name.
11330 Partially implements proposal 122.
11331 - Authorities can now come to a consensus on which method to use to
11332 compute the consensus. This gives us forward compatibility.
11335 - Stop publishing a new server descriptor just because we HUP or
11336 when we find our DirPort to be reachable but won't actually publish
11337 it. New descriptors without any real changes are dropped by the
11338 authorities, and can screw up our "publish every 18 hours" schedule.
11340 - When a router wasn't listed in a new networkstatus, we were leaving
11341 the flags for that router alone -- meaning it remained Named,
11342 Running, etc -- even though absence from the networkstatus means
11343 that it shouldn't be considered to exist at all anymore. Now we
11344 clear all the flags for routers that fall out of the networkstatus
11345 consensus. Fixes bug 529; bugfix on 0.1.2.x.
11346 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
11347 extrainfo documents and then discard them immediately for not
11348 matching the latest router. Bugfix on 0.2.0.1-alpha.
11350 o Minor features (v3 directory protocol):
11351 - Allow tor-gencert to generate a new certificate without replacing
11353 - Allow certificates to include an address.
11354 - When we change our directory-cache settings, reschedule all voting
11355 and download operations.
11356 - Reattempt certificate downloads immediately on failure, as long as
11357 we haven't failed a threshold number of times yet.
11358 - Delay retrying consensus downloads while we're downloading
11359 certificates to verify the one we just got. Also, count getting a
11360 consensus that we already have (or one that isn't valid) as a failure,
11361 and count failing to get the certificates after 20 minutes as a
11363 - Build circuits and download descriptors even if our consensus is a
11364 little expired. (This feature will go away once authorities are
11367 o Minor features (router descriptor cache):
11368 - If we find a cached-routers file that's been sitting around for more
11369 than 28 days unmodified, then most likely it's a leftover from
11370 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11372 - When we (as a cache) download a descriptor because it was listed
11373 in a consensus, remember when the consensus was supposed to expire,
11374 and don't expire the descriptor until then.
11376 o Minor features (performance):
11377 - Call routerlist_remove_old_routers() much less often. This should
11378 speed startup, especially on directory caches.
11379 - Don't try to launch new descriptor downloads quite so often when we
11380 already have enough directory information to build circuits.
11381 - Base64 decoding was actually showing up on our profile when parsing
11382 the initial descriptor file; switch to an in-process all-at-once
11383 implementation that's about 3.5x times faster than calling out to
11386 o Minor features (compilation):
11387 - Detect non-ASCII platforms (if any still exist) and refuse to
11388 build there: some of our code assumes that 'A' is 65 and so on.
11390 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
11391 - Make the "next period" votes into "current period" votes immediately
11392 after publishing the consensus; avoid a heisenbug that made them
11393 stick around indefinitely.
11394 - When we discard a vote as a duplicate, do not report this as
11396 - Treat missing v3 keys or certificates as an error when running as a
11397 v3 directory authority.
11398 - When we're configured to be a v3 authority, but we're only listed
11399 as a non-v3 authority in our DirServer line for ourself, correct
11401 - If an authority doesn't have a qualified hostname, just put
11402 its address in the vote. This fixes the problem where we referred to
11403 "moria on moria:9031."
11404 - Distinguish between detached signatures for the wrong period, and
11405 detached signatures for a divergent vote.
11406 - Fix a small memory leak when computing a consensus.
11407 - When there's no concensus, we were forming a vote every 30
11408 minutes, but writing the "valid-after" line in our vote based
11409 on our configured V3AuthVotingInterval: so unless the intervals
11410 matched up, we immediately rejected our own vote because it didn't
11411 start at the voting interval that caused us to construct a vote.
11413 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
11414 - Delete unverified-consensus when the real consensus is set.
11415 - Consider retrying a consensus networkstatus fetch immediately
11416 after one fails: don't wait 60 seconds to notice.
11417 - When fetching a consensus as a cache, wait until a newer consensus
11418 should exist before trying to replace the current one.
11419 - Use a more forgiving schedule for retrying failed consensus
11420 downloads than for other types.
11422 o Minor bugfixes (other directory issues):
11423 - Correct the implementation of "download votes by digest." Bugfix on
11425 - Authorities no longer send back "400 you're unreachable please fix
11426 it" errors to Tor servers that aren't online all the time. We're
11427 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
11429 o Minor bugfixes (controller):
11430 - Don't reset trusted dir server list when we set a configuration
11431 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
11432 - Respond to INT and TERM SIGNAL commands before we execute the
11433 signal, in case the signal shuts us down. We had a patch in
11434 0.1.2.1-alpha that tried to do this by queueing the response on
11435 the connection's buffer before shutting down, but that really
11436 isn't the same thing at all. Bug located by Matt Edman.
11438 o Minor bugfixes (misc):
11439 - Correctly check for bad options to the "PublishServerDescriptor"
11440 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
11441 - Stop leaking memory on failing case of base32_decode, and make
11442 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
11443 - Don't try to download extrainfo documents when we're trying to
11444 fetch enough directory info to build a circuit: having enough
11445 info should get priority. Bugfix on 0.2.0.x.
11446 - Don't complain that "your server has not managed to confirm that its
11447 ports are reachable" if we haven't been able to build any circuits
11448 yet. Bug found by spending four hours without a v3 consensus. Bugfix
11450 - Detect the reason for failing to mmap a descriptor file we just
11451 wrote, and give a more useful log message. Fixes bug 533. Bugfix
11454 o Code simplifications and refactoring:
11455 - Remove support for the old bw_accounting file: we've been storing
11456 bandwidth accounting information in the state file since
11457 0.1.2.5-alpha. This may result in bandwidth accounting errors
11458 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11459 downgrade to 0.1.1.x or earlier.
11460 - New convenience code to locate a file within the DataDirectory.
11461 - Move non-authority functionality out of dirvote.c.
11462 - Refactor the arguments for router_pick_{directory_|trusteddir}server
11463 so that they all take the same named flags.
11466 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11467 Unix users an easy way to script their Tor process (e.g. by
11468 adjusting bandwidth based on the time of the day).
11471 Changes in version 0.2.0.8-alpha - 2007-10-12
11472 This eighth development snapshot fixes a crash bug that's been bothering
11473 us since February 2007, lets bridge authorities store a list of bridge
11474 descriptors they've seen, gets v3 directory voting closer to working,
11475 starts caching v3 directory consensus documents on directory mirrors,
11476 and fixes a variety of smaller issues including some minor memory leaks.
11478 o Major features (router descriptor cache):
11479 - Store routers in a file called cached-descriptors instead of in
11480 cached-routers. Initialize cached-descriptors from cached-routers
11481 if the old format is around. The new format allows us to store
11482 annotations along with descriptors.
11483 - Use annotations to record the time we received each descriptor, its
11484 source, and its purpose.
11485 - Disable the SETROUTERPURPOSE controller command: it is now
11487 - Controllers should now specify cache=no or cache=yes when using
11488 the +POSTDESCRIPTOR command.
11489 - Bridge authorities now write bridge descriptors to disk, meaning
11490 we can export them to other programs and begin distributing them
11493 o Major features (directory authorities):
11494 - When a v3 authority is missing votes or signatures, it now tries
11496 - Directory authorities track weighted fractional uptime as well as
11497 weighted mean-time-between failures. WFU is suitable for deciding
11498 whether a node is "usually up", while MTBF is suitable for deciding
11499 whether a node is "likely to stay up." We need both, because
11500 "usually up" is a good requirement for guards, while "likely to
11501 stay up" is a good requirement for long-lived connections.
11503 o Major features (v3 directory system):
11504 - Caches now download v3 network status documents as needed,
11505 and download the descriptors listed in them.
11506 - All hosts now attempt to download and keep fresh v3 authority
11507 certificates, and re-attempt after failures.
11508 - More internal-consistency checks for vote parsing.
11510 o Major bugfixes (crashes):
11511 - If a connection is shut down abruptly because of something that
11512 happened inside connection_flushed_some(), do not call
11513 connection_finished_flushing(). Should fix bug 451. Bugfix on
11516 o Major bugfixes (performance):
11517 - Fix really bad O(n^2) performance when parsing a long list of
11518 routers: Instead of searching the entire list for an "extra-info "
11519 string which usually wasn't there, once for every routerinfo
11520 we read, just scan lines forward until we find one we like.
11522 - When we add data to a write buffer in response to the data on that
11523 write buffer getting low because of a flush, do not consider the
11524 newly added data as a candidate for immediate flushing, but rather
11525 make it wait until the next round of writing. Otherwise, we flush
11526 and refill recursively, and a single greedy TLS connection can
11527 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
11529 o Minor features (v3 authority system):
11530 - Add more ways for tools to download the votes that lead to the
11532 - Send a 503 when low on bandwidth and a vote, consensus, or
11533 certificate is requested.
11534 - If-modified-since is now implemented properly for all kinds of
11535 certificate requests.
11537 o Minor bugfixes (network statuses):
11538 - Tweak the implementation of proposal 109 slightly: allow at most
11539 two Tor servers on the same IP address, except if it's the location
11540 of a directory authority, in which case allow five. Bugfix on
11543 o Minor bugfixes (controller):
11544 - When sending a status event to the controller telling it that an
11545 OR address is reachable, set the port correctly. (Previously we
11546 were reporting the dir port.) Bugfix on 0.1.2.x.
11548 o Minor bugfixes (v3 directory system):
11549 - Fix logic to look up a cert by its signing key digest. Bugfix on
11551 - Only change the reply to a vote to "OK" if it's not already
11552 set. This gets rid of annoying "400 OK" log messages, which may
11553 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
11554 - When we get a valid consensus, recompute the voting schedule.
11555 - Base the valid-after time of a vote on the consensus voting
11556 schedule, not on our preferred schedule.
11557 - Make the return values and messages from signature uploads and
11558 downloads more sensible.
11559 - Fix a memory leak when serving votes and consensus documents, and
11560 another when serving certificates.
11562 o Minor bugfixes (performance):
11563 - Use a slightly simpler string hashing algorithm (copying Python's
11564 instead of Java's) and optimize our digest hashing algorithm to take
11565 advantage of 64-bit platforms and to remove some possibly-costly
11567 - Fix a minor memory leak whenever we parse guards from our state
11568 file. Bugfix on 0.2.0.7-alpha.
11569 - Fix a minor memory leak whenever we write out a file. Bugfix on
11571 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11572 command. Bugfix on 0.2.0.5-alpha.
11574 o Minor bugfixes (portability):
11575 - On some platforms, accept() can return a broken address. Detect
11576 this more quietly, and deal accordingly. Fixes bug 483.
11577 - Stop calling tor_strlower() on uninitialized memory in some cases.
11578 Bugfix in 0.2.0.7-alpha.
11580 o Minor bugfixes (usability):
11581 - Treat some 403 responses from directory servers as INFO rather than
11582 WARN-severity events.
11583 - It's not actually an error to find a non-pending entry in the DNS
11584 cache when canceling a pending resolve. Don't log unless stuff is
11585 fishy. Resolves bug 463.
11587 o Minor bugfixes (anonymity):
11588 - Never report that we've used more bandwidth than we're willing to
11589 relay: it leaks how much non-relay traffic we're using. Resolves
11591 - When looking for a circuit to cannibalize, consider family as well
11592 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11593 circuit cannibalization).
11595 o Code simplifications and refactoring:
11596 - Make a bunch of functions static. Remove some dead code.
11597 - Pull out about a third of the really big routerlist.c; put it in a
11598 new module, networkstatus.c.
11599 - Merge the extra fields in local_routerstatus_t back into
11600 routerstatus_t: we used to need one routerstatus_t for each
11601 authority's opinion, plus a local_routerstatus_t for the locally
11602 computed consensus opinion. To save space, we put the locally
11603 modified fields into local_routerstatus_t, and only the common
11604 stuff into routerstatus_t. But once v3 directories are in use,
11605 clients and caches will no longer need to hold authority opinions;
11606 thus, the rationale for keeping the types separate is now gone.
11607 - Make the code used to reschedule and reattempt downloads more
11609 - Turn all 'Are we a directory server/mirror?' logic into a call to
11611 - Remove the code to generate the oldest (v1) directory format.
11612 The code has been disabled since 0.2.0.5-alpha.
11615 Changes in version 0.2.0.7-alpha - 2007-09-21
11616 This seventh development snapshot makes bridges work again, makes bridge
11617 authorities work for the first time, fixes two huge performance flaws
11618 in hidden services, and fixes a variety of minor issues.
11620 o New directory authorities:
11621 - Set up moria1 and tor26 as the first v3 directory authorities. See
11622 doc/spec/dir-spec.txt for details on the new directory design.
11624 o Major bugfixes (crashes):
11625 - Fix possible segfaults in functions called from
11626 rend_process_relay_cell(). Bugfix on 0.1.2.x.
11628 o Major bugfixes (bridges):
11629 - Fix a bug that made servers send a "404 Not found" in response to
11630 attempts to fetch their server descriptor. This caused Tor servers
11631 to take many minutes to establish reachability for their DirPort,
11632 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
11633 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
11634 users configure that and specify a bridge with an identity
11635 fingerprint, now they will lookup the bridge descriptor at the
11636 default bridge authority via a one-hop tunnel, but once circuits
11637 are established they will switch to a three-hop tunnel for later
11638 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
11640 o Major bugfixes (hidden services):
11641 - Hidden services were choosing introduction points uniquely by
11642 hexdigest, but when constructing the hidden service descriptor
11643 they merely wrote the (potentially ambiguous) nickname.
11644 - Clients now use the v2 intro format for hidden service
11645 connections: they specify their chosen rendezvous point by identity
11646 digest rather than by (potentially ambiguous) nickname. Both
11647 are bugfixes on 0.1.2.x, and they could speed up hidden service
11648 connections dramatically. Thanks to Karsten Loesing.
11650 o Minor features (security):
11651 - As a client, do not believe any server that tells us that an
11652 address maps to an internal address space.
11653 - Make it possible to enable HashedControlPassword and
11654 CookieAuthentication at the same time.
11656 o Minor features (guard nodes):
11657 - Tag every guard node in our state file with the version that
11658 we believe added it, or with our own version if we add it. This way,
11659 if a user temporarily runs an old version of Tor and then switches
11660 back to a new one, she doesn't automatically lose her guards.
11662 o Minor features (speed):
11663 - When implementing AES counter mode, update only the portions of the
11664 counter buffer that need to change, and don't keep separate
11665 network-order and host-order counters when they are the same (i.e.,
11666 on big-endian hosts.)
11668 o Minor features (controller):
11669 - Accept LF instead of CRLF on controller, since some software has a
11670 hard time generating real Internet newlines.
11671 - Add GETINFO values for the server status events
11672 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
11675 o Removed features:
11676 - Routers no longer include bandwidth-history lines in their
11677 descriptors; this information is already available in extra-info
11678 documents, and including it in router descriptors took up 60%
11679 (!) of compressed router descriptor downloads. Completes
11680 implementation of proposal 104.
11681 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
11682 and TorControl.py, as they use the old v0 controller protocol,
11683 and are obsoleted by TorFlow anyway.
11684 - Drop support for v1 rendezvous descriptors, since we never used
11685 them anyway, and the code has probably rotted by now. Based on
11686 patch from Karsten Loesing.
11687 - On OSX, stop warning the user that kqueue support in libevent is
11688 "experimental", since it seems to have worked fine for ages.
11691 - When generating information telling us how to extend to a given
11692 router, do not try to include the nickname if it is absent. Fixes
11693 bug 467. Bugfix on 0.2.0.3-alpha.
11694 - Fix a user-triggerable (but not remotely-triggerable) segfault
11695 in expand_filename(). Bugfix on 0.1.2.x.
11696 - Fix a memory leak when freeing incomplete requests from DNSPort.
11697 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
11698 - Don't try to access (or alter) the state file when running
11699 --list-fingerprint or --verify-config or --hash-password. (Resolves
11700 bug 499.) Bugfix on 0.1.2.x.
11701 - Servers used to decline to publish their DirPort if their
11702 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
11703 were below a threshold. Now they only look at BandwidthRate and
11704 RelayBandwidthRate. Bugfix on 0.1.2.x.
11705 - Remove an optimization in the AES counter-mode code that assumed
11706 that the counter never exceeded 2^68. When the counter can be set
11707 arbitrarily as an IV (as it is by Karsten's new hidden services
11708 code), this assumption no longer holds. Bugfix on 0.1.2.x.
11709 - Resume listing "AUTHORITY" flag for authorities in network status.
11710 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
11712 o Code simplifications and refactoring:
11713 - Revamp file-writing logic so we don't need to have the entire
11714 contents of a file in memory at once before we write to disk. Tor,
11716 - Turn "descriptor store" into a full-fledged type.
11717 - Move all NT services code into a separate source file.
11718 - Unify all code that computes medians, percentile elements, etc.
11719 - Get rid of a needless malloc when parsing address policies.
11722 Changes in version 0.1.2.17 - 2007-08-30
11723 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
11724 X bundles. Vidalia 0.0.14 makes authentication required for the
11725 ControlPort in the default configuration, which addresses important
11726 security risks. Everybody who uses Vidalia (or another controller)
11729 In addition, this Tor update fixes major load balancing problems with
11730 path selection, which should speed things up a lot once many people
11733 o Major bugfixes (security):
11734 - We removed support for the old (v0) control protocol. It has been
11735 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
11736 become more of a headache than it's worth.
11738 o Major bugfixes (load balancing):
11739 - When choosing nodes for non-guard positions, weight guards
11740 proportionally less, since they already have enough load. Patch
11742 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11743 will allow fast Tor servers to get more attention.
11744 - When we're upgrading from an old Tor version, forget our current
11745 guards and pick new ones according to the new weightings. These
11746 three load balancing patches could raise effective network capacity
11747 by a factor of four. Thanks to Mike Perry for measurements.
11749 o Major bugfixes (stream expiration):
11750 - Expire not-yet-successful application streams in all cases if
11751 they've been around longer than SocksTimeout. Right now there are
11752 some cases where the stream will live forever, demanding a new
11753 circuit every 15 seconds. Fixes bug 454; reported by lodger.
11755 o Minor features (controller):
11756 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11757 is valid before any authentication has been received. It tells
11758 a controller what kind of authentication is expected, and what
11759 protocol is spoken. Implements proposal 119.
11761 o Minor bugfixes (performance):
11762 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
11763 greatly speeding up loading cached-routers from disk on startup.
11764 - Disable sentinel-based debugging for buffer code: we squashed all
11765 the bugs that this was supposed to detect a long time ago, and now
11766 its only effect is to change our buffer sizes from nice powers of
11767 two (which platform mallocs tend to like) to values slightly over
11768 powers of two (which make some platform mallocs sad).
11770 o Minor bugfixes (misc):
11771 - If exit bandwidth ever exceeds one third of total bandwidth, then
11772 use the correct formula to weight exit nodes when choosing paths.
11773 Based on patch from Mike Perry.
11774 - Choose perfectly fairly among routers when choosing by bandwidth and
11775 weighting by fraction of bandwidth provided by exits. Previously, we
11776 would choose with only approximate fairness, and correct ourselves
11777 if we ran off the end of the list.
11778 - If we require CookieAuthentication but we fail to write the
11779 cookie file, we would warn but not exit, and end up in a state
11780 where no controller could authenticate. Now we exit.
11781 - If we require CookieAuthentication, stop generating a new cookie
11782 every time we change any piece of our config.
11783 - Refuse to start with certain directory authority keys, and
11784 encourage people using them to stop.
11785 - Terminate multi-line control events properly. Original patch
11787 - Fix a minor memory leak when we fail to find enough suitable
11788 servers to choose a circuit.
11789 - Stop leaking part of the descriptor when we run into a particularly
11790 unparseable piece of it.
11793 Changes in version 0.2.0.6-alpha - 2007-08-26
11794 This sixth development snapshot features a new Vidalia version in the
11795 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
11796 the ControlPort in the default configuration, which addresses important
11799 In addition, this snapshot fixes major load balancing problems
11800 with path selection, which should speed things up a lot once many
11801 people have upgraded. The directory authorities also use a new
11802 mean-time-between-failure approach to tracking which servers are stable,
11803 rather than just looking at the most recent uptime.
11805 o New directory authorities:
11806 - Set up Tonga as the default bridge directory authority.
11809 - Directory authorities now track servers by weighted
11810 mean-times-between-failures. When we have 4 or more days of data,
11811 use measured MTBF rather than declared uptime to decide whether
11812 to call a router Stable. Implements proposal 108.
11814 o Major bugfixes (load balancing):
11815 - When choosing nodes for non-guard positions, weight guards
11816 proportionally less, since they already have enough load. Patch
11818 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
11819 will allow fast Tor servers to get more attention.
11820 - When we're upgrading from an old Tor version, forget our current
11821 guards and pick new ones according to the new weightings. These
11822 three load balancing patches could raise effective network capacity
11823 by a factor of four. Thanks to Mike Perry for measurements.
11825 o Major bugfixes (descriptor parsing):
11826 - Handle unexpected whitespace better in malformed descriptors. Bug
11827 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
11830 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
11831 GETINFO for Torstat to use until it can switch to using extrainfos.
11832 - Optionally (if built with -DEXPORTMALLINFO) export the output
11833 of mallinfo via http, as tor/mallinfo.txt. Only accessible
11837 - Do not intermix bridge routers with controller-added
11838 routers. (Bugfix on 0.2.0.x)
11839 - Do not fail with an assert when accept() returns an unexpected
11840 address family. Addresses but does not wholly fix bug 483. (Bugfix
11842 - Let directory authorities startup even when they can't generate
11843 a descriptor immediately, e.g. because they don't know their
11845 - Stop putting the authentication cookie in a file called "0"
11846 in your working directory if you don't specify anything for the
11847 new CookieAuthFile option. Reported by Matt Edman.
11848 - Make it possible to read the PROTOCOLINFO response in a way that
11849 conforms to our control-spec. Reported by Matt Edman.
11850 - Fix a minor memory leak when we fail to find enough suitable
11851 servers to choose a circuit. Bugfix on 0.1.2.x.
11852 - Stop leaking part of the descriptor when we run into a particularly
11853 unparseable piece of it. Bugfix on 0.1.2.x.
11854 - Unmap the extrainfo cache file on exit.
11857 Changes in version 0.2.0.5-alpha - 2007-08-19
11858 This fifth development snapshot fixes compilation on Windows again;
11859 fixes an obnoxious client-side bug that slowed things down and put
11860 extra load on the network; gets us closer to using the v3 directory
11861 voting scheme; makes it easier for Tor controllers to use cookie-based
11862 authentication; and fixes a variety of other bugs.
11864 o Removed features:
11865 - Version 1 directories are no longer generated in full. Instead,
11866 authorities generate and serve "stub" v1 directories that list
11867 no servers. This will stop Tor versions 0.1.0.x and earlier from
11868 working, but (for security reasons) nobody should be running those
11871 o Major bugfixes (compilation, 0.2.0.x):
11872 - Try to fix Win32 compilation again: improve checking for IPv6 types.
11873 - Try to fix MSVC compilation: build correctly on platforms that do
11874 not define s6_addr16 or s6_addr32.
11875 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
11878 o Major bugfixes (stream expiration):
11879 - Expire not-yet-successful application streams in all cases if
11880 they've been around longer than SocksTimeout. Right now there are
11881 some cases where the stream will live forever, demanding a new
11882 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
11883 reported by lodger.
11885 o Minor features (directory servers):
11886 - When somebody requests a list of statuses or servers, and we have
11887 none of those, return a 404 rather than an empty 200.
11889 o Minor features (directory voting):
11890 - Store v3 consensus status consensuses on disk, and reload them
11893 o Minor features (security):
11894 - Warn about unsafe ControlPort configurations.
11895 - Refuse to start with certain directory authority keys, and
11896 encourage people using them to stop.
11898 o Minor features (controller):
11899 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
11900 is valid before any authentication has been received. It tells
11901 a controller what kind of authentication is expected, and what
11902 protocol is spoken. Implements proposal 119.
11903 - New config option CookieAuthFile to choose a new location for the
11904 cookie authentication file, and config option
11905 CookieAuthFileGroupReadable to make it group-readable.
11907 o Minor features (unit testing):
11908 - Add command-line arguments to unit-test executable so that we can
11909 invoke any chosen test from the command line rather than having
11910 to run the whole test suite at once; and so that we can turn on
11911 logging for the unit tests.
11913 o Minor bugfixes (on 0.1.2.x):
11914 - If we require CookieAuthentication but we fail to write the
11915 cookie file, we would warn but not exit, and end up in a state
11916 where no controller could authenticate. Now we exit.
11917 - If we require CookieAuthentication, stop generating a new cookie
11918 every time we change any piece of our config.
11919 - When loading bandwidth history, do not believe any information in
11920 the future. Fixes bug 434.
11921 - When loading entry guard information, do not believe any information
11923 - When we have our clock set far in the future and generate an
11924 onion key, then re-set our clock to be correct, we should not stop
11925 the onion key from getting rotated.
11926 - Clean up torrc sample config file.
11927 - Do not automatically run configure from autogen.sh. This
11928 non-standard behavior tended to annoy people who have built other
11931 o Minor bugfixes (on 0.2.0.x):
11932 - Fix a bug with AutomapHostsOnResolve that would always cause
11933 the second request to fail. Bug reported by Kate. Bugfix on
11935 - Fix a bug in ADDRMAP controller replies that would sometimes
11936 try to print a NULL. Patch from tup.
11937 - Read v3 directory authority keys from the right location.
11938 - Numerous bugfixes to directory voting code.
11941 Changes in version 0.1.2.16 - 2007-08-01
11942 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
11943 remote attacker in certain situations to rewrite the user's torrc
11944 configuration file. This can completely compromise anonymity of users
11945 in most configurations, including those running the Vidalia bundles,
11946 TorK, etc. Or worse.
11948 o Major security fixes:
11949 - Close immediately after missing authentication on control port;
11950 do not allow multiple authentication attempts.
11953 Changes in version 0.2.0.4-alpha - 2007-08-01
11954 This fourth development snapshot fixes a critical security vulnerability
11955 for most users, specifically those running Vidalia, TorK, etc. Everybody
11956 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
11958 o Major security fixes:
11959 - Close immediately after missing authentication on control port;
11960 do not allow multiple authentication attempts.
11962 o Major bugfixes (compilation):
11963 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
11966 o Minor features (performance):
11967 - Be even more aggressive about releasing RAM from small
11968 empty buffers. Thanks to our free-list code, this shouldn't be too
11969 performance-intensive.
11970 - Disable sentinel-based debugging for buffer code: we squashed all
11971 the bugs that this was supposed to detect a long time ago, and
11972 now its only effect is to change our buffer sizes from nice
11973 powers of two (which platform mallocs tend to like) to values
11974 slightly over powers of two (which make some platform mallocs sad).
11975 - Log malloc statistics from mallinfo() on platforms where it
11979 Changes in version 0.2.0.3-alpha - 2007-07-29
11980 This third development snapshot introduces new experimental
11981 blocking-resistance features and a preliminary version of the v3
11982 directory voting design, and includes many other smaller features
11986 - The first pieces of our "bridge" design for blocking-resistance
11987 are implemented. People can run bridge directory authorities;
11988 people can run bridges; and people can configure their Tor clients
11989 with a set of bridges to use as the first hop into the Tor network.
11990 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
11992 - Create listener connections before we setuid to the configured
11993 User and Group. Now non-Windows users can choose port values
11994 under 1024, start Tor as root, and have Tor bind those ports
11995 before it changes to another UID. (Windows users could already
11997 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
11998 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
11999 on "vserver" accounts. (Patch from coderman.)
12000 - Be even more aggressive about separating local traffic from relayed
12001 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
12003 o Major features (experimental):
12004 - First cut of code for "v3 dir voting": directory authorities will
12005 vote on a common network status document rather than each publishing
12006 their own opinion. This code needs more testing and more corner-case
12007 handling before it's ready for use.
12010 - Directory authorities now call routers Fast if their bandwidth is
12011 at least 100KB/s, and consider their bandwidth adequate to be a
12012 Guard if it is at least 250KB/s, no matter the medians. This fix
12013 complements proposal 107. [Bugfix on 0.1.2.x]
12014 - Directory authorities now never mark more than 3 servers per IP as
12015 Valid and Running. (Implements proposal 109, by Kevin Bauer and
12017 - Minor change to organizationName and commonName generation
12018 procedures in TLS certificates during Tor handshakes, to invalidate
12019 some earlier censorware approaches. This is not a long-term
12020 solution, but applying it will give us a bit of time to look into
12021 the epidemiology of countermeasures as they spread.
12023 o Major bugfixes (directory):
12024 - Rewrite directory tokenization code to never run off the end of
12025 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
12027 o Minor features (controller):
12028 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
12029 match requests to applications. (Patch from Robert Hogan.)
12030 - Report address and port correctly on connections to DNSPort. (Patch
12031 from Robert Hogan.)
12032 - Add a RESOLVE command to launch hostname lookups. (Original patch
12033 from Robert Hogan.)
12034 - Add GETINFO status/enough-dir-info to let controllers tell whether
12035 Tor has downloaded sufficient directory information. (Patch
12037 - You can now use the ControlSocket option to tell Tor to listen for
12038 controller connections on Unix domain sockets on systems that
12039 support them. (Patch from Peter Palfrader.)
12040 - STREAM NEW events are generated for DNSPort requests and for
12041 tunneled directory connections. (Patch from Robert Hogan.)
12042 - New "GETINFO address-mappings/*" command to get address mappings
12043 with expiry information. "addr-mappings/*" is now deprecated.
12046 o Minor features (misc):
12047 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
12049 - The tor-gencert tool for v3 directory authorities now creates all
12050 files as readable to the file creator only, and write-protects
12051 the authority identity key.
12052 - When dumping memory usage, list bytes used in buffer memory
12054 - When running with dmalloc, dump more stats on hup and on exit.
12055 - Directory authorities now fail quickly and (relatively) harmlessly
12056 if they generate a network status document that is somehow
12059 o Traffic load balancing improvements:
12060 - If exit bandwidth ever exceeds one third of total bandwidth, then
12061 use the correct formula to weight exit nodes when choosing paths.
12062 (Based on patch from Mike Perry.)
12063 - Choose perfectly fairly among routers when choosing by bandwidth and
12064 weighting by fraction of bandwidth provided by exits. Previously, we
12065 would choose with only approximate fairness, and correct ourselves
12066 if we ran off the end of the list. [Bugfix on 0.1.2.x]
12068 o Performance improvements:
12069 - Be more aggressive with freeing buffer RAM or putting it on the
12071 - Use Critical Sections rather than Mutexes for synchronizing threads
12072 on win32; Mutexes are heavier-weight, and designed for synchronizing
12075 o Deprecated and removed features:
12076 - RedirectExits is now deprecated.
12077 - Stop allowing address masks that do not correspond to bit prefixes.
12078 We have warned about these for a really long time; now it's time
12079 to reject them. (Patch from croup.)
12081 o Minor bugfixes (directory):
12082 - Fix another crash bug related to extra-info caching. (Bug found by
12083 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
12084 - Directories no longer return a "304 not modified" when they don't
12085 have the networkstatus the client asked for. Also fix a memory
12086 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
12087 - We had accidentally labelled 0.1.2.x directory servers as not
12088 suitable for begin_dir requests, and had labelled no directory
12089 servers as suitable for uploading extra-info documents. [Bugfix
12092 o Minor bugfixes (dns):
12093 - Fix a crash when DNSPort is set more than once. (Patch from Robert
12094 Hogan.) [Bugfix on 0.2.0.2-alpha]
12095 - Add DNSPort connections to the global connection list, so that we
12096 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
12098 - Fix a dangling reference that could lead to a crash when DNSPort is
12099 changed or closed (Patch from Robert Hogan.) [Bugfix on
12102 o Minor bugfixes (controller):
12103 - Provide DNS expiry times in GMT, not in local time. For backward
12104 compatibility, ADDRMAP events only provide GMT expiry in an extended
12105 field. "GETINFO address-mappings" always does the right thing.
12106 - Use CRLF line endings properly in NS events.
12107 - Terminate multi-line control events properly. (Original patch
12108 from tup.) [Bugfix on 0.1.2.x-alpha]
12109 - Do not include spaces in SOURCE_ADDR fields in STREAM
12110 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
12113 Changes in version 0.1.2.15 - 2007-07-17
12114 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
12115 problems, fixes compilation on BSD, and fixes a variety of other
12116 bugs. Everybody should upgrade.
12118 o Major bugfixes (compilation):
12119 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
12121 o Major bugfixes (crashes):
12122 - Try even harder not to dereference the first character after
12123 an mmap(). Reported by lodger.
12124 - Fix a crash bug in directory authorities when we re-number the
12125 routerlist while inserting a new router.
12126 - When the cached-routers file is an even multiple of the page size,
12127 don't run off the end and crash. (Fixes bug 455; based on idea
12129 - Fix eventdns.c behavior on Solaris: It is critical to include
12130 orconfig.h _before_ sys/types.h, so that we can get the expected
12131 definition of _FILE_OFFSET_BITS.
12133 o Major bugfixes (security):
12134 - Fix a possible buffer overrun when using BSD natd support. Bug
12136 - When sending destroy cells from a circuit's origin, don't include
12137 the reason for tearing down the circuit. The spec says we didn't,
12138 and now we actually don't. Reported by lodger.
12139 - Keep streamids from different exits on a circuit separate. This
12140 bug may have allowed other routers on a given circuit to inject
12141 cells into streams. Reported by lodger; fixes bug 446.
12142 - If there's a never-before-connected-to guard node in our list,
12143 never choose any guards past it. This way we don't expand our
12144 guard list unless we need to.
12146 o Minor bugfixes (guard nodes):
12147 - Weight guard selection by bandwidth, so that low-bandwidth nodes
12148 don't get overused as guards.
12150 o Minor bugfixes (directory):
12151 - Correctly count the number of authorities that recommend each
12152 version. Previously, we were under-counting by 1.
12153 - Fix a potential crash bug when we load many server descriptors at
12154 once and some of them make others of them obsolete. Fixes bug 458.
12156 o Minor bugfixes (hidden services):
12157 - Stop tearing down the whole circuit when the user asks for a
12158 connection to a port that the hidden service didn't configure.
12161 o Minor bugfixes (misc):
12162 - On Windows, we were preventing other processes from reading
12163 cached-routers while Tor was running. Reported by janbar.
12164 - Fix a possible (but very unlikely) bug in picking routers by
12165 bandwidth. Add a log message to confirm that it is in fact
12166 unlikely. Patch from lodger.
12167 - Backport a couple of memory leak fixes.
12168 - Backport miscellaneous cosmetic bugfixes.
12171 Changes in version 0.2.0.2-alpha - 2007-06-02
12172 o Major bugfixes on 0.2.0.1-alpha:
12173 - Fix an assertion failure related to servers without extra-info digests.
12174 Resolves bugs 441 and 442.
12176 o Minor features (directory):
12177 - Support "If-Modified-Since" when answering HTTP requests for
12178 directories, running-routers documents, and network-status documents.
12179 (There's no need to support it for router descriptors, since those
12180 are downloaded by descriptor digest.)
12182 o Minor build issues:
12183 - Clear up some MIPSPro compiler warnings.
12184 - When building from a tarball on a machine that happens to have SVK
12185 installed, report the micro-revision as whatever version existed
12186 in the tarball, not as "x".
12189 Changes in version 0.2.0.1-alpha - 2007-06-01
12190 This early development snapshot provides new features for people running
12191 Tor as both a client and a server (check out the new RelayBandwidth
12192 config options); lets Tor run as a DNS proxy; and generally moves us
12193 forward on a lot of fronts.
12195 o Major features, server usability:
12196 - New config options RelayBandwidthRate and RelayBandwidthBurst:
12197 a separate set of token buckets for relayed traffic. Right now
12198 relayed traffic is defined as answers to directory requests, and
12199 OR connections that don't have any local circuits on them.
12201 o Major features, client usability:
12202 - A client-side DNS proxy feature to replace the need for
12203 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
12204 for DNS requests on port 9999, use the Tor network to resolve them
12205 anonymously, and send the reply back like a regular DNS server.
12206 The code still only implements a subset of DNS.
12207 - Make PreferTunneledDirConns and TunnelDirConns work even when
12208 we have no cached directory info. This means Tor clients can now
12209 do all of their connections protected by TLS.
12211 o Major features, performance and efficiency:
12212 - Directory authorities accept and serve "extra info" documents for
12213 routers. These documents contain fields from router descriptors
12214 that aren't usually needed, and that use a lot of excess
12215 bandwidth. Once these fields are removed from router descriptors,
12216 the bandwidth savings should be about 60%. [Partially implements
12218 - Servers upload extra-info documents to any authority that accepts
12219 them. Authorities (and caches that have been configured to download
12220 extra-info documents) download them as needed. [Partially implements
12222 - Change the way that Tor buffers data that it is waiting to write.
12223 Instead of queueing data cells in an enormous ring buffer for each
12224 client->OR or OR->OR connection, we now queue cells on a separate
12225 queue for each circuit. This lets us use less slack memory, and
12226 will eventually let us be smarter about prioritizing different kinds
12228 - Use memory pools to allocate cells with better speed and memory
12229 efficiency, especially on platforms where malloc() is inefficient.
12230 - Stop reading on edge connections when their corresponding circuit
12231 buffers are full; start again as the circuits empty out.
12233 o Major features, other:
12234 - Add an HSAuthorityRecordStats option that hidden service authorities
12235 can use to track statistics of overall hidden service usage without
12236 logging information that would be very useful to an attacker.
12237 - Start work implementing multi-level keys for directory authorities:
12238 Add a standalone tool to generate key certificates. (Proposal 103.)
12241 - Directory authorities now call routers Stable if they have an
12242 uptime of at least 30 days, even if that's not the median uptime
12243 in the network. Implements proposal 107, suggested by Kevin Bauer
12246 o Minor fixes (resource management):
12247 - Count the number of open sockets separately from the number
12248 of active connection_t objects. This will let us avoid underusing
12249 our allocated connection limit.
12250 - We no longer use socket pairs to link an edge connection to an
12251 anonymous directory connection or a DirPort test connection.
12252 Instead, we track the link internally and transfer the data
12253 in-process. This saves two sockets per "linked" connection (at the
12254 client and at the server), and avoids the nasty Windows socketpair()
12256 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
12257 for every single inactive connection_t. Free items from the
12258 4k/16k-buffer free lists when they haven't been used for a while.
12260 o Minor features (build):
12261 - Make autoconf search for libevent, openssl, and zlib consistently.
12262 - Update deprecated macros in configure.in.
12263 - When warning about missing headers, tell the user to let us
12264 know if the compile succeeds anyway, so we can downgrade the
12266 - Include the current subversion revision as part of the version
12267 string: either fetch it directly if we're in an SVN checkout, do
12268 some magic to guess it if we're in an SVK checkout, or use
12269 the last-detected version if we're building from a .tar.gz.
12270 Use this version consistently in log messages.
12272 o Minor features (logging):
12273 - Always prepend "Bug: " to any log message about a bug.
12274 - Put a platform string (e.g. "Linux i686") in the startup log
12275 message, so when people paste just their logs, we know if it's
12276 OpenBSD or Windows or what.
12277 - When logging memory usage, break down memory used in buffers by
12280 o Minor features (directory system):
12281 - New config option V2AuthoritativeDirectory that all directory
12282 authorities should set. This will let future authorities choose
12283 not to serve V2 directory information.
12284 - Directory authorities allow multiple router descriptors and/or extra
12285 info documents to be uploaded in a single go. This will make
12286 implementing proposal 104 simpler.
12288 o Minor features (controller):
12289 - Add a new config option __DisablePredictedCircuits designed for
12290 use by the controller, when we don't want Tor to build any circuits
12292 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
12293 so we can exit from the middle of the circuit.
12294 - Implement "getinfo status/circuit-established".
12295 - Implement "getinfo status/version/..." so a controller can tell
12296 whether the current version is recommended, and whether any versions
12297 are good, and how many authorities agree. (Patch from shibz.)
12299 o Minor features (hidden services):
12300 - Allow multiple HiddenServicePort directives with the same virtual
12301 port; when they occur, the user is sent round-robin to one
12302 of the target ports chosen at random. Partially fixes bug 393 by
12303 adding limited ad-hoc round-robining.
12305 o Minor features (other):
12307 - Add a new AutomapHostsOnResolve option: when it is enabled, any
12308 resolve request for hosts matching a given pattern causes Tor to
12309 generate an internal virtual address mapping for that host. This
12310 allows DNSPort to work sensibly with hidden service users. By
12311 default, .exit and .onion addresses are remapped; the list of
12312 patterns can be reconfigured with AutomapHostsSuffixes.
12313 - Add an "-F" option to tor-resolve to force a resolve for a .onion
12314 address. Thanks to the AutomapHostsOnResolve option, this is no
12315 longer a completely silly thing to do.
12316 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
12317 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
12318 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
12319 minus 1 byte: the actual maximum declared bandwidth.
12321 o Removed features:
12322 - Removed support for the old binary "version 0" controller protocol.
12323 This has been deprecated since 0.1.1, and warnings have been issued
12324 since 0.1.2. When we encounter a v0 control message, we now send
12325 back an error and close the connection.
12326 - Remove the old "dns worker" server DNS code: it hasn't been default
12327 since 0.1.2.2-alpha, and all the servers seem to be using the new
12330 o Minor bugfixes (portability):
12331 - Even though Windows is equally happy with / and \ as path separators,
12332 try to use \ consistently on Windows and / consistently on Unix: it
12333 makes the log messages nicer.
12334 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
12335 - Read resolv.conf files correctly on platforms where read() returns
12336 partial results on small file reads.
12338 o Minor bugfixes (directory):
12339 - Correctly enforce that elements of directory objects do not appear
12340 more often than they are allowed to appear.
12341 - When we are reporting the DirServer line we just parsed, we were
12342 logging the second stanza of the key fingerprint, not the first.
12344 o Minor bugfixes (logging):
12345 - When we hit an EOF on a log (probably because we're shutting down),
12346 don't try to remove the log from the list: just mark it as
12347 unusable. (Bulletproofs against bug 222.)
12349 o Minor bugfixes (other):
12350 - In the exitlist script, only consider the most recently published
12351 server descriptor for each server. Also, when the user requests
12352 a list of servers that _reject_ connections to a given address,
12353 explicitly exclude the IPs that also have servers that accept
12354 connections to that address. (Resolves bug 405.)
12355 - Stop allowing hibernating servers to be "stable" or "fast".
12356 - On Windows, we were preventing other processes from reading
12357 cached-routers while Tor was running. (Reported by janbar)
12358 - Make the NodeFamilies config option work. (Reported by
12359 lodger -- it has never actually worked, even though we added it
12361 - Check return values from pthread_mutex functions.
12362 - Don't save non-general-purpose router descriptors to the disk cache,
12363 because we have no way of remembering what their purpose was when
12365 - Add even more asserts to hunt down bug 417.
12366 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
12367 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
12368 Add a log message to confirm that it is in fact unlikely.
12370 o Minor bugfixes (controller):
12371 - Make 'getinfo fingerprint' return a 551 error if we're not a
12372 server, so we match what the control spec claims we do. Reported
12374 - Fix a typo in an error message when extendcircuit fails that
12375 caused us to not follow the \r\n-based delimiter protocol. Reported
12378 o Code simplifications and refactoring:
12379 - Stop passing around circuit_t and crypt_path_t pointers that are
12380 implicit in other procedure arguments.
12381 - Drop the old code to choke directory connections when the
12382 corresponding OR connections got full: thanks to the cell queue
12383 feature, OR conns don't get full any more.
12384 - Make dns_resolve() handle attaching connections to circuits
12385 properly, so the caller doesn't have to.
12386 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
12387 - Keep the connection array as a dynamic smartlist_t, rather than as
12388 a fixed-sized array. This is important, as the number of connections
12389 is becoming increasingly decoupled from the number of sockets.
12392 Changes in version 0.1.2.14 - 2007-05-25
12393 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12394 change especially affects those who serve or use hidden services),
12395 and fixes several other crash- and security-related bugs.
12397 o Directory authority changes:
12398 - Two directory authorities (moria1 and moria2) just moved to new
12399 IP addresses. This change will particularly affect those who serve
12400 or use hidden services.
12402 o Major bugfixes (crashes):
12403 - If a directory server runs out of space in the connection table
12404 as it's processing a begin_dir request, it will free the exit stream
12405 but leave it attached to the circuit, leading to unpredictable
12406 behavior. (Reported by seeess, fixes bug 425.)
12407 - Fix a bug in dirserv_remove_invalid() that would cause authorities
12408 to corrupt memory under some really unlikely scenarios.
12409 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
12410 - Avoid segfaults when reading from mmaped descriptor file. (Reported
12413 o Major bugfixes (security):
12414 - When choosing an entry guard for a circuit, avoid using guards
12415 that are in the same family as the chosen exit -- not just guards
12416 that are exactly the chosen exit. (Reported by lodger.)
12418 o Major bugfixes (resource management):
12419 - If a directory authority is down, skip it when deciding where to get
12420 networkstatus objects or descriptors. Otherwise we keep asking
12421 every 10 seconds forever. Fixes bug 384.
12422 - Count it as a failure if we fetch a valid network-status but we
12423 don't want to keep it. Otherwise we'll keep fetching it and keep
12424 not wanting to keep it. Fixes part of bug 422.
12425 - If all of our dirservers have given us bad or no networkstatuses
12426 lately, then stop hammering them once per minute even when we
12427 think they're failed. Fixes another part of bug 422.
12430 - Actually set the purpose correctly for descriptors inserted with
12431 purpose=controller.
12432 - When we have k non-v2 authorities in our DirServer config,
12433 we ignored the last k authorities in the list when updating our
12435 - Correctly back-off from requesting router descriptors that we are
12436 having a hard time downloading.
12437 - Read resolv.conf files correctly on platforms where read() returns
12438 partial results on small file reads.
12439 - Don't rebuild the entire router store every time we get 32K of
12440 routers: rebuild it when the journal gets very large, or when
12441 the gaps in the store get very large.
12444 - When routers publish SVN revisions in their router descriptors,
12445 authorities now include those versions correctly in networkstatus
12447 - Warn when using a version of libevent before 1.3b to run a server on
12448 OSX or BSD: these versions interact badly with userspace threads.
12451 Changes in version 0.1.2.13 - 2007-04-24
12452 This release features some major anonymity fixes, such as safer path
12453 selection; better client performance; faster bootstrapping, better
12454 address detection, and better DNS support for servers; write limiting as
12455 well as read limiting to make servers easier to run; and a huge pile of
12456 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
12458 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
12459 of the Freenode IRC network, remembering his patience and vision for
12460 free speech on the Internet.
12463 - Fix a memory leak when we ask for "all" networkstatuses and we
12464 get one we don't recognize.
12465 - Add more asserts to hunt down bug 417.
12466 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
12469 Changes in version 0.1.2.12-rc - 2007-03-16
12471 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
12472 directory information requested inside Tor connections (i.e. via
12473 begin_dir cells). It only triggered when the same connection was
12474 serving other data at the same time. Reported by seeess.
12477 - When creating a circuit via the controller, send a 'launched'
12478 event when we're done, so we follow the spec better.
12481 Changes in version 0.1.2.11-rc - 2007-03-15
12482 o Minor bugfixes (controller), reported by daejees:
12483 - Correct the control spec to match how the code actually responds
12484 to 'getinfo addr-mappings/*'.
12485 - The control spec described a GUARDS event, but the code
12486 implemented a GUARD event. Standardize on GUARD, but let people
12487 ask for GUARDS too.
12490 Changes in version 0.1.2.10-rc - 2007-03-07
12491 o Major bugfixes (Windows):
12492 - Do not load the NT services library functions (which may not exist)
12493 just to detect if we're a service trying to shut down. Now we run
12494 on Win98 and friends again.
12496 o Minor bugfixes (other):
12497 - Clarify a couple of log messages.
12498 - Fix a misleading socks5 error number.
12501 Changes in version 0.1.2.9-rc - 2007-03-02
12502 o Major bugfixes (Windows):
12503 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
12504 of the usual GCC "%llu". This prevents a bug when saving 64-bit
12505 int configuration values: the high-order 32 bits would get
12506 truncated. In particular, we were being bitten by the default
12507 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
12508 and maybe also bug 397.)
12510 o Minor bugfixes (performance):
12511 - Use OpenSSL's AES implementation on platforms where it's faster.
12512 This could save us as much as 10% CPU usage.
12514 o Minor bugfixes (server):
12515 - Do not rotate onion key immediately after setting it for the first
12518 o Minor bugfixes (directory authorities):
12519 - Stop calling servers that have been hibernating for a long time
12520 "stable". Also, stop letting hibernating or obsolete servers affect
12521 uptime and bandwidth cutoffs.
12522 - Stop listing hibernating servers in the v1 directory.
12524 o Minor bugfixes (hidden services):
12525 - Upload hidden service descriptors slightly less often, to reduce
12526 load on authorities.
12528 o Minor bugfixes (other):
12529 - Fix an assert that could trigger if a controller quickly set then
12530 cleared EntryNodes. Bug found by Udo van den Heuvel.
12531 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
12533 - Fix a potential race condition in the rpm installer. Found by
12535 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
12536 of 2 as indicating that the server is completely bad; it sometimes
12537 means that the server is just bad for the request in question. (may fix
12538 the last of bug 326.)
12539 - Disable encrypted directory connections when we don't have a server
12540 descriptor for the destination. We'll get this working again in
12544 Changes in version 0.1.2.8-beta - 2007-02-26
12545 o Major bugfixes (crashes):
12546 - Stop crashing when the controller asks us to resetconf more than
12547 one config option at once. (Vidalia 0.0.11 does this.)
12548 - Fix a crash that happened on Win98 when we're given command-line
12549 arguments: don't try to load NT service functions from advapi32.dll
12550 except when we need them. (Bug introduced in 0.1.2.7-alpha;
12552 - Fix a longstanding obscure crash bug that could occur when
12553 we run out of DNS worker processes. (Resolves bug 390.)
12555 o Major bugfixes (hidden services):
12556 - Correctly detect whether hidden service descriptor downloads are
12557 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
12559 o Major bugfixes (accounting):
12560 - When we start during an accounting interval before it's time to wake
12561 up, remember to wake up at the correct time. (May fix bug 342.)
12563 o Minor bugfixes (controller):
12564 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12565 clear the corresponding on_circuit variable, and remember later
12566 that we don't need to send a redundant CLOSED event. Resolves part
12568 - Report events where a resolve succeeded or where we got a socks
12569 protocol error correctly, rather than calling both of them
12571 - Change reported stream target addresses to IP consistently when
12572 we finally get the IP from an exit node.
12573 - Send log messages to the controller even if they happen to be very
12576 o Minor bugfixes (other):
12577 - Display correct results when reporting which versions are
12578 recommended, and how recommended they are. (Resolves bug 383.)
12579 - Improve our estimates for directory bandwidth to be less random:
12580 guess that an unrecognized directory will have the average bandwidth
12581 from all known directories, not that it will have the average
12582 bandwidth from those directories earlier than it on the list.
12583 - If we start a server with ClientOnly 1, then set ClientOnly to 0
12584 and hup, stop triggering an assert based on an empty onion_key.
12585 - On platforms with no working mmap() equivalent, don't warn the
12586 user when cached-routers doesn't exist.
12587 - Warn the user when mmap() [or its equivalent] fails for some reason
12588 other than file-not-found.
12589 - Don't warn the user when cached-routers.new doesn't exist: that's
12590 perfectly fine when starting up for the first time.
12591 - When EntryNodes are configured, rebuild the guard list to contain,
12592 in order: the EntryNodes that were guards before; the rest of the
12593 EntryNodes; the nodes that were guards before.
12594 - Mask out all signals in sub-threads; only the libevent signal
12595 handler should be processing them. This should prevent some crashes
12596 on some machines using pthreads. (Patch from coderman.)
12597 - Fix switched arguments on memset in the implementation of
12598 tor_munmap() for systems with no mmap() call.
12599 - When Tor receives a router descriptor that it asked for, but
12600 no longer wants (because it has received fresh networkstatuses
12601 in the meantime), do not warn the user. Cache the descriptor if
12602 we're a cache; drop it if we aren't.
12603 - Make earlier entry guards _really_ get retried when the network
12605 - On a malformed DNS reply, always give an error to the corresponding
12607 - Build with recent libevents on platforms that do not define the
12608 nonstandard types "u_int8_t" and friends.
12610 o Minor features (controller):
12611 - Warn the user when an application uses the obsolete binary v0
12612 control protocol. We're planning to remove support for it during
12613 the next development series, so it's good to give people some
12615 - Add STREAM_BW events to report per-entry-stream bandwidth
12616 use. (Patch from Robert Hogan.)
12617 - Rate-limit SIGNEWNYM signals in response to controllers that
12618 impolitely generate them for every single stream. (Patch from
12619 mwenge; closes bug 394.)
12620 - Make REMAP stream events have a SOURCE (cache or exit), and
12621 make them generated in every case where we get a successful
12622 connected or resolved cell.
12624 o Minor bugfixes (performance):
12625 - Call router_have_min_dir_info half as often. (This is showing up in
12626 some profiles, but not others.)
12627 - When using GCC, make log_debug never get called at all, and its
12628 arguments never get evaluated, when no debug logs are configured.
12629 (This is showing up in some profiles, but not others.)
12632 - Remove some never-implemented options. Mark PathlenCoinWeight as
12634 - Implement proposal 106: Stop requiring clients to have well-formed
12635 certificates; stop checking nicknames in certificates. (Clients
12636 have certificates so that they can look like Tor servers, but in
12637 the future we might want to allow them to look like regular TLS
12638 clients instead. Nicknames in certificates serve no purpose other
12639 than making our protocol easier to recognize on the wire.)
12640 - Revise messages on handshake failure again to be even more clear about
12641 which are incoming connections and which are outgoing.
12642 - Discard any v1 directory info that's over 1 month old (for
12643 directories) or over 1 week old (for running-routers lists).
12644 - Do not warn when individual nodes in the configuration's EntryNodes,
12645 ExitNodes, etc are down: warn only when all possible nodes
12646 are down. (Fixes bug 348.)
12647 - Always remove expired routers and networkstatus docs before checking
12648 whether we have enough information to build circuits. (Fixes
12650 - Put a lower-bound on MaxAdvertisedBandwidth.
12653 Changes in version 0.1.2.7-alpha - 2007-02-06
12654 o Major bugfixes (rate limiting):
12655 - Servers decline directory requests much more aggressively when
12656 they're low on bandwidth. Otherwise they end up queueing more and
12657 more directory responses, which can't be good for latency.
12658 - But never refuse directory requests from local addresses.
12659 - Fix a memory leak when sending a 503 response for a networkstatus
12661 - Be willing to read or write on local connections (e.g. controller
12662 connections) even when the global rate limiting buckets are empty.
12663 - If our system clock jumps back in time, don't publish a negative
12664 uptime in the descriptor. Also, don't let the global rate limiting
12665 buckets go absurdly negative.
12666 - Flush local controller connection buffers periodically as we're
12667 writing to them, so we avoid queueing 4+ megabytes of data before
12670 o Major bugfixes (NT services):
12671 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
12672 command-line flag so that admins can override the default by saying
12673 "tor --service install --user "SomeUser"". This will not affect
12674 existing installed services. Also, warn the user that the service
12675 will look for its configuration file in the service user's
12676 %appdata% directory. (We can't do the 'hardwire the user's appdata
12677 directory' trick any more, since we may not have read access to that
12680 o Major bugfixes (other):
12681 - Previously, we would cache up to 16 old networkstatus documents
12682 indefinitely, if they came from nontrusted authorities. Now we
12683 discard them if they are more than 10 days old.
12684 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
12686 - Detect and reject malformed DNS responses containing circular
12688 - If exits are rare enough that we're not marking exits as guards,
12689 ignore exit bandwidth when we're deciding the required bandwidth
12691 - When we're handling a directory connection tunneled over Tor,
12692 don't fill up internal memory buffers with all the data we want
12693 to tunnel; instead, only add it if the OR connection that will
12694 eventually receive it has some room for it. (This can lead to
12695 slowdowns in tunneled dir connections; a better solution will have
12696 to wait for 0.2.0.)
12698 o Minor bugfixes (dns):
12699 - Add some defensive programming to eventdns.c in an attempt to catch
12700 possible memory-stomping bugs.
12701 - Detect and reject DNS replies containing IPv4 or IPv6 records with
12702 an incorrect number of bytes. (Previously, we would ignore the
12704 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
12705 in the correct order, and doesn't crash.
12706 - Free memory held in recently-completed DNS lookup attempts on exit.
12707 This was not a memory leak, but may have been hiding memory leaks.
12708 - Handle TTL values correctly on reverse DNS lookups.
12709 - Treat failure to parse resolv.conf as an error.
12711 o Minor bugfixes (other):
12712 - Fix crash with "tor --list-fingerprint" (reported by seeess).
12713 - When computing clock skew from directory HTTP headers, consider what
12714 time it was when we finished asking for the directory, not what
12716 - Expire socks connections if they spend too long waiting for the
12717 handshake to finish. Previously we would let them sit around for
12718 days, if the connecting application didn't close them either.
12719 - And if the socks handshake hasn't started, don't send a
12720 "DNS resolve socks failed" handshake reply; just close it.
12721 - Stop using C functions that OpenBSD's linker doesn't like.
12722 - Don't launch requests for descriptors unless we have networkstatuses
12723 from at least half of the authorities. This delays the first
12724 download slightly under pathological circumstances, but can prevent
12725 us from downloading a bunch of descriptors we don't need.
12726 - Do not log IPs with TLS failures for incoming TLS
12727 connections. (Fixes bug 382.)
12728 - If the user asks to use invalid exit nodes, be willing to use
12730 - Stop using the reserved ac_cv namespace in our configure script.
12731 - Call stat() slightly less often; use fstat() when possible.
12732 - Refactor the way we handle pending circuits when an OR connection
12733 completes or fails, in an attempt to fix a rare crash bug.
12734 - Only rewrite a conn's address based on X-Forwarded-For: headers
12735 if it's a parseable public IP address; and stop adding extra quotes
12736 to the resulting address.
12739 - Weight directory requests by advertised bandwidth. Now we can
12740 let servers enable write limiting but still allow most clients to
12741 succeed at their directory requests. (We still ignore weights when
12742 choosing a directory authority; I hope this is a feature.)
12745 - Create a new file ReleaseNotes which was the old ChangeLog. The
12746 new ChangeLog file now includes the summaries for all development
12748 - Check for addresses with invalid characters at the exit as well
12749 as at the client, and warn less verbosely when they fail. You can
12750 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
12751 - Adapt a patch from goodell to let the contrib/exitlist script
12752 take arguments rather than require direct editing.
12753 - Inform the server operator when we decide not to advertise a
12754 DirPort due to AccountingMax enabled or a low BandwidthRate. It
12755 was confusing Zax, so now we're hopefully more helpful.
12756 - Bring us one step closer to being able to establish an encrypted
12757 directory tunnel without knowing a descriptor first. Still not
12758 ready yet. As part of the change, now assume we can use a
12759 create_fast cell if we don't know anything about a router.
12760 - Allow exit nodes to use nameservers running on ports other than 53.
12761 - Servers now cache reverse DNS replies.
12762 - Add an --ignore-missing-torrc command-line option so that we can
12763 get the "use sensible defaults if the configuration file doesn't
12764 exist" behavior even when specifying a torrc location on the command
12767 o Minor features (controller):
12768 - Track reasons for OR connection failure; make these reasons
12769 available via the controller interface. (Patch from Mike Perry.)
12770 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
12771 can learn when clients are sending malformed hostnames to Tor.
12772 - Clean up documentation for controller status events.
12773 - Add a REMAP status to stream events to note that a stream's
12774 address has changed because of a cached address or a MapAddress
12778 Changes in version 0.1.2.6-alpha - 2007-01-09
12780 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
12781 connection handles more than 4 gigs in either direction, we crash.
12782 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
12783 advertised exit node, somebody might try to exit from us when
12784 we're bootstrapping and before we've built our descriptor yet.
12785 Refuse the connection rather than crashing.
12788 - Warn if we (as a server) find that we've resolved an address that we
12789 weren't planning to resolve.
12790 - Warn that using select() on any libevent version before 1.1 will be
12791 unnecessarily slow (even for select()).
12792 - Flush ERR-level controller status events just like we currently
12793 flush ERR-level log events, so that a Tor shutdown doesn't prevent
12794 the controller from learning about current events.
12796 o Minor features (more controller status events):
12797 - Implement EXTERNAL_ADDRESS server status event so controllers can
12798 learn when our address changes.
12799 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
12800 can learn when directories reject our descriptor.
12801 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
12802 can learn when a client application is speaking a non-socks protocol
12804 - Implement DANGEROUS_SOCKS client status event so controllers
12805 can learn when a client application is leaking DNS addresses.
12806 - Implement BUG general status event so controllers can learn when
12807 Tor is unhappy about its internal invariants.
12808 - Implement CLOCK_SKEW general status event so controllers can learn
12809 when Tor thinks the system clock is set incorrectly.
12810 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
12811 server status events so controllers can learn when their descriptors
12812 are accepted by a directory.
12813 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
12814 server status events so controllers can learn about Tor's progress in
12815 deciding whether it's reachable from the outside.
12816 - Implement BAD_LIBEVENT general status event so controllers can learn
12817 when we have a version/method combination in libevent that needs to
12819 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
12820 and DNS_USELESS server status events so controllers can learn
12821 about changes to DNS server status.
12823 o Minor features (directory):
12824 - Authorities no longer recommend exits as guards if this would shift
12825 too much load to the exit nodes.
12828 Changes in version 0.1.2.5-alpha - 2007-01-06
12830 - Enable write limiting as well as read limiting. Now we sacrifice
12831 capacity if we're pushing out lots of directory traffic, rather
12832 than overrunning the user's intended bandwidth limits.
12833 - Include TLS overhead when counting bandwidth usage; previously, we
12834 would count only the bytes sent over TLS, but not the bytes used
12836 - Support running the Tor service with a torrc not in the same
12837 directory as tor.exe and default to using the torrc located in
12838 the %appdata%\Tor\ of the user who installed the service. Patch
12840 - Servers now check for the case when common DNS requests are going to
12841 wildcarded addresses (i.e. all getting the same answer), and change
12842 their exit policy to reject *:* if it's happening.
12843 - Implement BEGIN_DIR cells, so we can connect to the directory
12844 server via TLS to do encrypted directory requests rather than
12845 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
12846 config options if you like.
12848 o Minor features (config and docs):
12849 - Start using the state file to store bandwidth accounting data:
12850 the bw_accounting file is now obsolete. We'll keep generating it
12851 for a while for people who are still using 0.1.2.4-alpha.
12852 - Try to batch changes to the state file so that we do as few
12853 disk writes as possible while still storing important things in
12855 - The state file and the bw_accounting file get saved less often when
12856 the AvoidDiskWrites config option is set.
12857 - Make PIDFile work on Windows (untested).
12858 - Add internal descriptions for a bunch of configuration options:
12859 accessible via controller interface and in comments in saved
12861 - Reject *:563 (NNTPS) in the default exit policy. We already reject
12862 NNTP by default, so this seems like a sensible addition.
12863 - Clients now reject hostnames with invalid characters. This should
12864 avoid some inadvertent info leaks. Add an option
12865 AllowNonRFC953Hostnames to disable this behavior, in case somebody
12866 is running a private network with hosts called @, !, and #.
12867 - Add a maintainer script to tell us which options are missing
12868 documentation: "make check-docs".
12869 - Add a new address-spec.txt document to describe our special-case
12870 addresses: .exit, .onion, and .noconnnect.
12872 o Minor features (DNS):
12873 - Ongoing work on eventdns infrastructure: now it has dns server
12874 and ipv6 support. One day Tor will make use of it.
12875 - Add client-side caching for reverse DNS lookups.
12876 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
12877 - When we change nameservers or IP addresses, reset and re-launch
12878 our tests for DNS hijacking.
12880 o Minor features (directory):
12881 - Authorities now specify server versions in networkstatus. This adds
12882 about 2% to the size of compressed networkstatus docs, and allows
12883 clients to tell which servers support BEGIN_DIR and which don't.
12884 The implementation is forward-compatible with a proposed future
12885 protocol version scheme not tied to Tor versions.
12886 - DirServer configuration lines now have an orport= option so
12887 clients can open encrypted tunnels to the authorities without
12888 having downloaded their descriptors yet. Enabled for moria1,
12889 moria2, tor26, and lefkada now in the default configuration.
12890 - Directory servers are more willing to send a 503 "busy" if they
12891 are near their write limit, especially for v1 directory requests.
12892 Now they can use their limited bandwidth for actual Tor traffic.
12893 - Clients track responses with status 503 from dirservers. After a
12894 dirserver has given us a 503, we try not to use it until an hour has
12895 gone by, or until we have no dirservers that haven't given us a 503.
12896 - When we get a 503 from a directory, and we're not a server, we don't
12897 count the failure against the total number of failures allowed
12898 for the thing we're trying to download.
12899 - Report X-Your-Address-Is correctly from tunneled directory
12900 connections; don't report X-Your-Address-Is when it's an internal
12901 address; and never believe reported remote addresses when they're
12903 - Protect against an unlikely DoS attack on directory servers.
12904 - Add a BadDirectory flag to network status docs so that authorities
12905 can (eventually) tell clients about caches they believe to be
12908 o Minor features (controller):
12909 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
12910 - Reimplement GETINFO so that info/names stays in sync with the
12912 - Implement "GETINFO fingerprint".
12913 - Implement "SETEVENTS GUARD" so controllers can get updates on
12914 entry guard status as it changes.
12916 o Minor features (clean up obsolete pieces):
12917 - Remove some options that have been deprecated since at least
12918 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
12919 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
12920 to set log options.
12921 - We no longer look for identity and onion keys in "identity.key" and
12922 "onion.key" -- these were replaced by secret_id_key and
12923 secret_onion_key in 0.0.8pre1.
12924 - We no longer require unrecognized directory entries to be
12927 o Major bugfixes (security):
12928 - Stop sending the HttpProxyAuthenticator string to directory
12929 servers when directory connections are tunnelled through Tor.
12930 - Clients no longer store bandwidth history in the state file.
12931 - Do not log introduction points for hidden services if SafeLogging
12933 - When generating bandwidth history, round down to the nearest
12934 1k. When storing accounting data, round up to the nearest 1k.
12935 - When we're running as a server, remember when we last rotated onion
12936 keys, so that we will rotate keys once they're a week old even if
12937 we never stay up for a week ourselves.
12939 o Major bugfixes (other):
12940 - Fix a longstanding bug in eventdns that prevented the count of
12941 timed-out resolves from ever being reset. This bug caused us to
12942 give up on a nameserver the third time it timed out, and try it
12943 10 seconds later... and to give up on it every time it timed out
12945 - Take out the '5 second' timeout from the connection retry
12946 schedule. Now the first connect attempt will wait a full 10
12947 seconds before switching to a new circuit. Perhaps this will help
12948 a lot. Based on observations from Mike Perry.
12949 - Fix a bug on the Windows implementation of tor_mmap_file() that
12950 would prevent the cached-routers file from ever loading. Reported
12954 - Fix an assert failure when a directory authority sets
12955 AuthDirRejectUnlisted and then receives a descriptor from an
12956 unlisted router. Reported by seeess.
12957 - Avoid a double-free when parsing malformed DirServer lines.
12958 - Fix a bug when a BSD-style PF socket is first used. Patch from
12960 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
12961 to resolve an address at a given exit node even when they ask for
12963 - Servers no longer ever list themselves in their "family" line,
12964 even if configured to do so. This makes it easier to configure
12965 family lists conveniently.
12966 - When running as a server, don't fall back to 127.0.0.1 when no
12967 nameservers are configured in /etc/resolv.conf; instead, make the
12968 user fix resolv.conf or specify nameservers explicitly. (Resolves
12970 - Stop accepting certain malformed ports in configured exit policies.
12971 - Don't re-write the fingerprint file every restart, unless it has
12973 - Stop warning when a single nameserver fails: only warn when _all_ of
12974 our nameservers have failed. Also, when we only have one nameserver,
12975 raise the threshold for deciding that the nameserver is dead.
12976 - Directory authorities now only decide that routers are reachable
12977 if their identity keys are as expected.
12978 - When the user uses bad syntax in the Log config line, stop
12979 suggesting other bad syntax as a replacement.
12980 - Correctly detect ipv6 DNS capability on OpenBSD.
12982 o Minor bugfixes (controller):
12983 - Report the circuit number correctly in STREAM CLOSED events. Bug
12984 reported by Mike Perry.
12985 - Do not report bizarre values for results of accounting GETINFOs
12986 when the last second's write or read exceeds the allotted bandwidth.
12987 - Report "unrecognized key" rather than an empty string when the
12988 controller tries to fetch a networkstatus that doesn't exist.
12991 Changes in version 0.1.1.26 - 2006-12-14
12992 o Security bugfixes:
12993 - Stop sending the HttpProxyAuthenticator string to directory
12994 servers when directory connections are tunnelled through Tor.
12995 - Clients no longer store bandwidth history in the state file.
12996 - Do not log introduction points for hidden services if SafeLogging
13000 - Fix an assert failure when a directory authority sets
13001 AuthDirRejectUnlisted and then receives a descriptor from an
13002 unlisted router (reported by seeess).
13005 Changes in version 0.1.2.4-alpha - 2006-12-03
13007 - Add support for using natd; this allows FreeBSDs earlier than
13008 5.1.2 to have ipfw send connections through Tor without using
13009 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
13012 - Make all connections to addresses of the form ".noconnect"
13013 immediately get closed. This lets application/controller combos
13014 successfully test whether they're talking to the same Tor by
13015 watching for STREAM events.
13016 - Make cross.sh cross-compilation script work even when autogen.sh
13017 hasn't been run. (Patch from Michael Mohr.)
13018 - Statistics dumped by -USR2 now include a breakdown of public key
13019 operations, for profiling.
13022 - Fix a major leak when directory authorities parse their
13023 approved-routers list, a minor memory leak when we fail to pick
13024 an exit node, and a few rare leaks on errors.
13025 - Handle TransPort connections even when the server sends data before
13026 the client sends data. Previously, the connection would just hang
13027 until the client sent data. (Patch from tup based on patch from
13029 - Avoid assert failure when our cached-routers file is empty on
13033 - Don't log spurious warnings when we see a circuit close reason we
13034 don't recognize; it's probably just from a newer version of Tor.
13035 - Have directory authorities allow larger amounts of drift in uptime
13036 without replacing the server descriptor: previously, a server that
13037 restarted every 30 minutes could have 48 "interesting" descriptors
13039 - Start linking to the Tor specification and Tor reference manual
13040 correctly in the Windows installer.
13041 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13042 Tor/Privoxy we also uninstall Vidalia.
13043 - Resume building on Irix64, and fix a lot of warnings from its
13044 MIPSpro C compiler.
13045 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
13046 when we're running as a client.
13049 Changes in version 0.1.1.25 - 2006-11-04
13051 - When a client asks us to resolve (rather than connect to)
13052 an address, and we have a cached answer, give them the cached
13053 answer. Previously, we would give them no answer at all.
13054 - We were building exactly the wrong circuits when we predict
13055 hidden service requirements, meaning Tor would have to build all
13056 its circuits on demand.
13057 - If none of our live entry guards have a high uptime, but we
13058 require a guard with a high uptime, try adding a new guard before
13059 we give up on the requirement. This patch should make long-lived
13060 connections more stable on average.
13061 - When testing reachability of our DirPort, don't launch new
13062 tests when there's already one in progress -- unreachable
13063 servers were stacking up dozens of testing streams.
13065 o Security bugfixes:
13066 - When the user sends a NEWNYM signal, clear the client-side DNS
13067 cache too. Otherwise we continue to act on previous information.
13070 - Avoid a memory corruption bug when creating a hash table for
13072 - Avoid possibility of controller-triggered crash when misusing
13073 certain commands from a v0 controller on platforms that do not
13074 handle printf("%s",NULL) gracefully.
13075 - Avoid infinite loop on unexpected controller input.
13076 - Don't log spurious warnings when we see a circuit close reason we
13077 don't recognize; it's probably just from a newer version of Tor.
13078 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13079 Tor/Privoxy we also uninstall Vidalia.
13082 Changes in version 0.1.2.3-alpha - 2006-10-29
13084 - Prepare for servers to publish descriptors less often: never
13085 discard a descriptor simply for being too old until either it is
13086 recommended by no authorities, or until we get a better one for
13087 the same router. Make caches consider retaining old recommended
13088 routers for even longer.
13089 - If most authorities set a BadExit flag for a server, clients
13090 don't think of it as a general-purpose exit. Clients only consider
13091 authorities that advertise themselves as listing bad exits.
13092 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
13093 headers for content, so that we can work better in the presence of
13094 caching HTTP proxies.
13095 - Allow authorities to list nodes as bad exits by fingerprint or by
13098 o Minor features, controller:
13099 - Add a REASON field to CIRC events; for backward compatibility, this
13100 field is sent only to controllers that have enabled the extended
13101 event format. Also, add additional reason codes to explain why
13102 a given circuit has been destroyed or truncated. (Patches from
13104 - Add a REMOTE_REASON field to extended CIRC events to tell the
13105 controller about why a remote OR told us to close a circuit.
13106 - Stream events also now have REASON and REMOTE_REASON fields,
13107 working much like those for circuit events.
13108 - There's now a GETINFO ns/... field so that controllers can ask Tor
13109 about the current status of a router.
13110 - A new event type "NS" to inform a controller when our opinion of
13111 a router's status has changed.
13112 - Add a GETINFO events/names and GETINFO features/names so controllers
13113 can tell which events and features are supported.
13114 - A new CLEARDNSCACHE signal to allow controllers to clear the
13115 client-side DNS cache without expiring circuits.
13117 o Security bugfixes:
13118 - When the user sends a NEWNYM signal, clear the client-side DNS
13119 cache too. Otherwise we continue to act on previous information.
13122 - Avoid sending junk to controllers or segfaulting when a controller
13123 uses EVENT_NEW_DESC with verbose nicknames.
13124 - Stop triggering asserts if the controller tries to extend hidden
13125 service circuits (reported by mwenge).
13126 - Avoid infinite loop on unexpected controller input.
13127 - When the controller does a "GETINFO network-status", tell it
13128 about even those routers whose descriptors are very old, and use
13129 long nicknames where appropriate.
13130 - Change NT service functions to be loaded on demand. This lets us
13131 build with MinGW without breaking Tor for Windows 98 users.
13132 - Do DirPort reachability tests less often, since a single test
13133 chews through many circuits before giving up.
13134 - In the hidden service example in torrc.sample, stop recommending
13135 esoteric and discouraged hidden service options.
13136 - When stopping an NT service, wait up to 10 sec for it to actually
13137 stop. Patch from Matt Edman; resolves bug 295.
13138 - Fix handling of verbose nicknames with ORCONN controller events:
13139 make them show up exactly when requested, rather than exactly when
13141 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
13142 printing a duplicate "$" in the keys we send (reported by mwenge).
13143 - Correctly set maximum connection limit on Cygwin. (This time
13145 - Try to detect Windows correctly when cross-compiling.
13146 - Detect the size of the routers file correctly even if it is
13147 corrupted (on systems without mmap) or not page-aligned (on systems
13148 with mmap). This bug was harmless.
13149 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
13150 to open a stream fails; now we do in more cases. This should
13151 make clients able to find a good exit faster in some cases, since
13152 unhandleable requests will now get an error rather than timing out.
13153 - Resolve two memory leaks when rebuilding the on-disk router cache
13154 (reported by fookoowa).
13155 - Clean up minor code warnings suggested by the MIPSpro C compiler,
13156 and reported by some Centos users.
13157 - Controller signals now work on non-Unix platforms that don't define
13158 SIGUSR1 and SIGUSR2 the way we expect.
13159 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
13160 values before failing, and always enables eventdns.
13161 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
13162 Try to fix this in configure.in by checking for most functions
13163 before we check for libevent.
13166 Changes in version 0.1.2.2-alpha - 2006-10-07
13168 - Make our async eventdns library on-by-default for Tor servers,
13169 and plan to deprecate the separate dnsworker threads.
13170 - Add server-side support for "reverse" DNS lookups (using PTR
13171 records so clients can determine the canonical hostname for a given
13172 IPv4 address). Only supported by servers using eventdns; servers
13173 now announce in their descriptors whether they support eventdns.
13174 - Specify and implement client-side SOCKS5 interface for reverse DNS
13175 lookups (see doc/socks-extensions.txt).
13176 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
13177 connect to directory servers through Tor. Previously, clients needed
13178 to find Tor exits to make private connections to directory servers.
13179 - Avoid choosing Exit nodes for entry or middle hops when the
13180 total bandwidth available from non-Exit nodes is much higher than
13181 the total bandwidth available from Exit nodes.
13182 - Workaround for name servers (like Earthlink's) that hijack failing
13183 DNS requests and replace the no-such-server answer with a "helpful"
13184 redirect to an advertising-driven search portal. Also work around
13185 DNS hijackers who "helpfully" decline to hijack known-invalid
13186 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
13187 lets you turn it off.
13188 - Send out a burst of long-range padding cells once we've established
13189 that we're reachable. Spread them over 4 circuits, so hopefully
13190 a few will be fast. This exercises our bandwidth and bootstraps
13191 us into the directory more quickly.
13193 o New/improved config options:
13194 - Add new config option "ResolvConf" to let the server operator
13195 choose an alternate resolve.conf file when using eventdns.
13196 - Add an "EnforceDistinctSubnets" option to control our "exclude
13197 servers on the same /16" behavior. It's still on by default; this
13198 is mostly for people who want to operate private test networks with
13199 all the machines on the same subnet.
13200 - If one of our entry guards is on the ExcludeNodes list, or the
13201 directory authorities don't think it's a good guard, treat it as
13202 if it were unlisted: stop using it as a guard, and throw it off
13203 the guards list if it stays that way for a long time.
13204 - Allow directory authorities to be marked separately as authorities
13205 for the v1 directory protocol, the v2 directory protocol, and
13206 as hidden service directories, to make it easier to retire old
13207 authorities. V1 authorities should set "HSAuthoritativeDir 1"
13208 to continue being hidden service authorities too.
13209 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
13211 o Minor features, controller:
13212 - Fix CIRC controller events so that controllers can learn the
13213 identity digests of non-Named servers used in circuit paths.
13214 - Let controllers ask for more useful identifiers for servers. Instead
13215 of learning identity digests for un-Named servers and nicknames
13216 for Named servers, the new identifiers include digest, nickname,
13217 and indication of Named status. Off by default; see control-spec.txt
13218 for more information.
13219 - Add a "getinfo address" controller command so it can display Tor's
13220 best guess to the user.
13221 - New controller event to alert the controller when our server
13222 descriptor has changed.
13223 - Give more meaningful errors on controller authentication failure.
13225 o Minor features, other:
13226 - When asked to resolve a hostname, don't use non-exit servers unless
13227 requested to do so. This allows servers with broken DNS to be
13228 useful to the network.
13229 - Divide eventdns log messages into warn and info messages.
13230 - Reserve the nickname "Unnamed" for routers that can't pick
13231 a hostname: any router can call itself Unnamed; directory
13232 authorities will never allocate Unnamed to any particular router;
13233 clients won't believe that any router is the canonical Unnamed.
13234 - Only include function names in log messages for info/debug messages.
13235 For notice/warn/err, the content of the message should be clear on
13236 its own, and printing the function name only confuses users.
13237 - Avoid some false positives during reachability testing: don't try
13238 to test via a server that's on the same /24 as us.
13239 - If we fail to build a circuit to an intended enclave, and it's
13240 not mandatory that we use that enclave, stop wanting it.
13241 - When eventdns is enabled, allow multithreaded builds on NetBSD and
13242 OpenBSD. (We had previously disabled threads on these platforms
13243 because they didn't have working thread-safe resolver functions.)
13245 o Major bugfixes, anonymity/security:
13246 - If a client asked for a server by name, and there's a named server
13247 in our network-status but we don't have its descriptor yet, we
13248 could return an unnamed server instead.
13249 - Fix NetBSD bug that could allow someone to force uninitialized RAM
13250 to be sent to a server's DNS resolver. This only affects NetBSD
13251 and other platforms that do not bounds-check tolower().
13252 - Reject (most) attempts to use Tor circuits with length one. (If
13253 many people start using Tor as a one-hop proxy, exit nodes become
13254 a more attractive target for compromise.)
13255 - Just because your DirPort is open doesn't mean people should be
13256 able to remotely teach you about hidden service descriptors. Now
13257 only accept rendezvous posts if you've got HSAuthoritativeDir set.
13259 o Major bugfixes, other:
13260 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
13261 - When a client asks the server to resolve (not connect to)
13262 an address, and it has a cached answer, give them the cached answer.
13263 Previously, the server would give them no answer at all.
13264 - Allow really slow clients to not hang up five minutes into their
13265 directory downloads (suggested by Adam J. Richter).
13266 - We were building exactly the wrong circuits when we anticipated
13267 hidden service requirements, meaning Tor would have to build all
13268 its circuits on demand.
13269 - Avoid crashing when we mmap a router cache file of size 0.
13270 - When testing reachability of our DirPort, don't launch new
13271 tests when there's already one in progress -- unreachable
13272 servers were stacking up dozens of testing streams.
13274 o Minor bugfixes, correctness:
13275 - If we're a directory mirror and we ask for "all" network status
13276 documents, we would discard status documents from authorities
13277 we don't recognize.
13278 - Avoid a memory corruption bug when creating a hash table for
13280 - Avoid controller-triggered crash when misusing certain commands
13281 from a v0 controller on platforms that do not handle
13282 printf("%s",NULL) gracefully.
13283 - Don't crash when a controller sends a third argument to an
13284 "extendcircuit" request.
13285 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13286 response; fix error code when "getinfo dir/status/" fails.
13287 - Avoid crash when telling controller stream-status and a stream
13289 - Patch from Adam Langley to fix assert() in eventdns.c.
13290 - Fix a debug log message in eventdns to say "X resolved to Y"
13291 instead of "X resolved to X".
13292 - Make eventdns give strings for DNS errors, not just error numbers.
13293 - Track unreachable entry guards correctly: don't conflate
13294 'unreachable by us right now' with 'listed as down by the directory
13295 authorities'. With the old code, if a guard was unreachable by
13296 us but listed as running, it would clog our guard list forever.
13297 - Behave correctly in case we ever have a network with more than
13298 2GB/s total advertised capacity.
13299 - Make TrackExitHosts case-insensitive, and fix the behavior of
13300 ".suffix" TrackExitHosts items to avoid matching in the middle of
13302 - Finally fix the openssl warnings from newer gccs that believe that
13303 ignoring a return value is okay, but casting a return value and
13304 then ignoring it is a sign of madness.
13305 - Prevent the contrib/exitlist script from printing the same
13306 result more than once.
13307 - Patch from Steve Hildrey: Generate network status correctly on
13308 non-versioning dirservers.
13309 - Don't listen to the X-Your-Address-Is hint if you did the lookup
13310 via Tor; otherwise you'll think you're the exit node's IP address.
13312 o Minor bugfixes, performance:
13313 - Two small performance improvements on parsing descriptors.
13314 - Major performance improvement on inserting descriptors: change
13315 algorithm from O(n^2) to O(n).
13316 - Make the common memory allocation path faster on machines where
13317 malloc(0) returns a pointer.
13318 - Start remembering X-Your-Address-Is directory hints even if you're
13319 a client, so you can become a server more smoothly.
13320 - Avoid duplicate entries on MyFamily line in server descriptor.
13322 o Packaging, features:
13323 - Remove architecture from OS X builds. The official builds are
13324 now universal binaries.
13325 - The Debian package now uses --verify-config when (re)starting,
13326 to distinguish configuration errors from other errors.
13327 - Update RPMs to require libevent 1.1b.
13329 o Packaging, bugfixes:
13330 - Patches so Tor builds with MinGW on Windows.
13331 - Patches so Tor might run on Cygwin again.
13332 - Resume building on non-gcc compilers and ancient gcc. Resume
13333 building with the -O0 compile flag. Resume building cleanly on
13335 - Run correctly on OS X platforms with case-sensitive filesystems.
13336 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
13337 - Add autoconf checks so Tor can build on Solaris x86 again.
13340 - Documented (and renamed) ServerDNSSearchDomains and
13341 ServerDNSResolvConfFile options.
13342 - Be clearer that the *ListenAddress directives can be repeated
13346 Changes in version 0.1.1.24 - 2006-09-29
13348 - Allow really slow clients to not hang up five minutes into their
13349 directory downloads (suggested by Adam J. Richter).
13350 - Fix major performance regression from 0.1.0.x: instead of checking
13351 whether we have enough directory information every time we want to
13352 do something, only check when the directory information has changed.
13353 This should improve client CPU usage by 25-50%.
13354 - Don't crash if, after a server has been running for a while,
13355 it can't resolve its hostname.
13358 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13359 - Don't crash when the controller receives a third argument to an
13360 "extendcircuit" request.
13361 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13362 response; fix error code when "getinfo dir/status/" fails.
13363 - Fix configure.in to not produce broken configure files with
13364 more recent versions of autoconf. Thanks to Clint for his auto*
13366 - Fix security bug on NetBSD that could allow someone to force
13367 uninitialized RAM to be sent to a server's DNS resolver. This
13368 only affects NetBSD and other platforms that do not bounds-check
13370 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
13371 methods: these are known to be buggy.
13372 - If we're a directory mirror and we ask for "all" network status
13373 documents, we would discard status documents from authorities
13374 we don't recognize.
13377 Changes in version 0.1.2.1-alpha - 2006-08-27
13379 - Add "eventdns" async dns library from Adam Langley, tweaked to
13380 build on OSX and Windows. Only enabled if you pass the
13381 --enable-eventdns argument to configure.
13382 - Allow servers with no hostname or IP address to learn their
13383 IP address by asking the directory authorities. This code only
13384 kicks in when you would normally have exited with a "no address"
13385 error. Nothing's authenticated, so use with care.
13386 - Rather than waiting a fixed amount of time between retrying
13387 application connections, we wait only 5 seconds for the first,
13388 10 seconds for the second, and 15 seconds for each retry after
13389 that. Hopefully this will improve the expected user experience.
13390 - Patch from Tup to add support for transparent AP connections:
13391 this basically bundles the functionality of trans-proxy-tor
13392 into the Tor mainline. Now hosts with compliant pf/netfilter
13393 implementations can redirect TCP connections straight to Tor
13394 without diverting through SOCKS. Needs docs.
13395 - Busy directory servers save lots of memory by spooling server
13396 descriptors, v1 directories, and v2 networkstatus docs to buffers
13397 as needed rather than en masse. Also mmap the cached-routers
13398 files, so we don't need to keep the whole thing in memory too.
13399 - Automatically avoid picking more than one node from the same
13400 /16 network when constructing a circuit.
13401 - Revise and clean up the torrc.sample that we ship with; add
13402 a section for BandwidthRate and BandwidthBurst.
13405 - Split circuit_t into origin_circuit_t and or_circuit_t, and
13406 split connection_t into edge, or, dir, control, and base structs.
13407 These will save quite a bit of memory on busy servers, and they'll
13408 also help us track down bugs in the code and bugs in the spec.
13409 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
13410 or later. Log when we are doing this, so we can diagnose it when
13411 it fails. (Also, recommend libevent 1.1b for kqueue and
13412 win32 methods; deprecate libevent 1.0b harder; make libevent
13413 recommendation system saner.)
13414 - Start being able to build universal binaries on OS X (thanks
13416 - Export the default exit policy via the control port, so controllers
13417 don't need to guess what it is / will be later.
13418 - Add a man page entry for ProtocolWarnings.
13419 - Add TestVia config option to the man page.
13420 - Remove even more protocol-related warnings from Tor server logs,
13421 such as bad TLS handshakes and malformed begin cells.
13422 - Stop fetching descriptors if you're not a dir mirror and you
13423 haven't tried to establish any circuits lately. [This currently
13424 causes some dangerous behavior, because when you start up again
13425 you'll use your ancient server descriptors.]
13426 - New DirPort behavior: if you have your dirport set, you download
13427 descriptors aggressively like a directory mirror, whether or not
13428 your ORPort is set.
13429 - Get rid of the router_retry_connections notion. Now routers
13430 no longer try to rebuild long-term connections to directory
13431 authorities, and directory authorities no longer try to rebuild
13432 long-term connections to all servers. We still don't hang up
13433 connections in these two cases though -- we need to look at it
13434 more carefully to avoid flapping, and we likely need to wait til
13435 0.1.1.x is obsolete.
13436 - Drop compatibility with obsolete Tors that permit create cells
13437 to have the wrong circ_id_type.
13438 - Re-enable per-connection rate limiting. Get rid of the "OP
13439 bandwidth" concept. Lay groundwork for "bandwidth classes" --
13440 separate global buckets that apply depending on what sort of conn
13442 - Start publishing one minute or so after we find our ORPort
13443 to be reachable. This will help reduce the number of descriptors
13444 we have for ourselves floating around, since it's quite likely
13445 other things (e.g. DirPort) will change during that minute too.
13446 - Fork the v1 directory protocol into its own spec document,
13447 and mark dir-spec.txt as the currently correct (v2) spec.
13450 - When we find our DirPort to be reachable, publish a new descriptor
13451 so we'll tell the world (reported by pnx).
13452 - Publish a new descriptor after we hup/reload. This is important
13453 if our config has changed such that we'll want to start advertising
13454 our DirPort now, etc.
13455 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13456 - When we have a state file we cannot parse, tell the user and
13457 move it aside. Now we avoid situations where the user starts
13458 Tor in 1904, Tor writes a state file with that timestamp in it,
13459 the user fixes her clock, and Tor refuses to start.
13460 - Fix configure.in to not produce broken configure files with
13461 more recent versions of autoconf. Thanks to Clint for his auto*
13463 - "tor --verify-config" now exits with -1(255) or 0 depending on
13464 whether the config options are bad or good.
13465 - Resolve bug 321 when using dnsworkers: append a period to every
13466 address we resolve at the exit node, so that we do not accidentally
13467 pick up local addresses, and so that failing searches are retried
13468 in the resolver search domains. (This is already solved for
13469 eventdns.) (This breaks Blossom servers for now.)
13470 - If we are using an exit enclave and we can't connect, e.g. because
13471 its webserver is misconfigured to not listen on localhost, then
13472 back off and try connecting from somewhere else before we fail.
13475 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
13476 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
13477 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
13478 when the IP address is mapped through MapAddress to a hostname.
13479 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
13480 useless IPv6 DNS resolves.
13481 - Patch suggested by Karsten Loesing: respond to SIGNAL command
13482 before we execute the signal, in case the signal shuts us down.
13483 - Clean up AllowInvalidNodes man page entry.
13484 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
13485 - Add more asserts to track down an assert error on a windows Tor
13486 server with connection_add being called with socket == -1.
13487 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
13488 - Fix misleading log messages: an entry guard that is "unlisted",
13489 as well as not known to be "down" (because we've never heard
13490 of it), is not therefore "up".
13491 - Remove code to special-case "-cvs" ending, since it has not
13492 actually mattered since 0.0.9.
13493 - Make our socks5 handling more robust to broken socks clients:
13494 throw out everything waiting on the buffer in between socks
13495 handshake phases, since they can't possibly (so the theory
13496 goes) have predicted what we plan to respond to them.
13499 Changes in version 0.1.1.23 - 2006-07-30
13501 - Fast Tor servers, especially exit nodes, were triggering asserts
13502 due to a bug in handling the list of pending DNS resolves. Some
13503 bugs still remain here; we're hunting them.
13504 - Entry guards could crash clients by sending unexpected input.
13505 - More fixes on reachability testing: if you find yourself reachable,
13506 then don't ever make any client requests (so you stop predicting
13507 circuits), then hup or have your clock jump, then later your IP
13508 changes, you won't think circuits are working, so you won't try to
13509 test reachability, so you won't publish.
13512 - Avoid a crash if the controller does a resetconf firewallports
13513 and then a setconf fascistfirewall=1.
13514 - Avoid an integer underflow when the dir authority decides whether
13515 a router is stable: we might wrongly label it stable, and compute
13516 a slightly wrong median stability, when a descriptor is published
13518 - Fix a place where we might trigger an assert if we can't build our
13519 own server descriptor yet.
13522 Changes in version 0.1.1.22 - 2006-07-05
13524 - Fix a big bug that was causing servers to not find themselves
13525 reachable if they changed IP addresses. Since only 0.1.1.22+
13526 servers can do reachability testing correctly, now we automatically
13527 make sure to test via one of these.
13528 - Fix to allow clients and mirrors to learn directory info from
13529 descriptor downloads that get cut off partway through.
13530 - Directory authorities had a bug in deciding if a newly published
13531 descriptor was novel enough to make everybody want a copy -- a few
13532 servers seem to be publishing new descriptors many times a minute.
13534 - Fix a rare bug that was causing some servers to complain about
13535 "closing wedged cpuworkers" and skip some circuit create requests.
13536 - Make the Exit flag in directory status documents actually work.
13539 Changes in version 0.1.1.21 - 2006-06-10
13540 o Crash and assert fixes from 0.1.1.20:
13541 - Fix a rare crash on Tor servers that have enabled hibernation.
13542 - Fix a seg fault on startup for Tor networks that use only one
13543 directory authority.
13544 - Fix an assert from a race condition that occurs on Tor servers
13545 while exiting, where various threads are trying to log that they're
13546 exiting, and delete the logs, at the same time.
13547 - Make our unit tests pass again on certain obscure platforms.
13550 - Add support for building SUSE RPM packages.
13551 - Speed up initial bootstrapping for clients: if we are making our
13552 first ever connection to any entry guard, then don't mark it down
13554 - When only one Tor server in the network is labelled as a guard,
13555 and we've already picked him, we would cycle endlessly picking him
13556 again, being unhappy about it, etc. Now we specifically exclude
13557 current guards when picking a new guard.
13558 - Servers send create cells more reliably after the TLS connection
13559 is established: we were sometimes forgetting to send half of them
13560 when we had more than one pending.
13561 - If we get a create cell that asks us to extend somewhere, but the
13562 Tor server there doesn't match the expected digest, we now send
13563 a destroy cell back, rather than silently doing nothing.
13564 - Make options->RedirectExit work again.
13565 - Make cookie authentication for the controller work again.
13566 - Stop being picky about unusual characters in the arguments to
13567 mapaddress. It's none of our business.
13568 - Add a new config option "TestVia" that lets you specify preferred
13569 middle hops to use for test circuits. Perhaps this will let me
13570 debug the reachability problems better.
13572 o Log / documentation fixes:
13573 - If we're a server and some peer has a broken TLS certificate, don't
13574 log about it unless ProtocolWarnings is set, i.e., we want to hear
13575 about protocol violations by others.
13576 - Fix spelling of VirtualAddrNetwork in man page.
13577 - Add a better explanation at the top of the autogenerated torrc file
13578 about what happened to our old torrc.
13581 Changes in version 0.1.1.20 - 2006-05-23
13583 - Downgrade a log severity where servers complain that they're
13585 - Avoid a compile warning on FreeBSD.
13586 - Remove string size limit on NEWDESC messages; solve bug 291.
13587 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
13588 more thoroughly when we're running on windows.
13591 Changes in version 0.1.1.19-rc - 2006-05-03
13593 - Regenerate our local descriptor if it's dirty and we try to use
13594 it locally (e.g. if it changes during reachability detection).
13595 - If we setconf our ORPort to 0, we continued to listen on the
13596 old ORPort and receive connections.
13597 - Avoid a second warning about machine/limits.h on Debian
13599 - Be willing to add our own routerinfo into the routerlist.
13600 Now authorities will include themselves in their directories
13601 and network-statuses.
13602 - Stop trying to upload rendezvous descriptors to every
13603 directory authority: only try the v1 authorities.
13604 - Servers no longer complain when they think they're not
13605 registered with the directory authorities. There were too many
13607 - Backport dist-rpm changes so rpms can be built without errors.
13610 - Implement an option, VirtualAddrMask, to set which addresses
13611 get handed out in response to mapaddress requests. This works
13612 around a bug in tsocks where 127.0.0.0/8 is never socksified.
13615 Changes in version 0.1.1.18-rc - 2006-04-10
13617 - Work harder to download live network-statuses from all the
13618 directory authorities we know about. Improve the threshold
13619 decision logic so we're more robust to edge cases.
13620 - When fetching rendezvous descriptors, we were willing to ask
13621 v2 authorities too, which would always return 404.
13624 - Stop listing down or invalid nodes in the v1 directory. This will
13625 reduce its bulk by about 1/3, and reduce load on directory
13627 - When deciding whether a router is Fast or Guard-worthy, consider
13628 his advertised BandwidthRate and not just the BandwidthCapacity.
13629 - No longer ship INSTALL and README files -- they are useless now.
13630 - Force rpmbuild to behave and honor target_cpu.
13631 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
13632 - Start to include translated versions of the tor-doc-*.html
13633 files, along with the screenshots. Still needs more work.
13634 - Start sending back 512 and 451 errors if mapaddress fails,
13635 rather than not sending anything back at all.
13636 - When we fail to bind or listen on an incoming or outgoing
13637 socket, we should close it before failing. otherwise we just
13638 leak it. (thanks to weasel for finding.)
13639 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
13640 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
13641 - Make NoPublish (even though deprecated) work again.
13642 - Fix a minor security flaw where a versioning auth dirserver
13643 could list a recommended version many times in a row to make
13644 clients more convinced that it's recommended.
13645 - Fix crash bug if there are two unregistered servers running
13646 with the same nickname, one of them is down, and you ask for
13647 them by nickname in your EntryNodes or ExitNodes. Also, try
13648 to pick the one that's running rather than an arbitrary one.
13649 - Fix an infinite loop we could hit if we go offline for too long.
13650 - Complain when we hit WSAENOBUFS on recv() or write() too.
13651 Perhaps this will help us hunt the bug.
13652 - If you're not a versioning dirserver, don't put the string
13653 "client-versions \nserver-versions \n" in your network-status.
13654 - Lower the minimum required number of file descriptors to 1000,
13655 so we can have some overhead for Valgrind on Linux, where the
13656 default ulimit -n is 1024.
13659 - Add tor.dizum.com as the fifth authoritative directory server.
13660 - Add a new config option FetchUselessDescriptors, off by default,
13661 for when you plan to run "exitlist" on your client and you want
13662 to know about even the non-running descriptors.
13665 Changes in version 0.1.1.17-rc - 2006-03-28
13667 - Clients and servers since 0.1.1.10-alpha have been expiring
13668 connections whenever they are idle for 5 minutes and they *do*
13669 have circuits on them. Oops. With this new version, clients will
13670 discard their previous entry guard choices and avoid choosing
13671 entry guards running these flawed versions.
13672 - Fix memory leak when uncompressing concatenated zlib streams. This
13673 was causing substantial leaks over time on Tor servers.
13674 - The v1 directory was including servers as much as 48 hours old,
13675 because that's how the new routerlist->routers works. Now only
13676 include them if they're 20 hours old or less.
13679 - Resume building on irix64, netbsd 2.0, etc.
13680 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
13682 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
13683 and it is confusing some users.
13684 - Mirrors stop caching the v1 directory so often.
13685 - Make the max number of old descriptors that a cache will hold
13686 rise with the number of directory authorities, so we can scale.
13687 - Change our win32 uname() hack to be more forgiving about what
13688 win32 versions it thinks it's found.
13691 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
13693 - When the controller's *setconf commands fail, collect an error
13694 message in a string and hand it back to the controller.
13695 - Make the v2 dir's "Fast" flag based on relative capacity, just
13696 like "Stable" is based on median uptime. Name everything in the
13697 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
13698 - Log server fingerprint on startup, so new server operators don't
13699 have to go hunting around their filesystem for it.
13700 - Return a robots.txt on our dirport to discourage google indexing.
13701 - Let the controller ask for GETINFO dir/status/foo so it can ask
13702 directly rather than connecting to the dir port. Only works when
13703 dirport is set for now.
13705 o New config options rather than constants in the code:
13706 - SocksTimeout: How long do we let a socks connection wait
13707 unattached before we fail it?
13708 - CircuitBuildTimeout: Cull non-open circuits that were born
13709 at least this many seconds ago.
13710 - CircuitIdleTimeout: Cull open clean circuits that were born
13711 at least this many seconds ago.
13714 Changes in version 0.1.1.16-rc - 2006-03-18
13715 o Bugfixes on 0.1.1.15-rc:
13716 - Fix assert when the controller asks to attachstream a connect-wait
13717 or resolve-wait stream.
13718 - Now do address rewriting when the controller asks us to attach
13719 to a particular circuit too. This will let Blossom specify
13720 "moria2.exit" without having to learn what moria2's IP address is.
13721 - Make the "tor --verify-config" command-line work again, so people
13722 can automatically check if their torrc will parse.
13723 - Authoritative dirservers no longer require an open connection from
13724 a server to consider him "reachable". We need this change because
13725 when we add new auth dirservers, old servers won't know not to
13727 - Let Tor build on Sun CC again.
13728 - Fix an off-by-one buffer size in dirserv.c that magically never
13729 hit our three authorities but broke sjmurdoch's own tor network.
13730 - If we as a directory mirror don't know of any v1 directory
13731 authorities, then don't try to cache any v1 directories.
13732 - Stop warning about unknown servers in our family when they are
13733 given as hex digests.
13734 - Stop complaining as quickly to the server operator that he
13735 hasn't registered his nickname/key binding.
13736 - Various cleanups so we can add new V2 Auth Dirservers.
13737 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
13738 reflect the updated flags in our v2 dir protocol.
13739 - Resume allowing non-printable characters for exit streams (both
13740 for connecting and for resolving). Now we tolerate applications
13741 that don't follow the RFCs. But continue to block malformed names
13744 o Bugfixes on 0.1.0.x:
13745 - Fix assert bug in close_logs(): when we close and delete logs,
13746 remove them all from the global "logfiles" list.
13747 - Fix minor integer overflow in calculating when we expect to use up
13748 our bandwidth allocation before hibernating.
13749 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
13750 there are multiple SSLs installed with different versions.
13751 - When we try to be a server and Address is not explicitly set and
13752 our hostname resolves to a private IP address, try to use an
13753 interface address if it has a public address. Now Windows machines
13754 that think of themselves as localhost can work by default.
13757 - Let the controller ask for GETINFO dir/server/foo so it can ask
13758 directly rather than connecting to the dir port.
13759 - Let the controller tell us about certain router descriptors
13760 that it doesn't want Tor to use in circuits. Implement
13761 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
13762 - New config option SafeSocks to reject all application connections
13763 using unsafe socks protocols. Defaults to off.
13766 Changes in version 0.1.1.15-rc - 2006-03-11
13767 o Bugfixes and cleanups:
13768 - When we're printing strings from the network, don't try to print
13769 non-printable characters. This protects us against shell escape
13770 sequence exploits, and also against attacks to fool humans into
13771 misreading their logs.
13772 - Fix a bug where Tor would fail to establish any connections if you
13773 left it off for 24 hours and then started it: we were happy with
13774 the obsolete network statuses, but they all referred to router
13775 descriptors that were too old to fetch, so we ended up with no
13776 valid router descriptors.
13777 - Fix a seg fault in the controller's "getinfo orconn-status"
13778 command while listing status on incoming handshaking connections.
13779 Introduce a status name "NEW" for these connections.
13780 - If we get a linelist or linelist_s config option from the torrc
13781 (e.g. ExitPolicy) and it has no value, warn and skip rather than
13782 silently resetting it to its default.
13783 - Don't abandon entry guards until they've been down or gone for
13785 - Cleaner and quieter log messages.
13788 - New controller signal NEWNYM that makes new application requests
13789 use clean circuits.
13790 - Add a new circuit purpose 'controller' to let the controller ask
13791 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
13792 controller command to let you specify the purpose if you're
13793 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
13794 command to let you change a circuit's purpose after it's been
13796 - Accept "private:*" in routerdesc exit policies; not generated yet
13797 because older Tors do not understand it.
13798 - Add BSD-style contributed startup script "rc.subr" from Peter
13802 Changes in version 0.1.1.14-alpha - 2006-02-20
13803 o Bugfixes on 0.1.1.x:
13804 - Don't die if we ask for a stdout or stderr log (even implicitly)
13805 and we're set to RunAsDaemon -- just warn.
13806 - We still had a few bugs in the OR connection rotation code that
13807 caused directory servers to slowly aggregate connections to other
13808 fast Tor servers. This time for sure!
13809 - Make log entries on Win32 include the name of the function again.
13810 - We were treating a pair of exit policies if they were equal even
13811 if one said accept and the other said reject -- causing us to
13812 not always publish a new descriptor since we thought nothing
13814 - Retry pending server downloads as well as pending networkstatus
13815 downloads when we unexpectedly get a socks request.
13816 - We were ignoring the IS_FAST flag in the directory status,
13817 meaning we were willing to pick trivial-bandwidth nodes for "fast"
13819 - If the controller's SAVECONF command fails (e.g. due to file
13820 permissions), let the controller know that it failed.
13823 - If we're trying to be a Tor server and running Windows 95/98/ME
13824 as a server, explain that we'll likely crash.
13825 - When we're a server, a client asks for an old-style directory,
13826 and our write bucket is empty, don't give it to him. This way
13827 small servers can continue to serve the directory *sometimes*,
13828 without getting overloaded.
13829 - Compress exit policies even more -- look for duplicate lines
13831 - Clients now honor the "guard" flag in the router status when
13832 picking entry guards, rather than looking at is_fast or is_stable.
13833 - Retain unrecognized lines in $DATADIR/state file, so that we can
13834 be forward-compatible.
13835 - Generate 18.0.0.0/8 address policy format in descs when we can;
13836 warn when the mask is not reducible to a bit-prefix.
13837 - Let the user set ControlListenAddress in the torrc. This can be
13838 dangerous, but there are some cases (like a secured LAN) where it
13840 - Split ReachableAddresses into ReachableDirAddresses and
13841 ReachableORAddresses, so we can restrict Dir conns to port 80
13842 and OR conns to port 443.
13843 - Now we can target arch and OS in rpm builds (contributed by
13844 Phobos). Also make the resulting dist-rpm filename match the
13846 - New config options to help controllers: FetchServerDescriptors
13847 and FetchHidServDescriptors for whether to fetch server
13848 info and hidserv info or let the controller do it, and
13849 PublishServerDescriptor and PublishHidServDescriptors.
13850 - Also let the controller set the __AllDirActionsPrivate config
13851 option if you want all directory fetches/publishes to happen via
13852 Tor (it assumes your controller bootstraps your circuits).
13855 Changes in version 0.1.0.17 - 2006-02-17
13856 o Crash bugfixes on 0.1.0.x:
13857 - When servers with a non-zero DirPort came out of hibernation,
13858 sometimes they would trigger an assert.
13860 o Other important bugfixes:
13861 - On platforms that don't have getrlimit (like Windows), we were
13862 artificially constraining ourselves to a max of 1024
13863 connections. Now just assume that we can handle as many as 15000
13864 connections. Hopefully this won't cause other problems.
13866 o Backported features:
13867 - When we're a server, a client asks for an old-style directory,
13868 and our write bucket is empty, don't give it to him. This way
13869 small servers can continue to serve the directory *sometimes*,
13870 without getting overloaded.
13871 - Whenever you get a 503 in response to a directory fetch, try
13872 once more. This will become important once servers start sending
13873 503's whenever they feel busy.
13874 - Fetch a new directory every 120 minutes, not every 40 minutes.
13875 Now that we have hundreds of thousands of users running the old
13876 directory algorithm, it's starting to hurt a lot.
13877 - Bump up the period for forcing a hidden service descriptor upload
13878 from 20 minutes to 1 hour.
13881 Changes in version 0.1.1.13-alpha - 2006-02-09
13882 o Crashes in 0.1.1.x:
13883 - When you tried to setconf ORPort via the controller, Tor would
13884 crash. So people using TorCP to become a server were sad.
13885 - Solve (I hope) the stack-smashing bug that we were seeing on fast
13886 servers. The problem appears to be something do with OpenSSL's
13887 random number generation, or how we call it, or something. Let me
13888 know if the crashes continue.
13889 - Turn crypto hardware acceleration off by default, until we find
13890 somebody smart who can test it for us. (It appears to produce
13891 seg faults in at least some cases.)
13892 - Fix a rare assert error when we've tried all intro points for
13893 a hidden service and we try fetching the service descriptor again:
13894 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
13897 - Fix a major load balance bug: we were round-robining in 16 KB
13898 chunks, and servers with bandwidthrate of 20 KB, while downloading
13899 a 600 KB directory, would starve their other connections. Now we
13900 try to be a bit more fair.
13901 - Dir authorities and mirrors were never expiring the newest
13902 descriptor for each server, causing memory and directory bloat.
13903 - Fix memory-bloating and connection-bloating bug on servers: We
13904 were never closing any connection that had ever had a circuit on
13905 it, because we were checking conn->n_circuits == 0, yet we had a
13906 bug that let it go negative.
13907 - Make Tor work using squid as your http proxy again -- squid
13908 returns an error if you ask for a URL that's too long, and it uses
13909 a really generic error message. Plus, many people are behind a
13910 transparent squid so they don't even realize it.
13911 - On platforms that don't have getrlimit (like Windows), we were
13912 artificially constraining ourselves to a max of 1024
13913 connections. Now just assume that we can handle as many as 15000
13914 connections. Hopefully this won't cause other problems.
13915 - Add a new config option ExitPolicyRejectPrivate which defaults to
13916 1. This means all exit policies will begin with rejecting private
13917 addresses, unless the server operator explicitly turns it off.
13920 - Clients no longer download descriptors for non-running
13922 - Before we add new directory authorities, we should make it
13923 clear that only v1 authorities should receive/publish hidden
13924 service descriptors.
13927 - As soon as we've fetched some more directory info, immediately
13928 try to download more server descriptors. This way we don't have
13929 a 10 second pause during initial bootstrapping.
13930 - Remove even more loud log messages that the server operator can't
13932 - When we're running an obsolete or un-recommended version, make
13933 the log message more clear about what the problem is and what
13934 versions *are* still recommended.
13935 - Provide a more useful warn message when our onion queue gets full:
13936 the CPU is too slow or the exit policy is too liberal.
13937 - Don't warn when we receive a 503 from a dirserver/cache -- this
13938 will pave the way for them being able to refuse if they're busy.
13939 - When we fail to bind a listener, try to provide a more useful
13940 log message: e.g., "Is Tor already running?"
13941 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
13942 Goldberg can prove things about our handshake protocol more
13944 - MaxConn has been obsolete for a while now. Document the ConnLimit
13945 config option, which is a *minimum* number of file descriptors
13946 that must be available else Tor refuses to start.
13947 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
13948 if you log to syslog and want something other than LOG_DAEMON.
13949 - Make dirservers generate a separate "guard" flag to mean,
13950 "would make a good entry guard". Make clients parse it and vote
13951 on it. Not used by clients yet.
13952 - Implement --with-libevent-dir option to ./configure. Also, improve
13953 search techniques to find libevent, and use those for openssl too.
13954 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
13955 - Only start testing reachability once we've established a
13956 circuit. This will make startup on dirservers less noisy.
13957 - Don't try to upload hidden service descriptors until we have
13958 established a circuit.
13959 - Fix the controller's "attachstream 0" command to treat conn like
13960 it just connected, doing address remapping, handling .exit and
13961 .onion idioms, and so on. Now we're more uniform in making sure
13962 that the controller hears about new and closing connections.
13965 Changes in version 0.1.1.12-alpha - 2006-01-11
13966 o Bugfixes on 0.1.1.x:
13967 - The fix to close duplicate server connections was closing all
13968 Tor client connections if they didn't establish a circuit
13969 quickly enough. Oops.
13970 - Fix minor memory issue (double-free) that happened on exit.
13972 o Bugfixes on 0.1.0.x:
13973 - Tor didn't warn when it failed to open a log file.
13976 Changes in version 0.1.1.11-alpha - 2006-01-10
13977 o Crashes in 0.1.1.x:
13978 - Include all the assert/crash fixes from 0.1.0.16.
13979 - If you start Tor and then quit very quickly, there were some
13980 races that tried to free things that weren't allocated yet.
13981 - Fix a rare memory stomp if you're running hidden services.
13982 - Fix segfault when specifying DirServer in config without nickname.
13983 - Fix a seg fault when you finish connecting to a server but at
13984 that moment you dump his server descriptor.
13985 - Extendcircuit and Attachstream controller commands would
13986 assert/crash if you don't give them enough arguments.
13987 - Fix an assert error when we're out of space in the connection_list
13988 and we try to post a hidden service descriptor (reported by weasel).
13989 - If you specify a relative torrc path and you set RunAsDaemon in
13990 your torrc, then it chdir()'s to the new directory. If you HUP,
13991 it tries to load the new torrc location, fails, and exits.
13992 The fix: no longer allow a relative path to torrc using -f.
13995 - Implement "entry guards": automatically choose a handful of entry
13996 nodes and stick with them for all circuits. Only pick new guards
13997 when the ones you have are unsuitable, and if the old guards
13998 become suitable again, switch back. This will increase security
13999 dramatically against certain end-point attacks. The EntryNodes
14000 config option now provides some hints about which entry guards you
14001 want to use most; and StrictEntryNodes means to only use those.
14002 - New directory logic: download by descriptor digest, not by
14003 fingerprint. Caches try to download all listed digests from
14004 authorities; clients try to download "best" digests from caches.
14005 This avoids partitioning and isolating attacks better.
14006 - Make the "stable" router flag in network-status be the median of
14007 the uptimes of running valid servers, and make clients pay
14008 attention to the network-status flags. Thus the cutoff adapts
14009 to the stability of the network as a whole, making IRC, IM, etc
14010 connections more reliable.
14013 - Tor servers with dynamic IP addresses were needing to wait 18
14014 hours before they could start doing reachability testing using
14015 the new IP address and ports. This is because they were using
14016 the internal descriptor to learn what to test, yet they were only
14017 rebuilding the descriptor once they decided they were reachable.
14018 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
14019 to download certain server descriptors, throw them away, and then
14020 fetch them again after 30 minutes. Now mirrors throw away these
14021 server descriptors so clients can't get them.
14022 - We were leaving duplicate connections to other ORs open for a week,
14023 rather than closing them once we detect a duplicate. This only
14024 really affected authdirservers, but it affected them a lot.
14025 - Spread the authdirservers' reachability testing over the entire
14026 testing interval, so we don't try to do 500 TLS's at once every
14030 - If the network is down, and we try to connect to a conn because
14031 we have a circuit in mind, and we timeout (30 seconds) because the
14032 network never answers, we were expiring the circuit, but we weren't
14033 obsoleting the connection or telling the entry_guards functions.
14034 - Some Tor servers process billions of cells per day. These statistics
14035 need to be uint64_t's.
14036 - Check for integer overflows in more places, when adding elements
14037 to smartlists. This could possibly prevent a buffer overflow
14038 on malicious huge inputs. I don't see any, but I haven't looked
14040 - ReachableAddresses kept growing new "reject *:*" lines on every
14042 - When you "setconf log" via the controller, it should remove all
14043 logs. We were automatically adding back in a "log notice stdout".
14044 - Newly bootstrapped Tor networks couldn't establish hidden service
14045 circuits until they had nodes with high uptime. Be more tolerant.
14046 - We were marking servers down when they could not answer every piece
14047 of the directory request we sent them. This was far too harsh.
14048 - Fix the torify (tsocks) config file to not use Tor for localhost
14050 - Directory authorities now go to the proper authority when asking for
14051 a networkstatus, even when they want a compressed one.
14052 - Fix a harmless bug that was causing Tor servers to log
14053 "Got an end because of misc error, but we're not an AP. Closing."
14054 - Authorities were treating their own descriptor changes as cosmetic,
14055 meaning the descriptor available in the network-status and the
14056 descriptor that clients downloaded were different.
14057 - The OS X installer was adding a symlink for tor_resolve but
14058 the binary was called tor-resolve (reported by Thomas Hardly).
14059 - Workaround a problem with some http proxies where they refuse GET
14060 requests that specify "Content-Length: 0" (reported by Adrian).
14061 - Fix wrong log message when you add a "HiddenServiceNodes" config
14062 line without any HiddenServiceDir line (reported by Chris Thomas).
14065 - Write the TorVersion into the state file so we have a prayer of
14066 keeping forward and backward compatibility.
14067 - Revive the FascistFirewall config option rather than eliminating it:
14068 now it's a synonym for ReachableAddresses *:80,*:443.
14069 - Clients choose directory servers from the network status lists,
14070 not from their internal list of router descriptors. Now they can
14071 go to caches directly rather than needing to go to authorities
14073 - Directory authorities ignore router descriptors that have only
14074 cosmetic differences: do this for 0.1.0.x servers now too.
14075 - Add a new flag to network-status indicating whether the server
14076 can answer v2 directory requests too.
14077 - Authdirs now stop whining so loudly about bad descriptors that
14078 they fetch from other dirservers. So when there's a log complaint,
14079 it's for sure from a freshly uploaded descriptor.
14080 - Reduce memory requirements in our structs by changing the order
14082 - There used to be two ways to specify your listening ports in a
14083 server descriptor: on the "router" line and with a separate "ports"
14084 line. Remove support for the "ports" line.
14085 - New config option "AuthDirRejectUnlisted" for auth dirservers as
14086 a panic button: if we get flooded with unusable servers we can
14087 revert to only listing servers in the approved-routers file.
14088 - Auth dir servers can now mark a fingerprint as "!reject" or
14089 "!invalid" in the approved-routers file (as its nickname), to
14090 refuse descriptors outright or include them but marked as invalid.
14091 - Servers store bandwidth history across restarts/crashes.
14092 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
14093 get a better idea of why their circuits failed. Not used yet.
14094 - Directory mirrors now cache up to 16 unrecognized network-status
14095 docs. Now we can add new authdirservers and they'll be cached too.
14096 - When picking a random directory, prefer non-authorities if any
14098 - New controller option "getinfo desc/all-recent" to fetch the
14099 latest server descriptor for every router that Tor knows about.
14102 Changes in version 0.1.0.16 - 2006-01-02
14103 o Crash bugfixes on 0.1.0.x:
14104 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14105 corrupting the heap, losing FDs, or crashing when we need to resize
14106 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14107 - It turns out sparc64 platforms crash on unaligned memory access
14108 too -- so detect and avoid this.
14109 - Handle truncated compressed data correctly (by detecting it and
14111 - Fix possible-but-unlikely free(NULL) in control.c.
14112 - When we were closing connections, there was a rare case that
14113 stomped on memory, triggering seg faults and asserts.
14114 - Avoid potential infinite recursion when building a descriptor. (We
14115 don't know that it ever happened, but better to fix it anyway.)
14116 - We were neglecting to unlink marked circuits from soon-to-close OR
14117 connections, which caused some rare scribbling on freed memory.
14118 - Fix a memory stomping race bug when closing the joining point of two
14119 rendezvous circuits.
14120 - Fix an assert in time parsing found by Steven Murdoch.
14122 o Other bugfixes on 0.1.0.x:
14123 - When we're doing reachability testing, provide more useful log
14124 messages so the operator knows what to expect.
14125 - Do not check whether DirPort is reachable when we are suppressing
14126 advertising it because of hibernation.
14127 - When building with -static or on Solaris, we sometimes needed -ldl.
14128 - When we're deciding whether a stream has enough circuits around
14129 that can handle it, count the freshly dirty ones and not the ones
14130 that are so dirty they won't be able to handle it.
14131 - When we're expiring old circuits, we had a logic error that caused
14132 us to close new rendezvous circuits rather than old ones.
14133 - Give a more helpful log message when you try to change ORPort via
14134 the controller: you should upgrade Tor if you want that to work.
14135 - We were failing to parse Tor versions that start with "Tor ".
14136 - Tolerate faulty streams better: when a stream fails for reason
14137 exitpolicy, stop assuming that the router is lying about his exit
14138 policy. When a stream fails for reason misc, allow it to retry just
14139 as if it was resolvefailed. When a stream has failed three times,
14140 reset its failure count so we can try again and get all three tries.
14143 Changes in version 0.1.1.10-alpha - 2005-12-11
14144 o Correctness bugfixes on 0.1.0.x:
14145 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14146 corrupting the heap, losing FDs, or crashing when we need to resize
14147 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14148 - Stop doing the complex voodoo overkill checking for insecure
14149 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
14150 - When we were closing connections, there was a rare case that
14151 stomped on memory, triggering seg faults and asserts.
14152 - We were neglecting to unlink marked circuits from soon-to-close OR
14153 connections, which caused some rare scribbling on freed memory.
14154 - When we're deciding whether a stream has enough circuits around
14155 that can handle it, count the freshly dirty ones and not the ones
14156 that are so dirty they won't be able to handle it.
14157 - Recover better from TCP connections to Tor servers that are
14158 broken but don't tell you (it happens!); and rotate TLS
14159 connections once a week.
14160 - When we're expiring old circuits, we had a logic error that caused
14161 us to close new rendezvous circuits rather than old ones.
14162 - Fix a scary-looking but apparently harmless bug where circuits
14163 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
14164 servers, and never switch to state CIRCUIT_STATE_OPEN.
14165 - When building with -static or on Solaris, we sometimes needed to
14167 - Give a useful message when people run Tor as the wrong user,
14168 rather than telling them to start chowning random directories.
14169 - We were failing to inform the controller about new .onion streams.
14171 o Security bugfixes on 0.1.0.x:
14172 - Refuse server descriptors if the fingerprint line doesn't match
14173 the included identity key. Tor doesn't care, but other apps (and
14174 humans) might actually be trusting the fingerprint line.
14175 - We used to kill the circuit when we receive a relay command we
14176 don't recognize. Now we just drop it.
14177 - Start obeying our firewall options more rigorously:
14178 . If we can't get to a dirserver directly, try going via Tor.
14179 . Don't ever try to connect (as a client) to a place our
14180 firewall options forbid.
14181 . If we specify a proxy and also firewall options, obey the
14182 firewall options even when we're using the proxy: some proxies
14183 can only proxy to certain destinations.
14184 - Fix a bug found by Lasse Overlier: when we were making internal
14185 circuits (intended to be cannibalized later for rendezvous and
14186 introduction circuits), we were picking them so that they had
14187 useful exit nodes. There was no need for this, and it actually
14188 aids some statistical attacks.
14189 - Start treating internal circuits and exit circuits separately.
14190 It's important to keep them separate because internal circuits
14191 have their last hops picked like middle hops, rather than like
14192 exit hops. So exiting on them will break the user's expectations.
14194 o Bugfixes on 0.1.1.x:
14195 - Take out the mis-feature where we tried to detect IP address
14196 flapping for people with DynDNS, and chose not to upload a new
14197 server descriptor sometimes.
14198 - Try to be compatible with OpenSSL 0.9.6 again.
14199 - Log fix: when the controller is logging about .onion addresses,
14200 sometimes it didn't include the ".onion" part of the address.
14201 - Don't try to modify options->DirServers internally -- if the
14202 user didn't specify any, just add the default ones directly to
14203 the trusted dirserver list. This fixes a bug where people running
14204 controllers would use SETCONF on some totally unrelated config
14205 option, and Tor would start yelling at them about changing their
14207 - Let the controller's redirectstream command specify a port, in
14208 case the controller wants to change that too.
14209 - When we requested a pile of server descriptors, we sometimes
14210 accidentally launched a duplicate request for the first one.
14211 - Bugfix for trackhostexits: write down the fingerprint of the
14212 chosen exit, not its nickname, because the chosen exit might not
14214 - When parsing foo.exit, if foo is unknown, and we are leaving
14215 circuits unattached, set the chosen_exit field and leave the
14216 address empty. This matters because controllers got confused
14218 - Directory authorities no longer try to download server
14219 descriptors that they know they will reject.
14221 o Features and updates:
14222 - Replace balanced trees with hash tables: this should make stuff
14223 significantly faster.
14224 - Resume using the AES counter-mode implementation that we ship,
14225 rather than OpenSSL's. Ours is significantly faster.
14226 - Many other CPU and memory improvements.
14227 - Add a new config option FastFirstHopPK (on by default) so clients
14228 do a trivial crypto handshake for their first hop, since TLS has
14229 already taken care of confidentiality and authentication.
14230 - Add a new config option TestSocks so people can see if their
14231 applications are using socks4, socks4a, socks5-with-ip, or
14232 socks5-with-hostname. This way they don't have to keep mucking
14233 with tcpdump and wondering if something got cached somewhere.
14234 - Warn when listening on a public address for socks. I suspect a
14235 lot of people are setting themselves up as open socks proxies,
14236 and they have no idea that jerks on the Internet are using them,
14237 since they simply proxy the traffic into the Tor network.
14238 - Add "private:*" as an alias in configuration for policies. Now
14239 you can simplify your exit policy rather than needing to list
14240 every single internal or nonroutable network space.
14241 - Add a new controller event type that allows controllers to get
14242 all server descriptors that were uploaded to a router in its role
14243 as authoritative dirserver.
14244 - Start shipping socks-extensions.txt, tor-doc-unix.html,
14245 tor-doc-server.html, and stylesheet.css in the tarball.
14246 - Stop shipping tor-doc.html in the tarball.
14249 Changes in version 0.1.1.9-alpha - 2005-11-15
14250 o Usability improvements:
14251 - Start calling it FooListenAddress rather than FooBindAddress,
14252 since few of our users know what it means to bind an address
14254 - Reduce clutter in server logs. We're going to try to make
14255 them actually usable now. New config option ProtocolWarnings that
14256 lets you hear about how _other Tors_ are breaking the protocol. Off
14258 - Divide log messages into logging domains. Once we put some sort
14259 of interface on this, it will let people looking at more verbose
14260 log levels specify the topics they want to hear more about.
14261 - Make directory servers return better http 404 error messages
14262 instead of a generic "Servers unavailable".
14263 - Check for even more Windows version flags when writing the platform
14264 string in server descriptors, and note any we don't recognize.
14265 - Clean up more of the OpenSSL memory when exiting, so we can detect
14266 memory leaks better.
14267 - Make directory authorities be non-versioning, non-naming by
14268 default. Now we can add new directory servers without requiring
14269 their operators to pay close attention.
14270 - When logging via syslog, include the pid whenever we provide
14271 a log entry. Suggested by Todd Fries.
14273 o Performance improvements:
14274 - Directory servers now silently throw away new descriptors that
14275 haven't changed much if the timestamps are similar. We do this to
14276 tolerate older Tor servers that upload a new descriptor every 15
14277 minutes. (It seemed like a good idea at the time.)
14278 - Inline bottleneck smartlist functions; use fast versions by default.
14279 - Add a "Map from digest to void*" abstraction digestmap_t so we
14280 can do less hex encoding/decoding. Use it in router_get_by_digest()
14281 to resolve a performance bottleneck.
14282 - Allow tor_gzip_uncompress to extract as much as possible from
14283 truncated compressed data. Try to extract as many
14284 descriptors as possible from truncated http responses (when
14285 DIR_PURPOSE_FETCH_ROUTERDESC).
14286 - Make circ->onionskin a pointer, not a static array. moria2 was using
14287 125000 circuit_t's after it had been up for a few weeks, which
14288 translates to 20+ megs of wasted space.
14289 - The private half of our EDH handshake keys are now chosen out
14290 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
14292 o Security improvements:
14293 - Start making directory caches retain old routerinfos, so soon
14294 clients can start asking by digest of descriptor rather than by
14295 fingerprint of server.
14296 - Add half our entropy from RAND_poll in OpenSSL. This knows how
14297 to use egd (if present), openbsd weirdness (if present), vms/os2
14298 weirdness (if we ever port there), and more in the future.
14300 o Bugfixes on 0.1.0.x:
14301 - Do round-robin writes of at most 16 kB per write. This might be
14302 more fair on loaded Tor servers, and it might resolve our Windows
14303 crash bug. It might also slow things down.
14304 - Our TLS handshakes were generating a single public/private
14305 keypair for the TLS context, rather than making a new one for
14306 each new connections. Oops. (But we were still rotating them
14307 periodically, so it's not so bad.)
14308 - When we were cannibalizing a circuit with a particular exit
14309 node in mind, we weren't checking to see if that exit node was
14310 already present earlier in the circuit. Oops.
14311 - When a Tor server's IP changes (e.g. from a dyndns address),
14312 upload a new descriptor so clients will learn too.
14313 - Really busy servers were keeping enough circuits open on stable
14314 connections that they were wrapping around the circuit_id
14315 space. (It's only two bytes.) This exposed a bug where we would
14316 feel free to reuse a circuit_id even if it still exists but has
14317 been marked for close. Try to fix this bug. Some bug remains.
14318 - If we would close a stream early (e.g. it asks for a .exit that
14319 we know would refuse it) but the LeaveStreamsUnattached config
14320 option is set by the controller, then don't close it.
14322 o Bugfixes on 0.1.1.8-alpha:
14323 - Fix a big pile of memory leaks, some of them serious.
14324 - Do not try to download a routerdesc if we would immediately reject
14326 - Resume inserting a newline between all router descriptors when
14327 generating (old style) signed directories, since our spec says
14329 - When providing content-type application/octet-stream for
14330 server descriptors using .z, we were leaving out the
14331 content-encoding header. Oops. (Everything tolerated this just
14332 fine, but that doesn't mean we need to be part of the problem.)
14333 - Fix a potential seg fault in getconf and getinfo using version 1
14334 of the controller protocol.
14335 - Avoid crash: do not check whether DirPort is reachable when we
14336 are suppressing it because of hibernation.
14337 - Make --hash-password not crash on exit.
14340 Changes in version 0.1.1.8-alpha - 2005-10-07
14341 o New features (major):
14342 - Clients don't download or use the directory anymore. Now they
14343 download and use network-statuses from the trusted dirservers,
14344 and fetch individual server descriptors as needed from mirrors.
14345 See dir-spec.txt for all the gory details.
14346 - Be more conservative about whether to advertise our DirPort.
14347 The main change is to not advertise if we're running at capacity
14348 and either a) we could hibernate or b) our capacity is low and
14349 we're using a default DirPort.
14350 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
14352 o New features (minor):
14353 - Try to be smart about when to retry network-status and
14354 server-descriptor fetches. Still needs some tuning.
14355 - Stop parsing, storing, or using running-routers output (but
14356 mirrors still cache and serve it).
14357 - Consider a threshold of versioning dirservers (dirservers who have
14358 an opinion about which Tor versions are still recommended) before
14359 deciding whether to warn the user that he's obsolete.
14360 - Dirservers can now reject/invalidate by key and IP, with the
14361 config options "AuthDirInvalid" and "AuthDirReject". This is
14362 useful since currently we automatically list servers as running
14363 and usable even if we know they're jerks.
14364 - Provide dire warnings to any users who set DirServer; move it out
14365 of torrc.sample and into torrc.complete.
14366 - Add MyFamily to torrc.sample in the server section.
14367 - Add nicknames to the DirServer line, so we can refer to them
14368 without requiring all our users to memorize their IP addresses.
14369 - When we get an EOF or a timeout on a directory connection, note
14370 how many bytes of serverdesc we are dropping. This will help
14371 us determine whether it is smart to parse incomplete serverdesc
14373 - Add a new function to "change pseudonyms" -- that is, to stop
14374 using any currently-dirty circuits for new streams, so we don't
14375 link new actions to old actions. Currently it's only called on
14376 HUP (or SIGNAL RELOAD).
14377 - On sighup, if UseHelperNodes changed to 1, use new circuits.
14378 - Start using RAND_bytes rather than RAND_pseudo_bytes from
14379 OpenSSL. Also, reseed our entropy every hour, not just at
14380 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14382 o Fixes on 0.1.1.7-alpha:
14383 - Nobody ever implemented EVENT_ADDRMAP for control protocol
14384 version 0, so don't let version 0 controllers ask for it.
14385 - If you requested something with too many newlines via the
14386 v1 controller protocol, you could crash tor.
14387 - Fix a number of memory leaks, including some pretty serious ones.
14388 - Re-enable DirPort testing again, so Tor servers will be willing
14389 to advertise their DirPort if it's reachable.
14390 - On TLS handshake, only check the other router's nickname against
14391 its expected nickname if is_named is set.
14393 o Fixes forward-ported from 0.1.0.15:
14394 - Don't crash when we don't have any spare file descriptors and we
14395 try to spawn a dns or cpu worker.
14396 - Make the numbers in read-history and write-history into uint64s,
14397 so they don't overflow and publish negatives in the descriptor.
14399 o Fixes on 0.1.0.x:
14400 - For the OS X package's modified privoxy config file, comment
14401 out the "logfile" line so we don't log everything passed
14403 - We were whining about using socks4 or socks5-with-local-lookup
14404 even when it's an IP in the "virtual" range we designed exactly
14406 - We were leaking some memory every time the client changes IPs.
14407 - Never call free() on tor_malloc()d memory. This will help us
14408 use dmalloc to detect memory leaks.
14409 - Check for named servers when looking them up by nickname;
14410 warn when we'recalling a non-named server by its nickname;
14411 don't warn twice about the same name.
14412 - Try to list MyFamily elements by key, not by nickname, and warn
14413 if we've not heard of the server.
14414 - Make windows platform detection (uname equivalent) smarter.
14415 - It turns out sparc64 doesn't like unaligned access either.
14418 Changes in version 0.1.0.15 - 2005-09-23
14419 o Bugfixes on 0.1.0.x:
14420 - Reject ports 465 and 587 (spam targets) in default exit policy.
14421 - Don't crash when we don't have any spare file descriptors and we
14422 try to spawn a dns or cpu worker.
14423 - Get rid of IgnoreVersion undocumented config option, and make us
14424 only warn, never exit, when we're running an obsolete version.
14425 - Don't try to print a null string when your server finds itself to
14426 be unreachable and the Address config option is empty.
14427 - Make the numbers in read-history and write-history into uint64s,
14428 so they don't overflow and publish negatives in the descriptor.
14429 - Fix a minor memory leak in smartlist_string_remove().
14430 - We were only allowing ourselves to upload a server descriptor at
14431 most every 20 minutes, even if it changed earlier than that.
14432 - Clean up log entries that pointed to old URLs.
14435 Changes in version 0.1.1.7-alpha - 2005-09-14
14436 o Fixes on 0.1.1.6-alpha:
14437 - Exit servers were crashing when people asked them to make a
14438 connection to an address not in their exit policy.
14439 - Looking up a non-existent stream for a v1 control connection would
14441 - Fix a seg fault if we ask a dirserver for a descriptor by
14442 fingerprint but he doesn't know about him.
14443 - SETCONF was appending items to linelists, not clearing them.
14444 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
14445 out and refuse the setconf if it would fail.
14446 - Downgrade the dirserver log messages when whining about
14450 - Add Peter Palfrader's check-tor script to tor/contrib/
14451 It lets you easily check whether a given server (referenced by
14452 nickname) is reachable by you.
14453 - Numerous changes to move towards client-side v2 directories. Not
14456 o Fixes on 0.1.0.x:
14457 - If the user gave tor an odd number of command-line arguments,
14458 we were silently ignoring the last one. Now we complain and fail.
14459 [This wins the oldest-bug prize -- this bug has been present since
14460 November 2002, as released in Tor 0.0.0.]
14461 - Do not use unaligned memory access on alpha, mips, or mipsel.
14462 It *works*, but is very slow, so we treat them as if it doesn't.
14463 - Retry directory requests if we fail to get an answer we like
14464 from a given dirserver (we were retrying before, but only if
14465 we fail to connect).
14466 - When writing the RecommendedVersions line, sort them first.
14467 - When the client asked for a rendezvous port that the hidden
14468 service didn't want to provide, we were sending an IP address
14469 back along with the end cell. Fortunately, it was zero. But stop
14471 - Correct "your server is reachable" log entries to indicate that
14472 it was self-testing that told us so.
14475 Changes in version 0.1.1.6-alpha - 2005-09-09
14476 o Fixes on 0.1.1.5-alpha:
14477 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
14478 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
14479 - Fix bug with tor_memmem finding a match at the end of the string.
14480 - Make unit tests run without segfaulting.
14481 - Resolve some solaris x86 compile warnings.
14482 - Handle duplicate lines in approved-routers files without warning.
14483 - Fix bug where as soon as a server refused any requests due to his
14484 exit policy (e.g. when we ask for localhost and he tells us that's
14485 127.0.0.1 and he won't do it), we decided he wasn't obeying his
14486 exit policy using him for any exits.
14487 - Only do openssl hardware accelerator stuff if openssl version is
14490 o New controller features/fixes:
14491 - Add a "RESETCONF" command so you can set config options like
14492 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
14493 a config option in the torrc with no value, then it clears it
14494 entirely (rather than setting it to its default).
14495 - Add a "GETINFO config-file" to tell us where torrc is.
14496 - Avoid sending blank lines when GETINFO replies should be empty.
14497 - Add a QUIT command for the controller (for using it manually).
14498 - Fix a bug in SAVECONF that was adding default dirservers and
14499 other redundant entries to the torrc file.
14501 o Start on the new directory design:
14502 - Generate, publish, cache, serve new network-status format.
14503 - Publish individual descriptors (by fingerprint, by "all", and by
14505 - Publish client and server recommended versions separately.
14506 - Allow tor_gzip_uncompress() to handle multiple concatenated
14507 compressed strings. Serve compressed groups of router
14508 descriptors. The compression logic here could be more
14510 - Distinguish v1 authorities (all currently trusted directories)
14511 from v2 authorities (all trusted directories).
14512 - Change DirServers config line to note which dirs are v1 authorities.
14513 - Add configuration option "V1AuthoritativeDirectory 1" which
14514 moria1, moria2, and tor26 should set.
14515 - Remove option when getting directory cache to see whether they
14516 support running-routers; they all do now. Replace it with one
14517 to see whether caches support v2 stuff.
14520 - Dirservers now do their own external reachability testing of each
14521 Tor server, and only list them as running if they've been found to
14522 be reachable. We also send back warnings to the server's logs if
14523 it uploads a descriptor that we already believe is unreachable.
14524 - Implement exit enclaves: if we know an IP address for the
14525 destination, and there's a running Tor server at that address
14526 which allows exit to the destination, then extend the circuit to
14527 that exit first. This provides end-to-end encryption and end-to-end
14528 authentication. Also, if the user wants a .exit address or enclave,
14529 use 4 hops rather than 3, and cannibalize a general circ for it
14531 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
14532 controller. Also, rotate dns and cpu workers if the controller
14533 changes options that will affect them; and initialize the dns
14534 worker cache tree whether or not we start out as a server.
14535 - Only upload a new server descriptor when options change, 18
14536 hours have passed, uptime is reset, or bandwidth changes a lot.
14537 - Check [X-]Forwarded-For headers in HTTP requests when generating
14538 log messages. This lets people run dirservers (and caches) behind
14539 Apache but still know which IP addresses are causing warnings.
14541 o Config option changes:
14542 - Replace (Fascist)Firewall* config options with a new
14543 ReachableAddresses option that understands address policies.
14544 For example, "ReachableAddresses *:80,*:443"
14545 - Get rid of IgnoreVersion undocumented config option, and make us
14546 only warn, never exit, when we're running an obsolete version.
14547 - Make MonthlyAccountingStart config option truly obsolete now.
14549 o Fixes on 0.1.0.x:
14550 - Reject ports 465 and 587 in the default exit policy, since
14551 people have started using them for spam too.
14552 - It turns out we couldn't bootstrap a network since we added
14553 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14554 has never gone down. Add an AssumeReachable config option to let
14555 servers and dirservers bootstrap. When we're trying to build a
14556 high-uptime or high-bandwidth circuit but there aren't enough
14557 suitable servers, try being less picky rather than simply failing.
14558 - Our logic to decide if the OR we connected to was the right guy
14559 was brittle and maybe open to a mitm for unverified routers.
14560 - We weren't cannibalizing circuits correctly for
14561 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14562 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14563 build those from scratch. This should make hidden services faster.
14564 - Predict required circuits better, with an eye toward making hidden
14565 services faster on the service end.
14566 - Retry streams if the exit node sends back a 'misc' failure. This
14567 should result in fewer random failures. Also, after failing
14568 from resolve failed or misc, reset the num failures, so we give
14569 it a fair shake next time we try.
14570 - Clean up the rendezvous warn log msgs, and downgrade some to info.
14571 - Reduce severity on logs about dns worker spawning and culling.
14572 - When we're shutting down and we do something like try to post a
14573 server descriptor or rendezvous descriptor, don't complain that
14574 we seem to be unreachable. Of course we are, we're shutting down.
14575 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14576 We don't use them yet, but maybe one day our DNS resolver will be
14577 able to discover them.
14578 - Make ContactInfo mandatory for authoritative directory servers.
14579 - Require server descriptors to list IPv4 addresses -- hostnames
14580 are no longer allowed. This also fixes some potential security
14581 problems with people providing hostnames as their address and then
14582 preferentially resolving them to partition users.
14583 - Change log line for unreachability to explicitly suggest /etc/hosts
14584 as the culprit. Also make it clearer what IP address and ports we're
14585 testing for reachability.
14586 - Put quotes around user-supplied strings when logging so users are
14587 more likely to realize if they add bad characters (like quotes)
14589 - Let auth dir servers start without specifying an Address config
14591 - Make unit tests (and other invocations that aren't the real Tor)
14592 run without launching listeners, creating subdirectories, and so on.
14595 Changes in version 0.1.1.5-alpha - 2005-08-08
14596 o Bugfixes included in 0.1.0.14.
14598 o Bugfixes on 0.1.0.x:
14599 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
14600 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
14601 it would silently using ignore the 6668.
14604 Changes in version 0.1.0.14 - 2005-08-08
14605 o Bugfixes on 0.1.0.x:
14606 - Fix the other half of the bug with crypto handshakes
14608 - Fix an assert trigger if you send a 'signal term' via the
14609 controller when it's listening for 'event info' messages.
14612 Changes in version 0.1.1.4-alpha - 2005-08-04
14613 o Bugfixes included in 0.1.0.13.
14616 - Improve tor_gettimeofday() granularity on windows.
14617 - Make clients regenerate their keys when their IP address changes.
14618 - Implement some more GETINFO goodness: expose helper nodes, config
14619 options, getinfo keys.
14622 Changes in version 0.1.0.13 - 2005-08-04
14623 o Bugfixes on 0.1.0.x:
14624 - Fix a critical bug in the security of our crypto handshakes.
14625 - Fix a size_t underflow in smartlist_join_strings2() that made
14626 it do bad things when you hand it an empty smartlist.
14627 - Fix Windows installer to ship Tor license (thanks to Aphex for
14628 pointing out this oversight) and put a link to the doc directory
14630 - Explicitly set no-unaligned-access for sparc: it turns out the
14631 new gcc's let you compile broken code, but that doesn't make it
14635 Changes in version 0.1.1.3-alpha - 2005-07-23
14636 o Bugfixes on 0.1.1.2-alpha:
14637 - Fix a bug in handling the controller's "post descriptor"
14639 - Fix several bugs in handling the controller's "extend circuit"
14641 - Fix a bug in handling the controller's "stream status" event.
14642 - Fix an assert failure if we have a controller listening for
14643 circuit events and we go offline.
14644 - Re-allow hidden service descriptors to publish 0 intro points.
14645 - Fix a crash when generating your hidden service descriptor if
14646 you don't have enough intro points already.
14648 o New features on 0.1.1.2-alpha:
14649 - New controller function "getinfo accounting", to ask how
14650 many bytes we've used in this time period.
14651 - Experimental support for helper nodes: a lot of the risk from
14652 a small static adversary comes because users pick new random
14653 nodes every time they rebuild a circuit. Now users will try to
14654 stick to the same small set of entry nodes if they can. Not
14655 enabled by default yet.
14657 o Bugfixes on 0.1.0.12:
14658 - If you're an auth dir server, always publish your dirport,
14659 even if you haven't yet found yourself to be reachable.
14660 - Fix a size_t underflow in smartlist_join_strings2() that made
14661 it do bad things when you hand it an empty smartlist.
14664 Changes in version 0.1.0.12 - 2005-07-18
14665 o New directory servers:
14666 - tor26 has changed IP address.
14668 o Bugfixes on 0.1.0.x:
14669 - Fix a possible double-free in tor_gzip_uncompress().
14670 - When --disable-threads is set, do not search for or link against
14671 pthreads libraries.
14672 - Don't trigger an assert if an authoritative directory server
14673 claims its dirport is 0.
14674 - Fix bug with removing Tor as an NT service: some people were
14675 getting "The service did not return an error." Thanks to Matt
14679 Changes in version 0.1.1.2-alpha - 2005-07-15
14680 o New directory servers:
14681 - tor26 has changed IP address.
14683 o Bugfixes on 0.1.0.x, crashes/leaks:
14684 - Port the servers-not-obeying-their-exit-policies fix from
14686 - Fix an fd leak in start_daemon().
14687 - On Windows, you can't always reopen a port right after you've
14688 closed it. So change retry_listeners() to only close and re-open
14689 ports that have changed.
14690 - Fix a possible double-free in tor_gzip_uncompress().
14692 o Bugfixes on 0.1.0.x, usability:
14693 - When tor_socketpair() fails in Windows, give a reasonable
14694 Windows-style errno back.
14695 - Let people type "tor --install" as well as "tor -install" when
14697 want to make it an NT service.
14698 - NT service patch from Matt Edman to improve error messages.
14699 - When the controller asks for a config option with an abbreviated
14700 name, give the full name in our response.
14701 - Correct the man page entry on TrackHostExitsExpire.
14702 - Looks like we were never delivering deflated (i.e. compressed)
14703 running-routers lists, even when asked. Oops.
14704 - When --disable-threads is set, do not search for or link against
14705 pthreads libraries.
14707 o Bugfixes on 0.1.1.x:
14708 - Fix a seg fault with autodetecting which controller version is
14712 - New hidden service descriptor format: put a version in it, and
14713 let people specify introduction/rendezvous points that aren't
14714 in "the directory" (which is subjective anyway).
14715 - Allow the DEBUG controller event to work again. Mark certain log
14716 entries as "don't tell this to controllers", so we avoid cycles.
14719 Changes in version 0.1.0.11 - 2005-06-30
14720 o Bugfixes on 0.1.0.x:
14721 - Fix major security bug: servers were disregarding their
14722 exit policies if clients behaved unexpectedly.
14723 - Make OS X init script check for missing argument, so we don't
14724 confuse users who invoke it incorrectly.
14725 - Fix a seg fault in "tor --hash-password foo".
14726 - The MAPADDRESS control command was broken.
14729 Changes in version 0.1.1.1-alpha - 2005-06-29
14731 - Make OS X init script check for missing argument, so we don't
14732 confuse users who invoke it incorrectly.
14733 - Fix a seg fault in "tor --hash-password foo".
14734 - Fix a possible way to DoS dirservers.
14735 - When we complain that your exit policy implicitly allows local or
14736 private address spaces, name them explicitly so operators can
14738 - Make the log message less scary when all the dirservers are
14739 temporarily unreachable.
14740 - We were printing the number of idle dns workers incorrectly when
14744 - Revised controller protocol (version 1) that uses ascii rather
14745 than binary. Add supporting libraries in python and java so you
14746 can use the controller from your applications without caring how
14747 our protocol works.
14748 - Spiffy new support for crypto hardware accelerators. Can somebody
14752 Changes in version 0.0.9.10 - 2005-06-16
14753 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
14754 - Refuse relay cells that claim to have a length larger than the
14755 maximum allowed. This prevents a potential attack that could read
14756 arbitrary memory (e.g. keys) from an exit server's process
14760 Changes in version 0.1.0.10 - 2005-06-14
14761 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
14762 libevent before 1.1a.
14765 Changes in version 0.1.0.9-rc - 2005-06-09
14767 - Reset buf->highwater every time buf_shrink() is called, not just on
14768 a successful shrink. This was causing significant memory bloat.
14769 - Fix buffer overflow when checking hashed passwords.
14770 - Security fix: if seeding the RNG on Win32 fails, quit.
14771 - Allow seeding the RNG on Win32 even when you're not running as
14773 - Disable threading on Solaris too. Something is wonky with it,
14774 cpuworkers, and reentrant libs.
14775 - Reenable the part of the code that tries to flush as soon as an
14776 OR outbuf has a full TLS record available. Perhaps this will make
14777 OR outbufs not grow as huge except in rare cases, thus saving lots
14778 of CPU time plus memory.
14779 - Reject malformed .onion addresses rather then passing them on as
14780 normal web requests.
14781 - Adapt patch from Adam Langley: fix possible memory leak in
14782 tor_lookup_hostname().
14783 - Initialize libevent later in the startup process, so the logs are
14784 already established by the time we start logging libevent warns.
14785 - Use correct errno on win32 if libevent fails.
14786 - Check and warn about known-bad/slow libevent versions.
14787 - Pay more attention to the ClientOnly config option.
14788 - Have torctl.in/tor.sh.in check for location of su binary (needed
14790 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
14791 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
14792 HttpProxyAuthenticator
14793 - Stop warning about sigpipes in the logs. We're going to
14794 pretend that getting these occassionally is normal and fine.
14795 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
14797 installer screens; and don't put stuff into StartupItems unless
14798 the user asks you to.
14799 - Require servers that use the default dirservers to have public IP
14800 addresses. We have too many servers that are configured with private
14801 IPs and their admins never notice the log entries complaining that
14802 their descriptors are being rejected.
14803 - Add OSX uninstall instructions. An actual uninstall script will
14807 Changes in version 0.1.0.8-rc - 2005-05-23
14809 - It turns out that kqueue on OS X 10.3.9 was causing kernel
14810 panics. Disable kqueue on all OS X Tors.
14811 - Fix RPM: remove duplicate line accidentally added to the rpm
14813 - Disable threads on openbsd too, since its gethostaddr is not
14815 - Tolerate libevent 0.8 since it still works, even though it's
14817 - Enable building on Red Hat 9.0 again.
14818 - Allow the middle hop of the testing circuit to be running any
14819 version, now that most of them have the bugfix to let them connect
14820 to unknown servers. This will allow reachability testing to work
14821 even when 0.0.9.7-0.0.9.9 become obsolete.
14822 - Handle relay cells with rh.length too large. This prevents
14823 a potential attack that could read arbitrary memory (maybe even
14824 keys) from the exit server's process.
14825 - We screwed up the dirport reachability testing when we don't yet
14826 have a cached version of the directory. Hopefully now fixed.
14827 - Clean up router_load_single_router() (used by the controller),
14828 so it doesn't seg fault on error.
14829 - Fix a minor memory leak when somebody establishes an introduction
14830 point at your Tor server.
14831 - If a socks connection ends because read fails, don't warn that
14832 you're not sending a socks reply back.
14835 - Add HttpProxyAuthenticator config option too, that works like
14836 the HttpsProxyAuthenticator config option.
14837 - Encode hashed controller passwords in hex instead of base64,
14838 to make it easier to write controllers.
14841 Changes in version 0.1.0.7-rc - 2005-05-17
14843 - Fix a bug in the OS X package installer that prevented it from
14844 installing on Tiger.
14845 - Fix a script bug in the OS X package installer that made it
14846 complain during installation.
14847 - Find libevent even if it's hiding in /usr/local/ and your
14848 CFLAGS and LDFLAGS don't tell you to look there.
14849 - Be able to link with libevent as a shared library (the default
14850 after 1.0d), even if it's hiding in /usr/local/lib and even
14851 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
14852 assuming you're running gcc. Otherwise fail and give a useful
14854 - Fix a bug in the RPM packager: set home directory for _tor to
14855 something more reasonable when first installing.
14856 - Free a minor amount of memory that is still reachable on exit.
14859 Changes in version 0.1.0.6-rc - 2005-05-14
14861 - Implement --disable-threads configure option. Disable threads on
14862 netbsd by default, because it appears to have no reentrant resolver
14864 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
14865 release (1.1) detects and disables kqueue if it's broken.
14866 - Append default exit policy before checking for implicit internal
14867 addresses. Now we don't log a bunch of complaints on startup
14868 when using the default exit policy.
14869 - Some people were putting "Address " in their torrc, and they had
14870 a buggy resolver that resolved " " to 0.0.0.0. Oops.
14871 - If DataDir is ~/.tor, and that expands to /.tor, then default to
14872 LOCALSTATEDIR/tor instead.
14873 - Fix fragmented-message bug in TorControl.py.
14874 - Resolve a minor bug which would prevent unreachable dirports
14875 from getting suppressed in the published descriptor.
14876 - When the controller gave us a new descriptor, we weren't resolving
14877 it immediately, so Tor would think its address was 0.0.0.0 until
14878 we fetched a new directory.
14879 - Fix an uppercase/lowercase case error in suppressing a bogus
14880 libevent warning on some Linuxes.
14883 - Begin scrubbing sensitive strings from logs by default. Turn off
14884 the config option SafeLogging if you need to do debugging.
14885 - Switch to a new buffer management algorithm, which tries to avoid
14886 reallocing and copying quite as much. In first tests it looks like
14887 it uses *more* memory on average, but less cpu.
14888 - First cut at support for "create-fast" cells. Clients can use
14889 these when extending to their first hop, since the TLS already
14890 provides forward secrecy and authentication. Not enabled on
14892 - When dirservers refuse a router descriptor, we now log its
14893 contactinfo, platform, and the poster's IP address.
14894 - Call tor_free_all instead of connections_free_all after forking, to
14895 save memory on systems that need to fork.
14896 - Whine at you if you're a server and you don't set your contactinfo.
14897 - Implement --verify-config command-line option to check if your torrc
14898 is valid without actually launching Tor.
14899 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
14900 rather than just rejecting it.
14903 Changes in version 0.1.0.5-rc - 2005-04-27
14905 - Stop trying to print a null pointer if an OR conn fails because
14906 we didn't like its cert.
14908 - Switch our internal buffers implementation to use a ring buffer,
14909 to hopefully improve performance for fast servers a lot.
14910 - Add HttpsProxyAuthenticator support (basic auth only), based
14911 on patch from Adam Langley.
14912 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
14913 the fast servers that have been joining lately.
14914 - Give hidden service accesses extra time on the first attempt,
14915 since 60 seconds is often only barely enough. This might improve
14917 - Improve performance for dirservers: stop re-parsing the whole
14918 directory every time you regenerate it.
14919 - Add more debugging info to help us find the weird dns freebsd
14920 pthreads bug; cleaner debug messages to help track future issues.
14923 Changes in version 0.0.9.9 - 2005-04-23
14924 o Bugfixes on 0.0.9.x:
14925 - If unofficial Tor clients connect and send weird TLS certs, our
14926 Tor server triggers an assert. This release contains a minimal
14927 backport from the broader fix that we put into 0.1.0.4-rc.
14930 Changes in version 0.1.0.4-rc - 2005-04-23
14932 - If unofficial Tor clients connect and send weird TLS certs, our
14933 Tor server triggers an assert. Stop asserting, and start handling
14934 TLS errors better in other situations too.
14935 - When the controller asks us to tell it about all the debug-level
14936 logs, it turns out we were generating debug-level logs while
14937 telling it about them, which turns into a bad loop. Now keep
14938 track of whether you're sending a debug log to the controller,
14939 and don't log when you are.
14940 - Fix the "postdescriptor" feature of the controller interface: on
14941 non-complete success, only say "done" once.
14943 - Clients are now willing to load balance over up to 2mB, not 1mB,
14944 of advertised bandwidth capacity.
14945 - Add a NoPublish config option, so you can be a server (e.g. for
14946 testing running Tor servers in other Tor networks) without
14947 publishing your descriptor to the primary dirservers.
14950 Changes in version 0.1.0.3-rc - 2005-04-08
14951 o Improvements on 0.1.0.2-rc:
14952 - Client now retries when streams end early for 'hibernating' or
14953 'resource limit' reasons, rather than failing them.
14954 - More automated handling for dirserver operators:
14955 - Automatically approve nodes running 0.1.0.2-rc or later,
14956 now that the the reachability detection stuff is working.
14957 - Now we allow two unverified servers with the same nickname
14958 but different keys. But if a nickname is verified, only that
14959 nickname+key are allowed.
14960 - If you're an authdirserver connecting to an address:port,
14961 and it's not the OR you were expecting, forget about that
14962 descriptor. If he *was* the one you were expecting, then forget
14963 about all other descriptors for that address:port.
14964 - Allow servers to publish descriptors from 12 hours in the future.
14965 Corollary: only whine about clock skew from the dirserver if
14966 he's a trusted dirserver (since now even verified servers could
14967 have quite wrong clocks).
14968 - Adjust maximum skew and age for rendezvous descriptors: let skew
14969 be 48 hours rather than 90 minutes.
14970 - Efficiency improvements:
14971 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
14972 it much faster to look up a circuit for each relay cell.
14973 - Remove most calls to assert_all_pending_dns_resolves_ok(),
14974 since they're eating our cpu on exit nodes.
14975 - Stop wasting time doing a case insensitive comparison for every
14976 dns name every time we do any lookup. Canonicalize the names to
14977 lowercase and be done with it.
14978 - Start sending 'truncated' cells back rather than destroy cells,
14979 if the circuit closes in front of you. This means we won't have
14980 to abandon partially built circuits.
14981 - Only warn once per nickname from add_nickname_list_to_smartlist
14982 per failure, so an entrynode or exitnode choice that's down won't
14984 - Put a note in the torrc about abuse potential with the default
14986 - Revise control spec and implementation to allow all log messages to
14987 be sent to controller with their severities intact (suggested by
14988 Matt Edman). Update TorControl to handle new log event types.
14989 - Provide better explanation messages when controller's POSTDESCRIPTOR
14991 - Stop putting nodename in the Platform string in server descriptors.
14992 It doesn't actually help, and it is confusing/upsetting some people.
14994 o Bugfixes on 0.1.0.2-rc:
14995 - We were printing the host mask wrong in exit policies in server
14996 descriptors. This isn't a critical bug though, since we were still
14997 obeying the exit policy internally.
14998 - Fix Tor when compiled with libevent but without pthreads: move
14999 connection_unregister() from _connection_free() to
15001 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
15002 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
15003 when we look through the connection array, we'll find any of the
15004 cpu/dnsworkers. This is no good.
15006 o Bugfixes on 0.0.9.8:
15007 - Fix possible bug on threading platforms (e.g. win32) which was
15008 leaking a file descriptor whenever a cpuworker or dnsworker died.
15009 - When using preferred entry or exit nodes, ignore whether the
15010 circuit wants uptime or capacity. They asked for the nodes, they
15012 - chdir() to your datadirectory at the *end* of the daemonize process,
15013 not the beginning. This was a problem because the first time you
15014 run tor, if your datadir isn't there, and you have runasdaemon set
15015 to 1, it will try to chdir to it before it tries to create it. Oops.
15016 - Handle changed router status correctly when dirserver reloads
15017 fingerprint file. We used to be dropping all unverified descriptors
15018 right then. The bug was hidden because we would immediately
15019 fetch a directory from another dirserver, which would include the
15020 descriptors we just dropped.
15021 - When we're connecting to an OR and he's got a different nickname/key
15022 than we were expecting, only complain loudly if we're an OP or a
15023 dirserver. Complaining loudly to the OR admins just confuses them.
15024 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
15025 artificially capped at 500kB.
15028 Changes in version 0.0.9.8 - 2005-04-07
15029 o Bugfixes on 0.0.9.x:
15030 - We have a bug that I haven't found yet. Sometimes, very rarely,
15031 cpuworkers get stuck in the 'busy' state, even though the cpuworker
15032 thinks of itself as idle. This meant that no new circuits ever got
15033 established. Here's a workaround to kill any cpuworker that's been
15034 busy for more than 100 seconds.
15037 Changes in version 0.1.0.2-rc - 2005-04-01
15038 o Bugfixes on 0.1.0.1-rc:
15039 - Fixes on reachability detection:
15040 - Don't check for reachability while hibernating.
15041 - If ORPort is reachable but DirPort isn't, still publish the
15042 descriptor, but zero out DirPort until it's found reachable.
15043 - When building testing circs for ORPort testing, use only
15044 high-bandwidth nodes, so fewer circuits fail.
15045 - Complain about unreachable ORPort separately from unreachable
15046 DirPort, so the user knows what's going on.
15047 - Make sure we only conclude ORPort reachability if we didn't
15048 initiate the conn. Otherwise we could falsely conclude that
15049 we're reachable just because we connected to the guy earlier
15050 and he used that same pipe to extend to us.
15051 - Authdirservers shouldn't do ORPort reachability detection,
15052 since they're in clique mode, so it will be rare to find a
15053 server not already connected to them.
15054 - When building testing circuits, always pick middle hops running
15055 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
15056 bug. (This is a kludge; it will go away when 0.0.9.x becomes
15058 - When we decide we're reachable, actually publish our descriptor
15060 - Fix bug in redirectstream in the controller.
15061 - Fix the state descriptor strings so logs don't claim edge streams
15062 are in a different state than they actually are.
15063 - Use recent libevent features when possible (this only really affects
15064 win32 and osx right now, because the new libevent with these
15065 features hasn't been released yet). Add code to suppress spurious
15067 - Prevent possible segfault in connection_close_unattached_ap().
15068 - Fix newlines on torrc in win32.
15069 - Improve error msgs when tor-resolve fails.
15071 o Improvements on 0.0.9.x:
15072 - New experimental script tor/contrib/ExerciseServer.py (needs more
15073 work) that uses the controller interface to build circuits and
15074 fetch pages over them. This will help us bootstrap servers that
15075 have lots of capacity but haven't noticed it yet.
15076 - New experimental script tor/contrib/PathDemo.py (needs more work)
15077 that uses the controller interface to let you choose whole paths
15079 "<hostname>.<path,separated by dots>.<length of path>.path"
15080 - When we've connected to an OR and handshaked but didn't like
15081 the result, we were closing the conn without sending destroy
15082 cells back for pending circuits. Now send those destroys.
15085 Changes in version 0.0.9.7 - 2005-04-01
15086 o Bugfixes on 0.0.9.x:
15087 - Fix another race crash bug (thanks to Glenn Fink for reporting).
15088 - Compare identity to identity, not to nickname, when extending to
15089 a router not already in the directory. This was preventing us from
15090 extending to unknown routers. Oops.
15091 - Make sure to create OS X Tor user in <500 range, so we aren't
15092 creating actual system users.
15093 - Note where connection-that-hasn't-sent-end was marked, and fix
15094 a few really loud instances of this harmless bug (it's fixed more
15098 Changes in version 0.1.0.1-rc - 2005-03-28
15100 - Add reachability testing. Your Tor server will automatically try
15101 to see if its ORPort and DirPort are reachable from the outside,
15102 and it won't upload its descriptor until it decides they are.
15103 - Handle unavailable hidden services better. Handle slow or busy
15104 hidden services better.
15105 - Add support for CONNECTing through https proxies, with "HttpsProxy"
15107 - New exit policy: accept most low-numbered ports, rather than
15108 rejecting most low-numbered ports.
15109 - More Tor controller support (still experimental). See
15110 http://tor.eff.org/doc/control-spec.txt for all the new features,
15111 including signals to emulate unix signals from any platform;
15112 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
15113 closestream; closecircuit; etc.
15114 - Make nt services work and start on startup on win32 (based on
15115 patch by Matt Edman).
15116 - Add a new AddressMap config directive to rewrite incoming socks
15117 addresses. This lets you, for example, declare an implicit
15118 required exit node for certain sites.
15119 - Add a new TrackHostExits config directive to trigger addressmaps
15120 for certain incoming socks addresses -- for sites that break when
15121 your exit keeps changing (based on patch by Mike Perry).
15122 - Redo the client-side dns cache so it's just an addressmap too.
15123 - Notice when our IP changes, and reset stats/uptime/reachability.
15124 - When an application is using socks5, give him the whole variety of
15125 potential socks5 responses (connect refused, host unreachable, etc),
15126 rather than just "success" or "failure".
15127 - A more sane version numbering system. See
15128 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
15129 - New contributed script "exitlist": a simple python script to
15130 parse directories and find Tor nodes that exit to listed
15132 - New contributed script "privoxy-tor-toggle" to toggle whether
15133 Privoxy uses Tor. Seems to be configured for Debian by default.
15134 - Report HTTP reasons to client when getting a response from directory
15135 servers -- so you can actually know what went wrong.
15136 - New config option MaxAdvertisedBandwidth which lets you advertise
15137 a low bandwidthrate (to not attract as many circuits) while still
15138 allowing a higher bandwidthrate in reality.
15140 o Robustness/stability fixes:
15141 - Make Tor use Niels Provos's libevent instead of its current
15142 poll-but-sometimes-select mess. This will let us use faster async
15143 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
15145 - pthread support now too. This was forced because when we forked,
15146 we ended up wasting a lot of duplicate ram over time. Also switch
15147 to foo_r versions of some library calls to allow reentry and
15149 - Better handling for heterogeneous / unreliable nodes:
15150 - Annotate circuits w/ whether they aim to contain high uptime nodes
15151 and/or high capacity nodes. When building circuits, choose
15153 - This means that every single node in an intro rend circuit,
15154 not just the last one, will have a minimum uptime.
15155 - New config option LongLivedPorts to indicate application streams
15156 that will want high uptime circuits.
15157 - Servers reset uptime when a dir fetch entirely fails. This
15158 hopefully reflects stability of the server's network connectivity.
15159 - If somebody starts his tor server in Jan 2004 and then fixes his
15160 clock, don't make his published uptime be a year.
15161 - Reset published uptime when you wake up from hibernation.
15162 - Introduce a notion of 'internal' circs, which are chosen without
15163 regard to the exit policy of the last hop. Intro and rendezvous
15164 circs must be internal circs, to avoid leaking information. Resolve
15165 and connect streams can use internal circs if they want.
15166 - New circuit pooling algorithm: make sure to have enough circs around
15167 to satisfy any predicted ports, and also make sure to have 2 internal
15168 circs around if we've required internal circs lately (and with high
15169 uptime if we've seen that lately too).
15170 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
15171 which describes how often we retry making new circuits if current
15172 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
15173 how long we're willing to make use of an already-dirty circuit.
15174 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
15175 circ as necessary, if there are any completed ones lying around
15176 when we try to launch one.
15177 - Make hidden services try to establish a rendezvous for 30 seconds,
15178 rather than for n (where n=3) attempts to build a circuit.
15179 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
15180 "ShutdownWaitLength".
15181 - Try to be more zealous about calling connection_edge_end when
15182 things go bad with edge conns in connection.c.
15183 - Revise tor-spec to add more/better stream end reasons.
15184 - Revise all calls to connection_edge_end to avoid sending "misc",
15185 and to take errno into account where possible.
15188 - Fix a race condition that can trigger an assert, when we have a
15189 pending create cell and an OR connection fails right then.
15190 - Fix several double-mark-for-close bugs, e.g. where we were finding
15191 a conn for a cell even if that conn is already marked for close.
15192 - Make sequence of log messages when starting on win32 with no config
15193 file more reasonable.
15194 - When choosing an exit node for a new non-internal circ, don't take
15195 into account whether it'll be useful for any pending x.onion
15196 addresses -- it won't.
15197 - Turn addr_policy_compare from a tristate to a quadstate; this should
15198 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
15199 for google.com" problem.
15200 - Make "platform" string in descriptor more accurate for Win32 servers,
15201 so it's not just "unknown platform".
15202 - Fix an edge case in parsing config options (thanks weasel).
15203 If they say "--" on the commandline, it's not an option.
15204 - Reject odd-looking addresses at the client (e.g. addresses that
15205 contain a colon), rather than having the server drop them because
15207 - tor-resolve requests were ignoring .exit if there was a working circuit
15208 they could use instead.
15209 - REUSEADDR on normal platforms means you can rebind to the port
15210 right after somebody else has let it go. But REUSEADDR on win32
15211 means to let you bind to the port _even when somebody else
15212 already has it bound_! So, don't do that on Win32.
15213 - Change version parsing logic: a version is "obsolete" if it is not
15214 recommended and (1) there is a newer recommended version in the
15215 same series, or (2) there are no recommended versions in the same
15216 series, but there are some recommended versions in a newer series.
15217 A version is "new" if it is newer than any recommended version in
15219 - Stop most cases of hanging up on a socks connection without sending
15223 - Require BandwidthRate to be at least 20kB/s for servers.
15224 - When a dirserver causes you to give a warn, mention which dirserver
15226 - New config option DirAllowPrivateAddresses for authdirservers.
15227 Now by default they refuse router descriptors that have non-IP or
15228 private-IP addresses.
15229 - Stop publishing socksport in the directory, since it's not
15230 actually meant to be public. For compatibility, publish a 0 there
15232 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
15233 smart" value, that is low for servers and high for clients.
15234 - If our clock jumps forward by 100 seconds or more, assume something
15235 has gone wrong with our network and abandon all not-yet-used circs.
15236 - Warn when exit policy implicitly allows local addresses.
15237 - If we get an incredibly skewed timestamp from a dirserver mirror
15238 that isn't a verified OR, don't warn -- it's probably him that's
15240 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
15241 cookies to disk and doesn't log each web request to disk. (Thanks
15242 to Brett Carrington for pointing this out.)
15243 - When a client asks us for a dir mirror and we don't have one,
15244 launch an attempt to get a fresh one.
15245 - If we're hibernating and we get a SIGINT, exit immediately.
15246 - Add --with-dmalloc ./configure option, to track memory leaks.
15247 - And try to free all memory on closing, so we can detect what
15249 - Cache local dns resolves correctly even when they're .exit
15251 - Give a better warning when some other server advertises an
15252 ORPort that is actually an apache running ssl.
15253 - Add "opt hibernating 1" to server descriptor to make it clearer
15254 whether the server is hibernating.
15257 Changes in version 0.0.9.6 - 2005-03-24
15258 o Bugfixes on 0.0.9.x (crashes and asserts):
15259 - Add new end stream reasons to maintainance branch. Fix bug where
15260 reason (8) could trigger an assert. Prevent bug from recurring.
15261 - Apparently win32 stat wants paths to not end with a slash.
15262 - Fix assert triggers in assert_cpath_layer_ok(), where we were
15263 blowing away the circuit that conn->cpath_layer points to, then
15264 checking to see if the circ is well-formed. Backport check to make
15265 sure we dont use the cpath on a closed connection.
15266 - Prevent circuit_resume_edge_reading_helper() from trying to package
15267 inbufs for marked-for-close streams.
15268 - Don't crash on hup if your options->address has become unresolvable.
15269 - Some systems (like OS X) sometimes accept() a connection and tell
15270 you the remote host is 0.0.0.0:0. If this happens, due to some
15271 other mis-features, we get confused; so refuse the conn for now.
15273 o Bugfixes on 0.0.9.x (other):
15274 - Fix harmless but scary "Unrecognized content encoding" warn message.
15275 - Add new stream error reason: TORPROTOCOL reason means "you are not
15276 speaking a version of Tor I understand; say bye-bye to your stream."
15277 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
15278 into the future, now that we are more tolerant of skew. This
15279 resolves a bug where a Tor server would refuse to cache a directory
15280 because all the directories it gets are too far in the future;
15281 yet the Tor server never logs any complaints about clock skew.
15282 - Mac packaging magic: make man pages useable, and do not overwrite
15283 existing torrc files.
15284 - Make OS X log happily to /var/log/tor/tor.log
15287 Changes in version 0.0.9.5 - 2005-02-22
15288 o Bugfixes on 0.0.9.x:
15289 - Fix an assert race at exit nodes when resolve requests fail.
15290 - Stop picking unverified dir mirrors--it only leads to misery.
15291 - Patch from Matt Edman to make NT services work better. Service
15292 support is still not compiled into the executable by default.
15293 - Patch from Dmitri Bely so the Tor service runs better under
15294 the win32 SYSTEM account.
15295 - Make tor-resolve actually work (?) on Win32.
15296 - Fix a sign bug when getrlimit claims to have 4+ billion
15297 file descriptors available.
15298 - Stop refusing to start when bandwidthburst == bandwidthrate.
15299 - When create cells have been on the onion queue more than five
15300 seconds, just send back a destroy and take them off the list.
15303 Changes in version 0.0.9.4 - 2005-02-03
15304 o Bugfixes on 0.0.9:
15305 - Fix an assert bug that took down most of our servers: when
15306 a server claims to have 1 GB of bandwidthburst, don't
15308 - Don't crash as badly if we have spawned the max allowed number
15309 of dnsworkers, or we're out of file descriptors.
15310 - Block more file-sharing ports in the default exit policy.
15311 - MaxConn is now automatically set to the hard limit of max
15312 file descriptors we're allowed (ulimit -n), minus a few for
15314 - Give a clearer message when servers need to raise their
15315 ulimit -n when they start running out of file descriptors.
15316 - SGI Compatibility patches from Jan Schaumann.
15317 - Tolerate a corrupt cached directory better.
15318 - When a dirserver hasn't approved your server, list which one.
15319 - Go into soft hibernation after 95% of the bandwidth is used,
15320 not 99%. This is especially important for daily hibernators who
15321 have a small accounting max. Hopefully it will result in fewer
15322 cut connections when the hard hibernation starts.
15323 - Load-balance better when using servers that claim more than
15324 800kB/s of capacity.
15325 - Make NT services work (experimental, only used if compiled in).
15328 Changes in version 0.0.9.3 - 2005-01-21
15329 o Bugfixes on 0.0.9:
15330 - Backport the cpu use fixes from main branch, so busy servers won't
15331 need as much processor time.
15332 - Work better when we go offline and then come back, or when we
15333 run Tor at boot before the network is up. We do this by
15334 optimistically trying to fetch a new directory whenever an
15335 application request comes in and we think we're offline -- the
15336 human is hopefully a good measure of when the network is back.
15337 - Backport some minimal hidserv bugfixes: keep rend circuits open as
15338 long as you keep using them; actually publish hidserv descriptors
15339 shortly after they change, rather than waiting 20-40 minutes.
15340 - Enable Mac startup script by default.
15341 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
15342 - When you update AllowUnverifiedNodes or FirewallPorts via the
15343 controller's setconf feature, we were always appending, never
15345 - When you update HiddenServiceDir via setconf, it was screwing up
15346 the order of reading the lines, making it fail.
15347 - Do not rewrite a cached directory back to the cache; otherwise we
15348 will think it is recent and not fetch a newer one on startup.
15349 - Workaround for webservers that lie about Content-Encoding: Tor
15350 now tries to autodetect compressed directories and compression
15351 itself. This lets us Proxypass dir fetches through apache.
15354 Changes in version 0.0.9.2 - 2005-01-04
15355 o Bugfixes on 0.0.9 (crashes and asserts):
15356 - Fix an assert on startup when the disk is full and you're logging
15358 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
15359 style address, then we'd crash.
15360 - Fix an assert trigger when the running-routers string we get from
15361 a dirserver is broken.
15362 - Make worker threads start and run on win32. Now win32 servers
15364 - Bandaid (not actually fix, but now it doesn't crash) an assert
15365 where the dns worker dies mysteriously and the main Tor process
15366 doesn't remember anything about the address it was resolving.
15368 o Bugfixes on 0.0.9 (Win32):
15369 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
15370 name out of the warning/assert messages.
15371 - Fix a superficial "unhandled error on read" bug on win32.
15372 - The win32 installer no longer requires a click-through for our
15373 license, since our Free Software license grants rights but does not
15375 - Win32: When connecting to a dirserver fails, try another one
15376 immediately. (This was already working for non-win32 Tors.)
15377 - Stop trying to parse $HOME on win32 when hunting for default
15379 - Make tor-resolve.c work on win32 by calling network_init().
15381 o Bugfixes on 0.0.9 (other):
15382 - Make 0.0.9.x build on Solaris again.
15383 - Due to a fencepost error, we were blowing away the \n when reporting
15384 confvalue items in the controller. So asking for multiple config
15385 values at once couldn't work.
15386 - When listing circuits that are pending on an opening OR connection,
15387 if we're an OR we were listing circuits that *end* at us as
15388 being pending on every listener, dns/cpu worker, etc. Stop that.
15389 - Dirservers were failing to create 'running-routers' or 'directory'
15390 strings if we had more than some threshold of routers. Fix them so
15391 they can handle any number of routers.
15392 - Fix a superficial "Duplicate mark for close" bug.
15393 - Stop checking for clock skew for OR connections, even for servers.
15394 - Fix a fencepost error that was chopping off the last letter of any
15395 nickname that is the maximum allowed nickname length.
15396 - Update URLs in log messages so they point to the new website.
15397 - Fix a potential problem in mangling server private keys while
15398 writing to disk (not triggered yet, as far as we know).
15399 - Include the licenses for other free software we include in Tor,
15400 now that we're shipping binary distributions more regularly.
15403 Changes in version 0.0.9.1 - 2004-12-15
15404 o Bugfixes on 0.0.9:
15405 - Make hibernation actually work.
15406 - Make HashedControlPassword config option work.
15407 - When we're reporting event circuit status to a controller,
15408 don't use the stream status code.
15411 Changes in version 0.0.9 - 2004-12-12
15413 - Clean up manpage and torrc.sample file.
15414 - Clean up severities and text of log warnings.
15416 - Make servers trigger an assert when they enter hibernation.
15419 Changes in version 0.0.9rc7 - 2004-12-08
15420 o Bugfixes on 0.0.9rc:
15421 - Fix a stack-trashing crash when an exit node begins hibernating.
15422 - Avoid looking at unallocated memory while considering which
15423 ports we need to build circuits to cover.
15424 - Stop a sigpipe: when an 'end' cell races with eof from the app,
15425 we shouldn't hold-open-until-flush if the eof arrived first.
15426 - Fix a bug with init_cookie_authentication() in the controller.
15427 - When recommending new-format log lines, if the upper bound is
15428 LOG_ERR, leave it implicit.
15430 o Bugfixes on 0.0.8.1:
15431 - Fix a whole slew of memory leaks.
15432 - Fix isspace() and friends so they still make Solaris happy
15433 but also so they don't trigger asserts on win32.
15434 - Fix parse_iso_time on platforms without strptime (eg win32).
15435 - win32: tolerate extra "readable" events better.
15436 - win32: when being multithreaded, leave parent fdarray open.
15437 - Make unit tests work on win32.
15440 Changes in version 0.0.9rc6 - 2004-12-06
15441 o Bugfixes on 0.0.9pre:
15442 - Clean up some more integer underflow opportunities (not exploitable
15444 - While hibernating, hup should not regrow our listeners.
15445 - Send an end to the streams we close when we hibernate, rather
15446 than just chopping them off.
15447 - React to eof immediately on non-open edge connections.
15449 o Bugfixes on 0.0.8.1:
15450 - Calculate timeout for waiting for a connected cell from the time
15451 we sent the begin cell, not from the time the stream started. If
15452 it took a long time to establish the circuit, we would time out
15453 right after sending the begin cell.
15454 - Fix router_compare_addr_to_addr_policy: it was not treating a port
15455 of * as always matching, so we were picking reject *:* nodes as
15456 exit nodes too. Oops.
15459 - New circuit building strategy: keep a list of ports that we've
15460 used in the past 6 hours, and always try to have 2 circuits open
15461 or on the way that will handle each such port. Seed us with port
15462 80 so web users won't complain that Tor is "slow to start up".
15463 - Make kill -USR1 dump more useful stats about circuits.
15464 - When warning about retrying or giving up, print the address, so
15465 the user knows which one it's talking about.
15466 - If you haven't used a clean circuit in an hour, throw it away,
15467 just to be on the safe side. (This means after 6 hours a totally
15468 unused Tor client will have no circuits open.)
15471 Changes in version 0.0.9rc5 - 2004-12-01
15472 o Bugfixes on 0.0.8.1:
15473 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
15474 - Let resolve conns retry/expire also, rather than sticking around
15476 - If we are using select, make sure we stay within FD_SETSIZE.
15478 o Bugfixes on 0.0.9pre:
15479 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
15480 but doesn't seem to be currently; thanks to Ilja van Sprundel for
15482 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
15483 instead. Impose minima and maxima for all *Period options; impose
15484 even tighter maxima for fetching if we are a caching dirserver.
15485 Clip rather than rejecting.
15486 - Fetch cached running-routers from servers that serve it (that is,
15487 authdirservers and servers running 0.0.9rc5-cvs or later.)
15490 - Accept *:706 (silc) in default exit policy.
15491 - Implement new versioning format for post 0.1.
15492 - Support "foo.nickname.exit" addresses, to let Alice request the
15493 address "foo" as viewed by exit node "nickname". Based on a patch
15495 - Make tor --version --version dump the cvs Id of every file.
15498 Changes in version 0.0.9rc4 - 2004-11-28
15499 o Bugfixes on 0.0.8.1:
15500 - Make windows sockets actually non-blocking (oops), and handle
15501 win32 socket errors better.
15503 o Bugfixes on 0.0.9rc1:
15504 - Actually catch the -USR2 signal.
15507 Changes in version 0.0.9rc3 - 2004-11-25
15508 o Bugfixes on 0.0.8.1:
15509 - Flush the log file descriptor after we print "Tor opening log file",
15510 so we don't see those messages days later.
15512 o Bugfixes on 0.0.9rc1:
15513 - Make tor-resolve work again.
15514 - Avoid infinite loop in tor-resolve if tor hangs up on it.
15515 - Fix an assert trigger for clients/servers handling resolves.
15518 Changes in version 0.0.9rc2 - 2004-11-24
15519 o Bugfixes on 0.0.9rc1:
15520 - I broke socks5 support while fixing the eof bug.
15521 - Allow unitless bandwidths and intervals; they default to bytes
15523 - New servers don't start out hibernating; they are active until
15524 they run out of bytes, so they have a better estimate of how
15525 long it takes, and so their operators can know they're working.
15528 Changes in version 0.0.9rc1 - 2004-11-23
15529 o Bugfixes on 0.0.8.1:
15530 - Finally fix a bug that's been plaguing us for a year:
15531 With high load, circuit package window was reaching 0. Whenever
15532 we got a circuit-level sendme, we were reading a lot on each
15533 socket, but only writing out a bit. So we would eventually reach
15534 eof. This would be noticed and acted on even when there were still
15535 bytes sitting in the inbuf.
15536 - When poll() is interrupted, we shouldn't believe the revents values.
15538 o Bugfixes on 0.0.9pre6:
15539 - Fix hibernate bug that caused pre6 to be broken.
15540 - Don't keep rephist info for routers that haven't had activity for
15541 24 hours. (This matters now that clients have keys, since we track
15543 - Never call close_temp_logs while validating log options.
15544 - Fix backslash-escaping on tor.sh.in and torctl.in.
15547 - Implement weekly/monthly/daily accounting: now you specify your
15548 hibernation properties by
15549 AccountingMax N bytes|KB|MB|GB|TB
15550 AccountingStart day|week|month [day] HH:MM
15551 Defaults to "month 1 0:00".
15552 - Let bandwidth and interval config options be specified as 5 bytes,
15553 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15554 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15555 get back to normal.)
15556 - If your requested entry or exit node has advertised bandwidth 0,
15558 - Be more greedy about filling up relay cells -- we try reading again
15559 once we've processed the stuff we read, in case enough has arrived
15560 to fill the last cell completely.
15561 - Apply NT service patch from Osamu Fujino. Still needs more work.
15564 Changes in version 0.0.9pre6 - 2004-11-15
15565 o Bugfixes on 0.0.8.1:
15566 - Fix assert failure on malformed socks4a requests.
15567 - Use identity comparison, not nickname comparison, to choose which
15568 half of circuit-ID-space each side gets to use. This is needed
15569 because sometimes we think of a router as a nickname, and sometimes
15570 as a hex ID, and we can't predict what the other side will do.
15571 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15572 write() call will fail and we handle it there.
15573 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15574 and smartlist_len, which are two major profiling offenders.
15576 o Bugfixes on 0.0.9pre5:
15577 - Fix a bug in read_all that was corrupting config files on windows.
15578 - When we're raising the max number of open file descriptors to
15579 'unlimited', don't log that we just raised it to '-1'.
15580 - Include event code with events, as required by control-spec.txt.
15581 - Don't give a fingerprint when clients do --list-fingerprint:
15582 it's misleading, because it will never be the same again.
15583 - Stop using strlcpy in tor_strndup, since it was slowing us
15585 - Remove warn on startup about missing cached-directory file.
15586 - Make kill -USR1 work again.
15587 - Hibernate if we start tor during the "wait for wakeup-time" phase
15588 of an accounting interval. Log our hibernation plans better.
15589 - Authoritative dirservers now also cache their directory, so they
15590 have it on start-up.
15593 - Fetch running-routers; cache running-routers; compress
15594 running-routers; serve compressed running-routers.z
15595 - Add NSI installer script contributed by J Doe.
15596 - Commit VC6 and VC7 workspace/project files.
15597 - Commit a tor.spec for making RPM files, with help from jbash.
15598 - Add contrib/torctl.in contributed by Glenn Fink.
15599 - Implement the control-spec's SAVECONF command, to write your
15600 configuration to torrc.
15601 - Get cookie authentication for the controller closer to working.
15602 - Include control-spec.txt in the tarball.
15603 - When set_conf changes our server descriptor, upload a new copy.
15604 But don't upload it too often if there are frequent changes.
15605 - Document authentication config in man page, and document signals
15607 - Clean up confusing parts of man page and torrc.sample.
15608 - Make expand_filename handle ~ and ~username.
15609 - Use autoconf to enable largefile support where necessary. Use
15610 ftello where available, since ftell can fail at 2GB.
15611 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
15612 log more informatively.
15613 - Give a slightly more useful output for "tor -h".
15614 - Refuse application socks connections to port 0.
15615 - Check clock skew for verified servers, but allow unverified
15616 servers and clients to have any clock skew.
15617 - Break DirFetchPostPeriod into:
15618 - DirFetchPeriod for fetching full directory,
15619 - StatusFetchPeriod for fetching running-routers,
15620 - DirPostPeriod for posting server descriptor,
15621 - RendPostPeriod for posting hidden service descriptors.
15622 - Make sure the hidden service descriptors are at a random offset
15623 from each other, to hinder linkability.
15626 Changes in version 0.0.9pre5 - 2004-11-09
15627 o Bugfixes on 0.0.9pre4:
15628 - Fix a seg fault in unit tests (doesn't affect main program).
15629 - Fix an assert bug where a hidden service provider would fail if
15630 the first hop of his rendezvous circuit was down.
15631 - Hidden service operators now correctly handle version 1 style
15632 INTRODUCE1 cells (nobody generates them still, so not a critical
15634 - If do_hup fails, actually notice.
15635 - Handle more errnos from accept() without closing the listener.
15636 Some OpenBSD machines were closing their listeners because
15637 they ran out of file descriptors.
15638 - Send resolve cells to exit routers that are running a new
15639 enough version of the resolve code to work right.
15640 - Better handling of winsock includes on non-MSV win32 compilers.
15641 - Some people had wrapped their tor client/server in a script
15642 that would restart it whenever it died. This did not play well
15643 with our "shut down if your version is obsolete" code. Now people
15644 don't fetch a new directory if their local cached version is
15646 - Make our autogen.sh work on ksh as well as bash.
15649 - Hibernation: New config option "AccountingMaxKB" lets you
15650 set how many KBytes per month you want to allow your server to
15651 consume. Rather than spreading those bytes out evenly over the
15652 month, we instead hibernate for some of the month and pop up
15653 at a deterministic time, work until the bytes are consumed, then
15654 hibernate again. Config option "MonthlyAccountingStart" lets you
15655 specify which day of the month your billing cycle starts on.
15656 - Control interface: a separate program can now talk to your
15657 client/server over a socket, and get/set config options, receive
15658 notifications of circuits and streams starting/finishing/dying,
15659 bandwidth used, etc. The next step is to get some GUIs working.
15660 Let us know if you want to help out. See doc/control-spec.txt .
15661 - Ship a contrib/tor-control.py as an example script to interact
15662 with the control port.
15663 - "tor --hash-password zzyxz" will output a salted password for
15664 use in authenticating to the control interface.
15665 - New log format in config:
15666 "Log minsev[-maxsev] stdout|stderr|syslog" or
15667 "Log minsev[-maxsev] file /var/foo"
15670 - DirPolicy config option, to let people reject incoming addresses
15671 from their dirserver.
15672 - "tor --list-fingerprint" will list your identity key fingerprint
15674 - Add "pass" target for RedirectExit, to make it easier to break
15675 out of a sequence of RedirectExit rules.
15676 - Clients now generate a TLS cert too, in preparation for having
15677 them act more like real nodes.
15678 - Ship src/win32/ in the tarball, so people can use it to build.
15679 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
15681 - New "router-status" line in directory, to better bind each verified
15682 nickname to its identity key.
15683 - Deprecate unofficial config option abbreviations, and abbreviations
15684 not on the command line.
15685 - Add a pure-C tor-resolve implementation.
15686 - Use getrlimit and friends to ensure we can reach MaxConn (currently
15687 1024) file descriptors.
15689 o Code security improvements, inspired by Ilja:
15690 - Replace sprintf with snprintf. (I think they were all safe, but
15692 - Replace strcpy/strncpy with strlcpy in more places.
15693 - Avoid strcat; use snprintf or strlcat instead.
15694 - snprintf wrapper with consistent (though not C99) overflow behavior.
15697 Changes in version 0.0.9pre4 - 2004-10-17
15698 o Bugfixes on 0.0.9pre3:
15699 - If the server doesn't specify an exit policy, use the real default
15700 exit policy, not reject *:*.
15701 - Ignore fascistfirewall when uploading/downloading hidden service
15702 descriptors, since we go through Tor for those; and when using
15703 an HttpProxy, since we assume it can reach them all.
15704 - When looking for an authoritative dirserver, use only the ones
15705 configured at boot. Don't bother looking in the directory.
15706 - The rest of the fix for get_default_conf_file() on older win32.
15707 - Make 'Routerfile' config option obsolete.
15710 - New 'MyFamily nick1,...' config option for a server to
15711 specify other servers that shouldn't be used in the same circuit
15712 with it. Only believed if nick1 also specifies us.
15713 - New 'NodeFamily nick1,nick2,...' config option for a client to
15714 specify nodes that it doesn't want to use in the same circuit.
15715 - New 'Redirectexit pattern address:port' config option for a
15716 server to redirect exit connections, e.g. to a local squid.
15719 Changes in version 0.0.9pre3 - 2004-10-13
15720 o Bugfixes on 0.0.8.1:
15721 - Better torrc example lines for dirbindaddress and orbindaddress.
15722 - Improved bounds checking on parsed ints (e.g. config options and
15723 the ones we find in directories.)
15724 - Better handling of size_t vs int, so we're more robust on 64
15726 - Fix the rest of the bug where a newly started OR would appear
15727 as unverified even after we've added his fingerprint and hupped
15729 - Fix a bug from 0.0.7: when read() failed on a stream, we would
15730 close it without sending back an end. So 'connection refused'
15731 would simply be ignored and the user would get no response.
15733 o Bugfixes on 0.0.9pre2:
15734 - Serving the cached-on-disk directory to people is bad. We now
15735 provide no directory until we've fetched a fresh one.
15736 - Workaround for bug on windows where cached-directories get crlf
15738 - Make get_default_conf_file() work on older windows too.
15739 - If we write a *:* exit policy line in the descriptor, don't write
15740 any more exit policy lines.
15743 - Use only 0.0.9pre1 and later servers for resolve cells.
15744 - Make the dirservers file obsolete.
15745 - Include a dir-signing-key token in directories to tell the
15746 parsing entity which key is being used to sign.
15747 - Remove the built-in bulky default dirservers string.
15748 - New config option "Dirserver %s:%d [fingerprint]", which can be
15749 repeated as many times as needed. If no dirservers specified,
15750 default to moria1,moria2,tor26.
15751 - Make moria2 advertise a dirport of 80, so people behind firewalls
15752 will be able to get a directory.
15753 - Http proxy support
15754 - Dirservers translate requests for http://%s:%d/x to /x
15755 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
15756 be routed through this host.
15757 - Clients ask for /tor/x rather than /x for new enough dirservers.
15758 This way we can one day coexist peacefully with apache.
15759 - Clients specify a "Host: %s%d" http header, to be compatible
15760 with more proxies, and so running squid on an exit node can work.
15763 Changes in version 0.0.8.1 - 2004-10-13
15765 - Fix a seg fault that can be triggered remotely for Tor
15766 clients/servers with an open dirport.
15767 - Fix a rare assert trigger, where routerinfos for entries in
15768 our cpath would expire while we're building the path.
15769 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15770 - Fix a rare seg fault for people running hidden services on
15771 intermittent connections.
15772 - Fix a bug in parsing opt keywords with objects.
15773 - Fix a stale pointer assert bug when a stream detaches and
15775 - Fix a string format vulnerability (probably not exploitable)
15776 in reporting stats locally.
15777 - Fix an assert trigger: sometimes launching circuits can fail
15778 immediately, e.g. because too many circuits have failed recently.
15779 - Fix a compile warning on 64 bit platforms.
15782 Changes in version 0.0.9pre2 - 2004-10-03
15784 - Make fetching a cached directory work for 64-bit platforms too.
15785 - Make zlib.h a required header, not an optional header.
15788 Changes in version 0.0.9pre1 - 2004-10-01
15790 - Stop using separate defaults for no-config-file and
15791 empty-config-file. Now you have to explicitly turn off SocksPort,
15792 if you don't want it open.
15793 - Fix a bug in OutboundBindAddress so it (hopefully) works.
15794 - Improve man page to mention more of the 0.0.8 features.
15795 - Fix a rare seg fault for people running hidden services on
15796 intermittent connections.
15797 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
15799 - Fix more dns related bugs: send back resolve_failed and end cells
15800 more reliably when the resolve fails, rather than closing the
15801 circuit and then trying to send the cell. Also attach dummy resolve
15802 connections to a circuit *before* calling dns_resolve(), to fix
15803 a bug where cached answers would never be sent in RESOLVED cells.
15804 - When we run out of disk space, or other log writing error, don't
15805 crash. Just stop logging to that log and continue.
15806 - We were starting to daemonize before we opened our logs, so if
15807 there were any problems opening logs, we would complain to stderr,
15808 which wouldn't work, and then mysteriously exit.
15809 - Fix a rare bug where sometimes a verified OR would connect to us
15810 before he'd uploaded his descriptor, which would cause us to
15811 assign conn->nickname as though he's unverified. Now we look through
15812 the fingerprint list to see if he's there.
15813 - Fix a rare assert trigger, where routerinfos for entries in
15814 our cpath would expire while we're building the path.
15817 - Clients can ask dirservers for /dir.z to get a compressed version
15818 of the directory. Only works for servers running 0.0.9, of course.
15819 - Make clients cache directories and use them to seed their router
15820 lists at startup. This means clients have a datadir again.
15821 - Configuration infrastructure support for warning on obsolete
15823 - Respond to content-encoding headers by trying to uncompress as
15825 - Reply with a deflated directory when a client asks for "dir.z".
15826 We could use allow-encodings instead, but allow-encodings isn't
15827 specified in HTTP 1.0.
15828 - Raise the max dns workers from 50 to 100.
15829 - Discourage people from setting their dirfetchpostperiod more often
15830 than once per minute.
15831 - Protect dirservers from overzealous descriptor uploading -- wait
15832 10 seconds after directory gets dirty, before regenerating.
15835 Changes in version 0.0.8 - 2004-08-25
15836 o Port it to SunOS 5.9 / Athena
15839 Changes in version 0.0.8rc2 - 2004-08-20
15840 o Make it compile on cygwin again.
15841 o When picking unverified routers, skip those with low uptime and/or
15842 low bandwidth, depending on what properties you care about.
15845 Changes in version 0.0.8rc1 - 2004-08-18
15846 o Changes from 0.0.7.3:
15848 - Fix assert triggers: if the other side returns an address 0.0.0.0,
15849 don't put it into the client dns cache.
15850 - If a begin failed due to exit policy, but we believe the IP address
15851 should have been allowed, switch that router to exitpolicy reject *:*
15852 until we get our next directory.
15854 - Clients choose nodes proportional to advertised bandwidth.
15855 - Avoid using nodes with low uptime as introduction points.
15856 - Handle servers with dynamic IP addresses: don't replace
15857 options->Address with the resolved one at startup, and
15858 detect our address right before we make a routerinfo each time.
15859 - 'FascistFirewall' option to pick dirservers and ORs on specific
15860 ports; plus 'FirewallPorts' config option to tell FascistFirewall
15861 which ports are open. (Defaults to 80,443)
15862 - Be more aggressive about trying to make circuits when the network
15863 has changed (e.g. when you unsuspend your laptop).
15864 - Check for time skew on http headers; report date in response to
15866 - If the entrynode config line has only one node, don't pick it as
15868 - Add strict{entry|exit}nodes config options. If set to 1, then
15869 we refuse to build circuits that don't include the specified entry
15871 - OutboundBindAddress config option, to bind to a specific
15872 IP address for outgoing connect()s.
15873 - End truncated log entries (e.g. directories) with "[truncated]".
15875 o Patches to 0.0.8preX:
15877 - Patches to compile and run on win32 again (maybe)?
15878 - Fix crash when looking for ~/.torrc with no $HOME set.
15879 - Fix a race bug in the unit tests.
15880 - Handle verified/unverified name collisions better when new
15881 routerinfo's arrive in a directory.
15882 - Sometimes routers were getting entered into the stats before
15883 we'd assigned their identity_digest. Oops.
15884 - Only pick and establish intro points after we've gotten a
15887 - AllowUnverifiedNodes config option to let circuits choose no-name
15888 routers in entry,middle,exit,introduction,rendezvous positions.
15889 Allow middle and rendezvous positions by default.
15890 - Add a man page for tor-resolve.
15893 Changes in version 0.0.7.3 - 2004-08-12
15894 o Stop dnsworkers from triggering an assert failure when you
15895 ask them to resolve the host "".
15898 Changes in version 0.0.8pre3 - 2004-08-09
15899 o Changes from 0.0.7.2:
15900 - Allow multiple ORs with same nickname in routerlist -- now when
15901 people give us one identity key for a nickname, then later
15902 another, we don't constantly complain until the first expires.
15903 - Remember used bandwidth (both in and out), and publish 15-minute
15904 snapshots for the past day into our descriptor.
15905 - You can now fetch $DIRURL/running-routers to get just the
15906 running-routers line, not the whole descriptor list. (But
15907 clients don't use this yet.)
15908 - When people mistakenly use Tor as an http proxy, point them
15909 at the tor-doc.html rather than the INSTALL.
15910 - Remove our mostly unused -- and broken -- hex_encode()
15911 function. Use base16_encode() instead. (Thanks to Timo Lindfors
15912 for pointing out this bug.)
15913 - Rotate onion keys every 12 hours, not every 2 hours, so we have
15914 fewer problems with people using the wrong key.
15915 - Change the default exit policy to reject the default edonkey,
15916 kazaa, gnutella ports.
15917 - Add replace_file() to util.[ch] to handle win32's rename().
15919 o Changes from 0.0.8preX:
15920 - Fix two bugs in saving onion keys to disk when rotating, so
15921 hopefully we'll get fewer people using old onion keys.
15922 - Fix an assert error that was making SocksPolicy not work.
15923 - Be willing to expire routers that have an open dirport -- it's
15924 just the authoritative dirservers we want to not forget.
15925 - Reject tor-resolve requests for .onion addresses early, so we
15926 don't build a whole rendezvous circuit and then fail.
15927 - When you're warning a server that he's unverified, don't cry
15928 wolf unpredictably.
15929 - Fix a race condition: don't try to extend onto a connection
15930 that's still handshaking.
15931 - For servers in clique mode, require the conn to be open before
15932 you'll choose it for your path.
15933 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
15934 end relay cell, etc.
15935 - Measure bandwidth capacity over the last 24 hours, not just 12
15936 - Bugfix: authoritative dirservers were making and signing a new
15937 directory for each client, rather than reusing the cached one.
15940 Changes in version 0.0.8pre2 - 2004-08-04
15941 o Changes from 0.0.7.2:
15943 - Check directory signature _before_ you decide whether you're
15944 you're running an obsolete version and should exit.
15945 - Check directory signature _before_ you parse the running-routers
15946 list to decide who's running or verified.
15947 - Bugfixes and features:
15948 - Check return value of fclose while writing to disk, so we don't
15949 end up with broken files when servers run out of disk space.
15950 - Log a warning if the user uses an unsafe socks variant, so people
15951 are more likely to learn about privoxy or socat.
15952 - Dirservers now include RFC1123-style dates in the HTTP headers,
15953 which one day we will use to better detect clock skew.
15955 o Changes from 0.0.8pre1:
15956 - Make it compile without warnings again on win32.
15957 - Log a warning if you're running an unverified server, to let you
15958 know you might want to get it verified.
15959 - Only pick a default nickname if you plan to be a server.
15962 Changes in version 0.0.8pre1 - 2004-07-23
15964 - Made our unit tests compile again on OpenBSD 3.5, and tor
15965 itself compile again on OpenBSD on a sparc64.
15966 - We were neglecting milliseconds when logging on win32, so
15967 everything appeared to happen at the beginning of each second.
15969 o Protocol changes:
15970 - 'Extend' relay cell payloads now include the digest of the
15971 intended next hop's identity key. Now we can verify that we're
15972 extending to the right router, and also extend to routers we
15973 hadn't heard of before.
15976 - Tor nodes can now act as relays (with an advertised ORPort)
15977 without being manually verified by the dirserver operators.
15978 - Uploaded descriptors of unverified routers are now accepted
15979 by the dirservers, and included in the directory.
15980 - Verified routers are listed by nickname in the running-routers
15981 list; unverified routers are listed as "$<fingerprint>".
15982 - We now use hash-of-identity-key in most places rather than
15983 nickname or addr:port, for improved security/flexibility.
15984 - To avoid Sybil attacks, paths still use only verified servers.
15985 But now we have a chance to play around with hybrid approaches.
15986 - Nodes track bandwidth usage to estimate capacity (not used yet).
15987 - ClientOnly option for nodes that never want to become servers.
15988 - Directory caching.
15989 - "AuthoritativeDir 1" option for the official dirservers.
15990 - Now other nodes (clients and servers) will cache the latest
15991 directory they've pulled down.
15992 - They can enable their DirPort to serve it to others.
15993 - Clients will pull down a directory from any node with an open
15994 DirPort, and check the signature/timestamp correctly.
15995 - Authoritative dirservers now fetch directories from other
15996 authdirservers, to stay better synced.
15997 - Running-routers list tells who's down also, along with noting
15998 if they're verified (listed by nickname) or unverified (listed
16000 - Allow dirservers to serve running-router list separately.
16001 This isn't used yet.
16002 - ORs connect-on-demand to other ORs
16003 - If you get an extend cell to an OR you're not connected to,
16004 connect, handshake, and forward the create cell.
16005 - The authoritative dirservers stay connected to everybody,
16006 and everybody stays connected to 0.0.7 servers, but otherwise
16007 clients/servers expire unused connections after 5 minutes.
16008 - When servers get a sigint, they delay 30 seconds (refusing new
16009 connections) then exit. A second sigint causes immediate exit.
16010 - File and name management:
16011 - Look for .torrc if no CONFDIR "torrc" is found.
16012 - If no datadir is defined, then choose, make, and secure ~/.tor
16014 - If torrc not found, exitpolicy reject *:*.
16015 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
16016 - If no nickname is defined, derive default from hostname.
16017 - Rename secret key files, e.g. identity.key -> secret_id_key,
16018 to discourage people from mailing their identity key to tor-ops.
16019 - Refuse to build a circuit before the directory has arrived --
16020 it won't work anyway, since you won't know the right onion keys
16022 - Try other dirservers immediately if the one you try is down. This
16023 should tolerate down dirservers better now.
16024 - Parse tor version numbers so we can do an is-newer-than check
16025 rather than an is-in-the-list check.
16026 - New socks command 'resolve', to let us shim gethostbyname()
16028 - A 'tor_resolve' script to access the socks resolve functionality.
16029 - A new socks-extensions.txt doc file to describe our
16030 interpretation and extensions to the socks protocols.
16031 - Add a ContactInfo option, which gets published in descriptor.
16032 - Publish OR uptime in descriptor (and thus in directory) too.
16033 - Write tor version at the top of each log file
16034 - New docs in the tarball:
16036 - Document that you should proxy your SSL traffic too.
16039 Changes in version 0.0.7.2 - 2004-07-07
16040 o A better fix for the 0.0.0.0 problem, that will hopefully
16041 eliminate the remaining related assertion failures.
16044 Changes in version 0.0.7.1 - 2004-07-04
16045 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
16046 since internally we use 0.0.0.0 to signify "not yet resolved".
16049 Changes in version 0.0.7 - 2004-06-07
16050 o Updated the man page to reflect the new features.
16053 Changes in version 0.0.7rc2 - 2004-06-06
16054 o Changes from 0.0.7rc1:
16055 - Make it build on Win32 again.
16056 o Changes from 0.0.6.2:
16057 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
16061 Changes in version 0.0.7rc1 - 2004-06-02
16063 - On sighup, we were adding another log without removing the first
16064 one. So log messages would get duplicated n times for n sighups.
16065 - Several cases of using a connection after we'd freed it. The
16066 problem was that connections that are pending resolve are in both
16067 the pending_resolve tree, and also the circuit's resolving_streams
16068 list. When you want to remove one, you must remove it from both.
16069 - Fix a double-mark-for-close where an end cell arrived for a
16070 resolving stream, and then the resolve failed.
16071 - Check directory signatures based on name of signer, not on whom
16072 we got the directory from. This will let us cache directories more
16075 - Crank up some of our constants to handle more users.
16078 Changes in version 0.0.7pre1 - 2004-06-02
16079 o Fixes for crashes and other obnoxious bugs:
16080 - Fix an epipe bug: sometimes when directory connections failed
16081 to connect, we would give them a chance to flush before closing
16083 - When we detached from a circuit because of resolvefailed, we
16084 would immediately try the same circuit twice more, and then
16085 give up on the resolve thinking we'd tried three different
16087 - Limit the number of intro circuits we'll attempt to build for a
16088 hidden service per 15-minute period.
16089 - Check recommended-software string *early*, before actually parsing
16090 the directory. Thus we can detect an obsolete version and exit,
16091 even if the new directory format doesn't parse.
16092 o Fixes for security bugs:
16093 - Remember which nodes are dirservers when you startup, and if a
16094 random OR enables his dirport, don't automatically assume he's
16095 a trusted dirserver.
16097 - Directory connections were asking the wrong poll socket to
16098 start writing, and not asking themselves to start writing.
16099 - When we detached from a circuit because we sent a begin but
16100 didn't get a connected, we would use it again the first time;
16101 but after that we would correctly switch to a different one.
16102 - Stop warning when the first onion decrypt attempt fails; they
16103 will sometimes legitimately fail now that we rotate keys.
16104 - Override unaligned-access-ok check when $host_cpu is ia64 or
16105 arm. Apparently they allow it but the kernel whines.
16106 - Dirservers try to reconnect periodically too, in case connections
16108 - Fix some memory leaks in directory servers.
16109 - Allow backslash in Win32 filenames.
16110 - Made Tor build complain-free on FreeBSD, hopefully without
16111 breaking other BSD builds. We'll see.
16113 - Doxygen markup on all functions and global variables.
16114 - Make directory functions update routerlist, not replace it. So
16115 now directory disagreements are not so critical a problem.
16116 - Remove the upper limit on number of descriptors in a dirserver's
16117 directory (not that we were anywhere close).
16118 - Allow multiple logfiles at different severity ranges.
16119 - Allow *BindAddress to specify ":port" rather than setting *Port
16120 separately. Allow multiple instances of each BindAddress config
16121 option, so you can bind to multiple interfaces if you want.
16122 - Allow multiple exit policy lines, which are processed in order.
16123 Now we don't need that huge line with all the commas in it.
16124 - Enable accept/reject policies on SOCKS connections, so you can bind
16125 to 0.0.0.0 but still control who can use your OP.
16128 Changes in version 0.0.6.2 - 2004-05-16
16129 o Our integrity-checking digest was checking only the most recent cell,
16130 not the previous cells like we'd thought.
16131 Thanks to Stefan Mark for finding the flaw!
16134 Changes in version 0.0.6.1 - 2004-05-06
16135 o Fix two bugs in our AES counter-mode implementation (this affected
16136 onion-level stream encryption, but not TLS-level). It turns
16137 out we were doing something much more akin to a 16-character
16138 polyalphabetic cipher. Oops.
16139 Thanks to Stefan Mark for finding the flaw!
16140 o Retire moria3 as a directory server, and add tor26 as a directory
16144 Changes in version 0.0.6 - 2004-05-02
16145 [version bump only]
16148 Changes in version 0.0.6rc4 - 2004-05-01
16149 o Update the built-in dirservers list to use the new directory format
16150 o Fix a rare seg fault: if a node offering a hidden service attempts
16151 to build a circuit to Alice's rendezvous point and fails before it
16152 reaches the last hop, it retries with a different circuit, but
16154 o Handle windows socket errors correctly.
16157 Changes in version 0.0.6rc3 - 2004-04-28
16158 o Don't expire non-general excess circuits (if we had enough
16159 circuits open, we were expiring rendezvous circuits -- even
16160 when they had a stream attached. oops.)
16161 o Fetch randomness from /dev/urandom better (not via fopen/fread)
16162 o Better debugging for tls errors
16163 o Some versions of openssl have an SSL_pending function that erroneously
16164 returns bytes when there is a non-application record pending.
16165 o Set Content-Type on the directory and hidserv descriptor.
16166 o Remove IVs from cipher code, since AES-ctr has none.
16167 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
16168 o We were using an array of length zero in a few places.
16169 o win32's gethostbyname can't resolve an IP to an IP.
16170 o win32's close can't close a socket.
16173 Changes in version 0.0.6rc2 - 2004-04-26
16174 o Fix a bug where we were closing tls connections intermittently.
16175 It turns out openssl keeps its errors around -- so if an error
16176 happens, and you don't ask about it, and then another openssl
16177 operation happens and succeeds, and you ask if there was an error,
16178 it tells you about the first error. Fun fun.
16179 o Fix a bug that's been lurking since 27 may 03 (!)
16180 When passing back a destroy cell, we would use the wrong circ id.
16181 'Mostly harmless', but still worth fixing.
16182 o Since we don't support truncateds much, don't bother sending them;
16183 just close the circ.
16184 o check for <machine/limits.h> so we build on NetBSD again (I hope).
16185 o don't crash if a conn that sent a begin has suddenly lost its circuit
16186 (this was quite rare).
16189 Changes in version 0.0.6rc1 - 2004-04-25
16190 o We now rotate link (tls context) keys and onion keys.
16191 o CREATE cells now include oaep padding, so you can tell
16192 if you decrypted them correctly.
16193 o Add bandwidthburst to server descriptor.
16194 o Directories now say which dirserver signed them.
16195 o Use a tor_assert macro that logs failed assertions too.
16198 Changes in version 0.0.6pre5 - 2004-04-18
16199 o changes from 0.0.6pre4:
16200 - make tor build on broken freebsd 5.2 installs
16201 - fix a failed assert when you try an intro point, get a nack, and try
16202 a second one and it works.
16203 - when alice uses a port that the hidden service doesn't accept,
16204 it now sends back an end cell (denied by exit policy). otherwise
16205 alice would just have to wait to time out.
16206 - fix another rare bug: when we had tried all the intro
16207 points for a hidden service, we fetched the descriptor
16208 again, but we left our introcirc thinking it had already
16209 sent an intro, so it kept waiting for a response...
16210 - bugfix: when you sleep your hidden-service laptop, as soon
16211 as it wakes up it tries to upload a service descriptor, but
16212 socketpair fails for some reason (localhost not up yet?).
16213 now we simply give up on that upload, and we'll try again later.
16214 i'd still like to find the bug though.
16215 - if an intro circ waiting for an ack dies before getting one, then
16217 - we were reusing stale service descriptors and refetching usable
16221 Changes in version 0.0.6pre4 - 2004-04-14
16222 o changes from 0.0.6pre3:
16223 - when bob fails to connect to the rendezvous point, and his
16224 circ didn't fail because of the rendezvous point itself, then
16225 he retries a couple of times
16226 - we expire introduction and rendezvous circs more thoroughly
16227 (sometimes they were hanging around forever)
16228 - we expire unattached rendezvous streams that have been around
16229 too long (they were sticking around forever).
16230 - fix a measly fencepost error that was crashing everybody with
16234 Changes in version 0.0.6pre3 - 2004-04-14
16235 o changes from 0.0.6pre2:
16236 - make hup work again
16237 - fix some memory leaks for dirservers
16238 - allow more skew in rendezvous descriptor timestamps, to help
16239 handle people like blanu who don't know what time it is
16240 - normal circs are 3 hops, but some rend/intro circs are 4, if
16241 the initiator doesn't get to choose the last hop
16242 - send acks for introductions, so alice can know whether to try
16244 - bob publishes intro points more correctly
16245 o changes from 0.0.5:
16246 - fix an assert trigger that's been plaguing us since the days
16247 of 0.0.2prexx (thanks weasel!)
16248 - retry stream correctly when we fail to connect because of
16249 exit-policy-reject (should try another) or can't-resolve-address
16250 (also should try another, because dns on random internet servers
16252 - when we hup a dirserver and we've *removed* a server from the
16253 approved-routers list, now we remove that server from the
16254 in-memory directories too
16257 Changes in version 0.0.6pre2 - 2004-04-08
16258 o We fixed our base32 implementation. Now it works on all architectures.
16261 Changes in version 0.0.6pre1 - 2004-04-08
16263 - Hidden services and rendezvous points are implemented. Go to
16264 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
16265 hidden services. (This only works via a socks4a proxy such as
16266 Privoxy, and currently it's quite slow.)
16269 Changes in version 0.0.5 - 2004-03-30
16270 [version bump only]
16273 Changes in version 0.0.5rc3 - 2004-03-29
16274 o Install torrc as torrc.sample -- we no longer clobber your
16276 o Re-enable recommendedversion checking (we broke it in rc2, oops)
16277 o Add in a 'notice' log level for things the operator should hear
16278 but that aren't warnings
16281 Changes in version 0.0.5rc2 - 2004-03-29
16282 o Hold socks connection open until reply is flushed (if possible)
16283 o Make exit nodes resolve IPs to IPs immediately, rather than asking
16284 the dns farm to do it.
16285 o Fix c99 aliasing warnings in rephist.c
16286 o Don't include server descriptors that are older than 24 hours in the
16288 o Give socks 'reject' replies their whole 15s to attempt to flush,
16289 rather than seeing the 60s timeout and assuming the flush had failed.
16290 o Clean automake droppings from the cvs repository
16293 Changes in version 0.0.5rc1 - 2004-03-28
16294 o Fix mangled-state bug in directory fetching (was causing sigpipes).
16295 o Only build circuits after we've fetched the directory: clients were
16296 using only the directory servers before they'd fetched a directory.
16297 This also means longer startup time; so it goes.
16298 o Fix an assert trigger where an OP would fail to handshake, and we'd
16299 expect it to have a nickname.
16300 o Work around a tsocks bug: do a socks reject when AP connection dies
16301 early, else tsocks goes into an infinite loop.
16304 Changes in version 0.0.4 - 2004-03-26
16305 o When connecting to a dirserver or OR and the network is down,
16309 Changes in version 0.0.3 - 2004-03-26
16310 o Warn and fail if server chose a nickname with illegal characters
16311 o Port to Solaris and Sparc:
16312 - include missing header fcntl.h
16313 - have autoconf find -lsocket -lnsl automatically
16314 - deal with hardware word alignment
16315 - make uname() work (solaris has a different return convention)
16316 - switch from using signal() to sigaction()
16317 o Preliminary work on reputation system:
16318 - Keep statistics on success/fail of connect attempts; they're published
16319 by kill -USR1 currently.
16320 - Add a RunTesting option to try to learn link state by creating test
16321 circuits, even when SocksPort is off.
16322 - Remove unused open circuits when there are too many.
16325 Changes in version 0.0.2 - 2004-03-19
16326 - Include strlcpy and strlcat for safer string ops
16327 - define INADDR_NONE so we compile (but still not run) on solaris
16330 Changes in version 0.0.2pre27 - 2004-03-14
16332 - Allow internal tor networks (we were rejecting internal IPs,
16333 now we allow them if they're set explicitly).
16334 - And fix a few endian issues.
16337 Changes in version 0.0.2pre26 - 2004-03-14
16339 - If a stream times out after 15s without a connected cell, don't
16340 try that circuit again: try a new one.
16341 - Retry streams at most 4 times. Then give up.
16342 - When a dirserver gets a descriptor from an unknown router, it
16343 logs its fingerprint (so the dirserver operator can choose to
16344 accept it even without mail from the server operator).
16345 - Inform unapproved servers when we reject their descriptors.
16346 - Make tor build on Windows again. It works as a client, who knows
16348 - Clearer instructions in the torrc for how to set up a server.
16349 - Be more efficient about reading fd's when our global token bucket
16350 (used for rate limiting) becomes empty.
16352 - Stop asserting that computers always go forward in time. It's
16354 - When we sent a cell (e.g. destroy) and then marked an OR connection
16355 expired, we might close it before finishing a flush if the other
16356 side isn't reading right then.
16357 - Don't allow dirservers to start if they haven't defined
16358 RecommendedVersions
16359 - We were caching transient dns failures. Oops.
16360 - Prevent servers from publishing an internal IP as their address.
16361 - Address a strcat vulnerability in circuit.c
16364 Changes in version 0.0.2pre25 - 2004-03-04
16366 - Put the OR's IP in its router descriptor, not its fqdn. That way
16367 we'll stop being stalled by gethostbyname for nodes with flaky dns,
16370 - If the user typed in an address that didn't resolve, the server
16374 Changes in version 0.0.2pre24 - 2004-03-03
16376 - Fix an assertion failure in dns.c, where we were trying to dequeue
16377 a pending dns resolve even if it wasn't pending
16378 - Fix a spurious socks5 warning about still trying to write after the
16379 connection is finished.
16380 - Hold certain marked_for_close connections open until they're finished
16381 flushing, rather than losing bytes by closing them too early.
16382 - Correctly report the reason for ending a stream
16383 - Remove some duplicate calls to connection_mark_for_close
16384 - Put switch_id and start_daemon earlier in the boot sequence, so it
16385 will actually try to chdir() to options.DataDirectory
16386 - Make 'make test' exit(1) if a test fails; fix some unit tests
16387 - Make tor fail when you use a config option it doesn't know about,
16388 rather than warn and continue.
16389 - Make --version work
16390 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
16393 Changes in version 0.0.2pre23 - 2004-02-29
16395 - Print a statement when the first circ is finished, so the user
16396 knows it's working.
16397 - If a relay cell is unrecognized at the end of the circuit,
16398 send back a destroy. (So attacks to mutate cells are more
16400 - New config option 'excludenodes' to avoid certain nodes for circuits.
16401 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
16402 so you can collect coredumps there.
16404 - Fix a bug in tls flushing where sometimes data got wedged and
16405 didn't flush until more data got sent. Hopefully this bug was
16406 a big factor in the random delays we were seeing.
16407 - Make 'connected' cells include the resolved IP, so the client
16408 dns cache actually gets populated.
16409 - Disallow changing from ORPort=0 to ORPort>0 on hup.
16410 - When we time-out on a stream and detach from the circuit, send an
16411 end cell down it first.
16412 - Only warn about an unknown router (in exitnodes, entrynodes,
16413 excludenodes) after we've fetched a directory.
16416 Changes in version 0.0.2pre22 - 2004-02-26
16418 - Servers publish less revealing uname information in descriptors.
16419 - More memory tracking and assertions, to crash more usefully when
16421 - If the default torrc isn't there, just use some default defaults.
16422 Plus provide an internal dirservers file if they don't have one.
16423 - When the user tries to use Tor as an http proxy, give them an http
16424 501 failure explaining that we're a socks proxy.
16425 - Dump a new router.desc on hup, to help confused people who change
16426 their exit policies and then wonder why router.desc doesn't reflect
16428 - Clean up the generic tor.sh init script that we ship with.
16430 - If the exit stream is pending on the resolve, and a destroy arrives,
16431 then the stream wasn't getting removed from the pending list. I
16432 think this was the one causing recent server crashes.
16433 - Use a more robust poll on OSX 10.3, since their poll is flaky.
16434 - When it couldn't resolve any dirservers, it was useless from then on.
16435 Now it reloads the RouterFile (or default dirservers) if it has no
16437 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
16438 many users don't even *have* a /usr/local/sbin/.
16441 Changes in version 0.0.2pre21 - 2004-02-18
16443 - There's a ChangeLog file that actually reflects the changelog.
16444 - There's a 'torify' wrapper script, with an accompanying
16445 tor-tsocks.conf, that simplifies the process of using tsocks for
16446 tor. It even has a man page.
16447 - The tor binary gets installed to sbin rather than bin now.
16448 - Retry streams where the connected cell hasn't arrived in 15 seconds
16449 - Clean up exit policy handling -- get the default out of the torrc,
16450 so we can update it without forcing each server operator to fix
16452 - Allow imaps and pop3s in default exit policy
16454 - Prevent picking middleman nodes as the last node in the circuit
16457 Changes in version 0.0.2pre20 - 2004-01-30
16459 - We now have a deb package, and it's in debian unstable. Go to
16460 it, apt-getters. :)
16461 - I've split the TotalBandwidth option into BandwidthRate (how many
16462 bytes per second you want to allow, long-term) and
16463 BandwidthBurst (how many bytes you will allow at once before the cap
16464 kicks in). This better token bucket approach lets you, say, set
16465 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
16466 performance while not exceeding your monthly bandwidth quota.
16467 - Push out a tls record's worth of data once you've got it, rather
16468 than waiting until you've read everything waiting to be read. This
16469 may improve performance by pipelining better. We'll see.
16470 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
16471 from failed circuits (if they haven't been connected yet) and attach
16473 - Expire old streams that haven't managed to connect. Some day we'll
16474 have them reattach to new circuits instead.
16477 - Fix several memory leaks that were causing servers to become bloated
16479 - Fix a few very rare assert triggers. A few more remain.
16480 - Setuid to User _before_ complaining about running as root.
16483 Changes in version 0.0.2pre19 - 2004-01-07
16485 - Fix deadlock condition in dns farm. We were telling a child to die by
16486 closing the parent's file descriptor to him. But newer children were
16487 inheriting the open file descriptor from the parent, and since they
16488 weren't closing it, the socket never closed, so the child never read
16489 eof, so he never knew to exit. Similarly, dns workers were holding
16490 open other sockets, leading to all sorts of chaos.
16491 - New cleaner daemon() code for forking and backgrounding.
16492 - If you log to a file, it now prints an entry at the top of the
16493 logfile so you know it's working.
16494 - The onionskin challenge length was 30 bytes longer than necessary.
16495 - Started to patch up the spec so it's not quite so out of date.
16498 Changes in version 0.0.2pre18 - 2004-01-02
16500 - Fix endian issues with the 'integrity' field in the relay header.
16501 - Fix a potential bug where connections in state
16502 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
16505 Changes in version 0.0.2pre17 - 2003-12-30
16507 - Made --debuglogfile (or any second log file, actually) work.
16508 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
16509 adversary could force us into an infinite loop.
16512 - Each onionskin handshake now includes a hash of the computed key,
16513 to prove the server's identity and help perfect forward secrecy.
16514 - Changed cell size from 256 to 512 bytes (working toward compatibility
16516 - Changed cell length to 2 bytes, and moved it to the relay header.
16517 - Implemented end-to-end integrity checking for the payloads of
16519 - Separated streamid from 'recognized' (otherwise circuits will get
16520 messed up when we try to have streams exit from the middle). We
16521 use the integrity-checking to confirm that a cell is addressed to
16523 - Randomize the initial circid and streamid values, so an adversary who
16524 breaks into a node can't learn how many circuits or streams have
16528 Changes in version 0.0.2pre16 - 2003-12-14
16530 - Fixed a bug that made HUP trigger an assert
16531 - Fixed a bug where a circuit that immediately failed wasn't being
16532 counted as a failed circuit in counting retries.
16535 - Now we close the circuit when we get a truncated cell: otherwise we're
16536 open to an anonymity attack where a bad node in the path truncates
16537 the circuit and then we open streams at him.
16538 - Add port ranges to exit policies
16539 - Add a conservative default exit policy
16540 - Warn if you're running tor as root
16541 - on HUP, retry OR connections and close/rebind listeners
16542 - options.EntryNodes: try these nodes first when picking the first node
16543 - options.ExitNodes: if your best choices happen to include any of
16544 your preferred exit nodes, you choose among just those preferred
16546 - options.ExcludedNodes: nodes that are never picked in path building
16549 Changes in version 0.0.2pre15 - 2003-12-03
16550 o Robustness and bugfixes:
16551 - Sometimes clients would cache incorrect DNS resolves, which would
16552 really screw things up.
16553 - An OP that goes offline would slowly leak all its sockets and stop
16555 - A wide variety of bugfixes in exit node selection, exit policy
16556 handling, and processing pending streams when a new circuit is
16558 - Pick nodes for a path only from those the directory says are up
16559 - Choose randomly from all running dirservers, not always the first one
16560 - Increase allowed http header size for directory fetch.
16561 - Stop writing to stderr (if we're daemonized it will be closed).
16562 - Enable -g always, so cores will be more useful to me.
16563 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16566 - Wrote a man page. It lists commonly used options.
16569 - Change default loglevel to warn.
16570 - Make PidFile default to null rather than littering in your CWD.
16571 - OnionRouter config option is now obsolete. Instead it just checks
16573 - Moved to a single unified torrc file for both clients and servers.
16576 Changes in version 0.0.2pre14 - 2003-11-29
16577 o Robustness and bugfixes:
16578 - Force the admin to make the DataDirectory himself
16579 - to get ownership/permissions right
16580 - so clients no longer make a DataDirectory and then never use it
16581 - fix bug where a client who was offline for 45 minutes would never
16582 pull down a directory again
16583 - fix (or at least hide really well) the dns assert bug that was
16584 causing server crashes
16585 - warnings and improved robustness wrt clockskew for certs
16586 - use the native daemon(3) to daemonize, when available
16587 - exit if bind() fails
16588 - exit if neither socksport nor orport is defined
16589 - include our own tor_timegm (Win32 doesn't have its own)
16590 - bugfix for win32 with lots of connections
16591 - fix minor bias in PRNG
16592 - make dirserver more robust to corrupt cached directory
16595 - Wrote the design document (woo)
16597 o Circuit building and exit policies:
16598 - Circuits no longer try to use nodes that the directory has told them
16600 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
16601 bitcounts (18.0.0.0/8).
16602 - Make AP connections standby for a circuit if no suitable circuit
16603 exists, rather than failing
16604 - Circuits choose exit node based on addr/port, exit policies, and
16605 which AP connections are standing by
16606 - Bump min pathlen from 2 to 3
16607 - Relay end cells have a payload to describe why the stream ended.
16608 - If the stream failed because of exit policy, try again with a new
16610 - Clients have a dns cache to remember resolved addresses.
16611 - Notice more quickly when we have no working circuits
16614 - APPort is now called SocksPort
16615 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
16617 - RecommendedVersions is now a config variable rather than
16618 hardcoded (for dirservers)
16619 - Reloads config on HUP
16620 - Usage info on -h or --help
16621 - If you set User and Group config vars, it'll setu/gid to them.
16624 Changes in version 0.0.2pre13 - 2003-10-19
16625 o General stability:
16626 - SSL_write no longer fails when it returns WANTWRITE and the number
16627 of bytes in the buf has changed by the next SSL_write call.
16628 - Fix segfault fetching directory when network is down
16629 - Fix a variety of minor memory leaks
16630 - Dirservers reload the fingerprints file on HUP, so I don't have
16631 to take down the network when I approve a new router
16632 - Default server config file has explicit Address line to specify fqdn
16635 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
16636 - Make listener connections not ever alloc bufs
16638 o Autoconf improvements:
16639 - don't clobber an external CFLAGS in ./configure
16640 - Make install now works
16641 - create var/lib/tor on make install
16642 - autocreate a tor.sh initscript to help distribs
16643 - autocreate the torrc and sample-server-torrc with correct paths
16645 o Log files and Daemonizing now work:
16646 - If --DebugLogFile is specified, log to it at -l debug
16647 - If --LogFile is specified, use it instead of commandline
16648 - If --RunAsDaemon is set, tor forks and backgrounds on startup