1 Changes in version 0.2.8.1-alpha - 2016-02-0?
2 Tor 0.2.8.1-alpha is the first alpha release in its series. It
3 includes numerous small features and bugfixes against previous Tor
4 versions, and numerous small infrastructure improvements. The most
5 notable features are a set of improvements to the directory subsystem.
7 o Major features (security, Linux):
8 - When Tor starts as root on Linux and is told to switch user ID, it
9 can now retain the capability to bind to low ports. By default,
10 Tor will do this only when it's switching user ID and some low
11 ports have been configured. You can change this behavior with the
12 new option KeepBindCapabilities. Closes ticket 8195.
14 o Major features (directory system):
15 - When bootstrapping multiple consensus downloads at a time, use the
16 first one that starts downloading, and close the rest. This
17 reduces failures when authorities or fallback directories are slow
18 or down. Together with the code for feature 15775, this feature
19 should reduces failures due to fallback churn. Implements ticket
20 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
21 "mikeperry" and "teor".
22 - Include a trial list of default fallback directories, based on an
23 opt-in survey of suitable relays. Doing this should make clients
24 bootstrap more quickly and reliably, and reduce the load on the
25 directory authorities. Closes ticket 15775. Patch by "teor".
26 Candidates identified using an OnionOO script by "weasel", "teor",
27 "gsathya", and "karsten".
28 - Previously only relays that explicitly opened a directory port
29 (DirPort) accepted directory requests from clients. Now all
30 relays, with and without a DirPort, accept and serve tunneled
31 directory requests that they receive through their ORPort. You can
32 disable this behavior using the new DirCache option. Closes
36 - Update the V3 identity key for the dannenberg directory authority:
37 it was changed on 18 November 2015. Closes task 17906. Patch
40 o Minor features (security, clock):
41 - Warn when the system clock appears to move back in time (when the
42 state file was last written in the future). Tor doesn't know that
43 consensuses have expired if the clock is in the past. Patch by
44 "teor". Implements ticket 17188.
46 o Minor features (security, exit policies):
47 - ExitPolicyRejectPrivate now rejects more private addresses by
48 default. Specifically, it now rejects the relay's outbound bind
49 addresses (if configured), and the relay's configured port
50 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
51 0.2.0.11-alpha. Patch by "teor".
53 o Minor features (security, memory erasure):
54 - Set the unused entries in a smartlist to NULL. This helped catch
55 a (harmless) bug, and shouldn't affect performance too much.
56 Implements ticket 17026.
57 - Use SecureMemoryWipe() function to securely clean memory on
58 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
59 Implements feature 17986.
60 - Use explicit_bzero or memset_s when present. Previously, we'd use
61 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
62 from <logan@hackers.mu> and <selven@hackers.mu>.
63 - Make memwipe() do nothing when passed a NULL pointer or buffer of
64 zero size. Check size argument to memwipe() for underflow. Fixes
65 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
68 o Minor features (security, RNG):
69 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
70 positively are not allowed to fail. Previously we depended on
71 internal details of OpenSSL's behavior. Closes ticket 17686.
72 - Never use the system entropy output directly for anything besides
73 seeding the PRNG. When we want to generate important keys, instead
74 of using system entropy directly, we now hash it with the PRNG
75 stream. This may help resist certain attacks based on broken OS
76 entropy implementations. Closes part of ticket 17694.
77 - Use modern system calls (like getentropy() or getrandom()) to
78 generate strong entropy on platforms that have them. Closes
81 o Minor features (accounting):
82 - Added two modes to the AccountingRule option: One for limiting
83 only the number of bytes sent ("AccountingRule out"), and one for
84 limiting only the number of bytes received ("AccountingRule in").
85 Closes ticket 15989; patch from "unixninja92".
87 o Minor features (build):
88 - Since our build process now uses "make distcheck", we no longer
89 force "make dist" to depend on "make check". Closes ticket 17893;
90 patch from "cypherpunks."
91 - Tor now builds successfully with the recent OpenSSL 1.1
92 development branch, and with the latest LibreSSL. Closes tickets
93 17549, 17921, and 17984.
95 o Minor features (controller):
96 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
97 tickets 16774 and 17817. Patch by George Tankersley.
98 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
99 service descriptor from a service's local hidden service
100 descriptor cache. Closes ticket 14846.
101 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
102 controllers can examine the the reject rules added by
103 ExitPolicyRejectPrivate. This makes it easier for stem to display
106 o Minor features (crypto):
107 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
109 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
110 - When allocating a digest state object, allocate no more space than
111 we actually need. Previously, we would allocate as much space as
112 the state for the largest algorithm would need. This change saves
113 up to 672 bytes per circuit. Closes ticket 17796.
114 - Improve performance when hashing non-multiple of 8 sized buffers,
115 based on Andrew Moon's public domain SipHash-2-4 implementation.
116 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
118 o Minor features (directory downloads):
119 - Wait for busy authorities and fallback directories to become non-
120 busy when bootstrapping. (A similar change was made in 6c443e987d
121 for directory caches chosen from the consensus.) Closes ticket
122 17864; patch by "teor".
123 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
124 directory mirrors. The default is 1; set it to 0 to disable
125 fallbacks. Implements ticket 17576. Patch by "teor".
127 o Minor features (geoip):
128 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
131 o Minor features (IPv6):
132 - Add an argument 'ipv6=address:orport' to the DirAuthority and
133 FallbackDir torrc options, to specify an IPv6 address for an
134 authority or fallback directory. Add hard-coded ipv6 addresses for
135 directory authorities that have them. Closes ticket 17327; patch
136 from Nick Mathewson and "teor".
137 - Add address policy assume_action support for IPv6 addresses.
138 - Limit IPv6 mask bits to 128.
139 - Warn when comparing against an AF_UNSPEC address in a policy, it's
140 almost always a bug. Closes ticket 17863; patch by "teor".
141 - Allow users to configure directory authorities and fallback
142 directory servers with IPv6 addresses and ORPorts. Resolves
144 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
145 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
146 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
147 17638; bugfix on 0.0.2pre8. Patch by "teor".
149 o Minor features (logging):
150 - When logging to syslog, allow a tag to be added to the syslog
151 identity (the string prepended to every log message). The tag can
152 be configured with SyslogIdentityTag and defaults to none. Setting
153 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
156 o Minor features (portability):
157 - Use timingsafe_memcmp() where available. Closes ticket 17944;
158 patch from <logan@hackers.mu>.
160 o Minor features (relay, address discovery):
161 - Add a family argument to get_interface_addresses_raw() and
162 subfunctions to make network interface address interogation more
163 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
164 types of interfaces from the operating system. Resolves
166 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
167 fails to enumerate interface addresses using the platform-specific
168 API, have it rely on the UDP socket fallback technique to try and
169 find out what IP addresses (both IPv4 and IPv6) our machine has.
170 Resolves ticket 17951.
172 o Minor features (replay cache):
173 - The replay cache now uses SHA256 instead of SHA1. Implements
174 feature 8961. Patch by "teor", issue reported by "rransom".
176 o Minor features (unix file permissions):
177 - Defer creation of Unix sockets until after setuid. This avoids
178 needing CAP_CHOWN and CAP_FOWNER when using systemd's
179 CapabilityBoundingSet, or chown and fowner when using SELinux.
180 Implements part of ticket 17562. Patch from Jamie Nguyen.
181 - If any directory created by Tor is marked as group readable, the
182 filesystem group is allowed to be either the default GID or the
183 root user. Allowing root to read the DataDirectory prevents the
184 need for CAP_READ_SEARCH when using systemd's
185 CapabilityBoundingSet, or dac_read_search when using SELinux.
186 Implements part of ticket 17562. Patch from Jamie Nguyen.
187 - Introduce a new DataDirectoryGroupReadable option. If it is set to
188 1, the DataDirectory will be made readable by the default GID.
189 Implements part of ticket 17562. Patch from Jamie Nguyen.
191 o Minor bugfixes (accounting):
192 - The max bandwidth when using 'AccountRule sum' is now correctly
193 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
196 o Minor bugfixes (code correctness):
197 - When closing an entry connection, generate a warning if we should
198 have sent an end cell for it but we haven't. Fixes bug 17876;
199 bugfix on 0.2.3.2-alpha.
200 - Assert that allocated memory held by the reputation code is freed
201 according to its internal counters. Fixes bug 17753; bugfix
202 on tor-0.1.1.1-alpha.
203 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
206 o Minor bugfixes (compilation):
207 - Mark all object files that include micro-revision.i as depending
208 on it, so as to make parallel builds more reliable. Fixes bug
209 17826; bugfix on 0.2.5.1-alpha.
210 - Don't try to use the pthread_condattr_setclock() function unless
211 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
212 17819; bugfix on 0.2.6.3-alpha.
213 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
214 on tor-0.2.5.2-alpha.
215 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
216 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
217 - Fix search for libevent libraries on OpenBSD (and other systems
218 that install libevent 1 and libevent 2 in parallel). Fixes bug
219 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
220 - Isolate environment variables meant for tests from the rest of the
221 build system. Fixes bug 17818; bugfix on tor-0.2.7.3-rc.
222 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
224 - Remove config.log only from make distclean, not from make clean.
225 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
227 o Minor bugfixes (crypto):
228 - Check the return value of HMAC() and assert on failure. Fixes bug
229 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
231 o Minor bugfixes (fallback directories):
232 - Mark fallbacks as "too busy" when they return a 503 response,
233 rather than just marking authorities. Fixes bug 17572; bugfix on
234 0.2.4.7-alpha. Patch by "teor".
236 o Minor bugfixes (IPv6):
237 - Update the limits in max_dl_per_request for IPv6 address length.
238 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
240 o Minor bugfixes (linux seccomp2 sandbox):
241 - Fix a crash when using offline master ed25519 keys with the Linux
242 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-alpha.
244 o Minor bugfixes (logging):
245 - In log messages that include a function name, use __FUNCTION__
246 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
247 with clang __PRETTY_FUNCTION__ has extra information we don't
248 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
250 - Remove needless quotes from a log message about unparseable
251 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
253 o Minor bugfixes (portability):
254 - Remove an #endif from configure.ac so that we correctly detect the
255 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
258 o Minor bugfixes (relays):
259 - Check that both the ORPort and DirPort (if present) are reachable
260 before publishing a relay descriptor. Otherwise, relays publish a
261 descriptor with DirPort 0 when the DirPort reachability test takes
262 longer than the ORPort reachability test. Fixes bug 18050; bugfix
263 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
265 o Minor bugfixes (relays, hidden services):
266 - Refuse connection requests to private OR addresses unless
267 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
268 then refuse to send any cells to a private address. Fixes bugs
269 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
271 o Minor bugfixes (safe logging):
272 - When logging a malformed hostname received through socks4, scrub
273 it if SafeLogging says we should. Fixes bug 17419; bugfix
276 o Minor bugfixes (statistics code):
277 - Consistently check for overflow in round_*_to_next_multiple_of
278 functions, and add unit tests with additional and maximal values.
279 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
280 - Handle edge cases in the laplace functions: avoid division by
281 zero, avoid taking the log of zero, and silence clang type
282 conversion warnings using round and trunc. Add unit tests for edge
283 cases with maximal values. Fixes part of bug 13192; bugfix
286 o Minor bugfixes (testing):
287 - The test for log_heartbeat was incorrectly failing in timezones
288 with non-integer offsets. Instead of comparing the end of the time
289 string against a constant, compare it to the output of
290 format_local_iso_time when given the correct input. Fixes bug
291 18039; bugfix on 0.2.5.4-alpha.
292 - Make unit tests pass on IPv6-only systems, and systems without
293 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
294 bugfix on 0.2.7.3-rc. Patch by "teor".
295 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
297 - Check the full results of SHA256 and SHA512 digests in the unit
298 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
300 o Code simplification and refactoring:
301 - Move logging of redundant policy entries in
302 policies_parse_exit_policy_internal into its own function. Closes
303 ticket 17608; patch from "juce".
304 - Extract the more complicated parts of circuit_mark_for_close()
305 into a new function that we run periodically before circuits are
306 freed. This change removes more than half of the functions
307 currently in the "blob". Closes ticket 17218.
308 - Clean up a little duplicated code in
309 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
311 - Decouple the list of streams waiting to be attached to circuits
312 from the overall connection list. This change makes it possible to
313 attach streams quickly while simplifying Tor's callgraph and
314 avoiding O(N) scans of the entire connection list. Closes
316 - When a direct directory request fails immediately on launch,
317 instead of relaunching that request from inside the code that
318 launches it, instead mark the connection for teardown. This change
319 simplifies Tor's callback and prevents the directory-request
320 launching code from invoking itself recursively. Closes
322 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
323 use them. Closes ticket 17926.
326 - Add a description of the correct use of the '--keygen' command-
327 line option. Closes ticket 17583; based on text by 's7r'.
328 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
329 - Explain actual minima for BandwidthRate. Closes ticket 16382.
330 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
331 - Mention torspec URL in the manpage and point the reader to it
332 whenever we mention a document that belongs in torspce. Fixes
336 - Remove client-side support for connecting to Tor servers running
337 versions of Tor before 0.2.3.6-alpha. These servers didn't support
338 the v3 TLS handshake protocol, and are no longer allowed on the
339 Tor network. Implements the client side of ticket 11150. Based on
340 patches by Tom van der Woerdt.
343 - Add unit tests to check for common RNG failure modes, such as
344 returning all zeroes, identical values, or incrementing values
345 (OpenSSL's rand_predictable feature). Patch by "teor".
346 - Log more information when the backtrace tests fail. Closes ticket
347 17892. Patch from "cypherpunks."
348 - Always test both ed25519 backends, so that we can be sure that our
349 batch-open replacement code works. Part of ticket 16794.
350 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
351 portion of ticket 16831.
352 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
353 util_format.c, directory.c, and options_validate.c. Closes tickets
354 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
356 - Unit tests for directory_handle_command_get. Closes ticket 17004.
357 Patch from Reinaldo de Souza Jr.
360 Changes in version 0.2.7.6 - 2015-12-10
361 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
362 well as a minor bug in hidden service reliability.
364 o Major bugfixes (guard selection):
365 - Actually look at the Guard flag when selecting a new directory
366 guard. When we implemented the directory guard design, we
367 accidentally started treating all relays as if they have the Guard
368 flag during guard selection, leading to weaker anonymity and worse
369 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
372 o Minor features (geoip):
373 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
376 o Minor bugfixes (compilation):
377 - When checking for net/pfvar.h, include netinet/in.h if possible.
378 This fixes transparent proxy detection on OpenBSD. Fixes bug
379 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
380 - Fix a compilation warning with Clang 3.6: Do not check the
381 presence of an address which can never be NULL. Fixes bug 17781.
383 o Minor bugfixes (correctness):
384 - When displaying an IPv6 exit policy, include the mask bits
385 correctly even when the number is greater than 31. Fixes bug
386 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
387 - The wrong list was used when looking up expired intro points in a
388 rend service object, causing what we think could be reachability
389 issues for hidden services, and triggering a BUG log. Fixes bug
390 16702; bugfix on 0.2.7.2-alpha.
391 - Fix undefined behavior in the tor_cert_checksig function. Fixes
392 bug 17722; bugfix on 0.2.7.2-alpha.
395 Changes in version 0.2.7.5 - 2015-11-20
396 The Tor 0.2.7 release series is dedicated to the memory of Tor user
397 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
398 tirelessly to advocate human rights regardless of national borders,
399 and oppose the encroachments of mass surveillance. He opposed national
400 exceptionalism, he brought clarity to legal and policy debates, he
401 understood and predicted the impact of mass surveillance on the world,
402 and he laid the groundwork for resisting it. While serving on the Tor
403 Project's board of directors, he brought us his uncompromising focus
404 on technical excellence in the service of humankind. Caspar was an
405 inimitable force for good and a wonderful friend. He was kind,
406 humorous, generous, gallant, and believed we should protect one
407 another without exception. We honor him here for his ideals, his
408 efforts, and his accomplishments. Please honor his memory with works
409 that would make him proud.
411 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
413 The 0.2.7 series adds a more secure identity key type for relays,
414 improves cryptography performance, resolves several longstanding
415 hidden-service performance issues, improves controller support for
416 hidden services, and includes small bugfixes and performance
417 improvements throughout the program. This release series also includes
418 more tests than before, and significant simplifications to which parts
419 of Tor invoke which others.
421 (This release contains no code changes since 0.2.7.4-rc.)
424 Changes in version 0.2.7.4-rc - 2015-10-21
425 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
426 fixes some important memory leaks, and a scary-looking (but mostly
427 harmless in practice) invalid-read bug. It also has a few small
428 bugfixes, notably fixes for compilation and portability on different
429 platforms. If no further significant bounds are found, the next
430 release will the the official stable release.
432 o Major bugfixes (security, correctness):
433 - Fix an error that could cause us to read 4 bytes before the
434 beginning of an openssl string. This bug could be used to cause
435 Tor to crash on systems with unusual malloc implementations, or
436 systems with unusual hardening installed. Fixes bug 17404; bugfix
439 o Major bugfixes (correctness):
440 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
441 bug 17401; bugfix on 0.2.7.3-rc.
443 o Major bugfixes (memory leaks):
444 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
445 17398; bugfix on 0.2.6.1-alpha.
446 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
447 17402; bugfix on 0.2.7.3-rc.
448 - Fix a memory leak when reading an expired signing key from disk.
449 Fixes bug 17403; bugfix on 0.2.7.2-rc.
451 o Minor features (geoIP):
452 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
455 o Minor bugfixes (compilation):
456 - Repair compilation with the most recent (unreleased, alpha)
457 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
458 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
459 17251; bugfix on 0.2.7.2-alpha.
460 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
461 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
463 o Minor bugfixes (portability):
464 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
465 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
468 o Minor bugfixes (sandbox):
469 - Add the "hidserv-stats" filename to our sandbox filter for the
470 HiddenServiceStatistics option to work properly. Fixes bug 17354;
471 bugfix on tor-0.2.6.2-alpha. Patch from David Goulet.
473 o Minor bugfixes (testing):
474 - Add unit tests for get_interface_address* failure cases. Fixes bug
475 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
476 - Fix breakage when running 'make check' with BSD make. Fixes bug
477 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
478 - Make the get_ifaddrs_* unit tests more tolerant of different
479 network configurations. (Don't assume every test box has an IPv4
480 address, and don't assume every test box has a non-localhost
481 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
482 - Skip backtrace tests when backtrace support is not compiled in.
483 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
487 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
488 - Note that HiddenServicePorts can take a unix domain socket. Closes
492 Changes in version 0.2.7.3-rc - 2015-09-25
493 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
494 contains numerous usability fixes for Ed25519 keys, safeguards against
495 several misconfiguration problems, significant simplifications to
496 Tor's callgraph, and numerous bugfixes and small features.
498 This is the most tested release of Tor to date. The unit tests cover
499 39.40% of the code, and the integration tests (accessible with "make
500 test-full-online", requiring stem and chutney and a network
501 connection) raise the coverage to 64.49%.
503 o Major features (security, hidden services):
504 - Hidden services, if using the EntryNodes option, are required to
505 use more than one EntryNode, in order to avoid a guard discovery
506 attack. (This would only affect people who had configured hidden
507 services and manually specified the EntryNodes option with a
508 single entry-node. The impact was that it would be easy to
509 remotely identify the guard node used by such a hidden service.
510 See ticket for more information.) Fixes ticket 14917.
512 o Major features (Ed25519 keys, keypinning):
513 - The key-pinning option on directory authorities is now advisory-
514 only by default. In a future version, or when the AuthDirPinKeys
515 option is set, pins are enforced again. Disabling key-pinning
516 seemed like a good idea so that we can survive the fallout of any
517 usability problems associated with Ed25519 keys. Closes
520 o Major features (Ed25519 performance):
521 - Improve the speed of Ed25519 operations and Curve25519 keypair
522 generation when built targeting 32 bit x86 platforms with SSE2
523 available. Implements ticket 16535.
524 - Improve the runtime speed of Ed25519 signature verification by
525 using Ed25519-donna's batch verification support. Implements
528 o Major features (performance testing):
529 - The test-network.sh script now supports performance testing.
530 Requires corresponding chutney performance testing changes. Patch
531 by "teor". Closes ticket 14175.
533 o Major features (relay, Ed25519):
534 - Significant usability improvements for Ed25519 key management. Log
535 messages are better, and the code can recover from far more
536 failure conditions. Thanks to "s7r" for reporting and diagnosing
538 - Add a new OfflineMasterKey option to tell Tor never to try loading
539 or generating a secret Ed25519 identity key. You can use this in
540 combination with tor --keygen to manage offline and/or encrypted
541 Ed25519 keys. Implements ticket 16944.
542 - Add a --newpass option to allow changing or removing the
543 passphrase of an encrypted key with tor --keygen. Implements part
545 - On receiving a HUP signal, check to see whether the Ed25519
546 signing key has changed, and reload it if so. Closes ticket 16790.
548 o Major bugfixes (relay, Ed25519):
549 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
550 0.2.7.2-alpha. Reported by "s7r".
551 - Improve handling of expired signing keys with offline master keys.
552 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
554 o Minor features (client-side privacy):
555 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
556 lifespan when IsolateSOCKSAuth and streams with SOCKS
557 authentication are attached to the circuit. This allows
558 applications like TorBrowser to manage circuit lifetime on their
559 own. Implements feature 15482.
560 - When logging malformed hostnames from SOCKS5 requests, respect
561 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
563 o Minor features (compilation):
564 - Give a warning as early as possible when trying to build with an
565 unsupported OpenSSL version. Closes ticket 16901.
566 - Fail during configure if we're trying to build against an OpenSSL
567 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
568 which started requiring ECC.
570 o Minor features (geoip):
571 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
574 o Minor features (hidden services):
575 - Relays need to have the Fast flag to get the HSDir flag. As this
576 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
577 drop. This change should make some attacks against the hidden
578 service directory system harder. Fixes ticket 15963.
579 - Turn on hidden service statistics collection by setting the torrc
580 option HiddenServiceStatistics to "1" by default. (This keeps
581 track only of the fraction of traffic used by hidden services, and
582 the total number of hidden services in existence.) Closes
584 - Client now uses an introduction point failure cache to know when
585 to fetch or keep a descriptor in their cache. Previously, failures
586 were recorded implicitly, but not explicitly remembered. Closes
589 o Minor features (testing, authorities, documentation):
590 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
591 explicitly manage consensus flags in testing networks. Patch by
592 "robgjansen", modified by "teor". Implements part of ticket 14882.
594 o Minor bugfixes (security, exit policies):
595 - ExitPolicyRejectPrivate now also rejects the relay's published
596 IPv6 address (if any), and any publicly routable IPv4 or IPv6
597 addresses on any local interfaces. ticket 17027. Patch by "teor".
598 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
600 o Minor bug fixes (torrc exit policies):
601 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
602 produce IPv6 wildcard addresses. Previously they would produce
603 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
604 of bug 16069; bugfix on 0.2.4.7-alpha.
605 - When parsing torrc ExitPolicies, we now warn for a number of cases
606 where the user's intent is likely to differ from Tor's actual
607 behavior. These include: using an IPv4 address with an accept6 or
608 reject6 line; using "private" on an accept6 or reject6 line; and
609 including any ExitPolicy lines after accept *:* or reject *:*.
610 Related to ticket 16069.
611 - When parsing torrc ExitPolicies, we now issue an info-level
612 message when expanding an "accept/reject *" line to include both
613 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
614 - In each instance above, usage advice is provided to avoid the
615 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
616 16069; bugfix on 0.2.4.7-alpha.
618 o Minor bugfixes (authority):
619 - Don't assign "HSDir" to a router if it isn't Valid and Running.
620 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
621 - Downgrade log messages about Ed25519 key issues if they are in old
622 cached router descriptors. Fixes part of bug 16286; bugfix
624 - When we find an Ed25519 key issue in a cached descriptor, stop
625 saying the descriptor was just "uploaded". Fixes another part of
626 bug 16286; bugfix on 0.2.7.2-alpha.
628 o Minor bugfixes (control port):
629 - Repair a warning and a spurious result when getting the maximum
630 number of file descriptors from the controller. Fixes bug 16697;
631 bugfix on 0.2.7.2-alpha.
633 o Minor bugfixes (correctness):
634 - When calling channel_free_list(), avoid calling smartlist_remove()
635 while inside a FOREACH loop. This partially reverts commit
636 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
637 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
639 o Minor bugfixes (documentation):
640 - Advise users on how to configure separate IPv4 and IPv6 exit
641 policies in the manpage and sample torrcs. Related to ticket 16069.
642 - Fix the usage message of tor-resolve(1) so that it no longer lists
643 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
644 - Fix an error in the manual page and comments for
645 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
646 required "ORPort connectivity". While this is true, it is in no
647 way unique to the HSDir flag. Of all the flags, only HSDirs need a
648 DirPort configured in order for the authorities to assign that
649 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
652 o Minor bugfixes (Ed25519):
653 - Fix a memory leak when reading router descriptors with expired
654 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
656 o Minor bugfixes (linux seccomp2 sandbox):
657 - Allow bridge authorities to run correctly under the seccomp2
658 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
659 - Allow routers with ed25519 keys to run correctly under the
660 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
662 o Minor bugfixes (open file limit):
663 - Fix set_max_file_descriptors() to set by default the max open file
664 limit to the current limit when setrlimit() fails. Fixes bug
665 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
667 o Minor bugfixes (portability):
668 - Try harder to normalize the exit status of the Tor process to the
669 standard-provided range. Fixes bug 16975; bugfix on every version
671 - Check correctly for Windows socket errors in the workqueue
672 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
673 - Fix the behavior of crypto_rand_time_range() when told to consider
674 times before 1970. (These times were possible when running in a
675 simulated network environment where time()'s output starts at
676 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
677 - Restore correct operation of TLS client-cipher detection on
678 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
680 o Minor bugfixes (relay):
681 - Ensure that worker threads actually exit when a fatal error or
682 shutdown is indicated. This fix doesn't currently affect the
683 behavior of Tor, because Tor workers never indicates fatal error
684 or shutdown except in the unit tests. Fixes bug 16868; bugfix
686 - Unblock threads before releasing the work queue mutex to ensure
687 predictable scheduling behavior. Fixes bug 16644; bugfix
690 o Code simplification and refactoring:
691 - Change the function that's called when we need to retry all
692 downloads so that it only reschedules the downloads to happen
693 immediately, rather than launching them all at once itself. This
694 further simplifies Tor's callgraph.
695 - Move some format-parsing functions out of crypto.c and
696 crypto_curve25519.c into crypto_format.c and/or util_format.c.
697 - Move the client-only parts of init_keys() into a separate
698 function. Closes ticket 16763.
699 - Simplify the microdesc_free() implementation so that it no longer
700 appears (to code analysis tools) to potentially invoke a huge
701 suite of other microdesc functions.
702 - Simply the control graph further by deferring the inner body of
703 directory_all_unreachable() into a callback. Closes ticket 16762.
704 - Treat the loss of an owning controller as equivalent to a SIGTERM
705 signal. This removes a tiny amount of duplicated code, and
706 simplifies our callgraph. Closes ticket 16788.
707 - When generating an event to send to the controller, we no longer
708 put the event over the network immediately. Instead, we queue
709 these events, and use a Libevent callback to deliver them. This
710 change simplifies Tor's callgraph by reducing the number of
711 functions from which all other Tor functions are reachable. Closes
713 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
714 that try to scan or compile every file on Unix won't decide that
716 - Remove the unused "nulterminate" argument from buf_pullup().
719 - Recommend a 40 GB example AccountingMax in torrc.sample rather
720 than a 4 GB max. Closes ticket 16742.
721 - Include the TUNING document in our source tarball. It is referred
722 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
726 - The internal pure-C tor-fw-helper tool is now removed from the Tor
727 distribution, in favor of the pure-Go clone available from
728 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
729 used by the C tor-fw-helper are not, in our opinion, very
730 confidence- inspiring in their secure-programming techniques.
732 - Remove the code that would try to aggressively flush controller
733 connections while writing to them. This code was introduced in
734 0.1.2.7-alpha, in order to keep output buffers from exceeding
735 their limits. But there is no longer a maximum output buffer size,
736 and flushing data in this way caused some undesirable recursions
737 in our call graph. Closes ticket 16480.
740 - Make "bridges+hs" the default test network. This tests almost all
741 tor functionality during make test-network, while allowing tests
742 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
743 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
744 (chutney). Patches by "teor".
745 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
746 by-side in the same parent directory. Closes ticket 16903. Patch
748 - Use environment variables rather than autoconf substitutions to
749 send variables from the build system to the test scripts. This
750 change should be easier to maintain, and cause 'make distcheck' to
751 work better than before. Fixes bug 17148.
752 - Add a new set of callgraph analysis scripts that use clang to
753 produce a list of which Tor functions are reachable from which
754 other Tor functions. We're planning to use these to help simplify
755 our code structure by identifying illogical dependencies.
756 - Add new 'test-full' and 'test-full-online' targets to run all
757 tests, including integration tests with stem and chutney.
758 - Make the test-workqueue test work on Windows by initializing the
759 network before we begin.
760 - New make target (make test-network-all) to run multiple applicable
761 chutney test cases. Patch from Teor; closes 16953.
762 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
763 functions in dns.c. Implements a portion of ticket 16831.
764 - When building Tor with testing coverage enabled, run Chutney tests
765 (if any) using the 'tor-cov' coverage binary.
766 - When running test-network or test-stem, check for the absence of
767 stem/chutney before doing any build operations.
770 Changes in version 0.2.7.2-alpha - 2015-07-27
771 This, the second alpha in the Tor 0.2.7 series, has a number of new
772 features, including a way to manually pick the number of introduction
773 points for hidden services, and the much stronger Ed25519 signing key
774 algorithm for regular Tor relays (including support for encrypted
775 offline identity keys in the new algorithm).
777 Support for Ed25519 on relays is currently limited to signing router
778 descriptors; later alphas in this series will extend Ed25519 key
779 support to more parts of the Tor protocol.
781 o Major features (Ed25519 identity keys, Proposal 220):
782 - All relays now maintain a stronger identity key, using the Ed25519
783 elliptic curve signature format. This master key is designed so
784 that it can be kept offline. Relays also generate an online
785 signing key, and a set of other Ed25519 keys and certificates.
786 These are all automatically regenerated and rotated as needed.
787 Implements part of ticket 12498.
788 - Directory authorities now vote on Ed25519 identity keys along with
789 RSA1024 keys. Implements part of ticket 12498.
790 - Directory authorities track which Ed25519 identity keys have been
791 used with which RSA1024 identity keys, and do not allow them to
792 vary freely. Implements part of ticket 12498.
793 - Microdescriptors now include Ed25519 identity keys. Implements
794 part of ticket 12498.
795 - Add support for offline encrypted Ed25519 master keys. To use this
796 feature on your tor relay, run "tor --keygen" to make a new master
797 key (or to make a new signing key if you already have a master
798 key). Closes ticket 13642.
800 o Major features (Hidden services):
801 - Add the torrc option HiddenServiceNumIntroductionPoints, to
802 specify a fixed number of introduction points. Its maximum value
803 is 10 and default is 3. Using this option can increase a hidden
804 service's reliability under load, at the cost of making it more
805 visible that the hidden service is facing extra load. Closes
807 - Remove the adaptive algorithm for choosing the number of
808 introduction points, which used to change the number of
809 introduction points (poorly) depending on the number of
810 connections the HS sees. Closes ticket 4862.
812 o Major features (onion key cross-certification):
813 - Relay descriptors now include signatures of their own identity
814 keys, made using the TAP and ntor onion keys. These signatures
815 allow relays to prove ownership of their own onion keys. Because
816 of this change, microdescriptors will no longer need to include
817 RSA identity keys. Implements proposal 228; closes ticket 12499.
819 o Major features (performance):
820 - Improve the runtime speed of Ed25519 operations by using the
821 public-domain Ed25519-donna by Andrew M. ("floodyberry").
822 Implements ticket 16467.
823 - Improve the runtime speed of the ntor handshake by using an
824 optimized curve25519 basepoint scalarmult implementation from the
825 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
826 ideas by Adam Langley. Implements ticket 9663.
828 o Major bugfixes (client-side privacy, also in 0.2.6.9):
829 - Properly separate out each SOCKSPort when applying stream
830 isolation. The error occurred because each port's session group
831 was being overwritten by a default value when the listener
832 connection was initialized. Fixes bug 16247; bugfix on
833 0.2.6.3-alpha. Patch by "jojelino".
835 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
836 - Stop refusing to store updated hidden service descriptors on a
837 client. This reverts commit 9407040c59218 (which indeed fixed bug
838 14219, but introduced a major hidden service reachability
839 regression detailed in bug 16381). This is a temporary fix since
840 we can live with the minor issue in bug 14219 (it just results in
841 some load on the network) but the regression of 16381 is too much
842 of a setback. First-round fix for bug 16381; bugfix
845 o Major bugfixes (hidden services):
846 - When cannibalizing a circuit for an introduction point, always
847 extend to the chosen exit node (creating a 4 hop circuit).
848 Previously Tor would use the current circuit exit node, which
849 changed the original choice of introduction point, and could cause
850 the hidden service to skip excluded introduction points or
851 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
854 o Major bugfixes (open file limit):
855 - The open file limit wasn't checked before calling
856 tor_accept_socket_nonblocking(), which would make Tor exceed the
857 limit. Now, before opening a new socket, Tor validates the open
858 file limit just before, and if the max has been reached, return an
859 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
861 o Major bugfixes (stability, also in 0.2.6.10):
862 - Stop crashing with an assertion failure when parsing certain kinds
863 of malformed or truncated microdescriptors. Fixes bug 16400;
864 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
865 by "cypherpunks_backup".
866 - Stop random client-side assertion failures that could occur when
867 connecting to a busy hidden service, or connecting to a hidden
868 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
871 o Minor features (directory authorities, security, also in 0.2.6.9):
872 - The HSDir flag given by authorities now requires the Stable flag.
873 For the current network, this results in going from 2887 to 2806
874 HSDirs. Also, it makes it harder for an attacker to launch a sybil
875 attack by raising the effort for a relay to become Stable to
876 require at the very least 7 days, while maintaining the 96 hours
877 uptime requirement for HSDir. Implements ticket 8243.
879 o Minor features (client):
880 - Relax the validation of hostnames in SOCKS5 requests, allowing the
881 character '_' to appear, in order to cope with domains observed in
882 the wild that are serving non-RFC compliant records. Resolves
884 - Relax the validation done to hostnames in SOCKS5 requests, and
885 allow a single trailing '.' to cope with clients that pass FQDNs
886 using that syntax to explicitly indicate that the domain name is
887 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
888 - Add GroupWritable and WorldWritable options to unix-socket based
889 SocksPort and ControlPort options. These options apply to a single
890 socket, and override {Control,Socks}SocketsGroupWritable. Closes
893 o Minor features (control protocol):
894 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
895 the control protocol. Resolves ticket 15358.
897 o Minor features (directory authorities):
898 - Directory authorities no longer vote against the "Fast", "Stable",
899 and "HSDir" flags just because they were going to vote against
900 "Running": if the consensus turns out to be that the router was
901 running, then the authority's vote should count. Patch from Peter
902 Retzlaff; closes issue 8712.
904 o Minor features (geoip, also in 0.2.6.10):
905 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
906 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
908 o Minor features (hidden services):
909 - Add the new options "HiddenServiceMaxStreams" and
910 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
911 limit the maximum number of simultaneous streams per circuit, and
912 optionally tear down the circuit when the limit is exceeded. Part
915 o Minor features (portability):
916 - Use C99 variadic macros when the compiler is not GCC. This avoids
917 failing compilations on MSVC, and fixes a log-file-based race
918 condition in our old workarounds. Original patch from Gisle Vanem.
920 o Minor bugfixes (compilation, also in 0.2.6.9):
921 - Build with --enable-systemd correctly when libsystemd is
922 installed, but systemd is not. Fixes bug 16164; bugfix on
923 0.2.6.3-alpha. Patch from Peter Palfrader.
925 o Minor bugfixes (controller):
926 - Add the descriptor ID in each HS_DESC control event. It was
927 missing, but specified in control-spec.txt. Fixes bug 15881;
928 bugfix on 0.2.5.2-alpha.
930 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
931 - Check for failures from crypto_early_init, and refuse to continue.
932 A previous typo meant that we could keep going with an
933 uninitialized crypto library, and would have OpenSSL initialize
934 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
935 when implementing ticket 4900. Patch by "teor".
937 o Minor bugfixes (hidden services):
938 - Fix a crash when reloading configuration while at least one
939 configured and one ephemeral hidden service exists. Fixes bug
940 16060; bugfix on 0.2.7.1-alpha.
941 - Avoid crashing with a double-free bug when we create an ephemeral
942 hidden service but adding it fails for some reason. Fixes bug
943 16228; bugfix on 0.2.7.1-alpha.
945 o Minor bugfixes (Linux seccomp2 sandbox):
946 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
947 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
949 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
950 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
951 these when eventfd2() support is missing. Fixes bug 16363; bugfix
952 on 0.2.6.3-alpha. Patch from "teor".
954 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
955 - Fix sandboxing to work when running as a relay, by allowing the
956 renaming of secret_id_key, and allowing the eventfd2 and futex
957 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
959 - Allow systemd connections to work with the Linux seccomp2 sandbox
960 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
963 o Minor bugfixes (relay):
964 - Fix a rarely-encountered memory leak when failing to initialize
965 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
968 o Minor bugfixes (systemd):
969 - Fix an accidental formatting error that broke the systemd
970 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
971 - Tor's systemd unit file no longer contains extraneous spaces.
972 These spaces would sometimes confuse tools like deb-systemd-
973 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
975 o Minor bugfixes (tests):
976 - Use the configured Python executable when running test-stem-full.
977 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
979 o Minor bugfixes (tests, also in 0.2.6.9):
980 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
981 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
983 o Minor bugfixes (threads, comments):
984 - Always initialize return value in compute_desc_id in rendcommon.c
985 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
986 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
987 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
988 - Remove undefined directive-in-macro in test_util_writepid clang
989 3.7 complains that using a preprocessor directive inside a macro
990 invocation in test_util_writepid in test_util.c is undefined.
991 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
993 o Code simplification and refactoring:
994 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
995 to ensure they remain consistent and visible everywhere.
996 - Remove some vestigial workarounds for the MSVC6 compiler. We
997 haven't supported that in ages.
998 - The link authentication code has been refactored for better
999 testability and reliability. It now uses code generated with the
1000 "trunnel" binary encoding generator, to reduce the risk of bugs
1001 due to programmer error. Done as part of ticket 12498.
1004 - Include a specific and (hopefully) accurate documentation of the
1005 torrc file's meta-format in doc/torrc_format.txt. This is mainly
1006 of interest to people writing programs to parse or generate torrc
1007 files. This document is not a commitment to long-term
1008 compatibility; some aspects of the current format are a bit
1009 ridiculous. Closes ticket 2325.
1012 - Tor no longer supports copies of OpenSSL that are missing support
1013 for Elliptic Curve Cryptography. (We began using ECC when
1014 available in 0.2.4.8-alpha, for more safe and efficient key
1015 negotiation.) In particular, support for at least one of P256 or
1016 P224 is now required, with manual configuration needed if only
1017 P224 is available. Resolves ticket 16140.
1018 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1019 on an operating system that has not upgraded to OpenSSL 1.0 or
1020 later, and you compile Tor from source, you will need to install a
1021 more recent OpenSSL to link Tor against.) These versions of
1022 OpenSSL are still supported by the OpenSSL, but the numerous
1023 cryptographic improvements in later OpenSSL releases makes them a
1024 clear choice. Resolves ticket 16034.
1025 - Remove the HidServDirectoryV2 option. Now all relays offer to
1026 store hidden service descriptors. Related to 16543.
1027 - Remove the VoteOnHidServDirectoriesV2 option, since all
1028 authorities have long set it to 1. Closes ticket 16543.
1031 - Document use of coverity, clang static analyzer, and clang dynamic
1032 undefined behavior and address sanitizers in doc/HACKING. Include
1033 detailed usage instructions in the blacklist. Patch by "teor".
1034 Closes ticket 15817.
1035 - The link authentication protocol code now has extensive tests.
1036 - The relay descriptor signature testing code now has
1038 - The test_workqueue program now runs faster, and is enabled by
1039 default as a part of "make check".
1040 - Now that OpenSSL has its own scrypt implementation, add an unit
1041 test that checks for interoperability between libscrypt_scrypt()
1042 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
1043 and rely on EVP_PBE_scrypt() whenever possible. Resolves
1047 Changes in version 0.2.6.10 - 2015-07-12
1048 Tor version 0.2.6.10 fixes some significant stability and hidden
1049 service client bugs, bulletproofs the cryptography init process, and
1050 fixes a bug when using the sandbox code with some older versions of
1051 Linux. Everyone running an older version, especially an older version
1052 of 0.2.6, should upgrade.
1054 o Major bugfixes (hidden service clients, stability):
1055 - Stop refusing to store updated hidden service descriptors on a
1056 client. This reverts commit 9407040c59218 (which indeed fixed bug
1057 14219, but introduced a major hidden service reachability
1058 regression detailed in bug 16381). This is a temporary fix since
1059 we can live with the minor issue in bug 14219 (it just results in
1060 some load on the network) but the regression of 16381 is too much
1061 of a setback. First-round fix for bug 16381; bugfix
1064 o Major bugfixes (stability):
1065 - Stop crashing with an assertion failure when parsing certain kinds
1066 of malformed or truncated microdescriptors. Fixes bug 16400;
1067 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1068 by "cypherpunks_backup".
1069 - Stop random client-side assertion failures that could occur when
1070 connecting to a busy hidden service, or connecting to a hidden
1071 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1074 o Minor features (geoip):
1075 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1076 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1078 o Minor bugfixes (crypto error-handling):
1079 - Check for failures from crypto_early_init, and refuse to continue.
1080 A previous typo meant that we could keep going with an
1081 uninitialized crypto library, and would have OpenSSL initialize
1082 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1083 when implementing ticket 4900. Patch by "teor".
1085 o Minor bugfixes (Linux seccomp2 sandbox):
1086 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1087 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1088 on 0.2.6.3-alpha. Patch from "teor".
1091 Changes in version 0.2.6.9 - 2015-06-11
1092 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
1093 requirements for receiving an HSDir flag, and addresses some other small
1094 bugs in the systemd and sandbox code. Clients using circuit isolation
1095 should upgrade; all directory authorities should upgrade.
1097 o Major bugfixes (client-side privacy):
1098 - Properly separate out each SOCKSPort when applying stream
1099 isolation. The error occurred because each port's session group was
1100 being overwritten by a default value when the listener connection
1101 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
1104 o Minor feature (directory authorities, security):
1105 - The HSDir flag given by authorities now requires the Stable flag.
1106 For the current network, this results in going from 2887 to 2806
1107 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1108 attack by raising the effort for a relay to become Stable which
1109 takes at the very least 7 days to do so and by keeping the 96
1110 hours uptime requirement for HSDir. Implements ticket 8243.
1112 o Minor bugfixes (compilation):
1113 - Build with --enable-systemd correctly when libsystemd is
1114 installed, but systemd is not. Fixes bug 16164; bugfix on
1115 0.2.6.3-alpha. Patch from Peter Palfrader.
1117 o Minor bugfixes (Linux seccomp2 sandbox):
1118 - Fix sandboxing to work when running as a relaymby renaming of
1119 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
1120 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
1121 - Allow systemd connections to work with the Linux seccomp2 sandbox
1122 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1125 o Minor bugfixes (tests):
1126 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1127 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1130 Changes in version 0.2.6.8 - 2015-05-21
1131 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
1132 fixes an authority-side bug in assigning the HSDir flag. All directory
1133 authorities should upgrade.
1135 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
1136 - Revert commit that made directory authorities assign the HSDir
1137 flag to relay without a DirPort; this was bad because such relays
1138 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1139 on tor-0.2.6.3-alpha.
1141 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1142 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1143 a client authorized hidden service. Fixes bug 15823; bugfix
1146 o Minor features (geoip):
1147 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1148 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1152 Changes in version 0.2.7.1-alpha - 2015-05-12
1153 Tor 0.2.7.1-alpha is the first alpha release in its series. It
1154 includes numerous small features and bugfixes against previous Tor
1155 versions, and numerous small infrastructure improvements. The most
1156 notable features are several new ways for controllers to interact with
1157 the hidden services subsystem.
1159 o New system requirements:
1160 - Tor no longer includes workarounds to support Libevent versions
1161 before 1.3e. Libevent 2.0 or later is recommended. Closes
1164 o Major features (controller):
1165 - Add the ADD_ONION and DEL_ONION commands that allow the creation
1166 and management of hidden services via the controller. Closes
1168 - New "GETINFO onions/current" and "GETINFO onions/detached"
1169 commands to get information about hidden services created via the
1170 controller. Part of ticket 6411.
1171 - New HSFETCH command to launch a request for a hidden service
1172 descriptor. Closes ticket 14847.
1173 - New HSPOST command to upload a hidden service descriptor. Closes
1174 ticket 3523. Patch by "DonnchaC".
1176 o Major bugfixes (hidden services):
1177 - Revert commit that made directory authorities assign the HSDir
1178 flag to relay without a DirPort; this was bad because such relays
1179 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1180 on tor-0.2.6.3-alpha.
1182 o Minor features (clock-jump tolerance):
1183 - Recover better when our clock jumps back many hours, like might
1184 happen for Tails or Whonix users who start with a very wrong
1185 hardware clock, use Tor to discover a more accurate time, and then
1186 fix their clock. Resolves part of ticket 8766.
1188 o Minor features (command-line interface):
1189 - Make --hash-password imply --hush to prevent unnecessary noise.
1190 Closes ticket 15542. Patch from "cypherpunks".
1191 - Print a warning whenever we find a relative file path being used
1192 as torrc option. Resolves issue 14018.
1194 o Minor features (controller):
1195 - Add DirAuthority lines for default directory authorities to the
1196 output of the "GETINFO config/defaults" command if not already
1197 present. Implements ticket 14840.
1198 - Controllers can now use "GETINFO hs/client/desc/id/..." to
1199 retrieve items from the client's hidden service descriptor cache.
1200 Closes ticket 14845.
1201 - Implement a new controller command "GETINFO status/fresh-relay-
1202 descs" to fetch a descriptor/extrainfo pair that was generated on
1203 demand just for the controller's use. Implements ticket 14784.
1205 o Minor features (DoS-resistance):
1206 - Make it harder for attackers to overload hidden services with
1207 introductions, by blocking multiple introduction requests on the
1208 same circuit. Resolves ticket 15515.
1210 o Minor features (geoip):
1211 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1212 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1215 o Minor features (HS popularity countermeasure):
1216 - To avoid leaking HS popularity, don't cycle the introduction point
1217 when we've handled a fixed number of INTRODUCE2 cells but instead
1218 cycle it when a random number of introductions is reached, thus
1219 making it more difficult for an attacker to find out the amount of
1220 clients that have used the introduction point for a specific HS.
1221 Closes ticket 15745.
1223 o Minor features (logging):
1224 - Include the Tor version in all LD_BUG log messages, since people
1225 tend to cut and paste those into the bugtracker. Implements
1228 o Minor features (pluggable transports):
1229 - When launching managed pluggable transports on Linux systems,
1230 attempt to have the kernel deliver a SIGTERM on tor exit if the
1231 pluggable transport process is still running. Resolves
1233 - When launching managed pluggable transports, setup a valid open
1234 stdin in the child process that can be used to detect if tor has
1235 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
1236 can be used by implementations to detect this new behavior.
1237 Resolves ticket 15435.
1239 o Minor features (testing):
1240 - Add a test to verify that the compiler does not eliminate our
1241 memwipe() implementation. Closes ticket 15377.
1242 - Add make rule `check-changes` to verify the format of changes
1243 files. Closes ticket 15180.
1244 - Add unit tests for control_event_is_interesting(). Add a compile-
1245 time check that the number of events doesn't exceed the capacity
1246 of control_event_t.event_mask. Closes ticket 15431, checks for
1247 bugs similar to 13085. Patch by "teor".
1248 - Command-line argument tests moved to Stem. Resolves ticket 14806.
1249 - Integrate the ntor, backtrace, and zero-length keys tests into the
1250 automake test suite. Closes ticket 15344.
1251 - Remove assertions during builds to determine Tor's test coverage.
1252 We don't want to trigger these even in assertions, so including
1253 them artificially makes our branch coverage look worse than it is.
1254 This patch provides the new test-stem-full and coverage-html-full
1255 configure options. Implements ticket 15400.
1257 o Minor bugfixes (build):
1258 - Improve out-of-tree builds by making non-standard rules work and
1259 clean up additional files and directories. Fixes bug 15053; bugfix
1262 o Minor bugfixes (command-line interface):
1263 - When "--quiet" is provided along with "--validate-config", do not
1264 write anything to stdout on success. Fixes bug 14994; bugfix
1266 - When complaining about bad arguments to "--dump-config", use
1269 o Minor bugfixes (configuration, unit tests):
1270 - Only add the default fallback directories when the DirAuthorities,
1271 AlternateDirAuthority, and FallbackDir directory config options
1272 are set to their defaults. The default fallback directory list is
1273 currently empty, this fix will only change tor's behavior when it
1274 has default fallback directories. Includes unit tests for
1275 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
1276 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
1278 o Minor bugfixes (correctness):
1279 - For correctness, avoid modifying a constant string in
1280 handle_control_postdescriptor. Fixes bug 15546; bugfix
1282 - Remove side-effects from tor_assert() calls. This was harmless,
1283 because we never disable assertions, but it is bad style and
1284 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
1287 o Minor bugfixes (hidden service):
1288 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1289 a client authorized hidden service. Fixes bug 15823; bugfix
1291 - Remove an extraneous newline character from the end of hidden
1292 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
1294 o Minor bugfixes (interface):
1295 - Print usage information for --dump-config when it is used without
1296 an argument. Also, fix the error message to use different wording
1297 and add newline at the end. Fixes bug 15541; bugfix
1300 o Minor bugfixes (logs):
1301 - When building Tor under Clang, do not include an extra set of
1302 parentheses in log messages that include function names. Fixes bug
1303 15269; bugfix on every released version of Tor when compiled with
1304 recent enough Clang.
1306 o Minor bugfixes (network):
1307 - When attempting to use fallback technique for network interface
1308 lookup, disregard loopback and multicast addresses since they are
1309 unsuitable for public communications.
1311 o Minor bugfixes (statistics):
1312 - Disregard the ConnDirectionStatistics torrc options when Tor is
1313 not a relay since in that mode of operation no sensible data is
1314 being collected and because Tor might run into measurement hiccups
1315 when running as a client for some time, then becoming a relay.
1316 Fixes bug 15604; bugfix on 0.2.2.35.
1318 o Minor bugfixes (test networks):
1319 - When self-testing reachability, use ExtendAllowPrivateAddresses to
1320 determine if local/private addresses imply reachability. The
1321 previous fix used TestingTorNetwork, which implies
1322 ExtendAllowPrivateAddresses, but this excluded rare configurations
1323 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
1324 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
1325 issue discovered by CJ Ess.
1327 o Minor bugfixes (testing):
1328 - Check for matching value in server response in ntor_ref.py. Fixes
1329 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
1331 - Set the severity correctly when testing
1332 get_interface_addresses_ifaddrs() and
1333 get_interface_addresses_win32(), so that the tests fail gracefully
1334 instead of triggering an assertion. Fixes bug 15759; bugfix on
1335 0.2.6.3-alpha. Reported by Nicolas Derive.
1337 o Code simplification and refactoring:
1338 - Move the hacky fallback code out of get_interface_address6() into
1339 separate function and get it covered with unit-tests. Resolves
1341 - Refactor hidden service client-side cache lookup to intelligently
1342 report its various failure cases, and disentangle failure cases
1343 involving a lack of introduction points. Closes ticket 14391.
1344 - Use our own Base64 encoder instead of OpenSSL's, to allow more
1345 control over the output. Part of ticket 15652.
1348 - Improve the descriptions of statistics-related torrc options in
1349 the manpage to describe rationale and possible uses cases. Fixes
1351 - Improve the layout and formatting of ./configure --help messages.
1352 Closes ticket 15024. Patch from "cypherpunks".
1353 - Standardize on the term "server descriptor" in the manual page.
1354 Previously, we had used "router descriptor", "server descriptor",
1355 and "relay descriptor" interchangeably. Part of ticket 14987.
1358 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
1359 and always use the internal Base64 decoder. The internal decoder
1360 has been part of tor since tor-0.2.0.10-alpha, and no one should
1361 be using the OpenSSL one. Part of ticket 15652.
1362 - Remove the 'tor_strclear()' function; use memwipe() instead.
1363 Closes ticket 14922.
1366 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
1367 fingerprinting we now recommend pluggable transports; for forward-
1368 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
1369 - Remove the undocumented "--digests" command-line option. It
1370 complicated our build process, caused subtle build issues on
1371 multiple platforms, and is now redundant since we started
1372 including git version identifiers. Closes ticket 14742.
1373 - Tor no longer contains checks for ancient directory cache versions
1374 that didn't know about microdescriptors.
1375 - Tor no longer contains workarounds for stat files generated by
1376 super-old versions of Tor that didn't choose guards sensibly.
1379 Changes in version 0.2.4.27 - 2015-04-06
1380 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
1381 could be used by an attacker to crash hidden services, or crash clients
1382 visiting hidden services. Hidden services should upgrade as soon as
1383 possible; clients should upgrade whenever packages become available.
1385 This release also backports a simple improvement to make hidden
1386 services a bit less vulnerable to denial-of-service attacks.
1388 o Major bugfixes (security, hidden service):
1389 - Fix an issue that would allow a malicious client to trigger an
1390 assertion failure and halt a hidden service. Fixes bug 15600;
1391 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1392 - Fix a bug that could cause a client to crash with an assertion
1393 failure when parsing a malformed hidden service descriptor. Fixes
1394 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1396 o Minor features (DoS-resistance, hidden service):
1397 - Introduction points no longer allow multiple INTRODUCE1 cells to
1398 arrive on the same circuit. This should make it more expensive for
1399 attackers to overwhelm hidden services with introductions.
1400 Resolves ticket 15515.
1403 Changes in version 0.2.6.7 - 2015-04-06
1404 Tor 0.2.6.7 fixes two security issues that could be used by an
1405 attacker to crash hidden services, or crash clients visiting hidden
1406 services. Hidden services should upgrade as soon as possible; clients
1407 should upgrade whenever packages become available.
1409 This release also contains two simple improvements to make hidden
1410 services a bit less vulnerable to denial-of-service attacks.
1412 o Major bugfixes (security, hidden service):
1413 - Fix an issue that would allow a malicious client to trigger an
1414 assertion failure and halt a hidden service. Fixes bug 15600;
1415 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1416 - Fix a bug that could cause a client to crash with an assertion
1417 failure when parsing a malformed hidden service descriptor. Fixes
1418 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1420 o Minor features (DoS-resistance, hidden service):
1421 - Introduction points no longer allow multiple INTRODUCE1 cells to
1422 arrive on the same circuit. This should make it more expensive for
1423 attackers to overwhelm hidden services with introductions.
1424 Resolves ticket 15515.
1425 - Decrease the amount of reattempts that a hidden service performs
1426 when its rendezvous circuits fail. This reduces the computational
1427 cost for running a hidden service under heavy load. Resolves
1431 Changes in version 0.2.6.6 - 2015-03-24
1432 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1434 It adds numerous safety, security, correctness, and performance
1435 improvements. Client programs can be configured to use more kinds of
1436 sockets, AutomapHosts works better, the multithreading backend is
1437 improved, cell transmission is refactored, test coverage is much
1438 higher, more denial-of-service attacks are handled, guard selection is
1439 improved to handle long-term guards better, pluggable transports
1440 should work a bit better, and some annoying hidden service performance
1441 bugs should be addressed.
1443 o Minor bugfixes (portability):
1444 - Use the correct datatype in the SipHash-2-4 function to prevent
1445 compilers from assuming any sort of alignment. Fixes bug 15436;
1446 bugfix on 0.2.5.3-alpha.
1448 Changes in version 0.2.6.5-rc - 2015-03-18
1449 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
1450 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
1452 o Major bugfixes (client):
1453 - Avoid crashing when making certain configuration option changes on
1454 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
1457 o Major bugfixes (pluggable transports):
1458 - Initialize the extended OR Port authentication cookie before
1459 launching pluggable transports. This prevents a race condition
1460 that occured when server-side pluggable transports would cache the
1461 authentication cookie before it has been (re)generated. Fixes bug
1462 15240; bugfix on 0.2.5.1-alpha.
1464 o Major bugfixes (portability):
1465 - Do not crash on startup when running on Solaris. Fixes a bug
1466 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
1469 o Minor features (heartbeat):
1470 - On relays, report how many connections we negotiated using each
1471 version of the Tor link protocols. This information will let us
1472 know if removing support for very old versions of the Tor
1473 protocols is harming the network. Closes ticket 15212.
1475 o Code simplification and refactoring:
1476 - Refactor main loop to extract the 'loop' part. This makes it
1477 easier to run Tor under Shadow. Closes ticket 15176.
1480 Changes in version 0.2.5.11 - 2015-03-17
1481 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1483 It backports several bugfixes from the 0.2.6 branch, including a
1484 couple of medium-level security fixes for relays and exit nodes.
1485 It also updates the list of directory authorities.
1487 o Directory authority changes:
1488 - Remove turtles as a directory authority.
1489 - Add longclaw as a new (v3) directory authority. This implements
1490 ticket 13296. This keeps the directory authority count at 9.
1491 - The directory authority Faravahar has a new IP address. This
1492 closes ticket 14487.
1494 o Major bugfixes (crash, OSX, security):
1495 - Fix a remote denial-of-service opportunity caused by a bug in
1496 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1499 o Major bugfixes (relay, stability, possible security):
1500 - Fix a bug that could lead to a relay crashing with an assertion
1501 failure if a buffer of exactly the wrong layout was passed to
1502 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1503 0.2.0.10-alpha. Patch from 'cypherpunks'.
1504 - Do not assert if the 'data' pointer on a buffer is advanced to the
1505 very end of the buffer; log a BUG message instead. Only assert if
1506 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1508 o Major bugfixes (exit node stability):
1509 - Fix an assertion failure that could occur under high DNS load.
1510 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1511 diagnosed and fixed by "cypherpunks".
1513 o Major bugfixes (Linux seccomp2 sandbox):
1514 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1515 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1516 0.2.5.1-alpha. Patch from "sanic".
1518 o Minor features (controller):
1519 - New "GETINFO bw-event-cache" to get information about recent
1520 bandwidth events. Closes ticket 14128. Useful for controllers to
1521 get recent bandwidth history after the fix for ticket 13988.
1523 o Minor features (geoip):
1524 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1525 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1528 o Minor bugfixes (client, automapping):
1529 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1530 no value follows the option. Fixes bug 14142; bugfix on
1531 0.2.4.7-alpha. Patch by "teor".
1532 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1533 14195; bugfix on 0.1.0.1-rc.
1535 o Minor bugfixes (compilation):
1536 - Build without warnings with the stock OpenSSL srtp.h header, which
1537 has a duplicate declaration of SSL_get_selected_srtp_profile().
1538 Fixes bug 14220; this is OpenSSL's bug, not ours.
1540 o Minor bugfixes (directory authority):
1541 - Allow directory authorities to fetch more data from one another if
1542 they find themselves missing lots of votes. Previously, they had
1543 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1544 bugfix on 0.1.2.5-alpha.
1545 - Enlarge the buffer to read bwauth generated files to avoid an
1546 issue when parsing the file in dirserv_read_measured_bandwidths().
1547 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1549 o Minor bugfixes (statistics):
1550 - Increase period over which bandwidth observations are aggregated
1551 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1553 o Minor bugfixes (preventative security, C safety):
1554 - When reading a hexadecimal, base-32, or base-64 encoded value from
1555 a string, always overwrite the whole output buffer. This prevents
1556 some bugs where we would look at (but fortunately, not reveal)
1557 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1561 Changes in version 0.2.4.26 - 2015-03-17
1562 Tor 0.2.4.26 includes an updated list of directory authorities. It
1563 also backports a couple of stability and security bugfixes from 0.2.5
1566 o Directory authority changes:
1567 - Remove turtles as a directory authority.
1568 - Add longclaw as a new (v3) directory authority. This implements
1569 ticket 13296. This keeps the directory authority count at 9.
1570 - The directory authority Faravahar has a new IP address. This
1571 closes ticket 14487.
1573 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1574 - Fix an assertion failure that could occur under high DNS load.
1575 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1576 diagnosed and fixed by "cypherpunks".
1578 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1579 - Fix a bug that could lead to a relay crashing with an assertion
1580 failure if a buffer of exactly the wrong layout was passed to
1581 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1582 0.2.0.10-alpha. Patch from 'cypherpunks'.
1583 - Do not assert if the 'data' pointer on a buffer is advanced to the
1584 very end of the buffer; log a BUG message instead. Only assert if
1585 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1587 o Minor features (geoip):
1588 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1589 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1592 Changes in version 0.2.6.4-rc - 2015-03-09
1593 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
1594 attacker might be able to use in order to crash certain Tor
1595 directories. It also resolves some minor issues left over from, or
1596 introduced in, Tor 0.2.6.3-alpha or earlier.
1598 o Major bugfixes (crash, OSX, security):
1599 - Fix a remote denial-of-service opportunity caused by a bug in
1600 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1603 o Major bugfixes (relay, stability, possible security):
1604 - Fix a bug that could lead to a relay crashing with an assertion
1605 failure if a buffer of exactly the wrong layout is passed to
1606 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1607 0.2.0.10-alpha. Patch from "cypherpunks".
1608 - Do not assert if the 'data' pointer on a buffer is advanced to the
1609 very end of the buffer; log a BUG message instead. Only assert if
1610 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1612 o Major bugfixes (FreeBSD IPFW transparent proxy):
1613 - Fix address detection with FreeBSD transparent proxies, when
1614 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1617 o Major bugfixes (Linux seccomp2 sandbox):
1618 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
1619 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
1621 - Allow AF_UNIX hidden services to be used with the seccomp2
1622 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
1623 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1624 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1625 0.2.5.1-alpha. Patch from "sanic".
1627 o Minor features (controller):
1628 - Messages about problems in the bootstrap process now include
1629 information about the server we were trying to connect to when we
1630 noticed the problem. Closes ticket 15006.
1632 o Minor features (geoip):
1633 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1634 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1637 o Minor features (logs):
1638 - Quiet some log messages in the heartbeat and at startup. Closes
1641 o Minor bugfixes (certificate handling):
1642 - If an authority operator accidentally makes a signing certificate
1643 with a future publication time, do not discard its real signing
1644 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1645 - Remove any old authority certificates that have been superseded
1646 for at least two days. Previously, we would keep superseded
1647 certificates until they expired, if they were published close in
1648 time to the certificate that superseded them. Fixes bug 11454;
1649 bugfix on 0.2.1.8-alpha.
1651 o Minor bugfixes (compilation):
1652 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1654 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
1657 o Minor bugfixes (testing):
1658 - Fix endianness issues in unit test for resolve_my_address() to
1659 have it pass on big endian systems. Fixes bug 14980; bugfix on
1661 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1662 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1663 - When running the new 'make test-stem' target, use the configured
1664 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
1666 - When running the zero-length-keys tests, do not use the default
1667 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
1670 o Directory authority IP change:
1671 - The directory authority Faravahar has a new IP address. This
1672 closes ticket 14487.
1675 - Remove some lingering dead code that once supported mempools.
1676 Mempools were disabled by default in 0.2.5, and removed entirely
1677 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
1681 Changes in version 0.2.6.3-alpha - 2015-02-19
1682 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
1683 the 0.2.6.x series. It introduces support for more kinds of sockets,
1684 makes it harder to accidentally run an exit, improves our
1685 multithreading backend, incorporates several fixes for the
1686 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
1688 If no major regressions or security holes are found in this version,
1689 the next version will be a release candidate.
1691 o Deprecated versions:
1692 - Tor relays older than 0.2.4.18-rc are no longer allowed to
1693 advertise themselves on the network. Closes ticket 13555.
1695 o Major features (security, unix domain sockets):
1696 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
1697 applications can reach Tor without having to create AF_INET or
1698 AF_INET6 sockets, meaning they can completely disable their
1699 ability to make non-Tor network connections. To create a socket of
1700 this type, use "SocksPort unix:/path/to/socket". Implements
1702 - Support mapping hidden service virtual ports to AF_UNIX sockets.
1703 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
1704 Implements ticket 11485.
1706 o Major features (changed defaults):
1707 - Prevent relay operators from unintentionally running exits: When a
1708 relay is configured as an exit node, we now warn the user unless
1709 the "ExitRelay" option is set to 1. We warn even more loudly if
1710 the relay is configured with the default exit policy, since this
1711 can indicate accidental misconfiguration. Setting "ExitRelay 0"
1712 stops Tor from running as an exit relay. Closes ticket 10067.
1714 o Major features (directory system):
1715 - When downloading server- or microdescriptors from a directory
1716 server, we no longer launch multiple simultaneous requests to the
1717 same server. This reduces load on the directory servers,
1718 especially when directory guards are in use. Closes ticket 9969.
1719 - When downloading server- or microdescriptors over a tunneled
1720 connection, do not limit the length of our requests to what the
1721 Squid proxy is willing to handle. Part of ticket 9969.
1722 - Authorities can now vote on the correct digests and latest
1723 versions for different software packages. This allows packages
1724 that include Tor to use the Tor authority system as a way to get
1725 notified of updates and their correct digests. Implements proposal
1726 227. Closes ticket 10395.
1728 o Major features (guards):
1729 - Introduce the Guardfraction feature to improves load balancing on
1730 guard nodes. Specifically, it aims to reduce the traffic gap that
1731 guard nodes experience when they first get the Guard flag. This is
1732 a required step if we want to increase the guard lifetime to 9
1733 months or greater. Closes ticket 9321.
1735 o Major features (performance):
1736 - Make the CPU worker implementation more efficient by avoiding the
1737 kernel and lengthening pipelines. The original implementation used
1738 sockets to transfer data from the main thread to the workers, and
1739 didn't allow any thread to be assigned more than a single piece of
1740 work at once. The new implementation avoids communications
1741 overhead by making requests in shared memory, avoiding kernel IO
1742 where possible, and keeping more requests in flight at once.
1743 Implements ticket 9682.
1745 o Major features (relay):
1746 - Raise the minimum acceptable configured bandwidth rate for bridges
1747 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
1748 20 KiB/sec.) Closes ticket 13822.
1750 o Major bugfixes (exit node stability):
1751 - Fix an assertion failure that could occur under high DNS load.
1752 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1753 diagnosed and fixed by "cypherpunks".
1755 o Major bugfixes (mixed relay-client operation):
1756 - When running as a relay and client at the same time (not
1757 recommended), if we decide not to use a new guard because we want
1758 to retry older guards, only close the locally-originating circuits
1759 passing through that guard. Previously we would close all the
1760 circuits through that guard. Fixes bug 9819; bugfix on
1761 0.2.1.1-alpha. Reported by "skruffy".
1763 o Minor features (build):
1764 - New --disable-system-torrc compile-time option to prevent Tor from
1765 looking for the system-wide torrc or torrc-defaults files.
1766 Resolves ticket 13037.
1768 o Minor features (controller):
1769 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1770 events so controllers can observe circuit isolation inputs. Closes
1772 - ControlPort now supports the unix:/path/to/socket syntax as an
1773 alternative to the ControlSocket option, for consistency with
1774 SocksPort and HiddenServicePort. Closes ticket 14451.
1775 - New "GETINFO bw-event-cache" to get information about recent
1776 bandwidth events. Closes ticket 14128. Useful for controllers to
1777 get recent bandwidth history after the fix for ticket 13988.
1779 o Minor features (Denial of service resistance):
1780 - Count the total number of bytes used storing hidden service
1781 descriptors against the value of MaxMemInQueues. If we're low on
1782 memory, and more than 20% of our memory is used holding hidden
1783 service descriptors, free them until no more than 10% of our
1784 memory holds hidden service descriptors. Free the least recently
1785 fetched descriptors first. Resolves ticket 13806.
1786 - When we have recently been under memory pressure (over 3/4 of
1787 MaxMemInQueues is allocated), then allocate smaller zlib objects
1788 for small requests. Closes ticket 11791.
1790 o Minor features (geoip):
1791 - Update geoip and geoip6 files to the January 7 2015 Maxmind
1792 GeoLite2 Country database.
1794 o Minor features (guard nodes):
1795 - Reduce the time delay before saving guard status to disk from 10
1796 minutes to 30 seconds (or from one hour to 10 minutes if
1797 AvoidDiskWrites is set). Closes ticket 12485.
1799 o Minor features (hidden service):
1800 - Make Sybil attacks against hidden services harder by changing the
1801 minimum time required to get the HSDir flag from 25 hours up to 96
1802 hours. Addresses ticket 14149.
1803 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1804 services to disable the anti-scanning feature introduced in
1805 0.2.6.2-alpha. With this option not set, a connection to an
1806 unlisted port closes the circuit. With this option set, only a
1807 RELAY_DONE cell is sent. Closes ticket 14084.
1809 o Minor features (interface):
1810 - Implement "-f -" command-line option to read torrc configuration
1811 from standard input, if you don't want to store the torrc file in
1812 the file system. Implements feature 13865.
1814 o Minor features (logging):
1815 - Add a count of unique clients to the bridge heartbeat message.
1816 Resolves ticket 6852.
1817 - Suppress "router info incompatible with extra info" message when
1818 reading extrainfo documents from cache. (This message got loud
1819 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1821 - Elevate hidden service authorized-client message from DEBUG to
1822 INFO. Closes ticket 14015.
1824 o Minor features (stability):
1825 - Add assertions in our hash-table iteration code to check for
1826 corrupted values that could cause infinite loops. Closes
1829 o Minor features (systemd):
1830 - Various improvements and modernizations in systemd hardening
1831 support. Closes ticket 13805. Patch from Craig Andrews.
1833 o Minor features (testing networks):
1834 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1835 and the default on a testing network to 2 minutes. Drop the
1836 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1837 keep the default on a testing network at 30 seconds. This reduces
1838 HS bootstrap time to around 25 seconds. Also, change the default
1839 time in test-network.sh to match. Closes ticket 13401. Patch
1841 - Create TestingDirAuthVoteHSDir to correspond to
1842 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1843 HSDir flag for the listed relays regardless of uptime or ORPort
1844 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1845 Partial implementation for ticket 14067. Patch by "teor".
1847 o Minor features (tor2web mode):
1848 - Introduce the config option Tor2webRendezvousPoints, which allows
1849 clients in Tor2webMode to select a specific Rendezvous Point to be
1850 used in HS circuits. This might allow better performance for
1851 Tor2Web nodes. Implements ticket 12844.
1853 o Minor bugfixes (client DNS):
1854 - Report the correct cached DNS expiration times on SOCKS port or in
1855 DNS replies. Previously, we would report everything as "never
1856 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1857 - Avoid a small memory leak when we find a cached answer for a
1858 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1859 side DNS caching is off by default, and is not recommended.) Fixes
1860 bug 14259; bugfix on 0.2.0.1-alpha.
1862 o Minor bugfixes (client, automapping):
1863 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1864 no value follows the option. Fixes bug 14142; bugfix on
1865 0.2.4.7-alpha. Patch by "teor".
1866 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1867 14195; bugfix on 0.1.0.1-rc.
1868 - Prevent changes to other options from removing the wildcard value
1869 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1871 - Allow MapAddress and AutomapHostsOnResolve to work together when
1872 an address is mapped into another address type (like .onion) that
1873 must be automapped at resolve time. Fixes bug 7555; bugfix
1876 o Minor bugfixes (client, bridges):
1877 - When we are using bridges and we had a network connectivity
1878 problem, only retry connecting to our currently configured
1879 bridges, not all bridges we know about and remember using. Fixes
1880 bug 14216; bugfix on 0.2.2.17-alpha.
1882 o Minor bugfixes (client, IPv6):
1883 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1884 flag is not set; and not because the NoIPv4Traffic flag was set.
1885 Previously we'd looked at the NoIPv4Traffic flag for both types of
1886 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1888 o Minor bugfixes (compilation):
1889 - The address of an array in the middle of a structure will always
1890 be non-NULL. clang recognises this and complains. Disable the
1891 tautologous and redundant check to silence this warning. Fixes bug
1892 14001; bugfix on 0.2.1.2-alpha.
1893 - Avoid warnings when building with systemd 209 or later. Fixes bug
1894 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
1895 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1896 Addresses ticket 14188.
1897 - Build without warnings with the stock OpenSSL srtp.h header, which
1898 has a duplicate declaration of SSL_get_selected_srtp_profile().
1899 Fixes bug 14220; this is OpenSSL's bug, not ours.
1900 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1901 is not enabled at compile time. Previously, this code was included
1902 in a disabled state. See discussion on ticket 12844.
1903 - Remove the --disable-threads configure option again. It was
1904 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
1905 14819; bugfix on 0.2.6.2-alpha.
1907 o Minor bugfixes (controller):
1908 - Report "down" in response to the "GETINFO entry-guards" command
1909 when relays are down with an unreachable_since value. Previously,
1910 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1911 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1912 14116; bugfix on 0.2.2.9-alpha.
1913 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
1914 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
1916 o Minor bugfixes (directory authority):
1917 - Allow directory authorities to fetch more data from one another if
1918 they find themselves missing lots of votes. Previously, they had
1919 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1920 bugfix on 0.1.2.5-alpha.
1921 - Do not attempt to download extrainfo documents which we will be
1922 unable to validate with a matching server descriptor. Fixes bug
1923 13762; bugfix on 0.2.0.1-alpha.
1924 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1925 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1926 - Enlarge the buffer to read bwauth generated files to avoid an
1927 issue when parsing the file in dirserv_read_measured_bandwidths().
1928 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1930 o Minor bugfixes (file handling):
1931 - Stop failing when key files are zero-length. Instead, generate new
1932 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1933 on all versions of Tor. Patch by "teor".
1934 - Stop generating a fresh .old RSA onion key file when the .old file
1935 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1936 - Avoid overwriting .old key files with empty key files.
1937 - Skip loading zero-length extrainfo store, router store, stats,
1938 state, and key files.
1939 - Avoid crashing when trying to reload a torrc specified as a
1940 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1943 o Minor bugfixes (hidden services):
1944 - Close the introduction circuit when we have no more usable intro
1945 points, instead of waiting for it to time out. This also ensures
1946 that no follow-up HS descriptor fetch is triggered when the
1947 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1948 - When fetching a hidden service descriptor for a down service that
1949 was recently up, do not keep refetching until we try the same
1950 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1951 - Successfully launch Tor with a nonexistent hidden service
1952 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
1953 14106; bugfix on 0.2.6.2-alpha.
1955 o Minor bugfixes (logging):
1956 - Avoid crashing when there are more log domains than entries in
1957 domain_list. Bugfix on 0.2.3.1-alpha.
1958 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
1960 - Don't log messages to stdout twice when starting up. Fixes bug
1961 13993; bugfix on 0.2.6.1-alpha.
1963 o Minor bugfixes (parsing):
1964 - Stop accepting milliseconds (or other junk) at the end of
1965 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1966 - Support two-number and three-number version numbers correctly, in
1967 case we change the Tor versioning system in the future. Fixes bug
1968 13661; bugfix on 0.0.8pre1.
1970 o Minor bugfixes (path counting):
1971 - When deciding whether the consensus lists any exit nodes, count
1972 the number listed in the consensus, not the number we have
1973 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
1974 - When deciding whether we have any exit nodes, only examine
1975 ExitNodes when the ExitNodes option is actually set. Fixes part of
1976 bug 14918; bugfix on 0.2.6.2-alpha.
1977 - Get rid of redundant and possibly scary warnings that we are
1978 missing directory information while we bootstrap. Fixes part of
1979 bug 14918; bugfix on 0.2.6.2-alpha.
1981 o Minor bugfixes (portability):
1982 - Fix the ioctl()-based network interface lookup code so that it
1983 will work on systems that have variable-length struct ifreq, for
1985 - Fix scheduler compilation on targets where char is unsigned. Fixes
1986 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
1988 o Minor bugfixes (sandbox):
1989 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1990 Previously, glibc would try to write them to /dev/tty, and the
1991 sandbox would trap the call and make Tor exit prematurely. Fixes
1992 bug 14759; bugfix on 0.2.5.1-alpha.
1994 o Minor bugfixes (shutdown):
1995 - When shutting down, always call event_del() on lingering read or
1996 write events before freeing them. Otherwise, we risk double-frees
1997 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
2000 o Minor bugfixes (small memory leaks):
2001 - Avoid leaking memory when using IPv6 virtual address mappings.
2002 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
2005 o Minor bugfixes (statistics):
2006 - Increase period over which bandwidth observations are aggregated
2007 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2009 o Minor bugfixes (systemd support):
2010 - Fix detection and operation of systemd watchdog. Fixes part of bug
2011 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
2012 - Run correctly under systemd with the RunAsDaemon option set. Fixes
2013 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
2014 - Inform the systemd supervisor about more changes in the Tor
2015 process status. Implements part of ticket 14141. Patch from
2017 - Cause the "--disable-systemd" option to actually disable systemd
2018 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
2021 o Minor bugfixes (TLS):
2022 - Check more thoroughly throughout the TLS code for possible
2023 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
2025 o Minor bugfixes (transparent proxy):
2026 - Use getsockname, not getsockopt, to retrieve the address for a
2027 TPROXY-redirected connection. Fixes bug 13796; bugfix
2030 o Code simplification and refactoring:
2031 - Move fields related to isolating and configuring client ports into
2032 a shared structure. Previously, they were duplicated across
2033 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
2034 to copy them correctly had been the cause of at least one bug in
2035 the past. Closes ticket 8546.
2036 - Refactor the get_interface_addresses_raw() doom-function into
2037 multiple smaller and simpler subfunctions. Cover the resulting
2038 subfunctions with unit-tests. Fixes a significant portion of
2040 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
2041 only for version <= 0.2.2.24 which is now deprecated. Closes
2043 - Remove a test for a long-defunct broken version-one
2047 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
2048 for writing the OpenBSD-specific tips. Resolves ticket 13702.
2049 - Make the tor-resolve documentation match its help string and its
2050 options. Resolves part of ticket 14325.
2051 - Log a more useful error message from tor-resolve when failing to
2052 look up a hidden service address. Resolves part of ticket 14325.
2054 o Downgraded warnings:
2055 - Don't warn when we've attempted to contact a relay using the wrong
2056 ntor onion key. Closes ticket 9635.
2059 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
2060 longer silently accepted as an alias for "ExitNodes".
2061 - The --enable-mempool and --enable-buf-freelists options, which
2062 were originally created to work around bad malloc implementations,
2063 no longer exist. They were off-by-default in 0.2.5. Closes
2067 - Make the checkdir/perms test complete successfully even if the
2068 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
2069 - Test that tor does not fail when key files are zero-length. Check
2070 that tor generates new keys, and overwrites the empty key files.
2071 - Test that tor generates new keys when keys are missing
2072 (existing behavior).
2073 - Test that tor does not overwrite key files that already contain
2074 data (existing behavior). Tests bug 13111. Patch by "teor".
2075 - New "make test-stem" target to run stem integration tests.
2076 Requires that the "STEM_SOURCE_DIR" environment variable be set.
2077 Closes ticket 14107.
2078 - Make the test_cmdline_args.py script work correctly on Windows.
2079 Patch from Gisle Vanem.
2080 - Move the slower unit tests into a new "./src/test/test-slow"
2081 binary that can be run independently of the other tests. Closes
2083 - Avoid undefined behavior when sampling huge values from the
2084 Laplace distribution. This made unittests fail on Raspberry Pi.
2085 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
2088 Changes in version 0.2.6.2-alpha - 2014-12-31
2089 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
2090 It introduces a major new backend for deciding when to send cells on
2091 channels, which should lead down the road to big performance
2092 increases. It contains security and statistics features for better
2093 work on hidden services, and numerous bugfixes.
2095 This release contains many new unit tests, along with major
2096 performance improvements for running testing networks using Chutney.
2097 Thanks to a series of patches contributed by "teor", testing networks
2098 should now bootstrap in seconds, rather than minutes.
2100 o Major features (relay, infrastructure):
2101 - Complete revision of the code that relays use to decide which cell
2102 to send next. Formerly, we selected the best circuit to write on
2103 each channel, but we didn't select among channels in any
2104 sophisticated way. Now, we choose the best circuits globally from
2105 among those whose channels are ready to deliver traffic.
2107 This patch implements a new inter-cmux comparison API, a global
2108 high/low watermark mechanism and a global scheduler loop for
2109 transmission prioritization across all channels as well as among
2110 circuits on one channel. This schedule is currently tuned to
2111 (tolerantly) avoid making changes in network performance, but it
2112 should form the basis for major circuit performance increases in
2113 the future. Code by Andrea; tuning by Rob Jansen; implements
2116 o Major features (hidden services):
2117 - Make HS port scanning more difficult by immediately closing the
2118 circuit when a user attempts to connect to a nonexistent port.
2119 Closes ticket 13667.
2120 - Add a HiddenServiceStatistics option that allows Tor relays to
2121 gather and publish statistics about the overall size and volume of
2122 hidden service usage. Specifically, when this option is turned on,
2123 an HSDir will publish an approximate number of hidden services
2124 that have published descriptors to it the past 24 hours. Also, if
2125 a relay has acted as a hidden service rendezvous point, it will
2126 publish the approximate amount of rendezvous cells it has relayed
2127 the past 24 hours. The statistics themselves are obfuscated so
2128 that the exact values cannot be derived. For more details see
2129 proposal 238, "Better hidden service stats from Tor relays". This
2130 feature is currently disabled by default. Implements feature 13192.
2132 o Major bugfixes (client, automap):
2133 - Repair automapping with IPv6 addresses. This automapping should
2134 have worked previously, but one piece of debugging code that we
2135 inserted to detect a regression actually caused the regression to
2136 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
2137 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
2140 o Major bugfixes (hidden services):
2141 - When closing an introduction circuit that was opened in parallel
2142 with others, don't mark the introduction point as unreachable.
2143 Previously, the first successful connection to an introduction
2144 point would make the other introduction points get marked as
2145 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
2147 o Directory authority changes:
2148 - Remove turtles as a directory authority.
2149 - Add longclaw as a new (v3) directory authority. This implements
2150 ticket 13296. This keeps the directory authority count at 9.
2152 o Major removed features:
2153 - Tor clients no longer support connecting to hidden services
2154 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
2155 option has been removed. (There shouldn't be any hidden services
2156 running these versions on the network.) Closes ticket 7803.
2158 o Minor features (client):
2159 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
2160 is enabled, reject requests with IP addresses as hostnames.
2161 Resolves ticket 13315.
2163 o Minor features (controller):
2164 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
2165 write an unscheduled heartbeat message to the log. Implements
2168 o Minor features (geoip):
2169 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
2172 o Minor features (hidden services):
2173 - When re-enabling the network, don't try to build introduction
2174 circuits until we have successfully built a circuit. This makes
2175 hidden services come up faster when the network is re-enabled.
2176 Patch from "akwizgran". Closes ticket 13447.
2177 - When we fail to retrieve a hidden service descriptor, send the
2178 controller an "HS_DESC FAILED" controller event. Implements
2180 - New HiddenServiceDirGroupReadable option to cause hidden service
2181 directories and hostname files to be created group-readable. Patch
2182 from "anon", David Stainton, and "meejah". Closes ticket 11291.
2184 o Minor features (systemd):
2185 - Where supported, when running with systemd, report successful
2186 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
2187 - When running with systemd, support systemd watchdog messages. Part
2188 of ticket 11016. Patch by Michael Scherer.
2190 o Minor features (transparent proxy):
2191 - Update the transparent proxy option checks to allow for both ipfw
2192 and pf on OS X. Closes ticket 14002.
2193 - Use the correct option when using IPv6 with transparent proxy
2194 support on Linux. Resolves 13808. Patch by Francisco Blas
2197 o Minor bugfixes (preventative security, C safety):
2198 - When reading a hexadecimal, base-32, or base-64 encoded value from
2199 a string, always overwrite the whole output buffer. This prevents
2200 some bugs where we would look at (but fortunately, not reveal)
2201 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2203 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
2204 just the part that's used. This makes it harder for data leak bugs
2205 to occur in the event of other programming failures. Resolves
2208 o Minor bugfixes (client, microdescriptors):
2209 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
2210 computing which microdescriptors to download. This keeps us from
2211 erroneous download behavior if two microdescriptor digests ever
2212 have the same first 160 bits. Fixes part of bug 13399; bugfix
2214 - Reset a router's status if its microdescriptor digest changes,
2215 even if the first 160 bits remain the same. Fixes part of bug
2216 13399; bugfix on 0.2.3.1-alpha.
2218 o Minor bugfixes (compilation):
2219 - Silence clang warnings under --enable-expensive-hardening,
2220 including implicit truncation of 64 bit values to 32 bit, const
2221 char assignment to self, tautological compare, and additional
2222 parentheses around equality tests. Fixes bug 13577; bugfix
2224 - Fix a clang warning about checking whether an address in the
2225 middle of a structure is NULL. Fixes bug 14001; bugfix
2228 o Minor bugfixes (hidden services):
2229 - Correctly send a controller event when we find that a rendezvous
2230 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
2231 - Pre-check directory permissions for new hidden-services to avoid
2232 at least one case of "Bug: Acting on config options left us in a
2233 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
2234 - When adding a new hidden service (for example, via SETCONF), Tor
2235 no longer congratulates the user for running a relay. Fixes bug
2236 13941; bugfix on 0.2.6.1-alpha.
2237 - When fetching hidden service descriptors, we now check not only
2238 for whether we got the hidden service we had in mind, but also
2239 whether we got the particular descriptors we wanted. This prevents
2240 a class of inefficient but annoying DoS attacks by hidden service
2241 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
2244 o Minor bugfixes (Linux seccomp2 sandbox):
2245 - Make transparent proxy support work along with the seccomp2
2246 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
2247 by Francisco Blas Izquierdo Riera.
2248 - Fix a memory leak in tor-resolve when running with the sandbox
2249 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
2251 o Minor bugfixes (logging):
2252 - Downgrade warnings about RSA signature failures to info log level.
2253 Emit a warning when an extra info document is found incompatible
2254 with a corresponding router descriptor. Fixes bug 9812; bugfix
2256 - Make connection_ap_handshake_attach_circuit() log the circuit ID
2257 correctly. Fixes bug 13701; bugfix on 0.0.6.
2259 o Minor bugfixes (misc):
2260 - Stop allowing invalid address patterns like "*/24" that contain
2261 both a wildcard address and a bit prefix length. This affects all
2262 our address-range parsing code. Fixes bug 7484; bugfix
2265 o Minor bugfixes (testing networks, fast startup):
2266 - Allow Tor to build circuits using a consensus with no exits. If
2267 the consensus has no exits (typical of a bootstrapping test
2268 network), allow Tor to build circuits once enough descriptors have
2269 been downloaded. This assists in bootstrapping a testing Tor
2270 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
2272 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
2273 header to directory servers. This allows us to obtain consensuses
2274 promptly when the consensus interval is very short. This assists
2275 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
2276 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
2277 - Stop assuming that private addresses are local when checking
2278 reachability in a TestingTorNetwork. Instead, when testing, assume
2279 all OR connections are remote. (This is necessary due to many test
2280 scenarios running all relays on localhost.) This assists in
2281 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
2282 0.1.0.1-rc. Patch by "teor".
2283 - Avoid building exit circuits from a consensus with no exits. Now
2284 thanks to our fix for 13718, we accept a no-exit network as not
2285 wholly lost, but we need to remember not to try to build exit
2286 circuits on it. Closes ticket 13814; patch by "teor".
2287 - Stop requiring exits to have non-zero bandwithcapacity in a
2288 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
2289 ignore exit bandwidthcapacity. This assists in bootstrapping a
2290 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
2291 on 0.2.0.3-alpha. Patch by "teor".
2292 - Add "internal" to some bootstrap statuses when no exits are
2293 available. If the consensus does not contain Exits, Tor will only
2294 build internal circuits. In this case, relevant statuses will
2295 contain the word "internal" as indicated in the Tor control-
2296 spec.txt. When bootstrap completes, Tor will be ready to build
2297 internal circuits. If a future consensus contains Exits, exit
2298 circuits may become available. Fixes part of bug 13718; bugfix on
2299 0.2.4.10-alpha. Patch by "teor".
2300 - Decrease minimum consensus interval to 10 seconds when
2301 TestingTorNetwork is set, or 5 seconds for the first consensus.
2302 Fix assumptions throughout the code that assume larger intervals.
2303 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
2305 - Avoid excluding guards from path building in minimal test
2306 networks, when we're in a test network and excluding guards would
2307 exclude all relays. This typically occurs in incredibly small tor
2308 networks, and those using "TestingAuthVoteGuard *". Fixes part of
2309 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
2311 o Code simplification and refactoring:
2312 - Stop using can_complete_circuits as a global variable; access it
2313 with a function instead.
2314 - Avoid using operators directly as macro arguments: this lets us
2315 apply coccinelle transformations to our codebase more directly.
2316 Closes ticket 13172.
2317 - Combine the functions used to parse ClientTransportPlugin and
2318 ServerTransportPlugin into a single function. Closes ticket 6456.
2319 - Add inline functions and convenience macros for inspecting channel
2320 state. Refactor the code to use convenience macros instead of
2321 checking channel state directly. Fixes issue 7356.
2322 - Document all members of was_router_added_t and rename
2323 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
2324 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
2325 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
2326 constant instead of hardcoded value. Fixes issue 13840.
2327 - Refactor our generic strmap and digestmap types into a single
2328 implementation, so that we can add a new digest256map
2332 - Document the bridge-authority-only 'networkstatus-bridges' file.
2333 Closes ticket 13713; patch from "tom".
2334 - Fix typo in PredictedPortsRelevanceTime option description in
2335 manpage. Resolves issue 13707.
2336 - Stop suggesting that users specify relays by nickname: it isn't a
2337 good idea. Also, properly cross-reference how to specify relays in
2338 all parts of manual documenting options that take a list of
2339 relays. Closes ticket 13381.
2340 - Clarify the HiddenServiceDir option description in manpage to make
2341 it clear that relative paths are taken with respect to the current
2342 working directory. Also clarify that this behavior is not
2343 guaranteed to remain indefinitely. Fixes issue 13913.
2346 - New tests for many parts of channel, relay, and circuitmux
2347 functionality. Code by Andrea; part of 9262.
2348 - New tests for parse_transport_line(). Part of ticket 6456.
2349 - In the unit tests, use chgrp() to change the group of the unit
2350 test temporary directory to the current user, so that the sticky
2351 bit doesn't interfere with tests that check directory groups.
2353 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
2357 Changes in version 0.2.6.1-alpha - 2014-10-30
2358 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
2359 includes numerous code cleanups and new tests, and fixes a large
2360 number of annoying bugs. Out-of-memory conditions are handled better
2361 than in 0.2.5, pluggable transports have improved proxy support, and
2362 clients now use optimistic data for contacting hidden services. Also,
2363 we are now more robust to changes in what we consider a parseable
2364 directory object, so that tightening restrictions does not have a risk
2365 of introducing infinite download loops.
2367 This is the first alpha release in a new series, so expect there to be
2368 bugs. Users who would rather test out a more stable branch should stay
2369 with 0.2.5.x for now.
2371 o New compiler and system requirements:
2372 - Tor 0.2.6.x requires that your compiler support more of the C99
2373 language standard than before. The 'configure' script now detects
2374 whether your compiler supports C99 mid-block declarations and
2375 designated initializers. If it does not, Tor will not compile.
2377 We may revisit this requirement if it turns out that a significant
2378 number of people need to build Tor with compilers that don't
2379 bother implementing a 15-year-old standard. Closes ticket 13233.
2380 - Tor no longer supports systems without threading support. When we
2381 began working on Tor, there were several systems that didn't have
2382 threads, or where the thread support wasn't able to run the
2383 threads of a single process on multiple CPUs. That no longer
2384 holds: every system where Tor needs to run well now has threading
2385 support. Resolves ticket 12439.
2387 o Removed platform support:
2388 - We no longer include special code to build on Windows CE; as far
2389 as we know, nobody has used Tor on Windows CE in a very long time.
2390 Closes ticket 11446.
2392 o Major features (bridges):
2393 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2394 transports if they are configured via the "TOR_PT_PROXY"
2395 environment variable. Implements proposal 232. Resolves
2398 o Major features (client performance, hidden services):
2399 - Allow clients to use optimistic data when connecting to a hidden
2400 service, which should remove a round-trip from hidden service
2401 initialization. See proposal 181 for details. Implements
2404 o Major features (directory system):
2405 - Upon receiving an unparseable directory object, if its digest
2406 matches what we expected, then don't try to download it again.
2407 Previously, when we got a descriptor we didn't like, we would keep
2408 trying to download it over and over. Closes ticket 11243.
2410 o Major features (sample torrc):
2411 - Add a new, infrequently-changed "torrc.minimal". This file is
2412 similar to torrc.sample, but it will change as infrequently as
2413 possible, for the benefit of users whose systems prompt them for
2414 intervention whenever a default configuration file is changed.
2415 Making this change allows us to update torrc.sample to be a more
2416 generally useful "sample torrc".
2418 o Major bugfixes (directory authorities):
2419 - Do not assign the HSDir flag to relays if they are not Valid, or
2420 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2422 o Major bugfixes (directory bandwidth performance):
2423 - Don't flush the zlib buffer aggressively when compressing
2424 directory information for clients. This should save about 7% of
2425 the bandwidth currently used for compressed descriptors and
2426 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2428 o Minor features (security, memory wiping):
2429 - Ensure we securely wipe keys from memory after
2430 crypto_digest_get_digest and init_curve25519_keypair_from_file
2431 have finished using them. Resolves ticket 13477.
2433 o Minor features (security, out-of-memory handling):
2434 - When handling an out-of-memory condition, allocate less memory for
2435 temporary data structures. Fixes issue 10115.
2436 - When handling an out-of-memory condition, consider more types of
2437 buffers, including those on directory connections, and zlib
2438 buffers. Resolves ticket 11792.
2441 - When identity keypair is generated for first time, log a
2442 congratulatory message that links to the new relay lifecycle
2443 document. Implements feature 10427.
2445 o Minor features (client):
2446 - Clients are now willing to send optimistic data (before they
2447 receive a 'connected' cell) to relays of any version. (Relays
2448 without support for optimistic data are no longer supported on the
2449 Tor network.) Resolves ticket 13153.
2451 o Minor features (directory authorities):
2452 - Don't list relays with a bandwidth estimate of 0 in the consensus.
2453 Implements a feature proposed during discussion of bug 13000.
2454 - In tor-gencert, report an error if the user provides the same
2455 argument more than once.
2456 - If a directory authority can't find a best consensus method in the
2457 votes that it holds, it now falls back to its favorite consensus
2458 method. Previously, it fell back to method 1. Neither of these is
2459 likely to get enough signatures, but "fall back to favorite"
2460 doesn't require us to maintain support an obsolete consensus
2461 method. Implements part of proposal 215.
2463 o Minor features (logging):
2464 - On Unix-like systems, you can now use named pipes as the target of
2465 the Log option, and other options that try to append to files.
2466 Closes ticket 12061. Patch from "carlo von lynX".
2467 - When opening a log file at startup, send it every log message that
2468 we generated between startup and opening it. Previously, log
2469 messages that were generated before opening the log file were only
2470 logged to stdout. Closes ticket 6938.
2471 - Add a TruncateLogFile option to overwrite logs instead of
2472 appending to them. Closes ticket 5583.
2474 o Minor features (portability, Solaris):
2475 - Threads are no longer disabled by default on Solaris; we believe
2476 that the versions of Solaris with broken threading support are all
2477 obsolete by now. Resolves ticket 9495.
2479 o Minor features (relay):
2480 - Re-check our address after we detect a changed IP address from
2481 getsockname(). This ensures that the controller command "GETINFO
2482 address" will report the correct value. Resolves ticket 11582.
2484 - A new AccountingRule option lets Relays set whether they'd like
2485 AccountingMax to be applied separately to inbound and outbound
2486 traffic, or applied to the sum of inbound and outbound traffic.
2487 Resolves ticket 961. Patch by "chobe".
2489 o Minor features (testing networks):
2490 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
2491 the "Exit" flag regardless of their uptime, bandwidth, or exit
2492 policy. TestingTorNetwork must be set for this option to have any
2493 effect. Previously, authorities would take up to 35 minutes to
2494 give nodes the Exit flag in a test network. Partially implements
2497 o Minor features (validation):
2498 - Check all date/time values passed to tor_timegm and
2499 parse_rfc1123_time for validity, taking leap years into account.
2500 Improves HTTP header validation. Implemented with bug 13476.
2501 - In correct_tm(), limit the range of values returned by system
2502 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
2503 This means we don't have to deal with negative or too large dates,
2504 even if a clock is wrong. Otherwise we might fail to read a file
2505 written by us which includes such a date. Fixes bug 13476.
2507 o Minor bugfixes (bridge clients):
2508 - When configured to use a bridge without an identity digest (not
2509 recommended), avoid launching an extra channel to it when
2510 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
2512 o Minor bugfixes (bridges):
2513 - When DisableNetwork is set, do not launch pluggable transport
2514 plugins, and if any are running, terminate them. Fixes bug 13213;
2515 bugfix on 0.2.3.6-alpha.
2517 o Minor bugfixes (C correctness):
2518 - Fix several instances of possible integer overflow/underflow/NaN.
2519 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
2521 - In circuit_build_times_calculate_timeout() in circuitstats.c,
2522 avoid dividing by zero in the pareto calculations. This traps
2523 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2525 - Fix an integer overflow in format_time_interval(). Fixes bug
2526 13393; bugfix on 0.2.0.10-alpha.
2527 - Set the correct day of year value when the system's localtime(_r)
2528 or gmtime(_r) functions fail to set struct tm. Not externally
2529 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2530 - Avoid unlikely signed integer overflow in tor_timegm on systems
2531 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2533 o Minor bugfixes (client):
2534 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2535 BadExit flag are not considered worthy candidates. Fixes bug
2536 13066; bugfix on 0.1.2.3-alpha.
2537 - Use the consensus schedule for downloading consensuses, and not
2538 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2539 - Handle unsupported or malformed SOCKS5 requests properly by
2540 responding with the appropriate error message before closing the
2541 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2543 o Minor bugfixes (client, torrc):
2544 - Stop modifying the value of our DirReqStatistics torrc option just
2545 because we're not a bridge or relay. This bug was causing Tor
2546 Browser users to write "DirReqStatistics 0" in their torrc files
2547 as if they had chosen to change the config. Fixes bug 4244; bugfix
2549 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
2550 that our options have changed every time we SIGHUP. Fixes bug
2551 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
2553 o Minor bugfixes (controller):
2554 - Return an error when the second or later arguments of the
2555 "setevents" controller command are invalid events. Previously we
2556 would return success while silently skipping invalid events. Fixes
2557 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
2559 o Minor bugfixes (directory system):
2560 - Always believe that v3 directory authorities serve extra-info
2561 documents, whether they advertise "caches-extra-info" or not.
2562 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2563 - When running as a v3 directory authority, advertise that you serve
2564 extra-info documents so that clients who want them can find them
2565 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2566 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
2567 Previously, directories offering BRIDGE_DIRINFO and some other
2568 flag (i.e. microdescriptors or extrainfo) would be ignored when
2569 looking for bridges. Partially fixes bug 13163; bugfix
2572 o Minor bugfixes (networking):
2573 - Check for orconns and use connection_or_close_for_error() rather
2574 than connection_mark_for_close() directly in the getsockopt()
2575 failure case of connection_handle_write_impl(). Fixes bug 11302;
2576 bugfix on 0.2.4.4-alpha.
2578 o Minor bugfixes (relay):
2579 - When generating our family list, remove spaces from around the
2580 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
2581 - If our previous bandwidth estimate was 0 bytes, allow publishing a
2582 new relay descriptor immediately. Fixes bug 13000; bugfix
2585 o Minor bugfixes (testing networks):
2586 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
2587 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
2588 - Stop using the default authorities in networks which provide both
2589 AlternateDirAuthority and AlternateBridgeAuthority. Partially
2590 fixes bug 13163; bugfix on 0.2.0.13-alpha.
2592 o Minor bugfixes (testing):
2593 - Stop spawn test failures due to a race condition between the
2594 SIGCHLD handler updating the process status, and the test reading
2595 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
2597 o Minor bugfixes (testing, Windows):
2598 - Avoid passing an extra backslash when creating a temporary
2599 directory for running the unit tests on Windows. Fixes bug 12392;
2600 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
2602 o Minor bugfixes (windows):
2603 - Remove code to special-case handling of NTE_BAD_KEYSET when
2604 acquiring windows CryptoAPI context. This error can't actually
2605 occur for the parameters we're providing. Fixes bug 10816; bugfix
2608 o Minor bugfixes (zlib):
2609 - Avoid truncating a zlib stream when trying to finalize it with an
2610 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
2613 - Allow our configure script to build correctly with autoconf 2.62
2614 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
2615 - Improve the error message from ./configure to make it clear that
2616 when asciidoc has not been found, the user will have to either add
2617 --disable-asciidoc argument or install asciidoc. Resolves
2620 o Code simplification and refactoring:
2621 - Change the entry_is_live() function to take named bitfield
2622 elements instead of an unnamed list of booleans. Closes
2624 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
2625 Resolves ticket 12205.
2626 - Use calloc and reallocarray functions instead of multiply-
2627 then-malloc. This makes it less likely for us to fall victim to an
2628 integer overflow attack when allocating. Resolves ticket 12855.
2629 - Use the standard macro name SIZE_MAX, instead of our
2631 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
2632 functions which take them as arguments. Replace 0 with NO_DIRINFO
2633 in a function call for clarity. Seeks to prevent future issues
2635 - Avoid 4 null pointer errors under clang static analysis by using
2636 tor_assert() to prove that the pointers aren't null. Fixes
2638 - Rework the API of policies_parse_exit_policy() to use a bitmask to
2639 represent parsing options, instead of a confusing mess of
2640 booleans. Resolves ticket 8197.
2641 - Introduce a helper function to parse ExitPolicy in
2642 or_options_t structure.
2645 - Add a doc/TUNING document with tips for handling large numbers of
2646 TCP connections when running busy Tor relay. Update the warning
2647 message to point to this file when running out of sockets
2648 operating system is allowing to use simultaneously. Resolves
2652 - We no longer remind the user about configuration options that have
2653 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
2654 - Remove our old, non-weighted bandwidth-based node selection code.
2655 Previously, we used it as a fallback when we couldn't perform
2656 weighted bandwidth-based node selection. But that would only
2657 happen in the cases where we had no consensus, or when we had a
2658 consensus generated by buggy or ancient directory authorities. In
2659 either case, it's better to use the more modern, better maintained
2660 algorithm, with reasonable defaults for the weights. Closes
2662 - Remove the --disable-curve25519 configure option. Relays and
2663 clients now are required to support curve25519 and the
2665 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
2666 used to be deprecated synonyms for "StrictNodes", are now marked
2667 obsolete. Resolves ticket 12226.
2668 - Clients don't understand the BadDirectory flag in the consensus
2669 anymore, and ignore it.
2672 - Refactor the function that chooses guard nodes so that it can more
2673 easily be tested; write some tests for it.
2674 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
2675 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
2676 - Create unit tests for format_time_interval(). With bug 13393.
2677 - Add unit tests for tor_timegm signed overflow, tor_timegm and
2678 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
2679 tests (visible) fixes in bug 13476.
2680 - Add a "coverage-html" make target to generate HTML-visualized
2681 coverage results when building with --enable-coverage. (Requires
2682 lcov.) Patch from Kevin Murray.
2683 - Enable the backtrace handler (where supported) when running the
2685 - Revise all unit tests that used the legacy test_* macros to
2686 instead use the recommended tt_* macros. This patch was generated
2687 with coccinelle, to avoid manual errors. Closes ticket 13119.
2689 o Distribution (systemd):
2690 - systemd unit file: only allow tor to write to /var/lib/tor and
2691 /var/log/tor. The rest of the filesystem is accessible for reading
2692 only. Patch by intrigeri; resolves ticket 12751.
2693 - systemd unit file: ensure that the process and all its children
2694 can never gain new privileges. Patch by intrigeri; resolves
2696 - systemd unit file: set up /var/run/tor as writable for the Tor
2697 service. Patch by intrigeri; resolves ticket 13196.
2699 o Removed features (directory authorities):
2700 - Remove code that prevented authorities from listing Tor relays
2701 affected by CVE-2011-2769 as guards. These relays are already
2702 rejected altogether due to the minimum version requirement of
2703 0.2.3.16-alpha. Closes ticket 13152.
2704 - The "AuthDirRejectUnlisted" option no longer has any effect, as
2705 the fingerprints file (approved-routers) has been deprecated.
2706 - Directory authorities do not support being Naming dirauths anymore.
2707 The "NamingAuthoritativeDir" config option is now obsolete.
2708 - Directory authorities do not support giving out the BadDirectory
2710 - Directory authorities no longer advertise or support consensus
2711 methods 1 through 12 inclusive. These consensus methods were
2712 obsolete and/or insecure: maintaining the ability to support them
2713 served no good purpose. Implements part of proposal 215; closes
2716 o Testing (test-network.sh):
2717 - Stop using "echo -n", as some shells' built-in echo doesn't
2718 support "-n". Instead, use "/bin/echo -n". Partially fixes
2720 - Stop an apparent test-network hang when used with make -j2. Fixes
2722 - Add a --delay option to test-network.sh, which configures the
2723 delay before the chutney network tests for data transmission.
2724 Partially implements ticket 13161.
2727 Changes in version 0.2.5.10 - 2014-10-24
2728 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
2730 It adds several new security features, including improved
2731 denial-of-service resistance for relays, new compiler hardening
2732 options, and a system-call sandbox for hardened installations on Linux
2733 (requires seccomp2). The controller protocol has several new features,
2734 resolving IPv6 addresses should work better than before, and relays
2735 should be a little more CPU-efficient. We've added support for more
2736 OpenBSD and FreeBSD transparent proxy types. We've improved the build
2737 system and testing infrastructure to allow unit testing of more parts
2738 of the Tor codebase. Finally, we've addressed several nagging pluggable
2739 transport usability issues, and included numerous other small bugfixes
2740 and features mentioned below.
2742 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
2743 have accumulated many known flaws; everyone should upgrade.
2745 o Deprecated versions:
2746 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
2747 attention for some while.
2750 Changes in version 0.2.5.9-rc - 2014-10-20
2751 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
2752 series. It disables SSL3 in response to the recent "POODLE" attack
2753 (even though POODLE does not affect Tor). It also works around a crash
2754 bug caused by some operating systems' response to the "POODLE" attack
2755 (which does affect Tor). It also contains a few miscellaneous fixes.
2757 o Major security fixes:
2758 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2759 today support TLS 1.0 or later, so we can safely turn off support
2760 for this old (and insecure) protocol. Fixes bug 13426.
2762 o Major bugfixes (openssl bug workaround):
2763 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2764 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2765 13471. This is a workaround for an OpenSSL bug.
2768 - Disable the sandbox name resolver cache when running tor-resolve:
2769 tor-resolve doesn't use the sandbox code, and turning it on was
2770 breaking attempts to do tor-resolve on a non-default server on
2771 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
2773 o Compilation fixes:
2774 - Build and run correctly on systems like OpenBSD-current that have
2775 patched OpenSSL to remove get_cipher_by_char and/or its
2776 implementations. Fixes issue 13325.
2778 o Downgraded warnings:
2779 - Downgrade the severity of the 'unexpected sendme cell from client'
2780 from 'warn' to 'protocol warning'. Closes ticket 8093.
2783 Changes in version 0.2.4.25 - 2014-10-20
2784 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2785 (even though POODLE does not affect Tor). It also works around a crash
2786 bug caused by some operating systems' response to the "POODLE" attack
2787 (which does affect Tor).
2789 o Major security fixes (also in 0.2.5.9-rc):
2790 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2791 today support TLS 1.0 or later, so we can safely turn off support
2792 for this old (and insecure) protocol. Fixes bug 13426.
2794 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2795 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2796 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2797 13471. This is a workaround for an OpenSSL bug.
2800 Changes in version 0.2.5.8-rc - 2014-09-22
2801 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
2802 series. It fixes a bug that affects consistency and speed when
2803 connecting to hidden services, and it updates the location of one of
2804 the directory authorities.
2807 - Clients now send the correct address for their chosen rendezvous
2808 point when trying to access a hidden service. They used to send
2809 the wrong address, which would still work some of the time because
2810 they also sent the identity digest of the rendezvous point, and if
2811 the hidden service happened to try connecting to the rendezvous
2812 point from a relay that already had a connection open to it,
2813 the relay would reuse that connection. Now connections to hidden
2814 services should be more robust and faster. Also, this bug meant
2815 that clients were leaking to the hidden service whether they were
2816 on a little-endian (common) or big-endian (rare) system, which for
2817 some users might have reduced their anonymity. Fixes bug 13151;
2818 bugfix on 0.2.1.5-alpha.
2820 o Directory authority changes:
2821 - Change IP address for gabelmoo (v3 directory authority).
2824 Changes in version 0.2.4.24 - 2014-09-22
2825 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2826 connecting to hidden services, and it updates the location of one of
2827 the directory authorities.
2830 - Clients now send the correct address for their chosen rendezvous
2831 point when trying to access a hidden service. They used to send
2832 the wrong address, which would still work some of the time because
2833 they also sent the identity digest of the rendezvous point, and if
2834 the hidden service happened to try connecting to the rendezvous
2835 point from a relay that already had a connection open to it,
2836 the relay would reuse that connection. Now connections to hidden
2837 services should be more robust and faster. Also, this bug meant
2838 that clients were leaking to the hidden service whether they were
2839 on a little-endian (common) or big-endian (rare) system, which for
2840 some users might have reduced their anonymity. Fixes bug 13151;
2841 bugfix on 0.2.1.5-alpha.
2843 o Directory authority changes:
2844 - Change IP address for gabelmoo (v3 directory authority).
2846 o Minor features (geoip):
2847 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2851 Changes in version 0.2.5.7-rc - 2014-09-11
2852 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
2853 release series, and some long-standing bugs related to ORPort reachability
2854 testing and failure to send CREATE cells. It is the first release
2855 candidate for the Tor 0.2.5.x series.
2857 o Major bugfixes (client, startup):
2858 - Start making circuits as soon as DisabledNetwork is turned off.
2859 When Tor started with DisabledNetwork set, it would correctly
2860 conclude that it shouldn't build circuits, but it would mistakenly
2861 cache this conclusion, and continue believing it even when
2862 DisableNetwork is set to 0. Fixes the bug introduced by the fix
2863 for bug 11200; bugfix on 0.2.5.4-alpha.
2864 - Resume expanding abbreviations for command-line options. The fix
2865 for bug 4647 accidentally removed our hack from bug 586 that
2866 rewrote HashedControlPassword to __HashedControlSessionPassword
2867 when it appears on the commandline (which allowed the user to set
2868 her own HashedControlPassword in the torrc file while the
2869 controller generates a fresh session password for each run). Fixes
2870 bug 12948; bugfix on 0.2.5.1-alpha.
2871 - Warn about attempts to run hidden services and relays in the same
2872 process: that's probably not a good idea. Closes ticket 12908.
2874 o Major bugfixes (relay):
2875 - Avoid queuing or sending destroy cells for circuit ID zero when we
2876 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2877 Found and fixed by "cypherpunks".
2878 - Fix ORPort reachability detection on relays running behind a
2879 proxy, by correctly updating the "local" mark on the controlling
2880 channel when changing the address of an or_connection_t after the
2881 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2883 o Minor features (bridge):
2884 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2885 cookie file for the ExtORPort g+r by default.
2887 o Minor features (geoip):
2888 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2891 o Minor bugfixes (logging):
2892 - Reduce the log severity of the "Pluggable transport proxy does not
2893 provide any needed transports and will not be launched." message,
2894 since Tor Browser includes several ClientTransportPlugin lines in
2895 its torrc-defaults file, leading every Tor Browser user who looks
2896 at her logs to see these notices and wonder if they're dangerous.
2897 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
2898 - Downgrade "Unexpected onionskin length after decryption" warning
2899 to a protocol-warn, since there's nothing relay operators can do
2900 about a client that sends them a malformed create cell. Resolves
2901 bug 12996; bugfix on 0.0.6rc1.
2902 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2903 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2904 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2905 their names correctly. Fixes part of bug 12700; bugfix
2907 - When logging information about a relay cell whose command we don't
2908 recognize, log its command as an integer. Fixes part of bug 12700;
2909 bugfix on 0.2.1.10-alpha.
2910 - Escape all strings from the directory connection before logging
2911 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2913 o Minor bugfixes (controller):
2914 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
2915 bug 12864; bugfix on 0.2.5.1-alpha.
2916 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
2917 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
2920 o Minor bugfixes (compilation):
2921 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
2922 bugfix on 0.2.5.5-alpha.
2923 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
2924 0.2.5.1-alpha. Patch from "NewEraCracker".
2925 - In routerlist_assert_ok(), don't take the address of a
2926 routerinfo's cache_info member unless that routerinfo is non-NULL.
2927 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2928 - Fix a large number of false positive warnings from the clang
2929 analyzer static analysis tool. This should make real warnings
2930 easier for clang analyzer to find. Patch from "teor". Closes
2933 o Distribution (systemd):
2934 - Verify configuration file via ExecStartPre in the systemd unit
2935 file. Patch from intrigeri; resolves ticket 12730.
2936 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2937 current systemd unit uses "Type = simple", so systemd does not
2938 expect tor to fork. If the user has "RunAsDaemon 1" in their
2939 torrc, then things won't work as expected. This is e.g. the case
2940 on Debian (and derivatives), since there we pass "--defaults-torrc
2941 /usr/share/tor/tor-service-defaults-torrc" (that contains
2942 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2946 - Adjust the URLs in the README to refer to the new locations of
2947 several documents on the website. Fixes bug 12830. Patch from
2949 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2953 Changes in version 0.2.5.6-alpha - 2014-07-28
2954 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
2955 risk from guard rotation, and fixes a variety of other issues to get
2956 us closer to a release candidate.
2958 o Major features (also in 0.2.4.23):
2959 - Make the number of entry guards configurable via a new
2960 NumEntryGuards consensus parameter, and the number of directory
2961 guards configurable via a new NumDirectoryGuards consensus
2962 parameter. Implements ticket 12688.
2964 o Major bugfixes (also in 0.2.4.23):
2965 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2966 implementation that caused incorrect results on 32-bit
2967 implementations when certain malformed inputs were used along with
2968 a small class of private ntor keys. This bug does not currently
2969 appear to allow an attacker to learn private keys or impersonate a
2970 Tor server, but it could provide a means to distinguish 32-bit Tor
2971 implementations from 64-bit Tor implementations. Fixes bug 12694;
2972 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2976 - Perform circuit cleanup operations even when circuit
2977 construction operations are disabled (because the network is
2978 disabled, or because there isn't enough directory information).
2979 Previously, when we were not building predictive circuits, we
2980 were not closing expired circuits either. Fixes bug 8387; bugfix on
2981 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2982 became more strict about when we have "enough directory information
2986 - Authorities now assign the Guard flag to the fastest 25% of the
2987 network (it used to be the fastest 50%). Also raise the consensus
2988 weight that guarantees the Guard flag from 250 to 2000. For the
2989 current network, this results in about 1100 guards, down from 2500.
2990 This step paves the way for moving the number of entry guards
2991 down to 1 (proposal 236) while still providing reasonable expected
2992 performance for most users. Implements ticket 12690.
2993 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2995 - Slightly enhance the diagnostic message for bug 12184.
2997 o Minor bugfixes (also in 0.2.4.23):
2998 - Warn and drop the circuit if we receive an inbound 'relay early'
2999 cell. Those used to be normal to receive on hidden service circuits
3000 due to bug 1038, but the buggy Tor versions are long gone from
3001 the network so we can afford to resume watching for them. Resolves
3002 the rest of bug 1038; bugfix on 0.2.1.19.
3003 - Correct a confusing error message when trying to extend a circuit
3004 via the control protocol but we don't know a descriptor or
3005 microdescriptor for one of the specified relays. Fixes bug 12718;
3006 bugfix on 0.2.3.1-alpha.
3009 - Fix compilation when building with bufferevents enabled. (This
3010 configuration is still not expected to work, however.)
3011 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
3012 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
3014 - Compile correctly with builds and forks of OpenSSL (such as
3015 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
3016 0.2.1.1-alpha. Patch from "dhill".
3019 Changes in version 0.2.4.23 - 2014-07-28
3020 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3021 guard rotation, and also backports several important fixes from the
3022 Tor 0.2.5 alpha release series.
3025 - Clients now look at the "usecreatefast" consensus parameter to
3026 decide whether to use CREATE_FAST or CREATE cells for the first hop
3027 of their circuit. This approach can improve security on connections
3028 where Tor's circuit handshake is stronger than the available TLS
3029 connection security levels, but the tradeoff is more computational
3030 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3031 - Make the number of entry guards configurable via a new
3032 NumEntryGuards consensus parameter, and the number of directory
3033 guards configurable via a new NumDirectoryGuards consensus
3034 parameter. Implements ticket 12688.
3037 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3038 implementation that caused incorrect results on 32-bit
3039 implementations when certain malformed inputs were used along with
3040 a small class of private ntor keys. This bug does not currently
3041 appear to allow an attacker to learn private keys or impersonate a
3042 Tor server, but it could provide a means to distinguish 32-bit Tor
3043 implementations from 64-bit Tor implementations. Fixes bug 12694;
3044 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3048 - Warn and drop the circuit if we receive an inbound 'relay early'
3049 cell. Those used to be normal to receive on hidden service circuits
3050 due to bug 1038, but the buggy Tor versions are long gone from
3051 the network so we can afford to resume watching for them. Resolves
3052 the rest of bug 1038; bugfix on 0.2.1.19.
3053 - Correct a confusing error message when trying to extend a circuit
3054 via the control protocol but we don't know a descriptor or
3055 microdescriptor for one of the specified relays. Fixes bug 12718;
3056 bugfix on 0.2.3.1-alpha.
3057 - Avoid an illegal read from stack when initializing the TLS
3058 module using a version of OpenSSL without all of the ciphers
3059 used by the v2 link handshake. Fixes bug 12227; bugfix on
3060 0.2.4.8-alpha. Found by "starlight".
3063 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3067 Changes in version 0.2.5.5-alpha - 2014-06-18
3068 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
3069 0.2.5.x release series, including a couple of DoS issues, some
3070 performance regressions, a large number of bugs affecting the Linux
3071 seccomp2 sandbox code, and various other bugfixes. It also adds
3072 diagnostic bugfixes for a few tricky issues that we're trying to
3075 o Major features (security, traffic analysis resistance):
3076 - Several major improvements to the algorithm used to decide when to
3077 close TLS connections. Previous versions of Tor closed connections
3078 at a fixed interval after the last time a non-padding cell was
3079 sent over the connection, regardless of the target of the
3080 connection. Now, we randomize the intervals by adding up to 50% of
3081 their base value, we measure the length of time since connection
3082 last had at least one circuit, and we allow connections to known
3083 ORs to remain open a little longer (15 minutes instead of 3
3084 minutes minimum). These changes should improve Tor's resistance
3085 against some kinds of traffic analysis, and lower some overhead
3086 from needlessly closed connections. Fixes ticket 6799.
3087 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
3089 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
3090 - Fix a memory leak that could occur if a microdescriptor parse
3091 fails during the tokenizing step. This bug could enable a memory
3092 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3095 o Major bugfixes (security, directory authorities):
3096 - Directory authorities now include a digest of each relay's
3097 identity key as a part of its microdescriptor.
3099 This is a workaround for bug 11743 (reported by "cypherpunks"),
3100 where Tor clients do not support receiving multiple
3101 microdescriptors with the same SHA256 digest in the same
3102 consensus. When clients receive a consensus like this, they only
3103 use one of the relays. Without this fix, a hostile relay could
3104 selectively disable some client use of target relays by
3105 constructing a router descriptor with a different identity and the
3106 same microdescriptor parameters and getting the authorities to
3107 list it in a microdescriptor consensus. This fix prevents an
3108 attacker from causing a microdescriptor collision, because the
3109 router's identity is not forgeable.
3111 o Major bugfixes (relay):
3112 - Use a direct dirport connection when uploading non-anonymous
3113 descriptors to the directory authorities. Previously, relays would
3114 incorrectly use tunnel connections under a fairly wide variety of
3115 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
3116 - When a circuit accidentally has the same circuit ID for its
3117 forward and reverse direction, correctly detect the direction of
3118 cells using that circuit. Previously, this bug made roughly one
3119 circuit in a million non-functional. Fixes bug 12195; this is a
3120 bugfix on every version of Tor.
3122 o Major bugfixes (client, pluggable transports):
3123 - When managing pluggable transports, use OS notification facilities
3124 to learn if they have crashed, and don't attempt to kill any
3125 process that has already exited. Fixes bug 8746; bugfix
3128 o Minor features (diagnostic):
3129 - When logging a warning because of bug 7164, additionally check the
3130 hash table for consistency (as proposed on ticket 11737). This may
3131 help diagnose bug 7164.
3132 - When we log a heartbeat, log how many one-hop circuits we have
3133 that are at least 30 minutes old, and log status information about
3134 a few of them. This is an attempt to track down bug 8387.
3135 - When encountering an unexpected CR while writing text to a file on
3136 Windows, log the name of the file. Should help diagnosing
3138 - Give more specific warnings when a client notices that an onion
3139 handshake has failed. Fixes ticket 9635.
3140 - Add significant new logging code to attempt to diagnose bug 12184,
3141 where relays seem to run out of available circuit IDs.
3142 - Improve the diagnostic log message for bug 8387 even further to
3143 try to improve our odds of figuring out why one-hop directory
3144 circuits sometimes do not get closed.
3146 o Minor features (security, memory management):
3147 - Memory allocation tricks (mempools and buffer freelists) are now
3148 disabled by default. You can turn them back on with
3149 --enable-mempools and --enable-buf-freelists respectively. We're
3150 disabling these features because malloc performance is good enough
3151 on most platforms, and a similar feature in OpenSSL exacerbated
3152 exploitation of the Heartbleed attack. Resolves ticket 11476.
3154 o Minor features (security):
3155 - Apply the secure SipHash-2-4 function to the hash table mapping
3156 circuit IDs and channels to circuits. We missed this one when we
3157 were converting all the other hash functions to use SipHash back
3158 in 0.2.5.3-alpha. Resolves ticket 11750.
3160 o Minor features (build):
3161 - The configure script has a --disable-seccomp option to turn off
3162 support for libseccomp on systems that have it, in case it (or
3163 Tor's use of it) is broken. Resolves ticket 11628.
3165 o Minor features (other):
3166 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
3169 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
3170 - When running a hidden service, do not allow TunneledDirConns 0;
3171 this will keep the hidden service from running, and also
3172 make it publish its descriptors directly over HTTP. Fixes bug 10849;
3173 bugfix on 0.2.1.1-alpha.
3175 o Minor bugfixes (performance):
3176 - Avoid a bug where every successful connection made us recompute
3177 the flag telling us whether we have sufficient information to
3178 build circuits. Previously, we would forget our cached value
3179 whenever we successfully opened a channel (or marked a router as
3180 running or not running for any other reason), regardless of
3181 whether we had previously believed the router to be running. This
3182 forced us to run an expensive update operation far too often.
3183 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
3184 - Avoid using tor_memeq() for checking relay cell integrity. This
3185 removes a possible performance bottleneck. Fixes part of bug
3186 12169; bugfix on 0.2.1.31.
3188 o Minor bugfixes (compilation):
3189 - Fix compilation of test_status.c when building with MVSC. Bugfix
3190 on 0.2.5.4-alpha. Patch from Gisle Vanem.
3191 - Resolve GCC complaints on OpenBSD about discarding constness in
3192 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
3193 on 0.1.1.23. Patch from Dana Koch.
3194 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
3195 treatment of long and time_t as comparable types. Fixes part of
3196 bug 11633. Patch from Dana Koch.
3197 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
3198 11623; bugfix on 0.2.5.3-alpha.
3199 - When deciding whether to build the 64-bit curve25519
3200 implementation, detect platforms where we can compile 128-bit
3201 arithmetic but cannot link it. Fixes bug 11729; bugfix on
3202 0.2.4.8-alpha. Patch from "conradev".
3203 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
3204 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
3205 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
3208 o Minor bugfixes (Directory server):
3209 - When sending a compressed set of descriptors or microdescriptors,
3210 make sure to finalize the zlib stream. Previously, we would write
3211 all the compressed data, but if the last descriptor we wanted to
3212 send was missing or too old, we would not mark the stream as
3213 finished. This caused problems for decompression tools. Fixes bug
3214 11648; bugfix on 0.1.1.23.
3216 o Minor bugfixes (Linux seccomp sandbox):
3217 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
3218 11622; bugfix on 0.2.5.1-alpha.
3219 - Avoid crashing when re-opening listener ports with the seccomp
3220 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
3221 - Avoid crashing with the seccomp sandbox enabled along with
3222 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
3223 - When we receive a SIGHUP with the sandbox enabled, correctly
3224 support rotating our log files. Fixes bug 12032; bugfix
3226 - Avoid crash when running with sandboxing enabled and
3227 DirReqStatistics not disabled. Fixes bug 12035; bugfix
3229 - Fix a "BUG" warning when trying to write bridge-stats files with
3230 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
3232 - Prevent the sandbox from crashing on startup when run with the
3233 --enable-expensive-hardening configuration option. Fixes bug
3234 11477; bugfix on 0.2.5.4-alpha.
3235 - When running with DirPortFrontPage and sandboxing both enabled,
3236 reload the DirPortFrontPage correctly when restarting. Fixes bug
3237 12028; bugfix on 0.2.5.1-alpha.
3238 - Don't try to enable the sandbox when using the Tor binary to check
3239 its configuration, hash a passphrase, or so on. Doing so was
3240 crashing on startup for some users. Fixes bug 11609; bugfix
3242 - Avoid warnings when running with sandboxing and node statistics
3243 enabled at the same time. Fixes part of 12064; bugfix on
3244 0.2.5.1-alpha. Patch from Michael Wolf.
3245 - Avoid warnings when running with sandboxing enabled at the same
3246 time as cookie authentication, hidden services, or directory
3247 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
3248 - Do not allow options that require calls to exec to be enabled
3249 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
3250 bug 12043; bugfix on 0.2.5.1-alpha.
3251 - Handle failures in getpwnam()/getpwuid() when running with the
3252 User option set and the Linux syscall sandbox enabled. Fixes bug
3253 11946; bugfix on 0.2.5.1-alpha.
3254 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
3255 to avoid calling getaddrinfo() after installing the sandbox
3256 filters. Previously, it preloaded a cache with the IPv4 address
3257 for our hostname, and nothing else. Now, it loads the cache with
3258 every address that it used to initialize the Tor process. Fixes
3259 bug 11970; bugfix on 0.2.5.1-alpha.
3261 o Minor bugfixes (pluggable transports):
3262 - Enable the ExtORPortCookieAuthFile option, to allow changing the
3263 default location of the authentication token for the extended OR
3264 Port as used by sever-side pluggable transports. We had
3265 implemented this option before, but the code to make it settable
3266 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
3267 - Avoid another 60-second delay when starting Tor in a pluggable-
3268 transport-using configuration when we already have cached
3269 descriptors for our bridges. Fixes bug 11965; bugfix
3272 o Minor bugfixes (client):
3273 - Avoid "Tried to open a socket with DisableNetwork set" warnings
3274 when starting a client with bridges configured and DisableNetwork
3275 set. (Tor launcher starts Tor with DisableNetwork set the first
3276 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
3278 o Minor bugfixes (testing):
3279 - The Python parts of the test scripts now work on Python 3 as well
3280 as Python 2, so systems where '/usr/bin/python' is Python 3 will
3281 no longer have the tests break. Fixes bug 11608; bugfix
3283 - When looking for versions of python that we could run the tests
3284 with, check for "python2.7" and "python3.3"; previously we were
3285 only looking for "python", "python2", and "python3". Patch from
3286 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
3287 - Fix all valgrind warnings produced by the unit tests. There were
3288 over a thousand memory leak warnings previously, mostly produced
3289 by forgetting to free things in the unit test code. Fixes bug
3290 11618, bugfixes on many versions of Tor.
3292 o Minor bugfixes (tor-fw-helper):
3293 - Give a correct log message when tor-fw-helper fails to launch.
3294 (Previously, we would say something like "tor-fw-helper sent us a
3295 string we could not parse".) Fixes bug 9781; bugfix
3298 o Minor bugfixes (relay, threading):
3299 - Check return code on spawn_func() in cpuworker code, so that we
3300 don't think we've spawned a nonworking cpuworker and write junk to
3301 it forever. Fix related to bug 4345; bugfix on all released Tor
3302 versions. Found by "skruffy".
3303 - Use a pthread_attr to make sure that spawn_func() cannot return an
3304 error while at the same time launching a thread. Fix related to
3305 bug 4345; bugfix on all released Tor versions. Reported
3308 o Minor bugfixes (relay, oom prevention):
3309 - Correctly detect the total available system memory. We tried to do
3310 this in 0.2.5.4-alpha, but the code was set up to always return an
3311 error value, even on success. Fixes bug 11805; bugfix
3314 o Minor bugfixes (relay, other):
3315 - We now drop CREATE cells for already-existent circuit IDs and for
3316 zero-valued circuit IDs, regardless of other factors that might
3317 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
3319 - Avoid an illegal read from stack when initializing the TLS module
3320 using a version of OpenSSL without all of the ciphers used by the
3321 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
3323 - When rejecting DATA cells for stream_id zero, still count them
3324 against the circuit's deliver window so that we don't fail to send
3325 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
3327 o Minor bugfixes (logging):
3328 - Fix a misformatted log message about delayed directory fetches.
3329 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
3330 - Squelch a spurious LD_BUG message "No origin circuit for
3331 successful SOCKS stream" in certain hidden service failure cases;
3335 - Include a tor.service file in contrib/dist for use with systemd.
3336 Some distributions will be able to use this file unmodified;
3337 others will need to tweak it, or write their own. Patch from Jamie
3338 Nguyen; resolves ticket 8368.
3341 - Clean up several option names in the manpage to match their real
3342 names, add the missing documentation for a couple of testing and
3343 directory authority options, remove the documentation for a
3344 V2-directory fetching option that no longer exists. Resolves
3346 - Correct the documenation so that it lists the correct directory
3347 for the stats files. (They are in a subdirectory called "stats",
3349 - In the manpage, move more authority-only options into the
3350 directory authority section so that operators of regular directory
3351 caches don't get confused.
3354 - The contrib directory has been sorted and tidied. Before, it was
3355 an unsorted dumping ground for useful and not-so-useful things.
3356 Now, it is divided based on functionality, and the items which
3357 seemed to be nonfunctional or useless have been removed. Resolves
3358 ticket 8966; based on patches from "rl1987".
3361 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
3362 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
3363 - The TunnelDirConns and PreferTunnelledDirConns options no longer
3364 exist; tunneled directory connections have been available since
3365 0.1.2.5-alpha, and turning them off is not a good idea. This is a
3366 brute-force fix for 10849, where "TunnelDirConns 0" would break
3370 Changes in version 0.2.4.22 - 2014-05-16
3371 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3372 alpha release series. These include blocking all authority signing
3373 keys that may have been affected by the OpenSSL "heartbleed" bug,
3374 choosing a far more secure set of TLS ciphersuites by default, closing
3375 a couple of memory leaks that could be used to run a target relay out
3376 of RAM, and several others.
3378 o Major features (security, backport from 0.2.5.4-alpha):
3379 - Block authority signing keys that were used on authorities
3380 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3381 don't have any evidence that these keys _were_ compromised; we're
3382 doing this to be prudent.) Resolves ticket 11464.
3384 o Major bugfixes (security, OOM):
3385 - Fix a memory leak that could occur if a microdescriptor parse
3386 fails during the tokenizing step. This bug could enable a memory
3387 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3390 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3391 - The relay ciphersuite list is now generated automatically based on
3392 uniform criteria, and includes all OpenSSL ciphersuites with
3393 acceptable strength and forward secrecy. Previously, we had left
3394 some perfectly fine ciphersuites unsupported due to omission or
3395 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3396 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3397 - Relays now trust themselves to have a better view than clients of
3398 which TLS ciphersuites are better than others. (Thanks to bug
3399 11513, the relay list is now well-considered, whereas the client
3400 list has been chosen mainly for anti-fingerprinting purposes.)
3401 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3402 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3403 AES128. Resolves ticket 11528.
3404 - Clients now try to advertise the same list of ciphersuites as
3405 Firefox 28. This change enables selection of (fast) GCM
3406 ciphersuites, disables some strange old ciphers, and stops
3407 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3408 Resolves ticket 11438.
3410 o Minor bugfixes (configuration, security):
3411 - When running a hidden service, do not allow TunneledDirConns 0:
3412 trying to set that option together with a hidden service would
3413 otherwise prevent the hidden service from running, and also make
3414 it publish its descriptors directly over HTTP. Fixes bug 10849;
3415 bugfix on 0.2.1.1-alpha.
3417 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3418 - Avoid sending a garbage value to the controller when a circuit is
3419 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3421 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3422 - Stop leaking memory when we successfully resolve a PTR record.
3423 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3425 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3426 - Avoid 60-second delays in the bootstrapping process when Tor is
3427 launching for a second time while using bridges. Fixes bug 9229;
3428 bugfix on 0.2.0.3-alpha.
3430 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3431 - Give the correct URL in the warning message when trying to run a
3432 relay on an ancient version of Windows. Fixes bug 9393.
3434 o Minor bugfixes (compilation):
3435 - Fix a compilation error when compiling with --disable-curve25519.
3436 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3439 - Downgrade the warning severity for the the "md was still
3440 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3441 for trying to diagnose this bug, and the current warning in
3442 earlier versions of tor achieves nothing useful. Addresses warning
3445 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3446 - When we run out of usable circuit IDs on a channel, log only one
3447 warning for the whole channel, and describe how many circuits
3448 there were on the channel. Fixes part of ticket 11553.
3450 o Minor features (security, backport from 0.2.5.4-alpha):
3451 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
3452 leave the default at 8GBytes), to better support Raspberry Pi
3453 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
3455 o Documentation (backport from 0.2.5.4-alpha):
3456 - Correctly document that we search for a system torrc file before
3457 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3461 Changes in version 0.2.5.4-alpha - 2014-04-25
3462 Tor 0.2.5.4-alpha includes several security and performance
3463 improvements for clients and relays, including blacklisting authority
3464 signing keys that were used while susceptible to the OpenSSL
3465 "heartbleed" bug, fixing two expensive functions on busy relays,
3466 improved TLS ciphersuite preference lists, support for run-time
3467 hardening on compilers that support AddressSanitizer, and more work on
3468 the Linux sandbox code.
3470 There are also several usability fixes for clients (especially clients
3471 that use bridges), two new TransPort protocols supported (one on
3472 OpenBSD, one on FreeBSD), and various other bugfixes.
3474 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
3475 have accumulated many known flaws; everyone should upgrade.
3477 o Major features (security):
3478 - If you don't specify MaxMemInQueues yourself, Tor now tries to
3479 pick a good value based on your total system memory. Previously,
3480 the default was always 8 GB. You can still override the default by
3481 setting MaxMemInQueues yourself. Resolves ticket 11396.
3482 - Block authority signing keys that were used on authorities
3483 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3484 don't have any evidence that these keys _were_ compromised; we're
3485 doing this to be prudent.) Resolves ticket 11464.
3487 o Major features (relay performance):
3488 - Speed up server-side lookups of rendezvous and introduction point
3489 circuits by using hashtables instead of linear searches. These
3490 functions previously accounted between 3 and 7% of CPU usage on
3491 some busy relays. Resolves ticket 9841.
3492 - Avoid wasting CPU when extending a circuit over a channel that is
3493 nearly out of circuit IDs. Previously, we would do a linear scan
3494 over possible circuit IDs before finding one or deciding that we
3495 had exhausted our possibilities. Now, we try at most 64 random
3496 circuit IDs before deciding that we probably won't succeed. Fixes
3497 a possible root cause of ticket 11553.
3499 o Major features (seccomp2 sandbox, Linux only):
3500 - The seccomp2 sandbox can now run a test network for multiple hours
3501 without crashing. The sandbox is still experimental, and more bugs
3502 will probably turn up. To try it, enable "Sandbox 1" on a Linux
3503 host. Resolves ticket 11351.
3504 - Strengthen sandbox code: the sandbox can now test the arguments
3505 for rename(), and blocks _sysctl() entirely. Resolves another part
3507 - When the sandbox blocks a system call, it now tries to log a stack
3508 trace before exiting. Resolves ticket 11465.
3510 o Major bugfixes (TLS cipher selection):
3511 - The relay ciphersuite list is now generated automatically based on
3512 uniform criteria, and includes all OpenSSL ciphersuites with
3513 acceptable strength and forward secrecy. Previously, we had left
3514 some perfectly fine ciphersuites unsupported due to omission or
3515 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3516 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3517 - Relays now trust themselves to have a better view than clients of
3518 which TLS ciphersuites are better than others. (Thanks to bug
3519 11513, the relay list is now well-considered, whereas the client
3520 list has been chosen mainly for anti-fingerprinting purposes.)
3521 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3522 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3523 AES128. Resolves ticket 11528.
3524 - Clients now try to advertise the same list of ciphersuites as
3525 Firefox 28. This change enables selection of (fast) GCM
3526 ciphersuites, disables some strange old ciphers, and stops
3527 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3528 Resolves ticket 11438.
3530 o Major bugfixes (bridge client):
3531 - Avoid 60-second delays in the bootstrapping process when Tor is
3532 launching for a second time while using bridges. Fixes bug 9229;
3533 bugfix on 0.2.0.3-alpha.
3535 o Minor features (transparent proxy, *BSD):
3536 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3537 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3538 10267; patch from "yurivict".
3539 - Support OpenBSD's divert-to rules with the pf firewall for
3540 transparent proxy ports. To enable it, set "TransProxyType
3541 pf-divert". This allows Tor to run a TransPort transparent proxy
3542 port on OpenBSD 4.4 or later without root privileges. See the
3543 pf.conf(5) manual page for information on configuring pf to use
3544 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3546 o Minor features (security):
3547 - New --enable-expensive-hardening option to enable security
3548 hardening options that consume nontrivial amounts of CPU and
3549 memory. Right now, this includes AddressSanitizer and UbSan, which
3550 are supported in newer versions of GCC and Clang. Closes ticket
3553 o Minor features (log verbosity):
3554 - Demote the message that we give when a flushing connection times
3555 out for too long from NOTICE to INFO. It was usually meaningless.
3556 Resolves ticket 5286.
3557 - Don't log so many notice-level bootstrapping messages at startup
3558 about downloading descriptors. Previously, we'd log a notice
3559 whenever we learned about more routers. Now, we only log a notice
3560 at every 5% of progress. Fixes bug 9963.
3561 - Warn less verbosely when receiving a malformed
3562 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3563 - When we run out of usable circuit IDs on a channel, log only one
3564 warning for the whole channel, and describe how many circuits
3565 there were on the channel. Fixes part of ticket 11553.
3567 o Minor features (relay):
3568 - If a circuit timed out for at least 3 minutes, check if we have a
3569 new external IP address, and publish a new descriptor with the new
3570 IP address if it changed. Resolves ticket 2454.
3572 o Minor features (controller):
3573 - Make the entire exit policy available from the control port via
3574 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3576 - Because of the fix for ticket 11396, the real limit for memory
3577 usage may no longer match the configured MaxMemInQueues value. The
3578 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3580 o Minor features (bridge client):
3581 - Report a more useful failure message when we can't connect to a
3582 bridge because we don't have the right pluggable transport
3583 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3585 o Minor features (diagnostic):
3586 - Add more log messages to diagnose bug 7164, which causes
3587 intermittent "microdesc_free() called but md was still referenced"
3588 warnings. We now include more information, to figure out why we
3589 might be cleaning a microdescriptor for being too old if it's
3590 still referenced by a live node_t object.
3592 o Minor bugfixes (client, DNSPort):
3593 - When using DNSPort, try to respond to AAAA requests with AAAA
3594 answers. Previously, we hadn't looked at the request type when
3595 deciding which answer type to prefer. Fixes bug 10468; bugfix on
3597 - When receiving a DNS query for an unsupported record type, reply
3598 with no answer rather than with a NOTIMPL error. This behavior
3599 isn't correct either, but it will break fewer client programs, we
3600 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
3603 o Minor bugfixes (exit relay):
3604 - Stop leaking memory when we successfully resolve a PTR record.
3605 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3607 o Minor bugfixes (bridge client):
3608 - Stop accepting bridge lines containing hostnames. Doing so would
3609 cause clients to perform DNS requests on the hostnames, which was
3610 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3611 - Avoid a 60-second delay in the bootstrapping process when a Tor
3612 client with pluggable transports re-reads its configuration at
3613 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
3615 o Minor bugfixes (client, logging during bootstrap):
3616 - Warn only once if we start logging in an unsafe way. Previously,
3617 we complain as many times as we had problems. Fixes bug 9870;
3618 bugfix on 0.2.5.1-alpha.
3619 - Only report the first fatal bootstrap error on a given OR
3620 connection. This stops us from telling the controller bogus error
3621 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
3622 - Be more helpful when trying to run sandboxed on Linux without
3623 libseccomp. Instead of saying "Sandbox is not implemented on this
3624 platform", we now explain that we need to be built with
3625 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
3626 - Avoid generating spurious warnings when starting with
3627 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
3630 o Minor bugfixes (closing OR connections):
3631 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
3632 check if it's an or_connection_t and correctly call
3633 connection_or_close_for_error() rather than
3634 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
3636 - When closing all connections on setting DisableNetwork to 1, use
3637 connection_or_close_normally() rather than closing OR connections
3638 out from under the channel layer. Fixes bug 11306; bugfix on
3641 o Minor bugfixes (controller):
3642 - Avoid sending a garbage value to the controller when a circuit is
3643 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3645 o Minor bugfixes (tor-fw-helper):
3646 - Allow tor-fw-helper to build again by adding src/ext to its
3647 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
3649 o Minor bugfixes (bridges):
3650 - Avoid potential crashes or bad behavior when launching a
3651 server-side managed proxy with ORPort or ExtORPort temporarily
3652 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3654 o Minor bugfixes (platform-specific):
3655 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
3656 bug 11426; bugfix on 0.2.5.3-alpha.
3657 - When dumping a malformed directory object to disk, save it in
3658 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
3660 - Don't report failures from make_socket_reuseable() on incoming
3661 sockets on OSX: this can happen when incoming connections close
3662 early. Fixes bug 10081.
3664 o Minor bugfixes (trivial memory leaks):
3665 - Fix a small memory leak when signing a directory object. Fixes bug
3666 11275; bugfix on 0.2.4.13-alpha.
3667 - Free placeholder entries in our circuit table at exit; fixes a
3668 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
3669 - Don't re-initialize a second set of OpenSSL mutexes when starting
3670 up. Previously, we'd make one set of mutexes, and then immediately
3671 replace them with another. Fixes bug 11726; bugfix on
3673 - Resolve some memory leaks found by coverity in the unit tests, on
3674 exit in tor-gencert, and on a failure to compute digests for our
3675 own keys when generating a v3 networkstatus vote. These leaks
3676 should never have affected anyone in practice.
3678 o Minor bugfixes (hidden service):
3679 - Only retry attempts to connect to a chosen rendezvous point 8
3680 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
3682 o Minor bugfixes (misc code correctness):
3683 - Fix various instances of undefined behavior in channeltls.c,
3684 tor_memmem(), and eventdns.c that would cause us to construct
3685 pointers to memory outside an allocated object. (These invalid
3686 pointers were not accessed, but C does not even allow them to
3687 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
3688 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
3689 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
3690 fix some miscellaneous errors in our tests and codebase. Fixes bug
3691 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
3692 - Always check return values for unlink, munmap, UnmapViewOfFile;
3693 check strftime return values more often. In some cases all we can
3694 do is report a warning, but this may help prevent deeper bugs from
3695 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
3697 - Fix numerous warnings from the clang "scan-build" static analyzer.
3698 Some of these are programming style issues; some of them are false
3699 positives that indicated awkward code; some are undefined behavior
3700 cases related to constructing (but not using) invalid pointers;
3701 some are assumptions about API behavior; some are (harmlessly)
3702 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
3703 correct; and one or two are genuine bugs that weren't reachable
3704 from the rest of the program. Fixes bug 8793; bugfixes on many,
3708 - Build the torify.1 manpage again. Previously, we were only trying
3709 to build it when also building tor-fw-helper. That's why we didn't
3710 notice that we'd broken the ability to build it. Fixes bug 11321;
3711 bugfix on 0.2.5.1-alpha.
3712 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
3713 11061; bugfix on 0.2.4.7-alpha.
3714 - Correctly document that we search for a system torrc file before
3715 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3717 - Resolve warnings from Doxygen.
3719 o Code simplifications and refactoring:
3720 - Remove is_internal_IP() function. Resolves ticket 4645.
3721 - Remove unused function circuit_dump_by_chan from circuitlist.c.
3722 Closes issue 9107; patch from "marek".
3723 - Change our use of the ENUM_BF macro to avoid declarations that
3726 o Deprecated versions:
3727 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
3728 attention for some while. Directory authorities no longer accept
3729 descriptors from relays running any version of Tor prior to Tor
3730 0.2.3.16-alpha. Resolves ticket 11149.
3733 - New macros in test.h to simplify writing mock-functions for unit
3734 tests. Part of ticket 11507. Patch from Dana Koch.
3735 - Complete tests for the status.c module. Resolves ticket 11507.
3736 Patch from Dana Koch.
3739 - Remove all code for the long unused v1 directory protocol.
3740 Resolves ticket 11070.
3743 Changes in version 0.2.5.3-alpha - 2014-03-22
3744 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
3745 two new anti-DoS features for Tor relays, resolves a bug that kept
3746 SOCKS5 support for IPv6 from working, fixes several annoying usability
3747 issues for bridge users, and removes more old code for unused
3750 The Tor 0.2.5.x release series is now in patch-freeze: no feature
3751 patches not already written will be considered for inclusion in 0.2.5.x.
3753 o Major features (relay security, DoS-resistance):
3754 - When deciding whether we have run out of memory and we need to
3755 close circuits, also consider memory allocated in buffers for
3756 streams attached to each circuit.
3758 This change, which extends an anti-DoS feature introduced in
3759 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
3760 better resist more memory-based DoS attacks than before. Since the
3761 MaxMemInCellQueues option now applies to all queues, it is renamed
3762 to MaxMemInQueues. This feature fixes bug 10169.
3763 - Avoid hash-flooding denial-of-service attacks by using the secure
3764 SipHash-2-4 hash function for our hashtables. Without this
3765 feature, an attacker could degrade performance of a targeted
3766 client or server by flooding their data structures with a large
3767 number of entries to be stored at the same hash table position,
3768 thereby slowing down the Tor instance. With this feature, hash
3769 table positions are derived from a randomized cryptographic key,
3770 and an attacker cannot predict which entries will collide. Closes
3772 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
3773 the default at 8GBytes), to better support Raspberry Pi users. Fixes
3774 bug 9686; bugfix on 0.2.4.14-alpha.
3776 o Minor features (bridges, pluggable transports):
3777 - Bridges now write the SHA1 digest of their identity key
3778 fingerprint (that is, a hash of a hash of their public key) to
3779 notice-level logs, and to a new hashed-fingerprint file. This
3780 information will help bridge operators look up their bridge in
3781 Globe and similar tools. Resolves ticket 10884.
3782 - Improve the message that Tor displays when running as a bridge
3783 using pluggable transports without an Extended ORPort listener.
3784 Also, log the message in the log file too. Resolves ticket 11043.
3786 o Minor features (other):
3787 - Add a new option, PredictedPortsRelevanceTime, to control how long
3788 after having received a request to connect to a given port Tor
3789 will try to keep circuits ready in anticipation of future requests
3790 for that port. Patch from "unixninja92"; implements ticket 9176.
3791 - Generate a warning if any ports are listed in the SocksPolicy,
3792 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3793 AuthDirBadExit options. (These options only support address
3794 ranges.) Fixes part of ticket 11108.
3795 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
3798 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
3799 - Build without warnings under clang 3.4. (We have some macros that
3800 define static functions only some of which will get used later in
3801 the module. Starting with clang 3.4, these give a warning unless the
3802 unused attribute is set on them.) Resolves ticket 10904.
3803 - Fix build warnings about missing "a2x" comment when building the
3804 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3805 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3807 o Minor bugfixes (client):
3808 - Improve the log message when we can't connect to a hidden service
3809 because all of the hidden service directory nodes hosting its
3810 descriptor are excluded. Improves on our fix for bug 10722, which
3811 was a bugfix on 0.2.0.10-alpha.
3812 - Raise a control port warning when we fail to connect to all of
3813 our bridges. Previously, we didn't inform the controller, and
3814 the bootstrap process would stall. Fixes bug 11069; bugfix on
3816 - Exit immediately when a process-owning controller exits.
3817 Previously, tor relays would wait for a little while after their
3818 controller exited, as if they had gotten an INT signal -- but this
3819 was problematic, since there was no feedback for the user. To do a
3820 clean shutdown, controllers should send an INT signal and give Tor
3821 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
3822 - Stop attempting to connect to bridges before our pluggable
3823 transports are configured (harmless but resulted in some erroneous
3824 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
3825 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
3826 generating incorrect SOCKS5 responses, and confusing client
3827 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
3829 o Minor bugfixes (relays and bridges):
3830 - Avoid crashing on a malformed resolv.conf file when running a
3831 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
3832 - Non-exit relays no longer launch mock DNS requests to check for
3833 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
3834 non-exit relays stopped servicing DNS requests. Fixes bug 965;
3835 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
3836 - Bridges now report complete directory request statistics. Related
3837 to bug 5824; bugfix on 0.2.2.1-alpha.
3838 - Bridges now never collect statistics that were designed for
3839 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
3840 - Stop giving annoying warning messages when we decide not to launch
3841 a pluggable transport proxy that we don't need (because there are
3842 no bridges configured to use it). Resolves ticket 5018; bugfix
3844 - Give the correct URL in the warning message when trying to run a
3845 relay on an ancient version of Windows. Fixes bug 9393.
3847 o Minor bugfixes (backtrace support):
3848 - Support automatic backtraces on more platforms by using the
3849 "-fasynchronous-unwind-tables" compiler option. This option is
3850 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
3851 is on by default and table generation is not. This doesn't yet
3852 add Windows support; only Linux, OSX, and some BSDs are affected.
3853 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
3854 - Avoid strange behavior if two threads hit failed assertions at the
3855 same time and both try to log backtraces at once. (Previously, if
3856 this had happened, both threads would have stored their intermediate
3857 results in the same buffer, and generated junk outputs.) Reported by
3858 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
3859 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
3860 0.2.5.2-alpha; patch from Nick Hopper.
3862 o Minor bugfixes (unit tests):
3863 - Fix a small bug in the unit tests that might have made the tests
3864 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
3865 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
3868 - Remove all remaining code related to version-0 hidden service
3869 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
3870 the rest of bug 10841.
3873 - Document in the manpage that "KBytes" may also be written as
3874 "kilobytes" or "KB", that "Kbits" may also be written as
3875 "kilobits", and so forth. Closes ticket 9222.
3876 - Document that the ClientOnly config option overrides ORPort.
3877 Our old explanation made ClientOnly sound as though it did
3878 nothing at all. Resolves bug 9059.
3879 - Explain that SocksPolicy, DirPolicy, and similar options don't
3880 take port arguments. Fixes the other part of ticket 11108.
3881 - Fix a comment about the rend_server_descriptor_t.protocols field
3882 to more accurately describe its range. Also, make that field
3883 unsigned, to more accurately reflect its usage. Fixes bug 9099;
3884 bugfix on 0.2.1.5-alpha.
3885 - Fix the manpage's description of HiddenServiceAuthorizeClient:
3886 the maximum client name length is 16, not 19. Fixes bug 11118;
3887 bugfix on 0.2.1.6-alpha.
3889 o Code simplifications and refactoring:
3890 - Get rid of router->address, since in all cases it was just the
3891 string representation of router->addr. Resolves ticket 5528.
3893 o Test infrastructure:
3894 - Update to the latest version of tinytest.
3895 - Improve the tinytest implementation of string operation tests so
3896 that comparisons with NULL strings no longer crash the tests; they
3897 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
3900 Changes in version 0.2.4.21 - 2014-02-28
3901 Tor 0.2.4.21 further improves security against potential adversaries who
3902 find breaking 1024-bit crypto doable, and backports several stability
3903 and robustness patches from the 0.2.5 branch.
3905 o Major features (client security):
3906 - When we choose a path for a 3-hop circuit, make sure it contains
3907 at least one relay that supports the NTor circuit extension
3908 handshake. Otherwise, there is a chance that we're building
3909 a circuit that's worth attacking by an adversary who finds
3910 breaking 1024-bit crypto doable, and that chance changes the game
3911 theory. Implements ticket 9777.
3914 - Do not treat streams that fail with reason
3915 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3916 since it could also indicate an ENETUNREACH connection error. Fixes
3917 part of bug 10777; bugfix on 0.2.4.8-alpha.
3919 o Code simplification and refactoring:
3920 - Remove data structures which were introduced to implement the
3921 CellStatistics option: they are now redundant with the new timestamp
3922 field in the regular packed_cell_t data structure, which we did
3923 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3926 - Always clear OpenSSL bignums before freeing them -- even bignums
3927 that don't contain secrets. Resolves ticket 10793. Patch by
3929 - Build without warnings under clang 3.4. (We have some macros that
3930 define static functions only some of which will get used later in
3931 the module. Starting with clang 3.4, these give a warning unless the
3932 unused attribute is set on them.) Resolves ticket 10904.
3933 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3934 GeoLite2 Country database.
3937 - Set the listen() backlog limit to the largest actually supported
3938 on the system, not to the value in a header file. Fixes bug 9716;
3939 bugfix on every released Tor.
3940 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3941 exit node as a NOROUTE error, not an INTERNAL error, since they
3942 can apparently happen when trying to connect to the wrong sort
3943 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3944 - Fix build warnings about missing "a2x" comment when building the
3945 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3946 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3947 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3948 not entirely remove it from the connection lists. Fixes bug 9602;
3949 bugfix on 0.2.4.4-alpha.
3950 - Fix a segmentation fault in our benchmark code when running with
3951 Fedora's OpenSSL package, or any other OpenSSL that provides
3952 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3953 - Turn "circuit handshake stats since last time" log messages into a
3954 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3956 o Documentation fixes:
3957 - Document that all but one DirPort entry must have the NoAdvertise
3958 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3961 Changes in version 0.2.5.2-alpha - 2014-02-13
3962 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
3963 like the "poor random number generation" fix and the "building too many
3964 circuits" fix. It also further improves security against potential
3965 adversaries who find breaking 1024-bit crypto doable, and launches
3966 pluggable transports on demand (which gets us closer to integrating
3967 pluggable transport support by default -- not to be confused with Tor
3968 bundles enabling pluggable transports and bridges by default).
3970 o Major features (client security):
3971 - When we choose a path for a 3-hop circuit, make sure it contains
3972 at least one relay that supports the NTor circuit extension
3973 handshake. Otherwise, there is a chance that we're building
3974 a circuit that's worth attacking by an adversary who finds
3975 breaking 1024-bit crypto doable, and that chance changes the game
3976 theory. Implements ticket 9777.
3977 - Clients now look at the "usecreatefast" consensus parameter to
3978 decide whether to use CREATE_FAST or CREATE cells for the first hop
3979 of their circuit. This approach can improve security on connections
3980 where Tor's circuit handshake is stronger than the available TLS
3981 connection security levels, but the tradeoff is more computational
3982 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3984 o Major features (bridges):
3985 - Don't launch pluggable transport proxies if we don't have any
3986 bridges configured that would use them. Now we can list many
3987 pluggable transports, and Tor will dynamically start one when it
3988 hears a bridge address that needs it. Resolves ticket 5018.
3989 - The bridge directory authority now assigns status flags (Stable,
3990 Guard, etc) to bridges based on thresholds calculated over all
3991 Running bridges. Now bridgedb can finally make use of its features
3992 to e.g. include at least one Stable bridge in its answers. Fixes
3995 o Major features (other):
3996 - Extend ORCONN controller event to include an "ID" parameter,
3997 and add four new controller event types CONN_BW, CIRC_BW,
3998 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3999 The new events are emitted in private Tor networks only, with the
4000 goal of being able to better track performance and load during
4001 full-network simulations. Implements proposal 218 and ticket 7359.
4002 - On some platforms (currently: recent OSX versions, glibc-based
4003 platforms that support the ELF format, and a few other
4004 Unix-like operating systems), Tor can now dump stack traces
4005 when a crash occurs or an assertion fails. By default, traces
4006 are dumped to stderr (if possible) and to any logs that are
4007 reporting errors. Implements ticket 9299.
4010 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4011 not entirely remove it from the connection lists. Fixes bug 9602;
4012 bugfix on 0.2.4.4-alpha.
4013 - Do not treat streams that fail with reason
4014 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4015 since it could also indicate an ENETUNREACH connection error. Fixes
4016 part of bug 10777; bugfix on 0.2.4.8-alpha.
4018 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4019 - Do not allow OpenSSL engines to replace the PRNG, even when
4020 HardwareAccel is set. The only default builtin PRNG engine uses
4021 the Intel RDRAND instruction to replace the entire PRNG, and
4022 ignores all attempts to seed it with more entropy. That's
4023 cryptographically stupid: the right response to a new alleged
4024 entropy source is never to discard all previously used entropy
4025 sources. Fixes bug 10402; works around behavior introduced in
4026 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4028 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4029 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4030 - Avoid launching spurious extra circuits when a stream is pending.
4031 This fixes a bug where any circuit that _wasn't_ unusable for new
4032 streams would be treated as if it were, causing extra circuits to
4033 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4035 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4036 - No longer stop reading or writing on cpuworker connections when
4037 our rate limiting buckets go empty. Now we should handle circuit
4038 handshake requests more promptly. Resolves bug 9731.
4039 - Stop trying to bootstrap all our directory information from
4040 only our first guard. Discovered while fixing bug 9946; bugfix
4043 o Minor features (bridges, pluggable transports):
4044 - Add threshold cutoffs to the networkstatus document created by
4045 the Bridge Authority. Fixes bug 1117.
4046 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4047 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4048 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4049 Vidalia set this option for us.) Implements ticket 10297.
4051 o Minor features (security):
4052 - Always clear OpenSSL bignums before freeing them -- even bignums
4053 that don't contain secrets. Resolves ticket 10793. Patch by
4056 o Minor features (config options and command line):
4057 - Add an --allow-missing-torrc commandline option that tells Tor to
4058 run even if the configuration file specified by -f is not available.
4059 Implements ticket 10060.
4060 - Add support for the TPROXY transparent proxying facility on Linux.
4061 See documentation for the new TransProxyType option for more
4062 details. Implementation by "thomo". Closes ticket 10582.
4064 o Minor features (controller):
4065 - Add a new "HS_DESC" controller event that reports activities
4066 related to hidden service descriptors. Resolves ticket 8510.
4067 - New "DROPGUARDS" controller command to forget all current entry
4068 guards. Not recommended for ordinary use, since replacing guards
4069 too frequently makes several attacks easier. Resolves ticket 9934;
4072 o Minor features (build):
4073 - Assume that a user using ./configure --host wants to cross-compile,
4074 and give an error if we cannot find a properly named
4075 tool-chain. Add a --disable-tool-name-check option to proceed
4076 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4077 - If we run ./configure and the compiler recognizes -fstack-protector
4078 but the linker rejects it, warn the user about a potentially missing
4079 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4081 o Minor features (testing):
4082 - If Python is installed, "make check" now runs extra tests beyond
4083 the unit test scripts.
4084 - When bootstrapping a test network, sometimes very few relays get
4085 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4086 specify a set of relays which should be voted Guard regardless of
4087 their uptime or bandwidth. Addresses ticket 9206.
4089 o Minor features (log messages):
4090 - When ServerTransportPlugin is set on a bridge, Tor can write more
4091 useful statistics about bridge use in its extrainfo descriptors,
4092 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4093 log message to inform the user in this case. Resolves ticket 9651.
4094 - When receiving a new controller connection, log the origin address.
4095 Resolves ticket 9698; patch from "sigpipe".
4096 - When logging OpenSSL engine status at startup, log the status of
4097 more engines. Fixes ticket 10043; patch from Joshua Datko.
4098 - Turn "circuit handshake stats since last time" log messages into a
4099 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4101 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4102 - Improve the circuit queue out-of-memory handler. Previously, when
4103 we ran low on memory, we'd close whichever circuits had the most
4104 queued cells. Now, we close those that have the *oldest* queued
4105 cells, on the theory that those are most responsible for us
4106 running low on memory. Based on analysis from a forthcoming paper
4107 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4108 - Generate bootstrapping status update events correctly when fetching
4109 microdescriptors. Fixes bug 9927.
4110 - Update to the October 2 2013 Maxmind GeoLite Country database.
4112 o Minor bugfixes (clients):
4113 - When closing a channel that has already been open, do not close
4114 pending circuits that were waiting to connect to the same relay.
4115 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
4118 o Minor bugfixes (relays):
4119 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4120 exit node as a NOROUTE error, not an INTERNAL error, since they
4121 can apparently happen when trying to connect to the wrong sort
4122 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4124 o Minor bugfixes (bridges):
4125 - Fix a bug where the first connection works to a bridge that uses a
4126 pluggable transport with client-side parameters, but we don't send
4127 the client-side parameters on subsequent connections. (We don't
4128 use any pluggable transports with client-side parameters yet,
4129 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4130 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4132 o Minor bugfixes (node selection):
4133 - If ExcludeNodes is set, consider non-excluded hidden service
4134 directory servers before excluded ones. Do not consider excluded
4135 hidden service directory servers at all if StrictNodes is
4136 set. (Previously, we would sometimes decide to connect to those
4137 servers, and then realize before we initiated a connection that
4138 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4140 - If we set the ExitNodes option but it doesn't include any nodes
4141 that have the Exit flag, we would choose not to bootstrap. Now we
4142 bootstrap so long as ExitNodes includes nodes which can exit to
4143 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4145 o Minor bugfixes (controller and command-line):
4146 - If changing a config option via "setconf" fails in a recoverable
4147 way, we used to nonetheless write our new control ports to the
4148 file described by the "ControlPortWriteToFile" option. Now we only
4149 write out that file if we successfully switch to the new config
4150 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4151 - When a command-line option such as --version or --help that
4152 ordinarily implies --hush appears on the command line along with
4153 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
4154 only if it appeared later on the command line. Fixes bug 9578;
4155 bugfix on 0.2.5.1-alpha.
4157 o Minor bugfixes (code correctness):
4158 - Previously we used two temporary files when writing descriptors to
4159 disk; now we only use one. Fixes bug 1376.
4160 - Remove an erroneous (but impossible and thus harmless) pointer
4161 comparison that would have allowed compilers to skip a bounds
4162 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4163 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4164 - Fix an always-true assertion in pluggable transports code so it
4165 actually checks what it was trying to check. Fixes bug 10046;
4166 bugfix on 0.2.3.9-alpha. Found by "dcb".
4168 o Minor bugfixes (protocol correctness):
4169 - When receiving a VERSIONS cell with an odd number of bytes, close
4170 the connection immediately since the cell is malformed. Fixes bug
4171 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4174 o Minor bugfixes (build):
4175 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4176 turned off (that is, without support for v2 link handshakes). Fixes
4177 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4178 - Fix compilation warnings and startup issues when running with
4179 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
4181 - Fix compilation on Solaris 9, which didn't like us having an
4182 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
4184 o Minor bugfixes (testing):
4185 - Fix a segmentation fault in our benchmark code when running with
4186 Fedora's OpenSSL package, or any other OpenSSL that provides
4187 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4189 o Minor bugfixes (log messages):
4190 - Fix a bug where clients using bridges would report themselves
4191 as 50% bootstrapped even without a live consensus document.
4192 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4193 - Suppress a warning where, if there's only one directory authority
4194 in the network, we would complain that votes and signatures cannot
4195 be uploaded to other directory authorities. Fixes bug 10842;
4196 bugfix on 0.2.2.26-beta.
4197 - Report bootstrapping progress correctly when we're downloading
4198 microdescriptors. We had updated our "do we have enough microdescs
4199 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4200 (see bug 5956), but we left the bootstrap status event logic at
4201 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4202 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4204 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4205 - Avoid a crash bug when starting with a corrupted microdescriptor
4206 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4207 - If we fail to dump a previously cached microdescriptor to disk, avoid
4208 freeing duplicate data later on. Fixes bug 10423; bugfix on
4209 0.2.4.13-alpha. Spotted by "bobnomnom".
4211 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4212 - Correctly log long IPv6 exit policies, instead of truncating them
4213 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4214 - Our default TLS ecdhe groups were backwards: we meant to be using
4215 P224 for relays (for performance win) and P256 for bridges (since
4216 it is more common in the wild). Instead we had it backwards. After
4217 reconsideration, we decided that the default should be P256 on all
4218 hosts, since its security is probably better, and since P224 is
4219 reportedly used quite little in the wild. Found by "skruffy" on
4220 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4221 - Free directory authority certificate download statuses on exit
4222 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4224 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4225 - If the guard we choose first doesn't answer, we would try the
4226 second guard, but once we connected to the second guard we would
4227 abandon it and retry the first one, slowing down bootstrapping.
4228 The fix is to treat all our initially chosen guards as acceptable
4229 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4230 - Fix an assertion failure that would occur when disabling the
4231 ORPort setting on a running Tor process while accounting was
4232 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4233 - When examining the list of network interfaces to find our address,
4234 do not consider non-running or disabled network interfaces. Fixes
4235 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4236 - Avoid an off-by-one error when checking buffer boundaries when
4237 formatting the exit status of a pluggable transport helper.
4238 This is probably not an exploitable bug, but better safe than
4239 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4242 o Removed code and features:
4243 - Clients now reject any directory authority certificates lacking
4244 a dir-key-crosscert element. These have been included since
4245 0.2.1.9-alpha, so there's no real reason for them to be optional
4246 any longer. Completes proposal 157. Resolves ticket 10162.
4247 - Remove all code that existed to support the v2 directory system,
4248 since there are no longer any v2 directory authorities. Resolves
4250 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4251 options, which were used for designating authorities as "Hidden
4252 service authorities". There has been no use of hidden service
4253 authorities since 0.2.2.1-alpha, when we stopped uploading or
4254 downloading v0 hidden service descriptors. Fixes bug 10881; also
4255 part of a fix for bug 10841.
4257 o Code simplification and refactoring:
4258 - Remove some old fallback code designed to keep Tor clients working
4259 in a network with only two working relays. Elsewhere in the code we
4260 have long since stopped supporting such networks, so there wasn't
4261 much point in keeping it around. Addresses ticket 9926.
4262 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4263 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4264 - Remove data structures which were introduced to implement the
4265 CellStatistics option: they are now redundant with the addition
4266 of a timestamp to the regular packed_cell_t data structure, which
4267 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
4270 o Documentation (man page) fixes:
4271 - Update manpage to describe some of the files you can expect to
4272 find in Tor's DataDirectory. Addresses ticket 9839.
4273 - Document that all but one DirPort entry must have the NoAdvertise
4274 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4276 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4277 - Clarify the usage and risks of setting the ContactInfo torrc line
4278 for your relay or bridge. Resolves ticket 9854.
4279 - Add anchors to the manpage so we can link to the html version of
4280 the documentation for specific options. Resolves ticket 9866.
4281 - Replace remaining references to DirServer in man page and
4282 log entries. Resolves ticket 10124.
4285 - Make the "tor-gencert" tool used by directory authority operators
4286 create 2048-bit signing keys by default (rather than 1024-bit, since
4287 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4290 Changes in version 0.2.4.20 - 2013-12-22
4291 Tor 0.2.4.20 fixes potentially poor random number generation for users
4292 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4293 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
4294 and 4) have no state file in their DataDirectory (as would happen on
4295 first start). Users who generated relay or hidden service identity
4296 keys in such a situation should discard them and generate new ones.
4298 This release also fixes a logic error that caused Tor clients to build
4299 many more preemptive circuits than they actually need.
4302 - Do not allow OpenSSL engines to replace the PRNG, even when
4303 HardwareAccel is set. The only default builtin PRNG engine uses
4304 the Intel RDRAND instruction to replace the entire PRNG, and
4305 ignores all attempts to seed it with more entropy. That's
4306 cryptographically stupid: the right response to a new alleged
4307 entropy source is never to discard all previously used entropy
4308 sources. Fixes bug 10402; works around behavior introduced in
4309 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4311 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4312 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4313 - Avoid launching spurious extra circuits when a stream is pending.
4314 This fixes a bug where any circuit that _wasn't_ unusable for new
4315 streams would be treated as if it were, causing extra circuits to
4316 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4319 - Avoid a crash bug when starting with a corrupted microdescriptor
4320 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4321 - If we fail to dump a previously cached microdescriptor to disk, avoid
4322 freeing duplicate data later on. Fixes bug 10423; bugfix on
4323 0.2.4.13-alpha. Spotted by "bobnomnom".
4326 Changes in version 0.2.4.19 - 2013-12-11
4327 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
4328 (1986-2013). Aaron worked on diverse projects including helping to guide
4329 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
4330 transparency to the U.S government's PACER documents, and contributing
4331 design and development for Tor and Tor2Web. Aaron was one of the latest
4332 martyrs in our collective fight for civil liberties and human rights,
4333 and his death is all the more painful because he was one of us.
4335 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
4336 a new circuit handshake and link encryption that use ECC to provide
4337 better security and efficiency; makes relays better manage circuit
4338 creation requests; uses "directory guards" to reduce client enumeration
4339 risks; makes bridges collect and report statistics about the pluggable
4340 transports they support; cleans up and improves our geoip database;
4341 gets much closer to IPv6 support for clients, bridges, and relays; makes
4342 directory authorities use measured bandwidths rather than advertised
4343 ones when computing flags and thresholds; disables client-side DNS
4344 caching to reduce tracking risks; and fixes a big bug in bridge
4345 reachability testing. This release introduces two new design
4346 abstractions in the code: a new "channel" abstraction between circuits
4347 and or_connections to allow for implementing alternate relay-to-relay
4348 transports, and a new "circuitmux" abstraction storing the queue of
4349 circuits for a channel. The release also includes many stability,
4350 security, and privacy fixes.
4353 Changes in version 0.2.4.18-rc - 2013-11-16
4354 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
4355 series. It takes a variety of fixes from the 0.2.5.x branch to improve
4356 stability, performance, and better handling of edge cases.
4359 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4360 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4361 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4362 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4363 them to solve bug 6033.)
4366 - No longer stop reading or writing on cpuworker connections when
4367 our rate limiting buckets go empty. Now we should handle circuit
4368 handshake requests more promptly. Resolves bug 9731.
4369 - If we are unable to save a microdescriptor to the journal, do not
4370 drop it from memory and then reattempt downloading it. Fixes bug
4371 9645; bugfix on 0.2.2.6-alpha.
4372 - Stop trying to bootstrap all our directory information from
4373 only our first guard. Discovered while fixing bug 9946; bugfix
4375 - The new channel code sometimes lost track of in-progress circuits,
4376 causing long-running clients to stop building new circuits. The
4377 fix is to always call circuit_n_chan_done(chan, 0) from
4378 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4380 o Minor bugfixes (on 0.2.4.x):
4381 - Correctly log long IPv6 exit policies, instead of truncating them
4382 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4383 - Our default TLS ecdhe groups were backwards: we meant to be using
4384 P224 for relays (for performance win) and P256 for bridges (since
4385 it is more common in the wild). Instead we had it backwards. After
4386 reconsideration, we decided that the default should be P256 on all
4387 hosts, since its security is probably better, and since P224 is
4388 reportedly used quite little in the wild. Found by "skruffy" on
4389 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4390 - Free directory authority certificate download statuses on exit
4391 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4393 o Minor bugfixes (on 0.2.3.x and earlier):
4394 - If the guard we choose first doesn't answer, we would try the
4395 second guard, but once we connected to the second guard we would
4396 abandon it and retry the first one, slowing down bootstrapping.
4397 The fix is to treat all our initially chosen guards as acceptable
4398 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4399 - Fix an assertion failure that would occur when disabling the
4400 ORPort setting on a running Tor process while accounting was
4401 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4402 - When examining the list of network interfaces to find our address,
4403 do not consider non-running or disabled network interfaces. Fixes
4404 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4405 - Avoid an off-by-one error when checking buffer boundaries when
4406 formatting the exit status of a pluggable transport helper.
4407 This is probably not an exploitable bug, but better safe than
4408 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4411 o Minor features (protecting client timestamps):
4412 - Clients no longer send timestamps in their NETINFO cells. These were
4413 not used for anything, and they provided one small way for clients
4414 to be distinguished from each other as they moved from network to
4415 network or behind NAT. Implements part of proposal 222.
4416 - Clients now round timestamps in INTRODUCE cells down to the nearest
4417 10 minutes. If a new Support022HiddenServices option is set to 0, or
4418 if it's set to "auto" and the feature is disabled in the consensus,
4419 the timestamp is sent as 0 instead. Implements part of proposal 222.
4420 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4421 a big deal from a security point of view, but it achieves no actual
4422 good purpose, and isn't needed. Implements part of proposal 222.
4423 - Reduce down accuracy of timestamps in hidden service descriptors.
4424 Implements part of proposal 222.
4426 o Minor features (other):
4427 - Improve the circuit queue out-of-memory handler. Previously, when
4428 we ran low on memory, we'd close whichever circuits had the most
4429 queued cells. Now, we close those that have the *oldest* queued
4430 cells, on the theory that those are most responsible for us
4431 running low on memory. Based on analysis from a forthcoming paper
4432 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4433 - Generate bootstrapping status update events correctly when fetching
4434 microdescriptors. Fixes bug 9927.
4435 - Update to the October 2 2013 Maxmind GeoLite Country database.
4437 o Documentation fixes:
4438 - Clarify the usage and risks of setting the ContactInfo torrc line
4439 for your relay or bridge. Resolves ticket 9854.
4440 - Add anchors to the manpage so we can link to the html version of
4441 the documentation for specific options. Resolves ticket 9866.
4442 - Replace remaining references to DirServer in man page and
4443 log entries. Resolves ticket 10124.
4446 Changes in version 0.2.5.1-alpha - 2013-10-02
4447 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
4448 on Linux, allows bridges that offer pluggable transports to report usage
4449 statistics, fixes many issues to make testing easier, and provides
4450 a pile of minor features and bugfixes that have been waiting for a
4451 release of the new branch.
4453 This is the first alpha release in a new series, so expect there to
4454 be bugs. Users who would rather test out a more stable branch should
4455 stay with 0.2.4.x for now.
4457 o Major features (security):
4458 - Use the seccomp2 syscall filtering facility on Linux to limit
4459 which system calls Tor can invoke. This is an experimental,
4460 Linux-only feature to provide defense-in-depth against unknown
4461 attacks. To try turning it on, set "Sandbox 1" in your torrc
4462 file. Please be ready to report bugs. We hope to add support
4463 for better sandboxing in the future, including more fine-grained
4464 filters, better division of responsibility, and support for more
4465 platforms. This work has been done by Cristian-Matei Toader for
4466 Google Summer of Code.
4467 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4468 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4469 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4470 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4471 them to solve bug 6033.)
4473 o Major features (other):
4474 - Add support for passing arguments to managed pluggable transport
4475 proxies. Implements ticket 3594.
4476 - Bridges now track GeoIP information and the number of their users
4477 even when pluggable transports are in use, and report usage
4478 statistics in their extra-info descriptors. Resolves tickets 4773
4480 - Make testing Tor networks bootstrap better: lower directory fetch
4481 retry schedules and maximum interval without directory requests,
4482 and raise maximum download tries. Implements ticket 6752.
4483 - Add make target 'test-network' to run tests on a Chutney network.
4484 Implements ticket 8530.
4485 - The ntor handshake is now on-by-default, no matter what the
4486 directory authorities recommend. Implements ticket 8561.
4489 - Instead of writing destroy cells directly to outgoing connection
4490 buffers, queue them and intersperse them with other outgoing cells.
4491 This can prevent a set of resource starvation conditions where too
4492 many pending destroy cells prevent data cells from actually getting
4493 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4494 bugfix on 0.2.0.1-alpha.
4495 - If we are unable to save a microdescriptor to the journal, do not
4496 drop it from memory and then reattempt downloading it. Fixes bug
4497 9645; bugfix on 0.2.2.6-alpha.
4498 - The new channel code sometimes lost track of in-progress circuits,
4499 causing long-running clients to stop building new circuits. The
4500 fix is to always call circuit_n_chan_done(chan, 0) from
4501 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4504 - Tor now builds each source file in two modes: a mode that avoids
4505 exposing identifiers needlessly, and another mode that exposes
4506 more identifiers for testing. This lets the compiler do better at
4507 optimizing the production code, while enabling us to take more
4508 radical measures to let the unit tests test things.
4509 - The production builds no longer include functions used only in
4510 the unit tests; all functions exposed from a module only for
4511 unit-testing are now static in production builds.
4512 - Add an --enable-coverage configuration option to make the unit
4513 tests (and a new src/or/tor-cov target) to build with gcov test
4517 - We now have rudimentary function mocking support that our unit
4518 tests can use to test functions in isolation. Function mocking
4519 lets the tests temporarily replace a function's dependencies with
4520 stub functions, so that the tests can check the function without
4521 invoking the other functions it calls.
4522 - Add more unit tests for the <circid,channel>->circuit map, and
4523 the destroy-cell-tracking code to fix bug 7912.
4524 - Unit tests for failing cases of the TAP onion handshake.
4525 - More unit tests for address-manipulation functions.
4527 o Minor features (protecting client timestamps):
4528 - Clients no longer send timestamps in their NETINFO cells. These were
4529 not used for anything, and they provided one small way for clients
4530 to be distinguished from each other as they moved from network to
4531 network or behind NAT. Implements part of proposal 222.
4532 - Clients now round timestamps in INTRODUCE cells down to the nearest
4533 10 minutes. If a new Support022HiddenServices option is set to 0, or
4534 if it's set to "auto" and the feature is disabled in the consensus,
4535 the timestamp is sent as 0 instead. Implements part of proposal 222.
4536 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4537 a big deal from a security point of view, but it achieves no actual
4538 good purpose, and isn't needed. Implements part of proposal 222.
4539 - Reduce down accuracy of timestamps in hidden service descriptors.
4540 Implements part of proposal 222.
4542 o Minor features (config options):
4543 - Config (torrc) lines now handle fingerprints which are missing
4544 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4545 - Support a --dump-config option to print some or all of the
4546 configured options. Mainly useful for debugging the command-line
4547 option parsing code. Helps resolve ticket 4647.
4548 - Raise awareness of safer logging: notify user of potentially
4549 unsafe config options, like logging more verbosely than severity
4550 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4551 - Add a new configuration option TestingV3AuthVotingStartOffset
4552 that bootstraps a network faster by changing the timing for
4553 consensus votes. Addresses ticket 8532.
4554 - Add a new torrc option "ServerTransportOptions" that allows
4555 bridge operators to pass configuration parameters to their
4556 pluggable transports. Resolves ticket 8929.
4557 - The config (torrc) file now accepts bandwidth and space limits in
4558 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4559 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4562 o Minor features (build):
4563 - Add support for `--library-versions` flag. Implements ticket 6384.
4564 - Return the "unexpected sendme" warnings to a warn severity, but make
4565 them rate limited, to help diagnose ticket 8093.
4566 - Detect a missing asciidoc, and warn the user about it, during
4567 configure rather than at build time. Fixes issue 6506. Patch from
4570 o Minor features (other):
4571 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4572 sockets in a single system call. Implements ticket 5129.
4573 - Log current accounting state (bytes sent and received + remaining
4574 time for the current accounting period) in the relay's heartbeat
4575 message. Implements ticket 5526; patch from Peter Retzlaff.
4576 - Implement the TRANSPORT_LAUNCHED control port event that
4577 notifies controllers about new launched pluggable
4578 transports. Resolves ticket 5609.
4579 - If we're using the pure-C 32-bit curve25519_donna implementation
4580 of curve25519, build it with the -fomit-frame-pointer option to
4581 make it go faster on register-starved hosts. This improves our
4582 handshake performance by about 6% on i386 hosts without nacl.
4584 - Update to the September 4 2013 Maxmind GeoLite Country database.
4587 - Set the listen() backlog limit to the largest actually supported
4588 on the system, not to the value in a header file. Fixes bug 9716;
4589 bugfix on every released Tor.
4590 - No longer accept malformed http headers when parsing urls from
4591 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4592 bugfix on 0.0.6pre1.
4593 - In munge_extrainfo_into_routerinfo(), check the return value of
4594 memchr(). This would have been a serious issue if we ever passed
4595 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4597 - On the chance that somebody manages to build Tor on a
4598 platform where time_t is unsigned, correct the way that
4599 microdesc_add_to_cache() handles negative time arguments.
4600 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4601 - Reject relative control socket paths and emit a warning. Previously,
4602 single-component control socket paths would be rejected, but Tor
4603 would not log why it could not validate the config. Fixes bug 9258;
4604 bugfix on 0.2.3.16-alpha.
4606 o Minor bugfixes (command line):
4607 - Use a single command-line parser for parsing torrc options on the
4608 command line and for finding special command-line options to avoid
4609 inconsistent behavior for torrc option arguments that have the same
4610 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4612 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4613 9573; bugfix on 0.0.9pre5.
4615 o Minor fixes (build, auxiliary programs):
4616 - Stop preprocessing the "torify" script with autoconf, since
4617 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4619 - The tor-fw-helper program now follows the standard convention and
4620 exits with status code "0" on success. Fixes bug 9030; bugfix on
4621 0.2.3.1-alpha. Patch by Arlo Breault.
4622 - Corrected ./configure advice for what openssl dev package you should
4623 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4625 o Minor code improvements:
4626 - Remove constants and tests for PKCS1 padding; it's insecure and
4627 shouldn't be used for anything new. Fixes bug 8792; patch
4629 - Remove instances of strcpy() from the unit tests. They weren't
4630 hurting anything, since they were only in the unit tests, but it's
4631 embarassing to have strcpy() in the code at all, and some analysis
4632 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4633 0.2.3.8-alpha. Patch from Arlo Breault.
4636 - Remove migration code from when we renamed the "cached-routers"
4637 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4638 incidentally resolves ticket 6502 by cleaning up the related code
4639 a bit. Patch from Akshay Hebbar.
4641 o Code simplification and refactoring:
4642 - Extract the common duplicated code for creating a subdirectory
4643 of the data directory and writing to a file in it. Fixes ticket
4644 4282; patch from Peter Retzlaff.
4645 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4646 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4647 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4648 - Add a set of accessor functions for the circuit timeout data
4649 structure. Fixes ticket 6153; patch from "piet".
4650 - Clean up exit paths from connection_listener_new(). Closes ticket
4651 8789. Patch from Arlo Breault.
4652 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4653 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4654 - Use a doubly-linked list to implement the global circuit list.
4655 Resolves ticket 9108. Patch from Marek Majkowski.
4656 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4659 Changes in version 0.2.4.17-rc - 2013-09-05
4660 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
4661 series. It adds an emergency step to help us tolerate the massive
4662 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
4663 circuit-level handshakes now effectively jump the queue compared to
4664 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
4665 big bug hindering bridge reachability tests.
4668 - Relays now process the new "NTor" circuit-level handshake requests
4669 with higher priority than the old "TAP" circuit-level handshake
4670 requests. We still process some TAP requests to not totally starve
4671 0.2.3 clients when NTor becomes popular. A new consensus parameter
4672 "NumNTorsPerTAP" lets us tune the balance later if we need to.
4673 Implements ticket 9574.
4676 - If the circuit build timeout logic is disabled (via the consensus,
4677 or because we are an authority), then don't build testing circuits.
4678 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
4679 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
4680 previously they did not, which prevented them from receiving
4681 successful connections from relays for self-test or bandwidth
4682 testing. Also, when a relay is extending a circuit to a bridge,
4683 it needs to send a NETINFO cell, even when the bridge hasn't sent
4684 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
4685 - If the time to download the next old-style networkstatus is in
4686 the future, do not decline to consider whether to download the
4687 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
4691 - Avoid double-closing the listener socket in our socketpair()
4692 replacement (used on Windows) in the case where the addresses on
4693 our opened sockets don't match what we expected. Fixes bug 9400;
4694 bugfix on 0.0.2pre7. Found by Coverity.
4696 o Minor fixes (config options):
4697 - Avoid overflows when the user sets MaxCircuitDirtiness to a
4698 ridiculously high value, by imposing a (ridiculously high) 30-day
4699 maximum on MaxCircuitDirtiness.
4700 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
4701 message is logged at notice, not at info.
4702 - Warn and fail if a server is configured not to advertise any
4703 ORPorts at all. (We need *something* to put in our descriptor,
4704 or we just won't work.)
4707 - Track how many "TAP" and "NTor" circuit handshake requests we get,
4708 and how many we complete, and log it every hour to help relay
4709 operators follow trends in network load. Addresses ticket 9658.
4710 - Update to the August 7 2013 Maxmind GeoLite Country database.
4713 Changes in version 0.2.4.16-rc - 2013-08-10
4714 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
4715 series. It fixes several crash bugs in the 0.2.4 branch.
4718 - Fix a bug in the voting algorithm that could yield incorrect results
4719 when a non-naming authority declared too many flags. Fixes bug 9200;
4720 bugfix on 0.2.0.3-alpha.
4721 - Fix an uninitialized read that could in some cases lead to a remote
4722 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
4723 Anybody running a hidden service on the experimental 0.2.4.x
4724 branch should upgrade. (This is, so far as we know, unrelated to
4726 - Avoid an assertion failure when processing DNS replies without the
4727 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
4728 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
4729 0.2.4.15-rc. Found by stem integration tests.
4732 - Fix an invalid memory read that occured when a pluggable
4733 transport proxy failed its configuration protocol.
4734 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
4735 - When evaluating whether to use a connection that we haven't
4736 decided is canonical using a recent link protocol version,
4737 decide that it's canonical only if it used address _does_
4738 match the desired address. Fixes bug 9309; bugfix on
4739 0.2.4.4-alpha. Reported by skruffy.
4740 - Make the default behavior of NumDirectoryGuards be to track
4741 NumEntryGuards. Now a user who changes only NumEntryGuards will get
4742 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
4743 - Fix a spurious compilation warning with some older versions of
4744 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
4747 - Update to the July 3 2013 Maxmind GeoLite Country database.
4750 Changes in version 0.2.4.15-rc - 2013-07-01
4751 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
4752 series. It fixes a few smaller bugs, but generally appears stable.
4753 Please test it and let us know whether it is!
4756 - When receiving a new configuration file via the control port's
4757 LOADCONF command, do not treat the defaults file as absent.
4758 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
4761 - Issue a warning when running with the bufferevents backend enabled.
4762 It's still not stable, and people should know that they're likely
4763 to hit unexpected problems. Closes ticket 9147.
4766 Changes in version 0.2.4.14-alpha - 2013-06-18
4767 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
4768 present in 0.2.4.13-alpha.
4771 - When we have too much memory queued in circuits (according to a new
4772 MaxMemInCellQueues option), close the circuits consuming the most
4773 memory. This prevents us from running out of memory as a relay if
4774 circuits fill up faster than they can be drained. Fixes bug 9063;
4775 bugfix on the 54th commit of Tor. This bug is a further fix beyond
4776 bug 6252, whose fix was merged into 0.2.3.21-rc.
4778 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
4779 where we tried to solve this issue simply by imposing an upper limit
4780 on the number of queued cells for a single circuit. That approach
4781 proved to be problematic, since there are ways to provoke clients to
4782 send a number of cells in excess of any such reasonable limit. Fixes
4783 bug 9072; bugfix on 0.2.4.13-alpha.
4785 - Limit hidden service descriptors to at most ten introduction
4786 points, to slow one kind of guard enumeration. Fixes bug 9002;
4787 bugfix on 0.1.1.11-alpha.
4790 Changes in version 0.2.4.13-alpha - 2013-06-14
4791 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
4792 vulnerabilities, makes socks5 username/password circuit isolation
4793 actually actually work (this time for sure!), and cleans up a bunch
4794 of other issues in preparation for a release candidate.
4796 o Major bugfixes (robustness):
4797 - Close any circuit that has too many cells queued on it. Fixes
4798 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
4799 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
4800 - Prevent the get_freelists() function from running off the end of
4801 the list of freelists if it somehow gets an unrecognized
4802 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4804 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4805 when an exit connection with optimistic data succeeds immediately
4806 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4808 - Fix a directory authority crash bug when building a consensus
4809 using an older consensus as its basis. Fixes bug 8833. Bugfix
4813 - Avoid a memory leak where we would leak a consensus body when we
4814 find that a consensus which we couldn't previously verify due to
4815 missing certificates is now verifiable. Fixes bug 8719; bugfix
4817 - We used to always request authority certificates by identity digest,
4818 meaning we'd get the newest one even when we wanted one with a
4819 different signing key. Then we would complain about being given
4820 a certificate we already had, and never get the one we really
4821 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
4822 resource to request the one we want. Fixes bug 5595; bugfix on
4824 - Follow the socks5 protocol when offering username/password
4825 authentication. The fix for bug 8117 exposed this bug, and it
4826 turns out real-world applications like Pidgin do care. Bugfix on
4827 0.2.3.2-alpha; fixes bug 8879.
4828 - Prevent failures on Windows Vista and later when rebuilding the
4829 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
4830 bugfix on 0.2.4.12-alpha.
4833 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4834 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4835 - If for some reason we fail to write a microdescriptor while
4836 rebuilding the cache, do not let the annotations from that
4837 microdescriptor linger in the cache file, and do not let the
4838 microdescriptor stay recorded as present in its old location.
4839 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
4840 - Fix a memory leak that would occur whenever a configuration
4841 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4842 - Paste the description for PathBias parameters from the man
4843 page into or.h, so the code documents them too. Fixes bug 7982;
4844 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
4845 - Relays now treat a changed IPv6 ORPort as sufficient reason to
4846 publish an updated descriptor. Fixes bug 6026; bugfix on
4848 - When launching a resolve request on behalf of an AF_UNIX control
4849 socket, omit the address field of the new entry connection, used in
4850 subsequent controller events, rather than letting tor_dup_addr()
4851 set it to "<unknown address type>". Fixes bug 8639; bugfix on
4854 o Minor bugfixes (log messages):
4855 - Fix a scaling issue in the path bias accounting code that
4856 resulted in "Bug:" log messages from either
4857 pathbias_scale_close_rates() or pathbias_count_build_success().
4858 This represents a bugfix on a previous bugfix: the original fix
4859 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
4861 - Give a less useless error message when the user asks for an IPv4
4862 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
4866 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
4867 to tolerate bug 8093 for now.
4868 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
4869 in directory authority votes to describe whether they have enough
4870 measured bandwidths to ignore advertised (relay descriptor)
4871 bandwidth claims. Resolves ticket 8711.
4872 - Update to the June 5 2013 Maxmind GeoLite Country database.
4874 o Removed documentation:
4875 - Remove some of the older contents of doc/ as obsolete; move others
4876 to torspec.git. Fixes bug 8965.
4878 o Code simplification and refactoring:
4879 - Avoid using character buffers when constructing most directory
4880 objects: this approach was unwieldy and error-prone. Instead,
4881 build smartlists of strings, and concatenate them when done.
4884 Changes in version 0.2.4.12-alpha - 2013-04-18
4885 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
4886 process for lengthening the guard rotation period, makes directory
4887 authority opinions in the consensus a bit less gameable, makes socks5
4888 username/password circuit isolation actually work, and fixes a wide
4889 variety of other issues.
4892 - Raise the default time that a client keeps an entry guard from
4893 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4894 2012 paper. (We would make it even longer, but we need better client
4895 load balancing first.) Also, make the guard lifetime controllable
4896 via a new GuardLifetime torrc option and a GuardLifetime consensus
4897 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4898 - Directory authorities now prefer using measured bandwidths to
4899 advertised ones when computing flags and thresholds. Resolves
4901 - Directory authorities that have more than a threshold number
4902 of relays with measured bandwidths now treat relays with unmeasured
4903 bandwidths as having bandwidth 0. Resolves ticket 8435.
4905 o Major bugfixes (assert / resource use):
4906 - Avoid a bug where our response to TLS renegotiation under certain
4907 network conditions could lead to a busy-loop, with 100% CPU
4908 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4909 - Avoid an assertion when we discover that we'd like to write a cell
4910 onto a closing connection: just discard the cell. Fixes another
4911 case of bug 7350; bugfix on 0.2.4.4-alpha.
4913 o Major bugfixes (client-side privacy):
4914 - When we mark a circuit as unusable for new circuits, have it
4915 continue to be unusable for new circuits even if MaxCircuitDirtiness
4916 is increased too much at the wrong time, or the system clock jumps
4917 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
4918 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
4919 which have resolved to internal addresses") is set, apply that
4920 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
4921 - When an exit relay rejects a stream with reason "exit policy", but
4922 we only know an exit policy summary (e.g. from the microdesc
4923 consensus) for it, do not mark the relay as useless for all exiting.
4924 Instead, mark just the circuit as unsuitable for that particular
4925 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
4926 - Allow applications to get proper stream isolation with
4927 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
4928 username/password authentication also offer "no authentication". Tor
4929 had previously preferred "no authentication", so the applications
4930 never actually sent Tor their auth details. Now Tor selects
4931 username/password authentication if it's offered. You can disable
4932 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
4933 bug 8117; bugfix on 0.2.3.3-alpha.
4935 o Major bugfixes (other):
4936 - When unable to find any working directory nodes to use as a
4937 directory guard, give up rather than adding the same non-working
4938 nodes to the directory guard list over and over. Fixes bug 8231;
4939 bugfix on 0.2.4.8-alpha.
4942 - Reject as invalid most directory objects containing a NUL.
4943 Belt-and-suspender fix for bug 8037.
4944 - In our testsuite, create temporary directories with a bit more
4945 entropy in their name to make name collisions less likely. Fixes
4947 - Add CACHED keyword to ADDRMAP events in the control protocol
4948 to indicate whether a DNS result will be cached or not. Resolves
4950 - Update to the April 3 2013 Maxmind GeoLite Country database.
4952 o Minor features (build):
4953 - Detect and reject attempts to build Tor with threading support
4954 when OpenSSL has been compiled without threading support.
4956 - Clarify that when autoconf is checking for nacl, it is checking
4957 specifically for nacl with a fast curve25519 implementation.
4959 - Warn if building on a platform with an unsigned time_t: there
4960 are too many places where Tor currently assumes that time_t can
4961 hold negative values. We'd like to fix them all, but probably
4964 o Minor bugfixes (build):
4965 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4966 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4967 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4968 - Add the old src/or/micro-revision.i filename to CLEANFILES.
4969 On the off chance that somebody has one, it will go away as soon
4970 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
4971 - Build Tor correctly on 32-bit platforms where the compiler can build
4972 but not run code using the "uint128_t" construction. Fixes bug 8587;
4973 bugfix on 0.2.4.8-alpha.
4974 - Fix compilation warning with some versions of clang that would
4975 prefer the -Wswitch-enum compiler flag to warn about switch
4976 statements with missing enum values, even if those switch
4977 statements have a "default:" statement. Fixes bug 8598; bugfix
4980 o Minor bugfixes (protocol):
4981 - Fix the handling of a TRUNCATE cell when it arrives while the
4982 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
4983 - Fix a misframing issue when reading the version numbers in a
4984 VERSIONS cell. Previously we would recognize [00 01 00 02] as
4985 'version 1, version 2, and version 0x100', when it should have
4986 only included versions 1 and 2. Fixes bug 8059; bugfix on
4987 0.2.0.10-alpha. Reported pseudonymously.
4988 - Make the format and order of STREAM events for DNS lookups
4989 consistent among the various ways to launch DNS lookups. Fixes
4990 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
4991 - Correct our check for which versions of Tor support the EXTEND2
4992 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
4993 later, when support was really added in version 0.2.4.8-alpha.
4994 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
4996 o Minor bugfixes (other):
4997 - Correctly store microdescriptors and extrainfo descriptors with
4998 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
4999 Bug reported by "cypherpunks".
5000 - Increase the width of the field used to remember a connection's
5001 link protocol version to two bytes. Harmless for now, since the
5002 only currently recognized versions are one byte long. Reported
5003 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5004 - If the state file's path bias counts are invalid (presumably from a
5005 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5006 additional checks and log messages to the scaling of Path Bias
5007 counts, in case there still are remaining issues with scaling.
5008 Should help resolve bug 8235.
5009 - Eliminate several instances where we use "Nickname=ID" to refer to
5010 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5011 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5012 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
5014 o Minor bugfixes (syscalls):
5015 - Always check the return values of functions fcntl() and
5016 setsockopt(). We don't believe these are ever actually failing in
5017 practice, but better safe than sorry. Also, checking these return
5018 values should please analysis tools like Coverity. Patch from
5019 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5020 - Use direct writes rather than stdio when building microdescriptor
5021 caches, in an attempt to mitigate bug 8031, or at least make it
5024 o Minor bugfixes (config):
5025 - When rejecting a configuration because we were unable to parse a
5026 quoted string, log an actual error message. Fixes bug 7950; bugfix
5028 - Behave correctly when the user disables LearnCircuitBuildTimeout
5029 but doesn't tell us what they would like the timeout to be. Fixes
5030 bug 6304; bugfix on 0.2.2.14-alpha.
5031 - When autodetecting the number of CPUs, use the number of available
5032 CPUs in preference to the number of configured CPUs. Inform the
5033 user if this reduces the number of available CPUs. Fixes bug 8002;
5034 bugfix on 0.2.3.1-alpha.
5035 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5036 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5037 bug 8180; bugfix on 0.2.3.11-alpha.
5038 - Allow TestingTorNetworks to override the 4096-byte minimum for
5039 the Fast threshold. Otherwise they can't bootstrap until they've
5040 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
5041 - Fix some logic errors when the user manually overrides the
5042 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
5045 o Minor bugfixes (log messages to help diagnose bugs):
5046 - If we fail to free a microdescriptor because of bug 7164, log
5047 the filename and line number from which we tried to free it.
5048 - Add another diagnostic to the heartbeat message: track and log
5049 overhead that TLS is adding to the data we write. If this is
5050 high, we are sending too little data to SSL_write at a time.
5051 Diagnostic for bug 7707.
5052 - Add more detail to a log message about relaxed timeouts, to help
5054 - Warn more aggressively when flushing microdescriptors to a
5055 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5056 or at least make it more diagnosable.
5057 - Improve debugging output to help track down bug 8185 ("Bug:
5058 outgoing relay cell has n_chan==NULL. Dropping.")
5059 - Log the purpose of a path-bias testing circuit correctly.
5060 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
5062 o Minor bugfixes (0.2.4.x log messages that were too noisy):
5063 - Don't attempt to relax the timeout of already opened 1-hop circuits.
5064 They might never timeout. This should eliminate some/all cases of
5065 the relaxed timeout log message.
5066 - Use circuit creation time for network liveness evaluation. This
5067 should eliminate warning log messages about liveness caused
5068 by changes in timeout evaluation. Fixes bug 6572; bugfix on
5070 - Reduce a path bias length check from notice to info. The message
5071 is triggered when creating controller circuits. Fixes bug 8196;
5072 bugfix on 0.2.4.8-alpha.
5073 - Fix a path state issue that triggered a notice during relay startup.
5074 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
5075 - Reduce occurrences of warns about circuit purpose in
5076 connection_ap_expire_building(). Fixes bug 8477; bugfix on
5079 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
5080 - If we encounter a write failure on a SOCKS connection before we
5081 finish our SOCKS handshake, don't warn that we closed the
5082 connection before we could send a SOCKS reply. Fixes bug 8427;
5083 bugfix on 0.1.0.1-rc.
5084 - Correctly recognize that [::1] is a loopback address. Fixes
5085 bug 8377; bugfix on 0.2.1.3-alpha.
5086 - Fix a directory authority warn caused when we have a large amount
5087 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
5088 - Don't log inappropriate heartbeat messages when hibernating: a
5089 hibernating node is _expected_ to drop out of the consensus,
5090 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
5091 bugfix on 0.2.3.1-alpha.
5092 - Don't complain about bootstrapping problems while hibernating.
5093 These complaints reflect a general code problem, but not one
5094 with any problematic effects (no connections are actually
5095 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5097 o Documentation fixes:
5098 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
5099 names match. Fixes bug 7768.
5100 - Make the torify manpage no longer refer to tsocks; torify hasn't
5101 supported tsocks since 0.2.3.14-alpha.
5102 - Make the tor manpage no longer reference tsocks.
5103 - Fix the GeoIPExcludeUnknown documentation to refer to
5104 ExcludeExitNodes rather than the currently nonexistent
5105 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
5108 - The tor-tsocks.conf is no longer distributed or installed. We
5109 recommend that tsocks users use torsocks instead. Resolves
5113 Changes in version 0.2.4.11-alpha - 2013-03-11
5114 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
5115 more robust, makes hidden service authentication work again, and
5116 resolves a DPI fingerprint for Tor's SSL transport.
5118 o Major features (directory authorities):
5119 - Directory authorities now support a new consensus method (17)
5120 where they cap the published bandwidth of servers for which
5121 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5122 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5123 serve any v2 directory information. Now we can test disabling the
5124 old deprecated v2 directory format, and see whether doing so has
5125 any effect on network load. Begins to fix bug 6783.
5126 - Directory authorities now include inside each vote a statement of
5127 the performance thresholds they used when assigning flags.
5128 Implements ticket 8151.
5130 o Major bugfixes (directory authorities):
5131 - Stop marking every relay as having been down for one hour every
5132 time we restart a directory authority. These artificial downtimes
5133 were messing with our Stable and Guard flag calculations. Fixes
5134 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5136 o Major bugfixes (hidden services):
5137 - Allow hidden service authentication to succeed again. When we
5138 refactored the hidden service introduction code back
5139 in 0.2.4.1-alpha, we didn't update the code that checks
5140 whether authentication information is present, causing all
5141 authentication checks to return "false". Fix for bug 8207; bugfix
5142 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
5144 o Minor features (relays, bridges):
5145 - Make bridge relays check once a minute for whether their IP
5146 address has changed, rather than only every 15 minutes. Resolves
5148 - Refactor resolve_my_address() so it returns the method by which we
5149 decided our public IP address (explicitly configured, resolved from
5150 explicit hostname, guessed from interfaces, learned by gethostname).
5151 Now we can provide more helpful log messages when a relay guesses
5152 its IP address incorrectly (e.g. due to unexpected lines in
5153 /etc/hosts). Resolves ticket 2267.
5154 - Teach bridge-using clients to avoid 0.2.2 bridges when making
5155 microdescriptor-related dir requests, and only fall back to normal
5156 descriptors if none of their bridges can handle microdescriptors
5157 (as opposed to the fix in ticket 4013, which caused them to fall
5158 back to normal descriptors if *any* of their bridges preferred
5159 them). Resolves ticket 4994.
5160 - Randomize the lifetime of our SSL link certificate, so censors can't
5161 use the static value for filtering Tor flows. Resolves ticket 8443;
5162 related to ticket 4014 which was included in 0.2.2.33.
5163 - Support a new version of the link protocol that allows 4-byte circuit
5164 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
5165 a possible resource exhaustion issue. Closes ticket 7351; implements
5168 o Minor features (portability):
5169 - Tweak the curve25519-donna*.c implementations to tolerate systems
5170 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
5171 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5172 the signs of types during autoconf. This is better than our old
5173 approach, which didn't work when cross-compiling.
5174 - Detect the sign of enum values, rather than assuming that MSC is the
5175 only compiler where enum types are all signed. Fixes bug 7727;
5176 bugfix on 0.2.4.10-alpha.
5178 o Minor features (other):
5179 - Say "KBytes" rather than "KB" in the man page (for various values
5180 of K), to further reduce confusion about whether Tor counts in
5181 units of memory or fractions of units of memory. Resolves ticket 7054.
5182 - Clear the high bit on curve25519 public keys before passing them to
5183 our backend, in case we ever wind up using a backend that doesn't do
5184 so itself. If we used such a backend, and *didn't* clear the high bit,
5185 we could wind up in a situation where users with such backends would
5186 be distinguishable from users without. Fixes bug 8121; bugfix on
5188 - Update to the March 6 2013 Maxmind GeoLite Country database.
5190 o Minor bugfixes (clients):
5191 - When we receive a RELAY_END cell with the reason DONE, or with no
5192 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
5193 status as "connection refused". Previously we reported these cases
5194 as success but then immediately closed the connection. Fixes bug
5195 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
5196 - Downgrade an assertion in connection_ap_expire_beginning to an
5197 LD_BUG message. The fix for bug 8024 should prevent this message
5198 from displaying, but just in case, a warn that we can diagnose
5199 is better than more assert crashes. Fixes bug 8065; bugfix on
5201 - Lower path use bias thresholds to .80 for notice and .60 for warn.
5202 Also make the rate limiting flags for the path use bias log messages
5203 independent from the original path bias flags. Fixes bug 8161;
5204 bugfix on 0.2.4.10-alpha.
5206 o Minor bugfixes (relays):
5207 - Stop trying to resolve our hostname so often (e.g. every time we
5208 think about doing a directory fetch). Now we reuse the cached
5209 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
5210 and 2410 (bugfix on 0.1.2.2-alpha).
5211 - Stop sending a stray "(null)" in some cases for the server status
5212 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
5214 - When choosing which stream on a formerly stalled circuit to wake
5215 first, make better use of the platform's weak RNG. Previously,
5216 we had been using the % ("modulo") operator to try to generate a
5217 1/N chance of picking each stream, but this behaves badly with
5218 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
5220 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5221 Irix's random() only return 15 bits; Solaris's random() returns more
5222 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5223 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5225 o Minor bugfixes (directory authorities):
5226 - Directory authorities now use less space when formatting identical
5227 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
5230 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
5231 - Avoid leaking memory if we fail to compute a consensus signature
5232 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
5233 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
5235 - Fix a memory leak during safe-cookie controller authentication.
5236 Bugfix on 0.2.3.13-alpha.
5237 - Avoid memory leak of IPv6 policy content if we fail to format it into
5238 a router descriptor. Bugfix on 0.2.4.7-alpha.
5240 o Minor bugfixes (other code correctness issues):
5241 - Avoid a crash if we fail to generate an extrainfo descriptor.
5242 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
5244 - When detecting the largest possible file descriptor (in order to
5245 close all file descriptors when launching a new program), actually
5246 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
5247 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
5249 - Fix a copy-and-paste error when adding a missing A1 to a routerset
5250 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
5251 Bugfix on 0.2.4.10-alpha.
5252 - Fix an impossible-to-trigger integer overflow when estimating how
5253 long our onionskin queue would take. (This overflow would require us
5254 to accept 4 million onionskins before processing 100 of them.) Fixes
5255 bug 8210; bugfix on 0.2.4.10-alpha.
5257 o Code simplification and refactoring:
5258 - Add a wrapper function for the common "log a message with a
5262 Changes in version 0.2.4.10-alpha - 2013-02-04
5263 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
5264 certain attacks that flood the network with relays; changes the queue
5265 for circuit create requests from a sized-based limit to a time-based
5266 limit; resumes building with MSVC on Windows; and fixes a wide variety
5269 o Major bugfixes (directory authority):
5270 - When computing directory thresholds, ignore any rejected-as-sybil
5271 nodes during the computation so that they can't influence Fast,
5272 Guard, etc. (We should have done this for proposal 109.) Fixes
5274 - When marking a node as a likely sybil, reset its uptime metrics
5275 to zero, so that it cannot time towards getting marked as Guard,
5276 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5280 - When a TLS write is partially successful but incomplete, remember
5281 that the flushed part has been flushed, and notice that bytes were
5282 actually written. Reported and fixed pseudonymously. Fixes bug
5283 7708; bugfix on Tor 0.1.0.5-rc.
5284 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5285 ID: these could be used to create unexpected streams and circuits
5286 which would count as "present" to some parts of Tor but "absent"
5287 to others, leading to zombie circuits and streams or to a bandwidth
5288 denial-of-service. Fixes bug 7889; bugfix on every released version
5289 of Tor. Reported by "oftc_must_be_destroyed".
5290 - Rename all macros in our local copy of queue.h to begin with "TOR_".
5291 This change seems the only good way to permanently prevent conflicts
5292 with queue.h on various operating systems. Fixes bug 8107; bugfix
5295 o Major features (relay):
5296 - Instead of limiting the number of queued onionskins (aka circuit
5297 create requests) to a fixed, hard-to-configure number, we limit
5298 the size of the queue based on how many we expect to be able to
5299 process in a given amount of time. We estimate the time it will
5300 take to process an onionskin based on average processing time
5301 of previous onionskins. Closes ticket 7291. You'll never have to
5302 configure MaxOnionsPending again.
5304 o Major features (portability):
5305 - Resume building correctly with MSVC and Makefile.nmake. This patch
5306 resolves numerous bugs and fixes reported by ultramage, including
5307 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5308 - Make the ntor and curve25519 code build correctly with MSVC.
5309 Fix on 0.2.4.8-alpha.
5312 - When directory authorities are computing thresholds for flags,
5313 never let the threshold for the Fast flag fall below 4096
5314 bytes. Also, do not consider nodes with extremely low bandwidths
5315 when deciding thresholds for various directory flags. This change
5316 should raise our threshold for Fast relays, possibly in turn
5317 improving overall network performance; see ticket 1854. Resolves
5319 - The Tor client now ignores sub-domain components of a .onion
5320 address. This change makes HTTP "virtual" hosting
5321 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5322 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5323 hosted on the same hidden service. Implements proposal 204.
5324 - We compute the overhead from passing onionskins back and forth to
5325 cpuworkers, and report it when dumping statistics in response to
5326 SIGUSR1. Supports ticket 7291.
5328 o Minor features (path selection):
5329 - When deciding whether we have enough descriptors to build circuits,
5330 instead of looking at raw relay counts, look at which fraction
5331 of (bandwidth-weighted) paths we're able to build. This approach
5332 keeps clients from building circuits if their paths are likely to
5333 stand out statistically. The default fraction of paths needed is
5334 taken from the consensus directory; you can override it with the
5335 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5336 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5337 and we have GeoIP information, also exclude all nodes with unknown
5338 countries "??" and "A1". This behavior is controlled by the
5339 new GeoIPExcludeUnknown option: you can make such nodes always
5340 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5341 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5342 gets you the default behavior. Implements feature 7706.
5343 - Path Use Bias: Perform separate accounting for successful circuit
5344 use. Keep separate statistics on stream attempt rates versus stream
5345 success rates for each guard. Provide configurable thresholds to
5346 determine when to emit log messages or disable use of guards that
5347 fail too many stream attempts. Resolves ticket 7802.
5349 o Minor features (log messages):
5350 - When learning a fingerprint for a bridge, log its corresponding
5351 transport type. Implements ticket 7896.
5352 - Improve the log message when "Bug/attack: unexpected sendme cell
5353 from client" occurs, to help us track bug 8093.
5356 - Remove a couple of extraneous semicolons that were upsetting the
5357 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
5358 bugfix on 0.2.2.1-alpha.
5359 - Remove a source of rounding error during path bias count scaling;
5360 don't count cannibalized circuits as used for path bias until we
5361 actually try to use them; and fix a circuit_package_relay_cell()
5362 warning message about n_chan==NULL. Fixes bug 7802.
5363 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
5364 actually link against nacl when we're configured to use it. Fixes
5365 bug 7972; bugfix on 0.2.4.8-alpha.
5366 - Compile correctly with the --disable-curve25519 option. Fixes
5367 bug 8153; bugfix on 0.2.4.8-alpha.
5369 o Build improvements:
5370 - Do not report status verbosely from autogen.sh unless the -v flag
5371 is specified. Fixes issue 4664. Patch from Onizuka.
5372 - Replace all calls to snprintf() outside of src/ext with
5373 tor_snprintf(). Also remove the #define to replace snprintf with
5374 _snprintf on Windows; they have different semantics, and all of
5375 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5376 - Try to detect if we are ever building on a platform where
5377 memset(...,0,...) does not set the value of a double to 0.0. Such
5378 platforms are permitted by the C standard, though in practice
5379 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5380 currently support them, but it's better to detect them and fail
5381 than to perform erroneously.
5384 - Stop exporting estimates of v2 and v3 directory traffic shares
5385 in extrainfo documents. They were unneeded and sometimes inaccurate.
5386 Also stop exporting any v2 directory request statistics. Resolves
5388 - Drop support for detecting and warning about versions of Libevent
5389 before 1.3e. Nothing reasonable ships with them any longer;
5390 warning the user about them shouldn't be needed. Resolves ticket
5393 o Code simplifications and refactoring:
5394 - Rename "isin" functions to "contains", for grammar. Resolves
5396 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5397 with the natural logarithm function from the system libm. Resolves
5401 Changes in version 0.2.4.9-alpha - 2013-01-15
5402 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5406 - Fix backward compatibility logic when receiving an embedded ntor
5407 handshake tunneled in a CREATE cell. This clears up the "Bug:
5408 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5412 Changes in version 0.2.4.8-alpha - 2013-01-14
5413 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5414 risks, adds a new stronger and faster circuit handshake, and offers
5415 stronger and faster link encryption when both sides support it.
5418 - Preliminary support for directory guards (proposal 207): when
5419 possible, clients now use their entry guards for non-anonymous
5420 directory requests. This can help prevent client enumeration. Note
5421 that this behavior only works when we have a usable consensus
5422 directory, and when options about what to download are more or less
5423 standard. In the future we should re-bootstrap from our guards,
5424 rather than re-bootstrapping from the preconfigured list of
5425 directory sources that ships with Tor. Resolves ticket 6526.
5426 - Tor relays and clients now support a better CREATE/EXTEND cell
5427 format, allowing the sender to specify multiple address, identity,
5428 and handshake types. Implements Robert Ransom's proposal 200;
5431 o Major features (new circuit handshake):
5432 - Tor now supports a new circuit extension handshake designed by Ian
5433 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5434 circuit extension handshake, later called "TAP", was a bit slow
5435 (especially on the relay side), had a fragile security proof, and
5436 used weaker keys than we'd now prefer. The new circuit handshake
5437 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5438 function, making it significantly more secure than the older
5439 handshake, and significantly faster. Tor can use one of two built-in
5440 pure-C curve25519-donna implementations by Adam Langley, or it
5441 can link against the "nacl" library for a tuned version if present.
5443 The built-in version is very fast for 64-bit systems when building
5444 with GCC. The built-in 32-bit version is still faster than the
5445 old TAP protocol, but using libnacl is better on most such hosts.
5447 Clients don't currently use this protocol by default, since
5448 comparatively few clients support it so far. To try it, set
5449 UseNTorHandshake to 1.
5451 Implements proposal 216; closes ticket 7202.
5453 o Major features (better link encryption):
5454 - Relays can now enable the ECDHE TLS ciphersuites when available
5455 and appropriate. These ciphersuites let us negotiate forward-secure
5456 TLS secret keys more safely and more efficiently than with our
5457 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5458 public relays prefer the (faster) P224 group, and bridges prefer
5459 the (more common) P256 group; you can override this with the
5462 Enabling these ciphers was a little tricky, since for a long time,
5463 clients had been claiming to support them without actually doing
5464 so, in order to foil fingerprinting. But with the client-side
5465 implementation of proposal 198 in 0.2.3.17-beta, clients can now
5466 match the ciphers from recent Firefox versions *and* list the
5467 ciphers they actually mean, so relays can believe such clients
5468 when they advertise ECDHE support in their TLS ClientHello messages.
5470 This feature requires clients running 0.2.3.17-beta or later,
5471 and requires both sides to be running OpenSSL 1.0.0 or later
5472 with ECC support. OpenSSL 1.0.1, with the compile-time option
5473 "enable-ec_nistp_64_gcc_128", is highly recommended.
5475 Implements the relay side of proposal 198; closes ticket 7200.
5478 - Avoid crashing when, as a relay without IPv6-exit support, a
5479 client insists on getting an IPv6 address or nothing. Fixes bug
5480 7814; bugfix on 0.2.4.7-alpha.
5483 - Improve circuit build timeout handling for hidden services.
5484 In particular: adjust build timeouts more accurately depending
5485 upon the number of hop-RTTs that a particular circuit type
5486 undergoes. Additionally, launch intro circuits in parallel
5487 if they timeout, and take the first one to reply as valid.
5488 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5489 separate error codes; or at least, don't break for that reason.
5490 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5491 - Update to the January 2 2013 Maxmind GeoLite Country database.
5493 o Minor features (testing):
5494 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5495 (P-256) Diffie-Hellman handshakes to src/or/bench.
5496 - Add benchmark functions to test onion handshake performance.
5498 o Minor features (path bias detection):
5499 - Alter the Path Bias log messages to be more descriptive in terms
5500 of reporting timeouts and other statistics.
5501 - Create three levels of Path Bias log messages, as opposed to just
5502 two. These are configurable via consensus as well as via the torrc
5503 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5504 The default values are 0.70, 0.50, and 0.30 respectively.
5505 - Separate the log message levels from the decision to drop guards,
5506 which also is available via torrc option PathBiasDropGuards.
5507 PathBiasDropGuards still defaults to 0 (off).
5508 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5509 in combination with PathBiasExtremeRate.
5510 - Increase the default values for PathBiasScaleThreshold and
5511 PathBiasCircThreshold from (200, 20) to (300, 150).
5512 - Add in circuit usage accounting to path bias. If we try to use a
5513 built circuit but fail for any reason, it counts as path bias.
5514 Certain classes of circuits where the adversary gets to pick your
5515 destination node are exempt from this accounting. Usage accounting
5516 can be specifically disabled via consensus parameter or torrc.
5517 - Convert all internal path bias state to double-precision floating
5518 point, to avoid roundoff error and other issues.
5519 - Only record path bias information for circuits that have completed
5520 *two* hops. Assuming end-to-end tagging is the attack vector, this
5521 makes us more resilient to ambient circuit failure without any
5522 detection capability loss.
5524 o Minor bugfixes (log messages):
5525 - Rate-limit the "No circuits are opened. Relaxed timeout for a
5526 circuit with channel state open..." message to once per hour to
5527 keep it from filling the notice logs. Mitigates bug 7799 but does
5528 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
5529 - Avoid spurious warnings when configuring multiple client ports of
5530 which only some are nonlocal. Previously, we had claimed that some
5531 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5534 o Code simplifications and refactoring:
5535 - Get rid of a couple of harmless clang warnings, where we compared
5536 enums to ints. These warnings are newly introduced in clang 3.2.
5537 - Split the onion.c file into separate modules for the onion queue
5538 and the different handshakes it supports.
5539 - Remove the marshalling/unmarshalling code for sending requests to
5540 cpuworkers over a socket, and instead just send structs. The
5541 recipient will always be the same Tor binary as the sender, so
5542 any encoding is overkill.
5545 Changes in version 0.2.4.7-alpha - 2012-12-24
5546 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
5547 directory mirrors for more robust bootstrapping; fixes more issues where
5548 clients with changing network conditions refuse to make any circuits;
5549 adds initial support for exiting to IPv6 addresses; resumes being able
5550 to update our GeoIP database, and includes the geoip6 file this time;
5551 turns off the client-side DNS cache by default due to privacy risks;
5552 and fixes a variety of other issues.
5554 o Major features (client resilience):
5555 - Add a new "FallbackDir" torrc option to use when we can't use
5556 a directory mirror from the consensus (either because we lack a
5557 consensus, or because they're all down). Currently, all authorities
5558 are fallbacks by default, and there are no other default fallbacks,
5559 but that will change. This option will allow us to give clients a
5560 longer list of servers to try to get a consensus from when first
5561 connecting to the Tor network, and thereby reduce load on the
5562 directory authorities. Implements proposal 206, "Preconfigured
5563 directory sources for bootstrapping". We also removed the old
5564 "FallbackNetworkstatus" option, since we never got it working well
5565 enough to use it. Closes bug 572.
5566 - If we have no circuits open, use a relaxed timeout (the
5567 95-percentile cutoff) until a circuit succeeds. This heuristic
5568 should allow Tor to succeed at building circuits even when the
5569 network connection drastically changes. Should help with bug 3443.
5571 o Major features (IPv6):
5572 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5573 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5574 exit policy reads as you would like: the address * applies to all
5575 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5576 addresses only. On the client side, you'll need to wait until the
5577 authorities have upgraded, wait for enough exits to support IPv6,
5578 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
5579 ticket 5547, implements proposal 117 as revised in proposal 208.
5581 We DO NOT recommend that clients with actual anonymity needs start
5582 using IPv6 over Tor yet, since not enough exits support it yet.
5584 o Major features (geoip database):
5585 - Maxmind began labelling Tor relays as being in country "A1",
5586 which breaks by-country node selection inside Tor. Now we use a
5587 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5588 file with real country codes. This script fixes about 90% of "A1"
5589 entries automatically and uses manual country code assignments to
5590 fix the remaining 10%. See src/config/README.geoip for details.
5591 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
5592 Country database, as modified above.
5594 o Major bugfixes (client-side DNS):
5595 - Turn off the client-side DNS cache by default. Updating and using
5596 the DNS cache is now configurable on a per-client-port
5597 level. SOCKSPort, DNSPort, etc lines may now contain
5598 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5599 cache these types of DNS answers when we receive them from an
5600 exit node in response to an application request on this port, and
5601 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5602 cached DNS answers of these types, we shouldn't use them. It's
5603 potentially risky to use cached DNS answers at the client, since
5604 doing so can indicate to one exit what answers we've gotten
5605 for DNS lookups in the past. With IPv6, this becomes especially
5606 problematic. Using cached DNS answers for requests on the same
5607 circuit would present less linkability risk, since all traffic
5608 on a circuit is already linkable, but it would also provide
5609 little performance benefit: the exit node caches DNS replies
5610 too. Implements a simplified version of Proposal 205. Implements
5613 o Major bugfixes (other):
5614 - Alter circuit build timeout measurement to start at the point
5615 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5616 initialization). This should make our timeout measurements more
5617 uniform. Previously, we were sometimes including ORconn setup time
5618 in our circuit build time measurements. Should resolve bug 3443.
5619 - Fix an assertion that could trigger in hibernate_go_dormant() when
5620 closing an or_connection_t: call channel_mark_for_close() rather
5621 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
5623 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
5624 7655; bugfix on 0.2.4.6-alpha.
5627 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5628 operators select the address where their pluggable transports will
5629 listen for connections. Resolves ticket 7013.
5630 - Allow an optional $ before the node identity digest in the
5631 controller command GETINFO ns/id/<identity>, for consistency with
5632 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5633 - Log packaged cell fullness as part of the heartbeat message.
5634 Diagnosis to try to determine the extent of bug 7743.
5636 o Minor features (IPv6):
5637 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5638 prefer to hand out virtual IPv6 addresses, since there are more of
5639 them and we can't run out. To override this behavior and make IPv4
5640 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5641 or DNSPort you're using for resolving. Implements ticket 7571.
5642 - AutomapHostsOnResolve responses are now randomized, to avoid
5643 annoying situations where Tor is restarted and applications
5644 connect to the wrong addresses.
5645 - Never try more than 1000 times to pick a new virtual address when
5646 AutomapHostsOnResolve is set. That's good enough so long as we
5647 aren't close to handing out our entire virtual address space;
5648 if you're getting there, it's best to switch to IPv6 virtual
5652 - The ADDRMAP command can no longer generate an ill-formed error
5653 code on a failed MAPADDRESS. It now says "internal" rather than
5654 an English sentence fragment with spaces in the middle. Bugfix on
5656 - Fix log messages and comments to avoid saying "GMT" when we mean
5657 "UTC". Fixes bug 6113.
5658 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5660 - Fix a crash when debugging unit tests on Windows: deallocate a
5661 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5662 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5665 - The DirServer option is now DirAuthority, for consistency with
5666 current naming patterns. You can still use the old DirServer form.
5668 o Code simplification and refactoring:
5669 - Move the client-side address-map/virtual-address/DNS-cache code
5670 out of connection_edge.c into a new addressmap.c module.
5671 - Remove unused code for parsing v1 directories and "running routers"
5672 documents. Fixes bug 6887.
5675 Changes in version 0.2.3.25 - 2012-11-19
5676 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
5677 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
5678 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5679 programmer, and friend. Unstinting in his dedication to the cause of
5680 freedom, he inspired and helped many of us as we began our work on
5681 anonymity, and inspires us still. Please honor his memory by writing
5682 software to protect people's freedoms, and by helping others to do so.
5684 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
5685 significantly reduced directory overhead (via microdescriptors),
5686 enormous crypto performance improvements for fast relays on new
5687 enough hardware, a new v3 TLS handshake protocol that can better
5688 resist fingerprinting, support for protocol obfuscation plugins (aka
5689 pluggable transports), better scalability for hidden services, IPv6
5690 support for bridges, performance improvements like allowing clients
5691 to skip the first round-trip on the circuit ("optimistic data") and
5692 refilling token buckets more often, a new "stream isolation" design
5693 to isolate different applications on different circuits, and many
5694 stability, security, and privacy fixes.
5697 - Tor tries to wipe potentially sensitive data after using it, so
5698 that if some subsequent security failure exposes Tor's memory,
5699 the damage will be limited. But we had a bug where the compiler
5700 was eliminating these wipe operations when it decided that the
5701 memory was no longer visible to a (correctly running) program,
5702 hence defeating our attempt at defense in depth. We fix that
5703 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5704 is unlikely to optimize away. Future versions of Tor may use
5705 a less ridiculously heavy approach for this. Fixes bug 7352.
5706 Reported in an article by Andrey Karpov.
5709 - Fix a harmless bug when opting against publishing a relay descriptor
5710 because DisableNetwork is set. Fixes bug 7464; bugfix on
5714 Changes in version 0.2.4.6-alpha - 2012-11-13
5715 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
5716 makes our defense-in-depth memory wiping more reliable, and begins to
5717 count IPv6 addresses in bridge statistics,
5720 - Fix an assertion failure that could occur when closing a connection
5721 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
5723 - Tor tries to wipe potentially sensitive data after using it, so
5724 that if some subsequent security failure exposes Tor's memory,
5725 the damage will be limited. But we had a bug where the compiler
5726 was eliminating these wipe operations when it decided that the
5727 memory was no longer visible to a (correctly running) program,
5728 hence defeating our attempt at defense in depth. We fix that
5729 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5730 is unlikely to optimize away. Future versions of Tor may use
5731 a less ridiculously heavy approach for this. Fixes bug 7352.
5732 Reported in an article by Andrey Karpov.
5735 - Add GeoIP database for IPv6 addresses. The new config option
5737 - Bridge statistics now count bridge clients connecting over IPv6:
5738 bridge statistics files now list "bridge-ip-versions" and
5739 extra-info documents list "geoip6-db-digest". The control protocol
5740 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5741 implementation by "shkoo", addressing ticket 5055.
5744 - Warn when we are binding low ports when hibernation is enabled;
5745 previously we had warned when we were _advertising_ low ports with
5746 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5747 - Fix a harmless bug when opting against publishing a relay descriptor
5748 because DisableNetwork is set. Fixes bug 7464; bugfix on
5750 - Add warning message when a managed proxy dies during configuration.
5751 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
5752 - Fix a linking error when building tor-fw-helper without miniupnp.
5753 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
5754 - Check for closing an or_connection_t without going through correct
5755 channel functions; emit a warning and then call
5756 connection_or_close_for_error() so we don't assert as in bugs 7212
5758 - Compile correctly on compilers without C99 designated initializer
5759 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
5760 - Avoid a possible assert that can occur when channel_send_destroy() is
5761 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
5762 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
5763 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
5764 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
5765 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
5767 o Code simplification and refactoring:
5768 - Start using OpenBSD's implementation of queue.h, so that we don't
5769 need to hand-roll our own pointer and list structures whenever we
5770 need them. (We can't rely on a sys/queue.h, since some operating
5771 systems don't have them, and the ones that do have them don't all
5772 present the same extensions.)
5775 Changes in version 0.2.4.5-alpha - 2012-10-25
5776 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
5777 two important security vulnerabilities that could lead to remotely
5778 triggerable relay crashes, fix a major bug that was preventing clients
5779 from choosing suitable exit nodes, and refactor some of our code.
5781 o Major bugfixes (security, also in 0.2.3.24-rc):
5782 - Fix a group of remotely triggerable assertion failures related to
5783 incorrect link protocol negotiation. Found, diagnosed, and fixed
5784 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5786 - Fix a denial of service attack by which any directory authority
5787 could crash all the others, or by which a single v2 directory
5788 authority could crash everybody downloading v2 directory
5789 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5791 o Major bugfixes (also in 0.2.3.24-rc):
5792 - When parsing exit policy summaries from microdescriptors, we had
5793 previously been ignoring the last character in each one, so that
5794 "accept 80,443,8080" would be treated by clients as indicating
5795 a node that allows access to ports 80, 443, and 808. That would
5796 lead to clients attempting connections that could never work,
5797 and ignoring exit nodes that would support their connections. Now
5798 clients parse these exit policy summaries correctly. Fixes bug 7192;
5799 bugfix on 0.2.3.1-alpha.
5801 o Minor bugfixes (also in 0.2.3.24-rc):
5802 - Clients now consider the ClientRejectInternalAddresses config option
5803 when using a microdescriptor consensus stanza to decide whether
5804 an exit relay would allow exiting to an internal address. Fixes
5805 bug 7190; bugfix on 0.2.3.1-alpha.
5808 - Only disable TLS session ticket support when running as a TLS
5809 server. Now clients will blend better with regular Firefox
5810 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5812 o Code simplification and refactoring:
5813 - Start using OpenBSD's implementation of queue.h (originally by
5815 - Move the entry node code from circuitbuild.c to its own file.
5816 - Move the circuit build timeout tracking code from circuitbuild.c
5820 Changes in version 0.2.3.24-rc - 2012-10-25
5821 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
5822 could lead to remotely triggerable relay crashes, and fixes
5823 a major bug that was preventing clients from choosing suitable exit
5826 o Major bugfixes (security):
5827 - Fix a group of remotely triggerable assertion failures related to
5828 incorrect link protocol negotiation. Found, diagnosed, and fixed
5829 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5831 - Fix a denial of service attack by which any directory authority
5832 could crash all the others, or by which a single v2 directory
5833 authority could crash everybody downloading v2 directory
5834 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5837 - When parsing exit policy summaries from microdescriptors, we had
5838 previously been ignoring the last character in each one, so that
5839 "accept 80,443,8080" would be treated by clients as indicating
5840 a node that allows access to ports 80, 443, and 808. That would
5841 lead to clients attempting connections that could never work,
5842 and ignoring exit nodes that would support their connections. Now
5843 clients parse these exit policy summaries correctly. Fixes bug 7192;
5844 bugfix on 0.2.3.1-alpha.
5847 - Clients now consider the ClientRejectInternalAddresses config option
5848 when using a microdescriptor consensus stanza to decide whether
5849 an exit relay would allow exiting to an internal address. Fixes
5850 bug 7190; bugfix on 0.2.3.1-alpha.
5853 Changes in version 0.2.4.4-alpha - 2012-10-20
5854 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
5855 vulnerability introduced by a change in OpenSSL, fixes a remotely
5856 triggerable assert, and adds new channel_t and circuitmux_t abstractions
5857 that will make it easier to test new connection transport and cell
5858 scheduling algorithms.
5860 o New directory authorities (also in 0.2.3.23-rc):
5861 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5862 authority. Closes ticket 5749.
5864 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
5865 - Disable TLS session tickets. OpenSSL's implementation was giving
5866 our TLS session keys the lifetime of our TLS context objects, when
5867 perfect forward secrecy would want us to discard anything that
5868 could decrypt a link connection as soon as the link connection
5869 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5870 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5871 - Discard extraneous renegotiation attempts once the V3 link
5872 protocol has been initiated. Failure to do so left us open to
5873 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5874 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5876 o Internal abstraction features:
5877 - Introduce new channel_t abstraction between circuits and
5878 or_connection_t to allow for implementing alternate OR-to-OR
5879 transports. A channel_t is an abstract object which can either be a
5880 cell-bearing channel, which is responsible for authenticating and
5881 handshaking with the remote OR and transmitting cells to and from
5882 it, or a listening channel, which spawns new cell-bearing channels
5883 at the request of remote ORs. Implements part of ticket 6465.
5884 - Also new is the channel_tls_t subclass of channel_t, adapting it
5885 to the existing or_connection_t code. The V2/V3 protocol handshaking
5886 code which formerly resided in command.c has been moved below the
5887 channel_t abstraction layer and may be found in channeltls.c now.
5888 Implements the rest of ticket 6465.
5889 - Introduce new circuitmux_t storing the queue of circuits for
5890 a channel; this encapsulates and abstracts the queue logic and
5891 circuit selection policy, and allows the latter to be overridden
5892 easily by switching out a policy object. The existing EWMA behavior
5893 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5895 o Required libraries:
5896 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5897 strongly recommended.
5900 - Warn users who run hidden services on a Tor client with
5901 UseEntryGuards disabled that their hidden services will be
5902 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5903 attack which motivated Tor to support entry guards in the first
5904 place). Resolves ticket 6889.
5905 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5906 dhill. Resolves ticket 6982.
5907 - Option OutboundBindAddress can be specified multiple times and
5908 accepts IPv6 addresses. Resolves ticket 6876.
5910 o Minor bugfixes (also in 0.2.3.23-rc):
5911 - Don't serve or accept v2 hidden service descriptors over a
5912 relay's DirPort. It's never correct to do so, and disabling it
5913 might make it more annoying to exploit any bugs that turn up in the
5914 descriptor-parsing code. Fixes bug 7149.
5915 - Fix two cases in src/or/transports.c where we were calling
5916 fmt_addr() twice in a parameter list. Bug found by David
5917 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5918 - Fix memory leaks whenever we logged any message about the "path
5919 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5920 - When relays refuse a "create" cell because their queue of pending
5921 create cells is too big (typically because their cpu can't keep up
5922 with the arrival rate), send back reason "resource limit" rather
5923 than reason "internal", so network measurement scripts can get a
5924 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
5927 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5928 - Free some more still-in-use memory at exit, to make hunting for
5929 memory leaks easier. Resolves bug 7029.
5930 - When a Tor client gets a "truncated" relay cell, the first byte of
5931 its payload specifies why the circuit was truncated. We were
5932 ignoring this 'reason' byte when tearing down the circuit, resulting
5933 in the controller not being told why the circuit closed. Now we
5934 pass the reason from the truncated cell to the controller. Bugfix
5935 on 0.1.2.3-alpha; fixes bug 7039.
5936 - Downgrade "Failed to hand off onionskin" messages to "debug"
5937 severity, since they're typically redundant with the "Your computer
5938 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5939 - Make clients running with IPv6 bridges connect over IPv6 again,
5940 even without setting new config options ClientUseIPv6 and
5941 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
5942 - Use square brackets around IPv6 addresses in numerous places
5943 that needed them, including log messages, HTTPS CONNECT proxy
5944 requests, TransportProxy statefile entries, and pluggable transport
5945 extra-info lines. Fixes bug 7011; patch by David Fifield.
5947 o Code refactoring and cleanup:
5948 - Source files taken from other packages now reside in src/ext;
5949 previously they were scattered around the rest of Tor.
5950 - Avoid use of reserved identifiers in our C code. The C standard
5951 doesn't like us declaring anything that starts with an
5952 underscore, so let's knock it off before we get in trouble. Fix
5953 for bug 1031; bugfix on the first Tor commit.
5956 Changes in version 0.2.3.23-rc - 2012-10-20
5957 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
5958 vulnerability introduced by a change in OpenSSL, and fixes a variety
5959 of smaller bugs in preparation for the release.
5961 o New directory authorities:
5962 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5963 authority. Closes ticket 5749.
5965 o Major bugfixes (security/privacy):
5966 - Disable TLS session tickets. OpenSSL's implementation was giving
5967 our TLS session keys the lifetime of our TLS context objects, when
5968 perfect forward secrecy would want us to discard anything that
5969 could decrypt a link connection as soon as the link connection
5970 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5971 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5972 - Discard extraneous renegotiation attempts once the V3 link
5973 protocol has been initiated. Failure to do so left us open to
5974 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5975 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5978 - Fix a possible crash bug when checking for deactivated circuits
5979 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5980 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5982 o Minor bugfixes (on 0.2.3.x):
5983 - Fix two cases in src/or/transports.c where we were calling
5984 fmt_addr() twice in a parameter list. Bug found by David
5985 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5986 - Convert an assert in the pathbias code to a log message. The assert
5987 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5988 bugfix on 0.2.3.17-beta.
5989 - Fix memory leaks whenever we logged any message about the "path
5990 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5992 o Minor bugfixes (on 0.2.2.x and earlier):
5993 - Don't serve or accept v2 hidden service descriptors over a relay's
5994 DirPort. It's never correct to do so, and disabling it might
5995 make it more annoying to exploit any bugs that turn up in the
5996 descriptor-parsing code. Fixes bug 7149.
5997 - When relays refuse a "create" cell because their queue of pending
5998 create cells is too big (typically because their cpu can't keep up
5999 with the arrival rate), send back reason "resource limit" rather
6000 than reason "internal", so network measurement scripts can get a
6001 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6002 - Correct file sizes when reading binary files on Cygwin, to avoid
6003 a bug where Tor would fail to read its state file. Fixes bug 6844;
6004 bugfix on 0.1.2.7-alpha.
6005 - Avoid undefined behavior when parsing the list of supported
6006 rendezvous/introduction protocols in a hidden service descriptor.
6007 Previously, Tor would have confused (as-yet-unused) protocol version
6008 numbers greater than 32 with lower ones on many platforms. Fixes
6009 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6011 o Documentation fixes:
6012 - Clarify that hidden services are TCP only. Fixes bug 6024.
6015 Changes in version 0.2.4.3-alpha - 2012-09-22
6016 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
6017 assertion, resumes letting relays test reachability of their DirPort,
6018 and cleans up a bunch of smaller bugs.
6021 - Fix an assertion failure in tor_timegm() that could be triggered
6022 by a badly formatted directory object. Bug found by fuzzing with
6023 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6026 - Fix a possible crash bug when checking for deactivated circuits
6027 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6028 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6029 - Allow routers to detect that their own DirPorts are running. When
6030 we removed support for versions_supports_begindir, we also
6031 accidentally removed the mechanism we used to self-test our
6032 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
6033 bugfix on 0.2.4.2-alpha.
6035 o Security features:
6036 - Switch to a completely time-invariant approach for picking nodes
6037 weighted by bandwidth. Our old approach would run through the
6038 part of the loop after it had made its choice slightly slower
6039 than it ran through the part of the loop before it had made its
6040 choice. Addresses ticket 6538.
6041 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
6042 by tor2web clients allows hidden services to identify tor2web
6043 clients through their repeated selection of the same rendezvous
6044 and introduction point circuit endpoints (their guards). Resolves
6048 - Enable Tor to read configuration, state, and key information from
6049 a FIFO. Previously Tor would only read from files with a positive
6050 stat.st_size. Code from meejah; fixes bug 6044.
6053 - Correct file sizes when reading binary files on Cygwin, to avoid
6054 a bug where Tor would fail to read its state file. Fixes bug 6844;
6055 bugfix on 0.1.2.7-alpha.
6056 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6057 bugfix on 0.2.0.3-alpha.
6058 - When complaining about a client port on a public address, log
6059 which address we're complaining about. Fixes bug 4020; bugfix on
6060 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6061 - Convert an assert in the pathbias code to a log message. The assert
6062 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6063 bugfix on 0.2.3.17-beta.
6064 - Our new buildsystem was overzealous about rebuilding manpages: it
6065 would rebuild them all whenever any one of them changed. Now our
6066 dependency checking should be correct. Fixes bug 6843; bugfix on
6068 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
6069 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
6070 - Correct log printout about which address family is preferred
6071 when connecting to a bridge with both an IPv4 and IPv6 OR port.
6072 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
6074 o Minor bugfixes (code cleanliness):
6075 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6076 with large values. This situation was untriggered, but nevertheless
6077 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6078 - Reject consensus votes with more than 64 known-flags. We aren't even
6079 close to that limit yet, and our code doesn't handle it correctly.
6080 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6081 - Avoid undefined behavior when parsing the list of supported
6082 rendezvous/introduction protocols in a hidden service descriptor.
6083 Previously, Tor would have confused (as-yet-unused) protocol version
6084 numbers greater than 32 with lower ones on many platforms. Fixes
6085 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6086 - Fix handling of rendezvous client authorization types over 8.
6087 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6088 - Fix building with older versions of GCC (2.95, for one) that don't
6089 like preprocessor directives inside macro arguments. Found by
6090 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
6091 - Switch weighted node selection rule from using a list of doubles
6092 to using a list of int64_t. This change should make the process
6093 slightly easier to debug and maintain. Needed to finish ticket 6538.
6095 o Code simplification and refactoring:
6096 - Move the generic "config" code into a new file, and have "config.c"
6097 hold only torrc- and state-related code. Resolves ticket 6823.
6098 - Move the core of our "choose a weighted element at random" logic
6099 into its own function, and give it unit tests. Now the logic is
6100 testable, and a little less fragile too.
6101 - Removed the testing_since field of node_t, which hasn't been used
6102 for anything since 0.2.0.9-alpha.
6104 o Documentation fixes:
6105 - Clarify that hidden services are TCP only. Fixes bug 6024.
6106 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6110 Changes in version 0.2.3.22-rc - 2012-09-11
6111 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
6115 - Fix an assertion failure in tor_timegm() that could be triggered
6116 by a badly formatted directory object. Bug found by fuzzing with
6117 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6120 - Avoid segfault when starting up having run with an extremely old
6121 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6125 Changes in version 0.2.2.39 - 2012-09-11
6126 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
6130 - Fix an assertion failure in tor_timegm() that could be triggered
6131 by a badly formatted directory object. Bug found by fuzzing with
6132 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6133 - Do not crash when comparing an address with port value 0 to an
6134 address policy. This bug could have been used to cause a remote
6135 assertion failure by or against directory authorities, or to
6136 allow some applications to crash clients. Fixes bug 6690; bugfix
6140 Changes in version 0.2.4.2-alpha - 2012-09-10
6141 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
6142 raises the default rate limiting even more, and makes the bootstrapping
6143 log messages less noisy.
6146 - Automatically forward the TCP ports of pluggable transport
6147 proxies using tor-fw-helper if PortForwarding is enabled. Implements
6151 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
6152 to 1GB/1GB. The previous defaults were intended to be "basically
6153 infinite", but it turns out they're now limiting our 100mbit+
6154 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
6155 last time we raised it).
6158 - Detect when we're running with a version of OpenSSL other than the
6159 one we compiled with. This has occasionally given people hard-to-
6161 - Log fewer lines at level "notice" about our OpenSSL and Libevent
6162 versions and capabilities when everything is going right. Resolves
6163 part of ticket 6736.
6164 - Directory authorities no long accept descriptors for any version of
6165 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
6166 These versions are insecure, unsupported, or both. Implements
6170 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6171 to start with a triple-underscore so the controller won't touch it.
6172 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6173 - Avoid segfault when starting up having run with an extremely old
6174 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6176 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6177 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6178 - Don't follow the NULL pointer if microdescriptor generation fails.
6179 (This does not appear to be triggerable, but it's best to be safe.)
6180 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
6181 - Fix mis-declared dependencies on src/common/crypto.c and
6182 src/or/tor_main.c that could break out-of-tree builds under some
6183 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
6184 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
6185 6778; bugfix on 0.2.4.1-alpha.
6186 - Fix a harmless (in this case) build warning for implicitly
6187 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
6190 - Now that all versions before 0.2.2.x are disallowed, we no longer
6191 need to work around their missing features. Thus we can remove a
6192 bunch of compatibility code.
6195 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
6196 TCP ports to forward. In the past it only accepted two ports:
6197 the ORPort and the DirPort.
6200 Changes in version 0.2.4.1-alpha - 2012-09-05
6201 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
6202 bridgedb; lets relays use IPv6 addresses and directory authorities
6203 advertise them; and switches to a cleaner build interface.
6205 This is the first alpha release in a new series, so expect there to
6206 be bugs. Users who would rather test out a more stable branch should
6207 stay with 0.2.3.x for now.
6209 o Major features (bridges):
6210 - Bridges now report the pluggable transports they support to the
6211 bridge authority, so it can pass the supported transports on to
6212 bridgedb and/or eventually do reachability testing. Implements
6215 o Major features (IPv6):
6216 - Bridge authorities now accept IPv6 bridge addresses and include
6217 them in network status documents. Implements ticket 5534.
6218 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
6219 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
6220 to happen. Implements ticket 5535.
6221 - All kind of relays, not just bridges, can now advertise an IPv6
6222 OR port. Implements ticket 6362.
6223 - Directory authorities vote on IPv6 OR ports using the new consensus
6224 method 14. Implements ticket 6363.
6226 o Major features (build):
6227 - Switch to a nonrecursive Makefile structure. Now instead of each
6228 Makefile.am invoking other Makefile.am's, there is a master
6229 Makefile.am that includes the others. This change makes our build
6230 process slightly more maintainable, and improves parallelism for
6231 building with make -j. Original patch by Stewart Smith; various
6232 fixes by Jim Meyering.
6233 - Where available, we now use automake's "silent" make rules by
6234 default, so that warnings are easier to spot. You can get the old
6235 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
6237 o Minor features (code security and spec conformance):
6238 - Clear keys and key-derived material left on the stack in
6239 rendservice.c and rendclient.c. Check return value of
6240 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
6241 These fixes should make us more forward-secure against cold-boot
6242 attacks and the like. Fixes bug 2385.
6243 - Reject EXTEND cells sent to nonexistent streams. According to the
6244 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
6245 we were only checking for stream IDs that were currently in use.
6246 Found while hunting for more instances of bug 6271. Bugfix on
6247 0.0.2pre8, which introduced incremental circuit construction.
6249 o Minor features (streamlining);
6250 - No longer include the "opt" prefix when generating routerinfos
6251 or v2 directories: it has been needless since Tor 0.1.2. Closes
6253 - Remove some now-needless code that tried to aggressively flush
6254 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6255 cell queue logic has saved us from the failure mode that this code
6256 was supposed to prevent. Removing this code will limit the number
6257 of baroque control flow paths through Tor's network logic. Reported
6258 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6260 o Minor features (controller):
6261 - Add a "GETINFO signal/names" control port command. Implements
6263 - Provide default values for all options via "GETINFO config/defaults".
6264 Implements ticket 4971.
6266 o Minor features (IPv6):
6267 - New config option "AuthDirHasIPv6Connectivity 1" that directory
6268 authorities should set if they have IPv6 connectivity and want to
6269 do reachability tests for IPv6 relays. Implements feature 5974.
6270 - A relay with an IPv6 OR port now sends that address in NETINFO
6271 cells (in addition to its other address). Implements ticket 6364.
6273 o Minor features (log messages):
6274 - Omit the first heartbeat log message, because it never has anything
6275 useful to say, and it clutters up the bootstrapping messages.
6276 Resolves ticket 6758.
6277 - Don't log about reloading the microdescriptor cache at startup. Our
6278 bootstrap warnings are supposed to tell the user when there's a
6279 problem, and our bootstrap notices say when there isn't. Resolves
6280 ticket 6759; bugfix on 0.2.2.6-alpha.
6281 - Don't log "I learned some more directory information" when we're
6282 reading cached directory information. Reserve it for when new
6283 directory information arrives in response to a fetch. Resolves
6285 - Prevent rounding error in path bias counts when scaling
6286 them down, and use the correct scale factor default. Also demote
6287 some path bias related log messages down a level and make others
6288 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
6289 - We no longer warn so much when generating manpages from their
6292 o Code simplifications and refactoring:
6293 - Enhance our internal sscanf replacement so that we can eliminate
6294 the last remaining uses of the system sscanf. (Though those uses
6295 of sscanf were safe, sscanf itself is generally error prone, so
6296 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6298 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6299 - Move last_reachable and testing_since from routerinfo_t to node_t.
6300 Implements ticket 5529.
6301 - Add replaycache_t structure, functions and unit tests, then refactor
6302 rend_service_introduce() to be more clear to read, improve, debug,
6303 and test. Resolves bug 6177.
6304 - Finally remove support for malloc_good_size and malloc_usable_size.
6305 We had hoped that these functions would let us eke a little more
6306 memory out of our malloc implementation. Unfortunately, the only
6307 implementations that provided these functions are also ones that
6308 are already efficient about not overallocation: they never got us
6309 more than 7 or so bytes per allocation. Removing them saves us a
6310 little code complexity and a nontrivial amount of build complexity.
6313 - Tor maintainers now require Automake version 1.9 or later to build
6314 Tor from the Git repository. (Automake is not required when building
6315 from a source distribution.)
6318 Changes in version 0.2.3.21-rc - 2012-09-05
6319 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
6320 series. It fixes a trio of potential security bugs, fixes a bug where
6321 we were leaving some of the fast relays out of the microdescriptor
6322 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
6323 and cleans up other smaller issues.
6325 o Major bugfixes (security):
6326 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6327 could use this trick to make their circuits receive cells faster
6328 than our flow control would have allowed, or to gum up the network,
6329 or possibly to do targeted memory denial-of-service attacks on
6330 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6331 from July 2002, before the release of Tor 0.0.0. We had committed
6332 this patch previously, but we had to revert it because of bug 6271.
6333 Now that 6271 is fixed, this patch appears to work.
6334 - Reject any attempt to extend to an internal address. Without
6335 this fix, a router could be used to probe addresses on an internal
6336 network to see whether they were accepting connections. Fixes bug
6337 6710; bugfix on 0.0.8pre1.
6338 - Do not crash when comparing an address with port value 0 to an
6339 address policy. This bug could have been used to cause a remote
6340 assertion failure by or against directory authorities, or to
6341 allow some applications to crash clients. Fixes bug 6690; bugfix
6345 - Remove the upper bound on microdescriptor length. We were hitting
6346 the limit for routers with complex exit policies or family
6347 declarations, causing clients to not use them. Fixes the first
6348 piece of bug 6404; fix on 0.2.2.6-alpha.
6349 - Detect "ORPort 0" as meaning, uniformly, that we're not running
6350 as a relay. Previously, some of our code would treat the presence
6351 of any ORPort line as meaning that we should act like a relay,
6352 even though our new listener code would correctly not open any
6353 ORPorts for ORPort 0. Similar bugs in other Port options are also
6354 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
6357 - Avoid a pair of double-free and use-after-mark bugs that can
6358 occur with certain timings in canceled and re-received DNS
6359 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6360 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6361 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6362 - Allow one-hop directory fetching circuits the full "circuit build
6363 timeout" period, rather than just half of it, before failing them
6364 and marking the relay down. This fix should help reduce cases where
6365 clients declare relays (or worse, bridges) unreachable because
6366 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6367 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6369 - Authorities no longer include any router in their microdescriptor
6370 consensuses for which they couldn't generate or agree on a
6371 microdescriptor. Fixes the second piece of bug 6404; fix on
6373 - Detect and reject attempts to specify both "FooPort" and
6374 "FooPort 0" in the same configuration domain. (It's still okay
6375 to have a FooPort in your configuration file, and use "FooPort 0"
6376 on the command line to disable it.) Fixes the second half of bug
6377 6507; bugfix on 0.2.3.3-alpha.
6378 - Make wildcarded addresses (that is, ones beginning with "*.") work
6379 when provided via the controller's MapAddress command. Previously,
6380 they were accepted, but we never actually noticed that they were
6381 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
6382 - Avoid crashing on a malformed state file where EntryGuardPathBias
6383 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
6384 - Add a (probably redundant) memory clear between iterations of
6385 the router status voting loop, to prevent future coding errors
6386 where data might leak between iterations of the loop. Resolves
6389 o Minor bugfixes (log messages):
6390 - Downgrade "set buildtimeout to low value" messages to "info"
6391 severity; they were never an actual problem, there was never
6392 anything reasonable to do about them, and they tended to spam logs
6393 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6394 - Downgrade path-bias warning messages to "info". We'll try to get
6395 them working better in 0.2.4. Add internal circuit construction
6396 state to protect against the noisy warn message "Unexpectedly high
6397 circuit_successes". Also add some additional rate-limited notice
6398 messages to help determine the root cause of the warn. Fixes bug
6399 6475. Bugfix against 0.2.3.17-beta.
6400 - Move log message when unable to find a microdesc in a routerstatus
6401 entry to parse time. Previously we'd spam this warning every time
6402 we tried to figure out which microdescriptors to download. Fixes
6403 the third piece of bug 6404; fix on 0.2.3.18-rc.
6406 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6407 change when the authority is deciding whether to accept a newly
6408 uploaded descriptor. Implements ticket 6423.
6409 - Add missing documentation for consensus and microdesc files.
6410 Resolves ticket 6732.
6413 Changes in version 0.2.2.38 - 2012-08-12
6414 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6415 attack that could in theory leak path information.
6418 - Avoid an uninitialized memory read when reading a vote or consensus
6419 document that has an unrecognized flavor name. This read could
6420 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6421 - Try to leak less information about what relays a client is
6422 choosing to a side-channel attacker. Previously, a Tor client would
6423 stop iterating through the list of available relays as soon as it
6424 had chosen one, thus finishing a little earlier when it picked
6425 a router earlier in the list. If an attacker can recover this
6426 timing information (nontrivial but not proven to be impossible),
6427 they could learn some coarse-grained information about which relays
6428 a client was picking (middle nodes in particular are likelier to
6429 be affected than exits). The timing attack might be mitigated by
6430 other factors (see bug 6537 for some discussion), but it's best
6431 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6434 Changes in version 0.2.3.20-rc - 2012-08-05
6435 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6436 series. It fixes a pair of code security bugs and a potential anonymity
6437 issue, updates our RPM spec files, and cleans up other smaller issues.
6440 - Avoid read-from-freed-memory and double-free bugs that could occur
6441 when a DNS request fails while launching it. Fixes bug 6480;
6442 bugfix on 0.2.0.1-alpha.
6443 - Avoid an uninitialized memory read when reading a vote or consensus
6444 document that has an unrecognized flavor name. This read could
6445 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6446 - Try to leak less information about what relays a client is
6447 choosing to a side-channel attacker. Previously, a Tor client would
6448 stop iterating through the list of available relays as soon as it
6449 had chosen one, thus finishing a little earlier when it picked
6450 a router earlier in the list. If an attacker can recover this
6451 timing information (nontrivial but not proven to be impossible),
6452 they could learn some coarse-grained information about which relays
6453 a client was picking (middle nodes in particular are likelier to
6454 be affected than exits). The timing attack might be mitigated by
6455 other factors (see bug 6537 for some discussion), but it's best
6456 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6459 - Try to make the warning when giving an obsolete SOCKSListenAddress
6460 a little more useful.
6461 - Terminate active server managed proxies if Tor stops being a
6462 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
6463 - Provide a better error message about possible OSX Asciidoc failure
6464 reasons. Fixes bug 6436.
6465 - Warn when Tor is configured to use accounting in a way that can
6466 link a hidden service to some other hidden service or public
6467 address. Resolves ticket 6490.
6470 - Check return value of fputs() when writing authority certificate
6471 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6472 - Ignore ServerTransportPlugin lines when Tor is not configured as
6473 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
6474 - When disabling guards for having too high a proportion of failed
6475 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
6479 - Update our default RPM spec files to work with mock and rpmbuild
6480 on RHEL/Fedora. They have an updated set of dependencies and
6481 conflicts, a fix for an ancient typo when creating the "_tor"
6482 user, and better instructions. Thanks to Ondrej Mikle for the
6483 patch series. Fixes bug 6043.
6486 - Make it possible to set the TestingTorNetwork configuration
6487 option using AlternateDirAuthority and AlternateBridgeAuthority
6488 as an alternative to setting DirServer. Addresses ticket 6377.
6491 - Clarify the documentation for the Alternate*Authority options.
6493 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
6495 o Code simplification and refactoring:
6496 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
6497 10 lines. Also, don't nest them. Doing so in the past has
6498 led to hard-to-debug code. The new style is to use the
6499 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
6502 Changes in version 0.2.3.19-rc - 2012-07-06
6503 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
6504 series. It fixes the compile on Windows, reverts to a GeoIP database
6505 that isn't as broken, and fixes a flow control bug that has been around
6506 since the beginning of Tor.
6509 - Fix a bug handling SENDME cells on nonexistent streams that could
6510 result in bizarre window values. Report and patch contributed
6511 pseudonymously. Fixes part of bug 6271. This bug was introduced
6512 before the first Tor release, in svn commit r152.
6513 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
6514 June 2012 database, Maxmind marked many Tor relays as country "A1",
6515 which will cause risky behavior for clients that set EntryNodes
6516 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
6517 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
6518 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
6521 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
6522 bugfix on 0.2.1.10-alpha.
6525 Changes in version 0.2.3.18-rc - 2012-06-28
6526 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
6527 series. It fixes a few smaller bugs, but generally appears stable.
6528 Please test it and let us know whether it is!
6531 - Allow wildcarded mapaddress targets to be specified on the
6532 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
6533 - Make our linker option detection code more robust against linkers
6534 such as on FreeBSD 8, where a bad combination of options completes
6535 successfully but makes an unrunnable binary. Fixes bug 6173;
6536 bugfix on 0.2.3.17-beta.
6538 o Minor bugfixes (on 0.2.2.x and earlier):
6539 - Avoid a false positive in the util/threads unit test by increasing
6540 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6541 - Replace "Sending publish request" log messages with "Launching
6542 upload", so that they no longer confusingly imply that we're
6543 sending something to a directory we might not even be connected
6544 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6545 - Make sure to set *socket_error in all error cases in
6546 connection_connect(), so it can't produce a warning about
6547 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6548 0.2.1.1-alpha; resolves ticket 6028.
6549 - Downgrade "Got a certificate, but we already have it" log messages
6550 from warning to info, except when we're a dirauth. Fixes bug 5238;
6551 bugfix on 0.2.1.7-alpha.
6552 - When checking for requested signatures on the latest consensus
6553 before serving it to a client, make sure to check the right
6554 consensus flavor. Bugfix on 0.2.2.6-alpha.
6555 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6556 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6558 o Minor bugfixes (on 0.2.3.x):
6559 - Make format_helper_exit_status() avoid unnecessary space padding
6560 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
6562 - Downgrade a message about cleaning the microdescriptor cache to
6563 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
6564 - Log a BUG message at severity INFO if we have a networkstatus with
6565 a missing entry for some microdescriptor. Continues on a patch
6567 - Improve the log message when a managed proxy fails to launch. Fixes
6568 bug 5099; bugfix on 0.2.3.6-alpha.
6569 - Don't do DNS lookups when parsing corrupted managed proxy protocol
6570 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
6571 - When formatting wildcarded address mappings for the controller,
6572 be sure to include "*." as appropriate. Partially fixes bug 6244;
6573 bugfix on 0.2.3.9-alpha.
6574 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
6575 Bugfix on 0.2.3.13-alpha.
6576 - Stop logging messages about running with circuit timeout learning
6577 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
6578 - Disable a spurious warning about reading on a marked and flushing
6579 connection. We shouldn't be doing that, but apparently we
6580 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
6581 - Fix a bug that stopped AllowDotExit from working on addresses
6582 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
6585 o Code simplification, refactoring, unit tests:
6586 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6587 Libevent's notion of cached time when possible.
6588 - Remove duplicate code for invoking getrlimit() from control.c.
6589 - Add a unit test for the environment_variable_names_equal function.
6592 - Document the --defaults-torrc option, and the new (in 0.2.3)
6593 semantics for overriding, extending, and clearing lists of
6594 options. Closes bug 4748.
6597 Changes in version 0.2.3.17-beta - 2012-06-15
6598 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
6599 gets our TLS handshake back on track for being able to blend in with
6600 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
6601 with Vidalia, and otherwise continues to get us closer to a release
6605 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6606 - Update TLS cipher list to match Firefox 8 and later. Resolves
6608 - Implement the client side of proposal 198: remove support for
6609 clients falsely claiming to support standard ciphersuites that
6610 they can actually provide. As of modern OpenSSL versions, it's not
6611 necessary to fake any standard ciphersuite, and doing so prevents
6612 us from using better ciphersuites in the future, since servers
6613 can't know whether an advertised ciphersuite is really supported or
6614 not. Some hosts -- notably, ones with very old versions of OpenSSL
6615 or where OpenSSL has been built with ECC disabled -- will stand
6616 out because of this change; TBB users should not be affected.
6619 - Change the default value for DynamicDHGroups (introduced in
6620 0.2.3.9-alpha) to 0. This feature can make Tor relays less
6621 identifiable by their use of the mod_ssl DH group, but at
6622 the cost of some usability (#4721) and bridge tracing (#6087)
6623 regressions. Resolves ticket 5598.
6624 - Send a CRLF at the end of each STATUS_* control protocol event. This
6625 bug tickled a bug in Vidalia which would make it freeze. Fixes
6626 bug 6094; bugfix on 0.2.3.16-alpha.
6629 - Disable writing on marked-for-close connections when they are
6630 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6631 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6632 case for flushing marked connections.
6633 - Detect SSL handshake even when the initial attempt to write the
6634 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6635 - Change the AllowDotExit rules so they should actually work.
6636 We now enforce AllowDotExit only immediately after receiving an
6637 address via SOCKS or DNSPort: other sources are free to provide
6638 .exit addresses after the resolution occurs. Fixes bug 3940;
6639 bugfix on 0.2.2.1-alpha.
6640 - Fix a (harmless) integer overflow in cell statistics reported by
6641 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6642 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
6643 right places and never depends on the consensus parameters or
6644 computes adaptive timeouts when it is disabled. Fixes bug 5049;
6645 bugfix on 0.2.2.14-alpha.
6646 - When building Tor on Windows with -DUNICODE (not default), ensure
6647 that error messages, filenames, and DNS server names are always
6648 NUL-terminated when we convert them to a single-byte encoding.
6649 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6650 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6651 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6652 - Fix an edge case where TestingTorNetwork is set but the authorities
6653 and relays all have an uptime of zero, where the private Tor network
6654 could briefly lack support for hidden services. Fixes bug 3886;
6655 bugfix on 0.2.2.18-alpha.
6656 - Correct the manpage's descriptions for the default values of
6657 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
6659 - Fix the documentation for the --hush and --quiet command line
6660 options, which changed their behavior back in 0.2.3.3-alpha.
6661 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
6665 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6666 more information to it, so that we can track it down in case it
6667 returns again. Mitigates bug 5235.
6668 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6669 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6670 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
6671 - Warn the user when HTTPProxy, but no other proxy type, is
6672 configured. This can cause surprising behavior: it doesn't send
6673 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6674 directory traffic only. Resolves ticket 4663.
6675 - Issue a notice if a guard completes less than 40% of your circuits.
6676 Threshold is configurable by torrc option PathBiasNoticeRate and
6677 consensus parameter pb_noticepct. There is additional, off-by-
6678 default code to disable guards which fail too many circuits.
6679 Addresses ticket 5458.
6680 - Update to the June 6 2012 Maxmind GeoLite Country database.
6682 o Code simplifications and refactoring:
6683 - Remove validate_pluggable_transports_config(): its warning
6684 message is now handled by connection_or_connect().
6687 Changes in version 0.2.2.37 - 2012-06-06
6688 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
6689 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6693 - Work around a bug in OpenSSL that broke renegotiation with TLS
6694 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6695 the v2 Tor connection protocol when both sides were using OpenSSL
6696 1.0.1 would fail. Resolves ticket 6033.
6697 - When waiting for a client to renegotiate, don't allow it to add
6698 any bytes to the input buffer. This fixes a potential DoS issue.
6699 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6700 - Fix an edge case where if we fetch or publish a hidden service
6701 descriptor, we might build a 4-hop circuit and then use that circuit
6702 for exiting afterwards -- even if the new last hop doesn't obey our
6703 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6706 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6707 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6710 - Tell GCC and Clang to check for any errors in format strings passed
6711 to the tor_v*(print|scan)f functions.
6714 Changes in version 0.2.3.16-alpha - 2012-06-05
6715 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
6716 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6717 currently). It also fixes a variety of smaller bugs and other cleanups
6718 that get us closer to a release candidate.
6720 o Major bugfixes (general):
6721 - Work around a bug in OpenSSL that broke renegotiation with TLS
6722 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6723 the v2 Tor connection protocol when both sides were using OpenSSL
6724 1.0.1 would fail. Resolves ticket 6033.
6725 - When waiting for a client to renegotiate, don't allow it to add
6726 any bytes to the input buffer. This fixes a potential DoS issue.
6727 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6728 - Pass correct OR address to managed proxies (like obfsproxy),
6729 even when ORListenAddress is used. Fixes bug 4865; bugfix on
6731 - The advertised platform of a router now includes only its operating
6732 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
6733 service pack level (for Windows) or its CPU architecture (for Unix).
6734 We also no longer include the "git-XYZ" tag in the version. Resolves
6737 o Major bugfixes (clients):
6738 - If we are unable to find any exit that supports our predicted ports,
6739 stop calling them predicted, so that we don't loop and build
6740 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6741 which introduced predicted ports.
6742 - Fix an edge case where if we fetch or publish a hidden service
6743 descriptor, we might build a 4-hop circuit and then use that circuit
6744 for exiting afterwards -- even if the new last hop doesn't obey our
6745 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6746 - Check at each new consensus whether our entry guards were picked
6747 long enough ago that we should rotate them. Previously, we only
6748 did this check at startup, which could lead to us holding a guard
6749 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6750 - When fetching a bridge descriptor from a bridge authority,
6751 always do so anonymously, whether we have been able to open
6752 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6753 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6754 but we'll need to wait for bug 6010 before it's actually usable.
6756 o Major bugfixes (directory authorities):
6757 - When computing weight parameters, behave more robustly in the
6758 presence of a bad bwweightscale value. Previously, the authorities
6759 would crash if they agreed on a sufficiently broken weight_scale
6760 value: now, they use a reasonable default and carry on. Partial
6761 fix for 5786; bugfix on 0.2.2.17-alpha.
6762 - Check more thoroughly to prevent a rogue authority from
6763 double-voting on any consensus directory parameter. Previously,
6764 authorities would crash in this case if the total number of
6765 votes for any parameter exceeded the number of active voters,
6766 but would let it pass otherwise. Partial fix for bug 5786; bugfix
6770 - Rate-limit log messages when asked to connect anonymously to
6771 a private address. When these hit, they tended to hit fast and
6772 often. Also, don't bother trying to connect to addresses that we
6773 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6774 reply makes us think we have been lied to, even when the address the
6775 client tried to connect to was "localhost." Resolves ticket 2822.
6776 - Allow packagers to insert an extra string in server descriptor
6777 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
6778 Resolves the rest of ticket 2988.
6779 - Raise the threshold of server descriptors needed (75%) and exit
6780 server descriptors needed (50%) before we will declare ourselves
6781 bootstrapped. This will make clients start building circuits a
6782 little later, but makes the initially constructed circuits less
6783 skewed and less in conflict with further directory fetches. Fixes
6785 - Close any connection that sends unrecognized junk before the
6786 handshake. Solves an issue noted in bug 4369.
6787 - Improve log messages about managed transports. Resolves ticket 5070.
6788 - Tag a bridge's descriptor as "never to be sent unencrypted".
6789 This shouldn't matter, since bridges don't open non-anonymous
6790 connections to the bridge authority and don't allow unencrypted
6791 directory connections from clients, but we might as well make
6792 sure. Closes bug 5139.
6793 - Expose our view of whether we have gone dormant to the controller,
6794 via a new "GETINFO dormant" value. Torbutton and other controllers
6795 can use this to avoid doing periodic requests through Tor while
6796 it's dormant (bug 4718). Fixes bug 5954.
6797 - Tell GCC and Clang to check for any errors in format strings passed
6798 to the tor_v*(print|scan)f functions.
6799 - Update to the May 1 2012 Maxmind GeoLite Country database.
6801 o Minor bugfixes (already included in 0.2.2.36):
6802 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6803 Fixes bug 5346; bugfix on 0.0.8pre3.
6804 - Correct parsing of certain date types in parse_http_time().
6805 Without this patch, If-Modified-Since would behave
6806 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6807 Esteban Manchado Velázques.
6808 - Make our number-parsing functions always treat too-large values
6809 as an error, even when those values exceed the width of the
6810 underlying type. Previously, if the caller provided these
6811 functions with minima or maxima set to the extreme values of the
6812 underlying integer type, these functions would return those
6813 values on overflow rather than treating overflow as an error.
6814 Fixes part of bug 5786; bugfix on 0.0.9.
6815 - If we hit the error case where routerlist_insert() replaces an
6816 existing (old) server descriptor, make sure to remove that
6817 server descriptor from the old_routers list. Fix related to bug
6818 1776. Bugfix on 0.2.2.18-alpha.
6819 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6820 circuits. Fixes issue 5259.
6822 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
6823 - Prevent a null-pointer dereference when receiving a data cell
6824 for a nonexistent stream when the circuit in question has an
6825 empty deliver window. We don't believe this is triggerable,
6826 since we don't currently allow deliver windows to become empty,
6827 but the logic is tricky enough that it's better to make the code
6828 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6829 - Fix a memory leak when trying to launch a DNS request when the
6830 network is disabled or the nameservers are unconfigurable. Fixes
6831 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
6832 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
6833 - Don't hold a Windows file handle open for every file mapping;
6834 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6836 - Avoid O(n^2) performance characteristics when parsing a large
6837 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6838 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6839 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6841 - Make our replacement implementation of strtok_r() compatible with
6842 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6843 bugfix on 0.2.2.1-alpha.
6844 - Fix a NULL-pointer dereference on a badly formed
6845 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
6846 bugfix on 0.2.2.9-alpha.
6847 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6848 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6849 - Defensively refactor rend_mid_rendezvous() so that protocol
6850 violations and length checks happen in the beginning. Fixes
6852 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6853 that IPv6 stuff will compile on MSVC, and compilation issues
6854 will be easier to track down. Fixes bug 5861.
6856 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
6857 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6858 resource exhaustion, so that clients can adjust their load to
6859 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6860 started using END_STREAM_REASON_RESOURCELIMIT.
6861 - Don't check for whether the address we're using for outbound
6862 connections has changed until after the outbound connection has
6863 completed. On Windows, getsockname() doesn't succeed until the
6864 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6865 - If the configuration tries to set MyFamily on a bridge, refuse to
6866 do so, and warn about the security implications. Fixes bug 4657;
6867 bugfix on 0.2.0.3-alpha.
6868 - If the client fails to set a reasonable set of ciphersuites
6869 during its v2 handshake renegotiation, allow the renegotiation to
6870 continue nevertheless (i.e. send all the required certificates).
6871 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6872 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6873 option is set to 0 (which Vidalia version 0.2.16 now does when
6874 a SAVECONF attempt fails), perform other actions that SIGHUP
6875 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6877 - If we fail to write a microdescriptor to the disk cache, do not
6878 continue replacing the old microdescriptor file. Fixes bug 2954;
6879 bugfix on 0.2.2.6-alpha.
6880 - Exit nodes don't need to fetch certificates for authorities that
6881 they don't recognize; only directory authorities, bridges,
6882 and caches need to do that. Fixes part of bug 2297; bugfix on
6884 - Correctly handle checking the permissions on the parent
6885 directory of a control socket in the root directory. Bug found
6886 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6888 - When told to add a bridge with the same digest as a preexisting
6889 bridge but a different addr:port, change the addr:port as
6890 requested. Previously we would not notice the change. Fixes half
6891 of bug 5603; fix on 0.2.2.26-beta.
6892 - End AUTHCHALLENGE error messages (in the control protocol) with
6893 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
6895 o Minor bugfixes (on 0.2.3.x):
6896 - Turn an assertion (that the number of handshakes received as a
6897 server is not < 1) into a warning. Fixes bug 4873; bugfix on
6899 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
6900 we had reversed them when the answer was cached.) Fixes bug
6901 5723; bugfix on 0.2.3.1-alpha.
6902 - Work correctly on Linux systems with accept4 support advertised in
6903 their headers, but without accept4 support in the kernel. Fix
6904 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
6905 - When told to add a bridge with the same addr:port as a preexisting
6906 bridge but a different transport, change the transport as
6907 requested. Previously we would not notice the change. Fixes half
6908 of bug 5603; fix on 0.2.3.2-alpha.
6909 - Avoid a "double-reply" warning when replying to a SOCKS request
6910 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
6911 bugfix on 0.2.3.4-alpha.
6912 - Fix a bug where a bridge authority crashes if it has seen no
6913 directory requests when it's time to write statistics to disk.
6914 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
6916 - Don't try to open non-control listeners when DisableNetwork is set.
6917 Previously, we'd open all listeners, then immediately close them.
6918 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
6919 - Don't abort the managed proxy protocol if the managed proxy
6920 sends us an unrecognized line; ignore it instead. Fixes bug
6921 5910; bugfix on 0.2.3.9-alpha.
6922 - Fix a compile warning in crypto.c when compiling with clang 3.1.
6923 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
6924 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
6925 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
6926 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
6927 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
6928 - Resolve numerous small warnings and build issues with MSVC. Resolves
6931 o Documentation fixes:
6932 - Improve the manual's documentation for the NT Service command-line
6933 options. Addresses ticket 3964.
6934 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6935 - Document the changes to the ORPort and DirPort options, and the
6936 fact that {OR/Dir}ListenAddress is now unnecessary (and
6937 therefore deprecated). Resolves ticket 5597.
6940 - Remove the torrc.bridge file: we don't use it for anything, and
6941 it had become badly desynchronized from torrc.sample. Resolves
6945 Changes in version 0.2.2.36 - 2012-05-24
6946 Tor 0.2.2.36 updates the addresses for two of the eight directory
6947 authorities, fixes some potential anonymity and security issues,
6948 and fixes several crash bugs.
6950 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6951 known flaws, and nobody should be using them. You should upgrade. If
6952 you're using a Linux or BSD and its packages are obsolete, stop using
6953 those packages and upgrade anyway.
6955 o Directory authority changes:
6956 - Change IP address for maatuska (v3 directory authority).
6957 - Change IP address for ides (v3 directory authority), and rename
6961 - When building or running with any version of OpenSSL earlier
6962 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6963 versions have a bug (CVE-2011-4576) in which their block cipher
6964 padding includes uninitialized data, potentially leaking sensitive
6965 information to any peer with whom they make a SSLv3 connection. Tor
6966 does not use SSL v3 by default, but a hostile client or server
6967 could force an SSLv3 connection in order to gain information that
6968 they shouldn't have been able to get. The best solution here is to
6969 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6970 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6971 to make sure that the bug can't happen.
6972 - Never use a bridge or a controller-supplied node as an exit, even
6973 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6974 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6975 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6976 - Only build circuits if we have a sufficient threshold of the total
6977 descriptors that are marked in the consensus with the "Exit"
6978 flag. This mitigates an attack proposed by wanoskarnet, in which
6979 all of a client's bridges collude to restrict the exit nodes that
6980 the client knows about. Fixes bug 5343.
6981 - Provide controllers with a safer way to implement the cookie
6982 authentication mechanism. With the old method, if another locally
6983 running program could convince a controller that it was the Tor
6984 process, then that program could trick the controller into telling
6985 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6986 authentication method uses a challenge-response approach to prevent
6987 this attack. Fixes bug 5185; implements proposal 193.
6990 - Avoid logging uninitialized data when unable to decode a hidden
6991 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6992 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6993 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6995 - Fix builds when the path to sed, openssl, or sha1sum contains
6996 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6998 - Correct our replacements for the timeradd() and timersub() functions
6999 on platforms that lack them (for example, Windows). The timersub()
7000 function is used when expiring circuits, while timeradd() is
7001 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7002 bugfix on 0.2.2.24-alpha.
7003 - Fix the SOCKET_OK test that we use to tell when socket
7004 creation fails so that it works on Win64. Fixes part of bug 4533;
7005 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7008 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7009 Fixes bug 5346; bugfix on 0.0.8pre3.
7010 - Make our number-parsing functions always treat too-large values
7011 as an error, even when those values exceed the width of the
7012 underlying type. Previously, if the caller provided these
7013 functions with minima or maxima set to the extreme values of the
7014 underlying integer type, these functions would return those
7015 values on overflow rather than treating overflow as an error.
7016 Fixes part of bug 5786; bugfix on 0.0.9.
7017 - Older Linux kernels erroneously respond to strange nmap behavior
7018 by having accept() return successfully with a zero-length
7019 socket. When this happens, just close the connection. Previously,
7020 we would try harder to learn the remote address: but there was
7021 no such remote address to learn, and our method for trying to
7022 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7023 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7024 - Correct parsing of certain date types in parse_http_time().
7025 Without this patch, If-Modified-Since would behave
7026 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7027 Esteban Manchado Velázques.
7028 - Change the BridgePassword feature (part of the "bridge community"
7029 design, which is not yet implemented) to use a time-independent
7030 comparison. The old behavior might have allowed an adversary
7031 to use timing to guess the BridgePassword value. Fixes bug 5543;
7032 bugfix on 0.2.0.14-alpha.
7033 - Detect and reject certain misformed escape sequences in
7034 configuration values. Previously, these values would cause us
7035 to crash if received in a torrc file or over an authenticated
7036 control port. Bug found by Esteban Manchado Velázquez, and
7037 independently by Robert Connolly from Matta Consulting who further
7038 noted that it allows a post-authentication heap overflow. Patch
7039 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7040 bugfix on 0.2.0.16-alpha.
7041 - Fix a compile warning when using the --enable-openbsd-malloc
7042 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7043 - During configure, detect when we're building with clang version
7044 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7045 CFLAGS. clang doesn't support them yet.
7046 - When sending an HTTP/1.1 proxy request, include a Host header.
7047 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7048 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7049 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7050 - If we hit the error case where routerlist_insert() replaces an
7051 existing (old) server descriptor, make sure to remove that
7052 server descriptor from the old_routers list. Fix related to bug
7053 1776. Bugfix on 0.2.2.18-alpha.
7055 o Minor bugfixes (documentation and log messages):
7056 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7057 Fixes bug 4856; bugfix on Tor 0.0.6.
7058 - Update "ClientOnly" man page entry to explain that there isn't
7059 really any point to messing with it. Resolves ticket 5005.
7060 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7061 directory authority option (introduced in Tor 0.2.2.34).
7062 - Downgrade the "We're missing a certificate" message from notice
7063 to info: people kept mistaking it for a real problem, whereas it
7064 is seldom the problem even when we are failing to bootstrap. Fixes
7065 bug 5067; bugfix on 0.2.0.10-alpha.
7066 - Correctly spell "connect" in a log message on failure to create a
7067 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7068 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7069 circuits. Fixes issue 5259.
7072 - Directory authorities now reject versions of Tor older than
7073 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7074 inclusive. These versions accounted for only a small fraction of
7075 the Tor network, and have numerous known security issues. Resolves
7077 - Update to the May 1 2012 Maxmind GeoLite Country database.
7080 - When sending or relaying a RELAY_EARLY cell, we used to convert
7081 it to a RELAY cell if the connection was using the v1 link
7082 protocol. This was a workaround for older versions of Tor, which
7083 didn't handle RELAY_EARLY cells properly. Now that all supported
7084 versions can handle RELAY_EARLY cells, and now that we're enforcing
7085 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7086 remove this workaround. Addresses bug 4786.
7089 Changes in version 0.2.3.15-alpha - 2012-04-30
7090 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
7091 the development branch build on Windows again.
7093 o Minor bugfixes (on 0.2.2.x and earlier):
7094 - Make sure that there are no unhandled pending TLS errors before
7095 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7096 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7097 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7098 - Fix an assert that directory authorities could trigger on sighup
7099 during some configuration state transitions. We now don't treat
7100 it as a fatal error when the new descriptor we just generated in
7101 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
7102 - After we pick a directory mirror, we would refuse to use it if
7103 it's in our ExcludeExitNodes list, resulting in mysterious failures
7104 to bootstrap for people who just wanted to avoid exiting from
7105 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7106 - When building with --enable-static-tor on OpenBSD, do not
7107 erroneously attempt to link -lrt. Fixes bug 5103.
7109 o Minor bugfixes (on 0.2.3.x):
7110 - When Tor is built with kernel headers from a recent (last few
7111 years) Linux kernel, do not fail to run on older (pre-2.6.28
7112 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
7113 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
7115 - Fix compilation with miniupnpc version 1.6; patch from
7116 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
7117 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
7118 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
7119 - Fix compilation on platforms without unistd.h, or where environ
7120 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
7123 - Directory authorities are now a little more lenient at accepting
7124 older router descriptors, or newer router descriptors that don't
7125 make big changes. This should help ameliorate past and future
7126 issues where routers think they have uploaded valid descriptors,
7127 but the authorities don't think so. Fix for ticket 2479.
7128 - Make the code that clients use to detect an address change be
7129 IPv6-aware, so that it won't fill clients' logs with error
7130 messages when trying to get the IPv4 address of an IPv6
7131 connection. Implements ticket 5537.
7134 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
7135 authorities needed to use it for a while to keep the network working
7136 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
7137 that was six months ago. As of now, it should no longer be needed
7141 Changes in version 0.2.3.14-alpha - 2012-04-23
7142 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
7143 candidate. It also dramatically speeds up AES: fast relays should
7144 consider switching to the newer OpenSSL library.
7146 o Directory authority changes:
7147 - Change IP address for ides (v3 directory authority), and rename
7151 - Avoid logging uninitialized data when unable to decode a hidden
7152 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7153 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7154 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7156 - If authorities are unable to get a v2 consensus document from other
7157 directory authorities, they no longer fall back to fetching
7158 them from regular directory caches. Fixes bug 5635; bugfix on
7159 0.2.2.26-beta, where routers stopped downloading v2 consensus
7161 - When we start a Tor client with a normal consensus already cached,
7162 be willing to download a microdescriptor consensus. Fixes bug 4011;
7163 fix on 0.2.3.1-alpha.
7165 o Major features (performance):
7166 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
7167 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
7168 vectorized AES implementations as appropriate. These can be much,
7169 much faster than other AES implementations.
7171 o Minor bugfixes (0.2.2.x and earlier):
7172 - Don't launch more than 10 service-side introduction-point circuits
7173 for a hidden service in five minutes. Previously, we would consider
7174 launching more introduction-point circuits if at least one second
7175 had passed without any introduction-point circuits failing. Fixes
7176 bug 4607; bugfix on 0.0.7pre1.
7177 - Change the BridgePassword feature (part of the "bridge community"
7178 design, which is not yet implemented) to use a time-independent
7179 comparison. The old behavior might have allowed an adversary
7180 to use timing to guess the BridgePassword value. Fixes bug 5543;
7181 bugfix on 0.2.0.14-alpha.
7182 - Enforce correct return behavior of tor_vsscanf() when the '%%'
7183 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
7184 - When sending an HTTP/1.1 proxy request, include a Host header.
7185 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7186 - Don't log that we have "decided to publish new relay descriptor"
7187 unless we are actually publishing a descriptor. Fixes bug 3942;
7188 bugfix on 0.2.2.28-beta.
7190 o Minor bugfixes (0.2.3.x):
7191 - Fix a bug where a bridge authority crashes (on a failed assert)
7192 if it has seen no directory requests when it's time to write
7193 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
7194 - Fix bug stomping on ORPort option NoListen and ignoring option
7195 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
7196 - In the testsuite, provide a large enough buffer in the tor_sscanf
7197 unit test. Otherwise we'd overrun that buffer and crash during
7198 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
7200 - Make sure we create the keys directory if it doesn't exist and we're
7201 about to store the dynamic Diffie-Hellman parameters. Fixes bug
7202 5572; bugfix on 0.2.3.13-alpha.
7203 - Fix a small memory leak when trying to decode incorrect base16
7204 authenticator during SAFECOOKIE authentication. Found by
7205 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
7208 - Add more information to a log statement that might help track down
7209 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
7210 non-IP address" messages (or any Bug messages, for that matter!),
7211 please let us know about it.
7212 - Relays now understand an IPv6 address when they get one from a
7213 directory server. Resolves ticket 4875.
7214 - Resolve IPv6 addresses in bridge and entry statistics to country
7215 code "??" which means we at least count them. Resolves ticket 5053;
7216 improves on 0.2.3.9-alpha.
7217 - Update to the April 3 2012 Maxmind GeoLite Country database.
7218 - Begin a doc/state-contents.txt file to explain the contents of
7219 the Tor state file. Fixes bug 2987.
7221 o Default torrc changes:
7222 - Stop listing "socksport 9050" in torrc.sample. We open a socks
7223 port on 9050 by default anyway, so this should not change anything
7225 - Stop mentioning the deprecated *ListenAddress options in
7226 torrc.sample. Fixes bug 5438.
7227 - Document unit of bandwidth related options in sample torrc.
7231 - The "torify" script no longer supports the "tsocks" socksifier
7232 tool, since tsocks doesn't support DNS and UDP right for Tor.
7233 Everyone should be using torsocks instead. Fixes bugs 3530 and
7234 5180. Based on a patch by "ugh".
7237 - Change the symmetric cipher interface so that creating and
7238 initializing a stream cipher are no longer separate functions.
7239 - Remove all internal support for unpadded RSA. We never used it, and
7240 it would be a bad idea to start.
7243 Changes in version 0.2.3.13-alpha - 2012-03-26
7244 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
7245 in managed pluggable transports, as well as providing other cleanups
7246 that get us closer to a release candidate.
7248 o Directory authority changes:
7249 - Change IP address for maatuska (v3 directory authority).
7252 - Provide controllers with a safer way to implement the cookie
7253 authentication mechanism. With the old method, if another locally
7254 running program could convince a controller that it was the Tor
7255 process, then that program could trick the controller into telling
7256 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7257 authentication method uses a challenge-response approach to prevent
7258 this attack. Fixes bug 5185, implements proposal 193.
7259 - Never use a bridge or a controller-supplied node as an exit, even
7260 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7261 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7262 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7263 - Only build circuits if we have a sufficient threshold of the total
7264 descriptors that are marked in the consensus with the "Exit"
7265 flag. This mitigates an attack proposed by wanoskarnet, in which
7266 all of a client's bridges collude to restrict the exit nodes that
7267 the client knows about. Fixes bug 5343.
7269 o Major bugfixes (on Tor 0.2.3.x):
7270 - Avoid an assert when managed proxies like obfsproxy are configured,
7271 and we receive HUP signals or setconf attempts too rapidly. This
7272 situation happens most commonly when Vidalia tries to attach to
7273 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
7274 bugfix on 0.2.3.6-alpha.
7275 - Fix a relay-side pluggable transports bug where managed proxies were
7276 unreachable from the Internet, because Tor asked them to bind on
7277 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
7278 - Stop discarding command-line arguments when TestingTorNetwork
7279 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
7280 0.2.3.9-alpha, where task 4552 added support for two layers of
7282 - Resume allowing the unit tests to run in gdb. This was accidentally
7283 made impossible when the DisableDebuggerAttachment option was
7284 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
7285 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
7286 0.2.3.11-alpha. Reported by Anthony G. Basile.
7288 o Minor bugfixes (on 0.2.2.x and earlier):
7289 - Ensure we don't cannibalize circuits that are longer than three hops
7290 already, so we don't end up making circuits with 5 or more
7291 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
7292 0.1.0.1-rc which introduced cannibalization.
7293 - Detect and reject certain misformed escape sequences in
7294 configuration values. Previously, these values would cause us
7295 to crash if received in a torrc file or over an authenticated
7296 control port. Bug found by Esteban Manchado Velázquez, and
7297 independently by Robert Connolly from Matta Consulting who further
7298 noted that it allows a post-authentication heap overflow. Patch
7299 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7300 bugfix on 0.2.0.16-alpha.
7301 - Fix a compile warning when using the --enable-openbsd-malloc
7302 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7303 - Directory caches no longer refuse to clean out descriptors because
7304 of missing v2 networkstatus documents, unless they're configured
7305 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
7306 0.2.2.26-beta. Patch by Daniel Bryg.
7307 - Update to the latest version of the tinytest unit testing framework.
7308 This includes a couple of bugfixes that can be relevant for
7309 running forked unit tests on Windows, and removes all reserved
7312 o Minor bugfixes (on 0.2.3.x):
7313 - On a failed pipe() call, don't leak file descriptors. Fixes bug
7314 4296; bugfix on 0.2.3.1-alpha.
7315 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
7316 until after we have received a CERTS cell. Fixes bug 4361; bugfix
7317 on 0.2.3.6-alpha. Patch by "frosty".
7318 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
7319 option, so that the IP stack doesn't decide to use it for IPv4
7320 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
7321 - Ensure that variables set in Tor's environment cannot override
7322 environment variables that Tor passes to a managed
7323 pluggable-transport proxy. Previously, Tor would pass every
7324 variable in its environment to managed proxies along with the new
7325 ones, in such a way that on many operating systems, the inherited
7326 environment variables would override those which Tor tried to
7327 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
7328 bugfix on 0.2.3.9-alpha for Windows.
7331 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7332 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
7333 - Update to the March 6 2012 Maxmind GeoLite Country database.
7336 Changes in version 0.2.3.12-alpha - 2012-02-13
7337 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
7338 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
7339 when Tor is configured to use a pluggable transport like obfsproxy.
7342 - Fix builds when the path to sed, openssl, or sha1sum contains
7343 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7345 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
7346 connections. This change should allow busy exit relays to stop
7347 running out of available sockets as quickly. Fixes bug 4950;
7348 bugfix on 0.2.2.26-beta.
7349 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
7350 would ask the bridge for microdescriptors, which are only supported
7351 in 0.2.3.x, and then fail to bootstrap when it didn't get the
7352 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
7353 - Properly set up obfsproxy's environment when in managed mode. The
7354 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
7355 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
7356 5076 and 5082; bugfix on 0.2.3.6-alpha.
7359 - Use the dead_strip option when building Tor on OS X. This reduces
7360 binary size by almost 19% when linking openssl and libevent
7361 statically, which we do for Tor Browser Bundle.
7362 - Fix broken URLs in the sample torrc file, and tell readers about
7363 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7364 PublishServerDescriptor options. Addresses bug 4652.
7365 - Update to the February 7 2012 Maxmind GeoLite Country database.
7368 - Downgrade the "We're missing a certificate" message from notice
7369 to info: people kept mistaking it for a real problem, whereas it
7370 is seldom the problem even when we are failing to bootstrap. Fixes
7371 bug 5067; bugfix on 0.2.0.10-alpha.
7372 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
7373 managed pluggable transport server proxy's environment.
7374 Previously, we would put it there, even though Tor doesn't
7375 implement an 'extended server port' yet, and even though Tor
7376 almost certainly isn't listening at that address. For now, we set
7377 it to an empty string to avoid crashing older obfsproxies. Bugfix
7379 - Log the heartbeat message every HeartbeatPeriod seconds, not every
7380 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
7381 0.2.3.1-alpha. Bug reported by Scott Bennett.
7382 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
7383 bugfix on 0.2.3.11-alpha.
7384 - Update "ClientOnly" man page entry to explain that there isn't
7385 really any point to messing with it. Resolves ticket 5005.
7386 - Use the correct CVE number for CVE-2011-4576 in our comments and
7387 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
7390 o Code simplifications and refactoring:
7391 - Use the _WIN32 macro throughout our code to detect Windows.
7392 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7396 Changes in version 0.2.3.11-alpha - 2012-01-22
7397 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7398 the last step of the plan to limit maximum circuit length, includes
7399 a wide variety of hidden service performance and correctness fixes,
7400 works around an OpenSSL security flaw if your distro is too stubborn
7401 to upgrade, and fixes a bunch of smaller issues.
7404 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7405 part of "Proposal 110: Avoiding infinite length circuits" by
7406 refusing all circuit-extend requests that do not use a relay_early
7407 cell. This change helps Tor resist a class of denial-of-service
7408 attacks by limiting the maximum circuit length.
7409 - Adjust the number of introduction points that a hidden service
7410 will try to maintain based on how long its introduction points
7411 remain in use and how many introductions they handle. Fixes
7413 - Try to use system facilities for enumerating local interface
7414 addresses, before falling back to our old approach (which was
7415 binding a UDP socket, and calling getsockname() on it). That
7416 approach was scaring OS X users whose draconian firewall
7417 software warned about binding to UDP sockets, regardless of
7418 whether packets were sent. Now we try to use getifaddrs(),
7419 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7420 system supports. Resolves ticket 1827.
7422 o Major security workaround:
7423 - When building or running with any version of OpenSSL earlier
7424 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7425 versions have a bug (CVE-2011-4576) in which their block cipher
7426 padding includes uninitialized data, potentially leaking sensitive
7427 information to any peer with whom they make a SSLv3 connection. Tor
7428 does not use SSL v3 by default, but a hostile client or server
7429 could force an SSLv3 connection in order to gain information that
7430 they shouldn't have been able to get. The best solution here is to
7431 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7432 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7433 to make sure that the bug can't happen.
7436 - Fix the SOCKET_OK test that we use to tell when socket
7437 creation fails so that it works on Win64. Fixes part of bug 4533;
7438 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7439 - Correct our replacements for the timeradd() and timersub() functions
7440 on platforms that lack them (for example, Windows). The timersub()
7441 function is used when expiring circuits, while timeradd() is
7442 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7443 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
7444 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
7445 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
7446 bug at runtime, not compile time, because some distributions hack
7447 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
7448 on 0.2.3.9-alpha. Found by Pascal.
7450 o Minor features (controller):
7451 - Use absolute path names when reporting the torrc filename in the
7452 control protocol, so a controller can more easily find the torrc
7453 file. Resolves bug 1101.
7454 - Extend the control protocol to report flags that control a circuit's
7455 path selection in CIRC events and in replies to 'GETINFO
7456 circuit-status'. Implements part of ticket 2411.
7457 - Extend the control protocol to report the hidden service address
7458 and current state of a hidden-service-related circuit in CIRC
7459 events and in replies to 'GETINFO circuit-status'. Implements part
7461 - When reporting the path to the cookie file to the controller,
7462 give an absolute path. Resolves ticket 4881.
7463 - Allow controllers to request an event notification whenever a
7464 circuit is cannibalized or its purpose is changed. Implements
7465 part of ticket 3457.
7466 - Include the creation time of a circuit in CIRC and CIRC2
7467 control-port events and the list produced by the 'GETINFO
7468 circuit-status' control-port command.
7470 o Minor features (directory authorities):
7471 - Directory authorities now reject versions of Tor older than
7472 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7473 inclusive. These versions accounted for only a small fraction of
7474 the Tor network, and have numerous known security issues. Resolves
7476 - Authority operators can now vote for all relays in a given
7477 set of countries to be BadDir/BadExit/Invalid/Rejected.
7478 - Provide two consensus parameters (FastFlagMinThreshold and
7479 FastFlagMaxThreshold) to control the range of allowable bandwidths
7480 for the Fast directory flag. These allow authorities to run
7481 experiments on appropriate requirements for being a "Fast" node.
7482 The AuthDirFastGuarantee config value still applies. Implements
7484 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7485 directory authority option (introduced in Tor 0.2.2.34).
7487 o Minor features (other):
7488 - Don't disable the DirPort when we cannot exceed our AccountingMax
7489 limit during this interval because the effective bandwidthrate is
7490 low enough. This is useful in a situation where AccountMax is only
7491 used as an additional safeguard or to provide statistics.
7492 - Prepend an informative header to generated dynamic_dh_params files.
7493 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
7494 EntryNodes will have no effect. Resolves issue 2571.
7495 - Log more useful messages when we fail to disable debugger
7497 - Log which authority we're missing votes from when we go to fetch
7498 them from the other auths.
7499 - Log (at debug level) whenever a circuit's purpose is changed.
7500 - Add missing documentation for the MaxClientCircuitsPending,
7501 UseMicrodescriptors, UserspaceIOCPBuffers, and
7502 _UseFilteringSSLBufferevents options, all introduced during
7504 - Update to the January 3 2012 Maxmind GeoLite Country database.
7506 o Minor bugfixes (hidden services):
7507 - Don't close hidden service client circuits which have almost
7508 finished connecting to their destination when they reach
7509 the normal circuit-build timeout. Previously, we would close
7510 introduction circuits which are waiting for an acknowledgement
7511 from the introduction point, and rendezvous circuits which have
7512 been specified in an INTRODUCE1 cell sent to a hidden service,
7513 after the normal CBT. Now, we mark them as 'timed out', and launch
7514 another rendezvous attempt in parallel. This behavior change can
7515 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7516 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7517 - Don't close hidden-service-side rendezvous circuits when they
7518 reach the normal circuit-build timeout. This behavior change can
7519 be disabled using the new
7520 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7521 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7522 - Make sure we never mark the wrong rendezvous circuit as having
7523 had its introduction cell acknowleged by the introduction-point
7524 relay. Previously, when we received an INTRODUCE_ACK cell on a
7525 client-side hidden-service introduction circuit, we might have
7526 marked a rendezvous circuit other than the one we specified in
7527 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
7528 a warning message and interfered with the hidden service
7529 connection-establishment process. Fixes bug 4759; bugfix on
7530 0.2.3.3-alpha, when we added the stream-isolation feature which
7531 might cause Tor to open multiple rendezvous circuits for the same
7533 - Don't trigger an assertion failure when we mark a new client-side
7534 hidden-service introduction circuit for close during the process
7535 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
7538 o Minor bugfixes (log messages):
7539 - Correctly spell "connect" in a log message on failure to create a
7540 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
7542 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7543 Fixes bug 4856; bugfix on Tor 0.0.6.
7544 - Fix the log message describing how we work around discovering
7545 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7546 4837; bugfix on 0.2.2.9-alpha.
7547 - When logging about a disallowed .exit name, do not also call it
7548 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7550 o Minor bugfixes (build fixes):
7551 - During configure, detect when we're building with clang version
7552 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7553 CFLAGS. clang doesn't support them yet.
7554 - During configure, search for library containing cos function as
7555 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7556 against libm was hard-coded before. Fixes the first part of bug
7557 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7559 - Detect attempts to build Tor on (as yet hypothetical) versions
7560 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7561 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7562 - Preprocessor directives should not be put inside the arguments
7563 of a macro. This would break compilation with GCC releases prior
7564 to version 3.3. We would never recommend such an old GCC version,
7565 but it is apparently required for binary compatibility on some
7566 platforms (namely, certain builds of Haiku). Fixes the other part
7567 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
7570 o Minor bugfixes (other):
7571 - Older Linux kernels erroneously respond to strange nmap behavior
7572 by having accept() return successfully with a zero-length
7573 socket. When this happens, just close the connection. Previously,
7574 we would try harder to learn the remote address: but there was
7575 no such remote address to learn, and our method for trying to
7576 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7577 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7578 - Fix null-pointer access that could occur if TLS allocation failed.
7579 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
7580 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
7581 accidentally been reverted.
7582 - Fix our implementation of crypto_random_hostname() so it can't
7583 overflow on ridiculously large inputs. (No Tor version has ever
7584 provided this kind of bad inputs, but let's be correct in depth.)
7585 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7586 - Find more places in the code that should have been testing for
7587 invalid sockets using the SOCKET_OK macro. Required for a fix
7588 for bug 4533. Bugfix on 0.2.2.28-beta.
7589 - Fix an assertion failure when, while running with bufferevents, a
7590 connection finishes connecting after it is marked for close, but
7591 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
7592 - test_util_spawn_background_ok() hardcoded the expected value
7593 for ENOENT to 2. This isn't portable as error numbers are
7594 platform specific, and particularly the hurd has ENOENT at
7595 0x40000002. Construct expected string at runtime, using the correct
7596 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
7597 - Reject attempts to disable DisableDebuggerAttachment while Tor is
7598 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
7599 - Use an appropriate-width type for sockets in tor-fw-helper on
7600 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
7603 - When sending or relaying a RELAY_EARLY cell, we used to convert
7604 it to a RELAY cell if the connection was using the v1 link
7605 protocol. This was a workaround for older versions of Tor, which
7606 didn't handle RELAY_EARLY cells properly. Now that all supported
7607 versions can handle RELAY_EARLY cells, and now that we're enforcing
7608 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7609 remove this workaround. Addresses bug 4786.
7611 o Code simplifications and refactoring:
7612 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7613 own homebrewed ssl_state_to_string() replacement. Patch from
7614 Emile Snyder. Fixes bug 4653.
7615 - Use macros to indicate OpenSSL versions, so we don't need to worry
7616 about accidental hexadecimal bit shifts.
7617 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7619 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7620 - Use the smartlist_add_asprintf() alias more consistently.
7621 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7622 invalid value, rather than just -1.
7623 - Rename a handful of old identifiers, mostly related to crypto
7624 structures and crypto functions. By convention, our "create an
7625 object" functions are called "type_new()", our "free an object"
7626 functions are called "type_free()", and our types indicate that
7627 they are types only with a final "_t". But a handful of older
7628 types and functions broke these rules, with function names like
7629 "type_create" or "subsystem_op_type", or with type names like
7633 Changes in version 0.2.3.10-alpha - 2011-12-16
7634 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
7635 Tor's buffers code. Absolutely everybody should upgrade.
7637 The bug relied on an incorrect calculation when making data continuous
7638 in one of our IO buffers, if the first chunk of the buffer was
7639 misaligned by just the wrong amount. The miscalculation would allow an
7640 attacker to overflow a piece of heap-allocated memory. To mount this
7641 attack, the attacker would need to either open a SOCKS connection to
7642 Tor's SocksPort (usually restricted to localhost), or target a Tor
7643 instance configured to make its connections through a SOCKS proxy
7644 (which Tor does not do by default).
7646 Good security practice requires that all heap-overflow bugs should be
7647 presumed to be exploitable until proven otherwise, so we are treating
7648 this as a potential code execution attack. Please upgrade immediately!
7649 This bug does not affect bufferevents-based builds of Tor. Special
7650 thanks to "Vektor" for reporting this issue to us!
7652 This release also contains a few minor bugfixes for issues discovered
7656 - Fix a heap overflow bug that could occur when trying to pull
7657 data into the first chunk of a buffer, when that chunk had
7658 already had some data drained from it. Fixes CVE-2011-2778;
7659 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7662 - If we can't attach streams to a rendezvous circuit when we
7663 finish connecting to a hidden service, clear the rendezvous
7664 circuit's stream-isolation state and try to attach streams
7665 again. Previously, we cleared rendezvous circuits' isolation
7666 state either too early (if they were freshly built) or not at all
7667 (if they had been built earlier and were cannibalized). Bugfix on
7668 0.2.3.3-alpha; fixes bug 4655.
7669 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
7670 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
7671 - Fix an assertion failure when a relay with accounting enabled
7672 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
7675 - Update to the December 6 2011 Maxmind GeoLite Country database.
7678 Changes in version 0.2.2.35 - 2011-12-16
7679 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7680 buffers code. Absolutely everybody should upgrade.
7682 The bug relied on an incorrect calculation when making data continuous
7683 in one of our IO buffers, if the first chunk of the buffer was
7684 misaligned by just the wrong amount. The miscalculation would allow an
7685 attacker to overflow a piece of heap-allocated memory. To mount this
7686 attack, the attacker would need to either open a SOCKS connection to
7687 Tor's SocksPort (usually restricted to localhost), or target a Tor
7688 instance configured to make its connections through a SOCKS proxy
7689 (which Tor does not do by default).
7691 Good security practice requires that all heap-overflow bugs should be
7692 presumed to be exploitable until proven otherwise, so we are treating
7693 this as a potential code execution attack. Please upgrade immediately!
7694 This bug does not affect bufferevents-based builds of Tor. Special
7695 thanks to "Vektor" for reporting this issue to us!
7697 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7698 crash bugs for unusual configurations, and a long-term bug that
7699 would prevent Tor from starting on Windows machines with draconian
7702 With this release, we remind everyone that 0.2.0.x has reached its
7703 formal end-of-life. Those Tor versions have many known flaws, and
7704 nobody should be using them. You should upgrade -- ideally to the
7705 0.2.2.x series. If you're using a Linux or BSD and its packages are
7706 obsolete, stop using those packages and upgrade anyway.
7708 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7709 longer receive support after some time in early 2012.
7712 - Fix a heap overflow bug that could occur when trying to pull
7713 data into the first chunk of a buffer, when that chunk had
7714 already had some data drained from it. Fixes CVE-2011-2778;
7715 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7716 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7717 that it doesn't attempt to allocate a socketpair. This could cause
7718 some problems on Windows systems with overzealous firewalls. Fix for
7719 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7721 - If we mark an OR connection for close based on a cell we process,
7722 don't process any further cells on it. We already avoid further
7723 reads on marked-for-close connections, but now we also discard the
7724 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7725 which was the first version where we might mark a connection for
7726 close based on processing a cell on it.
7727 - Correctly sanity-check that we don't underflow on a memory
7728 allocation (and then assert) for hidden service introduction
7729 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7730 bugfix on 0.2.1.5-alpha.
7731 - Fix a memory leak when we check whether a hidden service
7732 descriptor has any usable introduction points left. Fixes bug
7733 4424. Bugfix on 0.2.2.25-alpha.
7734 - Don't crash when we're running as a relay and don't have a GeoIP
7735 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7736 we've had in the 0.2.3.x branch already.
7737 - When running as a client, do not print a misleading (and plain
7738 wrong) log message that we're collecting "directory request"
7739 statistics: clients don't collect statistics. Also don't create a
7740 useless (because empty) stats file in the stats/ directory. Fixes
7741 bug 4353; bugfix on 0.2.2.34.
7744 - Detect failure to initialize Libevent. This fix provides better
7745 detection for future instances of bug 4457.
7746 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7747 function. This was eating up hideously large amounts of time on some
7748 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7749 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7750 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7752 - Don't warn about unused log_mutex in log.c when building with
7753 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7754 0.1.0.6-rc which introduced --disable-threads.
7755 - When configuring, starting, or stopping an NT service, stop
7756 immediately after the service configuration attempt has succeeded
7757 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7758 - When sending a NETINFO cell, include the original address
7759 received for the other side, not its canonical address. Found
7760 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7761 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7762 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7763 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7764 occurred when a client tried to fetch a descriptor for a bridge
7765 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7766 - Backport fixes for a pair of compilation warnings on Windows.
7767 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7768 - If we had ever tried to call tor_addr_to_str on an address of
7769 unknown type, we would have done a strdup on an uninitialized
7770 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7771 Reported by "troll_un".
7772 - Correctly detect and handle transient lookup failures from
7773 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7774 Reported by "troll_un".
7775 - Fix null-pointer access that could occur if TLS allocation failed.
7776 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7777 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7778 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7781 - Add two new config options for directory authorities:
7782 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7783 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7784 that is always sufficient to satisfy the bandwidth requirement for
7785 the Guard flag. Now it will be easier for researchers to simulate
7786 Tor networks with different values. Resolves ticket 4484.
7787 - When Tor ignores a hidden service specified in its configuration,
7788 include the hidden service's directory in the warning message.
7789 Previously, we would only tell the user that some hidden service
7790 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7791 - Update to the December 6 2011 Maxmind GeoLite Country database.
7793 o Packaging changes:
7794 - Make it easier to automate expert package builds on Windows,
7795 by removing an absolute path from makensis.exe command.
7798 Changes in version 0.2.1.32 - 2011-12-16
7799 Tor 0.2.1.32 backports important security and privacy fixes for
7800 oldstable. This release is intended only for package maintainers and
7801 others who cannot use the 0.2.2 stable series. All others should be
7802 using Tor 0.2.2.x or newer.
7804 The Tor 0.2.1.x series will reach formal end-of-life some time in
7805 early 2012; we will stop releasing patches for it then.
7807 o Major bugfixes (also included in 0.2.2.x):
7808 - Correctly sanity-check that we don't underflow on a memory
7809 allocation (and then assert) for hidden service introduction
7810 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7811 bugfix on 0.2.1.5-alpha.
7812 - Fix a heap overflow bug that could occur when trying to pull
7813 data into the first chunk of a buffer, when that chunk had
7814 already had some data drained from it. Fixes CVE-2011-2778;
7815 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7818 - Update to the December 6 2011 Maxmind GeoLite Country database.
7821 Changes in version 0.2.3.9-alpha - 2011-12-08
7822 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
7823 a "DisableNetwork" security feature that bundles can use to avoid
7824 touching the network until bridges are configured, moves forward on
7825 the pluggable transport design, fixes a flaw in the hidden service
7826 design that unnecessarily prevented clients with wrong clocks from
7827 reaching hidden services, and fixes a wide variety of other issues.
7830 - Clients can now connect to private bridges over IPv6. Bridges
7831 still need at least one IPv4 address in order to connect to
7832 other relays. Note that we don't yet handle the case where the
7833 user has two bridge lines for the same bridge (one IPv4, one
7834 IPv6). Implements parts of proposal 186.
7835 - New "DisableNetwork" config option to prevent Tor from launching any
7836 connections or accepting any connections except on a control port.
7837 Bundles and controllers can set this option before letting Tor talk
7838 to the rest of the network, for example to prevent any connections
7839 to a non-bridge address. Packages like Orbot can also use this
7840 option to instruct Tor to save power when the network is off.
7841 - Clients and bridges can now be configured to use a separate
7842 "transport" proxy. This approach makes the censorship arms race
7843 easier by allowing bridges to use protocol obfuscation plugins. It
7844 implements the "managed proxy" part of proposal 180 (ticket 3472).
7845 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7846 implementation. It makes AES_CTR about 7% faster than our old one
7847 (which was about 10% faster than the one OpenSSL used to provide).
7848 Resolves ticket 4526.
7849 - Add a "tor2web mode" for clients that want to connect to hidden
7850 services non-anonymously (and possibly more quickly). As a safety
7851 measure to try to keep users from turning this on without knowing
7852 what they are doing, tor2web mode must be explicitly enabled at
7853 compile time, and a copy of Tor compiled to run in tor2web mode
7854 cannot be used as a normal Tor client. Implements feature 2553.
7855 - Add experimental support for running on Windows with IOCP and no
7856 kernel-space socket buffers. This feature is controlled by a new
7857 "UserspaceIOCPBuffers" config option (off by default), which has
7858 no effect unless Tor has been built with support for bufferevents,
7859 is running on Windows, and has enabled IOCP. This may, in the long
7860 run, help solve or mitigate bug 98.
7861 - Use a more secure consensus parameter voting algorithm. Now at
7862 least three directory authorities or a majority of them must
7863 vote on a given parameter before it will be included in the
7864 consensus. Implements proposal 178.
7867 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7868 They used to check that the timestamp was within 30 minutes
7869 of their system clock, so they could cap the size of their
7870 replay-detection cache, but that approach unnecessarily refused
7871 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7872 the v3 intro-point protocol (the first one which sent a timestamp
7873 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7874 - Only use the EVP interface when AES acceleration is enabled,
7875 to avoid a 5-7% performance regression. Resolves issue 4525;
7876 bugfix on 0.2.3.8-alpha.
7878 o Privacy/anonymity features (bridge detection):
7879 - Make bridge SSL certificates a bit more stealthy by using random
7880 serial numbers, in the same fashion as OpenSSL when generating
7881 self-signed certificates. Implements ticket 4584.
7882 - Introduce a new config option "DynamicDHGroups", enabled by
7883 default, which provides each bridge with a unique prime DH modulus
7884 to be used during SSL handshakes. This option attempts to help
7885 against censors who might use the Apache DH modulus as a static
7886 identifier for bridges. Addresses ticket 4548.
7888 o Minor features (new/different config options):
7889 - New configuration option "DisableDebuggerAttachment" (on by default)
7890 to prevent basic debugging attachment attempts by other processes.
7891 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7892 - Allow MapAddress directives to specify matches against super-domains,
7893 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7894 Implements issue 933.
7895 - Slightly change behavior of "list" options (that is, config
7896 options that can appear more than once) when they appear both in
7897 torrc and on the command line. Previously, the command-line options
7898 would be appended to the ones from torrc. Now, the command-line
7899 options override the torrc options entirely. This new behavior
7900 allows the user to override list options (like exit policies and
7901 ports to listen on) from the command line, rather than simply
7902 appending to the list.
7903 - You can get the old (appending) command-line behavior for "list"
7904 options by prefixing the option name with a "+".
7905 - You can remove all the values for a "list" option from the command
7906 line without adding any new ones by prefixing the option name
7908 - Add experimental support for a "defaults" torrc file to be parsed
7909 before the regular torrc. Torrc options override the defaults file's
7910 options in the same way that the command line overrides the torrc.
7911 The SAVECONF controller command saves only those options which
7912 differ between the current configuration and the defaults file. HUP
7913 reloads both files. (Note: This is an experimental feature; its
7914 behavior will probably be refined in future 0.2.3.x-alpha versions
7915 to better meet packagers' needs.) Implements task 4552.
7918 - Try to make the introductory warning message that Tor prints on
7919 startup more useful for actually finding help and information.
7920 Resolves ticket 2474.
7921 - Running "make version" now displays the version of Tor that
7922 we're about to build. Idea from katmagic; resolves issue 4400.
7923 - Expire old or over-used hidden service introduction points.
7924 Required by fix for bug 3460.
7925 - Move the replay-detection cache for the RSA-encrypted parts of
7926 INTRODUCE2 cells to the introduction point data structures.
7927 Previously, we would use one replay-detection cache per hidden
7928 service. Required by fix for bug 3460.
7929 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7930 public key replay-detection cache from 60 minutes to 5 minutes. This
7931 replay-detection cache is now used only to detect multiple
7932 INTRODUCE2 cells specifying the same rendezvous point, so we can
7933 avoid launching multiple simultaneous attempts to connect to it.
7935 o Minor bugfixes (on Tor 0.2.2.x and earlier):
7936 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7937 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7939 - Fix a minor formatting issue in one of tor-gencert's error messages.
7941 - Prevent a false positive from the check-spaces script, by disabling
7942 the "whitespace between function name and (" check for functions
7944 - Fix a log message suggesting that people contact a non-existent
7945 email address. Fixes bug 3448.
7946 - Fix null-pointer access that could occur if TLS allocation failed.
7947 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7948 - Report a real bootstrap problem to the controller on router
7949 identity mismatch. Previously we just said "foo", which probably
7950 made a lot of sense at the time. Fixes bug 4169; bugfix on
7952 - If we had ever tried to call tor_addr_to_str() on an address of
7953 unknown type, we would have done a strdup() on an uninitialized
7954 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7955 Reported by "troll_un".
7956 - Correctly detect and handle transient lookup failures from
7957 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7958 Reported by "troll_un".
7959 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7960 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7961 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7962 bug 4532; found by "troll_un".
7964 o Minor bugfixes (on Tor 0.2.3.x):
7965 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
7967 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
7968 circuit for use as a hidden service client's rendezvous point.
7969 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
7970 with help from wanoskarnet.
7971 - Restore behavior of overriding SocksPort, ORPort, and similar
7972 options from the command line. Bugfix on 0.2.3.3-alpha.
7975 - Properly handle the case where the build-tree is not the same
7976 as the source tree when generating src/common/common_sha1.i,
7977 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7978 bugfix on 0.2.0.1-alpha.
7980 o Code simplifications, cleanups, and refactorings:
7981 - Remove the pure attribute from all functions that used it
7982 previously. In many cases we assigned it incorrectly, because the
7983 functions might assert or call impure functions, and we don't have
7984 evidence that keeping the pure attribute is worthwhile. Implements
7985 changes suggested in ticket 4421.
7986 - Remove some dead code spotted by coverity. Fixes cid 432.
7987 Bugfix on 0.2.3.1-alpha, closes bug 4637.
7990 Changes in version 0.2.3.8-alpha - 2011-11-22
7991 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
7992 socketpair-related bug that has been bothering Windows users. It adds
7993 support to serve microdescriptors to controllers, so Vidalia's network
7994 map can resume listing relays (once Vidalia implements its side),
7995 and adds better support for hardware AES acceleration. Finally, it
7996 starts the process of adjusting the bandwidth cutoff for getting the
7997 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
7998 that tiny relays harm performance more than they help network capacity.
8001 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8002 that it doesn't attempt to allocate a socketpair. This could cause
8003 some problems on Windows systems with overzealous firewalls. Fix for
8004 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8006 - Correctly sanity-check that we don't underflow on a memory
8007 allocation (and then assert) for hidden service introduction
8008 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8009 bugfix on 0.2.1.5-alpha.
8010 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8011 flag. In the past few years the average relay speed has picked
8012 up, and while the "top 7/8 of the network get the Fast flag" and
8013 "all relays with 20KB or more of capacity get the Fast flag" rules
8014 used to have the same result, now the top 7/8 of the network has
8015 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8016 - Fix a rare assertion failure when checking whether a v0 hidden
8017 service descriptor has any usable introduction points left, and
8018 we don't have enough information to build a circuit to the first
8019 intro point named in the descriptor. The HS client code in
8020 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
8021 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
8022 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
8023 - Make bridge authorities not crash when they are asked for their own
8024 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
8025 - When running as a client, do not print a misleading (and plain
8026 wrong) log message that we're collecting "directory request"
8027 statistics: clients don't collect statistics. Also don't create a
8028 useless (because empty) stats file in the stats/ directory. Fixes
8029 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
8032 - Allow Tor controllers like Vidalia to obtain the microdescriptor
8033 for a relay by identity digest or nickname. Previously,
8034 microdescriptors were only available by their own digests, so a
8035 controller would have to ask for and parse the whole microdescriptor
8036 consensus in order to look up a single relay's microdesc. Fixes
8037 bug 3832; bugfix on 0.2.3.1-alpha.
8038 - Use OpenSSL's EVP interface for AES encryption, so that all AES
8039 operations can use hardware acceleration (if present). Resolves
8042 o Minor bugfixes (on 0.2.2.x and earlier):
8043 - Detect failure to initialize Libevent. This fix provides better
8044 detection for future instances of bug 4457.
8045 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8046 function. This was eating up hideously large amounts of time on some
8047 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8048 - Don't warn about unused log_mutex in log.c when building with
8049 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8050 0.1.0.6-rc which introduced --disable-threads.
8051 - Allow manual 'authenticate' commands to the controller interface
8052 from netcat (nc) as well as telnet. We were rejecting them because
8053 they didn't come with the expected whitespace at the end of the
8054 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8055 - Fix some (not actually triggerable) buffer size checks in usage of
8056 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8058 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8059 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8060 - When configuring, starting, or stopping an NT service, stop
8061 immediately after the service configuration attempt has succeeded
8062 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8063 - When sending a NETINFO cell, include the original address
8064 received for the other side, not its canonical address. Found
8065 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8066 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8067 can pick them up when the tests aren't disabled. Bugfix on
8068 0.2.2.4-alpha which introduced tinytest.
8069 - Fix a memory leak when we check whether a hidden service
8070 descriptor has any usable introduction points left. Fixes bug
8071 4424. Bugfix on 0.2.2.25-alpha.
8072 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8073 occurred when a client tried to fetch a descriptor for a bridge
8074 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8076 o Minor bugfixes (on 0.2.3.x):
8077 - Make util unit tests build correctly with MSVC. Bugfix on
8078 0.2.3.3-alpha. Patch by Gisle Vanem.
8079 - Successfully detect AUTH_CHALLENGE cells with no recognized
8080 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
8082 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
8083 it should still send a NETINFO cell to allow the connection to
8084 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
8086 - Log less loudly when we get an invalid authentication certificate
8087 from a source other than a directory authority: it's not unusual
8088 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
8090 - Tolerate servers with more clock skew in their authentication
8091 certificates than previously. Fixes bug 4371; bugfix on
8093 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
8094 on 0.2.3.4-alpha and 0.2.3.6-alpha.
8097 - Add two new config options for directory authorities:
8098 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8099 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8100 that is always sufficient to satisfy the bandwidth requirement for
8101 the Guard flag. Now it will be easier for researchers to simulate
8102 Tor networks with different values. Resolves ticket 4484.
8103 - When Tor ignores a hidden service specified in its configuration,
8104 include the hidden service's directory in the warning message.
8105 Previously, we would only tell the user that some hidden service
8106 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8107 - When we fail to initialize Libevent, retry with IOCP disabled so we
8108 don't need to turn on multi-threading support in Libevent, which in
8109 turn requires a working socketpair(). This is a workaround for bug
8110 4457, which affects Libevent versions from 2.0.1-alpha through
8112 - Detect when we try to build on a platform that doesn't define
8113 AF_UNSPEC to 0. We don't work there, so refuse to compile.
8114 - Update to the November 1 2011 Maxmind GeoLite Country database.
8116 o Packaging changes:
8117 - Make it easier to automate expert package builds on Windows,
8118 by removing an absolute path from makensis.exe command.
8120 o Code simplifications and refactoring:
8121 - Remove some redundant #include directives throughout the code.
8122 Patch from Andrea Gelmini.
8123 - Unconditionally use OpenSSL's AES implementation instead of our
8124 old built-in one. OpenSSL's AES has been better for a while, and
8125 relatively few servers should still be on any version of OpenSSL
8126 that doesn't have good optimized assembly AES.
8127 - Use the name "CERTS" consistently to refer to the new cell type;
8128 we were calling it CERT in some places and CERTS in others.
8131 - Numerous new unit tests for functions in util.c and address.c by
8133 - The long-disabled benchmark tests are now split into their own
8134 ./src/test/bench binary.
8135 - The benchmark tests can now use more accurate timers than
8136 gettimeofday() when such timers are available.
8139 Changes in version 0.2.3.7-alpha - 2011-10-30
8140 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
8141 the new v3 handshake. It also resolves yet another bridge address
8145 - If we mark an OR connection for close based on a cell we process,
8146 don't process any further cells on it. We already avoid further
8147 reads on marked-for-close connections, but now we also discard the
8148 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8149 which was the first version where we might mark a connection for
8150 close based on processing a cell on it.
8151 - Fix a double-free bug that would occur when we received an invalid
8152 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
8153 bugfix on 0.2.3.6-alpha.
8154 - Bridges no longer include their address in NETINFO cells on outgoing
8155 OR connections, to allow them to blend in better with clients.
8156 Removes another avenue for enumerating bridges. Reported by
8157 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
8158 cells were introduced.
8161 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
8162 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8165 Changes in version 0.2.3.6-alpha - 2011-10-26
8166 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
8167 anonymity vulnerability where an attacker can deanonymize Tor
8168 users. Everybody should upgrade.
8170 This release also features support for a new v3 connection handshake
8171 protocol, and fixes to make hidden service connections more robust.
8174 - Implement a new handshake protocol (v3) for authenticating Tors to
8175 each other over TLS. It should be more resistant to fingerprinting
8176 than previous protocols, and should require less TLS hacking for
8177 future Tor implementations. Implements proposal 176.
8178 - Allow variable-length padding cells to disguise the length of
8179 Tor's TLS records. Implements part of proposal 184.
8181 o Privacy/anonymity fixes (clients):
8182 - Clients and bridges no longer send TLS certificate chains on
8183 outgoing OR connections. Previously, each client or bridge would
8184 use the same cert chain for all outgoing OR connections until
8185 its IP address changes, which allowed any relay that the client
8186 or bridge contacted to determine which entry guards it is using.
8187 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8188 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8189 no longer considers that connection as suitable for satisfying a
8190 circuit EXTEND request. Now relays can protect clients from the
8191 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8192 - Directory authorities no longer assign the Guard flag to relays
8193 that haven't upgraded to the above "refuse EXTEND requests
8194 to client connections" fix. Now directory authorities can
8195 protect clients from the CVE-2011-2768 issue even if neither
8196 the clients nor the relays have upgraded yet. There's a new
8197 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8198 to let us transition smoothly, else tomorrow there would be no
8201 o Major bugfixes (hidden services):
8202 - Improve hidden service robustness: when an attempt to connect to
8203 a hidden service ends, be willing to refetch its hidden service
8204 descriptors from each of the HSDir relays responsible for them
8205 immediately. Previously, we would not consider refetching the
8206 service's descriptors from each HSDir for 15 minutes after the last
8207 fetch, which was inconvenient if the hidden service was not running
8208 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
8209 - When one of a hidden service's introduction points appears to be
8210 unreachable, stop trying it. Previously, we would keep trying
8211 to build circuits to the introduction point until we lost the
8212 descriptor, usually because the user gave up and restarted Tor.
8213 Partly fixes bug 3825.
8214 - Don't launch a useless circuit after failing to use one of a
8215 hidden service's introduction points. Previously, we would
8216 launch a new introduction circuit, but not set the hidden service
8217 which that circuit was intended to connect to, so it would never
8218 actually be used. A different piece of code would then create a
8219 new introduction circuit correctly. Bug reported by katmagic and
8220 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8222 o Major bugfixes (other):
8223 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8224 that they initiated. Relays could distinguish incoming bridge
8225 connections from client connections, creating another avenue for
8226 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8227 Found by "frosty_un".
8228 - Don't update the AccountingSoftLimitHitAt state file entry whenever
8229 tor gets started. This prevents a wrong average bandwidth
8230 estimate, which would cause relays to always start a new accounting
8231 interval at the earliest possible moment. Fixes bug 2003; bugfix
8232 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
8233 immensely in tracking this bug down.
8234 - Fix a crash bug when changing node restrictions while a DNS lookup
8235 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8238 o Minor bugfixes (on 0.2.2.x and earlier):
8239 - When a hidden service turns an extra service-side introduction
8240 circuit into a general-purpose circuit, free the rend_data and
8241 intro_key fields first, so we won't leak memory if the circuit
8242 is cannibalized for use as another service-side introduction
8243 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8244 - Rephrase the log message emitted if the TestSocks check is
8245 successful. Patch from Fabian Keil; fixes bug 4094.
8246 - Bridges now skip DNS self-tests, to act a little more stealthily.
8247 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8248 bridges. Patch by "warms0x".
8249 - Remove a confusing dollar sign from the example fingerprint in the
8250 man page, and also make the example fingerprint a valid one. Fixes
8251 bug 4309; bugfix on 0.2.1.3-alpha.
8252 - Fix internal bug-checking logic that was supposed to catch
8253 failures in digest generation so that it will fail more robustly
8254 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8255 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8256 - Report any failure in init_keys() calls launched because our
8257 IP address has changed. Spotted by Coverity Scan. Bugfix on
8258 0.1.1.4-alpha; fixes CID 484.
8260 o Minor bugfixes (on 0.2.3.x):
8261 - Fix a bug in configure.in that kept it from building a configure
8262 script with autoconf versions earlier than 2.61. Fixes bug 2430;
8263 bugfix on 0.2.3.1-alpha.
8264 - Don't warn users that they are exposing a client port to the
8265 Internet if they have specified an RFC1918 address. Previously,
8266 we would warn if the user had specified any non-loopback
8267 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
8268 - Fix memory leaks in the failing cases of the new SocksPort and
8269 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
8270 fixes coverity CIDs 485, 486, and 487.
8273 - When a hidden service's introduction point times out, consider
8274 trying it again during the next attempt to connect to the
8275 HS. Previously, we would not try it again unless a newly fetched
8276 descriptor contained it. Required by fixes for bugs 1297 and 3825.
8277 - The next version of Windows will be called Windows 8, and it has
8278 a major version of 6, minor version of 2. Correctly identify that
8279 version instead of calling it "Very recent version". Resolves
8280 ticket 4153; reported by funkstar.
8281 - The Bridge Authority now writes statistics on how many bridge
8282 descriptors it gave out in total, and how many unique descriptors
8283 it gave out. It also lists how often the most and least commonly
8284 fetched descriptors were given out, as well as the median and
8285 25th/75th percentile. Implements tickets 4200 and 4294.
8286 - Update to the October 4 2011 Maxmind GeoLite Country database.
8288 o Code simplifications and refactoring:
8289 - Remove some old code to remember statistics about which descriptors
8290 we've served as a directory mirror. The feature wasn't used and
8291 is outdated now that microdescriptors are around.
8292 - Rename Tor functions that turn strings into addresses, so that
8293 "parse" indicates that no hostname resolution occurs, and
8294 "lookup" indicates that hostname resolution may occur. This
8295 should help prevent mistakes in the future. Fixes bug 3512.
8298 Changes in version 0.2.2.34 - 2011-10-26
8299 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
8300 can deanonymize Tor users. Everybody should upgrade.
8302 The attack relies on four components: 1) Clients reuse their TLS cert
8303 when talking to different relays, so relays can recognize a user by
8304 the identity key in her cert. 2) An attacker who knows the client's
8305 identity key can probe each guard relay to see if that identity key
8306 is connected to that guard relay right now. 3) A variety of active
8307 attacks in the literature (starting from "Low-Cost Traffic Analysis
8308 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
8309 discover the guard relays that a Tor user visiting the website is using.
8310 4) Clients typically pick three guards at random, so the set of guards
8311 for a given user could well be a unique fingerprint for her. This
8312 release fixes components #1 and #2, which is enough to block the attack;
8313 the other two remain as open research problems. Special thanks to
8314 "frosty_un" for reporting the issue to us!
8316 Clients should upgrade so they are no longer recognizable by the TLS
8317 certs they present. Relays should upgrade so they no longer allow a
8318 remote attacker to probe them to test whether unpatched clients are
8319 currently connected to them.
8321 This release also fixes several vulnerabilities that allow an attacker
8322 to enumerate bridge relays. Some bridge enumeration attacks still
8323 remain; see for example proposal 188.
8325 o Privacy/anonymity fixes (clients):
8326 - Clients and bridges no longer send TLS certificate chains on
8327 outgoing OR connections. Previously, each client or bridge would
8328 use the same cert chain for all outgoing OR connections until
8329 its IP address changes, which allowed any relay that the client
8330 or bridge contacted to determine which entry guards it is using.
8331 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8332 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8333 no longer considers that connection as suitable for satisfying a
8334 circuit EXTEND request. Now relays can protect clients from the
8335 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8336 - Directory authorities no longer assign the Guard flag to relays
8337 that haven't upgraded to the above "refuse EXTEND requests
8338 to client connections" fix. Now directory authorities can
8339 protect clients from the CVE-2011-2768 issue even if neither
8340 the clients nor the relays have upgraded yet. There's a new
8341 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8342 to let us transition smoothly, else tomorrow there would be no
8345 o Privacy/anonymity fixes (bridge enumeration):
8346 - Bridge relays now do their directory fetches inside Tor TLS
8347 connections, like all the other clients do, rather than connecting
8348 directly to the DirPort like public relays do. Removes another
8349 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8350 - Bridges relays now build circuits for themselves in a more similar
8351 way to how clients build them. Removes another avenue for
8352 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8353 when bridges were introduced.
8354 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8355 that they initiated. Relays could distinguish incoming bridge
8356 connections from client connections, creating another avenue for
8357 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8358 Found by "frosty_un".
8361 - Fix a crash bug when changing node restrictions while a DNS lookup
8362 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8364 - Don't launch a useless circuit after failing to use one of a
8365 hidden service's introduction points. Previously, we would
8366 launch a new introduction circuit, but not set the hidden service
8367 which that circuit was intended to connect to, so it would never
8368 actually be used. A different piece of code would then create a
8369 new introduction circuit correctly. Bug reported by katmagic and
8370 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8373 - Change an integer overflow check in the OpenBSD_Malloc code so
8374 that GCC is less likely to eliminate it as impossible. Patch
8375 from Mansour Moufid. Fixes bug 4059.
8376 - When a hidden service turns an extra service-side introduction
8377 circuit into a general-purpose circuit, free the rend_data and
8378 intro_key fields first, so we won't leak memory if the circuit
8379 is cannibalized for use as another service-side introduction
8380 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8381 - Bridges now skip DNS self-tests, to act a little more stealthily.
8382 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8383 bridges. Patch by "warms0x".
8384 - Fix internal bug-checking logic that was supposed to catch
8385 failures in digest generation so that it will fail more robustly
8386 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8387 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8388 - Report any failure in init_keys() calls launched because our
8389 IP address has changed. Spotted by Coverity Scan. Bugfix on
8390 0.1.1.4-alpha; fixes CID 484.
8392 o Minor bugfixes (log messages and documentation):
8393 - Remove a confusing dollar sign from the example fingerprint in the
8394 man page, and also make the example fingerprint a valid one. Fixes
8395 bug 4309; bugfix on 0.2.1.3-alpha.
8396 - The next version of Windows will be called Windows 8, and it has
8397 a major version of 6, minor version of 2. Correctly identify that
8398 version instead of calling it "Very recent version". Resolves
8399 ticket 4153; reported by funkstar.
8400 - Downgrade log messages about circuit timeout calibration from
8401 "notice" to "info": they don't require or suggest any human
8402 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8403 bugfix on 0.2.2.14-alpha.
8406 - Turn on directory request statistics by default and include them in
8407 extra-info descriptors. Don't break if we have no GeoIP database.
8408 Backported from 0.2.3.1-alpha; implements ticket 3951.
8409 - Update to the October 4 2011 Maxmind GeoLite Country database.
8412 Changes in version 0.2.1.31 - 2011-10-26
8413 Tor 0.2.1.31 backports important security and privacy fixes for
8414 oldstable. This release is intended only for package maintainers and
8415 others who cannot use the 0.2.2 stable series. All others should be
8416 using Tor 0.2.2.x or newer.
8418 o Security fixes (also included in 0.2.2.x):
8419 - Replace all potentially sensitive memory comparison operations
8420 with versions whose runtime does not depend on the data being
8421 compared. This will help resist a class of attacks where an
8422 adversary can use variations in timing information to learn
8423 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8424 implementation by Robert Ransom based partially on code by DJB.)
8425 - Fix an assert in parsing router descriptors containing IPv6
8426 addresses. This one took down the directory authorities when
8427 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8429 o Privacy/anonymity fixes (also included in 0.2.2.x):
8430 - Clients and bridges no longer send TLS certificate chains on
8431 outgoing OR connections. Previously, each client or bridge would
8432 use the same cert chain for all outgoing OR connections until
8433 its IP address changes, which allowed any relay that the client
8434 or bridge contacted to determine which entry guards it is using.
8435 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8436 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8437 no longer considers that connection as suitable for satisfying a
8438 circuit EXTEND request. Now relays can protect clients from the
8439 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8440 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8441 that they initiated. Relays could distinguish incoming bridge
8442 connections from client connections, creating another avenue for
8443 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8444 Found by "frosty_un".
8445 - When receiving a hidden service descriptor, check that it is for
8446 the hidden service we wanted. Previously, Tor would store any
8447 hidden service descriptors that a directory gave it, whether it
8448 wanted them or not. This wouldn't have let an attacker impersonate
8449 a hidden service, but it did let directories pre-seed a client
8450 with descriptors that it didn't want. Bugfix on 0.0.6.
8451 - Avoid linkability based on cached hidden service descriptors: forget
8452 all hidden service descriptors cached as a client when processing a
8453 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8454 - Make the bridge directory authority refuse to answer directory
8455 requests for "all" descriptors. It used to include bridge
8456 descriptors in its answer, which was a major information leak.
8457 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8458 - Don't attach new streams to old rendezvous circuits after SIGNAL
8459 NEWNYM. Previously, we would keep using an existing rendezvous
8460 circuit if it remained open (i.e. if it were kept open by a
8461 long-lived stream, or if a new stream were attached to it before
8462 Tor could notice that it was old and no longer in use). Bugfix on
8463 0.1.1.15-rc; fixes bug 3375.
8465 o Minor bugfixes (also included in 0.2.2.x):
8466 - When we restart our relay, we might get a successful connection
8467 from the outside before we've started our reachability tests,
8468 triggering a warning: "ORPort found reachable, but I have no
8469 routerinfo yet. Failing to inform controller of success." This
8470 bug was harmless unless Tor is running under a controller
8471 like Vidalia, in which case the controller would never get a
8472 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8474 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8475 enabled. Fixes bug 1526.
8476 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8477 anything since 0.2.1.16-rc.
8478 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8479 None of the cases where we did this before were wrong, but by making
8480 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8481 - Fix a rare crash bug that could occur when a client was configured
8482 with a large number of bridges. Fixes bug 2629; bugfix on
8483 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8484 - Correct the warning displayed when a rendezvous descriptor exceeds
8485 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8487 - Fix an uncommon assertion failure when running with DNSPort under
8488 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8489 - When warning about missing zlib development packages during compile,
8490 give the correct package names. Bugfix on 0.2.0.1-alpha.
8491 - Require that introduction point keys and onion keys have public
8492 exponent 65537. Bugfix on 0.2.0.10-alpha.
8493 - Do not crash when our configuration file becomes unreadable, for
8494 example due to a permissions change, between when we start up
8495 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8497 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8499 - Always NUL-terminate the sun_path field of a sockaddr_un before
8500 passing it to the kernel. (Not a security issue: kernels are
8501 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8502 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8503 - Don't stack-allocate the list of supplementary GIDs when we're
8504 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8505 could take up to 256K, which is way too much stack. Found by
8506 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8508 o Minor bugfixes (only in 0.2.1.x):
8509 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
8510 rely on them. Bugfix on 0.2.1.30.
8511 - Use git revisions instead of svn revisions when generating our
8512 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8514 o Minor features (also included in 0.2.2.x):
8515 - Adjust the expiration time on our SSL session certificates to
8516 better match SSL certs seen in the wild. Resolves ticket 4014.
8517 - Allow nameservers with IPv6 address. Resolves bug 2574.
8518 - Update to the October 4 2011 Maxmind GeoLite Country database.
8521 Changes in version 0.2.3.5-alpha - 2011-09-28
8522 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
8523 bridge relays; fixes an assertion error that many users started hitting
8524 today; and adds the ability to refill token buckets more often than
8525 once per second, allowing significant performance improvements.
8528 - Bridge relays now do their directory fetches inside Tor TLS
8529 connections, like all the other clients do, rather than connecting
8530 directly to the DirPort like public relays do. Removes another
8531 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8532 - Bridges relays now build circuits for themselves in a more similar
8533 way to how clients build them. Removes another avenue for
8534 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8535 when bridges were introduced.
8538 - Fix an "Assertion md->held_by_node == 1 failed" error that could
8539 occur when the same microdescriptor was referenced by two node_t
8540 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
8542 o Major features (networking):
8543 - Add a new TokenBucketRefillInterval option to refill token buckets
8544 more frequently than once per second. This should improve network
8545 performance, alleviate queueing problems, and make traffic less
8546 bursty. Implements proposal 183; closes ticket 3630. Design by
8547 Florian Tschorsch and Björn Scheuermann; implementation by
8551 - Change an integer overflow check in the OpenBSD_Malloc code so
8552 that GCC is less likely to eliminate it as impossible. Patch
8553 from Mansour Moufid. Fixes bug 4059.
8555 o Minor bugfixes (usability):
8556 - Downgrade log messages about circuit timeout calibration from
8557 "notice" to "info": they don't require or suggest any human
8558 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8559 bugfix on 0.2.2.14-alpha.
8561 o Minor features (diagnostics):
8562 - When the system call to create a listener socket fails, log the
8563 error message explaining why. This may help diagnose bug 4027.
8566 Changes in version 0.2.3.4-alpha - 2011-09-13
8567 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
8568 tweak to Tor's TLS handshake that makes relays and bridges that run
8569 this new version reachable from Iran again. It also fixes a few new
8570 bugs in 0.2.3.x, and teaches relays to recognize when they're not
8571 listed in the network consensus and republish.
8573 o Major bugfixes (also part of 0.2.2.33):
8574 - Avoid an assertion failure when reloading a configuration with
8575 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8576 3923; bugfix on 0.2.2.25-alpha.
8578 o Minor features (security, also part of 0.2.2.33):
8579 - Check for replays of the public-key encrypted portion of an
8580 INTRODUCE1 cell, in addition to the current check for replays of
8581 the g^x value. This prevents a possible class of active attacks
8582 by an attacker who controls both an introduction point and a
8583 rendezvous point, and who uses the malleability of AES-CTR to
8584 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8585 that these attacks are infeasible (requiring the attacker to send
8586 on the order of zettabytes of altered cells in a short interval),
8587 but we'd rather block them off in case there are any classes of
8588 this attack that we missed. Reported by Willem Pinckaers.
8590 o Minor features (also part of 0.2.2.33):
8591 - Adjust the expiration time on our SSL session certificates to
8592 better match SSL certs seen in the wild. Resolves ticket 4014.
8593 - Change the default required uptime for a relay to be accepted as
8594 a HSDir (hidden service directory) from 24 hours to 25 hours.
8595 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8596 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8597 authorities to abstain from voting on assignment of the HSDir
8598 consensus flag. Related to bug 2649.
8599 - Update to the September 6 2011 Maxmind GeoLite Country database.
8601 o Minor bugfixes (also part of 0.2.2.33):
8602 - Demote the 'replay detected' log message emitted when a hidden
8603 service receives the same Diffie-Hellman public key in two different
8604 INTRODUCE2 cells to info level. A normal Tor client can cause that
8605 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8606 fixes part of bug 2442.
8607 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8608 level. There is nothing that a hidden service's operator can do
8609 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8611 - Clarify a log message specifying the characters permitted in
8612 HiddenServiceAuthorizeClient client names. Previously, the log
8613 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8614 given the impression that every ASCII character between "+" and "_"
8615 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8617 o Build fixes (also part of 0.2.2.33):
8618 - Clean up some code issues that prevented Tor from building on older
8619 BSDs. Fixes bug 3894; reported by "grarpamp".
8620 - Search for a platform-specific version of "ar" when cross-compiling.
8621 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8624 - Fix a bug where the SocksPort option (for example) would get
8625 ignored and replaced by the default if a SocksListenAddress
8626 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
8630 - Relays now try regenerating and uploading their descriptor more
8631 frequently if they are not listed in the consensus, or if the
8632 version of their descriptor listed in the consensus is too
8633 old. This fix should prevent situations where a server declines
8634 to re-publish itself because it has done so too recently, even
8635 though the authorities decided not to list its recent-enough
8636 descriptor. Fix for bug 3327.
8639 - Relays now include a reason for regenerating their descriptors
8640 in an HTTP header when uploading to the authorities. This will
8641 make it easier to debug descriptor-upload issues in the future.
8642 - When starting as root and then changing our UID via the User
8643 control option, and we have a ControlSocket configured, make sure
8644 that the ControlSocket is owned by the same account that Tor will
8645 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8648 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
8649 utility function used in the control-port code). This shouldn't
8650 ever happen unless Tor is completely out of memory, but if it did
8651 happen and Tor somehow recovered from it, Tor could have sent a log
8652 message to a control port in the middle of a reply to a controller
8653 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8654 - Make 'FetchUselessDescriptors' cause all descriptor types and
8655 all consensus types (including microdescriptors) to get fetched.
8656 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
8659 - Make a new "entry connection" struct as an internal subtype of "edge
8660 connection", to simplify the code and make exit connections smaller.
8663 Changes in version 0.2.2.33 - 2011-09-13
8664 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8665 TLS handshake that makes relays and bridges that run this new version
8666 reachable from Iran again.
8669 - Avoid an assertion failure when reloading a configuration with
8670 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8671 3923; bugfix on 0.2.2.25-alpha.
8673 o Minor features (security):
8674 - Check for replays of the public-key encrypted portion of an
8675 INTRODUCE1 cell, in addition to the current check for replays of
8676 the g^x value. This prevents a possible class of active attacks
8677 by an attacker who controls both an introduction point and a
8678 rendezvous point, and who uses the malleability of AES-CTR to
8679 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8680 that these attacks are infeasible (requiring the attacker to send
8681 on the order of zettabytes of altered cells in a short interval),
8682 but we'd rather block them off in case there are any classes of
8683 this attack that we missed. Reported by Willem Pinckaers.
8686 - Adjust the expiration time on our SSL session certificates to
8687 better match SSL certs seen in the wild. Resolves ticket 4014.
8688 - Change the default required uptime for a relay to be accepted as
8689 a HSDir (hidden service directory) from 24 hours to 25 hours.
8690 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8691 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8692 authorities to abstain from voting on assignment of the HSDir
8693 consensus flag. Related to bug 2649.
8694 - Update to the September 6 2011 Maxmind GeoLite Country database.
8696 o Minor bugfixes (documentation and log messages):
8697 - Correct the man page to explain that HashedControlPassword and
8698 CookieAuthentication can both be set, in which case either method
8699 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8700 when we decided to allow these config options to both be set. Issue
8702 - Demote the 'replay detected' log message emitted when a hidden
8703 service receives the same Diffie-Hellman public key in two different
8704 INTRODUCE2 cells to info level. A normal Tor client can cause that
8705 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8706 fixes part of bug 2442.
8707 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8708 level. There is nothing that a hidden service's operator can do
8709 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8711 - Clarify a log message specifying the characters permitted in
8712 HiddenServiceAuthorizeClient client names. Previously, the log
8713 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8714 given the impression that every ASCII character between "+" and "_"
8715 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8718 - Provide a substitute implementation of lround() for MSVC, which
8719 apparently lacks it. Patch from Gisle Vanem.
8720 - Clean up some code issues that prevented Tor from building on older
8721 BSDs. Fixes bug 3894; reported by "grarpamp".
8722 - Search for a platform-specific version of "ar" when cross-compiling.
8723 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8726 Changes in version 0.2.3.3-alpha - 2011-09-01
8727 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
8728 security, and provides client-side support for the microdescriptor
8729 and optimistic data features introduced earlier in the 0.2.3.x
8730 series. It also includes numerous critical bugfixes in the (optional)
8731 bufferevent-based networking backend.
8733 o Major features (stream isolation):
8734 - You can now configure Tor so that streams from different
8735 applications are isolated on different circuits, to prevent an
8736 attacker who sees your streams as they leave an exit node from
8737 linking your sessions to one another. To do this, choose some way
8738 to distinguish the applications: have them connect to different
8739 SocksPorts, or have one of them use SOCKS4 while the other uses
8740 SOCKS5, or have them pass different authentication strings to the
8741 SOCKS proxy. Then, use the new SocksPort syntax to configure the
8742 degree of isolation you need. This implements Proposal 171.
8743 - There's a new syntax for specifying multiple client ports (such as
8744 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
8745 multiple *Port entries with full addr:port syntax on each.
8746 The old *ListenAddress format is still supported, but you can't
8747 mix it with the new *Port syntax.
8749 o Major features (other):
8750 - Enable microdescriptor fetching by default for clients. This allows
8751 clients to download a much smaller amount of directory information.
8752 To disable it (and go back to the old-style consensus and
8753 descriptors), set "UseMicrodescriptors 0" in your torrc file.
8754 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
8755 "PortForwarding" config option), now supports Windows.
8756 - When using an exit relay running 0.2.3.x, clients can now
8757 "optimistically" send data before the exit relay reports that
8758 the stream has opened. This saves a round trip when starting
8759 connections where the client speaks first (such as web browsing).
8760 This behavior is controlled by a consensus parameter (currently
8761 disabled). To turn it on or off manually, use the "OptimisticData"
8762 torrc option. Implements proposal 181; code by Ian Goldberg.
8764 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
8765 - When using IOCP on Windows, we need to enable Libevent windows
8767 - The IOCP backend now works even when the user has not specified
8768 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
8769 Fixes part of bug 3752.
8770 - Correctly record the bytes we've read and written when using
8771 bufferevents, so that we can include them in our bandwidth history
8772 and advertised bandwidth. Fixes bug 3803.
8773 - Apply rate-limiting only at the bottom of a chain of filtering
8774 bufferevents. This prevents us from filling up internal read
8775 buffers and violating rate-limits when filtering bufferevents
8776 are enabled. Fixes part of bug 3804.
8777 - Add high-watermarks to the output buffers for filtered
8778 bufferevents. This prevents us from filling up internal write
8779 buffers and wasting CPU cycles when filtering bufferevents are
8780 enabled. Fixes part of bug 3804.
8781 - Correctly notice when data has been written from a bufferevent
8782 without flushing it completely. Fixes bug 3805.
8783 - Fix a bug where server-side tunneled bufferevent-based directory
8784 streams would get closed prematurely. Fixes bug 3814.
8785 - Fix a use-after-free error with per-connection rate-limiting
8786 buckets. Fixes bug 3888.
8788 o Major bugfixes (also part of 0.2.2.31-rc):
8789 - If we're configured to write our ControlPorts to disk, only write
8790 them after switching UID and creating the data directory. This way,
8791 we don't fail when starting up with a nonexistent DataDirectory
8792 and a ControlPortWriteToFile setting based on that directory. Fixes
8793 bug 3747; bugfix on Tor 0.2.2.26-beta.
8796 - Added a new CONF_CHANGED event so that controllers can be notified
8797 of any configuration changes made by other controllers, or by the
8798 user. Implements ticket 1692.
8799 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
8800 leak when using bufferevents, and lets Libevent worry about how to
8801 best copy data out of a buffer.
8802 - Replace files in stats/ rather than appending to them. Now that we
8803 include statistics in extra-info descriptors, it makes no sense to
8804 keep old statistics forever. Implements ticket 2930.
8806 o Minor features (build compatibility):
8807 - Limited, experimental support for building with nmake and MSVC.
8808 - Provide a substitute implementation of lround() for MSVC, which
8809 apparently lacks it. Patch from Gisle Vanem.
8811 o Minor features (also part of 0.2.2.31-rc):
8812 - Update to the August 2 2011 Maxmind GeoLite Country database.
8814 o Minor bugfixes (on 0.2.3.x-alpha):
8815 - Fix a spurious warning when parsing SOCKS requests with
8816 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
8817 - Get rid of a harmless warning that could happen on relays running
8818 with bufferevents. The warning was caused by someone doing an http
8819 request to a relay's orport. Also don't warn for a few related
8820 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
8822 o Minor bugfixes (on 2.2.x and earlier):
8823 - Correct the man page to explain that HashedControlPassword and
8824 CookieAuthentication can both be set, in which case either method
8825 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8826 when we decided to allow these config options to both be set. Issue
8828 - The "--quiet" and "--hush" options now apply not only to Tor's
8829 behavior before logs are configured, but also to Tor's behavior in
8830 the absense of configured logs. Fixes bug 3550; bugfix on
8833 o Minor bugfixes (also part of 0.2.2.31-rc):
8834 - Write several files in text mode, on OSes that distinguish text
8835 mode from binary mode (namely, Windows). These files are:
8836 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8837 that collect those statistics; 'client_keys' and 'hostname' for
8838 hidden services that use authentication; and (in the tor-gencert
8839 utility) newly generated identity and signing keys. Previously,
8840 we wouldn't specify text mode or binary mode, leading to an
8841 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8842 the DirRecordUsageByCountry option which would have triggered
8843 the assertion failure was added), although this assertion failure
8844 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8845 - Selectively disable deprecation warnings on OS X because Lion
8846 started deprecating the shipped copy of openssl. Fixes bug 3643.
8847 - Remove an extra pair of quotation marks around the error
8848 message in control-port STATUS_GENERAL BUG events. Bugfix on
8849 0.1.2.6-alpha; fixes bug 3732.
8850 - When unable to format an address as a string, report its value
8851 as "???" rather than reusing the last formatted address. Bugfix
8854 o Code simplifications and refactoring:
8855 - Rewrite the listener-selection logic so that parsing which ports
8856 we want to listen on is now separate from binding to the ports
8860 - Building Tor with bufferevent support now requires Libevent
8861 2.0.13-stable or later. Previous versions of Libevent had bugs in
8862 SSL-related bufferevents and related issues that would make Tor
8863 work badly with bufferevents. Requiring 2.0.13-stable also allows
8864 Tor with bufferevents to take advantage of Libevent APIs
8865 introduced after 2.0.8-rc.
8868 Changes in version 0.2.2.32 - 2011-08-27
8869 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8870 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8871 a founder of the PETS community, a leader in our field, a mentor,
8872 and a friend. He left us with these words: "I had the possibility
8873 to contribute to this world that is not as it should be. I hope I
8874 could help in some areas to make the world a better place, and that
8875 I could also encourage other people to be engaged in improving the
8876 world. Please, stay engaged. This world needs you, your love, your
8877 initiative -- now I cannot be part of that anymore."
8879 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8880 ready. More than two years in the making, this release features improved
8881 client performance and hidden service reliability, better compatibility
8882 for Android, correct behavior for bridges that listen on more than
8883 one address, more extensible and flexible directory object handling,
8884 better reporting of network statistics, improved code security, and
8885 many many other features and bugfixes.
8888 Changes in version 0.2.2.31-rc - 2011-08-17
8889 Tor 0.2.2.31-rc is the second and hopefully final release candidate
8890 for the Tor 0.2.2.x series.
8893 - Remove an extra pair of quotation marks around the error
8894 message in control-port STATUS_GENERAL BUG events. Bugfix on
8895 0.1.2.6-alpha; fixes bug 3732.
8896 - If we're configured to write our ControlPorts to disk, only write
8897 them after switching UID and creating the data directory. This way,
8898 we don't fail when starting up with a nonexistent DataDirectory
8899 and a ControlPortWriteToFile setting based on that directory. Fixes
8900 bug 3747; bugfix on Tor 0.2.2.26-beta.
8903 - Update to the August 2 2011 Maxmind GeoLite Country database.
8906 - Allow GETINFO fingerprint to return a fingerprint even when
8907 we have not yet built a router descriptor. Fixes bug 3577;
8908 bugfix on 0.2.0.1-alpha.
8909 - Write several files in text mode, on OSes that distinguish text
8910 mode from binary mode (namely, Windows). These files are:
8911 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8912 that collect those statistics; 'client_keys' and 'hostname' for
8913 hidden services that use authentication; and (in the tor-gencert
8914 utility) newly generated identity and signing keys. Previously,
8915 we wouldn't specify text mode or binary mode, leading to an
8916 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8917 the DirRecordUsageByCountry option which would have triggered
8918 the assertion failure was added), although this assertion failure
8919 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8920 - Selectively disable deprecation warnings on OS X because Lion
8921 started deprecating the shipped copy of openssl. Fixes bug 3643.
8922 - When unable to format an address as a string, report its value
8923 as "???" rather than reusing the last formatted address. Bugfix
8927 Changes in version 0.2.3.2-alpha - 2011-07-18
8928 Tor 0.2.3.2-alpha introduces two new experimental features:
8929 microdescriptors and pluggable transports. It also continues cleaning
8930 up a variety of recently introduced features.
8933 - Clients can now use microdescriptors instead of regular descriptors
8934 to build circuits. Microdescriptors are authority-generated
8935 summaries of regular descriptors' contents, designed to change
8936 very rarely (see proposal 158 for details). This feature is
8937 designed to save bandwidth, especially for clients on slow internet
8938 connections. It's off by default for now, since nearly no caches
8939 support it, but it will be on-by-default for clients in a future
8940 version. You can use the UseMicrodescriptors option to turn it on.
8941 - Tor clients using bridges can now be configured to use a separate
8942 'transport' proxy for each bridge. This approach helps to resist
8943 censorship by allowing bridges to use protocol obfuscation
8944 plugins. It implements part of proposal 180. Implements ticket 2841.
8945 - While we're trying to bootstrap, record how many TLS connections
8946 fail in each state, and report which states saw the most failures
8947 in response to any bootstrap failures. This feature may speed up
8948 diagnosis of censorship events. Implements ticket 3116.
8950 o Major bugfixes (on 0.2.3.1-alpha):
8951 - When configuring a large set of nodes in EntryNodes (as with
8952 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
8953 random subset to be guards, and choose them in random
8954 order. Fixes bug 2798.
8955 - Tor could crash when remembering a consensus in a non-used consensus
8956 flavor without having a current consensus set. Fixes bug 3361.
8957 - Comparing an unknown address to a microdescriptor's shortened exit
8958 policy would always give a "rejected" result. Fixes bug 3599.
8959 - Using microdescriptors as a client no longer prevents Tor from
8960 uploading and downloading hidden service descriptors. Fixes
8964 - Allow nameservers with IPv6 address. Resolves bug 2574.
8965 - Accept attempts to include a password authenticator in the
8966 handshake, as supported by SOCKS5. This handles SOCKS clients that
8967 don't know how to omit a password when authenticating. Resolves
8969 - When configuring a large set of nodes in EntryNodes, and there are
8970 enough of them listed as Guard so that we don't need to consider
8971 the non-guard entries, prefer the ones listed with the Guard flag.
8972 - Check for and recover from inconsistency in the microdescriptor
8973 cache. This will make it harder for us to accidentally free a
8974 microdescriptor without removing it from the appropriate data
8975 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8976 - Log SSL state transitions at log level DEBUG, log domain
8977 HANDSHAKE. This can be useful for debugging censorship events.
8978 Implements ticket 3264.
8979 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8980 implements ticket 3439.
8982 o Minor bugfixes (on 0.2.3.1-alpha):
8983 - Do not free all general-purpose regular descriptors just
8984 because microdescriptor use is enabled. Fixes bug 3113.
8985 - Correctly link libevent_openssl when --enable-static-libevent
8986 is passed to configure. Fixes bug 3118.
8987 - Bridges should not complain during their heartbeat log messages that
8988 they are unlisted in the consensus: that's more or less the point
8989 of being a bridge. Fixes bug 3183.
8990 - Report a SIGNAL event to controllers when acting on a delayed
8991 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
8992 event to the controller if we acted on a SIGNAL NEWNYM command
8993 immediately, and otherwise not report a SIGNAL event for the
8994 command at all. Fixes bug 3349.
8995 - Fix a crash when handling the SIGNAL controller command or
8996 reporting ERR-level status events with bufferevents enabled. Found
8997 by Robert Ransom. Fixes bug 3367.
8998 - Always ship the tor-fw-helper manpage in our release tarballs.
8999 Fixes bug 3389. Reported by Stephen Walker.
9000 - Fix a class of double-mark-for-close bugs when bufferevents
9001 are enabled. Fixes bug 3403.
9002 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
9003 - Add SIGNAL to the list returned by the 'GETINFO events/names'
9004 control-port command. Fixes part of bug 3465.
9005 - Prevent using negative indices during unit test runs when read_all()
9006 fails. Spotted by coverity.
9007 - Fix a rare memory leak when checking the nodelist without it being
9008 present. Found by coverity.
9009 - Only try to download a microdescriptor-flavored consensus from
9010 a directory cache that provides them.
9012 o Minor bugfixes (on 0.2.2.x and earlier):
9013 - Assert that hidden-service-related operations are not performed
9014 using single-hop circuits. Previously, Tor would assert that
9015 client-side streams are not attached to single-hop circuits,
9016 but not that other sensitive operations on the client and service
9017 side are not performed using single-hop circuits. Fixes bug 3332;
9019 - Don't publish a new relay descriptor when we reload our onion key,
9020 unless the onion key has actually changed. Fixes bug 3263 and
9021 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
9022 - Allow GETINFO fingerprint to return a fingerprint even when
9023 we have not yet built a router descriptor. Fixes bug 3577;
9024 bugfix on 0.2.0.1-alpha.
9025 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
9026 on 0.2.2.4-alpha; fixes bug 3427.
9028 o Code simplification and refactoring:
9029 - Use tor_sscanf() in place of scanf() in more places through the
9030 code. This makes us a little more locale-independent, and
9031 should help shut up code-analysis tools that can't tell
9032 a safe sscanf string from a dangerous one.
9033 - Use tt_assert(), not tor_assert(), for checking for test failures.
9034 This makes the unit tests more able to go on in the event that
9036 - Split connection_about_to_close() into separate functions for each
9040 - On Windows, we now define the _WIN32_WINNT macros only if they
9041 are not already defined. This lets the person building Tor decide,
9042 if they want, to require a later version of Windows.
9045 Changes in version 0.2.2.30-rc - 2011-07-07
9046 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
9047 series. It fixes a few smaller bugs, but generally appears stable.
9048 Please test it and let us know whether it is!
9051 - Send a SUCCEEDED stream event to the controller when a reverse
9052 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9053 discovered by katmagic.
9054 - Always NUL-terminate the sun_path field of a sockaddr_un before
9055 passing it to the kernel. (Not a security issue: kernels are
9056 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9057 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9058 - Don't stack-allocate the list of supplementary GIDs when we're
9059 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9060 could take up to 256K, which is way too much stack. Found by
9061 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9062 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
9063 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
9064 fixes part of bug 3465.
9065 - Fix a memory leak when receiving a descriptor for a hidden
9066 service we didn't ask for. Found by Coverity; CID #30. Bugfix
9070 - Update to the July 1 2011 Maxmind GeoLite Country database.
9073 Changes in version 0.2.2.29-beta - 2011-06-20
9074 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
9075 have bridge lines in their torrc but don't want to use them; gets
9076 us closer to having the control socket feature working on Debian;
9077 and fixes a variety of smaller bugs.
9080 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
9081 When we changed the default behavior to "use bridges if any
9082 are listed in the torrc", we surprised users who had bridges
9083 in their torrc files but who didn't actually want to use them.
9084 Partial resolution for bug 3354.
9087 - Don't attach new streams to old rendezvous circuits after SIGNAL
9088 NEWNYM. Previously, we would keep using an existing rendezvous
9089 circuit if it remained open (i.e. if it were kept open by a
9090 long-lived stream, or if a new stream were attached to it before
9091 Tor could notice that it was old and no longer in use). Bugfix on
9092 0.1.1.15-rc; fixes bug 3375.
9095 - Fix a bug when using ControlSocketsGroupWritable with User. The
9096 directory's group would be checked against the current group, not
9097 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
9098 bugfix on 0.2.2.26-beta.
9099 - Make connection_printf_to_buf()'s behavior sane. Its callers
9100 expect it to emit a CRLF iff the format string ends with CRLF;
9101 it actually emitted a CRLF iff (a) the format string ended with
9102 CRLF or (b) the resulting string was over 1023 characters long or
9103 (c) the format string did not end with CRLF *and* the resulting
9104 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9105 fixes part of bug 3407.
9106 - Make send_control_event_impl()'s behavior sane. Its callers
9107 expect it to always emit a CRLF at the end of the string; it
9108 might have emitted extra control characters as well. Bugfix on
9109 0.1.1.9-alpha; fixes another part of bug 3407.
9110 - Make crypto_rand_int() check the value of its input correctly.
9111 Previously, it accepted values up to UINT_MAX, but could return a
9112 negative number if given a value above INT_MAX+1. Found by George
9113 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9114 - Avoid a segfault when reading a malformed circuit build state
9115 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
9117 - When asked about a DNS record type we don't support via a
9118 client DNSPort, reply with NOTIMPL rather than an empty
9119 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
9120 - Fix a rare memory leak during stats writing. Found by coverity.
9123 - Update to the June 1 2011 Maxmind GeoLite Country database.
9125 o Code simplifications and refactoring:
9126 - Remove some dead code as indicated by coverity.
9127 - Remove a few dead assignments during router parsing. Found by
9129 - Add some forgotten return value checks during unit tests. Found
9131 - Don't use 1-bit wide signed bit fields. Found by coverity.
9134 Changes in version 0.2.2.28-beta - 2011-06-04
9135 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
9136 fixed a big bug in whether relays stay in the consensus consistently,
9137 we moved closer to handling bridges and hidden services correctly,
9138 and we started the process of better handling the dreaded "my Vidalia
9139 died, and now my Tor demands a password when I try to reconnect to it"
9143 - Don't decide to make a new descriptor when receiving a HUP signal.
9144 This bug has caused a lot of 0.2.2.x relays to disappear from the
9145 consensus periodically. Fixes the most common case of triggering
9146 bug 1810; bugfix on 0.2.2.7-alpha.
9147 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
9148 - Don't try to build descriptors if "ORPort auto" is set and we
9149 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
9151 - Resolve a crash that occurred when setting BridgeRelay to 1 with
9152 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
9153 - Apply circuit timeouts to opened hidden-service-related circuits
9154 based on the correct start time. Previously, we would apply the
9155 circuit build timeout based on time since the circuit's creation;
9156 it was supposed to be applied based on time since the circuit
9157 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
9158 - Use the same circuit timeout for client-side introduction
9159 circuits as for other four-hop circuits, rather than the timeout
9160 for single-hop directory-fetch circuits; the shorter timeout may
9161 have been appropriate with the static circuit build timeout in
9162 0.2.1.x and earlier, but caused many hidden service access attempts
9163 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
9164 on 0.2.2.2-alpha; fixes another part of bug 1297.
9165 - In ticket 2511 we fixed a case where you could use an unconfigured
9166 bridge if you had configured it as a bridge the last time you ran
9167 Tor. Now fix another edge case: if you had configured it as a bridge
9168 but then switched to a different bridge via the controller, you
9169 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
9173 - Add an __OwningControllerProcess configuration option and a
9174 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
9175 that when it exits, Tor will shut down. Implements feature 3049.
9176 - If "UseBridges 1" is set and no bridges are configured, Tor will
9177 now refuse to build any circuits until some bridges are set.
9178 If "UseBridges auto" is set, Tor will use bridges if they are
9179 configured and we are not running as a server, but otherwise will
9180 make circuits as usual. The new default is "auto". Patch by anonym,
9181 so the Tails LiveCD can stop automatically revealing you as a Tor
9185 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9186 - Remove a trailing asterisk from "exit-policy/default" in the
9187 output of the control port command "GETINFO info/names". Bugfix
9189 - Use a wide type to hold sockets when built for 64-bit Windows builds.
9191 - Warn when the user configures two HiddenServiceDir lines that point
9192 to the same directory. Bugfix on 0.0.6 (the version introducing
9193 HiddenServiceDir); fixes bug 3289.
9194 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
9195 part of bug 2748; bugfix on 0.2.0.10-alpha.
9196 - Log malformed requests for rendezvous descriptors as protocol
9197 warnings, not warnings. Also, use a more informative log message
9198 in case someone sees it at log level warning without prior
9199 info-level messages. Fixes the other part of bug 2748; bugfix
9201 - Clear the table recording the time of the last request for each
9202 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
9203 Previously, we would clear our HS descriptor cache on SIGNAL
9204 NEWNYM, but if we had previously retrieved a descriptor (or tried
9205 to) from every directory responsible for it, we would refuse to
9206 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
9208 - Fix a log message that said "bits" while displaying a value in
9209 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
9211 - When checking for 1024-bit keys, check for 1024 bits, not 128
9212 bytes. This allows Tor to correctly discard keys of length 1017
9213 through 1023. Bugfix on 0.0.9pre5.
9216 - Relays now log the reason for publishing a new relay descriptor,
9217 so we have a better chance of hunting down instances of bug 1810.
9218 Resolves ticket 3252.
9219 - Revise most log messages that refer to nodes by nickname to
9220 instead use the "$key=nickname at address" format. This should be
9221 more useful, especially since nicknames are less and less likely
9222 to be unique. Resolves ticket 3045.
9223 - Log (at info level) when purging pieces of hidden-service-client
9224 state because of SIGNAL NEWNYM.
9227 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9228 anything since 0.2.1.16-rc.
9231 Changes in version 0.2.2.27-beta - 2011-05-18
9232 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
9233 release, and also adds a few more general bugfixes.
9236 - Fix a crash bug when changing bridges in a running Tor process.
9237 Fixes bug 3213; bugfix on 0.2.2.26-beta.
9238 - When the controller configures a new bridge, don't wait 10 to 60
9239 seconds before trying to fetch its descriptor. Bugfix on
9240 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
9243 - Require that onion keys have exponent 65537 in microdescriptors too.
9244 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
9245 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
9246 Changed the limit to 512 characters by removing base64 newlines.
9247 Fixes bug 2752. Fix by Michael Yakubovich.
9248 - When a client starts or stops using bridges, never use a circuit
9249 that was built before the configuration change. This behavior could
9250 put at risk a user who uses bridges to ensure that her traffic
9251 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
9255 Changes in version 0.2.2.26-beta - 2011-05-17
9256 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
9257 also introduces a new "socksport auto" approach that should make it
9258 easier to run multiple Tors on the same system, and does a lot of
9259 cleanup to get us closer to a release candidate.
9261 o Security/privacy fixes:
9262 - Replace all potentially sensitive memory comparison operations
9263 with versions whose runtime does not depend on the data being
9264 compared. This will help resist a class of attacks where an
9265 adversary can use variations in timing information to learn
9266 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9267 implementation by Robert Ransom based partially on code by DJB.)
9268 - When receiving a hidden service descriptor, check that it is for
9269 the hidden service we wanted. Previously, Tor would store any
9270 hidden service descriptors that a directory gave it, whether it
9271 wanted them or not. This wouldn't have let an attacker impersonate
9272 a hidden service, but it did let directories pre-seed a client
9273 with descriptors that it didn't want. Bugfix on 0.0.6.
9274 - On SIGHUP, do not clear out all TrackHostExits mappings, client
9275 DNS cache entries, and virtual address mappings: that's what
9276 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
9279 - The options SocksPort, ControlPort, and so on now all accept a
9280 value "auto" that opens a socket on an OS-selected port. A
9281 new ControlPortWriteToFile option tells Tor to write its
9282 actual control port or ports to a chosen file. If the option
9283 ControlPortFileGroupReadable is set, the file is created as
9284 group-readable. Now users can run two Tor clients on the same
9285 system without needing to manually mess with parameters. Resolves
9286 part of ticket 3076.
9287 - Set SO_REUSEADDR on all sockets, not just listeners. This should
9288 help busy exit nodes avoid running out of useable ports just
9289 because all the ports have been used in the near past. Resolves
9293 - New "GETINFO net/listeners/(type)" controller command to return
9294 a list of addresses and ports that are bound for listeners for a
9295 given connection type. This is useful when the user has configured
9296 "SocksPort auto" and the controller needs to know which port got
9297 chosen. Resolves another part of ticket 3076.
9298 - Add a new ControlSocketsGroupWritable configuration option: when
9299 it is turned on, ControlSockets are group-writeable by the default
9300 group of the current user. Patch by Jérémy Bobbio; implements
9302 - Tor now refuses to create a ControlSocket in a directory that is
9303 world-readable (or group-readable if ControlSocketsGroupWritable
9304 is 0). This is necessary because some operating systems do not
9305 enforce permissions on an AF_UNIX sockets. Permissions on the
9306 directory holding the socket, however, seems to work everywhere.
9307 - Rate-limit a warning about failures to download v2 networkstatus
9308 documents. Resolves part of bug 1352.
9309 - Backport code from 0.2.3.x that allows directory authorities to
9310 clean their microdescriptor caches. Needed to resolve bug 2230.
9311 - When an HTTPS proxy reports "403 Forbidden", we now explain
9312 what it means rather than calling it an unexpected status code.
9313 Closes bug 2503. Patch from Michael Yakubovich.
9314 - Update to the May 1 2011 Maxmind GeoLite Country database.
9317 - Authorities now clean their microdesc cache periodically and when
9318 reading from disk initially, not only when adding new descriptors.
9319 This prevents a bug where we could lose microdescriptors. Bugfix
9320 on 0.2.2.6-alpha. Fixes bug 2230.
9321 - Do not crash when our configuration file becomes unreadable, for
9322 example due to a permissions change, between when we start up
9323 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9325 - Avoid a bug that would keep us from replacing a microdescriptor
9326 cache on Windows. (We would try to replace the file while still
9327 holding it open. That's fine on Unix, but Windows doesn't let us
9328 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
9329 - Add missing explanations for the authority-related torrc options
9330 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
9331 man page. Resolves issue 2379.
9332 - As an authority, do not upload our own vote or signature set to
9333 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
9334 it would get flagged as a duplicate. Resolves bug 3026.
9335 - Accept hidden service descriptors if we think we might be a hidden
9336 service directory, regardless of what our consensus says. This
9337 helps robustness, since clients and hidden services can sometimes
9338 have a more up-to-date view of the network consensus than we do,
9339 and if they think that the directory authorities list us a HSDir,
9340 we might actually be one. Related to bug 2732; bugfix on
9342 - When a controller changes TrackHostExits, remove mappings for
9343 hosts that should no longer have their exits tracked. Bugfix on
9345 - When a controller changes VirtualAddrNetwork, remove any mappings
9346 for hosts that were automapped to the old network. Bugfix on
9348 - When a controller changes one of the AutomapHosts* options, remove
9349 any mappings for hosts that should no longer be automapped. Bugfix
9351 - Do not reset the bridge descriptor download status every time we
9352 re-parse our configuration or get a configuration change. Fixes
9353 bug 3019; bugfix on 0.2.0.3-alpha.
9355 o Minor bugfixes (code cleanup):
9356 - When loading the microdesc journal, remember its current size.
9357 In 0.2.2, this helps prevent the microdesc journal from growing
9358 without limit on authorities (who are the only ones to use it in
9359 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9360 Fix posted by "cypherpunks."
9361 - The microdesc journal is supposed to get rebuilt only if it is
9362 at least _half_ the length of the store, not _twice_ the length
9363 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9364 - Fix a potential null-pointer dereference while computing a
9365 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
9367 - Avoid a possible null-pointer dereference when rebuilding the mdesc
9368 cache without actually having any descriptors to cache. Bugfix on
9369 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
9370 - If we fail to compute the identity digest of a v3 legacy keypair,
9371 warn, and don't use a buffer-full of junk instead. Bugfix on
9372 0.2.1.1-alpha; fixes bug 3106.
9373 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9374 where if the function had ever in the future been used to check
9375 for the presence of a too-large number, it would have given an
9376 incorrect result. (Fortunately, we only used it for 16-bit
9377 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9378 - Require that introduction point keys and onion handshake keys
9379 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9383 - Caches no longer download and serve v2 networkstatus documents
9384 unless FetchV2Networkstatus flag is set: these documents haven't
9385 haven't been used by clients or relays since 0.2.0.x. Resolves
9389 Changes in version 0.2.3.1-alpha - 2011-05-05
9390 Tor 0.2.3.1-alpha adds some new experimental features, including support
9391 for an improved network IO backend, IOCP networking on Windows,
9392 microdescriptor caching, "fast-start" support for streams, and automatic
9393 home router configuration. There are also numerous internal improvements
9394 to try to make the code easier for developers to work with.
9396 This is the first alpha release in a new series, so expect there to be
9397 bugs. Users who would rather test out a more stable branch should
9398 stay with 0.2.2.x for now.
9401 - Tor can now optionally build with the "bufferevents" buffered IO
9402 backend provided by Libevent 2. To use this feature, make sure you
9403 have the latest possible version of Libevent, and pass the
9404 --enable-bufferevents flag to configure when building Tor from
9405 source. This feature will make our networking code more flexible,
9406 let us stack layers on each other, and let us use more efficient
9407 zero-copy transports where available.
9408 - As an experimental feature, Tor can use IOCP for networking on Windows.
9409 Once this code is tuned and optimized, it promises much better
9410 performance than the select-based backend we've used in the past. To
9411 try this feature, you must build Tor with Libevent 2, configure Tor
9412 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9413 your torrc. There are known bugs here: only try this if you can help
9414 debug it as it breaks.
9415 - The EntryNodes option can now include country codes like {de} or IP
9416 addresses or network masks. Previously we had disallowed these options
9417 because we didn't have an efficient way to keep the list up to
9418 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9419 - Exit nodes now accept and queue data on not-yet-connected streams.
9420 Previously, the client wasn't allowed to send data until the stream was
9421 connected, which slowed down all connections. This change will enable
9422 clients to perform a "fast-start" on streams and send data without
9423 having to wait for a confirmation that the stream has opened. (Patch
9424 from Ian Goldberg; implements the server side of Proposal 174.)
9425 - Tor now has initial support for automatic port mapping on the many
9426 home routers that support NAT-PMP or UPnP. (Not yet supported on
9427 Windows). To build the support code, you'll need to have libnatpnp
9428 library and/or the libminiupnpc library, and you'll need to enable the
9429 feature specifically by passing "--enable-upnp" and/or
9430 "--enable-natpnp" to configure. To turn it on, use the new
9431 PortForwarding option.
9432 - Caches now download, cache, and serve multiple "flavors" of the
9433 consensus, including a flavor that describes microdescriptors.
9434 - Caches now download, cache, and serve microdescriptors -- small
9435 summaries of router descriptors that are authenticated by all of the
9436 directory authorities. Once enough caches are running this code,
9437 clients will be able to save significant amounts of directory bandwidth
9438 by downloading microdescriptors instead of router descriptors.
9441 - Make logging resolution configurable with a new LogTimeGranularity
9442 option, and change the default from 1 millisecond to 1 second.
9443 Implements enhancement 1668.
9444 - We log which torrc file we're using on startup. Implements ticket
9446 - Ordinarily, Tor does not count traffic from private addresses (like
9447 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
9448 There is now a new option, CountPrivateBandwidth, to disable this
9449 behavior. Patch from Daniel Cagara.
9450 - New --enable-static-tor configure option for building Tor as
9451 statically as possible. Idea, general hackery and thoughts from
9452 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
9454 - If you set the NumCPUs option to 0, Tor will now try to detect how
9455 many CPUs you have. This is the new default behavior.
9456 - Turn on directory request statistics by default and include them in
9457 extra-info descriptors. Don't break if we have no GeoIP database.
9458 - Relays that set "ConnDirectionStatistics 1" write statistics on the
9459 bidirectional use of connections to disk every 24 hours.
9460 - Add a GeoIP file digest to the extra-info descriptor. Implements
9462 - The NodeFamily option -- which let you declare that you want to
9463 consider nodes to be part of a family whether they list themselves
9464 that way or not -- now allows IP address ranges and country codes.
9465 - Add a new 'Heartbeat' log message type to periodically log a message
9466 describing Tor's status at level Notice. This feature is meant for
9467 operators who log at notice, and want to make sure that their Tor
9468 server is still working. Implementation by George Kadianakis.
9470 o Minor bugfixes (on 0.2.2.25-alpha):
9471 - When loading the microdesc journal, remember its current size.
9472 In 0.2.2, this helps prevent the microdesc journal from growing
9473 without limit on authorities (who are the only ones to use it in
9474 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9475 Fix posted by "cypherpunks."
9476 - The microdesc journal is supposed to get rebuilt only if it is
9477 at least _half_ the length of the store, not _twice_ the length
9478 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9479 - If as an authority we fail to compute the identity digest of a v3
9480 legacy keypair, warn, and don't use a buffer-full of junk instead.
9481 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
9482 - Authorities now clean their microdesc cache periodically and when
9483 reading from disk initially, not only when adding new descriptors.
9484 This prevents a bug where we could lose microdescriptors. Bugfix
9487 o Minor features (controller):
9488 - Add a new SIGNAL event to the controller interface so that
9489 controllers can be notified when Tor handles a signal. Resolves
9490 issue 1955. Patch by John Brooks.
9491 - Add a new GETINFO option to get total bytes read and written. Patch
9492 from pipe, revised by atagar. Resolves ticket 2345.
9493 - Implement some GETINFO controller fields to provide information about
9494 the Tor process's pid, euid, username, and resource limits.
9497 - Our build system requires automake 1.6 or later to create the
9498 Makefile.in files. Previously, you could have used 1.4.
9499 This only affects developers and people building Tor from git;
9500 people who build Tor from the source distribution without changing
9501 the Makefile.am files should be fine.
9502 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
9503 so on. This is more robust against some of the failure modes
9504 associated with running the autotools pieces on their own.
9506 o Minor packaging issues:
9507 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
9508 already created. Patch from Andreas Stieger. Fixes bug 2573.
9510 o Code simplifications and refactoring:
9511 - A major revision to our internal node-selecting and listing logic.
9512 Tor already had at least two major ways to look at the question of
9513 "which Tor servers do we know about": a list of router descriptors,
9514 and a list of entries in the current consensus. With
9515 microdescriptors, we're adding a third. Having so many systems
9516 without an abstraction layer over them was hurting the codebase.
9517 Now, we have a new "node_t" abstraction that presents a consistent
9518 interface to a client's view of a Tor node, and holds (nearly) all
9519 of the mutable state formerly in routerinfo_t and routerstatus_t.
9520 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
9521 no longer link against Libevent: they never used it, but
9522 our library structure used to force them to link it.
9525 - Remove some old code to work around even older versions of Tor that
9526 used forked processes to handle DNS requests. Such versions of Tor
9527 are no longer in use as servers.
9529 o Documentation fixes:
9530 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
9531 - Add missing documentation for the authority-related torrc options
9532 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
9536 Changes in version 0.2.2.25-alpha - 2011-04-29
9537 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
9538 robust, routers no longer overreport their bandwidth, Win7 should crash
9539 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
9540 now prevents hidden service-related activity from being linkable. It
9541 provides more information to Vidalia so you can see if your bridge is
9542 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
9543 StrictNodes configuration options to make them more reliable, more
9544 understandable, and more regularly applied. If you use those options,
9545 please see the revised documentation for them in the manual page.
9548 - Relays were publishing grossly inflated bandwidth values because
9549 they were writing their state files wrong--now they write the
9550 correct value. Also, resume reading bandwidth history from the
9551 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
9552 - Improve hidden service robustness: When we find that we have
9553 extended a hidden service's introduction circuit to a relay not
9554 listed as an introduction point in the HS descriptor we currently
9555 have, retry with an introduction point from the current
9556 descriptor. Previously we would just give up. Fixes bugs 1024 and
9557 1930; bugfix on 0.2.0.10-alpha.
9558 - Clients now stop trying to use an exit node associated with a given
9559 destination by TrackHostExits if they fail to reach that exit node.
9560 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
9561 - Fix crash bug on platforms where gmtime and localtime can return
9562 NULL. Windows 7 users were running into this one. Fixes part of bug
9563 2077. Bugfix on all versions of Tor. Found by boboper.
9565 o Security and stability fixes:
9566 - Don't double-free a parsable, but invalid, microdescriptor, even if
9567 it is followed in the blob we're parsing by an unparsable
9568 microdescriptor. Fixes an issue reported in a comment on bug 2954.
9569 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
9570 - If the Nickname configuration option isn't given, Tor would pick a
9571 nickname based on the local hostname as the nickname for a relay.
9572 Because nicknames are not very important in today's Tor and the
9573 "Unnamed" nickname has been implemented, this is now problematic
9574 behavior: It leaks information about the hostname without being
9575 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9576 introduced the Unnamed nickname. Reported by tagnaq.
9577 - Fix an uncommon assertion failure when running with DNSPort under
9578 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9579 - Avoid linkability based on cached hidden service descriptors: forget
9580 all hidden service descriptors cached as a client when processing a
9581 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9584 - Export GeoIP information on bridge usage to controllers even if we
9585 have not yet been running for 24 hours. Now Vidalia bridge operators
9586 can get more accurate and immediate feedback about their
9587 contributions to the network.
9589 o Major features and bugfixes (node selection):
9590 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9591 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
9592 options. Previously, we had been ambiguous in describing what
9593 counted as an "exit" node, and what operations exactly "StrictNodes
9594 0" would permit. This created confusion when people saw nodes built
9595 through unexpected circuits, and made it hard to tell real bugs from
9596 surprises. Now the intended behavior is:
9597 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9598 a node that delivers user traffic outside the Tor network.
9599 . "Entry", in the context of EntryNodes, means a node used as the
9600 first hop of a multihop circuit. It doesn't include direct
9601 connections to directory servers.
9602 . "ExcludeNodes" applies to all nodes.
9603 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9604 StrictNodes is set, Tor should avoid all nodes listed in
9605 ExcludeNodes, even when it will make user requests fail. When
9606 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9607 whenever it can, except when it must use an excluded node to
9608 perform self-tests, connect to a hidden service, provide a
9609 hidden service, fulfill a .exit request, upload directory
9610 information, or fetch directory information.
9611 Collectively, the changes to implement the behavior fix bug 1090.
9612 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9613 a node is listed in both, it's treated as excluded.
9614 - ExcludeNodes now applies to directory nodes -- as a preference if
9615 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9616 Don't exclude all the directory authorities and set StrictNodes to 1
9617 unless you really want your Tor to break.
9618 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9619 - ExcludeExitNodes now overrides .exit requests.
9620 - We don't use bridges listed in ExcludeNodes.
9621 - When StrictNodes is 1:
9622 . We now apply ExcludeNodes to hidden service introduction points
9623 and to rendezvous points selected by hidden service users. This
9624 can make your hidden service less reliable: use it with caution!
9625 . If we have used ExcludeNodes on ourself, do not try relay
9626 reachability self-tests.
9627 . If we have excluded all the directory authorities, we will not
9628 even try to upload our descriptor if we're a relay.
9629 . Do not honor .exit requests to an excluded node.
9630 - Remove a misfeature that caused us to ignore the Fast/Stable flags
9631 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
9632 - When the set of permitted nodes changes, we now remove any mappings
9633 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9635 - We never cannibalize a circuit that had excluded nodes on it, even
9636 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9637 - Revert a change where we would be laxer about attaching streams to
9638 circuits than when building the circuits. This was meant to prevent
9639 a set of bugs where streams were never attachable, but our improved
9640 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
9641 - Keep track of how many times we launch a new circuit to handle a
9642 given stream. Too many launches could indicate an inconsistency
9643 between our "launch a circuit to handle this stream" logic and our
9644 "attach this stream to one of the available circuits" logic.
9645 - Improve log messages related to excluded nodes.
9648 - Fix a spurious warning when moving from a short month to a long
9649 month on relays with month-based BandwidthAccounting. Bugfix on
9650 0.2.2.17-alpha; fixes bug 3020.
9651 - When a client finds that an origin circuit has run out of 16-bit
9652 stream IDs, we now mark it as unusable for new streams. Previously,
9653 we would try to close the entire circuit. Bugfix on 0.0.6.
9654 - Add a forgotten cast that caused a compile warning on OS X 10.6.
9655 Bugfix on 0.2.2.24-alpha.
9656 - Be more careful about reporting the correct error from a failed
9657 connect() system call. Under some circumstances, it was possible to
9658 look at an incorrect value for errno when sending the end reason.
9659 Bugfix on 0.1.0.1-rc.
9660 - Correctly handle an "impossible" overflow cases in connection byte
9661 counting, where we write or read more than 4GB on an edge connection
9662 in a single second. Bugfix on 0.1.2.8-beta.
9663 - Correct the warning displayed when a rendezvous descriptor exceeds
9664 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9666 - Clients and hidden services now use HSDir-flagged relays for hidden
9667 service descriptor downloads and uploads even if the relays have no
9668 DirPort set and the client has disabled TunnelDirConns. This will
9669 eventually allow us to give the HSDir flag to relays with no
9670 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
9671 - Downgrade "no current certificates known for authority" message from
9672 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9673 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
9674 2917. Bugfix on 0.1.1.1-alpha.
9675 - Only limit the lengths of single HS descriptors, even when multiple
9676 HS descriptors are published to an HSDir relay in a single POST
9677 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
9678 - Write the current time into the LastWritten line in our state file,
9679 rather than the time from the previous write attempt. Also, stop
9680 trying to use a time of -1 in our log statements. Fixes bug 3039;
9681 bugfix on 0.2.2.14-alpha.
9682 - Be more consistent in our treatment of file system paths. "~" should
9683 get expanded to the user's home directory in the Log config option.
9684 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
9685 feature for the -f and --DataDirectory options.
9688 - Make sure every relay writes a state file at least every 12 hours.
9689 Previously, a relay could go for weeks without writing its state
9690 file, and on a crash could lose its bandwidth history, capacity
9691 estimates, client country statistics, and so on. Addresses bug 3012.
9692 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
9693 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
9694 clients are already deprecated because of security bugs.
9695 - Don't allow v0 hidden service authorities to act as clients.
9696 Required by fix for bug 3000.
9697 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
9698 by fix for bug 3000.
9699 - Ensure that no empty [dirreq-](read|write)-history lines are added
9700 to an extrainfo document. Implements ticket 2497.
9702 o Code simplification and refactoring:
9703 - Remove workaround code to handle directory responses from servers
9704 that had bug 539 (they would send HTTP status 503 responses _and_
9705 send a body too). Since only server versions before
9706 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9707 keep the workaround in place.
9708 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9709 handling calculations where we have a known amount of clock skew and
9710 an allowed amount of unknown skew. But we only used it in three
9711 places, and we never adjusted the known/unknown skew values. This is
9712 still something we might want to do someday, but if we do, we'll
9713 want to do it differently.
9714 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9715 None of the cases where we did this before were wrong, but by making
9716 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9717 - Use GetTempDir to find the proper temporary directory location on
9718 Windows when generating temporary files for the unit tests. Patch by
9722 Changes in version 0.2.2.24-alpha - 2011-04-08
9723 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
9724 prevented Tor clients from effectively using "multihomed" bridges,
9725 that is, bridges that listen on multiple ports or IP addresses so users
9726 can continue to use some of their addresses even if others get blocked.
9729 - Fix a bug where bridge users who configure the non-canonical
9730 address of a bridge automatically switch to its canonical
9731 address. If a bridge listens at more than one address, it should be
9732 able to advertise those addresses independently and any non-blocked
9733 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
9735 - If you configured Tor to use bridge A, and then quit and
9736 configured Tor to use bridge B instead, it would happily continue
9737 to use bridge A if it's still reachable. While this behavior is
9738 a feature if your goal is connectivity, in some scenarios it's a
9739 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
9740 - Directory authorities now use data collected from their own
9741 uptime observations when choosing whether to assign the HSDir flag
9742 to relays, instead of trusting the uptime value the relay reports in
9743 its descriptor. This change helps prevent an attack where a small
9744 set of nodes with frequently-changing identity keys can blackhole
9745 a hidden service. (Only authorities need upgrade; others will be
9746 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
9749 - When we restart our relay, we might get a successful connection
9750 from the outside before we've started our reachability tests,
9751 triggering a warning: "ORPort found reachable, but I have no
9752 routerinfo yet. Failing to inform controller of success." This
9753 bug was harmless unless Tor is running under a controller
9754 like Vidalia, in which case the controller would never get a
9755 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9757 - Make directory authorities more accurate at recording when
9758 relays that have failed several reachability tests became
9759 unreachable, so we can provide more accuracy at assigning Stable,
9760 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
9761 - Fix an issue that prevented static linking of libevent on
9762 some platforms (notably Linux). Fixes bug 2698; bugfix on
9763 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
9764 the --with-static-libevent configure option).
9765 - We now ask the other side of a stream (the client or the exit)
9766 for more data on that stream when the amount of queued data on
9767 that stream dips low enough. Previously, we wouldn't ask the
9768 other side for more data until either it sent us more data (which
9769 it wasn't supposed to do if it had exhausted its window!) or we
9770 had completely flushed all our queued data. This flow control fix
9771 should improve throughput. Fixes bug 2756; bugfix on the earliest
9772 released versions of Tor (svn commit r152).
9773 - Avoid a double-mark-for-free warning when failing to attach a
9774 transparent proxy connection. (We thought we had fixed this in
9775 0.2.2.23-alpha, but it turns out our fix was checking the wrong
9776 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
9777 bug) and 0.2.2.23-alpha (the incorrect fix).
9778 - When warning about missing zlib development packages during compile,
9779 give the correct package names. Bugfix on 0.2.0.1-alpha.
9782 - Directory authorities now log the source of a rejected POSTed v3
9784 - Make compilation with clang possible when using
9785 --enable-gcc-warnings by removing two warning options that clang
9786 hasn't implemented yet and by fixing a few warnings. Implements
9788 - When expiring circuits, use microsecond timers rather than
9789 one-second timers. This can avoid an unpleasant situation where a
9790 circuit is launched near the end of one second and expired right
9791 near the beginning of the next, and prevent fluctuations in circuit
9793 - Use computed circuit-build timeouts to decide when to launch
9794 parallel introduction circuits for hidden services. (Previously,
9795 we would retry after 15 seconds.)
9796 - Update to the April 1 2011 Maxmind GeoLite Country database.
9799 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9800 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9802 o Documentation changes:
9803 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9804 - Resolve all doxygen warnings except those for missing documentation.
9806 - Add doxygen documentation for more functions, fields, and types.
9809 Changes in version 0.2.2.23-alpha - 2011-03-08
9810 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
9811 they restart they don't lose their bandwidth capacity estimate. This
9812 release also fixes a diverse set of user-facing bugs, ranging from
9813 relays overrunning their rate limiting to clients falsely warning about
9814 clock skew to bridge descriptor leaks by our bridge directory authority.
9817 - Stop sending a CLOCK_SKEW controller status event whenever
9818 we fetch directory information from a relay that has a wrong clock.
9819 Instead, only inform the controller when it's a trusted authority
9820 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9821 the rest of bug 1074.
9822 - Fix an assert in parsing router descriptors containing IPv6
9823 addresses. This one took down the directory authorities when
9824 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9825 - Make the bridge directory authority refuse to answer directory
9826 requests for "all" descriptors. It used to include bridge
9827 descriptors in its answer, which was a major information leak.
9828 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9829 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9830 Tor would ignore their RelayBandwidthBurst setting,
9831 potentially using more bandwidth than expected. Bugfix on
9832 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9833 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9834 hidserv" in her torrc. The 'hidserv' argument never controlled
9835 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9838 - Relays now save observed peak bandwidth throughput rates to their
9839 state file (along with total usage, which was already saved)
9840 so that they can determine their correct estimated bandwidth on
9841 restart. Resolves bug 1863, where Tor relays would reset their
9842 estimated bandwidth to 0 after restarting.
9843 - Directory authorities now take changes in router IP address and
9844 ORPort into account when determining router stability. Previously,
9845 if a router changed its IP or ORPort, the authorities would not
9846 treat it as having any downtime for the purposes of stability
9847 calculation, whereas clients would experience downtime since the
9848 change could take a while to propagate to them. Resolves issue 1035.
9849 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9850 Prevention (DEP) by default on Windows to make it harder for
9851 attackers to exploit vulnerabilities. Patch from John Brooks.
9853 o Minor bugfixes (on 0.2.1.x and earlier):
9854 - Fix a rare crash bug that could occur when a client was configured
9855 with a large number of bridges. Fixes bug 2629; bugfix on
9856 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9857 - Avoid a double mark-for-free warning when failing to attach a
9858 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9860 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9861 found by "cypherpunks". This bug was introduced before the first
9862 Tor release, in svn commit r110.
9863 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
9864 don't mention them in the manpage. Fixes bug 2450; issue
9865 spotted by keb and G-Lo.
9866 - Fix a bug in bandwidth history state parsing that could have been
9867 triggered if a future version of Tor ever changed the timing
9868 granularity at which bandwidth history is measured. Bugfix on
9870 - When a relay decides that its DNS is too broken for it to serve
9871 as an exit server, it advertised itself as a non-exit, but
9872 continued to act as an exit. This could create accidental
9873 partitioning opportunities for users. Instead, if a relay is
9874 going to advertise reject *:* as its exit policy, it should
9875 really act with exit policy "reject *:*". Fixes bug 2366.
9876 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9877 - In the special case where you configure a public exit relay as your
9878 bridge, Tor would be willing to use that exit relay as the last
9879 hop in your circuit as well. Now we fail that circuit instead.
9880 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9881 - Fix a bug with our locking implementation on Windows that couldn't
9882 correctly detect when a file was already locked. Fixes bug 2504,
9883 bugfix on 0.2.1.6-alpha.
9884 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9885 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9887 - Set target port in get_interface_address6() correctly. Bugfix
9888 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9889 - Directory authorities are now more robust to hops back in time
9890 when calculating router stability. Previously, if a run of uptime
9891 or downtime appeared to be negative, the calculation could give
9892 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9894 - Fix an assert that got triggered when using the TestingTorNetwork
9895 configuration option and then issuing a GETINFO config-text control
9896 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9898 o Minor bugfixes (on 0.2.2.x):
9899 - Clients should not weight BadExit nodes as Exits in their node
9900 selection. Similarly, directory authorities should not count BadExit
9901 bandwidth as Exit bandwidth when computing bandwidth-weights.
9902 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
9903 - Correctly clear our dir_read/dir_write history when there is an
9904 error parsing any bw history value from the state file. Bugfix on
9906 - Resolve a bug in verifying signatures of directory objects
9907 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
9908 Fixes bug 2409. Found by "piebeer".
9909 - Bridge authorities no longer crash on SIGHUP when they try to
9910 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
9914 - Log less aggressively about circuit timeout changes, and improve
9915 some other circuit timeout messages. Resolves bug 2004.
9916 - Log a little more clearly about the times at which we're no longer
9917 accepting new connections. Resolves bug 2181.
9918 - Reject attempts at the client side to open connections to private
9919 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9920 a randomly chosen exit node. Attempts to do so are always
9921 ill-defined, generally prevented by exit policies, and usually
9922 in error. This will also help to detect loops in transparent
9923 proxy configurations. You can disable this feature by setting
9924 "ClientRejectInternalAddresses 0" in your torrc.
9925 - Always treat failure to allocate an RSA key as an unrecoverable
9927 - Update to the March 1 2011 Maxmind GeoLite Country database.
9929 o Minor features (log subsystem):
9930 - Add documentation for configuring logging at different severities in
9931 different log domains. We've had this feature since 0.2.1.1-alpha,
9932 but for some reason it never made it into the manpage. Fixes
9934 - Make it simpler to specify "All log domains except for A and B".
9935 Previously you needed to say "[*,~A,~B]". Now you can just say
9937 - Add a "LogMessageDomains 1" option to include the domains of log
9938 messages along with the messages. Without this, there's no way
9939 to use log domains without reading the source or doing a lot
9942 o Packaging changes:
9943 - Stop shipping the Tor specs files and development proposal documents
9944 in the tarball. They are now in a separate git repository at
9945 git://git.torproject.org/torspec.git
9948 Changes in version 0.2.1.30 - 2011-02-23
9949 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9950 change is a slight tweak to Tor's TLS handshake that makes relays
9951 and bridges that run this new version reachable from Iran again.
9952 We don't expect this tweak will win the arms race long-term, but it
9953 buys us time until we roll out a better solution.
9956 - Stop sending a CLOCK_SKEW controller status event whenever
9957 we fetch directory information from a relay that has a wrong clock.
9958 Instead, only inform the controller when it's a trusted authority
9959 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9960 the rest of bug 1074.
9961 - Fix a bounds-checking error that could allow an attacker to
9962 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9964 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9965 Tor would ignore their RelayBandwidthBurst setting,
9966 potentially using more bandwidth than expected. Bugfix on
9967 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9968 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9969 hidserv" in her torrc. The 'hidserv' argument never controlled
9970 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9973 - Adjust our TLS Diffie-Hellman parameters to match those used by
9975 - Update to the February 1 2011 Maxmind GeoLite Country database.
9978 - Check for and reject overly long directory certificates and
9979 directory tokens before they have a chance to hit any assertions.
9980 Bugfix on 0.2.1.28. Found by "doorss".
9981 - Bring the logic that gathers routerinfos and assesses the
9982 acceptability of circuits into line. This prevents a Tor OP from
9983 getting locked in a cycle of choosing its local OR as an exit for a
9984 path (due to a .exit request) and then rejecting the circuit because
9985 its OR is not listed yet. It also prevents Tor clients from using an
9986 OR running in the same instance as an exit (due to a .exit request)
9987 if the OR does not meet the same requirements expected of an OR
9988 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9990 o Packaging changes:
9991 - Stop shipping the Tor specs files and development proposal documents
9992 in the tarball. They are now in a separate git repository at
9993 git://git.torproject.org/torspec.git
9994 - Do not include Git version tags as though they are SVN tags when
9995 generating a tarball from inside a repository that has switched
9996 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9999 Changes in version 0.2.2.22-alpha - 2011-01-25
10000 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
10001 main other change is a slight tweak to Tor's TLS handshake that makes
10002 relays and bridges that run this new version reachable from Iran again.
10003 We don't expect this tweak will win the arms race long-term, but it
10004 will buy us a bit more time until we roll out a better solution.
10007 - Fix a bounds-checking error that could allow an attacker to
10008 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10009 Found by "piebeer".
10010 - Don't assert when changing from bridge to relay or vice versa
10011 via the controller. The assert happened because we didn't properly
10012 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
10013 bug 2433. Reported by bastik.
10016 - Adjust our TLS Diffie-Hellman parameters to match those used by
10018 - Provide a log message stating which geoip file we're parsing
10019 instead of just stating that we're parsing the geoip file.
10020 Implements ticket 2432.
10023 - Check for and reject overly long directory certificates and
10024 directory tokens before they have a chance to hit any assertions.
10025 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
10028 Changes in version 0.2.2.21-alpha - 2011-01-15
10029 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
10030 continues our recent code security audit work. The main fix resolves
10031 a remote heap overflow vulnerability that can allow remote code
10032 execution (CVE-2011-0427). Other fixes address a variety of assert
10033 and crash bugs, most of which we think are hard to exploit remotely.
10035 o Major bugfixes (security), also included in 0.2.1.29:
10036 - Fix a heap overflow bug where an adversary could cause heap
10037 corruption. This bug probably allows remote code execution
10038 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10040 - Prevent a denial-of-service attack by disallowing any
10041 zlib-compressed data whose compression factor is implausibly
10042 high. Fixes part of bug 2324; reported by "doorss".
10043 - Zero out a few more keys in memory before freeing them. Fixes
10044 bug 2384 and part of bug 2385. These key instances found by
10045 "cypherpunks", based on Andrew Case's report about being able
10046 to find sensitive data in Tor's memory space if you have enough
10047 permissions. Bugfix on 0.0.2pre9.
10049 o Major bugfixes (crashes), also included in 0.2.1.29:
10050 - Prevent calls to Libevent from inside Libevent log handlers.
10051 This had potential to cause a nasty set of crashes, especially
10052 if running Libevent with debug logging enabled, and running
10053 Tor with a controller watching for low-severity log messages.
10054 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10055 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10056 underflow errors there too. Fixes the other part of bug 2324.
10057 - Fix a bug where we would assert if we ever had a
10058 cached-descriptors.new file (or another file read directly into
10059 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10060 on 0.2.1.25. Found by doorss.
10061 - Fix some potential asserts and parsing issues with grossly
10062 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10065 o Minor bugfixes (other), also included in 0.2.1.29:
10066 - Fix a bug with handling misformed replies to reverse DNS lookup
10067 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10068 bug reported by doorss.
10069 - Fix compilation on mingw when a pthreads compatibility library
10070 has been installed. (We don't want to use it, so we shouldn't
10071 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10072 - Fix a bug where we would declare that we had run out of virtual
10073 addresses when the address space was only half-exhausted. Bugfix
10075 - Correctly handle the case where AutomapHostsOnResolve is set but
10076 no virtual addresses are available. Fixes bug 2328; bugfix on
10077 0.1.2.1-alpha. Bug found by doorss.
10078 - Correctly handle wrapping around when we run out of virtual
10079 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
10081 o Minor features, also included in 0.2.1.29:
10082 - Update to the January 1 2011 Maxmind GeoLite Country database.
10083 - Introduce output size checks on all of our decryption functions.
10085 o Build changes, also included in 0.2.1.29:
10086 - Tor does not build packages correctly with Automake 1.6 and earlier;
10087 added a check to Makefile.am to make sure that we're building with
10088 Automake 1.7 or later.
10089 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10090 because we built it with a too-old version of automake. Thus that
10091 release broke ./configure --enable-openbsd-malloc, which is popular
10092 among really fast exit relays on Linux.
10094 o Major bugfixes, new in 0.2.2.21-alpha:
10095 - Prevent crash/heap corruption when the cbtnummodes consensus
10096 parameter is set to 0 or large values. Fixes bug 2317; bugfix
10099 o Major features, new in 0.2.2.21-alpha:
10100 - Introduce minimum/maximum values that clients will believe
10101 from the consensus. Now we'll have a better chance to avoid crashes
10102 or worse when a consensus param has a weird value.
10104 o Minor features, new in 0.2.2.21-alpha:
10105 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
10106 used on bridges, and it makes bridge scanning somewhat easier.
10107 - If writing the state file to disk fails, wait up to an hour before
10108 retrying again, rather than trying again each second. Fixes bug
10109 2346; bugfix on Tor 0.1.1.3-alpha.
10110 - Make Libevent log messages get delivered to controllers later,
10111 and not from inside the Libevent log handler. This prevents unsafe
10112 reentrant Libevent calls while still letting the log messages
10114 - Detect platforms that brokenly use a signed size_t, and refuse to
10115 build there. Found and analyzed by doorss and rransom.
10116 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
10119 o Minor bugfixes, new in 0.2.2.21-alpha:
10120 - Handle SOCKS messages longer than 128 bytes long correctly, rather
10121 than waiting forever for them to finish. Fixes bug 2330; bugfix
10122 on 0.2.0.16-alpha. Found by doorss.
10123 - Add assertions to check for overflow in arguments to
10124 base32_encode() and base32_decode(); fix a signed-unsigned
10125 comparison there too. These bugs are not actually reachable in Tor,
10126 but it's good to prevent future errors too. Found by doorss.
10127 - Correctly detect failures to create DNS requests when using Libevent
10128 versions before v2. (Before Libevent 2, we used our own evdns
10129 implementation. Its return values for Libevent's evdns_resolve_*()
10130 functions are not consistent with those from Libevent.) Fixes bug
10131 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
10133 o Documentation, new in 0.2.2.21-alpha:
10134 - Document the default socks host and port (127.0.0.1:9050) for
10138 Changes in version 0.2.1.29 - 2011-01-15
10139 Tor 0.2.1.29 continues our recent code security audit work. The main
10140 fix resolves a remote heap overflow vulnerability that can allow remote
10141 code execution. Other fixes address a variety of assert and crash bugs,
10142 most of which we think are hard to exploit remotely.
10144 o Major bugfixes (security):
10145 - Fix a heap overflow bug where an adversary could cause heap
10146 corruption. This bug probably allows remote code execution
10147 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10149 - Prevent a denial-of-service attack by disallowing any
10150 zlib-compressed data whose compression factor is implausibly
10151 high. Fixes part of bug 2324; reported by "doorss".
10152 - Zero out a few more keys in memory before freeing them. Fixes
10153 bug 2384 and part of bug 2385. These key instances found by
10154 "cypherpunks", based on Andrew Case's report about being able
10155 to find sensitive data in Tor's memory space if you have enough
10156 permissions. Bugfix on 0.0.2pre9.
10158 o Major bugfixes (crashes):
10159 - Prevent calls to Libevent from inside Libevent log handlers.
10160 This had potential to cause a nasty set of crashes, especially
10161 if running Libevent with debug logging enabled, and running
10162 Tor with a controller watching for low-severity log messages.
10163 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10164 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10165 underflow errors there too. Fixes the other part of bug 2324.
10166 - Fix a bug where we would assert if we ever had a
10167 cached-descriptors.new file (or another file read directly into
10168 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10169 on 0.2.1.25. Found by doorss.
10170 - Fix some potential asserts and parsing issues with grossly
10171 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10174 o Minor bugfixes (other):
10175 - Fix a bug with handling misformed replies to reverse DNS lookup
10176 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10177 bug reported by doorss.
10178 - Fix compilation on mingw when a pthreads compatibility library
10179 has been installed. (We don't want to use it, so we shouldn't
10180 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10181 - Fix a bug where we would declare that we had run out of virtual
10182 addresses when the address space was only half-exhausted. Bugfix
10184 - Correctly handle the case where AutomapHostsOnResolve is set but
10185 no virtual addresses are available. Fixes bug 2328; bugfix on
10186 0.1.2.1-alpha. Bug found by doorss.
10187 - Correctly handle wrapping around to when we run out of virtual
10188 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
10189 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10190 because we built it with a too-old version of automake. Thus that
10191 release broke ./configure --enable-openbsd-malloc, which is popular
10192 among really fast exit relays on Linux.
10195 - Update to the January 1 2011 Maxmind GeoLite Country database.
10196 - Introduce output size checks on all of our decryption functions.
10199 - Tor does not build packages correctly with Automake 1.6 and earlier;
10200 added a check to Makefile.am to make sure that we're building with
10201 Automake 1.7 or later.
10204 Changes in version 0.2.2.20-alpha - 2010-12-17
10205 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
10206 exploitable bugs. We also fix a variety of other significant bugs,
10207 change the IP address for one of our directory authorities, and update
10208 the minimum version that Tor relays must run to join the network.
10211 - Fix a remotely exploitable bug that could be used to crash instances
10212 of Tor remotely by overflowing on the heap. Remote-code execution
10213 hasn't been confirmed, but can't be ruled out. Everyone should
10214 upgrade. Bugfix on the 0.1.1 series and later.
10215 - Fix a bug that could break accounting on 64-bit systems with large
10216 time_t values, making them hibernate for impossibly long intervals.
10217 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
10218 - Fix a logic error in directory_fetches_from_authorities() that
10219 would cause all _non_-exits refusing single-hop-like circuits
10220 to fetch from authorities, when we wanted to have _exits_ fetch
10221 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
10223 - Fix a stream fairness bug that would cause newer streams on a given
10224 circuit to get preference when reading bytes from the origin or
10225 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
10226 introduced before the first Tor release, in svn revision r152.
10228 o Directory authority changes:
10229 - Change IP address and ports for gabelmoo (v3 directory authority).
10232 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
10233 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
10234 - Fix an off-by-one error in calculating some controller command
10235 argument lengths. Fortunately, this mistake is harmless since
10236 the controller code does redundant NUL termination too. Found by
10237 boboper. Bugfix on 0.1.1.1-alpha.
10238 - Do not dereference NULL if a bridge fails to build its
10239 extra-info descriptor. Found by an anonymous commenter on
10240 Trac. Bugfix on 0.2.2.19-alpha.
10243 - Update to the December 1 2010 Maxmind GeoLite Country database.
10244 - Directory authorities now reject relays running any versions of
10245 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
10246 known bugs that keep RELAY_EARLY cells from working on rendezvous
10247 circuits. Followup to fix for bug 2081.
10248 - Directory authorities now reject relays running any version of Tor
10249 older than 0.2.0.26-rc. That version is the earliest that fetches
10250 current directory information correctly. Fixes bug 2156.
10251 - Report only the top 10 ports in exit-port stats in order not to
10252 exceed the maximum extra-info descriptor length of 50 KB. Implements
10256 Changes in version 0.2.1.28 - 2010-12-17
10257 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
10258 exploitable bugs. We also took this opportunity to change the IP address
10259 for one of our directory authorities, and to update the geoip database
10263 - Fix a remotely exploitable bug that could be used to crash instances
10264 of Tor remotely by overflowing on the heap. Remote-code execution
10265 hasn't been confirmed, but can't be ruled out. Everyone should
10266 upgrade. Bugfix on the 0.1.1 series and later.
10268 o Directory authority changes:
10269 - Change IP address and ports for gabelmoo (v3 directory authority).
10272 - Update to the December 1 2010 Maxmind GeoLite Country database.
10275 Changes in version 0.2.1.27 - 2010-11-23
10276 Yet another OpenSSL security patch broke its compatibility with Tor:
10277 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
10278 also took this opportunity to fix several crash bugs, integrate a new
10279 directory authority, and update the bundled GeoIP database.
10282 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10283 No longer set the tlsext_host_name extension on server SSL objects;
10284 but continue to set it on client SSL objects. Our goal in setting
10285 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10286 bugfix on 0.2.1.1-alpha.
10287 - Do not log messages to the controller while shrinking buffer
10288 freelists. Doing so would sometimes make the controller connection
10289 try to allocate a buffer chunk, which would mess up the internals
10290 of the freelist and cause an assertion failure. Fixes bug 1125;
10291 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10292 - Learn our external IP address when we're a relay or bridge, even if
10293 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10294 where we introduced bridge relays that don't need to publish to
10295 be useful. Fixes bug 2050.
10296 - Do even more to reject (and not just ignore) annotations on
10297 router descriptors received anywhere but from the cache. Previously
10298 we would ignore such annotations at first, but cache them to disk
10299 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10300 - When you're using bridges and your network goes away and your
10301 bridges get marked as down, recover when you attempt a new socks
10302 connection (if the network is back), rather than waiting up to an
10303 hour to try fetching new descriptors for your bridges. Bugfix on
10304 0.2.0.3-alpha; fixes bug 1981.
10307 - Move to the November 2010 Maxmind GeoLite country db (rather
10308 than the June 2009 ip-to-country GeoIP db) for our statistics that
10309 count how many users relays are seeing from each country. Now we'll
10310 have more accurate data, especially for many African countries.
10312 o New directory authorities:
10313 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10317 - Fix an assertion failure that could occur in directory caches or
10318 bridge users when using a very short voting interval on a testing
10319 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
10321 - Enforce multiplicity rules when parsing annotations. Bugfix on
10322 0.2.0.8-alpha. Found by piebeer.
10323 - Allow handshaking OR connections to take a full KeepalivePeriod
10324 seconds to handshake. Previously, we would close them after
10325 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10326 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10328 - When building with --enable-gcc-warnings on OpenBSD, disable
10329 warnings in system headers. This makes --enable-gcc-warnings
10330 pass on OpenBSD 4.8.
10333 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10334 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10335 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10336 Servers can start sending this code when enough clients recognize
10337 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
10338 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10339 Patch from mingw-san.
10342 - Remove the old debian/ directory from the main Tor distribution.
10343 The official Tor-for-debian git repository lives at the URL
10344 https://git.torproject.org/debian/tor.git
10345 - Stop shipping the old doc/website/ directory in the tarball. We
10346 changed the website format in late 2010, and what we shipped in
10347 0.2.1.26 really wasn't that useful anyway.
10350 Changes in version 0.2.2.19-alpha - 2010-11-22
10351 Yet another OpenSSL security patch broke its compatibility with Tor:
10352 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
10355 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10356 No longer set the tlsext_host_name extension on server SSL objects;
10357 but continue to set it on client SSL objects. Our goal in setting
10358 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10359 bugfix on 0.2.1.1-alpha.
10362 - Try harder not to exceed the maximum length of 50 KB when writing
10363 statistics to extra-info descriptors. This bug was triggered by very
10364 fast relays reporting exit-port, entry, and dirreq statistics.
10365 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
10366 - Publish a router descriptor even if generating an extra-info
10367 descriptor fails. Previously we would not publish a router
10368 descriptor without an extra-info descriptor; this can cause fast
10369 exit relays collecting exit-port statistics to drop from the
10370 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10373 Changes in version 0.2.2.18-alpha - 2010-11-16
10374 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
10375 us lately, makes unpublished bridge relays able to detect their IP
10376 address, and fixes a wide variety of other bugs to get us much closer
10377 to a stable release.
10380 - Do even more to reject (and not just ignore) annotations on
10381 router descriptors received anywhere but from the cache. Previously
10382 we would ignore such annotations at first, but cache them to disk
10383 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10384 - Do not log messages to the controller while shrinking buffer
10385 freelists. Doing so would sometimes make the controller connection
10386 try to allocate a buffer chunk, which would mess up the internals
10387 of the freelist and cause an assertion failure. Fixes bug 1125;
10388 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10389 - Learn our external IP address when we're a relay or bridge, even if
10390 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10391 where we introduced bridge relays that don't need to publish to
10392 be useful. Fixes bug 2050.
10393 - Maintain separate TLS contexts and certificates for incoming and
10394 outgoing connections in bridge relays. Previously we would use the
10395 same TLS contexts and certs for incoming and outgoing connections.
10396 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10397 - Maintain separate identity keys for incoming and outgoing TLS
10398 contexts in bridge relays. Previously we would use the same
10399 identity keys for incoming and outgoing TLS contexts. Bugfix on
10400 0.2.0.3-alpha; addresses the other half of bug 988.
10401 - Avoid an assertion failure when we as an authority receive a
10402 duplicate upload of a router descriptor that we already have,
10403 but which we previously considered an obsolete descriptor.
10404 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10405 - Avoid a crash bug triggered by looking at a dangling pointer while
10406 setting the network status consensus. Found by Robert Ransom.
10407 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10408 - Fix a logic error where servers that _didn't_ act as exits would
10409 try to keep their server lists more aggressively up to date than
10410 exits, when it was supposed to be the other way around. Bugfix
10413 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10414 - When we're trying to guess whether we know our IP address as
10415 a relay, we would log various ways that we failed to guess
10416 our address, but never log that we ended up guessing it
10417 successfully. Now add a log line to help confused and anxious
10418 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10419 - Bring the logic that gathers routerinfos and assesses the
10420 acceptability of circuits into line. This prevents a Tor OP from
10421 getting locked in a cycle of choosing its local OR as an exit for a
10422 path (due to a .exit request) and then rejecting the circuit because
10423 its OR is not listed yet. It also prevents Tor clients from using an
10424 OR running in the same instance as an exit (due to a .exit request)
10425 if the OR does not meet the same requirements expected of an OR
10426 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10427 - Correctly describe errors that occur when generating a TLS object.
10428 Previously we would attribute them to a failure while generating a
10429 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10431 - Enforce multiplicity rules when parsing annotations. Bugfix on
10432 0.2.0.8-alpha. Found by piebeer.
10433 - Fix warnings that newer versions of autoconf produced during
10434 ./autogen.sh. These warnings appear to be harmless in our case,
10435 but they were extremely verbose. Fixes bug 2020.
10437 o Minor bugfixes (on Tor 0.2.2.x):
10438 - Enable protection of small arrays whenever we build with gcc
10439 hardening features, not only when also building with warnings
10440 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
10443 - Make hidden services work better in private Tor networks by not
10444 requiring any uptime to join the hidden service descriptor
10445 DHT. Implements ticket 2088.
10446 - Rate-limit the "your application is giving Tor only an IP address"
10447 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
10448 - When AllowSingleHopExits is set, print a warning to explain to the
10449 relay operator why most clients are avoiding her relay.
10450 - Update to the November 1 2010 Maxmind GeoLite Country database.
10452 o Code simplifications and refactoring:
10453 - When we fixed bug 1038 we had to put in a restriction not to send
10454 RELAY_EARLY cells on rend circuits. This was necessary as long
10455 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
10456 active. Now remove this obsolete check. Resolves bug 2081.
10457 - Some options used different conventions for uppercasing of acronyms
10458 when comparing manpage and source. Fix those in favor of the
10459 manpage, as it makes sense to capitalize acronyms.
10460 - Remove the torrc.complete file. It hasn't been kept up to date
10461 and users will have better luck checking out the manpage.
10462 - Remove the obsolete "NoPublish" option; it has been flagged
10463 as obsolete and has produced a warning since 0.1.1.18-rc.
10464 - Remove everything related to building the expert bundle for OS X.
10465 It has confused many users, doesn't work right on OS X 10.6,
10466 and is hard to get rid of once installed. Resolves bug 1274.
10469 Changes in version 0.2.2.17-alpha - 2010-09-30
10470 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
10471 to use one-hop circuits (which can put the exit relays at higher risk,
10472 plus unbalance the network); fixes a big bug in bandwidth accounting
10473 for relays that want to limit their monthly bandwidth use; fixes a
10474 big pile of bugs in how clients tolerate temporary network failure;
10475 and makes our adaptive circuit build timeout feature (which improves
10476 client performance if your network is fast while not breaking things
10477 if your network is slow) better handle bad networks.
10480 - Exit relays now try harder to block exit attempts from unknown
10481 relays, to make it harder for people to use them as one-hop proxies
10482 a la tortunnel. Controlled by the refuseunknownexits consensus
10483 parameter (currently enabled), or you can override it on your
10484 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
10486 o Major bugfixes (0.2.1.x and earlier):
10487 - Fix a bug in bandwidth accounting that could make us use twice
10488 the intended bandwidth when our interval start changes due to
10489 daylight saving time. Now we tolerate skew in stored vs computed
10490 interval starts: if the start of the period changes by no more than
10491 50% of the period's duration, we remember bytes that we transferred
10492 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
10493 - Always search the Windows system directory for system DLLs, and
10494 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
10495 - When you're using bridges and your network goes away and your
10496 bridges get marked as down, recover when you attempt a new socks
10497 connection (if the network is back), rather than waiting up to an
10498 hour to try fetching new descriptors for your bridges. Bugfix on
10499 0.2.0.3-alpha; fixes bug 1981.
10501 o Major bugfixes (on 0.2.2.x):
10502 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
10504 - Fix a segfault that could happen when operating a bridge relay with
10505 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
10506 - The consensus bandwidth-weights (used by clients to choose fast
10507 relays) entered an unexpected edge case in September where
10508 Exits were much scarcer than Guards, resulting in bad weight
10509 recommendations. Now we compute them using new constraints that
10510 should succeed in all cases. Also alter directory authorities to
10511 not include the bandwidth-weights line if they fail to produce
10512 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
10513 - When weighting bridges during path selection, we used to trust
10514 the bandwidths they provided in their descriptor, only capping them
10515 at 10MB/s. This turned out to be problematic for two reasons:
10516 Bridges could claim to handle a lot more traffic then they
10517 actually would, thus making more clients pick them and have a
10518 pretty effective DoS attack. The other issue is that new bridges
10519 that might not have a good estimate for their bw capacity yet
10520 would not get used at all unless no other bridges are available
10521 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
10523 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
10524 - Ignore cannibalized circuits when recording circuit build times.
10525 This should provide for a minor performance improvement for hidden
10526 service users using 0.2.2.14-alpha, and should remove two spurious
10527 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
10528 - Simplify the logic that causes us to decide if the network is
10529 unavailable for purposes of recording circuit build times. If we
10530 receive no cells whatsoever for the entire duration of a circuit's
10531 full measured lifetime, the network is probably down. Also ignore
10532 one-hop directory fetching circuit timeouts when calculating our
10533 circuit build times. These changes should hopefully reduce the
10534 cases where we see ridiculous circuit build timeouts for people
10535 with spotty wireless connections. Fixes part of bug 1772; bugfix
10537 - Prevent the circuit build timeout from becoming larger than
10538 the maximum build time we have ever seen. Also, prevent the time
10539 period for measurement circuits from becoming larger than twice that
10540 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
10543 - When we run out of directory information such that we can't build
10544 circuits, but then get enough that we can build circuits, log when
10545 we actually construct a circuit, so the user has a better chance of
10546 knowing what's going on. Fixes bug 1362.
10547 - Be more generous with how much bandwidth we'd use up (with
10548 accounting enabled) before entering "soft hibernation". Previously,
10549 we'd refuse new connections and circuits once we'd used up 95% of
10550 our allotment. Now, we use up 95% of our allotment, AND make sure
10551 that we have no more than 500MB (or 3 hours of expected traffic,
10552 whichever is lower) remaining before we enter soft hibernation.
10553 - If we've configured EntryNodes and our network goes away and/or all
10554 our entrynodes get marked down, optimistically retry them all when
10555 a new socks application request appears. Fixes bug 1882.
10556 - Add some more defensive programming for architectures that can't
10557 handle unaligned integer accesses. We don't know of any actual bugs
10558 right now, but that's the best time to fix them. Fixes bug 1943.
10559 - Support line continuations in the torrc config file. If a line
10560 ends with a single backslash character, the newline is ignored, and
10561 the configuration value is treated as continuing on the next line.
10564 o Minor bugfixes (on 0.2.1.x and earlier):
10565 - For bandwidth accounting, calculate our expected bandwidth rate
10566 based on the time during which we were active and not in
10567 soft-hibernation during the last interval. Previously, we were
10568 also considering the time spent in soft-hibernation. If this
10569 was a long time, we would wind up underestimating our bandwidth
10570 by a lot, and skewing our wakeup time towards the start of the
10571 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10573 o Minor bugfixes (on 0.2.2.x):
10574 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
10575 which were disabled by the circuit build timeout changes in
10576 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
10577 - Make sure we don't warn about missing bandwidth weights when
10578 choosing bridges or other relays not in the consensus. Bugfix on
10579 0.2.2.10-alpha; fixes bug 1805.
10580 - In our logs, do not double-report signatures from unrecognized
10581 authorities both as "from unknown authority" and "not
10582 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
10585 Changes in version 0.2.2.16-alpha - 2010-09-17
10586 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
10587 evident at exit relays), and also continues to resolve all the little
10588 bugs that have been filling up trac lately.
10590 o Major bugfixes (stream-level fairness):
10591 - When receiving a circuit-level SENDME for a blocked circuit, try
10592 to package cells fairly from all the streams that had previously
10593 been blocked on that circuit. Previously, we had started with the
10594 oldest stream, and allowed each stream to potentially exhaust
10595 the circuit's package window. This gave older streams on any
10596 given circuit priority over newer ones. Fixes bug 1937. Detected
10597 originally by Camilo Viecco. This bug was introduced before the
10598 first Tor release, in svn commit r152: it is the new winner of
10599 the longest-lived bug prize.
10600 - When the exit relay got a circuit-level sendme cell, it started
10601 reading on the exit streams, even if had 500 cells queued in the
10602 circuit queue already, so the circuit queue just grew and grew in
10603 some cases. We fix this by not re-enabling reading on receipt of a
10604 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10605 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10607 - Newly created streams were allowed to read cells onto circuits,
10608 even if the circuit's cell queue was blocked and waiting to drain.
10609 This created potential unfairness, as older streams would be
10610 blocked, but newer streams would gladly fill the queue completely.
10611 We add code to detect this situation and prevent any stream from
10612 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10616 - Update to the September 1 2010 Maxmind GeoLite Country database.
10617 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10618 not. This would lead to a cookie that is still not group readable.
10619 Closes bug 1843. Suggested by katmagic.
10620 - When logging a rate-limited warning, we now mention how many messages
10621 got suppressed since the last warning.
10622 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10623 do individual connection-level rate limiting of clients. The torrc
10624 config options with the same names trump the consensus params, if
10625 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10626 consensus params which were broken from 0.2.2.7-alpha through
10627 0.2.2.14-alpha. Closes bug 1947.
10628 - When a router changes IP address or port, authorities now launch
10629 a new reachability test for it. Implements ticket 1899.
10630 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10631 2 no signature, 4 required" messages about consensus signatures
10632 easier to read, and make sure they get logged at the same severity
10633 as the messages explaining which keys are which. Fixes bug 1290.
10634 - Don't warn when we have a consensus that we can't verify because
10635 of missing certificates, unless those certificates are ones
10636 that we have been trying and failing to download. Fixes bug 1145.
10637 - If you configure your bridge with a known identity fingerprint,
10638 and the bridge authority is unreachable (as it is in at least
10639 one country now), fall back to directly requesting the descriptor
10640 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
10642 - When building with --enable-gcc-warnings on OpenBSD, disable
10643 warnings in system headers. This makes --enable-gcc-warnings
10644 pass on OpenBSD 4.8.
10646 o Minor bugfixes (on 0.2.1.x and earlier):
10647 - Authorities will now attempt to download consensuses if their
10648 own efforts to make a live consensus have failed. This change
10649 means authorities that restart will fetch a valid consensus, and
10650 it means authorities that didn't agree with the current consensus
10651 will still fetch and serve it if it has enough signatures. Bugfix
10652 on 0.2.0.9-alpha; fixes bug 1300.
10653 - Ensure DNS requests launched by "RESOLVE" commands from the
10654 controller respect the __LeaveStreamsUnattached setconf options. The
10655 same goes for requests launched via DNSPort or transparent
10656 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10657 - Allow handshaking OR connections to take a full KeepalivePeriod
10658 seconds to handshake. Previously, we would close them after
10659 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10660 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10662 - Rate-limit "Failed to hand off onionskin" warnings.
10663 - Never relay a cell for a circuit we have already destroyed.
10664 Between marking a circuit as closeable and finally closing it,
10665 it may have been possible for a few queued cells to get relayed,
10666 even though they would have been immediately dropped by the next
10667 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10668 - Never queue a cell for a circuit that's already been marked
10670 - Never vote for a server as "Running" if we have a descriptor for
10671 it claiming to be hibernating, and that descriptor was published
10672 more recently than our last contact with the server. Bugfix on
10673 0.2.0.3-alpha; fixes bug 911.
10674 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
10677 o Minor bugfixes (on 0.2.2.x):
10678 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
10679 down if a directory fetch fails and you've configured either
10680 bridges or EntryNodes. The intent was to mark the relay as down
10681 _unless_ you're using bridges or EntryNodes, since if you are
10682 then you could quickly run out of entry points.
10683 - Fix the Windows directory-listing code. A bug introduced in
10684 0.2.2.14-alpha could make Windows directory servers forget to load
10685 some of their cached v2 networkstatus files.
10686 - Really allow clients to use relays as bridges. Fixes bug 1776;
10687 bugfix on 0.2.2.15-alpha.
10688 - Demote a warn to info that happens when the CellStatistics option
10689 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
10690 Reported by Moritz Bartl.
10691 - On Windows, build correctly either with or without Unicode support.
10692 This is necessary so that Tor can support fringe platforms like
10693 Windows 98 (which has no Unicode), or Windows CE (which has no
10694 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
10697 - Add a unit test for cross-platform directory-listing code.
10700 Changes in version 0.2.2.15-alpha - 2010-08-18
10701 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
10702 fixes a variety of other bugs that were preventing performance
10703 experiments from moving forward, fixes several bothersome memory leaks,
10704 and generally closes a lot of smaller bugs that have been filling up
10708 - Stop assigning the HSDir flag to relays that disable their
10709 DirPort (and thus will refuse to answer directory requests). This
10710 fix should dramatically improve the reachability of hidden services:
10711 hidden services and hidden service clients pick six HSDir relays
10712 to store and retrieve the hidden service descriptor, and currently
10713 about half of the HSDir relays will refuse to work. Bugfix on
10714 0.2.0.10-alpha; fixes part of bug 1693.
10715 - The PerConnBWRate and Burst config options, along with the
10716 bwconnrate and bwconnburst consensus params, initialized each conn's
10717 token bucket values only when the connection is established. Now we
10718 update them if the config options change, and update them every time
10719 we get a new consensus. Otherwise we can encounter an ugly edge
10720 case where we initialize an OR conn to client-level bandwidth,
10721 but then later the relay joins the consensus and we leave it
10722 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
10723 - Fix a regression that caused Tor to rebind its ports if it receives
10724 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
10727 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
10728 should give us approximately 40-50% more Guard-flagged nodes,
10729 improving the anonymity the Tor network can provide and also
10730 decreasing the dropoff in throughput that relays experience when
10731 they first get the Guard flag.
10732 - Allow enabling or disabling the *Statistics config options while
10736 - Update to the August 1 2010 Maxmind GeoLite Country database.
10737 - Have the controller interface give a more useful message than
10738 "Internal Error" in response to failed GETINFO requests.
10739 - Warn when the same option is provided more than once in a torrc
10740 file, on the command line, or in a single SETCONF statement, and
10741 the option is one that only accepts a single line. Closes bug 1384.
10742 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10743 Patch from mingw-san.
10744 - Add support for the country code "{??}" in torrc options like
10745 ExcludeNodes, to indicate all routers of unknown country. Closes
10747 - Relays report the number of bytes spent on answering directory
10748 requests in extra-info descriptors similar to {read,write}-history.
10749 Implements enhancement 1790.
10751 o Minor bugfixes (on 0.2.1.x and earlier):
10752 - Complain if PublishServerDescriptor is given multiple arguments that
10753 include 0 or 1. This configuration will be rejected in the future.
10754 Bugfix on 0.2.0.1-alpha; closes bug 1107.
10755 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
10756 Bugfix on 0.2.0.13-alpha; closes bug 928.
10757 - Change "Application request when we're believed to be offline."
10758 notice to "Application request when we haven't used client
10759 functionality lately.", to clarify that it's not an error. Bugfix
10760 on 0.0.9.3; fixes bug 1222.
10761 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
10762 would return "551 Internal error" rather than "552 Unrecognized key
10763 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
10764 - Users can't configure a regular relay to be their bridge. It didn't
10765 work because when Tor fetched the bridge descriptor, it found
10766 that it already had it, and didn't realize that the purpose of the
10767 descriptor had changed. Now we replace routers with a purpose other
10768 than bridge with bridge descriptors when fetching them. Bugfix on
10769 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
10770 refetch the descriptor with router purpose 'general', disabling
10772 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10773 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10774 on 0.2.0.10-alpha; fixes bug 1808.
10775 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10776 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10777 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10778 Servers can start sending this code when enough clients recognize
10779 it. Also update the spec to reflect this new reason. Bugfix on
10780 0.1.0.1-rc; fixes part of bug 1793.
10781 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10782 when we switch from being a public relay to a bridge. Otherwise
10783 there will still be clients that see the relay in their consensus,
10784 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
10786 - Instead of giving an assertion failure on an internal mismatch
10787 on estimated freelist size, just log a BUG warning and try later.
10788 Mitigates but does not fix bug 1125.
10789 - Fix an assertion failure that could occur in caches or bridge users
10790 when using a very short voting interval on a testing network.
10791 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
10793 o Minor bugfixes (on 0.2.2.x):
10794 - Alter directory authorities to always consider Exit-flagged nodes
10795 as potential Guard nodes in their votes. The actual decision to
10796 use Exits as Guards is done in the consensus bandwidth weights.
10797 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
10798 - When the controller is reporting the purpose of circuits that
10799 didn't finish building before the circuit build timeout, it was
10800 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
10801 - Our libevent version parsing code couldn't handle versions like
10802 1.4.14b-stable and incorrectly warned the user about using an
10803 old and broken version of libevent. Treat 1.4.14b-stable like
10804 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
10806 - Don't use substitution references like $(VAR:MOD) when
10807 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
10808 '$(:x)' to 'x' rather than the empty string. This bites us in
10809 doc/ when configured with --disable-asciidoc. Bugfix on
10810 0.2.2.9-alpha; fixes bug 1773.
10811 - Remove a spurious hidden service server-side log notice about
10812 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
10814 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
10816 - Correctly report written bytes on linked connections. Found while
10817 implementing 1790. Bugfix on 0.2.2.4-alpha.
10818 - Fix three memory leaks: one in circuit_build_times_parse_state(),
10819 one in dirvote_add_signatures_to_pending_consensus(), and one every
10820 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
10821 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
10823 o Code simplifications and refactoring:
10824 - Take a first step towards making or.h smaller by splitting out
10825 function definitions for all source files in src/or/. Leave
10826 structures and defines in or.h for now.
10827 - Remove a bunch of unused function declarations as well as a block of
10828 #if 0'd code from the unit tests. Closes bug 1824.
10829 - New unit tests for exit-port history statistics; refactored exit
10830 statistics code to be more easily tested.
10831 - Remove the old debian/ directory from the main Tor distribution.
10832 The official Tor-for-debian git repository lives at the URL
10833 https://git.torproject.org/debian/tor.git
10836 Changes in version 0.2.2.14-alpha - 2010-07-12
10837 Tor 0.2.2.14-alpha greatly improves client-side handling of
10838 circuit build timeouts, which are used to estimate speed and improve
10839 performance. We also move to a much better GeoIP database, port Tor to
10840 Windows CE, introduce new compile flags that improve code security,
10841 add an eighth v3 directory authority, and address a lot of more
10845 - Tor directory authorities no longer crash when started with a
10846 cached-microdesc-consensus file in their data directory. Bugfix
10847 on 0.2.2.6-alpha; fixes bug 1532.
10848 - Treat an unset $HOME like an empty $HOME rather than triggering an
10849 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
10850 - Ignore negative and large circuit build timeout values that can
10851 happen during a suspend or hibernate. These values caused various
10852 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
10853 - Alter calculation of Pareto distribution parameter 'Xm' for
10854 Circuit Build Timeout learning to use the weighted average of the
10855 top N=3 modes (because we have three entry guards). Considering
10856 multiple modes should improve the timeout calculation in some cases,
10857 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
10859 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
10860 right censored distribution model. This approach improves over the
10861 synthetic timeout generation approach that was producing insanely
10862 high timeout values. Now we calculate build timeouts using truncated
10863 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
10864 - Do not close circuits that are under construction when they reach
10865 the circuit build timeout. Instead, leave them building (but do not
10866 use them) for up until the time corresponding to the 95th percentile
10867 on the Pareto CDF or 60 seconds, whichever is greater. This is done
10868 to provide better data for the new Pareto model. This percentile
10869 can be controlled by the consensus.
10872 - Move to the June 2010 Maxmind GeoLite country db (rather than the
10873 June 2009 ip-to-country GeoIP db) for our statistics that count
10874 how many users relays are seeing from each country. Now we have
10875 more accurate data for many African countries.
10876 - Port Tor to build and run correctly on Windows CE systems, using
10877 the wcecompat library. Contributed by Valerio Lupi.
10878 - New "--enable-gcc-hardening" ./configure flag (off by default)
10879 to turn on gcc compile time hardening options. It ensures
10880 that signed ints have defined behavior (-fwrapv), enables
10881 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
10882 with canaries (-fstack-protector-all), turns on ASLR protection if
10883 supported by the kernel (-fPIE, -pie), and adds additional security
10884 related warnings. Verified to work on Mac OS X and Debian Lenny.
10885 - New "--enable-linker-hardening" ./configure flag (off by default)
10886 to turn on ELF specific hardening features (relro, now). This does
10887 not work with Mac OS X or any other non-ELF binary format.
10889 o New directory authorities:
10890 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10894 - New config option "WarnUnsafeSocks 0" disables the warning that
10895 occurs whenever Tor receives a socks handshake using a version of
10896 the socks protocol that can only provide an IP address (rather
10897 than a hostname). Setups that do DNS locally over Tor are fine,
10898 and we shouldn't spam the logs in that case.
10899 - Convert the HACKING file to asciidoc, and add a few new sections
10900 to it, explaining how we use Git, how we make changelogs, and
10901 what should go in a patch.
10902 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10903 event, to give information on the current rate of circuit timeouts
10904 over our stored history.
10905 - Add ability to disable circuit build time learning via consensus
10906 parameter and via a LearnCircuitBuildTimeout config option. Also
10907 automatically disable circuit build time calculation if we are
10908 either a AuthoritativeDirectory, or if we fail to write our state
10909 file. Fixes bug 1296.
10910 - More gracefully handle corrupt state files, removing asserts
10911 in favor of saving a backup and resetting state.
10912 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10916 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10918 - When a2x fails, mention that the user could disable manpages instead
10919 of trying to fix their asciidoc installation.
10920 - Where available, use Libevent 2.0's periodic timers so that our
10921 once-per-second cleanup code gets called even more closely to
10922 once per second than it would otherwise. Fixes bug 943.
10923 - If you run a bridge that listens on multiple IP addresses, and
10924 some user configures a bridge address that uses a different IP
10925 address than your bridge writes in its router descriptor, and the
10926 user doesn't specify an identity key, their Tor would discard the
10927 descriptor because "it isn't one of our configured bridges", and
10928 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
10929 Bugfix on 0.2.0.3-alpha.
10930 - If OpenSSL fails to make a duplicate of a private or public key, log
10931 an error message and try to exit cleanly. May help with debugging
10932 if bug 1209 ever remanifests.
10933 - Save a couple bytes in memory allocation every time we escape
10934 certain characters in a string. Patch from Florian Zumbiehl.
10935 - Make it explicit that we don't cannibalize one-hop circuits. This
10936 happens in the wild, but doesn't turn out to be a problem because
10937 we fortunately don't use those circuits. Many thanks to outofwords
10938 for the initial analysis and to swissknife who confirmed that
10939 two-hop circuits are actually created.
10940 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
10941 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
10942 - Eliminate a case where a circuit build time warning was displayed
10943 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
10946 Changes in version 0.2.1.26 - 2010-05-02
10947 Tor 0.2.1.26 addresses the recent connection and memory overload
10948 problems we've been seeing on relays, especially relays with their
10949 DirPort open. If your relay has been crashing, or you turned it off
10950 because it used too many resources, give this release a try.
10952 This release also fixes yet another instance of broken OpenSSL libraries
10953 that was causing some relays to drop out of the consensus.
10956 - Teach relays to defend themselves from connection overload. Relays
10957 now close idle circuits early if it looks like they were intended
10958 for directory fetches. Relays are also more aggressive about closing
10959 TLS connections that have no circuits on them. Such circuits are
10960 unlikely to be re-used, and tens of thousands of them were piling
10961 up at the fast relays, causing the relays to run out of sockets
10962 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10963 their directory fetches over TLS).
10964 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10965 that claim to be earlier than 0.9.8m, but which have in reality
10966 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10967 behavior. Possible fix for some cases of bug 1346.
10968 - Directory mirrors were fetching relay descriptors only from v2
10969 directory authorities, rather than v3 authorities like they should.
10970 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10971 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10974 - Finally get rid of the deprecated and now harmful notion of "clique
10975 mode", where directory authorities maintain TLS connections to
10979 - In the util/threads test, no longer free the test_mutex before all
10980 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10981 - The master thread could starve the worker threads quite badly on
10982 certain systems, causing them to run only partially in the allowed
10983 window. This resulted in test failures. Now the master thread sleeps
10984 occasionally for a few microseconds while the two worker-threads
10985 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10988 Changes in version 0.2.2.13-alpha - 2010-04-24
10989 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
10990 problems we've been seeing on relays, especially relays with their
10991 DirPort open. If your relay has been crashing, or you turned it off
10992 because it used too many resources, give this release a try.
10995 - Teach relays to defend themselves from connection overload. Relays
10996 now close idle circuits early if it looks like they were intended
10997 for directory fetches. Relays are also more aggressive about closing
10998 TLS connections that have no circuits on them. Such circuits are
10999 unlikely to be re-used, and tens of thousands of them were piling
11000 up at the fast relays, causing the relays to run out of sockets
11001 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11002 their directory fetches over TLS).
11005 - Finally get rid of the deprecated and now harmful notion of "clique
11006 mode", where directory authorities maintain TLS connections to
11008 - Directory authorities now do an immediate reachability check as soon
11009 as they hear about a new relay. This change should slightly reduce
11010 the time between setting up a relay and getting listed as running
11011 in the consensus. It should also improve the time between setting
11012 up a bridge and seeing use by bridge users.
11013 - Directory authorities no longer launch a TLS connection to every
11014 relay as they startup. Now that we have 2k+ descriptors cached,
11015 the resulting network hiccup is becoming a burden. Besides,
11016 authorities already avoid voting about Running for the first half
11017 hour of their uptime.
11020 Changes in version 0.2.2.12-alpha - 2010-04-20
11021 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
11022 handle and vote on descriptors. It was causing relays to drop out of
11026 - Many relays have been falling out of the consensus lately because
11027 not enough authorities know about their descriptor for them to get
11028 a majority of votes. When we deprecated the v2 directory protocol,
11029 we got rid of the only way that v3 authorities can hear from each
11030 other about other descriptors. Now authorities examine every v3
11031 vote for new descriptors, and fetch them from that authority. Bugfix
11033 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
11034 and a warning in or.h related to bandwidth_weight_rule_t that
11035 prevented clean compile on OS X. Fixes bug 1363; bugfix on
11037 - Fix a segfault on relays when DirReqStatistics is enabled
11038 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
11042 - Demote a confusing TLS warning that relay operators might get when
11043 someone tries to talk to their OrPort. It is neither the operator's
11044 fault nor can they do anything about it. Fixes bug 1364; bugfix
11048 Changes in version 0.2.2.11-alpha - 2010-04-15
11049 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
11050 libraries that was causing some relays to drop out of the consensus.
11053 - Directory mirrors were fetching relay descriptors only from v2
11054 directory authorities, rather than v3 authorities like they should.
11055 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11056 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11057 - Fix a parsing error that made every possible value of
11058 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
11059 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
11060 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
11061 about the option without breaking older ones.
11062 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11063 that claim to be earlier than 0.9.8m, but which have in reality
11064 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11065 behavior. Possible fix for some cases of bug 1346.
11068 - Experiment with a more aggressive approach to preventing clients
11069 from making one-hop exit streams. Exit relays who want to try it
11070 out can set "RefuseUnknownExits 1" in their torrc, and then look
11071 for "Attempt by %s to open a stream" log messages. Let us know
11073 - Add support for statically linking zlib by specifying
11074 --enable-static-zlib, to go with our support for statically linking
11075 openssl and libevent. Resolves bug 1358.
11078 - Fix a segfault that happens whenever a Tor client that is using
11079 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
11081 - When we cleaned up the contrib/tor-exit-notice.html file, we left
11082 out the first line. Fixes bug 1295.
11083 - When building the manpage from a tarball, we required asciidoc, but
11084 the asciidoc -> roff/html conversion was already done for the
11085 tarball. Make 'make' complain only when we need asciidoc (either
11086 because we're compiling directly from git, or because we altered
11087 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
11088 - When none of the directory authorities vote on any params, Tor
11089 segfaulted when trying to make the consensus from the votes. We
11090 didn't trigger the bug in practice, because authorities do include
11091 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
11094 - In the util/threads test, no longer free the test_mutex before all
11095 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11096 - The master thread could starve the worker threads quite badly on
11097 certain systems, causing them to run only partially in the allowed
11098 window. This resulted in test failures. Now the master thread sleeps
11099 occasionally for a few microseconds while the two worker-threads
11100 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11103 Changes in version 0.2.2.10-alpha - 2010-03-07
11104 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
11105 could prevent relays from guessing their IP address correctly. It also
11106 starts the groundwork for another client-side performance boost, since
11107 currently we're not making efficient use of relays that have both the
11108 Guard flag and the Exit flag.
11111 - Fix a regression from our patch for bug 1244 that caused relays
11112 to guess their IP address incorrectly if they didn't set Address
11113 in their torrc and/or their address fails to resolve. Bugfix on
11114 0.2.2.9-alpha; fixes bug 1269.
11116 o Major features (performance):
11117 - Directory authorities now compute consensus weightings that instruct
11118 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11119 and no flag. Clients that use these weightings will distribute
11120 network load more evenly across these different relay types. The
11121 weightings are in the consensus so we can change them globally in
11122 the future. Extra thanks to "outofwords" for finding some nasty
11123 security bugs in the first implementation of this feature.
11125 o Minor features (performance):
11126 - Always perform router selections using weighted relay bandwidth,
11127 even if we don't need a high capacity circuit at the time. Non-fast
11128 circuits now only differ from fast ones in that they can use relays
11129 not marked with the Fast flag. This "feature" could turn out to
11130 be a horrible bug; we should investigate more before it goes into
11134 - Allow disabling building of the manpages. Skipping the manpage
11135 speeds up the build considerably.
11137 o Minor bugfixes (on 0.2.2.x):
11138 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
11139 Bugfix on 0.2.2.9-alpha.
11140 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
11141 config option. Bugfix on 0.2.2.7-alpha.
11142 - Ship the asciidoc-helper file in the tarball, so that people can
11143 build from source if they want to, and touching the .1.txt files
11144 doesn't break the build. Bugfix on 0.2.2.9-alpha.
11146 o Minor bugfixes (on 0.2.1.x or earlier):
11147 - Fix a dereference-then-NULL-check sequence when publishing
11148 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11150 - Fix another dereference-then-NULL-check sequence. Bugfix on
11151 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11152 - Make sure we treat potentially not NUL-terminated strings correctly.
11153 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11155 o Code simplifications and refactoring:
11156 - Fix some urls in the exit notice file and make it XHTML1.1 strict
11157 compliant. Based on a patch from Christian Kujau.
11158 - Don't use sed in asciidoc-helper anymore.
11159 - Make the build process fail if asciidoc cannot be found and
11160 building with asciidoc isn't disabled.
11163 Changes in version 0.2.2.9-alpha - 2010-02-22
11164 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
11165 location of a directory authority, and cleans up a bunch of small bugs.
11167 o Directory authority changes:
11168 - Change IP address for dannenberg (v3 directory authority), and
11169 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11170 service directory authority) from the list.
11173 - Make Tor work again on the latest OS X: when deciding whether to
11174 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11175 version at run-time, not compile time. We need to do this because
11176 Apple doesn't update its dev-tools headers when it updates its
11177 libraries in a security patch.
11178 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11179 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11180 a memory leak when requesting a hidden service descriptor we've
11181 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11183 - Authorities could be tricked into giving out the Exit flag to relays
11184 that didn't allow exiting to any ports. This bug could screw
11185 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
11186 1238. Bug discovered by Martin Kowalczyk.
11187 - When freeing a session key, zero it out completely. We only zeroed
11188 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11189 patched by ekir. Fixes bug 1254.
11192 - Fix static compilation by listing the openssl libraries in the right
11193 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
11194 - Resume handling .exit hostnames in a special way: originally we
11195 stripped the .exit part and used the requested exit relay. In
11196 0.2.2.1-alpha we stopped treating them in any special way, meaning
11197 if you use a .exit address then Tor will pass it on to the exit
11198 relay. Now we reject the .exit stream outright, since that behavior
11199 might be more expected by the user. Found and diagnosed by Scott
11200 Bennett and Downie on or-talk.
11201 - Don't spam the controller with events when we have no file
11202 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
11203 for log messages was already solved from bug 748.)
11204 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
11206 - Make the DNSPort option work with libevent 2.x. Don't alter the
11207 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
11208 - Emit a GUARD DROPPED controller event for a case we missed.
11209 - Make more fields in the controller protocol case-insensitive, since
11210 control-spec.txt said they were.
11211 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11212 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11213 - Fix a spec conformance issue: the network-status-version token
11214 must be the first token in a v3 consensus or vote. Discovered by
11215 parakeep. Bugfix on 0.2.0.3-alpha.
11217 o Code simplifications and refactoring:
11218 - Generate our manpage and HTML documentation using Asciidoc. This
11219 change should make it easier to maintain the documentation, and
11220 produce nicer HTML.
11221 - Remove the --enable-iphone option. According to reports from Marco
11222 Bonetti, Tor builds fine without any special tweaking on recent
11223 iPhone SDK versions.
11224 - Removed some unnecessary files from the source distribution. The
11225 AUTHORS file has now been merged into the people page on the
11226 website. The roadmaps and design doc can now be found in the
11227 projects directory in svn.
11228 - Enabled various circuit build timeout constants to be controlled
11229 by consensus parameters. Also set better defaults for these
11230 parameters based on experimentation on broadband and simulated
11231 high latency links.
11234 - The 'EXTENDCIRCUIT' control port command can now be used with
11235 a circ id of 0 and no path. This feature will cause Tor to build
11236 a new 'fast' general purpose circuit using its own path selection
11238 - Added a BUILDTIMEOUT_SET controller event to describe changes
11239 to the circuit build timeout.
11240 - Future-proof the controller protocol a bit by ignoring keyword
11241 arguments we do not recognize.
11242 - Expand homedirs passed to tor-checkkey. This should silence a
11243 coverity complaint about passing a user-supplied string into
11244 open() without checking it.
11247 Changes in version 0.2.1.25 - 2010-03-16
11248 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
11249 prevent relays from guessing their IP address correctly. It also fixes
11250 several minor potential security bugs.
11253 - Fix a regression from our patch for bug 1244 that caused relays
11254 to guess their IP address incorrectly if they didn't set Address
11255 in their torrc and/or their address fails to resolve. Bugfix on
11256 0.2.1.23; fixes bug 1269.
11257 - When freeing a session key, zero it out completely. We only zeroed
11258 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11259 patched by ekir. Fixes bug 1254.
11262 - Fix a dereference-then-NULL-check sequence when publishing
11263 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11265 - Fix another dereference-then-NULL-check sequence. Bugfix on
11266 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11267 - Make sure we treat potentially not NUL-terminated strings correctly.
11268 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11272 Changes in version 0.2.1.24 - 2010-02-21
11273 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11277 - Work correctly out-of-the-box with even more vendor-patched versions
11278 of OpenSSL. In particular, make it so Debian and OS X don't need
11279 customized patches to run/build.
11282 Changes in version 0.2.1.23 - 2010-02-13
11283 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
11284 again on the latest OS X, and updates the location of a directory
11287 o Major bugfixes (performance):
11288 - We were selecting our guards uniformly at random, and then weighting
11289 which of our guards we'd use uniformly at random. This imbalance
11290 meant that Tor clients were severely limited on throughput (and
11291 probably latency too) by the first hop in their circuit. Now we
11292 select guards weighted by currently advertised bandwidth. We also
11293 automatically discard guards picked using the old algorithm. Fixes
11294 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11297 - Make Tor work again on the latest OS X: when deciding whether to
11298 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11299 version at run-time, not compile time. We need to do this because
11300 Apple doesn't update its dev-tools headers when it updates its
11301 libraries in a security patch.
11302 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11303 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11304 a memory leak when requesting a hidden service descriptor we've
11305 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11308 o Directory authority changes:
11309 - Change IP address for dannenberg (v3 directory authority), and
11310 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11311 service directory authority) from the list.
11314 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11315 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11318 - Avoid a mad rush at the beginning of each month when each client
11319 rotates half of its guards. Instead we spread the rotation out
11320 throughout the month, but we still avoid leaving a precise timestamp
11321 in the state file about when we first picked the guard. Improves
11322 over the behavior introduced in 0.1.2.17.
11325 Changes in version 0.2.2.8-alpha - 2010-01-26
11326 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
11327 causing bridge relays to disappear. If you're running a bridge,
11331 - Fix a memory corruption bug on bridges that occured during the
11332 inclusion of stats data in extra-info descriptors. Also fix the
11333 interface for geoip_get_bridge_stats* to prevent similar bugs in
11334 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
11335 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
11338 - Ignore OutboundBindAddress when connecting to localhost.
11339 Connections to localhost need to come _from_ localhost, or else
11340 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
11344 Changes in version 0.2.2.7-alpha - 2010-01-19
11345 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
11346 as laying the groundwork for further relay-side performance fixes. It
11347 also starts cleaning up client behavior with respect to the EntryNodes,
11348 ExitNodes, and StrictNodes config options.
11350 This release also rotates two directory authority keys, due to a
11351 security breach of some of the Torproject servers.
11353 o Directory authority changes:
11354 - Rotate keys (both v3 identity and relay identity) for moria1
11357 o Major features (performance):
11358 - We were selecting our guards uniformly at random, and then weighting
11359 which of our guards we'd use uniformly at random. This imbalance
11360 meant that Tor clients were severely limited on throughput (and
11361 probably latency too) by the first hop in their circuit. Now we
11362 select guards weighted by currently advertised bandwidth. We also
11363 automatically discard guards picked using the old algorithm. Fixes
11364 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11365 - When choosing which cells to relay first, relays can now favor
11366 circuits that have been quiet recently, to provide lower latency
11367 for low-volume circuits. By default, relays enable or disable this
11368 feature based on a setting in the consensus. You can override
11369 this default by using the new "CircuitPriorityHalflife" config
11370 option. Design and code by Ian Goldberg, Can Tang, and Chris
11372 - Add separate per-conn write limiting to go with the per-conn read
11373 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11374 but never per-conn write limits.
11375 - New consensus params "bwconnrate" and "bwconnburst" to let us
11376 rate-limit client connections as they enter the network. It's
11377 controlled in the consensus so we can turn it on and off for
11378 experiments. It's starting out off. Based on proposal 163.
11380 o Major features (relay selection options):
11381 - Switch to a StrictNodes config option, rather than the previous
11382 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
11383 "StrictExcludeNodes" option.
11384 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11385 change during a config reload, mark and discard all our origin
11386 circuits. This fix should address edge cases where we change the
11387 config options and but then choose a circuit that we created before
11389 - If EntryNodes or ExitNodes are set, be more willing to use an
11390 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
11392 - Make EntryNodes config option much more aggressive even when
11393 StrictNodes is not set. Before it would prepend your requested
11394 entrynodes to your list of guard nodes, but feel free to use others
11395 after that. Now it chooses only from your EntryNodes if any of
11396 those are available, and only falls back to others if a) they're
11397 all down and b) StrictNodes is not set.
11398 - Now we refresh your entry guards from EntryNodes at each consensus
11399 fetch -- rather than just at startup and then they slowly rot as
11400 the network changes.
11403 - Stop bridge directory authorities from answering dbg-stability.txt
11404 directory queries, which would let people fetch a list of all
11405 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11408 - Log a notice when we get a new control connection. Now it's easier
11409 for security-conscious users to recognize when a local application
11410 is knocking on their controller door. Suggested by bug 1196.
11411 - New config option "CircuitStreamTimeout" to override our internal
11412 timeout schedule for how many seconds until we detach a stream from
11413 a circuit and try a new circuit. If your network is particularly
11414 slow, you might want to set this to a number like 60.
11415 - New controller command "getinfo config-text". It returns the
11416 contents that Tor would write if you send it a SAVECONF command,
11417 so the controller can write the file to disk itself.
11418 - New options for SafeLogging to allow scrubbing only log messages
11419 generated while acting as a relay.
11420 - Ship the bridges spec file in the tarball too.
11421 - Avoid a mad rush at the beginning of each month when each client
11422 rotates half of its guards. Instead we spread the rotation out
11423 throughout the month, but we still avoid leaving a precise timestamp
11424 in the state file about when we first picked the guard. Improves
11425 over the behavior introduced in 0.1.2.17.
11427 o Minor bugfixes (compiling):
11428 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11429 hides it. Bugfix on 0.2.2.6-alpha.
11430 - Fix compilation on Solaris by removing support for the
11431 DisableAllSwap config option. Solaris doesn't have an rlimit for
11432 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11435 o Minor bugfixes (crashes):
11436 - Do not segfault when writing buffer stats when we haven't observed
11437 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11439 - If we're in the pathological case where there's no exit bandwidth
11440 but there is non-exit bandwidth, or no guard bandwidth but there
11441 is non-guard bandwidth, don't crash during path selection. Bugfix
11443 - Fix an impossible-to-actually-trigger buffer overflow in relay
11444 descriptor generation. Bugfix on 0.1.0.15.
11446 o Minor bugfixes (privacy):
11447 - Fix an instance where a Tor directory mirror might accidentally
11448 log the IP address of a misbehaving Tor client. Bugfix on
11450 - Don't list Windows capabilities in relay descriptors. We never made
11451 use of them, and maybe it's a bad idea to publish them. Bugfix
11454 o Minor bugfixes (other):
11455 - Resolve an edge case in path weighting that could make us misweight
11456 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
11457 - Fix statistics on client numbers by country as seen by bridges that
11458 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
11459 intervals instead of variable 12-to-48-hour intervals.
11460 - After we free an internal connection structure, overwrite it
11461 with a different memory value than we use for overwriting a freed
11462 internal circuit structure. Should help with debugging. Suggested
11464 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
11467 o Removed features:
11468 - Remove the HSAuthorityRecordStats option that version 0 hidden
11469 service authorities could have used to track statistics of overall
11470 hidden service usage.
11473 Changes in version 0.2.1.22 - 2010-01-19
11474 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
11475 authorities -- it would tell you its whole history of bridge descriptors
11476 if you make the right directory request. This stable update also
11477 rotates two of the seven v3 directory authority keys and locations.
11479 o Directory authority changes:
11480 - Rotate keys (both v3 identity and relay identity) for moria1
11484 - Stop bridge directory authorities from answering dbg-stability.txt
11485 directory queries, which would let people fetch a list of all
11486 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11489 Changes in version 0.2.1.21 - 2009-12-21
11490 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
11491 library. If you use Tor on Linux / Unix and you're getting SSL
11492 renegotiation errors, upgrading should help. We also recommend an
11493 upgrade if you're an exit relay.
11496 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11497 handshake from working unless we explicitly tell OpenSSL that we
11498 are using SSL renegotiation safely. We are, of course, but OpenSSL
11499 0.9.8l won't work unless we say we are.
11500 - Avoid crashing if the client is trying to upload many bytes and the
11501 circuit gets torn down at the same time, or if the flip side
11502 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
11505 - Do not refuse to learn about authority certs and v2 networkstatus
11506 documents that are older than the latest consensus. This bug might
11507 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11508 Spotted and fixed by xmux.
11509 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
11510 trigger platform-specific option misparsing case found by Coverity
11512 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
11513 trigger assert. Fixes bug 1173.
11516 Changes in version 0.2.2.6-alpha - 2009-11-19
11517 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
11518 support for the new lower-footprint "microdescriptor" directory design,
11519 future-proofing our consensus format against new hash functions or
11520 other changes, and an Android port. It also makes Tor compatible with
11521 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
11524 - Directory authorities can now create, vote on, and serve multiple
11525 parallel formats of directory data as part of their voting process.
11526 Partially implements Proposal 162: "Publish the consensus in
11528 - Directory authorities can now agree on and publish small summaries
11529 of router information that clients can use in place of regular
11530 server descriptors. This transition will eventually allow clients
11531 to use far less bandwidth for downloading information about the
11532 network. Begins the implementation of Proposal 158: "Clients
11533 download consensus + microdescriptors".
11534 - The directory voting system is now extensible to use multiple hash
11535 algorithms for signatures and resource selection. Newer formats
11536 are signed with SHA256, with a possibility for moving to a better
11537 hash algorithm in the future.
11538 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11539 current and future memory pages via mlockall(). On supported
11540 platforms (modern Linux and probably BSD but not Windows or OS X),
11541 this should effectively disable any and all attempts to page out
11542 memory. This option requires that you start your Tor as root --
11543 if you use DisableAllSwap, please consider using the User option
11544 to properly reduce the privileges of your Tor.
11545 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11546 to help Tor build correctly for Android phones.
11549 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11550 handshake from working unless we explicitly tell OpenSSL that we
11551 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
11552 won't work unless we say we are.
11555 - Fix a crash bug when trying to initialize the evdns module in
11556 Libevent 2. Bugfix on 0.2.1.16-rc.
11557 - Stop logging at severity 'warn' when some other Tor client tries
11558 to establish a circuit with us using weak DH keys. It's a protocol
11559 violation, but that doesn't mean ordinary users need to hear about
11560 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
11561 - Do not refuse to learn about authority certs and v2 networkstatus
11562 documents that are older than the latest consensus. This bug might
11563 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11564 Spotted and fixed by xmux.
11565 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
11566 - If all authorities restart at once right before a consensus vote,
11567 nobody will vote about "Running", and clients will get a consensus
11568 with no usable relays. Instead, authorities refuse to build a
11569 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11570 - If your relay can't keep up with the number of incoming create
11571 cells, it would log one warning per failure into your logs. Limit
11572 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
11573 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11574 on 0.2.0.3-alpha; fixes bug 1113.
11575 - Fix a memory leak on directory authorities during voting that was
11576 introduced in 0.2.2.1-alpha. Found via valgrind.
11579 Changes in version 0.2.1.20 - 2009-10-15
11580 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11581 services at once, prepares for more performance improvements, and
11582 fixes a bunch of smaller bugs.
11584 The Windows and OS X bundles also include a more recent Vidalia,
11585 and switch from Privoxy to Polipo.
11587 The OS X installers are now drag and drop. It's best to un-install
11588 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11589 you want to upgrade, you'll need to update the paths for Tor and Polipo
11590 in the Vidalia Settings window.
11593 - Send circuit or stream sendme cells when our window has decreased
11594 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11595 by Karsten when testing the "reduce circuit window" performance
11596 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11597 before the release of Tor 0.0.0. This is the new winner of the
11599 - Fix a remotely triggerable memory leak when a consensus document
11600 contains more than one signature from the same voter. Bugfix on
11602 - Avoid segfault in rare cases when finishing an introduction circuit
11603 as a client and finding out that we don't have an introduction key
11604 for it. Fixes bug 1073. Reported by Aaron Swartz.
11607 - Tor now reads the "circwindow" parameter out of the consensus,
11608 and uses that value for its circuit package window rather than the
11609 default of 1000 cells. Begins the implementation of proposal 168.
11611 o New directory authorities:
11612 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11614 - Move moria1 and tonga to alternate IP addresses.
11617 - Fix a signed/unsigned compile warning in 0.2.1.19.
11618 - Fix possible segmentation fault on directory authorities. Bugfix on
11620 - Fix an extremely rare infinite recursion bug that could occur if
11621 we tried to log a message after shutting down the log subsystem.
11622 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11623 - Fix an obscure bug where hidden services on 64-bit big-endian
11624 systems might mis-read the timestamp in v3 introduce cells, and
11625 refuse to connect back to the client. Discovered by "rotor".
11626 Bugfix on 0.2.1.6-alpha.
11627 - We were triggering a CLOCK_SKEW controller status event whenever
11628 we connect via the v2 connection protocol to any relay that has
11629 a wrong clock. Instead, we should only inform the controller when
11630 it's a trusted authority that claims our clock is wrong. Bugfix
11631 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11632 - We were telling the controller about CHECKING_REACHABILITY and
11633 REACHABILITY_FAILED status events whenever we launch a testing
11634 circuit or notice that one has failed. Instead, only tell the
11635 controller when we want to inform the user of overall success or
11636 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11638 - Don't warn when we're using a circuit that ends with a node
11639 excluded in ExcludeExitNodes, but the circuit is not used to access
11640 the outside world. This should help fix bug 1090. Bugfix on
11642 - Work around a small memory leak in some versions of OpenSSL that
11643 stopped the memory used by the hostname TLS extension from being
11647 - Add a "getinfo status/accepted-server-descriptor" controller
11648 command, which is the recommended way for controllers to learn
11649 whether our server descriptor has been successfully received by at
11650 least on directory authority. Un-recommend good-server-descriptor
11651 getinfo and status events until we have a better design for them.
11654 Changes in version 0.2.2.5-alpha - 2009-10-11
11655 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
11658 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11660 o Directory authorities:
11661 - Temporarily (just for this release) move dizum to an alternate
11665 Changes in version 0.2.2.4-alpha - 2009-10-10
11666 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
11667 introduces a new unit test framework, shifts directry authority
11668 addresses around to reduce the impact from recent blocking events,
11669 and fixes a few smaller bugs.
11672 - Fix several more asserts in the circuit_build_times code, for
11673 example one that causes Tor to fail to start once we have
11674 accumulated 5000 build times in the state file. Bugfixes on
11675 0.2.2.2-alpha; fixes bug 1108.
11677 o New directory authorities:
11678 - Move moria1 and Tonga to alternate IP addresses.
11681 - Log SSL state transitions at debug level during handshake, and
11682 include SSL states in error messages. This may help debug future
11683 SSL handshake issues.
11684 - Add a new "Handshake" log domain for activities that happen
11685 during the TLS handshake.
11686 - Revert to the "June 3 2009" ip-to-country file. The September one
11687 seems to have removed most US IP addresses.
11688 - Directory authorities now reject Tor relays with versions less than
11689 0.1.2.14. This step cuts out four relays from the current network,
11690 none of which are very big.
11693 - Fix a couple of smaller issues with gathering statistics. Bugfixes
11695 - Fix two memory leaks in the error case of
11696 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
11697 - Don't count one-hop circuits when we're estimating how long it
11698 takes circuits to build on average. Otherwise we'll set our circuit
11699 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
11700 - Directory authorities no longer change their opinion of, or vote on,
11701 whether a router is Running, unless they have themselves been
11702 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
11705 o Code simplifications and refactoring:
11706 - Revise our unit tests to use the "tinytest" framework, so we
11707 can run tests in their own processes, have smarter setup/teardown
11708 code, and so on. The unit test code has moved to its own
11709 subdirectory, and has been split into multiple modules.
11712 Changes in version 0.2.2.3-alpha - 2009-09-23
11713 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
11716 - Fix an overzealous assert in our new circuit build timeout code.
11717 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
11720 - If the networkstatus consensus tells us that we should use a
11721 negative circuit package window, ignore it. Otherwise we'll
11722 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
11725 Changes in version 0.2.2.2-alpha - 2009-09-21
11726 Tor 0.2.2.2-alpha introduces our latest performance improvement for
11727 clients: Tor tracks the average time it takes to build a circuit, and
11728 avoids using circuits that take too long to build. For fast connections,
11729 this feature can cut your expected latency in half. For slow or flaky
11730 connections, it could ruin your Tor experience. Let us know if it does!
11733 - Tor now tracks how long it takes to build client-side circuits
11734 over time, and adapts its timeout to local network performance.
11735 Since a circuit that takes a long time to build will also provide
11736 bad performance, we get significant latency improvements by
11737 discarding the slowest 20% of circuits. Specifically, Tor creates
11738 circuits more aggressively than usual until it has enough data
11739 points for a good timeout estimate. Implements proposal 151.
11740 We are especially looking for reports (good and bad) from users with
11741 both EDGE and broadband connections that can move from broadband
11742 to EDGE and find out if the build-time data in the .tor/state gets
11743 reset without loss of Tor usability. You should also see a notice
11744 log message telling you that Tor has reset its timeout.
11745 - Directory authorities can now vote on arbitary integer values as
11746 part of the consensus process. This is designed to help set
11747 network-wide parameters. Implements proposal 167.
11748 - Tor now reads the "circwindow" parameter out of the consensus,
11749 and uses that value for its circuit package window rather than the
11750 default of 1000 cells. Begins the implementation of proposal 168.
11753 - Fix a remotely triggerable memory leak when a consensus document
11754 contains more than one signature from the same voter. Bugfix on
11758 - Fix an extremely rare infinite recursion bug that could occur if
11759 we tried to log a message after shutting down the log subsystem.
11760 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11761 - Fix parsing for memory or time units given without a space between
11762 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
11763 - A networkstatus vote must contain exactly one signature. Spec
11764 conformance issue. Bugfix on 0.2.0.3-alpha.
11765 - Fix an obscure bug where hidden services on 64-bit big-endian
11766 systems might mis-read the timestamp in v3 introduce cells, and
11767 refuse to connect back to the client. Discovered by "rotor".
11768 Bugfix on 0.2.1.6-alpha.
11769 - We were triggering a CLOCK_SKEW controller status event whenever
11770 we connect via the v2 connection protocol to any relay that has
11771 a wrong clock. Instead, we should only inform the controller when
11772 it's a trusted authority that claims our clock is wrong. Bugfix
11773 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11774 - We were telling the controller about CHECKING_REACHABILITY and
11775 REACHABILITY_FAILED status events whenever we launch a testing
11776 circuit or notice that one has failed. Instead, only tell the
11777 controller when we want to inform the user of overall success or
11778 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11780 - Don't warn when we're using a circuit that ends with a node
11781 excluded in ExcludeExitNodes, but the circuit is not used to access
11782 the outside world. This should help fix bug 1090, but more problems
11783 remain. Bugfix on 0.2.1.6-alpha.
11784 - Work around a small memory leak in some versions of OpenSSL that
11785 stopped the memory used by the hostname TLS extension from being
11787 - Make our 'torify' script more portable; if we have only one of
11788 'torsocks' or 'tsocks' installed, don't complain to the user;
11789 and explain our warning about tsocks better.
11792 - Add a "getinfo status/accepted-server-descriptor" controller
11793 command, which is the recommended way for controllers to learn
11794 whether our server descriptor has been successfully received by at
11795 least on directory authority. Un-recommend good-server-descriptor
11796 getinfo and status events until we have a better design for them.
11797 - Update to the "September 4 2009" ip-to-country file.
11800 Changes in version 0.2.2.1-alpha - 2009-08-26
11801 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
11802 Tor clients to bootstrap on networks where only port 80 is reachable,
11803 makes it more straightforward to support hardware crypto accelerators,
11804 and starts the groundwork for gathering stats safely at relays.
11807 - Start the process of disabling ".exit" address notation, since it
11808 can be used for a variety of esoteric application-level attacks
11809 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11812 o New directory authorities:
11813 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11817 - New AccelName and AccelDir options add support for dynamic OpenSSL
11818 hardware crypto acceleration engines.
11819 - Tor now supports tunneling all of its outgoing connections over
11820 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11821 configuration options. Code by Christopher Davis.
11824 - Send circuit or stream sendme cells when our window has decreased
11825 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11826 by Karsten when testing the "reduce circuit window" performance
11827 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11828 before the release of Tor 0.0.0. This is the new winner of the
11831 o New options for gathering stats safely:
11832 - Directory mirrors that set "DirReqStatistics 1" write statistics
11833 about directory requests to disk every 24 hours. As compared to the
11834 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
11835 1) stats are written to disk exactly every 24 hours; 2) estimated
11836 shares of v2 and v3 requests are determined as mean values, not at
11837 the end of a measurement period; 3) unresolved requests are listed
11838 with country code '??'; 4) directories also measure download times.
11839 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11840 number of exit streams and transferred bytes per port to disk every
11842 - Relays that set "CellStatistics 1" write statistics on how long
11843 cells spend in their circuit queues to disk every 24 hours.
11844 - Entry nodes that set "EntryStatistics 1" write statistics on the
11845 rough number and origins of connecting clients to disk every 24
11847 - Relays that write any of the above statistics to disk and set
11848 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11849 their extra-info documents.
11852 - New --digests command-line switch to output the digests of the
11853 source files Tor was built with.
11854 - The "torify" script now uses torsocks where available.
11855 - The memarea code now uses a sentinel value at the end of each area
11856 to make sure nothing writes beyond the end of an area. This might
11857 help debug some conceivable causes of bug 930.
11858 - Time and memory units in the configuration file can now be set to
11859 fractional units. For example, "2.5 GB" is now a valid value for
11861 - Certain Tor clients (such as those behind check.torproject.org) may
11862 want to fetch the consensus in an extra early manner. To enable this
11863 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
11864 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
11865 as only certain clients who must have this information sooner should
11867 - Instead of adding the svn revision to the Tor version string, report
11868 the git commit (when we're building from a git checkout).
11871 - If any of the v3 certs we download are unparseable, we should
11872 actually notice the failure so we don't retry indefinitely. Bugfix
11873 on 0.2.0.x; reported by "rotator".
11874 - If the cached cert file is unparseable, warn but don't exit.
11875 - Fix possible segmentation fault on directory authorities. Bugfix on
11877 - When Tor fails to parse a descriptor of any kind, dump it to disk.
11878 Might help diagnosing bug 1051.
11880 o Deprecated and removed features:
11881 - The controller no longer accepts the old obsolete "addr-mappings/"
11882 or "unregistered-servers-" GETINFO values.
11883 - Hidden services no longer publish version 0 descriptors, and clients
11884 do not request or use version 0 descriptors. However, the old hidden
11885 service authorities still accept and serve version 0 descriptors
11886 when contacted by older hidden services/clients.
11887 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
11888 always on; using them is necessary for correct forward-compatible
11890 - Remove support for .noconnect style addresses. Nobody was using
11891 them, and they provided another avenue for detecting Tor users
11892 via application-level web tricks.
11894 o Packaging changes:
11895 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
11896 installer bundles. See
11897 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
11898 for details of what's new in Vidalia 0.2.3.
11899 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
11900 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
11901 configuration file, rather than the old Privoxy.
11902 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
11903 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
11904 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
11905 better compatibility with OS X 10.6, aka Snow Leopard.
11906 - OS X Vidalia Bundle: The multi-package installer is now replaced
11907 by a simple drag and drop to the /Applications folder. This change
11908 occurred with the upgrade to Vidalia 0.2.3.
11911 Changes in version 0.2.1.19 - 2009-07-28
11912 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11913 services on Tor 0.2.1.3-alpha through 0.2.1.18.
11916 - Make accessing hidden services on 0.2.1.x work right again.
11917 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11918 part of patch provided by "optimist".
11921 - When a relay/bridge is writing out its identity key fingerprint to
11922 the "fingerprint" file and to its logs, write it without spaces. Now
11923 it will look like the fingerprints in our bridges documentation,
11924 and confuse fewer users.
11927 - Relays no longer publish a new server descriptor if they change
11928 their MaxAdvertisedBandwidth config option but it doesn't end up
11929 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11930 fixes bug 1026. Patch from Sebastian.
11931 - Avoid leaking memory every time we get a create cell but we have
11932 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11933 fixes bug 1034. Reported by BarkerJr.
11936 Changes in version 0.2.1.18 - 2009-07-24
11937 Tor 0.2.1.18 lays the foundations for performance improvements,
11938 adds status events to help users diagnose bootstrap problems, adds
11939 optional authentication/authorization for hidden services, fixes a
11940 variety of potential anonymity problems, and includes a huge pile of
11941 other features and bug fixes.
11944 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11947 Changes in version 0.2.1.17-rc - 2009-07-07
11948 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
11949 candidate for the 0.2.1.x series. It lays the groundwork for further
11950 client performance improvements, and also fixes a big bug with directory
11951 authorities that were causing them to assign Guard and Stable flags
11954 The Windows bundles also finally include the geoip database that we
11955 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
11956 should actually install Torbutton rather than giving you a cryptic
11957 failure message (oops).
11960 - Clients now use the bandwidth values in the consensus, rather than
11961 the bandwidth values in each relay descriptor. This approach opens
11962 the door to more accurate bandwidth estimates once the directory
11963 authorities start doing active measurements. Implements more of
11967 - When Tor clients restart after 1-5 days, they discard all their
11968 cached descriptors as too old, but they still use the cached
11969 consensus document. This approach is good for robustness, but
11970 bad for performance: since they don't know any bandwidths, they
11971 end up choosing at random rather than weighting their choice by
11972 speed. Fixed by the above feature of putting bandwidths in the
11973 consensus. Bugfix on 0.2.0.x.
11974 - Directory authorities were neglecting to mark relays down in their
11975 internal histories if the relays fall off the routerlist without
11976 ever being found unreachable. So there were relays in the histories
11977 that haven't been seen for eight months, and are listed as being
11978 up for eight months. This wreaked havoc on the "median wfu"
11979 and "median mtbf" calculations, in turn making Guard and Stable
11980 flags very wrong, hurting network performance. Fixes bugs 696 and
11981 969. Bugfix on 0.2.0.6-alpha.
11984 - Serve the DirPortFrontPage page even when we have been approaching
11985 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
11986 - The control port would close the connection before flushing long
11987 replies, such as the network consensus, if a QUIT command was issued
11988 before the reply had completed. Now, the control port flushes all
11989 pending replies before closing the connection. Also fixed a spurious
11990 warning when a QUIT command is issued after a malformed or rejected
11991 AUTHENTICATE command, but before the connection was closed. Patch
11992 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
11993 - When we can't find an intro key for a v2 hidden service descriptor,
11994 fall back to the v0 hidden service descriptor and log a bug message.
11995 Workaround for bug 1024.
11996 - Fix a log message that did not respect the SafeLogging option.
12000 - If we're a relay and we change our IP address, be more verbose
12001 about the reason that made us change. Should help track down
12002 further bugs for relays on dynamic IP addresses.
12005 Changes in version 0.2.0.35 - 2009-06-24
12007 - Avoid crashing in the presence of certain malformed descriptors.
12008 Found by lark, and by automated fuzzing.
12009 - Fix an edge case where a malicious exit relay could convince a
12010 controller that the client's DNS question resolves to an internal IP
12011 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12014 - Finally fix the bug where dynamic-IP relays disappear when their
12015 IP address changes: directory mirrors were mistakenly telling
12016 them their old address if they asked via begin_dir, so they
12017 never got an accurate answer about their new address, so they
12018 just vanished after a day. For belt-and-suspenders, relays that
12019 don't set Address in their config now avoid using begin_dir for
12020 all direct connections. Should fix bugs 827, 883, and 900.
12021 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12022 that would occur on some exit nodes when DNS failures and timeouts
12023 occurred in certain patterns. Fix for bug 957.
12026 - When starting with a cache over a few days old, do not leak
12027 memory for the obsolete router descriptors in it. Bugfix on
12028 0.2.0.33; fixes bug 672.
12029 - Hidden service clients didn't use a cached service descriptor that
12030 was older than 15 minutes, but wouldn't fetch a new one either,
12031 because there was already one in the cache. Now, fetch a v2
12032 descriptor unless the same descriptor was added to the cache within
12033 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12036 Changes in version 0.2.1.16-rc - 2009-06-20
12037 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
12038 a bunch of minor bugs.
12041 - Fix an edge case where a malicious exit relay could convince a
12042 controller that the client's DNS question resolves to an internal IP
12043 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12045 o Major performance improvements (on 0.2.0.x):
12046 - Disable and refactor some debugging checks that forced a linear scan
12047 over the whole server-side DNS cache. These accounted for over 50%
12048 of CPU time on a relatively busy exit node's gprof profile. Found
12050 - Disable some debugging checks that appeared in exit node profile
12054 - Update to the "June 3 2009" ip-to-country file.
12055 - Do not have tor-resolve automatically refuse all .onion addresses;
12056 if AutomapHostsOnResolve is set in your torrc, this will work fine.
12058 o Minor bugfixes (on 0.2.0.x):
12059 - Log correct error messages for DNS-related network errors on
12061 - Fix a race condition that could cause crashes or memory corruption
12062 when running as a server with a controller listening for log
12064 - Avoid crashing when we have a policy specified in a DirPolicy or
12065 SocksPolicy or ReachableAddresses option with ports set on it,
12066 and we re-load the policy. May fix bug 996.
12067 - Hidden service clients didn't use a cached service descriptor that
12068 was older than 15 minutes, but wouldn't fetch a new one either,
12069 because there was already one in the cache. Now, fetch a v2
12070 descriptor unless the same descriptor was added to the cache within
12071 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12073 o Minor bugfixes (on 0.2.1.x):
12074 - Don't warn users about low port and hibernation mix when they
12075 provide a *ListenAddress directive to fix that. Bugfix on
12077 - When switching back and forth between bridge mode, do not start
12078 gathering GeoIP data until two hours have passed.
12079 - Do not complain that the user has requested an excluded node as
12080 an exit when the node is not really an exit. This could happen
12081 because the circuit was for testing, or an introduction point.
12085 Changes in version 0.2.1.15-rc - 2009-05-25
12086 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
12087 series. It fixes a major bug on fast exit relays, as well as a variety
12088 of more minor bugs.
12090 o Major bugfixes (on 0.2.0.x):
12091 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12092 that would occur on some exit nodes when DNS failures and timeouts
12093 occurred in certain patterns. Fix for bug 957.
12095 o Minor bugfixes (on 0.2.0.x):
12096 - Actually return -1 in the error case for read_bandwidth_usage().
12097 Harmless bug, since we currently don't care about the return value
12098 anywhere. Bugfix on 0.2.0.9-alpha.
12099 - Provide a more useful log message if bug 977 (related to buffer
12100 freelists) ever reappears, and do not crash right away.
12101 - Fix an assertion failure on 64-bit platforms when we allocated
12102 memory right up to the end of a memarea, then realigned the memory
12103 one step beyond the end. Fixes a possible cause of bug 930.
12104 - Protect the count of open sockets with a mutex, so we can't
12105 corrupt it when two threads are closing or opening sockets at once.
12106 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
12107 - Don't allow a bridge to publish its router descriptor to a
12108 non-bridge directory authority. Fixes part of bug 932.
12109 - When we change to or from being a bridge, reset our counts of
12110 client usage by country. Fixes bug 932.
12111 - Fix a bug that made stream bandwidth get misreported to the
12113 - Stop using malloc_usable_size() to use more area than we had
12114 actually allocated: it was safe, but made valgrind really unhappy.
12115 - Fix a memory leak when v3 directory authorities load their keys
12116 and cert from disk. Bugfix on 0.2.0.1-alpha.
12118 o Minor bugfixes (on 0.2.1.x):
12119 - Fix use of freed memory when deciding to mark a non-addable
12120 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
12123 Changes in version 0.2.1.14-rc - 2009-04-12
12124 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
12125 series. It begins fixing some major performance problems, and also
12126 finally addresses the bug that was causing relays on dynamic IP
12127 addresses to fall out of the directory.
12130 - Clients replace entry guards that were chosen more than a few months
12131 ago. This change should significantly improve client performance,
12132 especially once more people upgrade, since relays that have been
12133 a guard for a long time are currently overloaded.
12135 o Major bugfixes (on 0.2.0):
12136 - Finally fix the bug where dynamic-IP relays disappear when their
12137 IP address changes: directory mirrors were mistakenly telling
12138 them their old address if they asked via begin_dir, so they
12139 never got an accurate answer about their new address, so they
12140 just vanished after a day. For belt-and-suspenders, relays that
12141 don't set Address in their config now avoid using begin_dir for
12142 all direct connections. Should fix bugs 827, 883, and 900.
12143 - Relays were falling out of the networkstatus consensus for
12144 part of a day if they changed their local config but the
12145 authorities discarded their new descriptor as "not sufficiently
12146 different". Now directory authorities accept a descriptor as changed
12147 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
12148 patch by Sebastian.
12149 - Avoid crashing in the presence of certain malformed descriptors.
12150 Found by lark, and by automated fuzzing.
12153 - When generating circuit events with verbose nicknames for
12154 controllers, try harder to look up nicknames for routers on a
12155 circuit. (Previously, we would look in the router descriptors we had
12156 for nicknames, but not in the consensus.) Partial fix for bug 941.
12157 - If the bridge config line doesn't specify a port, assume 443.
12158 This makes bridge lines a bit smaller and easier for users to
12160 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
12161 bytes (aka 20KB/s), to match our documentation. Also update
12162 directory authorities so they always assign the Fast flag to relays
12163 with 20KB/s of capacity. Now people running relays won't suddenly
12164 find themselves not seeing any use, if the network gets faster
12166 - Update to the "April 3 2009" ip-to-country file.
12169 - Avoid trying to print raw memory to the logs when we decide to
12170 give up on downloading a given relay descriptor. Bugfix on
12172 - In tor-resolve, when the Tor client to use is specified by
12173 <hostname>:<port>, actually use the specified port rather than
12174 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
12175 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
12176 - When starting with a cache over a few days old, do not leak
12177 memory for the obsolete router descriptors in it. Bugfix on
12179 - Avoid double-free on list of successfully uploaded hidden
12180 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
12181 - Change memarea_strndup() implementation to work even when
12182 duplicating a string at the end of a page. This bug was
12183 harmless for now, but could have meant crashes later. Fix by
12184 lark. Bugfix on 0.2.1.1-alpha.
12185 - Limit uploaded directory documents to be 16M rather than 500K.
12186 The directory authorities were refusing v3 consensus votes from
12187 other authorities, since the votes are now 504K. Fixes bug 959;
12188 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
12189 - Directory authorities should never send a 503 "busy" response to
12190 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
12194 Changes in version 0.2.1.13-alpha - 2009-03-09
12195 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
12196 cleanups. We're finally getting close to a release candidate.
12199 - Correctly update the list of which countries we exclude as
12200 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
12201 lark. Bugfix on 0.2.1.6-alpha.
12203 o Minor bugfixes (on 0.2.0.x and earlier):
12204 - Automatically detect MacOSX versions earlier than 10.4.0, and
12205 disable kqueue from inside Tor when running with these versions.
12206 We previously did this from the startup script, but that was no
12207 help to people who didn't use the startup script. Resolves bug 863.
12208 - When we had picked an exit node for a connection, but marked it as
12209 "optional", and it turned out we had no onion key for the exit,
12210 stop wanting that exit and try again. This situation may not
12211 be possible now, but will probably become feasible with proposal
12212 158. Spotted by rovv. Fixes another case of bug 752.
12213 - Clients no longer cache certificates for authorities they do not
12214 recognize. Bugfix on 0.2.0.9-alpha.
12215 - When we can't transmit a DNS request due to a network error, retry
12216 it after a while, and eventually transmit a failing response to
12217 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
12218 - If the controller claimed responsibility for a stream, but that
12219 stream never finished making its connection, it would live
12220 forever in circuit_wait state. Now we close it after SocksTimeout
12221 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
12222 - Drop begin cells to a hidden service if they come from the middle
12223 of a circuit. Patch from lark.
12224 - When we erroneously receive two EXTEND cells for the same circuit
12225 ID on the same connection, drop the second. Patch from lark.
12226 - Fix a crash that occurs on exit nodes when a nameserver request
12227 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
12228 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
12230 - Do not assume that a stack-allocated character array will be
12231 64-bit aligned on platforms that demand that uint64_t access is
12232 aligned. Possible fix for bug 604.
12233 - Parse dates and IPv4 addresses in a locale- and libc-independent
12234 manner, to avoid platform-dependent behavior on malformed input.
12235 - Build correctly when configured to build outside the main source
12236 path. Patch from Michael Gold.
12237 - We were already rejecting relay begin cells with destination port
12238 of 0. Now also reject extend cells with destination port or address
12239 of 0. Suggested by lark.
12241 o Minor bugfixes (on 0.2.1.x):
12242 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
12243 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
12244 - If we're an exit node, scrub the IP address to which we are exiting
12245 in the logs. Bugfix on 0.2.1.8-alpha.
12248 - On Linux, use the prctl call to re-enable core dumps when the user
12250 - New controller event NEWCONSENSUS that lists the networkstatus
12251 lines for every recommended relay. Now controllers like Torflow
12252 can keep up-to-date on which relays they should be using.
12253 - Update to the "February 26 2009" ip-to-country file.
12256 Changes in version 0.2.0.34 - 2009-02-08
12257 Tor 0.2.0.34 features several more security-related fixes. You should
12258 upgrade, especially if you run an exit relay (remote crash) or a
12259 directory authority (remote infinite loop), or you're on an older
12260 (pre-XP) or not-recently-patched Windows (remote exploit).
12262 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
12263 have many known flaws, and nobody should be using them. You should
12264 upgrade. If you're using a Linux or BSD and its packages are obsolete,
12265 stop using those packages and upgrade anyway.
12268 - Fix an infinite-loop bug on handling corrupt votes under certain
12269 circumstances. Bugfix on 0.2.0.8-alpha.
12270 - Fix a temporary DoS vulnerability that could be performed by
12271 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12272 - Avoid a potential crash on exit nodes when processing malformed
12273 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
12274 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12275 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12278 - Fix compilation on systems where time_t is a 64-bit integer.
12279 Patch from Matthias Drochner.
12280 - Don't consider expiring already-closed client connections. Fixes
12281 bug 893. Bugfix on 0.0.2pre20.
12284 Changes in version 0.2.1.12-alpha - 2009-02-08
12285 Tor 0.2.1.12-alpha features several more security-related fixes. You
12286 should upgrade, especially if you run an exit relay (remote crash) or
12287 a directory authority (remote infinite loop), or you're on an older
12288 (pre-XP) or not-recently-patched Windows (remote exploit). It also
12289 includes a big pile of minor bugfixes and cleanups.
12292 - Fix an infinite-loop bug on handling corrupt votes under certain
12293 circumstances. Bugfix on 0.2.0.8-alpha.
12294 - Fix a temporary DoS vulnerability that could be performed by
12295 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12296 - Avoid a potential crash on exit nodes when processing malformed
12297 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
12300 - Let controllers actually ask for the "clients_seen" event for
12301 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
12302 reported by Matt Edman.
12303 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
12305 - Fix a bug in address parsing that was preventing bridges or hidden
12306 service targets from being at IPv6 addresses.
12307 - Solve a bug that kept hardware crypto acceleration from getting
12308 enabled when accounting was turned on. Fixes bug 907. Bugfix on
12310 - Remove a bash-ism from configure.in to build properly on non-Linux
12311 platforms. Bugfix on 0.2.1.1-alpha.
12312 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
12313 headers. Bugfix on 0.2.0.10-alpha.
12314 - Don't consider expiring already-closed client connections. Fixes
12315 bug 893. Bugfix on 0.0.2pre20.
12316 - Fix another interesting corner-case of bug 891 spotted by rovv:
12317 Previously, if two hosts had different amounts of clock drift, and
12318 one of them created a new connection with just the wrong timing,
12319 the other might decide to deprecate the new connection erroneously.
12320 Bugfix on 0.1.1.13-alpha.
12321 - Resolve a very rare crash bug that could occur when the user forced
12322 a nameserver reconfiguration during the middle of a nameserver
12323 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
12324 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
12325 Bugfix on 0.2.1.7-alpha.
12326 - If we're using bridges and our network goes away, be more willing
12327 to forgive our bridges and try again when we get an application
12328 request. Bugfix on 0.2.0.x.
12331 - Support platforms where time_t is 64 bits long. (Congratulations,
12332 NetBSD!) Patch from Matthias Drochner.
12333 - Add a 'getinfo status/clients-seen' controller command, in case
12334 controllers want to hear clients_seen events but connect late.
12337 - Disable GCC's strict alias optimization by default, to avoid the
12338 likelihood of its introducing subtle bugs whenever our code violates
12339 the letter of C99's alias rules.
12342 Changes in version 0.2.0.33 - 2009-01-21
12343 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
12344 useful to users. It also finally fixes a bug where a relay or client
12345 that's been off for many days would take a long time to bootstrap.
12347 This update also fixes an important security-related bug reported by
12348 Ilja van Sprundel. You should upgrade. (We'll send out more details
12349 about the bug once people have had some time to upgrade.)
12352 - Fix a heap-corruption bug that may be remotely triggerable on
12353 some platforms. Reported by Ilja van Sprundel.
12356 - When a stream at an exit relay is in state "resolving" or
12357 "connecting" and it receives an "end" relay cell, the exit relay
12358 would silently ignore the end cell and not close the stream. If
12359 the client never closes the circuit, then the exit relay never
12360 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
12361 reported by "wood".
12362 - When sending CREATED cells back for a given circuit, use a 64-bit
12363 connection ID to find the right connection, rather than an addr:port
12364 combination. Now that we can have multiple OR connections between
12365 the same ORs, it is no longer possible to use addr:port to uniquely
12366 identify a connection.
12367 - Bridge relays that had DirPort set to 0 would stop fetching
12368 descriptors shortly after startup, and then briefly resume
12369 after a new bandwidth test and/or after publishing a new bridge
12370 descriptor. Bridge users that try to bootstrap from them would
12371 get a recent networkstatus but would get descriptors from up to
12372 18 hours earlier, meaning most of the descriptors were obsolete
12373 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12374 - Prevent bridge relays from serving their 'extrainfo' document
12375 to anybody who asks, now that extrainfo docs include potentially
12376 sensitive aggregated client geoip summaries. Bugfix on
12378 - If the cached networkstatus consensus is more than five days old,
12379 discard it rather than trying to use it. In theory it could be
12380 useful because it lists alternate directory mirrors, but in practice
12381 it just means we spend many minutes trying directory mirrors that
12382 are long gone from the network. Also discard router descriptors as
12383 we load them if they are more than five days old, since the onion
12384 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
12387 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12388 could make gcc generate non-functional binary search code. Bugfix
12390 - Build correctly on platforms without socklen_t.
12391 - Compile without warnings on solaris.
12392 - Avoid potential crash on internal error during signature collection.
12393 Fixes bug 864. Patch from rovv.
12394 - Correct handling of possible malformed authority signing key
12395 certificates with internal signature types. Fixes bug 880.
12396 Bugfix on 0.2.0.3-alpha.
12397 - Fix a hard-to-trigger resource leak when logging credential status.
12399 - When we can't initialize DNS because the network is down, do not
12400 automatically stop Tor from starting. Instead, we retry failed
12401 dns_init() every 10 minutes, and change the exit policy to reject
12402 *:* until one succeeds. Fixes bug 691.
12403 - Use 64 bits instead of 32 bits for connection identifiers used with
12404 the controller protocol, to greatly reduce risk of identifier reuse.
12405 - When we're choosing an exit node for a circuit, and we have
12406 no pending streams, choose a good general exit rather than one that
12407 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12408 - Fix another case of assuming, when a specific exit is requested,
12409 that we know more than the user about what hosts it allows.
12410 Fixes one case of bug 752. Patch from rovv.
12411 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12412 seconds. Warn the user if lower values are given in the
12413 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12414 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12415 user if lower values are given in the configuration. Bugfix on
12416 0.1.1.17-rc. Patch by Sebastian.
12417 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12418 the cache because we already had a v0 descriptor with the same ID.
12419 Bugfix on 0.2.0.18-alpha.
12420 - Fix a race condition when freeing keys shared between main thread
12421 and CPU workers that could result in a memory leak. Bugfix on
12422 0.1.0.1-rc. Fixes bug 889.
12423 - Send a valid END cell back when a client tries to connect to a
12424 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12425 840. Patch from rovv.
12426 - Check which hops rendezvous stream cells are associated with to
12427 prevent possible guess-the-streamid injection attacks from
12428 intermediate hops. Fixes another case of bug 446. Based on patch
12430 - If a broken client asks a non-exit router to connect somewhere,
12431 do not even do the DNS lookup before rejecting the connection.
12432 Fixes another case of bug 619. Patch from rovv.
12433 - When a relay gets a create cell it can't decrypt (e.g. because it's
12434 using the wrong onion key), we were dropping it and letting the
12435 client time out. Now actually answer with a destroy cell. Fixes
12436 bug 904. Bugfix on 0.0.2pre8.
12438 o Minor bugfixes (hidden services):
12439 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12440 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12443 - Report the case where all signatures in a detached set are rejected
12444 differently than the case where there is an error handling the
12446 - When we realize that another process has modified our cached
12447 descriptors, print out a more useful error message rather than
12448 triggering an assertion. Fixes bug 885. Patch from Karsten.
12449 - Implement the 0x20 hack to better resist DNS poisoning: set the
12450 case on outgoing DNS requests randomly, and reject responses that do
12451 not match the case correctly. This logic can be disabled with the
12452 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
12453 of servers that do not reliably preserve case in replies. See
12454 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12456 - Check DNS replies for more matching fields to better resist DNS
12458 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12459 compress cells, which are basically all encrypted, compressed, or
12463 Changes in version 0.2.1.11-alpha - 2009-01-20
12464 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
12465 week it will take a long time to bootstrap again" bug. It also fixes
12466 an important security-related bug reported by Ilja van Sprundel. You
12467 should upgrade. (We'll send out more details about the bug once people
12468 have had some time to upgrade.)
12471 - Fix a heap-corruption bug that may be remotely triggerable on
12472 some platforms. Reported by Ilja van Sprundel.
12475 - Discard router descriptors as we load them if they are more than
12476 five days old. Otherwise if Tor is off for a long time and then
12477 starts with cached descriptors, it will try to use the onion
12478 keys in those obsolete descriptors when building circuits. Bugfix
12479 on 0.2.0.x. Fixes bug 887.
12482 - Try to make sure that the version of Libevent we're running with
12483 is binary-compatible with the one we built with. May address bug
12485 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
12486 for bug 905. Bugfix on 0.2.1.7-alpha.
12487 - Add a new --enable-local-appdata configuration switch to change
12488 the default location of the datadir on win32 from APPDATA to
12489 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
12490 entirely. Patch from coderman.
12493 - Make outbound DNS packets respect the OutboundBindAddress setting.
12494 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
12495 - When our circuit fails at the first hop (e.g. we get a destroy
12496 cell back), avoid using that OR connection anymore, and also
12497 tell all the one-hop directory requests waiting for it that they
12498 should fail. Bugfix on 0.2.1.3-alpha.
12499 - In the torify(1) manpage, mention that tsocks will leak your
12503 Changes in version 0.2.1.10-alpha - 2009-01-06
12504 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
12505 would make the bridge relay not so useful if it had DirPort set to 0,
12506 and one that could let an attacker learn a little bit of information
12507 about the bridge's users), and a bug that would cause your Tor relay
12508 to ignore a circuit create request it can't decrypt (rather than reply
12509 with an error). It also fixes a wide variety of other bugs.
12512 - If the cached networkstatus consensus is more than five days old,
12513 discard it rather than trying to use it. In theory it could
12514 be useful because it lists alternate directory mirrors, but in
12515 practice it just means we spend many minutes trying directory
12516 mirrors that are long gone from the network. Helps bug 887 a bit;
12518 - Bridge relays that had DirPort set to 0 would stop fetching
12519 descriptors shortly after startup, and then briefly resume
12520 after a new bandwidth test and/or after publishing a new bridge
12521 descriptor. Bridge users that try to bootstrap from them would
12522 get a recent networkstatus but would get descriptors from up to
12523 18 hours earlier, meaning most of the descriptors were obsolete
12524 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12525 - Prevent bridge relays from serving their 'extrainfo' document
12526 to anybody who asks, now that extrainfo docs include potentially
12527 sensitive aggregated client geoip summaries. Bugfix on
12531 - New controller event "clients_seen" to report a geoip-based summary
12532 of which countries we've seen clients from recently. Now controllers
12533 like Vidalia can show bridge operators that they're actually making
12535 - Build correctly against versions of OpenSSL 0.9.8 or later built
12536 without support for deprecated functions.
12537 - Update to the "December 19 2008" ip-to-country file.
12539 o Minor bugfixes (on 0.2.0.x):
12540 - Authorities now vote for the Stable flag for any router whose
12541 weighted MTBF is at least 5 days, regardless of the mean MTBF.
12542 - Do not remove routers as too old if we do not have any consensus
12543 document. Bugfix on 0.2.0.7-alpha.
12544 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12545 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12546 - When an exit relay resolves a stream address to a local IP address,
12547 do not just keep retrying that same exit relay over and
12548 over. Instead, just close the stream. Addresses bug 872. Bugfix
12549 on 0.2.0.32. Patch from rovv.
12550 - If a hidden service sends us an END cell, do not consider
12551 retrying the connection; just close it. Patch from rovv.
12552 - When we made bridge authorities stop serving bridge descriptors over
12553 unencrypted links, we also broke DirPort reachability testing for
12554 bridges. So bridges with a non-zero DirPort were printing spurious
12555 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
12556 - When a relay gets a create cell it can't decrypt (e.g. because it's
12557 using the wrong onion key), we were dropping it and letting the
12558 client time out. Now actually answer with a destroy cell. Fixes
12559 bug 904. Bugfix on 0.0.2pre8.
12560 - Squeeze 2-5% out of client performance (according to oprofile) by
12561 improving the implementation of some policy-manipulation functions.
12563 o Minor bugfixes (on 0.2.1.x):
12564 - Make get_interface_address() function work properly again; stop
12565 guessing the wrong parts of our address as our address.
12566 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
12567 send on that circuit. Otherwise we might violate the proposal-110
12568 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
12570 - When we're sending non-EXTEND cells to the first hop in a circuit,
12571 for example to use an encrypted directory connection, we don't need
12572 to use RELAY_EARLY cells: the first hop knows what kind of cell
12573 it is, and nobody else can even see the cell type. Conserving
12574 RELAY_EARLY cells makes it easier to cannibalize circuits like
12576 - Stop logging nameserver addresses in reverse order.
12577 - If we are retrying a directory download slowly over and over, do
12578 not automatically give up after the 254th failure. Bugfix on
12580 - Resume reporting accurate "stream end" reasons to the local control
12581 port. They were lost in the changes for Proposal 148. Bugfix on
12584 o Deprecated and removed features:
12585 - The old "tor --version --version" command, which would print out
12586 the subversion "Id" of most of the source files, is now removed. It
12587 turned out to be less useful than we'd expected, and harder to
12590 o Code simplifications and refactoring:
12591 - Change our header file guard macros to be less likely to conflict
12592 with system headers. Adam Langley noticed that we were conflicting
12593 with log.h on Android.
12594 - Tool-assisted documentation cleanup. Nearly every function or
12595 static variable in Tor should have its own documentation now.
12598 Changes in version 0.2.1.9-alpha - 2008-12-25
12599 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
12601 o New directory authorities:
12602 - gabelmoo (the authority run by Karsten Loesing) now has a new
12606 - Never use a connection with a mismatched address to extend a
12607 circuit, unless that connection is canonical. A canonical
12608 connection is one whose address is authenticated by the router's
12609 identity key, either in a NETINFO cell or in a router descriptor.
12610 - Avoid a possible memory corruption bug when receiving hidden service
12611 descriptors. Bugfix on 0.2.1.6-alpha.
12614 - Fix a logic error that would automatically reject all but the first
12615 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
12616 part of bug 813/868. Bug spotted by coderman.
12617 - When a stream at an exit relay is in state "resolving" or
12618 "connecting" and it receives an "end" relay cell, the exit relay
12619 would silently ignore the end cell and not close the stream. If
12620 the client never closes the circuit, then the exit relay never
12621 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
12622 reported by "wood".
12623 - When we can't initialize DNS because the network is down, do not
12624 automatically stop Tor from starting. Instead, retry failed
12625 dns_init() every 10 minutes, and change the exit policy to reject
12626 *:* until one succeeds. Fixes bug 691.
12629 - Give a better error message when an overzealous init script says
12630 "sudo -u username tor --user username". Makes Bug 882 easier for
12632 - When a directory authority gives us a new guess for our IP address,
12633 log which authority we used. Hopefully this will help us debug
12634 the recent complaints about bad IP address guesses.
12635 - Detect svn revision properly when we're using git-svn.
12636 - Try not to open more than one descriptor-downloading connection
12637 to an authority at once. This should reduce load on directory
12638 authorities. Fixes bug 366.
12639 - Add cross-certification to newly generated certificates, so that
12640 a signing key is enough information to look up a certificate.
12641 Partial implementation of proposal 157.
12642 - Start serving certificates by <identity digest, signing key digest>
12643 pairs. Partial implementation of proposal 157.
12644 - Clients now never report any stream end reason except 'MISC'.
12645 Implements proposal 148.
12646 - On platforms with a maximum syslog string length, truncate syslog
12647 messages to that length ourselves, rather than relying on the
12648 system to do it for us.
12649 - Optimize out calls to time(NULL) that occur for every IO operation,
12650 or for every cell. On systems where time() is a slow syscall,
12651 this fix will be slightly helpful.
12652 - Exit servers can now answer resolve requests for ip6.arpa addresses.
12653 - When we download a descriptor that we then immediately (as
12654 a directory authority) reject, do not retry downloading it right
12655 away. Should save some bandwidth on authorities. Fix for bug
12656 888. Patch by Sebastian Hahn.
12657 - When a download gets us zero good descriptors, do not notify
12658 Tor that new directory information has arrived.
12659 - Avoid some nasty corner cases in the logic for marking connections
12660 as too old or obsolete or noncanonical for circuits. Partial
12663 o Minor features (controller):
12664 - New CONSENSUS_ARRIVED event to note when a new consensus has
12665 been fetched and validated.
12666 - When we realize that another process has modified our cached
12667 descriptors file, print out a more useful error message rather
12668 than triggering an assertion. Fixes bug 885. Patch from Karsten.
12669 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
12670 controllers to prevent SIGHUP from reloading the
12671 configuration. Fixes bug 856.
12674 - Resume using the correct "REASON=" stream when telling the
12675 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
12676 - When a canonical connection appears later in our internal list
12677 than a noncanonical one for a given OR ID, always use the
12678 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
12680 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12681 seconds. Warn the user if lower values are given in the
12682 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12683 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12684 user if lower values are given in the configuration. Bugfix on
12685 0.1.1.17-rc. Patch by Sebastian.
12686 - Fix a race condition when freeing keys shared between main thread
12687 and CPU workers that could result in a memory leak. Bugfix on
12688 0.1.0.1-rc. Fixes bug 889.
12690 o Minor bugfixes (hidden services):
12691 - Do not throw away existing introduction points on SIGHUP (bugfix on
12692 0.0.6pre1); also, do not stall hidden services because we're
12693 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
12694 by John Brooks. Patch by Karsten. Fixes bug 874.
12695 - Fix a memory leak when we decline to add a v2 rendezvous
12696 descriptor to the cache because we already had a v0 descriptor
12697 with the same ID. Bugfix on 0.2.0.18-alpha.
12699 o Deprecated and removed features:
12700 - RedirectExits has been removed. It was deprecated since
12702 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
12703 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
12704 - Cell pools are now always enabled; --disable-cell-pools is ignored.
12706 o Code simplifications and refactoring:
12707 - Rename the confusing or_is_obsolete field to the more appropriate
12708 is_bad_for_new_circs, and move it to or_connection_t where it
12710 - Move edge-only flags from connection_t to edge_connection_t: not
12711 only is this better coding, but on machines of plausible alignment,
12712 it should save 4-8 bytes per connection_t. "Every little bit helps."
12713 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
12714 for consistency; keep old option working for backward compatibility.
12715 - Simplify the code for finding connections to use for a circuit.
12718 Changes in version 0.2.1.8-alpha - 2008-12-08
12719 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
12720 builds better on unusual platforms like Solaris and old OS X, and
12721 fixes a variety of other issues.
12724 - New DirPortFrontPage option that takes an html file and publishes
12725 it as "/" on the DirPort. Now relay operators can provide a
12726 disclaimer without needing to set up a separate webserver. There's
12727 a sample disclaimer in contrib/tor-exit-notice.html.
12730 - When the client is choosing entry guards, now it selects at most
12731 one guard from a given relay family. Otherwise we could end up with
12732 all of our entry points into the network run by the same operator.
12733 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
12736 - Fix a DOS opportunity during the voting signature collection process
12737 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12738 - Fix a possible segfault when establishing an exit connection. Bugfix
12742 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
12744 - Made Tor a little less aggressive about deleting expired
12745 certificates. Partial fix for bug 854.
12746 - Stop doing unaligned memory access that generated bus errors on
12747 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
12748 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
12749 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
12750 - Make USR2 log-level switch take effect immediately. Bugfix on
12752 - If one win32 nameserver fails to get added, continue adding the
12753 rest, and don't automatically fail.
12754 - Use fcntl() for locking when flock() is not available. Should fix
12755 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
12756 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12757 could make gcc generate non-functional binary search code. Bugfix
12759 - Build correctly on platforms without socklen_t.
12760 - Avoid potential crash on internal error during signature collection.
12761 Fixes bug 864. Patch from rovv.
12762 - Do not use C's stdio library for writing to log files. This will
12763 improve logging performance by a minute amount, and will stop
12764 leaking fds when our disk is full. Fixes bug 861.
12765 - Stop erroneous use of O_APPEND in cases where we did not in fact
12766 want to re-seek to the end of a file before every last write().
12767 - Correct handling of possible malformed authority signing key
12768 certificates with internal signature types. Fixes bug 880. Bugfix
12770 - Fix a hard-to-trigger resource leak when logging credential status.
12774 - Directory mirrors no longer fetch the v1 directory or
12775 running-routers files. They are obsolete, and nobody asks for them
12776 anymore. This is the first step to making v1 authorities obsolete.
12778 o Minor features (controller):
12779 - Return circuit purposes in response to GETINFO circuit-status. Fixes
12783 Changes in version 0.2.0.32 - 2008-11-20
12784 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12785 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12786 a smaller security flaw that might allow an attacker to access local
12787 services, further improves hidden service performance, and fixes a
12788 variety of other issues.
12791 - The "User" and "Group" config options did not clear the
12792 supplementary group entries for the Tor process. The "User" option
12793 is now more robust, and we now set the groups to the specified
12794 user's primary group. The "Group" option is now ignored. For more
12795 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12796 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12797 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12798 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12799 consistently obeyed: if an exit relay refuses a stream because its
12800 exit policy doesn't allow it, we would remember what IP address
12801 the relay said the destination address resolves to, even if it's
12802 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12805 - Fix a DOS opportunity during the voting signature collection process
12806 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12808 o Major bugfixes (hidden services):
12809 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12810 we were failing the whole hidden service request when the v0
12811 descriptor fetch fails, even if the v2 fetch is still pending and
12812 might succeed. Similarly, if the last v2 fetch fails, we were
12813 failing the whole hidden service request even if a v0 fetch is
12814 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12815 - When extending a circuit to a hidden service directory to upload a
12816 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12817 requests failed, because the router descriptor has not been
12818 downloaded yet. In these cases, do not attempt to upload the
12819 rendezvous descriptor, but wait until the router descriptor is
12820 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12821 descriptor from a hidden service directory for which the router
12822 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12826 - Fix several infrequent memory leaks spotted by Coverity.
12827 - When testing for libevent functions, set the LDFLAGS variable
12828 correctly. Found by Riastradh.
12829 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12830 bootstrapping with tunneled directory connections. Bugfix on
12831 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12832 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12833 and we know that server B rejects most-but-not all connections to
12834 port 80, we would previously reject the connection. Now, we assume
12835 the user knows what they were asking for. Fixes bug 752. Bugfix
12836 on 0.0.9rc5. Diagnosed by BarkerJr.
12837 - If we overrun our per-second write limits a little, count this as
12838 having used up our write allocation for the second, and choke
12839 outgoing directory writes. Previously, we had only counted this when
12840 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12841 Bugfix on 0.2.0.x (??).
12842 - Remove the old v2 directory authority 'lefkada' from the default
12843 list. It has been gone for many months.
12844 - Stop doing unaligned memory access that generated bus errors on
12845 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12846 - Make USR2 log-level switch take effect immediately. Bugfix on
12849 o Minor bugfixes (controller):
12850 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12851 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12854 Changes in version 0.2.1.7-alpha - 2008-11-08
12855 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
12856 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12857 a smaller security flaw that might allow an attacker to access local
12858 services, adds better defense against DNS poisoning attacks on exit
12859 relays, further improves hidden service performance, and fixes a
12860 variety of other issues.
12863 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12864 consistently obeyed: if an exit relay refuses a stream because its
12865 exit policy doesn't allow it, we would remember what IP address
12866 the relay said the destination address resolves to, even if it's
12867 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12868 - The "User" and "Group" config options did not clear the
12869 supplementary group entries for the Tor process. The "User" option
12870 is now more robust, and we now set the groups to the specified
12871 user's primary group. The "Group" option is now ignored. For more
12872 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12873 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12874 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
12875 - Do not use or believe expired v3 authority certificates. Patch
12876 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
12879 - Now NodeFamily and MyFamily config options allow spaces in
12880 identity fingerprints, so it's easier to paste them in.
12881 Suggested by Lucky Green.
12882 - Implement the 0x20 hack to better resist DNS poisoning: set the
12883 case on outgoing DNS requests randomly, and reject responses that do
12884 not match the case correctly. This logic can be disabled with the
12885 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
12886 of servers that do not reliably preserve case in replies. See
12887 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12889 - Preserve case in replies to DNSPort requests in order to support
12890 the 0x20 hack for resisting DNS poisoning attacks.
12892 o Hidden service performance improvements:
12893 - When the client launches an introduction circuit, retry with a
12894 new circuit after 30 seconds rather than 60 seconds.
12895 - Launch a second client-side introduction circuit in parallel
12896 after a delay of 15 seconds (based on work by Christian Wilms).
12897 - Hidden services start out building five intro circuits rather
12898 than three, and when the first three finish they publish a service
12899 descriptor using those. Now we publish our service descriptor much
12900 faster after restart.
12903 - Minor fix in the warning messages when you're having problems
12904 bootstrapping; also, be more forgiving of bootstrap problems when
12905 we're still making incremental progress on a given bootstrap phase.
12906 - When we're choosing an exit node for a circuit, and we have
12907 no pending streams, choose a good general exit rather than one that
12908 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12909 - Send a valid END cell back when a client tries to connect to a
12910 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12911 840. Patch from rovv.
12912 - If a broken client asks a non-exit router to connect somewhere,
12913 do not even do the DNS lookup before rejecting the connection.
12914 Fixes another case of bug 619. Patch from rovv.
12915 - Fix another case of assuming, when a specific exit is requested,
12916 that we know more than the user about what hosts it allows.
12917 Fixes another case of bug 752. Patch from rovv.
12918 - Check which hops rendezvous stream cells are associated with to
12919 prevent possible guess-the-streamid injection attacks from
12920 intermediate hops. Fixes another case of bug 446. Based on patch
12922 - Avoid using a negative right-shift when comparing 32-bit
12923 addresses. Possible fix for bug 845 and bug 811.
12924 - Make the assert_circuit_ok() function work correctly on circuits that
12925 have already been marked for close.
12926 - Fix read-off-the-end-of-string error in unit tests when decoding
12927 introduction points.
12928 - Fix uninitialized size field for memory area allocation: may improve
12929 memory performance during directory parsing.
12930 - Treat duplicate certificate fetches as failures, so that we do
12931 not try to re-fetch an expired certificate over and over and over.
12932 - Do not say we're fetching a certificate when we'll in fact skip it
12933 because of a pending download.
12936 Changes in version 0.2.1.6-alpha - 2008-09-30
12937 Tor 0.2.1.6-alpha further improves performance and robustness of
12938 hidden services, starts work on supporting per-country relay selection,
12939 and fixes a variety of smaller issues.
12942 - Implement proposal 121: make it possible to build hidden services
12943 that only certain clients are allowed to connect to. This is
12944 enforced at several points, so that unauthorized clients are unable
12945 to send INTRODUCE cells to the service, or even (depending on the
12946 type of authentication) to learn introduction points. This feature
12947 raises the bar for certain kinds of active attacks against hidden
12948 services. Code by Karsten Loesing.
12949 - Relays now store and serve v2 hidden service descriptors by default,
12950 i.e., the new default value for HidServDirectoryV2 is 1. This is
12951 the last step in proposal 114, which aims to make hidden service
12952 lookups more reliable.
12953 - Start work to allow node restrictions to include country codes. The
12954 syntax to exclude nodes in a country with country code XX is
12955 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
12956 refinement to decide what config options should take priority if
12957 you ask to both use a particular node and exclude it.
12958 - Allow ExitNodes list to include IP ranges and country codes, just
12959 like the Exclude*Nodes lists. Patch from Robert Hogan.
12962 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
12963 Tor to fail to start if you had it configured to use a bridge
12964 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
12965 - When extending a circuit to a hidden service directory to upload a
12966 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12967 requests failed, because the router descriptor had not been
12968 downloaded yet. In these cases, we now wait until the router
12969 descriptor is downloaded, and then retry. Likewise, clients
12970 now skip over a hidden service directory if they don't yet have
12971 its router descriptor, rather than futilely requesting it and
12972 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
12974 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12975 we were failing the whole hidden service request when the v0
12976 descriptor fetch fails, even if the v2 fetch is still pending and
12977 might succeed. Similarly, if the last v2 fetch fails, we were
12978 failing the whole hidden service request even if a v0 fetch is
12979 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12980 - DNS replies need to have names matching their requests, but
12981 these names should be in the questions section, not necessarily
12982 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
12985 - Update to the "September 1 2008" ip-to-country file.
12986 - Allow ports 465 and 587 in the default exit policy again. We had
12987 rejected them in 0.1.0.15, because back in 2005 they were commonly
12988 misconfigured and ended up as spam targets. We hear they are better
12989 locked down these days.
12990 - Use a lockfile to make sure that two Tor processes are not
12991 simultaneously running with the same datadir.
12992 - Serve the latest v3 networkstatus consensus via the control
12993 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
12994 - Better logging about stability/reliability calculations on directory
12996 - Drop the requirement to have an open dir port for storing and
12997 serving v2 hidden service descriptors.
12998 - Directory authorities now serve a /tor/dbg-stability.txt URL to
12999 help debug WFU and MTBF calculations.
13000 - Implement most of Proposal 152: allow specialized servers to permit
13001 single-hop circuits, and clients to use those servers to build
13002 single-hop circuits when using a specialized controller. Patch
13003 from Josh Albrecht. Resolves feature request 768.
13004 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13005 people find host:port too confusing.
13006 - Make TrackHostExit mappings expire a while after their last use, not
13007 after their creation. Patch from Robert Hogan.
13008 - Provide circuit purposes along with circuit events to the controller.
13011 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
13013 - Fixed some memory leaks -- some quite frequent, some almost
13014 impossible to trigger -- based on results from Coverity.
13015 - When testing for libevent functions, set the LDFLAGS variable
13016 correctly. Found by Riastradh.
13017 - Fix an assertion bug in parsing policy-related options; possible fix
13019 - Catch and report a few more bootstrapping failure cases when Tor
13020 fails to establish a TCP connection. Cleanup on 0.2.1.x.
13021 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13022 bootstrapping with tunneled directory connections. Bugfix on
13023 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13024 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13025 and we know that server B rejects most-but-not all connections to
13026 port 80, we would previously reject the connection. Now, we assume
13027 the user knows what they were asking for. Fixes bug 752. Bugfix
13028 on 0.0.9rc5. Diagnosed by BarkerJr.
13029 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13030 service directories if they have no advertised dir port. Bugfix
13032 - If we overrun our per-second write limits a little, count this as
13033 having used up our write allocation for the second, and choke
13034 outgoing directory writes. Previously, we had only counted this when
13035 we had met our limits precisely. Fixes bug 824. Patch by rovv.
13036 Bugfix on 0.2.0.x (??).
13037 - Avoid a "0 divided by 0" calculation when calculating router uptime
13038 at directory authorities. Bugfix on 0.2.0.8-alpha.
13039 - Make DNS resolved controller events into "CLOSED", not
13040 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13042 - Fix a bug where an unreachable relay would establish enough
13043 reachability testing circuits to do a bandwidth test -- if
13044 we already have a connection to the middle hop of the testing
13045 circuit, then it could establish the last hop by using the existing
13046 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13047 circuits no longer use entry guards in 0.2.1.3-alpha.
13048 - If we have correct permissions on $datadir, we complain to stdout
13049 and fail to start. But dangerous permissions on
13050 $datadir/cached-status/ would cause us to open a log and complain
13051 there. Now complain to stdout and fail to start in both cases. Fixes
13052 bug 820, reported by seeess.
13053 - Remove the old v2 directory authority 'lefkada' from the default
13054 list. It has been gone for many months.
13056 o Code simplifications and refactoring:
13057 - Revise the connection_new functions so that a more typesafe variant
13058 exists. This will work better with Coverity, and let us find any
13059 actual mistakes we're making here.
13060 - Refactor unit testing logic so that dmalloc can be used sensibly
13061 with unit tests to check for memory leaks.
13062 - Move all hidden-service related fields from connection and circuit
13063 structure to substructures: this way they won't eat so much memory.
13066 Changes in version 0.2.0.31 - 2008-09-03
13067 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13068 a big bug we're seeing where in rare cases traffic from one Tor stream
13069 gets mixed into another stream, and fixes a variety of smaller issues.
13072 - Make sure that two circuits can never exist on the same connection
13073 with the same circuit ID, even if one is marked for close. This
13074 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
13075 - Relays now reject risky extend cells: if the extend cell includes
13076 a digest of all zeroes, or asks to extend back to the relay that
13077 sent the extend cell, tear down the circuit. Ideas suggested
13079 - If not enough of our entry guards are available so we add a new
13080 one, we might use the new one even if it overlapped with the
13081 current circuit's exit relay (or its family). Anonymity bugfix
13082 pointed out by rovv.
13085 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13086 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13087 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13088 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13089 - Pick size of default geoip filename string correctly on windows.
13090 Fixes bug 806. Bugfix on 0.2.0.30.
13091 - Make the autoconf script accept the obsolete --with-ssl-dir
13092 option as an alias for the actually-working --with-openssl-dir
13093 option. Fix the help documentation to recommend --with-openssl-dir.
13094 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13095 - When using the TransPort option on OpenBSD, and using the User
13096 option to change UID and drop privileges, make sure to open
13097 /dev/pf before dropping privileges. Fixes bug 782. Patch from
13098 Christopher Davis. Bugfix on 0.1.2.1-alpha.
13099 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13100 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13101 on the client side when connecting to a hidden service. Bugfix
13102 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13103 - When closing an application-side connection because its circuit is
13104 getting torn down, generate the stream event correctly. Bugfix on
13105 0.1.2.x. Anonymous patch.
13108 Changes in version 0.2.1.5-alpha - 2008-08-31
13109 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
13110 in a lot of the infrastructure for adding authorization to hidden
13111 services, lays the groundwork for having clients read their load
13112 balancing information out of the networkstatus consensus rather than
13113 the individual router descriptors, addresses two potential anonymity
13114 issues, and fixes a variety of smaller issues.
13117 - Convert many internal address representations to optionally hold
13119 - Generate and accept IPv6 addresses in many protocol elements.
13120 - Make resolver code handle nameservers located at ipv6 addresses.
13121 - Begin implementation of proposal 121 ("Client authorization for
13122 hidden services"): configure hidden services with client
13123 authorization, publish descriptors for them, and configure
13124 authorization data for hidden services at clients. The next
13125 step is to actually access hidden services that perform client
13127 - More progress toward proposal 141: Network status consensus
13128 documents and votes now contain bandwidth information for each
13129 router and a summary of that router's exit policy. Eventually this
13130 will be used by clients so that they do not have to download every
13131 known descriptor before building circuits.
13133 o Major bugfixes (on 0.2.0.x and before):
13134 - When sending CREATED cells back for a given circuit, use a 64-bit
13135 connection ID to find the right connection, rather than an addr:port
13136 combination. Now that we can have multiple OR connections between
13137 the same ORs, it is no longer possible to use addr:port to uniquely
13138 identify a connection.
13139 - Relays now reject risky extend cells: if the extend cell includes
13140 a digest of all zeroes, or asks to extend back to the relay that
13141 sent the extend cell, tear down the circuit. Ideas suggested
13143 - If not enough of our entry guards are available so we add a new
13144 one, we might use the new one even if it overlapped with the
13145 current circuit's exit relay (or its family). Anonymity bugfix
13146 pointed out by rovv.
13149 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13150 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13151 - When using the TransPort option on OpenBSD, and using the User
13152 option to change UID and drop privileges, make sure to open /dev/pf
13153 before dropping privileges. Fixes bug 782. Patch from Christopher
13154 Davis. Bugfix on 0.1.2.1-alpha.
13155 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13156 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13157 - Add a missing safe_str() call for a debug log message.
13158 - Use 64 bits instead of 32 bits for connection identifiers used with
13159 the controller protocol, to greatly reduce risk of identifier reuse.
13160 - Make the autoconf script accept the obsolete --with-ssl-dir
13161 option as an alias for the actually-working --with-openssl-dir
13162 option. Fix the help documentation to recommend --with-openssl-dir.
13163 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13166 - Rate-limit too-many-sockets messages: when they happen, they happen
13167 a lot. Resolves bug 748.
13168 - Resist DNS poisoning a little better by making sure that names in
13169 answer sections match.
13170 - Print the SOCKS5 error message string as well as the error code
13171 when a tor-resolve request fails. Patch from Jacob.
13174 Changes in version 0.2.1.4-alpha - 2008-08-04
13175 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
13178 - The address part of exit policies was not correctly written
13179 to router descriptors. This generated router descriptors that failed
13180 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
13182 - Tor triggered a false assert when extending a circuit to a relay
13183 but we already have a connection open to that relay. Noticed by
13184 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
13187 - Fix a hidden service logging bug: in some edge cases, the router
13188 descriptor of a previously picked introduction point becomes
13189 obsolete and we need to give up on it rather than continually
13190 complaining that it has become obsolete. Observed by xiando. Bugfix
13193 o Removed features:
13194 - Take out the TestVia config option, since it was a workaround for
13195 a bug that was fixed in Tor 0.1.1.21.
13198 Changes in version 0.2.1.3-alpha - 2008-08-03
13199 Tor 0.2.1.3-alpha implements most of the pieces to prevent
13200 infinite-length circuit attacks (see proposal 110); fixes a bug that
13201 might cause exit relays to corrupt streams they send back; allows
13202 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
13203 ExcludeExitNodes config options; and fixes a big pile of bugs.
13205 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
13206 - Send a bootstrap problem "warn" event on the first problem if the
13207 reason is NO_ROUTE (that is, our network is down).
13210 - Implement most of proposal 110: The first K cells to be sent
13211 along a circuit are marked as special "early" cells; only K "early"
13212 cells will be allowed. Once this code is universal, we can block
13213 certain kinds of DOS attack by requiring that EXTEND commands must
13214 be sent using an "early" cell.
13217 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13218 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13219 on the client side when connecting to a hidden service. Bugfix
13220 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13221 - Ensure that two circuits can never exist on the same connection
13222 with the same circuit ID, even if one is marked for close. This
13223 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13226 - When relays do their initial bandwidth measurement, don't limit
13227 to just our entry guards for the test circuits. Otherwise we tend
13228 to have multiple test circuits going through a single entry guard,
13229 which makes our bandwidth test less accurate. Fixes part of bug 654;
13230 patch contributed by Josh Albrecht.
13231 - Add an ExcludeExitNodes option so users can list a set of nodes
13232 that should be be excluded from the exit node position, but
13233 allowed elsewhere. Implements proposal 151.
13234 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
13235 ExcludeNodes and ExcludeExitNodes lists.
13236 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
13237 be more efficient. Formerly it was quadratic in the number of
13238 servers; now it should be linear. Fixes bug 509.
13239 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
13240 and n_conn_id_digest fields into a separate structure that's
13241 only needed when the circuit has not yet attached to an n_conn.
13244 - Change the contrib/tor.logrotate script so it makes the new
13245 logs as "_tor:_tor" rather than the default, which is generally
13246 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13247 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13248 warnings (occasionally), but it can also cause the compiler to
13249 eliminate error-checking code. Suggested by Peter Gutmann.
13250 - When a hidden service is giving up on an introduction point candidate
13251 that was not included in the last published rendezvous descriptor,
13252 don't reschedule publication of the next descriptor. Fixes bug 763.
13254 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
13255 HiddenServiceExcludeNodes as obsolete: they never worked properly,
13256 and nobody claims to be using them. Fixes bug 754. Bugfix on
13257 0.1.0.1-rc. Patch from Christian Wilms.
13258 - Fix a small alignment and memory-wasting bug on buffer chunks.
13261 o Minor bugfixes (controller):
13262 - When closing an application-side connection because its circuit
13263 is getting torn down, generate the stream event correctly.
13264 Bugfix on 0.1.2.x. Anonymous patch.
13266 o Removed features:
13267 - Remove all backward-compatibility code to support relays running
13268 versions of Tor so old that they no longer work at all on the
13272 Changes in version 0.2.0.30 - 2008-07-15
13274 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13275 warnings (occasionally), but it can also cause the compiler to
13276 eliminate error-checking code. Suggested by Peter Gutmann.
13279 Changes in version 0.2.0.29-rc - 2008-07-08
13280 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
13281 hidden-service performance bugs, and fixes a bunch of smaller bugs.
13284 - If you have more than one bridge but don't know their keys,
13285 you would only launch a request for the descriptor of the first one
13286 on your list. (Tor considered launching requests for the others, but
13287 found that it already had a connection on the way for $0000...0000
13288 so it didn't open another.) Bugfix on 0.2.0.x.
13289 - If you have more than one bridge but don't know their keys, and the
13290 connection to one of the bridges failed, you would cancel all
13291 pending bridge connections. (After all, they all have the same
13292 digest.) Bugfix on 0.2.0.x.
13293 - When a hidden service was trying to establish an introduction point,
13294 and Tor had built circuits preemptively for such purposes, we
13295 were ignoring all the preemptive circuits and launching a new one
13296 instead. Bugfix on 0.2.0.14-alpha.
13297 - When a hidden service was trying to establish an introduction point,
13298 and Tor *did* manage to reuse one of the preemptively built
13299 circuits, it didn't correctly remember which one it used,
13300 so it asked for another one soon after, until there were no
13301 more preemptive circuits, at which point it launched one from
13302 scratch. Bugfix on 0.0.9.x.
13303 - Make directory servers include the X-Your-Address-Is: http header in
13304 their responses even for begin_dir conns. Now clients who only
13305 ever use begin_dir connections still have a way to learn their IP
13306 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
13309 - Fix a macro/CPP interaction that was confusing some compilers:
13310 some GCCs don't like #if/#endif pairs inside macro arguments.
13312 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
13313 Fixes bug 704; fix from Steven Murdoch.
13314 - When opening /dev/null in finish_daemonize(), do not pass the
13315 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
13316 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
13317 - Correctly detect transparent proxy support on Linux hosts that
13318 require in.h to be included before netfilter_ipv4.h. Patch
13320 - Disallow session resumption attempts during the renegotiation
13321 stage of the v2 handshake protocol. Clients should never be trying
13322 session resumption at this point, but apparently some did, in
13323 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
13324 found by Geoff Goodell.
13327 Changes in version 0.2.1.2-alpha - 2008-06-20
13328 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
13329 make it easier to set up your own private Tor network; fixes several
13330 big bugs with using more than one bridge relay; fixes a big bug with
13331 offering hidden services quickly after Tor starts; and uses a better
13332 API for reporting potential bootstrapping problems to the controller.
13335 - New TestingTorNetwork config option to allow adjustment of
13336 previously constant values that, while reasonable, could slow
13337 bootstrapping. Implements proposal 135. Patch from Karsten.
13340 - If you have more than one bridge but don't know their digests,
13341 you would only learn a request for the descriptor of the first one
13342 on your list. (Tor considered launching requests for the others, but
13343 found that it already had a connection on the way for $0000...0000
13344 so it didn't open another.) Bugfix on 0.2.0.x.
13345 - If you have more than one bridge but don't know their digests,
13346 and the connection to one of the bridges failed, you would cancel
13347 all pending bridge connections. (After all, they all have the
13348 same digest.) Bugfix on 0.2.0.x.
13349 - When establishing a hidden service, introduction points that
13350 originate from cannibalized circuits are completely ignored and not
13351 included in rendezvous service descriptors. This might be another
13352 reason for delay in making a hidden service available. Bugfix
13353 from long ago (0.0.9.x?)
13356 - Allow OpenSSL to use dynamic locks if it wants.
13357 - When building a consensus, do not include routers that are down.
13358 This will cut down 30% to 40% on consensus size. Implements
13360 - In directory authorities' approved-routers files, allow
13361 fingerprints with or without space.
13362 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13363 controller can query our current bootstrap state in case it attaches
13364 partway through and wants to catch up.
13365 - Send an initial "Starting" bootstrap status event, so we have a
13366 state to start out in.
13369 - Asking for a conditional consensus at .../consensus/<fingerprints>
13370 would crash a dirserver if it did not already have a
13371 consensus. Bugfix on 0.2.1.1-alpha.
13372 - Clean up some macro/CPP interactions: some GCC versions don't like
13373 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
13376 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
13377 - Directory authorities shouldn't complain about bootstrapping
13378 problems just because they do a lot of reachability testing and
13379 some of the connection attempts fail.
13380 - Start sending "count" and "recommendation" key/value pairs in
13381 bootstrap problem status events, so the controller can hear about
13382 problems even before Tor decides they're worth reporting for sure.
13383 - If you're using bridges, generate "bootstrap problem" warnings
13384 as soon as you run out of working bridges, rather than waiting
13385 for ten failures -- which will never happen if you have less than
13387 - If we close our OR connection because there's been a circuit
13388 pending on it for too long, we were telling our bootstrap status
13389 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
13392 Changes in version 0.2.1.1-alpha - 2008-06-13
13393 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
13394 were making the Tor process bloat especially on Linux; makes our TLS
13395 handshake blend in better; sends "bootstrap phase" status events to
13396 the controller, so it can keep the user informed of progress (and
13397 problems) fetching directory information and establishing circuits;
13398 and adds a variety of smaller features.
13401 - More work on making our TLS handshake blend in: modify the list
13402 of ciphers advertised by OpenSSL in client mode to even more
13403 closely resemble a common web browser. We cheat a little so that
13404 we can advertise ciphers that the locally installed OpenSSL doesn't
13406 - Start sending "bootstrap phase" status events to the controller,
13407 so it can keep the user informed of progress fetching directory
13408 information and establishing circuits. Also inform the controller
13409 if we think we're stuck at a particular bootstrap phase. Implements
13411 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13412 cross-platform entropy collection again. We used to use it, then
13413 stopped using it because of a bug that could crash systems that
13414 called RAND_poll when they had a lot of fds open. It looks like the
13415 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13416 at startup, and to call RAND_poll() when we reseed later only if
13417 we have a non-buggy OpenSSL version.
13420 - When we choose to abandon a new entry guard because we think our
13421 older ones might be better, close any circuits pending on that
13422 new entry guard connection. This fix should make us recover much
13423 faster when our network is down and then comes back. Bugfix on
13424 0.1.2.8-beta; found by lodger.
13426 o Memory fixes and improvements:
13427 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13428 to avoid unused RAM in buffer chunks and memory pools.
13429 - Speed up parsing and cut down on memory fragmentation by using
13430 stack-style allocations for parsing directory objects. Previously,
13431 this accounted for over 40% of allocations from within Tor's code
13432 on a typical directory cache.
13433 - Use a Bloom filter rather than a digest-based set to track which
13434 descriptors we need to keep around when we're cleaning out old
13435 router descriptors. This speeds up the computation significantly,
13436 and may reduce fragmentation.
13437 - Reduce the default smartlist size from 32 to 16; it turns out that
13438 most smartlists hold around 8-12 elements tops.
13439 - Make dumpstats() log the fullness and size of openssl-internal
13441 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13442 patch to their OpenSSL, turn it on to save memory on servers. This
13443 patch will (with any luck) get included in a mainline distribution
13445 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13446 compress cells, which are basically all encrypted, compressed,
13450 - Stop reloading the router list from disk for no reason when we
13451 run out of reachable directory mirrors. Once upon a time reloading
13452 it would set the 'is_running' flag back to 1 for them. It hasn't
13453 done that for a long time.
13454 - In very rare situations new hidden service descriptors were
13455 published earlier than 30 seconds after the last change to the
13456 service. (We currently think that a hidden service descriptor
13457 that's been stable for 30 seconds is worth publishing.)
13460 - Allow separate log levels to be configured for different logging
13461 domains. For example, this allows one to log all notices, warnings,
13462 or errors, plus all memory management messages of level debug or
13463 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13464 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13465 and stop using a warning that had become unfixably verbose under
13467 - New --hush command-line option similar to --quiet. While --quiet
13468 disables all logging to the console on startup, --hush limits the
13469 output to messages of warning and error severity.
13470 - Servers support a new URL scheme for consensus downloads that
13471 allows the client to specify which authorities are trusted.
13472 The server then only sends the consensus if the client will trust
13473 it. Otherwise a 404 error is sent back. Clients use this
13474 new scheme when the server supports it (meaning it's running
13475 0.2.1.1-alpha or later). Implements proposal 134.
13476 - New configure/torrc options (--enable-geoip-stats,
13477 DirRecordUsageByCountry) to record how many IPs we've served
13478 directory info to in each country code, how many status documents
13479 total we've sent to each country code, and what share of the total
13480 directory requests we should expect to see.
13481 - Use the TLS1 hostname extension to more closely resemble browser
13483 - Lots of new unit tests.
13484 - Add a macro to implement the common pattern of iterating through
13485 two parallel lists in lockstep.
13488 Changes in version 0.2.0.28-rc - 2008-06-13
13489 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
13490 performance bug, and fixes a bunch of smaller bugs.
13493 - Fix a bug where, when we were choosing the 'end stream reason' to
13494 put in our relay end cell that we send to the exit relay, Tor
13495 clients on Windows were sometimes sending the wrong 'reason'. The
13496 anonymity problem is that exit relays may be able to guess whether
13497 the client is running Windows, thus helping partition the anonymity
13498 set. Down the road we should stop sending reasons to exit relays,
13499 or otherwise prevent future versions of this bug.
13502 - While setting up a hidden service, some valid introduction circuits
13503 were overlooked and abandoned. This might be the reason for
13504 the long delay in making a hidden service available. Bugfix on
13508 - Update to the "June 9 2008" ip-to-country file.
13509 - Run 'make test' as part of 'make dist', so we stop releasing so
13510 many development snapshots that fail their unit tests.
13513 - When we're checking if we have enough dir info for each relay
13514 to begin establishing circuits, make sure that we actually have
13515 the descriptor listed in the consensus, not just any descriptor.
13517 - Bridge relays no longer print "xx=0" in their extrainfo document
13518 for every single country code in the geoip db. Bugfix on
13520 - Only warn when we fail to load the geoip file if we were planning to
13521 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
13522 - If we change our MaxAdvertisedBandwidth and then reload torrc,
13523 Tor won't realize it should publish a new relay descriptor. Fixes
13524 bug 688, reported by mfr. Bugfix on 0.1.2.x.
13525 - When we haven't had any application requests lately, don't bother
13526 logging that we have expired a bunch of descriptors. Bugfix
13528 - Make relay cells written on a connection count as non-padding when
13529 tracking how long a connection has been in use. Bugfix on
13530 0.2.0.1-alpha. Spotted by lodger.
13531 - Fix unit tests in 0.2.0.27-rc.
13532 - Fix compile on Windows.
13535 Changes in version 0.2.0.27-rc - 2008-06-03
13536 Tor 0.2.0.27-rc adds a few features we left out of the earlier
13537 release candidates. In particular, we now include an IP-to-country
13538 GeoIP database, so controllers can easily look up what country a
13539 given relay is in, and so bridge relays can give us some sanitized
13540 summaries about which countries are making use of bridges. (See proposal
13541 126-geoip-fetching.txt for details.)
13544 - Include an IP-to-country GeoIP file in the tarball, so bridge
13545 relays can report sanitized summaries of the usage they're seeing.
13548 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
13549 Robert Hogan. Fixes the first part of bug 681.
13550 - Make bridge authorities never serve extrainfo docs.
13551 - Add support to detect Libevent versions in the 1.4.x series
13553 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
13554 - Include a new contrib/tor-exit-notice.html file that exit relay
13555 operators can put on their website to help reduce abuse queries.
13558 - When tunneling an encrypted directory connection, and its first
13559 circuit fails, do not leave it unattached and ask the controller
13560 to deal. Fixes the second part of bug 681.
13561 - Make bridge authorities correctly expire old extrainfo documents
13565 Changes in version 0.2.0.26-rc - 2008-05-13
13566 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
13567 in Debian's OpenSSL packages. All users running any 0.2.0.x version
13568 should upgrade, whether they're running Debian or not.
13570 o Major security fixes:
13571 - Use new V3 directory authority keys on the tor26, gabelmoo, and
13572 moria1 V3 directory authorities. The old keys were generated with
13573 a vulnerable version of Debian's OpenSSL package, and must be
13574 considered compromised. Other authorities' keys were not generated
13575 with an affected version of OpenSSL.
13578 - List authority signatures as "unrecognized" based on DirServer
13579 lines, not on cert cache. Bugfix on 0.2.0.x.
13582 - Add a new V3AuthUseLegacyKey option to make it easier for
13583 authorities to change their identity keys if they have to.
13586 Changes in version 0.2.0.25-rc - 2008-04-23
13587 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
13590 - Remember to initialize threading before initializing logging.
13591 Otherwise, many BSD-family implementations will crash hard on
13592 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
13595 - Authorities correctly free policies on bad servers on
13596 exit. Fixes bug 672. Bugfix on 0.2.0.x.
13599 Changes in version 0.2.0.24-rc - 2008-04-22
13600 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
13601 v3 directory authority, makes relays with dynamic IP addresses and no
13602 DirPort notice more quickly when their IP address changes, fixes a few
13603 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
13605 o New directory authorities:
13606 - Take lefkada out of the list of v3 directory authorities, since
13607 it has been down for months.
13608 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
13612 - Detect address changes more quickly on non-directory mirror
13613 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
13615 o Minor features (security):
13616 - Reject requests for reverse-dns lookup of names that are in
13617 a private address space. Patch from lodger.
13618 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
13621 o Minor bugfixes (crashes):
13622 - Avoid a rare assert that can trigger when Tor doesn't have much
13623 directory information yet and it tries to fetch a v2 hidden
13624 service descriptor. Fixes bug 651, reported by nwf.
13625 - Initialize log mutex before initializing dmalloc. Otherwise,
13626 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
13627 - Use recursive pthread mutexes in order to avoid deadlock when
13628 logging debug-level messages to a controller. Bug spotted by nwf,
13629 bugfix on 0.2.0.16-alpha.
13631 o Minor bugfixes (resource management):
13632 - Keep address policies from leaking memory: start their refcount
13633 at 1, not 2. Bugfix on 0.2.0.16-alpha.
13634 - Free authority certificates on exit, so they don't look like memory
13635 leaks. Bugfix on 0.2.0.19-alpha.
13636 - Free static hashtables for policy maps and for TLS connections on
13637 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
13638 - Avoid allocating extra space when computing consensuses on 64-bit
13639 platforms. Bug spotted by aakova.
13641 o Minor bugfixes (misc):
13642 - Do not read the configuration file when we've only been told to
13643 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
13644 based on patch from Sebastian Hahn.
13645 - Exit relays that are used as a client can now reach themselves
13646 using the .exit notation, rather than just launching an infinite
13647 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
13648 - When attempting to open a logfile fails, tell us why.
13649 - Fix a dumb bug that was preventing us from knowing that we should
13650 preemptively build circuits to handle expected directory requests.
13651 Fixes bug 660. Bugfix on 0.1.2.x.
13652 - Warn less verbosely about clock skew from netinfo cells from
13653 untrusted sources. Fixes bug 663.
13654 - Make controller stream events for DNS requests more consistent,
13655 by adding "new stream" events for DNS requests, and removing
13656 spurious "stream closed" events" for cached reverse resolves.
13657 Patch from mwenge. Fixes bug 646.
13658 - Correctly notify one-hop connections when a circuit build has
13659 failed. Possible fix for bug 669. Found by lodger.
13662 Changes in version 0.2.0.23-rc - 2008-03-24
13663 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
13664 makes bootstrapping faster if the first directory mirror you contact
13665 is down. The bundles also include the new Vidalia 0.1.2 release.
13668 - When a tunneled directory request is made to a directory server
13669 that's down, notice after 30 seconds rather than 120 seconds. Also,
13670 fail any begindir streams that are pending on it, so they can
13671 retry elsewhere. This was causing multi-minute delays on bootstrap.
13674 Changes in version 0.2.0.22-rc - 2008-03-18
13675 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
13676 enables encrypted directory connections by default for non-relays, fixes
13677 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
13678 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
13681 - Enable encrypted directory connections by default for non-relays,
13682 so censor tools that block Tor directory connections based on their
13683 plaintext patterns will no longer work. This means Tor works in
13684 certain censored countries by default again.
13687 - Make sure servers always request certificates from clients during
13688 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
13689 - Do not enter a CPU-eating loop when a connection is closed in
13690 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
13691 diagnosed by lodger; bugfix on 0.2.0.20-rc.
13692 - Fix assertion failure that could occur when a blocked circuit
13693 became unblocked, and it had pending client DNS requests. Bugfix
13694 on 0.2.0.1-alpha. Fixes bug 632.
13696 o Minor bugfixes (on 0.1.2.x):
13697 - Generate "STATUS_SERVER" events rather than misspelled
13698 "STATUS_SEVER" events. Caught by mwenge.
13699 - When counting the number of bytes written on a TLS connection,
13700 look at the BIO actually used for writing to the network, not
13701 at the BIO used (sometimes) to buffer data for the network.
13702 Looking at different BIOs could result in write counts on the
13703 order of ULONG_MAX. Fixes bug 614.
13704 - On Windows, correctly detect errors when listing the contents of
13705 a directory. Fix from lodger.
13707 o Minor bugfixes (on 0.2.0.x):
13708 - Downgrade "sslv3 alert handshake failure" message to INFO.
13709 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
13710 left BandwidthRate and BandwidthBurst at the default, we would be
13711 silently limited by those defaults. Now raise them to match the
13712 RelayBandwidth* values.
13713 - Fix the SVK version detection logic to work correctly on a branch.
13714 - Make --enable-openbsd-malloc work correctly on Linux with alpha
13715 CPUs. Fixes bug 625.
13716 - Logging functions now check that the passed severity is sane.
13717 - Use proper log levels in the testsuite call of
13718 get_interface_address6().
13719 - When using a nonstandard malloc, do not use the platform values for
13720 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
13721 - Make the openbsd malloc code use 8k pages on alpha CPUs and
13723 - Detect mismatched page sizes when using --enable-openbsd-malloc.
13724 - Avoid double-marked-for-close warning when certain kinds of invalid
13725 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
13726 for bug 617. Bugfix on 0.2.0.1-alpha.
13727 - Make sure that the "NULL-means-reject *:*" convention is followed by
13728 all the policy manipulation functions, avoiding some possible crash
13729 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
13730 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
13731 actually works, and doesn't warn about every single reverse lookup.
13732 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
13735 - Only log guard node status when guard node status has changed.
13736 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
13737 make "INFO" 75% less verbose.
13740 Changes in version 0.2.0.21-rc - 2008-03-02
13741 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
13742 makes Tor work well with Vidalia again, fixes a rare assert bug,
13743 and fixes a pair of more minor bugs. The bundles also include Vidalia
13744 0.1.0 and Torbutton 1.1.16.
13747 - The control port should declare that it requires password auth
13748 when HashedControlSessionPassword is set too. Patch from Matt Edman;
13749 bugfix on 0.2.0.20-rc. Fixes bug 615.
13750 - Downgrade assert in connection_buckets_decrement() to a log message.
13751 This may help us solve bug 614, and in any case will make its
13752 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
13753 - We were sometimes miscounting the number of bytes read from the
13754 network, causing our rate limiting to not be followed exactly.
13755 Bugfix on 0.2.0.16-alpha. Reported by lodger.
13758 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
13759 OpenSSL versions should have been working fine. Diagnosis and patch
13760 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
13761 Bugfix on 0.2.0.20-rc.
13764 Changes in version 0.2.0.20-rc - 2008-02-24
13765 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
13766 makes more progress towards normalizing Tor's TLS handshake, makes
13767 hidden services work better again, helps relays bootstrap if they don't
13768 know their IP address, adds optional support for linking in openbsd's
13769 allocator or tcmalloc, allows really fast relays to scale past 15000
13770 sockets, and fixes a bunch of minor bugs reported by Veracode.
13773 - Enable the revised TLS handshake based on the one designed by
13774 Steven Murdoch in proposal 124, as revised in proposal 130. It
13775 includes version negotiation for OR connections as described in
13776 proposal 105. The new handshake is meant to be harder for censors
13777 to fingerprint, and it adds the ability to detect certain kinds of
13778 man-in-the-middle traffic analysis attacks. The version negotiation
13779 feature will allow us to improve Tor's link protocol more safely
13781 - Choose which bridge to use proportional to its advertised bandwidth,
13782 rather than uniformly at random. This should speed up Tor for
13783 bridge users. Also do this for people who set StrictEntryNodes.
13784 - When a TrackHostExits-chosen exit fails too many times in a row,
13785 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
13788 - Resolved problems with (re-)fetching hidden service descriptors.
13789 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
13790 and 0.2.0.19-alpha.
13791 - If we only ever used Tor for hidden service lookups or posts, we
13792 would stop building circuits and start refusing connections after
13793 24 hours, since we falsely believed that Tor was dormant. Reported
13794 by nwf; bugfix on 0.1.2.x.
13795 - Servers that don't know their own IP address should go to the
13796 authorities for their first directory fetch, even if their DirPort
13797 is off or if they don't know they're reachable yet. This will help
13798 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
13799 - When counting the number of open sockets, count not only the number
13800 of sockets we have received from the socket() call, but also
13801 the number we've gotten from accept() and socketpair(). This bug
13802 made us fail to count all sockets that we were using for incoming
13803 connections. Bugfix on 0.2.0.x.
13804 - Fix code used to find strings within buffers, when those strings
13805 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
13806 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
13807 - Add a new __HashedControlSessionPassword option for controllers
13808 to use for one-off session password hashes that shouldn't get
13809 saved to disk by SAVECONF --- Vidalia users were accumulating a
13810 pile of HashedControlPassword lines in their torrc files, one for
13811 each time they had restarted Tor and then clicked Save. Make Tor
13812 automatically convert "HashedControlPassword" to this new option but
13813 only when it's given on the command line. Partial fix for bug 586.
13815 o Minor features (performance):
13816 - Tune parameters for cell pool allocation to minimize amount of
13818 - Add OpenBSD malloc code from phk as an optional malloc
13819 replacement on Linux: some glibc libraries do very poorly
13820 with Tor's memory allocation patterns. Pass
13821 --enable-openbsd-malloc to get the replacement malloc code.
13822 - Add a --with-tcmalloc option to the configure script to link
13823 against tcmalloc (if present). Does not yet search for
13824 non-system include paths.
13825 - Stop imposing an arbitrary maximum on the number of file descriptors
13826 used for busy servers. Bug reported by Olaf Selke; patch from
13829 o Minor features (other):
13830 - When SafeLogging is disabled, log addresses along with all TLS
13832 - When building with --enable-gcc-warnings, check for whether Apple's
13833 warning "-Wshorten-64-to-32" is available.
13834 - Add a --passphrase-fd argument to the tor-gencert command for
13837 o Minor bugfixes (memory leaks and code problems):
13838 - We were leaking a file descriptor if Tor started with a zero-length
13839 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
13840 - Detect size overflow in zlib code. Reported by Justin Ferguson and
13842 - We were comparing the raw BridgePassword entry with a base64'ed
13843 version of it, when handling a "/tor/networkstatus-bridges"
13844 directory request. Now compare correctly. Noticed by Veracode.
13845 - Recover from bad tracked-since value in MTBF-history file.
13846 Should fix bug 537.
13847 - Alter the code that tries to recover from unhandled write
13848 errors, to not try to flush onto a socket that's given us
13849 unhandled errors. Bugfix on 0.1.2.x.
13850 - Make Unix controlsockets work correctly on OpenBSD. Patch from
13851 tup. Bugfix on 0.2.0.3-alpha.
13853 o Minor bugfixes (other):
13854 - If we have an extra-info document for our server, always make
13855 it available on the control port, even if we haven't gotten
13856 a copy of it from an authority yet. Patch from mwenge.
13857 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
13858 - Directory mirrors no longer include a guess at the client's IP
13859 address if the connection appears to be coming from the same /24
13860 network; it was producing too many wrong guesses.
13861 - Make the new hidden service code respect the SafeLogging setting.
13862 Bugfix on 0.2.0.x. Patch from Karsten.
13863 - When starting as an authority, do not overwrite all certificates
13864 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
13865 - If we're trying to flush the last bytes on a connection (for
13866 example, when answering a directory request), reset the
13867 time-to-give-up timeout every time we manage to write something
13868 on the socket. Bugfix on 0.1.2.x.
13869 - Change the behavior of "getinfo status/good-server-descriptor"
13870 so it doesn't return failure when any authority disappears.
13871 - Even though the man page said that "TrackHostExits ." should
13872 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
13873 - Report TLS "zero return" case as a "clean close" and "IO error"
13874 as a "close". Stop calling closes "unexpected closes": existing
13875 Tors don't use SSL_close(), so having a connection close without
13876 the TLS shutdown handshake is hardly unexpected.
13877 - Send NAMESERVER_STATUS messages for a single failed nameserver
13880 o Code simplifications and refactoring:
13881 - Remove the tor_strpartition function: its logic was confused,
13882 and it was only used for one thing that could be implemented far
13886 Changes in version 0.2.0.19-alpha - 2008-02-09
13887 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
13888 handshake, makes path selection for relays more secure and IP address
13889 guessing more robust, and generally fixes a lot of bugs in preparation
13890 for calling the 0.2.0 branch stable.
13893 - Do not include recognizeable strings in the commonname part of
13894 Tor's x509 certificates.
13897 - If we're a relay, avoid picking ourselves as an introduction point,
13898 a rendezvous point, or as the final hop for internal circuits. Bug
13899 reported by taranis and lodger. Bugfix on 0.1.2.x.
13900 - Patch from "Andrew S. Lists" to catch when we contact a directory
13901 mirror at IP address X and he says we look like we're coming from
13902 IP address X. Bugfix on 0.1.2.x.
13904 o Minor features (security):
13905 - Be more paranoid about overwriting sensitive memory on free(),
13906 as a defensive programming tactic to ensure forward secrecy.
13908 o Minor features (directory authority):
13909 - Actually validate the options passed to AuthDirReject,
13910 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
13911 - Reject router descriptors with out-of-range bandwidthcapacity or
13912 bandwidthburst values.
13914 o Minor features (controller):
13915 - Reject controller commands over 1MB in length. This keeps rogue
13916 processes from running us out of memory.
13918 o Minor features (misc):
13919 - Give more descriptive well-formedness errors for out-of-range
13920 hidden service descriptor/protocol versions.
13921 - Make memory debugging information describe more about history
13922 of cell allocation, so we can help reduce our memory use.
13924 o Deprecated features (controller):
13925 - The status/version/num-versioning and status/version/num-concurring
13926 GETINFO options are no longer useful in the v3 directory protocol:
13927 treat them as deprecated, and warn when they're used.
13930 - When our consensus networkstatus has been expired for a while, stop
13931 being willing to build circuits using it. Fixes bug 401. Bugfix
13933 - Directory caches now fetch certificates from all authorities
13934 listed in a networkstatus consensus, even when they do not
13935 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
13936 - When connecting to a bridge without specifying its key, insert
13937 the connection into the identity-to-connection map as soon as
13938 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
13939 - Detect versions of OS X where malloc_good_size() is present in the
13940 library but never actually declared. Resolves bug 587. Bugfix
13942 - Stop incorrectly truncating zlib responses to directory authority
13943 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
13944 - Stop recommending that every server operator send mail to tor-ops.
13945 Resolves bug 597. Bugfix on 0.1.2.x.
13946 - Don't trigger an assert if we start a directory authority with a
13947 private IP address (like 127.0.0.1).
13948 - Avoid possible failures when generating a directory with routers
13949 with over-long versions strings, or too many flags set. Bugfix
13951 - If an attempt to launch a DNS resolve request over the control
13952 port fails because we have overrun the limit on the number of
13953 connections, tell the controller that the request has failed.
13954 - Avoid using too little bandwidth when our clock skips a few
13955 seconds. Bugfix on 0.1.2.x.
13956 - Fix shell error when warning about missing packages in configure
13957 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
13958 - Do not become confused when receiving a spurious VERSIONS-like
13959 cell from a confused v1 client. Bugfix on 0.2.0.x.
13960 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
13961 introduction points for a hidden service have failed. Patch from
13962 Karsten Loesing. Bugfix on 0.2.0.x.
13964 o Code simplifications and refactoring:
13965 - Remove some needless generality from cpuworker code, for improved
13967 - Stop overloading the circuit_t.onionskin field for both "onionskin
13968 from a CREATE cell that we are waiting for a cpuworker to be
13969 assigned" and "onionskin from an EXTEND cell that we are going to
13970 send to an OR as soon as we are connected". Might help with bug 600.
13971 - Add an in-place version of aes_crypt() so that we can avoid doing a
13972 needless memcpy() call on each cell payload.
13975 Changes in version 0.2.0.18-alpha - 2008-01-25
13976 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
13977 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
13978 that can warn or reject connections to ports generally associated with
13979 vulnerable-plaintext protocols.
13981 o New directory authorities:
13982 - Set up dannenberg (run by CCC) as the sixth v3 directory
13986 - Fix a major memory leak when attempting to use the v2 TLS
13987 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
13988 - We accidentally enabled the under-development v2 TLS handshake
13989 code, which was causing log entries like "TLS error while
13990 renegotiating handshake". Disable it again. Resolves bug 590.
13991 - We were computing the wrong Content-Length: header for directory
13992 responses that need to be compressed on the fly, causing clients
13993 asking for those items to always fail. Bugfix on 0.2.0.x; partially
13997 - Avoid going directly to the directory authorities even if you're a
13998 relay, if you haven't found yourself reachable yet or if you've
13999 decided not to advertise your dirport yet. Addresses bug 556.
14000 - If we've gone 12 hours since our last bandwidth check, and we
14001 estimate we have less than 50KB bandwidth capacity but we could
14002 handle more, do another bandwidth test.
14003 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14004 Tor can warn and/or refuse connections to ports commonly used with
14005 vulnerable-plaintext protocols. Currently we warn on ports 23,
14006 109, 110, and 143, but we don't reject any.
14009 - When we setconf ClientOnly to 1, close any current OR and Dir
14010 listeners. Reported by mwenge.
14011 - When we get a consensus that's been signed by more people than
14012 we expect, don't log about it; it's not a big deal. Reported
14016 - Don't answer "/tor/networkstatus-bridges" directory requests if
14017 the request isn't encrypted.
14018 - Make "ClientOnly 1" config option disable directory ports too.
14019 - Patches from Karsten Loesing to make v2 hidden services more
14020 robust: work even when there aren't enough HSDir relays available;
14021 retry when a v2 rend desc fetch fails; but don't retry if we
14022 already have a usable v0 rend desc.
14025 Changes in version 0.2.0.17-alpha - 2008-01-17
14026 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
14029 - Make the tor-gencert man page get included correctly in the tarball.
14032 Changes in version 0.2.0.16-alpha - 2008-01-17
14033 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
14034 Loesing, and generally cleans up a lot of features and minor bugs.
14036 o New directory authorities:
14037 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
14040 o Major performance improvements:
14041 - Switch our old ring buffer implementation for one more like that
14042 used by free Unix kernels. The wasted space in a buffer with 1mb
14043 of data will now be more like 8k than 1mb. The new implementation
14044 also avoids realloc();realloc(); patterns that can contribute to
14045 memory fragmentation.
14048 - Configuration files now accept C-style strings as values. This
14049 helps encode characters not allowed in the current configuration
14050 file format, such as newline or #. Addresses bug 557.
14051 - Although we fixed bug 539 (where servers would send HTTP status 503
14052 responses _and_ send a body too), there are still servers out
14053 there that haven't upgraded. Therefore, make clients parse such
14054 bodies when they receive them.
14055 - When we're not serving v2 directory information, there is no reason
14056 to actually keep any around. Remove the obsolete files and directory
14057 on startup if they are very old and we aren't going to serve them.
14059 o Minor performance improvements:
14060 - Reference-count and share copies of address policy entries; only 5%
14061 of them were actually distinct.
14062 - Never walk through the list of logs if we know that no log is
14063 interested in a given message.
14066 - When an authority has not signed a consensus, do not try to
14067 download a nonexistent "certificate with key 00000000". Bugfix
14068 on 0.2.0.x. Fixes bug 569.
14069 - Fix a rare assert error when we're closing one of our threads:
14070 use a mutex to protect the list of logs, so we never write to the
14071 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
14072 bug 575, which is kind of the revenge of bug 222.
14073 - Patch from Karsten Loesing to complain less at both the client
14074 and the relay when a relay used to have the HSDir flag but doesn't
14075 anymore, and we try to upload a hidden service descriptor.
14076 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
14078 - Do not try to download missing certificates until we have tried
14079 to check our fallback consensus. Fixes bug 583.
14080 - Make bridges round reported GeoIP stats info up to the nearest
14081 estimate, not down. Now we can distinguish between "0 people from
14082 this country" and "1 person from this country".
14083 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
14084 - Avoid possible segfault if key generation fails in
14085 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
14086 - Avoid segfault in the case where a badly behaved v2 versioning
14087 directory sends a signed networkstatus with missing client-versions.
14089 - Avoid segfaults on certain complex invocations of
14090 router_get_by_hexdigest(). Bugfix on 0.1.2.
14091 - Correct bad index on array access in parse_http_time(). Bugfix
14093 - Fix possible bug in vote generation when server versions are present
14094 but client versions are not.
14095 - Fix rare bug on REDIRECTSTREAM control command when called with no
14096 port set: it could erroneously report an error when none had
14098 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
14099 compressing large objects and find ourselves with more than 4k
14100 left over. Bugfix on 0.2.0.
14101 - Fix a small memory leak when setting up a hidden service.
14102 - Fix a few memory leaks that could in theory happen under bizarre
14104 - Fix an assert if we post a general-purpose descriptor via the
14105 control port but that descriptor isn't mentioned in our current
14106 network consensus. Bug reported by Jon McLachlan; bugfix on
14109 o Minor features (controller):
14110 - Get NS events working again. Patch from tup.
14111 - The GETCONF command now escapes and quotes configuration values
14112 that don't otherwise fit into the torrc file.
14113 - The SETCONF command now handles quoted values correctly.
14115 o Minor features (directory authorities):
14116 - New configuration options to override default maximum number of
14117 servers allowed on a single IP address. This is important for
14118 running a test network on a single host.
14119 - Actually implement the -s option to tor-gencert.
14120 - Add a manual page for tor-gencert.
14122 o Minor features (bridges):
14123 - Bridge authorities no longer serve bridge descriptors over
14124 unencrypted connections.
14126 o Minor features (other):
14127 - Add hidden services and DNSPorts to the list of things that make
14128 Tor accept that it has running ports. Change starting Tor with no
14129 ports from a fatal error to a warning; we might change it back if
14130 this turns out to confuse anybody. Fixes bug 579.
14133 Changes in version 0.1.2.19 - 2008-01-17
14134 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
14135 exit policy a little bit more conservative so it's safer to run an
14136 exit relay on a home system, and fixes a variety of smaller issues.
14139 - Exit policies now reject connections that are addressed to a
14140 relay's public (external) IP address too, unless
14141 ExitPolicyRejectPrivate is turned off. We do this because too
14142 many relays are running nearby to services that trust them based
14143 on network address.
14146 - When the clock jumps forward a lot, do not allow the bandwidth
14147 buckets to become negative. Fixes bug 544.
14148 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14149 on every successful resolve. Reported by Mike Perry.
14150 - Purge old entries from the "rephist" database and the hidden
14151 service descriptor database even when DirPort is zero.
14152 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14153 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14154 crashing or mis-answering these requests.
14155 - When we decide to send a 503 response to a request for servers, do
14156 not then also send the server descriptors: this defeats the whole
14157 purpose. Fixes bug 539.
14160 - Changing the ExitPolicyRejectPrivate setting should cause us to
14161 rebuild our server descriptor.
14162 - Fix handling of hex nicknames when answering controller requests for
14163 networkstatus by name, or when deciding whether to warn about
14164 unknown routers in a config option. (Patch from mwenge.)
14165 - Fix a couple of hard-to-trigger autoconf problems that could result
14166 in really weird results on platforms whose sys/types.h files define
14167 nonstandard integer types.
14168 - Don't try to create the datadir when running --verify-config or
14169 --hash-password. Resolves bug 540.
14170 - If we were having problems getting a particular descriptor from the
14171 directory caches, and then we learned about a new descriptor for
14172 that router, we weren't resetting our failure count. Reported
14174 - Although we fixed bug 539 (where servers would send HTTP status 503
14175 responses _and_ send a body too), there are still servers out there
14176 that haven't upgraded. Therefore, make clients parse such bodies
14177 when they receive them.
14178 - Run correctly on systems where rlim_t is larger than unsigned long.
14179 This includes some 64-bit systems.
14180 - Run correctly on platforms (like some versions of OS X 10.5) where
14181 the real limit for number of open files is OPEN_FILES, not rlim_max
14182 from getrlimit(RLIMIT_NOFILES).
14183 - Avoid a spurious free on base64 failure.
14184 - Avoid segfaults on certain complex invocations of
14185 router_get_by_hexdigest().
14186 - Fix rare bug on REDIRECTSTREAM control command when called with no
14187 port set: it could erroneously report an error when none had
14191 Changes in version 0.2.0.15-alpha - 2007-12-25
14192 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
14193 features added in 0.2.0.13-alpha.
14196 - Fix several remotely triggerable asserts based on DirPort requests
14197 for a v2 or v3 networkstatus object before we were prepared. This
14198 was particularly bad for 0.2.0.13 and later bridge relays, who
14199 would never have a v2 networkstatus and would thus always crash
14200 when used. Bugfixes on 0.2.0.x.
14201 - Estimate the v3 networkstatus size more accurately, rather than
14202 estimating it at zero bytes and giving it artificially high priority
14203 compared to other directory requests. Bugfix on 0.2.0.x.
14206 - Fix configure.in logic for cross-compilation.
14207 - When we load a bridge descriptor from the cache, and it was
14208 previously unreachable, mark it as retriable so we won't just
14209 ignore it. Also, try fetching a new copy immediately. Bugfixes
14211 - The bridge GeoIP stats were counting other relays, for example
14212 self-reachability and authority-reachability tests.
14215 - Support compilation to target iPhone; patch from cjacker huang.
14216 To build for iPhone, pass the --enable-iphone option to configure.
14219 Changes in version 0.2.0.14-alpha - 2007-12-23
14221 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
14222 without a datadirectory from a previous Tor install. Reported
14224 - Fix a crash when we fetch a descriptor that turns out to be
14225 unexpected (it used to be in our networkstatus when we started
14226 fetching it, but it isn't in our current networkstatus), and we
14227 aren't using bridges. Bugfix on 0.2.0.x.
14228 - Fix a crash when accessing hidden services: it would work the first
14229 time you use a given introduction point for your service, but
14230 on subsequent requests we'd be using garbage memory. Fixed by
14231 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
14232 - Fix a crash when we load a bridge descriptor from disk but we don't
14233 currently have a Bridge line for it in our torrc. Bugfix on
14237 - If bridge authorities set BridgePassword, they will serve a
14238 snapshot of known bridge routerstatuses from their DirPort to
14239 anybody who knows that password. Unset by default.
14242 - Make the unit tests build again.
14243 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
14244 - Make PublishServerDescriptor default to 1, so the default doesn't
14245 have to change as we invent new directory protocol versions.
14246 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
14247 be included unless sys/time.h is already included. Fixes
14248 bug 553. Bugfix on 0.2.0.x.
14249 - If we receive a general-purpose descriptor and then receive an
14250 identical bridge-purpose descriptor soon after, don't discard
14251 the next one as a duplicate.
14254 - If BridgeRelay is set to 1, then the default for
14255 PublishServerDescriptor is now "bridge" rather than "v2,v3".
14256 - If the user sets RelayBandwidthRate but doesn't set
14257 RelayBandwidthBurst, then make them equal rather than erroring out.
14260 Changes in version 0.2.0.13-alpha - 2007-12-21
14261 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
14262 Goodell, fixes many more bugs, and adds a lot of infrastructure for
14265 o New directory authorities:
14266 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
14270 - Only update guard status (usable / not usable) once we have
14271 enough directory information. This was causing us to always pick
14272 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
14273 causing us to discard all our guards on startup if we hadn't been
14274 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
14275 - Purge old entries from the "rephist" database and the hidden
14276 service descriptor databases even when DirPort is zero. Bugfix
14278 - We were ignoring our RelayBandwidthRate for the first 30 seconds
14279 after opening a circuit -- even a relayed circuit. Bugfix on
14281 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14282 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14283 crashing or mis-answering these types of requests.
14284 - Relays were publishing their server descriptor to v1 and v2
14285 directory authorities, but they didn't try publishing to v3-only
14286 authorities. Fix this; and also stop publishing to v1 authorities.
14288 - When we were reading router descriptors from cache, we were ignoring
14289 the annotations -- so for example we were reading in bridge-purpose
14290 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
14291 - When we decided to send a 503 response to a request for servers, we
14292 were then also sending the server descriptors: this defeats the
14293 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
14296 - Bridge relays now behave like clients with respect to time
14297 intervals for downloading new consensus documents -- otherwise they
14298 stand out. Bridge users now wait until the end of the interval,
14299 so their bridge relay will be sure to have a new consensus document.
14300 - Three new config options (AlternateDirAuthority,
14301 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14302 user selectively replace the default directory authorities by type,
14303 rather than the all-or-nothing replacement that DirServer offers.
14304 - Tor can now be configured to read a GeoIP file from disk in one
14305 of two formats. This can be used by controllers to map IP addresses
14306 to countries. Eventually, it may support exit-by-country.
14307 - When possible, bridge relays remember which countries users
14308 are coming from, and report aggregate information in their
14309 extra-info documents, so that the bridge authorities can learn
14310 where Tor is blocked.
14311 - Bridge directory authorities now do reachability testing on the
14312 bridges they know. They provide router status summaries to the
14313 controller via "getinfo ns/purpose/bridge", and also dump summaries
14314 to a file periodically.
14315 - Stop fetching directory info so aggressively if your DirPort is
14316 on but your ORPort is off; stop fetching v2 dir info entirely.
14317 You can override these choices with the new FetchDirInfoEarly
14321 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
14322 consensus documents when there are too many relays at a single
14323 IP address. Now clear it in v2 network status documents too, and
14324 also clear it in routerinfo_t when the relay is no longer listed
14325 in the relevant networkstatus document.
14326 - Don't crash if we get an unexpected value for the
14327 PublishServerDescriptor config option. Reported by Matt Edman;
14328 bugfix on 0.2.0.9-alpha.
14329 - Our new v2 hidden service descriptor format allows descriptors
14330 that have no introduction points. But Tor crashed when we tried
14331 to build a descriptor with no intro points (and it would have
14332 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
14333 by Karsten Loesing.
14334 - Fix building with dmalloc 5.5.2 with glibc.
14335 - Reject uploaded descriptors and extrainfo documents if they're
14336 huge. Otherwise we'll cache them all over the network and it'll
14337 clog everything up. Reported by Aljosha Judmayer.
14338 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
14339 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
14340 - When the DANGEROUS_VERSION controller status event told us we're
14341 running an obsolete version, it used the string "OLD" to describe
14342 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
14343 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
14344 - If we can't expand our list of entry guards (e.g. because we're
14345 using bridges or we have StrictEntryNodes set), don't mark relays
14346 down when they fail a directory request. Otherwise we're too quick
14347 to mark all our entry points down. Bugfix on 0.1.2.x.
14348 - Fix handling of hex nicknames when answering controller requests for
14349 networkstatus by name, or when deciding whether to warn about unknown
14350 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
14351 - Fix a couple of hard-to-trigger autoconf problems that could result
14352 in really weird results on platforms whose sys/types.h files define
14353 nonstandard integer types. Bugfix on 0.1.2.x.
14354 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
14355 - Don't crash on name lookup when we have no current consensus. Fixes
14356 bug 538; bugfix on 0.2.0.x.
14357 - Only Tors that want to mirror the v2 directory info should
14358 create the "cached-status" directory in their datadir. (All Tors
14359 used to create it.) Bugfix on 0.2.0.9-alpha.
14360 - Directory authorities should only automatically download Extra Info
14361 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
14364 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14365 consumers. (We already do this on HUP.)
14366 - Authorities and caches fetch the v2 networkstatus documents
14367 less often, now that v3 is encouraged.
14368 - Add a new config option BridgeRelay that specifies you want to
14369 be a bridge relay. Right now the only difference is that it makes
14370 you answer begin_dir requests, and it makes you cache dir info,
14371 even if your DirPort isn't on.
14372 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14373 ask about source, timestamp of arrival, purpose, etc. We need
14374 something like this to help Vidalia not do GeoIP lookups on bridge
14376 - Allow multiple HashedControlPassword config lines, to support
14377 multiple controller passwords.
14378 - Authorities now decide whether they're authoritative for a given
14379 router based on the router's purpose.
14380 - New config options AuthDirBadDir and AuthDirListBadDirs for
14381 authorities to mark certain relays as "bad directories" in the
14382 networkstatus documents. Also supports the "!baddir" directive in
14383 the approved-routers file.
14386 Changes in version 0.2.0.12-alpha - 2007-11-16
14387 This twelfth development snapshot fixes some more build problems as
14388 well as a few minor bugs.
14391 - Make it build on OpenBSD again. Patch from tup.
14392 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
14393 package-building for Red Hat, OS X, etc.
14395 o Minor bugfixes (on 0.1.2.x):
14396 - Changing the ExitPolicyRejectPrivate setting should cause us to
14397 rebuild our server descriptor.
14399 o Minor bugfixes (on 0.2.0.x):
14400 - When we're lacking a consensus, don't try to perform rendezvous
14401 operations. Reported by Karsten Loesing.
14402 - Fix a small memory leak whenever we decide against using a
14403 newly picked entry guard. Reported by Mike Perry.
14404 - When authorities detected more than two relays running on the same
14405 IP address, they were clearing all the status flags but forgetting
14406 to clear the "hsdir" flag. So clients were being told that a
14407 given relay was the right choice for a v2 hsdir lookup, yet they
14408 never had its descriptor because it was marked as 'not running'
14410 - If we're trying to fetch a bridge descriptor and there's no way
14411 the bridge authority could help us (for example, we don't know
14412 a digest, or there is no bridge authority), don't be so eager to
14413 fall back to asking the bridge authority.
14414 - If we're using bridges or have strictentrynodes set, and our
14415 chosen exit is in the same family as all our bridges/entry guards,
14416 then be flexible about families.
14419 - When we negotiate a v2 link-layer connection (not yet implemented),
14420 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14421 negotiated a v1 connection for their next step. Initial code for
14425 Changes in version 0.2.0.11-alpha - 2007-11-12
14426 This eleventh development snapshot fixes some build problems with
14427 the previous snapshot. It also includes a more secure-by-default exit
14428 policy for relays, fixes an enormous memory leak for exit relays, and
14429 fixes another bug where servers were falling out of the directory list.
14432 - Exit policies now reject connections that are addressed to a
14433 relay's public (external) IP address too, unless
14434 ExitPolicyRejectPrivate is turned off. We do this because too
14435 many relays are running nearby to services that trust them based
14436 on network address. Bugfix on 0.1.2.x.
14439 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14440 on every successful resolve. Reported by Mike Perry; bugfix
14442 - On authorities, never downgrade to old router descriptors simply
14443 because they're listed in the consensus. This created a catch-22
14444 where we wouldn't list a new descriptor because there was an
14445 old one in the consensus, and we couldn't get the new one in the
14446 consensus because we wouldn't list it. Possible fix for bug 548.
14447 Also, this might cause bug 543 to appear on authorities; if so,
14448 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
14450 o Packaging fixes on 0.2.0.10-alpha:
14451 - We were including instructions about what to do with the
14452 src/config/fallback-consensus file, but we weren't actually
14453 including it in the tarball. Disable all of that for now.
14456 - Allow people to say PreferTunnelledDirConns rather than
14457 PreferTunneledDirConns, for those alternate-spellers out there.
14460 - Don't reevaluate all the information from our consensus document
14461 just because we've downloaded a v2 networkstatus that we intend
14462 to cache. Fixes bug 545; bugfix on 0.2.0.x.
14465 Changes in version 0.2.0.10-alpha - 2007-11-10
14466 This tenth development snapshot adds a third v3 directory authority
14467 run by Mike Perry, adds most of Karsten Loesing's new hidden service
14468 descriptor format, fixes a bad crash bug and new bridge bugs introduced
14469 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
14470 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
14471 addresses many more minor issues.
14473 o New directory authorities:
14474 - Set up ides (run by Mike Perry) as the third v3 directory authority.
14477 - Allow tunnelled directory connections to ask for an encrypted
14478 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14479 connection independently. Now we can make anonymized begin_dir
14480 connections for (e.g.) more secure hidden service posting and
14482 - More progress on proposal 114: code from Karsten Loesing to
14483 implement new hidden service descriptor format.
14484 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14485 accommodate the growing number of servers that use the default
14486 and are reaching it.
14487 - Directory authorities use a new formula for selecting which nodes
14488 to advertise as Guards: they must be in the top 7/8 in terms of
14489 how long we have known about them, and above the median of those
14490 nodes in terms of weighted fractional uptime.
14491 - Make "not enough dir info yet" warnings describe *why* Tor feels
14492 it doesn't have enough directory info yet.
14495 - Stop servers from crashing if they set a Family option (or
14496 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
14498 - Make bridge users work again -- the move to v3 directories in
14499 0.2.0.9-alpha had introduced a number of bugs that made bridges
14500 no longer work for clients.
14501 - When the clock jumps forward a lot, do not allow the bandwidth
14502 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
14504 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
14505 - When the consensus lists a router descriptor that we previously were
14506 mirroring, but that we considered non-canonical, reload the
14507 descriptor as canonical. This fixes bug 543 where Tor servers
14508 would start complaining after a few days that they don't have
14509 enough directory information to build a circuit.
14510 - Consider replacing the current consensus when certificates arrive
14511 that make the pending consensus valid. Previously, we were only
14512 considering replacement when the new certs _didn't_ help.
14513 - Fix an assert error on startup if we didn't already have the
14514 consensus and certs cached in our datadirectory: we were caching
14515 the consensus in consensus_waiting_for_certs but then free'ing it
14517 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
14518 Request) if we need more v3 certs but we've already got pending
14519 requests for all of them.
14520 - Correctly back off from failing certificate downloads. Fixes
14522 - Authorities don't vote on the Running flag if they have been running
14523 for less than 30 minutes themselves. Fixes bug 547, where a newly
14524 started authority would vote that everyone was down.
14526 o New requirements:
14527 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14528 it, it had no AES, and it hasn't seen any security patches since
14532 - Clients now hold circuitless TLS connections open for 1.5 times
14533 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14534 rebuild a new circuit over them within that timeframe. Previously,
14535 they held them open only for KeepalivePeriod (5 minutes).
14536 - Use "If-Modified-Since" to avoid retrieving consensus
14537 networkstatuses that we already have.
14538 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14539 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14540 we start knowing some directory caches.
14541 - When we receive a consensus from the future, warn about skew.
14542 - Improve skew reporting: try to give the user a better log message
14543 about how skewed they are, and how much this matters.
14544 - When we have a certificate for an authority, believe that
14545 certificate's claims about the authority's IP address.
14546 - New --quiet command-line option to suppress the default console log.
14547 Good in combination with --hash-password.
14548 - Authorities send back an X-Descriptor-Not-New header in response to
14549 an accepted-but-discarded descriptor upload. Partially implements
14551 - Make the log message for "tls error. breaking." more useful.
14552 - Better log messages about certificate downloads, to attempt to
14553 track down the second incarnation of bug 546.
14555 o Minor features (bridges):
14556 - If bridge users set UpdateBridgesFromAuthority, but the digest
14557 they ask for is a 404 from the bridge authority, they now fall
14558 back to trying the bridge directly.
14559 - Bridges now use begin_dir to publish their server descriptor to
14560 the bridge authority, even when they haven't set TunnelDirConns.
14562 o Minor features (controller):
14563 - When reporting clock skew, and we know that the clock is _at least
14564 as skewed_ as some value, but we don't know the actual value,
14565 report the value as a "minimum skew."
14568 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14569 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14573 - Refuse to start if both ORPort and UseBridges are set. Bugfix
14574 on 0.2.0.x, suggested by Matt Edman.
14575 - Don't stop fetching descriptors when FetchUselessDescriptors is
14576 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
14577 reported by tup and ioerror.
14578 - Better log message on vote from unknown authority.
14579 - Don't log "Launching 0 request for 0 router" message.
14581 o Minor bugfixes (memory leaks):
14582 - Stop leaking memory every time we parse a v3 certificate. Bugfix
14584 - Stop leaking memory every time we load a v3 certificate. Bugfix
14585 on 0.2.0.1-alpha. Fixes bug 536.
14586 - Stop leaking a cached networkstatus on exit. Bugfix on
14588 - Stop leaking voter information every time we free a consensus.
14589 Bugfix on 0.2.0.3-alpha.
14590 - Stop leaking signed data every time we check a voter signature.
14591 Bugfix on 0.2.0.3-alpha.
14592 - Stop leaking a signature every time we fail to parse a consensus or
14593 a vote. Bugfix on 0.2.0.3-alpha.
14594 - Stop leaking v2_download_status_map on shutdown. Bugfix on
14596 - Stop leaking conn->nickname every time we make a connection to a
14597 Tor relay without knowing its expected identity digest (e.g. when
14598 using bridges). Bugfix on 0.2.0.3-alpha.
14600 - Minor bugfixes (portability):
14601 - Run correctly on platforms where rlim_t is larger than unsigned
14602 long, and/or where the real limit for number of open files is
14603 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
14604 particular, these may be needed for OS X 10.5.
14607 Changes in version 0.1.2.18 - 2007-10-28
14608 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14609 hidden service introduction that were causing huge delays, and a big
14610 bug that was causing some servers to disappear from the network status
14611 lists for a few hours each day.
14613 o Major bugfixes (crashes):
14614 - If a connection is shut down abruptly because of something that
14615 happened inside connection_flushed_some(), do not call
14616 connection_finished_flushing(). Should fix bug 451:
14617 "connection_stop_writing: Assertion conn->write_event failed"
14618 Bugfix on 0.1.2.7-alpha.
14619 - Fix possible segfaults in functions called from
14620 rend_process_relay_cell().
14622 o Major bugfixes (hidden services):
14623 - Hidden services were choosing introduction points uniquely by
14624 hexdigest, but when constructing the hidden service descriptor
14625 they merely wrote the (potentially ambiguous) nickname.
14626 - Clients now use the v2 intro format for hidden service
14627 connections: they specify their chosen rendezvous point by identity
14628 digest rather than by (potentially ambiguous) nickname. These
14629 changes could speed up hidden service connections dramatically.
14631 o Major bugfixes (other):
14632 - Stop publishing a new server descriptor just because we get a
14633 HUP signal. This led (in a roundabout way) to some servers getting
14634 dropped from the networkstatus lists for a few hours each day.
14635 - When looking for a circuit to cannibalize, consider family as well
14636 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14637 circuit cannibalization).
14638 - When a router wasn't listed in a new networkstatus, we were leaving
14639 the flags for that router alone -- meaning it remained Named,
14640 Running, etc -- even though absence from the networkstatus means
14641 that it shouldn't be considered to exist at all anymore. Now we
14642 clear all the flags for routers that fall out of the networkstatus
14643 consensus. Fixes bug 529.
14646 - Don't try to access (or alter) the state file when running
14647 --list-fingerprint or --verify-config or --hash-password. Resolves
14649 - When generating information telling us how to extend to a given
14650 router, do not try to include the nickname if it is
14651 absent. Resolves bug 467.
14652 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14653 a way to trigger this remotely.)
14654 - When sending a status event to the controller telling it that an
14655 OR address is reachable, set the port correctly. (Previously we
14656 were reporting the dir port.)
14657 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14658 command. Bugfix on 0.1.2.17.
14659 - When loading bandwidth history, do not believe any information in
14660 the future. Fixes bug 434.
14661 - When loading entry guard information, do not believe any information
14663 - When we have our clock set far in the future and generate an
14664 onion key, then re-set our clock to be correct, we should not stop
14665 the onion key from getting rotated.
14666 - On some platforms, accept() can return a broken address. Detect
14667 this more quietly, and deal accordingly. Fixes bug 483.
14668 - It's not actually an error to find a non-pending entry in the DNS
14669 cache when canceling a pending resolve. Don't log unless stuff
14670 is fishy. Resolves bug 463.
14671 - Don't reset trusted dir server list when we set a configuration
14672 option. Patch from Robert Hogan.
14673 - Don't try to create the datadir when running --verify-config or
14674 --hash-password. Resolves bug 540.
14677 Changes in version 0.2.0.9-alpha - 2007-10-24
14678 This ninth development snapshot switches clients to the new v3 directory
14679 system; allows servers to be listed in the network status even when they
14680 have the same nickname as a registered server; and fixes many other
14681 bugs including a big one that was causing some servers to disappear
14682 from the network status lists for a few hours each day.
14684 o Major features (directory system):
14685 - Clients now download v3 consensus networkstatus documents instead
14686 of v2 networkstatus documents. Clients and caches now base their
14687 opinions about routers on these consensus documents. Clients only
14688 download router descriptors listed in the consensus.
14689 - Authorities now list servers who have the same nickname as
14690 a different named server, but list them with a new flag,
14691 "Unnamed". Now we can list servers that happen to pick the same
14692 nickname as a server that registered two years ago and then
14693 disappeared. Partially implements proposal 122.
14694 - If the consensus lists a router as "Unnamed", the name is assigned
14695 to a different router: do not identify the router by that name.
14696 Partially implements proposal 122.
14697 - Authorities can now come to a consensus on which method to use to
14698 compute the consensus. This gives us forward compatibility.
14701 - Stop publishing a new server descriptor just because we HUP or
14702 when we find our DirPort to be reachable but won't actually publish
14703 it. New descriptors without any real changes are dropped by the
14704 authorities, and can screw up our "publish every 18 hours" schedule.
14706 - When a router wasn't listed in a new networkstatus, we were leaving
14707 the flags for that router alone -- meaning it remained Named,
14708 Running, etc -- even though absence from the networkstatus means
14709 that it shouldn't be considered to exist at all anymore. Now we
14710 clear all the flags for routers that fall out of the networkstatus
14711 consensus. Fixes bug 529; bugfix on 0.1.2.x.
14712 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
14713 extrainfo documents and then discard them immediately for not
14714 matching the latest router. Bugfix on 0.2.0.1-alpha.
14716 o Minor features (v3 directory protocol):
14717 - Allow tor-gencert to generate a new certificate without replacing
14719 - Allow certificates to include an address.
14720 - When we change our directory-cache settings, reschedule all voting
14721 and download operations.
14722 - Reattempt certificate downloads immediately on failure, as long as
14723 we haven't failed a threshold number of times yet.
14724 - Delay retrying consensus downloads while we're downloading
14725 certificates to verify the one we just got. Also, count getting a
14726 consensus that we already have (or one that isn't valid) as a failure,
14727 and count failing to get the certificates after 20 minutes as a
14729 - Build circuits and download descriptors even if our consensus is a
14730 little expired. (This feature will go away once authorities are
14733 o Minor features (router descriptor cache):
14734 - If we find a cached-routers file that's been sitting around for more
14735 than 28 days unmodified, then most likely it's a leftover from
14736 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14738 - When we (as a cache) download a descriptor because it was listed
14739 in a consensus, remember when the consensus was supposed to expire,
14740 and don't expire the descriptor until then.
14742 o Minor features (performance):
14743 - Call routerlist_remove_old_routers() much less often. This should
14744 speed startup, especially on directory caches.
14745 - Don't try to launch new descriptor downloads quite so often when we
14746 already have enough directory information to build circuits.
14747 - Base64 decoding was actually showing up on our profile when parsing
14748 the initial descriptor file; switch to an in-process all-at-once
14749 implementation that's about 3.5x times faster than calling out to
14752 o Minor features (compilation):
14753 - Detect non-ASCII platforms (if any still exist) and refuse to
14754 build there: some of our code assumes that 'A' is 65 and so on.
14756 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
14757 - Make the "next period" votes into "current period" votes immediately
14758 after publishing the consensus; avoid a heisenbug that made them
14759 stick around indefinitely.
14760 - When we discard a vote as a duplicate, do not report this as
14762 - Treat missing v3 keys or certificates as an error when running as a
14763 v3 directory authority.
14764 - When we're configured to be a v3 authority, but we're only listed
14765 as a non-v3 authority in our DirServer line for ourself, correct
14767 - If an authority doesn't have a qualified hostname, just put
14768 its address in the vote. This fixes the problem where we referred to
14769 "moria on moria:9031."
14770 - Distinguish between detached signatures for the wrong period, and
14771 detached signatures for a divergent vote.
14772 - Fix a small memory leak when computing a consensus.
14773 - When there's no concensus, we were forming a vote every 30
14774 minutes, but writing the "valid-after" line in our vote based
14775 on our configured V3AuthVotingInterval: so unless the intervals
14776 matched up, we immediately rejected our own vote because it didn't
14777 start at the voting interval that caused us to construct a vote.
14779 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
14780 - Delete unverified-consensus when the real consensus is set.
14781 - Consider retrying a consensus networkstatus fetch immediately
14782 after one fails: don't wait 60 seconds to notice.
14783 - When fetching a consensus as a cache, wait until a newer consensus
14784 should exist before trying to replace the current one.
14785 - Use a more forgiving schedule for retrying failed consensus
14786 downloads than for other types.
14788 o Minor bugfixes (other directory issues):
14789 - Correct the implementation of "download votes by digest." Bugfix on
14791 - Authorities no longer send back "400 you're unreachable please fix
14792 it" errors to Tor servers that aren't online all the time. We're
14793 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
14795 o Minor bugfixes (controller):
14796 - Don't reset trusted dir server list when we set a configuration
14797 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
14798 - Respond to INT and TERM SIGNAL commands before we execute the
14799 signal, in case the signal shuts us down. We had a patch in
14800 0.1.2.1-alpha that tried to do this by queueing the response on
14801 the connection's buffer before shutting down, but that really
14802 isn't the same thing at all. Bug located by Matt Edman.
14804 o Minor bugfixes (misc):
14805 - Correctly check for bad options to the "PublishServerDescriptor"
14806 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
14807 - Stop leaking memory on failing case of base32_decode, and make
14808 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
14809 - Don't try to download extrainfo documents when we're trying to
14810 fetch enough directory info to build a circuit: having enough
14811 info should get priority. Bugfix on 0.2.0.x.
14812 - Don't complain that "your server has not managed to confirm that its
14813 ports are reachable" if we haven't been able to build any circuits
14814 yet. Bug found by spending four hours without a v3 consensus. Bugfix
14816 - Detect the reason for failing to mmap a descriptor file we just
14817 wrote, and give a more useful log message. Fixes bug 533. Bugfix
14820 o Code simplifications and refactoring:
14821 - Remove support for the old bw_accounting file: we've been storing
14822 bandwidth accounting information in the state file since
14823 0.1.2.5-alpha. This may result in bandwidth accounting errors
14824 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14825 downgrade to 0.1.1.x or earlier.
14826 - New convenience code to locate a file within the DataDirectory.
14827 - Move non-authority functionality out of dirvote.c.
14828 - Refactor the arguments for router_pick_{directory_|trusteddir}server
14829 so that they all take the same named flags.
14832 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14833 Unix users an easy way to script their Tor process (e.g. by
14834 adjusting bandwidth based on the time of the day).
14837 Changes in version 0.2.0.8-alpha - 2007-10-12
14838 This eighth development snapshot fixes a crash bug that's been bothering
14839 us since February 2007, lets bridge authorities store a list of bridge
14840 descriptors they've seen, gets v3 directory voting closer to working,
14841 starts caching v3 directory consensus documents on directory mirrors,
14842 and fixes a variety of smaller issues including some minor memory leaks.
14844 o Major features (router descriptor cache):
14845 - Store routers in a file called cached-descriptors instead of in
14846 cached-routers. Initialize cached-descriptors from cached-routers
14847 if the old format is around. The new format allows us to store
14848 annotations along with descriptors.
14849 - Use annotations to record the time we received each descriptor, its
14850 source, and its purpose.
14851 - Disable the SETROUTERPURPOSE controller command: it is now
14853 - Controllers should now specify cache=no or cache=yes when using
14854 the +POSTDESCRIPTOR command.
14855 - Bridge authorities now write bridge descriptors to disk, meaning
14856 we can export them to other programs and begin distributing them
14859 o Major features (directory authorities):
14860 - When a v3 authority is missing votes or signatures, it now tries
14862 - Directory authorities track weighted fractional uptime as well as
14863 weighted mean-time-between failures. WFU is suitable for deciding
14864 whether a node is "usually up", while MTBF is suitable for deciding
14865 whether a node is "likely to stay up." We need both, because
14866 "usually up" is a good requirement for guards, while "likely to
14867 stay up" is a good requirement for long-lived connections.
14869 o Major features (v3 directory system):
14870 - Caches now download v3 network status documents as needed,
14871 and download the descriptors listed in them.
14872 - All hosts now attempt to download and keep fresh v3 authority
14873 certificates, and re-attempt after failures.
14874 - More internal-consistency checks for vote parsing.
14876 o Major bugfixes (crashes):
14877 - If a connection is shut down abruptly because of something that
14878 happened inside connection_flushed_some(), do not call
14879 connection_finished_flushing(). Should fix bug 451. Bugfix on
14882 o Major bugfixes (performance):
14883 - Fix really bad O(n^2) performance when parsing a long list of
14884 routers: Instead of searching the entire list for an "extra-info "
14885 string which usually wasn't there, once for every routerinfo
14886 we read, just scan lines forward until we find one we like.
14888 - When we add data to a write buffer in response to the data on that
14889 write buffer getting low because of a flush, do not consider the
14890 newly added data as a candidate for immediate flushing, but rather
14891 make it wait until the next round of writing. Otherwise, we flush
14892 and refill recursively, and a single greedy TLS connection can
14893 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
14895 o Minor features (v3 authority system):
14896 - Add more ways for tools to download the votes that lead to the
14898 - Send a 503 when low on bandwidth and a vote, consensus, or
14899 certificate is requested.
14900 - If-modified-since is now implemented properly for all kinds of
14901 certificate requests.
14903 o Minor bugfixes (network statuses):
14904 - Tweak the implementation of proposal 109 slightly: allow at most
14905 two Tor servers on the same IP address, except if it's the location
14906 of a directory authority, in which case allow five. Bugfix on
14909 o Minor bugfixes (controller):
14910 - When sending a status event to the controller telling it that an
14911 OR address is reachable, set the port correctly. (Previously we
14912 were reporting the dir port.) Bugfix on 0.1.2.x.
14914 o Minor bugfixes (v3 directory system):
14915 - Fix logic to look up a cert by its signing key digest. Bugfix on
14917 - Only change the reply to a vote to "OK" if it's not already
14918 set. This gets rid of annoying "400 OK" log messages, which may
14919 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
14920 - When we get a valid consensus, recompute the voting schedule.
14921 - Base the valid-after time of a vote on the consensus voting
14922 schedule, not on our preferred schedule.
14923 - Make the return values and messages from signature uploads and
14924 downloads more sensible.
14925 - Fix a memory leak when serving votes and consensus documents, and
14926 another when serving certificates.
14928 o Minor bugfixes (performance):
14929 - Use a slightly simpler string hashing algorithm (copying Python's
14930 instead of Java's) and optimize our digest hashing algorithm to take
14931 advantage of 64-bit platforms and to remove some possibly-costly
14933 - Fix a minor memory leak whenever we parse guards from our state
14934 file. Bugfix on 0.2.0.7-alpha.
14935 - Fix a minor memory leak whenever we write out a file. Bugfix on
14937 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14938 command. Bugfix on 0.2.0.5-alpha.
14940 o Minor bugfixes (portability):
14941 - On some platforms, accept() can return a broken address. Detect
14942 this more quietly, and deal accordingly. Fixes bug 483.
14943 - Stop calling tor_strlower() on uninitialized memory in some cases.
14944 Bugfix in 0.2.0.7-alpha.
14946 o Minor bugfixes (usability):
14947 - Treat some 403 responses from directory servers as INFO rather than
14948 WARN-severity events.
14949 - It's not actually an error to find a non-pending entry in the DNS
14950 cache when canceling a pending resolve. Don't log unless stuff is
14951 fishy. Resolves bug 463.
14953 o Minor bugfixes (anonymity):
14954 - Never report that we've used more bandwidth than we're willing to
14955 relay: it leaks how much non-relay traffic we're using. Resolves
14957 - When looking for a circuit to cannibalize, consider family as well
14958 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14959 circuit cannibalization).
14961 o Code simplifications and refactoring:
14962 - Make a bunch of functions static. Remove some dead code.
14963 - Pull out about a third of the really big routerlist.c; put it in a
14964 new module, networkstatus.c.
14965 - Merge the extra fields in local_routerstatus_t back into
14966 routerstatus_t: we used to need one routerstatus_t for each
14967 authority's opinion, plus a local_routerstatus_t for the locally
14968 computed consensus opinion. To save space, we put the locally
14969 modified fields into local_routerstatus_t, and only the common
14970 stuff into routerstatus_t. But once v3 directories are in use,
14971 clients and caches will no longer need to hold authority opinions;
14972 thus, the rationale for keeping the types separate is now gone.
14973 - Make the code used to reschedule and reattempt downloads more
14975 - Turn all 'Are we a directory server/mirror?' logic into a call to
14977 - Remove the code to generate the oldest (v1) directory format.
14978 The code has been disabled since 0.2.0.5-alpha.
14981 Changes in version 0.2.0.7-alpha - 2007-09-21
14982 This seventh development snapshot makes bridges work again, makes bridge
14983 authorities work for the first time, fixes two huge performance flaws
14984 in hidden services, and fixes a variety of minor issues.
14986 o New directory authorities:
14987 - Set up moria1 and tor26 as the first v3 directory authorities. See
14988 doc/spec/dir-spec.txt for details on the new directory design.
14990 o Major bugfixes (crashes):
14991 - Fix possible segfaults in functions called from
14992 rend_process_relay_cell(). Bugfix on 0.1.2.x.
14994 o Major bugfixes (bridges):
14995 - Fix a bug that made servers send a "404 Not found" in response to
14996 attempts to fetch their server descriptor. This caused Tor servers
14997 to take many minutes to establish reachability for their DirPort,
14998 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
14999 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
15000 users configure that and specify a bridge with an identity
15001 fingerprint, now they will lookup the bridge descriptor at the
15002 default bridge authority via a one-hop tunnel, but once circuits
15003 are established they will switch to a three-hop tunnel for later
15004 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
15006 o Major bugfixes (hidden services):
15007 - Hidden services were choosing introduction points uniquely by
15008 hexdigest, but when constructing the hidden service descriptor
15009 they merely wrote the (potentially ambiguous) nickname.
15010 - Clients now use the v2 intro format for hidden service
15011 connections: they specify their chosen rendezvous point by identity
15012 digest rather than by (potentially ambiguous) nickname. Both
15013 are bugfixes on 0.1.2.x, and they could speed up hidden service
15014 connections dramatically. Thanks to Karsten Loesing.
15016 o Minor features (security):
15017 - As a client, do not believe any server that tells us that an
15018 address maps to an internal address space.
15019 - Make it possible to enable HashedControlPassword and
15020 CookieAuthentication at the same time.
15022 o Minor features (guard nodes):
15023 - Tag every guard node in our state file with the version that
15024 we believe added it, or with our own version if we add it. This way,
15025 if a user temporarily runs an old version of Tor and then switches
15026 back to a new one, she doesn't automatically lose her guards.
15028 o Minor features (speed):
15029 - When implementing AES counter mode, update only the portions of the
15030 counter buffer that need to change, and don't keep separate
15031 network-order and host-order counters when they are the same (i.e.,
15032 on big-endian hosts.)
15034 o Minor features (controller):
15035 - Accept LF instead of CRLF on controller, since some software has a
15036 hard time generating real Internet newlines.
15037 - Add GETINFO values for the server status events
15038 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15041 o Removed features:
15042 - Routers no longer include bandwidth-history lines in their
15043 descriptors; this information is already available in extra-info
15044 documents, and including it in router descriptors took up 60%
15045 (!) of compressed router descriptor downloads. Completes
15046 implementation of proposal 104.
15047 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15048 and TorControl.py, as they use the old v0 controller protocol,
15049 and are obsoleted by TorFlow anyway.
15050 - Drop support for v1 rendezvous descriptors, since we never used
15051 them anyway, and the code has probably rotted by now. Based on
15052 patch from Karsten Loesing.
15053 - On OSX, stop warning the user that kqueue support in libevent is
15054 "experimental", since it seems to have worked fine for ages.
15057 - When generating information telling us how to extend to a given
15058 router, do not try to include the nickname if it is absent. Fixes
15059 bug 467. Bugfix on 0.2.0.3-alpha.
15060 - Fix a user-triggerable (but not remotely-triggerable) segfault
15061 in expand_filename(). Bugfix on 0.1.2.x.
15062 - Fix a memory leak when freeing incomplete requests from DNSPort.
15063 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
15064 - Don't try to access (or alter) the state file when running
15065 --list-fingerprint or --verify-config or --hash-password. (Resolves
15066 bug 499.) Bugfix on 0.1.2.x.
15067 - Servers used to decline to publish their DirPort if their
15068 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
15069 were below a threshold. Now they only look at BandwidthRate and
15070 RelayBandwidthRate. Bugfix on 0.1.2.x.
15071 - Remove an optimization in the AES counter-mode code that assumed
15072 that the counter never exceeded 2^68. When the counter can be set
15073 arbitrarily as an IV (as it is by Karsten's new hidden services
15074 code), this assumption no longer holds. Bugfix on 0.1.2.x.
15075 - Resume listing "AUTHORITY" flag for authorities in network status.
15076 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
15078 o Code simplifications and refactoring:
15079 - Revamp file-writing logic so we don't need to have the entire
15080 contents of a file in memory at once before we write to disk. Tor,
15082 - Turn "descriptor store" into a full-fledged type.
15083 - Move all NT services code into a separate source file.
15084 - Unify all code that computes medians, percentile elements, etc.
15085 - Get rid of a needless malloc when parsing address policies.
15088 Changes in version 0.1.2.17 - 2007-08-30
15089 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15090 X bundles. Vidalia 0.0.14 makes authentication required for the
15091 ControlPort in the default configuration, which addresses important
15092 security risks. Everybody who uses Vidalia (or another controller)
15095 In addition, this Tor update fixes major load balancing problems with
15096 path selection, which should speed things up a lot once many people
15099 o Major bugfixes (security):
15100 - We removed support for the old (v0) control protocol. It has been
15101 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15102 become more of a headache than it's worth.
15104 o Major bugfixes (load balancing):
15105 - When choosing nodes for non-guard positions, weight guards
15106 proportionally less, since they already have enough load. Patch
15108 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15109 will allow fast Tor servers to get more attention.
15110 - When we're upgrading from an old Tor version, forget our current
15111 guards and pick new ones according to the new weightings. These
15112 three load balancing patches could raise effective network capacity
15113 by a factor of four. Thanks to Mike Perry for measurements.
15115 o Major bugfixes (stream expiration):
15116 - Expire not-yet-successful application streams in all cases if
15117 they've been around longer than SocksTimeout. Right now there are
15118 some cases where the stream will live forever, demanding a new
15119 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15121 o Minor features (controller):
15122 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15123 is valid before any authentication has been received. It tells
15124 a controller what kind of authentication is expected, and what
15125 protocol is spoken. Implements proposal 119.
15127 o Minor bugfixes (performance):
15128 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15129 greatly speeding up loading cached-routers from disk on startup.
15130 - Disable sentinel-based debugging for buffer code: we squashed all
15131 the bugs that this was supposed to detect a long time ago, and now
15132 its only effect is to change our buffer sizes from nice powers of
15133 two (which platform mallocs tend to like) to values slightly over
15134 powers of two (which make some platform mallocs sad).
15136 o Minor bugfixes (misc):
15137 - If exit bandwidth ever exceeds one third of total bandwidth, then
15138 use the correct formula to weight exit nodes when choosing paths.
15139 Based on patch from Mike Perry.
15140 - Choose perfectly fairly among routers when choosing by bandwidth and
15141 weighting by fraction of bandwidth provided by exits. Previously, we
15142 would choose with only approximate fairness, and correct ourselves
15143 if we ran off the end of the list.
15144 - If we require CookieAuthentication but we fail to write the
15145 cookie file, we would warn but not exit, and end up in a state
15146 where no controller could authenticate. Now we exit.
15147 - If we require CookieAuthentication, stop generating a new cookie
15148 every time we change any piece of our config.
15149 - Refuse to start with certain directory authority keys, and
15150 encourage people using them to stop.
15151 - Terminate multi-line control events properly. Original patch
15153 - Fix a minor memory leak when we fail to find enough suitable
15154 servers to choose a circuit.
15155 - Stop leaking part of the descriptor when we run into a particularly
15156 unparseable piece of it.
15159 Changes in version 0.2.0.6-alpha - 2007-08-26
15160 This sixth development snapshot features a new Vidalia version in the
15161 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
15162 the ControlPort in the default configuration, which addresses important
15165 In addition, this snapshot fixes major load balancing problems
15166 with path selection, which should speed things up a lot once many
15167 people have upgraded. The directory authorities also use a new
15168 mean-time-between-failure approach to tracking which servers are stable,
15169 rather than just looking at the most recent uptime.
15171 o New directory authorities:
15172 - Set up Tonga as the default bridge directory authority.
15175 - Directory authorities now track servers by weighted
15176 mean-times-between-failures. When we have 4 or more days of data,
15177 use measured MTBF rather than declared uptime to decide whether
15178 to call a router Stable. Implements proposal 108.
15180 o Major bugfixes (load balancing):
15181 - When choosing nodes for non-guard positions, weight guards
15182 proportionally less, since they already have enough load. Patch
15184 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15185 will allow fast Tor servers to get more attention.
15186 - When we're upgrading from an old Tor version, forget our current
15187 guards and pick new ones according to the new weightings. These
15188 three load balancing patches could raise effective network capacity
15189 by a factor of four. Thanks to Mike Perry for measurements.
15191 o Major bugfixes (descriptor parsing):
15192 - Handle unexpected whitespace better in malformed descriptors. Bug
15193 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
15196 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15197 GETINFO for Torstat to use until it can switch to using extrainfos.
15198 - Optionally (if built with -DEXPORTMALLINFO) export the output
15199 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15203 - Do not intermix bridge routers with controller-added
15204 routers. (Bugfix on 0.2.0.x)
15205 - Do not fail with an assert when accept() returns an unexpected
15206 address family. Addresses but does not wholly fix bug 483. (Bugfix
15208 - Let directory authorities startup even when they can't generate
15209 a descriptor immediately, e.g. because they don't know their
15211 - Stop putting the authentication cookie in a file called "0"
15212 in your working directory if you don't specify anything for the
15213 new CookieAuthFile option. Reported by Matt Edman.
15214 - Make it possible to read the PROTOCOLINFO response in a way that
15215 conforms to our control-spec. Reported by Matt Edman.
15216 - Fix a minor memory leak when we fail to find enough suitable
15217 servers to choose a circuit. Bugfix on 0.1.2.x.
15218 - Stop leaking part of the descriptor when we run into a particularly
15219 unparseable piece of it. Bugfix on 0.1.2.x.
15220 - Unmap the extrainfo cache file on exit.
15223 Changes in version 0.2.0.5-alpha - 2007-08-19
15224 This fifth development snapshot fixes compilation on Windows again;
15225 fixes an obnoxious client-side bug that slowed things down and put
15226 extra load on the network; gets us closer to using the v3 directory
15227 voting scheme; makes it easier for Tor controllers to use cookie-based
15228 authentication; and fixes a variety of other bugs.
15230 o Removed features:
15231 - Version 1 directories are no longer generated in full. Instead,
15232 authorities generate and serve "stub" v1 directories that list
15233 no servers. This will stop Tor versions 0.1.0.x and earlier from
15234 working, but (for security reasons) nobody should be running those
15237 o Major bugfixes (compilation, 0.2.0.x):
15238 - Try to fix Win32 compilation again: improve checking for IPv6 types.
15239 - Try to fix MSVC compilation: build correctly on platforms that do
15240 not define s6_addr16 or s6_addr32.
15241 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
15244 o Major bugfixes (stream expiration):
15245 - Expire not-yet-successful application streams in all cases if
15246 they've been around longer than SocksTimeout. Right now there are
15247 some cases where the stream will live forever, demanding a new
15248 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
15249 reported by lodger.
15251 o Minor features (directory servers):
15252 - When somebody requests a list of statuses or servers, and we have
15253 none of those, return a 404 rather than an empty 200.
15255 o Minor features (directory voting):
15256 - Store v3 consensus status consensuses on disk, and reload them
15259 o Minor features (security):
15260 - Warn about unsafe ControlPort configurations.
15261 - Refuse to start with certain directory authority keys, and
15262 encourage people using them to stop.
15264 o Minor features (controller):
15265 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15266 is valid before any authentication has been received. It tells
15267 a controller what kind of authentication is expected, and what
15268 protocol is spoken. Implements proposal 119.
15269 - New config option CookieAuthFile to choose a new location for the
15270 cookie authentication file, and config option
15271 CookieAuthFileGroupReadable to make it group-readable.
15273 o Minor features (unit testing):
15274 - Add command-line arguments to unit-test executable so that we can
15275 invoke any chosen test from the command line rather than having
15276 to run the whole test suite at once; and so that we can turn on
15277 logging for the unit tests.
15279 o Minor bugfixes (on 0.1.2.x):
15280 - If we require CookieAuthentication but we fail to write the
15281 cookie file, we would warn but not exit, and end up in a state
15282 where no controller could authenticate. Now we exit.
15283 - If we require CookieAuthentication, stop generating a new cookie
15284 every time we change any piece of our config.
15285 - When loading bandwidth history, do not believe any information in
15286 the future. Fixes bug 434.
15287 - When loading entry guard information, do not believe any information
15289 - When we have our clock set far in the future and generate an
15290 onion key, then re-set our clock to be correct, we should not stop
15291 the onion key from getting rotated.
15292 - Clean up torrc sample config file.
15293 - Do not automatically run configure from autogen.sh. This
15294 non-standard behavior tended to annoy people who have built other
15297 o Minor bugfixes (on 0.2.0.x):
15298 - Fix a bug with AutomapHostsOnResolve that would always cause
15299 the second request to fail. Bug reported by Kate. Bugfix on
15301 - Fix a bug in ADDRMAP controller replies that would sometimes
15302 try to print a NULL. Patch from tup.
15303 - Read v3 directory authority keys from the right location.
15304 - Numerous bugfixes to directory voting code.
15307 Changes in version 0.1.2.16 - 2007-08-01
15308 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15309 remote attacker in certain situations to rewrite the user's torrc
15310 configuration file. This can completely compromise anonymity of users
15311 in most configurations, including those running the Vidalia bundles,
15312 TorK, etc. Or worse.
15314 o Major security fixes:
15315 - Close immediately after missing authentication on control port;
15316 do not allow multiple authentication attempts.
15319 Changes in version 0.2.0.4-alpha - 2007-08-01
15320 This fourth development snapshot fixes a critical security vulnerability
15321 for most users, specifically those running Vidalia, TorK, etc. Everybody
15322 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
15324 o Major security fixes:
15325 - Close immediately after missing authentication on control port;
15326 do not allow multiple authentication attempts.
15328 o Major bugfixes (compilation):
15329 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
15332 o Minor features (performance):
15333 - Be even more aggressive about releasing RAM from small
15334 empty buffers. Thanks to our free-list code, this shouldn't be too
15335 performance-intensive.
15336 - Disable sentinel-based debugging for buffer code: we squashed all
15337 the bugs that this was supposed to detect a long time ago, and
15338 now its only effect is to change our buffer sizes from nice
15339 powers of two (which platform mallocs tend to like) to values
15340 slightly over powers of two (which make some platform mallocs sad).
15341 - Log malloc statistics from mallinfo() on platforms where it
15345 Changes in version 0.2.0.3-alpha - 2007-07-29
15346 This third development snapshot introduces new experimental
15347 blocking-resistance features and a preliminary version of the v3
15348 directory voting design, and includes many other smaller features
15352 - The first pieces of our "bridge" design for blocking-resistance
15353 are implemented. People can run bridge directory authorities;
15354 people can run bridges; and people can configure their Tor clients
15355 with a set of bridges to use as the first hop into the Tor network.
15356 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
15358 - Create listener connections before we setuid to the configured
15359 User and Group. Now non-Windows users can choose port values
15360 under 1024, start Tor as root, and have Tor bind those ports
15361 before it changes to another UID. (Windows users could already
15363 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15364 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15365 on "vserver" accounts. (Patch from coderman.)
15366 - Be even more aggressive about separating local traffic from relayed
15367 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
15369 o Major features (experimental):
15370 - First cut of code for "v3 dir voting": directory authorities will
15371 vote on a common network status document rather than each publishing
15372 their own opinion. This code needs more testing and more corner-case
15373 handling before it's ready for use.
15376 - Directory authorities now call routers Fast if their bandwidth is
15377 at least 100KB/s, and consider their bandwidth adequate to be a
15378 Guard if it is at least 250KB/s, no matter the medians. This fix
15379 complements proposal 107. [Bugfix on 0.1.2.x]
15380 - Directory authorities now never mark more than 3 servers per IP as
15381 Valid and Running. (Implements proposal 109, by Kevin Bauer and
15383 - Minor change to organizationName and commonName generation
15384 procedures in TLS certificates during Tor handshakes, to invalidate
15385 some earlier censorware approaches. This is not a long-term
15386 solution, but applying it will give us a bit of time to look into
15387 the epidemiology of countermeasures as they spread.
15389 o Major bugfixes (directory):
15390 - Rewrite directory tokenization code to never run off the end of
15391 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
15393 o Minor features (controller):
15394 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15395 match requests to applications. (Patch from Robert Hogan.)
15396 - Report address and port correctly on connections to DNSPort. (Patch
15397 from Robert Hogan.)
15398 - Add a RESOLVE command to launch hostname lookups. (Original patch
15399 from Robert Hogan.)
15400 - Add GETINFO status/enough-dir-info to let controllers tell whether
15401 Tor has downloaded sufficient directory information. (Patch
15403 - You can now use the ControlSocket option to tell Tor to listen for
15404 controller connections on Unix domain sockets on systems that
15405 support them. (Patch from Peter Palfrader.)
15406 - STREAM NEW events are generated for DNSPort requests and for
15407 tunneled directory connections. (Patch from Robert Hogan.)
15408 - New "GETINFO address-mappings/*" command to get address mappings
15409 with expiry information. "addr-mappings/*" is now deprecated.
15412 o Minor features (misc):
15413 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15415 - The tor-gencert tool for v3 directory authorities now creates all
15416 files as readable to the file creator only, and write-protects
15417 the authority identity key.
15418 - When dumping memory usage, list bytes used in buffer memory
15420 - When running with dmalloc, dump more stats on hup and on exit.
15421 - Directory authorities now fail quickly and (relatively) harmlessly
15422 if they generate a network status document that is somehow
15425 o Traffic load balancing improvements:
15426 - If exit bandwidth ever exceeds one third of total bandwidth, then
15427 use the correct formula to weight exit nodes when choosing paths.
15428 (Based on patch from Mike Perry.)
15429 - Choose perfectly fairly among routers when choosing by bandwidth and
15430 weighting by fraction of bandwidth provided by exits. Previously, we
15431 would choose with only approximate fairness, and correct ourselves
15432 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15434 o Performance improvements:
15435 - Be more aggressive with freeing buffer RAM or putting it on the
15437 - Use Critical Sections rather than Mutexes for synchronizing threads
15438 on win32; Mutexes are heavier-weight, and designed for synchronizing
15441 o Deprecated and removed features:
15442 - RedirectExits is now deprecated.
15443 - Stop allowing address masks that do not correspond to bit prefixes.
15444 We have warned about these for a really long time; now it's time
15445 to reject them. (Patch from croup.)
15447 o Minor bugfixes (directory):
15448 - Fix another crash bug related to extra-info caching. (Bug found by
15449 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
15450 - Directories no longer return a "304 not modified" when they don't
15451 have the networkstatus the client asked for. Also fix a memory
15452 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
15453 - We had accidentally labelled 0.1.2.x directory servers as not
15454 suitable for begin_dir requests, and had labelled no directory
15455 servers as suitable for uploading extra-info documents. [Bugfix
15458 o Minor bugfixes (dns):
15459 - Fix a crash when DNSPort is set more than once. (Patch from Robert
15460 Hogan.) [Bugfix on 0.2.0.2-alpha]
15461 - Add DNSPort connections to the global connection list, so that we
15462 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
15464 - Fix a dangling reference that could lead to a crash when DNSPort is
15465 changed or closed (Patch from Robert Hogan.) [Bugfix on
15468 o Minor bugfixes (controller):
15469 - Provide DNS expiry times in GMT, not in local time. For backward
15470 compatibility, ADDRMAP events only provide GMT expiry in an extended
15471 field. "GETINFO address-mappings" always does the right thing.
15472 - Use CRLF line endings properly in NS events.
15473 - Terminate multi-line control events properly. (Original patch
15474 from tup.) [Bugfix on 0.1.2.x-alpha]
15475 - Do not include spaces in SOURCE_ADDR fields in STREAM
15476 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
15479 Changes in version 0.1.2.15 - 2007-07-17
15480 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15481 problems, fixes compilation on BSD, and fixes a variety of other
15482 bugs. Everybody should upgrade.
15484 o Major bugfixes (compilation):
15485 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15487 o Major bugfixes (crashes):
15488 - Try even harder not to dereference the first character after
15489 an mmap(). Reported by lodger.
15490 - Fix a crash bug in directory authorities when we re-number the
15491 routerlist while inserting a new router.
15492 - When the cached-routers file is an even multiple of the page size,
15493 don't run off the end and crash. (Fixes bug 455; based on idea
15495 - Fix eventdns.c behavior on Solaris: It is critical to include
15496 orconfig.h _before_ sys/types.h, so that we can get the expected
15497 definition of _FILE_OFFSET_BITS.
15499 o Major bugfixes (security):
15500 - Fix a possible buffer overrun when using BSD natd support. Bug
15502 - When sending destroy cells from a circuit's origin, don't include
15503 the reason for tearing down the circuit. The spec says we didn't,
15504 and now we actually don't. Reported by lodger.
15505 - Keep streamids from different exits on a circuit separate. This
15506 bug may have allowed other routers on a given circuit to inject
15507 cells into streams. Reported by lodger; fixes bug 446.
15508 - If there's a never-before-connected-to guard node in our list,
15509 never choose any guards past it. This way we don't expand our
15510 guard list unless we need to.
15512 o Minor bugfixes (guard nodes):
15513 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15514 don't get overused as guards.
15516 o Minor bugfixes (directory):
15517 - Correctly count the number of authorities that recommend each
15518 version. Previously, we were under-counting by 1.
15519 - Fix a potential crash bug when we load many server descriptors at
15520 once and some of them make others of them obsolete. Fixes bug 458.
15522 o Minor bugfixes (hidden services):
15523 - Stop tearing down the whole circuit when the user asks for a
15524 connection to a port that the hidden service didn't configure.
15527 o Minor bugfixes (misc):
15528 - On Windows, we were preventing other processes from reading
15529 cached-routers while Tor was running. Reported by janbar.
15530 - Fix a possible (but very unlikely) bug in picking routers by
15531 bandwidth. Add a log message to confirm that it is in fact
15532 unlikely. Patch from lodger.
15533 - Backport a couple of memory leak fixes.
15534 - Backport miscellaneous cosmetic bugfixes.
15537 Changes in version 0.2.0.2-alpha - 2007-06-02
15538 o Major bugfixes on 0.2.0.1-alpha:
15539 - Fix an assertion failure related to servers without extra-info digests.
15540 Resolves bugs 441 and 442.
15542 o Minor features (directory):
15543 - Support "If-Modified-Since" when answering HTTP requests for
15544 directories, running-routers documents, and network-status documents.
15545 (There's no need to support it for router descriptors, since those
15546 are downloaded by descriptor digest.)
15548 o Minor build issues:
15549 - Clear up some MIPSPro compiler warnings.
15550 - When building from a tarball on a machine that happens to have SVK
15551 installed, report the micro-revision as whatever version existed
15552 in the tarball, not as "x".
15555 Changes in version 0.2.0.1-alpha - 2007-06-01
15556 This early development snapshot provides new features for people running
15557 Tor as both a client and a server (check out the new RelayBandwidth
15558 config options); lets Tor run as a DNS proxy; and generally moves us
15559 forward on a lot of fronts.
15561 o Major features, server usability:
15562 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15563 a separate set of token buckets for relayed traffic. Right now
15564 relayed traffic is defined as answers to directory requests, and
15565 OR connections that don't have any local circuits on them.
15567 o Major features, client usability:
15568 - A client-side DNS proxy feature to replace the need for
15569 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15570 for DNS requests on port 9999, use the Tor network to resolve them
15571 anonymously, and send the reply back like a regular DNS server.
15572 The code still only implements a subset of DNS.
15573 - Make PreferTunneledDirConns and TunnelDirConns work even when
15574 we have no cached directory info. This means Tor clients can now
15575 do all of their connections protected by TLS.
15577 o Major features, performance and efficiency:
15578 - Directory authorities accept and serve "extra info" documents for
15579 routers. These documents contain fields from router descriptors
15580 that aren't usually needed, and that use a lot of excess
15581 bandwidth. Once these fields are removed from router descriptors,
15582 the bandwidth savings should be about 60%. [Partially implements
15584 - Servers upload extra-info documents to any authority that accepts
15585 them. Authorities (and caches that have been configured to download
15586 extra-info documents) download them as needed. [Partially implements
15588 - Change the way that Tor buffers data that it is waiting to write.
15589 Instead of queueing data cells in an enormous ring buffer for each
15590 client->OR or OR->OR connection, we now queue cells on a separate
15591 queue for each circuit. This lets us use less slack memory, and
15592 will eventually let us be smarter about prioritizing different kinds
15594 - Use memory pools to allocate cells with better speed and memory
15595 efficiency, especially on platforms where malloc() is inefficient.
15596 - Stop reading on edge connections when their corresponding circuit
15597 buffers are full; start again as the circuits empty out.
15599 o Major features, other:
15600 - Add an HSAuthorityRecordStats option that hidden service authorities
15601 can use to track statistics of overall hidden service usage without
15602 logging information that would be very useful to an attacker.
15603 - Start work implementing multi-level keys for directory authorities:
15604 Add a standalone tool to generate key certificates. (Proposal 103.)
15607 - Directory authorities now call routers Stable if they have an
15608 uptime of at least 30 days, even if that's not the median uptime
15609 in the network. Implements proposal 107, suggested by Kevin Bauer
15612 o Minor fixes (resource management):
15613 - Count the number of open sockets separately from the number
15614 of active connection_t objects. This will let us avoid underusing
15615 our allocated connection limit.
15616 - We no longer use socket pairs to link an edge connection to an
15617 anonymous directory connection or a DirPort test connection.
15618 Instead, we track the link internally and transfer the data
15619 in-process. This saves two sockets per "linked" connection (at the
15620 client and at the server), and avoids the nasty Windows socketpair()
15622 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15623 for every single inactive connection_t. Free items from the
15624 4k/16k-buffer free lists when they haven't been used for a while.
15626 o Minor features (build):
15627 - Make autoconf search for libevent, openssl, and zlib consistently.
15628 - Update deprecated macros in configure.in.
15629 - When warning about missing headers, tell the user to let us
15630 know if the compile succeeds anyway, so we can downgrade the
15632 - Include the current subversion revision as part of the version
15633 string: either fetch it directly if we're in an SVN checkout, do
15634 some magic to guess it if we're in an SVK checkout, or use
15635 the last-detected version if we're building from a .tar.gz.
15636 Use this version consistently in log messages.
15638 o Minor features (logging):
15639 - Always prepend "Bug: " to any log message about a bug.
15640 - Put a platform string (e.g. "Linux i686") in the startup log
15641 message, so when people paste just their logs, we know if it's
15642 OpenBSD or Windows or what.
15643 - When logging memory usage, break down memory used in buffers by
15646 o Minor features (directory system):
15647 - New config option V2AuthoritativeDirectory that all directory
15648 authorities should set. This will let future authorities choose
15649 not to serve V2 directory information.
15650 - Directory authorities allow multiple router descriptors and/or extra
15651 info documents to be uploaded in a single go. This will make
15652 implementing proposal 104 simpler.
15654 o Minor features (controller):
15655 - Add a new config option __DisablePredictedCircuits designed for
15656 use by the controller, when we don't want Tor to build any circuits
15658 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15659 so we can exit from the middle of the circuit.
15660 - Implement "getinfo status/circuit-established".
15661 - Implement "getinfo status/version/..." so a controller can tell
15662 whether the current version is recommended, and whether any versions
15663 are good, and how many authorities agree. (Patch from shibz.)
15665 o Minor features (hidden services):
15666 - Allow multiple HiddenServicePort directives with the same virtual
15667 port; when they occur, the user is sent round-robin to one
15668 of the target ports chosen at random. Partially fixes bug 393 by
15669 adding limited ad-hoc round-robining.
15671 o Minor features (other):
15673 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15674 resolve request for hosts matching a given pattern causes Tor to
15675 generate an internal virtual address mapping for that host. This
15676 allows DNSPort to work sensibly with hidden service users. By
15677 default, .exit and .onion addresses are remapped; the list of
15678 patterns can be reconfigured with AutomapHostsSuffixes.
15679 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15680 address. Thanks to the AutomapHostsOnResolve option, this is no
15681 longer a completely silly thing to do.
15682 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15683 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15684 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15685 minus 1 byte: the actual maximum declared bandwidth.
15687 o Removed features:
15688 - Removed support for the old binary "version 0" controller protocol.
15689 This has been deprecated since 0.1.1, and warnings have been issued
15690 since 0.1.2. When we encounter a v0 control message, we now send
15691 back an error and close the connection.
15692 - Remove the old "dns worker" server DNS code: it hasn't been default
15693 since 0.1.2.2-alpha, and all the servers seem to be using the new
15696 o Minor bugfixes (portability):
15697 - Even though Windows is equally happy with / and \ as path separators,
15698 try to use \ consistently on Windows and / consistently on Unix: it
15699 makes the log messages nicer.
15700 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15701 - Read resolv.conf files correctly on platforms where read() returns
15702 partial results on small file reads.
15704 o Minor bugfixes (directory):
15705 - Correctly enforce that elements of directory objects do not appear
15706 more often than they are allowed to appear.
15707 - When we are reporting the DirServer line we just parsed, we were
15708 logging the second stanza of the key fingerprint, not the first.
15710 o Minor bugfixes (logging):
15711 - When we hit an EOF on a log (probably because we're shutting down),
15712 don't try to remove the log from the list: just mark it as
15713 unusable. (Bulletproofs against bug 222.)
15715 o Minor bugfixes (other):
15716 - In the exitlist script, only consider the most recently published
15717 server descriptor for each server. Also, when the user requests
15718 a list of servers that _reject_ connections to a given address,
15719 explicitly exclude the IPs that also have servers that accept
15720 connections to that address. (Resolves bug 405.)
15721 - Stop allowing hibernating servers to be "stable" or "fast".
15722 - On Windows, we were preventing other processes from reading
15723 cached-routers while Tor was running. (Reported by janbar)
15724 - Make the NodeFamilies config option work. (Reported by
15725 lodger -- it has never actually worked, even though we added it
15727 - Check return values from pthread_mutex functions.
15728 - Don't save non-general-purpose router descriptors to the disk cache,
15729 because we have no way of remembering what their purpose was when
15731 - Add even more asserts to hunt down bug 417.
15732 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
15733 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
15734 Add a log message to confirm that it is in fact unlikely.
15736 o Minor bugfixes (controller):
15737 - Make 'getinfo fingerprint' return a 551 error if we're not a
15738 server, so we match what the control spec claims we do. Reported
15740 - Fix a typo in an error message when extendcircuit fails that
15741 caused us to not follow the \r\n-based delimiter protocol. Reported
15744 o Code simplifications and refactoring:
15745 - Stop passing around circuit_t and crypt_path_t pointers that are
15746 implicit in other procedure arguments.
15747 - Drop the old code to choke directory connections when the
15748 corresponding OR connections got full: thanks to the cell queue
15749 feature, OR conns don't get full any more.
15750 - Make dns_resolve() handle attaching connections to circuits
15751 properly, so the caller doesn't have to.
15752 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
15753 - Keep the connection array as a dynamic smartlist_t, rather than as
15754 a fixed-sized array. This is important, as the number of connections
15755 is becoming increasingly decoupled from the number of sockets.
15758 Changes in version 0.1.2.14 - 2007-05-25
15759 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15760 change especially affects those who serve or use hidden services),
15761 and fixes several other crash- and security-related bugs.
15763 o Directory authority changes:
15764 - Two directory authorities (moria1 and moria2) just moved to new
15765 IP addresses. This change will particularly affect those who serve
15766 or use hidden services.
15768 o Major bugfixes (crashes):
15769 - If a directory server runs out of space in the connection table
15770 as it's processing a begin_dir request, it will free the exit stream
15771 but leave it attached to the circuit, leading to unpredictable
15772 behavior. (Reported by seeess, fixes bug 425.)
15773 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15774 to corrupt memory under some really unlikely scenarios.
15775 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15776 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15779 o Major bugfixes (security):
15780 - When choosing an entry guard for a circuit, avoid using guards
15781 that are in the same family as the chosen exit -- not just guards
15782 that are exactly the chosen exit. (Reported by lodger.)
15784 o Major bugfixes (resource management):
15785 - If a directory authority is down, skip it when deciding where to get
15786 networkstatus objects or descriptors. Otherwise we keep asking
15787 every 10 seconds forever. Fixes bug 384.
15788 - Count it as a failure if we fetch a valid network-status but we
15789 don't want to keep it. Otherwise we'll keep fetching it and keep
15790 not wanting to keep it. Fixes part of bug 422.
15791 - If all of our dirservers have given us bad or no networkstatuses
15792 lately, then stop hammering them once per minute even when we
15793 think they're failed. Fixes another part of bug 422.
15796 - Actually set the purpose correctly for descriptors inserted with
15797 purpose=controller.
15798 - When we have k non-v2 authorities in our DirServer config,
15799 we ignored the last k authorities in the list when updating our
15801 - Correctly back-off from requesting router descriptors that we are
15802 having a hard time downloading.
15803 - Read resolv.conf files correctly on platforms where read() returns
15804 partial results on small file reads.
15805 - Don't rebuild the entire router store every time we get 32K of
15806 routers: rebuild it when the journal gets very large, or when
15807 the gaps in the store get very large.
15810 - When routers publish SVN revisions in their router descriptors,
15811 authorities now include those versions correctly in networkstatus
15813 - Warn when using a version of libevent before 1.3b to run a server on
15814 OSX or BSD: these versions interact badly with userspace threads.
15817 Changes in version 0.1.2.13 - 2007-04-24
15818 This release features some major anonymity fixes, such as safer path
15819 selection; better client performance; faster bootstrapping, better
15820 address detection, and better DNS support for servers; write limiting as
15821 well as read limiting to make servers easier to run; and a huge pile of
15822 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15824 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15825 of the Freenode IRC network, remembering his patience and vision for
15826 free speech on the Internet.
15829 - Fix a memory leak when we ask for "all" networkstatuses and we
15830 get one we don't recognize.
15831 - Add more asserts to hunt down bug 417.
15832 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15835 Changes in version 0.1.2.12-rc - 2007-03-16
15837 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
15838 directory information requested inside Tor connections (i.e. via
15839 begin_dir cells). It only triggered when the same connection was
15840 serving other data at the same time. Reported by seeess.
15843 - When creating a circuit via the controller, send a 'launched'
15844 event when we're done, so we follow the spec better.
15847 Changes in version 0.1.2.11-rc - 2007-03-15
15848 o Minor bugfixes (controller), reported by daejees:
15849 - Correct the control spec to match how the code actually responds
15850 to 'getinfo addr-mappings/*'.
15851 - The control spec described a GUARDS event, but the code
15852 implemented a GUARD event. Standardize on GUARD, but let people
15853 ask for GUARDS too.
15856 Changes in version 0.1.2.10-rc - 2007-03-07
15857 o Major bugfixes (Windows):
15858 - Do not load the NT services library functions (which may not exist)
15859 just to detect if we're a service trying to shut down. Now we run
15860 on Win98 and friends again.
15862 o Minor bugfixes (other):
15863 - Clarify a couple of log messages.
15864 - Fix a misleading socks5 error number.
15867 Changes in version 0.1.2.9-rc - 2007-03-02
15868 o Major bugfixes (Windows):
15869 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
15870 of the usual GCC "%llu". This prevents a bug when saving 64-bit
15871 int configuration values: the high-order 32 bits would get
15872 truncated. In particular, we were being bitten by the default
15873 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
15874 and maybe also bug 397.)
15876 o Minor bugfixes (performance):
15877 - Use OpenSSL's AES implementation on platforms where it's faster.
15878 This could save us as much as 10% CPU usage.
15880 o Minor bugfixes (server):
15881 - Do not rotate onion key immediately after setting it for the first
15884 o Minor bugfixes (directory authorities):
15885 - Stop calling servers that have been hibernating for a long time
15886 "stable". Also, stop letting hibernating or obsolete servers affect
15887 uptime and bandwidth cutoffs.
15888 - Stop listing hibernating servers in the v1 directory.
15890 o Minor bugfixes (hidden services):
15891 - Upload hidden service descriptors slightly less often, to reduce
15892 load on authorities.
15894 o Minor bugfixes (other):
15895 - Fix an assert that could trigger if a controller quickly set then
15896 cleared EntryNodes. Bug found by Udo van den Heuvel.
15897 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
15899 - Fix a potential race condition in the rpm installer. Found by
15901 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
15902 of 2 as indicating that the server is completely bad; it sometimes
15903 means that the server is just bad for the request in question. (may fix
15904 the last of bug 326.)
15905 - Disable encrypted directory connections when we don't have a server
15906 descriptor for the destination. We'll get this working again in
15910 Changes in version 0.1.2.8-beta - 2007-02-26
15911 o Major bugfixes (crashes):
15912 - Stop crashing when the controller asks us to resetconf more than
15913 one config option at once. (Vidalia 0.0.11 does this.)
15914 - Fix a crash that happened on Win98 when we're given command-line
15915 arguments: don't try to load NT service functions from advapi32.dll
15916 except when we need them. (Bug introduced in 0.1.2.7-alpha;
15918 - Fix a longstanding obscure crash bug that could occur when
15919 we run out of DNS worker processes. (Resolves bug 390.)
15921 o Major bugfixes (hidden services):
15922 - Correctly detect whether hidden service descriptor downloads are
15923 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
15925 o Major bugfixes (accounting):
15926 - When we start during an accounting interval before it's time to wake
15927 up, remember to wake up at the correct time. (May fix bug 342.)
15929 o Minor bugfixes (controller):
15930 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15931 clear the corresponding on_circuit variable, and remember later
15932 that we don't need to send a redundant CLOSED event. Resolves part
15934 - Report events where a resolve succeeded or where we got a socks
15935 protocol error correctly, rather than calling both of them
15937 - Change reported stream target addresses to IP consistently when
15938 we finally get the IP from an exit node.
15939 - Send log messages to the controller even if they happen to be very
15942 o Minor bugfixes (other):
15943 - Display correct results when reporting which versions are
15944 recommended, and how recommended they are. (Resolves bug 383.)
15945 - Improve our estimates for directory bandwidth to be less random:
15946 guess that an unrecognized directory will have the average bandwidth
15947 from all known directories, not that it will have the average
15948 bandwidth from those directories earlier than it on the list.
15949 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15950 and hup, stop triggering an assert based on an empty onion_key.
15951 - On platforms with no working mmap() equivalent, don't warn the
15952 user when cached-routers doesn't exist.
15953 - Warn the user when mmap() [or its equivalent] fails for some reason
15954 other than file-not-found.
15955 - Don't warn the user when cached-routers.new doesn't exist: that's
15956 perfectly fine when starting up for the first time.
15957 - When EntryNodes are configured, rebuild the guard list to contain,
15958 in order: the EntryNodes that were guards before; the rest of the
15959 EntryNodes; the nodes that were guards before.
15960 - Mask out all signals in sub-threads; only the libevent signal
15961 handler should be processing them. This should prevent some crashes
15962 on some machines using pthreads. (Patch from coderman.)
15963 - Fix switched arguments on memset in the implementation of
15964 tor_munmap() for systems with no mmap() call.
15965 - When Tor receives a router descriptor that it asked for, but
15966 no longer wants (because it has received fresh networkstatuses
15967 in the meantime), do not warn the user. Cache the descriptor if
15968 we're a cache; drop it if we aren't.
15969 - Make earlier entry guards _really_ get retried when the network
15971 - On a malformed DNS reply, always give an error to the corresponding
15973 - Build with recent libevents on platforms that do not define the
15974 nonstandard types "u_int8_t" and friends.
15976 o Minor features (controller):
15977 - Warn the user when an application uses the obsolete binary v0
15978 control protocol. We're planning to remove support for it during
15979 the next development series, so it's good to give people some
15981 - Add STREAM_BW events to report per-entry-stream bandwidth
15982 use. (Patch from Robert Hogan.)
15983 - Rate-limit SIGNEWNYM signals in response to controllers that
15984 impolitely generate them for every single stream. (Patch from
15985 mwenge; closes bug 394.)
15986 - Make REMAP stream events have a SOURCE (cache or exit), and
15987 make them generated in every case where we get a successful
15988 connected or resolved cell.
15990 o Minor bugfixes (performance):
15991 - Call router_have_min_dir_info half as often. (This is showing up in
15992 some profiles, but not others.)
15993 - When using GCC, make log_debug never get called at all, and its
15994 arguments never get evaluated, when no debug logs are configured.
15995 (This is showing up in some profiles, but not others.)
15998 - Remove some never-implemented options. Mark PathlenCoinWeight as
16000 - Implement proposal 106: Stop requiring clients to have well-formed
16001 certificates; stop checking nicknames in certificates. (Clients
16002 have certificates so that they can look like Tor servers, but in
16003 the future we might want to allow them to look like regular TLS
16004 clients instead. Nicknames in certificates serve no purpose other
16005 than making our protocol easier to recognize on the wire.)
16006 - Revise messages on handshake failure again to be even more clear about
16007 which are incoming connections and which are outgoing.
16008 - Discard any v1 directory info that's over 1 month old (for
16009 directories) or over 1 week old (for running-routers lists).
16010 - Do not warn when individual nodes in the configuration's EntryNodes,
16011 ExitNodes, etc are down: warn only when all possible nodes
16012 are down. (Fixes bug 348.)
16013 - Always remove expired routers and networkstatus docs before checking
16014 whether we have enough information to build circuits. (Fixes
16016 - Put a lower-bound on MaxAdvertisedBandwidth.
16019 Changes in version 0.1.2.7-alpha - 2007-02-06
16020 o Major bugfixes (rate limiting):
16021 - Servers decline directory requests much more aggressively when
16022 they're low on bandwidth. Otherwise they end up queueing more and
16023 more directory responses, which can't be good for latency.
16024 - But never refuse directory requests from local addresses.
16025 - Fix a memory leak when sending a 503 response for a networkstatus
16027 - Be willing to read or write on local connections (e.g. controller
16028 connections) even when the global rate limiting buckets are empty.
16029 - If our system clock jumps back in time, don't publish a negative
16030 uptime in the descriptor. Also, don't let the global rate limiting
16031 buckets go absurdly negative.
16032 - Flush local controller connection buffers periodically as we're
16033 writing to them, so we avoid queueing 4+ megabytes of data before
16036 o Major bugfixes (NT services):
16037 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16038 command-line flag so that admins can override the default by saying
16039 "tor --service install --user "SomeUser"". This will not affect
16040 existing installed services. Also, warn the user that the service
16041 will look for its configuration file in the service user's
16042 %appdata% directory. (We can't do the 'hardwire the user's appdata
16043 directory' trick any more, since we may not have read access to that
16046 o Major bugfixes (other):
16047 - Previously, we would cache up to 16 old networkstatus documents
16048 indefinitely, if they came from nontrusted authorities. Now we
16049 discard them if they are more than 10 days old.
16050 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
16052 - Detect and reject malformed DNS responses containing circular
16054 - If exits are rare enough that we're not marking exits as guards,
16055 ignore exit bandwidth when we're deciding the required bandwidth
16057 - When we're handling a directory connection tunneled over Tor,
16058 don't fill up internal memory buffers with all the data we want
16059 to tunnel; instead, only add it if the OR connection that will
16060 eventually receive it has some room for it. (This can lead to
16061 slowdowns in tunneled dir connections; a better solution will have
16062 to wait for 0.2.0.)
16064 o Minor bugfixes (dns):
16065 - Add some defensive programming to eventdns.c in an attempt to catch
16066 possible memory-stomping bugs.
16067 - Detect and reject DNS replies containing IPv4 or IPv6 records with
16068 an incorrect number of bytes. (Previously, we would ignore the
16070 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
16071 in the correct order, and doesn't crash.
16072 - Free memory held in recently-completed DNS lookup attempts on exit.
16073 This was not a memory leak, but may have been hiding memory leaks.
16074 - Handle TTL values correctly on reverse DNS lookups.
16075 - Treat failure to parse resolv.conf as an error.
16077 o Minor bugfixes (other):
16078 - Fix crash with "tor --list-fingerprint" (reported by seeess).
16079 - When computing clock skew from directory HTTP headers, consider what
16080 time it was when we finished asking for the directory, not what
16082 - Expire socks connections if they spend too long waiting for the
16083 handshake to finish. Previously we would let them sit around for
16084 days, if the connecting application didn't close them either.
16085 - And if the socks handshake hasn't started, don't send a
16086 "DNS resolve socks failed" handshake reply; just close it.
16087 - Stop using C functions that OpenBSD's linker doesn't like.
16088 - Don't launch requests for descriptors unless we have networkstatuses
16089 from at least half of the authorities. This delays the first
16090 download slightly under pathological circumstances, but can prevent
16091 us from downloading a bunch of descriptors we don't need.
16092 - Do not log IPs with TLS failures for incoming TLS
16093 connections. (Fixes bug 382.)
16094 - If the user asks to use invalid exit nodes, be willing to use
16096 - Stop using the reserved ac_cv namespace in our configure script.
16097 - Call stat() slightly less often; use fstat() when possible.
16098 - Refactor the way we handle pending circuits when an OR connection
16099 completes or fails, in an attempt to fix a rare crash bug.
16100 - Only rewrite a conn's address based on X-Forwarded-For: headers
16101 if it's a parseable public IP address; and stop adding extra quotes
16102 to the resulting address.
16105 - Weight directory requests by advertised bandwidth. Now we can
16106 let servers enable write limiting but still allow most clients to
16107 succeed at their directory requests. (We still ignore weights when
16108 choosing a directory authority; I hope this is a feature.)
16111 - Create a new file ReleaseNotes which was the old ChangeLog. The
16112 new ChangeLog file now includes the summaries for all development
16114 - Check for addresses with invalid characters at the exit as well
16115 as at the client, and warn less verbosely when they fail. You can
16116 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
16117 - Adapt a patch from goodell to let the contrib/exitlist script
16118 take arguments rather than require direct editing.
16119 - Inform the server operator when we decide not to advertise a
16120 DirPort due to AccountingMax enabled or a low BandwidthRate. It
16121 was confusing Zax, so now we're hopefully more helpful.
16122 - Bring us one step closer to being able to establish an encrypted
16123 directory tunnel without knowing a descriptor first. Still not
16124 ready yet. As part of the change, now assume we can use a
16125 create_fast cell if we don't know anything about a router.
16126 - Allow exit nodes to use nameservers running on ports other than 53.
16127 - Servers now cache reverse DNS replies.
16128 - Add an --ignore-missing-torrc command-line option so that we can
16129 get the "use sensible defaults if the configuration file doesn't
16130 exist" behavior even when specifying a torrc location on the command
16133 o Minor features (controller):
16134 - Track reasons for OR connection failure; make these reasons
16135 available via the controller interface. (Patch from Mike Perry.)
16136 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16137 can learn when clients are sending malformed hostnames to Tor.
16138 - Clean up documentation for controller status events.
16139 - Add a REMAP status to stream events to note that a stream's
16140 address has changed because of a cached address or a MapAddress
16144 Changes in version 0.1.2.6-alpha - 2007-01-09
16146 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
16147 connection handles more than 4 gigs in either direction, we crash.
16148 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
16149 advertised exit node, somebody might try to exit from us when
16150 we're bootstrapping and before we've built our descriptor yet.
16151 Refuse the connection rather than crashing.
16154 - Warn if we (as a server) find that we've resolved an address that we
16155 weren't planning to resolve.
16156 - Warn that using select() on any libevent version before 1.1 will be
16157 unnecessarily slow (even for select()).
16158 - Flush ERR-level controller status events just like we currently
16159 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16160 the controller from learning about current events.
16162 o Minor features (more controller status events):
16163 - Implement EXTERNAL_ADDRESS server status event so controllers can
16164 learn when our address changes.
16165 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
16166 can learn when directories reject our descriptor.
16167 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
16168 can learn when a client application is speaking a non-socks protocol
16170 - Implement DANGEROUS_SOCKS client status event so controllers
16171 can learn when a client application is leaking DNS addresses.
16172 - Implement BUG general status event so controllers can learn when
16173 Tor is unhappy about its internal invariants.
16174 - Implement CLOCK_SKEW general status event so controllers can learn
16175 when Tor thinks the system clock is set incorrectly.
16176 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
16177 server status events so controllers can learn when their descriptors
16178 are accepted by a directory.
16179 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
16180 server status events so controllers can learn about Tor's progress in
16181 deciding whether it's reachable from the outside.
16182 - Implement BAD_LIBEVENT general status event so controllers can learn
16183 when we have a version/method combination in libevent that needs to
16185 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
16186 and DNS_USELESS server status events so controllers can learn
16187 about changes to DNS server status.
16189 o Minor features (directory):
16190 - Authorities no longer recommend exits as guards if this would shift
16191 too much load to the exit nodes.
16194 Changes in version 0.1.2.5-alpha - 2007-01-06
16196 - Enable write limiting as well as read limiting. Now we sacrifice
16197 capacity if we're pushing out lots of directory traffic, rather
16198 than overrunning the user's intended bandwidth limits.
16199 - Include TLS overhead when counting bandwidth usage; previously, we
16200 would count only the bytes sent over TLS, but not the bytes used
16202 - Support running the Tor service with a torrc not in the same
16203 directory as tor.exe and default to using the torrc located in
16204 the %appdata%\Tor\ of the user who installed the service. Patch
16206 - Servers now check for the case when common DNS requests are going to
16207 wildcarded addresses (i.e. all getting the same answer), and change
16208 their exit policy to reject *:* if it's happening.
16209 - Implement BEGIN_DIR cells, so we can connect to the directory
16210 server via TLS to do encrypted directory requests rather than
16211 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16212 config options if you like.
16214 o Minor features (config and docs):
16215 - Start using the state file to store bandwidth accounting data:
16216 the bw_accounting file is now obsolete. We'll keep generating it
16217 for a while for people who are still using 0.1.2.4-alpha.
16218 - Try to batch changes to the state file so that we do as few
16219 disk writes as possible while still storing important things in
16221 - The state file and the bw_accounting file get saved less often when
16222 the AvoidDiskWrites config option is set.
16223 - Make PIDFile work on Windows (untested).
16224 - Add internal descriptions for a bunch of configuration options:
16225 accessible via controller interface and in comments in saved
16227 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16228 NNTP by default, so this seems like a sensible addition.
16229 - Clients now reject hostnames with invalid characters. This should
16230 avoid some inadvertent info leaks. Add an option
16231 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16232 is running a private network with hosts called @, !, and #.
16233 - Add a maintainer script to tell us which options are missing
16234 documentation: "make check-docs".
16235 - Add a new address-spec.txt document to describe our special-case
16236 addresses: .exit, .onion, and .noconnnect.
16238 o Minor features (DNS):
16239 - Ongoing work on eventdns infrastructure: now it has dns server
16240 and ipv6 support. One day Tor will make use of it.
16241 - Add client-side caching for reverse DNS lookups.
16242 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16243 - When we change nameservers or IP addresses, reset and re-launch
16244 our tests for DNS hijacking.
16246 o Minor features (directory):
16247 - Authorities now specify server versions in networkstatus. This adds
16248 about 2% to the size of compressed networkstatus docs, and allows
16249 clients to tell which servers support BEGIN_DIR and which don't.
16250 The implementation is forward-compatible with a proposed future
16251 protocol version scheme not tied to Tor versions.
16252 - DirServer configuration lines now have an orport= option so
16253 clients can open encrypted tunnels to the authorities without
16254 having downloaded their descriptors yet. Enabled for moria1,
16255 moria2, tor26, and lefkada now in the default configuration.
16256 - Directory servers are more willing to send a 503 "busy" if they
16257 are near their write limit, especially for v1 directory requests.
16258 Now they can use their limited bandwidth for actual Tor traffic.
16259 - Clients track responses with status 503 from dirservers. After a
16260 dirserver has given us a 503, we try not to use it until an hour has
16261 gone by, or until we have no dirservers that haven't given us a 503.
16262 - When we get a 503 from a directory, and we're not a server, we don't
16263 count the failure against the total number of failures allowed
16264 for the thing we're trying to download.
16265 - Report X-Your-Address-Is correctly from tunneled directory
16266 connections; don't report X-Your-Address-Is when it's an internal
16267 address; and never believe reported remote addresses when they're
16269 - Protect against an unlikely DoS attack on directory servers.
16270 - Add a BadDirectory flag to network status docs so that authorities
16271 can (eventually) tell clients about caches they believe to be
16274 o Minor features (controller):
16275 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16276 - Reimplement GETINFO so that info/names stays in sync with the
16278 - Implement "GETINFO fingerprint".
16279 - Implement "SETEVENTS GUARD" so controllers can get updates on
16280 entry guard status as it changes.
16282 o Minor features (clean up obsolete pieces):
16283 - Remove some options that have been deprecated since at least
16284 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16285 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16286 to set log options.
16287 - We no longer look for identity and onion keys in "identity.key" and
16288 "onion.key" -- these were replaced by secret_id_key and
16289 secret_onion_key in 0.0.8pre1.
16290 - We no longer require unrecognized directory entries to be
16293 o Major bugfixes (security):
16294 - Stop sending the HttpProxyAuthenticator string to directory
16295 servers when directory connections are tunnelled through Tor.
16296 - Clients no longer store bandwidth history in the state file.
16297 - Do not log introduction points for hidden services if SafeLogging
16299 - When generating bandwidth history, round down to the nearest
16300 1k. When storing accounting data, round up to the nearest 1k.
16301 - When we're running as a server, remember when we last rotated onion
16302 keys, so that we will rotate keys once they're a week old even if
16303 we never stay up for a week ourselves.
16305 o Major bugfixes (other):
16306 - Fix a longstanding bug in eventdns that prevented the count of
16307 timed-out resolves from ever being reset. This bug caused us to
16308 give up on a nameserver the third time it timed out, and try it
16309 10 seconds later... and to give up on it every time it timed out
16311 - Take out the '5 second' timeout from the connection retry
16312 schedule. Now the first connect attempt will wait a full 10
16313 seconds before switching to a new circuit. Perhaps this will help
16314 a lot. Based on observations from Mike Perry.
16315 - Fix a bug on the Windows implementation of tor_mmap_file() that
16316 would prevent the cached-routers file from ever loading. Reported
16320 - Fix an assert failure when a directory authority sets
16321 AuthDirRejectUnlisted and then receives a descriptor from an
16322 unlisted router. Reported by seeess.
16323 - Avoid a double-free when parsing malformed DirServer lines.
16324 - Fix a bug when a BSD-style PF socket is first used. Patch from
16326 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
16327 to resolve an address at a given exit node even when they ask for
16329 - Servers no longer ever list themselves in their "family" line,
16330 even if configured to do so. This makes it easier to configure
16331 family lists conveniently.
16332 - When running as a server, don't fall back to 127.0.0.1 when no
16333 nameservers are configured in /etc/resolv.conf; instead, make the
16334 user fix resolv.conf or specify nameservers explicitly. (Resolves
16336 - Stop accepting certain malformed ports in configured exit policies.
16337 - Don't re-write the fingerprint file every restart, unless it has
16339 - Stop warning when a single nameserver fails: only warn when _all_ of
16340 our nameservers have failed. Also, when we only have one nameserver,
16341 raise the threshold for deciding that the nameserver is dead.
16342 - Directory authorities now only decide that routers are reachable
16343 if their identity keys are as expected.
16344 - When the user uses bad syntax in the Log config line, stop
16345 suggesting other bad syntax as a replacement.
16346 - Correctly detect ipv6 DNS capability on OpenBSD.
16348 o Minor bugfixes (controller):
16349 - Report the circuit number correctly in STREAM CLOSED events. Bug
16350 reported by Mike Perry.
16351 - Do not report bizarre values for results of accounting GETINFOs
16352 when the last second's write or read exceeds the allotted bandwidth.
16353 - Report "unrecognized key" rather than an empty string when the
16354 controller tries to fetch a networkstatus that doesn't exist.
16357 Changes in version 0.1.1.26 - 2006-12-14
16358 o Security bugfixes:
16359 - Stop sending the HttpProxyAuthenticator string to directory
16360 servers when directory connections are tunnelled through Tor.
16361 - Clients no longer store bandwidth history in the state file.
16362 - Do not log introduction points for hidden services if SafeLogging
16366 - Fix an assert failure when a directory authority sets
16367 AuthDirRejectUnlisted and then receives a descriptor from an
16368 unlisted router (reported by seeess).
16371 Changes in version 0.1.2.4-alpha - 2006-12-03
16373 - Add support for using natd; this allows FreeBSDs earlier than
16374 5.1.2 to have ipfw send connections through Tor without using
16375 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16378 - Make all connections to addresses of the form ".noconnect"
16379 immediately get closed. This lets application/controller combos
16380 successfully test whether they're talking to the same Tor by
16381 watching for STREAM events.
16382 - Make cross.sh cross-compilation script work even when autogen.sh
16383 hasn't been run. (Patch from Michael Mohr.)
16384 - Statistics dumped by -USR2 now include a breakdown of public key
16385 operations, for profiling.
16388 - Fix a major leak when directory authorities parse their
16389 approved-routers list, a minor memory leak when we fail to pick
16390 an exit node, and a few rare leaks on errors.
16391 - Handle TransPort connections even when the server sends data before
16392 the client sends data. Previously, the connection would just hang
16393 until the client sent data. (Patch from tup based on patch from
16395 - Avoid assert failure when our cached-routers file is empty on
16399 - Don't log spurious warnings when we see a circuit close reason we
16400 don't recognize; it's probably just from a newer version of Tor.
16401 - Have directory authorities allow larger amounts of drift in uptime
16402 without replacing the server descriptor: previously, a server that
16403 restarted every 30 minutes could have 48 "interesting" descriptors
16405 - Start linking to the Tor specification and Tor reference manual
16406 correctly in the Windows installer.
16407 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16408 Tor/Privoxy we also uninstall Vidalia.
16409 - Resume building on Irix64, and fix a lot of warnings from its
16410 MIPSpro C compiler.
16411 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16412 when we're running as a client.
16415 Changes in version 0.1.1.25 - 2006-11-04
16417 - When a client asks us to resolve (rather than connect to)
16418 an address, and we have a cached answer, give them the cached
16419 answer. Previously, we would give them no answer at all.
16420 - We were building exactly the wrong circuits when we predict
16421 hidden service requirements, meaning Tor would have to build all
16422 its circuits on demand.
16423 - If none of our live entry guards have a high uptime, but we
16424 require a guard with a high uptime, try adding a new guard before
16425 we give up on the requirement. This patch should make long-lived
16426 connections more stable on average.
16427 - When testing reachability of our DirPort, don't launch new
16428 tests when there's already one in progress -- unreachable
16429 servers were stacking up dozens of testing streams.
16431 o Security bugfixes:
16432 - When the user sends a NEWNYM signal, clear the client-side DNS
16433 cache too. Otherwise we continue to act on previous information.
16436 - Avoid a memory corruption bug when creating a hash table for
16438 - Avoid possibility of controller-triggered crash when misusing
16439 certain commands from a v0 controller on platforms that do not
16440 handle printf("%s",NULL) gracefully.
16441 - Avoid infinite loop on unexpected controller input.
16442 - Don't log spurious warnings when we see a circuit close reason we
16443 don't recognize; it's probably just from a newer version of Tor.
16444 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16445 Tor/Privoxy we also uninstall Vidalia.
16448 Changes in version 0.1.2.3-alpha - 2006-10-29
16450 - Prepare for servers to publish descriptors less often: never
16451 discard a descriptor simply for being too old until either it is
16452 recommended by no authorities, or until we get a better one for
16453 the same router. Make caches consider retaining old recommended
16454 routers for even longer.
16455 - If most authorities set a BadExit flag for a server, clients
16456 don't think of it as a general-purpose exit. Clients only consider
16457 authorities that advertise themselves as listing bad exits.
16458 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16459 headers for content, so that we can work better in the presence of
16460 caching HTTP proxies.
16461 - Allow authorities to list nodes as bad exits by fingerprint or by
16464 o Minor features, controller:
16465 - Add a REASON field to CIRC events; for backward compatibility, this
16466 field is sent only to controllers that have enabled the extended
16467 event format. Also, add additional reason codes to explain why
16468 a given circuit has been destroyed or truncated. (Patches from
16470 - Add a REMOTE_REASON field to extended CIRC events to tell the
16471 controller about why a remote OR told us to close a circuit.
16472 - Stream events also now have REASON and REMOTE_REASON fields,
16473 working much like those for circuit events.
16474 - There's now a GETINFO ns/... field so that controllers can ask Tor
16475 about the current status of a router.
16476 - A new event type "NS" to inform a controller when our opinion of
16477 a router's status has changed.
16478 - Add a GETINFO events/names and GETINFO features/names so controllers
16479 can tell which events and features are supported.
16480 - A new CLEARDNSCACHE signal to allow controllers to clear the
16481 client-side DNS cache without expiring circuits.
16483 o Security bugfixes:
16484 - When the user sends a NEWNYM signal, clear the client-side DNS
16485 cache too. Otherwise we continue to act on previous information.
16488 - Avoid sending junk to controllers or segfaulting when a controller
16489 uses EVENT_NEW_DESC with verbose nicknames.
16490 - Stop triggering asserts if the controller tries to extend hidden
16491 service circuits (reported by mwenge).
16492 - Avoid infinite loop on unexpected controller input.
16493 - When the controller does a "GETINFO network-status", tell it
16494 about even those routers whose descriptors are very old, and use
16495 long nicknames where appropriate.
16496 - Change NT service functions to be loaded on demand. This lets us
16497 build with MinGW without breaking Tor for Windows 98 users.
16498 - Do DirPort reachability tests less often, since a single test
16499 chews through many circuits before giving up.
16500 - In the hidden service example in torrc.sample, stop recommending
16501 esoteric and discouraged hidden service options.
16502 - When stopping an NT service, wait up to 10 sec for it to actually
16503 stop. Patch from Matt Edman; resolves bug 295.
16504 - Fix handling of verbose nicknames with ORCONN controller events:
16505 make them show up exactly when requested, rather than exactly when
16507 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
16508 printing a duplicate "$" in the keys we send (reported by mwenge).
16509 - Correctly set maximum connection limit on Cygwin. (This time
16511 - Try to detect Windows correctly when cross-compiling.
16512 - Detect the size of the routers file correctly even if it is
16513 corrupted (on systems without mmap) or not page-aligned (on systems
16514 with mmap). This bug was harmless.
16515 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16516 to open a stream fails; now we do in more cases. This should
16517 make clients able to find a good exit faster in some cases, since
16518 unhandleable requests will now get an error rather than timing out.
16519 - Resolve two memory leaks when rebuilding the on-disk router cache
16520 (reported by fookoowa).
16521 - Clean up minor code warnings suggested by the MIPSpro C compiler,
16522 and reported by some Centos users.
16523 - Controller signals now work on non-Unix platforms that don't define
16524 SIGUSR1 and SIGUSR2 the way we expect.
16525 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16526 values before failing, and always enables eventdns.
16527 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16528 Try to fix this in configure.in by checking for most functions
16529 before we check for libevent.
16532 Changes in version 0.1.2.2-alpha - 2006-10-07
16534 - Make our async eventdns library on-by-default for Tor servers,
16535 and plan to deprecate the separate dnsworker threads.
16536 - Add server-side support for "reverse" DNS lookups (using PTR
16537 records so clients can determine the canonical hostname for a given
16538 IPv4 address). Only supported by servers using eventdns; servers
16539 now announce in their descriptors whether they support eventdns.
16540 - Specify and implement client-side SOCKS5 interface for reverse DNS
16541 lookups (see doc/socks-extensions.txt).
16542 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
16543 connect to directory servers through Tor. Previously, clients needed
16544 to find Tor exits to make private connections to directory servers.
16545 - Avoid choosing Exit nodes for entry or middle hops when the
16546 total bandwidth available from non-Exit nodes is much higher than
16547 the total bandwidth available from Exit nodes.
16548 - Workaround for name servers (like Earthlink's) that hijack failing
16549 DNS requests and replace the no-such-server answer with a "helpful"
16550 redirect to an advertising-driven search portal. Also work around
16551 DNS hijackers who "helpfully" decline to hijack known-invalid
16552 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16553 lets you turn it off.
16554 - Send out a burst of long-range padding cells once we've established
16555 that we're reachable. Spread them over 4 circuits, so hopefully
16556 a few will be fast. This exercises our bandwidth and bootstraps
16557 us into the directory more quickly.
16559 o New/improved config options:
16560 - Add new config option "ResolvConf" to let the server operator
16561 choose an alternate resolve.conf file when using eventdns.
16562 - Add an "EnforceDistinctSubnets" option to control our "exclude
16563 servers on the same /16" behavior. It's still on by default; this
16564 is mostly for people who want to operate private test networks with
16565 all the machines on the same subnet.
16566 - If one of our entry guards is on the ExcludeNodes list, or the
16567 directory authorities don't think it's a good guard, treat it as
16568 if it were unlisted: stop using it as a guard, and throw it off
16569 the guards list if it stays that way for a long time.
16570 - Allow directory authorities to be marked separately as authorities
16571 for the v1 directory protocol, the v2 directory protocol, and
16572 as hidden service directories, to make it easier to retire old
16573 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16574 to continue being hidden service authorities too.
16575 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16577 o Minor features, controller:
16578 - Fix CIRC controller events so that controllers can learn the
16579 identity digests of non-Named servers used in circuit paths.
16580 - Let controllers ask for more useful identifiers for servers. Instead
16581 of learning identity digests for un-Named servers and nicknames
16582 for Named servers, the new identifiers include digest, nickname,
16583 and indication of Named status. Off by default; see control-spec.txt
16584 for more information.
16585 - Add a "getinfo address" controller command so it can display Tor's
16586 best guess to the user.
16587 - New controller event to alert the controller when our server
16588 descriptor has changed.
16589 - Give more meaningful errors on controller authentication failure.
16591 o Minor features, other:
16592 - When asked to resolve a hostname, don't use non-exit servers unless
16593 requested to do so. This allows servers with broken DNS to be
16594 useful to the network.
16595 - Divide eventdns log messages into warn and info messages.
16596 - Reserve the nickname "Unnamed" for routers that can't pick
16597 a hostname: any router can call itself Unnamed; directory
16598 authorities will never allocate Unnamed to any particular router;
16599 clients won't believe that any router is the canonical Unnamed.
16600 - Only include function names in log messages for info/debug messages.
16601 For notice/warn/err, the content of the message should be clear on
16602 its own, and printing the function name only confuses users.
16603 - Avoid some false positives during reachability testing: don't try
16604 to test via a server that's on the same /24 as us.
16605 - If we fail to build a circuit to an intended enclave, and it's
16606 not mandatory that we use that enclave, stop wanting it.
16607 - When eventdns is enabled, allow multithreaded builds on NetBSD and
16608 OpenBSD. (We had previously disabled threads on these platforms
16609 because they didn't have working thread-safe resolver functions.)
16611 o Major bugfixes, anonymity/security:
16612 - If a client asked for a server by name, and there's a named server
16613 in our network-status but we don't have its descriptor yet, we
16614 could return an unnamed server instead.
16615 - Fix NetBSD bug that could allow someone to force uninitialized RAM
16616 to be sent to a server's DNS resolver. This only affects NetBSD
16617 and other platforms that do not bounds-check tolower().
16618 - Reject (most) attempts to use Tor circuits with length one. (If
16619 many people start using Tor as a one-hop proxy, exit nodes become
16620 a more attractive target for compromise.)
16621 - Just because your DirPort is open doesn't mean people should be
16622 able to remotely teach you about hidden service descriptors. Now
16623 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16625 o Major bugfixes, other:
16626 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
16627 - When a client asks the server to resolve (not connect to)
16628 an address, and it has a cached answer, give them the cached answer.
16629 Previously, the server would give them no answer at all.
16630 - Allow really slow clients to not hang up five minutes into their
16631 directory downloads (suggested by Adam J. Richter).
16632 - We were building exactly the wrong circuits when we anticipated
16633 hidden service requirements, meaning Tor would have to build all
16634 its circuits on demand.
16635 - Avoid crashing when we mmap a router cache file of size 0.
16636 - When testing reachability of our DirPort, don't launch new
16637 tests when there's already one in progress -- unreachable
16638 servers were stacking up dozens of testing streams.
16640 o Minor bugfixes, correctness:
16641 - If we're a directory mirror and we ask for "all" network status
16642 documents, we would discard status documents from authorities
16643 we don't recognize.
16644 - Avoid a memory corruption bug when creating a hash table for
16646 - Avoid controller-triggered crash when misusing certain commands
16647 from a v0 controller on platforms that do not handle
16648 printf("%s",NULL) gracefully.
16649 - Don't crash when a controller sends a third argument to an
16650 "extendcircuit" request.
16651 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16652 response; fix error code when "getinfo dir/status/" fails.
16653 - Avoid crash when telling controller stream-status and a stream
16655 - Patch from Adam Langley to fix assert() in eventdns.c.
16656 - Fix a debug log message in eventdns to say "X resolved to Y"
16657 instead of "X resolved to X".
16658 - Make eventdns give strings for DNS errors, not just error numbers.
16659 - Track unreachable entry guards correctly: don't conflate
16660 'unreachable by us right now' with 'listed as down by the directory
16661 authorities'. With the old code, if a guard was unreachable by
16662 us but listed as running, it would clog our guard list forever.
16663 - Behave correctly in case we ever have a network with more than
16664 2GB/s total advertised capacity.
16665 - Make TrackExitHosts case-insensitive, and fix the behavior of
16666 ".suffix" TrackExitHosts items to avoid matching in the middle of
16668 - Finally fix the openssl warnings from newer gccs that believe that
16669 ignoring a return value is okay, but casting a return value and
16670 then ignoring it is a sign of madness.
16671 - Prevent the contrib/exitlist script from printing the same
16672 result more than once.
16673 - Patch from Steve Hildrey: Generate network status correctly on
16674 non-versioning dirservers.
16675 - Don't listen to the X-Your-Address-Is hint if you did the lookup
16676 via Tor; otherwise you'll think you're the exit node's IP address.
16678 o Minor bugfixes, performance:
16679 - Two small performance improvements on parsing descriptors.
16680 - Major performance improvement on inserting descriptors: change
16681 algorithm from O(n^2) to O(n).
16682 - Make the common memory allocation path faster on machines where
16683 malloc(0) returns a pointer.
16684 - Start remembering X-Your-Address-Is directory hints even if you're
16685 a client, so you can become a server more smoothly.
16686 - Avoid duplicate entries on MyFamily line in server descriptor.
16688 o Packaging, features:
16689 - Remove architecture from OS X builds. The official builds are
16690 now universal binaries.
16691 - The Debian package now uses --verify-config when (re)starting,
16692 to distinguish configuration errors from other errors.
16693 - Update RPMs to require libevent 1.1b.
16695 o Packaging, bugfixes:
16696 - Patches so Tor builds with MinGW on Windows.
16697 - Patches so Tor might run on Cygwin again.
16698 - Resume building on non-gcc compilers and ancient gcc. Resume
16699 building with the -O0 compile flag. Resume building cleanly on
16701 - Run correctly on OS X platforms with case-sensitive filesystems.
16702 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
16703 - Add autoconf checks so Tor can build on Solaris x86 again.
16706 - Documented (and renamed) ServerDNSSearchDomains and
16707 ServerDNSResolvConfFile options.
16708 - Be clearer that the *ListenAddress directives can be repeated
16712 Changes in version 0.1.1.24 - 2006-09-29
16714 - Allow really slow clients to not hang up five minutes into their
16715 directory downloads (suggested by Adam J. Richter).
16716 - Fix major performance regression from 0.1.0.x: instead of checking
16717 whether we have enough directory information every time we want to
16718 do something, only check when the directory information has changed.
16719 This should improve client CPU usage by 25-50%.
16720 - Don't crash if, after a server has been running for a while,
16721 it can't resolve its hostname.
16724 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16725 - Don't crash when the controller receives a third argument to an
16726 "extendcircuit" request.
16727 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16728 response; fix error code when "getinfo dir/status/" fails.
16729 - Fix configure.in to not produce broken configure files with
16730 more recent versions of autoconf. Thanks to Clint for his auto*
16732 - Fix security bug on NetBSD that could allow someone to force
16733 uninitialized RAM to be sent to a server's DNS resolver. This
16734 only affects NetBSD and other platforms that do not bounds-check
16736 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16737 methods: these are known to be buggy.
16738 - If we're a directory mirror and we ask for "all" network status
16739 documents, we would discard status documents from authorities
16740 we don't recognize.
16743 Changes in version 0.1.2.1-alpha - 2006-08-27
16745 - Add "eventdns" async dns library from Adam Langley, tweaked to
16746 build on OSX and Windows. Only enabled if you pass the
16747 --enable-eventdns argument to configure.
16748 - Allow servers with no hostname or IP address to learn their
16749 IP address by asking the directory authorities. This code only
16750 kicks in when you would normally have exited with a "no address"
16751 error. Nothing's authenticated, so use with care.
16752 - Rather than waiting a fixed amount of time between retrying
16753 application connections, we wait only 5 seconds for the first,
16754 10 seconds for the second, and 15 seconds for each retry after
16755 that. Hopefully this will improve the expected user experience.
16756 - Patch from Tup to add support for transparent AP connections:
16757 this basically bundles the functionality of trans-proxy-tor
16758 into the Tor mainline. Now hosts with compliant pf/netfilter
16759 implementations can redirect TCP connections straight to Tor
16760 without diverting through SOCKS. Needs docs.
16761 - Busy directory servers save lots of memory by spooling server
16762 descriptors, v1 directories, and v2 networkstatus docs to buffers
16763 as needed rather than en masse. Also mmap the cached-routers
16764 files, so we don't need to keep the whole thing in memory too.
16765 - Automatically avoid picking more than one node from the same
16766 /16 network when constructing a circuit.
16767 - Revise and clean up the torrc.sample that we ship with; add
16768 a section for BandwidthRate and BandwidthBurst.
16771 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16772 split connection_t into edge, or, dir, control, and base structs.
16773 These will save quite a bit of memory on busy servers, and they'll
16774 also help us track down bugs in the code and bugs in the spec.
16775 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16776 or later. Log when we are doing this, so we can diagnose it when
16777 it fails. (Also, recommend libevent 1.1b for kqueue and
16778 win32 methods; deprecate libevent 1.0b harder; make libevent
16779 recommendation system saner.)
16780 - Start being able to build universal binaries on OS X (thanks
16782 - Export the default exit policy via the control port, so controllers
16783 don't need to guess what it is / will be later.
16784 - Add a man page entry for ProtocolWarnings.
16785 - Add TestVia config option to the man page.
16786 - Remove even more protocol-related warnings from Tor server logs,
16787 such as bad TLS handshakes and malformed begin cells.
16788 - Stop fetching descriptors if you're not a dir mirror and you
16789 haven't tried to establish any circuits lately. [This currently
16790 causes some dangerous behavior, because when you start up again
16791 you'll use your ancient server descriptors.]
16792 - New DirPort behavior: if you have your dirport set, you download
16793 descriptors aggressively like a directory mirror, whether or not
16794 your ORPort is set.
16795 - Get rid of the router_retry_connections notion. Now routers
16796 no longer try to rebuild long-term connections to directory
16797 authorities, and directory authorities no longer try to rebuild
16798 long-term connections to all servers. We still don't hang up
16799 connections in these two cases though -- we need to look at it
16800 more carefully to avoid flapping, and we likely need to wait til
16801 0.1.1.x is obsolete.
16802 - Drop compatibility with obsolete Tors that permit create cells
16803 to have the wrong circ_id_type.
16804 - Re-enable per-connection rate limiting. Get rid of the "OP
16805 bandwidth" concept. Lay groundwork for "bandwidth classes" --
16806 separate global buckets that apply depending on what sort of conn
16808 - Start publishing one minute or so after we find our ORPort
16809 to be reachable. This will help reduce the number of descriptors
16810 we have for ourselves floating around, since it's quite likely
16811 other things (e.g. DirPort) will change during that minute too.
16812 - Fork the v1 directory protocol into its own spec document,
16813 and mark dir-spec.txt as the currently correct (v2) spec.
16816 - When we find our DirPort to be reachable, publish a new descriptor
16817 so we'll tell the world (reported by pnx).
16818 - Publish a new descriptor after we hup/reload. This is important
16819 if our config has changed such that we'll want to start advertising
16820 our DirPort now, etc.
16821 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16822 - When we have a state file we cannot parse, tell the user and
16823 move it aside. Now we avoid situations where the user starts
16824 Tor in 1904, Tor writes a state file with that timestamp in it,
16825 the user fixes her clock, and Tor refuses to start.
16826 - Fix configure.in to not produce broken configure files with
16827 more recent versions of autoconf. Thanks to Clint for his auto*
16829 - "tor --verify-config" now exits with -1(255) or 0 depending on
16830 whether the config options are bad or good.
16831 - Resolve bug 321 when using dnsworkers: append a period to every
16832 address we resolve at the exit node, so that we do not accidentally
16833 pick up local addresses, and so that failing searches are retried
16834 in the resolver search domains. (This is already solved for
16835 eventdns.) (This breaks Blossom servers for now.)
16836 - If we are using an exit enclave and we can't connect, e.g. because
16837 its webserver is misconfigured to not listen on localhost, then
16838 back off and try connecting from somewhere else before we fail.
16841 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
16842 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16843 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16844 when the IP address is mapped through MapAddress to a hostname.
16845 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16846 useless IPv6 DNS resolves.
16847 - Patch suggested by Karsten Loesing: respond to SIGNAL command
16848 before we execute the signal, in case the signal shuts us down.
16849 - Clean up AllowInvalidNodes man page entry.
16850 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16851 - Add more asserts to track down an assert error on a windows Tor
16852 server with connection_add being called with socket == -1.
16853 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16854 - Fix misleading log messages: an entry guard that is "unlisted",
16855 as well as not known to be "down" (because we've never heard
16856 of it), is not therefore "up".
16857 - Remove code to special-case "-cvs" ending, since it has not
16858 actually mattered since 0.0.9.
16859 - Make our socks5 handling more robust to broken socks clients:
16860 throw out everything waiting on the buffer in between socks
16861 handshake phases, since they can't possibly (so the theory
16862 goes) have predicted what we plan to respond to them.
16865 Changes in version 0.1.1.23 - 2006-07-30
16867 - Fast Tor servers, especially exit nodes, were triggering asserts
16868 due to a bug in handling the list of pending DNS resolves. Some
16869 bugs still remain here; we're hunting them.
16870 - Entry guards could crash clients by sending unexpected input.
16871 - More fixes on reachability testing: if you find yourself reachable,
16872 then don't ever make any client requests (so you stop predicting
16873 circuits), then hup or have your clock jump, then later your IP
16874 changes, you won't think circuits are working, so you won't try to
16875 test reachability, so you won't publish.
16878 - Avoid a crash if the controller does a resetconf firewallports
16879 and then a setconf fascistfirewall=1.
16880 - Avoid an integer underflow when the dir authority decides whether
16881 a router is stable: we might wrongly label it stable, and compute
16882 a slightly wrong median stability, when a descriptor is published
16884 - Fix a place where we might trigger an assert if we can't build our
16885 own server descriptor yet.
16888 Changes in version 0.1.1.22 - 2006-07-05
16890 - Fix a big bug that was causing servers to not find themselves
16891 reachable if they changed IP addresses. Since only 0.1.1.22+
16892 servers can do reachability testing correctly, now we automatically
16893 make sure to test via one of these.
16894 - Fix to allow clients and mirrors to learn directory info from
16895 descriptor downloads that get cut off partway through.
16896 - Directory authorities had a bug in deciding if a newly published
16897 descriptor was novel enough to make everybody want a copy -- a few
16898 servers seem to be publishing new descriptors many times a minute.
16900 - Fix a rare bug that was causing some servers to complain about
16901 "closing wedged cpuworkers" and skip some circuit create requests.
16902 - Make the Exit flag in directory status documents actually work.
16905 Changes in version 0.1.1.21 - 2006-06-10
16906 o Crash and assert fixes from 0.1.1.20:
16907 - Fix a rare crash on Tor servers that have enabled hibernation.
16908 - Fix a seg fault on startup for Tor networks that use only one
16909 directory authority.
16910 - Fix an assert from a race condition that occurs on Tor servers
16911 while exiting, where various threads are trying to log that they're
16912 exiting, and delete the logs, at the same time.
16913 - Make our unit tests pass again on certain obscure platforms.
16916 - Add support for building SUSE RPM packages.
16917 - Speed up initial bootstrapping for clients: if we are making our
16918 first ever connection to any entry guard, then don't mark it down
16920 - When only one Tor server in the network is labelled as a guard,
16921 and we've already picked him, we would cycle endlessly picking him
16922 again, being unhappy about it, etc. Now we specifically exclude
16923 current guards when picking a new guard.
16924 - Servers send create cells more reliably after the TLS connection
16925 is established: we were sometimes forgetting to send half of them
16926 when we had more than one pending.
16927 - If we get a create cell that asks us to extend somewhere, but the
16928 Tor server there doesn't match the expected digest, we now send
16929 a destroy cell back, rather than silently doing nothing.
16930 - Make options->RedirectExit work again.
16931 - Make cookie authentication for the controller work again.
16932 - Stop being picky about unusual characters in the arguments to
16933 mapaddress. It's none of our business.
16934 - Add a new config option "TestVia" that lets you specify preferred
16935 middle hops to use for test circuits. Perhaps this will let me
16936 debug the reachability problems better.
16938 o Log / documentation fixes:
16939 - If we're a server and some peer has a broken TLS certificate, don't
16940 log about it unless ProtocolWarnings is set, i.e., we want to hear
16941 about protocol violations by others.
16942 - Fix spelling of VirtualAddrNetwork in man page.
16943 - Add a better explanation at the top of the autogenerated torrc file
16944 about what happened to our old torrc.
16947 Changes in version 0.1.1.20 - 2006-05-23
16949 - Downgrade a log severity where servers complain that they're
16951 - Avoid a compile warning on FreeBSD.
16952 - Remove string size limit on NEWDESC messages; solve bug 291.
16953 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
16954 more thoroughly when we're running on windows.
16957 Changes in version 0.1.1.19-rc - 2006-05-03
16959 - Regenerate our local descriptor if it's dirty and we try to use
16960 it locally (e.g. if it changes during reachability detection).
16961 - If we setconf our ORPort to 0, we continued to listen on the
16962 old ORPort and receive connections.
16963 - Avoid a second warning about machine/limits.h on Debian
16965 - Be willing to add our own routerinfo into the routerlist.
16966 Now authorities will include themselves in their directories
16967 and network-statuses.
16968 - Stop trying to upload rendezvous descriptors to every
16969 directory authority: only try the v1 authorities.
16970 - Servers no longer complain when they think they're not
16971 registered with the directory authorities. There were too many
16973 - Backport dist-rpm changes so rpms can be built without errors.
16976 - Implement an option, VirtualAddrMask, to set which addresses
16977 get handed out in response to mapaddress requests. This works
16978 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16981 Changes in version 0.1.1.18-rc - 2006-04-10
16983 - Work harder to download live network-statuses from all the
16984 directory authorities we know about. Improve the threshold
16985 decision logic so we're more robust to edge cases.
16986 - When fetching rendezvous descriptors, we were willing to ask
16987 v2 authorities too, which would always return 404.
16990 - Stop listing down or invalid nodes in the v1 directory. This will
16991 reduce its bulk by about 1/3, and reduce load on directory
16993 - When deciding whether a router is Fast or Guard-worthy, consider
16994 his advertised BandwidthRate and not just the BandwidthCapacity.
16995 - No longer ship INSTALL and README files -- they are useless now.
16996 - Force rpmbuild to behave and honor target_cpu.
16997 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16998 - Start to include translated versions of the tor-doc-*.html
16999 files, along with the screenshots. Still needs more work.
17000 - Start sending back 512 and 451 errors if mapaddress fails,
17001 rather than not sending anything back at all.
17002 - When we fail to bind or listen on an incoming or outgoing
17003 socket, we should close it before failing. otherwise we just
17004 leak it. (thanks to weasel for finding.)
17005 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
17006 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
17007 - Make NoPublish (even though deprecated) work again.
17008 - Fix a minor security flaw where a versioning auth dirserver
17009 could list a recommended version many times in a row to make
17010 clients more convinced that it's recommended.
17011 - Fix crash bug if there are two unregistered servers running
17012 with the same nickname, one of them is down, and you ask for
17013 them by nickname in your EntryNodes or ExitNodes. Also, try
17014 to pick the one that's running rather than an arbitrary one.
17015 - Fix an infinite loop we could hit if we go offline for too long.
17016 - Complain when we hit WSAENOBUFS on recv() or write() too.
17017 Perhaps this will help us hunt the bug.
17018 - If you're not a versioning dirserver, don't put the string
17019 "client-versions \nserver-versions \n" in your network-status.
17020 - Lower the minimum required number of file descriptors to 1000,
17021 so we can have some overhead for Valgrind on Linux, where the
17022 default ulimit -n is 1024.
17025 - Add tor.dizum.com as the fifth authoritative directory server.
17026 - Add a new config option FetchUselessDescriptors, off by default,
17027 for when you plan to run "exitlist" on your client and you want
17028 to know about even the non-running descriptors.
17031 Changes in version 0.1.1.17-rc - 2006-03-28
17033 - Clients and servers since 0.1.1.10-alpha have been expiring
17034 connections whenever they are idle for 5 minutes and they *do*
17035 have circuits on them. Oops. With this new version, clients will
17036 discard their previous entry guard choices and avoid choosing
17037 entry guards running these flawed versions.
17038 - Fix memory leak when uncompressing concatenated zlib streams. This
17039 was causing substantial leaks over time on Tor servers.
17040 - The v1 directory was including servers as much as 48 hours old,
17041 because that's how the new routerlist->routers works. Now only
17042 include them if they're 20 hours old or less.
17045 - Resume building on irix64, netbsd 2.0, etc.
17046 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
17048 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17049 and it is confusing some users.
17050 - Mirrors stop caching the v1 directory so often.
17051 - Make the max number of old descriptors that a cache will hold
17052 rise with the number of directory authorities, so we can scale.
17053 - Change our win32 uname() hack to be more forgiving about what
17054 win32 versions it thinks it's found.
17057 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
17059 - When the controller's *setconf commands fail, collect an error
17060 message in a string and hand it back to the controller.
17061 - Make the v2 dir's "Fast" flag based on relative capacity, just
17062 like "Stable" is based on median uptime. Name everything in the
17063 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17064 - Log server fingerprint on startup, so new server operators don't
17065 have to go hunting around their filesystem for it.
17066 - Return a robots.txt on our dirport to discourage google indexing.
17067 - Let the controller ask for GETINFO dir/status/foo so it can ask
17068 directly rather than connecting to the dir port. Only works when
17069 dirport is set for now.
17071 o New config options rather than constants in the code:
17072 - SocksTimeout: How long do we let a socks connection wait
17073 unattached before we fail it?
17074 - CircuitBuildTimeout: Cull non-open circuits that were born
17075 at least this many seconds ago.
17076 - CircuitIdleTimeout: Cull open clean circuits that were born
17077 at least this many seconds ago.
17080 Changes in version 0.1.1.16-rc - 2006-03-18
17081 o Bugfixes on 0.1.1.15-rc:
17082 - Fix assert when the controller asks to attachstream a connect-wait
17083 or resolve-wait stream.
17084 - Now do address rewriting when the controller asks us to attach
17085 to a particular circuit too. This will let Blossom specify
17086 "moria2.exit" without having to learn what moria2's IP address is.
17087 - Make the "tor --verify-config" command-line work again, so people
17088 can automatically check if their torrc will parse.
17089 - Authoritative dirservers no longer require an open connection from
17090 a server to consider him "reachable". We need this change because
17091 when we add new auth dirservers, old servers won't know not to
17093 - Let Tor build on Sun CC again.
17094 - Fix an off-by-one buffer size in dirserv.c that magically never
17095 hit our three authorities but broke sjmurdoch's own tor network.
17096 - If we as a directory mirror don't know of any v1 directory
17097 authorities, then don't try to cache any v1 directories.
17098 - Stop warning about unknown servers in our family when they are
17099 given as hex digests.
17100 - Stop complaining as quickly to the server operator that he
17101 hasn't registered his nickname/key binding.
17102 - Various cleanups so we can add new V2 Auth Dirservers.
17103 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17104 reflect the updated flags in our v2 dir protocol.
17105 - Resume allowing non-printable characters for exit streams (both
17106 for connecting and for resolving). Now we tolerate applications
17107 that don't follow the RFCs. But continue to block malformed names
17110 o Bugfixes on 0.1.0.x:
17111 - Fix assert bug in close_logs(): when we close and delete logs,
17112 remove them all from the global "logfiles" list.
17113 - Fix minor integer overflow in calculating when we expect to use up
17114 our bandwidth allocation before hibernating.
17115 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
17116 there are multiple SSLs installed with different versions.
17117 - When we try to be a server and Address is not explicitly set and
17118 our hostname resolves to a private IP address, try to use an
17119 interface address if it has a public address. Now Windows machines
17120 that think of themselves as localhost can work by default.
17123 - Let the controller ask for GETINFO dir/server/foo so it can ask
17124 directly rather than connecting to the dir port.
17125 - Let the controller tell us about certain router descriptors
17126 that it doesn't want Tor to use in circuits. Implement
17127 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
17128 - New config option SafeSocks to reject all application connections
17129 using unsafe socks protocols. Defaults to off.
17132 Changes in version 0.1.1.15-rc - 2006-03-11
17133 o Bugfixes and cleanups:
17134 - When we're printing strings from the network, don't try to print
17135 non-printable characters. This protects us against shell escape
17136 sequence exploits, and also against attacks to fool humans into
17137 misreading their logs.
17138 - Fix a bug where Tor would fail to establish any connections if you
17139 left it off for 24 hours and then started it: we were happy with
17140 the obsolete network statuses, but they all referred to router
17141 descriptors that were too old to fetch, so we ended up with no
17142 valid router descriptors.
17143 - Fix a seg fault in the controller's "getinfo orconn-status"
17144 command while listing status on incoming handshaking connections.
17145 Introduce a status name "NEW" for these connections.
17146 - If we get a linelist or linelist_s config option from the torrc
17147 (e.g. ExitPolicy) and it has no value, warn and skip rather than
17148 silently resetting it to its default.
17149 - Don't abandon entry guards until they've been down or gone for
17151 - Cleaner and quieter log messages.
17154 - New controller signal NEWNYM that makes new application requests
17155 use clean circuits.
17156 - Add a new circuit purpose 'controller' to let the controller ask
17157 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
17158 controller command to let you specify the purpose if you're
17159 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
17160 command to let you change a circuit's purpose after it's been
17162 - Accept "private:*" in routerdesc exit policies; not generated yet
17163 because older Tors do not understand it.
17164 - Add BSD-style contributed startup script "rc.subr" from Peter
17168 Changes in version 0.1.1.14-alpha - 2006-02-20
17169 o Bugfixes on 0.1.1.x:
17170 - Don't die if we ask for a stdout or stderr log (even implicitly)
17171 and we're set to RunAsDaemon -- just warn.
17172 - We still had a few bugs in the OR connection rotation code that
17173 caused directory servers to slowly aggregate connections to other
17174 fast Tor servers. This time for sure!
17175 - Make log entries on Win32 include the name of the function again.
17176 - We were treating a pair of exit policies if they were equal even
17177 if one said accept and the other said reject -- causing us to
17178 not always publish a new descriptor since we thought nothing
17180 - Retry pending server downloads as well as pending networkstatus
17181 downloads when we unexpectedly get a socks request.
17182 - We were ignoring the IS_FAST flag in the directory status,
17183 meaning we were willing to pick trivial-bandwidth nodes for "fast"
17185 - If the controller's SAVECONF command fails (e.g. due to file
17186 permissions), let the controller know that it failed.
17189 - If we're trying to be a Tor server and running Windows 95/98/ME
17190 as a server, explain that we'll likely crash.
17191 - When we're a server, a client asks for an old-style directory,
17192 and our write bucket is empty, don't give it to him. This way
17193 small servers can continue to serve the directory *sometimes*,
17194 without getting overloaded.
17195 - Compress exit policies even more -- look for duplicate lines
17197 - Clients now honor the "guard" flag in the router status when
17198 picking entry guards, rather than looking at is_fast or is_stable.
17199 - Retain unrecognized lines in $DATADIR/state file, so that we can
17200 be forward-compatible.
17201 - Generate 18.0.0.0/8 address policy format in descs when we can;
17202 warn when the mask is not reducible to a bit-prefix.
17203 - Let the user set ControlListenAddress in the torrc. This can be
17204 dangerous, but there are some cases (like a secured LAN) where it
17206 - Split ReachableAddresses into ReachableDirAddresses and
17207 ReachableORAddresses, so we can restrict Dir conns to port 80
17208 and OR conns to port 443.
17209 - Now we can target arch and OS in rpm builds (contributed by
17210 Phobos). Also make the resulting dist-rpm filename match the
17212 - New config options to help controllers: FetchServerDescriptors
17213 and FetchHidServDescriptors for whether to fetch server
17214 info and hidserv info or let the controller do it, and
17215 PublishServerDescriptor and PublishHidServDescriptors.
17216 - Also let the controller set the __AllDirActionsPrivate config
17217 option if you want all directory fetches/publishes to happen via
17218 Tor (it assumes your controller bootstraps your circuits).
17221 Changes in version 0.1.0.17 - 2006-02-17
17222 o Crash bugfixes on 0.1.0.x:
17223 - When servers with a non-zero DirPort came out of hibernation,
17224 sometimes they would trigger an assert.
17226 o Other important bugfixes:
17227 - On platforms that don't have getrlimit (like Windows), we were
17228 artificially constraining ourselves to a max of 1024
17229 connections. Now just assume that we can handle as many as 15000
17230 connections. Hopefully this won't cause other problems.
17232 o Backported features:
17233 - When we're a server, a client asks for an old-style directory,
17234 and our write bucket is empty, don't give it to him. This way
17235 small servers can continue to serve the directory *sometimes*,
17236 without getting overloaded.
17237 - Whenever you get a 503 in response to a directory fetch, try
17238 once more. This will become important once servers start sending
17239 503's whenever they feel busy.
17240 - Fetch a new directory every 120 minutes, not every 40 minutes.
17241 Now that we have hundreds of thousands of users running the old
17242 directory algorithm, it's starting to hurt a lot.
17243 - Bump up the period for forcing a hidden service descriptor upload
17244 from 20 minutes to 1 hour.
17247 Changes in version 0.1.1.13-alpha - 2006-02-09
17248 o Crashes in 0.1.1.x:
17249 - When you tried to setconf ORPort via the controller, Tor would
17250 crash. So people using TorCP to become a server were sad.
17251 - Solve (I hope) the stack-smashing bug that we were seeing on fast
17252 servers. The problem appears to be something do with OpenSSL's
17253 random number generation, or how we call it, or something. Let me
17254 know if the crashes continue.
17255 - Turn crypto hardware acceleration off by default, until we find
17256 somebody smart who can test it for us. (It appears to produce
17257 seg faults in at least some cases.)
17258 - Fix a rare assert error when we've tried all intro points for
17259 a hidden service and we try fetching the service descriptor again:
17260 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
17263 - Fix a major load balance bug: we were round-robining in 16 KB
17264 chunks, and servers with bandwidthrate of 20 KB, while downloading
17265 a 600 KB directory, would starve their other connections. Now we
17266 try to be a bit more fair.
17267 - Dir authorities and mirrors were never expiring the newest
17268 descriptor for each server, causing memory and directory bloat.
17269 - Fix memory-bloating and connection-bloating bug on servers: We
17270 were never closing any connection that had ever had a circuit on
17271 it, because we were checking conn->n_circuits == 0, yet we had a
17272 bug that let it go negative.
17273 - Make Tor work using squid as your http proxy again -- squid
17274 returns an error if you ask for a URL that's too long, and it uses
17275 a really generic error message. Plus, many people are behind a
17276 transparent squid so they don't even realize it.
17277 - On platforms that don't have getrlimit (like Windows), we were
17278 artificially constraining ourselves to a max of 1024
17279 connections. Now just assume that we can handle as many as 15000
17280 connections. Hopefully this won't cause other problems.
17281 - Add a new config option ExitPolicyRejectPrivate which defaults to
17282 1. This means all exit policies will begin with rejecting private
17283 addresses, unless the server operator explicitly turns it off.
17286 - Clients no longer download descriptors for non-running
17288 - Before we add new directory authorities, we should make it
17289 clear that only v1 authorities should receive/publish hidden
17290 service descriptors.
17293 - As soon as we've fetched some more directory info, immediately
17294 try to download more server descriptors. This way we don't have
17295 a 10 second pause during initial bootstrapping.
17296 - Remove even more loud log messages that the server operator can't
17298 - When we're running an obsolete or un-recommended version, make
17299 the log message more clear about what the problem is and what
17300 versions *are* still recommended.
17301 - Provide a more useful warn message when our onion queue gets full:
17302 the CPU is too slow or the exit policy is too liberal.
17303 - Don't warn when we receive a 503 from a dirserver/cache -- this
17304 will pave the way for them being able to refuse if they're busy.
17305 - When we fail to bind a listener, try to provide a more useful
17306 log message: e.g., "Is Tor already running?"
17307 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
17308 Goldberg can prove things about our handshake protocol more
17310 - MaxConn has been obsolete for a while now. Document the ConnLimit
17311 config option, which is a *minimum* number of file descriptors
17312 that must be available else Tor refuses to start.
17313 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17314 if you log to syslog and want something other than LOG_DAEMON.
17315 - Make dirservers generate a separate "guard" flag to mean,
17316 "would make a good entry guard". Make clients parse it and vote
17317 on it. Not used by clients yet.
17318 - Implement --with-libevent-dir option to ./configure. Also, improve
17319 search techniques to find libevent, and use those for openssl too.
17320 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
17321 - Only start testing reachability once we've established a
17322 circuit. This will make startup on dirservers less noisy.
17323 - Don't try to upload hidden service descriptors until we have
17324 established a circuit.
17325 - Fix the controller's "attachstream 0" command to treat conn like
17326 it just connected, doing address remapping, handling .exit and
17327 .onion idioms, and so on. Now we're more uniform in making sure
17328 that the controller hears about new and closing connections.
17331 Changes in version 0.1.1.12-alpha - 2006-01-11
17332 o Bugfixes on 0.1.1.x:
17333 - The fix to close duplicate server connections was closing all
17334 Tor client connections if they didn't establish a circuit
17335 quickly enough. Oops.
17336 - Fix minor memory issue (double-free) that happened on exit.
17338 o Bugfixes on 0.1.0.x:
17339 - Tor didn't warn when it failed to open a log file.
17342 Changes in version 0.1.1.11-alpha - 2006-01-10
17343 o Crashes in 0.1.1.x:
17344 - Include all the assert/crash fixes from 0.1.0.16.
17345 - If you start Tor and then quit very quickly, there were some
17346 races that tried to free things that weren't allocated yet.
17347 - Fix a rare memory stomp if you're running hidden services.
17348 - Fix segfault when specifying DirServer in config without nickname.
17349 - Fix a seg fault when you finish connecting to a server but at
17350 that moment you dump his server descriptor.
17351 - Extendcircuit and Attachstream controller commands would
17352 assert/crash if you don't give them enough arguments.
17353 - Fix an assert error when we're out of space in the connection_list
17354 and we try to post a hidden service descriptor (reported by weasel).
17355 - If you specify a relative torrc path and you set RunAsDaemon in
17356 your torrc, then it chdir()'s to the new directory. If you HUP,
17357 it tries to load the new torrc location, fails, and exits.
17358 The fix: no longer allow a relative path to torrc using -f.
17361 - Implement "entry guards": automatically choose a handful of entry
17362 nodes and stick with them for all circuits. Only pick new guards
17363 when the ones you have are unsuitable, and if the old guards
17364 become suitable again, switch back. This will increase security
17365 dramatically against certain end-point attacks. The EntryNodes
17366 config option now provides some hints about which entry guards you
17367 want to use most; and StrictEntryNodes means to only use those.
17368 - New directory logic: download by descriptor digest, not by
17369 fingerprint. Caches try to download all listed digests from
17370 authorities; clients try to download "best" digests from caches.
17371 This avoids partitioning and isolating attacks better.
17372 - Make the "stable" router flag in network-status be the median of
17373 the uptimes of running valid servers, and make clients pay
17374 attention to the network-status flags. Thus the cutoff adapts
17375 to the stability of the network as a whole, making IRC, IM, etc
17376 connections more reliable.
17379 - Tor servers with dynamic IP addresses were needing to wait 18
17380 hours before they could start doing reachability testing using
17381 the new IP address and ports. This is because they were using
17382 the internal descriptor to learn what to test, yet they were only
17383 rebuilding the descriptor once they decided they were reachable.
17384 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
17385 to download certain server descriptors, throw them away, and then
17386 fetch them again after 30 minutes. Now mirrors throw away these
17387 server descriptors so clients can't get them.
17388 - We were leaving duplicate connections to other ORs open for a week,
17389 rather than closing them once we detect a duplicate. This only
17390 really affected authdirservers, but it affected them a lot.
17391 - Spread the authdirservers' reachability testing over the entire
17392 testing interval, so we don't try to do 500 TLS's at once every
17396 - If the network is down, and we try to connect to a conn because
17397 we have a circuit in mind, and we timeout (30 seconds) because the
17398 network never answers, we were expiring the circuit, but we weren't
17399 obsoleting the connection or telling the entry_guards functions.
17400 - Some Tor servers process billions of cells per day. These statistics
17401 need to be uint64_t's.
17402 - Check for integer overflows in more places, when adding elements
17403 to smartlists. This could possibly prevent a buffer overflow
17404 on malicious huge inputs. I don't see any, but I haven't looked
17406 - ReachableAddresses kept growing new "reject *:*" lines on every
17408 - When you "setconf log" via the controller, it should remove all
17409 logs. We were automatically adding back in a "log notice stdout".
17410 - Newly bootstrapped Tor networks couldn't establish hidden service
17411 circuits until they had nodes with high uptime. Be more tolerant.
17412 - We were marking servers down when they could not answer every piece
17413 of the directory request we sent them. This was far too harsh.
17414 - Fix the torify (tsocks) config file to not use Tor for localhost
17416 - Directory authorities now go to the proper authority when asking for
17417 a networkstatus, even when they want a compressed one.
17418 - Fix a harmless bug that was causing Tor servers to log
17419 "Got an end because of misc error, but we're not an AP. Closing."
17420 - Authorities were treating their own descriptor changes as cosmetic,
17421 meaning the descriptor available in the network-status and the
17422 descriptor that clients downloaded were different.
17423 - The OS X installer was adding a symlink for tor_resolve but
17424 the binary was called tor-resolve (reported by Thomas Hardly).
17425 - Workaround a problem with some http proxies where they refuse GET
17426 requests that specify "Content-Length: 0" (reported by Adrian).
17427 - Fix wrong log message when you add a "HiddenServiceNodes" config
17428 line without any HiddenServiceDir line (reported by Chris Thomas).
17431 - Write the TorVersion into the state file so we have a prayer of
17432 keeping forward and backward compatibility.
17433 - Revive the FascistFirewall config option rather than eliminating it:
17434 now it's a synonym for ReachableAddresses *:80,*:443.
17435 - Clients choose directory servers from the network status lists,
17436 not from their internal list of router descriptors. Now they can
17437 go to caches directly rather than needing to go to authorities
17439 - Directory authorities ignore router descriptors that have only
17440 cosmetic differences: do this for 0.1.0.x servers now too.
17441 - Add a new flag to network-status indicating whether the server
17442 can answer v2 directory requests too.
17443 - Authdirs now stop whining so loudly about bad descriptors that
17444 they fetch from other dirservers. So when there's a log complaint,
17445 it's for sure from a freshly uploaded descriptor.
17446 - Reduce memory requirements in our structs by changing the order
17448 - There used to be two ways to specify your listening ports in a
17449 server descriptor: on the "router" line and with a separate "ports"
17450 line. Remove support for the "ports" line.
17451 - New config option "AuthDirRejectUnlisted" for auth dirservers as
17452 a panic button: if we get flooded with unusable servers we can
17453 revert to only listing servers in the approved-routers file.
17454 - Auth dir servers can now mark a fingerprint as "!reject" or
17455 "!invalid" in the approved-routers file (as its nickname), to
17456 refuse descriptors outright or include them but marked as invalid.
17457 - Servers store bandwidth history across restarts/crashes.
17458 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17459 get a better idea of why their circuits failed. Not used yet.
17460 - Directory mirrors now cache up to 16 unrecognized network-status
17461 docs. Now we can add new authdirservers and they'll be cached too.
17462 - When picking a random directory, prefer non-authorities if any
17464 - New controller option "getinfo desc/all-recent" to fetch the
17465 latest server descriptor for every router that Tor knows about.
17468 Changes in version 0.1.0.16 - 2006-01-02
17469 o Crash bugfixes on 0.1.0.x:
17470 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17471 corrupting the heap, losing FDs, or crashing when we need to resize
17472 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17473 - It turns out sparc64 platforms crash on unaligned memory access
17474 too -- so detect and avoid this.
17475 - Handle truncated compressed data correctly (by detecting it and
17477 - Fix possible-but-unlikely free(NULL) in control.c.
17478 - When we were closing connections, there was a rare case that
17479 stomped on memory, triggering seg faults and asserts.
17480 - Avoid potential infinite recursion when building a descriptor. (We
17481 don't know that it ever happened, but better to fix it anyway.)
17482 - We were neglecting to unlink marked circuits from soon-to-close OR
17483 connections, which caused some rare scribbling on freed memory.
17484 - Fix a memory stomping race bug when closing the joining point of two
17485 rendezvous circuits.
17486 - Fix an assert in time parsing found by Steven Murdoch.
17488 o Other bugfixes on 0.1.0.x:
17489 - When we're doing reachability testing, provide more useful log
17490 messages so the operator knows what to expect.
17491 - Do not check whether DirPort is reachable when we are suppressing
17492 advertising it because of hibernation.
17493 - When building with -static or on Solaris, we sometimes needed -ldl.
17494 - When we're deciding whether a stream has enough circuits around
17495 that can handle it, count the freshly dirty ones and not the ones
17496 that are so dirty they won't be able to handle it.
17497 - When we're expiring old circuits, we had a logic error that caused
17498 us to close new rendezvous circuits rather than old ones.
17499 - Give a more helpful log message when you try to change ORPort via
17500 the controller: you should upgrade Tor if you want that to work.
17501 - We were failing to parse Tor versions that start with "Tor ".
17502 - Tolerate faulty streams better: when a stream fails for reason
17503 exitpolicy, stop assuming that the router is lying about his exit
17504 policy. When a stream fails for reason misc, allow it to retry just
17505 as if it was resolvefailed. When a stream has failed three times,
17506 reset its failure count so we can try again and get all three tries.
17509 Changes in version 0.1.1.10-alpha - 2005-12-11
17510 o Correctness bugfixes on 0.1.0.x:
17511 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17512 corrupting the heap, losing FDs, or crashing when we need to resize
17513 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17514 - Stop doing the complex voodoo overkill checking for insecure
17515 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17516 - When we were closing connections, there was a rare case that
17517 stomped on memory, triggering seg faults and asserts.
17518 - We were neglecting to unlink marked circuits from soon-to-close OR
17519 connections, which caused some rare scribbling on freed memory.
17520 - When we're deciding whether a stream has enough circuits around
17521 that can handle it, count the freshly dirty ones and not the ones
17522 that are so dirty they won't be able to handle it.
17523 - Recover better from TCP connections to Tor servers that are
17524 broken but don't tell you (it happens!); and rotate TLS
17525 connections once a week.
17526 - When we're expiring old circuits, we had a logic error that caused
17527 us to close new rendezvous circuits rather than old ones.
17528 - Fix a scary-looking but apparently harmless bug where circuits
17529 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17530 servers, and never switch to state CIRCUIT_STATE_OPEN.
17531 - When building with -static or on Solaris, we sometimes needed to
17533 - Give a useful message when people run Tor as the wrong user,
17534 rather than telling them to start chowning random directories.
17535 - We were failing to inform the controller about new .onion streams.
17537 o Security bugfixes on 0.1.0.x:
17538 - Refuse server descriptors if the fingerprint line doesn't match
17539 the included identity key. Tor doesn't care, but other apps (and
17540 humans) might actually be trusting the fingerprint line.
17541 - We used to kill the circuit when we receive a relay command we
17542 don't recognize. Now we just drop it.
17543 - Start obeying our firewall options more rigorously:
17544 . If we can't get to a dirserver directly, try going via Tor.
17545 . Don't ever try to connect (as a client) to a place our
17546 firewall options forbid.
17547 . If we specify a proxy and also firewall options, obey the
17548 firewall options even when we're using the proxy: some proxies
17549 can only proxy to certain destinations.
17550 - Fix a bug found by Lasse Overlier: when we were making internal
17551 circuits (intended to be cannibalized later for rendezvous and
17552 introduction circuits), we were picking them so that they had
17553 useful exit nodes. There was no need for this, and it actually
17554 aids some statistical attacks.
17555 - Start treating internal circuits and exit circuits separately.
17556 It's important to keep them separate because internal circuits
17557 have their last hops picked like middle hops, rather than like
17558 exit hops. So exiting on them will break the user's expectations.
17560 o Bugfixes on 0.1.1.x:
17561 - Take out the mis-feature where we tried to detect IP address
17562 flapping for people with DynDNS, and chose not to upload a new
17563 server descriptor sometimes.
17564 - Try to be compatible with OpenSSL 0.9.6 again.
17565 - Log fix: when the controller is logging about .onion addresses,
17566 sometimes it didn't include the ".onion" part of the address.
17567 - Don't try to modify options->DirServers internally -- if the
17568 user didn't specify any, just add the default ones directly to
17569 the trusted dirserver list. This fixes a bug where people running
17570 controllers would use SETCONF on some totally unrelated config
17571 option, and Tor would start yelling at them about changing their
17573 - Let the controller's redirectstream command specify a port, in
17574 case the controller wants to change that too.
17575 - When we requested a pile of server descriptors, we sometimes
17576 accidentally launched a duplicate request for the first one.
17577 - Bugfix for trackhostexits: write down the fingerprint of the
17578 chosen exit, not its nickname, because the chosen exit might not
17580 - When parsing foo.exit, if foo is unknown, and we are leaving
17581 circuits unattached, set the chosen_exit field and leave the
17582 address empty. This matters because controllers got confused
17584 - Directory authorities no longer try to download server
17585 descriptors that they know they will reject.
17587 o Features and updates:
17588 - Replace balanced trees with hash tables: this should make stuff
17589 significantly faster.
17590 - Resume using the AES counter-mode implementation that we ship,
17591 rather than OpenSSL's. Ours is significantly faster.
17592 - Many other CPU and memory improvements.
17593 - Add a new config option FastFirstHopPK (on by default) so clients
17594 do a trivial crypto handshake for their first hop, since TLS has
17595 already taken care of confidentiality and authentication.
17596 - Add a new config option TestSocks so people can see if their
17597 applications are using socks4, socks4a, socks5-with-ip, or
17598 socks5-with-hostname. This way they don't have to keep mucking
17599 with tcpdump and wondering if something got cached somewhere.
17600 - Warn when listening on a public address for socks. I suspect a
17601 lot of people are setting themselves up as open socks proxies,
17602 and they have no idea that jerks on the Internet are using them,
17603 since they simply proxy the traffic into the Tor network.
17604 - Add "private:*" as an alias in configuration for policies. Now
17605 you can simplify your exit policy rather than needing to list
17606 every single internal or nonroutable network space.
17607 - Add a new controller event type that allows controllers to get
17608 all server descriptors that were uploaded to a router in its role
17609 as authoritative dirserver.
17610 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17611 tor-doc-server.html, and stylesheet.css in the tarball.
17612 - Stop shipping tor-doc.html in the tarball.
17615 Changes in version 0.1.1.9-alpha - 2005-11-15
17616 o Usability improvements:
17617 - Start calling it FooListenAddress rather than FooBindAddress,
17618 since few of our users know what it means to bind an address
17620 - Reduce clutter in server logs. We're going to try to make
17621 them actually usable now. New config option ProtocolWarnings that
17622 lets you hear about how _other Tors_ are breaking the protocol. Off
17624 - Divide log messages into logging domains. Once we put some sort
17625 of interface on this, it will let people looking at more verbose
17626 log levels specify the topics they want to hear more about.
17627 - Make directory servers return better http 404 error messages
17628 instead of a generic "Servers unavailable".
17629 - Check for even more Windows version flags when writing the platform
17630 string in server descriptors, and note any we don't recognize.
17631 - Clean up more of the OpenSSL memory when exiting, so we can detect
17632 memory leaks better.
17633 - Make directory authorities be non-versioning, non-naming by
17634 default. Now we can add new directory servers without requiring
17635 their operators to pay close attention.
17636 - When logging via syslog, include the pid whenever we provide
17637 a log entry. Suggested by Todd Fries.
17639 o Performance improvements:
17640 - Directory servers now silently throw away new descriptors that
17641 haven't changed much if the timestamps are similar. We do this to
17642 tolerate older Tor servers that upload a new descriptor every 15
17643 minutes. (It seemed like a good idea at the time.)
17644 - Inline bottleneck smartlist functions; use fast versions by default.
17645 - Add a "Map from digest to void*" abstraction digestmap_t so we
17646 can do less hex encoding/decoding. Use it in router_get_by_digest()
17647 to resolve a performance bottleneck.
17648 - Allow tor_gzip_uncompress to extract as much as possible from
17649 truncated compressed data. Try to extract as many
17650 descriptors as possible from truncated http responses (when
17651 DIR_PURPOSE_FETCH_ROUTERDESC).
17652 - Make circ->onionskin a pointer, not a static array. moria2 was using
17653 125000 circuit_t's after it had been up for a few weeks, which
17654 translates to 20+ megs of wasted space.
17655 - The private half of our EDH handshake keys are now chosen out
17656 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17658 o Security improvements:
17659 - Start making directory caches retain old routerinfos, so soon
17660 clients can start asking by digest of descriptor rather than by
17661 fingerprint of server.
17662 - Add half our entropy from RAND_poll in OpenSSL. This knows how
17663 to use egd (if present), openbsd weirdness (if present), vms/os2
17664 weirdness (if we ever port there), and more in the future.
17666 o Bugfixes on 0.1.0.x:
17667 - Do round-robin writes of at most 16 kB per write. This might be
17668 more fair on loaded Tor servers, and it might resolve our Windows
17669 crash bug. It might also slow things down.
17670 - Our TLS handshakes were generating a single public/private
17671 keypair for the TLS context, rather than making a new one for
17672 each new connections. Oops. (But we were still rotating them
17673 periodically, so it's not so bad.)
17674 - When we were cannibalizing a circuit with a particular exit
17675 node in mind, we weren't checking to see if that exit node was
17676 already present earlier in the circuit. Oops.
17677 - When a Tor server's IP changes (e.g. from a dyndns address),
17678 upload a new descriptor so clients will learn too.
17679 - Really busy servers were keeping enough circuits open on stable
17680 connections that they were wrapping around the circuit_id
17681 space. (It's only two bytes.) This exposed a bug where we would
17682 feel free to reuse a circuit_id even if it still exists but has
17683 been marked for close. Try to fix this bug. Some bug remains.
17684 - If we would close a stream early (e.g. it asks for a .exit that
17685 we know would refuse it) but the LeaveStreamsUnattached config
17686 option is set by the controller, then don't close it.
17688 o Bugfixes on 0.1.1.8-alpha:
17689 - Fix a big pile of memory leaks, some of them serious.
17690 - Do not try to download a routerdesc if we would immediately reject
17692 - Resume inserting a newline between all router descriptors when
17693 generating (old style) signed directories, since our spec says
17695 - When providing content-type application/octet-stream for
17696 server descriptors using .z, we were leaving out the
17697 content-encoding header. Oops. (Everything tolerated this just
17698 fine, but that doesn't mean we need to be part of the problem.)
17699 - Fix a potential seg fault in getconf and getinfo using version 1
17700 of the controller protocol.
17701 - Avoid crash: do not check whether DirPort is reachable when we
17702 are suppressing it because of hibernation.
17703 - Make --hash-password not crash on exit.
17706 Changes in version 0.1.1.8-alpha - 2005-10-07
17707 o New features (major):
17708 - Clients don't download or use the directory anymore. Now they
17709 download and use network-statuses from the trusted dirservers,
17710 and fetch individual server descriptors as needed from mirrors.
17711 See dir-spec.txt for all the gory details.
17712 - Be more conservative about whether to advertise our DirPort.
17713 The main change is to not advertise if we're running at capacity
17714 and either a) we could hibernate or b) our capacity is low and
17715 we're using a default DirPort.
17716 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
17718 o New features (minor):
17719 - Try to be smart about when to retry network-status and
17720 server-descriptor fetches. Still needs some tuning.
17721 - Stop parsing, storing, or using running-routers output (but
17722 mirrors still cache and serve it).
17723 - Consider a threshold of versioning dirservers (dirservers who have
17724 an opinion about which Tor versions are still recommended) before
17725 deciding whether to warn the user that he's obsolete.
17726 - Dirservers can now reject/invalidate by key and IP, with the
17727 config options "AuthDirInvalid" and "AuthDirReject". This is
17728 useful since currently we automatically list servers as running
17729 and usable even if we know they're jerks.
17730 - Provide dire warnings to any users who set DirServer; move it out
17731 of torrc.sample and into torrc.complete.
17732 - Add MyFamily to torrc.sample in the server section.
17733 - Add nicknames to the DirServer line, so we can refer to them
17734 without requiring all our users to memorize their IP addresses.
17735 - When we get an EOF or a timeout on a directory connection, note
17736 how many bytes of serverdesc we are dropping. This will help
17737 us determine whether it is smart to parse incomplete serverdesc
17739 - Add a new function to "change pseudonyms" -- that is, to stop
17740 using any currently-dirty circuits for new streams, so we don't
17741 link new actions to old actions. Currently it's only called on
17742 HUP (or SIGNAL RELOAD).
17743 - On sighup, if UseHelperNodes changed to 1, use new circuits.
17744 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17745 OpenSSL. Also, reseed our entropy every hour, not just at
17746 startup. And entropy in 512-bit chunks, not 160-bit chunks.
17748 o Fixes on 0.1.1.7-alpha:
17749 - Nobody ever implemented EVENT_ADDRMAP for control protocol
17750 version 0, so don't let version 0 controllers ask for it.
17751 - If you requested something with too many newlines via the
17752 v1 controller protocol, you could crash tor.
17753 - Fix a number of memory leaks, including some pretty serious ones.
17754 - Re-enable DirPort testing again, so Tor servers will be willing
17755 to advertise their DirPort if it's reachable.
17756 - On TLS handshake, only check the other router's nickname against
17757 its expected nickname if is_named is set.
17759 o Fixes forward-ported from 0.1.0.15:
17760 - Don't crash when we don't have any spare file descriptors and we
17761 try to spawn a dns or cpu worker.
17762 - Make the numbers in read-history and write-history into uint64s,
17763 so they don't overflow and publish negatives in the descriptor.
17765 o Fixes on 0.1.0.x:
17766 - For the OS X package's modified privoxy config file, comment
17767 out the "logfile" line so we don't log everything passed
17769 - We were whining about using socks4 or socks5-with-local-lookup
17770 even when it's an IP in the "virtual" range we designed exactly
17772 - We were leaking some memory every time the client changes IPs.
17773 - Never call free() on tor_malloc()d memory. This will help us
17774 use dmalloc to detect memory leaks.
17775 - Check for named servers when looking them up by nickname;
17776 warn when we'recalling a non-named server by its nickname;
17777 don't warn twice about the same name.
17778 - Try to list MyFamily elements by key, not by nickname, and warn
17779 if we've not heard of the server.
17780 - Make windows platform detection (uname equivalent) smarter.
17781 - It turns out sparc64 doesn't like unaligned access either.
17784 Changes in version 0.1.0.15 - 2005-09-23
17785 o Bugfixes on 0.1.0.x:
17786 - Reject ports 465 and 587 (spam targets) in default exit policy.
17787 - Don't crash when we don't have any spare file descriptors and we
17788 try to spawn a dns or cpu worker.
17789 - Get rid of IgnoreVersion undocumented config option, and make us
17790 only warn, never exit, when we're running an obsolete version.
17791 - Don't try to print a null string when your server finds itself to
17792 be unreachable and the Address config option is empty.
17793 - Make the numbers in read-history and write-history into uint64s,
17794 so they don't overflow and publish negatives in the descriptor.
17795 - Fix a minor memory leak in smartlist_string_remove().
17796 - We were only allowing ourselves to upload a server descriptor at
17797 most every 20 minutes, even if it changed earlier than that.
17798 - Clean up log entries that pointed to old URLs.
17801 Changes in version 0.1.1.7-alpha - 2005-09-14
17802 o Fixes on 0.1.1.6-alpha:
17803 - Exit servers were crashing when people asked them to make a
17804 connection to an address not in their exit policy.
17805 - Looking up a non-existent stream for a v1 control connection would
17807 - Fix a seg fault if we ask a dirserver for a descriptor by
17808 fingerprint but he doesn't know about him.
17809 - SETCONF was appending items to linelists, not clearing them.
17810 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
17811 out and refuse the setconf if it would fail.
17812 - Downgrade the dirserver log messages when whining about
17816 - Add Peter Palfrader's check-tor script to tor/contrib/
17817 It lets you easily check whether a given server (referenced by
17818 nickname) is reachable by you.
17819 - Numerous changes to move towards client-side v2 directories. Not
17822 o Fixes on 0.1.0.x:
17823 - If the user gave tor an odd number of command-line arguments,
17824 we were silently ignoring the last one. Now we complain and fail.
17825 [This wins the oldest-bug prize -- this bug has been present since
17826 November 2002, as released in Tor 0.0.0.]
17827 - Do not use unaligned memory access on alpha, mips, or mipsel.
17828 It *works*, but is very slow, so we treat them as if it doesn't.
17829 - Retry directory requests if we fail to get an answer we like
17830 from a given dirserver (we were retrying before, but only if
17831 we fail to connect).
17832 - When writing the RecommendedVersions line, sort them first.
17833 - When the client asked for a rendezvous port that the hidden
17834 service didn't want to provide, we were sending an IP address
17835 back along with the end cell. Fortunately, it was zero. But stop
17837 - Correct "your server is reachable" log entries to indicate that
17838 it was self-testing that told us so.
17841 Changes in version 0.1.1.6-alpha - 2005-09-09
17842 o Fixes on 0.1.1.5-alpha:
17843 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
17844 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
17845 - Fix bug with tor_memmem finding a match at the end of the string.
17846 - Make unit tests run without segfaulting.
17847 - Resolve some solaris x86 compile warnings.
17848 - Handle duplicate lines in approved-routers files without warning.
17849 - Fix bug where as soon as a server refused any requests due to his
17850 exit policy (e.g. when we ask for localhost and he tells us that's
17851 127.0.0.1 and he won't do it), we decided he wasn't obeying his
17852 exit policy using him for any exits.
17853 - Only do openssl hardware accelerator stuff if openssl version is
17856 o New controller features/fixes:
17857 - Add a "RESETCONF" command so you can set config options like
17858 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17859 a config option in the torrc with no value, then it clears it
17860 entirely (rather than setting it to its default).
17861 - Add a "GETINFO config-file" to tell us where torrc is.
17862 - Avoid sending blank lines when GETINFO replies should be empty.
17863 - Add a QUIT command for the controller (for using it manually).
17864 - Fix a bug in SAVECONF that was adding default dirservers and
17865 other redundant entries to the torrc file.
17867 o Start on the new directory design:
17868 - Generate, publish, cache, serve new network-status format.
17869 - Publish individual descriptors (by fingerprint, by "all", and by
17871 - Publish client and server recommended versions separately.
17872 - Allow tor_gzip_uncompress() to handle multiple concatenated
17873 compressed strings. Serve compressed groups of router
17874 descriptors. The compression logic here could be more
17876 - Distinguish v1 authorities (all currently trusted directories)
17877 from v2 authorities (all trusted directories).
17878 - Change DirServers config line to note which dirs are v1 authorities.
17879 - Add configuration option "V1AuthoritativeDirectory 1" which
17880 moria1, moria2, and tor26 should set.
17881 - Remove option when getting directory cache to see whether they
17882 support running-routers; they all do now. Replace it with one
17883 to see whether caches support v2 stuff.
17886 - Dirservers now do their own external reachability testing of each
17887 Tor server, and only list them as running if they've been found to
17888 be reachable. We also send back warnings to the server's logs if
17889 it uploads a descriptor that we already believe is unreachable.
17890 - Implement exit enclaves: if we know an IP address for the
17891 destination, and there's a running Tor server at that address
17892 which allows exit to the destination, then extend the circuit to
17893 that exit first. This provides end-to-end encryption and end-to-end
17894 authentication. Also, if the user wants a .exit address or enclave,
17895 use 4 hops rather than 3, and cannibalize a general circ for it
17897 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
17898 controller. Also, rotate dns and cpu workers if the controller
17899 changes options that will affect them; and initialize the dns
17900 worker cache tree whether or not we start out as a server.
17901 - Only upload a new server descriptor when options change, 18
17902 hours have passed, uptime is reset, or bandwidth changes a lot.
17903 - Check [X-]Forwarded-For headers in HTTP requests when generating
17904 log messages. This lets people run dirservers (and caches) behind
17905 Apache but still know which IP addresses are causing warnings.
17907 o Config option changes:
17908 - Replace (Fascist)Firewall* config options with a new
17909 ReachableAddresses option that understands address policies.
17910 For example, "ReachableAddresses *:80,*:443"
17911 - Get rid of IgnoreVersion undocumented config option, and make us
17912 only warn, never exit, when we're running an obsolete version.
17913 - Make MonthlyAccountingStart config option truly obsolete now.
17915 o Fixes on 0.1.0.x:
17916 - Reject ports 465 and 587 in the default exit policy, since
17917 people have started using them for spam too.
17918 - It turns out we couldn't bootstrap a network since we added
17919 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17920 has never gone down. Add an AssumeReachable config option to let
17921 servers and dirservers bootstrap. When we're trying to build a
17922 high-uptime or high-bandwidth circuit but there aren't enough
17923 suitable servers, try being less picky rather than simply failing.
17924 - Our logic to decide if the OR we connected to was the right guy
17925 was brittle and maybe open to a mitm for unverified routers.
17926 - We weren't cannibalizing circuits correctly for
17927 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17928 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17929 build those from scratch. This should make hidden services faster.
17930 - Predict required circuits better, with an eye toward making hidden
17931 services faster on the service end.
17932 - Retry streams if the exit node sends back a 'misc' failure. This
17933 should result in fewer random failures. Also, after failing
17934 from resolve failed or misc, reset the num failures, so we give
17935 it a fair shake next time we try.
17936 - Clean up the rendezvous warn log msgs, and downgrade some to info.
17937 - Reduce severity on logs about dns worker spawning and culling.
17938 - When we're shutting down and we do something like try to post a
17939 server descriptor or rendezvous descriptor, don't complain that
17940 we seem to be unreachable. Of course we are, we're shutting down.
17941 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17942 We don't use them yet, but maybe one day our DNS resolver will be
17943 able to discover them.
17944 - Make ContactInfo mandatory for authoritative directory servers.
17945 - Require server descriptors to list IPv4 addresses -- hostnames
17946 are no longer allowed. This also fixes some potential security
17947 problems with people providing hostnames as their address and then
17948 preferentially resolving them to partition users.
17949 - Change log line for unreachability to explicitly suggest /etc/hosts
17950 as the culprit. Also make it clearer what IP address and ports we're
17951 testing for reachability.
17952 - Put quotes around user-supplied strings when logging so users are
17953 more likely to realize if they add bad characters (like quotes)
17955 - Let auth dir servers start without specifying an Address config
17957 - Make unit tests (and other invocations that aren't the real Tor)
17958 run without launching listeners, creating subdirectories, and so on.
17961 Changes in version 0.1.1.5-alpha - 2005-08-08
17962 o Bugfixes included in 0.1.0.14.
17964 o Bugfixes on 0.1.0.x:
17965 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17966 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17967 it would silently using ignore the 6668.
17970 Changes in version 0.1.0.14 - 2005-08-08
17971 o Bugfixes on 0.1.0.x:
17972 - Fix the other half of the bug with crypto handshakes
17974 - Fix an assert trigger if you send a 'signal term' via the
17975 controller when it's listening for 'event info' messages.
17978 Changes in version 0.1.1.4-alpha - 2005-08-04
17979 o Bugfixes included in 0.1.0.13.
17982 - Improve tor_gettimeofday() granularity on windows.
17983 - Make clients regenerate their keys when their IP address changes.
17984 - Implement some more GETINFO goodness: expose helper nodes, config
17985 options, getinfo keys.
17988 Changes in version 0.1.0.13 - 2005-08-04
17989 o Bugfixes on 0.1.0.x:
17990 - Fix a critical bug in the security of our crypto handshakes.
17991 - Fix a size_t underflow in smartlist_join_strings2() that made
17992 it do bad things when you hand it an empty smartlist.
17993 - Fix Windows installer to ship Tor license (thanks to Aphex for
17994 pointing out this oversight) and put a link to the doc directory
17996 - Explicitly set no-unaligned-access for sparc: it turns out the
17997 new gcc's let you compile broken code, but that doesn't make it
18001 Changes in version 0.1.1.3-alpha - 2005-07-23
18002 o Bugfixes on 0.1.1.2-alpha:
18003 - Fix a bug in handling the controller's "post descriptor"
18005 - Fix several bugs in handling the controller's "extend circuit"
18007 - Fix a bug in handling the controller's "stream status" event.
18008 - Fix an assert failure if we have a controller listening for
18009 circuit events and we go offline.
18010 - Re-allow hidden service descriptors to publish 0 intro points.
18011 - Fix a crash when generating your hidden service descriptor if
18012 you don't have enough intro points already.
18014 o New features on 0.1.1.2-alpha:
18015 - New controller function "getinfo accounting", to ask how
18016 many bytes we've used in this time period.
18017 - Experimental support for helper nodes: a lot of the risk from
18018 a small static adversary comes because users pick new random
18019 nodes every time they rebuild a circuit. Now users will try to
18020 stick to the same small set of entry nodes if they can. Not
18021 enabled by default yet.
18023 o Bugfixes on 0.1.0.12:
18024 - If you're an auth dir server, always publish your dirport,
18025 even if you haven't yet found yourself to be reachable.
18026 - Fix a size_t underflow in smartlist_join_strings2() that made
18027 it do bad things when you hand it an empty smartlist.
18030 Changes in version 0.1.0.12 - 2005-07-18
18031 o New directory servers:
18032 - tor26 has changed IP address.
18034 o Bugfixes on 0.1.0.x:
18035 - Fix a possible double-free in tor_gzip_uncompress().
18036 - When --disable-threads is set, do not search for or link against
18037 pthreads libraries.
18038 - Don't trigger an assert if an authoritative directory server
18039 claims its dirport is 0.
18040 - Fix bug with removing Tor as an NT service: some people were
18041 getting "The service did not return an error." Thanks to Matt
18045 Changes in version 0.1.1.2-alpha - 2005-07-15
18046 o New directory servers:
18047 - tor26 has changed IP address.
18049 o Bugfixes on 0.1.0.x, crashes/leaks:
18050 - Port the servers-not-obeying-their-exit-policies fix from
18052 - Fix an fd leak in start_daemon().
18053 - On Windows, you can't always reopen a port right after you've
18054 closed it. So change retry_listeners() to only close and re-open
18055 ports that have changed.
18056 - Fix a possible double-free in tor_gzip_uncompress().
18058 o Bugfixes on 0.1.0.x, usability:
18059 - When tor_socketpair() fails in Windows, give a reasonable
18060 Windows-style errno back.
18061 - Let people type "tor --install" as well as "tor -install" when
18063 want to make it an NT service.
18064 - NT service patch from Matt Edman to improve error messages.
18065 - When the controller asks for a config option with an abbreviated
18066 name, give the full name in our response.
18067 - Correct the man page entry on TrackHostExitsExpire.
18068 - Looks like we were never delivering deflated (i.e. compressed)
18069 running-routers lists, even when asked. Oops.
18070 - When --disable-threads is set, do not search for or link against
18071 pthreads libraries.
18073 o Bugfixes on 0.1.1.x:
18074 - Fix a seg fault with autodetecting which controller version is
18078 - New hidden service descriptor format: put a version in it, and
18079 let people specify introduction/rendezvous points that aren't
18080 in "the directory" (which is subjective anyway).
18081 - Allow the DEBUG controller event to work again. Mark certain log
18082 entries as "don't tell this to controllers", so we avoid cycles.
18085 Changes in version 0.1.0.11 - 2005-06-30
18086 o Bugfixes on 0.1.0.x:
18087 - Fix major security bug: servers were disregarding their
18088 exit policies if clients behaved unexpectedly.
18089 - Make OS X init script check for missing argument, so we don't
18090 confuse users who invoke it incorrectly.
18091 - Fix a seg fault in "tor --hash-password foo".
18092 - The MAPADDRESS control command was broken.
18095 Changes in version 0.1.1.1-alpha - 2005-06-29
18097 - Make OS X init script check for missing argument, so we don't
18098 confuse users who invoke it incorrectly.
18099 - Fix a seg fault in "tor --hash-password foo".
18100 - Fix a possible way to DoS dirservers.
18101 - When we complain that your exit policy implicitly allows local or
18102 private address spaces, name them explicitly so operators can
18104 - Make the log message less scary when all the dirservers are
18105 temporarily unreachable.
18106 - We were printing the number of idle dns workers incorrectly when
18110 - Revised controller protocol (version 1) that uses ascii rather
18111 than binary. Add supporting libraries in python and java so you
18112 can use the controller from your applications without caring how
18113 our protocol works.
18114 - Spiffy new support for crypto hardware accelerators. Can somebody
18118 Changes in version 0.0.9.10 - 2005-06-16
18119 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18120 - Refuse relay cells that claim to have a length larger than the
18121 maximum allowed. This prevents a potential attack that could read
18122 arbitrary memory (e.g. keys) from an exit server's process
18126 Changes in version 0.1.0.10 - 2005-06-14
18127 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
18128 libevent before 1.1a.
18131 Changes in version 0.1.0.9-rc - 2005-06-09
18133 - Reset buf->highwater every time buf_shrink() is called, not just on
18134 a successful shrink. This was causing significant memory bloat.
18135 - Fix buffer overflow when checking hashed passwords.
18136 - Security fix: if seeding the RNG on Win32 fails, quit.
18137 - Allow seeding the RNG on Win32 even when you're not running as
18139 - Disable threading on Solaris too. Something is wonky with it,
18140 cpuworkers, and reentrant libs.
18141 - Reenable the part of the code that tries to flush as soon as an
18142 OR outbuf has a full TLS record available. Perhaps this will make
18143 OR outbufs not grow as huge except in rare cases, thus saving lots
18144 of CPU time plus memory.
18145 - Reject malformed .onion addresses rather then passing them on as
18146 normal web requests.
18147 - Adapt patch from Adam Langley: fix possible memory leak in
18148 tor_lookup_hostname().
18149 - Initialize libevent later in the startup process, so the logs are
18150 already established by the time we start logging libevent warns.
18151 - Use correct errno on win32 if libevent fails.
18152 - Check and warn about known-bad/slow libevent versions.
18153 - Pay more attention to the ClientOnly config option.
18154 - Have torctl.in/tor.sh.in check for location of su binary (needed
18156 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
18157 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
18158 HttpProxyAuthenticator
18159 - Stop warning about sigpipes in the logs. We're going to
18160 pretend that getting these occassionally is normal and fine.
18161 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
18163 installer screens; and don't put stuff into StartupItems unless
18164 the user asks you to.
18165 - Require servers that use the default dirservers to have public IP
18166 addresses. We have too many servers that are configured with private
18167 IPs and their admins never notice the log entries complaining that
18168 their descriptors are being rejected.
18169 - Add OSX uninstall instructions. An actual uninstall script will
18173 Changes in version 0.1.0.8-rc - 2005-05-23
18175 - It turns out that kqueue on OS X 10.3.9 was causing kernel
18176 panics. Disable kqueue on all OS X Tors.
18177 - Fix RPM: remove duplicate line accidentally added to the rpm
18179 - Disable threads on openbsd too, since its gethostaddr is not
18181 - Tolerate libevent 0.8 since it still works, even though it's
18183 - Enable building on Red Hat 9.0 again.
18184 - Allow the middle hop of the testing circuit to be running any
18185 version, now that most of them have the bugfix to let them connect
18186 to unknown servers. This will allow reachability testing to work
18187 even when 0.0.9.7-0.0.9.9 become obsolete.
18188 - Handle relay cells with rh.length too large. This prevents
18189 a potential attack that could read arbitrary memory (maybe even
18190 keys) from the exit server's process.
18191 - We screwed up the dirport reachability testing when we don't yet
18192 have a cached version of the directory. Hopefully now fixed.
18193 - Clean up router_load_single_router() (used by the controller),
18194 so it doesn't seg fault on error.
18195 - Fix a minor memory leak when somebody establishes an introduction
18196 point at your Tor server.
18197 - If a socks connection ends because read fails, don't warn that
18198 you're not sending a socks reply back.
18201 - Add HttpProxyAuthenticator config option too, that works like
18202 the HttpsProxyAuthenticator config option.
18203 - Encode hashed controller passwords in hex instead of base64,
18204 to make it easier to write controllers.
18207 Changes in version 0.1.0.7-rc - 2005-05-17
18209 - Fix a bug in the OS X package installer that prevented it from
18210 installing on Tiger.
18211 - Fix a script bug in the OS X package installer that made it
18212 complain during installation.
18213 - Find libevent even if it's hiding in /usr/local/ and your
18214 CFLAGS and LDFLAGS don't tell you to look there.
18215 - Be able to link with libevent as a shared library (the default
18216 after 1.0d), even if it's hiding in /usr/local/lib and even
18217 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18218 assuming you're running gcc. Otherwise fail and give a useful
18220 - Fix a bug in the RPM packager: set home directory for _tor to
18221 something more reasonable when first installing.
18222 - Free a minor amount of memory that is still reachable on exit.
18225 Changes in version 0.1.0.6-rc - 2005-05-14
18227 - Implement --disable-threads configure option. Disable threads on
18228 netbsd by default, because it appears to have no reentrant resolver
18230 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
18231 release (1.1) detects and disables kqueue if it's broken.
18232 - Append default exit policy before checking for implicit internal
18233 addresses. Now we don't log a bunch of complaints on startup
18234 when using the default exit policy.
18235 - Some people were putting "Address " in their torrc, and they had
18236 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18237 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18238 LOCALSTATEDIR/tor instead.
18239 - Fix fragmented-message bug in TorControl.py.
18240 - Resolve a minor bug which would prevent unreachable dirports
18241 from getting suppressed in the published descriptor.
18242 - When the controller gave us a new descriptor, we weren't resolving
18243 it immediately, so Tor would think its address was 0.0.0.0 until
18244 we fetched a new directory.
18245 - Fix an uppercase/lowercase case error in suppressing a bogus
18246 libevent warning on some Linuxes.
18249 - Begin scrubbing sensitive strings from logs by default. Turn off
18250 the config option SafeLogging if you need to do debugging.
18251 - Switch to a new buffer management algorithm, which tries to avoid
18252 reallocing and copying quite as much. In first tests it looks like
18253 it uses *more* memory on average, but less cpu.
18254 - First cut at support for "create-fast" cells. Clients can use
18255 these when extending to their first hop, since the TLS already
18256 provides forward secrecy and authentication. Not enabled on
18258 - When dirservers refuse a router descriptor, we now log its
18259 contactinfo, platform, and the poster's IP address.
18260 - Call tor_free_all instead of connections_free_all after forking, to
18261 save memory on systems that need to fork.
18262 - Whine at you if you're a server and you don't set your contactinfo.
18263 - Implement --verify-config command-line option to check if your torrc
18264 is valid without actually launching Tor.
18265 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
18266 rather than just rejecting it.
18269 Changes in version 0.1.0.5-rc - 2005-04-27
18271 - Stop trying to print a null pointer if an OR conn fails because
18272 we didn't like its cert.
18274 - Switch our internal buffers implementation to use a ring buffer,
18275 to hopefully improve performance for fast servers a lot.
18276 - Add HttpsProxyAuthenticator support (basic auth only), based
18277 on patch from Adam Langley.
18278 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18279 the fast servers that have been joining lately.
18280 - Give hidden service accesses extra time on the first attempt,
18281 since 60 seconds is often only barely enough. This might improve
18283 - Improve performance for dirservers: stop re-parsing the whole
18284 directory every time you regenerate it.
18285 - Add more debugging info to help us find the weird dns freebsd
18286 pthreads bug; cleaner debug messages to help track future issues.
18289 Changes in version 0.0.9.9 - 2005-04-23
18290 o Bugfixes on 0.0.9.x:
18291 - If unofficial Tor clients connect and send weird TLS certs, our
18292 Tor server triggers an assert. This release contains a minimal
18293 backport from the broader fix that we put into 0.1.0.4-rc.
18296 Changes in version 0.1.0.4-rc - 2005-04-23
18298 - If unofficial Tor clients connect and send weird TLS certs, our
18299 Tor server triggers an assert. Stop asserting, and start handling
18300 TLS errors better in other situations too.
18301 - When the controller asks us to tell it about all the debug-level
18302 logs, it turns out we were generating debug-level logs while
18303 telling it about them, which turns into a bad loop. Now keep
18304 track of whether you're sending a debug log to the controller,
18305 and don't log when you are.
18306 - Fix the "postdescriptor" feature of the controller interface: on
18307 non-complete success, only say "done" once.
18309 - Clients are now willing to load balance over up to 2mB, not 1mB,
18310 of advertised bandwidth capacity.
18311 - Add a NoPublish config option, so you can be a server (e.g. for
18312 testing running Tor servers in other Tor networks) without
18313 publishing your descriptor to the primary dirservers.
18316 Changes in version 0.1.0.3-rc - 2005-04-08
18317 o Improvements on 0.1.0.2-rc:
18318 - Client now retries when streams end early for 'hibernating' or
18319 'resource limit' reasons, rather than failing them.
18320 - More automated handling for dirserver operators:
18321 - Automatically approve nodes running 0.1.0.2-rc or later,
18322 now that the the reachability detection stuff is working.
18323 - Now we allow two unverified servers with the same nickname
18324 but different keys. But if a nickname is verified, only that
18325 nickname+key are allowed.
18326 - If you're an authdirserver connecting to an address:port,
18327 and it's not the OR you were expecting, forget about that
18328 descriptor. If he *was* the one you were expecting, then forget
18329 about all other descriptors for that address:port.
18330 - Allow servers to publish descriptors from 12 hours in the future.
18331 Corollary: only whine about clock skew from the dirserver if
18332 he's a trusted dirserver (since now even verified servers could
18333 have quite wrong clocks).
18334 - Adjust maximum skew and age for rendezvous descriptors: let skew
18335 be 48 hours rather than 90 minutes.
18336 - Efficiency improvements:
18337 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18338 it much faster to look up a circuit for each relay cell.
18339 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18340 since they're eating our cpu on exit nodes.
18341 - Stop wasting time doing a case insensitive comparison for every
18342 dns name every time we do any lookup. Canonicalize the names to
18343 lowercase and be done with it.
18344 - Start sending 'truncated' cells back rather than destroy cells,
18345 if the circuit closes in front of you. This means we won't have
18346 to abandon partially built circuits.
18347 - Only warn once per nickname from add_nickname_list_to_smartlist
18348 per failure, so an entrynode or exitnode choice that's down won't
18350 - Put a note in the torrc about abuse potential with the default
18352 - Revise control spec and implementation to allow all log messages to
18353 be sent to controller with their severities intact (suggested by
18354 Matt Edman). Update TorControl to handle new log event types.
18355 - Provide better explanation messages when controller's POSTDESCRIPTOR
18357 - Stop putting nodename in the Platform string in server descriptors.
18358 It doesn't actually help, and it is confusing/upsetting some people.
18360 o Bugfixes on 0.1.0.2-rc:
18361 - We were printing the host mask wrong in exit policies in server
18362 descriptors. This isn't a critical bug though, since we were still
18363 obeying the exit policy internally.
18364 - Fix Tor when compiled with libevent but without pthreads: move
18365 connection_unregister() from _connection_free() to
18367 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
18368 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
18369 when we look through the connection array, we'll find any of the
18370 cpu/dnsworkers. This is no good.
18372 o Bugfixes on 0.0.9.8:
18373 - Fix possible bug on threading platforms (e.g. win32) which was
18374 leaking a file descriptor whenever a cpuworker or dnsworker died.
18375 - When using preferred entry or exit nodes, ignore whether the
18376 circuit wants uptime or capacity. They asked for the nodes, they
18378 - chdir() to your datadirectory at the *end* of the daemonize process,
18379 not the beginning. This was a problem because the first time you
18380 run tor, if your datadir isn't there, and you have runasdaemon set
18381 to 1, it will try to chdir to it before it tries to create it. Oops.
18382 - Handle changed router status correctly when dirserver reloads
18383 fingerprint file. We used to be dropping all unverified descriptors
18384 right then. The bug was hidden because we would immediately
18385 fetch a directory from another dirserver, which would include the
18386 descriptors we just dropped.
18387 - When we're connecting to an OR and he's got a different nickname/key
18388 than we were expecting, only complain loudly if we're an OP or a
18389 dirserver. Complaining loudly to the OR admins just confuses them.
18390 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18391 artificially capped at 500kB.
18394 Changes in version 0.0.9.8 - 2005-04-07
18395 o Bugfixes on 0.0.9.x:
18396 - We have a bug that I haven't found yet. Sometimes, very rarely,
18397 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18398 thinks of itself as idle. This meant that no new circuits ever got
18399 established. Here's a workaround to kill any cpuworker that's been
18400 busy for more than 100 seconds.
18403 Changes in version 0.1.0.2-rc - 2005-04-01
18404 o Bugfixes on 0.1.0.1-rc:
18405 - Fixes on reachability detection:
18406 - Don't check for reachability while hibernating.
18407 - If ORPort is reachable but DirPort isn't, still publish the
18408 descriptor, but zero out DirPort until it's found reachable.
18409 - When building testing circs for ORPort testing, use only
18410 high-bandwidth nodes, so fewer circuits fail.
18411 - Complain about unreachable ORPort separately from unreachable
18412 DirPort, so the user knows what's going on.
18413 - Make sure we only conclude ORPort reachability if we didn't
18414 initiate the conn. Otherwise we could falsely conclude that
18415 we're reachable just because we connected to the guy earlier
18416 and he used that same pipe to extend to us.
18417 - Authdirservers shouldn't do ORPort reachability detection,
18418 since they're in clique mode, so it will be rare to find a
18419 server not already connected to them.
18420 - When building testing circuits, always pick middle hops running
18421 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18422 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18424 - When we decide we're reachable, actually publish our descriptor
18426 - Fix bug in redirectstream in the controller.
18427 - Fix the state descriptor strings so logs don't claim edge streams
18428 are in a different state than they actually are.
18429 - Use recent libevent features when possible (this only really affects
18430 win32 and osx right now, because the new libevent with these
18431 features hasn't been released yet). Add code to suppress spurious
18433 - Prevent possible segfault in connection_close_unattached_ap().
18434 - Fix newlines on torrc in win32.
18435 - Improve error msgs when tor-resolve fails.
18437 o Improvements on 0.0.9.x:
18438 - New experimental script tor/contrib/ExerciseServer.py (needs more
18439 work) that uses the controller interface to build circuits and
18440 fetch pages over them. This will help us bootstrap servers that
18441 have lots of capacity but haven't noticed it yet.
18442 - New experimental script tor/contrib/PathDemo.py (needs more work)
18443 that uses the controller interface to let you choose whole paths
18445 "<hostname>.<path,separated by dots>.<length of path>.path"
18446 - When we've connected to an OR and handshaked but didn't like
18447 the result, we were closing the conn without sending destroy
18448 cells back for pending circuits. Now send those destroys.
18451 Changes in version 0.0.9.7 - 2005-04-01
18452 o Bugfixes on 0.0.9.x:
18453 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18454 - Compare identity to identity, not to nickname, when extending to
18455 a router not already in the directory. This was preventing us from
18456 extending to unknown routers. Oops.
18457 - Make sure to create OS X Tor user in <500 range, so we aren't
18458 creating actual system users.
18459 - Note where connection-that-hasn't-sent-end was marked, and fix
18460 a few really loud instances of this harmless bug (it's fixed more
18464 Changes in version 0.1.0.1-rc - 2005-03-28
18466 - Add reachability testing. Your Tor server will automatically try
18467 to see if its ORPort and DirPort are reachable from the outside,
18468 and it won't upload its descriptor until it decides they are.
18469 - Handle unavailable hidden services better. Handle slow or busy
18470 hidden services better.
18471 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18473 - New exit policy: accept most low-numbered ports, rather than
18474 rejecting most low-numbered ports.
18475 - More Tor controller support (still experimental). See
18476 http://tor.eff.org/doc/control-spec.txt for all the new features,
18477 including signals to emulate unix signals from any platform;
18478 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18479 closestream; closecircuit; etc.
18480 - Make nt services work and start on startup on win32 (based on
18481 patch by Matt Edman).
18482 - Add a new AddressMap config directive to rewrite incoming socks
18483 addresses. This lets you, for example, declare an implicit
18484 required exit node for certain sites.
18485 - Add a new TrackHostExits config directive to trigger addressmaps
18486 for certain incoming socks addresses -- for sites that break when
18487 your exit keeps changing (based on patch by Mike Perry).
18488 - Redo the client-side dns cache so it's just an addressmap too.
18489 - Notice when our IP changes, and reset stats/uptime/reachability.
18490 - When an application is using socks5, give him the whole variety of
18491 potential socks5 responses (connect refused, host unreachable, etc),
18492 rather than just "success" or "failure".
18493 - A more sane version numbering system. See
18494 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18495 - New contributed script "exitlist": a simple python script to
18496 parse directories and find Tor nodes that exit to listed
18498 - New contributed script "privoxy-tor-toggle" to toggle whether
18499 Privoxy uses Tor. Seems to be configured for Debian by default.
18500 - Report HTTP reasons to client when getting a response from directory
18501 servers -- so you can actually know what went wrong.
18502 - New config option MaxAdvertisedBandwidth which lets you advertise
18503 a low bandwidthrate (to not attract as many circuits) while still
18504 allowing a higher bandwidthrate in reality.
18506 o Robustness/stability fixes:
18507 - Make Tor use Niels Provos's libevent instead of its current
18508 poll-but-sometimes-select mess. This will let us use faster async
18509 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
18511 - pthread support now too. This was forced because when we forked,
18512 we ended up wasting a lot of duplicate ram over time. Also switch
18513 to foo_r versions of some library calls to allow reentry and
18515 - Better handling for heterogeneous / unreliable nodes:
18516 - Annotate circuits w/ whether they aim to contain high uptime nodes
18517 and/or high capacity nodes. When building circuits, choose
18519 - This means that every single node in an intro rend circuit,
18520 not just the last one, will have a minimum uptime.
18521 - New config option LongLivedPorts to indicate application streams
18522 that will want high uptime circuits.
18523 - Servers reset uptime when a dir fetch entirely fails. This
18524 hopefully reflects stability of the server's network connectivity.
18525 - If somebody starts his tor server in Jan 2004 and then fixes his
18526 clock, don't make his published uptime be a year.
18527 - Reset published uptime when you wake up from hibernation.
18528 - Introduce a notion of 'internal' circs, which are chosen without
18529 regard to the exit policy of the last hop. Intro and rendezvous
18530 circs must be internal circs, to avoid leaking information. Resolve
18531 and connect streams can use internal circs if they want.
18532 - New circuit pooling algorithm: make sure to have enough circs around
18533 to satisfy any predicted ports, and also make sure to have 2 internal
18534 circs around if we've required internal circs lately (and with high
18535 uptime if we've seen that lately too).
18536 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18537 which describes how often we retry making new circuits if current
18538 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18539 how long we're willing to make use of an already-dirty circuit.
18540 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18541 circ as necessary, if there are any completed ones lying around
18542 when we try to launch one.
18543 - Make hidden services try to establish a rendezvous for 30 seconds,
18544 rather than for n (where n=3) attempts to build a circuit.
18545 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
18546 "ShutdownWaitLength".
18547 - Try to be more zealous about calling connection_edge_end when
18548 things go bad with edge conns in connection.c.
18549 - Revise tor-spec to add more/better stream end reasons.
18550 - Revise all calls to connection_edge_end to avoid sending "misc",
18551 and to take errno into account where possible.
18554 - Fix a race condition that can trigger an assert, when we have a
18555 pending create cell and an OR connection fails right then.
18556 - Fix several double-mark-for-close bugs, e.g. where we were finding
18557 a conn for a cell even if that conn is already marked for close.
18558 - Make sequence of log messages when starting on win32 with no config
18559 file more reasonable.
18560 - When choosing an exit node for a new non-internal circ, don't take
18561 into account whether it'll be useful for any pending x.onion
18562 addresses -- it won't.
18563 - Turn addr_policy_compare from a tristate to a quadstate; this should
18564 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18565 for google.com" problem.
18566 - Make "platform" string in descriptor more accurate for Win32 servers,
18567 so it's not just "unknown platform".
18568 - Fix an edge case in parsing config options (thanks weasel).
18569 If they say "--" on the commandline, it's not an option.
18570 - Reject odd-looking addresses at the client (e.g. addresses that
18571 contain a colon), rather than having the server drop them because
18573 - tor-resolve requests were ignoring .exit if there was a working circuit
18574 they could use instead.
18575 - REUSEADDR on normal platforms means you can rebind to the port
18576 right after somebody else has let it go. But REUSEADDR on win32
18577 means to let you bind to the port _even when somebody else
18578 already has it bound_! So, don't do that on Win32.
18579 - Change version parsing logic: a version is "obsolete" if it is not
18580 recommended and (1) there is a newer recommended version in the
18581 same series, or (2) there are no recommended versions in the same
18582 series, but there are some recommended versions in a newer series.
18583 A version is "new" if it is newer than any recommended version in
18585 - Stop most cases of hanging up on a socks connection without sending
18589 - Require BandwidthRate to be at least 20kB/s for servers.
18590 - When a dirserver causes you to give a warn, mention which dirserver
18592 - New config option DirAllowPrivateAddresses for authdirservers.
18593 Now by default they refuse router descriptors that have non-IP or
18594 private-IP addresses.
18595 - Stop publishing socksport in the directory, since it's not
18596 actually meant to be public. For compatibility, publish a 0 there
18598 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18599 smart" value, that is low for servers and high for clients.
18600 - If our clock jumps forward by 100 seconds or more, assume something
18601 has gone wrong with our network and abandon all not-yet-used circs.
18602 - Warn when exit policy implicitly allows local addresses.
18603 - If we get an incredibly skewed timestamp from a dirserver mirror
18604 that isn't a verified OR, don't warn -- it's probably him that's
18606 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18607 cookies to disk and doesn't log each web request to disk. (Thanks
18608 to Brett Carrington for pointing this out.)
18609 - When a client asks us for a dir mirror and we don't have one,
18610 launch an attempt to get a fresh one.
18611 - If we're hibernating and we get a SIGINT, exit immediately.
18612 - Add --with-dmalloc ./configure option, to track memory leaks.
18613 - And try to free all memory on closing, so we can detect what
18615 - Cache local dns resolves correctly even when they're .exit
18617 - Give a better warning when some other server advertises an
18618 ORPort that is actually an apache running ssl.
18619 - Add "opt hibernating 1" to server descriptor to make it clearer
18620 whether the server is hibernating.
18623 Changes in version 0.0.9.6 - 2005-03-24
18624 o Bugfixes on 0.0.9.x (crashes and asserts):
18625 - Add new end stream reasons to maintainance branch. Fix bug where
18626 reason (8) could trigger an assert. Prevent bug from recurring.
18627 - Apparently win32 stat wants paths to not end with a slash.
18628 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18629 blowing away the circuit that conn->cpath_layer points to, then
18630 checking to see if the circ is well-formed. Backport check to make
18631 sure we dont use the cpath on a closed connection.
18632 - Prevent circuit_resume_edge_reading_helper() from trying to package
18633 inbufs for marked-for-close streams.
18634 - Don't crash on hup if your options->address has become unresolvable.
18635 - Some systems (like OS X) sometimes accept() a connection and tell
18636 you the remote host is 0.0.0.0:0. If this happens, due to some
18637 other mis-features, we get confused; so refuse the conn for now.
18639 o Bugfixes on 0.0.9.x (other):
18640 - Fix harmless but scary "Unrecognized content encoding" warn message.
18641 - Add new stream error reason: TORPROTOCOL reason means "you are not
18642 speaking a version of Tor I understand; say bye-bye to your stream."
18643 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18644 into the future, now that we are more tolerant of skew. This
18645 resolves a bug where a Tor server would refuse to cache a directory
18646 because all the directories it gets are too far in the future;
18647 yet the Tor server never logs any complaints about clock skew.
18648 - Mac packaging magic: make man pages useable, and do not overwrite
18649 existing torrc files.
18650 - Make OS X log happily to /var/log/tor/tor.log
18653 Changes in version 0.0.9.5 - 2005-02-22
18654 o Bugfixes on 0.0.9.x:
18655 - Fix an assert race at exit nodes when resolve requests fail.
18656 - Stop picking unverified dir mirrors--it only leads to misery.
18657 - Patch from Matt Edman to make NT services work better. Service
18658 support is still not compiled into the executable by default.
18659 - Patch from Dmitri Bely so the Tor service runs better under
18660 the win32 SYSTEM account.
18661 - Make tor-resolve actually work (?) on Win32.
18662 - Fix a sign bug when getrlimit claims to have 4+ billion
18663 file descriptors available.
18664 - Stop refusing to start when bandwidthburst == bandwidthrate.
18665 - When create cells have been on the onion queue more than five
18666 seconds, just send back a destroy and take them off the list.
18669 Changes in version 0.0.9.4 - 2005-02-03
18670 o Bugfixes on 0.0.9:
18671 - Fix an assert bug that took down most of our servers: when
18672 a server claims to have 1 GB of bandwidthburst, don't
18674 - Don't crash as badly if we have spawned the max allowed number
18675 of dnsworkers, or we're out of file descriptors.
18676 - Block more file-sharing ports in the default exit policy.
18677 - MaxConn is now automatically set to the hard limit of max
18678 file descriptors we're allowed (ulimit -n), minus a few for
18680 - Give a clearer message when servers need to raise their
18681 ulimit -n when they start running out of file descriptors.
18682 - SGI Compatibility patches from Jan Schaumann.
18683 - Tolerate a corrupt cached directory better.
18684 - When a dirserver hasn't approved your server, list which one.
18685 - Go into soft hibernation after 95% of the bandwidth is used,
18686 not 99%. This is especially important for daily hibernators who
18687 have a small accounting max. Hopefully it will result in fewer
18688 cut connections when the hard hibernation starts.
18689 - Load-balance better when using servers that claim more than
18690 800kB/s of capacity.
18691 - Make NT services work (experimental, only used if compiled in).
18694 Changes in version 0.0.9.3 - 2005-01-21
18695 o Bugfixes on 0.0.9:
18696 - Backport the cpu use fixes from main branch, so busy servers won't
18697 need as much processor time.
18698 - Work better when we go offline and then come back, or when we
18699 run Tor at boot before the network is up. We do this by
18700 optimistically trying to fetch a new directory whenever an
18701 application request comes in and we think we're offline -- the
18702 human is hopefully a good measure of when the network is back.
18703 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18704 long as you keep using them; actually publish hidserv descriptors
18705 shortly after they change, rather than waiting 20-40 minutes.
18706 - Enable Mac startup script by default.
18707 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18708 - When you update AllowUnverifiedNodes or FirewallPorts via the
18709 controller's setconf feature, we were always appending, never
18711 - When you update HiddenServiceDir via setconf, it was screwing up
18712 the order of reading the lines, making it fail.
18713 - Do not rewrite a cached directory back to the cache; otherwise we
18714 will think it is recent and not fetch a newer one on startup.
18715 - Workaround for webservers that lie about Content-Encoding: Tor
18716 now tries to autodetect compressed directories and compression
18717 itself. This lets us Proxypass dir fetches through apache.
18720 Changes in version 0.0.9.2 - 2005-01-04
18721 o Bugfixes on 0.0.9 (crashes and asserts):
18722 - Fix an assert on startup when the disk is full and you're logging
18724 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18725 style address, then we'd crash.
18726 - Fix an assert trigger when the running-routers string we get from
18727 a dirserver is broken.
18728 - Make worker threads start and run on win32. Now win32 servers
18730 - Bandaid (not actually fix, but now it doesn't crash) an assert
18731 where the dns worker dies mysteriously and the main Tor process
18732 doesn't remember anything about the address it was resolving.
18734 o Bugfixes on 0.0.9 (Win32):
18735 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18736 name out of the warning/assert messages.
18737 - Fix a superficial "unhandled error on read" bug on win32.
18738 - The win32 installer no longer requires a click-through for our
18739 license, since our Free Software license grants rights but does not
18741 - Win32: When connecting to a dirserver fails, try another one
18742 immediately. (This was already working for non-win32 Tors.)
18743 - Stop trying to parse $HOME on win32 when hunting for default
18745 - Make tor-resolve.c work on win32 by calling network_init().
18747 o Bugfixes on 0.0.9 (other):
18748 - Make 0.0.9.x build on Solaris again.
18749 - Due to a fencepost error, we were blowing away the \n when reporting
18750 confvalue items in the controller. So asking for multiple config
18751 values at once couldn't work.
18752 - When listing circuits that are pending on an opening OR connection,
18753 if we're an OR we were listing circuits that *end* at us as
18754 being pending on every listener, dns/cpu worker, etc. Stop that.
18755 - Dirservers were failing to create 'running-routers' or 'directory'
18756 strings if we had more than some threshold of routers. Fix them so
18757 they can handle any number of routers.
18758 - Fix a superficial "Duplicate mark for close" bug.
18759 - Stop checking for clock skew for OR connections, even for servers.
18760 - Fix a fencepost error that was chopping off the last letter of any
18761 nickname that is the maximum allowed nickname length.
18762 - Update URLs in log messages so they point to the new website.
18763 - Fix a potential problem in mangling server private keys while
18764 writing to disk (not triggered yet, as far as we know).
18765 - Include the licenses for other free software we include in Tor,
18766 now that we're shipping binary distributions more regularly.
18769 Changes in version 0.0.9.1 - 2004-12-15
18770 o Bugfixes on 0.0.9:
18771 - Make hibernation actually work.
18772 - Make HashedControlPassword config option work.
18773 - When we're reporting event circuit status to a controller,
18774 don't use the stream status code.
18777 Changes in version 0.0.9 - 2004-12-12
18779 - Clean up manpage and torrc.sample file.
18780 - Clean up severities and text of log warnings.
18782 - Make servers trigger an assert when they enter hibernation.
18785 Changes in version 0.0.9rc7 - 2004-12-08
18786 o Bugfixes on 0.0.9rc:
18787 - Fix a stack-trashing crash when an exit node begins hibernating.
18788 - Avoid looking at unallocated memory while considering which
18789 ports we need to build circuits to cover.
18790 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18791 we shouldn't hold-open-until-flush if the eof arrived first.
18792 - Fix a bug with init_cookie_authentication() in the controller.
18793 - When recommending new-format log lines, if the upper bound is
18794 LOG_ERR, leave it implicit.
18796 o Bugfixes on 0.0.8.1:
18797 - Fix a whole slew of memory leaks.
18798 - Fix isspace() and friends so they still make Solaris happy
18799 but also so they don't trigger asserts on win32.
18800 - Fix parse_iso_time on platforms without strptime (eg win32).
18801 - win32: tolerate extra "readable" events better.
18802 - win32: when being multithreaded, leave parent fdarray open.
18803 - Make unit tests work on win32.
18806 Changes in version 0.0.9rc6 - 2004-12-06
18807 o Bugfixes on 0.0.9pre:
18808 - Clean up some more integer underflow opportunities (not exploitable
18810 - While hibernating, hup should not regrow our listeners.
18811 - Send an end to the streams we close when we hibernate, rather
18812 than just chopping them off.
18813 - React to eof immediately on non-open edge connections.
18815 o Bugfixes on 0.0.8.1:
18816 - Calculate timeout for waiting for a connected cell from the time
18817 we sent the begin cell, not from the time the stream started. If
18818 it took a long time to establish the circuit, we would time out
18819 right after sending the begin cell.
18820 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18821 of * as always matching, so we were picking reject *:* nodes as
18822 exit nodes too. Oops.
18825 - New circuit building strategy: keep a list of ports that we've
18826 used in the past 6 hours, and always try to have 2 circuits open
18827 or on the way that will handle each such port. Seed us with port
18828 80 so web users won't complain that Tor is "slow to start up".
18829 - Make kill -USR1 dump more useful stats about circuits.
18830 - When warning about retrying or giving up, print the address, so
18831 the user knows which one it's talking about.
18832 - If you haven't used a clean circuit in an hour, throw it away,
18833 just to be on the safe side. (This means after 6 hours a totally
18834 unused Tor client will have no circuits open.)
18837 Changes in version 0.0.9rc5 - 2004-12-01
18838 o Bugfixes on 0.0.8.1:
18839 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18840 - Let resolve conns retry/expire also, rather than sticking around
18842 - If we are using select, make sure we stay within FD_SETSIZE.
18844 o Bugfixes on 0.0.9pre:
18845 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
18846 but doesn't seem to be currently; thanks to Ilja van Sprundel for
18848 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
18849 instead. Impose minima and maxima for all *Period options; impose
18850 even tighter maxima for fetching if we are a caching dirserver.
18851 Clip rather than rejecting.
18852 - Fetch cached running-routers from servers that serve it (that is,
18853 authdirservers and servers running 0.0.9rc5-cvs or later.)
18856 - Accept *:706 (silc) in default exit policy.
18857 - Implement new versioning format for post 0.1.
18858 - Support "foo.nickname.exit" addresses, to let Alice request the
18859 address "foo" as viewed by exit node "nickname". Based on a patch
18861 - Make tor --version --version dump the cvs Id of every file.
18864 Changes in version 0.0.9rc4 - 2004-11-28
18865 o Bugfixes on 0.0.8.1:
18866 - Make windows sockets actually non-blocking (oops), and handle
18867 win32 socket errors better.
18869 o Bugfixes on 0.0.9rc1:
18870 - Actually catch the -USR2 signal.
18873 Changes in version 0.0.9rc3 - 2004-11-25
18874 o Bugfixes on 0.0.8.1:
18875 - Flush the log file descriptor after we print "Tor opening log file",
18876 so we don't see those messages days later.
18878 o Bugfixes on 0.0.9rc1:
18879 - Make tor-resolve work again.
18880 - Avoid infinite loop in tor-resolve if tor hangs up on it.
18881 - Fix an assert trigger for clients/servers handling resolves.
18884 Changes in version 0.0.9rc2 - 2004-11-24
18885 o Bugfixes on 0.0.9rc1:
18886 - I broke socks5 support while fixing the eof bug.
18887 - Allow unitless bandwidths and intervals; they default to bytes
18889 - New servers don't start out hibernating; they are active until
18890 they run out of bytes, so they have a better estimate of how
18891 long it takes, and so their operators can know they're working.
18894 Changes in version 0.0.9rc1 - 2004-11-23
18895 o Bugfixes on 0.0.8.1:
18896 - Finally fix a bug that's been plaguing us for a year:
18897 With high load, circuit package window was reaching 0. Whenever
18898 we got a circuit-level sendme, we were reading a lot on each
18899 socket, but only writing out a bit. So we would eventually reach
18900 eof. This would be noticed and acted on even when there were still
18901 bytes sitting in the inbuf.
18902 - When poll() is interrupted, we shouldn't believe the revents values.
18904 o Bugfixes on 0.0.9pre6:
18905 - Fix hibernate bug that caused pre6 to be broken.
18906 - Don't keep rephist info for routers that haven't had activity for
18907 24 hours. (This matters now that clients have keys, since we track
18909 - Never call close_temp_logs while validating log options.
18910 - Fix backslash-escaping on tor.sh.in and torctl.in.
18913 - Implement weekly/monthly/daily accounting: now you specify your
18914 hibernation properties by
18915 AccountingMax N bytes|KB|MB|GB|TB
18916 AccountingStart day|week|month [day] HH:MM
18917 Defaults to "month 1 0:00".
18918 - Let bandwidth and interval config options be specified as 5 bytes,
18919 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18920 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18921 get back to normal.)
18922 - If your requested entry or exit node has advertised bandwidth 0,
18924 - Be more greedy about filling up relay cells -- we try reading again
18925 once we've processed the stuff we read, in case enough has arrived
18926 to fill the last cell completely.
18927 - Apply NT service patch from Osamu Fujino. Still needs more work.
18930 Changes in version 0.0.9pre6 - 2004-11-15
18931 o Bugfixes on 0.0.8.1:
18932 - Fix assert failure on malformed socks4a requests.
18933 - Use identity comparison, not nickname comparison, to choose which
18934 half of circuit-ID-space each side gets to use. This is needed
18935 because sometimes we think of a router as a nickname, and sometimes
18936 as a hex ID, and we can't predict what the other side will do.
18937 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18938 write() call will fail and we handle it there.
18939 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18940 and smartlist_len, which are two major profiling offenders.
18942 o Bugfixes on 0.0.9pre5:
18943 - Fix a bug in read_all that was corrupting config files on windows.
18944 - When we're raising the max number of open file descriptors to
18945 'unlimited', don't log that we just raised it to '-1'.
18946 - Include event code with events, as required by control-spec.txt.
18947 - Don't give a fingerprint when clients do --list-fingerprint:
18948 it's misleading, because it will never be the same again.
18949 - Stop using strlcpy in tor_strndup, since it was slowing us
18951 - Remove warn on startup about missing cached-directory file.
18952 - Make kill -USR1 work again.
18953 - Hibernate if we start tor during the "wait for wakeup-time" phase
18954 of an accounting interval. Log our hibernation plans better.
18955 - Authoritative dirservers now also cache their directory, so they
18956 have it on start-up.
18959 - Fetch running-routers; cache running-routers; compress
18960 running-routers; serve compressed running-routers.z
18961 - Add NSI installer script contributed by J Doe.
18962 - Commit VC6 and VC7 workspace/project files.
18963 - Commit a tor.spec for making RPM files, with help from jbash.
18964 - Add contrib/torctl.in contributed by Glenn Fink.
18965 - Implement the control-spec's SAVECONF command, to write your
18966 configuration to torrc.
18967 - Get cookie authentication for the controller closer to working.
18968 - Include control-spec.txt in the tarball.
18969 - When set_conf changes our server descriptor, upload a new copy.
18970 But don't upload it too often if there are frequent changes.
18971 - Document authentication config in man page, and document signals
18973 - Clean up confusing parts of man page and torrc.sample.
18974 - Make expand_filename handle ~ and ~username.
18975 - Use autoconf to enable largefile support where necessary. Use
18976 ftello where available, since ftell can fail at 2GB.
18977 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18978 log more informatively.
18979 - Give a slightly more useful output for "tor -h".
18980 - Refuse application socks connections to port 0.
18981 - Check clock skew for verified servers, but allow unverified
18982 servers and clients to have any clock skew.
18983 - Break DirFetchPostPeriod into:
18984 - DirFetchPeriod for fetching full directory,
18985 - StatusFetchPeriod for fetching running-routers,
18986 - DirPostPeriod for posting server descriptor,
18987 - RendPostPeriod for posting hidden service descriptors.
18988 - Make sure the hidden service descriptors are at a random offset
18989 from each other, to hinder linkability.
18992 Changes in version 0.0.9pre5 - 2004-11-09
18993 o Bugfixes on 0.0.9pre4:
18994 - Fix a seg fault in unit tests (doesn't affect main program).
18995 - Fix an assert bug where a hidden service provider would fail if
18996 the first hop of his rendezvous circuit was down.
18997 - Hidden service operators now correctly handle version 1 style
18998 INTRODUCE1 cells (nobody generates them still, so not a critical
19000 - If do_hup fails, actually notice.
19001 - Handle more errnos from accept() without closing the listener.
19002 Some OpenBSD machines were closing their listeners because
19003 they ran out of file descriptors.
19004 - Send resolve cells to exit routers that are running a new
19005 enough version of the resolve code to work right.
19006 - Better handling of winsock includes on non-MSV win32 compilers.
19007 - Some people had wrapped their tor client/server in a script
19008 that would restart it whenever it died. This did not play well
19009 with our "shut down if your version is obsolete" code. Now people
19010 don't fetch a new directory if their local cached version is
19012 - Make our autogen.sh work on ksh as well as bash.
19015 - Hibernation: New config option "AccountingMaxKB" lets you
19016 set how many KBytes per month you want to allow your server to
19017 consume. Rather than spreading those bytes out evenly over the
19018 month, we instead hibernate for some of the month and pop up
19019 at a deterministic time, work until the bytes are consumed, then
19020 hibernate again. Config option "MonthlyAccountingStart" lets you
19021 specify which day of the month your billing cycle starts on.
19022 - Control interface: a separate program can now talk to your
19023 client/server over a socket, and get/set config options, receive
19024 notifications of circuits and streams starting/finishing/dying,
19025 bandwidth used, etc. The next step is to get some GUIs working.
19026 Let us know if you want to help out. See doc/control-spec.txt .
19027 - Ship a contrib/tor-control.py as an example script to interact
19028 with the control port.
19029 - "tor --hash-password zzyxz" will output a salted password for
19030 use in authenticating to the control interface.
19031 - New log format in config:
19032 "Log minsev[-maxsev] stdout|stderr|syslog" or
19033 "Log minsev[-maxsev] file /var/foo"
19036 - DirPolicy config option, to let people reject incoming addresses
19037 from their dirserver.
19038 - "tor --list-fingerprint" will list your identity key fingerprint
19040 - Add "pass" target for RedirectExit, to make it easier to break
19041 out of a sequence of RedirectExit rules.
19042 - Clients now generate a TLS cert too, in preparation for having
19043 them act more like real nodes.
19044 - Ship src/win32/ in the tarball, so people can use it to build.
19045 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19047 - New "router-status" line in directory, to better bind each verified
19048 nickname to its identity key.
19049 - Deprecate unofficial config option abbreviations, and abbreviations
19050 not on the command line.
19051 - Add a pure-C tor-resolve implementation.
19052 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19053 1024) file descriptors.
19055 o Code security improvements, inspired by Ilja:
19056 - Replace sprintf with snprintf. (I think they were all safe, but
19058 - Replace strcpy/strncpy with strlcpy in more places.
19059 - Avoid strcat; use snprintf or strlcat instead.
19060 - snprintf wrapper with consistent (though not C99) overflow behavior.
19063 Changes in version 0.0.9pre4 - 2004-10-17
19064 o Bugfixes on 0.0.9pre3:
19065 - If the server doesn't specify an exit policy, use the real default
19066 exit policy, not reject *:*.
19067 - Ignore fascistfirewall when uploading/downloading hidden service
19068 descriptors, since we go through Tor for those; and when using
19069 an HttpProxy, since we assume it can reach them all.
19070 - When looking for an authoritative dirserver, use only the ones
19071 configured at boot. Don't bother looking in the directory.
19072 - The rest of the fix for get_default_conf_file() on older win32.
19073 - Make 'Routerfile' config option obsolete.
19076 - New 'MyFamily nick1,...' config option for a server to
19077 specify other servers that shouldn't be used in the same circuit
19078 with it. Only believed if nick1 also specifies us.
19079 - New 'NodeFamily nick1,nick2,...' config option for a client to
19080 specify nodes that it doesn't want to use in the same circuit.
19081 - New 'Redirectexit pattern address:port' config option for a
19082 server to redirect exit connections, e.g. to a local squid.
19085 Changes in version 0.0.9pre3 - 2004-10-13
19086 o Bugfixes on 0.0.8.1:
19087 - Better torrc example lines for dirbindaddress and orbindaddress.
19088 - Improved bounds checking on parsed ints (e.g. config options and
19089 the ones we find in directories.)
19090 - Better handling of size_t vs int, so we're more robust on 64
19092 - Fix the rest of the bug where a newly started OR would appear
19093 as unverified even after we've added his fingerprint and hupped
19095 - Fix a bug from 0.0.7: when read() failed on a stream, we would
19096 close it without sending back an end. So 'connection refused'
19097 would simply be ignored and the user would get no response.
19099 o Bugfixes on 0.0.9pre2:
19100 - Serving the cached-on-disk directory to people is bad. We now
19101 provide no directory until we've fetched a fresh one.
19102 - Workaround for bug on windows where cached-directories get crlf
19104 - Make get_default_conf_file() work on older windows too.
19105 - If we write a *:* exit policy line in the descriptor, don't write
19106 any more exit policy lines.
19109 - Use only 0.0.9pre1 and later servers for resolve cells.
19110 - Make the dirservers file obsolete.
19111 - Include a dir-signing-key token in directories to tell the
19112 parsing entity which key is being used to sign.
19113 - Remove the built-in bulky default dirservers string.
19114 - New config option "Dirserver %s:%d [fingerprint]", which can be
19115 repeated as many times as needed. If no dirservers specified,
19116 default to moria1,moria2,tor26.
19117 - Make moria2 advertise a dirport of 80, so people behind firewalls
19118 will be able to get a directory.
19119 - Http proxy support
19120 - Dirservers translate requests for http://%s:%d/x to /x
19121 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
19122 be routed through this host.
19123 - Clients ask for /tor/x rather than /x for new enough dirservers.
19124 This way we can one day coexist peacefully with apache.
19125 - Clients specify a "Host: %s%d" http header, to be compatible
19126 with more proxies, and so running squid on an exit node can work.
19129 Changes in version 0.0.8.1 - 2004-10-13
19131 - Fix a seg fault that can be triggered remotely for Tor
19132 clients/servers with an open dirport.
19133 - Fix a rare assert trigger, where routerinfos for entries in
19134 our cpath would expire while we're building the path.
19135 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19136 - Fix a rare seg fault for people running hidden services on
19137 intermittent connections.
19138 - Fix a bug in parsing opt keywords with objects.
19139 - Fix a stale pointer assert bug when a stream detaches and
19141 - Fix a string format vulnerability (probably not exploitable)
19142 in reporting stats locally.
19143 - Fix an assert trigger: sometimes launching circuits can fail
19144 immediately, e.g. because too many circuits have failed recently.
19145 - Fix a compile warning on 64 bit platforms.
19148 Changes in version 0.0.9pre2 - 2004-10-03
19150 - Make fetching a cached directory work for 64-bit platforms too.
19151 - Make zlib.h a required header, not an optional header.
19154 Changes in version 0.0.9pre1 - 2004-10-01
19156 - Stop using separate defaults for no-config-file and
19157 empty-config-file. Now you have to explicitly turn off SocksPort,
19158 if you don't want it open.
19159 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19160 - Improve man page to mention more of the 0.0.8 features.
19161 - Fix a rare seg fault for people running hidden services on
19162 intermittent connections.
19163 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
19165 - Fix more dns related bugs: send back resolve_failed and end cells
19166 more reliably when the resolve fails, rather than closing the
19167 circuit and then trying to send the cell. Also attach dummy resolve
19168 connections to a circuit *before* calling dns_resolve(), to fix
19169 a bug where cached answers would never be sent in RESOLVED cells.
19170 - When we run out of disk space, or other log writing error, don't
19171 crash. Just stop logging to that log and continue.
19172 - We were starting to daemonize before we opened our logs, so if
19173 there were any problems opening logs, we would complain to stderr,
19174 which wouldn't work, and then mysteriously exit.
19175 - Fix a rare bug where sometimes a verified OR would connect to us
19176 before he'd uploaded his descriptor, which would cause us to
19177 assign conn->nickname as though he's unverified. Now we look through
19178 the fingerprint list to see if he's there.
19179 - Fix a rare assert trigger, where routerinfos for entries in
19180 our cpath would expire while we're building the path.
19183 - Clients can ask dirservers for /dir.z to get a compressed version
19184 of the directory. Only works for servers running 0.0.9, of course.
19185 - Make clients cache directories and use them to seed their router
19186 lists at startup. This means clients have a datadir again.
19187 - Configuration infrastructure support for warning on obsolete
19189 - Respond to content-encoding headers by trying to uncompress as
19191 - Reply with a deflated directory when a client asks for "dir.z".
19192 We could use allow-encodings instead, but allow-encodings isn't
19193 specified in HTTP 1.0.
19194 - Raise the max dns workers from 50 to 100.
19195 - Discourage people from setting their dirfetchpostperiod more often
19196 than once per minute.
19197 - Protect dirservers from overzealous descriptor uploading -- wait
19198 10 seconds after directory gets dirty, before regenerating.
19201 Changes in version 0.0.8 - 2004-08-25
19202 o Port it to SunOS 5.9 / Athena
19205 Changes in version 0.0.8rc2 - 2004-08-20
19206 o Make it compile on cygwin again.
19207 o When picking unverified routers, skip those with low uptime and/or
19208 low bandwidth, depending on what properties you care about.
19211 Changes in version 0.0.8rc1 - 2004-08-18
19212 o Changes from 0.0.7.3:
19214 - Fix assert triggers: if the other side returns an address 0.0.0.0,
19215 don't put it into the client dns cache.
19216 - If a begin failed due to exit policy, but we believe the IP address
19217 should have been allowed, switch that router to exitpolicy reject *:*
19218 until we get our next directory.
19220 - Clients choose nodes proportional to advertised bandwidth.
19221 - Avoid using nodes with low uptime as introduction points.
19222 - Handle servers with dynamic IP addresses: don't replace
19223 options->Address with the resolved one at startup, and
19224 detect our address right before we make a routerinfo each time.
19225 - 'FascistFirewall' option to pick dirservers and ORs on specific
19226 ports; plus 'FirewallPorts' config option to tell FascistFirewall
19227 which ports are open. (Defaults to 80,443)
19228 - Be more aggressive about trying to make circuits when the network
19229 has changed (e.g. when you unsuspend your laptop).
19230 - Check for time skew on http headers; report date in response to
19232 - If the entrynode config line has only one node, don't pick it as
19234 - Add strict{entry|exit}nodes config options. If set to 1, then
19235 we refuse to build circuits that don't include the specified entry
19237 - OutboundBindAddress config option, to bind to a specific
19238 IP address for outgoing connect()s.
19239 - End truncated log entries (e.g. directories) with "[truncated]".
19241 o Patches to 0.0.8preX:
19243 - Patches to compile and run on win32 again (maybe)?
19244 - Fix crash when looking for ~/.torrc with no $HOME set.
19245 - Fix a race bug in the unit tests.
19246 - Handle verified/unverified name collisions better when new
19247 routerinfo's arrive in a directory.
19248 - Sometimes routers were getting entered into the stats before
19249 we'd assigned their identity_digest. Oops.
19250 - Only pick and establish intro points after we've gotten a
19253 - AllowUnverifiedNodes config option to let circuits choose no-name
19254 routers in entry,middle,exit,introduction,rendezvous positions.
19255 Allow middle and rendezvous positions by default.
19256 - Add a man page for tor-resolve.
19259 Changes in version 0.0.7.3 - 2004-08-12
19260 o Stop dnsworkers from triggering an assert failure when you
19261 ask them to resolve the host "".
19264 Changes in version 0.0.8pre3 - 2004-08-09
19265 o Changes from 0.0.7.2:
19266 - Allow multiple ORs with same nickname in routerlist -- now when
19267 people give us one identity key for a nickname, then later
19268 another, we don't constantly complain until the first expires.
19269 - Remember used bandwidth (both in and out), and publish 15-minute
19270 snapshots for the past day into our descriptor.
19271 - You can now fetch $DIRURL/running-routers to get just the
19272 running-routers line, not the whole descriptor list. (But
19273 clients don't use this yet.)
19274 - When people mistakenly use Tor as an http proxy, point them
19275 at the tor-doc.html rather than the INSTALL.
19276 - Remove our mostly unused -- and broken -- hex_encode()
19277 function. Use base16_encode() instead. (Thanks to Timo Lindfors
19278 for pointing out this bug.)
19279 - Rotate onion keys every 12 hours, not every 2 hours, so we have
19280 fewer problems with people using the wrong key.
19281 - Change the default exit policy to reject the default edonkey,
19282 kazaa, gnutella ports.
19283 - Add replace_file() to util.[ch] to handle win32's rename().
19285 o Changes from 0.0.8preX:
19286 - Fix two bugs in saving onion keys to disk when rotating, so
19287 hopefully we'll get fewer people using old onion keys.
19288 - Fix an assert error that was making SocksPolicy not work.
19289 - Be willing to expire routers that have an open dirport -- it's
19290 just the authoritative dirservers we want to not forget.
19291 - Reject tor-resolve requests for .onion addresses early, so we
19292 don't build a whole rendezvous circuit and then fail.
19293 - When you're warning a server that he's unverified, don't cry
19294 wolf unpredictably.
19295 - Fix a race condition: don't try to extend onto a connection
19296 that's still handshaking.
19297 - For servers in clique mode, require the conn to be open before
19298 you'll choose it for your path.
19299 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
19300 end relay cell, etc.
19301 - Measure bandwidth capacity over the last 24 hours, not just 12
19302 - Bugfix: authoritative dirservers were making and signing a new
19303 directory for each client, rather than reusing the cached one.
19306 Changes in version 0.0.8pre2 - 2004-08-04
19307 o Changes from 0.0.7.2:
19309 - Check directory signature _before_ you decide whether you're
19310 you're running an obsolete version and should exit.
19311 - Check directory signature _before_ you parse the running-routers
19312 list to decide who's running or verified.
19313 - Bugfixes and features:
19314 - Check return value of fclose while writing to disk, so we don't
19315 end up with broken files when servers run out of disk space.
19316 - Log a warning if the user uses an unsafe socks variant, so people
19317 are more likely to learn about privoxy or socat.
19318 - Dirservers now include RFC1123-style dates in the HTTP headers,
19319 which one day we will use to better detect clock skew.
19321 o Changes from 0.0.8pre1:
19322 - Make it compile without warnings again on win32.
19323 - Log a warning if you're running an unverified server, to let you
19324 know you might want to get it verified.
19325 - Only pick a default nickname if you plan to be a server.
19328 Changes in version 0.0.8pre1 - 2004-07-23
19330 - Made our unit tests compile again on OpenBSD 3.5, and tor
19331 itself compile again on OpenBSD on a sparc64.
19332 - We were neglecting milliseconds when logging on win32, so
19333 everything appeared to happen at the beginning of each second.
19335 o Protocol changes:
19336 - 'Extend' relay cell payloads now include the digest of the
19337 intended next hop's identity key. Now we can verify that we're
19338 extending to the right router, and also extend to routers we
19339 hadn't heard of before.
19342 - Tor nodes can now act as relays (with an advertised ORPort)
19343 without being manually verified by the dirserver operators.
19344 - Uploaded descriptors of unverified routers are now accepted
19345 by the dirservers, and included in the directory.
19346 - Verified routers are listed by nickname in the running-routers
19347 list; unverified routers are listed as "$<fingerprint>".
19348 - We now use hash-of-identity-key in most places rather than
19349 nickname or addr:port, for improved security/flexibility.
19350 - To avoid Sybil attacks, paths still use only verified servers.
19351 But now we have a chance to play around with hybrid approaches.
19352 - Nodes track bandwidth usage to estimate capacity (not used yet).
19353 - ClientOnly option for nodes that never want to become servers.
19354 - Directory caching.
19355 - "AuthoritativeDir 1" option for the official dirservers.
19356 - Now other nodes (clients and servers) will cache the latest
19357 directory they've pulled down.
19358 - They can enable their DirPort to serve it to others.
19359 - Clients will pull down a directory from any node with an open
19360 DirPort, and check the signature/timestamp correctly.
19361 - Authoritative dirservers now fetch directories from other
19362 authdirservers, to stay better synced.
19363 - Running-routers list tells who's down also, along with noting
19364 if they're verified (listed by nickname) or unverified (listed
19366 - Allow dirservers to serve running-router list separately.
19367 This isn't used yet.
19368 - ORs connect-on-demand to other ORs
19369 - If you get an extend cell to an OR you're not connected to,
19370 connect, handshake, and forward the create cell.
19371 - The authoritative dirservers stay connected to everybody,
19372 and everybody stays connected to 0.0.7 servers, but otherwise
19373 clients/servers expire unused connections after 5 minutes.
19374 - When servers get a sigint, they delay 30 seconds (refusing new
19375 connections) then exit. A second sigint causes immediate exit.
19376 - File and name management:
19377 - Look for .torrc if no CONFDIR "torrc" is found.
19378 - If no datadir is defined, then choose, make, and secure ~/.tor
19380 - If torrc not found, exitpolicy reject *:*.
19381 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19382 - If no nickname is defined, derive default from hostname.
19383 - Rename secret key files, e.g. identity.key -> secret_id_key,
19384 to discourage people from mailing their identity key to tor-ops.
19385 - Refuse to build a circuit before the directory has arrived --
19386 it won't work anyway, since you won't know the right onion keys
19388 - Try other dirservers immediately if the one you try is down. This
19389 should tolerate down dirservers better now.
19390 - Parse tor version numbers so we can do an is-newer-than check
19391 rather than an is-in-the-list check.
19392 - New socks command 'resolve', to let us shim gethostbyname()
19394 - A 'tor_resolve' script to access the socks resolve functionality.
19395 - A new socks-extensions.txt doc file to describe our
19396 interpretation and extensions to the socks protocols.
19397 - Add a ContactInfo option, which gets published in descriptor.
19398 - Publish OR uptime in descriptor (and thus in directory) too.
19399 - Write tor version at the top of each log file
19400 - New docs in the tarball:
19402 - Document that you should proxy your SSL traffic too.
19405 Changes in version 0.0.7.2 - 2004-07-07
19406 o A better fix for the 0.0.0.0 problem, that will hopefully
19407 eliminate the remaining related assertion failures.
19410 Changes in version 0.0.7.1 - 2004-07-04
19411 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19412 since internally we use 0.0.0.0 to signify "not yet resolved".
19415 Changes in version 0.0.7 - 2004-06-07
19416 o Updated the man page to reflect the new features.
19419 Changes in version 0.0.7rc2 - 2004-06-06
19420 o Changes from 0.0.7rc1:
19421 - Make it build on Win32 again.
19422 o Changes from 0.0.6.2:
19423 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19427 Changes in version 0.0.7rc1 - 2004-06-02
19429 - On sighup, we were adding another log without removing the first
19430 one. So log messages would get duplicated n times for n sighups.
19431 - Several cases of using a connection after we'd freed it. The
19432 problem was that connections that are pending resolve are in both
19433 the pending_resolve tree, and also the circuit's resolving_streams
19434 list. When you want to remove one, you must remove it from both.
19435 - Fix a double-mark-for-close where an end cell arrived for a
19436 resolving stream, and then the resolve failed.
19437 - Check directory signatures based on name of signer, not on whom
19438 we got the directory from. This will let us cache directories more
19441 - Crank up some of our constants to handle more users.
19444 Changes in version 0.0.7pre1 - 2004-06-02
19445 o Fixes for crashes and other obnoxious bugs:
19446 - Fix an epipe bug: sometimes when directory connections failed
19447 to connect, we would give them a chance to flush before closing
19449 - When we detached from a circuit because of resolvefailed, we
19450 would immediately try the same circuit twice more, and then
19451 give up on the resolve thinking we'd tried three different
19453 - Limit the number of intro circuits we'll attempt to build for a
19454 hidden service per 15-minute period.
19455 - Check recommended-software string *early*, before actually parsing
19456 the directory. Thus we can detect an obsolete version and exit,
19457 even if the new directory format doesn't parse.
19458 o Fixes for security bugs:
19459 - Remember which nodes are dirservers when you startup, and if a
19460 random OR enables his dirport, don't automatically assume he's
19461 a trusted dirserver.
19463 - Directory connections were asking the wrong poll socket to
19464 start writing, and not asking themselves to start writing.
19465 - When we detached from a circuit because we sent a begin but
19466 didn't get a connected, we would use it again the first time;
19467 but after that we would correctly switch to a different one.
19468 - Stop warning when the first onion decrypt attempt fails; they
19469 will sometimes legitimately fail now that we rotate keys.
19470 - Override unaligned-access-ok check when $host_cpu is ia64 or
19471 arm. Apparently they allow it but the kernel whines.
19472 - Dirservers try to reconnect periodically too, in case connections
19474 - Fix some memory leaks in directory servers.
19475 - Allow backslash in Win32 filenames.
19476 - Made Tor build complain-free on FreeBSD, hopefully without
19477 breaking other BSD builds. We'll see.
19479 - Doxygen markup on all functions and global variables.
19480 - Make directory functions update routerlist, not replace it. So
19481 now directory disagreements are not so critical a problem.
19482 - Remove the upper limit on number of descriptors in a dirserver's
19483 directory (not that we were anywhere close).
19484 - Allow multiple logfiles at different severity ranges.
19485 - Allow *BindAddress to specify ":port" rather than setting *Port
19486 separately. Allow multiple instances of each BindAddress config
19487 option, so you can bind to multiple interfaces if you want.
19488 - Allow multiple exit policy lines, which are processed in order.
19489 Now we don't need that huge line with all the commas in it.
19490 - Enable accept/reject policies on SOCKS connections, so you can bind
19491 to 0.0.0.0 but still control who can use your OP.
19494 Changes in version 0.0.6.2 - 2004-05-16
19495 o Our integrity-checking digest was checking only the most recent cell,
19496 not the previous cells like we'd thought.
19497 Thanks to Stefan Mark for finding the flaw!
19500 Changes in version 0.0.6.1 - 2004-05-06
19501 o Fix two bugs in our AES counter-mode implementation (this affected
19502 onion-level stream encryption, but not TLS-level). It turns
19503 out we were doing something much more akin to a 16-character
19504 polyalphabetic cipher. Oops.
19505 Thanks to Stefan Mark for finding the flaw!
19506 o Retire moria3 as a directory server, and add tor26 as a directory
19510 Changes in version 0.0.6 - 2004-05-02
19511 [version bump only]
19514 Changes in version 0.0.6rc4 - 2004-05-01
19515 o Update the built-in dirservers list to use the new directory format
19516 o Fix a rare seg fault: if a node offering a hidden service attempts
19517 to build a circuit to Alice's rendezvous point and fails before it
19518 reaches the last hop, it retries with a different circuit, but
19520 o Handle windows socket errors correctly.
19523 Changes in version 0.0.6rc3 - 2004-04-28
19524 o Don't expire non-general excess circuits (if we had enough
19525 circuits open, we were expiring rendezvous circuits -- even
19526 when they had a stream attached. oops.)
19527 o Fetch randomness from /dev/urandom better (not via fopen/fread)
19528 o Better debugging for tls errors
19529 o Some versions of openssl have an SSL_pending function that erroneously
19530 returns bytes when there is a non-application record pending.
19531 o Set Content-Type on the directory and hidserv descriptor.
19532 o Remove IVs from cipher code, since AES-ctr has none.
19533 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19534 o We were using an array of length zero in a few places.
19535 o win32's gethostbyname can't resolve an IP to an IP.
19536 o win32's close can't close a socket.
19539 Changes in version 0.0.6rc2 - 2004-04-26
19540 o Fix a bug where we were closing tls connections intermittently.
19541 It turns out openssl keeps its errors around -- so if an error
19542 happens, and you don't ask about it, and then another openssl
19543 operation happens and succeeds, and you ask if there was an error,
19544 it tells you about the first error. Fun fun.
19545 o Fix a bug that's been lurking since 27 may 03 (!)
19546 When passing back a destroy cell, we would use the wrong circ id.
19547 'Mostly harmless', but still worth fixing.
19548 o Since we don't support truncateds much, don't bother sending them;
19549 just close the circ.
19550 o check for <machine/limits.h> so we build on NetBSD again (I hope).
19551 o don't crash if a conn that sent a begin has suddenly lost its circuit
19552 (this was quite rare).
19555 Changes in version 0.0.6rc1 - 2004-04-25
19556 o We now rotate link (tls context) keys and onion keys.
19557 o CREATE cells now include oaep padding, so you can tell
19558 if you decrypted them correctly.
19559 o Add bandwidthburst to server descriptor.
19560 o Directories now say which dirserver signed them.
19561 o Use a tor_assert macro that logs failed assertions too.
19564 Changes in version 0.0.6pre5 - 2004-04-18
19565 o changes from 0.0.6pre4:
19566 - make tor build on broken freebsd 5.2 installs
19567 - fix a failed assert when you try an intro point, get a nack, and try
19568 a second one and it works.
19569 - when alice uses a port that the hidden service doesn't accept,
19570 it now sends back an end cell (denied by exit policy). otherwise
19571 alice would just have to wait to time out.
19572 - fix another rare bug: when we had tried all the intro
19573 points for a hidden service, we fetched the descriptor
19574 again, but we left our introcirc thinking it had already
19575 sent an intro, so it kept waiting for a response...
19576 - bugfix: when you sleep your hidden-service laptop, as soon
19577 as it wakes up it tries to upload a service descriptor, but
19578 socketpair fails for some reason (localhost not up yet?).
19579 now we simply give up on that upload, and we'll try again later.
19580 i'd still like to find the bug though.
19581 - if an intro circ waiting for an ack dies before getting one, then
19583 - we were reusing stale service descriptors and refetching usable
19587 Changes in version 0.0.6pre4 - 2004-04-14
19588 o changes from 0.0.6pre3:
19589 - when bob fails to connect to the rendezvous point, and his
19590 circ didn't fail because of the rendezvous point itself, then
19591 he retries a couple of times
19592 - we expire introduction and rendezvous circs more thoroughly
19593 (sometimes they were hanging around forever)
19594 - we expire unattached rendezvous streams that have been around
19595 too long (they were sticking around forever).
19596 - fix a measly fencepost error that was crashing everybody with
19600 Changes in version 0.0.6pre3 - 2004-04-14
19601 o changes from 0.0.6pre2:
19602 - make hup work again
19603 - fix some memory leaks for dirservers
19604 - allow more skew in rendezvous descriptor timestamps, to help
19605 handle people like blanu who don't know what time it is
19606 - normal circs are 3 hops, but some rend/intro circs are 4, if
19607 the initiator doesn't get to choose the last hop
19608 - send acks for introductions, so alice can know whether to try
19610 - bob publishes intro points more correctly
19611 o changes from 0.0.5:
19612 - fix an assert trigger that's been plaguing us since the days
19613 of 0.0.2prexx (thanks weasel!)
19614 - retry stream correctly when we fail to connect because of
19615 exit-policy-reject (should try another) or can't-resolve-address
19616 (also should try another, because dns on random internet servers
19618 - when we hup a dirserver and we've *removed* a server from the
19619 approved-routers list, now we remove that server from the
19620 in-memory directories too
19623 Changes in version 0.0.6pre2 - 2004-04-08
19624 o We fixed our base32 implementation. Now it works on all architectures.
19627 Changes in version 0.0.6pre1 - 2004-04-08
19629 - Hidden services and rendezvous points are implemented. Go to
19630 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19631 hidden services. (This only works via a socks4a proxy such as
19632 Privoxy, and currently it's quite slow.)
19635 Changes in version 0.0.5 - 2004-03-30
19636 [version bump only]
19639 Changes in version 0.0.5rc3 - 2004-03-29
19640 o Install torrc as torrc.sample -- we no longer clobber your
19642 o Re-enable recommendedversion checking (we broke it in rc2, oops)
19643 o Add in a 'notice' log level for things the operator should hear
19644 but that aren't warnings
19647 Changes in version 0.0.5rc2 - 2004-03-29
19648 o Hold socks connection open until reply is flushed (if possible)
19649 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19650 the dns farm to do it.
19651 o Fix c99 aliasing warnings in rephist.c
19652 o Don't include server descriptors that are older than 24 hours in the
19654 o Give socks 'reject' replies their whole 15s to attempt to flush,
19655 rather than seeing the 60s timeout and assuming the flush had failed.
19656 o Clean automake droppings from the cvs repository
19659 Changes in version 0.0.5rc1 - 2004-03-28
19660 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19661 o Only build circuits after we've fetched the directory: clients were
19662 using only the directory servers before they'd fetched a directory.
19663 This also means longer startup time; so it goes.
19664 o Fix an assert trigger where an OP would fail to handshake, and we'd
19665 expect it to have a nickname.
19666 o Work around a tsocks bug: do a socks reject when AP connection dies
19667 early, else tsocks goes into an infinite loop.
19670 Changes in version 0.0.4 - 2004-03-26
19671 o When connecting to a dirserver or OR and the network is down,
19675 Changes in version 0.0.3 - 2004-03-26
19676 o Warn and fail if server chose a nickname with illegal characters
19677 o Port to Solaris and Sparc:
19678 - include missing header fcntl.h
19679 - have autoconf find -lsocket -lnsl automatically
19680 - deal with hardware word alignment
19681 - make uname() work (solaris has a different return convention)
19682 - switch from using signal() to sigaction()
19683 o Preliminary work on reputation system:
19684 - Keep statistics on success/fail of connect attempts; they're published
19685 by kill -USR1 currently.
19686 - Add a RunTesting option to try to learn link state by creating test
19687 circuits, even when SocksPort is off.
19688 - Remove unused open circuits when there are too many.
19691 Changes in version 0.0.2 - 2004-03-19
19692 - Include strlcpy and strlcat for safer string ops
19693 - define INADDR_NONE so we compile (but still not run) on solaris
19696 Changes in version 0.0.2pre27 - 2004-03-14
19698 - Allow internal tor networks (we were rejecting internal IPs,
19699 now we allow them if they're set explicitly).
19700 - And fix a few endian issues.
19703 Changes in version 0.0.2pre26 - 2004-03-14
19705 - If a stream times out after 15s without a connected cell, don't
19706 try that circuit again: try a new one.
19707 - Retry streams at most 4 times. Then give up.
19708 - When a dirserver gets a descriptor from an unknown router, it
19709 logs its fingerprint (so the dirserver operator can choose to
19710 accept it even without mail from the server operator).
19711 - Inform unapproved servers when we reject their descriptors.
19712 - Make tor build on Windows again. It works as a client, who knows
19714 - Clearer instructions in the torrc for how to set up a server.
19715 - Be more efficient about reading fd's when our global token bucket
19716 (used for rate limiting) becomes empty.
19718 - Stop asserting that computers always go forward in time. It's
19720 - When we sent a cell (e.g. destroy) and then marked an OR connection
19721 expired, we might close it before finishing a flush if the other
19722 side isn't reading right then.
19723 - Don't allow dirservers to start if they haven't defined
19724 RecommendedVersions
19725 - We were caching transient dns failures. Oops.
19726 - Prevent servers from publishing an internal IP as their address.
19727 - Address a strcat vulnerability in circuit.c
19730 Changes in version 0.0.2pre25 - 2004-03-04
19732 - Put the OR's IP in its router descriptor, not its fqdn. That way
19733 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19736 - If the user typed in an address that didn't resolve, the server
19740 Changes in version 0.0.2pre24 - 2004-03-03
19742 - Fix an assertion failure in dns.c, where we were trying to dequeue
19743 a pending dns resolve even if it wasn't pending
19744 - Fix a spurious socks5 warning about still trying to write after the
19745 connection is finished.
19746 - Hold certain marked_for_close connections open until they're finished
19747 flushing, rather than losing bytes by closing them too early.
19748 - Correctly report the reason for ending a stream
19749 - Remove some duplicate calls to connection_mark_for_close
19750 - Put switch_id and start_daemon earlier in the boot sequence, so it
19751 will actually try to chdir() to options.DataDirectory
19752 - Make 'make test' exit(1) if a test fails; fix some unit tests
19753 - Make tor fail when you use a config option it doesn't know about,
19754 rather than warn and continue.
19755 - Make --version work
19756 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19759 Changes in version 0.0.2pre23 - 2004-02-29
19761 - Print a statement when the first circ is finished, so the user
19762 knows it's working.
19763 - If a relay cell is unrecognized at the end of the circuit,
19764 send back a destroy. (So attacks to mutate cells are more
19766 - New config option 'excludenodes' to avoid certain nodes for circuits.
19767 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19768 so you can collect coredumps there.
19770 - Fix a bug in tls flushing where sometimes data got wedged and
19771 didn't flush until more data got sent. Hopefully this bug was
19772 a big factor in the random delays we were seeing.
19773 - Make 'connected' cells include the resolved IP, so the client
19774 dns cache actually gets populated.
19775 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19776 - When we time-out on a stream and detach from the circuit, send an
19777 end cell down it first.
19778 - Only warn about an unknown router (in exitnodes, entrynodes,
19779 excludenodes) after we've fetched a directory.
19782 Changes in version 0.0.2pre22 - 2004-02-26
19784 - Servers publish less revealing uname information in descriptors.
19785 - More memory tracking and assertions, to crash more usefully when
19787 - If the default torrc isn't there, just use some default defaults.
19788 Plus provide an internal dirservers file if they don't have one.
19789 - When the user tries to use Tor as an http proxy, give them an http
19790 501 failure explaining that we're a socks proxy.
19791 - Dump a new router.desc on hup, to help confused people who change
19792 their exit policies and then wonder why router.desc doesn't reflect
19794 - Clean up the generic tor.sh init script that we ship with.
19796 - If the exit stream is pending on the resolve, and a destroy arrives,
19797 then the stream wasn't getting removed from the pending list. I
19798 think this was the one causing recent server crashes.
19799 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19800 - When it couldn't resolve any dirservers, it was useless from then on.
19801 Now it reloads the RouterFile (or default dirservers) if it has no
19803 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19804 many users don't even *have* a /usr/local/sbin/.
19807 Changes in version 0.0.2pre21 - 2004-02-18
19809 - There's a ChangeLog file that actually reflects the changelog.
19810 - There's a 'torify' wrapper script, with an accompanying
19811 tor-tsocks.conf, that simplifies the process of using tsocks for
19812 tor. It even has a man page.
19813 - The tor binary gets installed to sbin rather than bin now.
19814 - Retry streams where the connected cell hasn't arrived in 15 seconds
19815 - Clean up exit policy handling -- get the default out of the torrc,
19816 so we can update it without forcing each server operator to fix
19818 - Allow imaps and pop3s in default exit policy
19820 - Prevent picking middleman nodes as the last node in the circuit
19823 Changes in version 0.0.2pre20 - 2004-01-30
19825 - We now have a deb package, and it's in debian unstable. Go to
19826 it, apt-getters. :)
19827 - I've split the TotalBandwidth option into BandwidthRate (how many
19828 bytes per second you want to allow, long-term) and
19829 BandwidthBurst (how many bytes you will allow at once before the cap
19830 kicks in). This better token bucket approach lets you, say, set
19831 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19832 performance while not exceeding your monthly bandwidth quota.
19833 - Push out a tls record's worth of data once you've got it, rather
19834 than waiting until you've read everything waiting to be read. This
19835 may improve performance by pipelining better. We'll see.
19836 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19837 from failed circuits (if they haven't been connected yet) and attach
19839 - Expire old streams that haven't managed to connect. Some day we'll
19840 have them reattach to new circuits instead.
19843 - Fix several memory leaks that were causing servers to become bloated
19845 - Fix a few very rare assert triggers. A few more remain.
19846 - Setuid to User _before_ complaining about running as root.
19849 Changes in version 0.0.2pre19 - 2004-01-07
19851 - Fix deadlock condition in dns farm. We were telling a child to die by
19852 closing the parent's file descriptor to him. But newer children were
19853 inheriting the open file descriptor from the parent, and since they
19854 weren't closing it, the socket never closed, so the child never read
19855 eof, so he never knew to exit. Similarly, dns workers were holding
19856 open other sockets, leading to all sorts of chaos.
19857 - New cleaner daemon() code for forking and backgrounding.
19858 - If you log to a file, it now prints an entry at the top of the
19859 logfile so you know it's working.
19860 - The onionskin challenge length was 30 bytes longer than necessary.
19861 - Started to patch up the spec so it's not quite so out of date.
19864 Changes in version 0.0.2pre18 - 2004-01-02
19866 - Fix endian issues with the 'integrity' field in the relay header.
19867 - Fix a potential bug where connections in state
19868 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19871 Changes in version 0.0.2pre17 - 2003-12-30
19873 - Made --debuglogfile (or any second log file, actually) work.
19874 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19875 adversary could force us into an infinite loop.
19878 - Each onionskin handshake now includes a hash of the computed key,
19879 to prove the server's identity and help perfect forward secrecy.
19880 - Changed cell size from 256 to 512 bytes (working toward compatibility
19882 - Changed cell length to 2 bytes, and moved it to the relay header.
19883 - Implemented end-to-end integrity checking for the payloads of
19885 - Separated streamid from 'recognized' (otherwise circuits will get
19886 messed up when we try to have streams exit from the middle). We
19887 use the integrity-checking to confirm that a cell is addressed to
19889 - Randomize the initial circid and streamid values, so an adversary who
19890 breaks into a node can't learn how many circuits or streams have
19894 Changes in version 0.0.2pre16 - 2003-12-14
19896 - Fixed a bug that made HUP trigger an assert
19897 - Fixed a bug where a circuit that immediately failed wasn't being
19898 counted as a failed circuit in counting retries.
19901 - Now we close the circuit when we get a truncated cell: otherwise we're
19902 open to an anonymity attack where a bad node in the path truncates
19903 the circuit and then we open streams at him.
19904 - Add port ranges to exit policies
19905 - Add a conservative default exit policy
19906 - Warn if you're running tor as root
19907 - on HUP, retry OR connections and close/rebind listeners
19908 - options.EntryNodes: try these nodes first when picking the first node
19909 - options.ExitNodes: if your best choices happen to include any of
19910 your preferred exit nodes, you choose among just those preferred
19912 - options.ExcludedNodes: nodes that are never picked in path building
19915 Changes in version 0.0.2pre15 - 2003-12-03
19916 o Robustness and bugfixes:
19917 - Sometimes clients would cache incorrect DNS resolves, which would
19918 really screw things up.
19919 - An OP that goes offline would slowly leak all its sockets and stop
19921 - A wide variety of bugfixes in exit node selection, exit policy
19922 handling, and processing pending streams when a new circuit is
19924 - Pick nodes for a path only from those the directory says are up
19925 - Choose randomly from all running dirservers, not always the first one
19926 - Increase allowed http header size for directory fetch.
19927 - Stop writing to stderr (if we're daemonized it will be closed).
19928 - Enable -g always, so cores will be more useful to me.
19929 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19932 - Wrote a man page. It lists commonly used options.
19935 - Change default loglevel to warn.
19936 - Make PidFile default to null rather than littering in your CWD.
19937 - OnionRouter config option is now obsolete. Instead it just checks
19939 - Moved to a single unified torrc file for both clients and servers.
19942 Changes in version 0.0.2pre14 - 2003-11-29
19943 o Robustness and bugfixes:
19944 - Force the admin to make the DataDirectory himself
19945 - to get ownership/permissions right
19946 - so clients no longer make a DataDirectory and then never use it
19947 - fix bug where a client who was offline for 45 minutes would never
19948 pull down a directory again
19949 - fix (or at least hide really well) the dns assert bug that was
19950 causing server crashes
19951 - warnings and improved robustness wrt clockskew for certs
19952 - use the native daemon(3) to daemonize, when available
19953 - exit if bind() fails
19954 - exit if neither socksport nor orport is defined
19955 - include our own tor_timegm (Win32 doesn't have its own)
19956 - bugfix for win32 with lots of connections
19957 - fix minor bias in PRNG
19958 - make dirserver more robust to corrupt cached directory
19961 - Wrote the design document (woo)
19963 o Circuit building and exit policies:
19964 - Circuits no longer try to use nodes that the directory has told them
19966 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19967 bitcounts (18.0.0.0/8).
19968 - Make AP connections standby for a circuit if no suitable circuit
19969 exists, rather than failing
19970 - Circuits choose exit node based on addr/port, exit policies, and
19971 which AP connections are standing by
19972 - Bump min pathlen from 2 to 3
19973 - Relay end cells have a payload to describe why the stream ended.
19974 - If the stream failed because of exit policy, try again with a new
19976 - Clients have a dns cache to remember resolved addresses.
19977 - Notice more quickly when we have no working circuits
19980 - APPort is now called SocksPort
19981 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19983 - RecommendedVersions is now a config variable rather than
19984 hardcoded (for dirservers)
19985 - Reloads config on HUP
19986 - Usage info on -h or --help
19987 - If you set User and Group config vars, it'll setu/gid to them.
19990 Changes in version 0.0.2pre13 - 2003-10-19
19991 o General stability:
19992 - SSL_write no longer fails when it returns WANTWRITE and the number
19993 of bytes in the buf has changed by the next SSL_write call.
19994 - Fix segfault fetching directory when network is down
19995 - Fix a variety of minor memory leaks
19996 - Dirservers reload the fingerprints file on HUP, so I don't have
19997 to take down the network when I approve a new router
19998 - Default server config file has explicit Address line to specify fqdn
20001 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
20002 - Make listener connections not ever alloc bufs
20004 o Autoconf improvements:
20005 - don't clobber an external CFLAGS in ./configure
20006 - Make install now works
20007 - create var/lib/tor on make install
20008 - autocreate a tor.sh initscript to help distribs
20009 - autocreate the torrc and sample-server-torrc with correct paths
20011 o Log files and Daemonizing now work:
20012 - If --DebugLogFile is specified, log to it at -l debug
20013 - If --LogFile is specified, use it instead of commandline
20014 - If --RunAsDaemon is set, tor forks and backgrounds on startup