1 Changes in version 0.2.8.2-alpha - 2016-03-??
2 Tor 0.2.8.2-alpha is the second alpha in its series. XXXX write more
5 o New system requirements:
6 - Tor no longer supports versions of OpenSSL with a broken
7 implementation of counter mode. (This bug was present in OpenSSL
8 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
9 longer runs with, these versions.
10 - Tor no longer attempts to support platforms where the "time_t"
11 type is unsigned. (To the best of our knowledge, only OpenVMS does
12 this, and Tor has never actually built on OpenVMS.) Closes
15 o Major bugfixes (security, pointers):
16 - Avoid a difficult-to-trigger heap corruption attack when extending
17 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
18 bugfix on Tor 0.1.1.11-alpha, which fixed a related bug
19 incompletely. Reported by Guido Vranken.
21 o Major bugfixes (bridges, pluggable transports):
22 - Modify the check for OR connections to private addresses. Allow
23 bridges on private addresses, including pluggable transports that
24 ignore the (potentially private) address in the bridge line. Fixes
25 bug 18517; bugfix on 0.2.8.1-alpha. Reported by "gk", patch
28 o Major bugfixes (compilation):
29 - Repair hardened builds under the clang compiler. Previously, our
30 use of _FORTIFY_SOURCE would conflict with clang's address
31 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
33 o Major bugfixes (crash on shutdown):
34 - Correctly handle detaching circuits from cmuxes when doing
35 circuit_free_all() on shutdown. Fixes bug 18116; bugfix
38 o Major bugfixes (dns proxy mode, crash):
39 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
40 bugfix on 0.2.0.1-alpha. Patch from 'cypherpunks'.
42 o Major bugfixes (relays, bridge clients):
43 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
44 bridge clients use the address configured in the bridge line.
45 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
48 o Major bugfixes (voting):
49 - Actually enable Ed25519-based directory collation. Previously, the
50 code had been written, but some debugging code that had
51 accidentally been left in the codebase made it stay turned off.
52 Fixes bug 17702; bugfix on 0.2.7.2-alpha.
53 - When collating votes by Ed25519 identities, authorities now
54 include a "NoEdConsensus" flag if the ed25519 value (or lack
55 thereof) for a server does not reflect the majority consensus.
56 Related to bug 17668; bugfix on 0.2.7.2-alpha.
57 - When generating a vote with keypinning disabled, never include two
58 entries for the same ed25519 identity. This bug was causing
59 authorities to generate votes that they could not parse when a
60 router violated key pinning by changing its RSA identity but
61 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
62 18318. Bugfix on 0.2.7.2-alpha.
64 o Minor feature (IPv6):
65 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
66 to 1, tor prefers IPv6 directory addresses.
67 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
68 avoids using IPv4 for client OR and directory connections.
69 - Try harder to fulfil IP version restrictions ClientUseIPv4 0 and
70 ClientUseIPv6 0; and the preferences ClientPreferIPv6ORPort and
71 ClientPreferIPv6DirPort. Closes ticket 17840; patch by "teor".
73 o Minor features (bug-resistance):
74 - Make Tor survive errors involving connections without a
75 corresponding event object. Previously we'd fail with an
76 assertion; now we produce a log message. Related to bug 16248.
78 o Minor features (build):
79 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
80 as having possible IPfW support. Closes ticket 18448. Patch from
83 o Minor features (code hardening):
84 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
85 level code, to harden against accidental failures to NUL-
86 terminate. Part of ticket 17852. Patch from 'jsturgix'. Found
89 o Minor features (compilation):
90 - Note our minimum required autoconf/automake versions in the
91 appropriate locations. Closes ticket 17732.
93 o Minor features (crypto):
94 - Fix a segfault during startup: If unix socket was configured as
95 listener (such as a ControlSocket or a SocksPort unix socket), and
96 tor was started as root but not configured to switch to another
97 user, tor would segfault while trying to string compare a NULL
98 value. Fixes bug 18261; bugfix on 0.2.8.1-alpha. Patch by weasel.
99 - Validate the Diffie-Hellman hard coded parameters and ensure that
100 p is a safe prime, and g is suitable. Closes ticket 18221.
102 o Minor features (geoip):
103 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
106 o Minor features (linux seccomp2 sandbox):
107 - Detect and reject attempts to change our Address with "Sandbox 1"
108 enabled. Changing Address with Sandbox turned on would never
109 actually work, but previously it would fail in strange and
110 confusing ways. Found while fixing 18548.
112 o Minor features (robustness):
113 - Exit immediately with an error message if the code attempts to use
114 libevent without having initialized it. This should resolve some
115 frequently-made mistakes in our unit tests. Closes ticket 18241.
117 o Minor features (unix domain sockets):
118 - Since some operating systems do not consider the actual modes on a
119 UNIX domain socket itself, tor does not allow creating such a
120 socket in a directory that is group or world accessible if it is
121 supposed to be private. Likewise, it will not allow only group
122 accessible sockets in a world accessible directory. However, on
123 some operating systems this is unnecessary, so add a per-socket
124 option called RelaxDirModeCheck. Closes ticket 18458. Patch
127 o Minor bugfixes (exit policies, security):
128 - Refresh an exit relay's exit policy when interface addresses
129 change. Previously, tor only refreshed the exit policy when the
130 configured external address changed. Fixes bug 18208; bugfix on
131 tor 0.2.7.3. Patch by "teor".
133 o Minor bugfixes (security, hidden services):
134 - Prevent hidden services connecting to client-supplied rendezvous
135 addresses that are reserved as internal or multicast. Fixes bug
136 8976; bugfix on b7c172c9e in tor-0.2.3.21. Patch by "dgoulet"
139 o Minor bugfixes (security, win32):
140 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
141 attack. Fixes bug 18123; bugfix on all tor versions. Patch
145 - Bridges now refuse "rendezvous2" (hidden service descriptor)
146 publish attempts. Suggested by ticket 18332.
148 o Minor bugfixes (build):
149 - Do not link the unit tests against both the testing and non-
150 testing versions of the static libraries. Fixes bug 18490; bugfix
153 o Minor bugfixes (client):
154 - Count receipt of new microdescriptors as progress towards
155 bootstrapping. Now, when a user who has set EntryNodes finishes
156 bootstrapping, Tor automatically repopulates the guard set based
157 on this new directory information. Fixes bug 16825; bugfix
160 o Minor bugfixes (code correctness):
161 - Update to the latest version of Trunnel, which tries harder to
162 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
163 by clang address sanitizer. Fixes bug 18373; bugfix
166 o Minor bugfixes (configuration):
167 - Fix a tiny memory leak when parsing a port configuration ending in
168 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
170 o Minor bugfixes (containers):
171 - If we somehow attempt to construct a heap with more than
172 1073741822 elements, avoid an integer overflow when maintaining
173 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
175 o Minor bugfixes (correctness):
176 - Fix a bad memory handling bug that would occur if we had queued a
177 cell on a channel's incoming queue. Fortunately, we can't actually
178 queue a cell like that as our code is constructed today, but it's
179 best to avoid this kind of error, even if there isn't any code
180 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
182 o Minor bugfixes (crypto, static analysis):
183 - Silence spurious clang-scan warnings in the ed25519_donna code by
184 explicitly initialising some objects. Fixes bug 18384; bugfix on
185 0f3eeca9 in 0.2.7.2-alpha. Patch by "teor".
187 o Minor bugfixes (directory):
188 - When generating a URL for a directory server on an IPv6 address,
189 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
190 on 0.2.3.9-alpha. Patch from Malek.
192 o Minor bugfixes (fallback directory mirrors):
193 - When requesting extrainfo descriptors from a trusted directory
194 server, check whether it is an authority or a fallback directory
195 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
196 0.2.4.7-alpha. Reported by "atagar", patch by "teor".
198 o Minor bugfixes (hidden service client):
199 - Seven very fast consecutive requests to the same .onion address
200 triggers 7 descriptor fetches. The first six each pick a directory
201 (there are 6 overall) and the seventh one wasn't able to pick one
202 which was triggering a close on all current directory connections.
203 It has been fixed by not closing them if we have pending directory
204 fetch. Fixes bug 15937; bugfix on tor-0.2.7.1-alpha.
206 o Minor bugfixes (hidden service, control port):
207 - Add the onion address to the HS_DESC event for the UPLOADED action
208 both on success or failure. It was previously hardcoded with
209 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
211 o Minor bugfixes (linux seccomp2 sandbox):
212 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
213 enabled and no DNS resolvers configured. This should help TAILS
214 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
215 - Fix the sandbox's interoprability with unix sockets under setuid.
216 Fixes bug 18253; bugfix on 0.2.8.1-alpha.
217 - Allow the setrlimit syscall, and the prlimit and prlimit64
218 syscalls, which some libc implementations use under the hood.
219 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
221 o Minor bugfixes (logging):
222 - When logging information about an unparseable networkstatus vote
223 or consensus, do not say "vote" when we mean consensus. Fixes bug
224 18368; bugfix on 0.2.0.8-alpha.
225 - Scrub service in from "unrecognized service ID" log messages.
226 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
227 - Downgrade logs and backtraces about IP versions to info-level.
228 Only log backtraces once each time tor runs. Assists in diagnosing
229 bug 18351; bugfix on 0.2.8.1-alpha. Reported by "sysrqb" and
230 "Christian", patch by "teor".
232 o Minor bugfixes (memory safety):
233 - Avoid freeing an uninitialised pointer when opening a socket fails
234 in get_interface_addresses_ioctl. Fixes bug 18454; bugfix on
235 9f06ec0c in tor-0.2.3.11-alpha. Reported by "toralf" and
236 "cypherpunks", patch by "teor".
237 - Correctly duplicate addresses in get_interface_address6_list.
238 Fixes bug 18454; bugfix on 110765f5 in tor-0.2.8.1-alpha. Reported
239 by "toralf", patch by "cypherpunks".
241 o Minor bugfixes (private directory):
242 - Prevent a race condition when creating private directories. Fixes
243 part of bug 17852; bugfix on 0.2pre13. Part of ticket 17852. Patch
244 from 'jsturgix'. Found with Flawfinder.
246 o Minor bugfixes (test networks, IPv6):
247 - Allow internal IPv6 addresses in descriptors in test networks.
248 Fixes bug 17153; bugfix on 6b4af1071 in 0.2.3.16-alpha. Patch by
249 "teor", reported by "karsten".
251 o Minor bugfixes (testing):
252 - We no longer disable assertions in the unit tests when coverage is
253 enabled. Instead, we require you to say --disable-asserts-in-tests
254 to the configure script if you need assertions disabled in the
255 unit tests (for example, if you want to perform branch coverage).
256 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
258 o Minor bugfixes (time parsing):
259 - Avoid overflow in tor_timegm when parsing dates in and after 2038
260 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
261 0.0.2pre14. Patch by "teor".
263 o Minor bugfixes (tor-gencert):
264 - Correctly handle the case where an authority operator enters a
265 passphrase but sends an EOF before sending a newline. Fixes bug
266 17443; bugfix on 0.2.0.20-rc. Found by "junglefowl".
268 o Code simplification and refactoring:
269 - Quote all the string interpolations in configure.ac -- even those
270 which we are pretty sure can't contain spaces. Closes ticket
271 17744. Patch from "zerosion".
272 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
273 inplace, so there's no need to have a separate implementation for
274 the non-inplace code. Closes ticket 18258. Patch from Malek.
275 - Simplify return types for some crypto functions that can't
276 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
278 o Dependency updates:
279 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
280 later (released in 2008 and 2009 respectively). If you are
281 building Tor from the git repository instead of from the source
282 distribution, and your tools are older than this, you will need to
283 upgrade. Closes ticket 17732.
286 - Change build messages to refer to "Fedora" instead of "Fedora
287 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
288 Patches from "icanhasaccount" and "cypherpunks".
291 - Streamline relay-side hsdir handling: when relays consider whether
292 to accept an uploaded hidden service descriptor, they no longer
293 check whether they are one of the relays in the network that is
294 "supposed" to handle that descriptor. Implements ticket 18332.
295 - We no longer maintain an internal freelist in memarea.c.
296 Allocators should be good enough to make this code unnecessary,
297 and it's doubtful that it ever had any performance benefit.
300 - Fix several warnings from clang's address sanitizer produced in
302 - Treat backtrace test failures as expected on FreeBSD until we
303 solve bug 17808. Closes ticket 18204.
306 Changes in version 0.2.8.1-alpha - 2016-02-04
307 Tor 0.2.8.1-alpha is the first alpha release in its series. It
308 includes numerous small features and bugfixes against previous Tor
309 versions, and numerous small infrastructure improvements. The most
310 notable features are a set of improvements to the directory subsystem.
312 o Major features (security, Linux):
313 - When Tor starts as root on Linux and is told to switch user ID, it
314 can now retain the capability to bind to low ports. By default,
315 Tor will do this only when it's switching user ID and some low
316 ports have been configured. You can change this behavior with the
317 new option KeepBindCapabilities. Closes ticket 8195.
319 o Major features (directory system):
320 - When bootstrapping multiple consensus downloads at a time, use the
321 first one that starts downloading, and close the rest. This
322 reduces failures when authorities or fallback directories are slow
323 or down. Together with the code for feature 15775, this feature
324 should reduces failures due to fallback churn. Implements ticket
325 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
326 "mikeperry" and "teor".
327 - Include a trial list of default fallback directories, based on an
328 opt-in survey of suitable relays. Doing this should make clients
329 bootstrap more quickly and reliably, and reduce the load on the
330 directory authorities. Closes ticket 15775. Patch by "teor".
331 Candidates identified using an OnionOO script by "weasel", "teor",
332 "gsathya", and "karsten".
333 - Previously only relays that explicitly opened a directory port
334 (DirPort) accepted directory requests from clients. Now all
335 relays, with and without a DirPort, accept and serve tunneled
336 directory requests that they receive through their ORPort. You can
337 disable this behavior using the new DirCache option. Closes
341 - Update the V3 identity key for the dannenberg directory authority:
342 it was changed on 18 November 2015. Closes task 17906. Patch
345 o Minor features (security, clock):
346 - Warn when the system clock appears to move back in time (when the
347 state file was last written in the future). Tor doesn't know that
348 consensuses have expired if the clock is in the past. Patch by
349 "teor". Implements ticket 17188.
351 o Minor features (security, exit policies):
352 - ExitPolicyRejectPrivate now rejects more private addresses by
353 default. Specifically, it now rejects the relay's outbound bind
354 addresses (if configured), and the relay's configured port
355 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
356 0.2.0.11-alpha. Patch by "teor".
358 o Minor features (security, memory erasure):
359 - Set the unused entries in a smartlist to NULL. This helped catch
360 a (harmless) bug, and shouldn't affect performance too much.
361 Implements ticket 17026.
362 - Use SecureMemoryWipe() function to securely clean memory on
363 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
364 Implements feature 17986.
365 - Use explicit_bzero or memset_s when present. Previously, we'd use
366 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
367 from <logan@hackers.mu> and <selven@hackers.mu>.
368 - Make memwipe() do nothing when passed a NULL pointer or buffer of
369 zero size. Check size argument to memwipe() for underflow. Fixes
370 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
373 o Minor features (security, RNG):
374 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
375 positively are not allowed to fail. Previously we depended on
376 internal details of OpenSSL's behavior. Closes ticket 17686.
377 - Never use the system entropy output directly for anything besides
378 seeding the PRNG. When we want to generate important keys, instead
379 of using system entropy directly, we now hash it with the PRNG
380 stream. This may help resist certain attacks based on broken OS
381 entropy implementations. Closes part of ticket 17694.
382 - Use modern system calls (like getentropy() or getrandom()) to
383 generate strong entropy on platforms that have them. Closes
386 o Minor features (accounting):
387 - Added two modes to the AccountingRule option: One for limiting
388 only the number of bytes sent ("AccountingRule out"), and one for
389 limiting only the number of bytes received ("AccountingRule in").
390 Closes ticket 15989; patch from "unixninja92".
392 o Minor features (build):
393 - Since our build process now uses "make distcheck", we no longer
394 force "make dist" to depend on "make check". Closes ticket 17893;
395 patch from "cypherpunks."
396 - Tor now builds successfully with the recent OpenSSL 1.1
397 development branch, and with the latest LibreSSL. Closes tickets
398 17549, 17921, and 17984.
400 o Minor features (controller):
401 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
402 tickets 16774 and 17817. Patch by George Tankersley.
403 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
404 service descriptor from a service's local hidden service
405 descriptor cache. Closes ticket 14846.
406 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
407 controllers can examine the the reject rules added by
408 ExitPolicyRejectPrivate. This makes it easier for stem to display
411 o Minor features (crypto):
412 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
414 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
415 - When allocating a digest state object, allocate no more space than
416 we actually need. Previously, we would allocate as much space as
417 the state for the largest algorithm would need. This change saves
418 up to 672 bytes per circuit. Closes ticket 17796.
419 - Improve performance when hashing non-multiple of 8 sized buffers,
420 based on Andrew Moon's public domain SipHash-2-4 implementation.
421 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
423 o Minor features (directory downloads):
424 - Wait for busy authorities and fallback directories to become non-
425 busy when bootstrapping. (A similar change was made in 6c443e987d
426 for directory caches chosen from the consensus.) Closes ticket
427 17864; patch by "teor".
428 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
429 directory mirrors. The default is 1; set it to 0 to disable
430 fallbacks. Implements ticket 17576. Patch by "teor".
432 o Minor features (geoip):
433 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
436 o Minor features (IPv6):
437 - Add an argument 'ipv6=address:orport' to the DirAuthority and
438 FallbackDir torrc options, to specify an IPv6 address for an
439 authority or fallback directory. Add hard-coded ipv6 addresses for
440 directory authorities that have them. Closes ticket 17327; patch
441 from Nick Mathewson and "teor".
442 - Add address policy assume_action support for IPv6 addresses.
443 - Limit IPv6 mask bits to 128.
444 - Warn when comparing against an AF_UNSPEC address in a policy, it's
445 almost always a bug. Closes ticket 17863; patch by "teor".
446 - Allow users to configure directory authorities and fallback
447 directory servers with IPv6 addresses and ORPorts. Resolves
449 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
450 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
451 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
452 17638; bugfix on 0.0.2pre8. Patch by "teor".
454 o Minor features (logging):
455 - When logging to syslog, allow a tag to be added to the syslog
456 identity (the string prepended to every log message). The tag can
457 be configured with SyslogIdentityTag and defaults to none. Setting
458 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
461 o Minor features (portability):
462 - Use timingsafe_memcmp() where available. Closes ticket 17944;
463 patch from <logan@hackers.mu>.
465 o Minor features (relay, address discovery):
466 - Add a family argument to get_interface_addresses_raw() and
467 subfunctions to make network interface address interogation more
468 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
469 types of interfaces from the operating system. Resolves
471 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
472 fails to enumerate interface addresses using the platform-specific
473 API, have it rely on the UDP socket fallback technique to try and
474 find out what IP addresses (both IPv4 and IPv6) our machine has.
475 Resolves ticket 17951.
477 o Minor features (replay cache):
478 - The replay cache now uses SHA256 instead of SHA1. Implements
479 feature 8961. Patch by "teor", issue reported by "rransom".
481 o Minor features (unix file permissions):
482 - Defer creation of Unix sockets until after setuid. This avoids
483 needing CAP_CHOWN and CAP_FOWNER when using systemd's
484 CapabilityBoundingSet, or chown and fowner when using SELinux.
485 Implements part of ticket 17562. Patch from Jamie Nguyen.
486 - If any directory created by Tor is marked as group readable, the
487 filesystem group is allowed to be either the default GID or the
488 root user. Allowing root to read the DataDirectory prevents the
489 need for CAP_READ_SEARCH when using systemd's
490 CapabilityBoundingSet, or dac_read_search when using SELinux.
491 Implements part of ticket 17562. Patch from Jamie Nguyen.
492 - Introduce a new DataDirectoryGroupReadable option. If it is set to
493 1, the DataDirectory will be made readable by the default GID.
494 Implements part of ticket 17562. Patch from Jamie Nguyen.
496 o Minor bugfixes (accounting):
497 - The max bandwidth when using 'AccountRule sum' is now correctly
498 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
501 o Minor bugfixes (code correctness):
502 - When closing an entry connection, generate a warning if we should
503 have sent an end cell for it but we haven't. Fixes bug 17876;
504 bugfix on 0.2.3.2-alpha.
505 - Assert that allocated memory held by the reputation code is freed
506 according to its internal counters. Fixes bug 17753; bugfix
507 on tor-0.1.1.1-alpha.
508 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
511 o Minor bugfixes (compilation):
512 - Mark all object files that include micro-revision.i as depending
513 on it, so as to make parallel builds more reliable. Fixes bug
514 17826; bugfix on 0.2.5.1-alpha.
515 - Don't try to use the pthread_condattr_setclock() function unless
516 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
517 17819; bugfix on 0.2.6.3-alpha.
518 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
519 on tor-0.2.5.2-alpha.
520 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
521 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
522 - Fix search for libevent libraries on OpenBSD (and other systems
523 that install libevent 1 and libevent 2 in parallel). Fixes bug
524 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
525 - Isolate environment variables meant for tests from the rest of the
526 build system. Fixes bug 17818; bugfix on tor-0.2.7.3-rc.
527 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
529 - Remove config.log only from make distclean, not from make clean.
530 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
532 o Minor bugfixes (crypto):
533 - Check the return value of HMAC() and assert on failure. Fixes bug
534 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
536 o Minor bugfixes (fallback directories):
537 - Mark fallbacks as "too busy" when they return a 503 response,
538 rather than just marking authorities. Fixes bug 17572; bugfix on
539 0.2.4.7-alpha. Patch by "teor".
541 o Minor bugfixes (IPv6):
542 - Update the limits in max_dl_per_request for IPv6 address length.
543 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
545 o Minor bugfixes (linux seccomp2 sandbox):
546 - Fix a crash when using offline master ed25519 keys with the Linux
547 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-alpha.
549 o Minor bugfixes (logging):
550 - In log messages that include a function name, use __FUNCTION__
551 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
552 with clang __PRETTY_FUNCTION__ has extra information we don't
553 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
555 - Remove needless quotes from a log message about unparseable
556 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
558 o Minor bugfixes (portability):
559 - Remove an #endif from configure.ac so that we correctly detect the
560 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
563 o Minor bugfixes (relays):
564 - Check that both the ORPort and DirPort (if present) are reachable
565 before publishing a relay descriptor. Otherwise, relays publish a
566 descriptor with DirPort 0 when the DirPort reachability test takes
567 longer than the ORPort reachability test. Fixes bug 18050; bugfix
568 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
570 o Minor bugfixes (relays, hidden services):
571 - Refuse connection requests to private OR addresses unless
572 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
573 then refuse to send any cells to a private address. Fixes bugs
574 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
576 o Minor bugfixes (safe logging):
577 - When logging a malformed hostname received through socks4, scrub
578 it if SafeLogging says we should. Fixes bug 17419; bugfix
581 o Minor bugfixes (statistics code):
582 - Consistently check for overflow in round_*_to_next_multiple_of
583 functions, and add unit tests with additional and maximal values.
584 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
585 - Handle edge cases in the laplace functions: avoid division by
586 zero, avoid taking the log of zero, and silence clang type
587 conversion warnings using round and trunc. Add unit tests for edge
588 cases with maximal values. Fixes part of bug 13192; bugfix
591 o Minor bugfixes (testing):
592 - The test for log_heartbeat was incorrectly failing in timezones
593 with non-integer offsets. Instead of comparing the end of the time
594 string against a constant, compare it to the output of
595 format_local_iso_time when given the correct input. Fixes bug
596 18039; bugfix on 0.2.5.4-alpha.
597 - Make unit tests pass on IPv6-only systems, and systems without
598 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
599 bugfix on 0.2.7.3-rc. Patch by "teor".
600 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
602 - Check the full results of SHA256 and SHA512 digests in the unit
603 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
605 o Code simplification and refactoring:
606 - Move logging of redundant policy entries in
607 policies_parse_exit_policy_internal into its own function. Closes
608 ticket 17608; patch from "juce".
609 - Extract the more complicated parts of circuit_mark_for_close()
610 into a new function that we run periodically before circuits are
611 freed. This change removes more than half of the functions
612 currently in the "blob". Closes ticket 17218.
613 - Clean up a little duplicated code in
614 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
616 - Decouple the list of streams waiting to be attached to circuits
617 from the overall connection list. This change makes it possible to
618 attach streams quickly while simplifying Tor's callgraph and
619 avoiding O(N) scans of the entire connection list. Closes
621 - When a direct directory request fails immediately on launch,
622 instead of relaunching that request from inside the code that
623 launches it, instead mark the connection for teardown. This change
624 simplifies Tor's callback and prevents the directory-request
625 launching code from invoking itself recursively. Closes
627 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
628 use them. Closes ticket 17926.
631 - Add a description of the correct use of the '--keygen' command-
632 line option. Closes ticket 17583; based on text by 's7r'.
633 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
634 - Explain actual minima for BandwidthRate. Closes ticket 16382.
635 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
636 - Mention torspec URL in the manpage and point the reader to it
637 whenever we mention a document that belongs in torspce. Fixes
641 - Remove client-side support for connecting to Tor relays running
642 versions of Tor before 0.2.3.6-alpha. These relays didn't support
643 the v3 TLS handshake protocol, and are no longer allowed on the
644 Tor network. Implements the client side of ticket 11150. Based on
645 patches by Tom van der Woerdt.
648 - Add unit tests to check for common RNG failure modes, such as
649 returning all zeroes, identical values, or incrementing values
650 (OpenSSL's rand_predictable feature). Patch by "teor".
651 - Log more information when the backtrace tests fail. Closes ticket
652 17892. Patch from "cypherpunks."
653 - Always test both ed25519 backends, so that we can be sure that our
654 batch-open replacement code works. Part of ticket 16794.
655 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
656 portion of ticket 16831.
657 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
658 util_format.c, directory.c, and options_validate.c. Closes tickets
659 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
661 - Unit tests for directory_handle_command_get. Closes ticket 17004.
662 Patch from Reinaldo de Souza Jr.
665 Changes in version 0.2.7.6 - 2015-12-10
666 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
667 well as a minor bug in hidden service reliability.
669 o Major bugfixes (guard selection):
670 - Actually look at the Guard flag when selecting a new directory
671 guard. When we implemented the directory guard design, we
672 accidentally started treating all relays as if they have the Guard
673 flag during guard selection, leading to weaker anonymity and worse
674 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
677 o Minor features (geoip):
678 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
681 o Minor bugfixes (compilation):
682 - When checking for net/pfvar.h, include netinet/in.h if possible.
683 This fixes transparent proxy detection on OpenBSD. Fixes bug
684 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
685 - Fix a compilation warning with Clang 3.6: Do not check the
686 presence of an address which can never be NULL. Fixes bug 17781.
688 o Minor bugfixes (correctness):
689 - When displaying an IPv6 exit policy, include the mask bits
690 correctly even when the number is greater than 31. Fixes bug
691 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
692 - The wrong list was used when looking up expired intro points in a
693 rend service object, causing what we think could be reachability
694 issues for hidden services, and triggering a BUG log. Fixes bug
695 16702; bugfix on 0.2.7.2-alpha.
696 - Fix undefined behavior in the tor_cert_checksig function. Fixes
697 bug 17722; bugfix on 0.2.7.2-alpha.
700 Changes in version 0.2.7.5 - 2015-11-20
701 The Tor 0.2.7 release series is dedicated to the memory of Tor user
702 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
703 tirelessly to advocate human rights regardless of national borders,
704 and oppose the encroachments of mass surveillance. He opposed national
705 exceptionalism, he brought clarity to legal and policy debates, he
706 understood and predicted the impact of mass surveillance on the world,
707 and he laid the groundwork for resisting it. While serving on the Tor
708 Project's board of directors, he brought us his uncompromising focus
709 on technical excellence in the service of humankind. Caspar was an
710 inimitable force for good and a wonderful friend. He was kind,
711 humorous, generous, gallant, and believed we should protect one
712 another without exception. We honor him here for his ideals, his
713 efforts, and his accomplishments. Please honor his memory with works
714 that would make him proud.
716 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
718 The 0.2.7 series adds a more secure identity key type for relays,
719 improves cryptography performance, resolves several longstanding
720 hidden-service performance issues, improves controller support for
721 hidden services, and includes small bugfixes and performance
722 improvements throughout the program. This release series also includes
723 more tests than before, and significant simplifications to which parts
724 of Tor invoke which others.
726 (This release contains no code changes since 0.2.7.4-rc.)
729 Changes in version 0.2.7.4-rc - 2015-10-21
730 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
731 fixes some important memory leaks, and a scary-looking (but mostly
732 harmless in practice) invalid-read bug. It also has a few small
733 bugfixes, notably fixes for compilation and portability on different
734 platforms. If no further significant bounds are found, the next
735 release will the the official stable release.
737 o Major bugfixes (security, correctness):
738 - Fix an error that could cause us to read 4 bytes before the
739 beginning of an openssl string. This bug could be used to cause
740 Tor to crash on systems with unusual malloc implementations, or
741 systems with unusual hardening installed. Fixes bug 17404; bugfix
744 o Major bugfixes (correctness):
745 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
746 bug 17401; bugfix on 0.2.7.3-rc.
748 o Major bugfixes (memory leaks):
749 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
750 17398; bugfix on 0.2.6.1-alpha.
751 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
752 17402; bugfix on 0.2.7.3-rc.
753 - Fix a memory leak when reading an expired signing key from disk.
754 Fixes bug 17403; bugfix on 0.2.7.2-rc.
756 o Minor features (geoIP):
757 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
760 o Minor bugfixes (compilation):
761 - Repair compilation with the most recent (unreleased, alpha)
762 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
763 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
764 17251; bugfix on 0.2.7.2-alpha.
765 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
766 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
768 o Minor bugfixes (portability):
769 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
770 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
773 o Minor bugfixes (sandbox):
774 - Add the "hidserv-stats" filename to our sandbox filter for the
775 HiddenServiceStatistics option to work properly. Fixes bug 17354;
776 bugfix on tor-0.2.6.2-alpha. Patch from David Goulet.
778 o Minor bugfixes (testing):
779 - Add unit tests for get_interface_address* failure cases. Fixes bug
780 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
781 - Fix breakage when running 'make check' with BSD make. Fixes bug
782 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
783 - Make the get_ifaddrs_* unit tests more tolerant of different
784 network configurations. (Don't assume every test box has an IPv4
785 address, and don't assume every test box has a non-localhost
786 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
787 - Skip backtrace tests when backtrace support is not compiled in.
788 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
792 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
793 - Note that HiddenServicePorts can take a unix domain socket. Closes
797 Changes in version 0.2.7.3-rc - 2015-09-25
798 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
799 contains numerous usability fixes for Ed25519 keys, safeguards against
800 several misconfiguration problems, significant simplifications to
801 Tor's callgraph, and numerous bugfixes and small features.
803 This is the most tested release of Tor to date. The unit tests cover
804 39.40% of the code, and the integration tests (accessible with "make
805 test-full-online", requiring stem and chutney and a network
806 connection) raise the coverage to 64.49%.
808 o Major features (security, hidden services):
809 - Hidden services, if using the EntryNodes option, are required to
810 use more than one EntryNode, in order to avoid a guard discovery
811 attack. (This would only affect people who had configured hidden
812 services and manually specified the EntryNodes option with a
813 single entry-node. The impact was that it would be easy to
814 remotely identify the guard node used by such a hidden service.
815 See ticket for more information.) Fixes ticket 14917.
817 o Major features (Ed25519 keys, keypinning):
818 - The key-pinning option on directory authorities is now advisory-
819 only by default. In a future version, or when the AuthDirPinKeys
820 option is set, pins are enforced again. Disabling key-pinning
821 seemed like a good idea so that we can survive the fallout of any
822 usability problems associated with Ed25519 keys. Closes
825 o Major features (Ed25519 performance):
826 - Improve the speed of Ed25519 operations and Curve25519 keypair
827 generation when built targeting 32 bit x86 platforms with SSE2
828 available. Implements ticket 16535.
829 - Improve the runtime speed of Ed25519 signature verification by
830 using Ed25519-donna's batch verification support. Implements
833 o Major features (performance testing):
834 - The test-network.sh script now supports performance testing.
835 Requires corresponding chutney performance testing changes. Patch
836 by "teor". Closes ticket 14175.
838 o Major features (relay, Ed25519):
839 - Significant usability improvements for Ed25519 key management. Log
840 messages are better, and the code can recover from far more
841 failure conditions. Thanks to "s7r" for reporting and diagnosing
843 - Add a new OfflineMasterKey option to tell Tor never to try loading
844 or generating a secret Ed25519 identity key. You can use this in
845 combination with tor --keygen to manage offline and/or encrypted
846 Ed25519 keys. Implements ticket 16944.
847 - Add a --newpass option to allow changing or removing the
848 passphrase of an encrypted key with tor --keygen. Implements part
850 - On receiving a HUP signal, check to see whether the Ed25519
851 signing key has changed, and reload it if so. Closes ticket 16790.
853 o Major bugfixes (relay, Ed25519):
854 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
855 0.2.7.2-alpha. Reported by "s7r".
856 - Improve handling of expired signing keys with offline master keys.
857 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
859 o Minor features (client-side privacy):
860 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
861 lifespan when IsolateSOCKSAuth and streams with SOCKS
862 authentication are attached to the circuit. This allows
863 applications like TorBrowser to manage circuit lifetime on their
864 own. Implements feature 15482.
865 - When logging malformed hostnames from SOCKS5 requests, respect
866 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
868 o Minor features (compilation):
869 - Give a warning as early as possible when trying to build with an
870 unsupported OpenSSL version. Closes ticket 16901.
871 - Fail during configure if we're trying to build against an OpenSSL
872 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
873 which started requiring ECC.
875 o Minor features (geoip):
876 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
879 o Minor features (hidden services):
880 - Relays need to have the Fast flag to get the HSDir flag. As this
881 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
882 drop. This change should make some attacks against the hidden
883 service directory system harder. Fixes ticket 15963.
884 - Turn on hidden service statistics collection by setting the torrc
885 option HiddenServiceStatistics to "1" by default. (This keeps
886 track only of the fraction of traffic used by hidden services, and
887 the total number of hidden services in existence.) Closes
889 - Client now uses an introduction point failure cache to know when
890 to fetch or keep a descriptor in their cache. Previously, failures
891 were recorded implicitly, but not explicitly remembered. Closes
894 o Minor features (testing, authorities, documentation):
895 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
896 explicitly manage consensus flags in testing networks. Patch by
897 "robgjansen", modified by "teor". Implements part of ticket 14882.
899 o Minor bugfixes (security, exit policies):
900 - ExitPolicyRejectPrivate now also rejects the relay's published
901 IPv6 address (if any), and any publicly routable IPv4 or IPv6
902 addresses on any local interfaces. ticket 17027. Patch by "teor".
903 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
905 o Minor bug fixes (torrc exit policies):
906 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
907 produce IPv6 wildcard addresses. Previously they would produce
908 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
909 of bug 16069; bugfix on 0.2.4.7-alpha.
910 - When parsing torrc ExitPolicies, we now warn for a number of cases
911 where the user's intent is likely to differ from Tor's actual
912 behavior. These include: using an IPv4 address with an accept6 or
913 reject6 line; using "private" on an accept6 or reject6 line; and
914 including any ExitPolicy lines after accept *:* or reject *:*.
915 Related to ticket 16069.
916 - When parsing torrc ExitPolicies, we now issue an info-level
917 message when expanding an "accept/reject *" line to include both
918 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
919 - In each instance above, usage advice is provided to avoid the
920 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
921 16069; bugfix on 0.2.4.7-alpha.
923 o Minor bugfixes (authority):
924 - Don't assign "HSDir" to a router if it isn't Valid and Running.
925 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
926 - Downgrade log messages about Ed25519 key issues if they are in old
927 cached router descriptors. Fixes part of bug 16286; bugfix
929 - When we find an Ed25519 key issue in a cached descriptor, stop
930 saying the descriptor was just "uploaded". Fixes another part of
931 bug 16286; bugfix on 0.2.7.2-alpha.
933 o Minor bugfixes (control port):
934 - Repair a warning and a spurious result when getting the maximum
935 number of file descriptors from the controller. Fixes bug 16697;
936 bugfix on 0.2.7.2-alpha.
938 o Minor bugfixes (correctness):
939 - When calling channel_free_list(), avoid calling smartlist_remove()
940 while inside a FOREACH loop. This partially reverts commit
941 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
942 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
944 o Minor bugfixes (documentation):
945 - Advise users on how to configure separate IPv4 and IPv6 exit
946 policies in the manpage and sample torrcs. Related to ticket 16069.
947 - Fix the usage message of tor-resolve(1) so that it no longer lists
948 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
949 - Fix an error in the manual page and comments for
950 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
951 required "ORPort connectivity". While this is true, it is in no
952 way unique to the HSDir flag. Of all the flags, only HSDirs need a
953 DirPort configured in order for the authorities to assign that
954 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
957 o Minor bugfixes (Ed25519):
958 - Fix a memory leak when reading router descriptors with expired
959 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
961 o Minor bugfixes (linux seccomp2 sandbox):
962 - Allow bridge authorities to run correctly under the seccomp2
963 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
964 - Allow routers with ed25519 keys to run correctly under the
965 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
967 o Minor bugfixes (open file limit):
968 - Fix set_max_file_descriptors() to set by default the max open file
969 limit to the current limit when setrlimit() fails. Fixes bug
970 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
972 o Minor bugfixes (portability):
973 - Try harder to normalize the exit status of the Tor process to the
974 standard-provided range. Fixes bug 16975; bugfix on every version
976 - Check correctly for Windows socket errors in the workqueue
977 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
978 - Fix the behavior of crypto_rand_time_range() when told to consider
979 times before 1970. (These times were possible when running in a
980 simulated network environment where time()'s output starts at
981 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
982 - Restore correct operation of TLS client-cipher detection on
983 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
985 o Minor bugfixes (relay):
986 - Ensure that worker threads actually exit when a fatal error or
987 shutdown is indicated. This fix doesn't currently affect the
988 behavior of Tor, because Tor workers never indicates fatal error
989 or shutdown except in the unit tests. Fixes bug 16868; bugfix
991 - Unblock threads before releasing the work queue mutex to ensure
992 predictable scheduling behavior. Fixes bug 16644; bugfix
995 o Code simplification and refactoring:
996 - Change the function that's called when we need to retry all
997 downloads so that it only reschedules the downloads to happen
998 immediately, rather than launching them all at once itself. This
999 further simplifies Tor's callgraph.
1000 - Move some format-parsing functions out of crypto.c and
1001 crypto_curve25519.c into crypto_format.c and/or util_format.c.
1002 - Move the client-only parts of init_keys() into a separate
1003 function. Closes ticket 16763.
1004 - Simplify the microdesc_free() implementation so that it no longer
1005 appears (to code analysis tools) to potentially invoke a huge
1006 suite of other microdesc functions.
1007 - Simply the control graph further by deferring the inner body of
1008 directory_all_unreachable() into a callback. Closes ticket 16762.
1009 - Treat the loss of an owning controller as equivalent to a SIGTERM
1010 signal. This removes a tiny amount of duplicated code, and
1011 simplifies our callgraph. Closes ticket 16788.
1012 - When generating an event to send to the controller, we no longer
1013 put the event over the network immediately. Instead, we queue
1014 these events, and use a Libevent callback to deliver them. This
1015 change simplifies Tor's callgraph by reducing the number of
1016 functions from which all other Tor functions are reachable. Closes
1018 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
1019 that try to scan or compile every file on Unix won't decide that
1021 - Remove the unused "nulterminate" argument from buf_pullup().
1024 - Recommend a 40 GB example AccountingMax in torrc.sample rather
1025 than a 4 GB max. Closes ticket 16742.
1026 - Include the TUNING document in our source tarball. It is referred
1027 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
1031 - The internal pure-C tor-fw-helper tool is now removed from the Tor
1032 distribution, in favor of the pure-Go clone available from
1033 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
1034 used by the C tor-fw-helper are not, in our opinion, very
1035 confidence- inspiring in their secure-programming techniques.
1036 Closes ticket 13338.
1037 - Remove the code that would try to aggressively flush controller
1038 connections while writing to them. This code was introduced in
1039 0.1.2.7-alpha, in order to keep output buffers from exceeding
1040 their limits. But there is no longer a maximum output buffer size,
1041 and flushing data in this way caused some undesirable recursions
1042 in our call graph. Closes ticket 16480.
1045 - Make "bridges+hs" the default test network. This tests almost all
1046 tor functionality during make test-network, while allowing tests
1047 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
1048 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
1049 (chutney). Patches by "teor".
1050 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
1051 by-side in the same parent directory. Closes ticket 16903. Patch
1053 - Use environment variables rather than autoconf substitutions to
1054 send variables from the build system to the test scripts. This
1055 change should be easier to maintain, and cause 'make distcheck' to
1056 work better than before. Fixes bug 17148.
1057 - Add a new set of callgraph analysis scripts that use clang to
1058 produce a list of which Tor functions are reachable from which
1059 other Tor functions. We're planning to use these to help simplify
1060 our code structure by identifying illogical dependencies.
1061 - Add new 'test-full' and 'test-full-online' targets to run all
1062 tests, including integration tests with stem and chutney.
1063 - Make the test-workqueue test work on Windows by initializing the
1064 network before we begin.
1065 - New make target (make test-network-all) to run multiple applicable
1066 chutney test cases. Patch from Teor; closes 16953.
1067 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
1068 functions in dns.c. Implements a portion of ticket 16831.
1069 - When building Tor with testing coverage enabled, run Chutney tests
1070 (if any) using the 'tor-cov' coverage binary.
1071 - When running test-network or test-stem, check for the absence of
1072 stem/chutney before doing any build operations.
1075 Changes in version 0.2.7.2-alpha - 2015-07-27
1076 This, the second alpha in the Tor 0.2.7 series, has a number of new
1077 features, including a way to manually pick the number of introduction
1078 points for hidden services, and the much stronger Ed25519 signing key
1079 algorithm for regular Tor relays (including support for encrypted
1080 offline identity keys in the new algorithm).
1082 Support for Ed25519 on relays is currently limited to signing router
1083 descriptors; later alphas in this series will extend Ed25519 key
1084 support to more parts of the Tor protocol.
1086 o Major features (Ed25519 identity keys, Proposal 220):
1087 - All relays now maintain a stronger identity key, using the Ed25519
1088 elliptic curve signature format. This master key is designed so
1089 that it can be kept offline. Relays also generate an online
1090 signing key, and a set of other Ed25519 keys and certificates.
1091 These are all automatically regenerated and rotated as needed.
1092 Implements part of ticket 12498.
1093 - Directory authorities now vote on Ed25519 identity keys along with
1094 RSA1024 keys. Implements part of ticket 12498.
1095 - Directory authorities track which Ed25519 identity keys have been
1096 used with which RSA1024 identity keys, and do not allow them to
1097 vary freely. Implements part of ticket 12498.
1098 - Microdescriptors now include Ed25519 identity keys. Implements
1099 part of ticket 12498.
1100 - Add support for offline encrypted Ed25519 master keys. To use this
1101 feature on your tor relay, run "tor --keygen" to make a new master
1102 key (or to make a new signing key if you already have a master
1103 key). Closes ticket 13642.
1105 o Major features (Hidden services):
1106 - Add the torrc option HiddenServiceNumIntroductionPoints, to
1107 specify a fixed number of introduction points. Its maximum value
1108 is 10 and default is 3. Using this option can increase a hidden
1109 service's reliability under load, at the cost of making it more
1110 visible that the hidden service is facing extra load. Closes
1112 - Remove the adaptive algorithm for choosing the number of
1113 introduction points, which used to change the number of
1114 introduction points (poorly) depending on the number of
1115 connections the HS sees. Closes ticket 4862.
1117 o Major features (onion key cross-certification):
1118 - Relay descriptors now include signatures of their own identity
1119 keys, made using the TAP and ntor onion keys. These signatures
1120 allow relays to prove ownership of their own onion keys. Because
1121 of this change, microdescriptors will no longer need to include
1122 RSA identity keys. Implements proposal 228; closes ticket 12499.
1124 o Major features (performance):
1125 - Improve the runtime speed of Ed25519 operations by using the
1126 public-domain Ed25519-donna by Andrew M. ("floodyberry").
1127 Implements ticket 16467.
1128 - Improve the runtime speed of the ntor handshake by using an
1129 optimized curve25519 basepoint scalarmult implementation from the
1130 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
1131 ideas by Adam Langley. Implements ticket 9663.
1133 o Major bugfixes (client-side privacy, also in 0.2.6.9):
1134 - Properly separate out each SOCKSPort when applying stream
1135 isolation. The error occurred because each port's session group
1136 was being overwritten by a default value when the listener
1137 connection was initialized. Fixes bug 16247; bugfix on
1138 0.2.6.3-alpha. Patch by "jojelino".
1140 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
1141 - Stop refusing to store updated hidden service descriptors on a
1142 client. This reverts commit 9407040c59218 (which indeed fixed bug
1143 14219, but introduced a major hidden service reachability
1144 regression detailed in bug 16381). This is a temporary fix since
1145 we can live with the minor issue in bug 14219 (it just results in
1146 some load on the network) but the regression of 16381 is too much
1147 of a setback. First-round fix for bug 16381; bugfix
1150 o Major bugfixes (hidden services):
1151 - When cannibalizing a circuit for an introduction point, always
1152 extend to the chosen exit node (creating a 4 hop circuit).
1153 Previously Tor would use the current circuit exit node, which
1154 changed the original choice of introduction point, and could cause
1155 the hidden service to skip excluded introduction points or
1156 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
1159 o Major bugfixes (open file limit):
1160 - The open file limit wasn't checked before calling
1161 tor_accept_socket_nonblocking(), which would make Tor exceed the
1162 limit. Now, before opening a new socket, Tor validates the open
1163 file limit just before, and if the max has been reached, return an
1164 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
1166 o Major bugfixes (stability, also in 0.2.6.10):
1167 - Stop crashing with an assertion failure when parsing certain kinds
1168 of malformed or truncated microdescriptors. Fixes bug 16400;
1169 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1170 by "cypherpunks_backup".
1171 - Stop random client-side assertion failures that could occur when
1172 connecting to a busy hidden service, or connecting to a hidden
1173 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1176 o Minor features (directory authorities, security, also in 0.2.6.9):
1177 - The HSDir flag given by authorities now requires the Stable flag.
1178 For the current network, this results in going from 2887 to 2806
1179 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1180 attack by raising the effort for a relay to become Stable to
1181 require at the very least 7 days, while maintaining the 96 hours
1182 uptime requirement for HSDir. Implements ticket 8243.
1184 o Minor features (client):
1185 - Relax the validation of hostnames in SOCKS5 requests, allowing the
1186 character '_' to appear, in order to cope with domains observed in
1187 the wild that are serving non-RFC compliant records. Resolves
1189 - Relax the validation done to hostnames in SOCKS5 requests, and
1190 allow a single trailing '.' to cope with clients that pass FQDNs
1191 using that syntax to explicitly indicate that the domain name is
1192 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
1193 - Add GroupWritable and WorldWritable options to unix-socket based
1194 SocksPort and ControlPort options. These options apply to a single
1195 socket, and override {Control,Socks}SocketsGroupWritable. Closes
1198 o Minor features (control protocol):
1199 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
1200 the control protocol. Resolves ticket 15358.
1202 o Minor features (directory authorities):
1203 - Directory authorities no longer vote against the "Fast", "Stable",
1204 and "HSDir" flags just because they were going to vote against
1205 "Running": if the consensus turns out to be that the router was
1206 running, then the authority's vote should count. Patch from Peter
1207 Retzlaff; closes issue 8712.
1209 o Minor features (geoip, also in 0.2.6.10):
1210 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1211 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1213 o Minor features (hidden services):
1214 - Add the new options "HiddenServiceMaxStreams" and
1215 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
1216 limit the maximum number of simultaneous streams per circuit, and
1217 optionally tear down the circuit when the limit is exceeded. Part
1220 o Minor features (portability):
1221 - Use C99 variadic macros when the compiler is not GCC. This avoids
1222 failing compilations on MSVC, and fixes a log-file-based race
1223 condition in our old workarounds. Original patch from Gisle Vanem.
1225 o Minor bugfixes (compilation, also in 0.2.6.9):
1226 - Build with --enable-systemd correctly when libsystemd is
1227 installed, but systemd is not. Fixes bug 16164; bugfix on
1228 0.2.6.3-alpha. Patch from Peter Palfrader.
1230 o Minor bugfixes (controller):
1231 - Add the descriptor ID in each HS_DESC control event. It was
1232 missing, but specified in control-spec.txt. Fixes bug 15881;
1233 bugfix on 0.2.5.2-alpha.
1235 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
1236 - Check for failures from crypto_early_init, and refuse to continue.
1237 A previous typo meant that we could keep going with an
1238 uninitialized crypto library, and would have OpenSSL initialize
1239 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1240 when implementing ticket 4900. Patch by "teor".
1242 o Minor bugfixes (hidden services):
1243 - Fix a crash when reloading configuration while at least one
1244 configured and one ephemeral hidden service exists. Fixes bug
1245 16060; bugfix on 0.2.7.1-alpha.
1246 - Avoid crashing with a double-free bug when we create an ephemeral
1247 hidden service but adding it fails for some reason. Fixes bug
1248 16228; bugfix on 0.2.7.1-alpha.
1250 o Minor bugfixes (Linux seccomp2 sandbox):
1251 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
1252 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
1254 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
1255 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1256 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1257 on 0.2.6.3-alpha. Patch from "teor".
1259 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
1260 - Fix sandboxing to work when running as a relay, by allowing the
1261 renaming of secret_id_key, and allowing the eventfd2 and futex
1262 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
1264 - Allow systemd connections to work with the Linux seccomp2 sandbox
1265 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1268 o Minor bugfixes (relay):
1269 - Fix a rarely-encountered memory leak when failing to initialize
1270 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
1273 o Minor bugfixes (systemd):
1274 - Fix an accidental formatting error that broke the systemd
1275 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
1276 - Tor's systemd unit file no longer contains extraneous spaces.
1277 These spaces would sometimes confuse tools like deb-systemd-
1278 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
1280 o Minor bugfixes (tests):
1281 - Use the configured Python executable when running test-stem-full.
1282 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
1284 o Minor bugfixes (tests, also in 0.2.6.9):
1285 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1286 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1288 o Minor bugfixes (threads, comments):
1289 - Always initialize return value in compute_desc_id in rendcommon.c
1290 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1291 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
1292 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1293 - Remove undefined directive-in-macro in test_util_writepid clang
1294 3.7 complains that using a preprocessor directive inside a macro
1295 invocation in test_util_writepid in test_util.c is undefined.
1296 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1298 o Code simplification and refactoring:
1299 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
1300 to ensure they remain consistent and visible everywhere.
1301 - Remove some vestigial workarounds for the MSVC6 compiler. We
1302 haven't supported that in ages.
1303 - The link authentication code has been refactored for better
1304 testability and reliability. It now uses code generated with the
1305 "trunnel" binary encoding generator, to reduce the risk of bugs
1306 due to programmer error. Done as part of ticket 12498.
1309 - Include a specific and (hopefully) accurate documentation of the
1310 torrc file's meta-format in doc/torrc_format.txt. This is mainly
1311 of interest to people writing programs to parse or generate torrc
1312 files. This document is not a commitment to long-term
1313 compatibility; some aspects of the current format are a bit
1314 ridiculous. Closes ticket 2325.
1317 - Tor no longer supports copies of OpenSSL that are missing support
1318 for Elliptic Curve Cryptography. (We began using ECC when
1319 available in 0.2.4.8-alpha, for more safe and efficient key
1320 negotiation.) In particular, support for at least one of P256 or
1321 P224 is now required, with manual configuration needed if only
1322 P224 is available. Resolves ticket 16140.
1323 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1324 on an operating system that has not upgraded to OpenSSL 1.0 or
1325 later, and you compile Tor from source, you will need to install a
1326 more recent OpenSSL to link Tor against.) These versions of
1327 OpenSSL are still supported by the OpenSSL, but the numerous
1328 cryptographic improvements in later OpenSSL releases makes them a
1329 clear choice. Resolves ticket 16034.
1330 - Remove the HidServDirectoryV2 option. Now all relays offer to
1331 store hidden service descriptors. Related to 16543.
1332 - Remove the VoteOnHidServDirectoriesV2 option, since all
1333 authorities have long set it to 1. Closes ticket 16543.
1336 - Document use of coverity, clang static analyzer, and clang dynamic
1337 undefined behavior and address sanitizers in doc/HACKING. Include
1338 detailed usage instructions in the blacklist. Patch by "teor".
1339 Closes ticket 15817.
1340 - The link authentication protocol code now has extensive tests.
1341 - The relay descriptor signature testing code now has
1343 - The test_workqueue program now runs faster, and is enabled by
1344 default as a part of "make check".
1345 - Now that OpenSSL has its own scrypt implementation, add an unit
1346 test that checks for interoperability between libscrypt_scrypt()
1347 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
1348 and rely on EVP_PBE_scrypt() whenever possible. Resolves
1352 Changes in version 0.2.6.10 - 2015-07-12
1353 Tor version 0.2.6.10 fixes some significant stability and hidden
1354 service client bugs, bulletproofs the cryptography init process, and
1355 fixes a bug when using the sandbox code with some older versions of
1356 Linux. Everyone running an older version, especially an older version
1357 of 0.2.6, should upgrade.
1359 o Major bugfixes (hidden service clients, stability):
1360 - Stop refusing to store updated hidden service descriptors on a
1361 client. This reverts commit 9407040c59218 (which indeed fixed bug
1362 14219, but introduced a major hidden service reachability
1363 regression detailed in bug 16381). This is a temporary fix since
1364 we can live with the minor issue in bug 14219 (it just results in
1365 some load on the network) but the regression of 16381 is too much
1366 of a setback. First-round fix for bug 16381; bugfix
1369 o Major bugfixes (stability):
1370 - Stop crashing with an assertion failure when parsing certain kinds
1371 of malformed or truncated microdescriptors. Fixes bug 16400;
1372 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1373 by "cypherpunks_backup".
1374 - Stop random client-side assertion failures that could occur when
1375 connecting to a busy hidden service, or connecting to a hidden
1376 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1379 o Minor features (geoip):
1380 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1381 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1383 o Minor bugfixes (crypto error-handling):
1384 - Check for failures from crypto_early_init, and refuse to continue.
1385 A previous typo meant that we could keep going with an
1386 uninitialized crypto library, and would have OpenSSL initialize
1387 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1388 when implementing ticket 4900. Patch by "teor".
1390 o Minor bugfixes (Linux seccomp2 sandbox):
1391 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1392 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1393 on 0.2.6.3-alpha. Patch from "teor".
1396 Changes in version 0.2.6.9 - 2015-06-11
1397 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
1398 requirements for receiving an HSDir flag, and addresses some other small
1399 bugs in the systemd and sandbox code. Clients using circuit isolation
1400 should upgrade; all directory authorities should upgrade.
1402 o Major bugfixes (client-side privacy):
1403 - Properly separate out each SOCKSPort when applying stream
1404 isolation. The error occurred because each port's session group was
1405 being overwritten by a default value when the listener connection
1406 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
1409 o Minor feature (directory authorities, security):
1410 - The HSDir flag given by authorities now requires the Stable flag.
1411 For the current network, this results in going from 2887 to 2806
1412 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1413 attack by raising the effort for a relay to become Stable which
1414 takes at the very least 7 days to do so and by keeping the 96
1415 hours uptime requirement for HSDir. Implements ticket 8243.
1417 o Minor bugfixes (compilation):
1418 - Build with --enable-systemd correctly when libsystemd is
1419 installed, but systemd is not. Fixes bug 16164; bugfix on
1420 0.2.6.3-alpha. Patch from Peter Palfrader.
1422 o Minor bugfixes (Linux seccomp2 sandbox):
1423 - Fix sandboxing to work when running as a relaymby renaming of
1424 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
1425 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
1426 - Allow systemd connections to work with the Linux seccomp2 sandbox
1427 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1430 o Minor bugfixes (tests):
1431 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1432 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1435 Changes in version 0.2.6.8 - 2015-05-21
1436 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
1437 fixes an authority-side bug in assigning the HSDir flag. All directory
1438 authorities should upgrade.
1440 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
1441 - Revert commit that made directory authorities assign the HSDir
1442 flag to relay without a DirPort; this was bad because such relays
1443 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1444 on tor-0.2.6.3-alpha.
1446 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1447 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1448 a client authorized hidden service. Fixes bug 15823; bugfix
1451 o Minor features (geoip):
1452 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1453 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1457 Changes in version 0.2.7.1-alpha - 2015-05-12
1458 Tor 0.2.7.1-alpha is the first alpha release in its series. It
1459 includes numerous small features and bugfixes against previous Tor
1460 versions, and numerous small infrastructure improvements. The most
1461 notable features are several new ways for controllers to interact with
1462 the hidden services subsystem.
1464 o New system requirements:
1465 - Tor no longer includes workarounds to support Libevent versions
1466 before 1.3e. Libevent 2.0 or later is recommended. Closes
1469 o Major features (controller):
1470 - Add the ADD_ONION and DEL_ONION commands that allow the creation
1471 and management of hidden services via the controller. Closes
1473 - New "GETINFO onions/current" and "GETINFO onions/detached"
1474 commands to get information about hidden services created via the
1475 controller. Part of ticket 6411.
1476 - New HSFETCH command to launch a request for a hidden service
1477 descriptor. Closes ticket 14847.
1478 - New HSPOST command to upload a hidden service descriptor. Closes
1479 ticket 3523. Patch by "DonnchaC".
1481 o Major bugfixes (hidden services):
1482 - Revert commit that made directory authorities assign the HSDir
1483 flag to relay without a DirPort; this was bad because such relays
1484 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1485 on tor-0.2.6.3-alpha.
1487 o Minor features (clock-jump tolerance):
1488 - Recover better when our clock jumps back many hours, like might
1489 happen for Tails or Whonix users who start with a very wrong
1490 hardware clock, use Tor to discover a more accurate time, and then
1491 fix their clock. Resolves part of ticket 8766.
1493 o Minor features (command-line interface):
1494 - Make --hash-password imply --hush to prevent unnecessary noise.
1495 Closes ticket 15542. Patch from "cypherpunks".
1496 - Print a warning whenever we find a relative file path being used
1497 as torrc option. Resolves issue 14018.
1499 o Minor features (controller):
1500 - Add DirAuthority lines for default directory authorities to the
1501 output of the "GETINFO config/defaults" command if not already
1502 present. Implements ticket 14840.
1503 - Controllers can now use "GETINFO hs/client/desc/id/..." to
1504 retrieve items from the client's hidden service descriptor cache.
1505 Closes ticket 14845.
1506 - Implement a new controller command "GETINFO status/fresh-relay-
1507 descs" to fetch a descriptor/extrainfo pair that was generated on
1508 demand just for the controller's use. Implements ticket 14784.
1510 o Minor features (DoS-resistance):
1511 - Make it harder for attackers to overload hidden services with
1512 introductions, by blocking multiple introduction requests on the
1513 same circuit. Resolves ticket 15515.
1515 o Minor features (geoip):
1516 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1517 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1520 o Minor features (HS popularity countermeasure):
1521 - To avoid leaking HS popularity, don't cycle the introduction point
1522 when we've handled a fixed number of INTRODUCE2 cells but instead
1523 cycle it when a random number of introductions is reached, thus
1524 making it more difficult for an attacker to find out the amount of
1525 clients that have used the introduction point for a specific HS.
1526 Closes ticket 15745.
1528 o Minor features (logging):
1529 - Include the Tor version in all LD_BUG log messages, since people
1530 tend to cut and paste those into the bugtracker. Implements
1533 o Minor features (pluggable transports):
1534 - When launching managed pluggable transports on Linux systems,
1535 attempt to have the kernel deliver a SIGTERM on tor exit if the
1536 pluggable transport process is still running. Resolves
1538 - When launching managed pluggable transports, setup a valid open
1539 stdin in the child process that can be used to detect if tor has
1540 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
1541 can be used by implementations to detect this new behavior.
1542 Resolves ticket 15435.
1544 o Minor features (testing):
1545 - Add a test to verify that the compiler does not eliminate our
1546 memwipe() implementation. Closes ticket 15377.
1547 - Add make rule `check-changes` to verify the format of changes
1548 files. Closes ticket 15180.
1549 - Add unit tests for control_event_is_interesting(). Add a compile-
1550 time check that the number of events doesn't exceed the capacity
1551 of control_event_t.event_mask. Closes ticket 15431, checks for
1552 bugs similar to 13085. Patch by "teor".
1553 - Command-line argument tests moved to Stem. Resolves ticket 14806.
1554 - Integrate the ntor, backtrace, and zero-length keys tests into the
1555 automake test suite. Closes ticket 15344.
1556 - Remove assertions during builds to determine Tor's test coverage.
1557 We don't want to trigger these even in assertions, so including
1558 them artificially makes our branch coverage look worse than it is.
1559 This patch provides the new test-stem-full and coverage-html-full
1560 configure options. Implements ticket 15400.
1562 o Minor bugfixes (build):
1563 - Improve out-of-tree builds by making non-standard rules work and
1564 clean up additional files and directories. Fixes bug 15053; bugfix
1567 o Minor bugfixes (command-line interface):
1568 - When "--quiet" is provided along with "--validate-config", do not
1569 write anything to stdout on success. Fixes bug 14994; bugfix
1571 - When complaining about bad arguments to "--dump-config", use
1574 o Minor bugfixes (configuration, unit tests):
1575 - Only add the default fallback directories when the DirAuthorities,
1576 AlternateDirAuthority, and FallbackDir directory config options
1577 are set to their defaults. The default fallback directory list is
1578 currently empty, this fix will only change tor's behavior when it
1579 has default fallback directories. Includes unit tests for
1580 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
1581 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
1583 o Minor bugfixes (correctness):
1584 - For correctness, avoid modifying a constant string in
1585 handle_control_postdescriptor. Fixes bug 15546; bugfix
1587 - Remove side-effects from tor_assert() calls. This was harmless,
1588 because we never disable assertions, but it is bad style and
1589 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
1592 o Minor bugfixes (hidden service):
1593 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1594 a client authorized hidden service. Fixes bug 15823; bugfix
1596 - Remove an extraneous newline character from the end of hidden
1597 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
1599 o Minor bugfixes (interface):
1600 - Print usage information for --dump-config when it is used without
1601 an argument. Also, fix the error message to use different wording
1602 and add newline at the end. Fixes bug 15541; bugfix
1605 o Minor bugfixes (logs):
1606 - When building Tor under Clang, do not include an extra set of
1607 parentheses in log messages that include function names. Fixes bug
1608 15269; bugfix on every released version of Tor when compiled with
1609 recent enough Clang.
1611 o Minor bugfixes (network):
1612 - When attempting to use fallback technique for network interface
1613 lookup, disregard loopback and multicast addresses since they are
1614 unsuitable for public communications.
1616 o Minor bugfixes (statistics):
1617 - Disregard the ConnDirectionStatistics torrc options when Tor is
1618 not a relay since in that mode of operation no sensible data is
1619 being collected and because Tor might run into measurement hiccups
1620 when running as a client for some time, then becoming a relay.
1621 Fixes bug 15604; bugfix on 0.2.2.35.
1623 o Minor bugfixes (test networks):
1624 - When self-testing reachability, use ExtendAllowPrivateAddresses to
1625 determine if local/private addresses imply reachability. The
1626 previous fix used TestingTorNetwork, which implies
1627 ExtendAllowPrivateAddresses, but this excluded rare configurations
1628 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
1629 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
1630 issue discovered by CJ Ess.
1632 o Minor bugfixes (testing):
1633 - Check for matching value in server response in ntor_ref.py. Fixes
1634 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
1636 - Set the severity correctly when testing
1637 get_interface_addresses_ifaddrs() and
1638 get_interface_addresses_win32(), so that the tests fail gracefully
1639 instead of triggering an assertion. Fixes bug 15759; bugfix on
1640 0.2.6.3-alpha. Reported by Nicolas Derive.
1642 o Code simplification and refactoring:
1643 - Move the hacky fallback code out of get_interface_address6() into
1644 separate function and get it covered with unit-tests. Resolves
1646 - Refactor hidden service client-side cache lookup to intelligently
1647 report its various failure cases, and disentangle failure cases
1648 involving a lack of introduction points. Closes ticket 14391.
1649 - Use our own Base64 encoder instead of OpenSSL's, to allow more
1650 control over the output. Part of ticket 15652.
1653 - Improve the descriptions of statistics-related torrc options in
1654 the manpage to describe rationale and possible uses cases. Fixes
1656 - Improve the layout and formatting of ./configure --help messages.
1657 Closes ticket 15024. Patch from "cypherpunks".
1658 - Standardize on the term "server descriptor" in the manual page.
1659 Previously, we had used "router descriptor", "server descriptor",
1660 and "relay descriptor" interchangeably. Part of ticket 14987.
1663 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
1664 and always use the internal Base64 decoder. The internal decoder
1665 has been part of tor since tor-0.2.0.10-alpha, and no one should
1666 be using the OpenSSL one. Part of ticket 15652.
1667 - Remove the 'tor_strclear()' function; use memwipe() instead.
1668 Closes ticket 14922.
1671 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
1672 fingerprinting we now recommend pluggable transports; for forward-
1673 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
1674 - Remove the undocumented "--digests" command-line option. It
1675 complicated our build process, caused subtle build issues on
1676 multiple platforms, and is now redundant since we started
1677 including git version identifiers. Closes ticket 14742.
1678 - Tor no longer contains checks for ancient directory cache versions
1679 that didn't know about microdescriptors.
1680 - Tor no longer contains workarounds for stat files generated by
1681 super-old versions of Tor that didn't choose guards sensibly.
1684 Changes in version 0.2.4.27 - 2015-04-06
1685 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
1686 could be used by an attacker to crash hidden services, or crash clients
1687 visiting hidden services. Hidden services should upgrade as soon as
1688 possible; clients should upgrade whenever packages become available.
1690 This release also backports a simple improvement to make hidden
1691 services a bit less vulnerable to denial-of-service attacks.
1693 o Major bugfixes (security, hidden service):
1694 - Fix an issue that would allow a malicious client to trigger an
1695 assertion failure and halt a hidden service. Fixes bug 15600;
1696 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1697 - Fix a bug that could cause a client to crash with an assertion
1698 failure when parsing a malformed hidden service descriptor. Fixes
1699 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1701 o Minor features (DoS-resistance, hidden service):
1702 - Introduction points no longer allow multiple INTRODUCE1 cells to
1703 arrive on the same circuit. This should make it more expensive for
1704 attackers to overwhelm hidden services with introductions.
1705 Resolves ticket 15515.
1708 Changes in version 0.2.5.12 - 2015-04-06
1709 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
1710 could be used by an attacker to crash hidden services, or crash clients
1711 visiting hidden services. Hidden services should upgrade as soon as
1712 possible; clients should upgrade whenever packages become available.
1714 This release also backports a simple improvement to make hidden
1715 services a bit less vulnerable to denial-of-service attacks.
1717 o Major bugfixes (security, hidden service):
1718 - Fix an issue that would allow a malicious client to trigger an
1719 assertion failure and halt a hidden service. Fixes bug 15600;
1720 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1721 - Fix a bug that could cause a client to crash with an assertion
1722 failure when parsing a malformed hidden service descriptor. Fixes
1723 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1725 o Minor features (DoS-resistance, hidden service):
1726 - Introduction points no longer allow multiple INTRODUCE1 cells to
1727 arrive on the same circuit. This should make it more expensive for
1728 attackers to overwhelm hidden services with introductions.
1729 Resolves ticket 15515.
1732 Changes in version 0.2.6.7 - 2015-04-06
1733 Tor 0.2.6.7 fixes two security issues that could be used by an
1734 attacker to crash hidden services, or crash clients visiting hidden
1735 services. Hidden services should upgrade as soon as possible; clients
1736 should upgrade whenever packages become available.
1738 This release also contains two simple improvements to make hidden
1739 services a bit less vulnerable to denial-of-service attacks.
1741 o Major bugfixes (security, hidden service):
1742 - Fix an issue that would allow a malicious client to trigger an
1743 assertion failure and halt a hidden service. Fixes bug 15600;
1744 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1745 - Fix a bug that could cause a client to crash with an assertion
1746 failure when parsing a malformed hidden service descriptor. Fixes
1747 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1749 o Minor features (DoS-resistance, hidden service):
1750 - Introduction points no longer allow multiple INTRODUCE1 cells to
1751 arrive on the same circuit. This should make it more expensive for
1752 attackers to overwhelm hidden services with introductions.
1753 Resolves ticket 15515.
1754 - Decrease the amount of reattempts that a hidden service performs
1755 when its rendezvous circuits fail. This reduces the computational
1756 cost for running a hidden service under heavy load. Resolves
1760 Changes in version 0.2.6.6 - 2015-03-24
1761 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1763 It adds numerous safety, security, correctness, and performance
1764 improvements. Client programs can be configured to use more kinds of
1765 sockets, AutomapHosts works better, the multithreading backend is
1766 improved, cell transmission is refactored, test coverage is much
1767 higher, more denial-of-service attacks are handled, guard selection is
1768 improved to handle long-term guards better, pluggable transports
1769 should work a bit better, and some annoying hidden service performance
1770 bugs should be addressed.
1772 o Minor bugfixes (portability):
1773 - Use the correct datatype in the SipHash-2-4 function to prevent
1774 compilers from assuming any sort of alignment. Fixes bug 15436;
1775 bugfix on 0.2.5.3-alpha.
1777 Changes in version 0.2.6.5-rc - 2015-03-18
1778 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
1779 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
1781 o Major bugfixes (client):
1782 - Avoid crashing when making certain configuration option changes on
1783 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
1786 o Major bugfixes (pluggable transports):
1787 - Initialize the extended OR Port authentication cookie before
1788 launching pluggable transports. This prevents a race condition
1789 that occured when server-side pluggable transports would cache the
1790 authentication cookie before it has been (re)generated. Fixes bug
1791 15240; bugfix on 0.2.5.1-alpha.
1793 o Major bugfixes (portability):
1794 - Do not crash on startup when running on Solaris. Fixes a bug
1795 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
1798 o Minor features (heartbeat):
1799 - On relays, report how many connections we negotiated using each
1800 version of the Tor link protocols. This information will let us
1801 know if removing support for very old versions of the Tor
1802 protocols is harming the network. Closes ticket 15212.
1804 o Code simplification and refactoring:
1805 - Refactor main loop to extract the 'loop' part. This makes it
1806 easier to run Tor under Shadow. Closes ticket 15176.
1809 Changes in version 0.2.5.11 - 2015-03-17
1810 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1812 It backports several bugfixes from the 0.2.6 branch, including a
1813 couple of medium-level security fixes for relays and exit nodes.
1814 It also updates the list of directory authorities.
1816 o Directory authority changes:
1817 - Remove turtles as a directory authority.
1818 - Add longclaw as a new (v3) directory authority. This implements
1819 ticket 13296. This keeps the directory authority count at 9.
1820 - The directory authority Faravahar has a new IP address. This
1821 closes ticket 14487.
1823 o Major bugfixes (crash, OSX, security):
1824 - Fix a remote denial-of-service opportunity caused by a bug in
1825 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1828 o Major bugfixes (relay, stability, possible security):
1829 - Fix a bug that could lead to a relay crashing with an assertion
1830 failure if a buffer of exactly the wrong layout was passed to
1831 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1832 0.2.0.10-alpha. Patch from 'cypherpunks'.
1833 - Do not assert if the 'data' pointer on a buffer is advanced to the
1834 very end of the buffer; log a BUG message instead. Only assert if
1835 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1837 o Major bugfixes (exit node stability):
1838 - Fix an assertion failure that could occur under high DNS load.
1839 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1840 diagnosed and fixed by "cypherpunks".
1842 o Major bugfixes (Linux seccomp2 sandbox):
1843 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1844 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1845 0.2.5.1-alpha. Patch from "sanic".
1847 o Minor features (controller):
1848 - New "GETINFO bw-event-cache" to get information about recent
1849 bandwidth events. Closes ticket 14128. Useful for controllers to
1850 get recent bandwidth history after the fix for ticket 13988.
1852 o Minor features (geoip):
1853 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1854 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1857 o Minor bugfixes (client, automapping):
1858 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1859 no value follows the option. Fixes bug 14142; bugfix on
1860 0.2.4.7-alpha. Patch by "teor".
1861 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1862 14195; bugfix on 0.1.0.1-rc.
1864 o Minor bugfixes (compilation):
1865 - Build without warnings with the stock OpenSSL srtp.h header, which
1866 has a duplicate declaration of SSL_get_selected_srtp_profile().
1867 Fixes bug 14220; this is OpenSSL's bug, not ours.
1869 o Minor bugfixes (directory authority):
1870 - Allow directory authorities to fetch more data from one another if
1871 they find themselves missing lots of votes. Previously, they had
1872 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1873 bugfix on 0.1.2.5-alpha.
1874 - Enlarge the buffer to read bwauth generated files to avoid an
1875 issue when parsing the file in dirserv_read_measured_bandwidths().
1876 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1878 o Minor bugfixes (statistics):
1879 - Increase period over which bandwidth observations are aggregated
1880 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1882 o Minor bugfixes (preventative security, C safety):
1883 - When reading a hexadecimal, base-32, or base-64 encoded value from
1884 a string, always overwrite the whole output buffer. This prevents
1885 some bugs where we would look at (but fortunately, not reveal)
1886 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1890 Changes in version 0.2.4.26 - 2015-03-17
1891 Tor 0.2.4.26 includes an updated list of directory authorities. It
1892 also backports a couple of stability and security bugfixes from 0.2.5
1895 o Directory authority changes:
1896 - Remove turtles as a directory authority.
1897 - Add longclaw as a new (v3) directory authority. This implements
1898 ticket 13296. This keeps the directory authority count at 9.
1899 - The directory authority Faravahar has a new IP address. This
1900 closes ticket 14487.
1902 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1903 - Fix an assertion failure that could occur under high DNS load.
1904 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1905 diagnosed and fixed by "cypherpunks".
1907 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1908 - Fix a bug that could lead to a relay crashing with an assertion
1909 failure if a buffer of exactly the wrong layout was passed to
1910 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1911 0.2.0.10-alpha. Patch from 'cypherpunks'.
1912 - Do not assert if the 'data' pointer on a buffer is advanced to the
1913 very end of the buffer; log a BUG message instead. Only assert if
1914 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1916 o Minor features (geoip):
1917 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1918 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1921 Changes in version 0.2.6.4-rc - 2015-03-09
1922 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
1923 attacker might be able to use in order to crash certain Tor
1924 directories. It also resolves some minor issues left over from, or
1925 introduced in, Tor 0.2.6.3-alpha or earlier.
1927 o Major bugfixes (crash, OSX, security):
1928 - Fix a remote denial-of-service opportunity caused by a bug in
1929 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1932 o Major bugfixes (relay, stability, possible security):
1933 - Fix a bug that could lead to a relay crashing with an assertion
1934 failure if a buffer of exactly the wrong layout is passed to
1935 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1936 0.2.0.10-alpha. Patch from "cypherpunks".
1937 - Do not assert if the 'data' pointer on a buffer is advanced to the
1938 very end of the buffer; log a BUG message instead. Only assert if
1939 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1941 o Major bugfixes (FreeBSD IPFW transparent proxy):
1942 - Fix address detection with FreeBSD transparent proxies, when
1943 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1946 o Major bugfixes (Linux seccomp2 sandbox):
1947 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
1948 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
1950 - Allow AF_UNIX hidden services to be used with the seccomp2
1951 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
1952 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1953 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1954 0.2.5.1-alpha. Patch from "sanic".
1956 o Minor features (controller):
1957 - Messages about problems in the bootstrap process now include
1958 information about the server we were trying to connect to when we
1959 noticed the problem. Closes ticket 15006.
1961 o Minor features (geoip):
1962 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1963 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1966 o Minor features (logs):
1967 - Quiet some log messages in the heartbeat and at startup. Closes
1970 o Minor bugfixes (certificate handling):
1971 - If an authority operator accidentally makes a signing certificate
1972 with a future publication time, do not discard its real signing
1973 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1974 - Remove any old authority certificates that have been superseded
1975 for at least two days. Previously, we would keep superseded
1976 certificates until they expired, if they were published close in
1977 time to the certificate that superseded them. Fixes bug 11454;
1978 bugfix on 0.2.1.8-alpha.
1980 o Minor bugfixes (compilation):
1981 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1983 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
1986 o Minor bugfixes (testing):
1987 - Fix endianness issues in unit test for resolve_my_address() to
1988 have it pass on big endian systems. Fixes bug 14980; bugfix on
1990 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1991 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1992 - When running the new 'make test-stem' target, use the configured
1993 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
1995 - When running the zero-length-keys tests, do not use the default
1996 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
1999 o Directory authority IP change:
2000 - The directory authority Faravahar has a new IP address. This
2001 closes ticket 14487.
2004 - Remove some lingering dead code that once supported mempools.
2005 Mempools were disabled by default in 0.2.5, and removed entirely
2006 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
2010 Changes in version 0.2.6.3-alpha - 2015-02-19
2011 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
2012 the 0.2.6.x series. It introduces support for more kinds of sockets,
2013 makes it harder to accidentally run an exit, improves our
2014 multithreading backend, incorporates several fixes for the
2015 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
2017 If no major regressions or security holes are found in this version,
2018 the next version will be a release candidate.
2020 o Deprecated versions:
2021 - Tor relays older than 0.2.4.18-rc are no longer allowed to
2022 advertise themselves on the network. Closes ticket 13555.
2024 o Major features (security, unix domain sockets):
2025 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
2026 applications can reach Tor without having to create AF_INET or
2027 AF_INET6 sockets, meaning they can completely disable their
2028 ability to make non-Tor network connections. To create a socket of
2029 this type, use "SocksPort unix:/path/to/socket". Implements
2031 - Support mapping hidden service virtual ports to AF_UNIX sockets.
2032 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
2033 Implements ticket 11485.
2035 o Major features (changed defaults):
2036 - Prevent relay operators from unintentionally running exits: When a
2037 relay is configured as an exit node, we now warn the user unless
2038 the "ExitRelay" option is set to 1. We warn even more loudly if
2039 the relay is configured with the default exit policy, since this
2040 can indicate accidental misconfiguration. Setting "ExitRelay 0"
2041 stops Tor from running as an exit relay. Closes ticket 10067.
2043 o Major features (directory system):
2044 - When downloading server- or microdescriptors from a directory
2045 server, we no longer launch multiple simultaneous requests to the
2046 same server. This reduces load on the directory servers,
2047 especially when directory guards are in use. Closes ticket 9969.
2048 - When downloading server- or microdescriptors over a tunneled
2049 connection, do not limit the length of our requests to what the
2050 Squid proxy is willing to handle. Part of ticket 9969.
2051 - Authorities can now vote on the correct digests and latest
2052 versions for different software packages. This allows packages
2053 that include Tor to use the Tor authority system as a way to get
2054 notified of updates and their correct digests. Implements proposal
2055 227. Closes ticket 10395.
2057 o Major features (guards):
2058 - Introduce the Guardfraction feature to improves load balancing on
2059 guard nodes. Specifically, it aims to reduce the traffic gap that
2060 guard nodes experience when they first get the Guard flag. This is
2061 a required step if we want to increase the guard lifetime to 9
2062 months or greater. Closes ticket 9321.
2064 o Major features (performance):
2065 - Make the CPU worker implementation more efficient by avoiding the
2066 kernel and lengthening pipelines. The original implementation used
2067 sockets to transfer data from the main thread to the workers, and
2068 didn't allow any thread to be assigned more than a single piece of
2069 work at once. The new implementation avoids communications
2070 overhead by making requests in shared memory, avoiding kernel IO
2071 where possible, and keeping more requests in flight at once.
2072 Implements ticket 9682.
2074 o Major features (relay):
2075 - Raise the minimum acceptable configured bandwidth rate for bridges
2076 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
2077 20 KiB/sec.) Closes ticket 13822.
2079 o Major bugfixes (exit node stability):
2080 - Fix an assertion failure that could occur under high DNS load.
2081 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2082 diagnosed and fixed by "cypherpunks".
2084 o Major bugfixes (mixed relay-client operation):
2085 - When running as a relay and client at the same time (not
2086 recommended), if we decide not to use a new guard because we want
2087 to retry older guards, only close the locally-originating circuits
2088 passing through that guard. Previously we would close all the
2089 circuits through that guard. Fixes bug 9819; bugfix on
2090 0.2.1.1-alpha. Reported by "skruffy".
2092 o Minor features (build):
2093 - New --disable-system-torrc compile-time option to prevent Tor from
2094 looking for the system-wide torrc or torrc-defaults files.
2095 Resolves ticket 13037.
2097 o Minor features (controller):
2098 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
2099 events so controllers can observe circuit isolation inputs. Closes
2101 - ControlPort now supports the unix:/path/to/socket syntax as an
2102 alternative to the ControlSocket option, for consistency with
2103 SocksPort and HiddenServicePort. Closes ticket 14451.
2104 - New "GETINFO bw-event-cache" to get information about recent
2105 bandwidth events. Closes ticket 14128. Useful for controllers to
2106 get recent bandwidth history after the fix for ticket 13988.
2108 o Minor features (Denial of service resistance):
2109 - Count the total number of bytes used storing hidden service
2110 descriptors against the value of MaxMemInQueues. If we're low on
2111 memory, and more than 20% of our memory is used holding hidden
2112 service descriptors, free them until no more than 10% of our
2113 memory holds hidden service descriptors. Free the least recently
2114 fetched descriptors first. Resolves ticket 13806.
2115 - When we have recently been under memory pressure (over 3/4 of
2116 MaxMemInQueues is allocated), then allocate smaller zlib objects
2117 for small requests. Closes ticket 11791.
2119 o Minor features (geoip):
2120 - Update geoip and geoip6 files to the January 7 2015 Maxmind
2121 GeoLite2 Country database.
2123 o Minor features (guard nodes):
2124 - Reduce the time delay before saving guard status to disk from 10
2125 minutes to 30 seconds (or from one hour to 10 minutes if
2126 AvoidDiskWrites is set). Closes ticket 12485.
2128 o Minor features (hidden service):
2129 - Make Sybil attacks against hidden services harder by changing the
2130 minimum time required to get the HSDir flag from 25 hours up to 96
2131 hours. Addresses ticket 14149.
2132 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
2133 services to disable the anti-scanning feature introduced in
2134 0.2.6.2-alpha. With this option not set, a connection to an
2135 unlisted port closes the circuit. With this option set, only a
2136 RELAY_DONE cell is sent. Closes ticket 14084.
2138 o Minor features (interface):
2139 - Implement "-f -" command-line option to read torrc configuration
2140 from standard input, if you don't want to store the torrc file in
2141 the file system. Implements feature 13865.
2143 o Minor features (logging):
2144 - Add a count of unique clients to the bridge heartbeat message.
2145 Resolves ticket 6852.
2146 - Suppress "router info incompatible with extra info" message when
2147 reading extrainfo documents from cache. (This message got loud
2148 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
2150 - Elevate hidden service authorized-client message from DEBUG to
2151 INFO. Closes ticket 14015.
2153 o Minor features (stability):
2154 - Add assertions in our hash-table iteration code to check for
2155 corrupted values that could cause infinite loops. Closes
2158 o Minor features (systemd):
2159 - Various improvements and modernizations in systemd hardening
2160 support. Closes ticket 13805. Patch from Craig Andrews.
2162 o Minor features (testing networks):
2163 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
2164 and the default on a testing network to 2 minutes. Drop the
2165 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
2166 keep the default on a testing network at 30 seconds. This reduces
2167 HS bootstrap time to around 25 seconds. Also, change the default
2168 time in test-network.sh to match. Closes ticket 13401. Patch
2170 - Create TestingDirAuthVoteHSDir to correspond to
2171 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
2172 HSDir flag for the listed relays regardless of uptime or ORPort
2173 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
2174 Partial implementation for ticket 14067. Patch by "teor".
2176 o Minor features (tor2web mode):
2177 - Introduce the config option Tor2webRendezvousPoints, which allows
2178 clients in Tor2webMode to select a specific Rendezvous Point to be
2179 used in HS circuits. This might allow better performance for
2180 Tor2Web nodes. Implements ticket 12844.
2182 o Minor bugfixes (client DNS):
2183 - Report the correct cached DNS expiration times on SOCKS port or in
2184 DNS replies. Previously, we would report everything as "never
2185 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
2186 - Avoid a small memory leak when we find a cached answer for a
2187 reverse DNS lookup in a client-side DNS cache. (Remember, client-
2188 side DNS caching is off by default, and is not recommended.) Fixes
2189 bug 14259; bugfix on 0.2.0.1-alpha.
2191 o Minor bugfixes (client, automapping):
2192 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2193 no value follows the option. Fixes bug 14142; bugfix on
2194 0.2.4.7-alpha. Patch by "teor".
2195 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2196 14195; bugfix on 0.1.0.1-rc.
2197 - Prevent changes to other options from removing the wildcard value
2198 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
2200 - Allow MapAddress and AutomapHostsOnResolve to work together when
2201 an address is mapped into another address type (like .onion) that
2202 must be automapped at resolve time. Fixes bug 7555; bugfix
2205 o Minor bugfixes (client, bridges):
2206 - When we are using bridges and we had a network connectivity
2207 problem, only retry connecting to our currently configured
2208 bridges, not all bridges we know about and remember using. Fixes
2209 bug 14216; bugfix on 0.2.2.17-alpha.
2211 o Minor bugfixes (client, IPv6):
2212 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
2213 flag is not set; and not because the NoIPv4Traffic flag was set.
2214 Previously we'd looked at the NoIPv4Traffic flag for both types of
2215 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
2217 o Minor bugfixes (compilation):
2218 - The address of an array in the middle of a structure will always
2219 be non-NULL. clang recognises this and complains. Disable the
2220 tautologous and redundant check to silence this warning. Fixes bug
2221 14001; bugfix on 0.2.1.2-alpha.
2222 - Avoid warnings when building with systemd 209 or later. Fixes bug
2223 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
2224 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
2225 Addresses ticket 14188.
2226 - Build without warnings with the stock OpenSSL srtp.h header, which
2227 has a duplicate declaration of SSL_get_selected_srtp_profile().
2228 Fixes bug 14220; this is OpenSSL's bug, not ours.
2229 - Do not compile any code related to Tor2Web mode when Tor2Web mode
2230 is not enabled at compile time. Previously, this code was included
2231 in a disabled state. See discussion on ticket 12844.
2232 - Remove the --disable-threads configure option again. It was
2233 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
2234 14819; bugfix on 0.2.6.2-alpha.
2236 o Minor bugfixes (controller):
2237 - Report "down" in response to the "GETINFO entry-guards" command
2238 when relays are down with an unreachable_since value. Previously,
2239 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
2240 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
2241 14116; bugfix on 0.2.2.9-alpha.
2242 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
2243 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
2245 o Minor bugfixes (directory authority):
2246 - Allow directory authorities to fetch more data from one another if
2247 they find themselves missing lots of votes. Previously, they had
2248 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2249 bugfix on 0.1.2.5-alpha.
2250 - Do not attempt to download extrainfo documents which we will be
2251 unable to validate with a matching server descriptor. Fixes bug
2252 13762; bugfix on 0.2.0.1-alpha.
2253 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
2254 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
2255 - Enlarge the buffer to read bwauth generated files to avoid an
2256 issue when parsing the file in dirserv_read_measured_bandwidths().
2257 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2259 o Minor bugfixes (file handling):
2260 - Stop failing when key files are zero-length. Instead, generate new
2261 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
2262 on all versions of Tor. Patch by "teor".
2263 - Stop generating a fresh .old RSA onion key file when the .old file
2264 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
2265 - Avoid overwriting .old key files with empty key files.
2266 - Skip loading zero-length extrainfo store, router store, stats,
2267 state, and key files.
2268 - Avoid crashing when trying to reload a torrc specified as a
2269 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
2272 o Minor bugfixes (hidden services):
2273 - Close the introduction circuit when we have no more usable intro
2274 points, instead of waiting for it to time out. This also ensures
2275 that no follow-up HS descriptor fetch is triggered when the
2276 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
2277 - When fetching a hidden service descriptor for a down service that
2278 was recently up, do not keep refetching until we try the same
2279 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
2280 - Successfully launch Tor with a nonexistent hidden service
2281 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
2282 14106; bugfix on 0.2.6.2-alpha.
2284 o Minor bugfixes (logging):
2285 - Avoid crashing when there are more log domains than entries in
2286 domain_list. Bugfix on 0.2.3.1-alpha.
2287 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
2289 - Don't log messages to stdout twice when starting up. Fixes bug
2290 13993; bugfix on 0.2.6.1-alpha.
2292 o Minor bugfixes (parsing):
2293 - Stop accepting milliseconds (or other junk) at the end of
2294 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
2295 - Support two-number and three-number version numbers correctly, in
2296 case we change the Tor versioning system in the future. Fixes bug
2297 13661; bugfix on 0.0.8pre1.
2299 o Minor bugfixes (path counting):
2300 - When deciding whether the consensus lists any exit nodes, count
2301 the number listed in the consensus, not the number we have
2302 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
2303 - When deciding whether we have any exit nodes, only examine
2304 ExitNodes when the ExitNodes option is actually set. Fixes part of
2305 bug 14918; bugfix on 0.2.6.2-alpha.
2306 - Get rid of redundant and possibly scary warnings that we are
2307 missing directory information while we bootstrap. Fixes part of
2308 bug 14918; bugfix on 0.2.6.2-alpha.
2310 o Minor bugfixes (portability):
2311 - Fix the ioctl()-based network interface lookup code so that it
2312 will work on systems that have variable-length struct ifreq, for
2314 - Fix scheduler compilation on targets where char is unsigned. Fixes
2315 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
2317 o Minor bugfixes (sandbox):
2318 - Allow glibc fatal errors to be sent to stderr before Tor exits.
2319 Previously, glibc would try to write them to /dev/tty, and the
2320 sandbox would trap the call and make Tor exit prematurely. Fixes
2321 bug 14759; bugfix on 0.2.5.1-alpha.
2323 o Minor bugfixes (shutdown):
2324 - When shutting down, always call event_del() on lingering read or
2325 write events before freeing them. Otherwise, we risk double-frees
2326 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
2329 o Minor bugfixes (small memory leaks):
2330 - Avoid leaking memory when using IPv6 virtual address mappings.
2331 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
2334 o Minor bugfixes (statistics):
2335 - Increase period over which bandwidth observations are aggregated
2336 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2338 o Minor bugfixes (systemd support):
2339 - Fix detection and operation of systemd watchdog. Fixes part of bug
2340 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
2341 - Run correctly under systemd with the RunAsDaemon option set. Fixes
2342 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
2343 - Inform the systemd supervisor about more changes in the Tor
2344 process status. Implements part of ticket 14141. Patch from
2346 - Cause the "--disable-systemd" option to actually disable systemd
2347 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
2350 o Minor bugfixes (TLS):
2351 - Check more thoroughly throughout the TLS code for possible
2352 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
2354 o Minor bugfixes (transparent proxy):
2355 - Use getsockname, not getsockopt, to retrieve the address for a
2356 TPROXY-redirected connection. Fixes bug 13796; bugfix
2359 o Code simplification and refactoring:
2360 - Move fields related to isolating and configuring client ports into
2361 a shared structure. Previously, they were duplicated across
2362 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
2363 to copy them correctly had been the cause of at least one bug in
2364 the past. Closes ticket 8546.
2365 - Refactor the get_interface_addresses_raw() doom-function into
2366 multiple smaller and simpler subfunctions. Cover the resulting
2367 subfunctions with unit-tests. Fixes a significant portion of
2369 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
2370 only for version <= 0.2.2.24 which is now deprecated. Closes
2372 - Remove a test for a long-defunct broken version-one
2376 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
2377 for writing the OpenBSD-specific tips. Resolves ticket 13702.
2378 - Make the tor-resolve documentation match its help string and its
2379 options. Resolves part of ticket 14325.
2380 - Log a more useful error message from tor-resolve when failing to
2381 look up a hidden service address. Resolves part of ticket 14325.
2383 o Downgraded warnings:
2384 - Don't warn when we've attempted to contact a relay using the wrong
2385 ntor onion key. Closes ticket 9635.
2388 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
2389 longer silently accepted as an alias for "ExitNodes".
2390 - The --enable-mempool and --enable-buf-freelists options, which
2391 were originally created to work around bad malloc implementations,
2392 no longer exist. They were off-by-default in 0.2.5. Closes
2396 - Make the checkdir/perms test complete successfully even if the
2397 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
2398 - Test that tor does not fail when key files are zero-length. Check
2399 that tor generates new keys, and overwrites the empty key files.
2400 - Test that tor generates new keys when keys are missing
2401 (existing behavior).
2402 - Test that tor does not overwrite key files that already contain
2403 data (existing behavior). Tests bug 13111. Patch by "teor".
2404 - New "make test-stem" target to run stem integration tests.
2405 Requires that the "STEM_SOURCE_DIR" environment variable be set.
2406 Closes ticket 14107.
2407 - Make the test_cmdline_args.py script work correctly on Windows.
2408 Patch from Gisle Vanem.
2409 - Move the slower unit tests into a new "./src/test/test-slow"
2410 binary that can be run independently of the other tests. Closes
2412 - Avoid undefined behavior when sampling huge values from the
2413 Laplace distribution. This made unittests fail on Raspberry Pi.
2414 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
2417 Changes in version 0.2.6.2-alpha - 2014-12-31
2418 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
2419 It introduces a major new backend for deciding when to send cells on
2420 channels, which should lead down the road to big performance
2421 increases. It contains security and statistics features for better
2422 work on hidden services, and numerous bugfixes.
2424 This release contains many new unit tests, along with major
2425 performance improvements for running testing networks using Chutney.
2426 Thanks to a series of patches contributed by "teor", testing networks
2427 should now bootstrap in seconds, rather than minutes.
2429 o Major features (relay, infrastructure):
2430 - Complete revision of the code that relays use to decide which cell
2431 to send next. Formerly, we selected the best circuit to write on
2432 each channel, but we didn't select among channels in any
2433 sophisticated way. Now, we choose the best circuits globally from
2434 among those whose channels are ready to deliver traffic.
2436 This patch implements a new inter-cmux comparison API, a global
2437 high/low watermark mechanism and a global scheduler loop for
2438 transmission prioritization across all channels as well as among
2439 circuits on one channel. This schedule is currently tuned to
2440 (tolerantly) avoid making changes in network performance, but it
2441 should form the basis for major circuit performance increases in
2442 the future. Code by Andrea; tuning by Rob Jansen; implements
2445 o Major features (hidden services):
2446 - Make HS port scanning more difficult by immediately closing the
2447 circuit when a user attempts to connect to a nonexistent port.
2448 Closes ticket 13667.
2449 - Add a HiddenServiceStatistics option that allows Tor relays to
2450 gather and publish statistics about the overall size and volume of
2451 hidden service usage. Specifically, when this option is turned on,
2452 an HSDir will publish an approximate number of hidden services
2453 that have published descriptors to it the past 24 hours. Also, if
2454 a relay has acted as a hidden service rendezvous point, it will
2455 publish the approximate amount of rendezvous cells it has relayed
2456 the past 24 hours. The statistics themselves are obfuscated so
2457 that the exact values cannot be derived. For more details see
2458 proposal 238, "Better hidden service stats from Tor relays". This
2459 feature is currently disabled by default. Implements feature 13192.
2461 o Major bugfixes (client, automap):
2462 - Repair automapping with IPv6 addresses. This automapping should
2463 have worked previously, but one piece of debugging code that we
2464 inserted to detect a regression actually caused the regression to
2465 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
2466 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
2469 o Major bugfixes (hidden services):
2470 - When closing an introduction circuit that was opened in parallel
2471 with others, don't mark the introduction point as unreachable.
2472 Previously, the first successful connection to an introduction
2473 point would make the other introduction points get marked as
2474 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
2476 o Directory authority changes:
2477 - Remove turtles as a directory authority.
2478 - Add longclaw as a new (v3) directory authority. This implements
2479 ticket 13296. This keeps the directory authority count at 9.
2481 o Major removed features:
2482 - Tor clients no longer support connecting to hidden services
2483 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
2484 option has been removed. (There shouldn't be any hidden services
2485 running these versions on the network.) Closes ticket 7803.
2487 o Minor features (client):
2488 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
2489 is enabled, reject requests with IP addresses as hostnames.
2490 Resolves ticket 13315.
2492 o Minor features (controller):
2493 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
2494 write an unscheduled heartbeat message to the log. Implements
2497 o Minor features (geoip):
2498 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
2501 o Minor features (hidden services):
2502 - When re-enabling the network, don't try to build introduction
2503 circuits until we have successfully built a circuit. This makes
2504 hidden services come up faster when the network is re-enabled.
2505 Patch from "akwizgran". Closes ticket 13447.
2506 - When we fail to retrieve a hidden service descriptor, send the
2507 controller an "HS_DESC FAILED" controller event. Implements
2509 - New HiddenServiceDirGroupReadable option to cause hidden service
2510 directories and hostname files to be created group-readable. Patch
2511 from "anon", David Stainton, and "meejah". Closes ticket 11291.
2513 o Minor features (systemd):
2514 - Where supported, when running with systemd, report successful
2515 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
2516 - When running with systemd, support systemd watchdog messages. Part
2517 of ticket 11016. Patch by Michael Scherer.
2519 o Minor features (transparent proxy):
2520 - Update the transparent proxy option checks to allow for both ipfw
2521 and pf on OS X. Closes ticket 14002.
2522 - Use the correct option when using IPv6 with transparent proxy
2523 support on Linux. Resolves 13808. Patch by Francisco Blas
2526 o Minor bugfixes (preventative security, C safety):
2527 - When reading a hexadecimal, base-32, or base-64 encoded value from
2528 a string, always overwrite the whole output buffer. This prevents
2529 some bugs where we would look at (but fortunately, not reveal)
2530 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2532 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
2533 just the part that's used. This makes it harder for data leak bugs
2534 to occur in the event of other programming failures. Resolves
2537 o Minor bugfixes (client, microdescriptors):
2538 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
2539 computing which microdescriptors to download. This keeps us from
2540 erroneous download behavior if two microdescriptor digests ever
2541 have the same first 160 bits. Fixes part of bug 13399; bugfix
2543 - Reset a router's status if its microdescriptor digest changes,
2544 even if the first 160 bits remain the same. Fixes part of bug
2545 13399; bugfix on 0.2.3.1-alpha.
2547 o Minor bugfixes (compilation):
2548 - Silence clang warnings under --enable-expensive-hardening,
2549 including implicit truncation of 64 bit values to 32 bit, const
2550 char assignment to self, tautological compare, and additional
2551 parentheses around equality tests. Fixes bug 13577; bugfix
2553 - Fix a clang warning about checking whether an address in the
2554 middle of a structure is NULL. Fixes bug 14001; bugfix
2557 o Minor bugfixes (hidden services):
2558 - Correctly send a controller event when we find that a rendezvous
2559 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
2560 - Pre-check directory permissions for new hidden-services to avoid
2561 at least one case of "Bug: Acting on config options left us in a
2562 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
2563 - When adding a new hidden service (for example, via SETCONF), Tor
2564 no longer congratulates the user for running a relay. Fixes bug
2565 13941; bugfix on 0.2.6.1-alpha.
2566 - When fetching hidden service descriptors, we now check not only
2567 for whether we got the hidden service we had in mind, but also
2568 whether we got the particular descriptors we wanted. This prevents
2569 a class of inefficient but annoying DoS attacks by hidden service
2570 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
2573 o Minor bugfixes (Linux seccomp2 sandbox):
2574 - Make transparent proxy support work along with the seccomp2
2575 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
2576 by Francisco Blas Izquierdo Riera.
2577 - Fix a memory leak in tor-resolve when running with the sandbox
2578 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
2580 o Minor bugfixes (logging):
2581 - Downgrade warnings about RSA signature failures to info log level.
2582 Emit a warning when an extra info document is found incompatible
2583 with a corresponding router descriptor. Fixes bug 9812; bugfix
2585 - Make connection_ap_handshake_attach_circuit() log the circuit ID
2586 correctly. Fixes bug 13701; bugfix on 0.0.6.
2588 o Minor bugfixes (misc):
2589 - Stop allowing invalid address patterns like "*/24" that contain
2590 both a wildcard address and a bit prefix length. This affects all
2591 our address-range parsing code. Fixes bug 7484; bugfix
2594 o Minor bugfixes (testing networks, fast startup):
2595 - Allow Tor to build circuits using a consensus with no exits. If
2596 the consensus has no exits (typical of a bootstrapping test
2597 network), allow Tor to build circuits once enough descriptors have
2598 been downloaded. This assists in bootstrapping a testing Tor
2599 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
2601 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
2602 header to directory servers. This allows us to obtain consensuses
2603 promptly when the consensus interval is very short. This assists
2604 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
2605 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
2606 - Stop assuming that private addresses are local when checking
2607 reachability in a TestingTorNetwork. Instead, when testing, assume
2608 all OR connections are remote. (This is necessary due to many test
2609 scenarios running all relays on localhost.) This assists in
2610 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
2611 0.1.0.1-rc. Patch by "teor".
2612 - Avoid building exit circuits from a consensus with no exits. Now
2613 thanks to our fix for 13718, we accept a no-exit network as not
2614 wholly lost, but we need to remember not to try to build exit
2615 circuits on it. Closes ticket 13814; patch by "teor".
2616 - Stop requiring exits to have non-zero bandwithcapacity in a
2617 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
2618 ignore exit bandwidthcapacity. This assists in bootstrapping a
2619 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
2620 on 0.2.0.3-alpha. Patch by "teor".
2621 - Add "internal" to some bootstrap statuses when no exits are
2622 available. If the consensus does not contain Exits, Tor will only
2623 build internal circuits. In this case, relevant statuses will
2624 contain the word "internal" as indicated in the Tor control-
2625 spec.txt. When bootstrap completes, Tor will be ready to build
2626 internal circuits. If a future consensus contains Exits, exit
2627 circuits may become available. Fixes part of bug 13718; bugfix on
2628 0.2.4.10-alpha. Patch by "teor".
2629 - Decrease minimum consensus interval to 10 seconds when
2630 TestingTorNetwork is set, or 5 seconds for the first consensus.
2631 Fix assumptions throughout the code that assume larger intervals.
2632 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
2634 - Avoid excluding guards from path building in minimal test
2635 networks, when we're in a test network and excluding guards would
2636 exclude all relays. This typically occurs in incredibly small tor
2637 networks, and those using "TestingAuthVoteGuard *". Fixes part of
2638 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
2640 o Code simplification and refactoring:
2641 - Stop using can_complete_circuits as a global variable; access it
2642 with a function instead.
2643 - Avoid using operators directly as macro arguments: this lets us
2644 apply coccinelle transformations to our codebase more directly.
2645 Closes ticket 13172.
2646 - Combine the functions used to parse ClientTransportPlugin and
2647 ServerTransportPlugin into a single function. Closes ticket 6456.
2648 - Add inline functions and convenience macros for inspecting channel
2649 state. Refactor the code to use convenience macros instead of
2650 checking channel state directly. Fixes issue 7356.
2651 - Document all members of was_router_added_t and rename
2652 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
2653 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
2654 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
2655 constant instead of hardcoded value. Fixes issue 13840.
2656 - Refactor our generic strmap and digestmap types into a single
2657 implementation, so that we can add a new digest256map
2661 - Document the bridge-authority-only 'networkstatus-bridges' file.
2662 Closes ticket 13713; patch from "tom".
2663 - Fix typo in PredictedPortsRelevanceTime option description in
2664 manpage. Resolves issue 13707.
2665 - Stop suggesting that users specify relays by nickname: it isn't a
2666 good idea. Also, properly cross-reference how to specify relays in
2667 all parts of manual documenting options that take a list of
2668 relays. Closes ticket 13381.
2669 - Clarify the HiddenServiceDir option description in manpage to make
2670 it clear that relative paths are taken with respect to the current
2671 working directory. Also clarify that this behavior is not
2672 guaranteed to remain indefinitely. Fixes issue 13913.
2675 - New tests for many parts of channel, relay, and circuitmux
2676 functionality. Code by Andrea; part of 9262.
2677 - New tests for parse_transport_line(). Part of ticket 6456.
2678 - In the unit tests, use chgrp() to change the group of the unit
2679 test temporary directory to the current user, so that the sticky
2680 bit doesn't interfere with tests that check directory groups.
2682 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
2686 Changes in version 0.2.6.1-alpha - 2014-10-30
2687 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
2688 includes numerous code cleanups and new tests, and fixes a large
2689 number of annoying bugs. Out-of-memory conditions are handled better
2690 than in 0.2.5, pluggable transports have improved proxy support, and
2691 clients now use optimistic data for contacting hidden services. Also,
2692 we are now more robust to changes in what we consider a parseable
2693 directory object, so that tightening restrictions does not have a risk
2694 of introducing infinite download loops.
2696 This is the first alpha release in a new series, so expect there to be
2697 bugs. Users who would rather test out a more stable branch should stay
2698 with 0.2.5.x for now.
2700 o New compiler and system requirements:
2701 - Tor 0.2.6.x requires that your compiler support more of the C99
2702 language standard than before. The 'configure' script now detects
2703 whether your compiler supports C99 mid-block declarations and
2704 designated initializers. If it does not, Tor will not compile.
2706 We may revisit this requirement if it turns out that a significant
2707 number of people need to build Tor with compilers that don't
2708 bother implementing a 15-year-old standard. Closes ticket 13233.
2709 - Tor no longer supports systems without threading support. When we
2710 began working on Tor, there were several systems that didn't have
2711 threads, or where the thread support wasn't able to run the
2712 threads of a single process on multiple CPUs. That no longer
2713 holds: every system where Tor needs to run well now has threading
2714 support. Resolves ticket 12439.
2716 o Removed platform support:
2717 - We no longer include special code to build on Windows CE; as far
2718 as we know, nobody has used Tor on Windows CE in a very long time.
2719 Closes ticket 11446.
2721 o Major features (bridges):
2722 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2723 transports if they are configured via the "TOR_PT_PROXY"
2724 environment variable. Implements proposal 232. Resolves
2727 o Major features (client performance, hidden services):
2728 - Allow clients to use optimistic data when connecting to a hidden
2729 service, which should remove a round-trip from hidden service
2730 initialization. See proposal 181 for details. Implements
2733 o Major features (directory system):
2734 - Upon receiving an unparseable directory object, if its digest
2735 matches what we expected, then don't try to download it again.
2736 Previously, when we got a descriptor we didn't like, we would keep
2737 trying to download it over and over. Closes ticket 11243.
2739 o Major features (sample torrc):
2740 - Add a new, infrequently-changed "torrc.minimal". This file is
2741 similar to torrc.sample, but it will change as infrequently as
2742 possible, for the benefit of users whose systems prompt them for
2743 intervention whenever a default configuration file is changed.
2744 Making this change allows us to update torrc.sample to be a more
2745 generally useful "sample torrc".
2747 o Major bugfixes (directory authorities):
2748 - Do not assign the HSDir flag to relays if they are not Valid, or
2749 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2751 o Major bugfixes (directory bandwidth performance):
2752 - Don't flush the zlib buffer aggressively when compressing
2753 directory information for clients. This should save about 7% of
2754 the bandwidth currently used for compressed descriptors and
2755 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2757 o Minor features (security, memory wiping):
2758 - Ensure we securely wipe keys from memory after
2759 crypto_digest_get_digest and init_curve25519_keypair_from_file
2760 have finished using them. Resolves ticket 13477.
2762 o Minor features (security, out-of-memory handling):
2763 - When handling an out-of-memory condition, allocate less memory for
2764 temporary data structures. Fixes issue 10115.
2765 - When handling an out-of-memory condition, consider more types of
2766 buffers, including those on directory connections, and zlib
2767 buffers. Resolves ticket 11792.
2770 - When identity keypair is generated for first time, log a
2771 congratulatory message that links to the new relay lifecycle
2772 document. Implements feature 10427.
2774 o Minor features (client):
2775 - Clients are now willing to send optimistic data (before they
2776 receive a 'connected' cell) to relays of any version. (Relays
2777 without support for optimistic data are no longer supported on the
2778 Tor network.) Resolves ticket 13153.
2780 o Minor features (directory authorities):
2781 - Don't list relays with a bandwidth estimate of 0 in the consensus.
2782 Implements a feature proposed during discussion of bug 13000.
2783 - In tor-gencert, report an error if the user provides the same
2784 argument more than once.
2785 - If a directory authority can't find a best consensus method in the
2786 votes that it holds, it now falls back to its favorite consensus
2787 method. Previously, it fell back to method 1. Neither of these is
2788 likely to get enough signatures, but "fall back to favorite"
2789 doesn't require us to maintain support an obsolete consensus
2790 method. Implements part of proposal 215.
2792 o Minor features (logging):
2793 - On Unix-like systems, you can now use named pipes as the target of
2794 the Log option, and other options that try to append to files.
2795 Closes ticket 12061. Patch from "carlo von lynX".
2796 - When opening a log file at startup, send it every log message that
2797 we generated between startup and opening it. Previously, log
2798 messages that were generated before opening the log file were only
2799 logged to stdout. Closes ticket 6938.
2800 - Add a TruncateLogFile option to overwrite logs instead of
2801 appending to them. Closes ticket 5583.
2803 o Minor features (portability, Solaris):
2804 - Threads are no longer disabled by default on Solaris; we believe
2805 that the versions of Solaris with broken threading support are all
2806 obsolete by now. Resolves ticket 9495.
2808 o Minor features (relay):
2809 - Re-check our address after we detect a changed IP address from
2810 getsockname(). This ensures that the controller command "GETINFO
2811 address" will report the correct value. Resolves ticket 11582.
2813 - A new AccountingRule option lets Relays set whether they'd like
2814 AccountingMax to be applied separately to inbound and outbound
2815 traffic, or applied to the sum of inbound and outbound traffic.
2816 Resolves ticket 961. Patch by "chobe".
2818 o Minor features (testing networks):
2819 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
2820 the "Exit" flag regardless of their uptime, bandwidth, or exit
2821 policy. TestingTorNetwork must be set for this option to have any
2822 effect. Previously, authorities would take up to 35 minutes to
2823 give nodes the Exit flag in a test network. Partially implements
2826 o Minor features (validation):
2827 - Check all date/time values passed to tor_timegm and
2828 parse_rfc1123_time for validity, taking leap years into account.
2829 Improves HTTP header validation. Implemented with bug 13476.
2830 - In correct_tm(), limit the range of values returned by system
2831 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
2832 This means we don't have to deal with negative or too large dates,
2833 even if a clock is wrong. Otherwise we might fail to read a file
2834 written by us which includes such a date. Fixes bug 13476.
2836 o Minor bugfixes (bridge clients):
2837 - When configured to use a bridge without an identity digest (not
2838 recommended), avoid launching an extra channel to it when
2839 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
2841 o Minor bugfixes (bridges):
2842 - When DisableNetwork is set, do not launch pluggable transport
2843 plugins, and if any are running, terminate them. Fixes bug 13213;
2844 bugfix on 0.2.3.6-alpha.
2846 o Minor bugfixes (C correctness):
2847 - Fix several instances of possible integer overflow/underflow/NaN.
2848 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
2850 - In circuit_build_times_calculate_timeout() in circuitstats.c,
2851 avoid dividing by zero in the pareto calculations. This traps
2852 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2854 - Fix an integer overflow in format_time_interval(). Fixes bug
2855 13393; bugfix on 0.2.0.10-alpha.
2856 - Set the correct day of year value when the system's localtime(_r)
2857 or gmtime(_r) functions fail to set struct tm. Not externally
2858 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2859 - Avoid unlikely signed integer overflow in tor_timegm on systems
2860 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2862 o Minor bugfixes (client):
2863 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2864 BadExit flag are not considered worthy candidates. Fixes bug
2865 13066; bugfix on 0.1.2.3-alpha.
2866 - Use the consensus schedule for downloading consensuses, and not
2867 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2868 - Handle unsupported or malformed SOCKS5 requests properly by
2869 responding with the appropriate error message before closing the
2870 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2872 o Minor bugfixes (client, torrc):
2873 - Stop modifying the value of our DirReqStatistics torrc option just
2874 because we're not a bridge or relay. This bug was causing Tor
2875 Browser users to write "DirReqStatistics 0" in their torrc files
2876 as if they had chosen to change the config. Fixes bug 4244; bugfix
2878 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
2879 that our options have changed every time we SIGHUP. Fixes bug
2880 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
2882 o Minor bugfixes (controller):
2883 - Return an error when the second or later arguments of the
2884 "setevents" controller command are invalid events. Previously we
2885 would return success while silently skipping invalid events. Fixes
2886 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
2888 o Minor bugfixes (directory system):
2889 - Always believe that v3 directory authorities serve extra-info
2890 documents, whether they advertise "caches-extra-info" or not.
2891 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2892 - When running as a v3 directory authority, advertise that you serve
2893 extra-info documents so that clients who want them can find them
2894 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2895 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
2896 Previously, directories offering BRIDGE_DIRINFO and some other
2897 flag (i.e. microdescriptors or extrainfo) would be ignored when
2898 looking for bridges. Partially fixes bug 13163; bugfix
2901 o Minor bugfixes (networking):
2902 - Check for orconns and use connection_or_close_for_error() rather
2903 than connection_mark_for_close() directly in the getsockopt()
2904 failure case of connection_handle_write_impl(). Fixes bug 11302;
2905 bugfix on 0.2.4.4-alpha.
2907 o Minor bugfixes (relay):
2908 - When generating our family list, remove spaces from around the
2909 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
2910 - If our previous bandwidth estimate was 0 bytes, allow publishing a
2911 new relay descriptor immediately. Fixes bug 13000; bugfix
2914 o Minor bugfixes (testing networks):
2915 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
2916 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
2917 - Stop using the default authorities in networks which provide both
2918 AlternateDirAuthority and AlternateBridgeAuthority. Partially
2919 fixes bug 13163; bugfix on 0.2.0.13-alpha.
2921 o Minor bugfixes (testing):
2922 - Stop spawn test failures due to a race condition between the
2923 SIGCHLD handler updating the process status, and the test reading
2924 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
2926 o Minor bugfixes (testing, Windows):
2927 - Avoid passing an extra backslash when creating a temporary
2928 directory for running the unit tests on Windows. Fixes bug 12392;
2929 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
2931 o Minor bugfixes (windows):
2932 - Remove code to special-case handling of NTE_BAD_KEYSET when
2933 acquiring windows CryptoAPI context. This error can't actually
2934 occur for the parameters we're providing. Fixes bug 10816; bugfix
2937 o Minor bugfixes (zlib):
2938 - Avoid truncating a zlib stream when trying to finalize it with an
2939 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
2942 - Allow our configure script to build correctly with autoconf 2.62
2943 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
2944 - Improve the error message from ./configure to make it clear that
2945 when asciidoc has not been found, the user will have to either add
2946 --disable-asciidoc argument or install asciidoc. Resolves
2949 o Code simplification and refactoring:
2950 - Change the entry_is_live() function to take named bitfield
2951 elements instead of an unnamed list of booleans. Closes
2953 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
2954 Resolves ticket 12205.
2955 - Use calloc and reallocarray functions instead of multiply-
2956 then-malloc. This makes it less likely for us to fall victim to an
2957 integer overflow attack when allocating. Resolves ticket 12855.
2958 - Use the standard macro name SIZE_MAX, instead of our
2960 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
2961 functions which take them as arguments. Replace 0 with NO_DIRINFO
2962 in a function call for clarity. Seeks to prevent future issues
2964 - Avoid 4 null pointer errors under clang static analysis by using
2965 tor_assert() to prove that the pointers aren't null. Fixes
2967 - Rework the API of policies_parse_exit_policy() to use a bitmask to
2968 represent parsing options, instead of a confusing mess of
2969 booleans. Resolves ticket 8197.
2970 - Introduce a helper function to parse ExitPolicy in
2971 or_options_t structure.
2974 - Add a doc/TUNING document with tips for handling large numbers of
2975 TCP connections when running busy Tor relay. Update the warning
2976 message to point to this file when running out of sockets
2977 operating system is allowing to use simultaneously. Resolves
2981 - We no longer remind the user about configuration options that have
2982 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
2983 - Remove our old, non-weighted bandwidth-based node selection code.
2984 Previously, we used it as a fallback when we couldn't perform
2985 weighted bandwidth-based node selection. But that would only
2986 happen in the cases where we had no consensus, or when we had a
2987 consensus generated by buggy or ancient directory authorities. In
2988 either case, it's better to use the more modern, better maintained
2989 algorithm, with reasonable defaults for the weights. Closes
2991 - Remove the --disable-curve25519 configure option. Relays and
2992 clients now are required to support curve25519 and the
2994 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
2995 used to be deprecated synonyms for "StrictNodes", are now marked
2996 obsolete. Resolves ticket 12226.
2997 - Clients don't understand the BadDirectory flag in the consensus
2998 anymore, and ignore it.
3001 - Refactor the function that chooses guard nodes so that it can more
3002 easily be tested; write some tests for it.
3003 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3004 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3005 - Create unit tests for format_time_interval(). With bug 13393.
3006 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3007 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3008 tests (visible) fixes in bug 13476.
3009 - Add a "coverage-html" make target to generate HTML-visualized
3010 coverage results when building with --enable-coverage. (Requires
3011 lcov.) Patch from Kevin Murray.
3012 - Enable the backtrace handler (where supported) when running the
3014 - Revise all unit tests that used the legacy test_* macros to
3015 instead use the recommended tt_* macros. This patch was generated
3016 with coccinelle, to avoid manual errors. Closes ticket 13119.
3018 o Distribution (systemd):
3019 - systemd unit file: only allow tor to write to /var/lib/tor and
3020 /var/log/tor. The rest of the filesystem is accessible for reading
3021 only. Patch by intrigeri; resolves ticket 12751.
3022 - systemd unit file: ensure that the process and all its children
3023 can never gain new privileges. Patch by intrigeri; resolves
3025 - systemd unit file: set up /var/run/tor as writable for the Tor
3026 service. Patch by intrigeri; resolves ticket 13196.
3028 o Removed features (directory authorities):
3029 - Remove code that prevented authorities from listing Tor relays
3030 affected by CVE-2011-2769 as guards. These relays are already
3031 rejected altogether due to the minimum version requirement of
3032 0.2.3.16-alpha. Closes ticket 13152.
3033 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3034 the fingerprints file (approved-routers) has been deprecated.
3035 - Directory authorities do not support being Naming dirauths anymore.
3036 The "NamingAuthoritativeDir" config option is now obsolete.
3037 - Directory authorities do not support giving out the BadDirectory
3039 - Directory authorities no longer advertise or support consensus
3040 methods 1 through 12 inclusive. These consensus methods were
3041 obsolete and/or insecure: maintaining the ability to support them
3042 served no good purpose. Implements part of proposal 215; closes
3045 o Testing (test-network.sh):
3046 - Stop using "echo -n", as some shells' built-in echo doesn't
3047 support "-n". Instead, use "/bin/echo -n". Partially fixes
3049 - Stop an apparent test-network hang when used with make -j2. Fixes
3051 - Add a --delay option to test-network.sh, which configures the
3052 delay before the chutney network tests for data transmission.
3053 Partially implements ticket 13161.
3056 Changes in version 0.2.5.10 - 2014-10-24
3057 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
3059 It adds several new security features, including improved
3060 denial-of-service resistance for relays, new compiler hardening
3061 options, and a system-call sandbox for hardened installations on Linux
3062 (requires seccomp2). The controller protocol has several new features,
3063 resolving IPv6 addresses should work better than before, and relays
3064 should be a little more CPU-efficient. We've added support for more
3065 OpenBSD and FreeBSD transparent proxy types. We've improved the build
3066 system and testing infrastructure to allow unit testing of more parts
3067 of the Tor codebase. Finally, we've addressed several nagging pluggable
3068 transport usability issues, and included numerous other small bugfixes
3069 and features mentioned below.
3071 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
3072 have accumulated many known flaws; everyone should upgrade.
3074 o Deprecated versions:
3075 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
3076 attention for some while.
3079 Changes in version 0.2.5.9-rc - 2014-10-20
3080 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
3081 series. It disables SSL3 in response to the recent "POODLE" attack
3082 (even though POODLE does not affect Tor). It also works around a crash
3083 bug caused by some operating systems' response to the "POODLE" attack
3084 (which does affect Tor). It also contains a few miscellaneous fixes.
3086 o Major security fixes:
3087 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3088 today support TLS 1.0 or later, so we can safely turn off support
3089 for this old (and insecure) protocol. Fixes bug 13426.
3091 o Major bugfixes (openssl bug workaround):
3092 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3093 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3094 13471. This is a workaround for an OpenSSL bug.
3097 - Disable the sandbox name resolver cache when running tor-resolve:
3098 tor-resolve doesn't use the sandbox code, and turning it on was
3099 breaking attempts to do tor-resolve on a non-default server on
3100 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
3102 o Compilation fixes:
3103 - Build and run correctly on systems like OpenBSD-current that have
3104 patched OpenSSL to remove get_cipher_by_char and/or its
3105 implementations. Fixes issue 13325.
3107 o Downgraded warnings:
3108 - Downgrade the severity of the 'unexpected sendme cell from client'
3109 from 'warn' to 'protocol warning'. Closes ticket 8093.
3112 Changes in version 0.2.4.25 - 2014-10-20
3113 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
3114 (even though POODLE does not affect Tor). It also works around a crash
3115 bug caused by some operating systems' response to the "POODLE" attack
3116 (which does affect Tor).
3118 o Major security fixes (also in 0.2.5.9-rc):
3119 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3120 today support TLS 1.0 or later, so we can safely turn off support
3121 for this old (and insecure) protocol. Fixes bug 13426.
3123 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
3124 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3125 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3126 13471. This is a workaround for an OpenSSL bug.
3129 Changes in version 0.2.5.8-rc - 2014-09-22
3130 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
3131 series. It fixes a bug that affects consistency and speed when
3132 connecting to hidden services, and it updates the location of one of
3133 the directory authorities.
3136 - Clients now send the correct address for their chosen rendezvous
3137 point when trying to access a hidden service. They used to send
3138 the wrong address, which would still work some of the time because
3139 they also sent the identity digest of the rendezvous point, and if
3140 the hidden service happened to try connecting to the rendezvous
3141 point from a relay that already had a connection open to it,
3142 the relay would reuse that connection. Now connections to hidden
3143 services should be more robust and faster. Also, this bug meant
3144 that clients were leaking to the hidden service whether they were
3145 on a little-endian (common) or big-endian (rare) system, which for
3146 some users might have reduced their anonymity. Fixes bug 13151;
3147 bugfix on 0.2.1.5-alpha.
3149 o Directory authority changes:
3150 - Change IP address for gabelmoo (v3 directory authority).
3153 Changes in version 0.2.4.24 - 2014-09-22
3154 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
3155 connecting to hidden services, and it updates the location of one of
3156 the directory authorities.
3159 - Clients now send the correct address for their chosen rendezvous
3160 point when trying to access a hidden service. They used to send
3161 the wrong address, which would still work some of the time because
3162 they also sent the identity digest of the rendezvous point, and if
3163 the hidden service happened to try connecting to the rendezvous
3164 point from a relay that already had a connection open to it,
3165 the relay would reuse that connection. Now connections to hidden
3166 services should be more robust and faster. Also, this bug meant
3167 that clients were leaking to the hidden service whether they were
3168 on a little-endian (common) or big-endian (rare) system, which for
3169 some users might have reduced their anonymity. Fixes bug 13151;
3170 bugfix on 0.2.1.5-alpha.
3172 o Directory authority changes:
3173 - Change IP address for gabelmoo (v3 directory authority).
3175 o Minor features (geoip):
3176 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3180 Changes in version 0.2.5.7-rc - 2014-09-11
3181 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
3182 release series, and some long-standing bugs related to ORPort reachability
3183 testing and failure to send CREATE cells. It is the first release
3184 candidate for the Tor 0.2.5.x series.
3186 o Major bugfixes (client, startup):
3187 - Start making circuits as soon as DisabledNetwork is turned off.
3188 When Tor started with DisabledNetwork set, it would correctly
3189 conclude that it shouldn't build circuits, but it would mistakenly
3190 cache this conclusion, and continue believing it even when
3191 DisableNetwork is set to 0. Fixes the bug introduced by the fix
3192 for bug 11200; bugfix on 0.2.5.4-alpha.
3193 - Resume expanding abbreviations for command-line options. The fix
3194 for bug 4647 accidentally removed our hack from bug 586 that
3195 rewrote HashedControlPassword to __HashedControlSessionPassword
3196 when it appears on the commandline (which allowed the user to set
3197 her own HashedControlPassword in the torrc file while the
3198 controller generates a fresh session password for each run). Fixes
3199 bug 12948; bugfix on 0.2.5.1-alpha.
3200 - Warn about attempts to run hidden services and relays in the same
3201 process: that's probably not a good idea. Closes ticket 12908.
3203 o Major bugfixes (relay):
3204 - Avoid queuing or sending destroy cells for circuit ID zero when we
3205 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
3206 Found and fixed by "cypherpunks".
3207 - Fix ORPort reachability detection on relays running behind a
3208 proxy, by correctly updating the "local" mark on the controlling
3209 channel when changing the address of an or_connection_t after the
3210 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
3212 o Minor features (bridge):
3213 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
3214 cookie file for the ExtORPort g+r by default.
3216 o Minor features (geoip):
3217 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3220 o Minor bugfixes (logging):
3221 - Reduce the log severity of the "Pluggable transport proxy does not
3222 provide any needed transports and will not be launched." message,
3223 since Tor Browser includes several ClientTransportPlugin lines in
3224 its torrc-defaults file, leading every Tor Browser user who looks
3225 at her logs to see these notices and wonder if they're dangerous.
3226 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
3227 - Downgrade "Unexpected onionskin length after decryption" warning
3228 to a protocol-warn, since there's nothing relay operators can do
3229 about a client that sends them a malformed create cell. Resolves
3230 bug 12996; bugfix on 0.0.6rc1.
3231 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
3232 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
3233 - When logging information about an EXTEND2 or EXTENDED2 cell, log
3234 their names correctly. Fixes part of bug 12700; bugfix
3236 - When logging information about a relay cell whose command we don't
3237 recognize, log its command as an integer. Fixes part of bug 12700;
3238 bugfix on 0.2.1.10-alpha.
3239 - Escape all strings from the directory connection before logging
3240 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
3242 o Minor bugfixes (controller):
3243 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
3244 bug 12864; bugfix on 0.2.5.1-alpha.
3245 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
3246 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
3249 o Minor bugfixes (compilation):
3250 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
3251 bugfix on 0.2.5.5-alpha.
3252 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
3253 0.2.5.1-alpha. Patch from "NewEraCracker".
3254 - In routerlist_assert_ok(), don't take the address of a
3255 routerinfo's cache_info member unless that routerinfo is non-NULL.
3256 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
3257 - Fix a large number of false positive warnings from the clang
3258 analyzer static analysis tool. This should make real warnings
3259 easier for clang analyzer to find. Patch from "teor". Closes
3262 o Distribution (systemd):
3263 - Verify configuration file via ExecStartPre in the systemd unit
3264 file. Patch from intrigeri; resolves ticket 12730.
3265 - Explicitly disable RunAsDaemon in the systemd unit file. Our
3266 current systemd unit uses "Type = simple", so systemd does not
3267 expect tor to fork. If the user has "RunAsDaemon 1" in their
3268 torrc, then things won't work as expected. This is e.g. the case
3269 on Debian (and derivatives), since there we pass "--defaults-torrc
3270 /usr/share/tor/tor-service-defaults-torrc" (that contains
3271 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
3275 - Adjust the URLs in the README to refer to the new locations of
3276 several documents on the website. Fixes bug 12830. Patch from
3278 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
3282 Changes in version 0.2.5.6-alpha - 2014-07-28
3283 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
3284 risk from guard rotation, and fixes a variety of other issues to get
3285 us closer to a release candidate.
3287 o Major features (also in 0.2.4.23):
3288 - Make the number of entry guards configurable via a new
3289 NumEntryGuards consensus parameter, and the number of directory
3290 guards configurable via a new NumDirectoryGuards consensus
3291 parameter. Implements ticket 12688.
3293 o Major bugfixes (also in 0.2.4.23):
3294 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3295 implementation that caused incorrect results on 32-bit
3296 implementations when certain malformed inputs were used along with
3297 a small class of private ntor keys. This bug does not currently
3298 appear to allow an attacker to learn private keys or impersonate a
3299 Tor server, but it could provide a means to distinguish 32-bit Tor
3300 implementations from 64-bit Tor implementations. Fixes bug 12694;
3301 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3305 - Perform circuit cleanup operations even when circuit
3306 construction operations are disabled (because the network is
3307 disabled, or because there isn't enough directory information).
3308 Previously, when we were not building predictive circuits, we
3309 were not closing expired circuits either. Fixes bug 8387; bugfix on
3310 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
3311 became more strict about when we have "enough directory information
3315 - Authorities now assign the Guard flag to the fastest 25% of the
3316 network (it used to be the fastest 50%). Also raise the consensus
3317 weight that guarantees the Guard flag from 250 to 2000. For the
3318 current network, this results in about 1100 guards, down from 2500.
3319 This step paves the way for moving the number of entry guards
3320 down to 1 (proposal 236) while still providing reasonable expected
3321 performance for most users. Implements ticket 12690.
3322 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3324 - Slightly enhance the diagnostic message for bug 12184.
3326 o Minor bugfixes (also in 0.2.4.23):
3327 - Warn and drop the circuit if we receive an inbound 'relay early'
3328 cell. Those used to be normal to receive on hidden service circuits
3329 due to bug 1038, but the buggy Tor versions are long gone from
3330 the network so we can afford to resume watching for them. Resolves
3331 the rest of bug 1038; bugfix on 0.2.1.19.
3332 - Correct a confusing error message when trying to extend a circuit
3333 via the control protocol but we don't know a descriptor or
3334 microdescriptor for one of the specified relays. Fixes bug 12718;
3335 bugfix on 0.2.3.1-alpha.
3338 - Fix compilation when building with bufferevents enabled. (This
3339 configuration is still not expected to work, however.)
3340 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
3341 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
3343 - Compile correctly with builds and forks of OpenSSL (such as
3344 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
3345 0.2.1.1-alpha. Patch from "dhill".
3348 Changes in version 0.2.4.23 - 2014-07-28
3349 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3350 guard rotation, and also backports several important fixes from the
3351 Tor 0.2.5 alpha release series.
3354 - Clients now look at the "usecreatefast" consensus parameter to
3355 decide whether to use CREATE_FAST or CREATE cells for the first hop
3356 of their circuit. This approach can improve security on connections
3357 where Tor's circuit handshake is stronger than the available TLS
3358 connection security levels, but the tradeoff is more computational
3359 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3360 - Make the number of entry guards configurable via a new
3361 NumEntryGuards consensus parameter, and the number of directory
3362 guards configurable via a new NumDirectoryGuards consensus
3363 parameter. Implements ticket 12688.
3366 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3367 implementation that caused incorrect results on 32-bit
3368 implementations when certain malformed inputs were used along with
3369 a small class of private ntor keys. This bug does not currently
3370 appear to allow an attacker to learn private keys or impersonate a
3371 Tor server, but it could provide a means to distinguish 32-bit Tor
3372 implementations from 64-bit Tor implementations. Fixes bug 12694;
3373 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3377 - Warn and drop the circuit if we receive an inbound 'relay early'
3378 cell. Those used to be normal to receive on hidden service circuits
3379 due to bug 1038, but the buggy Tor versions are long gone from
3380 the network so we can afford to resume watching for them. Resolves
3381 the rest of bug 1038; bugfix on 0.2.1.19.
3382 - Correct a confusing error message when trying to extend a circuit
3383 via the control protocol but we don't know a descriptor or
3384 microdescriptor for one of the specified relays. Fixes bug 12718;
3385 bugfix on 0.2.3.1-alpha.
3386 - Avoid an illegal read from stack when initializing the TLS
3387 module using a version of OpenSSL without all of the ciphers
3388 used by the v2 link handshake. Fixes bug 12227; bugfix on
3389 0.2.4.8-alpha. Found by "starlight".
3392 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3396 Changes in version 0.2.5.5-alpha - 2014-06-18
3397 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
3398 0.2.5.x release series, including a couple of DoS issues, some
3399 performance regressions, a large number of bugs affecting the Linux
3400 seccomp2 sandbox code, and various other bugfixes. It also adds
3401 diagnostic bugfixes for a few tricky issues that we're trying to
3404 o Major features (security, traffic analysis resistance):
3405 - Several major improvements to the algorithm used to decide when to
3406 close TLS connections. Previous versions of Tor closed connections
3407 at a fixed interval after the last time a non-padding cell was
3408 sent over the connection, regardless of the target of the
3409 connection. Now, we randomize the intervals by adding up to 50% of
3410 their base value, we measure the length of time since connection
3411 last had at least one circuit, and we allow connections to known
3412 ORs to remain open a little longer (15 minutes instead of 3
3413 minutes minimum). These changes should improve Tor's resistance
3414 against some kinds of traffic analysis, and lower some overhead
3415 from needlessly closed connections. Fixes ticket 6799.
3416 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
3418 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
3419 - Fix a memory leak that could occur if a microdescriptor parse
3420 fails during the tokenizing step. This bug could enable a memory
3421 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3424 o Major bugfixes (security, directory authorities):
3425 - Directory authorities now include a digest of each relay's
3426 identity key as a part of its microdescriptor.
3428 This is a workaround for bug 11743 (reported by "cypherpunks"),
3429 where Tor clients do not support receiving multiple
3430 microdescriptors with the same SHA256 digest in the same
3431 consensus. When clients receive a consensus like this, they only
3432 use one of the relays. Without this fix, a hostile relay could
3433 selectively disable some client use of target relays by
3434 constructing a router descriptor with a different identity and the
3435 same microdescriptor parameters and getting the authorities to
3436 list it in a microdescriptor consensus. This fix prevents an
3437 attacker from causing a microdescriptor collision, because the
3438 router's identity is not forgeable.
3440 o Major bugfixes (relay):
3441 - Use a direct dirport connection when uploading non-anonymous
3442 descriptors to the directory authorities. Previously, relays would
3443 incorrectly use tunnel connections under a fairly wide variety of
3444 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
3445 - When a circuit accidentally has the same circuit ID for its
3446 forward and reverse direction, correctly detect the direction of
3447 cells using that circuit. Previously, this bug made roughly one
3448 circuit in a million non-functional. Fixes bug 12195; this is a
3449 bugfix on every version of Tor.
3451 o Major bugfixes (client, pluggable transports):
3452 - When managing pluggable transports, use OS notification facilities
3453 to learn if they have crashed, and don't attempt to kill any
3454 process that has already exited. Fixes bug 8746; bugfix
3457 o Minor features (diagnostic):
3458 - When logging a warning because of bug 7164, additionally check the
3459 hash table for consistency (as proposed on ticket 11737). This may
3460 help diagnose bug 7164.
3461 - When we log a heartbeat, log how many one-hop circuits we have
3462 that are at least 30 minutes old, and log status information about
3463 a few of them. This is an attempt to track down bug 8387.
3464 - When encountering an unexpected CR while writing text to a file on
3465 Windows, log the name of the file. Should help diagnosing
3467 - Give more specific warnings when a client notices that an onion
3468 handshake has failed. Fixes ticket 9635.
3469 - Add significant new logging code to attempt to diagnose bug 12184,
3470 where relays seem to run out of available circuit IDs.
3471 - Improve the diagnostic log message for bug 8387 even further to
3472 try to improve our odds of figuring out why one-hop directory
3473 circuits sometimes do not get closed.
3475 o Minor features (security, memory management):
3476 - Memory allocation tricks (mempools and buffer freelists) are now
3477 disabled by default. You can turn them back on with
3478 --enable-mempools and --enable-buf-freelists respectively. We're
3479 disabling these features because malloc performance is good enough
3480 on most platforms, and a similar feature in OpenSSL exacerbated
3481 exploitation of the Heartbleed attack. Resolves ticket 11476.
3483 o Minor features (security):
3484 - Apply the secure SipHash-2-4 function to the hash table mapping
3485 circuit IDs and channels to circuits. We missed this one when we
3486 were converting all the other hash functions to use SipHash back
3487 in 0.2.5.3-alpha. Resolves ticket 11750.
3489 o Minor features (build):
3490 - The configure script has a --disable-seccomp option to turn off
3491 support for libseccomp on systems that have it, in case it (or
3492 Tor's use of it) is broken. Resolves ticket 11628.
3494 o Minor features (other):
3495 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
3498 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
3499 - When running a hidden service, do not allow TunneledDirConns 0;
3500 this will keep the hidden service from running, and also
3501 make it publish its descriptors directly over HTTP. Fixes bug 10849;
3502 bugfix on 0.2.1.1-alpha.
3504 o Minor bugfixes (performance):
3505 - Avoid a bug where every successful connection made us recompute
3506 the flag telling us whether we have sufficient information to
3507 build circuits. Previously, we would forget our cached value
3508 whenever we successfully opened a channel (or marked a router as
3509 running or not running for any other reason), regardless of
3510 whether we had previously believed the router to be running. This
3511 forced us to run an expensive update operation far too often.
3512 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
3513 - Avoid using tor_memeq() for checking relay cell integrity. This
3514 removes a possible performance bottleneck. Fixes part of bug
3515 12169; bugfix on 0.2.1.31.
3517 o Minor bugfixes (compilation):
3518 - Fix compilation of test_status.c when building with MVSC. Bugfix
3519 on 0.2.5.4-alpha. Patch from Gisle Vanem.
3520 - Resolve GCC complaints on OpenBSD about discarding constness in
3521 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
3522 on 0.1.1.23. Patch from Dana Koch.
3523 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
3524 treatment of long and time_t as comparable types. Fixes part of
3525 bug 11633. Patch from Dana Koch.
3526 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
3527 11623; bugfix on 0.2.5.3-alpha.
3528 - When deciding whether to build the 64-bit curve25519
3529 implementation, detect platforms where we can compile 128-bit
3530 arithmetic but cannot link it. Fixes bug 11729; bugfix on
3531 0.2.4.8-alpha. Patch from "conradev".
3532 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
3533 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
3534 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
3537 o Minor bugfixes (Directory server):
3538 - When sending a compressed set of descriptors or microdescriptors,
3539 make sure to finalize the zlib stream. Previously, we would write
3540 all the compressed data, but if the last descriptor we wanted to
3541 send was missing or too old, we would not mark the stream as
3542 finished. This caused problems for decompression tools. Fixes bug
3543 11648; bugfix on 0.1.1.23.
3545 o Minor bugfixes (Linux seccomp sandbox):
3546 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
3547 11622; bugfix on 0.2.5.1-alpha.
3548 - Avoid crashing when re-opening listener ports with the seccomp
3549 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
3550 - Avoid crashing with the seccomp sandbox enabled along with
3551 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
3552 - When we receive a SIGHUP with the sandbox enabled, correctly
3553 support rotating our log files. Fixes bug 12032; bugfix
3555 - Avoid crash when running with sandboxing enabled and
3556 DirReqStatistics not disabled. Fixes bug 12035; bugfix
3558 - Fix a "BUG" warning when trying to write bridge-stats files with
3559 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
3561 - Prevent the sandbox from crashing on startup when run with the
3562 --enable-expensive-hardening configuration option. Fixes bug
3563 11477; bugfix on 0.2.5.4-alpha.
3564 - When running with DirPortFrontPage and sandboxing both enabled,
3565 reload the DirPortFrontPage correctly when restarting. Fixes bug
3566 12028; bugfix on 0.2.5.1-alpha.
3567 - Don't try to enable the sandbox when using the Tor binary to check
3568 its configuration, hash a passphrase, or so on. Doing so was
3569 crashing on startup for some users. Fixes bug 11609; bugfix
3571 - Avoid warnings when running with sandboxing and node statistics
3572 enabled at the same time. Fixes part of 12064; bugfix on
3573 0.2.5.1-alpha. Patch from Michael Wolf.
3574 - Avoid warnings when running with sandboxing enabled at the same
3575 time as cookie authentication, hidden services, or directory
3576 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
3577 - Do not allow options that require calls to exec to be enabled
3578 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
3579 bug 12043; bugfix on 0.2.5.1-alpha.
3580 - Handle failures in getpwnam()/getpwuid() when running with the
3581 User option set and the Linux syscall sandbox enabled. Fixes bug
3582 11946; bugfix on 0.2.5.1-alpha.
3583 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
3584 to avoid calling getaddrinfo() after installing the sandbox
3585 filters. Previously, it preloaded a cache with the IPv4 address
3586 for our hostname, and nothing else. Now, it loads the cache with
3587 every address that it used to initialize the Tor process. Fixes
3588 bug 11970; bugfix on 0.2.5.1-alpha.
3590 o Minor bugfixes (pluggable transports):
3591 - Enable the ExtORPortCookieAuthFile option, to allow changing the
3592 default location of the authentication token for the extended OR
3593 Port as used by sever-side pluggable transports. We had
3594 implemented this option before, but the code to make it settable
3595 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
3596 - Avoid another 60-second delay when starting Tor in a pluggable-
3597 transport-using configuration when we already have cached
3598 descriptors for our bridges. Fixes bug 11965; bugfix
3601 o Minor bugfixes (client):
3602 - Avoid "Tried to open a socket with DisableNetwork set" warnings
3603 when starting a client with bridges configured and DisableNetwork
3604 set. (Tor launcher starts Tor with DisableNetwork set the first
3605 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
3607 o Minor bugfixes (testing):
3608 - The Python parts of the test scripts now work on Python 3 as well
3609 as Python 2, so systems where '/usr/bin/python' is Python 3 will
3610 no longer have the tests break. Fixes bug 11608; bugfix
3612 - When looking for versions of python that we could run the tests
3613 with, check for "python2.7" and "python3.3"; previously we were
3614 only looking for "python", "python2", and "python3". Patch from
3615 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
3616 - Fix all valgrind warnings produced by the unit tests. There were
3617 over a thousand memory leak warnings previously, mostly produced
3618 by forgetting to free things in the unit test code. Fixes bug
3619 11618, bugfixes on many versions of Tor.
3621 o Minor bugfixes (tor-fw-helper):
3622 - Give a correct log message when tor-fw-helper fails to launch.
3623 (Previously, we would say something like "tor-fw-helper sent us a
3624 string we could not parse".) Fixes bug 9781; bugfix
3627 o Minor bugfixes (relay, threading):
3628 - Check return code on spawn_func() in cpuworker code, so that we
3629 don't think we've spawned a nonworking cpuworker and write junk to
3630 it forever. Fix related to bug 4345; bugfix on all released Tor
3631 versions. Found by "skruffy".
3632 - Use a pthread_attr to make sure that spawn_func() cannot return an
3633 error while at the same time launching a thread. Fix related to
3634 bug 4345; bugfix on all released Tor versions. Reported
3637 o Minor bugfixes (relay, oom prevention):
3638 - Correctly detect the total available system memory. We tried to do
3639 this in 0.2.5.4-alpha, but the code was set up to always return an
3640 error value, even on success. Fixes bug 11805; bugfix
3643 o Minor bugfixes (relay, other):
3644 - We now drop CREATE cells for already-existent circuit IDs and for
3645 zero-valued circuit IDs, regardless of other factors that might
3646 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
3648 - Avoid an illegal read from stack when initializing the TLS module
3649 using a version of OpenSSL without all of the ciphers used by the
3650 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
3652 - When rejecting DATA cells for stream_id zero, still count them
3653 against the circuit's deliver window so that we don't fail to send
3654 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
3656 o Minor bugfixes (logging):
3657 - Fix a misformatted log message about delayed directory fetches.
3658 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
3659 - Squelch a spurious LD_BUG message "No origin circuit for
3660 successful SOCKS stream" in certain hidden service failure cases;
3664 - Include a tor.service file in contrib/dist for use with systemd.
3665 Some distributions will be able to use this file unmodified;
3666 others will need to tweak it, or write their own. Patch from Jamie
3667 Nguyen; resolves ticket 8368.
3670 - Clean up several option names in the manpage to match their real
3671 names, add the missing documentation for a couple of testing and
3672 directory authority options, remove the documentation for a
3673 V2-directory fetching option that no longer exists. Resolves
3675 - Correct the documenation so that it lists the correct directory
3676 for the stats files. (They are in a subdirectory called "stats",
3678 - In the manpage, move more authority-only options into the
3679 directory authority section so that operators of regular directory
3680 caches don't get confused.
3683 - The contrib directory has been sorted and tidied. Before, it was
3684 an unsorted dumping ground for useful and not-so-useful things.
3685 Now, it is divided based on functionality, and the items which
3686 seemed to be nonfunctional or useless have been removed. Resolves
3687 ticket 8966; based on patches from "rl1987".
3690 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
3691 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
3692 - The TunnelDirConns and PreferTunnelledDirConns options no longer
3693 exist; tunneled directory connections have been available since
3694 0.1.2.5-alpha, and turning them off is not a good idea. This is a
3695 brute-force fix for 10849, where "TunnelDirConns 0" would break
3699 Changes in version 0.2.4.22 - 2014-05-16
3700 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3701 alpha release series. These include blocking all authority signing
3702 keys that may have been affected by the OpenSSL "heartbleed" bug,
3703 choosing a far more secure set of TLS ciphersuites by default, closing
3704 a couple of memory leaks that could be used to run a target relay out
3705 of RAM, and several others.
3707 o Major features (security, backport from 0.2.5.4-alpha):
3708 - Block authority signing keys that were used on authorities
3709 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3710 don't have any evidence that these keys _were_ compromised; we're
3711 doing this to be prudent.) Resolves ticket 11464.
3713 o Major bugfixes (security, OOM):
3714 - Fix a memory leak that could occur if a microdescriptor parse
3715 fails during the tokenizing step. This bug could enable a memory
3716 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3719 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3720 - The relay ciphersuite list is now generated automatically based on
3721 uniform criteria, and includes all OpenSSL ciphersuites with
3722 acceptable strength and forward secrecy. Previously, we had left
3723 some perfectly fine ciphersuites unsupported due to omission or
3724 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3725 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3726 - Relays now trust themselves to have a better view than clients of
3727 which TLS ciphersuites are better than others. (Thanks to bug
3728 11513, the relay list is now well-considered, whereas the client
3729 list has been chosen mainly for anti-fingerprinting purposes.)
3730 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3731 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3732 AES128. Resolves ticket 11528.
3733 - Clients now try to advertise the same list of ciphersuites as
3734 Firefox 28. This change enables selection of (fast) GCM
3735 ciphersuites, disables some strange old ciphers, and stops
3736 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3737 Resolves ticket 11438.
3739 o Minor bugfixes (configuration, security):
3740 - When running a hidden service, do not allow TunneledDirConns 0:
3741 trying to set that option together with a hidden service would
3742 otherwise prevent the hidden service from running, and also make
3743 it publish its descriptors directly over HTTP. Fixes bug 10849;
3744 bugfix on 0.2.1.1-alpha.
3746 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3747 - Avoid sending a garbage value to the controller when a circuit is
3748 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3750 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3751 - Stop leaking memory when we successfully resolve a PTR record.
3752 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3754 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3755 - Avoid 60-second delays in the bootstrapping process when Tor is
3756 launching for a second time while using bridges. Fixes bug 9229;
3757 bugfix on 0.2.0.3-alpha.
3759 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3760 - Give the correct URL in the warning message when trying to run a
3761 relay on an ancient version of Windows. Fixes bug 9393.
3763 o Minor bugfixes (compilation):
3764 - Fix a compilation error when compiling with --disable-curve25519.
3765 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3768 - Downgrade the warning severity for the the "md was still
3769 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3770 for trying to diagnose this bug, and the current warning in
3771 earlier versions of tor achieves nothing useful. Addresses warning
3774 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3775 - When we run out of usable circuit IDs on a channel, log only one
3776 warning for the whole channel, and describe how many circuits
3777 there were on the channel. Fixes part of ticket 11553.
3779 o Minor features (security, backport from 0.2.5.4-alpha):
3780 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
3781 leave the default at 8GBytes), to better support Raspberry Pi
3782 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
3784 o Documentation (backport from 0.2.5.4-alpha):
3785 - Correctly document that we search for a system torrc file before
3786 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3790 Changes in version 0.2.5.4-alpha - 2014-04-25
3791 Tor 0.2.5.4-alpha includes several security and performance
3792 improvements for clients and relays, including blacklisting authority
3793 signing keys that were used while susceptible to the OpenSSL
3794 "heartbleed" bug, fixing two expensive functions on busy relays,
3795 improved TLS ciphersuite preference lists, support for run-time
3796 hardening on compilers that support AddressSanitizer, and more work on
3797 the Linux sandbox code.
3799 There are also several usability fixes for clients (especially clients
3800 that use bridges), two new TransPort protocols supported (one on
3801 OpenBSD, one on FreeBSD), and various other bugfixes.
3803 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
3804 have accumulated many known flaws; everyone should upgrade.
3806 o Major features (security):
3807 - If you don't specify MaxMemInQueues yourself, Tor now tries to
3808 pick a good value based on your total system memory. Previously,
3809 the default was always 8 GB. You can still override the default by
3810 setting MaxMemInQueues yourself. Resolves ticket 11396.
3811 - Block authority signing keys that were used on authorities
3812 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3813 don't have any evidence that these keys _were_ compromised; we're
3814 doing this to be prudent.) Resolves ticket 11464.
3816 o Major features (relay performance):
3817 - Speed up server-side lookups of rendezvous and introduction point
3818 circuits by using hashtables instead of linear searches. These
3819 functions previously accounted between 3 and 7% of CPU usage on
3820 some busy relays. Resolves ticket 9841.
3821 - Avoid wasting CPU when extending a circuit over a channel that is
3822 nearly out of circuit IDs. Previously, we would do a linear scan
3823 over possible circuit IDs before finding one or deciding that we
3824 had exhausted our possibilities. Now, we try at most 64 random
3825 circuit IDs before deciding that we probably won't succeed. Fixes
3826 a possible root cause of ticket 11553.
3828 o Major features (seccomp2 sandbox, Linux only):
3829 - The seccomp2 sandbox can now run a test network for multiple hours
3830 without crashing. The sandbox is still experimental, and more bugs
3831 will probably turn up. To try it, enable "Sandbox 1" on a Linux
3832 host. Resolves ticket 11351.
3833 - Strengthen sandbox code: the sandbox can now test the arguments
3834 for rename(), and blocks _sysctl() entirely. Resolves another part
3836 - When the sandbox blocks a system call, it now tries to log a stack
3837 trace before exiting. Resolves ticket 11465.
3839 o Major bugfixes (TLS cipher selection):
3840 - The relay ciphersuite list is now generated automatically based on
3841 uniform criteria, and includes all OpenSSL ciphersuites with
3842 acceptable strength and forward secrecy. Previously, we had left
3843 some perfectly fine ciphersuites unsupported due to omission or
3844 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3845 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3846 - Relays now trust themselves to have a better view than clients of
3847 which TLS ciphersuites are better than others. (Thanks to bug
3848 11513, the relay list is now well-considered, whereas the client
3849 list has been chosen mainly for anti-fingerprinting purposes.)
3850 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3851 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3852 AES128. Resolves ticket 11528.
3853 - Clients now try to advertise the same list of ciphersuites as
3854 Firefox 28. This change enables selection of (fast) GCM
3855 ciphersuites, disables some strange old ciphers, and stops
3856 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3857 Resolves ticket 11438.
3859 o Major bugfixes (bridge client):
3860 - Avoid 60-second delays in the bootstrapping process when Tor is
3861 launching for a second time while using bridges. Fixes bug 9229;
3862 bugfix on 0.2.0.3-alpha.
3864 o Minor features (transparent proxy, *BSD):
3865 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3866 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3867 10267; patch from "yurivict".
3868 - Support OpenBSD's divert-to rules with the pf firewall for
3869 transparent proxy ports. To enable it, set "TransProxyType
3870 pf-divert". This allows Tor to run a TransPort transparent proxy
3871 port on OpenBSD 4.4 or later without root privileges. See the
3872 pf.conf(5) manual page for information on configuring pf to use
3873 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3875 o Minor features (security):
3876 - New --enable-expensive-hardening option to enable security
3877 hardening options that consume nontrivial amounts of CPU and
3878 memory. Right now, this includes AddressSanitizer and UbSan, which
3879 are supported in newer versions of GCC and Clang. Closes ticket
3882 o Minor features (log verbosity):
3883 - Demote the message that we give when a flushing connection times
3884 out for too long from NOTICE to INFO. It was usually meaningless.
3885 Resolves ticket 5286.
3886 - Don't log so many notice-level bootstrapping messages at startup
3887 about downloading descriptors. Previously, we'd log a notice
3888 whenever we learned about more routers. Now, we only log a notice
3889 at every 5% of progress. Fixes bug 9963.
3890 - Warn less verbosely when receiving a malformed
3891 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3892 - When we run out of usable circuit IDs on a channel, log only one
3893 warning for the whole channel, and describe how many circuits
3894 there were on the channel. Fixes part of ticket 11553.
3896 o Minor features (relay):
3897 - If a circuit timed out for at least 3 minutes, check if we have a
3898 new external IP address, and publish a new descriptor with the new
3899 IP address if it changed. Resolves ticket 2454.
3901 o Minor features (controller):
3902 - Make the entire exit policy available from the control port via
3903 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3905 - Because of the fix for ticket 11396, the real limit for memory
3906 usage may no longer match the configured MaxMemInQueues value. The
3907 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3909 o Minor features (bridge client):
3910 - Report a more useful failure message when we can't connect to a
3911 bridge because we don't have the right pluggable transport
3912 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3914 o Minor features (diagnostic):
3915 - Add more log messages to diagnose bug 7164, which causes
3916 intermittent "microdesc_free() called but md was still referenced"
3917 warnings. We now include more information, to figure out why we
3918 might be cleaning a microdescriptor for being too old if it's
3919 still referenced by a live node_t object.
3921 o Minor bugfixes (client, DNSPort):
3922 - When using DNSPort, try to respond to AAAA requests with AAAA
3923 answers. Previously, we hadn't looked at the request type when
3924 deciding which answer type to prefer. Fixes bug 10468; bugfix on
3926 - When receiving a DNS query for an unsupported record type, reply
3927 with no answer rather than with a NOTIMPL error. This behavior
3928 isn't correct either, but it will break fewer client programs, we
3929 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
3932 o Minor bugfixes (exit relay):
3933 - Stop leaking memory when we successfully resolve a PTR record.
3934 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3936 o Minor bugfixes (bridge client):
3937 - Stop accepting bridge lines containing hostnames. Doing so would
3938 cause clients to perform DNS requests on the hostnames, which was
3939 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3940 - Avoid a 60-second delay in the bootstrapping process when a Tor
3941 client with pluggable transports re-reads its configuration at
3942 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
3944 o Minor bugfixes (client, logging during bootstrap):
3945 - Warn only once if we start logging in an unsafe way. Previously,
3946 we complain as many times as we had problems. Fixes bug 9870;
3947 bugfix on 0.2.5.1-alpha.
3948 - Only report the first fatal bootstrap error on a given OR
3949 connection. This stops us from telling the controller bogus error
3950 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
3951 - Be more helpful when trying to run sandboxed on Linux without
3952 libseccomp. Instead of saying "Sandbox is not implemented on this
3953 platform", we now explain that we need to be built with
3954 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
3955 - Avoid generating spurious warnings when starting with
3956 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
3959 o Minor bugfixes (closing OR connections):
3960 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
3961 check if it's an or_connection_t and correctly call
3962 connection_or_close_for_error() rather than
3963 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
3965 - When closing all connections on setting DisableNetwork to 1, use
3966 connection_or_close_normally() rather than closing OR connections
3967 out from under the channel layer. Fixes bug 11306; bugfix on
3970 o Minor bugfixes (controller):
3971 - Avoid sending a garbage value to the controller when a circuit is
3972 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3974 o Minor bugfixes (tor-fw-helper):
3975 - Allow tor-fw-helper to build again by adding src/ext to its
3976 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
3978 o Minor bugfixes (bridges):
3979 - Avoid potential crashes or bad behavior when launching a
3980 server-side managed proxy with ORPort or ExtORPort temporarily
3981 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3983 o Minor bugfixes (platform-specific):
3984 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
3985 bug 11426; bugfix on 0.2.5.3-alpha.
3986 - When dumping a malformed directory object to disk, save it in
3987 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
3989 - Don't report failures from make_socket_reuseable() on incoming
3990 sockets on OSX: this can happen when incoming connections close
3991 early. Fixes bug 10081.
3993 o Minor bugfixes (trivial memory leaks):
3994 - Fix a small memory leak when signing a directory object. Fixes bug
3995 11275; bugfix on 0.2.4.13-alpha.
3996 - Free placeholder entries in our circuit table at exit; fixes a
3997 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
3998 - Don't re-initialize a second set of OpenSSL mutexes when starting
3999 up. Previously, we'd make one set of mutexes, and then immediately
4000 replace them with another. Fixes bug 11726; bugfix on
4002 - Resolve some memory leaks found by coverity in the unit tests, on
4003 exit in tor-gencert, and on a failure to compute digests for our
4004 own keys when generating a v3 networkstatus vote. These leaks
4005 should never have affected anyone in practice.
4007 o Minor bugfixes (hidden service):
4008 - Only retry attempts to connect to a chosen rendezvous point 8
4009 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4011 o Minor bugfixes (misc code correctness):
4012 - Fix various instances of undefined behavior in channeltls.c,
4013 tor_memmem(), and eventdns.c that would cause us to construct
4014 pointers to memory outside an allocated object. (These invalid
4015 pointers were not accessed, but C does not even allow them to
4016 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4017 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4018 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4019 fix some miscellaneous errors in our tests and codebase. Fixes bug
4020 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4021 - Always check return values for unlink, munmap, UnmapViewOfFile;
4022 check strftime return values more often. In some cases all we can
4023 do is report a warning, but this may help prevent deeper bugs from
4024 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4026 - Fix numerous warnings from the clang "scan-build" static analyzer.
4027 Some of these are programming style issues; some of them are false
4028 positives that indicated awkward code; some are undefined behavior
4029 cases related to constructing (but not using) invalid pointers;
4030 some are assumptions about API behavior; some are (harmlessly)
4031 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4032 correct; and one or two are genuine bugs that weren't reachable
4033 from the rest of the program. Fixes bug 8793; bugfixes on many,
4037 - Build the torify.1 manpage again. Previously, we were only trying
4038 to build it when also building tor-fw-helper. That's why we didn't
4039 notice that we'd broken the ability to build it. Fixes bug 11321;
4040 bugfix on 0.2.5.1-alpha.
4041 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4042 11061; bugfix on 0.2.4.7-alpha.
4043 - Correctly document that we search for a system torrc file before
4044 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4046 - Resolve warnings from Doxygen.
4048 o Code simplifications and refactoring:
4049 - Remove is_internal_IP() function. Resolves ticket 4645.
4050 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4051 Closes issue 9107; patch from "marek".
4052 - Change our use of the ENUM_BF macro to avoid declarations that
4055 o Deprecated versions:
4056 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
4057 attention for some while. Directory authorities no longer accept
4058 descriptors from relays running any version of Tor prior to Tor
4059 0.2.3.16-alpha. Resolves ticket 11149.
4062 - New macros in test.h to simplify writing mock-functions for unit
4063 tests. Part of ticket 11507. Patch from Dana Koch.
4064 - Complete tests for the status.c module. Resolves ticket 11507.
4065 Patch from Dana Koch.
4068 - Remove all code for the long unused v1 directory protocol.
4069 Resolves ticket 11070.
4072 Changes in version 0.2.5.3-alpha - 2014-03-22
4073 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
4074 two new anti-DoS features for Tor relays, resolves a bug that kept
4075 SOCKS5 support for IPv6 from working, fixes several annoying usability
4076 issues for bridge users, and removes more old code for unused
4079 The Tor 0.2.5.x release series is now in patch-freeze: no feature
4080 patches not already written will be considered for inclusion in 0.2.5.x.
4082 o Major features (relay security, DoS-resistance):
4083 - When deciding whether we have run out of memory and we need to
4084 close circuits, also consider memory allocated in buffers for
4085 streams attached to each circuit.
4087 This change, which extends an anti-DoS feature introduced in
4088 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4089 better resist more memory-based DoS attacks than before. Since the
4090 MaxMemInCellQueues option now applies to all queues, it is renamed
4091 to MaxMemInQueues. This feature fixes bug 10169.
4092 - Avoid hash-flooding denial-of-service attacks by using the secure
4093 SipHash-2-4 hash function for our hashtables. Without this
4094 feature, an attacker could degrade performance of a targeted
4095 client or server by flooding their data structures with a large
4096 number of entries to be stored at the same hash table position,
4097 thereby slowing down the Tor instance. With this feature, hash
4098 table positions are derived from a randomized cryptographic key,
4099 and an attacker cannot predict which entries will collide. Closes
4101 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
4102 the default at 8GBytes), to better support Raspberry Pi users. Fixes
4103 bug 9686; bugfix on 0.2.4.14-alpha.
4105 o Minor features (bridges, pluggable transports):
4106 - Bridges now write the SHA1 digest of their identity key
4107 fingerprint (that is, a hash of a hash of their public key) to
4108 notice-level logs, and to a new hashed-fingerprint file. This
4109 information will help bridge operators look up their bridge in
4110 Globe and similar tools. Resolves ticket 10884.
4111 - Improve the message that Tor displays when running as a bridge
4112 using pluggable transports without an Extended ORPort listener.
4113 Also, log the message in the log file too. Resolves ticket 11043.
4115 o Minor features (other):
4116 - Add a new option, PredictedPortsRelevanceTime, to control how long
4117 after having received a request to connect to a given port Tor
4118 will try to keep circuits ready in anticipation of future requests
4119 for that port. Patch from "unixninja92"; implements ticket 9176.
4120 - Generate a warning if any ports are listed in the SocksPolicy,
4121 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4122 AuthDirBadExit options. (These options only support address
4123 ranges.) Fixes part of ticket 11108.
4124 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
4127 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
4128 - Build without warnings under clang 3.4. (We have some macros that
4129 define static functions only some of which will get used later in
4130 the module. Starting with clang 3.4, these give a warning unless the
4131 unused attribute is set on them.) Resolves ticket 10904.
4132 - Fix build warnings about missing "a2x" comment when building the
4133 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4134 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4136 o Minor bugfixes (client):
4137 - Improve the log message when we can't connect to a hidden service
4138 because all of the hidden service directory nodes hosting its
4139 descriptor are excluded. Improves on our fix for bug 10722, which
4140 was a bugfix on 0.2.0.10-alpha.
4141 - Raise a control port warning when we fail to connect to all of
4142 our bridges. Previously, we didn't inform the controller, and
4143 the bootstrap process would stall. Fixes bug 11069; bugfix on
4145 - Exit immediately when a process-owning controller exits.
4146 Previously, tor relays would wait for a little while after their
4147 controller exited, as if they had gotten an INT signal -- but this
4148 was problematic, since there was no feedback for the user. To do a
4149 clean shutdown, controllers should send an INT signal and give Tor
4150 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4151 - Stop attempting to connect to bridges before our pluggable
4152 transports are configured (harmless but resulted in some erroneous
4153 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4154 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4155 generating incorrect SOCKS5 responses, and confusing client
4156 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4158 o Minor bugfixes (relays and bridges):
4159 - Avoid crashing on a malformed resolv.conf file when running a
4160 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4161 - Non-exit relays no longer launch mock DNS requests to check for
4162 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4163 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4164 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4165 - Bridges now report complete directory request statistics. Related
4166 to bug 5824; bugfix on 0.2.2.1-alpha.
4167 - Bridges now never collect statistics that were designed for
4168 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4169 - Stop giving annoying warning messages when we decide not to launch
4170 a pluggable transport proxy that we don't need (because there are
4171 no bridges configured to use it). Resolves ticket 5018; bugfix
4173 - Give the correct URL in the warning message when trying to run a
4174 relay on an ancient version of Windows. Fixes bug 9393.
4176 o Minor bugfixes (backtrace support):
4177 - Support automatic backtraces on more platforms by using the
4178 "-fasynchronous-unwind-tables" compiler option. This option is
4179 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
4180 is on by default and table generation is not. This doesn't yet
4181 add Windows support; only Linux, OSX, and some BSDs are affected.
4182 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
4183 - Avoid strange behavior if two threads hit failed assertions at the
4184 same time and both try to log backtraces at once. (Previously, if
4185 this had happened, both threads would have stored their intermediate
4186 results in the same buffer, and generated junk outputs.) Reported by
4187 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
4188 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
4189 0.2.5.2-alpha; patch from Nick Hopper.
4191 o Minor bugfixes (unit tests):
4192 - Fix a small bug in the unit tests that might have made the tests
4193 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
4194 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
4197 - Remove all remaining code related to version-0 hidden service
4198 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4199 the rest of bug 10841.
4202 - Document in the manpage that "KBytes" may also be written as
4203 "kilobytes" or "KB", that "Kbits" may also be written as
4204 "kilobits", and so forth. Closes ticket 9222.
4205 - Document that the ClientOnly config option overrides ORPort.
4206 Our old explanation made ClientOnly sound as though it did
4207 nothing at all. Resolves bug 9059.
4208 - Explain that SocksPolicy, DirPolicy, and similar options don't
4209 take port arguments. Fixes the other part of ticket 11108.
4210 - Fix a comment about the rend_server_descriptor_t.protocols field
4211 to more accurately describe its range. Also, make that field
4212 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4213 bugfix on 0.2.1.5-alpha.
4214 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4215 the maximum client name length is 16, not 19. Fixes bug 11118;
4216 bugfix on 0.2.1.6-alpha.
4218 o Code simplifications and refactoring:
4219 - Get rid of router->address, since in all cases it was just the
4220 string representation of router->addr. Resolves ticket 5528.
4222 o Test infrastructure:
4223 - Update to the latest version of tinytest.
4224 - Improve the tinytest implementation of string operation tests so
4225 that comparisons with NULL strings no longer crash the tests; they
4226 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4229 Changes in version 0.2.4.21 - 2014-02-28
4230 Tor 0.2.4.21 further improves security against potential adversaries who
4231 find breaking 1024-bit crypto doable, and backports several stability
4232 and robustness patches from the 0.2.5 branch.
4234 o Major features (client security):
4235 - When we choose a path for a 3-hop circuit, make sure it contains
4236 at least one relay that supports the NTor circuit extension
4237 handshake. Otherwise, there is a chance that we're building
4238 a circuit that's worth attacking by an adversary who finds
4239 breaking 1024-bit crypto doable, and that chance changes the game
4240 theory. Implements ticket 9777.
4243 - Do not treat streams that fail with reason
4244 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4245 since it could also indicate an ENETUNREACH connection error. Fixes
4246 part of bug 10777; bugfix on 0.2.4.8-alpha.
4248 o Code simplification and refactoring:
4249 - Remove data structures which were introduced to implement the
4250 CellStatistics option: they are now redundant with the new timestamp
4251 field in the regular packed_cell_t data structure, which we did
4252 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
4255 - Always clear OpenSSL bignums before freeing them -- even bignums
4256 that don't contain secrets. Resolves ticket 10793. Patch by
4258 - Build without warnings under clang 3.4. (We have some macros that
4259 define static functions only some of which will get used later in
4260 the module. Starting with clang 3.4, these give a warning unless the
4261 unused attribute is set on them.) Resolves ticket 10904.
4262 - Update geoip and geoip6 files to the February 7 2014 Maxmind
4263 GeoLite2 Country database.
4266 - Set the listen() backlog limit to the largest actually supported
4267 on the system, not to the value in a header file. Fixes bug 9716;
4268 bugfix on every released Tor.
4269 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4270 exit node as a NOROUTE error, not an INTERNAL error, since they
4271 can apparently happen when trying to connect to the wrong sort
4272 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4273 - Fix build warnings about missing "a2x" comment when building the
4274 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4275 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4276 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4277 not entirely remove it from the connection lists. Fixes bug 9602;
4278 bugfix on 0.2.4.4-alpha.
4279 - Fix a segmentation fault in our benchmark code when running with
4280 Fedora's OpenSSL package, or any other OpenSSL that provides
4281 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4282 - Turn "circuit handshake stats since last time" log messages into a
4283 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4285 o Documentation fixes:
4286 - Document that all but one DirPort entry must have the NoAdvertise
4287 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4290 Changes in version 0.2.5.2-alpha - 2014-02-13
4291 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
4292 like the "poor random number generation" fix and the "building too many
4293 circuits" fix. It also further improves security against potential
4294 adversaries who find breaking 1024-bit crypto doable, and launches
4295 pluggable transports on demand (which gets us closer to integrating
4296 pluggable transport support by default -- not to be confused with Tor
4297 bundles enabling pluggable transports and bridges by default).
4299 o Major features (client security):
4300 - When we choose a path for a 3-hop circuit, make sure it contains
4301 at least one relay that supports the NTor circuit extension
4302 handshake. Otherwise, there is a chance that we're building
4303 a circuit that's worth attacking by an adversary who finds
4304 breaking 1024-bit crypto doable, and that chance changes the game
4305 theory. Implements ticket 9777.
4306 - Clients now look at the "usecreatefast" consensus parameter to
4307 decide whether to use CREATE_FAST or CREATE cells for the first hop
4308 of their circuit. This approach can improve security on connections
4309 where Tor's circuit handshake is stronger than the available TLS
4310 connection security levels, but the tradeoff is more computational
4311 load on guard relays. Implements proposal 221. Resolves ticket 9386.
4313 o Major features (bridges):
4314 - Don't launch pluggable transport proxies if we don't have any
4315 bridges configured that would use them. Now we can list many
4316 pluggable transports, and Tor will dynamically start one when it
4317 hears a bridge address that needs it. Resolves ticket 5018.
4318 - The bridge directory authority now assigns status flags (Stable,
4319 Guard, etc) to bridges based on thresholds calculated over all
4320 Running bridges. Now bridgedb can finally make use of its features
4321 to e.g. include at least one Stable bridge in its answers. Fixes
4324 o Major features (other):
4325 - Extend ORCONN controller event to include an "ID" parameter,
4326 and add four new controller event types CONN_BW, CIRC_BW,
4327 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4328 The new events are emitted in private Tor networks only, with the
4329 goal of being able to better track performance and load during
4330 full-network simulations. Implements proposal 218 and ticket 7359.
4331 - On some platforms (currently: recent OSX versions, glibc-based
4332 platforms that support the ELF format, and a few other
4333 Unix-like operating systems), Tor can now dump stack traces
4334 when a crash occurs or an assertion fails. By default, traces
4335 are dumped to stderr (if possible) and to any logs that are
4336 reporting errors. Implements ticket 9299.
4339 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4340 not entirely remove it from the connection lists. Fixes bug 9602;
4341 bugfix on 0.2.4.4-alpha.
4342 - Do not treat streams that fail with reason
4343 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4344 since it could also indicate an ENETUNREACH connection error. Fixes
4345 part of bug 10777; bugfix on 0.2.4.8-alpha.
4347 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4348 - Do not allow OpenSSL engines to replace the PRNG, even when
4349 HardwareAccel is set. The only default builtin PRNG engine uses
4350 the Intel RDRAND instruction to replace the entire PRNG, and
4351 ignores all attempts to seed it with more entropy. That's
4352 cryptographically stupid: the right response to a new alleged
4353 entropy source is never to discard all previously used entropy
4354 sources. Fixes bug 10402; works around behavior introduced in
4355 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4357 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4358 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4359 - Avoid launching spurious extra circuits when a stream is pending.
4360 This fixes a bug where any circuit that _wasn't_ unusable for new
4361 streams would be treated as if it were, causing extra circuits to
4362 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4364 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4365 - No longer stop reading or writing on cpuworker connections when
4366 our rate limiting buckets go empty. Now we should handle circuit
4367 handshake requests more promptly. Resolves bug 9731.
4368 - Stop trying to bootstrap all our directory information from
4369 only our first guard. Discovered while fixing bug 9946; bugfix
4372 o Minor features (bridges, pluggable transports):
4373 - Add threshold cutoffs to the networkstatus document created by
4374 the Bridge Authority. Fixes bug 1117.
4375 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4376 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4377 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4378 Vidalia set this option for us.) Implements ticket 10297.
4380 o Minor features (security):
4381 - Always clear OpenSSL bignums before freeing them -- even bignums
4382 that don't contain secrets. Resolves ticket 10793. Patch by
4385 o Minor features (config options and command line):
4386 - Add an --allow-missing-torrc commandline option that tells Tor to
4387 run even if the configuration file specified by -f is not available.
4388 Implements ticket 10060.
4389 - Add support for the TPROXY transparent proxying facility on Linux.
4390 See documentation for the new TransProxyType option for more
4391 details. Implementation by "thomo". Closes ticket 10582.
4393 o Minor features (controller):
4394 - Add a new "HS_DESC" controller event that reports activities
4395 related to hidden service descriptors. Resolves ticket 8510.
4396 - New "DROPGUARDS" controller command to forget all current entry
4397 guards. Not recommended for ordinary use, since replacing guards
4398 too frequently makes several attacks easier. Resolves ticket 9934;
4401 o Minor features (build):
4402 - Assume that a user using ./configure --host wants to cross-compile,
4403 and give an error if we cannot find a properly named
4404 tool-chain. Add a --disable-tool-name-check option to proceed
4405 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4406 - If we run ./configure and the compiler recognizes -fstack-protector
4407 but the linker rejects it, warn the user about a potentially missing
4408 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4410 o Minor features (testing):
4411 - If Python is installed, "make check" now runs extra tests beyond
4412 the unit test scripts.
4413 - When bootstrapping a test network, sometimes very few relays get
4414 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4415 specify a set of relays which should be voted Guard regardless of
4416 their uptime or bandwidth. Addresses ticket 9206.
4418 o Minor features (log messages):
4419 - When ServerTransportPlugin is set on a bridge, Tor can write more
4420 useful statistics about bridge use in its extrainfo descriptors,
4421 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4422 log message to inform the user in this case. Resolves ticket 9651.
4423 - When receiving a new controller connection, log the origin address.
4424 Resolves ticket 9698; patch from "sigpipe".
4425 - When logging OpenSSL engine status at startup, log the status of
4426 more engines. Fixes ticket 10043; patch from Joshua Datko.
4427 - Turn "circuit handshake stats since last time" log messages into a
4428 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4430 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4431 - Improve the circuit queue out-of-memory handler. Previously, when
4432 we ran low on memory, we'd close whichever circuits had the most
4433 queued cells. Now, we close those that have the *oldest* queued
4434 cells, on the theory that those are most responsible for us
4435 running low on memory. Based on analysis from a forthcoming paper
4436 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4437 - Generate bootstrapping status update events correctly when fetching
4438 microdescriptors. Fixes bug 9927.
4439 - Update to the October 2 2013 Maxmind GeoLite Country database.
4441 o Minor bugfixes (clients):
4442 - When closing a channel that has already been open, do not close
4443 pending circuits that were waiting to connect to the same relay.
4444 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
4447 o Minor bugfixes (relays):
4448 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4449 exit node as a NOROUTE error, not an INTERNAL error, since they
4450 can apparently happen when trying to connect to the wrong sort
4451 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4453 o Minor bugfixes (bridges):
4454 - Fix a bug where the first connection works to a bridge that uses a
4455 pluggable transport with client-side parameters, but we don't send
4456 the client-side parameters on subsequent connections. (We don't
4457 use any pluggable transports with client-side parameters yet,
4458 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4459 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4461 o Minor bugfixes (node selection):
4462 - If ExcludeNodes is set, consider non-excluded hidden service
4463 directory servers before excluded ones. Do not consider excluded
4464 hidden service directory servers at all if StrictNodes is
4465 set. (Previously, we would sometimes decide to connect to those
4466 servers, and then realize before we initiated a connection that
4467 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4469 - If we set the ExitNodes option but it doesn't include any nodes
4470 that have the Exit flag, we would choose not to bootstrap. Now we
4471 bootstrap so long as ExitNodes includes nodes which can exit to
4472 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4474 o Minor bugfixes (controller and command-line):
4475 - If changing a config option via "setconf" fails in a recoverable
4476 way, we used to nonetheless write our new control ports to the
4477 file described by the "ControlPortWriteToFile" option. Now we only
4478 write out that file if we successfully switch to the new config
4479 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4480 - When a command-line option such as --version or --help that
4481 ordinarily implies --hush appears on the command line along with
4482 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
4483 only if it appeared later on the command line. Fixes bug 9578;
4484 bugfix on 0.2.5.1-alpha.
4486 o Minor bugfixes (code correctness):
4487 - Previously we used two temporary files when writing descriptors to
4488 disk; now we only use one. Fixes bug 1376.
4489 - Remove an erroneous (but impossible and thus harmless) pointer
4490 comparison that would have allowed compilers to skip a bounds
4491 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4492 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4493 - Fix an always-true assertion in pluggable transports code so it
4494 actually checks what it was trying to check. Fixes bug 10046;
4495 bugfix on 0.2.3.9-alpha. Found by "dcb".
4497 o Minor bugfixes (protocol correctness):
4498 - When receiving a VERSIONS cell with an odd number of bytes, close
4499 the connection immediately since the cell is malformed. Fixes bug
4500 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4503 o Minor bugfixes (build):
4504 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4505 turned off (that is, without support for v2 link handshakes). Fixes
4506 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4507 - Fix compilation warnings and startup issues when running with
4508 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
4510 - Fix compilation on Solaris 9, which didn't like us having an
4511 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
4513 o Minor bugfixes (testing):
4514 - Fix a segmentation fault in our benchmark code when running with
4515 Fedora's OpenSSL package, or any other OpenSSL that provides
4516 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4518 o Minor bugfixes (log messages):
4519 - Fix a bug where clients using bridges would report themselves
4520 as 50% bootstrapped even without a live consensus document.
4521 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4522 - Suppress a warning where, if there's only one directory authority
4523 in the network, we would complain that votes and signatures cannot
4524 be uploaded to other directory authorities. Fixes bug 10842;
4525 bugfix on 0.2.2.26-beta.
4526 - Report bootstrapping progress correctly when we're downloading
4527 microdescriptors. We had updated our "do we have enough microdescs
4528 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4529 (see bug 5956), but we left the bootstrap status event logic at
4530 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4531 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4533 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4534 - Avoid a crash bug when starting with a corrupted microdescriptor
4535 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4536 - If we fail to dump a previously cached microdescriptor to disk, avoid
4537 freeing duplicate data later on. Fixes bug 10423; bugfix on
4538 0.2.4.13-alpha. Spotted by "bobnomnom".
4540 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4541 - Correctly log long IPv6 exit policies, instead of truncating them
4542 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4543 - Our default TLS ecdhe groups were backwards: we meant to be using
4544 P224 for relays (for performance win) and P256 for bridges (since
4545 it is more common in the wild). Instead we had it backwards. After
4546 reconsideration, we decided that the default should be P256 on all
4547 hosts, since its security is probably better, and since P224 is
4548 reportedly used quite little in the wild. Found by "skruffy" on
4549 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4550 - Free directory authority certificate download statuses on exit
4551 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4553 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4554 - If the guard we choose first doesn't answer, we would try the
4555 second guard, but once we connected to the second guard we would
4556 abandon it and retry the first one, slowing down bootstrapping.
4557 The fix is to treat all our initially chosen guards as acceptable
4558 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4559 - Fix an assertion failure that would occur when disabling the
4560 ORPort setting on a running Tor process while accounting was
4561 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4562 - When examining the list of network interfaces to find our address,
4563 do not consider non-running or disabled network interfaces. Fixes
4564 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4565 - Avoid an off-by-one error when checking buffer boundaries when
4566 formatting the exit status of a pluggable transport helper.
4567 This is probably not an exploitable bug, but better safe than
4568 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4571 o Removed code and features:
4572 - Clients now reject any directory authority certificates lacking
4573 a dir-key-crosscert element. These have been included since
4574 0.2.1.9-alpha, so there's no real reason for them to be optional
4575 any longer. Completes proposal 157. Resolves ticket 10162.
4576 - Remove all code that existed to support the v2 directory system,
4577 since there are no longer any v2 directory authorities. Resolves
4579 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4580 options, which were used for designating authorities as "Hidden
4581 service authorities". There has been no use of hidden service
4582 authorities since 0.2.2.1-alpha, when we stopped uploading or
4583 downloading v0 hidden service descriptors. Fixes bug 10881; also
4584 part of a fix for bug 10841.
4586 o Code simplification and refactoring:
4587 - Remove some old fallback code designed to keep Tor clients working
4588 in a network with only two working relays. Elsewhere in the code we
4589 have long since stopped supporting such networks, so there wasn't
4590 much point in keeping it around. Addresses ticket 9926.
4591 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4592 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4593 - Remove data structures which were introduced to implement the
4594 CellStatistics option: they are now redundant with the addition
4595 of a timestamp to the regular packed_cell_t data structure, which
4596 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
4599 o Documentation (man page) fixes:
4600 - Update manpage to describe some of the files you can expect to
4601 find in Tor's DataDirectory. Addresses ticket 9839.
4602 - Document that all but one DirPort entry must have the NoAdvertise
4603 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4605 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4606 - Clarify the usage and risks of setting the ContactInfo torrc line
4607 for your relay or bridge. Resolves ticket 9854.
4608 - Add anchors to the manpage so we can link to the html version of
4609 the documentation for specific options. Resolves ticket 9866.
4610 - Replace remaining references to DirServer in man page and
4611 log entries. Resolves ticket 10124.
4614 - Make the "tor-gencert" tool used by directory authority operators
4615 create 2048-bit signing keys by default (rather than 1024-bit, since
4616 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4619 Changes in version 0.2.4.20 - 2013-12-22
4620 Tor 0.2.4.20 fixes potentially poor random number generation for users
4621 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4622 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
4623 and 4) have no state file in their DataDirectory (as would happen on
4624 first start). Users who generated relay or hidden service identity
4625 keys in such a situation should discard them and generate new ones.
4627 This release also fixes a logic error that caused Tor clients to build
4628 many more preemptive circuits than they actually need.
4631 - Do not allow OpenSSL engines to replace the PRNG, even when
4632 HardwareAccel is set. The only default builtin PRNG engine uses
4633 the Intel RDRAND instruction to replace the entire PRNG, and
4634 ignores all attempts to seed it with more entropy. That's
4635 cryptographically stupid: the right response to a new alleged
4636 entropy source is never to discard all previously used entropy
4637 sources. Fixes bug 10402; works around behavior introduced in
4638 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4640 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4641 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4642 - Avoid launching spurious extra circuits when a stream is pending.
4643 This fixes a bug where any circuit that _wasn't_ unusable for new
4644 streams would be treated as if it were, causing extra circuits to
4645 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4648 - Avoid a crash bug when starting with a corrupted microdescriptor
4649 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4650 - If we fail to dump a previously cached microdescriptor to disk, avoid
4651 freeing duplicate data later on. Fixes bug 10423; bugfix on
4652 0.2.4.13-alpha. Spotted by "bobnomnom".
4655 Changes in version 0.2.4.19 - 2013-12-11
4656 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
4657 (1986-2013). Aaron worked on diverse projects including helping to guide
4658 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
4659 transparency to the U.S government's PACER documents, and contributing
4660 design and development for Tor and Tor2Web. Aaron was one of the latest
4661 martyrs in our collective fight for civil liberties and human rights,
4662 and his death is all the more painful because he was one of us.
4664 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
4665 a new circuit handshake and link encryption that use ECC to provide
4666 better security and efficiency; makes relays better manage circuit
4667 creation requests; uses "directory guards" to reduce client enumeration
4668 risks; makes bridges collect and report statistics about the pluggable
4669 transports they support; cleans up and improves our geoip database;
4670 gets much closer to IPv6 support for clients, bridges, and relays; makes
4671 directory authorities use measured bandwidths rather than advertised
4672 ones when computing flags and thresholds; disables client-side DNS
4673 caching to reduce tracking risks; and fixes a big bug in bridge
4674 reachability testing. This release introduces two new design
4675 abstractions in the code: a new "channel" abstraction between circuits
4676 and or_connections to allow for implementing alternate relay-to-relay
4677 transports, and a new "circuitmux" abstraction storing the queue of
4678 circuits for a channel. The release also includes many stability,
4679 security, and privacy fixes.
4682 Changes in version 0.2.4.18-rc - 2013-11-16
4683 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
4684 series. It takes a variety of fixes from the 0.2.5.x branch to improve
4685 stability, performance, and better handling of edge cases.
4688 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4689 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4690 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4691 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4692 them to solve bug 6033.)
4695 - No longer stop reading or writing on cpuworker connections when
4696 our rate limiting buckets go empty. Now we should handle circuit
4697 handshake requests more promptly. Resolves bug 9731.
4698 - If we are unable to save a microdescriptor to the journal, do not
4699 drop it from memory and then reattempt downloading it. Fixes bug
4700 9645; bugfix on 0.2.2.6-alpha.
4701 - Stop trying to bootstrap all our directory information from
4702 only our first guard. Discovered while fixing bug 9946; bugfix
4704 - The new channel code sometimes lost track of in-progress circuits,
4705 causing long-running clients to stop building new circuits. The
4706 fix is to always call circuit_n_chan_done(chan, 0) from
4707 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4709 o Minor bugfixes (on 0.2.4.x):
4710 - Correctly log long IPv6 exit policies, instead of truncating them
4711 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4712 - Our default TLS ecdhe groups were backwards: we meant to be using
4713 P224 for relays (for performance win) and P256 for bridges (since
4714 it is more common in the wild). Instead we had it backwards. After
4715 reconsideration, we decided that the default should be P256 on all
4716 hosts, since its security is probably better, and since P224 is
4717 reportedly used quite little in the wild. Found by "skruffy" on
4718 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4719 - Free directory authority certificate download statuses on exit
4720 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4722 o Minor bugfixes (on 0.2.3.x and earlier):
4723 - If the guard we choose first doesn't answer, we would try the
4724 second guard, but once we connected to the second guard we would
4725 abandon it and retry the first one, slowing down bootstrapping.
4726 The fix is to treat all our initially chosen guards as acceptable
4727 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4728 - Fix an assertion failure that would occur when disabling the
4729 ORPort setting on a running Tor process while accounting was
4730 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4731 - When examining the list of network interfaces to find our address,
4732 do not consider non-running or disabled network interfaces. Fixes
4733 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4734 - Avoid an off-by-one error when checking buffer boundaries when
4735 formatting the exit status of a pluggable transport helper.
4736 This is probably not an exploitable bug, but better safe than
4737 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4740 o Minor features (protecting client timestamps):
4741 - Clients no longer send timestamps in their NETINFO cells. These were
4742 not used for anything, and they provided one small way for clients
4743 to be distinguished from each other as they moved from network to
4744 network or behind NAT. Implements part of proposal 222.
4745 - Clients now round timestamps in INTRODUCE cells down to the nearest
4746 10 minutes. If a new Support022HiddenServices option is set to 0, or
4747 if it's set to "auto" and the feature is disabled in the consensus,
4748 the timestamp is sent as 0 instead. Implements part of proposal 222.
4749 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4750 a big deal from a security point of view, but it achieves no actual
4751 good purpose, and isn't needed. Implements part of proposal 222.
4752 - Reduce down accuracy of timestamps in hidden service descriptors.
4753 Implements part of proposal 222.
4755 o Minor features (other):
4756 - Improve the circuit queue out-of-memory handler. Previously, when
4757 we ran low on memory, we'd close whichever circuits had the most
4758 queued cells. Now, we close those that have the *oldest* queued
4759 cells, on the theory that those are most responsible for us
4760 running low on memory. Based on analysis from a forthcoming paper
4761 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4762 - Generate bootstrapping status update events correctly when fetching
4763 microdescriptors. Fixes bug 9927.
4764 - Update to the October 2 2013 Maxmind GeoLite Country database.
4766 o Documentation fixes:
4767 - Clarify the usage and risks of setting the ContactInfo torrc line
4768 for your relay or bridge. Resolves ticket 9854.
4769 - Add anchors to the manpage so we can link to the html version of
4770 the documentation for specific options. Resolves ticket 9866.
4771 - Replace remaining references to DirServer in man page and
4772 log entries. Resolves ticket 10124.
4775 Changes in version 0.2.5.1-alpha - 2013-10-02
4776 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
4777 on Linux, allows bridges that offer pluggable transports to report usage
4778 statistics, fixes many issues to make testing easier, and provides
4779 a pile of minor features and bugfixes that have been waiting for a
4780 release of the new branch.
4782 This is the first alpha release in a new series, so expect there to
4783 be bugs. Users who would rather test out a more stable branch should
4784 stay with 0.2.4.x for now.
4786 o Major features (security):
4787 - Use the seccomp2 syscall filtering facility on Linux to limit
4788 which system calls Tor can invoke. This is an experimental,
4789 Linux-only feature to provide defense-in-depth against unknown
4790 attacks. To try turning it on, set "Sandbox 1" in your torrc
4791 file. Please be ready to report bugs. We hope to add support
4792 for better sandboxing in the future, including more fine-grained
4793 filters, better division of responsibility, and support for more
4794 platforms. This work has been done by Cristian-Matei Toader for
4795 Google Summer of Code.
4796 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4797 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4798 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4799 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4800 them to solve bug 6033.)
4802 o Major features (other):
4803 - Add support for passing arguments to managed pluggable transport
4804 proxies. Implements ticket 3594.
4805 - Bridges now track GeoIP information and the number of their users
4806 even when pluggable transports are in use, and report usage
4807 statistics in their extra-info descriptors. Resolves tickets 4773
4809 - Make testing Tor networks bootstrap better: lower directory fetch
4810 retry schedules and maximum interval without directory requests,
4811 and raise maximum download tries. Implements ticket 6752.
4812 - Add make target 'test-network' to run tests on a Chutney network.
4813 Implements ticket 8530.
4814 - The ntor handshake is now on-by-default, no matter what the
4815 directory authorities recommend. Implements ticket 8561.
4818 - Instead of writing destroy cells directly to outgoing connection
4819 buffers, queue them and intersperse them with other outgoing cells.
4820 This can prevent a set of resource starvation conditions where too
4821 many pending destroy cells prevent data cells from actually getting
4822 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4823 bugfix on 0.2.0.1-alpha.
4824 - If we are unable to save a microdescriptor to the journal, do not
4825 drop it from memory and then reattempt downloading it. Fixes bug
4826 9645; bugfix on 0.2.2.6-alpha.
4827 - The new channel code sometimes lost track of in-progress circuits,
4828 causing long-running clients to stop building new circuits. The
4829 fix is to always call circuit_n_chan_done(chan, 0) from
4830 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4833 - Tor now builds each source file in two modes: a mode that avoids
4834 exposing identifiers needlessly, and another mode that exposes
4835 more identifiers for testing. This lets the compiler do better at
4836 optimizing the production code, while enabling us to take more
4837 radical measures to let the unit tests test things.
4838 - The production builds no longer include functions used only in
4839 the unit tests; all functions exposed from a module only for
4840 unit-testing are now static in production builds.
4841 - Add an --enable-coverage configuration option to make the unit
4842 tests (and a new src/or/tor-cov target) to build with gcov test
4846 - We now have rudimentary function mocking support that our unit
4847 tests can use to test functions in isolation. Function mocking
4848 lets the tests temporarily replace a function's dependencies with
4849 stub functions, so that the tests can check the function without
4850 invoking the other functions it calls.
4851 - Add more unit tests for the <circid,channel>->circuit map, and
4852 the destroy-cell-tracking code to fix bug 7912.
4853 - Unit tests for failing cases of the TAP onion handshake.
4854 - More unit tests for address-manipulation functions.
4856 o Minor features (protecting client timestamps):
4857 - Clients no longer send timestamps in their NETINFO cells. These were
4858 not used for anything, and they provided one small way for clients
4859 to be distinguished from each other as they moved from network to
4860 network or behind NAT. Implements part of proposal 222.
4861 - Clients now round timestamps in INTRODUCE cells down to the nearest
4862 10 minutes. If a new Support022HiddenServices option is set to 0, or
4863 if it's set to "auto" and the feature is disabled in the consensus,
4864 the timestamp is sent as 0 instead. Implements part of proposal 222.
4865 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4866 a big deal from a security point of view, but it achieves no actual
4867 good purpose, and isn't needed. Implements part of proposal 222.
4868 - Reduce down accuracy of timestamps in hidden service descriptors.
4869 Implements part of proposal 222.
4871 o Minor features (config options):
4872 - Config (torrc) lines now handle fingerprints which are missing
4873 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4874 - Support a --dump-config option to print some or all of the
4875 configured options. Mainly useful for debugging the command-line
4876 option parsing code. Helps resolve ticket 4647.
4877 - Raise awareness of safer logging: notify user of potentially
4878 unsafe config options, like logging more verbosely than severity
4879 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4880 - Add a new configuration option TestingV3AuthVotingStartOffset
4881 that bootstraps a network faster by changing the timing for
4882 consensus votes. Addresses ticket 8532.
4883 - Add a new torrc option "ServerTransportOptions" that allows
4884 bridge operators to pass configuration parameters to their
4885 pluggable transports. Resolves ticket 8929.
4886 - The config (torrc) file now accepts bandwidth and space limits in
4887 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4888 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4891 o Minor features (build):
4892 - Add support for `--library-versions` flag. Implements ticket 6384.
4893 - Return the "unexpected sendme" warnings to a warn severity, but make
4894 them rate limited, to help diagnose ticket 8093.
4895 - Detect a missing asciidoc, and warn the user about it, during
4896 configure rather than at build time. Fixes issue 6506. Patch from
4899 o Minor features (other):
4900 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4901 sockets in a single system call. Implements ticket 5129.
4902 - Log current accounting state (bytes sent and received + remaining
4903 time for the current accounting period) in the relay's heartbeat
4904 message. Implements ticket 5526; patch from Peter Retzlaff.
4905 - Implement the TRANSPORT_LAUNCHED control port event that
4906 notifies controllers about new launched pluggable
4907 transports. Resolves ticket 5609.
4908 - If we're using the pure-C 32-bit curve25519_donna implementation
4909 of curve25519, build it with the -fomit-frame-pointer option to
4910 make it go faster on register-starved hosts. This improves our
4911 handshake performance by about 6% on i386 hosts without nacl.
4913 - Update to the September 4 2013 Maxmind GeoLite Country database.
4916 - Set the listen() backlog limit to the largest actually supported
4917 on the system, not to the value in a header file. Fixes bug 9716;
4918 bugfix on every released Tor.
4919 - No longer accept malformed http headers when parsing urls from
4920 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4921 bugfix on 0.0.6pre1.
4922 - In munge_extrainfo_into_routerinfo(), check the return value of
4923 memchr(). This would have been a serious issue if we ever passed
4924 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4926 - On the chance that somebody manages to build Tor on a
4927 platform where time_t is unsigned, correct the way that
4928 microdesc_add_to_cache() handles negative time arguments.
4929 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4930 - Reject relative control socket paths and emit a warning. Previously,
4931 single-component control socket paths would be rejected, but Tor
4932 would not log why it could not validate the config. Fixes bug 9258;
4933 bugfix on 0.2.3.16-alpha.
4935 o Minor bugfixes (command line):
4936 - Use a single command-line parser for parsing torrc options on the
4937 command line and for finding special command-line options to avoid
4938 inconsistent behavior for torrc option arguments that have the same
4939 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4941 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4942 9573; bugfix on 0.0.9pre5.
4944 o Minor fixes (build, auxiliary programs):
4945 - Stop preprocessing the "torify" script with autoconf, since
4946 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4948 - The tor-fw-helper program now follows the standard convention and
4949 exits with status code "0" on success. Fixes bug 9030; bugfix on
4950 0.2.3.1-alpha. Patch by Arlo Breault.
4951 - Corrected ./configure advice for what openssl dev package you should
4952 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4954 o Minor code improvements:
4955 - Remove constants and tests for PKCS1 padding; it's insecure and
4956 shouldn't be used for anything new. Fixes bug 8792; patch
4958 - Remove instances of strcpy() from the unit tests. They weren't
4959 hurting anything, since they were only in the unit tests, but it's
4960 embarassing to have strcpy() in the code at all, and some analysis
4961 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4962 0.2.3.8-alpha. Patch from Arlo Breault.
4965 - Remove migration code from when we renamed the "cached-routers"
4966 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4967 incidentally resolves ticket 6502 by cleaning up the related code
4968 a bit. Patch from Akshay Hebbar.
4970 o Code simplification and refactoring:
4971 - Extract the common duplicated code for creating a subdirectory
4972 of the data directory and writing to a file in it. Fixes ticket
4973 4282; patch from Peter Retzlaff.
4974 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4975 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4976 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4977 - Add a set of accessor functions for the circuit timeout data
4978 structure. Fixes ticket 6153; patch from "piet".
4979 - Clean up exit paths from connection_listener_new(). Closes ticket
4980 8789. Patch from Arlo Breault.
4981 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4982 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4983 - Use a doubly-linked list to implement the global circuit list.
4984 Resolves ticket 9108. Patch from Marek Majkowski.
4985 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4988 Changes in version 0.2.4.17-rc - 2013-09-05
4989 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
4990 series. It adds an emergency step to help us tolerate the massive
4991 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
4992 circuit-level handshakes now effectively jump the queue compared to
4993 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
4994 big bug hindering bridge reachability tests.
4997 - Relays now process the new "NTor" circuit-level handshake requests
4998 with higher priority than the old "TAP" circuit-level handshake
4999 requests. We still process some TAP requests to not totally starve
5000 0.2.3 clients when NTor becomes popular. A new consensus parameter
5001 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5002 Implements ticket 9574.
5005 - If the circuit build timeout logic is disabled (via the consensus,
5006 or because we are an authority), then don't build testing circuits.
5007 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5008 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5009 previously they did not, which prevented them from receiving
5010 successful connections from relays for self-test or bandwidth
5011 testing. Also, when a relay is extending a circuit to a bridge,
5012 it needs to send a NETINFO cell, even when the bridge hasn't sent
5013 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5014 - If the time to download the next old-style networkstatus is in
5015 the future, do not decline to consider whether to download the
5016 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5020 - Avoid double-closing the listener socket in our socketpair()
5021 replacement (used on Windows) in the case where the addresses on
5022 our opened sockets don't match what we expected. Fixes bug 9400;
5023 bugfix on 0.0.2pre7. Found by Coverity.
5025 o Minor fixes (config options):
5026 - Avoid overflows when the user sets MaxCircuitDirtiness to a
5027 ridiculously high value, by imposing a (ridiculously high) 30-day
5028 maximum on MaxCircuitDirtiness.
5029 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
5030 message is logged at notice, not at info.
5031 - Warn and fail if a server is configured not to advertise any
5032 ORPorts at all. (We need *something* to put in our descriptor,
5033 or we just won't work.)
5036 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5037 and how many we complete, and log it every hour to help relay
5038 operators follow trends in network load. Addresses ticket 9658.
5039 - Update to the August 7 2013 Maxmind GeoLite Country database.
5042 Changes in version 0.2.4.16-rc - 2013-08-10
5043 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
5044 series. It fixes several crash bugs in the 0.2.4 branch.
5047 - Fix a bug in the voting algorithm that could yield incorrect results
5048 when a non-naming authority declared too many flags. Fixes bug 9200;
5049 bugfix on 0.2.0.3-alpha.
5050 - Fix an uninitialized read that could in some cases lead to a remote
5051 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
5052 Anybody running a hidden service on the experimental 0.2.4.x
5053 branch should upgrade. (This is, so far as we know, unrelated to
5055 - Avoid an assertion failure when processing DNS replies without the
5056 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
5057 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
5058 0.2.4.15-rc. Found by stem integration tests.
5061 - Fix an invalid memory read that occured when a pluggable
5062 transport proxy failed its configuration protocol.
5063 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
5064 - When evaluating whether to use a connection that we haven't
5065 decided is canonical using a recent link protocol version,
5066 decide that it's canonical only if it used address _does_
5067 match the desired address. Fixes bug 9309; bugfix on
5068 0.2.4.4-alpha. Reported by skruffy.
5069 - Make the default behavior of NumDirectoryGuards be to track
5070 NumEntryGuards. Now a user who changes only NumEntryGuards will get
5071 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
5072 - Fix a spurious compilation warning with some older versions of
5073 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
5076 - Update to the July 3 2013 Maxmind GeoLite Country database.
5079 Changes in version 0.2.4.15-rc - 2013-07-01
5080 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
5081 series. It fixes a few smaller bugs, but generally appears stable.
5082 Please test it and let us know whether it is!
5085 - When receiving a new configuration file via the control port's
5086 LOADCONF command, do not treat the defaults file as absent.
5087 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5090 - Issue a warning when running with the bufferevents backend enabled.
5091 It's still not stable, and people should know that they're likely
5092 to hit unexpected problems. Closes ticket 9147.
5095 Changes in version 0.2.4.14-alpha - 2013-06-18
5096 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
5097 present in 0.2.4.13-alpha.
5100 - When we have too much memory queued in circuits (according to a new
5101 MaxMemInCellQueues option), close the circuits consuming the most
5102 memory. This prevents us from running out of memory as a relay if
5103 circuits fill up faster than they can be drained. Fixes bug 9063;
5104 bugfix on the 54th commit of Tor. This bug is a further fix beyond
5105 bug 6252, whose fix was merged into 0.2.3.21-rc.
5107 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
5108 where we tried to solve this issue simply by imposing an upper limit
5109 on the number of queued cells for a single circuit. That approach
5110 proved to be problematic, since there are ways to provoke clients to
5111 send a number of cells in excess of any such reasonable limit. Fixes
5112 bug 9072; bugfix on 0.2.4.13-alpha.
5114 - Limit hidden service descriptors to at most ten introduction
5115 points, to slow one kind of guard enumeration. Fixes bug 9002;
5116 bugfix on 0.1.1.11-alpha.
5119 Changes in version 0.2.4.13-alpha - 2013-06-14
5120 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
5121 vulnerabilities, makes socks5 username/password circuit isolation
5122 actually actually work (this time for sure!), and cleans up a bunch
5123 of other issues in preparation for a release candidate.
5125 o Major bugfixes (robustness):
5126 - Close any circuit that has too many cells queued on it. Fixes
5127 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
5128 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
5129 - Prevent the get_freelists() function from running off the end of
5130 the list of freelists if it somehow gets an unrecognized
5131 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5133 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5134 when an exit connection with optimistic data succeeds immediately
5135 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5137 - Fix a directory authority crash bug when building a consensus
5138 using an older consensus as its basis. Fixes bug 8833. Bugfix
5142 - Avoid a memory leak where we would leak a consensus body when we
5143 find that a consensus which we couldn't previously verify due to
5144 missing certificates is now verifiable. Fixes bug 8719; bugfix
5146 - We used to always request authority certificates by identity digest,
5147 meaning we'd get the newest one even when we wanted one with a
5148 different signing key. Then we would complain about being given
5149 a certificate we already had, and never get the one we really
5150 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5151 resource to request the one we want. Fixes bug 5595; bugfix on
5153 - Follow the socks5 protocol when offering username/password
5154 authentication. The fix for bug 8117 exposed this bug, and it
5155 turns out real-world applications like Pidgin do care. Bugfix on
5156 0.2.3.2-alpha; fixes bug 8879.
5157 - Prevent failures on Windows Vista and later when rebuilding the
5158 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
5159 bugfix on 0.2.4.12-alpha.
5162 - Fix an impossible buffer overrun in the AES unit tests. Fixes
5163 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
5164 - If for some reason we fail to write a microdescriptor while
5165 rebuilding the cache, do not let the annotations from that
5166 microdescriptor linger in the cache file, and do not let the
5167 microdescriptor stay recorded as present in its old location.
5168 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
5169 - Fix a memory leak that would occur whenever a configuration
5170 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5171 - Paste the description for PathBias parameters from the man
5172 page into or.h, so the code documents them too. Fixes bug 7982;
5173 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
5174 - Relays now treat a changed IPv6 ORPort as sufficient reason to
5175 publish an updated descriptor. Fixes bug 6026; bugfix on
5177 - When launching a resolve request on behalf of an AF_UNIX control
5178 socket, omit the address field of the new entry connection, used in
5179 subsequent controller events, rather than letting tor_dup_addr()
5180 set it to "<unknown address type>". Fixes bug 8639; bugfix on
5183 o Minor bugfixes (log messages):
5184 - Fix a scaling issue in the path bias accounting code that
5185 resulted in "Bug:" log messages from either
5186 pathbias_scale_close_rates() or pathbias_count_build_success().
5187 This represents a bugfix on a previous bugfix: the original fix
5188 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
5190 - Give a less useless error message when the user asks for an IPv4
5191 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
5195 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
5196 to tolerate bug 8093 for now.
5197 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5198 in directory authority votes to describe whether they have enough
5199 measured bandwidths to ignore advertised (relay descriptor)
5200 bandwidth claims. Resolves ticket 8711.
5201 - Update to the June 5 2013 Maxmind GeoLite Country database.
5203 o Removed documentation:
5204 - Remove some of the older contents of doc/ as obsolete; move others
5205 to torspec.git. Fixes bug 8965.
5207 o Code simplification and refactoring:
5208 - Avoid using character buffers when constructing most directory
5209 objects: this approach was unwieldy and error-prone. Instead,
5210 build smartlists of strings, and concatenate them when done.
5213 Changes in version 0.2.4.12-alpha - 2013-04-18
5214 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
5215 process for lengthening the guard rotation period, makes directory
5216 authority opinions in the consensus a bit less gameable, makes socks5
5217 username/password circuit isolation actually work, and fixes a wide
5218 variety of other issues.
5221 - Raise the default time that a client keeps an entry guard from
5222 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5223 2012 paper. (We would make it even longer, but we need better client
5224 load balancing first.) Also, make the guard lifetime controllable
5225 via a new GuardLifetime torrc option and a GuardLifetime consensus
5226 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5227 - Directory authorities now prefer using measured bandwidths to
5228 advertised ones when computing flags and thresholds. Resolves
5230 - Directory authorities that have more than a threshold number
5231 of relays with measured bandwidths now treat relays with unmeasured
5232 bandwidths as having bandwidth 0. Resolves ticket 8435.
5234 o Major bugfixes (assert / resource use):
5235 - Avoid a bug where our response to TLS renegotiation under certain
5236 network conditions could lead to a busy-loop, with 100% CPU
5237 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5238 - Avoid an assertion when we discover that we'd like to write a cell
5239 onto a closing connection: just discard the cell. Fixes another
5240 case of bug 7350; bugfix on 0.2.4.4-alpha.
5242 o Major bugfixes (client-side privacy):
5243 - When we mark a circuit as unusable for new circuits, have it
5244 continue to be unusable for new circuits even if MaxCircuitDirtiness
5245 is increased too much at the wrong time, or the system clock jumps
5246 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5247 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5248 which have resolved to internal addresses") is set, apply that
5249 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5250 - When an exit relay rejects a stream with reason "exit policy", but
5251 we only know an exit policy summary (e.g. from the microdesc
5252 consensus) for it, do not mark the relay as useless for all exiting.
5253 Instead, mark just the circuit as unsuitable for that particular
5254 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5255 - Allow applications to get proper stream isolation with
5256 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5257 username/password authentication also offer "no authentication". Tor
5258 had previously preferred "no authentication", so the applications
5259 never actually sent Tor their auth details. Now Tor selects
5260 username/password authentication if it's offered. You can disable
5261 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5262 bug 8117; bugfix on 0.2.3.3-alpha.
5264 o Major bugfixes (other):
5265 - When unable to find any working directory nodes to use as a
5266 directory guard, give up rather than adding the same non-working
5267 nodes to the directory guard list over and over. Fixes bug 8231;
5268 bugfix on 0.2.4.8-alpha.
5271 - Reject as invalid most directory objects containing a NUL.
5272 Belt-and-suspender fix for bug 8037.
5273 - In our testsuite, create temporary directories with a bit more
5274 entropy in their name to make name collisions less likely. Fixes
5276 - Add CACHED keyword to ADDRMAP events in the control protocol
5277 to indicate whether a DNS result will be cached or not. Resolves
5279 - Update to the April 3 2013 Maxmind GeoLite Country database.
5281 o Minor features (build):
5282 - Detect and reject attempts to build Tor with threading support
5283 when OpenSSL has been compiled without threading support.
5285 - Clarify that when autoconf is checking for nacl, it is checking
5286 specifically for nacl with a fast curve25519 implementation.
5288 - Warn if building on a platform with an unsigned time_t: there
5289 are too many places where Tor currently assumes that time_t can
5290 hold negative values. We'd like to fix them all, but probably
5293 o Minor bugfixes (build):
5294 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
5295 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
5296 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
5297 - Add the old src/or/micro-revision.i filename to CLEANFILES.
5298 On the off chance that somebody has one, it will go away as soon
5299 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
5300 - Build Tor correctly on 32-bit platforms where the compiler can build
5301 but not run code using the "uint128_t" construction. Fixes bug 8587;
5302 bugfix on 0.2.4.8-alpha.
5303 - Fix compilation warning with some versions of clang that would
5304 prefer the -Wswitch-enum compiler flag to warn about switch
5305 statements with missing enum values, even if those switch
5306 statements have a "default:" statement. Fixes bug 8598; bugfix
5309 o Minor bugfixes (protocol):
5310 - Fix the handling of a TRUNCATE cell when it arrives while the
5311 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5312 - Fix a misframing issue when reading the version numbers in a
5313 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5314 'version 1, version 2, and version 0x100', when it should have
5315 only included versions 1 and 2. Fixes bug 8059; bugfix on
5316 0.2.0.10-alpha. Reported pseudonymously.
5317 - Make the format and order of STREAM events for DNS lookups
5318 consistent among the various ways to launch DNS lookups. Fixes
5319 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
5320 - Correct our check for which versions of Tor support the EXTEND2
5321 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
5322 later, when support was really added in version 0.2.4.8-alpha.
5323 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
5325 o Minor bugfixes (other):
5326 - Correctly store microdescriptors and extrainfo descriptors with
5327 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
5328 Bug reported by "cypherpunks".
5329 - Increase the width of the field used to remember a connection's
5330 link protocol version to two bytes. Harmless for now, since the
5331 only currently recognized versions are one byte long. Reported
5332 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5333 - If the state file's path bias counts are invalid (presumably from a
5334 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5335 additional checks and log messages to the scaling of Path Bias
5336 counts, in case there still are remaining issues with scaling.
5337 Should help resolve bug 8235.
5338 - Eliminate several instances where we use "Nickname=ID" to refer to
5339 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5340 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5341 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
5343 o Minor bugfixes (syscalls):
5344 - Always check the return values of functions fcntl() and
5345 setsockopt(). We don't believe these are ever actually failing in
5346 practice, but better safe than sorry. Also, checking these return
5347 values should please analysis tools like Coverity. Patch from
5348 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5349 - Use direct writes rather than stdio when building microdescriptor
5350 caches, in an attempt to mitigate bug 8031, or at least make it
5353 o Minor bugfixes (config):
5354 - When rejecting a configuration because we were unable to parse a
5355 quoted string, log an actual error message. Fixes bug 7950; bugfix
5357 - Behave correctly when the user disables LearnCircuitBuildTimeout
5358 but doesn't tell us what they would like the timeout to be. Fixes
5359 bug 6304; bugfix on 0.2.2.14-alpha.
5360 - When autodetecting the number of CPUs, use the number of available
5361 CPUs in preference to the number of configured CPUs. Inform the
5362 user if this reduces the number of available CPUs. Fixes bug 8002;
5363 bugfix on 0.2.3.1-alpha.
5364 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5365 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5366 bug 8180; bugfix on 0.2.3.11-alpha.
5367 - Allow TestingTorNetworks to override the 4096-byte minimum for
5368 the Fast threshold. Otherwise they can't bootstrap until they've
5369 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
5370 - Fix some logic errors when the user manually overrides the
5371 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
5374 o Minor bugfixes (log messages to help diagnose bugs):
5375 - If we fail to free a microdescriptor because of bug 7164, log
5376 the filename and line number from which we tried to free it.
5377 - Add another diagnostic to the heartbeat message: track and log
5378 overhead that TLS is adding to the data we write. If this is
5379 high, we are sending too little data to SSL_write at a time.
5380 Diagnostic for bug 7707.
5381 - Add more detail to a log message about relaxed timeouts, to help
5383 - Warn more aggressively when flushing microdescriptors to a
5384 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5385 or at least make it more diagnosable.
5386 - Improve debugging output to help track down bug 8185 ("Bug:
5387 outgoing relay cell has n_chan==NULL. Dropping.")
5388 - Log the purpose of a path-bias testing circuit correctly.
5389 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
5391 o Minor bugfixes (0.2.4.x log messages that were too noisy):
5392 - Don't attempt to relax the timeout of already opened 1-hop circuits.
5393 They might never timeout. This should eliminate some/all cases of
5394 the relaxed timeout log message.
5395 - Use circuit creation time for network liveness evaluation. This
5396 should eliminate warning log messages about liveness caused
5397 by changes in timeout evaluation. Fixes bug 6572; bugfix on
5399 - Reduce a path bias length check from notice to info. The message
5400 is triggered when creating controller circuits. Fixes bug 8196;
5401 bugfix on 0.2.4.8-alpha.
5402 - Fix a path state issue that triggered a notice during relay startup.
5403 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
5404 - Reduce occurrences of warns about circuit purpose in
5405 connection_ap_expire_building(). Fixes bug 8477; bugfix on
5408 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
5409 - If we encounter a write failure on a SOCKS connection before we
5410 finish our SOCKS handshake, don't warn that we closed the
5411 connection before we could send a SOCKS reply. Fixes bug 8427;
5412 bugfix on 0.1.0.1-rc.
5413 - Correctly recognize that [::1] is a loopback address. Fixes
5414 bug 8377; bugfix on 0.2.1.3-alpha.
5415 - Fix a directory authority warn caused when we have a large amount
5416 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
5417 - Don't log inappropriate heartbeat messages when hibernating: a
5418 hibernating node is _expected_ to drop out of the consensus,
5419 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
5420 bugfix on 0.2.3.1-alpha.
5421 - Don't complain about bootstrapping problems while hibernating.
5422 These complaints reflect a general code problem, but not one
5423 with any problematic effects (no connections are actually
5424 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5426 o Documentation fixes:
5427 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
5428 names match. Fixes bug 7768.
5429 - Make the torify manpage no longer refer to tsocks; torify hasn't
5430 supported tsocks since 0.2.3.14-alpha.
5431 - Make the tor manpage no longer reference tsocks.
5432 - Fix the GeoIPExcludeUnknown documentation to refer to
5433 ExcludeExitNodes rather than the currently nonexistent
5434 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
5437 - The tor-tsocks.conf is no longer distributed or installed. We
5438 recommend that tsocks users use torsocks instead. Resolves
5442 Changes in version 0.2.4.11-alpha - 2013-03-11
5443 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
5444 more robust, makes hidden service authentication work again, and
5445 resolves a DPI fingerprint for Tor's SSL transport.
5447 o Major features (directory authorities):
5448 - Directory authorities now support a new consensus method (17)
5449 where they cap the published bandwidth of servers for which
5450 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5451 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5452 serve any v2 directory information. Now we can test disabling the
5453 old deprecated v2 directory format, and see whether doing so has
5454 any effect on network load. Begins to fix bug 6783.
5455 - Directory authorities now include inside each vote a statement of
5456 the performance thresholds they used when assigning flags.
5457 Implements ticket 8151.
5459 o Major bugfixes (directory authorities):
5460 - Stop marking every relay as having been down for one hour every
5461 time we restart a directory authority. These artificial downtimes
5462 were messing with our Stable and Guard flag calculations. Fixes
5463 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5465 o Major bugfixes (hidden services):
5466 - Allow hidden service authentication to succeed again. When we
5467 refactored the hidden service introduction code back
5468 in 0.2.4.1-alpha, we didn't update the code that checks
5469 whether authentication information is present, causing all
5470 authentication checks to return "false". Fix for bug 8207; bugfix
5471 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
5473 o Minor features (relays, bridges):
5474 - Make bridge relays check once a minute for whether their IP
5475 address has changed, rather than only every 15 minutes. Resolves
5477 - Refactor resolve_my_address() so it returns the method by which we
5478 decided our public IP address (explicitly configured, resolved from
5479 explicit hostname, guessed from interfaces, learned by gethostname).
5480 Now we can provide more helpful log messages when a relay guesses
5481 its IP address incorrectly (e.g. due to unexpected lines in
5482 /etc/hosts). Resolves ticket 2267.
5483 - Teach bridge-using clients to avoid 0.2.2 bridges when making
5484 microdescriptor-related dir requests, and only fall back to normal
5485 descriptors if none of their bridges can handle microdescriptors
5486 (as opposed to the fix in ticket 4013, which caused them to fall
5487 back to normal descriptors if *any* of their bridges preferred
5488 them). Resolves ticket 4994.
5489 - Randomize the lifetime of our SSL link certificate, so censors can't
5490 use the static value for filtering Tor flows. Resolves ticket 8443;
5491 related to ticket 4014 which was included in 0.2.2.33.
5492 - Support a new version of the link protocol that allows 4-byte circuit
5493 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
5494 a possible resource exhaustion issue. Closes ticket 7351; implements
5497 o Minor features (portability):
5498 - Tweak the curve25519-donna*.c implementations to tolerate systems
5499 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
5500 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5501 the signs of types during autoconf. This is better than our old
5502 approach, which didn't work when cross-compiling.
5503 - Detect the sign of enum values, rather than assuming that MSC is the
5504 only compiler where enum types are all signed. Fixes bug 7727;
5505 bugfix on 0.2.4.10-alpha.
5507 o Minor features (other):
5508 - Say "KBytes" rather than "KB" in the man page (for various values
5509 of K), to further reduce confusion about whether Tor counts in
5510 units of memory or fractions of units of memory. Resolves ticket 7054.
5511 - Clear the high bit on curve25519 public keys before passing them to
5512 our backend, in case we ever wind up using a backend that doesn't do
5513 so itself. If we used such a backend, and *didn't* clear the high bit,
5514 we could wind up in a situation where users with such backends would
5515 be distinguishable from users without. Fixes bug 8121; bugfix on
5517 - Update to the March 6 2013 Maxmind GeoLite Country database.
5519 o Minor bugfixes (clients):
5520 - When we receive a RELAY_END cell with the reason DONE, or with no
5521 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
5522 status as "connection refused". Previously we reported these cases
5523 as success but then immediately closed the connection. Fixes bug
5524 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
5525 - Downgrade an assertion in connection_ap_expire_beginning to an
5526 LD_BUG message. The fix for bug 8024 should prevent this message
5527 from displaying, but just in case, a warn that we can diagnose
5528 is better than more assert crashes. Fixes bug 8065; bugfix on
5530 - Lower path use bias thresholds to .80 for notice and .60 for warn.
5531 Also make the rate limiting flags for the path use bias log messages
5532 independent from the original path bias flags. Fixes bug 8161;
5533 bugfix on 0.2.4.10-alpha.
5535 o Minor bugfixes (relays):
5536 - Stop trying to resolve our hostname so often (e.g. every time we
5537 think about doing a directory fetch). Now we reuse the cached
5538 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
5539 and 2410 (bugfix on 0.1.2.2-alpha).
5540 - Stop sending a stray "(null)" in some cases for the server status
5541 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
5543 - When choosing which stream on a formerly stalled circuit to wake
5544 first, make better use of the platform's weak RNG. Previously,
5545 we had been using the % ("modulo") operator to try to generate a
5546 1/N chance of picking each stream, but this behaves badly with
5547 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
5549 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5550 Irix's random() only return 15 bits; Solaris's random() returns more
5551 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5552 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5554 o Minor bugfixes (directory authorities):
5555 - Directory authorities now use less space when formatting identical
5556 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
5559 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
5560 - Avoid leaking memory if we fail to compute a consensus signature
5561 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
5562 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
5564 - Fix a memory leak during safe-cookie controller authentication.
5565 Bugfix on 0.2.3.13-alpha.
5566 - Avoid memory leak of IPv6 policy content if we fail to format it into
5567 a router descriptor. Bugfix on 0.2.4.7-alpha.
5569 o Minor bugfixes (other code correctness issues):
5570 - Avoid a crash if we fail to generate an extrainfo descriptor.
5571 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
5573 - When detecting the largest possible file descriptor (in order to
5574 close all file descriptors when launching a new program), actually
5575 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
5576 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
5578 - Fix a copy-and-paste error when adding a missing A1 to a routerset
5579 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
5580 Bugfix on 0.2.4.10-alpha.
5581 - Fix an impossible-to-trigger integer overflow when estimating how
5582 long our onionskin queue would take. (This overflow would require us
5583 to accept 4 million onionskins before processing 100 of them.) Fixes
5584 bug 8210; bugfix on 0.2.4.10-alpha.
5586 o Code simplification and refactoring:
5587 - Add a wrapper function for the common "log a message with a
5591 Changes in version 0.2.4.10-alpha - 2013-02-04
5592 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
5593 certain attacks that flood the network with relays; changes the queue
5594 for circuit create requests from a sized-based limit to a time-based
5595 limit; resumes building with MSVC on Windows; and fixes a wide variety
5598 o Major bugfixes (directory authority):
5599 - When computing directory thresholds, ignore any rejected-as-sybil
5600 nodes during the computation so that they can't influence Fast,
5601 Guard, etc. (We should have done this for proposal 109.) Fixes
5603 - When marking a node as a likely sybil, reset its uptime metrics
5604 to zero, so that it cannot time towards getting marked as Guard,
5605 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5609 - When a TLS write is partially successful but incomplete, remember
5610 that the flushed part has been flushed, and notice that bytes were
5611 actually written. Reported and fixed pseudonymously. Fixes bug
5612 7708; bugfix on Tor 0.1.0.5-rc.
5613 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5614 ID: these could be used to create unexpected streams and circuits
5615 which would count as "present" to some parts of Tor but "absent"
5616 to others, leading to zombie circuits and streams or to a bandwidth
5617 denial-of-service. Fixes bug 7889; bugfix on every released version
5618 of Tor. Reported by "oftc_must_be_destroyed".
5619 - Rename all macros in our local copy of queue.h to begin with "TOR_".
5620 This change seems the only good way to permanently prevent conflicts
5621 with queue.h on various operating systems. Fixes bug 8107; bugfix
5624 o Major features (relay):
5625 - Instead of limiting the number of queued onionskins (aka circuit
5626 create requests) to a fixed, hard-to-configure number, we limit
5627 the size of the queue based on how many we expect to be able to
5628 process in a given amount of time. We estimate the time it will
5629 take to process an onionskin based on average processing time
5630 of previous onionskins. Closes ticket 7291. You'll never have to
5631 configure MaxOnionsPending again.
5633 o Major features (portability):
5634 - Resume building correctly with MSVC and Makefile.nmake. This patch
5635 resolves numerous bugs and fixes reported by ultramage, including
5636 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5637 - Make the ntor and curve25519 code build correctly with MSVC.
5638 Fix on 0.2.4.8-alpha.
5641 - When directory authorities are computing thresholds for flags,
5642 never let the threshold for the Fast flag fall below 4096
5643 bytes. Also, do not consider nodes with extremely low bandwidths
5644 when deciding thresholds for various directory flags. This change
5645 should raise our threshold for Fast relays, possibly in turn
5646 improving overall network performance; see ticket 1854. Resolves
5648 - The Tor client now ignores sub-domain components of a .onion
5649 address. This change makes HTTP "virtual" hosting
5650 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5651 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5652 hosted on the same hidden service. Implements proposal 204.
5653 - We compute the overhead from passing onionskins back and forth to
5654 cpuworkers, and report it when dumping statistics in response to
5655 SIGUSR1. Supports ticket 7291.
5657 o Minor features (path selection):
5658 - When deciding whether we have enough descriptors to build circuits,
5659 instead of looking at raw relay counts, look at which fraction
5660 of (bandwidth-weighted) paths we're able to build. This approach
5661 keeps clients from building circuits if their paths are likely to
5662 stand out statistically. The default fraction of paths needed is
5663 taken from the consensus directory; you can override it with the
5664 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5665 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5666 and we have GeoIP information, also exclude all nodes with unknown
5667 countries "??" and "A1". This behavior is controlled by the
5668 new GeoIPExcludeUnknown option: you can make such nodes always
5669 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5670 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5671 gets you the default behavior. Implements feature 7706.
5672 - Path Use Bias: Perform separate accounting for successful circuit
5673 use. Keep separate statistics on stream attempt rates versus stream
5674 success rates for each guard. Provide configurable thresholds to
5675 determine when to emit log messages or disable use of guards that
5676 fail too many stream attempts. Resolves ticket 7802.
5678 o Minor features (log messages):
5679 - When learning a fingerprint for a bridge, log its corresponding
5680 transport type. Implements ticket 7896.
5681 - Improve the log message when "Bug/attack: unexpected sendme cell
5682 from client" occurs, to help us track bug 8093.
5685 - Remove a couple of extraneous semicolons that were upsetting the
5686 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
5687 bugfix on 0.2.2.1-alpha.
5688 - Remove a source of rounding error during path bias count scaling;
5689 don't count cannibalized circuits as used for path bias until we
5690 actually try to use them; and fix a circuit_package_relay_cell()
5691 warning message about n_chan==NULL. Fixes bug 7802.
5692 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
5693 actually link against nacl when we're configured to use it. Fixes
5694 bug 7972; bugfix on 0.2.4.8-alpha.
5695 - Compile correctly with the --disable-curve25519 option. Fixes
5696 bug 8153; bugfix on 0.2.4.8-alpha.
5698 o Build improvements:
5699 - Do not report status verbosely from autogen.sh unless the -v flag
5700 is specified. Fixes issue 4664. Patch from Onizuka.
5701 - Replace all calls to snprintf() outside of src/ext with
5702 tor_snprintf(). Also remove the #define to replace snprintf with
5703 _snprintf on Windows; they have different semantics, and all of
5704 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5705 - Try to detect if we are ever building on a platform where
5706 memset(...,0,...) does not set the value of a double to 0.0. Such
5707 platforms are permitted by the C standard, though in practice
5708 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5709 currently support them, but it's better to detect them and fail
5710 than to perform erroneously.
5713 - Stop exporting estimates of v2 and v3 directory traffic shares
5714 in extrainfo documents. They were unneeded and sometimes inaccurate.
5715 Also stop exporting any v2 directory request statistics. Resolves
5717 - Drop support for detecting and warning about versions of Libevent
5718 before 1.3e. Nothing reasonable ships with them any longer;
5719 warning the user about them shouldn't be needed. Resolves ticket
5722 o Code simplifications and refactoring:
5723 - Rename "isin" functions to "contains", for grammar. Resolves
5725 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5726 with the natural logarithm function from the system libm. Resolves
5730 Changes in version 0.2.4.9-alpha - 2013-01-15
5731 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5735 - Fix backward compatibility logic when receiving an embedded ntor
5736 handshake tunneled in a CREATE cell. This clears up the "Bug:
5737 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5741 Changes in version 0.2.4.8-alpha - 2013-01-14
5742 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5743 risks, adds a new stronger and faster circuit handshake, and offers
5744 stronger and faster link encryption when both sides support it.
5747 - Preliminary support for directory guards (proposal 207): when
5748 possible, clients now use their entry guards for non-anonymous
5749 directory requests. This can help prevent client enumeration. Note
5750 that this behavior only works when we have a usable consensus
5751 directory, and when options about what to download are more or less
5752 standard. In the future we should re-bootstrap from our guards,
5753 rather than re-bootstrapping from the preconfigured list of
5754 directory sources that ships with Tor. Resolves ticket 6526.
5755 - Tor relays and clients now support a better CREATE/EXTEND cell
5756 format, allowing the sender to specify multiple address, identity,
5757 and handshake types. Implements Robert Ransom's proposal 200;
5760 o Major features (new circuit handshake):
5761 - Tor now supports a new circuit extension handshake designed by Ian
5762 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5763 circuit extension handshake, later called "TAP", was a bit slow
5764 (especially on the relay side), had a fragile security proof, and
5765 used weaker keys than we'd now prefer. The new circuit handshake
5766 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5767 function, making it significantly more secure than the older
5768 handshake, and significantly faster. Tor can use one of two built-in
5769 pure-C curve25519-donna implementations by Adam Langley, or it
5770 can link against the "nacl" library for a tuned version if present.
5772 The built-in version is very fast for 64-bit systems when building
5773 with GCC. The built-in 32-bit version is still faster than the
5774 old TAP protocol, but using libnacl is better on most such hosts.
5776 Clients don't currently use this protocol by default, since
5777 comparatively few clients support it so far. To try it, set
5778 UseNTorHandshake to 1.
5780 Implements proposal 216; closes ticket 7202.
5782 o Major features (better link encryption):
5783 - Relays can now enable the ECDHE TLS ciphersuites when available
5784 and appropriate. These ciphersuites let us negotiate forward-secure
5785 TLS secret keys more safely and more efficiently than with our
5786 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5787 public relays prefer the (faster) P224 group, and bridges prefer
5788 the (more common) P256 group; you can override this with the
5791 Enabling these ciphers was a little tricky, since for a long time,
5792 clients had been claiming to support them without actually doing
5793 so, in order to foil fingerprinting. But with the client-side
5794 implementation of proposal 198 in 0.2.3.17-beta, clients can now
5795 match the ciphers from recent Firefox versions *and* list the
5796 ciphers they actually mean, so relays can believe such clients
5797 when they advertise ECDHE support in their TLS ClientHello messages.
5799 This feature requires clients running 0.2.3.17-beta or later,
5800 and requires both sides to be running OpenSSL 1.0.0 or later
5801 with ECC support. OpenSSL 1.0.1, with the compile-time option
5802 "enable-ec_nistp_64_gcc_128", is highly recommended.
5804 Implements the relay side of proposal 198; closes ticket 7200.
5807 - Avoid crashing when, as a relay without IPv6-exit support, a
5808 client insists on getting an IPv6 address or nothing. Fixes bug
5809 7814; bugfix on 0.2.4.7-alpha.
5812 - Improve circuit build timeout handling for hidden services.
5813 In particular: adjust build timeouts more accurately depending
5814 upon the number of hop-RTTs that a particular circuit type
5815 undergoes. Additionally, launch intro circuits in parallel
5816 if they timeout, and take the first one to reply as valid.
5817 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5818 separate error codes; or at least, don't break for that reason.
5819 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5820 - Update to the January 2 2013 Maxmind GeoLite Country database.
5822 o Minor features (testing):
5823 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5824 (P-256) Diffie-Hellman handshakes to src/or/bench.
5825 - Add benchmark functions to test onion handshake performance.
5827 o Minor features (path bias detection):
5828 - Alter the Path Bias log messages to be more descriptive in terms
5829 of reporting timeouts and other statistics.
5830 - Create three levels of Path Bias log messages, as opposed to just
5831 two. These are configurable via consensus as well as via the torrc
5832 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5833 The default values are 0.70, 0.50, and 0.30 respectively.
5834 - Separate the log message levels from the decision to drop guards,
5835 which also is available via torrc option PathBiasDropGuards.
5836 PathBiasDropGuards still defaults to 0 (off).
5837 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5838 in combination with PathBiasExtremeRate.
5839 - Increase the default values for PathBiasScaleThreshold and
5840 PathBiasCircThreshold from (200, 20) to (300, 150).
5841 - Add in circuit usage accounting to path bias. If we try to use a
5842 built circuit but fail for any reason, it counts as path bias.
5843 Certain classes of circuits where the adversary gets to pick your
5844 destination node are exempt from this accounting. Usage accounting
5845 can be specifically disabled via consensus parameter or torrc.
5846 - Convert all internal path bias state to double-precision floating
5847 point, to avoid roundoff error and other issues.
5848 - Only record path bias information for circuits that have completed
5849 *two* hops. Assuming end-to-end tagging is the attack vector, this
5850 makes us more resilient to ambient circuit failure without any
5851 detection capability loss.
5853 o Minor bugfixes (log messages):
5854 - Rate-limit the "No circuits are opened. Relaxed timeout for a
5855 circuit with channel state open..." message to once per hour to
5856 keep it from filling the notice logs. Mitigates bug 7799 but does
5857 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
5858 - Avoid spurious warnings when configuring multiple client ports of
5859 which only some are nonlocal. Previously, we had claimed that some
5860 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5863 o Code simplifications and refactoring:
5864 - Get rid of a couple of harmless clang warnings, where we compared
5865 enums to ints. These warnings are newly introduced in clang 3.2.
5866 - Split the onion.c file into separate modules for the onion queue
5867 and the different handshakes it supports.
5868 - Remove the marshalling/unmarshalling code for sending requests to
5869 cpuworkers over a socket, and instead just send structs. The
5870 recipient will always be the same Tor binary as the sender, so
5871 any encoding is overkill.
5874 Changes in version 0.2.4.7-alpha - 2012-12-24
5875 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
5876 directory mirrors for more robust bootstrapping; fixes more issues where
5877 clients with changing network conditions refuse to make any circuits;
5878 adds initial support for exiting to IPv6 addresses; resumes being able
5879 to update our GeoIP database, and includes the geoip6 file this time;
5880 turns off the client-side DNS cache by default due to privacy risks;
5881 and fixes a variety of other issues.
5883 o Major features (client resilience):
5884 - Add a new "FallbackDir" torrc option to use when we can't use
5885 a directory mirror from the consensus (either because we lack a
5886 consensus, or because they're all down). Currently, all authorities
5887 are fallbacks by default, and there are no other default fallbacks,
5888 but that will change. This option will allow us to give clients a
5889 longer list of servers to try to get a consensus from when first
5890 connecting to the Tor network, and thereby reduce load on the
5891 directory authorities. Implements proposal 206, "Preconfigured
5892 directory sources for bootstrapping". We also removed the old
5893 "FallbackNetworkstatus" option, since we never got it working well
5894 enough to use it. Closes bug 572.
5895 - If we have no circuits open, use a relaxed timeout (the
5896 95-percentile cutoff) until a circuit succeeds. This heuristic
5897 should allow Tor to succeed at building circuits even when the
5898 network connection drastically changes. Should help with bug 3443.
5900 o Major features (IPv6):
5901 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5902 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5903 exit policy reads as you would like: the address * applies to all
5904 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5905 addresses only. On the client side, you'll need to wait until the
5906 authorities have upgraded, wait for enough exits to support IPv6,
5907 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
5908 ticket 5547, implements proposal 117 as revised in proposal 208.
5910 We DO NOT recommend that clients with actual anonymity needs start
5911 using IPv6 over Tor yet, since not enough exits support it yet.
5913 o Major features (geoip database):
5914 - Maxmind began labelling Tor relays as being in country "A1",
5915 which breaks by-country node selection inside Tor. Now we use a
5916 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5917 file with real country codes. This script fixes about 90% of "A1"
5918 entries automatically and uses manual country code assignments to
5919 fix the remaining 10%. See src/config/README.geoip for details.
5920 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
5921 Country database, as modified above.
5923 o Major bugfixes (client-side DNS):
5924 - Turn off the client-side DNS cache by default. Updating and using
5925 the DNS cache is now configurable on a per-client-port
5926 level. SOCKSPort, DNSPort, etc lines may now contain
5927 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5928 cache these types of DNS answers when we receive them from an
5929 exit node in response to an application request on this port, and
5930 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5931 cached DNS answers of these types, we shouldn't use them. It's
5932 potentially risky to use cached DNS answers at the client, since
5933 doing so can indicate to one exit what answers we've gotten
5934 for DNS lookups in the past. With IPv6, this becomes especially
5935 problematic. Using cached DNS answers for requests on the same
5936 circuit would present less linkability risk, since all traffic
5937 on a circuit is already linkable, but it would also provide
5938 little performance benefit: the exit node caches DNS replies
5939 too. Implements a simplified version of Proposal 205. Implements
5942 o Major bugfixes (other):
5943 - Alter circuit build timeout measurement to start at the point
5944 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5945 initialization). This should make our timeout measurements more
5946 uniform. Previously, we were sometimes including ORconn setup time
5947 in our circuit build time measurements. Should resolve bug 3443.
5948 - Fix an assertion that could trigger in hibernate_go_dormant() when
5949 closing an or_connection_t: call channel_mark_for_close() rather
5950 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
5952 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
5953 7655; bugfix on 0.2.4.6-alpha.
5956 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5957 operators select the address where their pluggable transports will
5958 listen for connections. Resolves ticket 7013.
5959 - Allow an optional $ before the node identity digest in the
5960 controller command GETINFO ns/id/<identity>, for consistency with
5961 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5962 - Log packaged cell fullness as part of the heartbeat message.
5963 Diagnosis to try to determine the extent of bug 7743.
5965 o Minor features (IPv6):
5966 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5967 prefer to hand out virtual IPv6 addresses, since there are more of
5968 them and we can't run out. To override this behavior and make IPv4
5969 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5970 or DNSPort you're using for resolving. Implements ticket 7571.
5971 - AutomapHostsOnResolve responses are now randomized, to avoid
5972 annoying situations where Tor is restarted and applications
5973 connect to the wrong addresses.
5974 - Never try more than 1000 times to pick a new virtual address when
5975 AutomapHostsOnResolve is set. That's good enough so long as we
5976 aren't close to handing out our entire virtual address space;
5977 if you're getting there, it's best to switch to IPv6 virtual
5981 - The ADDRMAP command can no longer generate an ill-formed error
5982 code on a failed MAPADDRESS. It now says "internal" rather than
5983 an English sentence fragment with spaces in the middle. Bugfix on
5985 - Fix log messages and comments to avoid saying "GMT" when we mean
5986 "UTC". Fixes bug 6113.
5987 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5989 - Fix a crash when debugging unit tests on Windows: deallocate a
5990 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5991 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5994 - The DirServer option is now DirAuthority, for consistency with
5995 current naming patterns. You can still use the old DirServer form.
5997 o Code simplification and refactoring:
5998 - Move the client-side address-map/virtual-address/DNS-cache code
5999 out of connection_edge.c into a new addressmap.c module.
6000 - Remove unused code for parsing v1 directories and "running routers"
6001 documents. Fixes bug 6887.
6004 Changes in version 0.2.3.25 - 2012-11-19
6005 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6006 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6007 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6008 programmer, and friend. Unstinting in his dedication to the cause of
6009 freedom, he inspired and helped many of us as we began our work on
6010 anonymity, and inspires us still. Please honor his memory by writing
6011 software to protect people's freedoms, and by helping others to do so.
6013 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6014 significantly reduced directory overhead (via microdescriptors),
6015 enormous crypto performance improvements for fast relays on new
6016 enough hardware, a new v3 TLS handshake protocol that can better
6017 resist fingerprinting, support for protocol obfuscation plugins (aka
6018 pluggable transports), better scalability for hidden services, IPv6
6019 support for bridges, performance improvements like allowing clients
6020 to skip the first round-trip on the circuit ("optimistic data") and
6021 refilling token buckets more often, a new "stream isolation" design
6022 to isolate different applications on different circuits, and many
6023 stability, security, and privacy fixes.
6026 - Tor tries to wipe potentially sensitive data after using it, so
6027 that if some subsequent security failure exposes Tor's memory,
6028 the damage will be limited. But we had a bug where the compiler
6029 was eliminating these wipe operations when it decided that the
6030 memory was no longer visible to a (correctly running) program,
6031 hence defeating our attempt at defense in depth. We fix that
6032 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6033 is unlikely to optimize away. Future versions of Tor may use
6034 a less ridiculously heavy approach for this. Fixes bug 7352.
6035 Reported in an article by Andrey Karpov.
6038 - Fix a harmless bug when opting against publishing a relay descriptor
6039 because DisableNetwork is set. Fixes bug 7464; bugfix on
6043 Changes in version 0.2.4.6-alpha - 2012-11-13
6044 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
6045 makes our defense-in-depth memory wiping more reliable, and begins to
6046 count IPv6 addresses in bridge statistics,
6049 - Fix an assertion failure that could occur when closing a connection
6050 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
6052 - Tor tries to wipe potentially sensitive data after using it, so
6053 that if some subsequent security failure exposes Tor's memory,
6054 the damage will be limited. But we had a bug where the compiler
6055 was eliminating these wipe operations when it decided that the
6056 memory was no longer visible to a (correctly running) program,
6057 hence defeating our attempt at defense in depth. We fix that
6058 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6059 is unlikely to optimize away. Future versions of Tor may use
6060 a less ridiculously heavy approach for this. Fixes bug 7352.
6061 Reported in an article by Andrey Karpov.
6064 - Add GeoIP database for IPv6 addresses. The new config option
6066 - Bridge statistics now count bridge clients connecting over IPv6:
6067 bridge statistics files now list "bridge-ip-versions" and
6068 extra-info documents list "geoip6-db-digest". The control protocol
6069 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
6070 implementation by "shkoo", addressing ticket 5055.
6073 - Warn when we are binding low ports when hibernation is enabled;
6074 previously we had warned when we were _advertising_ low ports with
6075 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
6076 - Fix a harmless bug when opting against publishing a relay descriptor
6077 because DisableNetwork is set. Fixes bug 7464; bugfix on
6079 - Add warning message when a managed proxy dies during configuration.
6080 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
6081 - Fix a linking error when building tor-fw-helper without miniupnp.
6082 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
6083 - Check for closing an or_connection_t without going through correct
6084 channel functions; emit a warning and then call
6085 connection_or_close_for_error() so we don't assert as in bugs 7212
6087 - Compile correctly on compilers without C99 designated initializer
6088 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
6089 - Avoid a possible assert that can occur when channel_send_destroy() is
6090 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
6091 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
6092 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
6093 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
6094 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
6096 o Code simplification and refactoring:
6097 - Start using OpenBSD's implementation of queue.h, so that we don't
6098 need to hand-roll our own pointer and list structures whenever we
6099 need them. (We can't rely on a sys/queue.h, since some operating
6100 systems don't have them, and the ones that do have them don't all
6101 present the same extensions.)
6104 Changes in version 0.2.4.5-alpha - 2012-10-25
6105 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
6106 two important security vulnerabilities that could lead to remotely
6107 triggerable relay crashes, fix a major bug that was preventing clients
6108 from choosing suitable exit nodes, and refactor some of our code.
6110 o Major bugfixes (security, also in 0.2.3.24-rc):
6111 - Fix a group of remotely triggerable assertion failures related to
6112 incorrect link protocol negotiation. Found, diagnosed, and fixed
6113 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6115 - Fix a denial of service attack by which any directory authority
6116 could crash all the others, or by which a single v2 directory
6117 authority could crash everybody downloading v2 directory
6118 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6120 o Major bugfixes (also in 0.2.3.24-rc):
6121 - When parsing exit policy summaries from microdescriptors, we had
6122 previously been ignoring the last character in each one, so that
6123 "accept 80,443,8080" would be treated by clients as indicating
6124 a node that allows access to ports 80, 443, and 808. That would
6125 lead to clients attempting connections that could never work,
6126 and ignoring exit nodes that would support their connections. Now
6127 clients parse these exit policy summaries correctly. Fixes bug 7192;
6128 bugfix on 0.2.3.1-alpha.
6130 o Minor bugfixes (also in 0.2.3.24-rc):
6131 - Clients now consider the ClientRejectInternalAddresses config option
6132 when using a microdescriptor consensus stanza to decide whether
6133 an exit relay would allow exiting to an internal address. Fixes
6134 bug 7190; bugfix on 0.2.3.1-alpha.
6137 - Only disable TLS session ticket support when running as a TLS
6138 server. Now clients will blend better with regular Firefox
6139 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6141 o Code simplification and refactoring:
6142 - Start using OpenBSD's implementation of queue.h (originally by
6144 - Move the entry node code from circuitbuild.c to its own file.
6145 - Move the circuit build timeout tracking code from circuitbuild.c
6149 Changes in version 0.2.3.24-rc - 2012-10-25
6150 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
6151 could lead to remotely triggerable relay crashes, and fixes
6152 a major bug that was preventing clients from choosing suitable exit
6155 o Major bugfixes (security):
6156 - Fix a group of remotely triggerable assertion failures related to
6157 incorrect link protocol negotiation. Found, diagnosed, and fixed
6158 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6160 - Fix a denial of service attack by which any directory authority
6161 could crash all the others, or by which a single v2 directory
6162 authority could crash everybody downloading v2 directory
6163 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6166 - When parsing exit policy summaries from microdescriptors, we had
6167 previously been ignoring the last character in each one, so that
6168 "accept 80,443,8080" would be treated by clients as indicating
6169 a node that allows access to ports 80, 443, and 808. That would
6170 lead to clients attempting connections that could never work,
6171 and ignoring exit nodes that would support their connections. Now
6172 clients parse these exit policy summaries correctly. Fixes bug 7192;
6173 bugfix on 0.2.3.1-alpha.
6176 - Clients now consider the ClientRejectInternalAddresses config option
6177 when using a microdescriptor consensus stanza to decide whether
6178 an exit relay would allow exiting to an internal address. Fixes
6179 bug 7190; bugfix on 0.2.3.1-alpha.
6182 Changes in version 0.2.4.4-alpha - 2012-10-20
6183 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
6184 vulnerability introduced by a change in OpenSSL, fixes a remotely
6185 triggerable assert, and adds new channel_t and circuitmux_t abstractions
6186 that will make it easier to test new connection transport and cell
6187 scheduling algorithms.
6189 o New directory authorities (also in 0.2.3.23-rc):
6190 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6191 authority. Closes ticket 5749.
6193 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
6194 - Disable TLS session tickets. OpenSSL's implementation was giving
6195 our TLS session keys the lifetime of our TLS context objects, when
6196 perfect forward secrecy would want us to discard anything that
6197 could decrypt a link connection as soon as the link connection
6198 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6199 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6200 - Discard extraneous renegotiation attempts once the V3 link
6201 protocol has been initiated. Failure to do so left us open to
6202 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6203 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6205 o Internal abstraction features:
6206 - Introduce new channel_t abstraction between circuits and
6207 or_connection_t to allow for implementing alternate OR-to-OR
6208 transports. A channel_t is an abstract object which can either be a
6209 cell-bearing channel, which is responsible for authenticating and
6210 handshaking with the remote OR and transmitting cells to and from
6211 it, or a listening channel, which spawns new cell-bearing channels
6212 at the request of remote ORs. Implements part of ticket 6465.
6213 - Also new is the channel_tls_t subclass of channel_t, adapting it
6214 to the existing or_connection_t code. The V2/V3 protocol handshaking
6215 code which formerly resided in command.c has been moved below the
6216 channel_t abstraction layer and may be found in channeltls.c now.
6217 Implements the rest of ticket 6465.
6218 - Introduce new circuitmux_t storing the queue of circuits for
6219 a channel; this encapsulates and abstracts the queue logic and
6220 circuit selection policy, and allows the latter to be overridden
6221 easily by switching out a policy object. The existing EWMA behavior
6222 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
6224 o Required libraries:
6225 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
6226 strongly recommended.
6229 - Warn users who run hidden services on a Tor client with
6230 UseEntryGuards disabled that their hidden services will be
6231 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
6232 attack which motivated Tor to support entry guards in the first
6233 place). Resolves ticket 6889.
6234 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
6235 dhill. Resolves ticket 6982.
6236 - Option OutboundBindAddress can be specified multiple times and
6237 accepts IPv6 addresses. Resolves ticket 6876.
6239 o Minor bugfixes (also in 0.2.3.23-rc):
6240 - Don't serve or accept v2 hidden service descriptors over a
6241 relay's DirPort. It's never correct to do so, and disabling it
6242 might make it more annoying to exploit any bugs that turn up in the
6243 descriptor-parsing code. Fixes bug 7149.
6244 - Fix two cases in src/or/transports.c where we were calling
6245 fmt_addr() twice in a parameter list. Bug found by David
6246 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6247 - Fix memory leaks whenever we logged any message about the "path
6248 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6249 - When relays refuse a "create" cell because their queue of pending
6250 create cells is too big (typically because their cpu can't keep up
6251 with the arrival rate), send back reason "resource limit" rather
6252 than reason "internal", so network measurement scripts can get a
6253 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
6256 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6257 - Free some more still-in-use memory at exit, to make hunting for
6258 memory leaks easier. Resolves bug 7029.
6259 - When a Tor client gets a "truncated" relay cell, the first byte of
6260 its payload specifies why the circuit was truncated. We were
6261 ignoring this 'reason' byte when tearing down the circuit, resulting
6262 in the controller not being told why the circuit closed. Now we
6263 pass the reason from the truncated cell to the controller. Bugfix
6264 on 0.1.2.3-alpha; fixes bug 7039.
6265 - Downgrade "Failed to hand off onionskin" messages to "debug"
6266 severity, since they're typically redundant with the "Your computer
6267 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6268 - Make clients running with IPv6 bridges connect over IPv6 again,
6269 even without setting new config options ClientUseIPv6 and
6270 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
6271 - Use square brackets around IPv6 addresses in numerous places
6272 that needed them, including log messages, HTTPS CONNECT proxy
6273 requests, TransportProxy statefile entries, and pluggable transport
6274 extra-info lines. Fixes bug 7011; patch by David Fifield.
6276 o Code refactoring and cleanup:
6277 - Source files taken from other packages now reside in src/ext;
6278 previously they were scattered around the rest of Tor.
6279 - Avoid use of reserved identifiers in our C code. The C standard
6280 doesn't like us declaring anything that starts with an
6281 underscore, so let's knock it off before we get in trouble. Fix
6282 for bug 1031; bugfix on the first Tor commit.
6285 Changes in version 0.2.3.23-rc - 2012-10-20
6286 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
6287 vulnerability introduced by a change in OpenSSL, and fixes a variety
6288 of smaller bugs in preparation for the release.
6290 o New directory authorities:
6291 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6292 authority. Closes ticket 5749.
6294 o Major bugfixes (security/privacy):
6295 - Disable TLS session tickets. OpenSSL's implementation was giving
6296 our TLS session keys the lifetime of our TLS context objects, when
6297 perfect forward secrecy would want us to discard anything that
6298 could decrypt a link connection as soon as the link connection
6299 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6300 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6301 - Discard extraneous renegotiation attempts once the V3 link
6302 protocol has been initiated. Failure to do so left us open to
6303 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6304 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6307 - Fix a possible crash bug when checking for deactivated circuits
6308 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6309 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6311 o Minor bugfixes (on 0.2.3.x):
6312 - Fix two cases in src/or/transports.c where we were calling
6313 fmt_addr() twice in a parameter list. Bug found by David
6314 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6315 - Convert an assert in the pathbias code to a log message. The assert
6316 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6317 bugfix on 0.2.3.17-beta.
6318 - Fix memory leaks whenever we logged any message about the "path
6319 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6321 o Minor bugfixes (on 0.2.2.x and earlier):
6322 - Don't serve or accept v2 hidden service descriptors over a relay's
6323 DirPort. It's never correct to do so, and disabling it might
6324 make it more annoying to exploit any bugs that turn up in the
6325 descriptor-parsing code. Fixes bug 7149.
6326 - When relays refuse a "create" cell because their queue of pending
6327 create cells is too big (typically because their cpu can't keep up
6328 with the arrival rate), send back reason "resource limit" rather
6329 than reason "internal", so network measurement scripts can get a
6330 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6331 - Correct file sizes when reading binary files on Cygwin, to avoid
6332 a bug where Tor would fail to read its state file. Fixes bug 6844;
6333 bugfix on 0.1.2.7-alpha.
6334 - Avoid undefined behavior when parsing the list of supported
6335 rendezvous/introduction protocols in a hidden service descriptor.
6336 Previously, Tor would have confused (as-yet-unused) protocol version
6337 numbers greater than 32 with lower ones on many platforms. Fixes
6338 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6340 o Documentation fixes:
6341 - Clarify that hidden services are TCP only. Fixes bug 6024.
6344 Changes in version 0.2.4.3-alpha - 2012-09-22
6345 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
6346 assertion, resumes letting relays test reachability of their DirPort,
6347 and cleans up a bunch of smaller bugs.
6350 - Fix an assertion failure in tor_timegm() that could be triggered
6351 by a badly formatted directory object. Bug found by fuzzing with
6352 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6355 - Fix a possible crash bug when checking for deactivated circuits
6356 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6357 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6358 - Allow routers to detect that their own DirPorts are running. When
6359 we removed support for versions_supports_begindir, we also
6360 accidentally removed the mechanism we used to self-test our
6361 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
6362 bugfix on 0.2.4.2-alpha.
6364 o Security features:
6365 - Switch to a completely time-invariant approach for picking nodes
6366 weighted by bandwidth. Our old approach would run through the
6367 part of the loop after it had made its choice slightly slower
6368 than it ran through the part of the loop before it had made its
6369 choice. Addresses ticket 6538.
6370 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
6371 by tor2web clients allows hidden services to identify tor2web
6372 clients through their repeated selection of the same rendezvous
6373 and introduction point circuit endpoints (their guards). Resolves
6377 - Enable Tor to read configuration, state, and key information from
6378 a FIFO. Previously Tor would only read from files with a positive
6379 stat.st_size. Code from meejah; fixes bug 6044.
6382 - Correct file sizes when reading binary files on Cygwin, to avoid
6383 a bug where Tor would fail to read its state file. Fixes bug 6844;
6384 bugfix on 0.1.2.7-alpha.
6385 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6386 bugfix on 0.2.0.3-alpha.
6387 - When complaining about a client port on a public address, log
6388 which address we're complaining about. Fixes bug 4020; bugfix on
6389 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6390 - Convert an assert in the pathbias code to a log message. The assert
6391 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6392 bugfix on 0.2.3.17-beta.
6393 - Our new buildsystem was overzealous about rebuilding manpages: it
6394 would rebuild them all whenever any one of them changed. Now our
6395 dependency checking should be correct. Fixes bug 6843; bugfix on
6397 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
6398 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
6399 - Correct log printout about which address family is preferred
6400 when connecting to a bridge with both an IPv4 and IPv6 OR port.
6401 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
6403 o Minor bugfixes (code cleanliness):
6404 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6405 with large values. This situation was untriggered, but nevertheless
6406 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6407 - Reject consensus votes with more than 64 known-flags. We aren't even
6408 close to that limit yet, and our code doesn't handle it correctly.
6409 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6410 - Avoid undefined behavior when parsing the list of supported
6411 rendezvous/introduction protocols in a hidden service descriptor.
6412 Previously, Tor would have confused (as-yet-unused) protocol version
6413 numbers greater than 32 with lower ones on many platforms. Fixes
6414 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6415 - Fix handling of rendezvous client authorization types over 8.
6416 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6417 - Fix building with older versions of GCC (2.95, for one) that don't
6418 like preprocessor directives inside macro arguments. Found by
6419 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
6420 - Switch weighted node selection rule from using a list of doubles
6421 to using a list of int64_t. This change should make the process
6422 slightly easier to debug and maintain. Needed to finish ticket 6538.
6424 o Code simplification and refactoring:
6425 - Move the generic "config" code into a new file, and have "config.c"
6426 hold only torrc- and state-related code. Resolves ticket 6823.
6427 - Move the core of our "choose a weighted element at random" logic
6428 into its own function, and give it unit tests. Now the logic is
6429 testable, and a little less fragile too.
6430 - Removed the testing_since field of node_t, which hasn't been used
6431 for anything since 0.2.0.9-alpha.
6433 o Documentation fixes:
6434 - Clarify that hidden services are TCP only. Fixes bug 6024.
6435 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6439 Changes in version 0.2.3.22-rc - 2012-09-11
6440 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
6444 - Fix an assertion failure in tor_timegm() that could be triggered
6445 by a badly formatted directory object. Bug found by fuzzing with
6446 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6449 - Avoid segfault when starting up having run with an extremely old
6450 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6454 Changes in version 0.2.2.39 - 2012-09-11
6455 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
6459 - Fix an assertion failure in tor_timegm() that could be triggered
6460 by a badly formatted directory object. Bug found by fuzzing with
6461 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6462 - Do not crash when comparing an address with port value 0 to an
6463 address policy. This bug could have been used to cause a remote
6464 assertion failure by or against directory authorities, or to
6465 allow some applications to crash clients. Fixes bug 6690; bugfix
6469 Changes in version 0.2.4.2-alpha - 2012-09-10
6470 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
6471 raises the default rate limiting even more, and makes the bootstrapping
6472 log messages less noisy.
6475 - Automatically forward the TCP ports of pluggable transport
6476 proxies using tor-fw-helper if PortForwarding is enabled. Implements
6480 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
6481 to 1GB/1GB. The previous defaults were intended to be "basically
6482 infinite", but it turns out they're now limiting our 100mbit+
6483 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
6484 last time we raised it).
6487 - Detect when we're running with a version of OpenSSL other than the
6488 one we compiled with. This has occasionally given people hard-to-
6490 - Log fewer lines at level "notice" about our OpenSSL and Libevent
6491 versions and capabilities when everything is going right. Resolves
6492 part of ticket 6736.
6493 - Directory authorities no long accept descriptors for any version of
6494 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
6495 These versions are insecure, unsupported, or both. Implements
6499 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6500 to start with a triple-underscore so the controller won't touch it.
6501 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6502 - Avoid segfault when starting up having run with an extremely old
6503 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6505 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6506 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6507 - Don't follow the NULL pointer if microdescriptor generation fails.
6508 (This does not appear to be triggerable, but it's best to be safe.)
6509 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
6510 - Fix mis-declared dependencies on src/common/crypto.c and
6511 src/or/tor_main.c that could break out-of-tree builds under some
6512 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
6513 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
6514 6778; bugfix on 0.2.4.1-alpha.
6515 - Fix a harmless (in this case) build warning for implicitly
6516 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
6519 - Now that all versions before 0.2.2.x are disallowed, we no longer
6520 need to work around their missing features. Thus we can remove a
6521 bunch of compatibility code.
6524 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
6525 TCP ports to forward. In the past it only accepted two ports:
6526 the ORPort and the DirPort.
6529 Changes in version 0.2.4.1-alpha - 2012-09-05
6530 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
6531 bridgedb; lets relays use IPv6 addresses and directory authorities
6532 advertise them; and switches to a cleaner build interface.
6534 This is the first alpha release in a new series, so expect there to
6535 be bugs. Users who would rather test out a more stable branch should
6536 stay with 0.2.3.x for now.
6538 o Major features (bridges):
6539 - Bridges now report the pluggable transports they support to the
6540 bridge authority, so it can pass the supported transports on to
6541 bridgedb and/or eventually do reachability testing. Implements
6544 o Major features (IPv6):
6545 - Bridge authorities now accept IPv6 bridge addresses and include
6546 them in network status documents. Implements ticket 5534.
6547 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
6548 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
6549 to happen. Implements ticket 5535.
6550 - All kind of relays, not just bridges, can now advertise an IPv6
6551 OR port. Implements ticket 6362.
6552 - Directory authorities vote on IPv6 OR ports using the new consensus
6553 method 14. Implements ticket 6363.
6555 o Major features (build):
6556 - Switch to a nonrecursive Makefile structure. Now instead of each
6557 Makefile.am invoking other Makefile.am's, there is a master
6558 Makefile.am that includes the others. This change makes our build
6559 process slightly more maintainable, and improves parallelism for
6560 building with make -j. Original patch by Stewart Smith; various
6561 fixes by Jim Meyering.
6562 - Where available, we now use automake's "silent" make rules by
6563 default, so that warnings are easier to spot. You can get the old
6564 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
6566 o Minor features (code security and spec conformance):
6567 - Clear keys and key-derived material left on the stack in
6568 rendservice.c and rendclient.c. Check return value of
6569 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
6570 These fixes should make us more forward-secure against cold-boot
6571 attacks and the like. Fixes bug 2385.
6572 - Reject EXTEND cells sent to nonexistent streams. According to the
6573 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
6574 we were only checking for stream IDs that were currently in use.
6575 Found while hunting for more instances of bug 6271. Bugfix on
6576 0.0.2pre8, which introduced incremental circuit construction.
6578 o Minor features (streamlining);
6579 - No longer include the "opt" prefix when generating routerinfos
6580 or v2 directories: it has been needless since Tor 0.1.2. Closes
6582 - Remove some now-needless code that tried to aggressively flush
6583 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6584 cell queue logic has saved us from the failure mode that this code
6585 was supposed to prevent. Removing this code will limit the number
6586 of baroque control flow paths through Tor's network logic. Reported
6587 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6589 o Minor features (controller):
6590 - Add a "GETINFO signal/names" control port command. Implements
6592 - Provide default values for all options via "GETINFO config/defaults".
6593 Implements ticket 4971.
6595 o Minor features (IPv6):
6596 - New config option "AuthDirHasIPv6Connectivity 1" that directory
6597 authorities should set if they have IPv6 connectivity and want to
6598 do reachability tests for IPv6 relays. Implements feature 5974.
6599 - A relay with an IPv6 OR port now sends that address in NETINFO
6600 cells (in addition to its other address). Implements ticket 6364.
6602 o Minor features (log messages):
6603 - Omit the first heartbeat log message, because it never has anything
6604 useful to say, and it clutters up the bootstrapping messages.
6605 Resolves ticket 6758.
6606 - Don't log about reloading the microdescriptor cache at startup. Our
6607 bootstrap warnings are supposed to tell the user when there's a
6608 problem, and our bootstrap notices say when there isn't. Resolves
6609 ticket 6759; bugfix on 0.2.2.6-alpha.
6610 - Don't log "I learned some more directory information" when we're
6611 reading cached directory information. Reserve it for when new
6612 directory information arrives in response to a fetch. Resolves
6614 - Prevent rounding error in path bias counts when scaling
6615 them down, and use the correct scale factor default. Also demote
6616 some path bias related log messages down a level and make others
6617 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
6618 - We no longer warn so much when generating manpages from their
6621 o Code simplifications and refactoring:
6622 - Enhance our internal sscanf replacement so that we can eliminate
6623 the last remaining uses of the system sscanf. (Though those uses
6624 of sscanf were safe, sscanf itself is generally error prone, so
6625 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6627 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6628 - Move last_reachable and testing_since from routerinfo_t to node_t.
6629 Implements ticket 5529.
6630 - Add replaycache_t structure, functions and unit tests, then refactor
6631 rend_service_introduce() to be more clear to read, improve, debug,
6632 and test. Resolves bug 6177.
6633 - Finally remove support for malloc_good_size and malloc_usable_size.
6634 We had hoped that these functions would let us eke a little more
6635 memory out of our malloc implementation. Unfortunately, the only
6636 implementations that provided these functions are also ones that
6637 are already efficient about not overallocation: they never got us
6638 more than 7 or so bytes per allocation. Removing them saves us a
6639 little code complexity and a nontrivial amount of build complexity.
6642 - Tor maintainers now require Automake version 1.9 or later to build
6643 Tor from the Git repository. (Automake is not required when building
6644 from a source distribution.)
6647 Changes in version 0.2.3.21-rc - 2012-09-05
6648 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
6649 series. It fixes a trio of potential security bugs, fixes a bug where
6650 we were leaving some of the fast relays out of the microdescriptor
6651 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
6652 and cleans up other smaller issues.
6654 o Major bugfixes (security):
6655 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6656 could use this trick to make their circuits receive cells faster
6657 than our flow control would have allowed, or to gum up the network,
6658 or possibly to do targeted memory denial-of-service attacks on
6659 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6660 from July 2002, before the release of Tor 0.0.0. We had committed
6661 this patch previously, but we had to revert it because of bug 6271.
6662 Now that 6271 is fixed, this patch appears to work.
6663 - Reject any attempt to extend to an internal address. Without
6664 this fix, a router could be used to probe addresses on an internal
6665 network to see whether they were accepting connections. Fixes bug
6666 6710; bugfix on 0.0.8pre1.
6667 - Do not crash when comparing an address with port value 0 to an
6668 address policy. This bug could have been used to cause a remote
6669 assertion failure by or against directory authorities, or to
6670 allow some applications to crash clients. Fixes bug 6690; bugfix
6674 - Remove the upper bound on microdescriptor length. We were hitting
6675 the limit for routers with complex exit policies or family
6676 declarations, causing clients to not use them. Fixes the first
6677 piece of bug 6404; fix on 0.2.2.6-alpha.
6678 - Detect "ORPort 0" as meaning, uniformly, that we're not running
6679 as a relay. Previously, some of our code would treat the presence
6680 of any ORPort line as meaning that we should act like a relay,
6681 even though our new listener code would correctly not open any
6682 ORPorts for ORPort 0. Similar bugs in other Port options are also
6683 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
6686 - Avoid a pair of double-free and use-after-mark bugs that can
6687 occur with certain timings in canceled and re-received DNS
6688 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6689 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6690 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6691 - Allow one-hop directory fetching circuits the full "circuit build
6692 timeout" period, rather than just half of it, before failing them
6693 and marking the relay down. This fix should help reduce cases where
6694 clients declare relays (or worse, bridges) unreachable because
6695 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6696 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6698 - Authorities no longer include any router in their microdescriptor
6699 consensuses for which they couldn't generate or agree on a
6700 microdescriptor. Fixes the second piece of bug 6404; fix on
6702 - Detect and reject attempts to specify both "FooPort" and
6703 "FooPort 0" in the same configuration domain. (It's still okay
6704 to have a FooPort in your configuration file, and use "FooPort 0"
6705 on the command line to disable it.) Fixes the second half of bug
6706 6507; bugfix on 0.2.3.3-alpha.
6707 - Make wildcarded addresses (that is, ones beginning with "*.") work
6708 when provided via the controller's MapAddress command. Previously,
6709 they were accepted, but we never actually noticed that they were
6710 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
6711 - Avoid crashing on a malformed state file where EntryGuardPathBias
6712 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
6713 - Add a (probably redundant) memory clear between iterations of
6714 the router status voting loop, to prevent future coding errors
6715 where data might leak between iterations of the loop. Resolves
6718 o Minor bugfixes (log messages):
6719 - Downgrade "set buildtimeout to low value" messages to "info"
6720 severity; they were never an actual problem, there was never
6721 anything reasonable to do about them, and they tended to spam logs
6722 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6723 - Downgrade path-bias warning messages to "info". We'll try to get
6724 them working better in 0.2.4. Add internal circuit construction
6725 state to protect against the noisy warn message "Unexpectedly high
6726 circuit_successes". Also add some additional rate-limited notice
6727 messages to help determine the root cause of the warn. Fixes bug
6728 6475. Bugfix against 0.2.3.17-beta.
6729 - Move log message when unable to find a microdesc in a routerstatus
6730 entry to parse time. Previously we'd spam this warning every time
6731 we tried to figure out which microdescriptors to download. Fixes
6732 the third piece of bug 6404; fix on 0.2.3.18-rc.
6735 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6736 change when the authority is deciding whether to accept a newly
6737 uploaded descriptor. Implements ticket 6423.
6738 - Add missing documentation for consensus and microdesc files.
6739 Resolves ticket 6732.
6742 Changes in version 0.2.2.38 - 2012-08-12
6743 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6744 attack that could in theory leak path information.
6747 - Avoid an uninitialized memory read when reading a vote or consensus
6748 document that has an unrecognized flavor name. This read could
6749 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6750 - Try to leak less information about what relays a client is
6751 choosing to a side-channel attacker. Previously, a Tor client would
6752 stop iterating through the list of available relays as soon as it
6753 had chosen one, thus finishing a little earlier when it picked
6754 a router earlier in the list. If an attacker can recover this
6755 timing information (nontrivial but not proven to be impossible),
6756 they could learn some coarse-grained information about which relays
6757 a client was picking (middle nodes in particular are likelier to
6758 be affected than exits). The timing attack might be mitigated by
6759 other factors (see bug 6537 for some discussion), but it's best
6760 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6763 Changes in version 0.2.3.20-rc - 2012-08-05
6764 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6765 series. It fixes a pair of code security bugs and a potential anonymity
6766 issue, updates our RPM spec files, and cleans up other smaller issues.
6769 - Avoid read-from-freed-memory and double-free bugs that could occur
6770 when a DNS request fails while launching it. Fixes bug 6480;
6771 bugfix on 0.2.0.1-alpha.
6772 - Avoid an uninitialized memory read when reading a vote or consensus
6773 document that has an unrecognized flavor name. This read could
6774 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6775 - Try to leak less information about what relays a client is
6776 choosing to a side-channel attacker. Previously, a Tor client would
6777 stop iterating through the list of available relays as soon as it
6778 had chosen one, thus finishing a little earlier when it picked
6779 a router earlier in the list. If an attacker can recover this
6780 timing information (nontrivial but not proven to be impossible),
6781 they could learn some coarse-grained information about which relays
6782 a client was picking (middle nodes in particular are likelier to
6783 be affected than exits). The timing attack might be mitigated by
6784 other factors (see bug 6537 for some discussion), but it's best
6785 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6788 - Try to make the warning when giving an obsolete SOCKSListenAddress
6789 a little more useful.
6790 - Terminate active server managed proxies if Tor stops being a
6791 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
6792 - Provide a better error message about possible OSX Asciidoc failure
6793 reasons. Fixes bug 6436.
6794 - Warn when Tor is configured to use accounting in a way that can
6795 link a hidden service to some other hidden service or public
6796 address. Resolves ticket 6490.
6799 - Check return value of fputs() when writing authority certificate
6800 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6801 - Ignore ServerTransportPlugin lines when Tor is not configured as
6802 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
6803 - When disabling guards for having too high a proportion of failed
6804 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
6808 - Update our default RPM spec files to work with mock and rpmbuild
6809 on RHEL/Fedora. They have an updated set of dependencies and
6810 conflicts, a fix for an ancient typo when creating the "_tor"
6811 user, and better instructions. Thanks to Ondrej Mikle for the
6812 patch series. Fixes bug 6043.
6815 - Make it possible to set the TestingTorNetwork configuration
6816 option using AlternateDirAuthority and AlternateBridgeAuthority
6817 as an alternative to setting DirServer. Addresses ticket 6377.
6820 - Clarify the documentation for the Alternate*Authority options.
6822 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
6824 o Code simplification and refactoring:
6825 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
6826 10 lines. Also, don't nest them. Doing so in the past has
6827 led to hard-to-debug code. The new style is to use the
6828 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
6831 Changes in version 0.2.3.19-rc - 2012-07-06
6832 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
6833 series. It fixes the compile on Windows, reverts to a GeoIP database
6834 that isn't as broken, and fixes a flow control bug that has been around
6835 since the beginning of Tor.
6838 - Fix a bug handling SENDME cells on nonexistent streams that could
6839 result in bizarre window values. Report and patch contributed
6840 pseudonymously. Fixes part of bug 6271. This bug was introduced
6841 before the first Tor release, in svn commit r152.
6842 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
6843 June 2012 database, Maxmind marked many Tor relays as country "A1",
6844 which will cause risky behavior for clients that set EntryNodes
6845 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
6846 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
6847 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
6850 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
6851 bugfix on 0.2.1.10-alpha.
6854 Changes in version 0.2.3.18-rc - 2012-06-28
6855 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
6856 series. It fixes a few smaller bugs, but generally appears stable.
6857 Please test it and let us know whether it is!
6860 - Allow wildcarded mapaddress targets to be specified on the
6861 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
6862 - Make our linker option detection code more robust against linkers
6863 such as on FreeBSD 8, where a bad combination of options completes
6864 successfully but makes an unrunnable binary. Fixes bug 6173;
6865 bugfix on 0.2.3.17-beta.
6867 o Minor bugfixes (on 0.2.2.x and earlier):
6868 - Avoid a false positive in the util/threads unit test by increasing
6869 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6870 - Replace "Sending publish request" log messages with "Launching
6871 upload", so that they no longer confusingly imply that we're
6872 sending something to a directory we might not even be connected
6873 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6874 - Make sure to set *socket_error in all error cases in
6875 connection_connect(), so it can't produce a warning about
6876 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6877 0.2.1.1-alpha; resolves ticket 6028.
6878 - Downgrade "Got a certificate, but we already have it" log messages
6879 from warning to info, except when we're a dirauth. Fixes bug 5238;
6880 bugfix on 0.2.1.7-alpha.
6881 - When checking for requested signatures on the latest consensus
6882 before serving it to a client, make sure to check the right
6883 consensus flavor. Bugfix on 0.2.2.6-alpha.
6884 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6885 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6887 o Minor bugfixes (on 0.2.3.x):
6888 - Make format_helper_exit_status() avoid unnecessary space padding
6889 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
6891 - Downgrade a message about cleaning the microdescriptor cache to
6892 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
6893 - Log a BUG message at severity INFO if we have a networkstatus with
6894 a missing entry for some microdescriptor. Continues on a patch
6896 - Improve the log message when a managed proxy fails to launch. Fixes
6897 bug 5099; bugfix on 0.2.3.6-alpha.
6898 - Don't do DNS lookups when parsing corrupted managed proxy protocol
6899 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
6900 - When formatting wildcarded address mappings for the controller,
6901 be sure to include "*." as appropriate. Partially fixes bug 6244;
6902 bugfix on 0.2.3.9-alpha.
6903 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
6904 Bugfix on 0.2.3.13-alpha.
6905 - Stop logging messages about running with circuit timeout learning
6906 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
6907 - Disable a spurious warning about reading on a marked and flushing
6908 connection. We shouldn't be doing that, but apparently we
6909 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
6910 - Fix a bug that stopped AllowDotExit from working on addresses
6911 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
6914 o Code simplification, refactoring, unit tests:
6915 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6916 Libevent's notion of cached time when possible.
6917 - Remove duplicate code for invoking getrlimit() from control.c.
6918 - Add a unit test for the environment_variable_names_equal function.
6921 - Document the --defaults-torrc option, and the new (in 0.2.3)
6922 semantics for overriding, extending, and clearing lists of
6923 options. Closes bug 4748.
6926 Changes in version 0.2.3.17-beta - 2012-06-15
6927 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
6928 gets our TLS handshake back on track for being able to blend in with
6929 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
6930 with Vidalia, and otherwise continues to get us closer to a release
6934 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6935 - Update TLS cipher list to match Firefox 8 and later. Resolves
6937 - Implement the client side of proposal 198: remove support for
6938 clients falsely claiming to support standard ciphersuites that
6939 they can actually provide. As of modern OpenSSL versions, it's not
6940 necessary to fake any standard ciphersuite, and doing so prevents
6941 us from using better ciphersuites in the future, since servers
6942 can't know whether an advertised ciphersuite is really supported or
6943 not. Some hosts -- notably, ones with very old versions of OpenSSL
6944 or where OpenSSL has been built with ECC disabled -- will stand
6945 out because of this change; TBB users should not be affected.
6948 - Change the default value for DynamicDHGroups (introduced in
6949 0.2.3.9-alpha) to 0. This feature can make Tor relays less
6950 identifiable by their use of the mod_ssl DH group, but at
6951 the cost of some usability (#4721) and bridge tracing (#6087)
6952 regressions. Resolves ticket 5598.
6953 - Send a CRLF at the end of each STATUS_* control protocol event. This
6954 bug tickled a bug in Vidalia which would make it freeze. Fixes
6955 bug 6094; bugfix on 0.2.3.16-alpha.
6958 - Disable writing on marked-for-close connections when they are
6959 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6960 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6961 case for flushing marked connections.
6962 - Detect SSL handshake even when the initial attempt to write the
6963 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6964 - Change the AllowDotExit rules so they should actually work.
6965 We now enforce AllowDotExit only immediately after receiving an
6966 address via SOCKS or DNSPort: other sources are free to provide
6967 .exit addresses after the resolution occurs. Fixes bug 3940;
6968 bugfix on 0.2.2.1-alpha.
6969 - Fix a (harmless) integer overflow in cell statistics reported by
6970 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6971 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
6972 right places and never depends on the consensus parameters or
6973 computes adaptive timeouts when it is disabled. Fixes bug 5049;
6974 bugfix on 0.2.2.14-alpha.
6975 - When building Tor on Windows with -DUNICODE (not default), ensure
6976 that error messages, filenames, and DNS server names are always
6977 NUL-terminated when we convert them to a single-byte encoding.
6978 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6979 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6980 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6981 - Fix an edge case where TestingTorNetwork is set but the authorities
6982 and relays all have an uptime of zero, where the private Tor network
6983 could briefly lack support for hidden services. Fixes bug 3886;
6984 bugfix on 0.2.2.18-alpha.
6985 - Correct the manpage's descriptions for the default values of
6986 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
6988 - Fix the documentation for the --hush and --quiet command line
6989 options, which changed their behavior back in 0.2.3.3-alpha.
6990 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
6994 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6995 more information to it, so that we can track it down in case it
6996 returns again. Mitigates bug 5235.
6997 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6998 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6999 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7000 - Warn the user when HTTPProxy, but no other proxy type, is
7001 configured. This can cause surprising behavior: it doesn't send
7002 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
7003 directory traffic only. Resolves ticket 4663.
7004 - Issue a notice if a guard completes less than 40% of your circuits.
7005 Threshold is configurable by torrc option PathBiasNoticeRate and
7006 consensus parameter pb_noticepct. There is additional, off-by-
7007 default code to disable guards which fail too many circuits.
7008 Addresses ticket 5458.
7009 - Update to the June 6 2012 Maxmind GeoLite Country database.
7011 o Code simplifications and refactoring:
7012 - Remove validate_pluggable_transports_config(): its warning
7013 message is now handled by connection_or_connect().
7016 Changes in version 0.2.2.37 - 2012-06-06
7017 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7018 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7022 - Work around a bug in OpenSSL that broke renegotiation with TLS
7023 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7024 the v2 Tor connection protocol when both sides were using OpenSSL
7025 1.0.1 would fail. Resolves ticket 6033.
7026 - When waiting for a client to renegotiate, don't allow it to add
7027 any bytes to the input buffer. This fixes a potential DoS issue.
7028 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7029 - Fix an edge case where if we fetch or publish a hidden service
7030 descriptor, we might build a 4-hop circuit and then use that circuit
7031 for exiting afterwards -- even if the new last hop doesn't obey our
7032 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7035 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7036 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7039 - Tell GCC and Clang to check for any errors in format strings passed
7040 to the tor_v*(print|scan)f functions.
7043 Changes in version 0.2.3.16-alpha - 2012-06-05
7044 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
7045 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7046 currently). It also fixes a variety of smaller bugs and other cleanups
7047 that get us closer to a release candidate.
7049 o Major bugfixes (general):
7050 - Work around a bug in OpenSSL that broke renegotiation with TLS
7051 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7052 the v2 Tor connection protocol when both sides were using OpenSSL
7053 1.0.1 would fail. Resolves ticket 6033.
7054 - When waiting for a client to renegotiate, don't allow it to add
7055 any bytes to the input buffer. This fixes a potential DoS issue.
7056 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7057 - Pass correct OR address to managed proxies (like obfsproxy),
7058 even when ORListenAddress is used. Fixes bug 4865; bugfix on
7060 - The advertised platform of a router now includes only its operating
7061 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
7062 service pack level (for Windows) or its CPU architecture (for Unix).
7063 We also no longer include the "git-XYZ" tag in the version. Resolves
7066 o Major bugfixes (clients):
7067 - If we are unable to find any exit that supports our predicted ports,
7068 stop calling them predicted, so that we don't loop and build
7069 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
7070 which introduced predicted ports.
7071 - Fix an edge case where if we fetch or publish a hidden service
7072 descriptor, we might build a 4-hop circuit and then use that circuit
7073 for exiting afterwards -- even if the new last hop doesn't obey our
7074 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7075 - Check at each new consensus whether our entry guards were picked
7076 long enough ago that we should rotate them. Previously, we only
7077 did this check at startup, which could lead to us holding a guard
7078 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
7079 - When fetching a bridge descriptor from a bridge authority,
7080 always do so anonymously, whether we have been able to open
7081 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
7082 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
7083 but we'll need to wait for bug 6010 before it's actually usable.
7085 o Major bugfixes (directory authorities):
7086 - When computing weight parameters, behave more robustly in the
7087 presence of a bad bwweightscale value. Previously, the authorities
7088 would crash if they agreed on a sufficiently broken weight_scale
7089 value: now, they use a reasonable default and carry on. Partial
7090 fix for 5786; bugfix on 0.2.2.17-alpha.
7091 - Check more thoroughly to prevent a rogue authority from
7092 double-voting on any consensus directory parameter. Previously,
7093 authorities would crash in this case if the total number of
7094 votes for any parameter exceeded the number of active voters,
7095 but would let it pass otherwise. Partial fix for bug 5786; bugfix
7099 - Rate-limit log messages when asked to connect anonymously to
7100 a private address. When these hit, they tended to hit fast and
7101 often. Also, don't bother trying to connect to addresses that we
7102 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7103 reply makes us think we have been lied to, even when the address the
7104 client tried to connect to was "localhost." Resolves ticket 2822.
7105 - Allow packagers to insert an extra string in server descriptor
7106 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
7107 Resolves the rest of ticket 2988.
7108 - Raise the threshold of server descriptors needed (75%) and exit
7109 server descriptors needed (50%) before we will declare ourselves
7110 bootstrapped. This will make clients start building circuits a
7111 little later, but makes the initially constructed circuits less
7112 skewed and less in conflict with further directory fetches. Fixes
7114 - Close any connection that sends unrecognized junk before the
7115 handshake. Solves an issue noted in bug 4369.
7116 - Improve log messages about managed transports. Resolves ticket 5070.
7117 - Tag a bridge's descriptor as "never to be sent unencrypted".
7118 This shouldn't matter, since bridges don't open non-anonymous
7119 connections to the bridge authority and don't allow unencrypted
7120 directory connections from clients, but we might as well make
7121 sure. Closes bug 5139.
7122 - Expose our view of whether we have gone dormant to the controller,
7123 via a new "GETINFO dormant" value. Torbutton and other controllers
7124 can use this to avoid doing periodic requests through Tor while
7125 it's dormant (bug 4718). Fixes bug 5954.
7126 - Tell GCC and Clang to check for any errors in format strings passed
7127 to the tor_v*(print|scan)f functions.
7128 - Update to the May 1 2012 Maxmind GeoLite Country database.
7130 o Minor bugfixes (already included in 0.2.2.36):
7131 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7132 Fixes bug 5346; bugfix on 0.0.8pre3.
7133 - Correct parsing of certain date types in parse_http_time().
7134 Without this patch, If-Modified-Since would behave
7135 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7136 Esteban Manchado Velázques.
7137 - Make our number-parsing functions always treat too-large values
7138 as an error, even when those values exceed the width of the
7139 underlying type. Previously, if the caller provided these
7140 functions with minima or maxima set to the extreme values of the
7141 underlying integer type, these functions would return those
7142 values on overflow rather than treating overflow as an error.
7143 Fixes part of bug 5786; bugfix on 0.0.9.
7144 - If we hit the error case where routerlist_insert() replaces an
7145 existing (old) server descriptor, make sure to remove that
7146 server descriptor from the old_routers list. Fix related to bug
7147 1776. Bugfix on 0.2.2.18-alpha.
7148 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7149 circuits. Fixes issue 5259.
7151 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
7152 - Prevent a null-pointer dereference when receiving a data cell
7153 for a nonexistent stream when the circuit in question has an
7154 empty deliver window. We don't believe this is triggerable,
7155 since we don't currently allow deliver windows to become empty,
7156 but the logic is tricky enough that it's better to make the code
7157 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
7158 - Fix a memory leak when trying to launch a DNS request when the
7159 network is disabled or the nameservers are unconfigurable. Fixes
7160 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
7161 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
7162 - Don't hold a Windows file handle open for every file mapping;
7163 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7165 - Avoid O(n^2) performance characteristics when parsing a large
7166 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
7167 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7168 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7170 - Make our replacement implementation of strtok_r() compatible with
7171 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
7172 bugfix on 0.2.2.1-alpha.
7173 - Fix a NULL-pointer dereference on a badly formed
7174 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
7175 bugfix on 0.2.2.9-alpha.
7176 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7177 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7178 - Defensively refactor rend_mid_rendezvous() so that protocol
7179 violations and length checks happen in the beginning. Fixes
7181 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7182 that IPv6 stuff will compile on MSVC, and compilation issues
7183 will be easier to track down. Fixes bug 5861.
7185 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
7186 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7187 resource exhaustion, so that clients can adjust their load to
7188 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7189 started using END_STREAM_REASON_RESOURCELIMIT.
7190 - Don't check for whether the address we're using for outbound
7191 connections has changed until after the outbound connection has
7192 completed. On Windows, getsockname() doesn't succeed until the
7193 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7194 - If the configuration tries to set MyFamily on a bridge, refuse to
7195 do so, and warn about the security implications. Fixes bug 4657;
7196 bugfix on 0.2.0.3-alpha.
7197 - If the client fails to set a reasonable set of ciphersuites
7198 during its v2 handshake renegotiation, allow the renegotiation to
7199 continue nevertheless (i.e. send all the required certificates).
7200 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7201 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7202 option is set to 0 (which Vidalia version 0.2.16 now does when
7203 a SAVECONF attempt fails), perform other actions that SIGHUP
7204 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7206 - If we fail to write a microdescriptor to the disk cache, do not
7207 continue replacing the old microdescriptor file. Fixes bug 2954;
7208 bugfix on 0.2.2.6-alpha.
7209 - Exit nodes don't need to fetch certificates for authorities that
7210 they don't recognize; only directory authorities, bridges,
7211 and caches need to do that. Fixes part of bug 2297; bugfix on
7213 - Correctly handle checking the permissions on the parent
7214 directory of a control socket in the root directory. Bug found
7215 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7217 - When told to add a bridge with the same digest as a preexisting
7218 bridge but a different addr:port, change the addr:port as
7219 requested. Previously we would not notice the change. Fixes half
7220 of bug 5603; fix on 0.2.2.26-beta.
7221 - End AUTHCHALLENGE error messages (in the control protocol) with
7222 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
7224 o Minor bugfixes (on 0.2.3.x):
7225 - Turn an assertion (that the number of handshakes received as a
7226 server is not < 1) into a warning. Fixes bug 4873; bugfix on
7228 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
7229 we had reversed them when the answer was cached.) Fixes bug
7230 5723; bugfix on 0.2.3.1-alpha.
7231 - Work correctly on Linux systems with accept4 support advertised in
7232 their headers, but without accept4 support in the kernel. Fix
7233 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
7234 - When told to add a bridge with the same addr:port as a preexisting
7235 bridge but a different transport, change the transport as
7236 requested. Previously we would not notice the change. Fixes half
7237 of bug 5603; fix on 0.2.3.2-alpha.
7238 - Avoid a "double-reply" warning when replying to a SOCKS request
7239 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
7240 bugfix on 0.2.3.4-alpha.
7241 - Fix a bug where a bridge authority crashes if it has seen no
7242 directory requests when it's time to write statistics to disk.
7243 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
7245 - Don't try to open non-control listeners when DisableNetwork is set.
7246 Previously, we'd open all listeners, then immediately close them.
7247 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
7248 - Don't abort the managed proxy protocol if the managed proxy
7249 sends us an unrecognized line; ignore it instead. Fixes bug
7250 5910; bugfix on 0.2.3.9-alpha.
7251 - Fix a compile warning in crypto.c when compiling with clang 3.1.
7252 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
7253 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
7254 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
7255 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
7256 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
7257 - Resolve numerous small warnings and build issues with MSVC. Resolves
7260 o Documentation fixes:
7261 - Improve the manual's documentation for the NT Service command-line
7262 options. Addresses ticket 3964.
7263 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7264 - Document the changes to the ORPort and DirPort options, and the
7265 fact that {OR/Dir}ListenAddress is now unnecessary (and
7266 therefore deprecated). Resolves ticket 5597.
7269 - Remove the torrc.bridge file: we don't use it for anything, and
7270 it had become badly desynchronized from torrc.sample. Resolves
7274 Changes in version 0.2.2.36 - 2012-05-24
7275 Tor 0.2.2.36 updates the addresses for two of the eight directory
7276 authorities, fixes some potential anonymity and security issues,
7277 and fixes several crash bugs.
7279 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7280 known flaws, and nobody should be using them. You should upgrade. If
7281 you're using a Linux or BSD and its packages are obsolete, stop using
7282 those packages and upgrade anyway.
7284 o Directory authority changes:
7285 - Change IP address for maatuska (v3 directory authority).
7286 - Change IP address for ides (v3 directory authority), and rename
7290 - When building or running with any version of OpenSSL earlier
7291 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7292 versions have a bug (CVE-2011-4576) in which their block cipher
7293 padding includes uninitialized data, potentially leaking sensitive
7294 information to any peer with whom they make a SSLv3 connection. Tor
7295 does not use SSL v3 by default, but a hostile client or server
7296 could force an SSLv3 connection in order to gain information that
7297 they shouldn't have been able to get. The best solution here is to
7298 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7299 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7300 to make sure that the bug can't happen.
7301 - Never use a bridge or a controller-supplied node as an exit, even
7302 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7303 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7304 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7305 - Only build circuits if we have a sufficient threshold of the total
7306 descriptors that are marked in the consensus with the "Exit"
7307 flag. This mitigates an attack proposed by wanoskarnet, in which
7308 all of a client's bridges collude to restrict the exit nodes that
7309 the client knows about. Fixes bug 5343.
7310 - Provide controllers with a safer way to implement the cookie
7311 authentication mechanism. With the old method, if another locally
7312 running program could convince a controller that it was the Tor
7313 process, then that program could trick the controller into telling
7314 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7315 authentication method uses a challenge-response approach to prevent
7316 this attack. Fixes bug 5185; implements proposal 193.
7319 - Avoid logging uninitialized data when unable to decode a hidden
7320 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7321 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7322 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7324 - Fix builds when the path to sed, openssl, or sha1sum contains
7325 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7327 - Correct our replacements for the timeradd() and timersub() functions
7328 on platforms that lack them (for example, Windows). The timersub()
7329 function is used when expiring circuits, while timeradd() is
7330 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7331 bugfix on 0.2.2.24-alpha.
7332 - Fix the SOCKET_OK test that we use to tell when socket
7333 creation fails so that it works on Win64. Fixes part of bug 4533;
7334 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7337 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7338 Fixes bug 5346; bugfix on 0.0.8pre3.
7339 - Make our number-parsing functions always treat too-large values
7340 as an error, even when those values exceed the width of the
7341 underlying type. Previously, if the caller provided these
7342 functions with minima or maxima set to the extreme values of the
7343 underlying integer type, these functions would return those
7344 values on overflow rather than treating overflow as an error.
7345 Fixes part of bug 5786; bugfix on 0.0.9.
7346 - Older Linux kernels erroneously respond to strange nmap behavior
7347 by having accept() return successfully with a zero-length
7348 socket. When this happens, just close the connection. Previously,
7349 we would try harder to learn the remote address: but there was
7350 no such remote address to learn, and our method for trying to
7351 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7352 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7353 - Correct parsing of certain date types in parse_http_time().
7354 Without this patch, If-Modified-Since would behave
7355 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7356 Esteban Manchado Velázques.
7357 - Change the BridgePassword feature (part of the "bridge community"
7358 design, which is not yet implemented) to use a time-independent
7359 comparison. The old behavior might have allowed an adversary
7360 to use timing to guess the BridgePassword value. Fixes bug 5543;
7361 bugfix on 0.2.0.14-alpha.
7362 - Detect and reject certain misformed escape sequences in
7363 configuration values. Previously, these values would cause us
7364 to crash if received in a torrc file or over an authenticated
7365 control port. Bug found by Esteban Manchado Velázquez, and
7366 independently by Robert Connolly from Matta Consulting who further
7367 noted that it allows a post-authentication heap overflow. Patch
7368 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7369 bugfix on 0.2.0.16-alpha.
7370 - Fix a compile warning when using the --enable-openbsd-malloc
7371 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7372 - During configure, detect when we're building with clang version
7373 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7374 CFLAGS. clang doesn't support them yet.
7375 - When sending an HTTP/1.1 proxy request, include a Host header.
7376 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7377 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7378 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7379 - If we hit the error case where routerlist_insert() replaces an
7380 existing (old) server descriptor, make sure to remove that
7381 server descriptor from the old_routers list. Fix related to bug
7382 1776. Bugfix on 0.2.2.18-alpha.
7384 o Minor bugfixes (documentation and log messages):
7385 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7386 Fixes bug 4856; bugfix on Tor 0.0.6.
7387 - Update "ClientOnly" man page entry to explain that there isn't
7388 really any point to messing with it. Resolves ticket 5005.
7389 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7390 directory authority option (introduced in Tor 0.2.2.34).
7391 - Downgrade the "We're missing a certificate" message from notice
7392 to info: people kept mistaking it for a real problem, whereas it
7393 is seldom the problem even when we are failing to bootstrap. Fixes
7394 bug 5067; bugfix on 0.2.0.10-alpha.
7395 - Correctly spell "connect" in a log message on failure to create a
7396 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7397 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7398 circuits. Fixes issue 5259.
7401 - Directory authorities now reject versions of Tor older than
7402 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7403 inclusive. These versions accounted for only a small fraction of
7404 the Tor network, and have numerous known security issues. Resolves
7406 - Update to the May 1 2012 Maxmind GeoLite Country database.
7409 - When sending or relaying a RELAY_EARLY cell, we used to convert
7410 it to a RELAY cell if the connection was using the v1 link
7411 protocol. This was a workaround for older versions of Tor, which
7412 didn't handle RELAY_EARLY cells properly. Now that all supported
7413 versions can handle RELAY_EARLY cells, and now that we're enforcing
7414 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7415 remove this workaround. Addresses bug 4786.
7418 Changes in version 0.2.3.15-alpha - 2012-04-30
7419 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
7420 the development branch build on Windows again.
7422 o Minor bugfixes (on 0.2.2.x and earlier):
7423 - Make sure that there are no unhandled pending TLS errors before
7424 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7425 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7426 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7427 - Fix an assert that directory authorities could trigger on sighup
7428 during some configuration state transitions. We now don't treat
7429 it as a fatal error when the new descriptor we just generated in
7430 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
7431 - After we pick a directory mirror, we would refuse to use it if
7432 it's in our ExcludeExitNodes list, resulting in mysterious failures
7433 to bootstrap for people who just wanted to avoid exiting from
7434 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7435 - When building with --enable-static-tor on OpenBSD, do not
7436 erroneously attempt to link -lrt. Fixes bug 5103.
7438 o Minor bugfixes (on 0.2.3.x):
7439 - When Tor is built with kernel headers from a recent (last few
7440 years) Linux kernel, do not fail to run on older (pre-2.6.28
7441 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
7442 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
7444 - Fix compilation with miniupnpc version 1.6; patch from
7445 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
7446 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
7447 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
7448 - Fix compilation on platforms without unistd.h, or where environ
7449 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
7452 - Directory authorities are now a little more lenient at accepting
7453 older router descriptors, or newer router descriptors that don't
7454 make big changes. This should help ameliorate past and future
7455 issues where routers think they have uploaded valid descriptors,
7456 but the authorities don't think so. Fix for ticket 2479.
7457 - Make the code that clients use to detect an address change be
7458 IPv6-aware, so that it won't fill clients' logs with error
7459 messages when trying to get the IPv4 address of an IPv6
7460 connection. Implements ticket 5537.
7463 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
7464 authorities needed to use it for a while to keep the network working
7465 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
7466 that was six months ago. As of now, it should no longer be needed
7470 Changes in version 0.2.3.14-alpha - 2012-04-23
7471 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
7472 candidate. It also dramatically speeds up AES: fast relays should
7473 consider switching to the newer OpenSSL library.
7475 o Directory authority changes:
7476 - Change IP address for ides (v3 directory authority), and rename
7480 - Avoid logging uninitialized data when unable to decode a hidden
7481 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7482 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7483 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7485 - If authorities are unable to get a v2 consensus document from other
7486 directory authorities, they no longer fall back to fetching
7487 them from regular directory caches. Fixes bug 5635; bugfix on
7488 0.2.2.26-beta, where routers stopped downloading v2 consensus
7490 - When we start a Tor client with a normal consensus already cached,
7491 be willing to download a microdescriptor consensus. Fixes bug 4011;
7492 fix on 0.2.3.1-alpha.
7494 o Major features (performance):
7495 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
7496 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
7497 vectorized AES implementations as appropriate. These can be much,
7498 much faster than other AES implementations.
7500 o Minor bugfixes (0.2.2.x and earlier):
7501 - Don't launch more than 10 service-side introduction-point circuits
7502 for a hidden service in five minutes. Previously, we would consider
7503 launching more introduction-point circuits if at least one second
7504 had passed without any introduction-point circuits failing. Fixes
7505 bug 4607; bugfix on 0.0.7pre1.
7506 - Change the BridgePassword feature (part of the "bridge community"
7507 design, which is not yet implemented) to use a time-independent
7508 comparison. The old behavior might have allowed an adversary
7509 to use timing to guess the BridgePassword value. Fixes bug 5543;
7510 bugfix on 0.2.0.14-alpha.
7511 - Enforce correct return behavior of tor_vsscanf() when the '%%'
7512 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
7513 - When sending an HTTP/1.1 proxy request, include a Host header.
7514 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7515 - Don't log that we have "decided to publish new relay descriptor"
7516 unless we are actually publishing a descriptor. Fixes bug 3942;
7517 bugfix on 0.2.2.28-beta.
7519 o Minor bugfixes (0.2.3.x):
7520 - Fix a bug where a bridge authority crashes (on a failed assert)
7521 if it has seen no directory requests when it's time to write
7522 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
7523 - Fix bug stomping on ORPort option NoListen and ignoring option
7524 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
7525 - In the testsuite, provide a large enough buffer in the tor_sscanf
7526 unit test. Otherwise we'd overrun that buffer and crash during
7527 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
7529 - Make sure we create the keys directory if it doesn't exist and we're
7530 about to store the dynamic Diffie-Hellman parameters. Fixes bug
7531 5572; bugfix on 0.2.3.13-alpha.
7532 - Fix a small memory leak when trying to decode incorrect base16
7533 authenticator during SAFECOOKIE authentication. Found by
7534 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
7537 - Add more information to a log statement that might help track down
7538 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
7539 non-IP address" messages (or any Bug messages, for that matter!),
7540 please let us know about it.
7541 - Relays now understand an IPv6 address when they get one from a
7542 directory server. Resolves ticket 4875.
7543 - Resolve IPv6 addresses in bridge and entry statistics to country
7544 code "??" which means we at least count them. Resolves ticket 5053;
7545 improves on 0.2.3.9-alpha.
7546 - Update to the April 3 2012 Maxmind GeoLite Country database.
7547 - Begin a doc/state-contents.txt file to explain the contents of
7548 the Tor state file. Fixes bug 2987.
7550 o Default torrc changes:
7551 - Stop listing "socksport 9050" in torrc.sample. We open a socks
7552 port on 9050 by default anyway, so this should not change anything
7554 - Stop mentioning the deprecated *ListenAddress options in
7555 torrc.sample. Fixes bug 5438.
7556 - Document unit of bandwidth related options in sample torrc.
7560 - The "torify" script no longer supports the "tsocks" socksifier
7561 tool, since tsocks doesn't support DNS and UDP right for Tor.
7562 Everyone should be using torsocks instead. Fixes bugs 3530 and
7563 5180. Based on a patch by "ugh".
7566 - Change the symmetric cipher interface so that creating and
7567 initializing a stream cipher are no longer separate functions.
7568 - Remove all internal support for unpadded RSA. We never used it, and
7569 it would be a bad idea to start.
7572 Changes in version 0.2.3.13-alpha - 2012-03-26
7573 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
7574 in managed pluggable transports, as well as providing other cleanups
7575 that get us closer to a release candidate.
7577 o Directory authority changes:
7578 - Change IP address for maatuska (v3 directory authority).
7581 - Provide controllers with a safer way to implement the cookie
7582 authentication mechanism. With the old method, if another locally
7583 running program could convince a controller that it was the Tor
7584 process, then that program could trick the controller into telling
7585 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7586 authentication method uses a challenge-response approach to prevent
7587 this attack. Fixes bug 5185, implements proposal 193.
7588 - Never use a bridge or a controller-supplied node as an exit, even
7589 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7590 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7591 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7592 - Only build circuits if we have a sufficient threshold of the total
7593 descriptors that are marked in the consensus with the "Exit"
7594 flag. This mitigates an attack proposed by wanoskarnet, in which
7595 all of a client's bridges collude to restrict the exit nodes that
7596 the client knows about. Fixes bug 5343.
7598 o Major bugfixes (on Tor 0.2.3.x):
7599 - Avoid an assert when managed proxies like obfsproxy are configured,
7600 and we receive HUP signals or setconf attempts too rapidly. This
7601 situation happens most commonly when Vidalia tries to attach to
7602 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
7603 bugfix on 0.2.3.6-alpha.
7604 - Fix a relay-side pluggable transports bug where managed proxies were
7605 unreachable from the Internet, because Tor asked them to bind on
7606 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
7607 - Stop discarding command-line arguments when TestingTorNetwork
7608 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
7609 0.2.3.9-alpha, where task 4552 added support for two layers of
7611 - Resume allowing the unit tests to run in gdb. This was accidentally
7612 made impossible when the DisableDebuggerAttachment option was
7613 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
7614 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
7615 0.2.3.11-alpha. Reported by Anthony G. Basile.
7617 o Minor bugfixes (on 0.2.2.x and earlier):
7618 - Ensure we don't cannibalize circuits that are longer than three hops
7619 already, so we don't end up making circuits with 5 or more
7620 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
7621 0.1.0.1-rc which introduced cannibalization.
7622 - Detect and reject certain misformed escape sequences in
7623 configuration values. Previously, these values would cause us
7624 to crash if received in a torrc file or over an authenticated
7625 control port. Bug found by Esteban Manchado Velázquez, and
7626 independently by Robert Connolly from Matta Consulting who further
7627 noted that it allows a post-authentication heap overflow. Patch
7628 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7629 bugfix on 0.2.0.16-alpha.
7630 - Fix a compile warning when using the --enable-openbsd-malloc
7631 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7632 - Directory caches no longer refuse to clean out descriptors because
7633 of missing v2 networkstatus documents, unless they're configured
7634 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
7635 0.2.2.26-beta. Patch by Daniel Bryg.
7636 - Update to the latest version of the tinytest unit testing framework.
7637 This includes a couple of bugfixes that can be relevant for
7638 running forked unit tests on Windows, and removes all reserved
7641 o Minor bugfixes (on 0.2.3.x):
7642 - On a failed pipe() call, don't leak file descriptors. Fixes bug
7643 4296; bugfix on 0.2.3.1-alpha.
7644 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
7645 until after we have received a CERTS cell. Fixes bug 4361; bugfix
7646 on 0.2.3.6-alpha. Patch by "frosty".
7647 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
7648 option, so that the IP stack doesn't decide to use it for IPv4
7649 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
7650 - Ensure that variables set in Tor's environment cannot override
7651 environment variables that Tor passes to a managed
7652 pluggable-transport proxy. Previously, Tor would pass every
7653 variable in its environment to managed proxies along with the new
7654 ones, in such a way that on many operating systems, the inherited
7655 environment variables would override those which Tor tried to
7656 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
7657 bugfix on 0.2.3.9-alpha for Windows.
7660 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7661 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
7662 - Update to the March 6 2012 Maxmind GeoLite Country database.
7665 Changes in version 0.2.3.12-alpha - 2012-02-13
7666 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
7667 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
7668 when Tor is configured to use a pluggable transport like obfsproxy.
7671 - Fix builds when the path to sed, openssl, or sha1sum contains
7672 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7674 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
7675 connections. This change should allow busy exit relays to stop
7676 running out of available sockets as quickly. Fixes bug 4950;
7677 bugfix on 0.2.2.26-beta.
7678 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
7679 would ask the bridge for microdescriptors, which are only supported
7680 in 0.2.3.x, and then fail to bootstrap when it didn't get the
7681 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
7682 - Properly set up obfsproxy's environment when in managed mode. The
7683 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
7684 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
7685 5076 and 5082; bugfix on 0.2.3.6-alpha.
7688 - Use the dead_strip option when building Tor on OS X. This reduces
7689 binary size by almost 19% when linking openssl and libevent
7690 statically, which we do for Tor Browser Bundle.
7691 - Fix broken URLs in the sample torrc file, and tell readers about
7692 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7693 PublishServerDescriptor options. Addresses bug 4652.
7694 - Update to the February 7 2012 Maxmind GeoLite Country database.
7697 - Downgrade the "We're missing a certificate" message from notice
7698 to info: people kept mistaking it for a real problem, whereas it
7699 is seldom the problem even when we are failing to bootstrap. Fixes
7700 bug 5067; bugfix on 0.2.0.10-alpha.
7701 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
7702 managed pluggable transport server proxy's environment.
7703 Previously, we would put it there, even though Tor doesn't
7704 implement an 'extended server port' yet, and even though Tor
7705 almost certainly isn't listening at that address. For now, we set
7706 it to an empty string to avoid crashing older obfsproxies. Bugfix
7708 - Log the heartbeat message every HeartbeatPeriod seconds, not every
7709 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
7710 0.2.3.1-alpha. Bug reported by Scott Bennett.
7711 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
7712 bugfix on 0.2.3.11-alpha.
7713 - Update "ClientOnly" man page entry to explain that there isn't
7714 really any point to messing with it. Resolves ticket 5005.
7715 - Use the correct CVE number for CVE-2011-4576 in our comments and
7716 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
7719 o Code simplifications and refactoring:
7720 - Use the _WIN32 macro throughout our code to detect Windows.
7721 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7725 Changes in version 0.2.3.11-alpha - 2012-01-22
7726 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7727 the last step of the plan to limit maximum circuit length, includes
7728 a wide variety of hidden service performance and correctness fixes,
7729 works around an OpenSSL security flaw if your distro is too stubborn
7730 to upgrade, and fixes a bunch of smaller issues.
7733 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7734 part of "Proposal 110: Avoiding infinite length circuits" by
7735 refusing all circuit-extend requests that do not use a relay_early
7736 cell. This change helps Tor resist a class of denial-of-service
7737 attacks by limiting the maximum circuit length.
7738 - Adjust the number of introduction points that a hidden service
7739 will try to maintain based on how long its introduction points
7740 remain in use and how many introductions they handle. Fixes
7742 - Try to use system facilities for enumerating local interface
7743 addresses, before falling back to our old approach (which was
7744 binding a UDP socket, and calling getsockname() on it). That
7745 approach was scaring OS X users whose draconian firewall
7746 software warned about binding to UDP sockets, regardless of
7747 whether packets were sent. Now we try to use getifaddrs(),
7748 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7749 system supports. Resolves ticket 1827.
7751 o Major security workaround:
7752 - When building or running with any version of OpenSSL earlier
7753 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7754 versions have a bug (CVE-2011-4576) in which their block cipher
7755 padding includes uninitialized data, potentially leaking sensitive
7756 information to any peer with whom they make a SSLv3 connection. Tor
7757 does not use SSL v3 by default, but a hostile client or server
7758 could force an SSLv3 connection in order to gain information that
7759 they shouldn't have been able to get. The best solution here is to
7760 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7761 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7762 to make sure that the bug can't happen.
7765 - Fix the SOCKET_OK test that we use to tell when socket
7766 creation fails so that it works on Win64. Fixes part of bug 4533;
7767 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7768 - Correct our replacements for the timeradd() and timersub() functions
7769 on platforms that lack them (for example, Windows). The timersub()
7770 function is used when expiring circuits, while timeradd() is
7771 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7772 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
7773 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
7774 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
7775 bug at runtime, not compile time, because some distributions hack
7776 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
7777 on 0.2.3.9-alpha. Found by Pascal.
7779 o Minor features (controller):
7780 - Use absolute path names when reporting the torrc filename in the
7781 control protocol, so a controller can more easily find the torrc
7782 file. Resolves bug 1101.
7783 - Extend the control protocol to report flags that control a circuit's
7784 path selection in CIRC events and in replies to 'GETINFO
7785 circuit-status'. Implements part of ticket 2411.
7786 - Extend the control protocol to report the hidden service address
7787 and current state of a hidden-service-related circuit in CIRC
7788 events and in replies to 'GETINFO circuit-status'. Implements part
7790 - When reporting the path to the cookie file to the controller,
7791 give an absolute path. Resolves ticket 4881.
7792 - Allow controllers to request an event notification whenever a
7793 circuit is cannibalized or its purpose is changed. Implements
7794 part of ticket 3457.
7795 - Include the creation time of a circuit in CIRC and CIRC2
7796 control-port events and the list produced by the 'GETINFO
7797 circuit-status' control-port command.
7799 o Minor features (directory authorities):
7800 - Directory authorities now reject versions of Tor older than
7801 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7802 inclusive. These versions accounted for only a small fraction of
7803 the Tor network, and have numerous known security issues. Resolves
7805 - Authority operators can now vote for all relays in a given
7806 set of countries to be BadDir/BadExit/Invalid/Rejected.
7807 - Provide two consensus parameters (FastFlagMinThreshold and
7808 FastFlagMaxThreshold) to control the range of allowable bandwidths
7809 for the Fast directory flag. These allow authorities to run
7810 experiments on appropriate requirements for being a "Fast" node.
7811 The AuthDirFastGuarantee config value still applies. Implements
7813 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7814 directory authority option (introduced in Tor 0.2.2.34).
7816 o Minor features (other):
7817 - Don't disable the DirPort when we cannot exceed our AccountingMax
7818 limit during this interval because the effective bandwidthrate is
7819 low enough. This is useful in a situation where AccountMax is only
7820 used as an additional safeguard or to provide statistics.
7821 - Prepend an informative header to generated dynamic_dh_params files.
7822 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
7823 EntryNodes will have no effect. Resolves issue 2571.
7824 - Log more useful messages when we fail to disable debugger
7826 - Log which authority we're missing votes from when we go to fetch
7827 them from the other auths.
7828 - Log (at debug level) whenever a circuit's purpose is changed.
7829 - Add missing documentation for the MaxClientCircuitsPending,
7830 UseMicrodescriptors, UserspaceIOCPBuffers, and
7831 _UseFilteringSSLBufferevents options, all introduced during
7833 - Update to the January 3 2012 Maxmind GeoLite Country database.
7835 o Minor bugfixes (hidden services):
7836 - Don't close hidden service client circuits which have almost
7837 finished connecting to their destination when they reach
7838 the normal circuit-build timeout. Previously, we would close
7839 introduction circuits which are waiting for an acknowledgement
7840 from the introduction point, and rendezvous circuits which have
7841 been specified in an INTRODUCE1 cell sent to a hidden service,
7842 after the normal CBT. Now, we mark them as 'timed out', and launch
7843 another rendezvous attempt in parallel. This behavior change can
7844 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7845 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7846 - Don't close hidden-service-side rendezvous circuits when they
7847 reach the normal circuit-build timeout. This behavior change can
7848 be disabled using the new
7849 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7850 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7851 - Make sure we never mark the wrong rendezvous circuit as having
7852 had its introduction cell acknowleged by the introduction-point
7853 relay. Previously, when we received an INTRODUCE_ACK cell on a
7854 client-side hidden-service introduction circuit, we might have
7855 marked a rendezvous circuit other than the one we specified in
7856 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
7857 a warning message and interfered with the hidden service
7858 connection-establishment process. Fixes bug 4759; bugfix on
7859 0.2.3.3-alpha, when we added the stream-isolation feature which
7860 might cause Tor to open multiple rendezvous circuits for the same
7862 - Don't trigger an assertion failure when we mark a new client-side
7863 hidden-service introduction circuit for close during the process
7864 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
7867 o Minor bugfixes (log messages):
7868 - Correctly spell "connect" in a log message on failure to create a
7869 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
7871 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7872 Fixes bug 4856; bugfix on Tor 0.0.6.
7873 - Fix the log message describing how we work around discovering
7874 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7875 4837; bugfix on 0.2.2.9-alpha.
7876 - When logging about a disallowed .exit name, do not also call it
7877 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7879 o Minor bugfixes (build fixes):
7880 - During configure, detect when we're building with clang version
7881 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7882 CFLAGS. clang doesn't support them yet.
7883 - During configure, search for library containing cos function as
7884 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7885 against libm was hard-coded before. Fixes the first part of bug
7886 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7888 - Detect attempts to build Tor on (as yet hypothetical) versions
7889 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7890 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7891 - Preprocessor directives should not be put inside the arguments
7892 of a macro. This would break compilation with GCC releases prior
7893 to version 3.3. We would never recommend such an old GCC version,
7894 but it is apparently required for binary compatibility on some
7895 platforms (namely, certain builds of Haiku). Fixes the other part
7896 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
7899 o Minor bugfixes (other):
7900 - Older Linux kernels erroneously respond to strange nmap behavior
7901 by having accept() return successfully with a zero-length
7902 socket. When this happens, just close the connection. Previously,
7903 we would try harder to learn the remote address: but there was
7904 no such remote address to learn, and our method for trying to
7905 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7906 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7907 - Fix null-pointer access that could occur if TLS allocation failed.
7908 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
7909 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
7910 accidentally been reverted.
7911 - Fix our implementation of crypto_random_hostname() so it can't
7912 overflow on ridiculously large inputs. (No Tor version has ever
7913 provided this kind of bad inputs, but let's be correct in depth.)
7914 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7915 - Find more places in the code that should have been testing for
7916 invalid sockets using the SOCKET_OK macro. Required for a fix
7917 for bug 4533. Bugfix on 0.2.2.28-beta.
7918 - Fix an assertion failure when, while running with bufferevents, a
7919 connection finishes connecting after it is marked for close, but
7920 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
7921 - test_util_spawn_background_ok() hardcoded the expected value
7922 for ENOENT to 2. This isn't portable as error numbers are
7923 platform specific, and particularly the hurd has ENOENT at
7924 0x40000002. Construct expected string at runtime, using the correct
7925 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
7926 - Reject attempts to disable DisableDebuggerAttachment while Tor is
7927 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
7928 - Use an appropriate-width type for sockets in tor-fw-helper on
7929 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
7932 - When sending or relaying a RELAY_EARLY cell, we used to convert
7933 it to a RELAY cell if the connection was using the v1 link
7934 protocol. This was a workaround for older versions of Tor, which
7935 didn't handle RELAY_EARLY cells properly. Now that all supported
7936 versions can handle RELAY_EARLY cells, and now that we're enforcing
7937 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7938 remove this workaround. Addresses bug 4786.
7940 o Code simplifications and refactoring:
7941 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7942 own homebrewed ssl_state_to_string() replacement. Patch from
7943 Emile Snyder. Fixes bug 4653.
7944 - Use macros to indicate OpenSSL versions, so we don't need to worry
7945 about accidental hexadecimal bit shifts.
7946 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7948 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7949 - Use the smartlist_add_asprintf() alias more consistently.
7950 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7951 invalid value, rather than just -1.
7952 - Rename a handful of old identifiers, mostly related to crypto
7953 structures and crypto functions. By convention, our "create an
7954 object" functions are called "type_new()", our "free an object"
7955 functions are called "type_free()", and our types indicate that
7956 they are types only with a final "_t". But a handful of older
7957 types and functions broke these rules, with function names like
7958 "type_create" or "subsystem_op_type", or with type names like
7962 Changes in version 0.2.3.10-alpha - 2011-12-16
7963 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
7964 Tor's buffers code. Absolutely everybody should upgrade.
7966 The bug relied on an incorrect calculation when making data continuous
7967 in one of our IO buffers, if the first chunk of the buffer was
7968 misaligned by just the wrong amount. The miscalculation would allow an
7969 attacker to overflow a piece of heap-allocated memory. To mount this
7970 attack, the attacker would need to either open a SOCKS connection to
7971 Tor's SocksPort (usually restricted to localhost), or target a Tor
7972 instance configured to make its connections through a SOCKS proxy
7973 (which Tor does not do by default).
7975 Good security practice requires that all heap-overflow bugs should be
7976 presumed to be exploitable until proven otherwise, so we are treating
7977 this as a potential code execution attack. Please upgrade immediately!
7978 This bug does not affect bufferevents-based builds of Tor. Special
7979 thanks to "Vektor" for reporting this issue to us!
7981 This release also contains a few minor bugfixes for issues discovered
7985 - Fix a heap overflow bug that could occur when trying to pull
7986 data into the first chunk of a buffer, when that chunk had
7987 already had some data drained from it. Fixes CVE-2011-2778;
7988 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7991 - If we can't attach streams to a rendezvous circuit when we
7992 finish connecting to a hidden service, clear the rendezvous
7993 circuit's stream-isolation state and try to attach streams
7994 again. Previously, we cleared rendezvous circuits' isolation
7995 state either too early (if they were freshly built) or not at all
7996 (if they had been built earlier and were cannibalized). Bugfix on
7997 0.2.3.3-alpha; fixes bug 4655.
7998 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
7999 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
8000 - Fix an assertion failure when a relay with accounting enabled
8001 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
8004 - Update to the December 6 2011 Maxmind GeoLite Country database.
8007 Changes in version 0.2.2.35 - 2011-12-16
8008 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
8009 buffers code. Absolutely everybody should upgrade.
8011 The bug relied on an incorrect calculation when making data continuous
8012 in one of our IO buffers, if the first chunk of the buffer was
8013 misaligned by just the wrong amount. The miscalculation would allow an
8014 attacker to overflow a piece of heap-allocated memory. To mount this
8015 attack, the attacker would need to either open a SOCKS connection to
8016 Tor's SocksPort (usually restricted to localhost), or target a Tor
8017 instance configured to make its connections through a SOCKS proxy
8018 (which Tor does not do by default).
8020 Good security practice requires that all heap-overflow bugs should be
8021 presumed to be exploitable until proven otherwise, so we are treating
8022 this as a potential code execution attack. Please upgrade immediately!
8023 This bug does not affect bufferevents-based builds of Tor. Special
8024 thanks to "Vektor" for reporting this issue to us!
8026 Tor 0.2.2.35 also fixes several bugs in previous versions, including
8027 crash bugs for unusual configurations, and a long-term bug that
8028 would prevent Tor from starting on Windows machines with draconian
8031 With this release, we remind everyone that 0.2.0.x has reached its
8032 formal end-of-life. Those Tor versions have many known flaws, and
8033 nobody should be using them. You should upgrade -- ideally to the
8034 0.2.2.x series. If you're using a Linux or BSD and its packages are
8035 obsolete, stop using those packages and upgrade anyway.
8037 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
8038 longer receive support after some time in early 2012.
8041 - Fix a heap overflow bug that could occur when trying to pull
8042 data into the first chunk of a buffer, when that chunk had
8043 already had some data drained from it. Fixes CVE-2011-2778;
8044 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8045 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8046 that it doesn't attempt to allocate a socketpair. This could cause
8047 some problems on Windows systems with overzealous firewalls. Fix for
8048 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8050 - If we mark an OR connection for close based on a cell we process,
8051 don't process any further cells on it. We already avoid further
8052 reads on marked-for-close connections, but now we also discard the
8053 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8054 which was the first version where we might mark a connection for
8055 close based on processing a cell on it.
8056 - Correctly sanity-check that we don't underflow on a memory
8057 allocation (and then assert) for hidden service introduction
8058 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8059 bugfix on 0.2.1.5-alpha.
8060 - Fix a memory leak when we check whether a hidden service
8061 descriptor has any usable introduction points left. Fixes bug
8062 4424. Bugfix on 0.2.2.25-alpha.
8063 - Don't crash when we're running as a relay and don't have a GeoIP
8064 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
8065 we've had in the 0.2.3.x branch already.
8066 - When running as a client, do not print a misleading (and plain
8067 wrong) log message that we're collecting "directory request"
8068 statistics: clients don't collect statistics. Also don't create a
8069 useless (because empty) stats file in the stats/ directory. Fixes
8070 bug 4353; bugfix on 0.2.2.34.
8073 - Detect failure to initialize Libevent. This fix provides better
8074 detection for future instances of bug 4457.
8075 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8076 function. This was eating up hideously large amounts of time on some
8077 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8078 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8079 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8081 - Don't warn about unused log_mutex in log.c when building with
8082 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8083 0.1.0.6-rc which introduced --disable-threads.
8084 - When configuring, starting, or stopping an NT service, stop
8085 immediately after the service configuration attempt has succeeded
8086 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8087 - When sending a NETINFO cell, include the original address
8088 received for the other side, not its canonical address. Found
8089 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8090 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
8091 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8092 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8093 occurred when a client tried to fetch a descriptor for a bridge
8094 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8095 - Backport fixes for a pair of compilation warnings on Windows.
8096 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
8097 - If we had ever tried to call tor_addr_to_str on an address of
8098 unknown type, we would have done a strdup on an uninitialized
8099 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8100 Reported by "troll_un".
8101 - Correctly detect and handle transient lookup failures from
8102 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8103 Reported by "troll_un".
8104 - Fix null-pointer access that could occur if TLS allocation failed.
8105 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8106 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8107 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8110 - Add two new config options for directory authorities:
8111 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8112 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8113 that is always sufficient to satisfy the bandwidth requirement for
8114 the Guard flag. Now it will be easier for researchers to simulate
8115 Tor networks with different values. Resolves ticket 4484.
8116 - When Tor ignores a hidden service specified in its configuration,
8117 include the hidden service's directory in the warning message.
8118 Previously, we would only tell the user that some hidden service
8119 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8120 - Update to the December 6 2011 Maxmind GeoLite Country database.
8122 o Packaging changes:
8123 - Make it easier to automate expert package builds on Windows,
8124 by removing an absolute path from makensis.exe command.
8127 Changes in version 0.2.1.32 - 2011-12-16
8128 Tor 0.2.1.32 backports important security and privacy fixes for
8129 oldstable. This release is intended only for package maintainers and
8130 others who cannot use the 0.2.2 stable series. All others should be
8131 using Tor 0.2.2.x or newer.
8133 The Tor 0.2.1.x series will reach formal end-of-life some time in
8134 early 2012; we will stop releasing patches for it then.
8136 o Major bugfixes (also included in 0.2.2.x):
8137 - Correctly sanity-check that we don't underflow on a memory
8138 allocation (and then assert) for hidden service introduction
8139 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8140 bugfix on 0.2.1.5-alpha.
8141 - Fix a heap overflow bug that could occur when trying to pull
8142 data into the first chunk of a buffer, when that chunk had
8143 already had some data drained from it. Fixes CVE-2011-2778;
8144 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8147 - Update to the December 6 2011 Maxmind GeoLite Country database.
8150 Changes in version 0.2.3.9-alpha - 2011-12-08
8151 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
8152 a "DisableNetwork" security feature that bundles can use to avoid
8153 touching the network until bridges are configured, moves forward on
8154 the pluggable transport design, fixes a flaw in the hidden service
8155 design that unnecessarily prevented clients with wrong clocks from
8156 reaching hidden services, and fixes a wide variety of other issues.
8159 - Clients can now connect to private bridges over IPv6. Bridges
8160 still need at least one IPv4 address in order to connect to
8161 other relays. Note that we don't yet handle the case where the
8162 user has two bridge lines for the same bridge (one IPv4, one
8163 IPv6). Implements parts of proposal 186.
8164 - New "DisableNetwork" config option to prevent Tor from launching any
8165 connections or accepting any connections except on a control port.
8166 Bundles and controllers can set this option before letting Tor talk
8167 to the rest of the network, for example to prevent any connections
8168 to a non-bridge address. Packages like Orbot can also use this
8169 option to instruct Tor to save power when the network is off.
8170 - Clients and bridges can now be configured to use a separate
8171 "transport" proxy. This approach makes the censorship arms race
8172 easier by allowing bridges to use protocol obfuscation plugins. It
8173 implements the "managed proxy" part of proposal 180 (ticket 3472).
8174 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
8175 implementation. It makes AES_CTR about 7% faster than our old one
8176 (which was about 10% faster than the one OpenSSL used to provide).
8177 Resolves ticket 4526.
8178 - Add a "tor2web mode" for clients that want to connect to hidden
8179 services non-anonymously (and possibly more quickly). As a safety
8180 measure to try to keep users from turning this on without knowing
8181 what they are doing, tor2web mode must be explicitly enabled at
8182 compile time, and a copy of Tor compiled to run in tor2web mode
8183 cannot be used as a normal Tor client. Implements feature 2553.
8184 - Add experimental support for running on Windows with IOCP and no
8185 kernel-space socket buffers. This feature is controlled by a new
8186 "UserspaceIOCPBuffers" config option (off by default), which has
8187 no effect unless Tor has been built with support for bufferevents,
8188 is running on Windows, and has enabled IOCP. This may, in the long
8189 run, help solve or mitigate bug 98.
8190 - Use a more secure consensus parameter voting algorithm. Now at
8191 least three directory authorities or a majority of them must
8192 vote on a given parameter before it will be included in the
8193 consensus. Implements proposal 178.
8196 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
8197 They used to check that the timestamp was within 30 minutes
8198 of their system clock, so they could cap the size of their
8199 replay-detection cache, but that approach unnecessarily refused
8200 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
8201 the v3 intro-point protocol (the first one which sent a timestamp
8202 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
8203 - Only use the EVP interface when AES acceleration is enabled,
8204 to avoid a 5-7% performance regression. Resolves issue 4525;
8205 bugfix on 0.2.3.8-alpha.
8207 o Privacy/anonymity features (bridge detection):
8208 - Make bridge SSL certificates a bit more stealthy by using random
8209 serial numbers, in the same fashion as OpenSSL when generating
8210 self-signed certificates. Implements ticket 4584.
8211 - Introduce a new config option "DynamicDHGroups", enabled by
8212 default, which provides each bridge with a unique prime DH modulus
8213 to be used during SSL handshakes. This option attempts to help
8214 against censors who might use the Apache DH modulus as a static
8215 identifier for bridges. Addresses ticket 4548.
8217 o Minor features (new/different config options):
8218 - New configuration option "DisableDebuggerAttachment" (on by default)
8219 to prevent basic debugging attachment attempts by other processes.
8220 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
8221 - Allow MapAddress directives to specify matches against super-domains,
8222 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
8223 Implements issue 933.
8224 - Slightly change behavior of "list" options (that is, config
8225 options that can appear more than once) when they appear both in
8226 torrc and on the command line. Previously, the command-line options
8227 would be appended to the ones from torrc. Now, the command-line
8228 options override the torrc options entirely. This new behavior
8229 allows the user to override list options (like exit policies and
8230 ports to listen on) from the command line, rather than simply
8231 appending to the list.
8232 - You can get the old (appending) command-line behavior for "list"
8233 options by prefixing the option name with a "+".
8234 - You can remove all the values for a "list" option from the command
8235 line without adding any new ones by prefixing the option name
8237 - Add experimental support for a "defaults" torrc file to be parsed
8238 before the regular torrc. Torrc options override the defaults file's
8239 options in the same way that the command line overrides the torrc.
8240 The SAVECONF controller command saves only those options which
8241 differ between the current configuration and the defaults file. HUP
8242 reloads both files. (Note: This is an experimental feature; its
8243 behavior will probably be refined in future 0.2.3.x-alpha versions
8244 to better meet packagers' needs.) Implements task 4552.
8247 - Try to make the introductory warning message that Tor prints on
8248 startup more useful for actually finding help and information.
8249 Resolves ticket 2474.
8250 - Running "make version" now displays the version of Tor that
8251 we're about to build. Idea from katmagic; resolves issue 4400.
8252 - Expire old or over-used hidden service introduction points.
8253 Required by fix for bug 3460.
8254 - Move the replay-detection cache for the RSA-encrypted parts of
8255 INTRODUCE2 cells to the introduction point data structures.
8256 Previously, we would use one replay-detection cache per hidden
8257 service. Required by fix for bug 3460.
8258 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
8259 public key replay-detection cache from 60 minutes to 5 minutes. This
8260 replay-detection cache is now used only to detect multiple
8261 INTRODUCE2 cells specifying the same rendezvous point, so we can
8262 avoid launching multiple simultaneous attempts to connect to it.
8264 o Minor bugfixes (on Tor 0.2.2.x and earlier):
8265 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8266 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8268 - Fix a minor formatting issue in one of tor-gencert's error messages.
8270 - Prevent a false positive from the check-spaces script, by disabling
8271 the "whitespace between function name and (" check for functions
8273 - Fix a log message suggesting that people contact a non-existent
8274 email address. Fixes bug 3448.
8275 - Fix null-pointer access that could occur if TLS allocation failed.
8276 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8277 - Report a real bootstrap problem to the controller on router
8278 identity mismatch. Previously we just said "foo", which probably
8279 made a lot of sense at the time. Fixes bug 4169; bugfix on
8281 - If we had ever tried to call tor_addr_to_str() on an address of
8282 unknown type, we would have done a strdup() on an uninitialized
8283 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8284 Reported by "troll_un".
8285 - Correctly detect and handle transient lookup failures from
8286 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8287 Reported by "troll_un".
8288 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8289 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8290 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
8291 bug 4532; found by "troll_un".
8293 o Minor bugfixes (on Tor 0.2.3.x):
8294 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
8296 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
8297 circuit for use as a hidden service client's rendezvous point.
8298 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
8299 with help from wanoskarnet.
8300 - Restore behavior of overriding SocksPort, ORPort, and similar
8301 options from the command line. Bugfix on 0.2.3.3-alpha.
8304 - Properly handle the case where the build-tree is not the same
8305 as the source tree when generating src/common/common_sha1.i,
8306 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
8307 bugfix on 0.2.0.1-alpha.
8309 o Code simplifications, cleanups, and refactorings:
8310 - Remove the pure attribute from all functions that used it
8311 previously. In many cases we assigned it incorrectly, because the
8312 functions might assert or call impure functions, and we don't have
8313 evidence that keeping the pure attribute is worthwhile. Implements
8314 changes suggested in ticket 4421.
8315 - Remove some dead code spotted by coverity. Fixes cid 432.
8316 Bugfix on 0.2.3.1-alpha, closes bug 4637.
8319 Changes in version 0.2.3.8-alpha - 2011-11-22
8320 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
8321 socketpair-related bug that has been bothering Windows users. It adds
8322 support to serve microdescriptors to controllers, so Vidalia's network
8323 map can resume listing relays (once Vidalia implements its side),
8324 and adds better support for hardware AES acceleration. Finally, it
8325 starts the process of adjusting the bandwidth cutoff for getting the
8326 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
8327 that tiny relays harm performance more than they help network capacity.
8330 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8331 that it doesn't attempt to allocate a socketpair. This could cause
8332 some problems on Windows systems with overzealous firewalls. Fix for
8333 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8335 - Correctly sanity-check that we don't underflow on a memory
8336 allocation (and then assert) for hidden service introduction
8337 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8338 bugfix on 0.2.1.5-alpha.
8339 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8340 flag. In the past few years the average relay speed has picked
8341 up, and while the "top 7/8 of the network get the Fast flag" and
8342 "all relays with 20KB or more of capacity get the Fast flag" rules
8343 used to have the same result, now the top 7/8 of the network has
8344 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8345 - Fix a rare assertion failure when checking whether a v0 hidden
8346 service descriptor has any usable introduction points left, and
8347 we don't have enough information to build a circuit to the first
8348 intro point named in the descriptor. The HS client code in
8349 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
8350 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
8351 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
8352 - Make bridge authorities not crash when they are asked for their own
8353 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
8354 - When running as a client, do not print a misleading (and plain
8355 wrong) log message that we're collecting "directory request"
8356 statistics: clients don't collect statistics. Also don't create a
8357 useless (because empty) stats file in the stats/ directory. Fixes
8358 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
8361 - Allow Tor controllers like Vidalia to obtain the microdescriptor
8362 for a relay by identity digest or nickname. Previously,
8363 microdescriptors were only available by their own digests, so a
8364 controller would have to ask for and parse the whole microdescriptor
8365 consensus in order to look up a single relay's microdesc. Fixes
8366 bug 3832; bugfix on 0.2.3.1-alpha.
8367 - Use OpenSSL's EVP interface for AES encryption, so that all AES
8368 operations can use hardware acceleration (if present). Resolves
8371 o Minor bugfixes (on 0.2.2.x and earlier):
8372 - Detect failure to initialize Libevent. This fix provides better
8373 detection for future instances of bug 4457.
8374 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8375 function. This was eating up hideously large amounts of time on some
8376 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8377 - Don't warn about unused log_mutex in log.c when building with
8378 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8379 0.1.0.6-rc which introduced --disable-threads.
8380 - Allow manual 'authenticate' commands to the controller interface
8381 from netcat (nc) as well as telnet. We were rejecting them because
8382 they didn't come with the expected whitespace at the end of the
8383 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8384 - Fix some (not actually triggerable) buffer size checks in usage of
8385 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8387 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8388 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8389 - When configuring, starting, or stopping an NT service, stop
8390 immediately after the service configuration attempt has succeeded
8391 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8392 - When sending a NETINFO cell, include the original address
8393 received for the other side, not its canonical address. Found
8394 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8395 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8396 can pick them up when the tests aren't disabled. Bugfix on
8397 0.2.2.4-alpha which introduced tinytest.
8398 - Fix a memory leak when we check whether a hidden service
8399 descriptor has any usable introduction points left. Fixes bug
8400 4424. Bugfix on 0.2.2.25-alpha.
8401 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8402 occurred when a client tried to fetch a descriptor for a bridge
8403 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8405 o Minor bugfixes (on 0.2.3.x):
8406 - Make util unit tests build correctly with MSVC. Bugfix on
8407 0.2.3.3-alpha. Patch by Gisle Vanem.
8408 - Successfully detect AUTH_CHALLENGE cells with no recognized
8409 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
8411 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
8412 it should still send a NETINFO cell to allow the connection to
8413 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
8415 - Log less loudly when we get an invalid authentication certificate
8416 from a source other than a directory authority: it's not unusual
8417 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
8419 - Tolerate servers with more clock skew in their authentication
8420 certificates than previously. Fixes bug 4371; bugfix on
8422 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
8423 on 0.2.3.4-alpha and 0.2.3.6-alpha.
8426 - Add two new config options for directory authorities:
8427 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8428 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8429 that is always sufficient to satisfy the bandwidth requirement for
8430 the Guard flag. Now it will be easier for researchers to simulate
8431 Tor networks with different values. Resolves ticket 4484.
8432 - When Tor ignores a hidden service specified in its configuration,
8433 include the hidden service's directory in the warning message.
8434 Previously, we would only tell the user that some hidden service
8435 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8436 - When we fail to initialize Libevent, retry with IOCP disabled so we
8437 don't need to turn on multi-threading support in Libevent, which in
8438 turn requires a working socketpair(). This is a workaround for bug
8439 4457, which affects Libevent versions from 2.0.1-alpha through
8441 - Detect when we try to build on a platform that doesn't define
8442 AF_UNSPEC to 0. We don't work there, so refuse to compile.
8443 - Update to the November 1 2011 Maxmind GeoLite Country database.
8445 o Packaging changes:
8446 - Make it easier to automate expert package builds on Windows,
8447 by removing an absolute path from makensis.exe command.
8449 o Code simplifications and refactoring:
8450 - Remove some redundant #include directives throughout the code.
8451 Patch from Andrea Gelmini.
8452 - Unconditionally use OpenSSL's AES implementation instead of our
8453 old built-in one. OpenSSL's AES has been better for a while, and
8454 relatively few servers should still be on any version of OpenSSL
8455 that doesn't have good optimized assembly AES.
8456 - Use the name "CERTS" consistently to refer to the new cell type;
8457 we were calling it CERT in some places and CERTS in others.
8460 - Numerous new unit tests for functions in util.c and address.c by
8462 - The long-disabled benchmark tests are now split into their own
8463 ./src/test/bench binary.
8464 - The benchmark tests can now use more accurate timers than
8465 gettimeofday() when such timers are available.
8468 Changes in version 0.2.3.7-alpha - 2011-10-30
8469 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
8470 the new v3 handshake. It also resolves yet another bridge address
8474 - If we mark an OR connection for close based on a cell we process,
8475 don't process any further cells on it. We already avoid further
8476 reads on marked-for-close connections, but now we also discard the
8477 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8478 which was the first version where we might mark a connection for
8479 close based on processing a cell on it.
8480 - Fix a double-free bug that would occur when we received an invalid
8481 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
8482 bugfix on 0.2.3.6-alpha.
8483 - Bridges no longer include their address in NETINFO cells on outgoing
8484 OR connections, to allow them to blend in better with clients.
8485 Removes another avenue for enumerating bridges. Reported by
8486 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
8487 cells were introduced.
8490 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
8491 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8494 Changes in version 0.2.3.6-alpha - 2011-10-26
8495 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
8496 anonymity vulnerability where an attacker can deanonymize Tor
8497 users. Everybody should upgrade.
8499 This release also features support for a new v3 connection handshake
8500 protocol, and fixes to make hidden service connections more robust.
8503 - Implement a new handshake protocol (v3) for authenticating Tors to
8504 each other over TLS. It should be more resistant to fingerprinting
8505 than previous protocols, and should require less TLS hacking for
8506 future Tor implementations. Implements proposal 176.
8507 - Allow variable-length padding cells to disguise the length of
8508 Tor's TLS records. Implements part of proposal 184.
8510 o Privacy/anonymity fixes (clients):
8511 - Clients and bridges no longer send TLS certificate chains on
8512 outgoing OR connections. Previously, each client or bridge would
8513 use the same cert chain for all outgoing OR connections until
8514 its IP address changes, which allowed any relay that the client
8515 or bridge contacted to determine which entry guards it is using.
8516 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8517 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8518 no longer considers that connection as suitable for satisfying a
8519 circuit EXTEND request. Now relays can protect clients from the
8520 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8521 - Directory authorities no longer assign the Guard flag to relays
8522 that haven't upgraded to the above "refuse EXTEND requests
8523 to client connections" fix. Now directory authorities can
8524 protect clients from the CVE-2011-2768 issue even if neither
8525 the clients nor the relays have upgraded yet. There's a new
8526 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8527 to let us transition smoothly, else tomorrow there would be no
8530 o Major bugfixes (hidden services):
8531 - Improve hidden service robustness: when an attempt to connect to
8532 a hidden service ends, be willing to refetch its hidden service
8533 descriptors from each of the HSDir relays responsible for them
8534 immediately. Previously, we would not consider refetching the
8535 service's descriptors from each HSDir for 15 minutes after the last
8536 fetch, which was inconvenient if the hidden service was not running
8537 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
8538 - When one of a hidden service's introduction points appears to be
8539 unreachable, stop trying it. Previously, we would keep trying
8540 to build circuits to the introduction point until we lost the
8541 descriptor, usually because the user gave up and restarted Tor.
8542 Partly fixes bug 3825.
8543 - Don't launch a useless circuit after failing to use one of a
8544 hidden service's introduction points. Previously, we would
8545 launch a new introduction circuit, but not set the hidden service
8546 which that circuit was intended to connect to, so it would never
8547 actually be used. A different piece of code would then create a
8548 new introduction circuit correctly. Bug reported by katmagic and
8549 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8551 o Major bugfixes (other):
8552 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8553 that they initiated. Relays could distinguish incoming bridge
8554 connections from client connections, creating another avenue for
8555 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8556 Found by "frosty_un".
8557 - Don't update the AccountingSoftLimitHitAt state file entry whenever
8558 tor gets started. This prevents a wrong average bandwidth
8559 estimate, which would cause relays to always start a new accounting
8560 interval at the earliest possible moment. Fixes bug 2003; bugfix
8561 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
8562 immensely in tracking this bug down.
8563 - Fix a crash bug when changing node restrictions while a DNS lookup
8564 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8567 o Minor bugfixes (on 0.2.2.x and earlier):
8568 - When a hidden service turns an extra service-side introduction
8569 circuit into a general-purpose circuit, free the rend_data and
8570 intro_key fields first, so we won't leak memory if the circuit
8571 is cannibalized for use as another service-side introduction
8572 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8573 - Rephrase the log message emitted if the TestSocks check is
8574 successful. Patch from Fabian Keil; fixes bug 4094.
8575 - Bridges now skip DNS self-tests, to act a little more stealthily.
8576 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8577 bridges. Patch by "warms0x".
8578 - Remove a confusing dollar sign from the example fingerprint in the
8579 man page, and also make the example fingerprint a valid one. Fixes
8580 bug 4309; bugfix on 0.2.1.3-alpha.
8581 - Fix internal bug-checking logic that was supposed to catch
8582 failures in digest generation so that it will fail more robustly
8583 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8584 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8585 - Report any failure in init_keys() calls launched because our
8586 IP address has changed. Spotted by Coverity Scan. Bugfix on
8587 0.1.1.4-alpha; fixes CID 484.
8589 o Minor bugfixes (on 0.2.3.x):
8590 - Fix a bug in configure.in that kept it from building a configure
8591 script with autoconf versions earlier than 2.61. Fixes bug 2430;
8592 bugfix on 0.2.3.1-alpha.
8593 - Don't warn users that they are exposing a client port to the
8594 Internet if they have specified an RFC1918 address. Previously,
8595 we would warn if the user had specified any non-loopback
8596 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
8597 - Fix memory leaks in the failing cases of the new SocksPort and
8598 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
8599 fixes coverity CIDs 485, 486, and 487.
8602 - When a hidden service's introduction point times out, consider
8603 trying it again during the next attempt to connect to the
8604 HS. Previously, we would not try it again unless a newly fetched
8605 descriptor contained it. Required by fixes for bugs 1297 and 3825.
8606 - The next version of Windows will be called Windows 8, and it has
8607 a major version of 6, minor version of 2. Correctly identify that
8608 version instead of calling it "Very recent version". Resolves
8609 ticket 4153; reported by funkstar.
8610 - The Bridge Authority now writes statistics on how many bridge
8611 descriptors it gave out in total, and how many unique descriptors
8612 it gave out. It also lists how often the most and least commonly
8613 fetched descriptors were given out, as well as the median and
8614 25th/75th percentile. Implements tickets 4200 and 4294.
8615 - Update to the October 4 2011 Maxmind GeoLite Country database.
8617 o Code simplifications and refactoring:
8618 - Remove some old code to remember statistics about which descriptors
8619 we've served as a directory mirror. The feature wasn't used and
8620 is outdated now that microdescriptors are around.
8621 - Rename Tor functions that turn strings into addresses, so that
8622 "parse" indicates that no hostname resolution occurs, and
8623 "lookup" indicates that hostname resolution may occur. This
8624 should help prevent mistakes in the future. Fixes bug 3512.
8627 Changes in version 0.2.2.34 - 2011-10-26
8628 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
8629 can deanonymize Tor users. Everybody should upgrade.
8631 The attack relies on four components: 1) Clients reuse their TLS cert
8632 when talking to different relays, so relays can recognize a user by
8633 the identity key in her cert. 2) An attacker who knows the client's
8634 identity key can probe each guard relay to see if that identity key
8635 is connected to that guard relay right now. 3) A variety of active
8636 attacks in the literature (starting from "Low-Cost Traffic Analysis
8637 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
8638 discover the guard relays that a Tor user visiting the website is using.
8639 4) Clients typically pick three guards at random, so the set of guards
8640 for a given user could well be a unique fingerprint for her. This
8641 release fixes components #1 and #2, which is enough to block the attack;
8642 the other two remain as open research problems. Special thanks to
8643 "frosty_un" for reporting the issue to us!
8645 Clients should upgrade so they are no longer recognizable by the TLS
8646 certs they present. Relays should upgrade so they no longer allow a
8647 remote attacker to probe them to test whether unpatched clients are
8648 currently connected to them.
8650 This release also fixes several vulnerabilities that allow an attacker
8651 to enumerate bridge relays. Some bridge enumeration attacks still
8652 remain; see for example proposal 188.
8654 o Privacy/anonymity fixes (clients):
8655 - Clients and bridges no longer send TLS certificate chains on
8656 outgoing OR connections. Previously, each client or bridge would
8657 use the same cert chain for all outgoing OR connections until
8658 its IP address changes, which allowed any relay that the client
8659 or bridge contacted to determine which entry guards it is using.
8660 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8661 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8662 no longer considers that connection as suitable for satisfying a
8663 circuit EXTEND request. Now relays can protect clients from the
8664 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8665 - Directory authorities no longer assign the Guard flag to relays
8666 that haven't upgraded to the above "refuse EXTEND requests
8667 to client connections" fix. Now directory authorities can
8668 protect clients from the CVE-2011-2768 issue even if neither
8669 the clients nor the relays have upgraded yet. There's a new
8670 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8671 to let us transition smoothly, else tomorrow there would be no
8674 o Privacy/anonymity fixes (bridge enumeration):
8675 - Bridge relays now do their directory fetches inside Tor TLS
8676 connections, like all the other clients do, rather than connecting
8677 directly to the DirPort like public relays do. Removes another
8678 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8679 - Bridges relays now build circuits for themselves in a more similar
8680 way to how clients build them. Removes another avenue for
8681 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8682 when bridges were introduced.
8683 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8684 that they initiated. Relays could distinguish incoming bridge
8685 connections from client connections, creating another avenue for
8686 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8687 Found by "frosty_un".
8690 - Fix a crash bug when changing node restrictions while a DNS lookup
8691 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8693 - Don't launch a useless circuit after failing to use one of a
8694 hidden service's introduction points. Previously, we would
8695 launch a new introduction circuit, but not set the hidden service
8696 which that circuit was intended to connect to, so it would never
8697 actually be used. A different piece of code would then create a
8698 new introduction circuit correctly. Bug reported by katmagic and
8699 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8702 - Change an integer overflow check in the OpenBSD_Malloc code so
8703 that GCC is less likely to eliminate it as impossible. Patch
8704 from Mansour Moufid. Fixes bug 4059.
8705 - When a hidden service turns an extra service-side introduction
8706 circuit into a general-purpose circuit, free the rend_data and
8707 intro_key fields first, so we won't leak memory if the circuit
8708 is cannibalized for use as another service-side introduction
8709 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8710 - Bridges now skip DNS self-tests, to act a little more stealthily.
8711 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8712 bridges. Patch by "warms0x".
8713 - Fix internal bug-checking logic that was supposed to catch
8714 failures in digest generation so that it will fail more robustly
8715 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8716 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8717 - Report any failure in init_keys() calls launched because our
8718 IP address has changed. Spotted by Coverity Scan. Bugfix on
8719 0.1.1.4-alpha; fixes CID 484.
8721 o Minor bugfixes (log messages and documentation):
8722 - Remove a confusing dollar sign from the example fingerprint in the
8723 man page, and also make the example fingerprint a valid one. Fixes
8724 bug 4309; bugfix on 0.2.1.3-alpha.
8725 - The next version of Windows will be called Windows 8, and it has
8726 a major version of 6, minor version of 2. Correctly identify that
8727 version instead of calling it "Very recent version". Resolves
8728 ticket 4153; reported by funkstar.
8729 - Downgrade log messages about circuit timeout calibration from
8730 "notice" to "info": they don't require or suggest any human
8731 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8732 bugfix on 0.2.2.14-alpha.
8735 - Turn on directory request statistics by default and include them in
8736 extra-info descriptors. Don't break if we have no GeoIP database.
8737 Backported from 0.2.3.1-alpha; implements ticket 3951.
8738 - Update to the October 4 2011 Maxmind GeoLite Country database.
8741 Changes in version 0.2.1.31 - 2011-10-26
8742 Tor 0.2.1.31 backports important security and privacy fixes for
8743 oldstable. This release is intended only for package maintainers and
8744 others who cannot use the 0.2.2 stable series. All others should be
8745 using Tor 0.2.2.x or newer.
8747 o Security fixes (also included in 0.2.2.x):
8748 - Replace all potentially sensitive memory comparison operations
8749 with versions whose runtime does not depend on the data being
8750 compared. This will help resist a class of attacks where an
8751 adversary can use variations in timing information to learn
8752 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8753 implementation by Robert Ransom based partially on code by DJB.)
8754 - Fix an assert in parsing router descriptors containing IPv6
8755 addresses. This one took down the directory authorities when
8756 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8758 o Privacy/anonymity fixes (also included in 0.2.2.x):
8759 - Clients and bridges no longer send TLS certificate chains on
8760 outgoing OR connections. Previously, each client or bridge would
8761 use the same cert chain for all outgoing OR connections until
8762 its IP address changes, which allowed any relay that the client
8763 or bridge contacted to determine which entry guards it is using.
8764 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8765 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8766 no longer considers that connection as suitable for satisfying a
8767 circuit EXTEND request. Now relays can protect clients from the
8768 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8769 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8770 that they initiated. Relays could distinguish incoming bridge
8771 connections from client connections, creating another avenue for
8772 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8773 Found by "frosty_un".
8774 - When receiving a hidden service descriptor, check that it is for
8775 the hidden service we wanted. Previously, Tor would store any
8776 hidden service descriptors that a directory gave it, whether it
8777 wanted them or not. This wouldn't have let an attacker impersonate
8778 a hidden service, but it did let directories pre-seed a client
8779 with descriptors that it didn't want. Bugfix on 0.0.6.
8780 - Avoid linkability based on cached hidden service descriptors: forget
8781 all hidden service descriptors cached as a client when processing a
8782 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8783 - Make the bridge directory authority refuse to answer directory
8784 requests for "all" descriptors. It used to include bridge
8785 descriptors in its answer, which was a major information leak.
8786 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8787 - Don't attach new streams to old rendezvous circuits after SIGNAL
8788 NEWNYM. Previously, we would keep using an existing rendezvous
8789 circuit if it remained open (i.e. if it were kept open by a
8790 long-lived stream, or if a new stream were attached to it before
8791 Tor could notice that it was old and no longer in use). Bugfix on
8792 0.1.1.15-rc; fixes bug 3375.
8794 o Minor bugfixes (also included in 0.2.2.x):
8795 - When we restart our relay, we might get a successful connection
8796 from the outside before we've started our reachability tests,
8797 triggering a warning: "ORPort found reachable, but I have no
8798 routerinfo yet. Failing to inform controller of success." This
8799 bug was harmless unless Tor is running under a controller
8800 like Vidalia, in which case the controller would never get a
8801 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8803 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8804 enabled. Fixes bug 1526.
8805 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8806 anything since 0.2.1.16-rc.
8807 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8808 None of the cases where we did this before were wrong, but by making
8809 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8810 - Fix a rare crash bug that could occur when a client was configured
8811 with a large number of bridges. Fixes bug 2629; bugfix on
8812 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8813 - Correct the warning displayed when a rendezvous descriptor exceeds
8814 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8816 - Fix an uncommon assertion failure when running with DNSPort under
8817 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8818 - When warning about missing zlib development packages during compile,
8819 give the correct package names. Bugfix on 0.2.0.1-alpha.
8820 - Require that introduction point keys and onion keys have public
8821 exponent 65537. Bugfix on 0.2.0.10-alpha.
8822 - Do not crash when our configuration file becomes unreadable, for
8823 example due to a permissions change, between when we start up
8824 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8826 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8828 - Always NUL-terminate the sun_path field of a sockaddr_un before
8829 passing it to the kernel. (Not a security issue: kernels are
8830 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8831 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8832 - Don't stack-allocate the list of supplementary GIDs when we're
8833 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8834 could take up to 256K, which is way too much stack. Found by
8835 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8837 o Minor bugfixes (only in 0.2.1.x):
8838 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
8839 rely on them. Bugfix on 0.2.1.30.
8840 - Use git revisions instead of svn revisions when generating our
8841 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8843 o Minor features (also included in 0.2.2.x):
8844 - Adjust the expiration time on our SSL session certificates to
8845 better match SSL certs seen in the wild. Resolves ticket 4014.
8846 - Allow nameservers with IPv6 address. Resolves bug 2574.
8847 - Update to the October 4 2011 Maxmind GeoLite Country database.
8850 Changes in version 0.2.3.5-alpha - 2011-09-28
8851 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
8852 bridge relays; fixes an assertion error that many users started hitting
8853 today; and adds the ability to refill token buckets more often than
8854 once per second, allowing significant performance improvements.
8857 - Bridge relays now do their directory fetches inside Tor TLS
8858 connections, like all the other clients do, rather than connecting
8859 directly to the DirPort like public relays do. Removes another
8860 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8861 - Bridges relays now build circuits for themselves in a more similar
8862 way to how clients build them. Removes another avenue for
8863 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8864 when bridges were introduced.
8867 - Fix an "Assertion md->held_by_node == 1 failed" error that could
8868 occur when the same microdescriptor was referenced by two node_t
8869 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
8871 o Major features (networking):
8872 - Add a new TokenBucketRefillInterval option to refill token buckets
8873 more frequently than once per second. This should improve network
8874 performance, alleviate queueing problems, and make traffic less
8875 bursty. Implements proposal 183; closes ticket 3630. Design by
8876 Florian Tschorsch and Björn Scheuermann; implementation by
8880 - Change an integer overflow check in the OpenBSD_Malloc code so
8881 that GCC is less likely to eliminate it as impossible. Patch
8882 from Mansour Moufid. Fixes bug 4059.
8884 o Minor bugfixes (usability):
8885 - Downgrade log messages about circuit timeout calibration from
8886 "notice" to "info": they don't require or suggest any human
8887 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8888 bugfix on 0.2.2.14-alpha.
8890 o Minor features (diagnostics):
8891 - When the system call to create a listener socket fails, log the
8892 error message explaining why. This may help diagnose bug 4027.
8895 Changes in version 0.2.3.4-alpha - 2011-09-13
8896 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
8897 tweak to Tor's TLS handshake that makes relays and bridges that run
8898 this new version reachable from Iran again. It also fixes a few new
8899 bugs in 0.2.3.x, and teaches relays to recognize when they're not
8900 listed in the network consensus and republish.
8902 o Major bugfixes (also part of 0.2.2.33):
8903 - Avoid an assertion failure when reloading a configuration with
8904 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8905 3923; bugfix on 0.2.2.25-alpha.
8907 o Minor features (security, also part of 0.2.2.33):
8908 - Check for replays of the public-key encrypted portion of an
8909 INTRODUCE1 cell, in addition to the current check for replays of
8910 the g^x value. This prevents a possible class of active attacks
8911 by an attacker who controls both an introduction point and a
8912 rendezvous point, and who uses the malleability of AES-CTR to
8913 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8914 that these attacks are infeasible (requiring the attacker to send
8915 on the order of zettabytes of altered cells in a short interval),
8916 but we'd rather block them off in case there are any classes of
8917 this attack that we missed. Reported by Willem Pinckaers.
8919 o Minor features (also part of 0.2.2.33):
8920 - Adjust the expiration time on our SSL session certificates to
8921 better match SSL certs seen in the wild. Resolves ticket 4014.
8922 - Change the default required uptime for a relay to be accepted as
8923 a HSDir (hidden service directory) from 24 hours to 25 hours.
8924 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8925 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8926 authorities to abstain from voting on assignment of the HSDir
8927 consensus flag. Related to bug 2649.
8928 - Update to the September 6 2011 Maxmind GeoLite Country database.
8930 o Minor bugfixes (also part of 0.2.2.33):
8931 - Demote the 'replay detected' log message emitted when a hidden
8932 service receives the same Diffie-Hellman public key in two different
8933 INTRODUCE2 cells to info level. A normal Tor client can cause that
8934 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8935 fixes part of bug 2442.
8936 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8937 level. There is nothing that a hidden service's operator can do
8938 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8940 - Clarify a log message specifying the characters permitted in
8941 HiddenServiceAuthorizeClient client names. Previously, the log
8942 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8943 given the impression that every ASCII character between "+" and "_"
8944 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8946 o Build fixes (also part of 0.2.2.33):
8947 - Clean up some code issues that prevented Tor from building on older
8948 BSDs. Fixes bug 3894; reported by "grarpamp".
8949 - Search for a platform-specific version of "ar" when cross-compiling.
8950 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8953 - Fix a bug where the SocksPort option (for example) would get
8954 ignored and replaced by the default if a SocksListenAddress
8955 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
8959 - Relays now try regenerating and uploading their descriptor more
8960 frequently if they are not listed in the consensus, or if the
8961 version of their descriptor listed in the consensus is too
8962 old. This fix should prevent situations where a server declines
8963 to re-publish itself because it has done so too recently, even
8964 though the authorities decided not to list its recent-enough
8965 descriptor. Fix for bug 3327.
8968 - Relays now include a reason for regenerating their descriptors
8969 in an HTTP header when uploading to the authorities. This will
8970 make it easier to debug descriptor-upload issues in the future.
8971 - When starting as root and then changing our UID via the User
8972 control option, and we have a ControlSocket configured, make sure
8973 that the ControlSocket is owned by the same account that Tor will
8974 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8977 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
8978 utility function used in the control-port code). This shouldn't
8979 ever happen unless Tor is completely out of memory, but if it did
8980 happen and Tor somehow recovered from it, Tor could have sent a log
8981 message to a control port in the middle of a reply to a controller
8982 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8983 - Make 'FetchUselessDescriptors' cause all descriptor types and
8984 all consensus types (including microdescriptors) to get fetched.
8985 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
8988 - Make a new "entry connection" struct as an internal subtype of "edge
8989 connection", to simplify the code and make exit connections smaller.
8992 Changes in version 0.2.2.33 - 2011-09-13
8993 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8994 TLS handshake that makes relays and bridges that run this new version
8995 reachable from Iran again.
8998 - Avoid an assertion failure when reloading a configuration with
8999 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9000 3923; bugfix on 0.2.2.25-alpha.
9002 o Minor features (security):
9003 - Check for replays of the public-key encrypted portion of an
9004 INTRODUCE1 cell, in addition to the current check for replays of
9005 the g^x value. This prevents a possible class of active attacks
9006 by an attacker who controls both an introduction point and a
9007 rendezvous point, and who uses the malleability of AES-CTR to
9008 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9009 that these attacks are infeasible (requiring the attacker to send
9010 on the order of zettabytes of altered cells in a short interval),
9011 but we'd rather block them off in case there are any classes of
9012 this attack that we missed. Reported by Willem Pinckaers.
9015 - Adjust the expiration time on our SSL session certificates to
9016 better match SSL certs seen in the wild. Resolves ticket 4014.
9017 - Change the default required uptime for a relay to be accepted as
9018 a HSDir (hidden service directory) from 24 hours to 25 hours.
9019 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9020 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9021 authorities to abstain from voting on assignment of the HSDir
9022 consensus flag. Related to bug 2649.
9023 - Update to the September 6 2011 Maxmind GeoLite Country database.
9025 o Minor bugfixes (documentation and log messages):
9026 - Correct the man page to explain that HashedControlPassword and
9027 CookieAuthentication can both be set, in which case either method
9028 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9029 when we decided to allow these config options to both be set. Issue
9031 - Demote the 'replay detected' log message emitted when a hidden
9032 service receives the same Diffie-Hellman public key in two different
9033 INTRODUCE2 cells to info level. A normal Tor client can cause that
9034 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9035 fixes part of bug 2442.
9036 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9037 level. There is nothing that a hidden service's operator can do
9038 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9040 - Clarify a log message specifying the characters permitted in
9041 HiddenServiceAuthorizeClient client names. Previously, the log
9042 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9043 given the impression that every ASCII character between "+" and "_"
9044 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9047 - Provide a substitute implementation of lround() for MSVC, which
9048 apparently lacks it. Patch from Gisle Vanem.
9049 - Clean up some code issues that prevented Tor from building on older
9050 BSDs. Fixes bug 3894; reported by "grarpamp".
9051 - Search for a platform-specific version of "ar" when cross-compiling.
9052 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9055 Changes in version 0.2.3.3-alpha - 2011-09-01
9056 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
9057 security, and provides client-side support for the microdescriptor
9058 and optimistic data features introduced earlier in the 0.2.3.x
9059 series. It also includes numerous critical bugfixes in the (optional)
9060 bufferevent-based networking backend.
9062 o Major features (stream isolation):
9063 - You can now configure Tor so that streams from different
9064 applications are isolated on different circuits, to prevent an
9065 attacker who sees your streams as they leave an exit node from
9066 linking your sessions to one another. To do this, choose some way
9067 to distinguish the applications: have them connect to different
9068 SocksPorts, or have one of them use SOCKS4 while the other uses
9069 SOCKS5, or have them pass different authentication strings to the
9070 SOCKS proxy. Then, use the new SocksPort syntax to configure the
9071 degree of isolation you need. This implements Proposal 171.
9072 - There's a new syntax for specifying multiple client ports (such as
9073 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
9074 multiple *Port entries with full addr:port syntax on each.
9075 The old *ListenAddress format is still supported, but you can't
9076 mix it with the new *Port syntax.
9078 o Major features (other):
9079 - Enable microdescriptor fetching by default for clients. This allows
9080 clients to download a much smaller amount of directory information.
9081 To disable it (and go back to the old-style consensus and
9082 descriptors), set "UseMicrodescriptors 0" in your torrc file.
9083 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
9084 "PortForwarding" config option), now supports Windows.
9085 - When using an exit relay running 0.2.3.x, clients can now
9086 "optimistically" send data before the exit relay reports that
9087 the stream has opened. This saves a round trip when starting
9088 connections where the client speaks first (such as web browsing).
9089 This behavior is controlled by a consensus parameter (currently
9090 disabled). To turn it on or off manually, use the "OptimisticData"
9091 torrc option. Implements proposal 181; code by Ian Goldberg.
9093 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
9094 - When using IOCP on Windows, we need to enable Libevent windows
9096 - The IOCP backend now works even when the user has not specified
9097 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
9098 Fixes part of bug 3752.
9099 - Correctly record the bytes we've read and written when using
9100 bufferevents, so that we can include them in our bandwidth history
9101 and advertised bandwidth. Fixes bug 3803.
9102 - Apply rate-limiting only at the bottom of a chain of filtering
9103 bufferevents. This prevents us from filling up internal read
9104 buffers and violating rate-limits when filtering bufferevents
9105 are enabled. Fixes part of bug 3804.
9106 - Add high-watermarks to the output buffers for filtered
9107 bufferevents. This prevents us from filling up internal write
9108 buffers and wasting CPU cycles when filtering bufferevents are
9109 enabled. Fixes part of bug 3804.
9110 - Correctly notice when data has been written from a bufferevent
9111 without flushing it completely. Fixes bug 3805.
9112 - Fix a bug where server-side tunneled bufferevent-based directory
9113 streams would get closed prematurely. Fixes bug 3814.
9114 - Fix a use-after-free error with per-connection rate-limiting
9115 buckets. Fixes bug 3888.
9117 o Major bugfixes (also part of 0.2.2.31-rc):
9118 - If we're configured to write our ControlPorts to disk, only write
9119 them after switching UID and creating the data directory. This way,
9120 we don't fail when starting up with a nonexistent DataDirectory
9121 and a ControlPortWriteToFile setting based on that directory. Fixes
9122 bug 3747; bugfix on Tor 0.2.2.26-beta.
9125 - Added a new CONF_CHANGED event so that controllers can be notified
9126 of any configuration changes made by other controllers, or by the
9127 user. Implements ticket 1692.
9128 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
9129 leak when using bufferevents, and lets Libevent worry about how to
9130 best copy data out of a buffer.
9131 - Replace files in stats/ rather than appending to them. Now that we
9132 include statistics in extra-info descriptors, it makes no sense to
9133 keep old statistics forever. Implements ticket 2930.
9135 o Minor features (build compatibility):
9136 - Limited, experimental support for building with nmake and MSVC.
9137 - Provide a substitute implementation of lround() for MSVC, which
9138 apparently lacks it. Patch from Gisle Vanem.
9140 o Minor features (also part of 0.2.2.31-rc):
9141 - Update to the August 2 2011 Maxmind GeoLite Country database.
9143 o Minor bugfixes (on 0.2.3.x-alpha):
9144 - Fix a spurious warning when parsing SOCKS requests with
9145 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
9146 - Get rid of a harmless warning that could happen on relays running
9147 with bufferevents. The warning was caused by someone doing an http
9148 request to a relay's orport. Also don't warn for a few related
9149 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
9151 o Minor bugfixes (on 2.2.x and earlier):
9152 - Correct the man page to explain that HashedControlPassword and
9153 CookieAuthentication can both be set, in which case either method
9154 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9155 when we decided to allow these config options to both be set. Issue
9157 - The "--quiet" and "--hush" options now apply not only to Tor's
9158 behavior before logs are configured, but also to Tor's behavior in
9159 the absense of configured logs. Fixes bug 3550; bugfix on
9162 o Minor bugfixes (also part of 0.2.2.31-rc):
9163 - Write several files in text mode, on OSes that distinguish text
9164 mode from binary mode (namely, Windows). These files are:
9165 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9166 that collect those statistics; 'client_keys' and 'hostname' for
9167 hidden services that use authentication; and (in the tor-gencert
9168 utility) newly generated identity and signing keys. Previously,
9169 we wouldn't specify text mode or binary mode, leading to an
9170 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9171 the DirRecordUsageByCountry option which would have triggered
9172 the assertion failure was added), although this assertion failure
9173 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9174 - Selectively disable deprecation warnings on OS X because Lion
9175 started deprecating the shipped copy of openssl. Fixes bug 3643.
9176 - Remove an extra pair of quotation marks around the error
9177 message in control-port STATUS_GENERAL BUG events. Bugfix on
9178 0.1.2.6-alpha; fixes bug 3732.
9179 - When unable to format an address as a string, report its value
9180 as "???" rather than reusing the last formatted address. Bugfix
9183 o Code simplifications and refactoring:
9184 - Rewrite the listener-selection logic so that parsing which ports
9185 we want to listen on is now separate from binding to the ports
9189 - Building Tor with bufferevent support now requires Libevent
9190 2.0.13-stable or later. Previous versions of Libevent had bugs in
9191 SSL-related bufferevents and related issues that would make Tor
9192 work badly with bufferevents. Requiring 2.0.13-stable also allows
9193 Tor with bufferevents to take advantage of Libevent APIs
9194 introduced after 2.0.8-rc.
9197 Changes in version 0.2.2.32 - 2011-08-27
9198 The Tor 0.2.2 release series is dedicated to the memory of Andreas
9199 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9200 a founder of the PETS community, a leader in our field, a mentor,
9201 and a friend. He left us with these words: "I had the possibility
9202 to contribute to this world that is not as it should be. I hope I
9203 could help in some areas to make the world a better place, and that
9204 I could also encourage other people to be engaged in improving the
9205 world. Please, stay engaged. This world needs you, your love, your
9206 initiative -- now I cannot be part of that anymore."
9208 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
9209 ready. More than two years in the making, this release features improved
9210 client performance and hidden service reliability, better compatibility
9211 for Android, correct behavior for bridges that listen on more than
9212 one address, more extensible and flexible directory object handling,
9213 better reporting of network statistics, improved code security, and
9214 many many other features and bugfixes.
9217 Changes in version 0.2.2.31-rc - 2011-08-17
9218 Tor 0.2.2.31-rc is the second and hopefully final release candidate
9219 for the Tor 0.2.2.x series.
9222 - Remove an extra pair of quotation marks around the error
9223 message in control-port STATUS_GENERAL BUG events. Bugfix on
9224 0.1.2.6-alpha; fixes bug 3732.
9225 - If we're configured to write our ControlPorts to disk, only write
9226 them after switching UID and creating the data directory. This way,
9227 we don't fail when starting up with a nonexistent DataDirectory
9228 and a ControlPortWriteToFile setting based on that directory. Fixes
9229 bug 3747; bugfix on Tor 0.2.2.26-beta.
9232 - Update to the August 2 2011 Maxmind GeoLite Country database.
9235 - Allow GETINFO fingerprint to return a fingerprint even when
9236 we have not yet built a router descriptor. Fixes bug 3577;
9237 bugfix on 0.2.0.1-alpha.
9238 - Write several files in text mode, on OSes that distinguish text
9239 mode from binary mode (namely, Windows). These files are:
9240 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9241 that collect those statistics; 'client_keys' and 'hostname' for
9242 hidden services that use authentication; and (in the tor-gencert
9243 utility) newly generated identity and signing keys. Previously,
9244 we wouldn't specify text mode or binary mode, leading to an
9245 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9246 the DirRecordUsageByCountry option which would have triggered
9247 the assertion failure was added), although this assertion failure
9248 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9249 - Selectively disable deprecation warnings on OS X because Lion
9250 started deprecating the shipped copy of openssl. Fixes bug 3643.
9251 - When unable to format an address as a string, report its value
9252 as "???" rather than reusing the last formatted address. Bugfix
9256 Changes in version 0.2.3.2-alpha - 2011-07-18
9257 Tor 0.2.3.2-alpha introduces two new experimental features:
9258 microdescriptors and pluggable transports. It also continues cleaning
9259 up a variety of recently introduced features.
9262 - Clients can now use microdescriptors instead of regular descriptors
9263 to build circuits. Microdescriptors are authority-generated
9264 summaries of regular descriptors' contents, designed to change
9265 very rarely (see proposal 158 for details). This feature is
9266 designed to save bandwidth, especially for clients on slow internet
9267 connections. It's off by default for now, since nearly no caches
9268 support it, but it will be on-by-default for clients in a future
9269 version. You can use the UseMicrodescriptors option to turn it on.
9270 - Tor clients using bridges can now be configured to use a separate
9271 'transport' proxy for each bridge. This approach helps to resist
9272 censorship by allowing bridges to use protocol obfuscation
9273 plugins. It implements part of proposal 180. Implements ticket 2841.
9274 - While we're trying to bootstrap, record how many TLS connections
9275 fail in each state, and report which states saw the most failures
9276 in response to any bootstrap failures. This feature may speed up
9277 diagnosis of censorship events. Implements ticket 3116.
9279 o Major bugfixes (on 0.2.3.1-alpha):
9280 - When configuring a large set of nodes in EntryNodes (as with
9281 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
9282 random subset to be guards, and choose them in random
9283 order. Fixes bug 2798.
9284 - Tor could crash when remembering a consensus in a non-used consensus
9285 flavor without having a current consensus set. Fixes bug 3361.
9286 - Comparing an unknown address to a microdescriptor's shortened exit
9287 policy would always give a "rejected" result. Fixes bug 3599.
9288 - Using microdescriptors as a client no longer prevents Tor from
9289 uploading and downloading hidden service descriptors. Fixes
9293 - Allow nameservers with IPv6 address. Resolves bug 2574.
9294 - Accept attempts to include a password authenticator in the
9295 handshake, as supported by SOCKS5. This handles SOCKS clients that
9296 don't know how to omit a password when authenticating. Resolves
9298 - When configuring a large set of nodes in EntryNodes, and there are
9299 enough of them listed as Guard so that we don't need to consider
9300 the non-guard entries, prefer the ones listed with the Guard flag.
9301 - Check for and recover from inconsistency in the microdescriptor
9302 cache. This will make it harder for us to accidentally free a
9303 microdescriptor without removing it from the appropriate data
9304 structures. Fixes issue 3135; issue noted by "wanoskarnet".
9305 - Log SSL state transitions at log level DEBUG, log domain
9306 HANDSHAKE. This can be useful for debugging censorship events.
9307 Implements ticket 3264.
9308 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
9309 implements ticket 3439.
9311 o Minor bugfixes (on 0.2.3.1-alpha):
9312 - Do not free all general-purpose regular descriptors just
9313 because microdescriptor use is enabled. Fixes bug 3113.
9314 - Correctly link libevent_openssl when --enable-static-libevent
9315 is passed to configure. Fixes bug 3118.
9316 - Bridges should not complain during their heartbeat log messages that
9317 they are unlisted in the consensus: that's more or less the point
9318 of being a bridge. Fixes bug 3183.
9319 - Report a SIGNAL event to controllers when acting on a delayed
9320 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
9321 event to the controller if we acted on a SIGNAL NEWNYM command
9322 immediately, and otherwise not report a SIGNAL event for the
9323 command at all. Fixes bug 3349.
9324 - Fix a crash when handling the SIGNAL controller command or
9325 reporting ERR-level status events with bufferevents enabled. Found
9326 by Robert Ransom. Fixes bug 3367.
9327 - Always ship the tor-fw-helper manpage in our release tarballs.
9328 Fixes bug 3389. Reported by Stephen Walker.
9329 - Fix a class of double-mark-for-close bugs when bufferevents
9330 are enabled. Fixes bug 3403.
9331 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
9332 - Add SIGNAL to the list returned by the 'GETINFO events/names'
9333 control-port command. Fixes part of bug 3465.
9334 - Prevent using negative indices during unit test runs when read_all()
9335 fails. Spotted by coverity.
9336 - Fix a rare memory leak when checking the nodelist without it being
9337 present. Found by coverity.
9338 - Only try to download a microdescriptor-flavored consensus from
9339 a directory cache that provides them.
9341 o Minor bugfixes (on 0.2.2.x and earlier):
9342 - Assert that hidden-service-related operations are not performed
9343 using single-hop circuits. Previously, Tor would assert that
9344 client-side streams are not attached to single-hop circuits,
9345 but not that other sensitive operations on the client and service
9346 side are not performed using single-hop circuits. Fixes bug 3332;
9348 - Don't publish a new relay descriptor when we reload our onion key,
9349 unless the onion key has actually changed. Fixes bug 3263 and
9350 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
9351 - Allow GETINFO fingerprint to return a fingerprint even when
9352 we have not yet built a router descriptor. Fixes bug 3577;
9353 bugfix on 0.2.0.1-alpha.
9354 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
9355 on 0.2.2.4-alpha; fixes bug 3427.
9357 o Code simplification and refactoring:
9358 - Use tor_sscanf() in place of scanf() in more places through the
9359 code. This makes us a little more locale-independent, and
9360 should help shut up code-analysis tools that can't tell
9361 a safe sscanf string from a dangerous one.
9362 - Use tt_assert(), not tor_assert(), for checking for test failures.
9363 This makes the unit tests more able to go on in the event that
9365 - Split connection_about_to_close() into separate functions for each
9369 - On Windows, we now define the _WIN32_WINNT macros only if they
9370 are not already defined. This lets the person building Tor decide,
9371 if they want, to require a later version of Windows.
9374 Changes in version 0.2.2.30-rc - 2011-07-07
9375 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
9376 series. It fixes a few smaller bugs, but generally appears stable.
9377 Please test it and let us know whether it is!
9380 - Send a SUCCEEDED stream event to the controller when a reverse
9381 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9382 discovered by katmagic.
9383 - Always NUL-terminate the sun_path field of a sockaddr_un before
9384 passing it to the kernel. (Not a security issue: kernels are
9385 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9386 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9387 - Don't stack-allocate the list of supplementary GIDs when we're
9388 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9389 could take up to 256K, which is way too much stack. Found by
9390 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9391 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
9392 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
9393 fixes part of bug 3465.
9394 - Fix a memory leak when receiving a descriptor for a hidden
9395 service we didn't ask for. Found by Coverity; CID #30. Bugfix
9399 - Update to the July 1 2011 Maxmind GeoLite Country database.
9402 Changes in version 0.2.2.29-beta - 2011-06-20
9403 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
9404 have bridge lines in their torrc but don't want to use them; gets
9405 us closer to having the control socket feature working on Debian;
9406 and fixes a variety of smaller bugs.
9409 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
9410 When we changed the default behavior to "use bridges if any
9411 are listed in the torrc", we surprised users who had bridges
9412 in their torrc files but who didn't actually want to use them.
9413 Partial resolution for bug 3354.
9416 - Don't attach new streams to old rendezvous circuits after SIGNAL
9417 NEWNYM. Previously, we would keep using an existing rendezvous
9418 circuit if it remained open (i.e. if it were kept open by a
9419 long-lived stream, or if a new stream were attached to it before
9420 Tor could notice that it was old and no longer in use). Bugfix on
9421 0.1.1.15-rc; fixes bug 3375.
9424 - Fix a bug when using ControlSocketsGroupWritable with User. The
9425 directory's group would be checked against the current group, not
9426 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
9427 bugfix on 0.2.2.26-beta.
9428 - Make connection_printf_to_buf()'s behavior sane. Its callers
9429 expect it to emit a CRLF iff the format string ends with CRLF;
9430 it actually emitted a CRLF iff (a) the format string ended with
9431 CRLF or (b) the resulting string was over 1023 characters long or
9432 (c) the format string did not end with CRLF *and* the resulting
9433 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9434 fixes part of bug 3407.
9435 - Make send_control_event_impl()'s behavior sane. Its callers
9436 expect it to always emit a CRLF at the end of the string; it
9437 might have emitted extra control characters as well. Bugfix on
9438 0.1.1.9-alpha; fixes another part of bug 3407.
9439 - Make crypto_rand_int() check the value of its input correctly.
9440 Previously, it accepted values up to UINT_MAX, but could return a
9441 negative number if given a value above INT_MAX+1. Found by George
9442 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9443 - Avoid a segfault when reading a malformed circuit build state
9444 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
9446 - When asked about a DNS record type we don't support via a
9447 client DNSPort, reply with NOTIMPL rather than an empty
9448 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
9449 - Fix a rare memory leak during stats writing. Found by coverity.
9452 - Update to the June 1 2011 Maxmind GeoLite Country database.
9454 o Code simplifications and refactoring:
9455 - Remove some dead code as indicated by coverity.
9456 - Remove a few dead assignments during router parsing. Found by
9458 - Add some forgotten return value checks during unit tests. Found
9460 - Don't use 1-bit wide signed bit fields. Found by coverity.
9463 Changes in version 0.2.2.28-beta - 2011-06-04
9464 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
9465 fixed a big bug in whether relays stay in the consensus consistently,
9466 we moved closer to handling bridges and hidden services correctly,
9467 and we started the process of better handling the dreaded "my Vidalia
9468 died, and now my Tor demands a password when I try to reconnect to it"
9472 - Don't decide to make a new descriptor when receiving a HUP signal.
9473 This bug has caused a lot of 0.2.2.x relays to disappear from the
9474 consensus periodically. Fixes the most common case of triggering
9475 bug 1810; bugfix on 0.2.2.7-alpha.
9476 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
9477 - Don't try to build descriptors if "ORPort auto" is set and we
9478 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
9480 - Resolve a crash that occurred when setting BridgeRelay to 1 with
9481 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
9482 - Apply circuit timeouts to opened hidden-service-related circuits
9483 based on the correct start time. Previously, we would apply the
9484 circuit build timeout based on time since the circuit's creation;
9485 it was supposed to be applied based on time since the circuit
9486 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
9487 - Use the same circuit timeout for client-side introduction
9488 circuits as for other four-hop circuits, rather than the timeout
9489 for single-hop directory-fetch circuits; the shorter timeout may
9490 have been appropriate with the static circuit build timeout in
9491 0.2.1.x and earlier, but caused many hidden service access attempts
9492 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
9493 on 0.2.2.2-alpha; fixes another part of bug 1297.
9494 - In ticket 2511 we fixed a case where you could use an unconfigured
9495 bridge if you had configured it as a bridge the last time you ran
9496 Tor. Now fix another edge case: if you had configured it as a bridge
9497 but then switched to a different bridge via the controller, you
9498 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
9502 - Add an __OwningControllerProcess configuration option and a
9503 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
9504 that when it exits, Tor will shut down. Implements feature 3049.
9505 - If "UseBridges 1" is set and no bridges are configured, Tor will
9506 now refuse to build any circuits until some bridges are set.
9507 If "UseBridges auto" is set, Tor will use bridges if they are
9508 configured and we are not running as a server, but otherwise will
9509 make circuits as usual. The new default is "auto". Patch by anonym,
9510 so the Tails LiveCD can stop automatically revealing you as a Tor
9514 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9515 - Remove a trailing asterisk from "exit-policy/default" in the
9516 output of the control port command "GETINFO info/names". Bugfix
9518 - Use a wide type to hold sockets when built for 64-bit Windows builds.
9520 - Warn when the user configures two HiddenServiceDir lines that point
9521 to the same directory. Bugfix on 0.0.6 (the version introducing
9522 HiddenServiceDir); fixes bug 3289.
9523 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
9524 part of bug 2748; bugfix on 0.2.0.10-alpha.
9525 - Log malformed requests for rendezvous descriptors as protocol
9526 warnings, not warnings. Also, use a more informative log message
9527 in case someone sees it at log level warning without prior
9528 info-level messages. Fixes the other part of bug 2748; bugfix
9530 - Clear the table recording the time of the last request for each
9531 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
9532 Previously, we would clear our HS descriptor cache on SIGNAL
9533 NEWNYM, but if we had previously retrieved a descriptor (or tried
9534 to) from every directory responsible for it, we would refuse to
9535 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
9537 - Fix a log message that said "bits" while displaying a value in
9538 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
9540 - When checking for 1024-bit keys, check for 1024 bits, not 128
9541 bytes. This allows Tor to correctly discard keys of length 1017
9542 through 1023. Bugfix on 0.0.9pre5.
9545 - Relays now log the reason for publishing a new relay descriptor,
9546 so we have a better chance of hunting down instances of bug 1810.
9547 Resolves ticket 3252.
9548 - Revise most log messages that refer to nodes by nickname to
9549 instead use the "$key=nickname at address" format. This should be
9550 more useful, especially since nicknames are less and less likely
9551 to be unique. Resolves ticket 3045.
9552 - Log (at info level) when purging pieces of hidden-service-client
9553 state because of SIGNAL NEWNYM.
9556 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9557 anything since 0.2.1.16-rc.
9560 Changes in version 0.2.2.27-beta - 2011-05-18
9561 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
9562 release, and also adds a few more general bugfixes.
9565 - Fix a crash bug when changing bridges in a running Tor process.
9566 Fixes bug 3213; bugfix on 0.2.2.26-beta.
9567 - When the controller configures a new bridge, don't wait 10 to 60
9568 seconds before trying to fetch its descriptor. Bugfix on
9569 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
9572 - Require that onion keys have exponent 65537 in microdescriptors too.
9573 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
9574 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
9575 Changed the limit to 512 characters by removing base64 newlines.
9576 Fixes bug 2752. Fix by Michael Yakubovich.
9577 - When a client starts or stops using bridges, never use a circuit
9578 that was built before the configuration change. This behavior could
9579 put at risk a user who uses bridges to ensure that her traffic
9580 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
9584 Changes in version 0.2.2.26-beta - 2011-05-17
9585 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
9586 also introduces a new "socksport auto" approach that should make it
9587 easier to run multiple Tors on the same system, and does a lot of
9588 cleanup to get us closer to a release candidate.
9590 o Security/privacy fixes:
9591 - Replace all potentially sensitive memory comparison operations
9592 with versions whose runtime does not depend on the data being
9593 compared. This will help resist a class of attacks where an
9594 adversary can use variations in timing information to learn
9595 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9596 implementation by Robert Ransom based partially on code by DJB.)
9597 - When receiving a hidden service descriptor, check that it is for
9598 the hidden service we wanted. Previously, Tor would store any
9599 hidden service descriptors that a directory gave it, whether it
9600 wanted them or not. This wouldn't have let an attacker impersonate
9601 a hidden service, but it did let directories pre-seed a client
9602 with descriptors that it didn't want. Bugfix on 0.0.6.
9603 - On SIGHUP, do not clear out all TrackHostExits mappings, client
9604 DNS cache entries, and virtual address mappings: that's what
9605 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
9608 - The options SocksPort, ControlPort, and so on now all accept a
9609 value "auto" that opens a socket on an OS-selected port. A
9610 new ControlPortWriteToFile option tells Tor to write its
9611 actual control port or ports to a chosen file. If the option
9612 ControlPortFileGroupReadable is set, the file is created as
9613 group-readable. Now users can run two Tor clients on the same
9614 system without needing to manually mess with parameters. Resolves
9615 part of ticket 3076.
9616 - Set SO_REUSEADDR on all sockets, not just listeners. This should
9617 help busy exit nodes avoid running out of useable ports just
9618 because all the ports have been used in the near past. Resolves
9622 - New "GETINFO net/listeners/(type)" controller command to return
9623 a list of addresses and ports that are bound for listeners for a
9624 given connection type. This is useful when the user has configured
9625 "SocksPort auto" and the controller needs to know which port got
9626 chosen. Resolves another part of ticket 3076.
9627 - Add a new ControlSocketsGroupWritable configuration option: when
9628 it is turned on, ControlSockets are group-writeable by the default
9629 group of the current user. Patch by Jérémy Bobbio; implements
9631 - Tor now refuses to create a ControlSocket in a directory that is
9632 world-readable (or group-readable if ControlSocketsGroupWritable
9633 is 0). This is necessary because some operating systems do not
9634 enforce permissions on an AF_UNIX sockets. Permissions on the
9635 directory holding the socket, however, seems to work everywhere.
9636 - Rate-limit a warning about failures to download v2 networkstatus
9637 documents. Resolves part of bug 1352.
9638 - Backport code from 0.2.3.x that allows directory authorities to
9639 clean their microdescriptor caches. Needed to resolve bug 2230.
9640 - When an HTTPS proxy reports "403 Forbidden", we now explain
9641 what it means rather than calling it an unexpected status code.
9642 Closes bug 2503. Patch from Michael Yakubovich.
9643 - Update to the May 1 2011 Maxmind GeoLite Country database.
9646 - Authorities now clean their microdesc cache periodically and when
9647 reading from disk initially, not only when adding new descriptors.
9648 This prevents a bug where we could lose microdescriptors. Bugfix
9649 on 0.2.2.6-alpha. Fixes bug 2230.
9650 - Do not crash when our configuration file becomes unreadable, for
9651 example due to a permissions change, between when we start up
9652 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9654 - Avoid a bug that would keep us from replacing a microdescriptor
9655 cache on Windows. (We would try to replace the file while still
9656 holding it open. That's fine on Unix, but Windows doesn't let us
9657 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
9658 - Add missing explanations for the authority-related torrc options
9659 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
9660 man page. Resolves issue 2379.
9661 - As an authority, do not upload our own vote or signature set to
9662 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
9663 it would get flagged as a duplicate. Resolves bug 3026.
9664 - Accept hidden service descriptors if we think we might be a hidden
9665 service directory, regardless of what our consensus says. This
9666 helps robustness, since clients and hidden services can sometimes
9667 have a more up-to-date view of the network consensus than we do,
9668 and if they think that the directory authorities list us a HSDir,
9669 we might actually be one. Related to bug 2732; bugfix on
9671 - When a controller changes TrackHostExits, remove mappings for
9672 hosts that should no longer have their exits tracked. Bugfix on
9674 - When a controller changes VirtualAddrNetwork, remove any mappings
9675 for hosts that were automapped to the old network. Bugfix on
9677 - When a controller changes one of the AutomapHosts* options, remove
9678 any mappings for hosts that should no longer be automapped. Bugfix
9680 - Do not reset the bridge descriptor download status every time we
9681 re-parse our configuration or get a configuration change. Fixes
9682 bug 3019; bugfix on 0.2.0.3-alpha.
9684 o Minor bugfixes (code cleanup):
9685 - When loading the microdesc journal, remember its current size.
9686 In 0.2.2, this helps prevent the microdesc journal from growing
9687 without limit on authorities (who are the only ones to use it in
9688 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9689 Fix posted by "cypherpunks."
9690 - The microdesc journal is supposed to get rebuilt only if it is
9691 at least _half_ the length of the store, not _twice_ the length
9692 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9693 - Fix a potential null-pointer dereference while computing a
9694 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
9696 - Avoid a possible null-pointer dereference when rebuilding the mdesc
9697 cache without actually having any descriptors to cache. Bugfix on
9698 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
9699 - If we fail to compute the identity digest of a v3 legacy keypair,
9700 warn, and don't use a buffer-full of junk instead. Bugfix on
9701 0.2.1.1-alpha; fixes bug 3106.
9702 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9703 where if the function had ever in the future been used to check
9704 for the presence of a too-large number, it would have given an
9705 incorrect result. (Fortunately, we only used it for 16-bit
9706 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9707 - Require that introduction point keys and onion handshake keys
9708 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9712 - Caches no longer download and serve v2 networkstatus documents
9713 unless FetchV2Networkstatus flag is set: these documents haven't
9714 haven't been used by clients or relays since 0.2.0.x. Resolves
9718 Changes in version 0.2.3.1-alpha - 2011-05-05
9719 Tor 0.2.3.1-alpha adds some new experimental features, including support
9720 for an improved network IO backend, IOCP networking on Windows,
9721 microdescriptor caching, "fast-start" support for streams, and automatic
9722 home router configuration. There are also numerous internal improvements
9723 to try to make the code easier for developers to work with.
9725 This is the first alpha release in a new series, so expect there to be
9726 bugs. Users who would rather test out a more stable branch should
9727 stay with 0.2.2.x for now.
9730 - Tor can now optionally build with the "bufferevents" buffered IO
9731 backend provided by Libevent 2. To use this feature, make sure you
9732 have the latest possible version of Libevent, and pass the
9733 --enable-bufferevents flag to configure when building Tor from
9734 source. This feature will make our networking code more flexible,
9735 let us stack layers on each other, and let us use more efficient
9736 zero-copy transports where available.
9737 - As an experimental feature, Tor can use IOCP for networking on Windows.
9738 Once this code is tuned and optimized, it promises much better
9739 performance than the select-based backend we've used in the past. To
9740 try this feature, you must build Tor with Libevent 2, configure Tor
9741 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9742 your torrc. There are known bugs here: only try this if you can help
9743 debug it as it breaks.
9744 - The EntryNodes option can now include country codes like {de} or IP
9745 addresses or network masks. Previously we had disallowed these options
9746 because we didn't have an efficient way to keep the list up to
9747 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9748 - Exit nodes now accept and queue data on not-yet-connected streams.
9749 Previously, the client wasn't allowed to send data until the stream was
9750 connected, which slowed down all connections. This change will enable
9751 clients to perform a "fast-start" on streams and send data without
9752 having to wait for a confirmation that the stream has opened. (Patch
9753 from Ian Goldberg; implements the server side of Proposal 174.)
9754 - Tor now has initial support for automatic port mapping on the many
9755 home routers that support NAT-PMP or UPnP. (Not yet supported on
9756 Windows). To build the support code, you'll need to have libnatpnp
9757 library and/or the libminiupnpc library, and you'll need to enable the
9758 feature specifically by passing "--enable-upnp" and/or
9759 "--enable-natpnp" to configure. To turn it on, use the new
9760 PortForwarding option.
9761 - Caches now download, cache, and serve multiple "flavors" of the
9762 consensus, including a flavor that describes microdescriptors.
9763 - Caches now download, cache, and serve microdescriptors -- small
9764 summaries of router descriptors that are authenticated by all of the
9765 directory authorities. Once enough caches are running this code,
9766 clients will be able to save significant amounts of directory bandwidth
9767 by downloading microdescriptors instead of router descriptors.
9770 - Make logging resolution configurable with a new LogTimeGranularity
9771 option, and change the default from 1 millisecond to 1 second.
9772 Implements enhancement 1668.
9773 - We log which torrc file we're using on startup. Implements ticket
9775 - Ordinarily, Tor does not count traffic from private addresses (like
9776 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
9777 There is now a new option, CountPrivateBandwidth, to disable this
9778 behavior. Patch from Daniel Cagara.
9779 - New --enable-static-tor configure option for building Tor as
9780 statically as possible. Idea, general hackery and thoughts from
9781 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
9783 - If you set the NumCPUs option to 0, Tor will now try to detect how
9784 many CPUs you have. This is the new default behavior.
9785 - Turn on directory request statistics by default and include them in
9786 extra-info descriptors. Don't break if we have no GeoIP database.
9787 - Relays that set "ConnDirectionStatistics 1" write statistics on the
9788 bidirectional use of connections to disk every 24 hours.
9789 - Add a GeoIP file digest to the extra-info descriptor. Implements
9791 - The NodeFamily option -- which let you declare that you want to
9792 consider nodes to be part of a family whether they list themselves
9793 that way or not -- now allows IP address ranges and country codes.
9794 - Add a new 'Heartbeat' log message type to periodically log a message
9795 describing Tor's status at level Notice. This feature is meant for
9796 operators who log at notice, and want to make sure that their Tor
9797 server is still working. Implementation by George Kadianakis.
9799 o Minor bugfixes (on 0.2.2.25-alpha):
9800 - When loading the microdesc journal, remember its current size.
9801 In 0.2.2, this helps prevent the microdesc journal from growing
9802 without limit on authorities (who are the only ones to use it in
9803 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9804 Fix posted by "cypherpunks."
9805 - The microdesc journal is supposed to get rebuilt only if it is
9806 at least _half_ the length of the store, not _twice_ the length
9807 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9808 - If as an authority we fail to compute the identity digest of a v3
9809 legacy keypair, warn, and don't use a buffer-full of junk instead.
9810 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
9811 - Authorities now clean their microdesc cache periodically and when
9812 reading from disk initially, not only when adding new descriptors.
9813 This prevents a bug where we could lose microdescriptors. Bugfix
9816 o Minor features (controller):
9817 - Add a new SIGNAL event to the controller interface so that
9818 controllers can be notified when Tor handles a signal. Resolves
9819 issue 1955. Patch by John Brooks.
9820 - Add a new GETINFO option to get total bytes read and written. Patch
9821 from pipe, revised by atagar. Resolves ticket 2345.
9822 - Implement some GETINFO controller fields to provide information about
9823 the Tor process's pid, euid, username, and resource limits.
9826 - Our build system requires automake 1.6 or later to create the
9827 Makefile.in files. Previously, you could have used 1.4.
9828 This only affects developers and people building Tor from git;
9829 people who build Tor from the source distribution without changing
9830 the Makefile.am files should be fine.
9831 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
9832 so on. This is more robust against some of the failure modes
9833 associated with running the autotools pieces on their own.
9835 o Minor packaging issues:
9836 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
9837 already created. Patch from Andreas Stieger. Fixes bug 2573.
9839 o Code simplifications and refactoring:
9840 - A major revision to our internal node-selecting and listing logic.
9841 Tor already had at least two major ways to look at the question of
9842 "which Tor servers do we know about": a list of router descriptors,
9843 and a list of entries in the current consensus. With
9844 microdescriptors, we're adding a third. Having so many systems
9845 without an abstraction layer over them was hurting the codebase.
9846 Now, we have a new "node_t" abstraction that presents a consistent
9847 interface to a client's view of a Tor node, and holds (nearly) all
9848 of the mutable state formerly in routerinfo_t and routerstatus_t.
9849 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
9850 no longer link against Libevent: they never used it, but
9851 our library structure used to force them to link it.
9854 - Remove some old code to work around even older versions of Tor that
9855 used forked processes to handle DNS requests. Such versions of Tor
9856 are no longer in use as servers.
9858 o Documentation fixes:
9859 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
9860 - Add missing documentation for the authority-related torrc options
9861 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
9865 Changes in version 0.2.2.25-alpha - 2011-04-29
9866 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
9867 robust, routers no longer overreport their bandwidth, Win7 should crash
9868 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
9869 now prevents hidden service-related activity from being linkable. It
9870 provides more information to Vidalia so you can see if your bridge is
9871 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
9872 StrictNodes configuration options to make them more reliable, more
9873 understandable, and more regularly applied. If you use those options,
9874 please see the revised documentation for them in the manual page.
9877 - Relays were publishing grossly inflated bandwidth values because
9878 they were writing their state files wrong--now they write the
9879 correct value. Also, resume reading bandwidth history from the
9880 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
9881 - Improve hidden service robustness: When we find that we have
9882 extended a hidden service's introduction circuit to a relay not
9883 listed as an introduction point in the HS descriptor we currently
9884 have, retry with an introduction point from the current
9885 descriptor. Previously we would just give up. Fixes bugs 1024 and
9886 1930; bugfix on 0.2.0.10-alpha.
9887 - Clients now stop trying to use an exit node associated with a given
9888 destination by TrackHostExits if they fail to reach that exit node.
9889 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
9890 - Fix crash bug on platforms where gmtime and localtime can return
9891 NULL. Windows 7 users were running into this one. Fixes part of bug
9892 2077. Bugfix on all versions of Tor. Found by boboper.
9894 o Security and stability fixes:
9895 - Don't double-free a parsable, but invalid, microdescriptor, even if
9896 it is followed in the blob we're parsing by an unparsable
9897 microdescriptor. Fixes an issue reported in a comment on bug 2954.
9898 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
9899 - If the Nickname configuration option isn't given, Tor would pick a
9900 nickname based on the local hostname as the nickname for a relay.
9901 Because nicknames are not very important in today's Tor and the
9902 "Unnamed" nickname has been implemented, this is now problematic
9903 behavior: It leaks information about the hostname without being
9904 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9905 introduced the Unnamed nickname. Reported by tagnaq.
9906 - Fix an uncommon assertion failure when running with DNSPort under
9907 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9908 - Avoid linkability based on cached hidden service descriptors: forget
9909 all hidden service descriptors cached as a client when processing a
9910 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9913 - Export GeoIP information on bridge usage to controllers even if we
9914 have not yet been running for 24 hours. Now Vidalia bridge operators
9915 can get more accurate and immediate feedback about their
9916 contributions to the network.
9918 o Major features and bugfixes (node selection):
9919 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9920 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
9921 options. Previously, we had been ambiguous in describing what
9922 counted as an "exit" node, and what operations exactly "StrictNodes
9923 0" would permit. This created confusion when people saw nodes built
9924 through unexpected circuits, and made it hard to tell real bugs from
9925 surprises. Now the intended behavior is:
9926 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9927 a node that delivers user traffic outside the Tor network.
9928 . "Entry", in the context of EntryNodes, means a node used as the
9929 first hop of a multihop circuit. It doesn't include direct
9930 connections to directory servers.
9931 . "ExcludeNodes" applies to all nodes.
9932 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9933 StrictNodes is set, Tor should avoid all nodes listed in
9934 ExcludeNodes, even when it will make user requests fail. When
9935 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9936 whenever it can, except when it must use an excluded node to
9937 perform self-tests, connect to a hidden service, provide a
9938 hidden service, fulfill a .exit request, upload directory
9939 information, or fetch directory information.
9940 Collectively, the changes to implement the behavior fix bug 1090.
9941 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9942 a node is listed in both, it's treated as excluded.
9943 - ExcludeNodes now applies to directory nodes -- as a preference if
9944 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9945 Don't exclude all the directory authorities and set StrictNodes to 1
9946 unless you really want your Tor to break.
9947 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9948 - ExcludeExitNodes now overrides .exit requests.
9949 - We don't use bridges listed in ExcludeNodes.
9950 - When StrictNodes is 1:
9951 . We now apply ExcludeNodes to hidden service introduction points
9952 and to rendezvous points selected by hidden service users. This
9953 can make your hidden service less reliable: use it with caution!
9954 . If we have used ExcludeNodes on ourself, do not try relay
9955 reachability self-tests.
9956 . If we have excluded all the directory authorities, we will not
9957 even try to upload our descriptor if we're a relay.
9958 . Do not honor .exit requests to an excluded node.
9959 - Remove a misfeature that caused us to ignore the Fast/Stable flags
9960 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
9961 - When the set of permitted nodes changes, we now remove any mappings
9962 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9964 - We never cannibalize a circuit that had excluded nodes on it, even
9965 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9966 - Revert a change where we would be laxer about attaching streams to
9967 circuits than when building the circuits. This was meant to prevent
9968 a set of bugs where streams were never attachable, but our improved
9969 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
9970 - Keep track of how many times we launch a new circuit to handle a
9971 given stream. Too many launches could indicate an inconsistency
9972 between our "launch a circuit to handle this stream" logic and our
9973 "attach this stream to one of the available circuits" logic.
9974 - Improve log messages related to excluded nodes.
9977 - Fix a spurious warning when moving from a short month to a long
9978 month on relays with month-based BandwidthAccounting. Bugfix on
9979 0.2.2.17-alpha; fixes bug 3020.
9980 - When a client finds that an origin circuit has run out of 16-bit
9981 stream IDs, we now mark it as unusable for new streams. Previously,
9982 we would try to close the entire circuit. Bugfix on 0.0.6.
9983 - Add a forgotten cast that caused a compile warning on OS X 10.6.
9984 Bugfix on 0.2.2.24-alpha.
9985 - Be more careful about reporting the correct error from a failed
9986 connect() system call. Under some circumstances, it was possible to
9987 look at an incorrect value for errno when sending the end reason.
9988 Bugfix on 0.1.0.1-rc.
9989 - Correctly handle an "impossible" overflow cases in connection byte
9990 counting, where we write or read more than 4GB on an edge connection
9991 in a single second. Bugfix on 0.1.2.8-beta.
9992 - Correct the warning displayed when a rendezvous descriptor exceeds
9993 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9995 - Clients and hidden services now use HSDir-flagged relays for hidden
9996 service descriptor downloads and uploads even if the relays have no
9997 DirPort set and the client has disabled TunnelDirConns. This will
9998 eventually allow us to give the HSDir flag to relays with no
9999 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
10000 - Downgrade "no current certificates known for authority" message from
10001 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
10002 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
10003 2917. Bugfix on 0.1.1.1-alpha.
10004 - Only limit the lengths of single HS descriptors, even when multiple
10005 HS descriptors are published to an HSDir relay in a single POST
10006 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
10007 - Write the current time into the LastWritten line in our state file,
10008 rather than the time from the previous write attempt. Also, stop
10009 trying to use a time of -1 in our log statements. Fixes bug 3039;
10010 bugfix on 0.2.2.14-alpha.
10011 - Be more consistent in our treatment of file system paths. "~" should
10012 get expanded to the user's home directory in the Log config option.
10013 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
10014 feature for the -f and --DataDirectory options.
10017 - Make sure every relay writes a state file at least every 12 hours.
10018 Previously, a relay could go for weeks without writing its state
10019 file, and on a crash could lose its bandwidth history, capacity
10020 estimates, client country statistics, and so on. Addresses bug 3012.
10021 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
10022 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
10023 clients are already deprecated because of security bugs.
10024 - Don't allow v0 hidden service authorities to act as clients.
10025 Required by fix for bug 3000.
10026 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
10027 by fix for bug 3000.
10028 - Ensure that no empty [dirreq-](read|write)-history lines are added
10029 to an extrainfo document. Implements ticket 2497.
10031 o Code simplification and refactoring:
10032 - Remove workaround code to handle directory responses from servers
10033 that had bug 539 (they would send HTTP status 503 responses _and_
10034 send a body too). Since only server versions before
10035 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
10036 keep the workaround in place.
10037 - Remove the old 'fuzzy time' logic. It was supposed to be used for
10038 handling calculations where we have a known amount of clock skew and
10039 an allowed amount of unknown skew. But we only used it in three
10040 places, and we never adjusted the known/unknown skew values. This is
10041 still something we might want to do someday, but if we do, we'll
10042 want to do it differently.
10043 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
10044 None of the cases where we did this before were wrong, but by making
10045 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
10046 - Use GetTempDir to find the proper temporary directory location on
10047 Windows when generating temporary files for the unit tests. Patch by
10051 Changes in version 0.2.2.24-alpha - 2011-04-08
10052 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
10053 prevented Tor clients from effectively using "multihomed" bridges,
10054 that is, bridges that listen on multiple ports or IP addresses so users
10055 can continue to use some of their addresses even if others get blocked.
10058 - Fix a bug where bridge users who configure the non-canonical
10059 address of a bridge automatically switch to its canonical
10060 address. If a bridge listens at more than one address, it should be
10061 able to advertise those addresses independently and any non-blocked
10062 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
10064 - If you configured Tor to use bridge A, and then quit and
10065 configured Tor to use bridge B instead, it would happily continue
10066 to use bridge A if it's still reachable. While this behavior is
10067 a feature if your goal is connectivity, in some scenarios it's a
10068 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
10069 - Directory authorities now use data collected from their own
10070 uptime observations when choosing whether to assign the HSDir flag
10071 to relays, instead of trusting the uptime value the relay reports in
10072 its descriptor. This change helps prevent an attack where a small
10073 set of nodes with frequently-changing identity keys can blackhole
10074 a hidden service. (Only authorities need upgrade; others will be
10075 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
10078 - When we restart our relay, we might get a successful connection
10079 from the outside before we've started our reachability tests,
10080 triggering a warning: "ORPort found reachable, but I have no
10081 routerinfo yet. Failing to inform controller of success." This
10082 bug was harmless unless Tor is running under a controller
10083 like Vidalia, in which case the controller would never get a
10084 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
10086 - Make directory authorities more accurate at recording when
10087 relays that have failed several reachability tests became
10088 unreachable, so we can provide more accuracy at assigning Stable,
10089 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
10090 - Fix an issue that prevented static linking of libevent on
10091 some platforms (notably Linux). Fixes bug 2698; bugfix on
10092 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
10093 the --with-static-libevent configure option).
10094 - We now ask the other side of a stream (the client or the exit)
10095 for more data on that stream when the amount of queued data on
10096 that stream dips low enough. Previously, we wouldn't ask the
10097 other side for more data until either it sent us more data (which
10098 it wasn't supposed to do if it had exhausted its window!) or we
10099 had completely flushed all our queued data. This flow control fix
10100 should improve throughput. Fixes bug 2756; bugfix on the earliest
10101 released versions of Tor (svn commit r152).
10102 - Avoid a double-mark-for-free warning when failing to attach a
10103 transparent proxy connection. (We thought we had fixed this in
10104 0.2.2.23-alpha, but it turns out our fix was checking the wrong
10105 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
10106 bug) and 0.2.2.23-alpha (the incorrect fix).
10107 - When warning about missing zlib development packages during compile,
10108 give the correct package names. Bugfix on 0.2.0.1-alpha.
10111 - Directory authorities now log the source of a rejected POSTed v3
10112 networkstatus vote.
10113 - Make compilation with clang possible when using
10114 --enable-gcc-warnings by removing two warning options that clang
10115 hasn't implemented yet and by fixing a few warnings. Implements
10117 - When expiring circuits, use microsecond timers rather than
10118 one-second timers. This can avoid an unpleasant situation where a
10119 circuit is launched near the end of one second and expired right
10120 near the beginning of the next, and prevent fluctuations in circuit
10122 - Use computed circuit-build timeouts to decide when to launch
10123 parallel introduction circuits for hidden services. (Previously,
10124 we would retry after 15 seconds.)
10125 - Update to the April 1 2011 Maxmind GeoLite Country database.
10128 - Create the /var/run/tor directory on startup on OpenSUSE if it is
10129 not already created. Patch from Andreas Stieger. Fixes bug 2573.
10131 o Documentation changes:
10132 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
10133 - Resolve all doxygen warnings except those for missing documentation.
10135 - Add doxygen documentation for more functions, fields, and types.
10138 Changes in version 0.2.2.23-alpha - 2011-03-08
10139 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
10140 they restart they don't lose their bandwidth capacity estimate. This
10141 release also fixes a diverse set of user-facing bugs, ranging from
10142 relays overrunning their rate limiting to clients falsely warning about
10143 clock skew to bridge descriptor leaks by our bridge directory authority.
10146 - Stop sending a CLOCK_SKEW controller status event whenever
10147 we fetch directory information from a relay that has a wrong clock.
10148 Instead, only inform the controller when it's a trusted authority
10149 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10150 the rest of bug 1074.
10151 - Fix an assert in parsing router descriptors containing IPv6
10152 addresses. This one took down the directory authorities when
10153 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
10154 - Make the bridge directory authority refuse to answer directory
10155 requests for "all" descriptors. It used to include bridge
10156 descriptors in its answer, which was a major information leak.
10157 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
10158 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10159 Tor would ignore their RelayBandwidthBurst setting,
10160 potentially using more bandwidth than expected. Bugfix on
10161 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10162 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10163 hidserv" in her torrc. The 'hidserv' argument never controlled
10164 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10167 - Relays now save observed peak bandwidth throughput rates to their
10168 state file (along with total usage, which was already saved)
10169 so that they can determine their correct estimated bandwidth on
10170 restart. Resolves bug 1863, where Tor relays would reset their
10171 estimated bandwidth to 0 after restarting.
10172 - Directory authorities now take changes in router IP address and
10173 ORPort into account when determining router stability. Previously,
10174 if a router changed its IP or ORPort, the authorities would not
10175 treat it as having any downtime for the purposes of stability
10176 calculation, whereas clients would experience downtime since the
10177 change could take a while to propagate to them. Resolves issue 1035.
10178 - Enable Address Space Layout Randomization (ASLR) and Data Execution
10179 Prevention (DEP) by default on Windows to make it harder for
10180 attackers to exploit vulnerabilities. Patch from John Brooks.
10182 o Minor bugfixes (on 0.2.1.x and earlier):
10183 - Fix a rare crash bug that could occur when a client was configured
10184 with a large number of bridges. Fixes bug 2629; bugfix on
10185 0.2.1.2-alpha. Bugfix by trac user "shitlei".
10186 - Avoid a double mark-for-free warning when failing to attach a
10187 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
10189 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
10190 found by "cypherpunks". This bug was introduced before the first
10191 Tor release, in svn commit r110.
10192 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
10193 don't mention them in the manpage. Fixes bug 2450; issue
10194 spotted by keb and G-Lo.
10195 - Fix a bug in bandwidth history state parsing that could have been
10196 triggered if a future version of Tor ever changed the timing
10197 granularity at which bandwidth history is measured. Bugfix on
10198 Tor 0.1.1.11-alpha.
10199 - When a relay decides that its DNS is too broken for it to serve
10200 as an exit server, it advertised itself as a non-exit, but
10201 continued to act as an exit. This could create accidental
10202 partitioning opportunities for users. Instead, if a relay is
10203 going to advertise reject *:* as its exit policy, it should
10204 really act with exit policy "reject *:*". Fixes bug 2366.
10205 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
10206 - In the special case where you configure a public exit relay as your
10207 bridge, Tor would be willing to use that exit relay as the last
10208 hop in your circuit as well. Now we fail that circuit instead.
10209 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
10210 - Fix a bug with our locking implementation on Windows that couldn't
10211 correctly detect when a file was already locked. Fixes bug 2504,
10212 bugfix on 0.2.1.6-alpha.
10213 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
10214 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
10216 - Set target port in get_interface_address6() correctly. Bugfix
10217 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
10218 - Directory authorities are now more robust to hops back in time
10219 when calculating router stability. Previously, if a run of uptime
10220 or downtime appeared to be negative, the calculation could give
10221 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
10223 - Fix an assert that got triggered when using the TestingTorNetwork
10224 configuration option and then issuing a GETINFO config-text control
10225 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
10227 o Minor bugfixes (on 0.2.2.x):
10228 - Clients should not weight BadExit nodes as Exits in their node
10229 selection. Similarly, directory authorities should not count BadExit
10230 bandwidth as Exit bandwidth when computing bandwidth-weights.
10231 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
10232 - Correctly clear our dir_read/dir_write history when there is an
10233 error parsing any bw history value from the state file. Bugfix on
10234 Tor 0.2.2.15-alpha.
10235 - Resolve a bug in verifying signatures of directory objects
10236 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
10237 Fixes bug 2409. Found by "piebeer".
10238 - Bridge authorities no longer crash on SIGHUP when they try to
10239 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
10243 - Log less aggressively about circuit timeout changes, and improve
10244 some other circuit timeout messages. Resolves bug 2004.
10245 - Log a little more clearly about the times at which we're no longer
10246 accepting new connections. Resolves bug 2181.
10247 - Reject attempts at the client side to open connections to private
10248 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
10249 a randomly chosen exit node. Attempts to do so are always
10250 ill-defined, generally prevented by exit policies, and usually
10251 in error. This will also help to detect loops in transparent
10252 proxy configurations. You can disable this feature by setting
10253 "ClientRejectInternalAddresses 0" in your torrc.
10254 - Always treat failure to allocate an RSA key as an unrecoverable
10256 - Update to the March 1 2011 Maxmind GeoLite Country database.
10258 o Minor features (log subsystem):
10259 - Add documentation for configuring logging at different severities in
10260 different log domains. We've had this feature since 0.2.1.1-alpha,
10261 but for some reason it never made it into the manpage. Fixes
10263 - Make it simpler to specify "All log domains except for A and B".
10264 Previously you needed to say "[*,~A,~B]". Now you can just say
10266 - Add a "LogMessageDomains 1" option to include the domains of log
10267 messages along with the messages. Without this, there's no way
10268 to use log domains without reading the source or doing a lot
10271 o Packaging changes:
10272 - Stop shipping the Tor specs files and development proposal documents
10273 in the tarball. They are now in a separate git repository at
10274 git://git.torproject.org/torspec.git
10277 Changes in version 0.2.1.30 - 2011-02-23
10278 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
10279 change is a slight tweak to Tor's TLS handshake that makes relays
10280 and bridges that run this new version reachable from Iran again.
10281 We don't expect this tweak will win the arms race long-term, but it
10282 buys us time until we roll out a better solution.
10285 - Stop sending a CLOCK_SKEW controller status event whenever
10286 we fetch directory information from a relay that has a wrong clock.
10287 Instead, only inform the controller when it's a trusted authority
10288 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10289 the rest of bug 1074.
10290 - Fix a bounds-checking error that could allow an attacker to
10291 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10292 Found by "piebeer".
10293 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10294 Tor would ignore their RelayBandwidthBurst setting,
10295 potentially using more bandwidth than expected. Bugfix on
10296 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10297 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10298 hidserv" in her torrc. The 'hidserv' argument never controlled
10299 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10302 - Adjust our TLS Diffie-Hellman parameters to match those used by
10304 - Update to the February 1 2011 Maxmind GeoLite Country database.
10307 - Check for and reject overly long directory certificates and
10308 directory tokens before they have a chance to hit any assertions.
10309 Bugfix on 0.2.1.28. Found by "doorss".
10310 - Bring the logic that gathers routerinfos and assesses the
10311 acceptability of circuits into line. This prevents a Tor OP from
10312 getting locked in a cycle of choosing its local OR as an exit for a
10313 path (due to a .exit request) and then rejecting the circuit because
10314 its OR is not listed yet. It also prevents Tor clients from using an
10315 OR running in the same instance as an exit (due to a .exit request)
10316 if the OR does not meet the same requirements expected of an OR
10317 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10319 o Packaging changes:
10320 - Stop shipping the Tor specs files and development proposal documents
10321 in the tarball. They are now in a separate git repository at
10322 git://git.torproject.org/torspec.git
10323 - Do not include Git version tags as though they are SVN tags when
10324 generating a tarball from inside a repository that has switched
10325 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
10328 Changes in version 0.2.2.22-alpha - 2011-01-25
10329 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
10330 main other change is a slight tweak to Tor's TLS handshake that makes
10331 relays and bridges that run this new version reachable from Iran again.
10332 We don't expect this tweak will win the arms race long-term, but it
10333 will buy us a bit more time until we roll out a better solution.
10336 - Fix a bounds-checking error that could allow an attacker to
10337 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10338 Found by "piebeer".
10339 - Don't assert when changing from bridge to relay or vice versa
10340 via the controller. The assert happened because we didn't properly
10341 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
10342 bug 2433. Reported by bastik.
10345 - Adjust our TLS Diffie-Hellman parameters to match those used by
10347 - Provide a log message stating which geoip file we're parsing
10348 instead of just stating that we're parsing the geoip file.
10349 Implements ticket 2432.
10352 - Check for and reject overly long directory certificates and
10353 directory tokens before they have a chance to hit any assertions.
10354 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
10357 Changes in version 0.2.2.21-alpha - 2011-01-15
10358 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
10359 continues our recent code security audit work. The main fix resolves
10360 a remote heap overflow vulnerability that can allow remote code
10361 execution (CVE-2011-0427). Other fixes address a variety of assert
10362 and crash bugs, most of which we think are hard to exploit remotely.
10364 o Major bugfixes (security), also included in 0.2.1.29:
10365 - Fix a heap overflow bug where an adversary could cause heap
10366 corruption. This bug probably allows remote code execution
10367 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10369 - Prevent a denial-of-service attack by disallowing any
10370 zlib-compressed data whose compression factor is implausibly
10371 high. Fixes part of bug 2324; reported by "doorss".
10372 - Zero out a few more keys in memory before freeing them. Fixes
10373 bug 2384 and part of bug 2385. These key instances found by
10374 "cypherpunks", based on Andrew Case's report about being able
10375 to find sensitive data in Tor's memory space if you have enough
10376 permissions. Bugfix on 0.0.2pre9.
10378 o Major bugfixes (crashes), also included in 0.2.1.29:
10379 - Prevent calls to Libevent from inside Libevent log handlers.
10380 This had potential to cause a nasty set of crashes, especially
10381 if running Libevent with debug logging enabled, and running
10382 Tor with a controller watching for low-severity log messages.
10383 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10384 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10385 underflow errors there too. Fixes the other part of bug 2324.
10386 - Fix a bug where we would assert if we ever had a
10387 cached-descriptors.new file (or another file read directly into
10388 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10389 on 0.2.1.25. Found by doorss.
10390 - Fix some potential asserts and parsing issues with grossly
10391 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10394 o Minor bugfixes (other), also included in 0.2.1.29:
10395 - Fix a bug with handling misformed replies to reverse DNS lookup
10396 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10397 bug reported by doorss.
10398 - Fix compilation on mingw when a pthreads compatibility library
10399 has been installed. (We don't want to use it, so we shouldn't
10400 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10401 - Fix a bug where we would declare that we had run out of virtual
10402 addresses when the address space was only half-exhausted. Bugfix
10404 - Correctly handle the case where AutomapHostsOnResolve is set but
10405 no virtual addresses are available. Fixes bug 2328; bugfix on
10406 0.1.2.1-alpha. Bug found by doorss.
10407 - Correctly handle wrapping around when we run out of virtual
10408 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
10410 o Minor features, also included in 0.2.1.29:
10411 - Update to the January 1 2011 Maxmind GeoLite Country database.
10412 - Introduce output size checks on all of our decryption functions.
10414 o Build changes, also included in 0.2.1.29:
10415 - Tor does not build packages correctly with Automake 1.6 and earlier;
10416 added a check to Makefile.am to make sure that we're building with
10417 Automake 1.7 or later.
10418 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10419 because we built it with a too-old version of automake. Thus that
10420 release broke ./configure --enable-openbsd-malloc, which is popular
10421 among really fast exit relays on Linux.
10423 o Major bugfixes, new in 0.2.2.21-alpha:
10424 - Prevent crash/heap corruption when the cbtnummodes consensus
10425 parameter is set to 0 or large values. Fixes bug 2317; bugfix
10428 o Major features, new in 0.2.2.21-alpha:
10429 - Introduce minimum/maximum values that clients will believe
10430 from the consensus. Now we'll have a better chance to avoid crashes
10431 or worse when a consensus param has a weird value.
10433 o Minor features, new in 0.2.2.21-alpha:
10434 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
10435 used on bridges, and it makes bridge scanning somewhat easier.
10436 - If writing the state file to disk fails, wait up to an hour before
10437 retrying again, rather than trying again each second. Fixes bug
10438 2346; bugfix on Tor 0.1.1.3-alpha.
10439 - Make Libevent log messages get delivered to controllers later,
10440 and not from inside the Libevent log handler. This prevents unsafe
10441 reentrant Libevent calls while still letting the log messages
10443 - Detect platforms that brokenly use a signed size_t, and refuse to
10444 build there. Found and analyzed by doorss and rransom.
10445 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
10448 o Minor bugfixes, new in 0.2.2.21-alpha:
10449 - Handle SOCKS messages longer than 128 bytes long correctly, rather
10450 than waiting forever for them to finish. Fixes bug 2330; bugfix
10451 on 0.2.0.16-alpha. Found by doorss.
10452 - Add assertions to check for overflow in arguments to
10453 base32_encode() and base32_decode(); fix a signed-unsigned
10454 comparison there too. These bugs are not actually reachable in Tor,
10455 but it's good to prevent future errors too. Found by doorss.
10456 - Correctly detect failures to create DNS requests when using Libevent
10457 versions before v2. (Before Libevent 2, we used our own evdns
10458 implementation. Its return values for Libevent's evdns_resolve_*()
10459 functions are not consistent with those from Libevent.) Fixes bug
10460 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
10462 o Documentation, new in 0.2.2.21-alpha:
10463 - Document the default socks host and port (127.0.0.1:9050) for
10467 Changes in version 0.2.1.29 - 2011-01-15
10468 Tor 0.2.1.29 continues our recent code security audit work. The main
10469 fix resolves a remote heap overflow vulnerability that can allow remote
10470 code execution. Other fixes address a variety of assert and crash bugs,
10471 most of which we think are hard to exploit remotely.
10473 o Major bugfixes (security):
10474 - Fix a heap overflow bug where an adversary could cause heap
10475 corruption. This bug probably allows remote code execution
10476 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10478 - Prevent a denial-of-service attack by disallowing any
10479 zlib-compressed data whose compression factor is implausibly
10480 high. Fixes part of bug 2324; reported by "doorss".
10481 - Zero out a few more keys in memory before freeing them. Fixes
10482 bug 2384 and part of bug 2385. These key instances found by
10483 "cypherpunks", based on Andrew Case's report about being able
10484 to find sensitive data in Tor's memory space if you have enough
10485 permissions. Bugfix on 0.0.2pre9.
10487 o Major bugfixes (crashes):
10488 - Prevent calls to Libevent from inside Libevent log handlers.
10489 This had potential to cause a nasty set of crashes, especially
10490 if running Libevent with debug logging enabled, and running
10491 Tor with a controller watching for low-severity log messages.
10492 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10493 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10494 underflow errors there too. Fixes the other part of bug 2324.
10495 - Fix a bug where we would assert if we ever had a
10496 cached-descriptors.new file (or another file read directly into
10497 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10498 on 0.2.1.25. Found by doorss.
10499 - Fix some potential asserts and parsing issues with grossly
10500 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10503 o Minor bugfixes (other):
10504 - Fix a bug with handling misformed replies to reverse DNS lookup
10505 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10506 bug reported by doorss.
10507 - Fix compilation on mingw when a pthreads compatibility library
10508 has been installed. (We don't want to use it, so we shouldn't
10509 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10510 - Fix a bug where we would declare that we had run out of virtual
10511 addresses when the address space was only half-exhausted. Bugfix
10513 - Correctly handle the case where AutomapHostsOnResolve is set but
10514 no virtual addresses are available. Fixes bug 2328; bugfix on
10515 0.1.2.1-alpha. Bug found by doorss.
10516 - Correctly handle wrapping around to when we run out of virtual
10517 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
10518 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10519 because we built it with a too-old version of automake. Thus that
10520 release broke ./configure --enable-openbsd-malloc, which is popular
10521 among really fast exit relays on Linux.
10524 - Update to the January 1 2011 Maxmind GeoLite Country database.
10525 - Introduce output size checks on all of our decryption functions.
10528 - Tor does not build packages correctly with Automake 1.6 and earlier;
10529 added a check to Makefile.am to make sure that we're building with
10530 Automake 1.7 or later.
10533 Changes in version 0.2.2.20-alpha - 2010-12-17
10534 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
10535 exploitable bugs. We also fix a variety of other significant bugs,
10536 change the IP address for one of our directory authorities, and update
10537 the minimum version that Tor relays must run to join the network.
10540 - Fix a remotely exploitable bug that could be used to crash instances
10541 of Tor remotely by overflowing on the heap. Remote-code execution
10542 hasn't been confirmed, but can't be ruled out. Everyone should
10543 upgrade. Bugfix on the 0.1.1 series and later.
10544 - Fix a bug that could break accounting on 64-bit systems with large
10545 time_t values, making them hibernate for impossibly long intervals.
10546 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
10547 - Fix a logic error in directory_fetches_from_authorities() that
10548 would cause all _non_-exits refusing single-hop-like circuits
10549 to fetch from authorities, when we wanted to have _exits_ fetch
10550 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
10552 - Fix a stream fairness bug that would cause newer streams on a given
10553 circuit to get preference when reading bytes from the origin or
10554 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
10555 introduced before the first Tor release, in svn revision r152.
10557 o Directory authority changes:
10558 - Change IP address and ports for gabelmoo (v3 directory authority).
10561 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
10562 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
10563 - Fix an off-by-one error in calculating some controller command
10564 argument lengths. Fortunately, this mistake is harmless since
10565 the controller code does redundant NUL termination too. Found by
10566 boboper. Bugfix on 0.1.1.1-alpha.
10567 - Do not dereference NULL if a bridge fails to build its
10568 extra-info descriptor. Found by an anonymous commenter on
10569 Trac. Bugfix on 0.2.2.19-alpha.
10572 - Update to the December 1 2010 Maxmind GeoLite Country database.
10573 - Directory authorities now reject relays running any versions of
10574 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
10575 known bugs that keep RELAY_EARLY cells from working on rendezvous
10576 circuits. Followup to fix for bug 2081.
10577 - Directory authorities now reject relays running any version of Tor
10578 older than 0.2.0.26-rc. That version is the earliest that fetches
10579 current directory information correctly. Fixes bug 2156.
10580 - Report only the top 10 ports in exit-port stats in order not to
10581 exceed the maximum extra-info descriptor length of 50 KB. Implements
10585 Changes in version 0.2.1.28 - 2010-12-17
10586 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
10587 exploitable bugs. We also took this opportunity to change the IP address
10588 for one of our directory authorities, and to update the geoip database
10592 - Fix a remotely exploitable bug that could be used to crash instances
10593 of Tor remotely by overflowing on the heap. Remote-code execution
10594 hasn't been confirmed, but can't be ruled out. Everyone should
10595 upgrade. Bugfix on the 0.1.1 series and later.
10597 o Directory authority changes:
10598 - Change IP address and ports for gabelmoo (v3 directory authority).
10601 - Update to the December 1 2010 Maxmind GeoLite Country database.
10604 Changes in version 0.2.1.27 - 2010-11-23
10605 Yet another OpenSSL security patch broke its compatibility with Tor:
10606 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
10607 also took this opportunity to fix several crash bugs, integrate a new
10608 directory authority, and update the bundled GeoIP database.
10611 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10612 No longer set the tlsext_host_name extension on server SSL objects;
10613 but continue to set it on client SSL objects. Our goal in setting
10614 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10615 bugfix on 0.2.1.1-alpha.
10616 - Do not log messages to the controller while shrinking buffer
10617 freelists. Doing so would sometimes make the controller connection
10618 try to allocate a buffer chunk, which would mess up the internals
10619 of the freelist and cause an assertion failure. Fixes bug 1125;
10620 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10621 - Learn our external IP address when we're a relay or bridge, even if
10622 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10623 where we introduced bridge relays that don't need to publish to
10624 be useful. Fixes bug 2050.
10625 - Do even more to reject (and not just ignore) annotations on
10626 router descriptors received anywhere but from the cache. Previously
10627 we would ignore such annotations at first, but cache them to disk
10628 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10629 - When you're using bridges and your network goes away and your
10630 bridges get marked as down, recover when you attempt a new socks
10631 connection (if the network is back), rather than waiting up to an
10632 hour to try fetching new descriptors for your bridges. Bugfix on
10633 0.2.0.3-alpha; fixes bug 1981.
10636 - Move to the November 2010 Maxmind GeoLite country db (rather
10637 than the June 2009 ip-to-country GeoIP db) for our statistics that
10638 count how many users relays are seeing from each country. Now we'll
10639 have more accurate data, especially for many African countries.
10641 o New directory authorities:
10642 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10646 - Fix an assertion failure that could occur in directory caches or
10647 bridge users when using a very short voting interval on a testing
10648 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
10650 - Enforce multiplicity rules when parsing annotations. Bugfix on
10651 0.2.0.8-alpha. Found by piebeer.
10652 - Allow handshaking OR connections to take a full KeepalivePeriod
10653 seconds to handshake. Previously, we would close them after
10654 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10655 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10657 - When building with --enable-gcc-warnings on OpenBSD, disable
10658 warnings in system headers. This makes --enable-gcc-warnings
10659 pass on OpenBSD 4.8.
10662 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10663 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10664 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10665 Servers can start sending this code when enough clients recognize
10666 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
10667 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10668 Patch from mingw-san.
10671 - Remove the old debian/ directory from the main Tor distribution.
10672 The official Tor-for-debian git repository lives at the URL
10673 https://git.torproject.org/debian/tor.git
10674 - Stop shipping the old doc/website/ directory in the tarball. We
10675 changed the website format in late 2010, and what we shipped in
10676 0.2.1.26 really wasn't that useful anyway.
10679 Changes in version 0.2.2.19-alpha - 2010-11-22
10680 Yet another OpenSSL security patch broke its compatibility with Tor:
10681 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
10684 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10685 No longer set the tlsext_host_name extension on server SSL objects;
10686 but continue to set it on client SSL objects. Our goal in setting
10687 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10688 bugfix on 0.2.1.1-alpha.
10691 - Try harder not to exceed the maximum length of 50 KB when writing
10692 statistics to extra-info descriptors. This bug was triggered by very
10693 fast relays reporting exit-port, entry, and dirreq statistics.
10694 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
10695 - Publish a router descriptor even if generating an extra-info
10696 descriptor fails. Previously we would not publish a router
10697 descriptor without an extra-info descriptor; this can cause fast
10698 exit relays collecting exit-port statistics to drop from the
10699 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10702 Changes in version 0.2.2.18-alpha - 2010-11-16
10703 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
10704 us lately, makes unpublished bridge relays able to detect their IP
10705 address, and fixes a wide variety of other bugs to get us much closer
10706 to a stable release.
10709 - Do even more to reject (and not just ignore) annotations on
10710 router descriptors received anywhere but from the cache. Previously
10711 we would ignore such annotations at first, but cache them to disk
10712 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10713 - Do not log messages to the controller while shrinking buffer
10714 freelists. Doing so would sometimes make the controller connection
10715 try to allocate a buffer chunk, which would mess up the internals
10716 of the freelist and cause an assertion failure. Fixes bug 1125;
10717 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10718 - Learn our external IP address when we're a relay or bridge, even if
10719 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10720 where we introduced bridge relays that don't need to publish to
10721 be useful. Fixes bug 2050.
10722 - Maintain separate TLS contexts and certificates for incoming and
10723 outgoing connections in bridge relays. Previously we would use the
10724 same TLS contexts and certs for incoming and outgoing connections.
10725 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10726 - Maintain separate identity keys for incoming and outgoing TLS
10727 contexts in bridge relays. Previously we would use the same
10728 identity keys for incoming and outgoing TLS contexts. Bugfix on
10729 0.2.0.3-alpha; addresses the other half of bug 988.
10730 - Avoid an assertion failure when we as an authority receive a
10731 duplicate upload of a router descriptor that we already have,
10732 but which we previously considered an obsolete descriptor.
10733 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10734 - Avoid a crash bug triggered by looking at a dangling pointer while
10735 setting the network status consensus. Found by Robert Ransom.
10736 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10737 - Fix a logic error where servers that _didn't_ act as exits would
10738 try to keep their server lists more aggressively up to date than
10739 exits, when it was supposed to be the other way around. Bugfix
10742 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10743 - When we're trying to guess whether we know our IP address as
10744 a relay, we would log various ways that we failed to guess
10745 our address, but never log that we ended up guessing it
10746 successfully. Now add a log line to help confused and anxious
10747 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10748 - Bring the logic that gathers routerinfos and assesses the
10749 acceptability of circuits into line. This prevents a Tor OP from
10750 getting locked in a cycle of choosing its local OR as an exit for a
10751 path (due to a .exit request) and then rejecting the circuit because
10752 its OR is not listed yet. It also prevents Tor clients from using an
10753 OR running in the same instance as an exit (due to a .exit request)
10754 if the OR does not meet the same requirements expected of an OR
10755 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10756 - Correctly describe errors that occur when generating a TLS object.
10757 Previously we would attribute them to a failure while generating a
10758 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10760 - Enforce multiplicity rules when parsing annotations. Bugfix on
10761 0.2.0.8-alpha. Found by piebeer.
10762 - Fix warnings that newer versions of autoconf produced during
10763 ./autogen.sh. These warnings appear to be harmless in our case,
10764 but they were extremely verbose. Fixes bug 2020.
10766 o Minor bugfixes (on Tor 0.2.2.x):
10767 - Enable protection of small arrays whenever we build with gcc
10768 hardening features, not only when also building with warnings
10769 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
10772 - Make hidden services work better in private Tor networks by not
10773 requiring any uptime to join the hidden service descriptor
10774 DHT. Implements ticket 2088.
10775 - Rate-limit the "your application is giving Tor only an IP address"
10776 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
10777 - When AllowSingleHopExits is set, print a warning to explain to the
10778 relay operator why most clients are avoiding her relay.
10779 - Update to the November 1 2010 Maxmind GeoLite Country database.
10781 o Code simplifications and refactoring:
10782 - When we fixed bug 1038 we had to put in a restriction not to send
10783 RELAY_EARLY cells on rend circuits. This was necessary as long
10784 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
10785 active. Now remove this obsolete check. Resolves bug 2081.
10786 - Some options used different conventions for uppercasing of acronyms
10787 when comparing manpage and source. Fix those in favor of the
10788 manpage, as it makes sense to capitalize acronyms.
10789 - Remove the torrc.complete file. It hasn't been kept up to date
10790 and users will have better luck checking out the manpage.
10791 - Remove the obsolete "NoPublish" option; it has been flagged
10792 as obsolete and has produced a warning since 0.1.1.18-rc.
10793 - Remove everything related to building the expert bundle for OS X.
10794 It has confused many users, doesn't work right on OS X 10.6,
10795 and is hard to get rid of once installed. Resolves bug 1274.
10798 Changes in version 0.2.2.17-alpha - 2010-09-30
10799 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
10800 to use one-hop circuits (which can put the exit relays at higher risk,
10801 plus unbalance the network); fixes a big bug in bandwidth accounting
10802 for relays that want to limit their monthly bandwidth use; fixes a
10803 big pile of bugs in how clients tolerate temporary network failure;
10804 and makes our adaptive circuit build timeout feature (which improves
10805 client performance if your network is fast while not breaking things
10806 if your network is slow) better handle bad networks.
10809 - Exit relays now try harder to block exit attempts from unknown
10810 relays, to make it harder for people to use them as one-hop proxies
10811 a la tortunnel. Controlled by the refuseunknownexits consensus
10812 parameter (currently enabled), or you can override it on your
10813 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
10815 o Major bugfixes (0.2.1.x and earlier):
10816 - Fix a bug in bandwidth accounting that could make us use twice
10817 the intended bandwidth when our interval start changes due to
10818 daylight saving time. Now we tolerate skew in stored vs computed
10819 interval starts: if the start of the period changes by no more than
10820 50% of the period's duration, we remember bytes that we transferred
10821 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
10822 - Always search the Windows system directory for system DLLs, and
10823 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
10824 - When you're using bridges and your network goes away and your
10825 bridges get marked as down, recover when you attempt a new socks
10826 connection (if the network is back), rather than waiting up to an
10827 hour to try fetching new descriptors for your bridges. Bugfix on
10828 0.2.0.3-alpha; fixes bug 1981.
10830 o Major bugfixes (on 0.2.2.x):
10831 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
10833 - Fix a segfault that could happen when operating a bridge relay with
10834 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
10835 - The consensus bandwidth-weights (used by clients to choose fast
10836 relays) entered an unexpected edge case in September where
10837 Exits were much scarcer than Guards, resulting in bad weight
10838 recommendations. Now we compute them using new constraints that
10839 should succeed in all cases. Also alter directory authorities to
10840 not include the bandwidth-weights line if they fail to produce
10841 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
10842 - When weighting bridges during path selection, we used to trust
10843 the bandwidths they provided in their descriptor, only capping them
10844 at 10MB/s. This turned out to be problematic for two reasons:
10845 Bridges could claim to handle a lot more traffic then they
10846 actually would, thus making more clients pick them and have a
10847 pretty effective DoS attack. The other issue is that new bridges
10848 that might not have a good estimate for their bw capacity yet
10849 would not get used at all unless no other bridges are available
10850 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
10852 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
10853 - Ignore cannibalized circuits when recording circuit build times.
10854 This should provide for a minor performance improvement for hidden
10855 service users using 0.2.2.14-alpha, and should remove two spurious
10856 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
10857 - Simplify the logic that causes us to decide if the network is
10858 unavailable for purposes of recording circuit build times. If we
10859 receive no cells whatsoever for the entire duration of a circuit's
10860 full measured lifetime, the network is probably down. Also ignore
10861 one-hop directory fetching circuit timeouts when calculating our
10862 circuit build times. These changes should hopefully reduce the
10863 cases where we see ridiculous circuit build timeouts for people
10864 with spotty wireless connections. Fixes part of bug 1772; bugfix
10866 - Prevent the circuit build timeout from becoming larger than
10867 the maximum build time we have ever seen. Also, prevent the time
10868 period for measurement circuits from becoming larger than twice that
10869 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
10872 - When we run out of directory information such that we can't build
10873 circuits, but then get enough that we can build circuits, log when
10874 we actually construct a circuit, so the user has a better chance of
10875 knowing what's going on. Fixes bug 1362.
10876 - Be more generous with how much bandwidth we'd use up (with
10877 accounting enabled) before entering "soft hibernation". Previously,
10878 we'd refuse new connections and circuits once we'd used up 95% of
10879 our allotment. Now, we use up 95% of our allotment, AND make sure
10880 that we have no more than 500MB (or 3 hours of expected traffic,
10881 whichever is lower) remaining before we enter soft hibernation.
10882 - If we've configured EntryNodes and our network goes away and/or all
10883 our entrynodes get marked down, optimistically retry them all when
10884 a new socks application request appears. Fixes bug 1882.
10885 - Add some more defensive programming for architectures that can't
10886 handle unaligned integer accesses. We don't know of any actual bugs
10887 right now, but that's the best time to fix them. Fixes bug 1943.
10888 - Support line continuations in the torrc config file. If a line
10889 ends with a single backslash character, the newline is ignored, and
10890 the configuration value is treated as continuing on the next line.
10893 o Minor bugfixes (on 0.2.1.x and earlier):
10894 - For bandwidth accounting, calculate our expected bandwidth rate
10895 based on the time during which we were active and not in
10896 soft-hibernation during the last interval. Previously, we were
10897 also considering the time spent in soft-hibernation. If this
10898 was a long time, we would wind up underestimating our bandwidth
10899 by a lot, and skewing our wakeup time towards the start of the
10900 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10902 o Minor bugfixes (on 0.2.2.x):
10903 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
10904 which were disabled by the circuit build timeout changes in
10905 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
10906 - Make sure we don't warn about missing bandwidth weights when
10907 choosing bridges or other relays not in the consensus. Bugfix on
10908 0.2.2.10-alpha; fixes bug 1805.
10909 - In our logs, do not double-report signatures from unrecognized
10910 authorities both as "from unknown authority" and "not
10911 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
10914 Changes in version 0.2.2.16-alpha - 2010-09-17
10915 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
10916 evident at exit relays), and also continues to resolve all the little
10917 bugs that have been filling up trac lately.
10919 o Major bugfixes (stream-level fairness):
10920 - When receiving a circuit-level SENDME for a blocked circuit, try
10921 to package cells fairly from all the streams that had previously
10922 been blocked on that circuit. Previously, we had started with the
10923 oldest stream, and allowed each stream to potentially exhaust
10924 the circuit's package window. This gave older streams on any
10925 given circuit priority over newer ones. Fixes bug 1937. Detected
10926 originally by Camilo Viecco. This bug was introduced before the
10927 first Tor release, in svn commit r152: it is the new winner of
10928 the longest-lived bug prize.
10929 - When the exit relay got a circuit-level sendme cell, it started
10930 reading on the exit streams, even if had 500 cells queued in the
10931 circuit queue already, so the circuit queue just grew and grew in
10932 some cases. We fix this by not re-enabling reading on receipt of a
10933 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10934 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10936 - Newly created streams were allowed to read cells onto circuits,
10937 even if the circuit's cell queue was blocked and waiting to drain.
10938 This created potential unfairness, as older streams would be
10939 blocked, but newer streams would gladly fill the queue completely.
10940 We add code to detect this situation and prevent any stream from
10941 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10945 - Update to the September 1 2010 Maxmind GeoLite Country database.
10946 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10947 not. This would lead to a cookie that is still not group readable.
10948 Closes bug 1843. Suggested by katmagic.
10949 - When logging a rate-limited warning, we now mention how many messages
10950 got suppressed since the last warning.
10951 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10952 do individual connection-level rate limiting of clients. The torrc
10953 config options with the same names trump the consensus params, if
10954 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10955 consensus params which were broken from 0.2.2.7-alpha through
10956 0.2.2.14-alpha. Closes bug 1947.
10957 - When a router changes IP address or port, authorities now launch
10958 a new reachability test for it. Implements ticket 1899.
10959 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10960 2 no signature, 4 required" messages about consensus signatures
10961 easier to read, and make sure they get logged at the same severity
10962 as the messages explaining which keys are which. Fixes bug 1290.
10963 - Don't warn when we have a consensus that we can't verify because
10964 of missing certificates, unless those certificates are ones
10965 that we have been trying and failing to download. Fixes bug 1145.
10966 - If you configure your bridge with a known identity fingerprint,
10967 and the bridge authority is unreachable (as it is in at least
10968 one country now), fall back to directly requesting the descriptor
10969 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
10971 - When building with --enable-gcc-warnings on OpenBSD, disable
10972 warnings in system headers. This makes --enable-gcc-warnings
10973 pass on OpenBSD 4.8.
10975 o Minor bugfixes (on 0.2.1.x and earlier):
10976 - Authorities will now attempt to download consensuses if their
10977 own efforts to make a live consensus have failed. This change
10978 means authorities that restart will fetch a valid consensus, and
10979 it means authorities that didn't agree with the current consensus
10980 will still fetch and serve it if it has enough signatures. Bugfix
10981 on 0.2.0.9-alpha; fixes bug 1300.
10982 - Ensure DNS requests launched by "RESOLVE" commands from the
10983 controller respect the __LeaveStreamsUnattached setconf options. The
10984 same goes for requests launched via DNSPort or transparent
10985 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10986 - Allow handshaking OR connections to take a full KeepalivePeriod
10987 seconds to handshake. Previously, we would close them after
10988 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10989 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10991 - Rate-limit "Failed to hand off onionskin" warnings.
10992 - Never relay a cell for a circuit we have already destroyed.
10993 Between marking a circuit as closeable and finally closing it,
10994 it may have been possible for a few queued cells to get relayed,
10995 even though they would have been immediately dropped by the next
10996 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10997 - Never queue a cell for a circuit that's already been marked
10999 - Never vote for a server as "Running" if we have a descriptor for
11000 it claiming to be hibernating, and that descriptor was published
11001 more recently than our last contact with the server. Bugfix on
11002 0.2.0.3-alpha; fixes bug 911.
11003 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
11006 o Minor bugfixes (on 0.2.2.x):
11007 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
11008 down if a directory fetch fails and you've configured either
11009 bridges or EntryNodes. The intent was to mark the relay as down
11010 _unless_ you're using bridges or EntryNodes, since if you are
11011 then you could quickly run out of entry points.
11012 - Fix the Windows directory-listing code. A bug introduced in
11013 0.2.2.14-alpha could make Windows directory servers forget to load
11014 some of their cached v2 networkstatus files.
11015 - Really allow clients to use relays as bridges. Fixes bug 1776;
11016 bugfix on 0.2.2.15-alpha.
11017 - Demote a warn to info that happens when the CellStatistics option
11018 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
11019 Reported by Moritz Bartl.
11020 - On Windows, build correctly either with or without Unicode support.
11021 This is necessary so that Tor can support fringe platforms like
11022 Windows 98 (which has no Unicode), or Windows CE (which has no
11023 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
11026 - Add a unit test for cross-platform directory-listing code.
11029 Changes in version 0.2.2.15-alpha - 2010-08-18
11030 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
11031 fixes a variety of other bugs that were preventing performance
11032 experiments from moving forward, fixes several bothersome memory leaks,
11033 and generally closes a lot of smaller bugs that have been filling up
11037 - Stop assigning the HSDir flag to relays that disable their
11038 DirPort (and thus will refuse to answer directory requests). This
11039 fix should dramatically improve the reachability of hidden services:
11040 hidden services and hidden service clients pick six HSDir relays
11041 to store and retrieve the hidden service descriptor, and currently
11042 about half of the HSDir relays will refuse to work. Bugfix on
11043 0.2.0.10-alpha; fixes part of bug 1693.
11044 - The PerConnBWRate and Burst config options, along with the
11045 bwconnrate and bwconnburst consensus params, initialized each conn's
11046 token bucket values only when the connection is established. Now we
11047 update them if the config options change, and update them every time
11048 we get a new consensus. Otherwise we can encounter an ugly edge
11049 case where we initialize an OR conn to client-level bandwidth,
11050 but then later the relay joins the consensus and we leave it
11051 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
11052 - Fix a regression that caused Tor to rebind its ports if it receives
11053 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
11056 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11057 should give us approximately 40-50% more Guard-flagged nodes,
11058 improving the anonymity the Tor network can provide and also
11059 decreasing the dropoff in throughput that relays experience when
11060 they first get the Guard flag.
11061 - Allow enabling or disabling the *Statistics config options while
11065 - Update to the August 1 2010 Maxmind GeoLite Country database.
11066 - Have the controller interface give a more useful message than
11067 "Internal Error" in response to failed GETINFO requests.
11068 - Warn when the same option is provided more than once in a torrc
11069 file, on the command line, or in a single SETCONF statement, and
11070 the option is one that only accepts a single line. Closes bug 1384.
11071 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11072 Patch from mingw-san.
11073 - Add support for the country code "{??}" in torrc options like
11074 ExcludeNodes, to indicate all routers of unknown country. Closes
11076 - Relays report the number of bytes spent on answering directory
11077 requests in extra-info descriptors similar to {read,write}-history.
11078 Implements enhancement 1790.
11080 o Minor bugfixes (on 0.2.1.x and earlier):
11081 - Complain if PublishServerDescriptor is given multiple arguments that
11082 include 0 or 1. This configuration will be rejected in the future.
11083 Bugfix on 0.2.0.1-alpha; closes bug 1107.
11084 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
11085 Bugfix on 0.2.0.13-alpha; closes bug 928.
11086 - Change "Application request when we're believed to be offline."
11087 notice to "Application request when we haven't used client
11088 functionality lately.", to clarify that it's not an error. Bugfix
11089 on 0.0.9.3; fixes bug 1222.
11090 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
11091 would return "551 Internal error" rather than "552 Unrecognized key
11092 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
11093 - Users can't configure a regular relay to be their bridge. It didn't
11094 work because when Tor fetched the bridge descriptor, it found
11095 that it already had it, and didn't realize that the purpose of the
11096 descriptor had changed. Now we replace routers with a purpose other
11097 than bridge with bridge descriptors when fetching them. Bugfix on
11098 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
11099 refetch the descriptor with router purpose 'general', disabling
11101 - Fix a rare bug in rend_fn unit tests: we would fail a test when
11102 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
11103 on 0.2.0.10-alpha; fixes bug 1808.
11104 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11105 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11106 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11107 Servers can start sending this code when enough clients recognize
11108 it. Also update the spec to reflect this new reason. Bugfix on
11109 0.1.0.1-rc; fixes part of bug 1793.
11110 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
11111 when we switch from being a public relay to a bridge. Otherwise
11112 there will still be clients that see the relay in their consensus,
11113 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
11115 - Instead of giving an assertion failure on an internal mismatch
11116 on estimated freelist size, just log a BUG warning and try later.
11117 Mitigates but does not fix bug 1125.
11118 - Fix an assertion failure that could occur in caches or bridge users
11119 when using a very short voting interval on a testing network.
11120 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
11122 o Minor bugfixes (on 0.2.2.x):
11123 - Alter directory authorities to always consider Exit-flagged nodes
11124 as potential Guard nodes in their votes. The actual decision to
11125 use Exits as Guards is done in the consensus bandwidth weights.
11126 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
11127 - When the controller is reporting the purpose of circuits that
11128 didn't finish building before the circuit build timeout, it was
11129 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
11130 - Our libevent version parsing code couldn't handle versions like
11131 1.4.14b-stable and incorrectly warned the user about using an
11132 old and broken version of libevent. Treat 1.4.14b-stable like
11133 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
11135 - Don't use substitution references like $(VAR:MOD) when
11136 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
11137 '$(:x)' to 'x' rather than the empty string. This bites us in
11138 doc/ when configured with --disable-asciidoc. Bugfix on
11139 0.2.2.9-alpha; fixes bug 1773.
11140 - Remove a spurious hidden service server-side log notice about
11141 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
11143 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
11145 - Correctly report written bytes on linked connections. Found while
11146 implementing 1790. Bugfix on 0.2.2.4-alpha.
11147 - Fix three memory leaks: one in circuit_build_times_parse_state(),
11148 one in dirvote_add_signatures_to_pending_consensus(), and one every
11149 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
11150 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
11152 o Code simplifications and refactoring:
11153 - Take a first step towards making or.h smaller by splitting out
11154 function definitions for all source files in src/or/. Leave
11155 structures and defines in or.h for now.
11156 - Remove a bunch of unused function declarations as well as a block of
11157 #if 0'd code from the unit tests. Closes bug 1824.
11158 - New unit tests for exit-port history statistics; refactored exit
11159 statistics code to be more easily tested.
11160 - Remove the old debian/ directory from the main Tor distribution.
11161 The official Tor-for-debian git repository lives at the URL
11162 https://git.torproject.org/debian/tor.git
11165 Changes in version 0.2.2.14-alpha - 2010-07-12
11166 Tor 0.2.2.14-alpha greatly improves client-side handling of
11167 circuit build timeouts, which are used to estimate speed and improve
11168 performance. We also move to a much better GeoIP database, port Tor to
11169 Windows CE, introduce new compile flags that improve code security,
11170 add an eighth v3 directory authority, and address a lot of more
11174 - Tor directory authorities no longer crash when started with a
11175 cached-microdesc-consensus file in their data directory. Bugfix
11176 on 0.2.2.6-alpha; fixes bug 1532.
11177 - Treat an unset $HOME like an empty $HOME rather than triggering an
11178 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
11179 - Ignore negative and large circuit build timeout values that can
11180 happen during a suspend or hibernate. These values caused various
11181 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
11182 - Alter calculation of Pareto distribution parameter 'Xm' for
11183 Circuit Build Timeout learning to use the weighted average of the
11184 top N=3 modes (because we have three entry guards). Considering
11185 multiple modes should improve the timeout calculation in some cases,
11186 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
11188 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
11189 right censored distribution model. This approach improves over the
11190 synthetic timeout generation approach that was producing insanely
11191 high timeout values. Now we calculate build timeouts using truncated
11192 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
11193 - Do not close circuits that are under construction when they reach
11194 the circuit build timeout. Instead, leave them building (but do not
11195 use them) for up until the time corresponding to the 95th percentile
11196 on the Pareto CDF or 60 seconds, whichever is greater. This is done
11197 to provide better data for the new Pareto model. This percentile
11198 can be controlled by the consensus.
11201 - Move to the June 2010 Maxmind GeoLite country db (rather than the
11202 June 2009 ip-to-country GeoIP db) for our statistics that count
11203 how many users relays are seeing from each country. Now we have
11204 more accurate data for many African countries.
11205 - Port Tor to build and run correctly on Windows CE systems, using
11206 the wcecompat library. Contributed by Valerio Lupi.
11207 - New "--enable-gcc-hardening" ./configure flag (off by default)
11208 to turn on gcc compile time hardening options. It ensures
11209 that signed ints have defined behavior (-fwrapv), enables
11210 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
11211 with canaries (-fstack-protector-all), turns on ASLR protection if
11212 supported by the kernel (-fPIE, -pie), and adds additional security
11213 related warnings. Verified to work on Mac OS X and Debian Lenny.
11214 - New "--enable-linker-hardening" ./configure flag (off by default)
11215 to turn on ELF specific hardening features (relro, now). This does
11216 not work with Mac OS X or any other non-ELF binary format.
11218 o New directory authorities:
11219 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11223 - New config option "WarnUnsafeSocks 0" disables the warning that
11224 occurs whenever Tor receives a socks handshake using a version of
11225 the socks protocol that can only provide an IP address (rather
11226 than a hostname). Setups that do DNS locally over Tor are fine,
11227 and we shouldn't spam the logs in that case.
11228 - Convert the HACKING file to asciidoc, and add a few new sections
11229 to it, explaining how we use Git, how we make changelogs, and
11230 what should go in a patch.
11231 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
11232 event, to give information on the current rate of circuit timeouts
11233 over our stored history.
11234 - Add ability to disable circuit build time learning via consensus
11235 parameter and via a LearnCircuitBuildTimeout config option. Also
11236 automatically disable circuit build time calculation if we are
11237 either a AuthoritativeDirectory, or if we fail to write our state
11238 file. Fixes bug 1296.
11239 - More gracefully handle corrupt state files, removing asserts
11240 in favor of saving a backup and resetting state.
11241 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
11245 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11247 - When a2x fails, mention that the user could disable manpages instead
11248 of trying to fix their asciidoc installation.
11249 - Where available, use Libevent 2.0's periodic timers so that our
11250 once-per-second cleanup code gets called even more closely to
11251 once per second than it would otherwise. Fixes bug 943.
11252 - If you run a bridge that listens on multiple IP addresses, and
11253 some user configures a bridge address that uses a different IP
11254 address than your bridge writes in its router descriptor, and the
11255 user doesn't specify an identity key, their Tor would discard the
11256 descriptor because "it isn't one of our configured bridges", and
11257 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
11258 Bugfix on 0.2.0.3-alpha.
11259 - If OpenSSL fails to make a duplicate of a private or public key, log
11260 an error message and try to exit cleanly. May help with debugging
11261 if bug 1209 ever remanifests.
11262 - Save a couple bytes in memory allocation every time we escape
11263 certain characters in a string. Patch from Florian Zumbiehl.
11264 - Make it explicit that we don't cannibalize one-hop circuits. This
11265 happens in the wild, but doesn't turn out to be a problem because
11266 we fortunately don't use those circuits. Many thanks to outofwords
11267 for the initial analysis and to swissknife who confirmed that
11268 two-hop circuits are actually created.
11269 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
11270 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
11271 - Eliminate a case where a circuit build time warning was displayed
11272 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
11275 Changes in version 0.2.1.26 - 2010-05-02
11276 Tor 0.2.1.26 addresses the recent connection and memory overload
11277 problems we've been seeing on relays, especially relays with their
11278 DirPort open. If your relay has been crashing, or you turned it off
11279 because it used too many resources, give this release a try.
11281 This release also fixes yet another instance of broken OpenSSL libraries
11282 that was causing some relays to drop out of the consensus.
11285 - Teach relays to defend themselves from connection overload. Relays
11286 now close idle circuits early if it looks like they were intended
11287 for directory fetches. Relays are also more aggressive about closing
11288 TLS connections that have no circuits on them. Such circuits are
11289 unlikely to be re-used, and tens of thousands of them were piling
11290 up at the fast relays, causing the relays to run out of sockets
11291 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11292 their directory fetches over TLS).
11293 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11294 that claim to be earlier than 0.9.8m, but which have in reality
11295 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11296 behavior. Possible fix for some cases of bug 1346.
11297 - Directory mirrors were fetching relay descriptors only from v2
11298 directory authorities, rather than v3 authorities like they should.
11299 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11300 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11303 - Finally get rid of the deprecated and now harmful notion of "clique
11304 mode", where directory authorities maintain TLS connections to
11308 - In the util/threads test, no longer free the test_mutex before all
11309 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11310 - The master thread could starve the worker threads quite badly on
11311 certain systems, causing them to run only partially in the allowed
11312 window. This resulted in test failures. Now the master thread sleeps
11313 occasionally for a few microseconds while the two worker-threads
11314 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11317 Changes in version 0.2.2.13-alpha - 2010-04-24
11318 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
11319 problems we've been seeing on relays, especially relays with their
11320 DirPort open. If your relay has been crashing, or you turned it off
11321 because it used too many resources, give this release a try.
11324 - Teach relays to defend themselves from connection overload. Relays
11325 now close idle circuits early if it looks like they were intended
11326 for directory fetches. Relays are also more aggressive about closing
11327 TLS connections that have no circuits on them. Such circuits are
11328 unlikely to be re-used, and tens of thousands of them were piling
11329 up at the fast relays, causing the relays to run out of sockets
11330 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11331 their directory fetches over TLS).
11334 - Finally get rid of the deprecated and now harmful notion of "clique
11335 mode", where directory authorities maintain TLS connections to
11337 - Directory authorities now do an immediate reachability check as soon
11338 as they hear about a new relay. This change should slightly reduce
11339 the time between setting up a relay and getting listed as running
11340 in the consensus. It should also improve the time between setting
11341 up a bridge and seeing use by bridge users.
11342 - Directory authorities no longer launch a TLS connection to every
11343 relay as they startup. Now that we have 2k+ descriptors cached,
11344 the resulting network hiccup is becoming a burden. Besides,
11345 authorities already avoid voting about Running for the first half
11346 hour of their uptime.
11349 Changes in version 0.2.2.12-alpha - 2010-04-20
11350 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
11351 handle and vote on descriptors. It was causing relays to drop out of
11355 - Many relays have been falling out of the consensus lately because
11356 not enough authorities know about their descriptor for them to get
11357 a majority of votes. When we deprecated the v2 directory protocol,
11358 we got rid of the only way that v3 authorities can hear from each
11359 other about other descriptors. Now authorities examine every v3
11360 vote for new descriptors, and fetch them from that authority. Bugfix
11362 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
11363 and a warning in or.h related to bandwidth_weight_rule_t that
11364 prevented clean compile on OS X. Fixes bug 1363; bugfix on
11366 - Fix a segfault on relays when DirReqStatistics is enabled
11367 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
11371 - Demote a confusing TLS warning that relay operators might get when
11372 someone tries to talk to their OrPort. It is neither the operator's
11373 fault nor can they do anything about it. Fixes bug 1364; bugfix
11377 Changes in version 0.2.2.11-alpha - 2010-04-15
11378 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
11379 libraries that was causing some relays to drop out of the consensus.
11382 - Directory mirrors were fetching relay descriptors only from v2
11383 directory authorities, rather than v3 authorities like they should.
11384 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11385 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11386 - Fix a parsing error that made every possible value of
11387 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
11388 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
11389 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
11390 about the option without breaking older ones.
11391 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11392 that claim to be earlier than 0.9.8m, but which have in reality
11393 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11394 behavior. Possible fix for some cases of bug 1346.
11397 - Experiment with a more aggressive approach to preventing clients
11398 from making one-hop exit streams. Exit relays who want to try it
11399 out can set "RefuseUnknownExits 1" in their torrc, and then look
11400 for "Attempt by %s to open a stream" log messages. Let us know
11402 - Add support for statically linking zlib by specifying
11403 --enable-static-zlib, to go with our support for statically linking
11404 openssl and libevent. Resolves bug 1358.
11407 - Fix a segfault that happens whenever a Tor client that is using
11408 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
11410 - When we cleaned up the contrib/tor-exit-notice.html file, we left
11411 out the first line. Fixes bug 1295.
11412 - When building the manpage from a tarball, we required asciidoc, but
11413 the asciidoc -> roff/html conversion was already done for the
11414 tarball. Make 'make' complain only when we need asciidoc (either
11415 because we're compiling directly from git, or because we altered
11416 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
11417 - When none of the directory authorities vote on any params, Tor
11418 segfaulted when trying to make the consensus from the votes. We
11419 didn't trigger the bug in practice, because authorities do include
11420 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
11423 - In the util/threads test, no longer free the test_mutex before all
11424 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11425 - The master thread could starve the worker threads quite badly on
11426 certain systems, causing them to run only partially in the allowed
11427 window. This resulted in test failures. Now the master thread sleeps
11428 occasionally for a few microseconds while the two worker-threads
11429 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11432 Changes in version 0.2.2.10-alpha - 2010-03-07
11433 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
11434 could prevent relays from guessing their IP address correctly. It also
11435 starts the groundwork for another client-side performance boost, since
11436 currently we're not making efficient use of relays that have both the
11437 Guard flag and the Exit flag.
11440 - Fix a regression from our patch for bug 1244 that caused relays
11441 to guess their IP address incorrectly if they didn't set Address
11442 in their torrc and/or their address fails to resolve. Bugfix on
11443 0.2.2.9-alpha; fixes bug 1269.
11445 o Major features (performance):
11446 - Directory authorities now compute consensus weightings that instruct
11447 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11448 and no flag. Clients that use these weightings will distribute
11449 network load more evenly across these different relay types. The
11450 weightings are in the consensus so we can change them globally in
11451 the future. Extra thanks to "outofwords" for finding some nasty
11452 security bugs in the first implementation of this feature.
11454 o Minor features (performance):
11455 - Always perform router selections using weighted relay bandwidth,
11456 even if we don't need a high capacity circuit at the time. Non-fast
11457 circuits now only differ from fast ones in that they can use relays
11458 not marked with the Fast flag. This "feature" could turn out to
11459 be a horrible bug; we should investigate more before it goes into
11463 - Allow disabling building of the manpages. Skipping the manpage
11464 speeds up the build considerably.
11466 o Minor bugfixes (on 0.2.2.x):
11467 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
11468 Bugfix on 0.2.2.9-alpha.
11469 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
11470 config option. Bugfix on 0.2.2.7-alpha.
11471 - Ship the asciidoc-helper file in the tarball, so that people can
11472 build from source if they want to, and touching the .1.txt files
11473 doesn't break the build. Bugfix on 0.2.2.9-alpha.
11475 o Minor bugfixes (on 0.2.1.x or earlier):
11476 - Fix a dereference-then-NULL-check sequence when publishing
11477 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11479 - Fix another dereference-then-NULL-check sequence. Bugfix on
11480 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11481 - Make sure we treat potentially not NUL-terminated strings correctly.
11482 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11484 o Code simplifications and refactoring:
11485 - Fix some urls in the exit notice file and make it XHTML1.1 strict
11486 compliant. Based on a patch from Christian Kujau.
11487 - Don't use sed in asciidoc-helper anymore.
11488 - Make the build process fail if asciidoc cannot be found and
11489 building with asciidoc isn't disabled.
11492 Changes in version 0.2.2.9-alpha - 2010-02-22
11493 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
11494 location of a directory authority, and cleans up a bunch of small bugs.
11496 o Directory authority changes:
11497 - Change IP address for dannenberg (v3 directory authority), and
11498 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11499 service directory authority) from the list.
11502 - Make Tor work again on the latest OS X: when deciding whether to
11503 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11504 version at run-time, not compile time. We need to do this because
11505 Apple doesn't update its dev-tools headers when it updates its
11506 libraries in a security patch.
11507 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11508 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11509 a memory leak when requesting a hidden service descriptor we've
11510 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11512 - Authorities could be tricked into giving out the Exit flag to relays
11513 that didn't allow exiting to any ports. This bug could screw
11514 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
11515 1238. Bug discovered by Martin Kowalczyk.
11516 - When freeing a session key, zero it out completely. We only zeroed
11517 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11518 patched by ekir. Fixes bug 1254.
11521 - Fix static compilation by listing the openssl libraries in the right
11522 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
11523 - Resume handling .exit hostnames in a special way: originally we
11524 stripped the .exit part and used the requested exit relay. In
11525 0.2.2.1-alpha we stopped treating them in any special way, meaning
11526 if you use a .exit address then Tor will pass it on to the exit
11527 relay. Now we reject the .exit stream outright, since that behavior
11528 might be more expected by the user. Found and diagnosed by Scott
11529 Bennett and Downie on or-talk.
11530 - Don't spam the controller with events when we have no file
11531 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
11532 for log messages was already solved from bug 748.)
11533 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
11535 - Make the DNSPort option work with libevent 2.x. Don't alter the
11536 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
11537 - Emit a GUARD DROPPED controller event for a case we missed.
11538 - Make more fields in the controller protocol case-insensitive, since
11539 control-spec.txt said they were.
11540 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11541 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11542 - Fix a spec conformance issue: the network-status-version token
11543 must be the first token in a v3 consensus or vote. Discovered by
11544 parakeep. Bugfix on 0.2.0.3-alpha.
11546 o Code simplifications and refactoring:
11547 - Generate our manpage and HTML documentation using Asciidoc. This
11548 change should make it easier to maintain the documentation, and
11549 produce nicer HTML.
11550 - Remove the --enable-iphone option. According to reports from Marco
11551 Bonetti, Tor builds fine without any special tweaking on recent
11552 iPhone SDK versions.
11553 - Removed some unnecessary files from the source distribution. The
11554 AUTHORS file has now been merged into the people page on the
11555 website. The roadmaps and design doc can now be found in the
11556 projects directory in svn.
11557 - Enabled various circuit build timeout constants to be controlled
11558 by consensus parameters. Also set better defaults for these
11559 parameters based on experimentation on broadband and simulated
11560 high latency links.
11563 - The 'EXTENDCIRCUIT' control port command can now be used with
11564 a circ id of 0 and no path. This feature will cause Tor to build
11565 a new 'fast' general purpose circuit using its own path selection
11567 - Added a BUILDTIMEOUT_SET controller event to describe changes
11568 to the circuit build timeout.
11569 - Future-proof the controller protocol a bit by ignoring keyword
11570 arguments we do not recognize.
11571 - Expand homedirs passed to tor-checkkey. This should silence a
11572 coverity complaint about passing a user-supplied string into
11573 open() without checking it.
11576 Changes in version 0.2.1.25 - 2010-03-16
11577 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
11578 prevent relays from guessing their IP address correctly. It also fixes
11579 several minor potential security bugs.
11582 - Fix a regression from our patch for bug 1244 that caused relays
11583 to guess their IP address incorrectly if they didn't set Address
11584 in their torrc and/or their address fails to resolve. Bugfix on
11585 0.2.1.23; fixes bug 1269.
11586 - When freeing a session key, zero it out completely. We only zeroed
11587 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11588 patched by ekir. Fixes bug 1254.
11591 - Fix a dereference-then-NULL-check sequence when publishing
11592 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11594 - Fix another dereference-then-NULL-check sequence. Bugfix on
11595 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11596 - Make sure we treat potentially not NUL-terminated strings correctly.
11597 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11601 Changes in version 0.2.1.24 - 2010-02-21
11602 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11606 - Work correctly out-of-the-box with even more vendor-patched versions
11607 of OpenSSL. In particular, make it so Debian and OS X don't need
11608 customized patches to run/build.
11611 Changes in version 0.2.1.23 - 2010-02-13
11612 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
11613 again on the latest OS X, and updates the location of a directory
11616 o Major bugfixes (performance):
11617 - We were selecting our guards uniformly at random, and then weighting
11618 which of our guards we'd use uniformly at random. This imbalance
11619 meant that Tor clients were severely limited on throughput (and
11620 probably latency too) by the first hop in their circuit. Now we
11621 select guards weighted by currently advertised bandwidth. We also
11622 automatically discard guards picked using the old algorithm. Fixes
11623 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11626 - Make Tor work again on the latest OS X: when deciding whether to
11627 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11628 version at run-time, not compile time. We need to do this because
11629 Apple doesn't update its dev-tools headers when it updates its
11630 libraries in a security patch.
11631 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11632 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11633 a memory leak when requesting a hidden service descriptor we've
11634 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11637 o Directory authority changes:
11638 - Change IP address for dannenberg (v3 directory authority), and
11639 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11640 service directory authority) from the list.
11643 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11644 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11647 - Avoid a mad rush at the beginning of each month when each client
11648 rotates half of its guards. Instead we spread the rotation out
11649 throughout the month, but we still avoid leaving a precise timestamp
11650 in the state file about when we first picked the guard. Improves
11651 over the behavior introduced in 0.1.2.17.
11654 Changes in version 0.2.2.8-alpha - 2010-01-26
11655 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
11656 causing bridge relays to disappear. If you're running a bridge,
11660 - Fix a memory corruption bug on bridges that occured during the
11661 inclusion of stats data in extra-info descriptors. Also fix the
11662 interface for geoip_get_bridge_stats* to prevent similar bugs in
11663 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
11664 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
11667 - Ignore OutboundBindAddress when connecting to localhost.
11668 Connections to localhost need to come _from_ localhost, or else
11669 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
11673 Changes in version 0.2.2.7-alpha - 2010-01-19
11674 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
11675 as laying the groundwork for further relay-side performance fixes. It
11676 also starts cleaning up client behavior with respect to the EntryNodes,
11677 ExitNodes, and StrictNodes config options.
11679 This release also rotates two directory authority keys, due to a
11680 security breach of some of the Torproject servers.
11682 o Directory authority changes:
11683 - Rotate keys (both v3 identity and relay identity) for moria1
11686 o Major features (performance):
11687 - We were selecting our guards uniformly at random, and then weighting
11688 which of our guards we'd use uniformly at random. This imbalance
11689 meant that Tor clients were severely limited on throughput (and
11690 probably latency too) by the first hop in their circuit. Now we
11691 select guards weighted by currently advertised bandwidth. We also
11692 automatically discard guards picked using the old algorithm. Fixes
11693 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11694 - When choosing which cells to relay first, relays can now favor
11695 circuits that have been quiet recently, to provide lower latency
11696 for low-volume circuits. By default, relays enable or disable this
11697 feature based on a setting in the consensus. You can override
11698 this default by using the new "CircuitPriorityHalflife" config
11699 option. Design and code by Ian Goldberg, Can Tang, and Chris
11701 - Add separate per-conn write limiting to go with the per-conn read
11702 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11703 but never per-conn write limits.
11704 - New consensus params "bwconnrate" and "bwconnburst" to let us
11705 rate-limit client connections as they enter the network. It's
11706 controlled in the consensus so we can turn it on and off for
11707 experiments. It's starting out off. Based on proposal 163.
11709 o Major features (relay selection options):
11710 - Switch to a StrictNodes config option, rather than the previous
11711 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
11712 "StrictExcludeNodes" option.
11713 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11714 change during a config reload, mark and discard all our origin
11715 circuits. This fix should address edge cases where we change the
11716 config options and but then choose a circuit that we created before
11718 - If EntryNodes or ExitNodes are set, be more willing to use an
11719 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
11721 - Make EntryNodes config option much more aggressive even when
11722 StrictNodes is not set. Before it would prepend your requested
11723 entrynodes to your list of guard nodes, but feel free to use others
11724 after that. Now it chooses only from your EntryNodes if any of
11725 those are available, and only falls back to others if a) they're
11726 all down and b) StrictNodes is not set.
11727 - Now we refresh your entry guards from EntryNodes at each consensus
11728 fetch -- rather than just at startup and then they slowly rot as
11729 the network changes.
11732 - Stop bridge directory authorities from answering dbg-stability.txt
11733 directory queries, which would let people fetch a list of all
11734 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11737 - Log a notice when we get a new control connection. Now it's easier
11738 for security-conscious users to recognize when a local application
11739 is knocking on their controller door. Suggested by bug 1196.
11740 - New config option "CircuitStreamTimeout" to override our internal
11741 timeout schedule for how many seconds until we detach a stream from
11742 a circuit and try a new circuit. If your network is particularly
11743 slow, you might want to set this to a number like 60.
11744 - New controller command "getinfo config-text". It returns the
11745 contents that Tor would write if you send it a SAVECONF command,
11746 so the controller can write the file to disk itself.
11747 - New options for SafeLogging to allow scrubbing only log messages
11748 generated while acting as a relay.
11749 - Ship the bridges spec file in the tarball too.
11750 - Avoid a mad rush at the beginning of each month when each client
11751 rotates half of its guards. Instead we spread the rotation out
11752 throughout the month, but we still avoid leaving a precise timestamp
11753 in the state file about when we first picked the guard. Improves
11754 over the behavior introduced in 0.1.2.17.
11756 o Minor bugfixes (compiling):
11757 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11758 hides it. Bugfix on 0.2.2.6-alpha.
11759 - Fix compilation on Solaris by removing support for the
11760 DisableAllSwap config option. Solaris doesn't have an rlimit for
11761 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11764 o Minor bugfixes (crashes):
11765 - Do not segfault when writing buffer stats when we haven't observed
11766 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11768 - If we're in the pathological case where there's no exit bandwidth
11769 but there is non-exit bandwidth, or no guard bandwidth but there
11770 is non-guard bandwidth, don't crash during path selection. Bugfix
11772 - Fix an impossible-to-actually-trigger buffer overflow in relay
11773 descriptor generation. Bugfix on 0.1.0.15.
11775 o Minor bugfixes (privacy):
11776 - Fix an instance where a Tor directory mirror might accidentally
11777 log the IP address of a misbehaving Tor client. Bugfix on
11779 - Don't list Windows capabilities in relay descriptors. We never made
11780 use of them, and maybe it's a bad idea to publish them. Bugfix
11783 o Minor bugfixes (other):
11784 - Resolve an edge case in path weighting that could make us misweight
11785 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
11786 - Fix statistics on client numbers by country as seen by bridges that
11787 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
11788 intervals instead of variable 12-to-48-hour intervals.
11789 - After we free an internal connection structure, overwrite it
11790 with a different memory value than we use for overwriting a freed
11791 internal circuit structure. Should help with debugging. Suggested
11793 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
11796 o Removed features:
11797 - Remove the HSAuthorityRecordStats option that version 0 hidden
11798 service authorities could have used to track statistics of overall
11799 hidden service usage.
11802 Changes in version 0.2.1.22 - 2010-01-19
11803 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
11804 authorities -- it would tell you its whole history of bridge descriptors
11805 if you make the right directory request. This stable update also
11806 rotates two of the seven v3 directory authority keys and locations.
11808 o Directory authority changes:
11809 - Rotate keys (both v3 identity and relay identity) for moria1
11813 - Stop bridge directory authorities from answering dbg-stability.txt
11814 directory queries, which would let people fetch a list of all
11815 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11818 Changes in version 0.2.1.21 - 2009-12-21
11819 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
11820 library. If you use Tor on Linux / Unix and you're getting SSL
11821 renegotiation errors, upgrading should help. We also recommend an
11822 upgrade if you're an exit relay.
11825 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11826 handshake from working unless we explicitly tell OpenSSL that we
11827 are using SSL renegotiation safely. We are, of course, but OpenSSL
11828 0.9.8l won't work unless we say we are.
11829 - Avoid crashing if the client is trying to upload many bytes and the
11830 circuit gets torn down at the same time, or if the flip side
11831 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
11834 - Do not refuse to learn about authority certs and v2 networkstatus
11835 documents that are older than the latest consensus. This bug might
11836 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11837 Spotted and fixed by xmux.
11838 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
11839 trigger platform-specific option misparsing case found by Coverity
11841 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
11842 trigger assert. Fixes bug 1173.
11845 Changes in version 0.2.2.6-alpha - 2009-11-19
11846 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
11847 support for the new lower-footprint "microdescriptor" directory design,
11848 future-proofing our consensus format against new hash functions or
11849 other changes, and an Android port. It also makes Tor compatible with
11850 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
11853 - Directory authorities can now create, vote on, and serve multiple
11854 parallel formats of directory data as part of their voting process.
11855 Partially implements Proposal 162: "Publish the consensus in
11857 - Directory authorities can now agree on and publish small summaries
11858 of router information that clients can use in place of regular
11859 server descriptors. This transition will eventually allow clients
11860 to use far less bandwidth for downloading information about the
11861 network. Begins the implementation of Proposal 158: "Clients
11862 download consensus + microdescriptors".
11863 - The directory voting system is now extensible to use multiple hash
11864 algorithms for signatures and resource selection. Newer formats
11865 are signed with SHA256, with a possibility for moving to a better
11866 hash algorithm in the future.
11867 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11868 current and future memory pages via mlockall(). On supported
11869 platforms (modern Linux and probably BSD but not Windows or OS X),
11870 this should effectively disable any and all attempts to page out
11871 memory. This option requires that you start your Tor as root --
11872 if you use DisableAllSwap, please consider using the User option
11873 to properly reduce the privileges of your Tor.
11874 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11875 to help Tor build correctly for Android phones.
11878 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11879 handshake from working unless we explicitly tell OpenSSL that we
11880 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
11881 won't work unless we say we are.
11884 - Fix a crash bug when trying to initialize the evdns module in
11885 Libevent 2. Bugfix on 0.2.1.16-rc.
11886 - Stop logging at severity 'warn' when some other Tor client tries
11887 to establish a circuit with us using weak DH keys. It's a protocol
11888 violation, but that doesn't mean ordinary users need to hear about
11889 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
11890 - Do not refuse to learn about authority certs and v2 networkstatus
11891 documents that are older than the latest consensus. This bug might
11892 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11893 Spotted and fixed by xmux.
11894 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
11895 - If all authorities restart at once right before a consensus vote,
11896 nobody will vote about "Running", and clients will get a consensus
11897 with no usable relays. Instead, authorities refuse to build a
11898 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11899 - If your relay can't keep up with the number of incoming create
11900 cells, it would log one warning per failure into your logs. Limit
11901 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
11902 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11903 on 0.2.0.3-alpha; fixes bug 1113.
11904 - Fix a memory leak on directory authorities during voting that was
11905 introduced in 0.2.2.1-alpha. Found via valgrind.
11908 Changes in version 0.2.1.20 - 2009-10-15
11909 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11910 services at once, prepares for more performance improvements, and
11911 fixes a bunch of smaller bugs.
11913 The Windows and OS X bundles also include a more recent Vidalia,
11914 and switch from Privoxy to Polipo.
11916 The OS X installers are now drag and drop. It's best to un-install
11917 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11918 you want to upgrade, you'll need to update the paths for Tor and Polipo
11919 in the Vidalia Settings window.
11922 - Send circuit or stream sendme cells when our window has decreased
11923 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11924 by Karsten when testing the "reduce circuit window" performance
11925 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11926 before the release of Tor 0.0.0. This is the new winner of the
11928 - Fix a remotely triggerable memory leak when a consensus document
11929 contains more than one signature from the same voter. Bugfix on
11931 - Avoid segfault in rare cases when finishing an introduction circuit
11932 as a client and finding out that we don't have an introduction key
11933 for it. Fixes bug 1073. Reported by Aaron Swartz.
11936 - Tor now reads the "circwindow" parameter out of the consensus,
11937 and uses that value for its circuit package window rather than the
11938 default of 1000 cells. Begins the implementation of proposal 168.
11940 o New directory authorities:
11941 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11943 - Move moria1 and tonga to alternate IP addresses.
11946 - Fix a signed/unsigned compile warning in 0.2.1.19.
11947 - Fix possible segmentation fault on directory authorities. Bugfix on
11949 - Fix an extremely rare infinite recursion bug that could occur if
11950 we tried to log a message after shutting down the log subsystem.
11951 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11952 - Fix an obscure bug where hidden services on 64-bit big-endian
11953 systems might mis-read the timestamp in v3 introduce cells, and
11954 refuse to connect back to the client. Discovered by "rotor".
11955 Bugfix on 0.2.1.6-alpha.
11956 - We were triggering a CLOCK_SKEW controller status event whenever
11957 we connect via the v2 connection protocol to any relay that has
11958 a wrong clock. Instead, we should only inform the controller when
11959 it's a trusted authority that claims our clock is wrong. Bugfix
11960 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11961 - We were telling the controller about CHECKING_REACHABILITY and
11962 REACHABILITY_FAILED status events whenever we launch a testing
11963 circuit or notice that one has failed. Instead, only tell the
11964 controller when we want to inform the user of overall success or
11965 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11967 - Don't warn when we're using a circuit that ends with a node
11968 excluded in ExcludeExitNodes, but the circuit is not used to access
11969 the outside world. This should help fix bug 1090. Bugfix on
11971 - Work around a small memory leak in some versions of OpenSSL that
11972 stopped the memory used by the hostname TLS extension from being
11976 - Add a "getinfo status/accepted-server-descriptor" controller
11977 command, which is the recommended way for controllers to learn
11978 whether our server descriptor has been successfully received by at
11979 least on directory authority. Un-recommend good-server-descriptor
11980 getinfo and status events until we have a better design for them.
11983 Changes in version 0.2.2.5-alpha - 2009-10-11
11984 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
11987 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11989 o Directory authorities:
11990 - Temporarily (just for this release) move dizum to an alternate
11994 Changes in version 0.2.2.4-alpha - 2009-10-10
11995 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
11996 introduces a new unit test framework, shifts directry authority
11997 addresses around to reduce the impact from recent blocking events,
11998 and fixes a few smaller bugs.
12001 - Fix several more asserts in the circuit_build_times code, for
12002 example one that causes Tor to fail to start once we have
12003 accumulated 5000 build times in the state file. Bugfixes on
12004 0.2.2.2-alpha; fixes bug 1108.
12006 o New directory authorities:
12007 - Move moria1 and Tonga to alternate IP addresses.
12010 - Log SSL state transitions at debug level during handshake, and
12011 include SSL states in error messages. This may help debug future
12012 SSL handshake issues.
12013 - Add a new "Handshake" log domain for activities that happen
12014 during the TLS handshake.
12015 - Revert to the "June 3 2009" ip-to-country file. The September one
12016 seems to have removed most US IP addresses.
12017 - Directory authorities now reject Tor relays with versions less than
12018 0.1.2.14. This step cuts out four relays from the current network,
12019 none of which are very big.
12022 - Fix a couple of smaller issues with gathering statistics. Bugfixes
12024 - Fix two memory leaks in the error case of
12025 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
12026 - Don't count one-hop circuits when we're estimating how long it
12027 takes circuits to build on average. Otherwise we'll set our circuit
12028 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
12029 - Directory authorities no longer change their opinion of, or vote on,
12030 whether a router is Running, unless they have themselves been
12031 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12034 o Code simplifications and refactoring:
12035 - Revise our unit tests to use the "tinytest" framework, so we
12036 can run tests in their own processes, have smarter setup/teardown
12037 code, and so on. The unit test code has moved to its own
12038 subdirectory, and has been split into multiple modules.
12041 Changes in version 0.2.2.3-alpha - 2009-09-23
12042 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
12045 - Fix an overzealous assert in our new circuit build timeout code.
12046 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
12049 - If the networkstatus consensus tells us that we should use a
12050 negative circuit package window, ignore it. Otherwise we'll
12051 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
12054 Changes in version 0.2.2.2-alpha - 2009-09-21
12055 Tor 0.2.2.2-alpha introduces our latest performance improvement for
12056 clients: Tor tracks the average time it takes to build a circuit, and
12057 avoids using circuits that take too long to build. For fast connections,
12058 this feature can cut your expected latency in half. For slow or flaky
12059 connections, it could ruin your Tor experience. Let us know if it does!
12062 - Tor now tracks how long it takes to build client-side circuits
12063 over time, and adapts its timeout to local network performance.
12064 Since a circuit that takes a long time to build will also provide
12065 bad performance, we get significant latency improvements by
12066 discarding the slowest 20% of circuits. Specifically, Tor creates
12067 circuits more aggressively than usual until it has enough data
12068 points for a good timeout estimate. Implements proposal 151.
12069 We are especially looking for reports (good and bad) from users with
12070 both EDGE and broadband connections that can move from broadband
12071 to EDGE and find out if the build-time data in the .tor/state gets
12072 reset without loss of Tor usability. You should also see a notice
12073 log message telling you that Tor has reset its timeout.
12074 - Directory authorities can now vote on arbitary integer values as
12075 part of the consensus process. This is designed to help set
12076 network-wide parameters. Implements proposal 167.
12077 - Tor now reads the "circwindow" parameter out of the consensus,
12078 and uses that value for its circuit package window rather than the
12079 default of 1000 cells. Begins the implementation of proposal 168.
12082 - Fix a remotely triggerable memory leak when a consensus document
12083 contains more than one signature from the same voter. Bugfix on
12087 - Fix an extremely rare infinite recursion bug that could occur if
12088 we tried to log a message after shutting down the log subsystem.
12089 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12090 - Fix parsing for memory or time units given without a space between
12091 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
12092 - A networkstatus vote must contain exactly one signature. Spec
12093 conformance issue. Bugfix on 0.2.0.3-alpha.
12094 - Fix an obscure bug where hidden services on 64-bit big-endian
12095 systems might mis-read the timestamp in v3 introduce cells, and
12096 refuse to connect back to the client. Discovered by "rotor".
12097 Bugfix on 0.2.1.6-alpha.
12098 - We were triggering a CLOCK_SKEW controller status event whenever
12099 we connect via the v2 connection protocol to any relay that has
12100 a wrong clock. Instead, we should only inform the controller when
12101 it's a trusted authority that claims our clock is wrong. Bugfix
12102 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12103 - We were telling the controller about CHECKING_REACHABILITY and
12104 REACHABILITY_FAILED status events whenever we launch a testing
12105 circuit or notice that one has failed. Instead, only tell the
12106 controller when we want to inform the user of overall success or
12107 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12109 - Don't warn when we're using a circuit that ends with a node
12110 excluded in ExcludeExitNodes, but the circuit is not used to access
12111 the outside world. This should help fix bug 1090, but more problems
12112 remain. Bugfix on 0.2.1.6-alpha.
12113 - Work around a small memory leak in some versions of OpenSSL that
12114 stopped the memory used by the hostname TLS extension from being
12116 - Make our 'torify' script more portable; if we have only one of
12117 'torsocks' or 'tsocks' installed, don't complain to the user;
12118 and explain our warning about tsocks better.
12121 - Add a "getinfo status/accepted-server-descriptor" controller
12122 command, which is the recommended way for controllers to learn
12123 whether our server descriptor has been successfully received by at
12124 least on directory authority. Un-recommend good-server-descriptor
12125 getinfo and status events until we have a better design for them.
12126 - Update to the "September 4 2009" ip-to-country file.
12129 Changes in version 0.2.2.1-alpha - 2009-08-26
12130 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
12131 Tor clients to bootstrap on networks where only port 80 is reachable,
12132 makes it more straightforward to support hardware crypto accelerators,
12133 and starts the groundwork for gathering stats safely at relays.
12136 - Start the process of disabling ".exit" address notation, since it
12137 can be used for a variety of esoteric application-level attacks
12138 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12141 o New directory authorities:
12142 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12146 - New AccelName and AccelDir options add support for dynamic OpenSSL
12147 hardware crypto acceleration engines.
12148 - Tor now supports tunneling all of its outgoing connections over
12149 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12150 configuration options. Code by Christopher Davis.
12153 - Send circuit or stream sendme cells when our window has decreased
12154 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12155 by Karsten when testing the "reduce circuit window" performance
12156 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12157 before the release of Tor 0.0.0. This is the new winner of the
12160 o New options for gathering stats safely:
12161 - Directory mirrors that set "DirReqStatistics 1" write statistics
12162 about directory requests to disk every 24 hours. As compared to the
12163 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
12164 1) stats are written to disk exactly every 24 hours; 2) estimated
12165 shares of v2 and v3 requests are determined as mean values, not at
12166 the end of a measurement period; 3) unresolved requests are listed
12167 with country code '??'; 4) directories also measure download times.
12168 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12169 number of exit streams and transferred bytes per port to disk every
12171 - Relays that set "CellStatistics 1" write statistics on how long
12172 cells spend in their circuit queues to disk every 24 hours.
12173 - Entry nodes that set "EntryStatistics 1" write statistics on the
12174 rough number and origins of connecting clients to disk every 24
12176 - Relays that write any of the above statistics to disk and set
12177 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12178 their extra-info documents.
12181 - New --digests command-line switch to output the digests of the
12182 source files Tor was built with.
12183 - The "torify" script now uses torsocks where available.
12184 - The memarea code now uses a sentinel value at the end of each area
12185 to make sure nothing writes beyond the end of an area. This might
12186 help debug some conceivable causes of bug 930.
12187 - Time and memory units in the configuration file can now be set to
12188 fractional units. For example, "2.5 GB" is now a valid value for
12190 - Certain Tor clients (such as those behind check.torproject.org) may
12191 want to fetch the consensus in an extra early manner. To enable this
12192 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12193 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12194 as only certain clients who must have this information sooner should
12196 - Instead of adding the svn revision to the Tor version string, report
12197 the git commit (when we're building from a git checkout).
12200 - If any of the v3 certs we download are unparseable, we should
12201 actually notice the failure so we don't retry indefinitely. Bugfix
12202 on 0.2.0.x; reported by "rotator".
12203 - If the cached cert file is unparseable, warn but don't exit.
12204 - Fix possible segmentation fault on directory authorities. Bugfix on
12206 - When Tor fails to parse a descriptor of any kind, dump it to disk.
12207 Might help diagnosing bug 1051.
12209 o Deprecated and removed features:
12210 - The controller no longer accepts the old obsolete "addr-mappings/"
12211 or "unregistered-servers-" GETINFO values.
12212 - Hidden services no longer publish version 0 descriptors, and clients
12213 do not request or use version 0 descriptors. However, the old hidden
12214 service authorities still accept and serve version 0 descriptors
12215 when contacted by older hidden services/clients.
12216 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
12217 always on; using them is necessary for correct forward-compatible
12219 - Remove support for .noconnect style addresses. Nobody was using
12220 them, and they provided another avenue for detecting Tor users
12221 via application-level web tricks.
12223 o Packaging changes:
12224 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
12225 installer bundles. See
12226 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
12227 for details of what's new in Vidalia 0.2.3.
12228 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
12229 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
12230 configuration file, rather than the old Privoxy.
12231 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
12232 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
12233 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
12234 better compatibility with OS X 10.6, aka Snow Leopard.
12235 - OS X Vidalia Bundle: The multi-package installer is now replaced
12236 by a simple drag and drop to the /Applications folder. This change
12237 occurred with the upgrade to Vidalia 0.2.3.
12240 Changes in version 0.2.1.19 - 2009-07-28
12241 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
12242 services on Tor 0.2.1.3-alpha through 0.2.1.18.
12245 - Make accessing hidden services on 0.2.1.x work right again.
12246 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
12247 part of patch provided by "optimist".
12250 - When a relay/bridge is writing out its identity key fingerprint to
12251 the "fingerprint" file and to its logs, write it without spaces. Now
12252 it will look like the fingerprints in our bridges documentation,
12253 and confuse fewer users.
12256 - Relays no longer publish a new server descriptor if they change
12257 their MaxAdvertisedBandwidth config option but it doesn't end up
12258 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
12259 fixes bug 1026. Patch from Sebastian.
12260 - Avoid leaking memory every time we get a create cell but we have
12261 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
12262 fixes bug 1034. Reported by BarkerJr.
12265 Changes in version 0.2.1.18 - 2009-07-24
12266 Tor 0.2.1.18 lays the foundations for performance improvements,
12267 adds status events to help users diagnose bootstrap problems, adds
12268 optional authentication/authorization for hidden services, fixes a
12269 variety of potential anonymity problems, and includes a huge pile of
12270 other features and bug fixes.
12273 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
12276 Changes in version 0.2.1.17-rc - 2009-07-07
12277 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
12278 candidate for the 0.2.1.x series. It lays the groundwork for further
12279 client performance improvements, and also fixes a big bug with directory
12280 authorities that were causing them to assign Guard and Stable flags
12283 The Windows bundles also finally include the geoip database that we
12284 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
12285 should actually install Torbutton rather than giving you a cryptic
12286 failure message (oops).
12289 - Clients now use the bandwidth values in the consensus, rather than
12290 the bandwidth values in each relay descriptor. This approach opens
12291 the door to more accurate bandwidth estimates once the directory
12292 authorities start doing active measurements. Implements more of
12296 - When Tor clients restart after 1-5 days, they discard all their
12297 cached descriptors as too old, but they still use the cached
12298 consensus document. This approach is good for robustness, but
12299 bad for performance: since they don't know any bandwidths, they
12300 end up choosing at random rather than weighting their choice by
12301 speed. Fixed by the above feature of putting bandwidths in the
12302 consensus. Bugfix on 0.2.0.x.
12303 - Directory authorities were neglecting to mark relays down in their
12304 internal histories if the relays fall off the routerlist without
12305 ever being found unreachable. So there were relays in the histories
12306 that haven't been seen for eight months, and are listed as being
12307 up for eight months. This wreaked havoc on the "median wfu"
12308 and "median mtbf" calculations, in turn making Guard and Stable
12309 flags very wrong, hurting network performance. Fixes bugs 696 and
12310 969. Bugfix on 0.2.0.6-alpha.
12313 - Serve the DirPortFrontPage page even when we have been approaching
12314 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
12315 - The control port would close the connection before flushing long
12316 replies, such as the network consensus, if a QUIT command was issued
12317 before the reply had completed. Now, the control port flushes all
12318 pending replies before closing the connection. Also fixed a spurious
12319 warning when a QUIT command is issued after a malformed or rejected
12320 AUTHENTICATE command, but before the connection was closed. Patch
12321 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
12322 - When we can't find an intro key for a v2 hidden service descriptor,
12323 fall back to the v0 hidden service descriptor and log a bug message.
12324 Workaround for bug 1024.
12325 - Fix a log message that did not respect the SafeLogging option.
12329 - If we're a relay and we change our IP address, be more verbose
12330 about the reason that made us change. Should help track down
12331 further bugs for relays on dynamic IP addresses.
12334 Changes in version 0.2.0.35 - 2009-06-24
12336 - Avoid crashing in the presence of certain malformed descriptors.
12337 Found by lark, and by automated fuzzing.
12338 - Fix an edge case where a malicious exit relay could convince a
12339 controller that the client's DNS question resolves to an internal IP
12340 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12343 - Finally fix the bug where dynamic-IP relays disappear when their
12344 IP address changes: directory mirrors were mistakenly telling
12345 them their old address if they asked via begin_dir, so they
12346 never got an accurate answer about their new address, so they
12347 just vanished after a day. For belt-and-suspenders, relays that
12348 don't set Address in their config now avoid using begin_dir for
12349 all direct connections. Should fix bugs 827, 883, and 900.
12350 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12351 that would occur on some exit nodes when DNS failures and timeouts
12352 occurred in certain patterns. Fix for bug 957.
12355 - When starting with a cache over a few days old, do not leak
12356 memory for the obsolete router descriptors in it. Bugfix on
12357 0.2.0.33; fixes bug 672.
12358 - Hidden service clients didn't use a cached service descriptor that
12359 was older than 15 minutes, but wouldn't fetch a new one either,
12360 because there was already one in the cache. Now, fetch a v2
12361 descriptor unless the same descriptor was added to the cache within
12362 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12365 Changes in version 0.2.1.16-rc - 2009-06-20
12366 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
12367 a bunch of minor bugs.
12370 - Fix an edge case where a malicious exit relay could convince a
12371 controller that the client's DNS question resolves to an internal IP
12372 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12374 o Major performance improvements (on 0.2.0.x):
12375 - Disable and refactor some debugging checks that forced a linear scan
12376 over the whole server-side DNS cache. These accounted for over 50%
12377 of CPU time on a relatively busy exit node's gprof profile. Found
12379 - Disable some debugging checks that appeared in exit node profile
12383 - Update to the "June 3 2009" ip-to-country file.
12384 - Do not have tor-resolve automatically refuse all .onion addresses;
12385 if AutomapHostsOnResolve is set in your torrc, this will work fine.
12387 o Minor bugfixes (on 0.2.0.x):
12388 - Log correct error messages for DNS-related network errors on
12390 - Fix a race condition that could cause crashes or memory corruption
12391 when running as a server with a controller listening for log
12393 - Avoid crashing when we have a policy specified in a DirPolicy or
12394 SocksPolicy or ReachableAddresses option with ports set on it,
12395 and we re-load the policy. May fix bug 996.
12396 - Hidden service clients didn't use a cached service descriptor that
12397 was older than 15 minutes, but wouldn't fetch a new one either,
12398 because there was already one in the cache. Now, fetch a v2
12399 descriptor unless the same descriptor was added to the cache within
12400 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12402 o Minor bugfixes (on 0.2.1.x):
12403 - Don't warn users about low port and hibernation mix when they
12404 provide a *ListenAddress directive to fix that. Bugfix on
12406 - When switching back and forth between bridge mode, do not start
12407 gathering GeoIP data until two hours have passed.
12408 - Do not complain that the user has requested an excluded node as
12409 an exit when the node is not really an exit. This could happen
12410 because the circuit was for testing, or an introduction point.
12414 Changes in version 0.2.1.15-rc - 2009-05-25
12415 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
12416 series. It fixes a major bug on fast exit relays, as well as a variety
12417 of more minor bugs.
12419 o Major bugfixes (on 0.2.0.x):
12420 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12421 that would occur on some exit nodes when DNS failures and timeouts
12422 occurred in certain patterns. Fix for bug 957.
12424 o Minor bugfixes (on 0.2.0.x):
12425 - Actually return -1 in the error case for read_bandwidth_usage().
12426 Harmless bug, since we currently don't care about the return value
12427 anywhere. Bugfix on 0.2.0.9-alpha.
12428 - Provide a more useful log message if bug 977 (related to buffer
12429 freelists) ever reappears, and do not crash right away.
12430 - Fix an assertion failure on 64-bit platforms when we allocated
12431 memory right up to the end of a memarea, then realigned the memory
12432 one step beyond the end. Fixes a possible cause of bug 930.
12433 - Protect the count of open sockets with a mutex, so we can't
12434 corrupt it when two threads are closing or opening sockets at once.
12435 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
12436 - Don't allow a bridge to publish its router descriptor to a
12437 non-bridge directory authority. Fixes part of bug 932.
12438 - When we change to or from being a bridge, reset our counts of
12439 client usage by country. Fixes bug 932.
12440 - Fix a bug that made stream bandwidth get misreported to the
12442 - Stop using malloc_usable_size() to use more area than we had
12443 actually allocated: it was safe, but made valgrind really unhappy.
12444 - Fix a memory leak when v3 directory authorities load their keys
12445 and cert from disk. Bugfix on 0.2.0.1-alpha.
12447 o Minor bugfixes (on 0.2.1.x):
12448 - Fix use of freed memory when deciding to mark a non-addable
12449 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
12452 Changes in version 0.2.1.14-rc - 2009-04-12
12453 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
12454 series. It begins fixing some major performance problems, and also
12455 finally addresses the bug that was causing relays on dynamic IP
12456 addresses to fall out of the directory.
12459 - Clients replace entry guards that were chosen more than a few months
12460 ago. This change should significantly improve client performance,
12461 especially once more people upgrade, since relays that have been
12462 a guard for a long time are currently overloaded.
12464 o Major bugfixes (on 0.2.0):
12465 - Finally fix the bug where dynamic-IP relays disappear when their
12466 IP address changes: directory mirrors were mistakenly telling
12467 them their old address if they asked via begin_dir, so they
12468 never got an accurate answer about their new address, so they
12469 just vanished after a day. For belt-and-suspenders, relays that
12470 don't set Address in their config now avoid using begin_dir for
12471 all direct connections. Should fix bugs 827, 883, and 900.
12472 - Relays were falling out of the networkstatus consensus for
12473 part of a day if they changed their local config but the
12474 authorities discarded their new descriptor as "not sufficiently
12475 different". Now directory authorities accept a descriptor as changed
12476 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
12477 patch by Sebastian.
12478 - Avoid crashing in the presence of certain malformed descriptors.
12479 Found by lark, and by automated fuzzing.
12482 - When generating circuit events with verbose nicknames for
12483 controllers, try harder to look up nicknames for routers on a
12484 circuit. (Previously, we would look in the router descriptors we had
12485 for nicknames, but not in the consensus.) Partial fix for bug 941.
12486 - If the bridge config line doesn't specify a port, assume 443.
12487 This makes bridge lines a bit smaller and easier for users to
12489 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
12490 bytes (aka 20KB/s), to match our documentation. Also update
12491 directory authorities so they always assign the Fast flag to relays
12492 with 20KB/s of capacity. Now people running relays won't suddenly
12493 find themselves not seeing any use, if the network gets faster
12495 - Update to the "April 3 2009" ip-to-country file.
12498 - Avoid trying to print raw memory to the logs when we decide to
12499 give up on downloading a given relay descriptor. Bugfix on
12501 - In tor-resolve, when the Tor client to use is specified by
12502 <hostname>:<port>, actually use the specified port rather than
12503 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
12504 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
12505 - When starting with a cache over a few days old, do not leak
12506 memory for the obsolete router descriptors in it. Bugfix on
12508 - Avoid double-free on list of successfully uploaded hidden
12509 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
12510 - Change memarea_strndup() implementation to work even when
12511 duplicating a string at the end of a page. This bug was
12512 harmless for now, but could have meant crashes later. Fix by
12513 lark. Bugfix on 0.2.1.1-alpha.
12514 - Limit uploaded directory documents to be 16M rather than 500K.
12515 The directory authorities were refusing v3 consensus votes from
12516 other authorities, since the votes are now 504K. Fixes bug 959;
12517 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
12518 - Directory authorities should never send a 503 "busy" response to
12519 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
12523 Changes in version 0.2.1.13-alpha - 2009-03-09
12524 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
12525 cleanups. We're finally getting close to a release candidate.
12528 - Correctly update the list of which countries we exclude as
12529 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
12530 lark. Bugfix on 0.2.1.6-alpha.
12532 o Minor bugfixes (on 0.2.0.x and earlier):
12533 - Automatically detect MacOSX versions earlier than 10.4.0, and
12534 disable kqueue from inside Tor when running with these versions.
12535 We previously did this from the startup script, but that was no
12536 help to people who didn't use the startup script. Resolves bug 863.
12537 - When we had picked an exit node for a connection, but marked it as
12538 "optional", and it turned out we had no onion key for the exit,
12539 stop wanting that exit and try again. This situation may not
12540 be possible now, but will probably become feasible with proposal
12541 158. Spotted by rovv. Fixes another case of bug 752.
12542 - Clients no longer cache certificates for authorities they do not
12543 recognize. Bugfix on 0.2.0.9-alpha.
12544 - When we can't transmit a DNS request due to a network error, retry
12545 it after a while, and eventually transmit a failing response to
12546 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
12547 - If the controller claimed responsibility for a stream, but that
12548 stream never finished making its connection, it would live
12549 forever in circuit_wait state. Now we close it after SocksTimeout
12550 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
12551 - Drop begin cells to a hidden service if they come from the middle
12552 of a circuit. Patch from lark.
12553 - When we erroneously receive two EXTEND cells for the same circuit
12554 ID on the same connection, drop the second. Patch from lark.
12555 - Fix a crash that occurs on exit nodes when a nameserver request
12556 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
12557 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
12559 - Do not assume that a stack-allocated character array will be
12560 64-bit aligned on platforms that demand that uint64_t access is
12561 aligned. Possible fix for bug 604.
12562 - Parse dates and IPv4 addresses in a locale- and libc-independent
12563 manner, to avoid platform-dependent behavior on malformed input.
12564 - Build correctly when configured to build outside the main source
12565 path. Patch from Michael Gold.
12566 - We were already rejecting relay begin cells with destination port
12567 of 0. Now also reject extend cells with destination port or address
12568 of 0. Suggested by lark.
12570 o Minor bugfixes (on 0.2.1.x):
12571 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
12572 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
12573 - If we're an exit node, scrub the IP address to which we are exiting
12574 in the logs. Bugfix on 0.2.1.8-alpha.
12577 - On Linux, use the prctl call to re-enable core dumps when the user
12579 - New controller event NEWCONSENSUS that lists the networkstatus
12580 lines for every recommended relay. Now controllers like Torflow
12581 can keep up-to-date on which relays they should be using.
12582 - Update to the "February 26 2009" ip-to-country file.
12585 Changes in version 0.2.0.34 - 2009-02-08
12586 Tor 0.2.0.34 features several more security-related fixes. You should
12587 upgrade, especially if you run an exit relay (remote crash) or a
12588 directory authority (remote infinite loop), or you're on an older
12589 (pre-XP) or not-recently-patched Windows (remote exploit).
12591 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
12592 have many known flaws, and nobody should be using them. You should
12593 upgrade. If you're using a Linux or BSD and its packages are obsolete,
12594 stop using those packages and upgrade anyway.
12597 - Fix an infinite-loop bug on handling corrupt votes under certain
12598 circumstances. Bugfix on 0.2.0.8-alpha.
12599 - Fix a temporary DoS vulnerability that could be performed by
12600 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12601 - Avoid a potential crash on exit nodes when processing malformed
12602 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
12603 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12604 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12607 - Fix compilation on systems where time_t is a 64-bit integer.
12608 Patch from Matthias Drochner.
12609 - Don't consider expiring already-closed client connections. Fixes
12610 bug 893. Bugfix on 0.0.2pre20.
12613 Changes in version 0.2.1.12-alpha - 2009-02-08
12614 Tor 0.2.1.12-alpha features several more security-related fixes. You
12615 should upgrade, especially if you run an exit relay (remote crash) or
12616 a directory authority (remote infinite loop), or you're on an older
12617 (pre-XP) or not-recently-patched Windows (remote exploit). It also
12618 includes a big pile of minor bugfixes and cleanups.
12621 - Fix an infinite-loop bug on handling corrupt votes under certain
12622 circumstances. Bugfix on 0.2.0.8-alpha.
12623 - Fix a temporary DoS vulnerability that could be performed by
12624 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12625 - Avoid a potential crash on exit nodes when processing malformed
12626 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
12629 - Let controllers actually ask for the "clients_seen" event for
12630 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
12631 reported by Matt Edman.
12632 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
12634 - Fix a bug in address parsing that was preventing bridges or hidden
12635 service targets from being at IPv6 addresses.
12636 - Solve a bug that kept hardware crypto acceleration from getting
12637 enabled when accounting was turned on. Fixes bug 907. Bugfix on
12639 - Remove a bash-ism from configure.in to build properly on non-Linux
12640 platforms. Bugfix on 0.2.1.1-alpha.
12641 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
12642 headers. Bugfix on 0.2.0.10-alpha.
12643 - Don't consider expiring already-closed client connections. Fixes
12644 bug 893. Bugfix on 0.0.2pre20.
12645 - Fix another interesting corner-case of bug 891 spotted by rovv:
12646 Previously, if two hosts had different amounts of clock drift, and
12647 one of them created a new connection with just the wrong timing,
12648 the other might decide to deprecate the new connection erroneously.
12649 Bugfix on 0.1.1.13-alpha.
12650 - Resolve a very rare crash bug that could occur when the user forced
12651 a nameserver reconfiguration during the middle of a nameserver
12652 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
12653 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
12654 Bugfix on 0.2.1.7-alpha.
12655 - If we're using bridges and our network goes away, be more willing
12656 to forgive our bridges and try again when we get an application
12657 request. Bugfix on 0.2.0.x.
12660 - Support platforms where time_t is 64 bits long. (Congratulations,
12661 NetBSD!) Patch from Matthias Drochner.
12662 - Add a 'getinfo status/clients-seen' controller command, in case
12663 controllers want to hear clients_seen events but connect late.
12666 - Disable GCC's strict alias optimization by default, to avoid the
12667 likelihood of its introducing subtle bugs whenever our code violates
12668 the letter of C99's alias rules.
12671 Changes in version 0.2.0.33 - 2009-01-21
12672 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
12673 useful to users. It also finally fixes a bug where a relay or client
12674 that's been off for many days would take a long time to bootstrap.
12676 This update also fixes an important security-related bug reported by
12677 Ilja van Sprundel. You should upgrade. (We'll send out more details
12678 about the bug once people have had some time to upgrade.)
12681 - Fix a heap-corruption bug that may be remotely triggerable on
12682 some platforms. Reported by Ilja van Sprundel.
12685 - When a stream at an exit relay is in state "resolving" or
12686 "connecting" and it receives an "end" relay cell, the exit relay
12687 would silently ignore the end cell and not close the stream. If
12688 the client never closes the circuit, then the exit relay never
12689 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
12690 reported by "wood".
12691 - When sending CREATED cells back for a given circuit, use a 64-bit
12692 connection ID to find the right connection, rather than an addr:port
12693 combination. Now that we can have multiple OR connections between
12694 the same ORs, it is no longer possible to use addr:port to uniquely
12695 identify a connection.
12696 - Bridge relays that had DirPort set to 0 would stop fetching
12697 descriptors shortly after startup, and then briefly resume
12698 after a new bandwidth test and/or after publishing a new bridge
12699 descriptor. Bridge users that try to bootstrap from them would
12700 get a recent networkstatus but would get descriptors from up to
12701 18 hours earlier, meaning most of the descriptors were obsolete
12702 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12703 - Prevent bridge relays from serving their 'extrainfo' document
12704 to anybody who asks, now that extrainfo docs include potentially
12705 sensitive aggregated client geoip summaries. Bugfix on
12707 - If the cached networkstatus consensus is more than five days old,
12708 discard it rather than trying to use it. In theory it could be
12709 useful because it lists alternate directory mirrors, but in practice
12710 it just means we spend many minutes trying directory mirrors that
12711 are long gone from the network. Also discard router descriptors as
12712 we load them if they are more than five days old, since the onion
12713 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
12716 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12717 could make gcc generate non-functional binary search code. Bugfix
12719 - Build correctly on platforms without socklen_t.
12720 - Compile without warnings on solaris.
12721 - Avoid potential crash on internal error during signature collection.
12722 Fixes bug 864. Patch from rovv.
12723 - Correct handling of possible malformed authority signing key
12724 certificates with internal signature types. Fixes bug 880.
12725 Bugfix on 0.2.0.3-alpha.
12726 - Fix a hard-to-trigger resource leak when logging credential status.
12728 - When we can't initialize DNS because the network is down, do not
12729 automatically stop Tor from starting. Instead, we retry failed
12730 dns_init() every 10 minutes, and change the exit policy to reject
12731 *:* until one succeeds. Fixes bug 691.
12732 - Use 64 bits instead of 32 bits for connection identifiers used with
12733 the controller protocol, to greatly reduce risk of identifier reuse.
12734 - When we're choosing an exit node for a circuit, and we have
12735 no pending streams, choose a good general exit rather than one that
12736 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12737 - Fix another case of assuming, when a specific exit is requested,
12738 that we know more than the user about what hosts it allows.
12739 Fixes one case of bug 752. Patch from rovv.
12740 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12741 seconds. Warn the user if lower values are given in the
12742 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12743 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12744 user if lower values are given in the configuration. Bugfix on
12745 0.1.1.17-rc. Patch by Sebastian.
12746 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12747 the cache because we already had a v0 descriptor with the same ID.
12748 Bugfix on 0.2.0.18-alpha.
12749 - Fix a race condition when freeing keys shared between main thread
12750 and CPU workers that could result in a memory leak. Bugfix on
12751 0.1.0.1-rc. Fixes bug 889.
12752 - Send a valid END cell back when a client tries to connect to a
12753 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12754 840. Patch from rovv.
12755 - Check which hops rendezvous stream cells are associated with to
12756 prevent possible guess-the-streamid injection attacks from
12757 intermediate hops. Fixes another case of bug 446. Based on patch
12759 - If a broken client asks a non-exit router to connect somewhere,
12760 do not even do the DNS lookup before rejecting the connection.
12761 Fixes another case of bug 619. Patch from rovv.
12762 - When a relay gets a create cell it can't decrypt (e.g. because it's
12763 using the wrong onion key), we were dropping it and letting the
12764 client time out. Now actually answer with a destroy cell. Fixes
12765 bug 904. Bugfix on 0.0.2pre8.
12767 o Minor bugfixes (hidden services):
12768 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12769 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12772 - Report the case where all signatures in a detached set are rejected
12773 differently than the case where there is an error handling the
12775 - When we realize that another process has modified our cached
12776 descriptors, print out a more useful error message rather than
12777 triggering an assertion. Fixes bug 885. Patch from Karsten.
12778 - Implement the 0x20 hack to better resist DNS poisoning: set the
12779 case on outgoing DNS requests randomly, and reject responses that do
12780 not match the case correctly. This logic can be disabled with the
12781 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
12782 of servers that do not reliably preserve case in replies. See
12783 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12785 - Check DNS replies for more matching fields to better resist DNS
12787 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12788 compress cells, which are basically all encrypted, compressed, or
12792 Changes in version 0.2.1.11-alpha - 2009-01-20
12793 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
12794 week it will take a long time to bootstrap again" bug. It also fixes
12795 an important security-related bug reported by Ilja van Sprundel. You
12796 should upgrade. (We'll send out more details about the bug once people
12797 have had some time to upgrade.)
12800 - Fix a heap-corruption bug that may be remotely triggerable on
12801 some platforms. Reported by Ilja van Sprundel.
12804 - Discard router descriptors as we load them if they are more than
12805 five days old. Otherwise if Tor is off for a long time and then
12806 starts with cached descriptors, it will try to use the onion
12807 keys in those obsolete descriptors when building circuits. Bugfix
12808 on 0.2.0.x. Fixes bug 887.
12811 - Try to make sure that the version of Libevent we're running with
12812 is binary-compatible with the one we built with. May address bug
12814 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
12815 for bug 905. Bugfix on 0.2.1.7-alpha.
12816 - Add a new --enable-local-appdata configuration switch to change
12817 the default location of the datadir on win32 from APPDATA to
12818 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
12819 entirely. Patch from coderman.
12822 - Make outbound DNS packets respect the OutboundBindAddress setting.
12823 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
12824 - When our circuit fails at the first hop (e.g. we get a destroy
12825 cell back), avoid using that OR connection anymore, and also
12826 tell all the one-hop directory requests waiting for it that they
12827 should fail. Bugfix on 0.2.1.3-alpha.
12828 - In the torify(1) manpage, mention that tsocks will leak your
12832 Changes in version 0.2.1.10-alpha - 2009-01-06
12833 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
12834 would make the bridge relay not so useful if it had DirPort set to 0,
12835 and one that could let an attacker learn a little bit of information
12836 about the bridge's users), and a bug that would cause your Tor relay
12837 to ignore a circuit create request it can't decrypt (rather than reply
12838 with an error). It also fixes a wide variety of other bugs.
12841 - If the cached networkstatus consensus is more than five days old,
12842 discard it rather than trying to use it. In theory it could
12843 be useful because it lists alternate directory mirrors, but in
12844 practice it just means we spend many minutes trying directory
12845 mirrors that are long gone from the network. Helps bug 887 a bit;
12847 - Bridge relays that had DirPort set to 0 would stop fetching
12848 descriptors shortly after startup, and then briefly resume
12849 after a new bandwidth test and/or after publishing a new bridge
12850 descriptor. Bridge users that try to bootstrap from them would
12851 get a recent networkstatus but would get descriptors from up to
12852 18 hours earlier, meaning most of the descriptors were obsolete
12853 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12854 - Prevent bridge relays from serving their 'extrainfo' document
12855 to anybody who asks, now that extrainfo docs include potentially
12856 sensitive aggregated client geoip summaries. Bugfix on
12860 - New controller event "clients_seen" to report a geoip-based summary
12861 of which countries we've seen clients from recently. Now controllers
12862 like Vidalia can show bridge operators that they're actually making
12864 - Build correctly against versions of OpenSSL 0.9.8 or later built
12865 without support for deprecated functions.
12866 - Update to the "December 19 2008" ip-to-country file.
12868 o Minor bugfixes (on 0.2.0.x):
12869 - Authorities now vote for the Stable flag for any router whose
12870 weighted MTBF is at least 5 days, regardless of the mean MTBF.
12871 - Do not remove routers as too old if we do not have any consensus
12872 document. Bugfix on 0.2.0.7-alpha.
12873 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12874 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12875 - When an exit relay resolves a stream address to a local IP address,
12876 do not just keep retrying that same exit relay over and
12877 over. Instead, just close the stream. Addresses bug 872. Bugfix
12878 on 0.2.0.32. Patch from rovv.
12879 - If a hidden service sends us an END cell, do not consider
12880 retrying the connection; just close it. Patch from rovv.
12881 - When we made bridge authorities stop serving bridge descriptors over
12882 unencrypted links, we also broke DirPort reachability testing for
12883 bridges. So bridges with a non-zero DirPort were printing spurious
12884 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
12885 - When a relay gets a create cell it can't decrypt (e.g. because it's
12886 using the wrong onion key), we were dropping it and letting the
12887 client time out. Now actually answer with a destroy cell. Fixes
12888 bug 904. Bugfix on 0.0.2pre8.
12889 - Squeeze 2-5% out of client performance (according to oprofile) by
12890 improving the implementation of some policy-manipulation functions.
12892 o Minor bugfixes (on 0.2.1.x):
12893 - Make get_interface_address() function work properly again; stop
12894 guessing the wrong parts of our address as our address.
12895 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
12896 send on that circuit. Otherwise we might violate the proposal-110
12897 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
12899 - When we're sending non-EXTEND cells to the first hop in a circuit,
12900 for example to use an encrypted directory connection, we don't need
12901 to use RELAY_EARLY cells: the first hop knows what kind of cell
12902 it is, and nobody else can even see the cell type. Conserving
12903 RELAY_EARLY cells makes it easier to cannibalize circuits like
12905 - Stop logging nameserver addresses in reverse order.
12906 - If we are retrying a directory download slowly over and over, do
12907 not automatically give up after the 254th failure. Bugfix on
12909 - Resume reporting accurate "stream end" reasons to the local control
12910 port. They were lost in the changes for Proposal 148. Bugfix on
12913 o Deprecated and removed features:
12914 - The old "tor --version --version" command, which would print out
12915 the subversion "Id" of most of the source files, is now removed. It
12916 turned out to be less useful than we'd expected, and harder to
12919 o Code simplifications and refactoring:
12920 - Change our header file guard macros to be less likely to conflict
12921 with system headers. Adam Langley noticed that we were conflicting
12922 with log.h on Android.
12923 - Tool-assisted documentation cleanup. Nearly every function or
12924 static variable in Tor should have its own documentation now.
12927 Changes in version 0.2.1.9-alpha - 2008-12-25
12928 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
12930 o New directory authorities:
12931 - gabelmoo (the authority run by Karsten Loesing) now has a new
12935 - Never use a connection with a mismatched address to extend a
12936 circuit, unless that connection is canonical. A canonical
12937 connection is one whose address is authenticated by the router's
12938 identity key, either in a NETINFO cell or in a router descriptor.
12939 - Avoid a possible memory corruption bug when receiving hidden service
12940 descriptors. Bugfix on 0.2.1.6-alpha.
12943 - Fix a logic error that would automatically reject all but the first
12944 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
12945 part of bug 813/868. Bug spotted by coderman.
12946 - When a stream at an exit relay is in state "resolving" or
12947 "connecting" and it receives an "end" relay cell, the exit relay
12948 would silently ignore the end cell and not close the stream. If
12949 the client never closes the circuit, then the exit relay never
12950 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
12951 reported by "wood".
12952 - When we can't initialize DNS because the network is down, do not
12953 automatically stop Tor from starting. Instead, retry failed
12954 dns_init() every 10 minutes, and change the exit policy to reject
12955 *:* until one succeeds. Fixes bug 691.
12958 - Give a better error message when an overzealous init script says
12959 "sudo -u username tor --user username". Makes Bug 882 easier for
12961 - When a directory authority gives us a new guess for our IP address,
12962 log which authority we used. Hopefully this will help us debug
12963 the recent complaints about bad IP address guesses.
12964 - Detect svn revision properly when we're using git-svn.
12965 - Try not to open more than one descriptor-downloading connection
12966 to an authority at once. This should reduce load on directory
12967 authorities. Fixes bug 366.
12968 - Add cross-certification to newly generated certificates, so that
12969 a signing key is enough information to look up a certificate.
12970 Partial implementation of proposal 157.
12971 - Start serving certificates by <identity digest, signing key digest>
12972 pairs. Partial implementation of proposal 157.
12973 - Clients now never report any stream end reason except 'MISC'.
12974 Implements proposal 148.
12975 - On platforms with a maximum syslog string length, truncate syslog
12976 messages to that length ourselves, rather than relying on the
12977 system to do it for us.
12978 - Optimize out calls to time(NULL) that occur for every IO operation,
12979 or for every cell. On systems where time() is a slow syscall,
12980 this fix will be slightly helpful.
12981 - Exit servers can now answer resolve requests for ip6.arpa addresses.
12982 - When we download a descriptor that we then immediately (as
12983 a directory authority) reject, do not retry downloading it right
12984 away. Should save some bandwidth on authorities. Fix for bug
12985 888. Patch by Sebastian Hahn.
12986 - When a download gets us zero good descriptors, do not notify
12987 Tor that new directory information has arrived.
12988 - Avoid some nasty corner cases in the logic for marking connections
12989 as too old or obsolete or noncanonical for circuits. Partial
12992 o Minor features (controller):
12993 - New CONSENSUS_ARRIVED event to note when a new consensus has
12994 been fetched and validated.
12995 - When we realize that another process has modified our cached
12996 descriptors file, print out a more useful error message rather
12997 than triggering an assertion. Fixes bug 885. Patch from Karsten.
12998 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
12999 controllers to prevent SIGHUP from reloading the
13000 configuration. Fixes bug 856.
13003 - Resume using the correct "REASON=" stream when telling the
13004 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
13005 - When a canonical connection appears later in our internal list
13006 than a noncanonical one for a given OR ID, always use the
13007 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
13009 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13010 seconds. Warn the user if lower values are given in the
13011 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13012 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13013 user if lower values are given in the configuration. Bugfix on
13014 0.1.1.17-rc. Patch by Sebastian.
13015 - Fix a race condition when freeing keys shared between main thread
13016 and CPU workers that could result in a memory leak. Bugfix on
13017 0.1.0.1-rc. Fixes bug 889.
13019 o Minor bugfixes (hidden services):
13020 - Do not throw away existing introduction points on SIGHUP (bugfix on
13021 0.0.6pre1); also, do not stall hidden services because we're
13022 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
13023 by John Brooks. Patch by Karsten. Fixes bug 874.
13024 - Fix a memory leak when we decline to add a v2 rendezvous
13025 descriptor to the cache because we already had a v0 descriptor
13026 with the same ID. Bugfix on 0.2.0.18-alpha.
13028 o Deprecated and removed features:
13029 - RedirectExits has been removed. It was deprecated since
13031 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
13032 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
13033 - Cell pools are now always enabled; --disable-cell-pools is ignored.
13035 o Code simplifications and refactoring:
13036 - Rename the confusing or_is_obsolete field to the more appropriate
13037 is_bad_for_new_circs, and move it to or_connection_t where it
13039 - Move edge-only flags from connection_t to edge_connection_t: not
13040 only is this better coding, but on machines of plausible alignment,
13041 it should save 4-8 bytes per connection_t. "Every little bit helps."
13042 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
13043 for consistency; keep old option working for backward compatibility.
13044 - Simplify the code for finding connections to use for a circuit.
13047 Changes in version 0.2.1.8-alpha - 2008-12-08
13048 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
13049 builds better on unusual platforms like Solaris and old OS X, and
13050 fixes a variety of other issues.
13053 - New DirPortFrontPage option that takes an html file and publishes
13054 it as "/" on the DirPort. Now relay operators can provide a
13055 disclaimer without needing to set up a separate webserver. There's
13056 a sample disclaimer in contrib/tor-exit-notice.html.
13059 - When the client is choosing entry guards, now it selects at most
13060 one guard from a given relay family. Otherwise we could end up with
13061 all of our entry points into the network run by the same operator.
13062 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13065 - Fix a DOS opportunity during the voting signature collection process
13066 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13067 - Fix a possible segfault when establishing an exit connection. Bugfix
13071 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
13073 - Made Tor a little less aggressive about deleting expired
13074 certificates. Partial fix for bug 854.
13075 - Stop doing unaligned memory access that generated bus errors on
13076 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
13077 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
13078 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
13079 - Make USR2 log-level switch take effect immediately. Bugfix on
13081 - If one win32 nameserver fails to get added, continue adding the
13082 rest, and don't automatically fail.
13083 - Use fcntl() for locking when flock() is not available. Should fix
13084 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
13085 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13086 could make gcc generate non-functional binary search code. Bugfix
13088 - Build correctly on platforms without socklen_t.
13089 - Avoid potential crash on internal error during signature collection.
13090 Fixes bug 864. Patch from rovv.
13091 - Do not use C's stdio library for writing to log files. This will
13092 improve logging performance by a minute amount, and will stop
13093 leaking fds when our disk is full. Fixes bug 861.
13094 - Stop erroneous use of O_APPEND in cases where we did not in fact
13095 want to re-seek to the end of a file before every last write().
13096 - Correct handling of possible malformed authority signing key
13097 certificates with internal signature types. Fixes bug 880. Bugfix
13099 - Fix a hard-to-trigger resource leak when logging credential status.
13103 - Directory mirrors no longer fetch the v1 directory or
13104 running-routers files. They are obsolete, and nobody asks for them
13105 anymore. This is the first step to making v1 authorities obsolete.
13107 o Minor features (controller):
13108 - Return circuit purposes in response to GETINFO circuit-status. Fixes
13112 Changes in version 0.2.0.32 - 2008-11-20
13113 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
13114 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13115 a smaller security flaw that might allow an attacker to access local
13116 services, further improves hidden service performance, and fixes a
13117 variety of other issues.
13120 - The "User" and "Group" config options did not clear the
13121 supplementary group entries for the Tor process. The "User" option
13122 is now more robust, and we now set the groups to the specified
13123 user's primary group. The "Group" option is now ignored. For more
13124 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13125 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13126 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
13127 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13128 consistently obeyed: if an exit relay refuses a stream because its
13129 exit policy doesn't allow it, we would remember what IP address
13130 the relay said the destination address resolves to, even if it's
13131 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13134 - Fix a DOS opportunity during the voting signature collection process
13135 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13137 o Major bugfixes (hidden services):
13138 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13139 we were failing the whole hidden service request when the v0
13140 descriptor fetch fails, even if the v2 fetch is still pending and
13141 might succeed. Similarly, if the last v2 fetch fails, we were
13142 failing the whole hidden service request even if a v0 fetch is
13143 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13144 - When extending a circuit to a hidden service directory to upload a
13145 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13146 requests failed, because the router descriptor has not been
13147 downloaded yet. In these cases, do not attempt to upload the
13148 rendezvous descriptor, but wait until the router descriptor is
13149 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
13150 descriptor from a hidden service directory for which the router
13151 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
13155 - Fix several infrequent memory leaks spotted by Coverity.
13156 - When testing for libevent functions, set the LDFLAGS variable
13157 correctly. Found by Riastradh.
13158 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13159 bootstrapping with tunneled directory connections. Bugfix on
13160 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13161 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13162 and we know that server B rejects most-but-not all connections to
13163 port 80, we would previously reject the connection. Now, we assume
13164 the user knows what they were asking for. Fixes bug 752. Bugfix
13165 on 0.0.9rc5. Diagnosed by BarkerJr.
13166 - If we overrun our per-second write limits a little, count this as
13167 having used up our write allocation for the second, and choke
13168 outgoing directory writes. Previously, we had only counted this when
13169 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
13170 Bugfix on 0.2.0.x (??).
13171 - Remove the old v2 directory authority 'lefkada' from the default
13172 list. It has been gone for many months.
13173 - Stop doing unaligned memory access that generated bus errors on
13174 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
13175 - Make USR2 log-level switch take effect immediately. Bugfix on
13178 o Minor bugfixes (controller):
13179 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
13180 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
13183 Changes in version 0.2.1.7-alpha - 2008-11-08
13184 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
13185 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13186 a smaller security flaw that might allow an attacker to access local
13187 services, adds better defense against DNS poisoning attacks on exit
13188 relays, further improves hidden service performance, and fixes a
13189 variety of other issues.
13192 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13193 consistently obeyed: if an exit relay refuses a stream because its
13194 exit policy doesn't allow it, we would remember what IP address
13195 the relay said the destination address resolves to, even if it's
13196 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13197 - The "User" and "Group" config options did not clear the
13198 supplementary group entries for the Tor process. The "User" option
13199 is now more robust, and we now set the groups to the specified
13200 user's primary group. The "Group" option is now ignored. For more
13201 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13202 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13203 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
13204 - Do not use or believe expired v3 authority certificates. Patch
13205 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13208 - Now NodeFamily and MyFamily config options allow spaces in
13209 identity fingerprints, so it's easier to paste them in.
13210 Suggested by Lucky Green.
13211 - Implement the 0x20 hack to better resist DNS poisoning: set the
13212 case on outgoing DNS requests randomly, and reject responses that do
13213 not match the case correctly. This logic can be disabled with the
13214 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
13215 of servers that do not reliably preserve case in replies. See
13216 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13218 - Preserve case in replies to DNSPort requests in order to support
13219 the 0x20 hack for resisting DNS poisoning attacks.
13221 o Hidden service performance improvements:
13222 - When the client launches an introduction circuit, retry with a
13223 new circuit after 30 seconds rather than 60 seconds.
13224 - Launch a second client-side introduction circuit in parallel
13225 after a delay of 15 seconds (based on work by Christian Wilms).
13226 - Hidden services start out building five intro circuits rather
13227 than three, and when the first three finish they publish a service
13228 descriptor using those. Now we publish our service descriptor much
13229 faster after restart.
13232 - Minor fix in the warning messages when you're having problems
13233 bootstrapping; also, be more forgiving of bootstrap problems when
13234 we're still making incremental progress on a given bootstrap phase.
13235 - When we're choosing an exit node for a circuit, and we have
13236 no pending streams, choose a good general exit rather than one that
13237 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13238 - Send a valid END cell back when a client tries to connect to a
13239 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13240 840. Patch from rovv.
13241 - If a broken client asks a non-exit router to connect somewhere,
13242 do not even do the DNS lookup before rejecting the connection.
13243 Fixes another case of bug 619. Patch from rovv.
13244 - Fix another case of assuming, when a specific exit is requested,
13245 that we know more than the user about what hosts it allows.
13246 Fixes another case of bug 752. Patch from rovv.
13247 - Check which hops rendezvous stream cells are associated with to
13248 prevent possible guess-the-streamid injection attacks from
13249 intermediate hops. Fixes another case of bug 446. Based on patch
13251 - Avoid using a negative right-shift when comparing 32-bit
13252 addresses. Possible fix for bug 845 and bug 811.
13253 - Make the assert_circuit_ok() function work correctly on circuits that
13254 have already been marked for close.
13255 - Fix read-off-the-end-of-string error in unit tests when decoding
13256 introduction points.
13257 - Fix uninitialized size field for memory area allocation: may improve
13258 memory performance during directory parsing.
13259 - Treat duplicate certificate fetches as failures, so that we do
13260 not try to re-fetch an expired certificate over and over and over.
13261 - Do not say we're fetching a certificate when we'll in fact skip it
13262 because of a pending download.
13265 Changes in version 0.2.1.6-alpha - 2008-09-30
13266 Tor 0.2.1.6-alpha further improves performance and robustness of
13267 hidden services, starts work on supporting per-country relay selection,
13268 and fixes a variety of smaller issues.
13271 - Implement proposal 121: make it possible to build hidden services
13272 that only certain clients are allowed to connect to. This is
13273 enforced at several points, so that unauthorized clients are unable
13274 to send INTRODUCE cells to the service, or even (depending on the
13275 type of authentication) to learn introduction points. This feature
13276 raises the bar for certain kinds of active attacks against hidden
13277 services. Code by Karsten Loesing.
13278 - Relays now store and serve v2 hidden service descriptors by default,
13279 i.e., the new default value for HidServDirectoryV2 is 1. This is
13280 the last step in proposal 114, which aims to make hidden service
13281 lookups more reliable.
13282 - Start work to allow node restrictions to include country codes. The
13283 syntax to exclude nodes in a country with country code XX is
13284 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
13285 refinement to decide what config options should take priority if
13286 you ask to both use a particular node and exclude it.
13287 - Allow ExitNodes list to include IP ranges and country codes, just
13288 like the Exclude*Nodes lists. Patch from Robert Hogan.
13291 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
13292 Tor to fail to start if you had it configured to use a bridge
13293 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
13294 - When extending a circuit to a hidden service directory to upload a
13295 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13296 requests failed, because the router descriptor had not been
13297 downloaded yet. In these cases, we now wait until the router
13298 descriptor is downloaded, and then retry. Likewise, clients
13299 now skip over a hidden service directory if they don't yet have
13300 its router descriptor, rather than futilely requesting it and
13301 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
13303 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13304 we were failing the whole hidden service request when the v0
13305 descriptor fetch fails, even if the v2 fetch is still pending and
13306 might succeed. Similarly, if the last v2 fetch fails, we were
13307 failing the whole hidden service request even if a v0 fetch is
13308 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13309 - DNS replies need to have names matching their requests, but
13310 these names should be in the questions section, not necessarily
13311 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
13314 - Update to the "September 1 2008" ip-to-country file.
13315 - Allow ports 465 and 587 in the default exit policy again. We had
13316 rejected them in 0.1.0.15, because back in 2005 they were commonly
13317 misconfigured and ended up as spam targets. We hear they are better
13318 locked down these days.
13319 - Use a lockfile to make sure that two Tor processes are not
13320 simultaneously running with the same datadir.
13321 - Serve the latest v3 networkstatus consensus via the control
13322 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13323 - Better logging about stability/reliability calculations on directory
13325 - Drop the requirement to have an open dir port for storing and
13326 serving v2 hidden service descriptors.
13327 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13328 help debug WFU and MTBF calculations.
13329 - Implement most of Proposal 152: allow specialized servers to permit
13330 single-hop circuits, and clients to use those servers to build
13331 single-hop circuits when using a specialized controller. Patch
13332 from Josh Albrecht. Resolves feature request 768.
13333 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13334 people find host:port too confusing.
13335 - Make TrackHostExit mappings expire a while after their last use, not
13336 after their creation. Patch from Robert Hogan.
13337 - Provide circuit purposes along with circuit events to the controller.
13340 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
13342 - Fixed some memory leaks -- some quite frequent, some almost
13343 impossible to trigger -- based on results from Coverity.
13344 - When testing for libevent functions, set the LDFLAGS variable
13345 correctly. Found by Riastradh.
13346 - Fix an assertion bug in parsing policy-related options; possible fix
13348 - Catch and report a few more bootstrapping failure cases when Tor
13349 fails to establish a TCP connection. Cleanup on 0.2.1.x.
13350 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13351 bootstrapping with tunneled directory connections. Bugfix on
13352 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13353 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13354 and we know that server B rejects most-but-not all connections to
13355 port 80, we would previously reject the connection. Now, we assume
13356 the user knows what they were asking for. Fixes bug 752. Bugfix
13357 on 0.0.9rc5. Diagnosed by BarkerJr.
13358 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13359 service directories if they have no advertised dir port. Bugfix
13361 - If we overrun our per-second write limits a little, count this as
13362 having used up our write allocation for the second, and choke
13363 outgoing directory writes. Previously, we had only counted this when
13364 we had met our limits precisely. Fixes bug 824. Patch by rovv.
13365 Bugfix on 0.2.0.x (??).
13366 - Avoid a "0 divided by 0" calculation when calculating router uptime
13367 at directory authorities. Bugfix on 0.2.0.8-alpha.
13368 - Make DNS resolved controller events into "CLOSED", not
13369 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13371 - Fix a bug where an unreachable relay would establish enough
13372 reachability testing circuits to do a bandwidth test -- if
13373 we already have a connection to the middle hop of the testing
13374 circuit, then it could establish the last hop by using the existing
13375 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13376 circuits no longer use entry guards in 0.2.1.3-alpha.
13377 - If we have correct permissions on $datadir, we complain to stdout
13378 and fail to start. But dangerous permissions on
13379 $datadir/cached-status/ would cause us to open a log and complain
13380 there. Now complain to stdout and fail to start in both cases. Fixes
13381 bug 820, reported by seeess.
13382 - Remove the old v2 directory authority 'lefkada' from the default
13383 list. It has been gone for many months.
13385 o Code simplifications and refactoring:
13386 - Revise the connection_new functions so that a more typesafe variant
13387 exists. This will work better with Coverity, and let us find any
13388 actual mistakes we're making here.
13389 - Refactor unit testing logic so that dmalloc can be used sensibly
13390 with unit tests to check for memory leaks.
13391 - Move all hidden-service related fields from connection and circuit
13392 structure to substructures: this way they won't eat so much memory.
13395 Changes in version 0.2.0.31 - 2008-09-03
13396 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13397 a big bug we're seeing where in rare cases traffic from one Tor stream
13398 gets mixed into another stream, and fixes a variety of smaller issues.
13401 - Make sure that two circuits can never exist on the same connection
13402 with the same circuit ID, even if one is marked for close. This
13403 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
13404 - Relays now reject risky extend cells: if the extend cell includes
13405 a digest of all zeroes, or asks to extend back to the relay that
13406 sent the extend cell, tear down the circuit. Ideas suggested
13408 - If not enough of our entry guards are available so we add a new
13409 one, we might use the new one even if it overlapped with the
13410 current circuit's exit relay (or its family). Anonymity bugfix
13411 pointed out by rovv.
13414 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13415 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13416 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13417 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13418 - Pick size of default geoip filename string correctly on windows.
13419 Fixes bug 806. Bugfix on 0.2.0.30.
13420 - Make the autoconf script accept the obsolete --with-ssl-dir
13421 option as an alias for the actually-working --with-openssl-dir
13422 option. Fix the help documentation to recommend --with-openssl-dir.
13423 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13424 - When using the TransPort option on OpenBSD, and using the User
13425 option to change UID and drop privileges, make sure to open
13426 /dev/pf before dropping privileges. Fixes bug 782. Patch from
13427 Christopher Davis. Bugfix on 0.1.2.1-alpha.
13428 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13429 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13430 on the client side when connecting to a hidden service. Bugfix
13431 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13432 - When closing an application-side connection because its circuit is
13433 getting torn down, generate the stream event correctly. Bugfix on
13434 0.1.2.x. Anonymous patch.
13437 Changes in version 0.2.1.5-alpha - 2008-08-31
13438 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
13439 in a lot of the infrastructure for adding authorization to hidden
13440 services, lays the groundwork for having clients read their load
13441 balancing information out of the networkstatus consensus rather than
13442 the individual router descriptors, addresses two potential anonymity
13443 issues, and fixes a variety of smaller issues.
13446 - Convert many internal address representations to optionally hold
13448 - Generate and accept IPv6 addresses in many protocol elements.
13449 - Make resolver code handle nameservers located at ipv6 addresses.
13450 - Begin implementation of proposal 121 ("Client authorization for
13451 hidden services"): configure hidden services with client
13452 authorization, publish descriptors for them, and configure
13453 authorization data for hidden services at clients. The next
13454 step is to actually access hidden services that perform client
13456 - More progress toward proposal 141: Network status consensus
13457 documents and votes now contain bandwidth information for each
13458 router and a summary of that router's exit policy. Eventually this
13459 will be used by clients so that they do not have to download every
13460 known descriptor before building circuits.
13462 o Major bugfixes (on 0.2.0.x and before):
13463 - When sending CREATED cells back for a given circuit, use a 64-bit
13464 connection ID to find the right connection, rather than an addr:port
13465 combination. Now that we can have multiple OR connections between
13466 the same ORs, it is no longer possible to use addr:port to uniquely
13467 identify a connection.
13468 - Relays now reject risky extend cells: if the extend cell includes
13469 a digest of all zeroes, or asks to extend back to the relay that
13470 sent the extend cell, tear down the circuit. Ideas suggested
13472 - If not enough of our entry guards are available so we add a new
13473 one, we might use the new one even if it overlapped with the
13474 current circuit's exit relay (or its family). Anonymity bugfix
13475 pointed out by rovv.
13478 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13479 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13480 - When using the TransPort option on OpenBSD, and using the User
13481 option to change UID and drop privileges, make sure to open /dev/pf
13482 before dropping privileges. Fixes bug 782. Patch from Christopher
13483 Davis. Bugfix on 0.1.2.1-alpha.
13484 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13485 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13486 - Add a missing safe_str() call for a debug log message.
13487 - Use 64 bits instead of 32 bits for connection identifiers used with
13488 the controller protocol, to greatly reduce risk of identifier reuse.
13489 - Make the autoconf script accept the obsolete --with-ssl-dir
13490 option as an alias for the actually-working --with-openssl-dir
13491 option. Fix the help documentation to recommend --with-openssl-dir.
13492 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13495 - Rate-limit too-many-sockets messages: when they happen, they happen
13496 a lot. Resolves bug 748.
13497 - Resist DNS poisoning a little better by making sure that names in
13498 answer sections match.
13499 - Print the SOCKS5 error message string as well as the error code
13500 when a tor-resolve request fails. Patch from Jacob.
13503 Changes in version 0.2.1.4-alpha - 2008-08-04
13504 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
13507 - The address part of exit policies was not correctly written
13508 to router descriptors. This generated router descriptors that failed
13509 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
13511 - Tor triggered a false assert when extending a circuit to a relay
13512 but we already have a connection open to that relay. Noticed by
13513 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
13516 - Fix a hidden service logging bug: in some edge cases, the router
13517 descriptor of a previously picked introduction point becomes
13518 obsolete and we need to give up on it rather than continually
13519 complaining that it has become obsolete. Observed by xiando. Bugfix
13522 o Removed features:
13523 - Take out the TestVia config option, since it was a workaround for
13524 a bug that was fixed in Tor 0.1.1.21.
13527 Changes in version 0.2.1.3-alpha - 2008-08-03
13528 Tor 0.2.1.3-alpha implements most of the pieces to prevent
13529 infinite-length circuit attacks (see proposal 110); fixes a bug that
13530 might cause exit relays to corrupt streams they send back; allows
13531 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
13532 ExcludeExitNodes config options; and fixes a big pile of bugs.
13534 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
13535 - Send a bootstrap problem "warn" event on the first problem if the
13536 reason is NO_ROUTE (that is, our network is down).
13539 - Implement most of proposal 110: The first K cells to be sent
13540 along a circuit are marked as special "early" cells; only K "early"
13541 cells will be allowed. Once this code is universal, we can block
13542 certain kinds of DOS attack by requiring that EXTEND commands must
13543 be sent using an "early" cell.
13546 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13547 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13548 on the client side when connecting to a hidden service. Bugfix
13549 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13550 - Ensure that two circuits can never exist on the same connection
13551 with the same circuit ID, even if one is marked for close. This
13552 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13555 - When relays do their initial bandwidth measurement, don't limit
13556 to just our entry guards for the test circuits. Otherwise we tend
13557 to have multiple test circuits going through a single entry guard,
13558 which makes our bandwidth test less accurate. Fixes part of bug 654;
13559 patch contributed by Josh Albrecht.
13560 - Add an ExcludeExitNodes option so users can list a set of nodes
13561 that should be be excluded from the exit node position, but
13562 allowed elsewhere. Implements proposal 151.
13563 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
13564 ExcludeNodes and ExcludeExitNodes lists.
13565 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
13566 be more efficient. Formerly it was quadratic in the number of
13567 servers; now it should be linear. Fixes bug 509.
13568 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
13569 and n_conn_id_digest fields into a separate structure that's
13570 only needed when the circuit has not yet attached to an n_conn.
13573 - Change the contrib/tor.logrotate script so it makes the new
13574 logs as "_tor:_tor" rather than the default, which is generally
13575 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13576 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13577 warnings (occasionally), but it can also cause the compiler to
13578 eliminate error-checking code. Suggested by Peter Gutmann.
13579 - When a hidden service is giving up on an introduction point candidate
13580 that was not included in the last published rendezvous descriptor,
13581 don't reschedule publication of the next descriptor. Fixes bug 763.
13583 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
13584 HiddenServiceExcludeNodes as obsolete: they never worked properly,
13585 and nobody claims to be using them. Fixes bug 754. Bugfix on
13586 0.1.0.1-rc. Patch from Christian Wilms.
13587 - Fix a small alignment and memory-wasting bug on buffer chunks.
13590 o Minor bugfixes (controller):
13591 - When closing an application-side connection because its circuit
13592 is getting torn down, generate the stream event correctly.
13593 Bugfix on 0.1.2.x. Anonymous patch.
13595 o Removed features:
13596 - Remove all backward-compatibility code to support relays running
13597 versions of Tor so old that they no longer work at all on the
13601 Changes in version 0.2.0.30 - 2008-07-15
13603 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13604 warnings (occasionally), but it can also cause the compiler to
13605 eliminate error-checking code. Suggested by Peter Gutmann.
13608 Changes in version 0.2.0.29-rc - 2008-07-08
13609 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
13610 hidden-service performance bugs, and fixes a bunch of smaller bugs.
13613 - If you have more than one bridge but don't know their keys,
13614 you would only launch a request for the descriptor of the first one
13615 on your list. (Tor considered launching requests for the others, but
13616 found that it already had a connection on the way for $0000...0000
13617 so it didn't open another.) Bugfix on 0.2.0.x.
13618 - If you have more than one bridge but don't know their keys, and the
13619 connection to one of the bridges failed, you would cancel all
13620 pending bridge connections. (After all, they all have the same
13621 digest.) Bugfix on 0.2.0.x.
13622 - When a hidden service was trying to establish an introduction point,
13623 and Tor had built circuits preemptively for such purposes, we
13624 were ignoring all the preemptive circuits and launching a new one
13625 instead. Bugfix on 0.2.0.14-alpha.
13626 - When a hidden service was trying to establish an introduction point,
13627 and Tor *did* manage to reuse one of the preemptively built
13628 circuits, it didn't correctly remember which one it used,
13629 so it asked for another one soon after, until there were no
13630 more preemptive circuits, at which point it launched one from
13631 scratch. Bugfix on 0.0.9.x.
13632 - Make directory servers include the X-Your-Address-Is: http header in
13633 their responses even for begin_dir conns. Now clients who only
13634 ever use begin_dir connections still have a way to learn their IP
13635 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
13638 - Fix a macro/CPP interaction that was confusing some compilers:
13639 some GCCs don't like #if/#endif pairs inside macro arguments.
13641 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
13642 Fixes bug 704; fix from Steven Murdoch.
13643 - When opening /dev/null in finish_daemonize(), do not pass the
13644 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
13645 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
13646 - Correctly detect transparent proxy support on Linux hosts that
13647 require in.h to be included before netfilter_ipv4.h. Patch
13649 - Disallow session resumption attempts during the renegotiation
13650 stage of the v2 handshake protocol. Clients should never be trying
13651 session resumption at this point, but apparently some did, in
13652 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
13653 found by Geoff Goodell.
13656 Changes in version 0.2.1.2-alpha - 2008-06-20
13657 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
13658 make it easier to set up your own private Tor network; fixes several
13659 big bugs with using more than one bridge relay; fixes a big bug with
13660 offering hidden services quickly after Tor starts; and uses a better
13661 API for reporting potential bootstrapping problems to the controller.
13664 - New TestingTorNetwork config option to allow adjustment of
13665 previously constant values that, while reasonable, could slow
13666 bootstrapping. Implements proposal 135. Patch from Karsten.
13669 - If you have more than one bridge but don't know their digests,
13670 you would only learn a request for the descriptor of the first one
13671 on your list. (Tor considered launching requests for the others, but
13672 found that it already had a connection on the way for $0000...0000
13673 so it didn't open another.) Bugfix on 0.2.0.x.
13674 - If you have more than one bridge but don't know their digests,
13675 and the connection to one of the bridges failed, you would cancel
13676 all pending bridge connections. (After all, they all have the
13677 same digest.) Bugfix on 0.2.0.x.
13678 - When establishing a hidden service, introduction points that
13679 originate from cannibalized circuits are completely ignored and not
13680 included in rendezvous service descriptors. This might be another
13681 reason for delay in making a hidden service available. Bugfix
13682 from long ago (0.0.9.x?)
13685 - Allow OpenSSL to use dynamic locks if it wants.
13686 - When building a consensus, do not include routers that are down.
13687 This will cut down 30% to 40% on consensus size. Implements
13689 - In directory authorities' approved-routers files, allow
13690 fingerprints with or without space.
13691 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13692 controller can query our current bootstrap state in case it attaches
13693 partway through and wants to catch up.
13694 - Send an initial "Starting" bootstrap status event, so we have a
13695 state to start out in.
13698 - Asking for a conditional consensus at .../consensus/<fingerprints>
13699 would crash a dirserver if it did not already have a
13700 consensus. Bugfix on 0.2.1.1-alpha.
13701 - Clean up some macro/CPP interactions: some GCC versions don't like
13702 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
13705 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
13706 - Directory authorities shouldn't complain about bootstrapping
13707 problems just because they do a lot of reachability testing and
13708 some of the connection attempts fail.
13709 - Start sending "count" and "recommendation" key/value pairs in
13710 bootstrap problem status events, so the controller can hear about
13711 problems even before Tor decides they're worth reporting for sure.
13712 - If you're using bridges, generate "bootstrap problem" warnings
13713 as soon as you run out of working bridges, rather than waiting
13714 for ten failures -- which will never happen if you have less than
13716 - If we close our OR connection because there's been a circuit
13717 pending on it for too long, we were telling our bootstrap status
13718 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
13721 Changes in version 0.2.1.1-alpha - 2008-06-13
13722 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
13723 were making the Tor process bloat especially on Linux; makes our TLS
13724 handshake blend in better; sends "bootstrap phase" status events to
13725 the controller, so it can keep the user informed of progress (and
13726 problems) fetching directory information and establishing circuits;
13727 and adds a variety of smaller features.
13730 - More work on making our TLS handshake blend in: modify the list
13731 of ciphers advertised by OpenSSL in client mode to even more
13732 closely resemble a common web browser. We cheat a little so that
13733 we can advertise ciphers that the locally installed OpenSSL doesn't
13735 - Start sending "bootstrap phase" status events to the controller,
13736 so it can keep the user informed of progress fetching directory
13737 information and establishing circuits. Also inform the controller
13738 if we think we're stuck at a particular bootstrap phase. Implements
13740 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13741 cross-platform entropy collection again. We used to use it, then
13742 stopped using it because of a bug that could crash systems that
13743 called RAND_poll when they had a lot of fds open. It looks like the
13744 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13745 at startup, and to call RAND_poll() when we reseed later only if
13746 we have a non-buggy OpenSSL version.
13749 - When we choose to abandon a new entry guard because we think our
13750 older ones might be better, close any circuits pending on that
13751 new entry guard connection. This fix should make us recover much
13752 faster when our network is down and then comes back. Bugfix on
13753 0.1.2.8-beta; found by lodger.
13755 o Memory fixes and improvements:
13756 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13757 to avoid unused RAM in buffer chunks and memory pools.
13758 - Speed up parsing and cut down on memory fragmentation by using
13759 stack-style allocations for parsing directory objects. Previously,
13760 this accounted for over 40% of allocations from within Tor's code
13761 on a typical directory cache.
13762 - Use a Bloom filter rather than a digest-based set to track which
13763 descriptors we need to keep around when we're cleaning out old
13764 router descriptors. This speeds up the computation significantly,
13765 and may reduce fragmentation.
13766 - Reduce the default smartlist size from 32 to 16; it turns out that
13767 most smartlists hold around 8-12 elements tops.
13768 - Make dumpstats() log the fullness and size of openssl-internal
13770 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13771 patch to their OpenSSL, turn it on to save memory on servers. This
13772 patch will (with any luck) get included in a mainline distribution
13774 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13775 compress cells, which are basically all encrypted, compressed,
13779 - Stop reloading the router list from disk for no reason when we
13780 run out of reachable directory mirrors. Once upon a time reloading
13781 it would set the 'is_running' flag back to 1 for them. It hasn't
13782 done that for a long time.
13783 - In very rare situations new hidden service descriptors were
13784 published earlier than 30 seconds after the last change to the
13785 service. (We currently think that a hidden service descriptor
13786 that's been stable for 30 seconds is worth publishing.)
13789 - Allow separate log levels to be configured for different logging
13790 domains. For example, this allows one to log all notices, warnings,
13791 or errors, plus all memory management messages of level debug or
13792 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13793 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13794 and stop using a warning that had become unfixably verbose under
13796 - New --hush command-line option similar to --quiet. While --quiet
13797 disables all logging to the console on startup, --hush limits the
13798 output to messages of warning and error severity.
13799 - Servers support a new URL scheme for consensus downloads that
13800 allows the client to specify which authorities are trusted.
13801 The server then only sends the consensus if the client will trust
13802 it. Otherwise a 404 error is sent back. Clients use this
13803 new scheme when the server supports it (meaning it's running
13804 0.2.1.1-alpha or later). Implements proposal 134.
13805 - New configure/torrc options (--enable-geoip-stats,
13806 DirRecordUsageByCountry) to record how many IPs we've served
13807 directory info to in each country code, how many status documents
13808 total we've sent to each country code, and what share of the total
13809 directory requests we should expect to see.
13810 - Use the TLS1 hostname extension to more closely resemble browser
13812 - Lots of new unit tests.
13813 - Add a macro to implement the common pattern of iterating through
13814 two parallel lists in lockstep.
13817 Changes in version 0.2.0.28-rc - 2008-06-13
13818 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
13819 performance bug, and fixes a bunch of smaller bugs.
13822 - Fix a bug where, when we were choosing the 'end stream reason' to
13823 put in our relay end cell that we send to the exit relay, Tor
13824 clients on Windows were sometimes sending the wrong 'reason'. The
13825 anonymity problem is that exit relays may be able to guess whether
13826 the client is running Windows, thus helping partition the anonymity
13827 set. Down the road we should stop sending reasons to exit relays,
13828 or otherwise prevent future versions of this bug.
13831 - While setting up a hidden service, some valid introduction circuits
13832 were overlooked and abandoned. This might be the reason for
13833 the long delay in making a hidden service available. Bugfix on
13837 - Update to the "June 9 2008" ip-to-country file.
13838 - Run 'make test' as part of 'make dist', so we stop releasing so
13839 many development snapshots that fail their unit tests.
13842 - When we're checking if we have enough dir info for each relay
13843 to begin establishing circuits, make sure that we actually have
13844 the descriptor listed in the consensus, not just any descriptor.
13846 - Bridge relays no longer print "xx=0" in their extrainfo document
13847 for every single country code in the geoip db. Bugfix on
13849 - Only warn when we fail to load the geoip file if we were planning to
13850 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
13851 - If we change our MaxAdvertisedBandwidth and then reload torrc,
13852 Tor won't realize it should publish a new relay descriptor. Fixes
13853 bug 688, reported by mfr. Bugfix on 0.1.2.x.
13854 - When we haven't had any application requests lately, don't bother
13855 logging that we have expired a bunch of descriptors. Bugfix
13857 - Make relay cells written on a connection count as non-padding when
13858 tracking how long a connection has been in use. Bugfix on
13859 0.2.0.1-alpha. Spotted by lodger.
13860 - Fix unit tests in 0.2.0.27-rc.
13861 - Fix compile on Windows.
13864 Changes in version 0.2.0.27-rc - 2008-06-03
13865 Tor 0.2.0.27-rc adds a few features we left out of the earlier
13866 release candidates. In particular, we now include an IP-to-country
13867 GeoIP database, so controllers can easily look up what country a
13868 given relay is in, and so bridge relays can give us some sanitized
13869 summaries about which countries are making use of bridges. (See proposal
13870 126-geoip-fetching.txt for details.)
13873 - Include an IP-to-country GeoIP file in the tarball, so bridge
13874 relays can report sanitized summaries of the usage they're seeing.
13877 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
13878 Robert Hogan. Fixes the first part of bug 681.
13879 - Make bridge authorities never serve extrainfo docs.
13880 - Add support to detect Libevent versions in the 1.4.x series
13882 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
13883 - Include a new contrib/tor-exit-notice.html file that exit relay
13884 operators can put on their website to help reduce abuse queries.
13887 - When tunneling an encrypted directory connection, and its first
13888 circuit fails, do not leave it unattached and ask the controller
13889 to deal. Fixes the second part of bug 681.
13890 - Make bridge authorities correctly expire old extrainfo documents
13894 Changes in version 0.2.0.26-rc - 2008-05-13
13895 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
13896 in Debian's OpenSSL packages. All users running any 0.2.0.x version
13897 should upgrade, whether they're running Debian or not.
13899 o Major security fixes:
13900 - Use new V3 directory authority keys on the tor26, gabelmoo, and
13901 moria1 V3 directory authorities. The old keys were generated with
13902 a vulnerable version of Debian's OpenSSL package, and must be
13903 considered compromised. Other authorities' keys were not generated
13904 with an affected version of OpenSSL.
13907 - List authority signatures as "unrecognized" based on DirServer
13908 lines, not on cert cache. Bugfix on 0.2.0.x.
13911 - Add a new V3AuthUseLegacyKey option to make it easier for
13912 authorities to change their identity keys if they have to.
13915 Changes in version 0.2.0.25-rc - 2008-04-23
13916 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
13919 - Remember to initialize threading before initializing logging.
13920 Otherwise, many BSD-family implementations will crash hard on
13921 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
13924 - Authorities correctly free policies on bad servers on
13925 exit. Fixes bug 672. Bugfix on 0.2.0.x.
13928 Changes in version 0.2.0.24-rc - 2008-04-22
13929 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
13930 v3 directory authority, makes relays with dynamic IP addresses and no
13931 DirPort notice more quickly when their IP address changes, fixes a few
13932 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
13934 o New directory authorities:
13935 - Take lefkada out of the list of v3 directory authorities, since
13936 it has been down for months.
13937 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
13941 - Detect address changes more quickly on non-directory mirror
13942 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
13944 o Minor features (security):
13945 - Reject requests for reverse-dns lookup of names that are in
13946 a private address space. Patch from lodger.
13947 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
13950 o Minor bugfixes (crashes):
13951 - Avoid a rare assert that can trigger when Tor doesn't have much
13952 directory information yet and it tries to fetch a v2 hidden
13953 service descriptor. Fixes bug 651, reported by nwf.
13954 - Initialize log mutex before initializing dmalloc. Otherwise,
13955 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
13956 - Use recursive pthread mutexes in order to avoid deadlock when
13957 logging debug-level messages to a controller. Bug spotted by nwf,
13958 bugfix on 0.2.0.16-alpha.
13960 o Minor bugfixes (resource management):
13961 - Keep address policies from leaking memory: start their refcount
13962 at 1, not 2. Bugfix on 0.2.0.16-alpha.
13963 - Free authority certificates on exit, so they don't look like memory
13964 leaks. Bugfix on 0.2.0.19-alpha.
13965 - Free static hashtables for policy maps and for TLS connections on
13966 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
13967 - Avoid allocating extra space when computing consensuses on 64-bit
13968 platforms. Bug spotted by aakova.
13970 o Minor bugfixes (misc):
13971 - Do not read the configuration file when we've only been told to
13972 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
13973 based on patch from Sebastian Hahn.
13974 - Exit relays that are used as a client can now reach themselves
13975 using the .exit notation, rather than just launching an infinite
13976 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
13977 - When attempting to open a logfile fails, tell us why.
13978 - Fix a dumb bug that was preventing us from knowing that we should
13979 preemptively build circuits to handle expected directory requests.
13980 Fixes bug 660. Bugfix on 0.1.2.x.
13981 - Warn less verbosely about clock skew from netinfo cells from
13982 untrusted sources. Fixes bug 663.
13983 - Make controller stream events for DNS requests more consistent,
13984 by adding "new stream" events for DNS requests, and removing
13985 spurious "stream closed" events" for cached reverse resolves.
13986 Patch from mwenge. Fixes bug 646.
13987 - Correctly notify one-hop connections when a circuit build has
13988 failed. Possible fix for bug 669. Found by lodger.
13991 Changes in version 0.2.0.23-rc - 2008-03-24
13992 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
13993 makes bootstrapping faster if the first directory mirror you contact
13994 is down. The bundles also include the new Vidalia 0.1.2 release.
13997 - When a tunneled directory request is made to a directory server
13998 that's down, notice after 30 seconds rather than 120 seconds. Also,
13999 fail any begindir streams that are pending on it, so they can
14000 retry elsewhere. This was causing multi-minute delays on bootstrap.
14003 Changes in version 0.2.0.22-rc - 2008-03-18
14004 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
14005 enables encrypted directory connections by default for non-relays, fixes
14006 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
14007 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
14010 - Enable encrypted directory connections by default for non-relays,
14011 so censor tools that block Tor directory connections based on their
14012 plaintext patterns will no longer work. This means Tor works in
14013 certain censored countries by default again.
14016 - Make sure servers always request certificates from clients during
14017 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
14018 - Do not enter a CPU-eating loop when a connection is closed in
14019 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
14020 diagnosed by lodger; bugfix on 0.2.0.20-rc.
14021 - Fix assertion failure that could occur when a blocked circuit
14022 became unblocked, and it had pending client DNS requests. Bugfix
14023 on 0.2.0.1-alpha. Fixes bug 632.
14025 o Minor bugfixes (on 0.1.2.x):
14026 - Generate "STATUS_SERVER" events rather than misspelled
14027 "STATUS_SEVER" events. Caught by mwenge.
14028 - When counting the number of bytes written on a TLS connection,
14029 look at the BIO actually used for writing to the network, not
14030 at the BIO used (sometimes) to buffer data for the network.
14031 Looking at different BIOs could result in write counts on the
14032 order of ULONG_MAX. Fixes bug 614.
14033 - On Windows, correctly detect errors when listing the contents of
14034 a directory. Fix from lodger.
14036 o Minor bugfixes (on 0.2.0.x):
14037 - Downgrade "sslv3 alert handshake failure" message to INFO.
14038 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
14039 left BandwidthRate and BandwidthBurst at the default, we would be
14040 silently limited by those defaults. Now raise them to match the
14041 RelayBandwidth* values.
14042 - Fix the SVK version detection logic to work correctly on a branch.
14043 - Make --enable-openbsd-malloc work correctly on Linux with alpha
14044 CPUs. Fixes bug 625.
14045 - Logging functions now check that the passed severity is sane.
14046 - Use proper log levels in the testsuite call of
14047 get_interface_address6().
14048 - When using a nonstandard malloc, do not use the platform values for
14049 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
14050 - Make the openbsd malloc code use 8k pages on alpha CPUs and
14052 - Detect mismatched page sizes when using --enable-openbsd-malloc.
14053 - Avoid double-marked-for-close warning when certain kinds of invalid
14054 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
14055 for bug 617. Bugfix on 0.2.0.1-alpha.
14056 - Make sure that the "NULL-means-reject *:*" convention is followed by
14057 all the policy manipulation functions, avoiding some possible crash
14058 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
14059 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
14060 actually works, and doesn't warn about every single reverse lookup.
14061 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
14064 - Only log guard node status when guard node status has changed.
14065 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
14066 make "INFO" 75% less verbose.
14069 Changes in version 0.2.0.21-rc - 2008-03-02
14070 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
14071 makes Tor work well with Vidalia again, fixes a rare assert bug,
14072 and fixes a pair of more minor bugs. The bundles also include Vidalia
14073 0.1.0 and Torbutton 1.1.16.
14076 - The control port should declare that it requires password auth
14077 when HashedControlSessionPassword is set too. Patch from Matt Edman;
14078 bugfix on 0.2.0.20-rc. Fixes bug 615.
14079 - Downgrade assert in connection_buckets_decrement() to a log message.
14080 This may help us solve bug 614, and in any case will make its
14081 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
14082 - We were sometimes miscounting the number of bytes read from the
14083 network, causing our rate limiting to not be followed exactly.
14084 Bugfix on 0.2.0.16-alpha. Reported by lodger.
14087 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
14088 OpenSSL versions should have been working fine. Diagnosis and patch
14089 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
14090 Bugfix on 0.2.0.20-rc.
14093 Changes in version 0.2.0.20-rc - 2008-02-24
14094 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
14095 makes more progress towards normalizing Tor's TLS handshake, makes
14096 hidden services work better again, helps relays bootstrap if they don't
14097 know their IP address, adds optional support for linking in openbsd's
14098 allocator or tcmalloc, allows really fast relays to scale past 15000
14099 sockets, and fixes a bunch of minor bugs reported by Veracode.
14102 - Enable the revised TLS handshake based on the one designed by
14103 Steven Murdoch in proposal 124, as revised in proposal 130. It
14104 includes version negotiation for OR connections as described in
14105 proposal 105. The new handshake is meant to be harder for censors
14106 to fingerprint, and it adds the ability to detect certain kinds of
14107 man-in-the-middle traffic analysis attacks. The version negotiation
14108 feature will allow us to improve Tor's link protocol more safely
14110 - Choose which bridge to use proportional to its advertised bandwidth,
14111 rather than uniformly at random. This should speed up Tor for
14112 bridge users. Also do this for people who set StrictEntryNodes.
14113 - When a TrackHostExits-chosen exit fails too many times in a row,
14114 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
14117 - Resolved problems with (re-)fetching hidden service descriptors.
14118 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
14119 and 0.2.0.19-alpha.
14120 - If we only ever used Tor for hidden service lookups or posts, we
14121 would stop building circuits and start refusing connections after
14122 24 hours, since we falsely believed that Tor was dormant. Reported
14123 by nwf; bugfix on 0.1.2.x.
14124 - Servers that don't know their own IP address should go to the
14125 authorities for their first directory fetch, even if their DirPort
14126 is off or if they don't know they're reachable yet. This will help
14127 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
14128 - When counting the number of open sockets, count not only the number
14129 of sockets we have received from the socket() call, but also
14130 the number we've gotten from accept() and socketpair(). This bug
14131 made us fail to count all sockets that we were using for incoming
14132 connections. Bugfix on 0.2.0.x.
14133 - Fix code used to find strings within buffers, when those strings
14134 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
14135 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
14136 - Add a new __HashedControlSessionPassword option for controllers
14137 to use for one-off session password hashes that shouldn't get
14138 saved to disk by SAVECONF --- Vidalia users were accumulating a
14139 pile of HashedControlPassword lines in their torrc files, one for
14140 each time they had restarted Tor and then clicked Save. Make Tor
14141 automatically convert "HashedControlPassword" to this new option but
14142 only when it's given on the command line. Partial fix for bug 586.
14144 o Minor features (performance):
14145 - Tune parameters for cell pool allocation to minimize amount of
14147 - Add OpenBSD malloc code from phk as an optional malloc
14148 replacement on Linux: some glibc libraries do very poorly
14149 with Tor's memory allocation patterns. Pass
14150 --enable-openbsd-malloc to get the replacement malloc code.
14151 - Add a --with-tcmalloc option to the configure script to link
14152 against tcmalloc (if present). Does not yet search for
14153 non-system include paths.
14154 - Stop imposing an arbitrary maximum on the number of file descriptors
14155 used for busy servers. Bug reported by Olaf Selke; patch from
14158 o Minor features (other):
14159 - When SafeLogging is disabled, log addresses along with all TLS
14161 - When building with --enable-gcc-warnings, check for whether Apple's
14162 warning "-Wshorten-64-to-32" is available.
14163 - Add a --passphrase-fd argument to the tor-gencert command for
14166 o Minor bugfixes (memory leaks and code problems):
14167 - We were leaking a file descriptor if Tor started with a zero-length
14168 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
14169 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14171 - We were comparing the raw BridgePassword entry with a base64'ed
14172 version of it, when handling a "/tor/networkstatus-bridges"
14173 directory request. Now compare correctly. Noticed by Veracode.
14174 - Recover from bad tracked-since value in MTBF-history file.
14175 Should fix bug 537.
14176 - Alter the code that tries to recover from unhandled write
14177 errors, to not try to flush onto a socket that's given us
14178 unhandled errors. Bugfix on 0.1.2.x.
14179 - Make Unix controlsockets work correctly on OpenBSD. Patch from
14180 tup. Bugfix on 0.2.0.3-alpha.
14182 o Minor bugfixes (other):
14183 - If we have an extra-info document for our server, always make
14184 it available on the control port, even if we haven't gotten
14185 a copy of it from an authority yet. Patch from mwenge.
14186 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
14187 - Directory mirrors no longer include a guess at the client's IP
14188 address if the connection appears to be coming from the same /24
14189 network; it was producing too many wrong guesses.
14190 - Make the new hidden service code respect the SafeLogging setting.
14191 Bugfix on 0.2.0.x. Patch from Karsten.
14192 - When starting as an authority, do not overwrite all certificates
14193 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
14194 - If we're trying to flush the last bytes on a connection (for
14195 example, when answering a directory request), reset the
14196 time-to-give-up timeout every time we manage to write something
14197 on the socket. Bugfix on 0.1.2.x.
14198 - Change the behavior of "getinfo status/good-server-descriptor"
14199 so it doesn't return failure when any authority disappears.
14200 - Even though the man page said that "TrackHostExits ." should
14201 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
14202 - Report TLS "zero return" case as a "clean close" and "IO error"
14203 as a "close". Stop calling closes "unexpected closes": existing
14204 Tors don't use SSL_close(), so having a connection close without
14205 the TLS shutdown handshake is hardly unexpected.
14206 - Send NAMESERVER_STATUS messages for a single failed nameserver
14209 o Code simplifications and refactoring:
14210 - Remove the tor_strpartition function: its logic was confused,
14211 and it was only used for one thing that could be implemented far
14215 Changes in version 0.2.0.19-alpha - 2008-02-09
14216 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
14217 handshake, makes path selection for relays more secure and IP address
14218 guessing more robust, and generally fixes a lot of bugs in preparation
14219 for calling the 0.2.0 branch stable.
14222 - Do not include recognizeable strings in the commonname part of
14223 Tor's x509 certificates.
14226 - If we're a relay, avoid picking ourselves as an introduction point,
14227 a rendezvous point, or as the final hop for internal circuits. Bug
14228 reported by taranis and lodger. Bugfix on 0.1.2.x.
14229 - Patch from "Andrew S. Lists" to catch when we contact a directory
14230 mirror at IP address X and he says we look like we're coming from
14231 IP address X. Bugfix on 0.1.2.x.
14233 o Minor features (security):
14234 - Be more paranoid about overwriting sensitive memory on free(),
14235 as a defensive programming tactic to ensure forward secrecy.
14237 o Minor features (directory authority):
14238 - Actually validate the options passed to AuthDirReject,
14239 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14240 - Reject router descriptors with out-of-range bandwidthcapacity or
14241 bandwidthburst values.
14243 o Minor features (controller):
14244 - Reject controller commands over 1MB in length. This keeps rogue
14245 processes from running us out of memory.
14247 o Minor features (misc):
14248 - Give more descriptive well-formedness errors for out-of-range
14249 hidden service descriptor/protocol versions.
14250 - Make memory debugging information describe more about history
14251 of cell allocation, so we can help reduce our memory use.
14253 o Deprecated features (controller):
14254 - The status/version/num-versioning and status/version/num-concurring
14255 GETINFO options are no longer useful in the v3 directory protocol:
14256 treat them as deprecated, and warn when they're used.
14259 - When our consensus networkstatus has been expired for a while, stop
14260 being willing to build circuits using it. Fixes bug 401. Bugfix
14262 - Directory caches now fetch certificates from all authorities
14263 listed in a networkstatus consensus, even when they do not
14264 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
14265 - When connecting to a bridge without specifying its key, insert
14266 the connection into the identity-to-connection map as soon as
14267 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
14268 - Detect versions of OS X where malloc_good_size() is present in the
14269 library but never actually declared. Resolves bug 587. Bugfix
14271 - Stop incorrectly truncating zlib responses to directory authority
14272 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
14273 - Stop recommending that every server operator send mail to tor-ops.
14274 Resolves bug 597. Bugfix on 0.1.2.x.
14275 - Don't trigger an assert if we start a directory authority with a
14276 private IP address (like 127.0.0.1).
14277 - Avoid possible failures when generating a directory with routers
14278 with over-long versions strings, or too many flags set. Bugfix
14280 - If an attempt to launch a DNS resolve request over the control
14281 port fails because we have overrun the limit on the number of
14282 connections, tell the controller that the request has failed.
14283 - Avoid using too little bandwidth when our clock skips a few
14284 seconds. Bugfix on 0.1.2.x.
14285 - Fix shell error when warning about missing packages in configure
14286 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
14287 - Do not become confused when receiving a spurious VERSIONS-like
14288 cell from a confused v1 client. Bugfix on 0.2.0.x.
14289 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
14290 introduction points for a hidden service have failed. Patch from
14291 Karsten Loesing. Bugfix on 0.2.0.x.
14293 o Code simplifications and refactoring:
14294 - Remove some needless generality from cpuworker code, for improved
14296 - Stop overloading the circuit_t.onionskin field for both "onionskin
14297 from a CREATE cell that we are waiting for a cpuworker to be
14298 assigned" and "onionskin from an EXTEND cell that we are going to
14299 send to an OR as soon as we are connected". Might help with bug 600.
14300 - Add an in-place version of aes_crypt() so that we can avoid doing a
14301 needless memcpy() call on each cell payload.
14304 Changes in version 0.2.0.18-alpha - 2008-01-25
14305 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
14306 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
14307 that can warn or reject connections to ports generally associated with
14308 vulnerable-plaintext protocols.
14310 o New directory authorities:
14311 - Set up dannenberg (run by CCC) as the sixth v3 directory
14315 - Fix a major memory leak when attempting to use the v2 TLS
14316 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
14317 - We accidentally enabled the under-development v2 TLS handshake
14318 code, which was causing log entries like "TLS error while
14319 renegotiating handshake". Disable it again. Resolves bug 590.
14320 - We were computing the wrong Content-Length: header for directory
14321 responses that need to be compressed on the fly, causing clients
14322 asking for those items to always fail. Bugfix on 0.2.0.x; partially
14326 - Avoid going directly to the directory authorities even if you're a
14327 relay, if you haven't found yourself reachable yet or if you've
14328 decided not to advertise your dirport yet. Addresses bug 556.
14329 - If we've gone 12 hours since our last bandwidth check, and we
14330 estimate we have less than 50KB bandwidth capacity but we could
14331 handle more, do another bandwidth test.
14332 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14333 Tor can warn and/or refuse connections to ports commonly used with
14334 vulnerable-plaintext protocols. Currently we warn on ports 23,
14335 109, 110, and 143, but we don't reject any.
14338 - When we setconf ClientOnly to 1, close any current OR and Dir
14339 listeners. Reported by mwenge.
14340 - When we get a consensus that's been signed by more people than
14341 we expect, don't log about it; it's not a big deal. Reported
14345 - Don't answer "/tor/networkstatus-bridges" directory requests if
14346 the request isn't encrypted.
14347 - Make "ClientOnly 1" config option disable directory ports too.
14348 - Patches from Karsten Loesing to make v2 hidden services more
14349 robust: work even when there aren't enough HSDir relays available;
14350 retry when a v2 rend desc fetch fails; but don't retry if we
14351 already have a usable v0 rend desc.
14354 Changes in version 0.2.0.17-alpha - 2008-01-17
14355 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
14358 - Make the tor-gencert man page get included correctly in the tarball.
14361 Changes in version 0.2.0.16-alpha - 2008-01-17
14362 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
14363 Loesing, and generally cleans up a lot of features and minor bugs.
14365 o New directory authorities:
14366 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
14369 o Major performance improvements:
14370 - Switch our old ring buffer implementation for one more like that
14371 used by free Unix kernels. The wasted space in a buffer with 1mb
14372 of data will now be more like 8k than 1mb. The new implementation
14373 also avoids realloc();realloc(); patterns that can contribute to
14374 memory fragmentation.
14377 - Configuration files now accept C-style strings as values. This
14378 helps encode characters not allowed in the current configuration
14379 file format, such as newline or #. Addresses bug 557.
14380 - Although we fixed bug 539 (where servers would send HTTP status 503
14381 responses _and_ send a body too), there are still servers out
14382 there that haven't upgraded. Therefore, make clients parse such
14383 bodies when they receive them.
14384 - When we're not serving v2 directory information, there is no reason
14385 to actually keep any around. Remove the obsolete files and directory
14386 on startup if they are very old and we aren't going to serve them.
14388 o Minor performance improvements:
14389 - Reference-count and share copies of address policy entries; only 5%
14390 of them were actually distinct.
14391 - Never walk through the list of logs if we know that no log is
14392 interested in a given message.
14395 - When an authority has not signed a consensus, do not try to
14396 download a nonexistent "certificate with key 00000000". Bugfix
14397 on 0.2.0.x. Fixes bug 569.
14398 - Fix a rare assert error when we're closing one of our threads:
14399 use a mutex to protect the list of logs, so we never write to the
14400 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
14401 bug 575, which is kind of the revenge of bug 222.
14402 - Patch from Karsten Loesing to complain less at both the client
14403 and the relay when a relay used to have the HSDir flag but doesn't
14404 anymore, and we try to upload a hidden service descriptor.
14405 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
14407 - Do not try to download missing certificates until we have tried
14408 to check our fallback consensus. Fixes bug 583.
14409 - Make bridges round reported GeoIP stats info up to the nearest
14410 estimate, not down. Now we can distinguish between "0 people from
14411 this country" and "1 person from this country".
14412 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
14413 - Avoid possible segfault if key generation fails in
14414 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
14415 - Avoid segfault in the case where a badly behaved v2 versioning
14416 directory sends a signed networkstatus with missing client-versions.
14418 - Avoid segfaults on certain complex invocations of
14419 router_get_by_hexdigest(). Bugfix on 0.1.2.
14420 - Correct bad index on array access in parse_http_time(). Bugfix
14422 - Fix possible bug in vote generation when server versions are present
14423 but client versions are not.
14424 - Fix rare bug on REDIRECTSTREAM control command when called with no
14425 port set: it could erroneously report an error when none had
14427 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
14428 compressing large objects and find ourselves with more than 4k
14429 left over. Bugfix on 0.2.0.
14430 - Fix a small memory leak when setting up a hidden service.
14431 - Fix a few memory leaks that could in theory happen under bizarre
14433 - Fix an assert if we post a general-purpose descriptor via the
14434 control port but that descriptor isn't mentioned in our current
14435 network consensus. Bug reported by Jon McLachlan; bugfix on
14438 o Minor features (controller):
14439 - Get NS events working again. Patch from tup.
14440 - The GETCONF command now escapes and quotes configuration values
14441 that don't otherwise fit into the torrc file.
14442 - The SETCONF command now handles quoted values correctly.
14444 o Minor features (directory authorities):
14445 - New configuration options to override default maximum number of
14446 servers allowed on a single IP address. This is important for
14447 running a test network on a single host.
14448 - Actually implement the -s option to tor-gencert.
14449 - Add a manual page for tor-gencert.
14451 o Minor features (bridges):
14452 - Bridge authorities no longer serve bridge descriptors over
14453 unencrypted connections.
14455 o Minor features (other):
14456 - Add hidden services and DNSPorts to the list of things that make
14457 Tor accept that it has running ports. Change starting Tor with no
14458 ports from a fatal error to a warning; we might change it back if
14459 this turns out to confuse anybody. Fixes bug 579.
14462 Changes in version 0.1.2.19 - 2008-01-17
14463 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
14464 exit policy a little bit more conservative so it's safer to run an
14465 exit relay on a home system, and fixes a variety of smaller issues.
14468 - Exit policies now reject connections that are addressed to a
14469 relay's public (external) IP address too, unless
14470 ExitPolicyRejectPrivate is turned off. We do this because too
14471 many relays are running nearby to services that trust them based
14472 on network address.
14475 - When the clock jumps forward a lot, do not allow the bandwidth
14476 buckets to become negative. Fixes bug 544.
14477 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14478 on every successful resolve. Reported by Mike Perry.
14479 - Purge old entries from the "rephist" database and the hidden
14480 service descriptor database even when DirPort is zero.
14481 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14482 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14483 crashing or mis-answering these requests.
14484 - When we decide to send a 503 response to a request for servers, do
14485 not then also send the server descriptors: this defeats the whole
14486 purpose. Fixes bug 539.
14489 - Changing the ExitPolicyRejectPrivate setting should cause us to
14490 rebuild our server descriptor.
14491 - Fix handling of hex nicknames when answering controller requests for
14492 networkstatus by name, or when deciding whether to warn about
14493 unknown routers in a config option. (Patch from mwenge.)
14494 - Fix a couple of hard-to-trigger autoconf problems that could result
14495 in really weird results on platforms whose sys/types.h files define
14496 nonstandard integer types.
14497 - Don't try to create the datadir when running --verify-config or
14498 --hash-password. Resolves bug 540.
14499 - If we were having problems getting a particular descriptor from the
14500 directory caches, and then we learned about a new descriptor for
14501 that router, we weren't resetting our failure count. Reported
14503 - Although we fixed bug 539 (where servers would send HTTP status 503
14504 responses _and_ send a body too), there are still servers out there
14505 that haven't upgraded. Therefore, make clients parse such bodies
14506 when they receive them.
14507 - Run correctly on systems where rlim_t is larger than unsigned long.
14508 This includes some 64-bit systems.
14509 - Run correctly on platforms (like some versions of OS X 10.5) where
14510 the real limit for number of open files is OPEN_FILES, not rlim_max
14511 from getrlimit(RLIMIT_NOFILES).
14512 - Avoid a spurious free on base64 failure.
14513 - Avoid segfaults on certain complex invocations of
14514 router_get_by_hexdigest().
14515 - Fix rare bug on REDIRECTSTREAM control command when called with no
14516 port set: it could erroneously report an error when none had
14520 Changes in version 0.2.0.15-alpha - 2007-12-25
14521 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
14522 features added in 0.2.0.13-alpha.
14525 - Fix several remotely triggerable asserts based on DirPort requests
14526 for a v2 or v3 networkstatus object before we were prepared. This
14527 was particularly bad for 0.2.0.13 and later bridge relays, who
14528 would never have a v2 networkstatus and would thus always crash
14529 when used. Bugfixes on 0.2.0.x.
14530 - Estimate the v3 networkstatus size more accurately, rather than
14531 estimating it at zero bytes and giving it artificially high priority
14532 compared to other directory requests. Bugfix on 0.2.0.x.
14535 - Fix configure.in logic for cross-compilation.
14536 - When we load a bridge descriptor from the cache, and it was
14537 previously unreachable, mark it as retriable so we won't just
14538 ignore it. Also, try fetching a new copy immediately. Bugfixes
14540 - The bridge GeoIP stats were counting other relays, for example
14541 self-reachability and authority-reachability tests.
14544 - Support compilation to target iPhone; patch from cjacker huang.
14545 To build for iPhone, pass the --enable-iphone option to configure.
14548 Changes in version 0.2.0.14-alpha - 2007-12-23
14550 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
14551 without a datadirectory from a previous Tor install. Reported
14553 - Fix a crash when we fetch a descriptor that turns out to be
14554 unexpected (it used to be in our networkstatus when we started
14555 fetching it, but it isn't in our current networkstatus), and we
14556 aren't using bridges. Bugfix on 0.2.0.x.
14557 - Fix a crash when accessing hidden services: it would work the first
14558 time you use a given introduction point for your service, but
14559 on subsequent requests we'd be using garbage memory. Fixed by
14560 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
14561 - Fix a crash when we load a bridge descriptor from disk but we don't
14562 currently have a Bridge line for it in our torrc. Bugfix on
14566 - If bridge authorities set BridgePassword, they will serve a
14567 snapshot of known bridge routerstatuses from their DirPort to
14568 anybody who knows that password. Unset by default.
14571 - Make the unit tests build again.
14572 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
14573 - Make PublishServerDescriptor default to 1, so the default doesn't
14574 have to change as we invent new directory protocol versions.
14575 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
14576 be included unless sys/time.h is already included. Fixes
14577 bug 553. Bugfix on 0.2.0.x.
14578 - If we receive a general-purpose descriptor and then receive an
14579 identical bridge-purpose descriptor soon after, don't discard
14580 the next one as a duplicate.
14583 - If BridgeRelay is set to 1, then the default for
14584 PublishServerDescriptor is now "bridge" rather than "v2,v3".
14585 - If the user sets RelayBandwidthRate but doesn't set
14586 RelayBandwidthBurst, then make them equal rather than erroring out.
14589 Changes in version 0.2.0.13-alpha - 2007-12-21
14590 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
14591 Goodell, fixes many more bugs, and adds a lot of infrastructure for
14594 o New directory authorities:
14595 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
14599 - Only update guard status (usable / not usable) once we have
14600 enough directory information. This was causing us to always pick
14601 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
14602 causing us to discard all our guards on startup if we hadn't been
14603 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
14604 - Purge old entries from the "rephist" database and the hidden
14605 service descriptor databases even when DirPort is zero. Bugfix
14607 - We were ignoring our RelayBandwidthRate for the first 30 seconds
14608 after opening a circuit -- even a relayed circuit. Bugfix on
14610 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14611 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14612 crashing or mis-answering these types of requests.
14613 - Relays were publishing their server descriptor to v1 and v2
14614 directory authorities, but they didn't try publishing to v3-only
14615 authorities. Fix this; and also stop publishing to v1 authorities.
14617 - When we were reading router descriptors from cache, we were ignoring
14618 the annotations -- so for example we were reading in bridge-purpose
14619 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
14620 - When we decided to send a 503 response to a request for servers, we
14621 were then also sending the server descriptors: this defeats the
14622 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
14625 - Bridge relays now behave like clients with respect to time
14626 intervals for downloading new consensus documents -- otherwise they
14627 stand out. Bridge users now wait until the end of the interval,
14628 so their bridge relay will be sure to have a new consensus document.
14629 - Three new config options (AlternateDirAuthority,
14630 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14631 user selectively replace the default directory authorities by type,
14632 rather than the all-or-nothing replacement that DirServer offers.
14633 - Tor can now be configured to read a GeoIP file from disk in one
14634 of two formats. This can be used by controllers to map IP addresses
14635 to countries. Eventually, it may support exit-by-country.
14636 - When possible, bridge relays remember which countries users
14637 are coming from, and report aggregate information in their
14638 extra-info documents, so that the bridge authorities can learn
14639 where Tor is blocked.
14640 - Bridge directory authorities now do reachability testing on the
14641 bridges they know. They provide router status summaries to the
14642 controller via "getinfo ns/purpose/bridge", and also dump summaries
14643 to a file periodically.
14644 - Stop fetching directory info so aggressively if your DirPort is
14645 on but your ORPort is off; stop fetching v2 dir info entirely.
14646 You can override these choices with the new FetchDirInfoEarly
14650 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
14651 consensus documents when there are too many relays at a single
14652 IP address. Now clear it in v2 network status documents too, and
14653 also clear it in routerinfo_t when the relay is no longer listed
14654 in the relevant networkstatus document.
14655 - Don't crash if we get an unexpected value for the
14656 PublishServerDescriptor config option. Reported by Matt Edman;
14657 bugfix on 0.2.0.9-alpha.
14658 - Our new v2 hidden service descriptor format allows descriptors
14659 that have no introduction points. But Tor crashed when we tried
14660 to build a descriptor with no intro points (and it would have
14661 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
14662 by Karsten Loesing.
14663 - Fix building with dmalloc 5.5.2 with glibc.
14664 - Reject uploaded descriptors and extrainfo documents if they're
14665 huge. Otherwise we'll cache them all over the network and it'll
14666 clog everything up. Reported by Aljosha Judmayer.
14667 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
14668 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
14669 - When the DANGEROUS_VERSION controller status event told us we're
14670 running an obsolete version, it used the string "OLD" to describe
14671 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
14672 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
14673 - If we can't expand our list of entry guards (e.g. because we're
14674 using bridges or we have StrictEntryNodes set), don't mark relays
14675 down when they fail a directory request. Otherwise we're too quick
14676 to mark all our entry points down. Bugfix on 0.1.2.x.
14677 - Fix handling of hex nicknames when answering controller requests for
14678 networkstatus by name, or when deciding whether to warn about unknown
14679 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
14680 - Fix a couple of hard-to-trigger autoconf problems that could result
14681 in really weird results on platforms whose sys/types.h files define
14682 nonstandard integer types. Bugfix on 0.1.2.x.
14683 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
14684 - Don't crash on name lookup when we have no current consensus. Fixes
14685 bug 538; bugfix on 0.2.0.x.
14686 - Only Tors that want to mirror the v2 directory info should
14687 create the "cached-status" directory in their datadir. (All Tors
14688 used to create it.) Bugfix on 0.2.0.9-alpha.
14689 - Directory authorities should only automatically download Extra Info
14690 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
14693 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14694 consumers. (We already do this on HUP.)
14695 - Authorities and caches fetch the v2 networkstatus documents
14696 less often, now that v3 is encouraged.
14697 - Add a new config option BridgeRelay that specifies you want to
14698 be a bridge relay. Right now the only difference is that it makes
14699 you answer begin_dir requests, and it makes you cache dir info,
14700 even if your DirPort isn't on.
14701 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14702 ask about source, timestamp of arrival, purpose, etc. We need
14703 something like this to help Vidalia not do GeoIP lookups on bridge
14705 - Allow multiple HashedControlPassword config lines, to support
14706 multiple controller passwords.
14707 - Authorities now decide whether they're authoritative for a given
14708 router based on the router's purpose.
14709 - New config options AuthDirBadDir and AuthDirListBadDirs for
14710 authorities to mark certain relays as "bad directories" in the
14711 networkstatus documents. Also supports the "!baddir" directive in
14712 the approved-routers file.
14715 Changes in version 0.2.0.12-alpha - 2007-11-16
14716 This twelfth development snapshot fixes some more build problems as
14717 well as a few minor bugs.
14720 - Make it build on OpenBSD again. Patch from tup.
14721 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
14722 package-building for Red Hat, OS X, etc.
14724 o Minor bugfixes (on 0.1.2.x):
14725 - Changing the ExitPolicyRejectPrivate setting should cause us to
14726 rebuild our server descriptor.
14728 o Minor bugfixes (on 0.2.0.x):
14729 - When we're lacking a consensus, don't try to perform rendezvous
14730 operations. Reported by Karsten Loesing.
14731 - Fix a small memory leak whenever we decide against using a
14732 newly picked entry guard. Reported by Mike Perry.
14733 - When authorities detected more than two relays running on the same
14734 IP address, they were clearing all the status flags but forgetting
14735 to clear the "hsdir" flag. So clients were being told that a
14736 given relay was the right choice for a v2 hsdir lookup, yet they
14737 never had its descriptor because it was marked as 'not running'
14739 - If we're trying to fetch a bridge descriptor and there's no way
14740 the bridge authority could help us (for example, we don't know
14741 a digest, or there is no bridge authority), don't be so eager to
14742 fall back to asking the bridge authority.
14743 - If we're using bridges or have strictentrynodes set, and our
14744 chosen exit is in the same family as all our bridges/entry guards,
14745 then be flexible about families.
14748 - When we negotiate a v2 link-layer connection (not yet implemented),
14749 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14750 negotiated a v1 connection for their next step. Initial code for
14754 Changes in version 0.2.0.11-alpha - 2007-11-12
14755 This eleventh development snapshot fixes some build problems with
14756 the previous snapshot. It also includes a more secure-by-default exit
14757 policy for relays, fixes an enormous memory leak for exit relays, and
14758 fixes another bug where servers were falling out of the directory list.
14761 - Exit policies now reject connections that are addressed to a
14762 relay's public (external) IP address too, unless
14763 ExitPolicyRejectPrivate is turned off. We do this because too
14764 many relays are running nearby to services that trust them based
14765 on network address. Bugfix on 0.1.2.x.
14768 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14769 on every successful resolve. Reported by Mike Perry; bugfix
14771 - On authorities, never downgrade to old router descriptors simply
14772 because they're listed in the consensus. This created a catch-22
14773 where we wouldn't list a new descriptor because there was an
14774 old one in the consensus, and we couldn't get the new one in the
14775 consensus because we wouldn't list it. Possible fix for bug 548.
14776 Also, this might cause bug 543 to appear on authorities; if so,
14777 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
14779 o Packaging fixes on 0.2.0.10-alpha:
14780 - We were including instructions about what to do with the
14781 src/config/fallback-consensus file, but we weren't actually
14782 including it in the tarball. Disable all of that for now.
14785 - Allow people to say PreferTunnelledDirConns rather than
14786 PreferTunneledDirConns, for those alternate-spellers out there.
14789 - Don't reevaluate all the information from our consensus document
14790 just because we've downloaded a v2 networkstatus that we intend
14791 to cache. Fixes bug 545; bugfix on 0.2.0.x.
14794 Changes in version 0.2.0.10-alpha - 2007-11-10
14795 This tenth development snapshot adds a third v3 directory authority
14796 run by Mike Perry, adds most of Karsten Loesing's new hidden service
14797 descriptor format, fixes a bad crash bug and new bridge bugs introduced
14798 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
14799 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
14800 addresses many more minor issues.
14802 o New directory authorities:
14803 - Set up ides (run by Mike Perry) as the third v3 directory authority.
14806 - Allow tunnelled directory connections to ask for an encrypted
14807 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14808 connection independently. Now we can make anonymized begin_dir
14809 connections for (e.g.) more secure hidden service posting and
14811 - More progress on proposal 114: code from Karsten Loesing to
14812 implement new hidden service descriptor format.
14813 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14814 accommodate the growing number of servers that use the default
14815 and are reaching it.
14816 - Directory authorities use a new formula for selecting which nodes
14817 to advertise as Guards: they must be in the top 7/8 in terms of
14818 how long we have known about them, and above the median of those
14819 nodes in terms of weighted fractional uptime.
14820 - Make "not enough dir info yet" warnings describe *why* Tor feels
14821 it doesn't have enough directory info yet.
14824 - Stop servers from crashing if they set a Family option (or
14825 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
14827 - Make bridge users work again -- the move to v3 directories in
14828 0.2.0.9-alpha had introduced a number of bugs that made bridges
14829 no longer work for clients.
14830 - When the clock jumps forward a lot, do not allow the bandwidth
14831 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
14833 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
14834 - When the consensus lists a router descriptor that we previously were
14835 mirroring, but that we considered non-canonical, reload the
14836 descriptor as canonical. This fixes bug 543 where Tor servers
14837 would start complaining after a few days that they don't have
14838 enough directory information to build a circuit.
14839 - Consider replacing the current consensus when certificates arrive
14840 that make the pending consensus valid. Previously, we were only
14841 considering replacement when the new certs _didn't_ help.
14842 - Fix an assert error on startup if we didn't already have the
14843 consensus and certs cached in our datadirectory: we were caching
14844 the consensus in consensus_waiting_for_certs but then free'ing it
14846 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
14847 Request) if we need more v3 certs but we've already got pending
14848 requests for all of them.
14849 - Correctly back off from failing certificate downloads. Fixes
14851 - Authorities don't vote on the Running flag if they have been running
14852 for less than 30 minutes themselves. Fixes bug 547, where a newly
14853 started authority would vote that everyone was down.
14855 o New requirements:
14856 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14857 it, it had no AES, and it hasn't seen any security patches since
14861 - Clients now hold circuitless TLS connections open for 1.5 times
14862 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14863 rebuild a new circuit over them within that timeframe. Previously,
14864 they held them open only for KeepalivePeriod (5 minutes).
14865 - Use "If-Modified-Since" to avoid retrieving consensus
14866 networkstatuses that we already have.
14867 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14868 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14869 we start knowing some directory caches.
14870 - When we receive a consensus from the future, warn about skew.
14871 - Improve skew reporting: try to give the user a better log message
14872 about how skewed they are, and how much this matters.
14873 - When we have a certificate for an authority, believe that
14874 certificate's claims about the authority's IP address.
14875 - New --quiet command-line option to suppress the default console log.
14876 Good in combination with --hash-password.
14877 - Authorities send back an X-Descriptor-Not-New header in response to
14878 an accepted-but-discarded descriptor upload. Partially implements
14880 - Make the log message for "tls error. breaking." more useful.
14881 - Better log messages about certificate downloads, to attempt to
14882 track down the second incarnation of bug 546.
14884 o Minor features (bridges):
14885 - If bridge users set UpdateBridgesFromAuthority, but the digest
14886 they ask for is a 404 from the bridge authority, they now fall
14887 back to trying the bridge directly.
14888 - Bridges now use begin_dir to publish their server descriptor to
14889 the bridge authority, even when they haven't set TunnelDirConns.
14891 o Minor features (controller):
14892 - When reporting clock skew, and we know that the clock is _at least
14893 as skewed_ as some value, but we don't know the actual value,
14894 report the value as a "minimum skew."
14897 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14898 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14902 - Refuse to start if both ORPort and UseBridges are set. Bugfix
14903 on 0.2.0.x, suggested by Matt Edman.
14904 - Don't stop fetching descriptors when FetchUselessDescriptors is
14905 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
14906 reported by tup and ioerror.
14907 - Better log message on vote from unknown authority.
14908 - Don't log "Launching 0 request for 0 router" message.
14910 o Minor bugfixes (memory leaks):
14911 - Stop leaking memory every time we parse a v3 certificate. Bugfix
14913 - Stop leaking memory every time we load a v3 certificate. Bugfix
14914 on 0.2.0.1-alpha. Fixes bug 536.
14915 - Stop leaking a cached networkstatus on exit. Bugfix on
14917 - Stop leaking voter information every time we free a consensus.
14918 Bugfix on 0.2.0.3-alpha.
14919 - Stop leaking signed data every time we check a voter signature.
14920 Bugfix on 0.2.0.3-alpha.
14921 - Stop leaking a signature every time we fail to parse a consensus or
14922 a vote. Bugfix on 0.2.0.3-alpha.
14923 - Stop leaking v2_download_status_map on shutdown. Bugfix on
14925 - Stop leaking conn->nickname every time we make a connection to a
14926 Tor relay without knowing its expected identity digest (e.g. when
14927 using bridges). Bugfix on 0.2.0.3-alpha.
14929 - Minor bugfixes (portability):
14930 - Run correctly on platforms where rlim_t is larger than unsigned
14931 long, and/or where the real limit for number of open files is
14932 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
14933 particular, these may be needed for OS X 10.5.
14936 Changes in version 0.1.2.18 - 2007-10-28
14937 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14938 hidden service introduction that were causing huge delays, and a big
14939 bug that was causing some servers to disappear from the network status
14940 lists for a few hours each day.
14942 o Major bugfixes (crashes):
14943 - If a connection is shut down abruptly because of something that
14944 happened inside connection_flushed_some(), do not call
14945 connection_finished_flushing(). Should fix bug 451:
14946 "connection_stop_writing: Assertion conn->write_event failed"
14947 Bugfix on 0.1.2.7-alpha.
14948 - Fix possible segfaults in functions called from
14949 rend_process_relay_cell().
14951 o Major bugfixes (hidden services):
14952 - Hidden services were choosing introduction points uniquely by
14953 hexdigest, but when constructing the hidden service descriptor
14954 they merely wrote the (potentially ambiguous) nickname.
14955 - Clients now use the v2 intro format for hidden service
14956 connections: they specify their chosen rendezvous point by identity
14957 digest rather than by (potentially ambiguous) nickname. These
14958 changes could speed up hidden service connections dramatically.
14960 o Major bugfixes (other):
14961 - Stop publishing a new server descriptor just because we get a
14962 HUP signal. This led (in a roundabout way) to some servers getting
14963 dropped from the networkstatus lists for a few hours each day.
14964 - When looking for a circuit to cannibalize, consider family as well
14965 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14966 circuit cannibalization).
14967 - When a router wasn't listed in a new networkstatus, we were leaving
14968 the flags for that router alone -- meaning it remained Named,
14969 Running, etc -- even though absence from the networkstatus means
14970 that it shouldn't be considered to exist at all anymore. Now we
14971 clear all the flags for routers that fall out of the networkstatus
14972 consensus. Fixes bug 529.
14975 - Don't try to access (or alter) the state file when running
14976 --list-fingerprint or --verify-config or --hash-password. Resolves
14978 - When generating information telling us how to extend to a given
14979 router, do not try to include the nickname if it is
14980 absent. Resolves bug 467.
14981 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14982 a way to trigger this remotely.)
14983 - When sending a status event to the controller telling it that an
14984 OR address is reachable, set the port correctly. (Previously we
14985 were reporting the dir port.)
14986 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14987 command. Bugfix on 0.1.2.17.
14988 - When loading bandwidth history, do not believe any information in
14989 the future. Fixes bug 434.
14990 - When loading entry guard information, do not believe any information
14992 - When we have our clock set far in the future and generate an
14993 onion key, then re-set our clock to be correct, we should not stop
14994 the onion key from getting rotated.
14995 - On some platforms, accept() can return a broken address. Detect
14996 this more quietly, and deal accordingly. Fixes bug 483.
14997 - It's not actually an error to find a non-pending entry in the DNS
14998 cache when canceling a pending resolve. Don't log unless stuff
14999 is fishy. Resolves bug 463.
15000 - Don't reset trusted dir server list when we set a configuration
15001 option. Patch from Robert Hogan.
15002 - Don't try to create the datadir when running --verify-config or
15003 --hash-password. Resolves bug 540.
15006 Changes in version 0.2.0.9-alpha - 2007-10-24
15007 This ninth development snapshot switches clients to the new v3 directory
15008 system; allows servers to be listed in the network status even when they
15009 have the same nickname as a registered server; and fixes many other
15010 bugs including a big one that was causing some servers to disappear
15011 from the network status lists for a few hours each day.
15013 o Major features (directory system):
15014 - Clients now download v3 consensus networkstatus documents instead
15015 of v2 networkstatus documents. Clients and caches now base their
15016 opinions about routers on these consensus documents. Clients only
15017 download router descriptors listed in the consensus.
15018 - Authorities now list servers who have the same nickname as
15019 a different named server, but list them with a new flag,
15020 "Unnamed". Now we can list servers that happen to pick the same
15021 nickname as a server that registered two years ago and then
15022 disappeared. Partially implements proposal 122.
15023 - If the consensus lists a router as "Unnamed", the name is assigned
15024 to a different router: do not identify the router by that name.
15025 Partially implements proposal 122.
15026 - Authorities can now come to a consensus on which method to use to
15027 compute the consensus. This gives us forward compatibility.
15030 - Stop publishing a new server descriptor just because we HUP or
15031 when we find our DirPort to be reachable but won't actually publish
15032 it. New descriptors without any real changes are dropped by the
15033 authorities, and can screw up our "publish every 18 hours" schedule.
15035 - When a router wasn't listed in a new networkstatus, we were leaving
15036 the flags for that router alone -- meaning it remained Named,
15037 Running, etc -- even though absence from the networkstatus means
15038 that it shouldn't be considered to exist at all anymore. Now we
15039 clear all the flags for routers that fall out of the networkstatus
15040 consensus. Fixes bug 529; bugfix on 0.1.2.x.
15041 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
15042 extrainfo documents and then discard them immediately for not
15043 matching the latest router. Bugfix on 0.2.0.1-alpha.
15045 o Minor features (v3 directory protocol):
15046 - Allow tor-gencert to generate a new certificate without replacing
15048 - Allow certificates to include an address.
15049 - When we change our directory-cache settings, reschedule all voting
15050 and download operations.
15051 - Reattempt certificate downloads immediately on failure, as long as
15052 we haven't failed a threshold number of times yet.
15053 - Delay retrying consensus downloads while we're downloading
15054 certificates to verify the one we just got. Also, count getting a
15055 consensus that we already have (or one that isn't valid) as a failure,
15056 and count failing to get the certificates after 20 minutes as a
15058 - Build circuits and download descriptors even if our consensus is a
15059 little expired. (This feature will go away once authorities are
15062 o Minor features (router descriptor cache):
15063 - If we find a cached-routers file that's been sitting around for more
15064 than 28 days unmodified, then most likely it's a leftover from
15065 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15067 - When we (as a cache) download a descriptor because it was listed
15068 in a consensus, remember when the consensus was supposed to expire,
15069 and don't expire the descriptor until then.
15071 o Minor features (performance):
15072 - Call routerlist_remove_old_routers() much less often. This should
15073 speed startup, especially on directory caches.
15074 - Don't try to launch new descriptor downloads quite so often when we
15075 already have enough directory information to build circuits.
15076 - Base64 decoding was actually showing up on our profile when parsing
15077 the initial descriptor file; switch to an in-process all-at-once
15078 implementation that's about 3.5x times faster than calling out to
15081 o Minor features (compilation):
15082 - Detect non-ASCII platforms (if any still exist) and refuse to
15083 build there: some of our code assumes that 'A' is 65 and so on.
15085 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
15086 - Make the "next period" votes into "current period" votes immediately
15087 after publishing the consensus; avoid a heisenbug that made them
15088 stick around indefinitely.
15089 - When we discard a vote as a duplicate, do not report this as
15091 - Treat missing v3 keys or certificates as an error when running as a
15092 v3 directory authority.
15093 - When we're configured to be a v3 authority, but we're only listed
15094 as a non-v3 authority in our DirServer line for ourself, correct
15096 - If an authority doesn't have a qualified hostname, just put
15097 its address in the vote. This fixes the problem where we referred to
15098 "moria on moria:9031."
15099 - Distinguish between detached signatures for the wrong period, and
15100 detached signatures for a divergent vote.
15101 - Fix a small memory leak when computing a consensus.
15102 - When there's no concensus, we were forming a vote every 30
15103 minutes, but writing the "valid-after" line in our vote based
15104 on our configured V3AuthVotingInterval: so unless the intervals
15105 matched up, we immediately rejected our own vote because it didn't
15106 start at the voting interval that caused us to construct a vote.
15108 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
15109 - Delete unverified-consensus when the real consensus is set.
15110 - Consider retrying a consensus networkstatus fetch immediately
15111 after one fails: don't wait 60 seconds to notice.
15112 - When fetching a consensus as a cache, wait until a newer consensus
15113 should exist before trying to replace the current one.
15114 - Use a more forgiving schedule for retrying failed consensus
15115 downloads than for other types.
15117 o Minor bugfixes (other directory issues):
15118 - Correct the implementation of "download votes by digest." Bugfix on
15120 - Authorities no longer send back "400 you're unreachable please fix
15121 it" errors to Tor servers that aren't online all the time. We're
15122 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
15124 o Minor bugfixes (controller):
15125 - Don't reset trusted dir server list when we set a configuration
15126 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
15127 - Respond to INT and TERM SIGNAL commands before we execute the
15128 signal, in case the signal shuts us down. We had a patch in
15129 0.1.2.1-alpha that tried to do this by queueing the response on
15130 the connection's buffer before shutting down, but that really
15131 isn't the same thing at all. Bug located by Matt Edman.
15133 o Minor bugfixes (misc):
15134 - Correctly check for bad options to the "PublishServerDescriptor"
15135 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
15136 - Stop leaking memory on failing case of base32_decode, and make
15137 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
15138 - Don't try to download extrainfo documents when we're trying to
15139 fetch enough directory info to build a circuit: having enough
15140 info should get priority. Bugfix on 0.2.0.x.
15141 - Don't complain that "your server has not managed to confirm that its
15142 ports are reachable" if we haven't been able to build any circuits
15143 yet. Bug found by spending four hours without a v3 consensus. Bugfix
15145 - Detect the reason for failing to mmap a descriptor file we just
15146 wrote, and give a more useful log message. Fixes bug 533. Bugfix
15149 o Code simplifications and refactoring:
15150 - Remove support for the old bw_accounting file: we've been storing
15151 bandwidth accounting information in the state file since
15152 0.1.2.5-alpha. This may result in bandwidth accounting errors
15153 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15154 downgrade to 0.1.1.x or earlier.
15155 - New convenience code to locate a file within the DataDirectory.
15156 - Move non-authority functionality out of dirvote.c.
15157 - Refactor the arguments for router_pick_{directory_|trusteddir}server
15158 so that they all take the same named flags.
15161 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15162 Unix users an easy way to script their Tor process (e.g. by
15163 adjusting bandwidth based on the time of the day).
15166 Changes in version 0.2.0.8-alpha - 2007-10-12
15167 This eighth development snapshot fixes a crash bug that's been bothering
15168 us since February 2007, lets bridge authorities store a list of bridge
15169 descriptors they've seen, gets v3 directory voting closer to working,
15170 starts caching v3 directory consensus documents on directory mirrors,
15171 and fixes a variety of smaller issues including some minor memory leaks.
15173 o Major features (router descriptor cache):
15174 - Store routers in a file called cached-descriptors instead of in
15175 cached-routers. Initialize cached-descriptors from cached-routers
15176 if the old format is around. The new format allows us to store
15177 annotations along with descriptors.
15178 - Use annotations to record the time we received each descriptor, its
15179 source, and its purpose.
15180 - Disable the SETROUTERPURPOSE controller command: it is now
15182 - Controllers should now specify cache=no or cache=yes when using
15183 the +POSTDESCRIPTOR command.
15184 - Bridge authorities now write bridge descriptors to disk, meaning
15185 we can export them to other programs and begin distributing them
15188 o Major features (directory authorities):
15189 - When a v3 authority is missing votes or signatures, it now tries
15191 - Directory authorities track weighted fractional uptime as well as
15192 weighted mean-time-between failures. WFU is suitable for deciding
15193 whether a node is "usually up", while MTBF is suitable for deciding
15194 whether a node is "likely to stay up." We need both, because
15195 "usually up" is a good requirement for guards, while "likely to
15196 stay up" is a good requirement for long-lived connections.
15198 o Major features (v3 directory system):
15199 - Caches now download v3 network status documents as needed,
15200 and download the descriptors listed in them.
15201 - All hosts now attempt to download and keep fresh v3 authority
15202 certificates, and re-attempt after failures.
15203 - More internal-consistency checks for vote parsing.
15205 o Major bugfixes (crashes):
15206 - If a connection is shut down abruptly because of something that
15207 happened inside connection_flushed_some(), do not call
15208 connection_finished_flushing(). Should fix bug 451. Bugfix on
15211 o Major bugfixes (performance):
15212 - Fix really bad O(n^2) performance when parsing a long list of
15213 routers: Instead of searching the entire list for an "extra-info "
15214 string which usually wasn't there, once for every routerinfo
15215 we read, just scan lines forward until we find one we like.
15217 - When we add data to a write buffer in response to the data on that
15218 write buffer getting low because of a flush, do not consider the
15219 newly added data as a candidate for immediate flushing, but rather
15220 make it wait until the next round of writing. Otherwise, we flush
15221 and refill recursively, and a single greedy TLS connection can
15222 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
15224 o Minor features (v3 authority system):
15225 - Add more ways for tools to download the votes that lead to the
15227 - Send a 503 when low on bandwidth and a vote, consensus, or
15228 certificate is requested.
15229 - If-modified-since is now implemented properly for all kinds of
15230 certificate requests.
15232 o Minor bugfixes (network statuses):
15233 - Tweak the implementation of proposal 109 slightly: allow at most
15234 two Tor servers on the same IP address, except if it's the location
15235 of a directory authority, in which case allow five. Bugfix on
15238 o Minor bugfixes (controller):
15239 - When sending a status event to the controller telling it that an
15240 OR address is reachable, set the port correctly. (Previously we
15241 were reporting the dir port.) Bugfix on 0.1.2.x.
15243 o Minor bugfixes (v3 directory system):
15244 - Fix logic to look up a cert by its signing key digest. Bugfix on
15246 - Only change the reply to a vote to "OK" if it's not already
15247 set. This gets rid of annoying "400 OK" log messages, which may
15248 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
15249 - When we get a valid consensus, recompute the voting schedule.
15250 - Base the valid-after time of a vote on the consensus voting
15251 schedule, not on our preferred schedule.
15252 - Make the return values and messages from signature uploads and
15253 downloads more sensible.
15254 - Fix a memory leak when serving votes and consensus documents, and
15255 another when serving certificates.
15257 o Minor bugfixes (performance):
15258 - Use a slightly simpler string hashing algorithm (copying Python's
15259 instead of Java's) and optimize our digest hashing algorithm to take
15260 advantage of 64-bit platforms and to remove some possibly-costly
15262 - Fix a minor memory leak whenever we parse guards from our state
15263 file. Bugfix on 0.2.0.7-alpha.
15264 - Fix a minor memory leak whenever we write out a file. Bugfix on
15266 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15267 command. Bugfix on 0.2.0.5-alpha.
15269 o Minor bugfixes (portability):
15270 - On some platforms, accept() can return a broken address. Detect
15271 this more quietly, and deal accordingly. Fixes bug 483.
15272 - Stop calling tor_strlower() on uninitialized memory in some cases.
15273 Bugfix in 0.2.0.7-alpha.
15275 o Minor bugfixes (usability):
15276 - Treat some 403 responses from directory servers as INFO rather than
15277 WARN-severity events.
15278 - It's not actually an error to find a non-pending entry in the DNS
15279 cache when canceling a pending resolve. Don't log unless stuff is
15280 fishy. Resolves bug 463.
15282 o Minor bugfixes (anonymity):
15283 - Never report that we've used more bandwidth than we're willing to
15284 relay: it leaks how much non-relay traffic we're using. Resolves
15286 - When looking for a circuit to cannibalize, consider family as well
15287 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15288 circuit cannibalization).
15290 o Code simplifications and refactoring:
15291 - Make a bunch of functions static. Remove some dead code.
15292 - Pull out about a third of the really big routerlist.c; put it in a
15293 new module, networkstatus.c.
15294 - Merge the extra fields in local_routerstatus_t back into
15295 routerstatus_t: we used to need one routerstatus_t for each
15296 authority's opinion, plus a local_routerstatus_t for the locally
15297 computed consensus opinion. To save space, we put the locally
15298 modified fields into local_routerstatus_t, and only the common
15299 stuff into routerstatus_t. But once v3 directories are in use,
15300 clients and caches will no longer need to hold authority opinions;
15301 thus, the rationale for keeping the types separate is now gone.
15302 - Make the code used to reschedule and reattempt downloads more
15304 - Turn all 'Are we a directory server/mirror?' logic into a call to
15306 - Remove the code to generate the oldest (v1) directory format.
15307 The code has been disabled since 0.2.0.5-alpha.
15310 Changes in version 0.2.0.7-alpha - 2007-09-21
15311 This seventh development snapshot makes bridges work again, makes bridge
15312 authorities work for the first time, fixes two huge performance flaws
15313 in hidden services, and fixes a variety of minor issues.
15315 o New directory authorities:
15316 - Set up moria1 and tor26 as the first v3 directory authorities. See
15317 doc/spec/dir-spec.txt for details on the new directory design.
15319 o Major bugfixes (crashes):
15320 - Fix possible segfaults in functions called from
15321 rend_process_relay_cell(). Bugfix on 0.1.2.x.
15323 o Major bugfixes (bridges):
15324 - Fix a bug that made servers send a "404 Not found" in response to
15325 attempts to fetch their server descriptor. This caused Tor servers
15326 to take many minutes to establish reachability for their DirPort,
15327 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
15328 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
15329 users configure that and specify a bridge with an identity
15330 fingerprint, now they will lookup the bridge descriptor at the
15331 default bridge authority via a one-hop tunnel, but once circuits
15332 are established they will switch to a three-hop tunnel for later
15333 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
15335 o Major bugfixes (hidden services):
15336 - Hidden services were choosing introduction points uniquely by
15337 hexdigest, but when constructing the hidden service descriptor
15338 they merely wrote the (potentially ambiguous) nickname.
15339 - Clients now use the v2 intro format for hidden service
15340 connections: they specify their chosen rendezvous point by identity
15341 digest rather than by (potentially ambiguous) nickname. Both
15342 are bugfixes on 0.1.2.x, and they could speed up hidden service
15343 connections dramatically. Thanks to Karsten Loesing.
15345 o Minor features (security):
15346 - As a client, do not believe any server that tells us that an
15347 address maps to an internal address space.
15348 - Make it possible to enable HashedControlPassword and
15349 CookieAuthentication at the same time.
15351 o Minor features (guard nodes):
15352 - Tag every guard node in our state file with the version that
15353 we believe added it, or with our own version if we add it. This way,
15354 if a user temporarily runs an old version of Tor and then switches
15355 back to a new one, she doesn't automatically lose her guards.
15357 o Minor features (speed):
15358 - When implementing AES counter mode, update only the portions of the
15359 counter buffer that need to change, and don't keep separate
15360 network-order and host-order counters when they are the same (i.e.,
15361 on big-endian hosts.)
15363 o Minor features (controller):
15364 - Accept LF instead of CRLF on controller, since some software has a
15365 hard time generating real Internet newlines.
15366 - Add GETINFO values for the server status events
15367 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15370 o Removed features:
15371 - Routers no longer include bandwidth-history lines in their
15372 descriptors; this information is already available in extra-info
15373 documents, and including it in router descriptors took up 60%
15374 (!) of compressed router descriptor downloads. Completes
15375 implementation of proposal 104.
15376 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15377 and TorControl.py, as they use the old v0 controller protocol,
15378 and are obsoleted by TorFlow anyway.
15379 - Drop support for v1 rendezvous descriptors, since we never used
15380 them anyway, and the code has probably rotted by now. Based on
15381 patch from Karsten Loesing.
15382 - On OSX, stop warning the user that kqueue support in libevent is
15383 "experimental", since it seems to have worked fine for ages.
15386 - When generating information telling us how to extend to a given
15387 router, do not try to include the nickname if it is absent. Fixes
15388 bug 467. Bugfix on 0.2.0.3-alpha.
15389 - Fix a user-triggerable (but not remotely-triggerable) segfault
15390 in expand_filename(). Bugfix on 0.1.2.x.
15391 - Fix a memory leak when freeing incomplete requests from DNSPort.
15392 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
15393 - Don't try to access (or alter) the state file when running
15394 --list-fingerprint or --verify-config or --hash-password. (Resolves
15395 bug 499.) Bugfix on 0.1.2.x.
15396 - Servers used to decline to publish their DirPort if their
15397 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
15398 were below a threshold. Now they only look at BandwidthRate and
15399 RelayBandwidthRate. Bugfix on 0.1.2.x.
15400 - Remove an optimization in the AES counter-mode code that assumed
15401 that the counter never exceeded 2^68. When the counter can be set
15402 arbitrarily as an IV (as it is by Karsten's new hidden services
15403 code), this assumption no longer holds. Bugfix on 0.1.2.x.
15404 - Resume listing "AUTHORITY" flag for authorities in network status.
15405 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
15407 o Code simplifications and refactoring:
15408 - Revamp file-writing logic so we don't need to have the entire
15409 contents of a file in memory at once before we write to disk. Tor,
15411 - Turn "descriptor store" into a full-fledged type.
15412 - Move all NT services code into a separate source file.
15413 - Unify all code that computes medians, percentile elements, etc.
15414 - Get rid of a needless malloc when parsing address policies.
15417 Changes in version 0.1.2.17 - 2007-08-30
15418 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15419 X bundles. Vidalia 0.0.14 makes authentication required for the
15420 ControlPort in the default configuration, which addresses important
15421 security risks. Everybody who uses Vidalia (or another controller)
15424 In addition, this Tor update fixes major load balancing problems with
15425 path selection, which should speed things up a lot once many people
15428 o Major bugfixes (security):
15429 - We removed support for the old (v0) control protocol. It has been
15430 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15431 become more of a headache than it's worth.
15433 o Major bugfixes (load balancing):
15434 - When choosing nodes for non-guard positions, weight guards
15435 proportionally less, since they already have enough load. Patch
15437 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15438 will allow fast Tor servers to get more attention.
15439 - When we're upgrading from an old Tor version, forget our current
15440 guards and pick new ones according to the new weightings. These
15441 three load balancing patches could raise effective network capacity
15442 by a factor of four. Thanks to Mike Perry for measurements.
15444 o Major bugfixes (stream expiration):
15445 - Expire not-yet-successful application streams in all cases if
15446 they've been around longer than SocksTimeout. Right now there are
15447 some cases where the stream will live forever, demanding a new
15448 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15450 o Minor features (controller):
15451 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15452 is valid before any authentication has been received. It tells
15453 a controller what kind of authentication is expected, and what
15454 protocol is spoken. Implements proposal 119.
15456 o Minor bugfixes (performance):
15457 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15458 greatly speeding up loading cached-routers from disk on startup.
15459 - Disable sentinel-based debugging for buffer code: we squashed all
15460 the bugs that this was supposed to detect a long time ago, and now
15461 its only effect is to change our buffer sizes from nice powers of
15462 two (which platform mallocs tend to like) to values slightly over
15463 powers of two (which make some platform mallocs sad).
15465 o Minor bugfixes (misc):
15466 - If exit bandwidth ever exceeds one third of total bandwidth, then
15467 use the correct formula to weight exit nodes when choosing paths.
15468 Based on patch from Mike Perry.
15469 - Choose perfectly fairly among routers when choosing by bandwidth and
15470 weighting by fraction of bandwidth provided by exits. Previously, we
15471 would choose with only approximate fairness, and correct ourselves
15472 if we ran off the end of the list.
15473 - If we require CookieAuthentication but we fail to write the
15474 cookie file, we would warn but not exit, and end up in a state
15475 where no controller could authenticate. Now we exit.
15476 - If we require CookieAuthentication, stop generating a new cookie
15477 every time we change any piece of our config.
15478 - Refuse to start with certain directory authority keys, and
15479 encourage people using them to stop.
15480 - Terminate multi-line control events properly. Original patch
15482 - Fix a minor memory leak when we fail to find enough suitable
15483 servers to choose a circuit.
15484 - Stop leaking part of the descriptor when we run into a particularly
15485 unparseable piece of it.
15488 Changes in version 0.2.0.6-alpha - 2007-08-26
15489 This sixth development snapshot features a new Vidalia version in the
15490 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
15491 the ControlPort in the default configuration, which addresses important
15494 In addition, this snapshot fixes major load balancing problems
15495 with path selection, which should speed things up a lot once many
15496 people have upgraded. The directory authorities also use a new
15497 mean-time-between-failure approach to tracking which servers are stable,
15498 rather than just looking at the most recent uptime.
15500 o New directory authorities:
15501 - Set up Tonga as the default bridge directory authority.
15504 - Directory authorities now track servers by weighted
15505 mean-times-between-failures. When we have 4 or more days of data,
15506 use measured MTBF rather than declared uptime to decide whether
15507 to call a router Stable. Implements proposal 108.
15509 o Major bugfixes (load balancing):
15510 - When choosing nodes for non-guard positions, weight guards
15511 proportionally less, since they already have enough load. Patch
15513 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15514 will allow fast Tor servers to get more attention.
15515 - When we're upgrading from an old Tor version, forget our current
15516 guards and pick new ones according to the new weightings. These
15517 three load balancing patches could raise effective network capacity
15518 by a factor of four. Thanks to Mike Perry for measurements.
15520 o Major bugfixes (descriptor parsing):
15521 - Handle unexpected whitespace better in malformed descriptors. Bug
15522 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
15525 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15526 GETINFO for Torstat to use until it can switch to using extrainfos.
15527 - Optionally (if built with -DEXPORTMALLINFO) export the output
15528 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15532 - Do not intermix bridge routers with controller-added
15533 routers. (Bugfix on 0.2.0.x)
15534 - Do not fail with an assert when accept() returns an unexpected
15535 address family. Addresses but does not wholly fix bug 483. (Bugfix
15537 - Let directory authorities startup even when they can't generate
15538 a descriptor immediately, e.g. because they don't know their
15540 - Stop putting the authentication cookie in a file called "0"
15541 in your working directory if you don't specify anything for the
15542 new CookieAuthFile option. Reported by Matt Edman.
15543 - Make it possible to read the PROTOCOLINFO response in a way that
15544 conforms to our control-spec. Reported by Matt Edman.
15545 - Fix a minor memory leak when we fail to find enough suitable
15546 servers to choose a circuit. Bugfix on 0.1.2.x.
15547 - Stop leaking part of the descriptor when we run into a particularly
15548 unparseable piece of it. Bugfix on 0.1.2.x.
15549 - Unmap the extrainfo cache file on exit.
15552 Changes in version 0.2.0.5-alpha - 2007-08-19
15553 This fifth development snapshot fixes compilation on Windows again;
15554 fixes an obnoxious client-side bug that slowed things down and put
15555 extra load on the network; gets us closer to using the v3 directory
15556 voting scheme; makes it easier for Tor controllers to use cookie-based
15557 authentication; and fixes a variety of other bugs.
15559 o Removed features:
15560 - Version 1 directories are no longer generated in full. Instead,
15561 authorities generate and serve "stub" v1 directories that list
15562 no servers. This will stop Tor versions 0.1.0.x and earlier from
15563 working, but (for security reasons) nobody should be running those
15566 o Major bugfixes (compilation, 0.2.0.x):
15567 - Try to fix Win32 compilation again: improve checking for IPv6 types.
15568 - Try to fix MSVC compilation: build correctly on platforms that do
15569 not define s6_addr16 or s6_addr32.
15570 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
15573 o Major bugfixes (stream expiration):
15574 - Expire not-yet-successful application streams in all cases if
15575 they've been around longer than SocksTimeout. Right now there are
15576 some cases where the stream will live forever, demanding a new
15577 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
15578 reported by lodger.
15580 o Minor features (directory servers):
15581 - When somebody requests a list of statuses or servers, and we have
15582 none of those, return a 404 rather than an empty 200.
15584 o Minor features (directory voting):
15585 - Store v3 consensus status consensuses on disk, and reload them
15588 o Minor features (security):
15589 - Warn about unsafe ControlPort configurations.
15590 - Refuse to start with certain directory authority keys, and
15591 encourage people using them to stop.
15593 o Minor features (controller):
15594 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15595 is valid before any authentication has been received. It tells
15596 a controller what kind of authentication is expected, and what
15597 protocol is spoken. Implements proposal 119.
15598 - New config option CookieAuthFile to choose a new location for the
15599 cookie authentication file, and config option
15600 CookieAuthFileGroupReadable to make it group-readable.
15602 o Minor features (unit testing):
15603 - Add command-line arguments to unit-test executable so that we can
15604 invoke any chosen test from the command line rather than having
15605 to run the whole test suite at once; and so that we can turn on
15606 logging for the unit tests.
15608 o Minor bugfixes (on 0.1.2.x):
15609 - If we require CookieAuthentication but we fail to write the
15610 cookie file, we would warn but not exit, and end up in a state
15611 where no controller could authenticate. Now we exit.
15612 - If we require CookieAuthentication, stop generating a new cookie
15613 every time we change any piece of our config.
15614 - When loading bandwidth history, do not believe any information in
15615 the future. Fixes bug 434.
15616 - When loading entry guard information, do not believe any information
15618 - When we have our clock set far in the future and generate an
15619 onion key, then re-set our clock to be correct, we should not stop
15620 the onion key from getting rotated.
15621 - Clean up torrc sample config file.
15622 - Do not automatically run configure from autogen.sh. This
15623 non-standard behavior tended to annoy people who have built other
15626 o Minor bugfixes (on 0.2.0.x):
15627 - Fix a bug with AutomapHostsOnResolve that would always cause
15628 the second request to fail. Bug reported by Kate. Bugfix on
15630 - Fix a bug in ADDRMAP controller replies that would sometimes
15631 try to print a NULL. Patch from tup.
15632 - Read v3 directory authority keys from the right location.
15633 - Numerous bugfixes to directory voting code.
15636 Changes in version 0.1.2.16 - 2007-08-01
15637 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15638 remote attacker in certain situations to rewrite the user's torrc
15639 configuration file. This can completely compromise anonymity of users
15640 in most configurations, including those running the Vidalia bundles,
15641 TorK, etc. Or worse.
15643 o Major security fixes:
15644 - Close immediately after missing authentication on control port;
15645 do not allow multiple authentication attempts.
15648 Changes in version 0.2.0.4-alpha - 2007-08-01
15649 This fourth development snapshot fixes a critical security vulnerability
15650 for most users, specifically those running Vidalia, TorK, etc. Everybody
15651 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
15653 o Major security fixes:
15654 - Close immediately after missing authentication on control port;
15655 do not allow multiple authentication attempts.
15657 o Major bugfixes (compilation):
15658 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
15661 o Minor features (performance):
15662 - Be even more aggressive about releasing RAM from small
15663 empty buffers. Thanks to our free-list code, this shouldn't be too
15664 performance-intensive.
15665 - Disable sentinel-based debugging for buffer code: we squashed all
15666 the bugs that this was supposed to detect a long time ago, and
15667 now its only effect is to change our buffer sizes from nice
15668 powers of two (which platform mallocs tend to like) to values
15669 slightly over powers of two (which make some platform mallocs sad).
15670 - Log malloc statistics from mallinfo() on platforms where it
15674 Changes in version 0.2.0.3-alpha - 2007-07-29
15675 This third development snapshot introduces new experimental
15676 blocking-resistance features and a preliminary version of the v3
15677 directory voting design, and includes many other smaller features
15681 - The first pieces of our "bridge" design for blocking-resistance
15682 are implemented. People can run bridge directory authorities;
15683 people can run bridges; and people can configure their Tor clients
15684 with a set of bridges to use as the first hop into the Tor network.
15685 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
15687 - Create listener connections before we setuid to the configured
15688 User and Group. Now non-Windows users can choose port values
15689 under 1024, start Tor as root, and have Tor bind those ports
15690 before it changes to another UID. (Windows users could already
15692 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15693 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15694 on "vserver" accounts. (Patch from coderman.)
15695 - Be even more aggressive about separating local traffic from relayed
15696 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
15698 o Major features (experimental):
15699 - First cut of code for "v3 dir voting": directory authorities will
15700 vote on a common network status document rather than each publishing
15701 their own opinion. This code needs more testing and more corner-case
15702 handling before it's ready for use.
15705 - Directory authorities now call routers Fast if their bandwidth is
15706 at least 100KB/s, and consider their bandwidth adequate to be a
15707 Guard if it is at least 250KB/s, no matter the medians. This fix
15708 complements proposal 107. [Bugfix on 0.1.2.x]
15709 - Directory authorities now never mark more than 3 servers per IP as
15710 Valid and Running. (Implements proposal 109, by Kevin Bauer and
15712 - Minor change to organizationName and commonName generation
15713 procedures in TLS certificates during Tor handshakes, to invalidate
15714 some earlier censorware approaches. This is not a long-term
15715 solution, but applying it will give us a bit of time to look into
15716 the epidemiology of countermeasures as they spread.
15718 o Major bugfixes (directory):
15719 - Rewrite directory tokenization code to never run off the end of
15720 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
15722 o Minor features (controller):
15723 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15724 match requests to applications. (Patch from Robert Hogan.)
15725 - Report address and port correctly on connections to DNSPort. (Patch
15726 from Robert Hogan.)
15727 - Add a RESOLVE command to launch hostname lookups. (Original patch
15728 from Robert Hogan.)
15729 - Add GETINFO status/enough-dir-info to let controllers tell whether
15730 Tor has downloaded sufficient directory information. (Patch
15732 - You can now use the ControlSocket option to tell Tor to listen for
15733 controller connections on Unix domain sockets on systems that
15734 support them. (Patch from Peter Palfrader.)
15735 - STREAM NEW events are generated for DNSPort requests and for
15736 tunneled directory connections. (Patch from Robert Hogan.)
15737 - New "GETINFO address-mappings/*" command to get address mappings
15738 with expiry information. "addr-mappings/*" is now deprecated.
15741 o Minor features (misc):
15742 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15744 - The tor-gencert tool for v3 directory authorities now creates all
15745 files as readable to the file creator only, and write-protects
15746 the authority identity key.
15747 - When dumping memory usage, list bytes used in buffer memory
15749 - When running with dmalloc, dump more stats on hup and on exit.
15750 - Directory authorities now fail quickly and (relatively) harmlessly
15751 if they generate a network status document that is somehow
15754 o Traffic load balancing improvements:
15755 - If exit bandwidth ever exceeds one third of total bandwidth, then
15756 use the correct formula to weight exit nodes when choosing paths.
15757 (Based on patch from Mike Perry.)
15758 - Choose perfectly fairly among routers when choosing by bandwidth and
15759 weighting by fraction of bandwidth provided by exits. Previously, we
15760 would choose with only approximate fairness, and correct ourselves
15761 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15763 o Performance improvements:
15764 - Be more aggressive with freeing buffer RAM or putting it on the
15766 - Use Critical Sections rather than Mutexes for synchronizing threads
15767 on win32; Mutexes are heavier-weight, and designed for synchronizing
15770 o Deprecated and removed features:
15771 - RedirectExits is now deprecated.
15772 - Stop allowing address masks that do not correspond to bit prefixes.
15773 We have warned about these for a really long time; now it's time
15774 to reject them. (Patch from croup.)
15776 o Minor bugfixes (directory):
15777 - Fix another crash bug related to extra-info caching. (Bug found by
15778 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
15779 - Directories no longer return a "304 not modified" when they don't
15780 have the networkstatus the client asked for. Also fix a memory
15781 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
15782 - We had accidentally labelled 0.1.2.x directory servers as not
15783 suitable for begin_dir requests, and had labelled no directory
15784 servers as suitable for uploading extra-info documents. [Bugfix
15787 o Minor bugfixes (dns):
15788 - Fix a crash when DNSPort is set more than once. (Patch from Robert
15789 Hogan.) [Bugfix on 0.2.0.2-alpha]
15790 - Add DNSPort connections to the global connection list, so that we
15791 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
15793 - Fix a dangling reference that could lead to a crash when DNSPort is
15794 changed or closed (Patch from Robert Hogan.) [Bugfix on
15797 o Minor bugfixes (controller):
15798 - Provide DNS expiry times in GMT, not in local time. For backward
15799 compatibility, ADDRMAP events only provide GMT expiry in an extended
15800 field. "GETINFO address-mappings" always does the right thing.
15801 - Use CRLF line endings properly in NS events.
15802 - Terminate multi-line control events properly. (Original patch
15803 from tup.) [Bugfix on 0.1.2.x-alpha]
15804 - Do not include spaces in SOURCE_ADDR fields in STREAM
15805 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
15808 Changes in version 0.1.2.15 - 2007-07-17
15809 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15810 problems, fixes compilation on BSD, and fixes a variety of other
15811 bugs. Everybody should upgrade.
15813 o Major bugfixes (compilation):
15814 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15816 o Major bugfixes (crashes):
15817 - Try even harder not to dereference the first character after
15818 an mmap(). Reported by lodger.
15819 - Fix a crash bug in directory authorities when we re-number the
15820 routerlist while inserting a new router.
15821 - When the cached-routers file is an even multiple of the page size,
15822 don't run off the end and crash. (Fixes bug 455; based on idea
15824 - Fix eventdns.c behavior on Solaris: It is critical to include
15825 orconfig.h _before_ sys/types.h, so that we can get the expected
15826 definition of _FILE_OFFSET_BITS.
15828 o Major bugfixes (security):
15829 - Fix a possible buffer overrun when using BSD natd support. Bug
15831 - When sending destroy cells from a circuit's origin, don't include
15832 the reason for tearing down the circuit. The spec says we didn't,
15833 and now we actually don't. Reported by lodger.
15834 - Keep streamids from different exits on a circuit separate. This
15835 bug may have allowed other routers on a given circuit to inject
15836 cells into streams. Reported by lodger; fixes bug 446.
15837 - If there's a never-before-connected-to guard node in our list,
15838 never choose any guards past it. This way we don't expand our
15839 guard list unless we need to.
15841 o Minor bugfixes (guard nodes):
15842 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15843 don't get overused as guards.
15845 o Minor bugfixes (directory):
15846 - Correctly count the number of authorities that recommend each
15847 version. Previously, we were under-counting by 1.
15848 - Fix a potential crash bug when we load many server descriptors at
15849 once and some of them make others of them obsolete. Fixes bug 458.
15851 o Minor bugfixes (hidden services):
15852 - Stop tearing down the whole circuit when the user asks for a
15853 connection to a port that the hidden service didn't configure.
15856 o Minor bugfixes (misc):
15857 - On Windows, we were preventing other processes from reading
15858 cached-routers while Tor was running. Reported by janbar.
15859 - Fix a possible (but very unlikely) bug in picking routers by
15860 bandwidth. Add a log message to confirm that it is in fact
15861 unlikely. Patch from lodger.
15862 - Backport a couple of memory leak fixes.
15863 - Backport miscellaneous cosmetic bugfixes.
15866 Changes in version 0.2.0.2-alpha - 2007-06-02
15867 o Major bugfixes on 0.2.0.1-alpha:
15868 - Fix an assertion failure related to servers without extra-info digests.
15869 Resolves bugs 441 and 442.
15871 o Minor features (directory):
15872 - Support "If-Modified-Since" when answering HTTP requests for
15873 directories, running-routers documents, and network-status documents.
15874 (There's no need to support it for router descriptors, since those
15875 are downloaded by descriptor digest.)
15877 o Minor build issues:
15878 - Clear up some MIPSPro compiler warnings.
15879 - When building from a tarball on a machine that happens to have SVK
15880 installed, report the micro-revision as whatever version existed
15881 in the tarball, not as "x".
15884 Changes in version 0.2.0.1-alpha - 2007-06-01
15885 This early development snapshot provides new features for people running
15886 Tor as both a client and a server (check out the new RelayBandwidth
15887 config options); lets Tor run as a DNS proxy; and generally moves us
15888 forward on a lot of fronts.
15890 o Major features, server usability:
15891 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15892 a separate set of token buckets for relayed traffic. Right now
15893 relayed traffic is defined as answers to directory requests, and
15894 OR connections that don't have any local circuits on them.
15896 o Major features, client usability:
15897 - A client-side DNS proxy feature to replace the need for
15898 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15899 for DNS requests on port 9999, use the Tor network to resolve them
15900 anonymously, and send the reply back like a regular DNS server.
15901 The code still only implements a subset of DNS.
15902 - Make PreferTunneledDirConns and TunnelDirConns work even when
15903 we have no cached directory info. This means Tor clients can now
15904 do all of their connections protected by TLS.
15906 o Major features, performance and efficiency:
15907 - Directory authorities accept and serve "extra info" documents for
15908 routers. These documents contain fields from router descriptors
15909 that aren't usually needed, and that use a lot of excess
15910 bandwidth. Once these fields are removed from router descriptors,
15911 the bandwidth savings should be about 60%. [Partially implements
15913 - Servers upload extra-info documents to any authority that accepts
15914 them. Authorities (and caches that have been configured to download
15915 extra-info documents) download them as needed. [Partially implements
15917 - Change the way that Tor buffers data that it is waiting to write.
15918 Instead of queueing data cells in an enormous ring buffer for each
15919 client->OR or OR->OR connection, we now queue cells on a separate
15920 queue for each circuit. This lets us use less slack memory, and
15921 will eventually let us be smarter about prioritizing different kinds
15923 - Use memory pools to allocate cells with better speed and memory
15924 efficiency, especially on platforms where malloc() is inefficient.
15925 - Stop reading on edge connections when their corresponding circuit
15926 buffers are full; start again as the circuits empty out.
15928 o Major features, other:
15929 - Add an HSAuthorityRecordStats option that hidden service authorities
15930 can use to track statistics of overall hidden service usage without
15931 logging information that would be very useful to an attacker.
15932 - Start work implementing multi-level keys for directory authorities:
15933 Add a standalone tool to generate key certificates. (Proposal 103.)
15936 - Directory authorities now call routers Stable if they have an
15937 uptime of at least 30 days, even if that's not the median uptime
15938 in the network. Implements proposal 107, suggested by Kevin Bauer
15941 o Minor fixes (resource management):
15942 - Count the number of open sockets separately from the number
15943 of active connection_t objects. This will let us avoid underusing
15944 our allocated connection limit.
15945 - We no longer use socket pairs to link an edge connection to an
15946 anonymous directory connection or a DirPort test connection.
15947 Instead, we track the link internally and transfer the data
15948 in-process. This saves two sockets per "linked" connection (at the
15949 client and at the server), and avoids the nasty Windows socketpair()
15951 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15952 for every single inactive connection_t. Free items from the
15953 4k/16k-buffer free lists when they haven't been used for a while.
15955 o Minor features (build):
15956 - Make autoconf search for libevent, openssl, and zlib consistently.
15957 - Update deprecated macros in configure.in.
15958 - When warning about missing headers, tell the user to let us
15959 know if the compile succeeds anyway, so we can downgrade the
15961 - Include the current subversion revision as part of the version
15962 string: either fetch it directly if we're in an SVN checkout, do
15963 some magic to guess it if we're in an SVK checkout, or use
15964 the last-detected version if we're building from a .tar.gz.
15965 Use this version consistently in log messages.
15967 o Minor features (logging):
15968 - Always prepend "Bug: " to any log message about a bug.
15969 - Put a platform string (e.g. "Linux i686") in the startup log
15970 message, so when people paste just their logs, we know if it's
15971 OpenBSD or Windows or what.
15972 - When logging memory usage, break down memory used in buffers by
15975 o Minor features (directory system):
15976 - New config option V2AuthoritativeDirectory that all directory
15977 authorities should set. This will let future authorities choose
15978 not to serve V2 directory information.
15979 - Directory authorities allow multiple router descriptors and/or extra
15980 info documents to be uploaded in a single go. This will make
15981 implementing proposal 104 simpler.
15983 o Minor features (controller):
15984 - Add a new config option __DisablePredictedCircuits designed for
15985 use by the controller, when we don't want Tor to build any circuits
15987 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15988 so we can exit from the middle of the circuit.
15989 - Implement "getinfo status/circuit-established".
15990 - Implement "getinfo status/version/..." so a controller can tell
15991 whether the current version is recommended, and whether any versions
15992 are good, and how many authorities agree. (Patch from shibz.)
15994 o Minor features (hidden services):
15995 - Allow multiple HiddenServicePort directives with the same virtual
15996 port; when they occur, the user is sent round-robin to one
15997 of the target ports chosen at random. Partially fixes bug 393 by
15998 adding limited ad-hoc round-robining.
16000 o Minor features (other):
16002 - Add a new AutomapHostsOnResolve option: when it is enabled, any
16003 resolve request for hosts matching a given pattern causes Tor to
16004 generate an internal virtual address mapping for that host. This
16005 allows DNSPort to work sensibly with hidden service users. By
16006 default, .exit and .onion addresses are remapped; the list of
16007 patterns can be reconfigured with AutomapHostsSuffixes.
16008 - Add an "-F" option to tor-resolve to force a resolve for a .onion
16009 address. Thanks to the AutomapHostsOnResolve option, this is no
16010 longer a completely silly thing to do.
16011 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
16012 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
16013 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
16014 minus 1 byte: the actual maximum declared bandwidth.
16016 o Removed features:
16017 - Removed support for the old binary "version 0" controller protocol.
16018 This has been deprecated since 0.1.1, and warnings have been issued
16019 since 0.1.2. When we encounter a v0 control message, we now send
16020 back an error and close the connection.
16021 - Remove the old "dns worker" server DNS code: it hasn't been default
16022 since 0.1.2.2-alpha, and all the servers seem to be using the new
16025 o Minor bugfixes (portability):
16026 - Even though Windows is equally happy with / and \ as path separators,
16027 try to use \ consistently on Windows and / consistently on Unix: it
16028 makes the log messages nicer.
16029 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16030 - Read resolv.conf files correctly on platforms where read() returns
16031 partial results on small file reads.
16033 o Minor bugfixes (directory):
16034 - Correctly enforce that elements of directory objects do not appear
16035 more often than they are allowed to appear.
16036 - When we are reporting the DirServer line we just parsed, we were
16037 logging the second stanza of the key fingerprint, not the first.
16039 o Minor bugfixes (logging):
16040 - When we hit an EOF on a log (probably because we're shutting down),
16041 don't try to remove the log from the list: just mark it as
16042 unusable. (Bulletproofs against bug 222.)
16044 o Minor bugfixes (other):
16045 - In the exitlist script, only consider the most recently published
16046 server descriptor for each server. Also, when the user requests
16047 a list of servers that _reject_ connections to a given address,
16048 explicitly exclude the IPs that also have servers that accept
16049 connections to that address. (Resolves bug 405.)
16050 - Stop allowing hibernating servers to be "stable" or "fast".
16051 - On Windows, we were preventing other processes from reading
16052 cached-routers while Tor was running. (Reported by janbar)
16053 - Make the NodeFamilies config option work. (Reported by
16054 lodger -- it has never actually worked, even though we added it
16056 - Check return values from pthread_mutex functions.
16057 - Don't save non-general-purpose router descriptors to the disk cache,
16058 because we have no way of remembering what their purpose was when
16060 - Add even more asserts to hunt down bug 417.
16061 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
16062 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
16063 Add a log message to confirm that it is in fact unlikely.
16065 o Minor bugfixes (controller):
16066 - Make 'getinfo fingerprint' return a 551 error if we're not a
16067 server, so we match what the control spec claims we do. Reported
16069 - Fix a typo in an error message when extendcircuit fails that
16070 caused us to not follow the \r\n-based delimiter protocol. Reported
16073 o Code simplifications and refactoring:
16074 - Stop passing around circuit_t and crypt_path_t pointers that are
16075 implicit in other procedure arguments.
16076 - Drop the old code to choke directory connections when the
16077 corresponding OR connections got full: thanks to the cell queue
16078 feature, OR conns don't get full any more.
16079 - Make dns_resolve() handle attaching connections to circuits
16080 properly, so the caller doesn't have to.
16081 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
16082 - Keep the connection array as a dynamic smartlist_t, rather than as
16083 a fixed-sized array. This is important, as the number of connections
16084 is becoming increasingly decoupled from the number of sockets.
16087 Changes in version 0.1.2.14 - 2007-05-25
16088 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16089 change especially affects those who serve or use hidden services),
16090 and fixes several other crash- and security-related bugs.
16092 o Directory authority changes:
16093 - Two directory authorities (moria1 and moria2) just moved to new
16094 IP addresses. This change will particularly affect those who serve
16095 or use hidden services.
16097 o Major bugfixes (crashes):
16098 - If a directory server runs out of space in the connection table
16099 as it's processing a begin_dir request, it will free the exit stream
16100 but leave it attached to the circuit, leading to unpredictable
16101 behavior. (Reported by seeess, fixes bug 425.)
16102 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16103 to corrupt memory under some really unlikely scenarios.
16104 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16105 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16108 o Major bugfixes (security):
16109 - When choosing an entry guard for a circuit, avoid using guards
16110 that are in the same family as the chosen exit -- not just guards
16111 that are exactly the chosen exit. (Reported by lodger.)
16113 o Major bugfixes (resource management):
16114 - If a directory authority is down, skip it when deciding where to get
16115 networkstatus objects or descriptors. Otherwise we keep asking
16116 every 10 seconds forever. Fixes bug 384.
16117 - Count it as a failure if we fetch a valid network-status but we
16118 don't want to keep it. Otherwise we'll keep fetching it and keep
16119 not wanting to keep it. Fixes part of bug 422.
16120 - If all of our dirservers have given us bad or no networkstatuses
16121 lately, then stop hammering them once per minute even when we
16122 think they're failed. Fixes another part of bug 422.
16125 - Actually set the purpose correctly for descriptors inserted with
16126 purpose=controller.
16127 - When we have k non-v2 authorities in our DirServer config,
16128 we ignored the last k authorities in the list when updating our
16130 - Correctly back-off from requesting router descriptors that we are
16131 having a hard time downloading.
16132 - Read resolv.conf files correctly on platforms where read() returns
16133 partial results on small file reads.
16134 - Don't rebuild the entire router store every time we get 32K of
16135 routers: rebuild it when the journal gets very large, or when
16136 the gaps in the store get very large.
16139 - When routers publish SVN revisions in their router descriptors,
16140 authorities now include those versions correctly in networkstatus
16142 - Warn when using a version of libevent before 1.3b to run a server on
16143 OSX or BSD: these versions interact badly with userspace threads.
16146 Changes in version 0.1.2.13 - 2007-04-24
16147 This release features some major anonymity fixes, such as safer path
16148 selection; better client performance; faster bootstrapping, better
16149 address detection, and better DNS support for servers; write limiting as
16150 well as read limiting to make servers easier to run; and a huge pile of
16151 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16153 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16154 of the Freenode IRC network, remembering his patience and vision for
16155 free speech on the Internet.
16158 - Fix a memory leak when we ask for "all" networkstatuses and we
16159 get one we don't recognize.
16160 - Add more asserts to hunt down bug 417.
16161 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16164 Changes in version 0.1.2.12-rc - 2007-03-16
16166 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
16167 directory information requested inside Tor connections (i.e. via
16168 begin_dir cells). It only triggered when the same connection was
16169 serving other data at the same time. Reported by seeess.
16172 - When creating a circuit via the controller, send a 'launched'
16173 event when we're done, so we follow the spec better.
16176 Changes in version 0.1.2.11-rc - 2007-03-15
16177 o Minor bugfixes (controller), reported by daejees:
16178 - Correct the control spec to match how the code actually responds
16179 to 'getinfo addr-mappings/*'.
16180 - The control spec described a GUARDS event, but the code
16181 implemented a GUARD event. Standardize on GUARD, but let people
16182 ask for GUARDS too.
16185 Changes in version 0.1.2.10-rc - 2007-03-07
16186 o Major bugfixes (Windows):
16187 - Do not load the NT services library functions (which may not exist)
16188 just to detect if we're a service trying to shut down. Now we run
16189 on Win98 and friends again.
16191 o Minor bugfixes (other):
16192 - Clarify a couple of log messages.
16193 - Fix a misleading socks5 error number.
16196 Changes in version 0.1.2.9-rc - 2007-03-02
16197 o Major bugfixes (Windows):
16198 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
16199 of the usual GCC "%llu". This prevents a bug when saving 64-bit
16200 int configuration values: the high-order 32 bits would get
16201 truncated. In particular, we were being bitten by the default
16202 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
16203 and maybe also bug 397.)
16205 o Minor bugfixes (performance):
16206 - Use OpenSSL's AES implementation on platforms where it's faster.
16207 This could save us as much as 10% CPU usage.
16209 o Minor bugfixes (server):
16210 - Do not rotate onion key immediately after setting it for the first
16213 o Minor bugfixes (directory authorities):
16214 - Stop calling servers that have been hibernating for a long time
16215 "stable". Also, stop letting hibernating or obsolete servers affect
16216 uptime and bandwidth cutoffs.
16217 - Stop listing hibernating servers in the v1 directory.
16219 o Minor bugfixes (hidden services):
16220 - Upload hidden service descriptors slightly less often, to reduce
16221 load on authorities.
16223 o Minor bugfixes (other):
16224 - Fix an assert that could trigger if a controller quickly set then
16225 cleared EntryNodes. Bug found by Udo van den Heuvel.
16226 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
16228 - Fix a potential race condition in the rpm installer. Found by
16230 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
16231 of 2 as indicating that the server is completely bad; it sometimes
16232 means that the server is just bad for the request in question. (may fix
16233 the last of bug 326.)
16234 - Disable encrypted directory connections when we don't have a server
16235 descriptor for the destination. We'll get this working again in
16239 Changes in version 0.1.2.8-beta - 2007-02-26
16240 o Major bugfixes (crashes):
16241 - Stop crashing when the controller asks us to resetconf more than
16242 one config option at once. (Vidalia 0.0.11 does this.)
16243 - Fix a crash that happened on Win98 when we're given command-line
16244 arguments: don't try to load NT service functions from advapi32.dll
16245 except when we need them. (Bug introduced in 0.1.2.7-alpha;
16247 - Fix a longstanding obscure crash bug that could occur when
16248 we run out of DNS worker processes. (Resolves bug 390.)
16250 o Major bugfixes (hidden services):
16251 - Correctly detect whether hidden service descriptor downloads are
16252 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
16254 o Major bugfixes (accounting):
16255 - When we start during an accounting interval before it's time to wake
16256 up, remember to wake up at the correct time. (May fix bug 342.)
16258 o Minor bugfixes (controller):
16259 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16260 clear the corresponding on_circuit variable, and remember later
16261 that we don't need to send a redundant CLOSED event. Resolves part
16263 - Report events where a resolve succeeded or where we got a socks
16264 protocol error correctly, rather than calling both of them
16266 - Change reported stream target addresses to IP consistently when
16267 we finally get the IP from an exit node.
16268 - Send log messages to the controller even if they happen to be very
16271 o Minor bugfixes (other):
16272 - Display correct results when reporting which versions are
16273 recommended, and how recommended they are. (Resolves bug 383.)
16274 - Improve our estimates for directory bandwidth to be less random:
16275 guess that an unrecognized directory will have the average bandwidth
16276 from all known directories, not that it will have the average
16277 bandwidth from those directories earlier than it on the list.
16278 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16279 and hup, stop triggering an assert based on an empty onion_key.
16280 - On platforms with no working mmap() equivalent, don't warn the
16281 user when cached-routers doesn't exist.
16282 - Warn the user when mmap() [or its equivalent] fails for some reason
16283 other than file-not-found.
16284 - Don't warn the user when cached-routers.new doesn't exist: that's
16285 perfectly fine when starting up for the first time.
16286 - When EntryNodes are configured, rebuild the guard list to contain,
16287 in order: the EntryNodes that were guards before; the rest of the
16288 EntryNodes; the nodes that were guards before.
16289 - Mask out all signals in sub-threads; only the libevent signal
16290 handler should be processing them. This should prevent some crashes
16291 on some machines using pthreads. (Patch from coderman.)
16292 - Fix switched arguments on memset in the implementation of
16293 tor_munmap() for systems with no mmap() call.
16294 - When Tor receives a router descriptor that it asked for, but
16295 no longer wants (because it has received fresh networkstatuses
16296 in the meantime), do not warn the user. Cache the descriptor if
16297 we're a cache; drop it if we aren't.
16298 - Make earlier entry guards _really_ get retried when the network
16300 - On a malformed DNS reply, always give an error to the corresponding
16302 - Build with recent libevents on platforms that do not define the
16303 nonstandard types "u_int8_t" and friends.
16305 o Minor features (controller):
16306 - Warn the user when an application uses the obsolete binary v0
16307 control protocol. We're planning to remove support for it during
16308 the next development series, so it's good to give people some
16310 - Add STREAM_BW events to report per-entry-stream bandwidth
16311 use. (Patch from Robert Hogan.)
16312 - Rate-limit SIGNEWNYM signals in response to controllers that
16313 impolitely generate them for every single stream. (Patch from
16314 mwenge; closes bug 394.)
16315 - Make REMAP stream events have a SOURCE (cache or exit), and
16316 make them generated in every case where we get a successful
16317 connected or resolved cell.
16319 o Minor bugfixes (performance):
16320 - Call router_have_min_dir_info half as often. (This is showing up in
16321 some profiles, but not others.)
16322 - When using GCC, make log_debug never get called at all, and its
16323 arguments never get evaluated, when no debug logs are configured.
16324 (This is showing up in some profiles, but not others.)
16327 - Remove some never-implemented options. Mark PathlenCoinWeight as
16329 - Implement proposal 106: Stop requiring clients to have well-formed
16330 certificates; stop checking nicknames in certificates. (Clients
16331 have certificates so that they can look like Tor servers, but in
16332 the future we might want to allow them to look like regular TLS
16333 clients instead. Nicknames in certificates serve no purpose other
16334 than making our protocol easier to recognize on the wire.)
16335 - Revise messages on handshake failure again to be even more clear about
16336 which are incoming connections and which are outgoing.
16337 - Discard any v1 directory info that's over 1 month old (for
16338 directories) or over 1 week old (for running-routers lists).
16339 - Do not warn when individual nodes in the configuration's EntryNodes,
16340 ExitNodes, etc are down: warn only when all possible nodes
16341 are down. (Fixes bug 348.)
16342 - Always remove expired routers and networkstatus docs before checking
16343 whether we have enough information to build circuits. (Fixes
16345 - Put a lower-bound on MaxAdvertisedBandwidth.
16348 Changes in version 0.1.2.7-alpha - 2007-02-06
16349 o Major bugfixes (rate limiting):
16350 - Servers decline directory requests much more aggressively when
16351 they're low on bandwidth. Otherwise they end up queueing more and
16352 more directory responses, which can't be good for latency.
16353 - But never refuse directory requests from local addresses.
16354 - Fix a memory leak when sending a 503 response for a networkstatus
16356 - Be willing to read or write on local connections (e.g. controller
16357 connections) even when the global rate limiting buckets are empty.
16358 - If our system clock jumps back in time, don't publish a negative
16359 uptime in the descriptor. Also, don't let the global rate limiting
16360 buckets go absurdly negative.
16361 - Flush local controller connection buffers periodically as we're
16362 writing to them, so we avoid queueing 4+ megabytes of data before
16365 o Major bugfixes (NT services):
16366 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16367 command-line flag so that admins can override the default by saying
16368 "tor --service install --user "SomeUser"". This will not affect
16369 existing installed services. Also, warn the user that the service
16370 will look for its configuration file in the service user's
16371 %appdata% directory. (We can't do the 'hardwire the user's appdata
16372 directory' trick any more, since we may not have read access to that
16375 o Major bugfixes (other):
16376 - Previously, we would cache up to 16 old networkstatus documents
16377 indefinitely, if they came from nontrusted authorities. Now we
16378 discard them if they are more than 10 days old.
16379 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
16381 - Detect and reject malformed DNS responses containing circular
16383 - If exits are rare enough that we're not marking exits as guards,
16384 ignore exit bandwidth when we're deciding the required bandwidth
16386 - When we're handling a directory connection tunneled over Tor,
16387 don't fill up internal memory buffers with all the data we want
16388 to tunnel; instead, only add it if the OR connection that will
16389 eventually receive it has some room for it. (This can lead to
16390 slowdowns in tunneled dir connections; a better solution will have
16391 to wait for 0.2.0.)
16393 o Minor bugfixes (dns):
16394 - Add some defensive programming to eventdns.c in an attempt to catch
16395 possible memory-stomping bugs.
16396 - Detect and reject DNS replies containing IPv4 or IPv6 records with
16397 an incorrect number of bytes. (Previously, we would ignore the
16399 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
16400 in the correct order, and doesn't crash.
16401 - Free memory held in recently-completed DNS lookup attempts on exit.
16402 This was not a memory leak, but may have been hiding memory leaks.
16403 - Handle TTL values correctly on reverse DNS lookups.
16404 - Treat failure to parse resolv.conf as an error.
16406 o Minor bugfixes (other):
16407 - Fix crash with "tor --list-fingerprint" (reported by seeess).
16408 - When computing clock skew from directory HTTP headers, consider what
16409 time it was when we finished asking for the directory, not what
16411 - Expire socks connections if they spend too long waiting for the
16412 handshake to finish. Previously we would let them sit around for
16413 days, if the connecting application didn't close them either.
16414 - And if the socks handshake hasn't started, don't send a
16415 "DNS resolve socks failed" handshake reply; just close it.
16416 - Stop using C functions that OpenBSD's linker doesn't like.
16417 - Don't launch requests for descriptors unless we have networkstatuses
16418 from at least half of the authorities. This delays the first
16419 download slightly under pathological circumstances, but can prevent
16420 us from downloading a bunch of descriptors we don't need.
16421 - Do not log IPs with TLS failures for incoming TLS
16422 connections. (Fixes bug 382.)
16423 - If the user asks to use invalid exit nodes, be willing to use
16425 - Stop using the reserved ac_cv namespace in our configure script.
16426 - Call stat() slightly less often; use fstat() when possible.
16427 - Refactor the way we handle pending circuits when an OR connection
16428 completes or fails, in an attempt to fix a rare crash bug.
16429 - Only rewrite a conn's address based on X-Forwarded-For: headers
16430 if it's a parseable public IP address; and stop adding extra quotes
16431 to the resulting address.
16434 - Weight directory requests by advertised bandwidth. Now we can
16435 let servers enable write limiting but still allow most clients to
16436 succeed at their directory requests. (We still ignore weights when
16437 choosing a directory authority; I hope this is a feature.)
16440 - Create a new file ReleaseNotes which was the old ChangeLog. The
16441 new ChangeLog file now includes the summaries for all development
16443 - Check for addresses with invalid characters at the exit as well
16444 as at the client, and warn less verbosely when they fail. You can
16445 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
16446 - Adapt a patch from goodell to let the contrib/exitlist script
16447 take arguments rather than require direct editing.
16448 - Inform the server operator when we decide not to advertise a
16449 DirPort due to AccountingMax enabled or a low BandwidthRate. It
16450 was confusing Zax, so now we're hopefully more helpful.
16451 - Bring us one step closer to being able to establish an encrypted
16452 directory tunnel without knowing a descriptor first. Still not
16453 ready yet. As part of the change, now assume we can use a
16454 create_fast cell if we don't know anything about a router.
16455 - Allow exit nodes to use nameservers running on ports other than 53.
16456 - Servers now cache reverse DNS replies.
16457 - Add an --ignore-missing-torrc command-line option so that we can
16458 get the "use sensible defaults if the configuration file doesn't
16459 exist" behavior even when specifying a torrc location on the command
16462 o Minor features (controller):
16463 - Track reasons for OR connection failure; make these reasons
16464 available via the controller interface. (Patch from Mike Perry.)
16465 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16466 can learn when clients are sending malformed hostnames to Tor.
16467 - Clean up documentation for controller status events.
16468 - Add a REMAP status to stream events to note that a stream's
16469 address has changed because of a cached address or a MapAddress
16473 Changes in version 0.1.2.6-alpha - 2007-01-09
16475 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
16476 connection handles more than 4 gigs in either direction, we crash.
16477 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
16478 advertised exit node, somebody might try to exit from us when
16479 we're bootstrapping and before we've built our descriptor yet.
16480 Refuse the connection rather than crashing.
16483 - Warn if we (as a server) find that we've resolved an address that we
16484 weren't planning to resolve.
16485 - Warn that using select() on any libevent version before 1.1 will be
16486 unnecessarily slow (even for select()).
16487 - Flush ERR-level controller status events just like we currently
16488 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16489 the controller from learning about current events.
16491 o Minor features (more controller status events):
16492 - Implement EXTERNAL_ADDRESS server status event so controllers can
16493 learn when our address changes.
16494 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
16495 can learn when directories reject our descriptor.
16496 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
16497 can learn when a client application is speaking a non-socks protocol
16499 - Implement DANGEROUS_SOCKS client status event so controllers
16500 can learn when a client application is leaking DNS addresses.
16501 - Implement BUG general status event so controllers can learn when
16502 Tor is unhappy about its internal invariants.
16503 - Implement CLOCK_SKEW general status event so controllers can learn
16504 when Tor thinks the system clock is set incorrectly.
16505 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
16506 server status events so controllers can learn when their descriptors
16507 are accepted by a directory.
16508 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
16509 server status events so controllers can learn about Tor's progress in
16510 deciding whether it's reachable from the outside.
16511 - Implement BAD_LIBEVENT general status event so controllers can learn
16512 when we have a version/method combination in libevent that needs to
16514 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
16515 and DNS_USELESS server status events so controllers can learn
16516 about changes to DNS server status.
16518 o Minor features (directory):
16519 - Authorities no longer recommend exits as guards if this would shift
16520 too much load to the exit nodes.
16523 Changes in version 0.1.2.5-alpha - 2007-01-06
16525 - Enable write limiting as well as read limiting. Now we sacrifice
16526 capacity if we're pushing out lots of directory traffic, rather
16527 than overrunning the user's intended bandwidth limits.
16528 - Include TLS overhead when counting bandwidth usage; previously, we
16529 would count only the bytes sent over TLS, but not the bytes used
16531 - Support running the Tor service with a torrc not in the same
16532 directory as tor.exe and default to using the torrc located in
16533 the %appdata%\Tor\ of the user who installed the service. Patch
16535 - Servers now check for the case when common DNS requests are going to
16536 wildcarded addresses (i.e. all getting the same answer), and change
16537 their exit policy to reject *:* if it's happening.
16538 - Implement BEGIN_DIR cells, so we can connect to the directory
16539 server via TLS to do encrypted directory requests rather than
16540 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16541 config options if you like.
16543 o Minor features (config and docs):
16544 - Start using the state file to store bandwidth accounting data:
16545 the bw_accounting file is now obsolete. We'll keep generating it
16546 for a while for people who are still using 0.1.2.4-alpha.
16547 - Try to batch changes to the state file so that we do as few
16548 disk writes as possible while still storing important things in
16550 - The state file and the bw_accounting file get saved less often when
16551 the AvoidDiskWrites config option is set.
16552 - Make PIDFile work on Windows (untested).
16553 - Add internal descriptions for a bunch of configuration options:
16554 accessible via controller interface and in comments in saved
16556 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16557 NNTP by default, so this seems like a sensible addition.
16558 - Clients now reject hostnames with invalid characters. This should
16559 avoid some inadvertent info leaks. Add an option
16560 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16561 is running a private network with hosts called @, !, and #.
16562 - Add a maintainer script to tell us which options are missing
16563 documentation: "make check-docs".
16564 - Add a new address-spec.txt document to describe our special-case
16565 addresses: .exit, .onion, and .noconnnect.
16567 o Minor features (DNS):
16568 - Ongoing work on eventdns infrastructure: now it has dns server
16569 and ipv6 support. One day Tor will make use of it.
16570 - Add client-side caching for reverse DNS lookups.
16571 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16572 - When we change nameservers or IP addresses, reset and re-launch
16573 our tests for DNS hijacking.
16575 o Minor features (directory):
16576 - Authorities now specify server versions in networkstatus. This adds
16577 about 2% to the size of compressed networkstatus docs, and allows
16578 clients to tell which servers support BEGIN_DIR and which don't.
16579 The implementation is forward-compatible with a proposed future
16580 protocol version scheme not tied to Tor versions.
16581 - DirServer configuration lines now have an orport= option so
16582 clients can open encrypted tunnels to the authorities without
16583 having downloaded their descriptors yet. Enabled for moria1,
16584 moria2, tor26, and lefkada now in the default configuration.
16585 - Directory servers are more willing to send a 503 "busy" if they
16586 are near their write limit, especially for v1 directory requests.
16587 Now they can use their limited bandwidth for actual Tor traffic.
16588 - Clients track responses with status 503 from dirservers. After a
16589 dirserver has given us a 503, we try not to use it until an hour has
16590 gone by, or until we have no dirservers that haven't given us a 503.
16591 - When we get a 503 from a directory, and we're not a server, we don't
16592 count the failure against the total number of failures allowed
16593 for the thing we're trying to download.
16594 - Report X-Your-Address-Is correctly from tunneled directory
16595 connections; don't report X-Your-Address-Is when it's an internal
16596 address; and never believe reported remote addresses when they're
16598 - Protect against an unlikely DoS attack on directory servers.
16599 - Add a BadDirectory flag to network status docs so that authorities
16600 can (eventually) tell clients about caches they believe to be
16603 o Minor features (controller):
16604 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16605 - Reimplement GETINFO so that info/names stays in sync with the
16607 - Implement "GETINFO fingerprint".
16608 - Implement "SETEVENTS GUARD" so controllers can get updates on
16609 entry guard status as it changes.
16611 o Minor features (clean up obsolete pieces):
16612 - Remove some options that have been deprecated since at least
16613 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16614 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16615 to set log options.
16616 - We no longer look for identity and onion keys in "identity.key" and
16617 "onion.key" -- these were replaced by secret_id_key and
16618 secret_onion_key in 0.0.8pre1.
16619 - We no longer require unrecognized directory entries to be
16622 o Major bugfixes (security):
16623 - Stop sending the HttpProxyAuthenticator string to directory
16624 servers when directory connections are tunnelled through Tor.
16625 - Clients no longer store bandwidth history in the state file.
16626 - Do not log introduction points for hidden services if SafeLogging
16628 - When generating bandwidth history, round down to the nearest
16629 1k. When storing accounting data, round up to the nearest 1k.
16630 - When we're running as a server, remember when we last rotated onion
16631 keys, so that we will rotate keys once they're a week old even if
16632 we never stay up for a week ourselves.
16634 o Major bugfixes (other):
16635 - Fix a longstanding bug in eventdns that prevented the count of
16636 timed-out resolves from ever being reset. This bug caused us to
16637 give up on a nameserver the third time it timed out, and try it
16638 10 seconds later... and to give up on it every time it timed out
16640 - Take out the '5 second' timeout from the connection retry
16641 schedule. Now the first connect attempt will wait a full 10
16642 seconds before switching to a new circuit. Perhaps this will help
16643 a lot. Based on observations from Mike Perry.
16644 - Fix a bug on the Windows implementation of tor_mmap_file() that
16645 would prevent the cached-routers file from ever loading. Reported
16649 - Fix an assert failure when a directory authority sets
16650 AuthDirRejectUnlisted and then receives a descriptor from an
16651 unlisted router. Reported by seeess.
16652 - Avoid a double-free when parsing malformed DirServer lines.
16653 - Fix a bug when a BSD-style PF socket is first used. Patch from
16655 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
16656 to resolve an address at a given exit node even when they ask for
16658 - Servers no longer ever list themselves in their "family" line,
16659 even if configured to do so. This makes it easier to configure
16660 family lists conveniently.
16661 - When running as a server, don't fall back to 127.0.0.1 when no
16662 nameservers are configured in /etc/resolv.conf; instead, make the
16663 user fix resolv.conf or specify nameservers explicitly. (Resolves
16665 - Stop accepting certain malformed ports in configured exit policies.
16666 - Don't re-write the fingerprint file every restart, unless it has
16668 - Stop warning when a single nameserver fails: only warn when _all_ of
16669 our nameservers have failed. Also, when we only have one nameserver,
16670 raise the threshold for deciding that the nameserver is dead.
16671 - Directory authorities now only decide that routers are reachable
16672 if their identity keys are as expected.
16673 - When the user uses bad syntax in the Log config line, stop
16674 suggesting other bad syntax as a replacement.
16675 - Correctly detect ipv6 DNS capability on OpenBSD.
16677 o Minor bugfixes (controller):
16678 - Report the circuit number correctly in STREAM CLOSED events. Bug
16679 reported by Mike Perry.
16680 - Do not report bizarre values for results of accounting GETINFOs
16681 when the last second's write or read exceeds the allotted bandwidth.
16682 - Report "unrecognized key" rather than an empty string when the
16683 controller tries to fetch a networkstatus that doesn't exist.
16686 Changes in version 0.1.1.26 - 2006-12-14
16687 o Security bugfixes:
16688 - Stop sending the HttpProxyAuthenticator string to directory
16689 servers when directory connections are tunnelled through Tor.
16690 - Clients no longer store bandwidth history in the state file.
16691 - Do not log introduction points for hidden services if SafeLogging
16695 - Fix an assert failure when a directory authority sets
16696 AuthDirRejectUnlisted and then receives a descriptor from an
16697 unlisted router (reported by seeess).
16700 Changes in version 0.1.2.4-alpha - 2006-12-03
16702 - Add support for using natd; this allows FreeBSDs earlier than
16703 5.1.2 to have ipfw send connections through Tor without using
16704 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16707 - Make all connections to addresses of the form ".noconnect"
16708 immediately get closed. This lets application/controller combos
16709 successfully test whether they're talking to the same Tor by
16710 watching for STREAM events.
16711 - Make cross.sh cross-compilation script work even when autogen.sh
16712 hasn't been run. (Patch from Michael Mohr.)
16713 - Statistics dumped by -USR2 now include a breakdown of public key
16714 operations, for profiling.
16717 - Fix a major leak when directory authorities parse their
16718 approved-routers list, a minor memory leak when we fail to pick
16719 an exit node, and a few rare leaks on errors.
16720 - Handle TransPort connections even when the server sends data before
16721 the client sends data. Previously, the connection would just hang
16722 until the client sent data. (Patch from tup based on patch from
16724 - Avoid assert failure when our cached-routers file is empty on
16728 - Don't log spurious warnings when we see a circuit close reason we
16729 don't recognize; it's probably just from a newer version of Tor.
16730 - Have directory authorities allow larger amounts of drift in uptime
16731 without replacing the server descriptor: previously, a server that
16732 restarted every 30 minutes could have 48 "interesting" descriptors
16734 - Start linking to the Tor specification and Tor reference manual
16735 correctly in the Windows installer.
16736 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16737 Tor/Privoxy we also uninstall Vidalia.
16738 - Resume building on Irix64, and fix a lot of warnings from its
16739 MIPSpro C compiler.
16740 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16741 when we're running as a client.
16744 Changes in version 0.1.1.25 - 2006-11-04
16746 - When a client asks us to resolve (rather than connect to)
16747 an address, and we have a cached answer, give them the cached
16748 answer. Previously, we would give them no answer at all.
16749 - We were building exactly the wrong circuits when we predict
16750 hidden service requirements, meaning Tor would have to build all
16751 its circuits on demand.
16752 - If none of our live entry guards have a high uptime, but we
16753 require a guard with a high uptime, try adding a new guard before
16754 we give up on the requirement. This patch should make long-lived
16755 connections more stable on average.
16756 - When testing reachability of our DirPort, don't launch new
16757 tests when there's already one in progress -- unreachable
16758 servers were stacking up dozens of testing streams.
16760 o Security bugfixes:
16761 - When the user sends a NEWNYM signal, clear the client-side DNS
16762 cache too. Otherwise we continue to act on previous information.
16765 - Avoid a memory corruption bug when creating a hash table for
16767 - Avoid possibility of controller-triggered crash when misusing
16768 certain commands from a v0 controller on platforms that do not
16769 handle printf("%s",NULL) gracefully.
16770 - Avoid infinite loop on unexpected controller input.
16771 - Don't log spurious warnings when we see a circuit close reason we
16772 don't recognize; it's probably just from a newer version of Tor.
16773 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16774 Tor/Privoxy we also uninstall Vidalia.
16777 Changes in version 0.1.2.3-alpha - 2006-10-29
16779 - Prepare for servers to publish descriptors less often: never
16780 discard a descriptor simply for being too old until either it is
16781 recommended by no authorities, or until we get a better one for
16782 the same router. Make caches consider retaining old recommended
16783 routers for even longer.
16784 - If most authorities set a BadExit flag for a server, clients
16785 don't think of it as a general-purpose exit. Clients only consider
16786 authorities that advertise themselves as listing bad exits.
16787 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16788 headers for content, so that we can work better in the presence of
16789 caching HTTP proxies.
16790 - Allow authorities to list nodes as bad exits by fingerprint or by
16793 o Minor features, controller:
16794 - Add a REASON field to CIRC events; for backward compatibility, this
16795 field is sent only to controllers that have enabled the extended
16796 event format. Also, add additional reason codes to explain why
16797 a given circuit has been destroyed or truncated. (Patches from
16799 - Add a REMOTE_REASON field to extended CIRC events to tell the
16800 controller about why a remote OR told us to close a circuit.
16801 - Stream events also now have REASON and REMOTE_REASON fields,
16802 working much like those for circuit events.
16803 - There's now a GETINFO ns/... field so that controllers can ask Tor
16804 about the current status of a router.
16805 - A new event type "NS" to inform a controller when our opinion of
16806 a router's status has changed.
16807 - Add a GETINFO events/names and GETINFO features/names so controllers
16808 can tell which events and features are supported.
16809 - A new CLEARDNSCACHE signal to allow controllers to clear the
16810 client-side DNS cache without expiring circuits.
16812 o Security bugfixes:
16813 - When the user sends a NEWNYM signal, clear the client-side DNS
16814 cache too. Otherwise we continue to act on previous information.
16817 - Avoid sending junk to controllers or segfaulting when a controller
16818 uses EVENT_NEW_DESC with verbose nicknames.
16819 - Stop triggering asserts if the controller tries to extend hidden
16820 service circuits (reported by mwenge).
16821 - Avoid infinite loop on unexpected controller input.
16822 - When the controller does a "GETINFO network-status", tell it
16823 about even those routers whose descriptors are very old, and use
16824 long nicknames where appropriate.
16825 - Change NT service functions to be loaded on demand. This lets us
16826 build with MinGW without breaking Tor for Windows 98 users.
16827 - Do DirPort reachability tests less often, since a single test
16828 chews through many circuits before giving up.
16829 - In the hidden service example in torrc.sample, stop recommending
16830 esoteric and discouraged hidden service options.
16831 - When stopping an NT service, wait up to 10 sec for it to actually
16832 stop. Patch from Matt Edman; resolves bug 295.
16833 - Fix handling of verbose nicknames with ORCONN controller events:
16834 make them show up exactly when requested, rather than exactly when
16836 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
16837 printing a duplicate "$" in the keys we send (reported by mwenge).
16838 - Correctly set maximum connection limit on Cygwin. (This time
16840 - Try to detect Windows correctly when cross-compiling.
16841 - Detect the size of the routers file correctly even if it is
16842 corrupted (on systems without mmap) or not page-aligned (on systems
16843 with mmap). This bug was harmless.
16844 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16845 to open a stream fails; now we do in more cases. This should
16846 make clients able to find a good exit faster in some cases, since
16847 unhandleable requests will now get an error rather than timing out.
16848 - Resolve two memory leaks when rebuilding the on-disk router cache
16849 (reported by fookoowa).
16850 - Clean up minor code warnings suggested by the MIPSpro C compiler,
16851 and reported by some Centos users.
16852 - Controller signals now work on non-Unix platforms that don't define
16853 SIGUSR1 and SIGUSR2 the way we expect.
16854 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16855 values before failing, and always enables eventdns.
16856 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16857 Try to fix this in configure.in by checking for most functions
16858 before we check for libevent.
16861 Changes in version 0.1.2.2-alpha - 2006-10-07
16863 - Make our async eventdns library on-by-default for Tor servers,
16864 and plan to deprecate the separate dnsworker threads.
16865 - Add server-side support for "reverse" DNS lookups (using PTR
16866 records so clients can determine the canonical hostname for a given
16867 IPv4 address). Only supported by servers using eventdns; servers
16868 now announce in their descriptors whether they support eventdns.
16869 - Specify and implement client-side SOCKS5 interface for reverse DNS
16870 lookups (see doc/socks-extensions.txt).
16871 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
16872 connect to directory servers through Tor. Previously, clients needed
16873 to find Tor exits to make private connections to directory servers.
16874 - Avoid choosing Exit nodes for entry or middle hops when the
16875 total bandwidth available from non-Exit nodes is much higher than
16876 the total bandwidth available from Exit nodes.
16877 - Workaround for name servers (like Earthlink's) that hijack failing
16878 DNS requests and replace the no-such-server answer with a "helpful"
16879 redirect to an advertising-driven search portal. Also work around
16880 DNS hijackers who "helpfully" decline to hijack known-invalid
16881 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16882 lets you turn it off.
16883 - Send out a burst of long-range padding cells once we've established
16884 that we're reachable. Spread them over 4 circuits, so hopefully
16885 a few will be fast. This exercises our bandwidth and bootstraps
16886 us into the directory more quickly.
16888 o New/improved config options:
16889 - Add new config option "ResolvConf" to let the server operator
16890 choose an alternate resolve.conf file when using eventdns.
16891 - Add an "EnforceDistinctSubnets" option to control our "exclude
16892 servers on the same /16" behavior. It's still on by default; this
16893 is mostly for people who want to operate private test networks with
16894 all the machines on the same subnet.
16895 - If one of our entry guards is on the ExcludeNodes list, or the
16896 directory authorities don't think it's a good guard, treat it as
16897 if it were unlisted: stop using it as a guard, and throw it off
16898 the guards list if it stays that way for a long time.
16899 - Allow directory authorities to be marked separately as authorities
16900 for the v1 directory protocol, the v2 directory protocol, and
16901 as hidden service directories, to make it easier to retire old
16902 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16903 to continue being hidden service authorities too.
16904 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16906 o Minor features, controller:
16907 - Fix CIRC controller events so that controllers can learn the
16908 identity digests of non-Named servers used in circuit paths.
16909 - Let controllers ask for more useful identifiers for servers. Instead
16910 of learning identity digests for un-Named servers and nicknames
16911 for Named servers, the new identifiers include digest, nickname,
16912 and indication of Named status. Off by default; see control-spec.txt
16913 for more information.
16914 - Add a "getinfo address" controller command so it can display Tor's
16915 best guess to the user.
16916 - New controller event to alert the controller when our server
16917 descriptor has changed.
16918 - Give more meaningful errors on controller authentication failure.
16920 o Minor features, other:
16921 - When asked to resolve a hostname, don't use non-exit servers unless
16922 requested to do so. This allows servers with broken DNS to be
16923 useful to the network.
16924 - Divide eventdns log messages into warn and info messages.
16925 - Reserve the nickname "Unnamed" for routers that can't pick
16926 a hostname: any router can call itself Unnamed; directory
16927 authorities will never allocate Unnamed to any particular router;
16928 clients won't believe that any router is the canonical Unnamed.
16929 - Only include function names in log messages for info/debug messages.
16930 For notice/warn/err, the content of the message should be clear on
16931 its own, and printing the function name only confuses users.
16932 - Avoid some false positives during reachability testing: don't try
16933 to test via a server that's on the same /24 as us.
16934 - If we fail to build a circuit to an intended enclave, and it's
16935 not mandatory that we use that enclave, stop wanting it.
16936 - When eventdns is enabled, allow multithreaded builds on NetBSD and
16937 OpenBSD. (We had previously disabled threads on these platforms
16938 because they didn't have working thread-safe resolver functions.)
16940 o Major bugfixes, anonymity/security:
16941 - If a client asked for a server by name, and there's a named server
16942 in our network-status but we don't have its descriptor yet, we
16943 could return an unnamed server instead.
16944 - Fix NetBSD bug that could allow someone to force uninitialized RAM
16945 to be sent to a server's DNS resolver. This only affects NetBSD
16946 and other platforms that do not bounds-check tolower().
16947 - Reject (most) attempts to use Tor circuits with length one. (If
16948 many people start using Tor as a one-hop proxy, exit nodes become
16949 a more attractive target for compromise.)
16950 - Just because your DirPort is open doesn't mean people should be
16951 able to remotely teach you about hidden service descriptors. Now
16952 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16954 o Major bugfixes, other:
16955 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
16956 - When a client asks the server to resolve (not connect to)
16957 an address, and it has a cached answer, give them the cached answer.
16958 Previously, the server would give them no answer at all.
16959 - Allow really slow clients to not hang up five minutes into their
16960 directory downloads (suggested by Adam J. Richter).
16961 - We were building exactly the wrong circuits when we anticipated
16962 hidden service requirements, meaning Tor would have to build all
16963 its circuits on demand.
16964 - Avoid crashing when we mmap a router cache file of size 0.
16965 - When testing reachability of our DirPort, don't launch new
16966 tests when there's already one in progress -- unreachable
16967 servers were stacking up dozens of testing streams.
16969 o Minor bugfixes, correctness:
16970 - If we're a directory mirror and we ask for "all" network status
16971 documents, we would discard status documents from authorities
16972 we don't recognize.
16973 - Avoid a memory corruption bug when creating a hash table for
16975 - Avoid controller-triggered crash when misusing certain commands
16976 from a v0 controller on platforms that do not handle
16977 printf("%s",NULL) gracefully.
16978 - Don't crash when a controller sends a third argument to an
16979 "extendcircuit" request.
16980 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16981 response; fix error code when "getinfo dir/status/" fails.
16982 - Avoid crash when telling controller stream-status and a stream
16984 - Patch from Adam Langley to fix assert() in eventdns.c.
16985 - Fix a debug log message in eventdns to say "X resolved to Y"
16986 instead of "X resolved to X".
16987 - Make eventdns give strings for DNS errors, not just error numbers.
16988 - Track unreachable entry guards correctly: don't conflate
16989 'unreachable by us right now' with 'listed as down by the directory
16990 authorities'. With the old code, if a guard was unreachable by
16991 us but listed as running, it would clog our guard list forever.
16992 - Behave correctly in case we ever have a network with more than
16993 2GB/s total advertised capacity.
16994 - Make TrackExitHosts case-insensitive, and fix the behavior of
16995 ".suffix" TrackExitHosts items to avoid matching in the middle of
16997 - Finally fix the openssl warnings from newer gccs that believe that
16998 ignoring a return value is okay, but casting a return value and
16999 then ignoring it is a sign of madness.
17000 - Prevent the contrib/exitlist script from printing the same
17001 result more than once.
17002 - Patch from Steve Hildrey: Generate network status correctly on
17003 non-versioning dirservers.
17004 - Don't listen to the X-Your-Address-Is hint if you did the lookup
17005 via Tor; otherwise you'll think you're the exit node's IP address.
17007 o Minor bugfixes, performance:
17008 - Two small performance improvements on parsing descriptors.
17009 - Major performance improvement on inserting descriptors: change
17010 algorithm from O(n^2) to O(n).
17011 - Make the common memory allocation path faster on machines where
17012 malloc(0) returns a pointer.
17013 - Start remembering X-Your-Address-Is directory hints even if you're
17014 a client, so you can become a server more smoothly.
17015 - Avoid duplicate entries on MyFamily line in server descriptor.
17017 o Packaging, features:
17018 - Remove architecture from OS X builds. The official builds are
17019 now universal binaries.
17020 - The Debian package now uses --verify-config when (re)starting,
17021 to distinguish configuration errors from other errors.
17022 - Update RPMs to require libevent 1.1b.
17024 o Packaging, bugfixes:
17025 - Patches so Tor builds with MinGW on Windows.
17026 - Patches so Tor might run on Cygwin again.
17027 - Resume building on non-gcc compilers and ancient gcc. Resume
17028 building with the -O0 compile flag. Resume building cleanly on
17030 - Run correctly on OS X platforms with case-sensitive filesystems.
17031 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
17032 - Add autoconf checks so Tor can build on Solaris x86 again.
17035 - Documented (and renamed) ServerDNSSearchDomains and
17036 ServerDNSResolvConfFile options.
17037 - Be clearer that the *ListenAddress directives can be repeated
17041 Changes in version 0.1.1.24 - 2006-09-29
17043 - Allow really slow clients to not hang up five minutes into their
17044 directory downloads (suggested by Adam J. Richter).
17045 - Fix major performance regression from 0.1.0.x: instead of checking
17046 whether we have enough directory information every time we want to
17047 do something, only check when the directory information has changed.
17048 This should improve client CPU usage by 25-50%.
17049 - Don't crash if, after a server has been running for a while,
17050 it can't resolve its hostname.
17053 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17054 - Don't crash when the controller receives a third argument to an
17055 "extendcircuit" request.
17056 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17057 response; fix error code when "getinfo dir/status/" fails.
17058 - Fix configure.in to not produce broken configure files with
17059 more recent versions of autoconf. Thanks to Clint for his auto*
17061 - Fix security bug on NetBSD that could allow someone to force
17062 uninitialized RAM to be sent to a server's DNS resolver. This
17063 only affects NetBSD and other platforms that do not bounds-check
17065 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17066 methods: these are known to be buggy.
17067 - If we're a directory mirror and we ask for "all" network status
17068 documents, we would discard status documents from authorities
17069 we don't recognize.
17072 Changes in version 0.1.2.1-alpha - 2006-08-27
17074 - Add "eventdns" async dns library from Adam Langley, tweaked to
17075 build on OSX and Windows. Only enabled if you pass the
17076 --enable-eventdns argument to configure.
17077 - Allow servers with no hostname or IP address to learn their
17078 IP address by asking the directory authorities. This code only
17079 kicks in when you would normally have exited with a "no address"
17080 error. Nothing's authenticated, so use with care.
17081 - Rather than waiting a fixed amount of time between retrying
17082 application connections, we wait only 5 seconds for the first,
17083 10 seconds for the second, and 15 seconds for each retry after
17084 that. Hopefully this will improve the expected user experience.
17085 - Patch from Tup to add support for transparent AP connections:
17086 this basically bundles the functionality of trans-proxy-tor
17087 into the Tor mainline. Now hosts with compliant pf/netfilter
17088 implementations can redirect TCP connections straight to Tor
17089 without diverting through SOCKS. Needs docs.
17090 - Busy directory servers save lots of memory by spooling server
17091 descriptors, v1 directories, and v2 networkstatus docs to buffers
17092 as needed rather than en masse. Also mmap the cached-routers
17093 files, so we don't need to keep the whole thing in memory too.
17094 - Automatically avoid picking more than one node from the same
17095 /16 network when constructing a circuit.
17096 - Revise and clean up the torrc.sample that we ship with; add
17097 a section for BandwidthRate and BandwidthBurst.
17100 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17101 split connection_t into edge, or, dir, control, and base structs.
17102 These will save quite a bit of memory on busy servers, and they'll
17103 also help us track down bugs in the code and bugs in the spec.
17104 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
17105 or later. Log when we are doing this, so we can diagnose it when
17106 it fails. (Also, recommend libevent 1.1b for kqueue and
17107 win32 methods; deprecate libevent 1.0b harder; make libevent
17108 recommendation system saner.)
17109 - Start being able to build universal binaries on OS X (thanks
17111 - Export the default exit policy via the control port, so controllers
17112 don't need to guess what it is / will be later.
17113 - Add a man page entry for ProtocolWarnings.
17114 - Add TestVia config option to the man page.
17115 - Remove even more protocol-related warnings from Tor server logs,
17116 such as bad TLS handshakes and malformed begin cells.
17117 - Stop fetching descriptors if you're not a dir mirror and you
17118 haven't tried to establish any circuits lately. [This currently
17119 causes some dangerous behavior, because when you start up again
17120 you'll use your ancient server descriptors.]
17121 - New DirPort behavior: if you have your dirport set, you download
17122 descriptors aggressively like a directory mirror, whether or not
17123 your ORPort is set.
17124 - Get rid of the router_retry_connections notion. Now routers
17125 no longer try to rebuild long-term connections to directory
17126 authorities, and directory authorities no longer try to rebuild
17127 long-term connections to all servers. We still don't hang up
17128 connections in these two cases though -- we need to look at it
17129 more carefully to avoid flapping, and we likely need to wait til
17130 0.1.1.x is obsolete.
17131 - Drop compatibility with obsolete Tors that permit create cells
17132 to have the wrong circ_id_type.
17133 - Re-enable per-connection rate limiting. Get rid of the "OP
17134 bandwidth" concept. Lay groundwork for "bandwidth classes" --
17135 separate global buckets that apply depending on what sort of conn
17137 - Start publishing one minute or so after we find our ORPort
17138 to be reachable. This will help reduce the number of descriptors
17139 we have for ourselves floating around, since it's quite likely
17140 other things (e.g. DirPort) will change during that minute too.
17141 - Fork the v1 directory protocol into its own spec document,
17142 and mark dir-spec.txt as the currently correct (v2) spec.
17145 - When we find our DirPort to be reachable, publish a new descriptor
17146 so we'll tell the world (reported by pnx).
17147 - Publish a new descriptor after we hup/reload. This is important
17148 if our config has changed such that we'll want to start advertising
17149 our DirPort now, etc.
17150 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17151 - When we have a state file we cannot parse, tell the user and
17152 move it aside. Now we avoid situations where the user starts
17153 Tor in 1904, Tor writes a state file with that timestamp in it,
17154 the user fixes her clock, and Tor refuses to start.
17155 - Fix configure.in to not produce broken configure files with
17156 more recent versions of autoconf. Thanks to Clint for his auto*
17158 - "tor --verify-config" now exits with -1(255) or 0 depending on
17159 whether the config options are bad or good.
17160 - Resolve bug 321 when using dnsworkers: append a period to every
17161 address we resolve at the exit node, so that we do not accidentally
17162 pick up local addresses, and so that failing searches are retried
17163 in the resolver search domains. (This is already solved for
17164 eventdns.) (This breaks Blossom servers for now.)
17165 - If we are using an exit enclave and we can't connect, e.g. because
17166 its webserver is misconfigured to not listen on localhost, then
17167 back off and try connecting from somewhere else before we fail.
17170 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
17171 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
17172 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17173 when the IP address is mapped through MapAddress to a hostname.
17174 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
17175 useless IPv6 DNS resolves.
17176 - Patch suggested by Karsten Loesing: respond to SIGNAL command
17177 before we execute the signal, in case the signal shuts us down.
17178 - Clean up AllowInvalidNodes man page entry.
17179 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17180 - Add more asserts to track down an assert error on a windows Tor
17181 server with connection_add being called with socket == -1.
17182 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17183 - Fix misleading log messages: an entry guard that is "unlisted",
17184 as well as not known to be "down" (because we've never heard
17185 of it), is not therefore "up".
17186 - Remove code to special-case "-cvs" ending, since it has not
17187 actually mattered since 0.0.9.
17188 - Make our socks5 handling more robust to broken socks clients:
17189 throw out everything waiting on the buffer in between socks
17190 handshake phases, since they can't possibly (so the theory
17191 goes) have predicted what we plan to respond to them.
17194 Changes in version 0.1.1.23 - 2006-07-30
17196 - Fast Tor servers, especially exit nodes, were triggering asserts
17197 due to a bug in handling the list of pending DNS resolves. Some
17198 bugs still remain here; we're hunting them.
17199 - Entry guards could crash clients by sending unexpected input.
17200 - More fixes on reachability testing: if you find yourself reachable,
17201 then don't ever make any client requests (so you stop predicting
17202 circuits), then hup or have your clock jump, then later your IP
17203 changes, you won't think circuits are working, so you won't try to
17204 test reachability, so you won't publish.
17207 - Avoid a crash if the controller does a resetconf firewallports
17208 and then a setconf fascistfirewall=1.
17209 - Avoid an integer underflow when the dir authority decides whether
17210 a router is stable: we might wrongly label it stable, and compute
17211 a slightly wrong median stability, when a descriptor is published
17213 - Fix a place where we might trigger an assert if we can't build our
17214 own server descriptor yet.
17217 Changes in version 0.1.1.22 - 2006-07-05
17219 - Fix a big bug that was causing servers to not find themselves
17220 reachable if they changed IP addresses. Since only 0.1.1.22+
17221 servers can do reachability testing correctly, now we automatically
17222 make sure to test via one of these.
17223 - Fix to allow clients and mirrors to learn directory info from
17224 descriptor downloads that get cut off partway through.
17225 - Directory authorities had a bug in deciding if a newly published
17226 descriptor was novel enough to make everybody want a copy -- a few
17227 servers seem to be publishing new descriptors many times a minute.
17229 - Fix a rare bug that was causing some servers to complain about
17230 "closing wedged cpuworkers" and skip some circuit create requests.
17231 - Make the Exit flag in directory status documents actually work.
17234 Changes in version 0.1.1.21 - 2006-06-10
17235 o Crash and assert fixes from 0.1.1.20:
17236 - Fix a rare crash on Tor servers that have enabled hibernation.
17237 - Fix a seg fault on startup for Tor networks that use only one
17238 directory authority.
17239 - Fix an assert from a race condition that occurs on Tor servers
17240 while exiting, where various threads are trying to log that they're
17241 exiting, and delete the logs, at the same time.
17242 - Make our unit tests pass again on certain obscure platforms.
17245 - Add support for building SUSE RPM packages.
17246 - Speed up initial bootstrapping for clients: if we are making our
17247 first ever connection to any entry guard, then don't mark it down
17249 - When only one Tor server in the network is labelled as a guard,
17250 and we've already picked him, we would cycle endlessly picking him
17251 again, being unhappy about it, etc. Now we specifically exclude
17252 current guards when picking a new guard.
17253 - Servers send create cells more reliably after the TLS connection
17254 is established: we were sometimes forgetting to send half of them
17255 when we had more than one pending.
17256 - If we get a create cell that asks us to extend somewhere, but the
17257 Tor server there doesn't match the expected digest, we now send
17258 a destroy cell back, rather than silently doing nothing.
17259 - Make options->RedirectExit work again.
17260 - Make cookie authentication for the controller work again.
17261 - Stop being picky about unusual characters in the arguments to
17262 mapaddress. It's none of our business.
17263 - Add a new config option "TestVia" that lets you specify preferred
17264 middle hops to use for test circuits. Perhaps this will let me
17265 debug the reachability problems better.
17267 o Log / documentation fixes:
17268 - If we're a server and some peer has a broken TLS certificate, don't
17269 log about it unless ProtocolWarnings is set, i.e., we want to hear
17270 about protocol violations by others.
17271 - Fix spelling of VirtualAddrNetwork in man page.
17272 - Add a better explanation at the top of the autogenerated torrc file
17273 about what happened to our old torrc.
17276 Changes in version 0.1.1.20 - 2006-05-23
17278 - Downgrade a log severity where servers complain that they're
17280 - Avoid a compile warning on FreeBSD.
17281 - Remove string size limit on NEWDESC messages; solve bug 291.
17282 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
17283 more thoroughly when we're running on windows.
17286 Changes in version 0.1.1.19-rc - 2006-05-03
17288 - Regenerate our local descriptor if it's dirty and we try to use
17289 it locally (e.g. if it changes during reachability detection).
17290 - If we setconf our ORPort to 0, we continued to listen on the
17291 old ORPort and receive connections.
17292 - Avoid a second warning about machine/limits.h on Debian
17294 - Be willing to add our own routerinfo into the routerlist.
17295 Now authorities will include themselves in their directories
17296 and network-statuses.
17297 - Stop trying to upload rendezvous descriptors to every
17298 directory authority: only try the v1 authorities.
17299 - Servers no longer complain when they think they're not
17300 registered with the directory authorities. There were too many
17302 - Backport dist-rpm changes so rpms can be built without errors.
17305 - Implement an option, VirtualAddrMask, to set which addresses
17306 get handed out in response to mapaddress requests. This works
17307 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17310 Changes in version 0.1.1.18-rc - 2006-04-10
17312 - Work harder to download live network-statuses from all the
17313 directory authorities we know about. Improve the threshold
17314 decision logic so we're more robust to edge cases.
17315 - When fetching rendezvous descriptors, we were willing to ask
17316 v2 authorities too, which would always return 404.
17319 - Stop listing down or invalid nodes in the v1 directory. This will
17320 reduce its bulk by about 1/3, and reduce load on directory
17322 - When deciding whether a router is Fast or Guard-worthy, consider
17323 his advertised BandwidthRate and not just the BandwidthCapacity.
17324 - No longer ship INSTALL and README files -- they are useless now.
17325 - Force rpmbuild to behave and honor target_cpu.
17326 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17327 - Start to include translated versions of the tor-doc-*.html
17328 files, along with the screenshots. Still needs more work.
17329 - Start sending back 512 and 451 errors if mapaddress fails,
17330 rather than not sending anything back at all.
17331 - When we fail to bind or listen on an incoming or outgoing
17332 socket, we should close it before failing. otherwise we just
17333 leak it. (thanks to weasel for finding.)
17334 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
17335 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
17336 - Make NoPublish (even though deprecated) work again.
17337 - Fix a minor security flaw where a versioning auth dirserver
17338 could list a recommended version many times in a row to make
17339 clients more convinced that it's recommended.
17340 - Fix crash bug if there are two unregistered servers running
17341 with the same nickname, one of them is down, and you ask for
17342 them by nickname in your EntryNodes or ExitNodes. Also, try
17343 to pick the one that's running rather than an arbitrary one.
17344 - Fix an infinite loop we could hit if we go offline for too long.
17345 - Complain when we hit WSAENOBUFS on recv() or write() too.
17346 Perhaps this will help us hunt the bug.
17347 - If you're not a versioning dirserver, don't put the string
17348 "client-versions \nserver-versions \n" in your network-status.
17349 - Lower the minimum required number of file descriptors to 1000,
17350 so we can have some overhead for Valgrind on Linux, where the
17351 default ulimit -n is 1024.
17354 - Add tor.dizum.com as the fifth authoritative directory server.
17355 - Add a new config option FetchUselessDescriptors, off by default,
17356 for when you plan to run "exitlist" on your client and you want
17357 to know about even the non-running descriptors.
17360 Changes in version 0.1.1.17-rc - 2006-03-28
17362 - Clients and servers since 0.1.1.10-alpha have been expiring
17363 connections whenever they are idle for 5 minutes and they *do*
17364 have circuits on them. Oops. With this new version, clients will
17365 discard their previous entry guard choices and avoid choosing
17366 entry guards running these flawed versions.
17367 - Fix memory leak when uncompressing concatenated zlib streams. This
17368 was causing substantial leaks over time on Tor servers.
17369 - The v1 directory was including servers as much as 48 hours old,
17370 because that's how the new routerlist->routers works. Now only
17371 include them if they're 20 hours old or less.
17374 - Resume building on irix64, netbsd 2.0, etc.
17375 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
17377 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17378 and it is confusing some users.
17379 - Mirrors stop caching the v1 directory so often.
17380 - Make the max number of old descriptors that a cache will hold
17381 rise with the number of directory authorities, so we can scale.
17382 - Change our win32 uname() hack to be more forgiving about what
17383 win32 versions it thinks it's found.
17386 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
17388 - When the controller's *setconf commands fail, collect an error
17389 message in a string and hand it back to the controller.
17390 - Make the v2 dir's "Fast" flag based on relative capacity, just
17391 like "Stable" is based on median uptime. Name everything in the
17392 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17393 - Log server fingerprint on startup, so new server operators don't
17394 have to go hunting around their filesystem for it.
17395 - Return a robots.txt on our dirport to discourage google indexing.
17396 - Let the controller ask for GETINFO dir/status/foo so it can ask
17397 directly rather than connecting to the dir port. Only works when
17398 dirport is set for now.
17400 o New config options rather than constants in the code:
17401 - SocksTimeout: How long do we let a socks connection wait
17402 unattached before we fail it?
17403 - CircuitBuildTimeout: Cull non-open circuits that were born
17404 at least this many seconds ago.
17405 - CircuitIdleTimeout: Cull open clean circuits that were born
17406 at least this many seconds ago.
17409 Changes in version 0.1.1.16-rc - 2006-03-18
17410 o Bugfixes on 0.1.1.15-rc:
17411 - Fix assert when the controller asks to attachstream a connect-wait
17412 or resolve-wait stream.
17413 - Now do address rewriting when the controller asks us to attach
17414 to a particular circuit too. This will let Blossom specify
17415 "moria2.exit" without having to learn what moria2's IP address is.
17416 - Make the "tor --verify-config" command-line work again, so people
17417 can automatically check if their torrc will parse.
17418 - Authoritative dirservers no longer require an open connection from
17419 a server to consider him "reachable". We need this change because
17420 when we add new auth dirservers, old servers won't know not to
17422 - Let Tor build on Sun CC again.
17423 - Fix an off-by-one buffer size in dirserv.c that magically never
17424 hit our three authorities but broke sjmurdoch's own tor network.
17425 - If we as a directory mirror don't know of any v1 directory
17426 authorities, then don't try to cache any v1 directories.
17427 - Stop warning about unknown servers in our family when they are
17428 given as hex digests.
17429 - Stop complaining as quickly to the server operator that he
17430 hasn't registered his nickname/key binding.
17431 - Various cleanups so we can add new V2 Auth Dirservers.
17432 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17433 reflect the updated flags in our v2 dir protocol.
17434 - Resume allowing non-printable characters for exit streams (both
17435 for connecting and for resolving). Now we tolerate applications
17436 that don't follow the RFCs. But continue to block malformed names
17439 o Bugfixes on 0.1.0.x:
17440 - Fix assert bug in close_logs(): when we close and delete logs,
17441 remove them all from the global "logfiles" list.
17442 - Fix minor integer overflow in calculating when we expect to use up
17443 our bandwidth allocation before hibernating.
17444 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
17445 there are multiple SSLs installed with different versions.
17446 - When we try to be a server and Address is not explicitly set and
17447 our hostname resolves to a private IP address, try to use an
17448 interface address if it has a public address. Now Windows machines
17449 that think of themselves as localhost can work by default.
17452 - Let the controller ask for GETINFO dir/server/foo so it can ask
17453 directly rather than connecting to the dir port.
17454 - Let the controller tell us about certain router descriptors
17455 that it doesn't want Tor to use in circuits. Implement
17456 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
17457 - New config option SafeSocks to reject all application connections
17458 using unsafe socks protocols. Defaults to off.
17461 Changes in version 0.1.1.15-rc - 2006-03-11
17462 o Bugfixes and cleanups:
17463 - When we're printing strings from the network, don't try to print
17464 non-printable characters. This protects us against shell escape
17465 sequence exploits, and also against attacks to fool humans into
17466 misreading their logs.
17467 - Fix a bug where Tor would fail to establish any connections if you
17468 left it off for 24 hours and then started it: we were happy with
17469 the obsolete network statuses, but they all referred to router
17470 descriptors that were too old to fetch, so we ended up with no
17471 valid router descriptors.
17472 - Fix a seg fault in the controller's "getinfo orconn-status"
17473 command while listing status on incoming handshaking connections.
17474 Introduce a status name "NEW" for these connections.
17475 - If we get a linelist or linelist_s config option from the torrc
17476 (e.g. ExitPolicy) and it has no value, warn and skip rather than
17477 silently resetting it to its default.
17478 - Don't abandon entry guards until they've been down or gone for
17480 - Cleaner and quieter log messages.
17483 - New controller signal NEWNYM that makes new application requests
17484 use clean circuits.
17485 - Add a new circuit purpose 'controller' to let the controller ask
17486 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
17487 controller command to let you specify the purpose if you're
17488 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
17489 command to let you change a circuit's purpose after it's been
17491 - Accept "private:*" in routerdesc exit policies; not generated yet
17492 because older Tors do not understand it.
17493 - Add BSD-style contributed startup script "rc.subr" from Peter
17497 Changes in version 0.1.1.14-alpha - 2006-02-20
17498 o Bugfixes on 0.1.1.x:
17499 - Don't die if we ask for a stdout or stderr log (even implicitly)
17500 and we're set to RunAsDaemon -- just warn.
17501 - We still had a few bugs in the OR connection rotation code that
17502 caused directory servers to slowly aggregate connections to other
17503 fast Tor servers. This time for sure!
17504 - Make log entries on Win32 include the name of the function again.
17505 - We were treating a pair of exit policies if they were equal even
17506 if one said accept and the other said reject -- causing us to
17507 not always publish a new descriptor since we thought nothing
17509 - Retry pending server downloads as well as pending networkstatus
17510 downloads when we unexpectedly get a socks request.
17511 - We were ignoring the IS_FAST flag in the directory status,
17512 meaning we were willing to pick trivial-bandwidth nodes for "fast"
17514 - If the controller's SAVECONF command fails (e.g. due to file
17515 permissions), let the controller know that it failed.
17518 - If we're trying to be a Tor server and running Windows 95/98/ME
17519 as a server, explain that we'll likely crash.
17520 - When we're a server, a client asks for an old-style directory,
17521 and our write bucket is empty, don't give it to him. This way
17522 small servers can continue to serve the directory *sometimes*,
17523 without getting overloaded.
17524 - Compress exit policies even more -- look for duplicate lines
17526 - Clients now honor the "guard" flag in the router status when
17527 picking entry guards, rather than looking at is_fast or is_stable.
17528 - Retain unrecognized lines in $DATADIR/state file, so that we can
17529 be forward-compatible.
17530 - Generate 18.0.0.0/8 address policy format in descs when we can;
17531 warn when the mask is not reducible to a bit-prefix.
17532 - Let the user set ControlListenAddress in the torrc. This can be
17533 dangerous, but there are some cases (like a secured LAN) where it
17535 - Split ReachableAddresses into ReachableDirAddresses and
17536 ReachableORAddresses, so we can restrict Dir conns to port 80
17537 and OR conns to port 443.
17538 - Now we can target arch and OS in rpm builds (contributed by
17539 Phobos). Also make the resulting dist-rpm filename match the
17541 - New config options to help controllers: FetchServerDescriptors
17542 and FetchHidServDescriptors for whether to fetch server
17543 info and hidserv info or let the controller do it, and
17544 PublishServerDescriptor and PublishHidServDescriptors.
17545 - Also let the controller set the __AllDirActionsPrivate config
17546 option if you want all directory fetches/publishes to happen via
17547 Tor (it assumes your controller bootstraps your circuits).
17550 Changes in version 0.1.0.17 - 2006-02-17
17551 o Crash bugfixes on 0.1.0.x:
17552 - When servers with a non-zero DirPort came out of hibernation,
17553 sometimes they would trigger an assert.
17555 o Other important bugfixes:
17556 - On platforms that don't have getrlimit (like Windows), we were
17557 artificially constraining ourselves to a max of 1024
17558 connections. Now just assume that we can handle as many as 15000
17559 connections. Hopefully this won't cause other problems.
17561 o Backported features:
17562 - When we're a server, a client asks for an old-style directory,
17563 and our write bucket is empty, don't give it to him. This way
17564 small servers can continue to serve the directory *sometimes*,
17565 without getting overloaded.
17566 - Whenever you get a 503 in response to a directory fetch, try
17567 once more. This will become important once servers start sending
17568 503's whenever they feel busy.
17569 - Fetch a new directory every 120 minutes, not every 40 minutes.
17570 Now that we have hundreds of thousands of users running the old
17571 directory algorithm, it's starting to hurt a lot.
17572 - Bump up the period for forcing a hidden service descriptor upload
17573 from 20 minutes to 1 hour.
17576 Changes in version 0.1.1.13-alpha - 2006-02-09
17577 o Crashes in 0.1.1.x:
17578 - When you tried to setconf ORPort via the controller, Tor would
17579 crash. So people using TorCP to become a server were sad.
17580 - Solve (I hope) the stack-smashing bug that we were seeing on fast
17581 servers. The problem appears to be something do with OpenSSL's
17582 random number generation, or how we call it, or something. Let me
17583 know if the crashes continue.
17584 - Turn crypto hardware acceleration off by default, until we find
17585 somebody smart who can test it for us. (It appears to produce
17586 seg faults in at least some cases.)
17587 - Fix a rare assert error when we've tried all intro points for
17588 a hidden service and we try fetching the service descriptor again:
17589 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
17592 - Fix a major load balance bug: we were round-robining in 16 KB
17593 chunks, and servers with bandwidthrate of 20 KB, while downloading
17594 a 600 KB directory, would starve their other connections. Now we
17595 try to be a bit more fair.
17596 - Dir authorities and mirrors were never expiring the newest
17597 descriptor for each server, causing memory and directory bloat.
17598 - Fix memory-bloating and connection-bloating bug on servers: We
17599 were never closing any connection that had ever had a circuit on
17600 it, because we were checking conn->n_circuits == 0, yet we had a
17601 bug that let it go negative.
17602 - Make Tor work using squid as your http proxy again -- squid
17603 returns an error if you ask for a URL that's too long, and it uses
17604 a really generic error message. Plus, many people are behind a
17605 transparent squid so they don't even realize it.
17606 - On platforms that don't have getrlimit (like Windows), we were
17607 artificially constraining ourselves to a max of 1024
17608 connections. Now just assume that we can handle as many as 15000
17609 connections. Hopefully this won't cause other problems.
17610 - Add a new config option ExitPolicyRejectPrivate which defaults to
17611 1. This means all exit policies will begin with rejecting private
17612 addresses, unless the server operator explicitly turns it off.
17615 - Clients no longer download descriptors for non-running
17617 - Before we add new directory authorities, we should make it
17618 clear that only v1 authorities should receive/publish hidden
17619 service descriptors.
17622 - As soon as we've fetched some more directory info, immediately
17623 try to download more server descriptors. This way we don't have
17624 a 10 second pause during initial bootstrapping.
17625 - Remove even more loud log messages that the server operator can't
17627 - When we're running an obsolete or un-recommended version, make
17628 the log message more clear about what the problem is and what
17629 versions *are* still recommended.
17630 - Provide a more useful warn message when our onion queue gets full:
17631 the CPU is too slow or the exit policy is too liberal.
17632 - Don't warn when we receive a 503 from a dirserver/cache -- this
17633 will pave the way for them being able to refuse if they're busy.
17634 - When we fail to bind a listener, try to provide a more useful
17635 log message: e.g., "Is Tor already running?"
17636 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
17637 Goldberg can prove things about our handshake protocol more
17639 - MaxConn has been obsolete for a while now. Document the ConnLimit
17640 config option, which is a *minimum* number of file descriptors
17641 that must be available else Tor refuses to start.
17642 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17643 if you log to syslog and want something other than LOG_DAEMON.
17644 - Make dirservers generate a separate "guard" flag to mean,
17645 "would make a good entry guard". Make clients parse it and vote
17646 on it. Not used by clients yet.
17647 - Implement --with-libevent-dir option to ./configure. Also, improve
17648 search techniques to find libevent, and use those for openssl too.
17649 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
17650 - Only start testing reachability once we've established a
17651 circuit. This will make startup on dirservers less noisy.
17652 - Don't try to upload hidden service descriptors until we have
17653 established a circuit.
17654 - Fix the controller's "attachstream 0" command to treat conn like
17655 it just connected, doing address remapping, handling .exit and
17656 .onion idioms, and so on. Now we're more uniform in making sure
17657 that the controller hears about new and closing connections.
17660 Changes in version 0.1.1.12-alpha - 2006-01-11
17661 o Bugfixes on 0.1.1.x:
17662 - The fix to close duplicate server connections was closing all
17663 Tor client connections if they didn't establish a circuit
17664 quickly enough. Oops.
17665 - Fix minor memory issue (double-free) that happened on exit.
17667 o Bugfixes on 0.1.0.x:
17668 - Tor didn't warn when it failed to open a log file.
17671 Changes in version 0.1.1.11-alpha - 2006-01-10
17672 o Crashes in 0.1.1.x:
17673 - Include all the assert/crash fixes from 0.1.0.16.
17674 - If you start Tor and then quit very quickly, there were some
17675 races that tried to free things that weren't allocated yet.
17676 - Fix a rare memory stomp if you're running hidden services.
17677 - Fix segfault when specifying DirServer in config without nickname.
17678 - Fix a seg fault when you finish connecting to a server but at
17679 that moment you dump his server descriptor.
17680 - Extendcircuit and Attachstream controller commands would
17681 assert/crash if you don't give them enough arguments.
17682 - Fix an assert error when we're out of space in the connection_list
17683 and we try to post a hidden service descriptor (reported by weasel).
17684 - If you specify a relative torrc path and you set RunAsDaemon in
17685 your torrc, then it chdir()'s to the new directory. If you HUP,
17686 it tries to load the new torrc location, fails, and exits.
17687 The fix: no longer allow a relative path to torrc using -f.
17690 - Implement "entry guards": automatically choose a handful of entry
17691 nodes and stick with them for all circuits. Only pick new guards
17692 when the ones you have are unsuitable, and if the old guards
17693 become suitable again, switch back. This will increase security
17694 dramatically against certain end-point attacks. The EntryNodes
17695 config option now provides some hints about which entry guards you
17696 want to use most; and StrictEntryNodes means to only use those.
17697 - New directory logic: download by descriptor digest, not by
17698 fingerprint. Caches try to download all listed digests from
17699 authorities; clients try to download "best" digests from caches.
17700 This avoids partitioning and isolating attacks better.
17701 - Make the "stable" router flag in network-status be the median of
17702 the uptimes of running valid servers, and make clients pay
17703 attention to the network-status flags. Thus the cutoff adapts
17704 to the stability of the network as a whole, making IRC, IM, etc
17705 connections more reliable.
17708 - Tor servers with dynamic IP addresses were needing to wait 18
17709 hours before they could start doing reachability testing using
17710 the new IP address and ports. This is because they were using
17711 the internal descriptor to learn what to test, yet they were only
17712 rebuilding the descriptor once they decided they were reachable.
17713 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
17714 to download certain server descriptors, throw them away, and then
17715 fetch them again after 30 minutes. Now mirrors throw away these
17716 server descriptors so clients can't get them.
17717 - We were leaving duplicate connections to other ORs open for a week,
17718 rather than closing them once we detect a duplicate. This only
17719 really affected authdirservers, but it affected them a lot.
17720 - Spread the authdirservers' reachability testing over the entire
17721 testing interval, so we don't try to do 500 TLS's at once every
17725 - If the network is down, and we try to connect to a conn because
17726 we have a circuit in mind, and we timeout (30 seconds) because the
17727 network never answers, we were expiring the circuit, but we weren't
17728 obsoleting the connection or telling the entry_guards functions.
17729 - Some Tor servers process billions of cells per day. These statistics
17730 need to be uint64_t's.
17731 - Check for integer overflows in more places, when adding elements
17732 to smartlists. This could possibly prevent a buffer overflow
17733 on malicious huge inputs. I don't see any, but I haven't looked
17735 - ReachableAddresses kept growing new "reject *:*" lines on every
17737 - When you "setconf log" via the controller, it should remove all
17738 logs. We were automatically adding back in a "log notice stdout".
17739 - Newly bootstrapped Tor networks couldn't establish hidden service
17740 circuits until they had nodes with high uptime. Be more tolerant.
17741 - We were marking servers down when they could not answer every piece
17742 of the directory request we sent them. This was far too harsh.
17743 - Fix the torify (tsocks) config file to not use Tor for localhost
17745 - Directory authorities now go to the proper authority when asking for
17746 a networkstatus, even when they want a compressed one.
17747 - Fix a harmless bug that was causing Tor servers to log
17748 "Got an end because of misc error, but we're not an AP. Closing."
17749 - Authorities were treating their own descriptor changes as cosmetic,
17750 meaning the descriptor available in the network-status and the
17751 descriptor that clients downloaded were different.
17752 - The OS X installer was adding a symlink for tor_resolve but
17753 the binary was called tor-resolve (reported by Thomas Hardly).
17754 - Workaround a problem with some http proxies where they refuse GET
17755 requests that specify "Content-Length: 0" (reported by Adrian).
17756 - Fix wrong log message when you add a "HiddenServiceNodes" config
17757 line without any HiddenServiceDir line (reported by Chris Thomas).
17760 - Write the TorVersion into the state file so we have a prayer of
17761 keeping forward and backward compatibility.
17762 - Revive the FascistFirewall config option rather than eliminating it:
17763 now it's a synonym for ReachableAddresses *:80,*:443.
17764 - Clients choose directory servers from the network status lists,
17765 not from their internal list of router descriptors. Now they can
17766 go to caches directly rather than needing to go to authorities
17768 - Directory authorities ignore router descriptors that have only
17769 cosmetic differences: do this for 0.1.0.x servers now too.
17770 - Add a new flag to network-status indicating whether the server
17771 can answer v2 directory requests too.
17772 - Authdirs now stop whining so loudly about bad descriptors that
17773 they fetch from other dirservers. So when there's a log complaint,
17774 it's for sure from a freshly uploaded descriptor.
17775 - Reduce memory requirements in our structs by changing the order
17777 - There used to be two ways to specify your listening ports in a
17778 server descriptor: on the "router" line and with a separate "ports"
17779 line. Remove support for the "ports" line.
17780 - New config option "AuthDirRejectUnlisted" for auth dirservers as
17781 a panic button: if we get flooded with unusable servers we can
17782 revert to only listing servers in the approved-routers file.
17783 - Auth dir servers can now mark a fingerprint as "!reject" or
17784 "!invalid" in the approved-routers file (as its nickname), to
17785 refuse descriptors outright or include them but marked as invalid.
17786 - Servers store bandwidth history across restarts/crashes.
17787 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17788 get a better idea of why their circuits failed. Not used yet.
17789 - Directory mirrors now cache up to 16 unrecognized network-status
17790 docs. Now we can add new authdirservers and they'll be cached too.
17791 - When picking a random directory, prefer non-authorities if any
17793 - New controller option "getinfo desc/all-recent" to fetch the
17794 latest server descriptor for every router that Tor knows about.
17797 Changes in version 0.1.0.16 - 2006-01-02
17798 o Crash bugfixes on 0.1.0.x:
17799 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17800 corrupting the heap, losing FDs, or crashing when we need to resize
17801 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17802 - It turns out sparc64 platforms crash on unaligned memory access
17803 too -- so detect and avoid this.
17804 - Handle truncated compressed data correctly (by detecting it and
17806 - Fix possible-but-unlikely free(NULL) in control.c.
17807 - When we were closing connections, there was a rare case that
17808 stomped on memory, triggering seg faults and asserts.
17809 - Avoid potential infinite recursion when building a descriptor. (We
17810 don't know that it ever happened, but better to fix it anyway.)
17811 - We were neglecting to unlink marked circuits from soon-to-close OR
17812 connections, which caused some rare scribbling on freed memory.
17813 - Fix a memory stomping race bug when closing the joining point of two
17814 rendezvous circuits.
17815 - Fix an assert in time parsing found by Steven Murdoch.
17817 o Other bugfixes on 0.1.0.x:
17818 - When we're doing reachability testing, provide more useful log
17819 messages so the operator knows what to expect.
17820 - Do not check whether DirPort is reachable when we are suppressing
17821 advertising it because of hibernation.
17822 - When building with -static or on Solaris, we sometimes needed -ldl.
17823 - When we're deciding whether a stream has enough circuits around
17824 that can handle it, count the freshly dirty ones and not the ones
17825 that are so dirty they won't be able to handle it.
17826 - When we're expiring old circuits, we had a logic error that caused
17827 us to close new rendezvous circuits rather than old ones.
17828 - Give a more helpful log message when you try to change ORPort via
17829 the controller: you should upgrade Tor if you want that to work.
17830 - We were failing to parse Tor versions that start with "Tor ".
17831 - Tolerate faulty streams better: when a stream fails for reason
17832 exitpolicy, stop assuming that the router is lying about his exit
17833 policy. When a stream fails for reason misc, allow it to retry just
17834 as if it was resolvefailed. When a stream has failed three times,
17835 reset its failure count so we can try again and get all three tries.
17838 Changes in version 0.1.1.10-alpha - 2005-12-11
17839 o Correctness bugfixes on 0.1.0.x:
17840 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17841 corrupting the heap, losing FDs, or crashing when we need to resize
17842 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17843 - Stop doing the complex voodoo overkill checking for insecure
17844 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17845 - When we were closing connections, there was a rare case that
17846 stomped on memory, triggering seg faults and asserts.
17847 - We were neglecting to unlink marked circuits from soon-to-close OR
17848 connections, which caused some rare scribbling on freed memory.
17849 - When we're deciding whether a stream has enough circuits around
17850 that can handle it, count the freshly dirty ones and not the ones
17851 that are so dirty they won't be able to handle it.
17852 - Recover better from TCP connections to Tor servers that are
17853 broken but don't tell you (it happens!); and rotate TLS
17854 connections once a week.
17855 - When we're expiring old circuits, we had a logic error that caused
17856 us to close new rendezvous circuits rather than old ones.
17857 - Fix a scary-looking but apparently harmless bug where circuits
17858 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17859 servers, and never switch to state CIRCUIT_STATE_OPEN.
17860 - When building with -static or on Solaris, we sometimes needed to
17862 - Give a useful message when people run Tor as the wrong user,
17863 rather than telling them to start chowning random directories.
17864 - We were failing to inform the controller about new .onion streams.
17866 o Security bugfixes on 0.1.0.x:
17867 - Refuse server descriptors if the fingerprint line doesn't match
17868 the included identity key. Tor doesn't care, but other apps (and
17869 humans) might actually be trusting the fingerprint line.
17870 - We used to kill the circuit when we receive a relay command we
17871 don't recognize. Now we just drop it.
17872 - Start obeying our firewall options more rigorously:
17873 . If we can't get to a dirserver directly, try going via Tor.
17874 . Don't ever try to connect (as a client) to a place our
17875 firewall options forbid.
17876 . If we specify a proxy and also firewall options, obey the
17877 firewall options even when we're using the proxy: some proxies
17878 can only proxy to certain destinations.
17879 - Fix a bug found by Lasse Overlier: when we were making internal
17880 circuits (intended to be cannibalized later for rendezvous and
17881 introduction circuits), we were picking them so that they had
17882 useful exit nodes. There was no need for this, and it actually
17883 aids some statistical attacks.
17884 - Start treating internal circuits and exit circuits separately.
17885 It's important to keep them separate because internal circuits
17886 have their last hops picked like middle hops, rather than like
17887 exit hops. So exiting on them will break the user's expectations.
17889 o Bugfixes on 0.1.1.x:
17890 - Take out the mis-feature where we tried to detect IP address
17891 flapping for people with DynDNS, and chose not to upload a new
17892 server descriptor sometimes.
17893 - Try to be compatible with OpenSSL 0.9.6 again.
17894 - Log fix: when the controller is logging about .onion addresses,
17895 sometimes it didn't include the ".onion" part of the address.
17896 - Don't try to modify options->DirServers internally -- if the
17897 user didn't specify any, just add the default ones directly to
17898 the trusted dirserver list. This fixes a bug where people running
17899 controllers would use SETCONF on some totally unrelated config
17900 option, and Tor would start yelling at them about changing their
17902 - Let the controller's redirectstream command specify a port, in
17903 case the controller wants to change that too.
17904 - When we requested a pile of server descriptors, we sometimes
17905 accidentally launched a duplicate request for the first one.
17906 - Bugfix for trackhostexits: write down the fingerprint of the
17907 chosen exit, not its nickname, because the chosen exit might not
17909 - When parsing foo.exit, if foo is unknown, and we are leaving
17910 circuits unattached, set the chosen_exit field and leave the
17911 address empty. This matters because controllers got confused
17913 - Directory authorities no longer try to download server
17914 descriptors that they know they will reject.
17916 o Features and updates:
17917 - Replace balanced trees with hash tables: this should make stuff
17918 significantly faster.
17919 - Resume using the AES counter-mode implementation that we ship,
17920 rather than OpenSSL's. Ours is significantly faster.
17921 - Many other CPU and memory improvements.
17922 - Add a new config option FastFirstHopPK (on by default) so clients
17923 do a trivial crypto handshake for their first hop, since TLS has
17924 already taken care of confidentiality and authentication.
17925 - Add a new config option TestSocks so people can see if their
17926 applications are using socks4, socks4a, socks5-with-ip, or
17927 socks5-with-hostname. This way they don't have to keep mucking
17928 with tcpdump and wondering if something got cached somewhere.
17929 - Warn when listening on a public address for socks. I suspect a
17930 lot of people are setting themselves up as open socks proxies,
17931 and they have no idea that jerks on the Internet are using them,
17932 since they simply proxy the traffic into the Tor network.
17933 - Add "private:*" as an alias in configuration for policies. Now
17934 you can simplify your exit policy rather than needing to list
17935 every single internal or nonroutable network space.
17936 - Add a new controller event type that allows controllers to get
17937 all server descriptors that were uploaded to a router in its role
17938 as authoritative dirserver.
17939 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17940 tor-doc-server.html, and stylesheet.css in the tarball.
17941 - Stop shipping tor-doc.html in the tarball.
17944 Changes in version 0.1.1.9-alpha - 2005-11-15
17945 o Usability improvements:
17946 - Start calling it FooListenAddress rather than FooBindAddress,
17947 since few of our users know what it means to bind an address
17949 - Reduce clutter in server logs. We're going to try to make
17950 them actually usable now. New config option ProtocolWarnings that
17951 lets you hear about how _other Tors_ are breaking the protocol. Off
17953 - Divide log messages into logging domains. Once we put some sort
17954 of interface on this, it will let people looking at more verbose
17955 log levels specify the topics they want to hear more about.
17956 - Make directory servers return better http 404 error messages
17957 instead of a generic "Servers unavailable".
17958 - Check for even more Windows version flags when writing the platform
17959 string in server descriptors, and note any we don't recognize.
17960 - Clean up more of the OpenSSL memory when exiting, so we can detect
17961 memory leaks better.
17962 - Make directory authorities be non-versioning, non-naming by
17963 default. Now we can add new directory servers without requiring
17964 their operators to pay close attention.
17965 - When logging via syslog, include the pid whenever we provide
17966 a log entry. Suggested by Todd Fries.
17968 o Performance improvements:
17969 - Directory servers now silently throw away new descriptors that
17970 haven't changed much if the timestamps are similar. We do this to
17971 tolerate older Tor servers that upload a new descriptor every 15
17972 minutes. (It seemed like a good idea at the time.)
17973 - Inline bottleneck smartlist functions; use fast versions by default.
17974 - Add a "Map from digest to void*" abstraction digestmap_t so we
17975 can do less hex encoding/decoding. Use it in router_get_by_digest()
17976 to resolve a performance bottleneck.
17977 - Allow tor_gzip_uncompress to extract as much as possible from
17978 truncated compressed data. Try to extract as many
17979 descriptors as possible from truncated http responses (when
17980 DIR_PURPOSE_FETCH_ROUTERDESC).
17981 - Make circ->onionskin a pointer, not a static array. moria2 was using
17982 125000 circuit_t's after it had been up for a few weeks, which
17983 translates to 20+ megs of wasted space.
17984 - The private half of our EDH handshake keys are now chosen out
17985 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17987 o Security improvements:
17988 - Start making directory caches retain old routerinfos, so soon
17989 clients can start asking by digest of descriptor rather than by
17990 fingerprint of server.
17991 - Add half our entropy from RAND_poll in OpenSSL. This knows how
17992 to use egd (if present), openbsd weirdness (if present), vms/os2
17993 weirdness (if we ever port there), and more in the future.
17995 o Bugfixes on 0.1.0.x:
17996 - Do round-robin writes of at most 16 kB per write. This might be
17997 more fair on loaded Tor servers, and it might resolve our Windows
17998 crash bug. It might also slow things down.
17999 - Our TLS handshakes were generating a single public/private
18000 keypair for the TLS context, rather than making a new one for
18001 each new connections. Oops. (But we were still rotating them
18002 periodically, so it's not so bad.)
18003 - When we were cannibalizing a circuit with a particular exit
18004 node in mind, we weren't checking to see if that exit node was
18005 already present earlier in the circuit. Oops.
18006 - When a Tor server's IP changes (e.g. from a dyndns address),
18007 upload a new descriptor so clients will learn too.
18008 - Really busy servers were keeping enough circuits open on stable
18009 connections that they were wrapping around the circuit_id
18010 space. (It's only two bytes.) This exposed a bug where we would
18011 feel free to reuse a circuit_id even if it still exists but has
18012 been marked for close. Try to fix this bug. Some bug remains.
18013 - If we would close a stream early (e.g. it asks for a .exit that
18014 we know would refuse it) but the LeaveStreamsUnattached config
18015 option is set by the controller, then don't close it.
18017 o Bugfixes on 0.1.1.8-alpha:
18018 - Fix a big pile of memory leaks, some of them serious.
18019 - Do not try to download a routerdesc if we would immediately reject
18021 - Resume inserting a newline between all router descriptors when
18022 generating (old style) signed directories, since our spec says
18024 - When providing content-type application/octet-stream for
18025 server descriptors using .z, we were leaving out the
18026 content-encoding header. Oops. (Everything tolerated this just
18027 fine, but that doesn't mean we need to be part of the problem.)
18028 - Fix a potential seg fault in getconf and getinfo using version 1
18029 of the controller protocol.
18030 - Avoid crash: do not check whether DirPort is reachable when we
18031 are suppressing it because of hibernation.
18032 - Make --hash-password not crash on exit.
18035 Changes in version 0.1.1.8-alpha - 2005-10-07
18036 o New features (major):
18037 - Clients don't download or use the directory anymore. Now they
18038 download and use network-statuses from the trusted dirservers,
18039 and fetch individual server descriptors as needed from mirrors.
18040 See dir-spec.txt for all the gory details.
18041 - Be more conservative about whether to advertise our DirPort.
18042 The main change is to not advertise if we're running at capacity
18043 and either a) we could hibernate or b) our capacity is low and
18044 we're using a default DirPort.
18045 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
18047 o New features (minor):
18048 - Try to be smart about when to retry network-status and
18049 server-descriptor fetches. Still needs some tuning.
18050 - Stop parsing, storing, or using running-routers output (but
18051 mirrors still cache and serve it).
18052 - Consider a threshold of versioning dirservers (dirservers who have
18053 an opinion about which Tor versions are still recommended) before
18054 deciding whether to warn the user that he's obsolete.
18055 - Dirservers can now reject/invalidate by key and IP, with the
18056 config options "AuthDirInvalid" and "AuthDirReject". This is
18057 useful since currently we automatically list servers as running
18058 and usable even if we know they're jerks.
18059 - Provide dire warnings to any users who set DirServer; move it out
18060 of torrc.sample and into torrc.complete.
18061 - Add MyFamily to torrc.sample in the server section.
18062 - Add nicknames to the DirServer line, so we can refer to them
18063 without requiring all our users to memorize their IP addresses.
18064 - When we get an EOF or a timeout on a directory connection, note
18065 how many bytes of serverdesc we are dropping. This will help
18066 us determine whether it is smart to parse incomplete serverdesc
18068 - Add a new function to "change pseudonyms" -- that is, to stop
18069 using any currently-dirty circuits for new streams, so we don't
18070 link new actions to old actions. Currently it's only called on
18071 HUP (or SIGNAL RELOAD).
18072 - On sighup, if UseHelperNodes changed to 1, use new circuits.
18073 - Start using RAND_bytes rather than RAND_pseudo_bytes from
18074 OpenSSL. Also, reseed our entropy every hour, not just at
18075 startup. And entropy in 512-bit chunks, not 160-bit chunks.
18077 o Fixes on 0.1.1.7-alpha:
18078 - Nobody ever implemented EVENT_ADDRMAP for control protocol
18079 version 0, so don't let version 0 controllers ask for it.
18080 - If you requested something with too many newlines via the
18081 v1 controller protocol, you could crash tor.
18082 - Fix a number of memory leaks, including some pretty serious ones.
18083 - Re-enable DirPort testing again, so Tor servers will be willing
18084 to advertise their DirPort if it's reachable.
18085 - On TLS handshake, only check the other router's nickname against
18086 its expected nickname if is_named is set.
18088 o Fixes forward-ported from 0.1.0.15:
18089 - Don't crash when we don't have any spare file descriptors and we
18090 try to spawn a dns or cpu worker.
18091 - Make the numbers in read-history and write-history into uint64s,
18092 so they don't overflow and publish negatives in the descriptor.
18094 o Fixes on 0.1.0.x:
18095 - For the OS X package's modified privoxy config file, comment
18096 out the "logfile" line so we don't log everything passed
18098 - We were whining about using socks4 or socks5-with-local-lookup
18099 even when it's an IP in the "virtual" range we designed exactly
18101 - We were leaking some memory every time the client changes IPs.
18102 - Never call free() on tor_malloc()d memory. This will help us
18103 use dmalloc to detect memory leaks.
18104 - Check for named servers when looking them up by nickname;
18105 warn when we'recalling a non-named server by its nickname;
18106 don't warn twice about the same name.
18107 - Try to list MyFamily elements by key, not by nickname, and warn
18108 if we've not heard of the server.
18109 - Make windows platform detection (uname equivalent) smarter.
18110 - It turns out sparc64 doesn't like unaligned access either.
18113 Changes in version 0.1.0.15 - 2005-09-23
18114 o Bugfixes on 0.1.0.x:
18115 - Reject ports 465 and 587 (spam targets) in default exit policy.
18116 - Don't crash when we don't have any spare file descriptors and we
18117 try to spawn a dns or cpu worker.
18118 - Get rid of IgnoreVersion undocumented config option, and make us
18119 only warn, never exit, when we're running an obsolete version.
18120 - Don't try to print a null string when your server finds itself to
18121 be unreachable and the Address config option is empty.
18122 - Make the numbers in read-history and write-history into uint64s,
18123 so they don't overflow and publish negatives in the descriptor.
18124 - Fix a minor memory leak in smartlist_string_remove().
18125 - We were only allowing ourselves to upload a server descriptor at
18126 most every 20 minutes, even if it changed earlier than that.
18127 - Clean up log entries that pointed to old URLs.
18130 Changes in version 0.1.1.7-alpha - 2005-09-14
18131 o Fixes on 0.1.1.6-alpha:
18132 - Exit servers were crashing when people asked them to make a
18133 connection to an address not in their exit policy.
18134 - Looking up a non-existent stream for a v1 control connection would
18136 - Fix a seg fault if we ask a dirserver for a descriptor by
18137 fingerprint but he doesn't know about him.
18138 - SETCONF was appending items to linelists, not clearing them.
18139 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
18140 out and refuse the setconf if it would fail.
18141 - Downgrade the dirserver log messages when whining about
18145 - Add Peter Palfrader's check-tor script to tor/contrib/
18146 It lets you easily check whether a given server (referenced by
18147 nickname) is reachable by you.
18148 - Numerous changes to move towards client-side v2 directories. Not
18151 o Fixes on 0.1.0.x:
18152 - If the user gave tor an odd number of command-line arguments,
18153 we were silently ignoring the last one. Now we complain and fail.
18154 [This wins the oldest-bug prize -- this bug has been present since
18155 November 2002, as released in Tor 0.0.0.]
18156 - Do not use unaligned memory access on alpha, mips, or mipsel.
18157 It *works*, but is very slow, so we treat them as if it doesn't.
18158 - Retry directory requests if we fail to get an answer we like
18159 from a given dirserver (we were retrying before, but only if
18160 we fail to connect).
18161 - When writing the RecommendedVersions line, sort them first.
18162 - When the client asked for a rendezvous port that the hidden
18163 service didn't want to provide, we were sending an IP address
18164 back along with the end cell. Fortunately, it was zero. But stop
18166 - Correct "your server is reachable" log entries to indicate that
18167 it was self-testing that told us so.
18170 Changes in version 0.1.1.6-alpha - 2005-09-09
18171 o Fixes on 0.1.1.5-alpha:
18172 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
18173 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
18174 - Fix bug with tor_memmem finding a match at the end of the string.
18175 - Make unit tests run without segfaulting.
18176 - Resolve some solaris x86 compile warnings.
18177 - Handle duplicate lines in approved-routers files without warning.
18178 - Fix bug where as soon as a server refused any requests due to his
18179 exit policy (e.g. when we ask for localhost and he tells us that's
18180 127.0.0.1 and he won't do it), we decided he wasn't obeying his
18181 exit policy using him for any exits.
18182 - Only do openssl hardware accelerator stuff if openssl version is
18185 o New controller features/fixes:
18186 - Add a "RESETCONF" command so you can set config options like
18187 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
18188 a config option in the torrc with no value, then it clears it
18189 entirely (rather than setting it to its default).
18190 - Add a "GETINFO config-file" to tell us where torrc is.
18191 - Avoid sending blank lines when GETINFO replies should be empty.
18192 - Add a QUIT command for the controller (for using it manually).
18193 - Fix a bug in SAVECONF that was adding default dirservers and
18194 other redundant entries to the torrc file.
18196 o Start on the new directory design:
18197 - Generate, publish, cache, serve new network-status format.
18198 - Publish individual descriptors (by fingerprint, by "all", and by
18200 - Publish client and server recommended versions separately.
18201 - Allow tor_gzip_uncompress() to handle multiple concatenated
18202 compressed strings. Serve compressed groups of router
18203 descriptors. The compression logic here could be more
18205 - Distinguish v1 authorities (all currently trusted directories)
18206 from v2 authorities (all trusted directories).
18207 - Change DirServers config line to note which dirs are v1 authorities.
18208 - Add configuration option "V1AuthoritativeDirectory 1" which
18209 moria1, moria2, and tor26 should set.
18210 - Remove option when getting directory cache to see whether they
18211 support running-routers; they all do now. Replace it with one
18212 to see whether caches support v2 stuff.
18215 - Dirservers now do their own external reachability testing of each
18216 Tor server, and only list them as running if they've been found to
18217 be reachable. We also send back warnings to the server's logs if
18218 it uploads a descriptor that we already believe is unreachable.
18219 - Implement exit enclaves: if we know an IP address for the
18220 destination, and there's a running Tor server at that address
18221 which allows exit to the destination, then extend the circuit to
18222 that exit first. This provides end-to-end encryption and end-to-end
18223 authentication. Also, if the user wants a .exit address or enclave,
18224 use 4 hops rather than 3, and cannibalize a general circ for it
18226 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
18227 controller. Also, rotate dns and cpu workers if the controller
18228 changes options that will affect them; and initialize the dns
18229 worker cache tree whether or not we start out as a server.
18230 - Only upload a new server descriptor when options change, 18
18231 hours have passed, uptime is reset, or bandwidth changes a lot.
18232 - Check [X-]Forwarded-For headers in HTTP requests when generating
18233 log messages. This lets people run dirservers (and caches) behind
18234 Apache but still know which IP addresses are causing warnings.
18236 o Config option changes:
18237 - Replace (Fascist)Firewall* config options with a new
18238 ReachableAddresses option that understands address policies.
18239 For example, "ReachableAddresses *:80,*:443"
18240 - Get rid of IgnoreVersion undocumented config option, and make us
18241 only warn, never exit, when we're running an obsolete version.
18242 - Make MonthlyAccountingStart config option truly obsolete now.
18244 o Fixes on 0.1.0.x:
18245 - Reject ports 465 and 587 in the default exit policy, since
18246 people have started using them for spam too.
18247 - It turns out we couldn't bootstrap a network since we added
18248 reachability detection in 0.1.0.1-rc. Good thing the Tor network
18249 has never gone down. Add an AssumeReachable config option to let
18250 servers and dirservers bootstrap. When we're trying to build a
18251 high-uptime or high-bandwidth circuit but there aren't enough
18252 suitable servers, try being less picky rather than simply failing.
18253 - Our logic to decide if the OR we connected to was the right guy
18254 was brittle and maybe open to a mitm for unverified routers.
18255 - We weren't cannibalizing circuits correctly for
18256 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
18257 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
18258 build those from scratch. This should make hidden services faster.
18259 - Predict required circuits better, with an eye toward making hidden
18260 services faster on the service end.
18261 - Retry streams if the exit node sends back a 'misc' failure. This
18262 should result in fewer random failures. Also, after failing
18263 from resolve failed or misc, reset the num failures, so we give
18264 it a fair shake next time we try.
18265 - Clean up the rendezvous warn log msgs, and downgrade some to info.
18266 - Reduce severity on logs about dns worker spawning and culling.
18267 - When we're shutting down and we do something like try to post a
18268 server descriptor or rendezvous descriptor, don't complain that
18269 we seem to be unreachable. Of course we are, we're shutting down.
18270 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
18271 We don't use them yet, but maybe one day our DNS resolver will be
18272 able to discover them.
18273 - Make ContactInfo mandatory for authoritative directory servers.
18274 - Require server descriptors to list IPv4 addresses -- hostnames
18275 are no longer allowed. This also fixes some potential security
18276 problems with people providing hostnames as their address and then
18277 preferentially resolving them to partition users.
18278 - Change log line for unreachability to explicitly suggest /etc/hosts
18279 as the culprit. Also make it clearer what IP address and ports we're
18280 testing for reachability.
18281 - Put quotes around user-supplied strings when logging so users are
18282 more likely to realize if they add bad characters (like quotes)
18284 - Let auth dir servers start without specifying an Address config
18286 - Make unit tests (and other invocations that aren't the real Tor)
18287 run without launching listeners, creating subdirectories, and so on.
18290 Changes in version 0.1.1.5-alpha - 2005-08-08
18291 o Bugfixes included in 0.1.0.14.
18293 o Bugfixes on 0.1.0.x:
18294 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
18295 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
18296 it would silently using ignore the 6668.
18299 Changes in version 0.1.0.14 - 2005-08-08
18300 o Bugfixes on 0.1.0.x:
18301 - Fix the other half of the bug with crypto handshakes
18303 - Fix an assert trigger if you send a 'signal term' via the
18304 controller when it's listening for 'event info' messages.
18307 Changes in version 0.1.1.4-alpha - 2005-08-04
18308 o Bugfixes included in 0.1.0.13.
18311 - Improve tor_gettimeofday() granularity on windows.
18312 - Make clients regenerate their keys when their IP address changes.
18313 - Implement some more GETINFO goodness: expose helper nodes, config
18314 options, getinfo keys.
18317 Changes in version 0.1.0.13 - 2005-08-04
18318 o Bugfixes on 0.1.0.x:
18319 - Fix a critical bug in the security of our crypto handshakes.
18320 - Fix a size_t underflow in smartlist_join_strings2() that made
18321 it do bad things when you hand it an empty smartlist.
18322 - Fix Windows installer to ship Tor license (thanks to Aphex for
18323 pointing out this oversight) and put a link to the doc directory
18325 - Explicitly set no-unaligned-access for sparc: it turns out the
18326 new gcc's let you compile broken code, but that doesn't make it
18330 Changes in version 0.1.1.3-alpha - 2005-07-23
18331 o Bugfixes on 0.1.1.2-alpha:
18332 - Fix a bug in handling the controller's "post descriptor"
18334 - Fix several bugs in handling the controller's "extend circuit"
18336 - Fix a bug in handling the controller's "stream status" event.
18337 - Fix an assert failure if we have a controller listening for
18338 circuit events and we go offline.
18339 - Re-allow hidden service descriptors to publish 0 intro points.
18340 - Fix a crash when generating your hidden service descriptor if
18341 you don't have enough intro points already.
18343 o New features on 0.1.1.2-alpha:
18344 - New controller function "getinfo accounting", to ask how
18345 many bytes we've used in this time period.
18346 - Experimental support for helper nodes: a lot of the risk from
18347 a small static adversary comes because users pick new random
18348 nodes every time they rebuild a circuit. Now users will try to
18349 stick to the same small set of entry nodes if they can. Not
18350 enabled by default yet.
18352 o Bugfixes on 0.1.0.12:
18353 - If you're an auth dir server, always publish your dirport,
18354 even if you haven't yet found yourself to be reachable.
18355 - Fix a size_t underflow in smartlist_join_strings2() that made
18356 it do bad things when you hand it an empty smartlist.
18359 Changes in version 0.1.0.12 - 2005-07-18
18360 o New directory servers:
18361 - tor26 has changed IP address.
18363 o Bugfixes on 0.1.0.x:
18364 - Fix a possible double-free in tor_gzip_uncompress().
18365 - When --disable-threads is set, do not search for or link against
18366 pthreads libraries.
18367 - Don't trigger an assert if an authoritative directory server
18368 claims its dirport is 0.
18369 - Fix bug with removing Tor as an NT service: some people were
18370 getting "The service did not return an error." Thanks to Matt
18374 Changes in version 0.1.1.2-alpha - 2005-07-15
18375 o New directory servers:
18376 - tor26 has changed IP address.
18378 o Bugfixes on 0.1.0.x, crashes/leaks:
18379 - Port the servers-not-obeying-their-exit-policies fix from
18381 - Fix an fd leak in start_daemon().
18382 - On Windows, you can't always reopen a port right after you've
18383 closed it. So change retry_listeners() to only close and re-open
18384 ports that have changed.
18385 - Fix a possible double-free in tor_gzip_uncompress().
18387 o Bugfixes on 0.1.0.x, usability:
18388 - When tor_socketpair() fails in Windows, give a reasonable
18389 Windows-style errno back.
18390 - Let people type "tor --install" as well as "tor -install" when
18392 want to make it an NT service.
18393 - NT service patch from Matt Edman to improve error messages.
18394 - When the controller asks for a config option with an abbreviated
18395 name, give the full name in our response.
18396 - Correct the man page entry on TrackHostExitsExpire.
18397 - Looks like we were never delivering deflated (i.e. compressed)
18398 running-routers lists, even when asked. Oops.
18399 - When --disable-threads is set, do not search for or link against
18400 pthreads libraries.
18402 o Bugfixes on 0.1.1.x:
18403 - Fix a seg fault with autodetecting which controller version is
18407 - New hidden service descriptor format: put a version in it, and
18408 let people specify introduction/rendezvous points that aren't
18409 in "the directory" (which is subjective anyway).
18410 - Allow the DEBUG controller event to work again. Mark certain log
18411 entries as "don't tell this to controllers", so we avoid cycles.
18414 Changes in version 0.1.0.11 - 2005-06-30
18415 o Bugfixes on 0.1.0.x:
18416 - Fix major security bug: servers were disregarding their
18417 exit policies if clients behaved unexpectedly.
18418 - Make OS X init script check for missing argument, so we don't
18419 confuse users who invoke it incorrectly.
18420 - Fix a seg fault in "tor --hash-password foo".
18421 - The MAPADDRESS control command was broken.
18424 Changes in version 0.1.1.1-alpha - 2005-06-29
18426 - Make OS X init script check for missing argument, so we don't
18427 confuse users who invoke it incorrectly.
18428 - Fix a seg fault in "tor --hash-password foo".
18429 - Fix a possible way to DoS dirservers.
18430 - When we complain that your exit policy implicitly allows local or
18431 private address spaces, name them explicitly so operators can
18433 - Make the log message less scary when all the dirservers are
18434 temporarily unreachable.
18435 - We were printing the number of idle dns workers incorrectly when
18439 - Revised controller protocol (version 1) that uses ascii rather
18440 than binary. Add supporting libraries in python and java so you
18441 can use the controller from your applications without caring how
18442 our protocol works.
18443 - Spiffy new support for crypto hardware accelerators. Can somebody
18447 Changes in version 0.0.9.10 - 2005-06-16
18448 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18449 - Refuse relay cells that claim to have a length larger than the
18450 maximum allowed. This prevents a potential attack that could read
18451 arbitrary memory (e.g. keys) from an exit server's process
18455 Changes in version 0.1.0.10 - 2005-06-14
18456 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
18457 libevent before 1.1a.
18460 Changes in version 0.1.0.9-rc - 2005-06-09
18462 - Reset buf->highwater every time buf_shrink() is called, not just on
18463 a successful shrink. This was causing significant memory bloat.
18464 - Fix buffer overflow when checking hashed passwords.
18465 - Security fix: if seeding the RNG on Win32 fails, quit.
18466 - Allow seeding the RNG on Win32 even when you're not running as
18468 - Disable threading on Solaris too. Something is wonky with it,
18469 cpuworkers, and reentrant libs.
18470 - Reenable the part of the code that tries to flush as soon as an
18471 OR outbuf has a full TLS record available. Perhaps this will make
18472 OR outbufs not grow as huge except in rare cases, thus saving lots
18473 of CPU time plus memory.
18474 - Reject malformed .onion addresses rather then passing them on as
18475 normal web requests.
18476 - Adapt patch from Adam Langley: fix possible memory leak in
18477 tor_lookup_hostname().
18478 - Initialize libevent later in the startup process, so the logs are
18479 already established by the time we start logging libevent warns.
18480 - Use correct errno on win32 if libevent fails.
18481 - Check and warn about known-bad/slow libevent versions.
18482 - Pay more attention to the ClientOnly config option.
18483 - Have torctl.in/tor.sh.in check for location of su binary (needed
18485 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
18486 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
18487 HttpProxyAuthenticator
18488 - Stop warning about sigpipes in the logs. We're going to
18489 pretend that getting these occassionally is normal and fine.
18490 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
18492 installer screens; and don't put stuff into StartupItems unless
18493 the user asks you to.
18494 - Require servers that use the default dirservers to have public IP
18495 addresses. We have too many servers that are configured with private
18496 IPs and their admins never notice the log entries complaining that
18497 their descriptors are being rejected.
18498 - Add OSX uninstall instructions. An actual uninstall script will
18502 Changes in version 0.1.0.8-rc - 2005-05-23
18504 - It turns out that kqueue on OS X 10.3.9 was causing kernel
18505 panics. Disable kqueue on all OS X Tors.
18506 - Fix RPM: remove duplicate line accidentally added to the rpm
18508 - Disable threads on openbsd too, since its gethostaddr is not
18510 - Tolerate libevent 0.8 since it still works, even though it's
18512 - Enable building on Red Hat 9.0 again.
18513 - Allow the middle hop of the testing circuit to be running any
18514 version, now that most of them have the bugfix to let them connect
18515 to unknown servers. This will allow reachability testing to work
18516 even when 0.0.9.7-0.0.9.9 become obsolete.
18517 - Handle relay cells with rh.length too large. This prevents
18518 a potential attack that could read arbitrary memory (maybe even
18519 keys) from the exit server's process.
18520 - We screwed up the dirport reachability testing when we don't yet
18521 have a cached version of the directory. Hopefully now fixed.
18522 - Clean up router_load_single_router() (used by the controller),
18523 so it doesn't seg fault on error.
18524 - Fix a minor memory leak when somebody establishes an introduction
18525 point at your Tor server.
18526 - If a socks connection ends because read fails, don't warn that
18527 you're not sending a socks reply back.
18530 - Add HttpProxyAuthenticator config option too, that works like
18531 the HttpsProxyAuthenticator config option.
18532 - Encode hashed controller passwords in hex instead of base64,
18533 to make it easier to write controllers.
18536 Changes in version 0.1.0.7-rc - 2005-05-17
18538 - Fix a bug in the OS X package installer that prevented it from
18539 installing on Tiger.
18540 - Fix a script bug in the OS X package installer that made it
18541 complain during installation.
18542 - Find libevent even if it's hiding in /usr/local/ and your
18543 CFLAGS and LDFLAGS don't tell you to look there.
18544 - Be able to link with libevent as a shared library (the default
18545 after 1.0d), even if it's hiding in /usr/local/lib and even
18546 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18547 assuming you're running gcc. Otherwise fail and give a useful
18549 - Fix a bug in the RPM packager: set home directory for _tor to
18550 something more reasonable when first installing.
18551 - Free a minor amount of memory that is still reachable on exit.
18554 Changes in version 0.1.0.6-rc - 2005-05-14
18556 - Implement --disable-threads configure option. Disable threads on
18557 netbsd by default, because it appears to have no reentrant resolver
18559 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
18560 release (1.1) detects and disables kqueue if it's broken.
18561 - Append default exit policy before checking for implicit internal
18562 addresses. Now we don't log a bunch of complaints on startup
18563 when using the default exit policy.
18564 - Some people were putting "Address " in their torrc, and they had
18565 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18566 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18567 LOCALSTATEDIR/tor instead.
18568 - Fix fragmented-message bug in TorControl.py.
18569 - Resolve a minor bug which would prevent unreachable dirports
18570 from getting suppressed in the published descriptor.
18571 - When the controller gave us a new descriptor, we weren't resolving
18572 it immediately, so Tor would think its address was 0.0.0.0 until
18573 we fetched a new directory.
18574 - Fix an uppercase/lowercase case error in suppressing a bogus
18575 libevent warning on some Linuxes.
18578 - Begin scrubbing sensitive strings from logs by default. Turn off
18579 the config option SafeLogging if you need to do debugging.
18580 - Switch to a new buffer management algorithm, which tries to avoid
18581 reallocing and copying quite as much. In first tests it looks like
18582 it uses *more* memory on average, but less cpu.
18583 - First cut at support for "create-fast" cells. Clients can use
18584 these when extending to their first hop, since the TLS already
18585 provides forward secrecy and authentication. Not enabled on
18587 - When dirservers refuse a router descriptor, we now log its
18588 contactinfo, platform, and the poster's IP address.
18589 - Call tor_free_all instead of connections_free_all after forking, to
18590 save memory on systems that need to fork.
18591 - Whine at you if you're a server and you don't set your contactinfo.
18592 - Implement --verify-config command-line option to check if your torrc
18593 is valid without actually launching Tor.
18594 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
18595 rather than just rejecting it.
18598 Changes in version 0.1.0.5-rc - 2005-04-27
18600 - Stop trying to print a null pointer if an OR conn fails because
18601 we didn't like its cert.
18603 - Switch our internal buffers implementation to use a ring buffer,
18604 to hopefully improve performance for fast servers a lot.
18605 - Add HttpsProxyAuthenticator support (basic auth only), based
18606 on patch from Adam Langley.
18607 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18608 the fast servers that have been joining lately.
18609 - Give hidden service accesses extra time on the first attempt,
18610 since 60 seconds is often only barely enough. This might improve
18612 - Improve performance for dirservers: stop re-parsing the whole
18613 directory every time you regenerate it.
18614 - Add more debugging info to help us find the weird dns freebsd
18615 pthreads bug; cleaner debug messages to help track future issues.
18618 Changes in version 0.0.9.9 - 2005-04-23
18619 o Bugfixes on 0.0.9.x:
18620 - If unofficial Tor clients connect and send weird TLS certs, our
18621 Tor server triggers an assert. This release contains a minimal
18622 backport from the broader fix that we put into 0.1.0.4-rc.
18625 Changes in version 0.1.0.4-rc - 2005-04-23
18627 - If unofficial Tor clients connect and send weird TLS certs, our
18628 Tor server triggers an assert. Stop asserting, and start handling
18629 TLS errors better in other situations too.
18630 - When the controller asks us to tell it about all the debug-level
18631 logs, it turns out we were generating debug-level logs while
18632 telling it about them, which turns into a bad loop. Now keep
18633 track of whether you're sending a debug log to the controller,
18634 and don't log when you are.
18635 - Fix the "postdescriptor" feature of the controller interface: on
18636 non-complete success, only say "done" once.
18638 - Clients are now willing to load balance over up to 2mB, not 1mB,
18639 of advertised bandwidth capacity.
18640 - Add a NoPublish config option, so you can be a server (e.g. for
18641 testing running Tor servers in other Tor networks) without
18642 publishing your descriptor to the primary dirservers.
18645 Changes in version 0.1.0.3-rc - 2005-04-08
18646 o Improvements on 0.1.0.2-rc:
18647 - Client now retries when streams end early for 'hibernating' or
18648 'resource limit' reasons, rather than failing them.
18649 - More automated handling for dirserver operators:
18650 - Automatically approve nodes running 0.1.0.2-rc or later,
18651 now that the the reachability detection stuff is working.
18652 - Now we allow two unverified servers with the same nickname
18653 but different keys. But if a nickname is verified, only that
18654 nickname+key are allowed.
18655 - If you're an authdirserver connecting to an address:port,
18656 and it's not the OR you were expecting, forget about that
18657 descriptor. If he *was* the one you were expecting, then forget
18658 about all other descriptors for that address:port.
18659 - Allow servers to publish descriptors from 12 hours in the future.
18660 Corollary: only whine about clock skew from the dirserver if
18661 he's a trusted dirserver (since now even verified servers could
18662 have quite wrong clocks).
18663 - Adjust maximum skew and age for rendezvous descriptors: let skew
18664 be 48 hours rather than 90 minutes.
18665 - Efficiency improvements:
18666 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18667 it much faster to look up a circuit for each relay cell.
18668 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18669 since they're eating our cpu on exit nodes.
18670 - Stop wasting time doing a case insensitive comparison for every
18671 dns name every time we do any lookup. Canonicalize the names to
18672 lowercase and be done with it.
18673 - Start sending 'truncated' cells back rather than destroy cells,
18674 if the circuit closes in front of you. This means we won't have
18675 to abandon partially built circuits.
18676 - Only warn once per nickname from add_nickname_list_to_smartlist
18677 per failure, so an entrynode or exitnode choice that's down won't
18679 - Put a note in the torrc about abuse potential with the default
18681 - Revise control spec and implementation to allow all log messages to
18682 be sent to controller with their severities intact (suggested by
18683 Matt Edman). Update TorControl to handle new log event types.
18684 - Provide better explanation messages when controller's POSTDESCRIPTOR
18686 - Stop putting nodename in the Platform string in server descriptors.
18687 It doesn't actually help, and it is confusing/upsetting some people.
18689 o Bugfixes on 0.1.0.2-rc:
18690 - We were printing the host mask wrong in exit policies in server
18691 descriptors. This isn't a critical bug though, since we were still
18692 obeying the exit policy internally.
18693 - Fix Tor when compiled with libevent but without pthreads: move
18694 connection_unregister() from _connection_free() to
18696 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
18697 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
18698 when we look through the connection array, we'll find any of the
18699 cpu/dnsworkers. This is no good.
18701 o Bugfixes on 0.0.9.8:
18702 - Fix possible bug on threading platforms (e.g. win32) which was
18703 leaking a file descriptor whenever a cpuworker or dnsworker died.
18704 - When using preferred entry or exit nodes, ignore whether the
18705 circuit wants uptime or capacity. They asked for the nodes, they
18707 - chdir() to your datadirectory at the *end* of the daemonize process,
18708 not the beginning. This was a problem because the first time you
18709 run tor, if your datadir isn't there, and you have runasdaemon set
18710 to 1, it will try to chdir to it before it tries to create it. Oops.
18711 - Handle changed router status correctly when dirserver reloads
18712 fingerprint file. We used to be dropping all unverified descriptors
18713 right then. The bug was hidden because we would immediately
18714 fetch a directory from another dirserver, which would include the
18715 descriptors we just dropped.
18716 - When we're connecting to an OR and he's got a different nickname/key
18717 than we were expecting, only complain loudly if we're an OP or a
18718 dirserver. Complaining loudly to the OR admins just confuses them.
18719 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18720 artificially capped at 500kB.
18723 Changes in version 0.0.9.8 - 2005-04-07
18724 o Bugfixes on 0.0.9.x:
18725 - We have a bug that I haven't found yet. Sometimes, very rarely,
18726 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18727 thinks of itself as idle. This meant that no new circuits ever got
18728 established. Here's a workaround to kill any cpuworker that's been
18729 busy for more than 100 seconds.
18732 Changes in version 0.1.0.2-rc - 2005-04-01
18733 o Bugfixes on 0.1.0.1-rc:
18734 - Fixes on reachability detection:
18735 - Don't check for reachability while hibernating.
18736 - If ORPort is reachable but DirPort isn't, still publish the
18737 descriptor, but zero out DirPort until it's found reachable.
18738 - When building testing circs for ORPort testing, use only
18739 high-bandwidth nodes, so fewer circuits fail.
18740 - Complain about unreachable ORPort separately from unreachable
18741 DirPort, so the user knows what's going on.
18742 - Make sure we only conclude ORPort reachability if we didn't
18743 initiate the conn. Otherwise we could falsely conclude that
18744 we're reachable just because we connected to the guy earlier
18745 and he used that same pipe to extend to us.
18746 - Authdirservers shouldn't do ORPort reachability detection,
18747 since they're in clique mode, so it will be rare to find a
18748 server not already connected to them.
18749 - When building testing circuits, always pick middle hops running
18750 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18751 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18753 - When we decide we're reachable, actually publish our descriptor
18755 - Fix bug in redirectstream in the controller.
18756 - Fix the state descriptor strings so logs don't claim edge streams
18757 are in a different state than they actually are.
18758 - Use recent libevent features when possible (this only really affects
18759 win32 and osx right now, because the new libevent with these
18760 features hasn't been released yet). Add code to suppress spurious
18762 - Prevent possible segfault in connection_close_unattached_ap().
18763 - Fix newlines on torrc in win32.
18764 - Improve error msgs when tor-resolve fails.
18766 o Improvements on 0.0.9.x:
18767 - New experimental script tor/contrib/ExerciseServer.py (needs more
18768 work) that uses the controller interface to build circuits and
18769 fetch pages over them. This will help us bootstrap servers that
18770 have lots of capacity but haven't noticed it yet.
18771 - New experimental script tor/contrib/PathDemo.py (needs more work)
18772 that uses the controller interface to let you choose whole paths
18774 "<hostname>.<path,separated by dots>.<length of path>.path"
18775 - When we've connected to an OR and handshaked but didn't like
18776 the result, we were closing the conn without sending destroy
18777 cells back for pending circuits. Now send those destroys.
18780 Changes in version 0.0.9.7 - 2005-04-01
18781 o Bugfixes on 0.0.9.x:
18782 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18783 - Compare identity to identity, not to nickname, when extending to
18784 a router not already in the directory. This was preventing us from
18785 extending to unknown routers. Oops.
18786 - Make sure to create OS X Tor user in <500 range, so we aren't
18787 creating actual system users.
18788 - Note where connection-that-hasn't-sent-end was marked, and fix
18789 a few really loud instances of this harmless bug (it's fixed more
18793 Changes in version 0.1.0.1-rc - 2005-03-28
18795 - Add reachability testing. Your Tor server will automatically try
18796 to see if its ORPort and DirPort are reachable from the outside,
18797 and it won't upload its descriptor until it decides they are.
18798 - Handle unavailable hidden services better. Handle slow or busy
18799 hidden services better.
18800 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18802 - New exit policy: accept most low-numbered ports, rather than
18803 rejecting most low-numbered ports.
18804 - More Tor controller support (still experimental). See
18805 http://tor.eff.org/doc/control-spec.txt for all the new features,
18806 including signals to emulate unix signals from any platform;
18807 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18808 closestream; closecircuit; etc.
18809 - Make nt services work and start on startup on win32 (based on
18810 patch by Matt Edman).
18811 - Add a new AddressMap config directive to rewrite incoming socks
18812 addresses. This lets you, for example, declare an implicit
18813 required exit node for certain sites.
18814 - Add a new TrackHostExits config directive to trigger addressmaps
18815 for certain incoming socks addresses -- for sites that break when
18816 your exit keeps changing (based on patch by Mike Perry).
18817 - Redo the client-side dns cache so it's just an addressmap too.
18818 - Notice when our IP changes, and reset stats/uptime/reachability.
18819 - When an application is using socks5, give him the whole variety of
18820 potential socks5 responses (connect refused, host unreachable, etc),
18821 rather than just "success" or "failure".
18822 - A more sane version numbering system. See
18823 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18824 - New contributed script "exitlist": a simple python script to
18825 parse directories and find Tor nodes that exit to listed
18827 - New contributed script "privoxy-tor-toggle" to toggle whether
18828 Privoxy uses Tor. Seems to be configured for Debian by default.
18829 - Report HTTP reasons to client when getting a response from directory
18830 servers -- so you can actually know what went wrong.
18831 - New config option MaxAdvertisedBandwidth which lets you advertise
18832 a low bandwidthrate (to not attract as many circuits) while still
18833 allowing a higher bandwidthrate in reality.
18835 o Robustness/stability fixes:
18836 - Make Tor use Niels Provos's libevent instead of its current
18837 poll-but-sometimes-select mess. This will let us use faster async
18838 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
18840 - pthread support now too. This was forced because when we forked,
18841 we ended up wasting a lot of duplicate ram over time. Also switch
18842 to foo_r versions of some library calls to allow reentry and
18844 - Better handling for heterogeneous / unreliable nodes:
18845 - Annotate circuits w/ whether they aim to contain high uptime nodes
18846 and/or high capacity nodes. When building circuits, choose
18848 - This means that every single node in an intro rend circuit,
18849 not just the last one, will have a minimum uptime.
18850 - New config option LongLivedPorts to indicate application streams
18851 that will want high uptime circuits.
18852 - Servers reset uptime when a dir fetch entirely fails. This
18853 hopefully reflects stability of the server's network connectivity.
18854 - If somebody starts his tor server in Jan 2004 and then fixes his
18855 clock, don't make his published uptime be a year.
18856 - Reset published uptime when you wake up from hibernation.
18857 - Introduce a notion of 'internal' circs, which are chosen without
18858 regard to the exit policy of the last hop. Intro and rendezvous
18859 circs must be internal circs, to avoid leaking information. Resolve
18860 and connect streams can use internal circs if they want.
18861 - New circuit pooling algorithm: make sure to have enough circs around
18862 to satisfy any predicted ports, and also make sure to have 2 internal
18863 circs around if we've required internal circs lately (and with high
18864 uptime if we've seen that lately too).
18865 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18866 which describes how often we retry making new circuits if current
18867 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18868 how long we're willing to make use of an already-dirty circuit.
18869 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18870 circ as necessary, if there are any completed ones lying around
18871 when we try to launch one.
18872 - Make hidden services try to establish a rendezvous for 30 seconds,
18873 rather than for n (where n=3) attempts to build a circuit.
18874 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
18875 "ShutdownWaitLength".
18876 - Try to be more zealous about calling connection_edge_end when
18877 things go bad with edge conns in connection.c.
18878 - Revise tor-spec to add more/better stream end reasons.
18879 - Revise all calls to connection_edge_end to avoid sending "misc",
18880 and to take errno into account where possible.
18883 - Fix a race condition that can trigger an assert, when we have a
18884 pending create cell and an OR connection fails right then.
18885 - Fix several double-mark-for-close bugs, e.g. where we were finding
18886 a conn for a cell even if that conn is already marked for close.
18887 - Make sequence of log messages when starting on win32 with no config
18888 file more reasonable.
18889 - When choosing an exit node for a new non-internal circ, don't take
18890 into account whether it'll be useful for any pending x.onion
18891 addresses -- it won't.
18892 - Turn addr_policy_compare from a tristate to a quadstate; this should
18893 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18894 for google.com" problem.
18895 - Make "platform" string in descriptor more accurate for Win32 servers,
18896 so it's not just "unknown platform".
18897 - Fix an edge case in parsing config options (thanks weasel).
18898 If they say "--" on the commandline, it's not an option.
18899 - Reject odd-looking addresses at the client (e.g. addresses that
18900 contain a colon), rather than having the server drop them because
18902 - tor-resolve requests were ignoring .exit if there was a working circuit
18903 they could use instead.
18904 - REUSEADDR on normal platforms means you can rebind to the port
18905 right after somebody else has let it go. But REUSEADDR on win32
18906 means to let you bind to the port _even when somebody else
18907 already has it bound_! So, don't do that on Win32.
18908 - Change version parsing logic: a version is "obsolete" if it is not
18909 recommended and (1) there is a newer recommended version in the
18910 same series, or (2) there are no recommended versions in the same
18911 series, but there are some recommended versions in a newer series.
18912 A version is "new" if it is newer than any recommended version in
18914 - Stop most cases of hanging up on a socks connection without sending
18918 - Require BandwidthRate to be at least 20kB/s for servers.
18919 - When a dirserver causes you to give a warn, mention which dirserver
18921 - New config option DirAllowPrivateAddresses for authdirservers.
18922 Now by default they refuse router descriptors that have non-IP or
18923 private-IP addresses.
18924 - Stop publishing socksport in the directory, since it's not
18925 actually meant to be public. For compatibility, publish a 0 there
18927 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18928 smart" value, that is low for servers and high for clients.
18929 - If our clock jumps forward by 100 seconds or more, assume something
18930 has gone wrong with our network and abandon all not-yet-used circs.
18931 - Warn when exit policy implicitly allows local addresses.
18932 - If we get an incredibly skewed timestamp from a dirserver mirror
18933 that isn't a verified OR, don't warn -- it's probably him that's
18935 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18936 cookies to disk and doesn't log each web request to disk. (Thanks
18937 to Brett Carrington for pointing this out.)
18938 - When a client asks us for a dir mirror and we don't have one,
18939 launch an attempt to get a fresh one.
18940 - If we're hibernating and we get a SIGINT, exit immediately.
18941 - Add --with-dmalloc ./configure option, to track memory leaks.
18942 - And try to free all memory on closing, so we can detect what
18944 - Cache local dns resolves correctly even when they're .exit
18946 - Give a better warning when some other server advertises an
18947 ORPort that is actually an apache running ssl.
18948 - Add "opt hibernating 1" to server descriptor to make it clearer
18949 whether the server is hibernating.
18952 Changes in version 0.0.9.6 - 2005-03-24
18953 o Bugfixes on 0.0.9.x (crashes and asserts):
18954 - Add new end stream reasons to maintainance branch. Fix bug where
18955 reason (8) could trigger an assert. Prevent bug from recurring.
18956 - Apparently win32 stat wants paths to not end with a slash.
18957 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18958 blowing away the circuit that conn->cpath_layer points to, then
18959 checking to see if the circ is well-formed. Backport check to make
18960 sure we dont use the cpath on a closed connection.
18961 - Prevent circuit_resume_edge_reading_helper() from trying to package
18962 inbufs for marked-for-close streams.
18963 - Don't crash on hup if your options->address has become unresolvable.
18964 - Some systems (like OS X) sometimes accept() a connection and tell
18965 you the remote host is 0.0.0.0:0. If this happens, due to some
18966 other mis-features, we get confused; so refuse the conn for now.
18968 o Bugfixes on 0.0.9.x (other):
18969 - Fix harmless but scary "Unrecognized content encoding" warn message.
18970 - Add new stream error reason: TORPROTOCOL reason means "you are not
18971 speaking a version of Tor I understand; say bye-bye to your stream."
18972 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18973 into the future, now that we are more tolerant of skew. This
18974 resolves a bug where a Tor server would refuse to cache a directory
18975 because all the directories it gets are too far in the future;
18976 yet the Tor server never logs any complaints about clock skew.
18977 - Mac packaging magic: make man pages useable, and do not overwrite
18978 existing torrc files.
18979 - Make OS X log happily to /var/log/tor/tor.log
18982 Changes in version 0.0.9.5 - 2005-02-22
18983 o Bugfixes on 0.0.9.x:
18984 - Fix an assert race at exit nodes when resolve requests fail.
18985 - Stop picking unverified dir mirrors--it only leads to misery.
18986 - Patch from Matt Edman to make NT services work better. Service
18987 support is still not compiled into the executable by default.
18988 - Patch from Dmitri Bely so the Tor service runs better under
18989 the win32 SYSTEM account.
18990 - Make tor-resolve actually work (?) on Win32.
18991 - Fix a sign bug when getrlimit claims to have 4+ billion
18992 file descriptors available.
18993 - Stop refusing to start when bandwidthburst == bandwidthrate.
18994 - When create cells have been on the onion queue more than five
18995 seconds, just send back a destroy and take them off the list.
18998 Changes in version 0.0.9.4 - 2005-02-03
18999 o Bugfixes on 0.0.9:
19000 - Fix an assert bug that took down most of our servers: when
19001 a server claims to have 1 GB of bandwidthburst, don't
19003 - Don't crash as badly if we have spawned the max allowed number
19004 of dnsworkers, or we're out of file descriptors.
19005 - Block more file-sharing ports in the default exit policy.
19006 - MaxConn is now automatically set to the hard limit of max
19007 file descriptors we're allowed (ulimit -n), minus a few for
19009 - Give a clearer message when servers need to raise their
19010 ulimit -n when they start running out of file descriptors.
19011 - SGI Compatibility patches from Jan Schaumann.
19012 - Tolerate a corrupt cached directory better.
19013 - When a dirserver hasn't approved your server, list which one.
19014 - Go into soft hibernation after 95% of the bandwidth is used,
19015 not 99%. This is especially important for daily hibernators who
19016 have a small accounting max. Hopefully it will result in fewer
19017 cut connections when the hard hibernation starts.
19018 - Load-balance better when using servers that claim more than
19019 800kB/s of capacity.
19020 - Make NT services work (experimental, only used if compiled in).
19023 Changes in version 0.0.9.3 - 2005-01-21
19024 o Bugfixes on 0.0.9:
19025 - Backport the cpu use fixes from main branch, so busy servers won't
19026 need as much processor time.
19027 - Work better when we go offline and then come back, or when we
19028 run Tor at boot before the network is up. We do this by
19029 optimistically trying to fetch a new directory whenever an
19030 application request comes in and we think we're offline -- the
19031 human is hopefully a good measure of when the network is back.
19032 - Backport some minimal hidserv bugfixes: keep rend circuits open as
19033 long as you keep using them; actually publish hidserv descriptors
19034 shortly after they change, rather than waiting 20-40 minutes.
19035 - Enable Mac startup script by default.
19036 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
19037 - When you update AllowUnverifiedNodes or FirewallPorts via the
19038 controller's setconf feature, we were always appending, never
19040 - When you update HiddenServiceDir via setconf, it was screwing up
19041 the order of reading the lines, making it fail.
19042 - Do not rewrite a cached directory back to the cache; otherwise we
19043 will think it is recent and not fetch a newer one on startup.
19044 - Workaround for webservers that lie about Content-Encoding: Tor
19045 now tries to autodetect compressed directories and compression
19046 itself. This lets us Proxypass dir fetches through apache.
19049 Changes in version 0.0.9.2 - 2005-01-04
19050 o Bugfixes on 0.0.9 (crashes and asserts):
19051 - Fix an assert on startup when the disk is full and you're logging
19053 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
19054 style address, then we'd crash.
19055 - Fix an assert trigger when the running-routers string we get from
19056 a dirserver is broken.
19057 - Make worker threads start and run on win32. Now win32 servers
19059 - Bandaid (not actually fix, but now it doesn't crash) an assert
19060 where the dns worker dies mysteriously and the main Tor process
19061 doesn't remember anything about the address it was resolving.
19063 o Bugfixes on 0.0.9 (Win32):
19064 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
19065 name out of the warning/assert messages.
19066 - Fix a superficial "unhandled error on read" bug on win32.
19067 - The win32 installer no longer requires a click-through for our
19068 license, since our Free Software license grants rights but does not
19070 - Win32: When connecting to a dirserver fails, try another one
19071 immediately. (This was already working for non-win32 Tors.)
19072 - Stop trying to parse $HOME on win32 when hunting for default
19074 - Make tor-resolve.c work on win32 by calling network_init().
19076 o Bugfixes on 0.0.9 (other):
19077 - Make 0.0.9.x build on Solaris again.
19078 - Due to a fencepost error, we were blowing away the \n when reporting
19079 confvalue items in the controller. So asking for multiple config
19080 values at once couldn't work.
19081 - When listing circuits that are pending on an opening OR connection,
19082 if we're an OR we were listing circuits that *end* at us as
19083 being pending on every listener, dns/cpu worker, etc. Stop that.
19084 - Dirservers were failing to create 'running-routers' or 'directory'
19085 strings if we had more than some threshold of routers. Fix them so
19086 they can handle any number of routers.
19087 - Fix a superficial "Duplicate mark for close" bug.
19088 - Stop checking for clock skew for OR connections, even for servers.
19089 - Fix a fencepost error that was chopping off the last letter of any
19090 nickname that is the maximum allowed nickname length.
19091 - Update URLs in log messages so they point to the new website.
19092 - Fix a potential problem in mangling server private keys while
19093 writing to disk (not triggered yet, as far as we know).
19094 - Include the licenses for other free software we include in Tor,
19095 now that we're shipping binary distributions more regularly.
19098 Changes in version 0.0.9.1 - 2004-12-15
19099 o Bugfixes on 0.0.9:
19100 - Make hibernation actually work.
19101 - Make HashedControlPassword config option work.
19102 - When we're reporting event circuit status to a controller,
19103 don't use the stream status code.
19106 Changes in version 0.0.9 - 2004-12-12
19108 - Clean up manpage and torrc.sample file.
19109 - Clean up severities and text of log warnings.
19111 - Make servers trigger an assert when they enter hibernation.
19114 Changes in version 0.0.9rc7 - 2004-12-08
19115 o Bugfixes on 0.0.9rc:
19116 - Fix a stack-trashing crash when an exit node begins hibernating.
19117 - Avoid looking at unallocated memory while considering which
19118 ports we need to build circuits to cover.
19119 - Stop a sigpipe: when an 'end' cell races with eof from the app,
19120 we shouldn't hold-open-until-flush if the eof arrived first.
19121 - Fix a bug with init_cookie_authentication() in the controller.
19122 - When recommending new-format log lines, if the upper bound is
19123 LOG_ERR, leave it implicit.
19125 o Bugfixes on 0.0.8.1:
19126 - Fix a whole slew of memory leaks.
19127 - Fix isspace() and friends so they still make Solaris happy
19128 but also so they don't trigger asserts on win32.
19129 - Fix parse_iso_time on platforms without strptime (eg win32).
19130 - win32: tolerate extra "readable" events better.
19131 - win32: when being multithreaded, leave parent fdarray open.
19132 - Make unit tests work on win32.
19135 Changes in version 0.0.9rc6 - 2004-12-06
19136 o Bugfixes on 0.0.9pre:
19137 - Clean up some more integer underflow opportunities (not exploitable
19139 - While hibernating, hup should not regrow our listeners.
19140 - Send an end to the streams we close when we hibernate, rather
19141 than just chopping them off.
19142 - React to eof immediately on non-open edge connections.
19144 o Bugfixes on 0.0.8.1:
19145 - Calculate timeout for waiting for a connected cell from the time
19146 we sent the begin cell, not from the time the stream started. If
19147 it took a long time to establish the circuit, we would time out
19148 right after sending the begin cell.
19149 - Fix router_compare_addr_to_addr_policy: it was not treating a port
19150 of * as always matching, so we were picking reject *:* nodes as
19151 exit nodes too. Oops.
19154 - New circuit building strategy: keep a list of ports that we've
19155 used in the past 6 hours, and always try to have 2 circuits open
19156 or on the way that will handle each such port. Seed us with port
19157 80 so web users won't complain that Tor is "slow to start up".
19158 - Make kill -USR1 dump more useful stats about circuits.
19159 - When warning about retrying or giving up, print the address, so
19160 the user knows which one it's talking about.
19161 - If you haven't used a clean circuit in an hour, throw it away,
19162 just to be on the safe side. (This means after 6 hours a totally
19163 unused Tor client will have no circuits open.)
19166 Changes in version 0.0.9rc5 - 2004-12-01
19167 o Bugfixes on 0.0.8.1:
19168 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
19169 - Let resolve conns retry/expire also, rather than sticking around
19171 - If we are using select, make sure we stay within FD_SETSIZE.
19173 o Bugfixes on 0.0.9pre:
19174 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
19175 but doesn't seem to be currently; thanks to Ilja van Sprundel for
19177 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
19178 instead. Impose minima and maxima for all *Period options; impose
19179 even tighter maxima for fetching if we are a caching dirserver.
19180 Clip rather than rejecting.
19181 - Fetch cached running-routers from servers that serve it (that is,
19182 authdirservers and servers running 0.0.9rc5-cvs or later.)
19185 - Accept *:706 (silc) in default exit policy.
19186 - Implement new versioning format for post 0.1.
19187 - Support "foo.nickname.exit" addresses, to let Alice request the
19188 address "foo" as viewed by exit node "nickname". Based on a patch
19190 - Make tor --version --version dump the cvs Id of every file.
19193 Changes in version 0.0.9rc4 - 2004-11-28
19194 o Bugfixes on 0.0.8.1:
19195 - Make windows sockets actually non-blocking (oops), and handle
19196 win32 socket errors better.
19198 o Bugfixes on 0.0.9rc1:
19199 - Actually catch the -USR2 signal.
19202 Changes in version 0.0.9rc3 - 2004-11-25
19203 o Bugfixes on 0.0.8.1:
19204 - Flush the log file descriptor after we print "Tor opening log file",
19205 so we don't see those messages days later.
19207 o Bugfixes on 0.0.9rc1:
19208 - Make tor-resolve work again.
19209 - Avoid infinite loop in tor-resolve if tor hangs up on it.
19210 - Fix an assert trigger for clients/servers handling resolves.
19213 Changes in version 0.0.9rc2 - 2004-11-24
19214 o Bugfixes on 0.0.9rc1:
19215 - I broke socks5 support while fixing the eof bug.
19216 - Allow unitless bandwidths and intervals; they default to bytes
19218 - New servers don't start out hibernating; they are active until
19219 they run out of bytes, so they have a better estimate of how
19220 long it takes, and so their operators can know they're working.
19223 Changes in version 0.0.9rc1 - 2004-11-23
19224 o Bugfixes on 0.0.8.1:
19225 - Finally fix a bug that's been plaguing us for a year:
19226 With high load, circuit package window was reaching 0. Whenever
19227 we got a circuit-level sendme, we were reading a lot on each
19228 socket, but only writing out a bit. So we would eventually reach
19229 eof. This would be noticed and acted on even when there were still
19230 bytes sitting in the inbuf.
19231 - When poll() is interrupted, we shouldn't believe the revents values.
19233 o Bugfixes on 0.0.9pre6:
19234 - Fix hibernate bug that caused pre6 to be broken.
19235 - Don't keep rephist info for routers that haven't had activity for
19236 24 hours. (This matters now that clients have keys, since we track
19238 - Never call close_temp_logs while validating log options.
19239 - Fix backslash-escaping on tor.sh.in and torctl.in.
19242 - Implement weekly/monthly/daily accounting: now you specify your
19243 hibernation properties by
19244 AccountingMax N bytes|KB|MB|GB|TB
19245 AccountingStart day|week|month [day] HH:MM
19246 Defaults to "month 1 0:00".
19247 - Let bandwidth and interval config options be specified as 5 bytes,
19248 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
19249 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
19250 get back to normal.)
19251 - If your requested entry or exit node has advertised bandwidth 0,
19253 - Be more greedy about filling up relay cells -- we try reading again
19254 once we've processed the stuff we read, in case enough has arrived
19255 to fill the last cell completely.
19256 - Apply NT service patch from Osamu Fujino. Still needs more work.
19259 Changes in version 0.0.9pre6 - 2004-11-15
19260 o Bugfixes on 0.0.8.1:
19261 - Fix assert failure on malformed socks4a requests.
19262 - Use identity comparison, not nickname comparison, to choose which
19263 half of circuit-ID-space each side gets to use. This is needed
19264 because sometimes we think of a router as a nickname, and sometimes
19265 as a hex ID, and we can't predict what the other side will do.
19266 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
19267 write() call will fail and we handle it there.
19268 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
19269 and smartlist_len, which are two major profiling offenders.
19271 o Bugfixes on 0.0.9pre5:
19272 - Fix a bug in read_all that was corrupting config files on windows.
19273 - When we're raising the max number of open file descriptors to
19274 'unlimited', don't log that we just raised it to '-1'.
19275 - Include event code with events, as required by control-spec.txt.
19276 - Don't give a fingerprint when clients do --list-fingerprint:
19277 it's misleading, because it will never be the same again.
19278 - Stop using strlcpy in tor_strndup, since it was slowing us
19280 - Remove warn on startup about missing cached-directory file.
19281 - Make kill -USR1 work again.
19282 - Hibernate if we start tor during the "wait for wakeup-time" phase
19283 of an accounting interval. Log our hibernation plans better.
19284 - Authoritative dirservers now also cache their directory, so they
19285 have it on start-up.
19288 - Fetch running-routers; cache running-routers; compress
19289 running-routers; serve compressed running-routers.z
19290 - Add NSI installer script contributed by J Doe.
19291 - Commit VC6 and VC7 workspace/project files.
19292 - Commit a tor.spec for making RPM files, with help from jbash.
19293 - Add contrib/torctl.in contributed by Glenn Fink.
19294 - Implement the control-spec's SAVECONF command, to write your
19295 configuration to torrc.
19296 - Get cookie authentication for the controller closer to working.
19297 - Include control-spec.txt in the tarball.
19298 - When set_conf changes our server descriptor, upload a new copy.
19299 But don't upload it too often if there are frequent changes.
19300 - Document authentication config in man page, and document signals
19302 - Clean up confusing parts of man page and torrc.sample.
19303 - Make expand_filename handle ~ and ~username.
19304 - Use autoconf to enable largefile support where necessary. Use
19305 ftello where available, since ftell can fail at 2GB.
19306 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
19307 log more informatively.
19308 - Give a slightly more useful output for "tor -h".
19309 - Refuse application socks connections to port 0.
19310 - Check clock skew for verified servers, but allow unverified
19311 servers and clients to have any clock skew.
19312 - Break DirFetchPostPeriod into:
19313 - DirFetchPeriod for fetching full directory,
19314 - StatusFetchPeriod for fetching running-routers,
19315 - DirPostPeriod for posting server descriptor,
19316 - RendPostPeriod for posting hidden service descriptors.
19317 - Make sure the hidden service descriptors are at a random offset
19318 from each other, to hinder linkability.
19321 Changes in version 0.0.9pre5 - 2004-11-09
19322 o Bugfixes on 0.0.9pre4:
19323 - Fix a seg fault in unit tests (doesn't affect main program).
19324 - Fix an assert bug where a hidden service provider would fail if
19325 the first hop of his rendezvous circuit was down.
19326 - Hidden service operators now correctly handle version 1 style
19327 INTRODUCE1 cells (nobody generates them still, so not a critical
19329 - If do_hup fails, actually notice.
19330 - Handle more errnos from accept() without closing the listener.
19331 Some OpenBSD machines were closing their listeners because
19332 they ran out of file descriptors.
19333 - Send resolve cells to exit routers that are running a new
19334 enough version of the resolve code to work right.
19335 - Better handling of winsock includes on non-MSV win32 compilers.
19336 - Some people had wrapped their tor client/server in a script
19337 that would restart it whenever it died. This did not play well
19338 with our "shut down if your version is obsolete" code. Now people
19339 don't fetch a new directory if their local cached version is
19341 - Make our autogen.sh work on ksh as well as bash.
19344 - Hibernation: New config option "AccountingMaxKB" lets you
19345 set how many KBytes per month you want to allow your server to
19346 consume. Rather than spreading those bytes out evenly over the
19347 month, we instead hibernate for some of the month and pop up
19348 at a deterministic time, work until the bytes are consumed, then
19349 hibernate again. Config option "MonthlyAccountingStart" lets you
19350 specify which day of the month your billing cycle starts on.
19351 - Control interface: a separate program can now talk to your
19352 client/server over a socket, and get/set config options, receive
19353 notifications of circuits and streams starting/finishing/dying,
19354 bandwidth used, etc. The next step is to get some GUIs working.
19355 Let us know if you want to help out. See doc/control-spec.txt .
19356 - Ship a contrib/tor-control.py as an example script to interact
19357 with the control port.
19358 - "tor --hash-password zzyxz" will output a salted password for
19359 use in authenticating to the control interface.
19360 - New log format in config:
19361 "Log minsev[-maxsev] stdout|stderr|syslog" or
19362 "Log minsev[-maxsev] file /var/foo"
19365 - DirPolicy config option, to let people reject incoming addresses
19366 from their dirserver.
19367 - "tor --list-fingerprint" will list your identity key fingerprint
19369 - Add "pass" target for RedirectExit, to make it easier to break
19370 out of a sequence of RedirectExit rules.
19371 - Clients now generate a TLS cert too, in preparation for having
19372 them act more like real nodes.
19373 - Ship src/win32/ in the tarball, so people can use it to build.
19374 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19376 - New "router-status" line in directory, to better bind each verified
19377 nickname to its identity key.
19378 - Deprecate unofficial config option abbreviations, and abbreviations
19379 not on the command line.
19380 - Add a pure-C tor-resolve implementation.
19381 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19382 1024) file descriptors.
19384 o Code security improvements, inspired by Ilja:
19385 - Replace sprintf with snprintf. (I think they were all safe, but
19387 - Replace strcpy/strncpy with strlcpy in more places.
19388 - Avoid strcat; use snprintf or strlcat instead.
19389 - snprintf wrapper with consistent (though not C99) overflow behavior.
19392 Changes in version 0.0.9pre4 - 2004-10-17
19393 o Bugfixes on 0.0.9pre3:
19394 - If the server doesn't specify an exit policy, use the real default
19395 exit policy, not reject *:*.
19396 - Ignore fascistfirewall when uploading/downloading hidden service
19397 descriptors, since we go through Tor for those; and when using
19398 an HttpProxy, since we assume it can reach them all.
19399 - When looking for an authoritative dirserver, use only the ones
19400 configured at boot. Don't bother looking in the directory.
19401 - The rest of the fix for get_default_conf_file() on older win32.
19402 - Make 'Routerfile' config option obsolete.
19405 - New 'MyFamily nick1,...' config option for a server to
19406 specify other servers that shouldn't be used in the same circuit
19407 with it. Only believed if nick1 also specifies us.
19408 - New 'NodeFamily nick1,nick2,...' config option for a client to
19409 specify nodes that it doesn't want to use in the same circuit.
19410 - New 'Redirectexit pattern address:port' config option for a
19411 server to redirect exit connections, e.g. to a local squid.
19414 Changes in version 0.0.9pre3 - 2004-10-13
19415 o Bugfixes on 0.0.8.1:
19416 - Better torrc example lines for dirbindaddress and orbindaddress.
19417 - Improved bounds checking on parsed ints (e.g. config options and
19418 the ones we find in directories.)
19419 - Better handling of size_t vs int, so we're more robust on 64
19421 - Fix the rest of the bug where a newly started OR would appear
19422 as unverified even after we've added his fingerprint and hupped
19424 - Fix a bug from 0.0.7: when read() failed on a stream, we would
19425 close it without sending back an end. So 'connection refused'
19426 would simply be ignored and the user would get no response.
19428 o Bugfixes on 0.0.9pre2:
19429 - Serving the cached-on-disk directory to people is bad. We now
19430 provide no directory until we've fetched a fresh one.
19431 - Workaround for bug on windows where cached-directories get crlf
19433 - Make get_default_conf_file() work on older windows too.
19434 - If we write a *:* exit policy line in the descriptor, don't write
19435 any more exit policy lines.
19438 - Use only 0.0.9pre1 and later servers for resolve cells.
19439 - Make the dirservers file obsolete.
19440 - Include a dir-signing-key token in directories to tell the
19441 parsing entity which key is being used to sign.
19442 - Remove the built-in bulky default dirservers string.
19443 - New config option "Dirserver %s:%d [fingerprint]", which can be
19444 repeated as many times as needed. If no dirservers specified,
19445 default to moria1,moria2,tor26.
19446 - Make moria2 advertise a dirport of 80, so people behind firewalls
19447 will be able to get a directory.
19448 - Http proxy support
19449 - Dirservers translate requests for http://%s:%d/x to /x
19450 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
19451 be routed through this host.
19452 - Clients ask for /tor/x rather than /x for new enough dirservers.
19453 This way we can one day coexist peacefully with apache.
19454 - Clients specify a "Host: %s%d" http header, to be compatible
19455 with more proxies, and so running squid on an exit node can work.
19458 Changes in version 0.0.8.1 - 2004-10-13
19460 - Fix a seg fault that can be triggered remotely for Tor
19461 clients/servers with an open dirport.
19462 - Fix a rare assert trigger, where routerinfos for entries in
19463 our cpath would expire while we're building the path.
19464 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19465 - Fix a rare seg fault for people running hidden services on
19466 intermittent connections.
19467 - Fix a bug in parsing opt keywords with objects.
19468 - Fix a stale pointer assert bug when a stream detaches and
19470 - Fix a string format vulnerability (probably not exploitable)
19471 in reporting stats locally.
19472 - Fix an assert trigger: sometimes launching circuits can fail
19473 immediately, e.g. because too many circuits have failed recently.
19474 - Fix a compile warning on 64 bit platforms.
19477 Changes in version 0.0.9pre2 - 2004-10-03
19479 - Make fetching a cached directory work for 64-bit platforms too.
19480 - Make zlib.h a required header, not an optional header.
19483 Changes in version 0.0.9pre1 - 2004-10-01
19485 - Stop using separate defaults for no-config-file and
19486 empty-config-file. Now you have to explicitly turn off SocksPort,
19487 if you don't want it open.
19488 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19489 - Improve man page to mention more of the 0.0.8 features.
19490 - Fix a rare seg fault for people running hidden services on
19491 intermittent connections.
19492 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
19494 - Fix more dns related bugs: send back resolve_failed and end cells
19495 more reliably when the resolve fails, rather than closing the
19496 circuit and then trying to send the cell. Also attach dummy resolve
19497 connections to a circuit *before* calling dns_resolve(), to fix
19498 a bug where cached answers would never be sent in RESOLVED cells.
19499 - When we run out of disk space, or other log writing error, don't
19500 crash. Just stop logging to that log and continue.
19501 - We were starting to daemonize before we opened our logs, so if
19502 there were any problems opening logs, we would complain to stderr,
19503 which wouldn't work, and then mysteriously exit.
19504 - Fix a rare bug where sometimes a verified OR would connect to us
19505 before he'd uploaded his descriptor, which would cause us to
19506 assign conn->nickname as though he's unverified. Now we look through
19507 the fingerprint list to see if he's there.
19508 - Fix a rare assert trigger, where routerinfos for entries in
19509 our cpath would expire while we're building the path.
19512 - Clients can ask dirservers for /dir.z to get a compressed version
19513 of the directory. Only works for servers running 0.0.9, of course.
19514 - Make clients cache directories and use them to seed their router
19515 lists at startup. This means clients have a datadir again.
19516 - Configuration infrastructure support for warning on obsolete
19518 - Respond to content-encoding headers by trying to uncompress as
19520 - Reply with a deflated directory when a client asks for "dir.z".
19521 We could use allow-encodings instead, but allow-encodings isn't
19522 specified in HTTP 1.0.
19523 - Raise the max dns workers from 50 to 100.
19524 - Discourage people from setting their dirfetchpostperiod more often
19525 than once per minute.
19526 - Protect dirservers from overzealous descriptor uploading -- wait
19527 10 seconds after directory gets dirty, before regenerating.
19530 Changes in version 0.0.8 - 2004-08-25
19531 o Port it to SunOS 5.9 / Athena
19534 Changes in version 0.0.8rc2 - 2004-08-20
19535 o Make it compile on cygwin again.
19536 o When picking unverified routers, skip those with low uptime and/or
19537 low bandwidth, depending on what properties you care about.
19540 Changes in version 0.0.8rc1 - 2004-08-18
19541 o Changes from 0.0.7.3:
19543 - Fix assert triggers: if the other side returns an address 0.0.0.0,
19544 don't put it into the client dns cache.
19545 - If a begin failed due to exit policy, but we believe the IP address
19546 should have been allowed, switch that router to exitpolicy reject *:*
19547 until we get our next directory.
19549 - Clients choose nodes proportional to advertised bandwidth.
19550 - Avoid using nodes with low uptime as introduction points.
19551 - Handle servers with dynamic IP addresses: don't replace
19552 options->Address with the resolved one at startup, and
19553 detect our address right before we make a routerinfo each time.
19554 - 'FascistFirewall' option to pick dirservers and ORs on specific
19555 ports; plus 'FirewallPorts' config option to tell FascistFirewall
19556 which ports are open. (Defaults to 80,443)
19557 - Be more aggressive about trying to make circuits when the network
19558 has changed (e.g. when you unsuspend your laptop).
19559 - Check for time skew on http headers; report date in response to
19561 - If the entrynode config line has only one node, don't pick it as
19563 - Add strict{entry|exit}nodes config options. If set to 1, then
19564 we refuse to build circuits that don't include the specified entry
19566 - OutboundBindAddress config option, to bind to a specific
19567 IP address for outgoing connect()s.
19568 - End truncated log entries (e.g. directories) with "[truncated]".
19570 o Patches to 0.0.8preX:
19572 - Patches to compile and run on win32 again (maybe)?
19573 - Fix crash when looking for ~/.torrc with no $HOME set.
19574 - Fix a race bug in the unit tests.
19575 - Handle verified/unverified name collisions better when new
19576 routerinfo's arrive in a directory.
19577 - Sometimes routers were getting entered into the stats before
19578 we'd assigned their identity_digest. Oops.
19579 - Only pick and establish intro points after we've gotten a
19582 - AllowUnverifiedNodes config option to let circuits choose no-name
19583 routers in entry,middle,exit,introduction,rendezvous positions.
19584 Allow middle and rendezvous positions by default.
19585 - Add a man page for tor-resolve.
19588 Changes in version 0.0.7.3 - 2004-08-12
19589 o Stop dnsworkers from triggering an assert failure when you
19590 ask them to resolve the host "".
19593 Changes in version 0.0.8pre3 - 2004-08-09
19594 o Changes from 0.0.7.2:
19595 - Allow multiple ORs with same nickname in routerlist -- now when
19596 people give us one identity key for a nickname, then later
19597 another, we don't constantly complain until the first expires.
19598 - Remember used bandwidth (both in and out), and publish 15-minute
19599 snapshots for the past day into our descriptor.
19600 - You can now fetch $DIRURL/running-routers to get just the
19601 running-routers line, not the whole descriptor list. (But
19602 clients don't use this yet.)
19603 - When people mistakenly use Tor as an http proxy, point them
19604 at the tor-doc.html rather than the INSTALL.
19605 - Remove our mostly unused -- and broken -- hex_encode()
19606 function. Use base16_encode() instead. (Thanks to Timo Lindfors
19607 for pointing out this bug.)
19608 - Rotate onion keys every 12 hours, not every 2 hours, so we have
19609 fewer problems with people using the wrong key.
19610 - Change the default exit policy to reject the default edonkey,
19611 kazaa, gnutella ports.
19612 - Add replace_file() to util.[ch] to handle win32's rename().
19614 o Changes from 0.0.8preX:
19615 - Fix two bugs in saving onion keys to disk when rotating, so
19616 hopefully we'll get fewer people using old onion keys.
19617 - Fix an assert error that was making SocksPolicy not work.
19618 - Be willing to expire routers that have an open dirport -- it's
19619 just the authoritative dirservers we want to not forget.
19620 - Reject tor-resolve requests for .onion addresses early, so we
19621 don't build a whole rendezvous circuit and then fail.
19622 - When you're warning a server that he's unverified, don't cry
19623 wolf unpredictably.
19624 - Fix a race condition: don't try to extend onto a connection
19625 that's still handshaking.
19626 - For servers in clique mode, require the conn to be open before
19627 you'll choose it for your path.
19628 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
19629 end relay cell, etc.
19630 - Measure bandwidth capacity over the last 24 hours, not just 12
19631 - Bugfix: authoritative dirservers were making and signing a new
19632 directory for each client, rather than reusing the cached one.
19635 Changes in version 0.0.8pre2 - 2004-08-04
19636 o Changes from 0.0.7.2:
19638 - Check directory signature _before_ you decide whether you're
19639 you're running an obsolete version and should exit.
19640 - Check directory signature _before_ you parse the running-routers
19641 list to decide who's running or verified.
19642 - Bugfixes and features:
19643 - Check return value of fclose while writing to disk, so we don't
19644 end up with broken files when servers run out of disk space.
19645 - Log a warning if the user uses an unsafe socks variant, so people
19646 are more likely to learn about privoxy or socat.
19647 - Dirservers now include RFC1123-style dates in the HTTP headers,
19648 which one day we will use to better detect clock skew.
19650 o Changes from 0.0.8pre1:
19651 - Make it compile without warnings again on win32.
19652 - Log a warning if you're running an unverified server, to let you
19653 know you might want to get it verified.
19654 - Only pick a default nickname if you plan to be a server.
19657 Changes in version 0.0.8pre1 - 2004-07-23
19659 - Made our unit tests compile again on OpenBSD 3.5, and tor
19660 itself compile again on OpenBSD on a sparc64.
19661 - We were neglecting milliseconds when logging on win32, so
19662 everything appeared to happen at the beginning of each second.
19664 o Protocol changes:
19665 - 'Extend' relay cell payloads now include the digest of the
19666 intended next hop's identity key. Now we can verify that we're
19667 extending to the right router, and also extend to routers we
19668 hadn't heard of before.
19671 - Tor nodes can now act as relays (with an advertised ORPort)
19672 without being manually verified by the dirserver operators.
19673 - Uploaded descriptors of unverified routers are now accepted
19674 by the dirservers, and included in the directory.
19675 - Verified routers are listed by nickname in the running-routers
19676 list; unverified routers are listed as "$<fingerprint>".
19677 - We now use hash-of-identity-key in most places rather than
19678 nickname or addr:port, for improved security/flexibility.
19679 - To avoid Sybil attacks, paths still use only verified servers.
19680 But now we have a chance to play around with hybrid approaches.
19681 - Nodes track bandwidth usage to estimate capacity (not used yet).
19682 - ClientOnly option for nodes that never want to become servers.
19683 - Directory caching.
19684 - "AuthoritativeDir 1" option for the official dirservers.
19685 - Now other nodes (clients and servers) will cache the latest
19686 directory they've pulled down.
19687 - They can enable their DirPort to serve it to others.
19688 - Clients will pull down a directory from any node with an open
19689 DirPort, and check the signature/timestamp correctly.
19690 - Authoritative dirservers now fetch directories from other
19691 authdirservers, to stay better synced.
19692 - Running-routers list tells who's down also, along with noting
19693 if they're verified (listed by nickname) or unverified (listed
19695 - Allow dirservers to serve running-router list separately.
19696 This isn't used yet.
19697 - ORs connect-on-demand to other ORs
19698 - If you get an extend cell to an OR you're not connected to,
19699 connect, handshake, and forward the create cell.
19700 - The authoritative dirservers stay connected to everybody,
19701 and everybody stays connected to 0.0.7 servers, but otherwise
19702 clients/servers expire unused connections after 5 minutes.
19703 - When servers get a sigint, they delay 30 seconds (refusing new
19704 connections) then exit. A second sigint causes immediate exit.
19705 - File and name management:
19706 - Look for .torrc if no CONFDIR "torrc" is found.
19707 - If no datadir is defined, then choose, make, and secure ~/.tor
19709 - If torrc not found, exitpolicy reject *:*.
19710 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19711 - If no nickname is defined, derive default from hostname.
19712 - Rename secret key files, e.g. identity.key -> secret_id_key,
19713 to discourage people from mailing their identity key to tor-ops.
19714 - Refuse to build a circuit before the directory has arrived --
19715 it won't work anyway, since you won't know the right onion keys
19717 - Try other dirservers immediately if the one you try is down. This
19718 should tolerate down dirservers better now.
19719 - Parse tor version numbers so we can do an is-newer-than check
19720 rather than an is-in-the-list check.
19721 - New socks command 'resolve', to let us shim gethostbyname()
19723 - A 'tor_resolve' script to access the socks resolve functionality.
19724 - A new socks-extensions.txt doc file to describe our
19725 interpretation and extensions to the socks protocols.
19726 - Add a ContactInfo option, which gets published in descriptor.
19727 - Publish OR uptime in descriptor (and thus in directory) too.
19728 - Write tor version at the top of each log file
19729 - New docs in the tarball:
19731 - Document that you should proxy your SSL traffic too.
19734 Changes in version 0.0.7.2 - 2004-07-07
19735 o A better fix for the 0.0.0.0 problem, that will hopefully
19736 eliminate the remaining related assertion failures.
19739 Changes in version 0.0.7.1 - 2004-07-04
19740 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19741 since internally we use 0.0.0.0 to signify "not yet resolved".
19744 Changes in version 0.0.7 - 2004-06-07
19745 o Updated the man page to reflect the new features.
19748 Changes in version 0.0.7rc2 - 2004-06-06
19749 o Changes from 0.0.7rc1:
19750 - Make it build on Win32 again.
19751 o Changes from 0.0.6.2:
19752 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19756 Changes in version 0.0.7rc1 - 2004-06-02
19758 - On sighup, we were adding another log without removing the first
19759 one. So log messages would get duplicated n times for n sighups.
19760 - Several cases of using a connection after we'd freed it. The
19761 problem was that connections that are pending resolve are in both
19762 the pending_resolve tree, and also the circuit's resolving_streams
19763 list. When you want to remove one, you must remove it from both.
19764 - Fix a double-mark-for-close where an end cell arrived for a
19765 resolving stream, and then the resolve failed.
19766 - Check directory signatures based on name of signer, not on whom
19767 we got the directory from. This will let us cache directories more
19770 - Crank up some of our constants to handle more users.
19773 Changes in version 0.0.7pre1 - 2004-06-02
19774 o Fixes for crashes and other obnoxious bugs:
19775 - Fix an epipe bug: sometimes when directory connections failed
19776 to connect, we would give them a chance to flush before closing
19778 - When we detached from a circuit because of resolvefailed, we
19779 would immediately try the same circuit twice more, and then
19780 give up on the resolve thinking we'd tried three different
19782 - Limit the number of intro circuits we'll attempt to build for a
19783 hidden service per 15-minute period.
19784 - Check recommended-software string *early*, before actually parsing
19785 the directory. Thus we can detect an obsolete version and exit,
19786 even if the new directory format doesn't parse.
19787 o Fixes for security bugs:
19788 - Remember which nodes are dirservers when you startup, and if a
19789 random OR enables his dirport, don't automatically assume he's
19790 a trusted dirserver.
19792 - Directory connections were asking the wrong poll socket to
19793 start writing, and not asking themselves to start writing.
19794 - When we detached from a circuit because we sent a begin but
19795 didn't get a connected, we would use it again the first time;
19796 but after that we would correctly switch to a different one.
19797 - Stop warning when the first onion decrypt attempt fails; they
19798 will sometimes legitimately fail now that we rotate keys.
19799 - Override unaligned-access-ok check when $host_cpu is ia64 or
19800 arm. Apparently they allow it but the kernel whines.
19801 - Dirservers try to reconnect periodically too, in case connections
19803 - Fix some memory leaks in directory servers.
19804 - Allow backslash in Win32 filenames.
19805 - Made Tor build complain-free on FreeBSD, hopefully without
19806 breaking other BSD builds. We'll see.
19808 - Doxygen markup on all functions and global variables.
19809 - Make directory functions update routerlist, not replace it. So
19810 now directory disagreements are not so critical a problem.
19811 - Remove the upper limit on number of descriptors in a dirserver's
19812 directory (not that we were anywhere close).
19813 - Allow multiple logfiles at different severity ranges.
19814 - Allow *BindAddress to specify ":port" rather than setting *Port
19815 separately. Allow multiple instances of each BindAddress config
19816 option, so you can bind to multiple interfaces if you want.
19817 - Allow multiple exit policy lines, which are processed in order.
19818 Now we don't need that huge line with all the commas in it.
19819 - Enable accept/reject policies on SOCKS connections, so you can bind
19820 to 0.0.0.0 but still control who can use your OP.
19823 Changes in version 0.0.6.2 - 2004-05-16
19824 o Our integrity-checking digest was checking only the most recent cell,
19825 not the previous cells like we'd thought.
19826 Thanks to Stefan Mark for finding the flaw!
19829 Changes in version 0.0.6.1 - 2004-05-06
19830 o Fix two bugs in our AES counter-mode implementation (this affected
19831 onion-level stream encryption, but not TLS-level). It turns
19832 out we were doing something much more akin to a 16-character
19833 polyalphabetic cipher. Oops.
19834 Thanks to Stefan Mark for finding the flaw!
19835 o Retire moria3 as a directory server, and add tor26 as a directory
19839 Changes in version 0.0.6 - 2004-05-02
19840 [version bump only]
19843 Changes in version 0.0.6rc4 - 2004-05-01
19844 o Update the built-in dirservers list to use the new directory format
19845 o Fix a rare seg fault: if a node offering a hidden service attempts
19846 to build a circuit to Alice's rendezvous point and fails before it
19847 reaches the last hop, it retries with a different circuit, but
19849 o Handle windows socket errors correctly.
19852 Changes in version 0.0.6rc3 - 2004-04-28
19853 o Don't expire non-general excess circuits (if we had enough
19854 circuits open, we were expiring rendezvous circuits -- even
19855 when they had a stream attached. oops.)
19856 o Fetch randomness from /dev/urandom better (not via fopen/fread)
19857 o Better debugging for tls errors
19858 o Some versions of openssl have an SSL_pending function that erroneously
19859 returns bytes when there is a non-application record pending.
19860 o Set Content-Type on the directory and hidserv descriptor.
19861 o Remove IVs from cipher code, since AES-ctr has none.
19862 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19863 o We were using an array of length zero in a few places.
19864 o win32's gethostbyname can't resolve an IP to an IP.
19865 o win32's close can't close a socket.
19868 Changes in version 0.0.6rc2 - 2004-04-26
19869 o Fix a bug where we were closing tls connections intermittently.
19870 It turns out openssl keeps its errors around -- so if an error
19871 happens, and you don't ask about it, and then another openssl
19872 operation happens and succeeds, and you ask if there was an error,
19873 it tells you about the first error. Fun fun.
19874 o Fix a bug that's been lurking since 27 may 03 (!)
19875 When passing back a destroy cell, we would use the wrong circ id.
19876 'Mostly harmless', but still worth fixing.
19877 o Since we don't support truncateds much, don't bother sending them;
19878 just close the circ.
19879 o check for <machine/limits.h> so we build on NetBSD again (I hope).
19880 o don't crash if a conn that sent a begin has suddenly lost its circuit
19881 (this was quite rare).
19884 Changes in version 0.0.6rc1 - 2004-04-25
19885 o We now rotate link (tls context) keys and onion keys.
19886 o CREATE cells now include oaep padding, so you can tell
19887 if you decrypted them correctly.
19888 o Add bandwidthburst to server descriptor.
19889 o Directories now say which dirserver signed them.
19890 o Use a tor_assert macro that logs failed assertions too.
19893 Changes in version 0.0.6pre5 - 2004-04-18
19894 o changes from 0.0.6pre4:
19895 - make tor build on broken freebsd 5.2 installs
19896 - fix a failed assert when you try an intro point, get a nack, and try
19897 a second one and it works.
19898 - when alice uses a port that the hidden service doesn't accept,
19899 it now sends back an end cell (denied by exit policy). otherwise
19900 alice would just have to wait to time out.
19901 - fix another rare bug: when we had tried all the intro
19902 points for a hidden service, we fetched the descriptor
19903 again, but we left our introcirc thinking it had already
19904 sent an intro, so it kept waiting for a response...
19905 - bugfix: when you sleep your hidden-service laptop, as soon
19906 as it wakes up it tries to upload a service descriptor, but
19907 socketpair fails for some reason (localhost not up yet?).
19908 now we simply give up on that upload, and we'll try again later.
19909 i'd still like to find the bug though.
19910 - if an intro circ waiting for an ack dies before getting one, then
19912 - we were reusing stale service descriptors and refetching usable
19916 Changes in version 0.0.6pre4 - 2004-04-14
19917 o changes from 0.0.6pre3:
19918 - when bob fails to connect to the rendezvous point, and his
19919 circ didn't fail because of the rendezvous point itself, then
19920 he retries a couple of times
19921 - we expire introduction and rendezvous circs more thoroughly
19922 (sometimes they were hanging around forever)
19923 - we expire unattached rendezvous streams that have been around
19924 too long (they were sticking around forever).
19925 - fix a measly fencepost error that was crashing everybody with
19929 Changes in version 0.0.6pre3 - 2004-04-14
19930 o changes from 0.0.6pre2:
19931 - make hup work again
19932 - fix some memory leaks for dirservers
19933 - allow more skew in rendezvous descriptor timestamps, to help
19934 handle people like blanu who don't know what time it is
19935 - normal circs are 3 hops, but some rend/intro circs are 4, if
19936 the initiator doesn't get to choose the last hop
19937 - send acks for introductions, so alice can know whether to try
19939 - bob publishes intro points more correctly
19940 o changes from 0.0.5:
19941 - fix an assert trigger that's been plaguing us since the days
19942 of 0.0.2prexx (thanks weasel!)
19943 - retry stream correctly when we fail to connect because of
19944 exit-policy-reject (should try another) or can't-resolve-address
19945 (also should try another, because dns on random internet servers
19947 - when we hup a dirserver and we've *removed* a server from the
19948 approved-routers list, now we remove that server from the
19949 in-memory directories too
19952 Changes in version 0.0.6pre2 - 2004-04-08
19953 o We fixed our base32 implementation. Now it works on all architectures.
19956 Changes in version 0.0.6pre1 - 2004-04-08
19958 - Hidden services and rendezvous points are implemented. Go to
19959 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19960 hidden services. (This only works via a socks4a proxy such as
19961 Privoxy, and currently it's quite slow.)
19964 Changes in version 0.0.5 - 2004-03-30
19965 [version bump only]
19968 Changes in version 0.0.5rc3 - 2004-03-29
19969 o Install torrc as torrc.sample -- we no longer clobber your
19971 o Re-enable recommendedversion checking (we broke it in rc2, oops)
19972 o Add in a 'notice' log level for things the operator should hear
19973 but that aren't warnings
19976 Changes in version 0.0.5rc2 - 2004-03-29
19977 o Hold socks connection open until reply is flushed (if possible)
19978 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19979 the dns farm to do it.
19980 o Fix c99 aliasing warnings in rephist.c
19981 o Don't include server descriptors that are older than 24 hours in the
19983 o Give socks 'reject' replies their whole 15s to attempt to flush,
19984 rather than seeing the 60s timeout and assuming the flush had failed.
19985 o Clean automake droppings from the cvs repository
19988 Changes in version 0.0.5rc1 - 2004-03-28
19989 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19990 o Only build circuits after we've fetched the directory: clients were
19991 using only the directory servers before they'd fetched a directory.
19992 This also means longer startup time; so it goes.
19993 o Fix an assert trigger where an OP would fail to handshake, and we'd
19994 expect it to have a nickname.
19995 o Work around a tsocks bug: do a socks reject when AP connection dies
19996 early, else tsocks goes into an infinite loop.
19999 Changes in version 0.0.4 - 2004-03-26
20000 o When connecting to a dirserver or OR and the network is down,
20004 Changes in version 0.0.3 - 2004-03-26
20005 o Warn and fail if server chose a nickname with illegal characters
20006 o Port to Solaris and Sparc:
20007 - include missing header fcntl.h
20008 - have autoconf find -lsocket -lnsl automatically
20009 - deal with hardware word alignment
20010 - make uname() work (solaris has a different return convention)
20011 - switch from using signal() to sigaction()
20012 o Preliminary work on reputation system:
20013 - Keep statistics on success/fail of connect attempts; they're published
20014 by kill -USR1 currently.
20015 - Add a RunTesting option to try to learn link state by creating test
20016 circuits, even when SocksPort is off.
20017 - Remove unused open circuits when there are too many.
20020 Changes in version 0.0.2 - 2004-03-19
20021 - Include strlcpy and strlcat for safer string ops
20022 - define INADDR_NONE so we compile (but still not run) on solaris
20025 Changes in version 0.0.2pre27 - 2004-03-14
20027 - Allow internal tor networks (we were rejecting internal IPs,
20028 now we allow them if they're set explicitly).
20029 - And fix a few endian issues.
20032 Changes in version 0.0.2pre26 - 2004-03-14
20034 - If a stream times out after 15s without a connected cell, don't
20035 try that circuit again: try a new one.
20036 - Retry streams at most 4 times. Then give up.
20037 - When a dirserver gets a descriptor from an unknown router, it
20038 logs its fingerprint (so the dirserver operator can choose to
20039 accept it even without mail from the server operator).
20040 - Inform unapproved servers when we reject their descriptors.
20041 - Make tor build on Windows again. It works as a client, who knows
20043 - Clearer instructions in the torrc for how to set up a server.
20044 - Be more efficient about reading fd's when our global token bucket
20045 (used for rate limiting) becomes empty.
20047 - Stop asserting that computers always go forward in time. It's
20049 - When we sent a cell (e.g. destroy) and then marked an OR connection
20050 expired, we might close it before finishing a flush if the other
20051 side isn't reading right then.
20052 - Don't allow dirservers to start if they haven't defined
20053 RecommendedVersions
20054 - We were caching transient dns failures. Oops.
20055 - Prevent servers from publishing an internal IP as their address.
20056 - Address a strcat vulnerability in circuit.c
20059 Changes in version 0.0.2pre25 - 2004-03-04
20061 - Put the OR's IP in its router descriptor, not its fqdn. That way
20062 we'll stop being stalled by gethostbyname for nodes with flaky dns,
20065 - If the user typed in an address that didn't resolve, the server
20069 Changes in version 0.0.2pre24 - 2004-03-03
20071 - Fix an assertion failure in dns.c, where we were trying to dequeue
20072 a pending dns resolve even if it wasn't pending
20073 - Fix a spurious socks5 warning about still trying to write after the
20074 connection is finished.
20075 - Hold certain marked_for_close connections open until they're finished
20076 flushing, rather than losing bytes by closing them too early.
20077 - Correctly report the reason for ending a stream
20078 - Remove some duplicate calls to connection_mark_for_close
20079 - Put switch_id and start_daemon earlier in the boot sequence, so it
20080 will actually try to chdir() to options.DataDirectory
20081 - Make 'make test' exit(1) if a test fails; fix some unit tests
20082 - Make tor fail when you use a config option it doesn't know about,
20083 rather than warn and continue.
20084 - Make --version work
20085 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
20088 Changes in version 0.0.2pre23 - 2004-02-29
20090 - Print a statement when the first circ is finished, so the user
20091 knows it's working.
20092 - If a relay cell is unrecognized at the end of the circuit,
20093 send back a destroy. (So attacks to mutate cells are more
20095 - New config option 'excludenodes' to avoid certain nodes for circuits.
20096 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
20097 so you can collect coredumps there.
20099 - Fix a bug in tls flushing where sometimes data got wedged and
20100 didn't flush until more data got sent. Hopefully this bug was
20101 a big factor in the random delays we were seeing.
20102 - Make 'connected' cells include the resolved IP, so the client
20103 dns cache actually gets populated.
20104 - Disallow changing from ORPort=0 to ORPort>0 on hup.
20105 - When we time-out on a stream and detach from the circuit, send an
20106 end cell down it first.
20107 - Only warn about an unknown router (in exitnodes, entrynodes,
20108 excludenodes) after we've fetched a directory.
20111 Changes in version 0.0.2pre22 - 2004-02-26
20113 - Servers publish less revealing uname information in descriptors.
20114 - More memory tracking and assertions, to crash more usefully when
20116 - If the default torrc isn't there, just use some default defaults.
20117 Plus provide an internal dirservers file if they don't have one.
20118 - When the user tries to use Tor as an http proxy, give them an http
20119 501 failure explaining that we're a socks proxy.
20120 - Dump a new router.desc on hup, to help confused people who change
20121 their exit policies and then wonder why router.desc doesn't reflect
20123 - Clean up the generic tor.sh init script that we ship with.
20125 - If the exit stream is pending on the resolve, and a destroy arrives,
20126 then the stream wasn't getting removed from the pending list. I
20127 think this was the one causing recent server crashes.
20128 - Use a more robust poll on OSX 10.3, since their poll is flaky.
20129 - When it couldn't resolve any dirservers, it was useless from then on.
20130 Now it reloads the RouterFile (or default dirservers) if it has no
20132 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
20133 many users don't even *have* a /usr/local/sbin/.
20136 Changes in version 0.0.2pre21 - 2004-02-18
20138 - There's a ChangeLog file that actually reflects the changelog.
20139 - There's a 'torify' wrapper script, with an accompanying
20140 tor-tsocks.conf, that simplifies the process of using tsocks for
20141 tor. It even has a man page.
20142 - The tor binary gets installed to sbin rather than bin now.
20143 - Retry streams where the connected cell hasn't arrived in 15 seconds
20144 - Clean up exit policy handling -- get the default out of the torrc,
20145 so we can update it without forcing each server operator to fix
20147 - Allow imaps and pop3s in default exit policy
20149 - Prevent picking middleman nodes as the last node in the circuit
20152 Changes in version 0.0.2pre20 - 2004-01-30
20154 - We now have a deb package, and it's in debian unstable. Go to
20155 it, apt-getters. :)
20156 - I've split the TotalBandwidth option into BandwidthRate (how many
20157 bytes per second you want to allow, long-term) and
20158 BandwidthBurst (how many bytes you will allow at once before the cap
20159 kicks in). This better token bucket approach lets you, say, set
20160 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
20161 performance while not exceeding your monthly bandwidth quota.
20162 - Push out a tls record's worth of data once you've got it, rather
20163 than waiting until you've read everything waiting to be read. This
20164 may improve performance by pipelining better. We'll see.
20165 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
20166 from failed circuits (if they haven't been connected yet) and attach
20168 - Expire old streams that haven't managed to connect. Some day we'll
20169 have them reattach to new circuits instead.
20172 - Fix several memory leaks that were causing servers to become bloated
20174 - Fix a few very rare assert triggers. A few more remain.
20175 - Setuid to User _before_ complaining about running as root.
20178 Changes in version 0.0.2pre19 - 2004-01-07
20180 - Fix deadlock condition in dns farm. We were telling a child to die by
20181 closing the parent's file descriptor to him. But newer children were
20182 inheriting the open file descriptor from the parent, and since they
20183 weren't closing it, the socket never closed, so the child never read
20184 eof, so he never knew to exit. Similarly, dns workers were holding
20185 open other sockets, leading to all sorts of chaos.
20186 - New cleaner daemon() code for forking and backgrounding.
20187 - If you log to a file, it now prints an entry at the top of the
20188 logfile so you know it's working.
20189 - The onionskin challenge length was 30 bytes longer than necessary.
20190 - Started to patch up the spec so it's not quite so out of date.
20193 Changes in version 0.0.2pre18 - 2004-01-02
20195 - Fix endian issues with the 'integrity' field in the relay header.
20196 - Fix a potential bug where connections in state
20197 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
20200 Changes in version 0.0.2pre17 - 2003-12-30
20202 - Made --debuglogfile (or any second log file, actually) work.
20203 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
20204 adversary could force us into an infinite loop.
20207 - Each onionskin handshake now includes a hash of the computed key,
20208 to prove the server's identity and help perfect forward secrecy.
20209 - Changed cell size from 256 to 512 bytes (working toward compatibility
20211 - Changed cell length to 2 bytes, and moved it to the relay header.
20212 - Implemented end-to-end integrity checking for the payloads of
20214 - Separated streamid from 'recognized' (otherwise circuits will get
20215 messed up when we try to have streams exit from the middle). We
20216 use the integrity-checking to confirm that a cell is addressed to
20218 - Randomize the initial circid and streamid values, so an adversary who
20219 breaks into a node can't learn how many circuits or streams have
20223 Changes in version 0.0.2pre16 - 2003-12-14
20225 - Fixed a bug that made HUP trigger an assert
20226 - Fixed a bug where a circuit that immediately failed wasn't being
20227 counted as a failed circuit in counting retries.
20230 - Now we close the circuit when we get a truncated cell: otherwise we're
20231 open to an anonymity attack where a bad node in the path truncates
20232 the circuit and then we open streams at him.
20233 - Add port ranges to exit policies
20234 - Add a conservative default exit policy
20235 - Warn if you're running tor as root
20236 - on HUP, retry OR connections and close/rebind listeners
20237 - options.EntryNodes: try these nodes first when picking the first node
20238 - options.ExitNodes: if your best choices happen to include any of
20239 your preferred exit nodes, you choose among just those preferred
20241 - options.ExcludedNodes: nodes that are never picked in path building
20244 Changes in version 0.0.2pre15 - 2003-12-03
20245 o Robustness and bugfixes:
20246 - Sometimes clients would cache incorrect DNS resolves, which would
20247 really screw things up.
20248 - An OP that goes offline would slowly leak all its sockets and stop
20250 - A wide variety of bugfixes in exit node selection, exit policy
20251 handling, and processing pending streams when a new circuit is
20253 - Pick nodes for a path only from those the directory says are up
20254 - Choose randomly from all running dirservers, not always the first one
20255 - Increase allowed http header size for directory fetch.
20256 - Stop writing to stderr (if we're daemonized it will be closed).
20257 - Enable -g always, so cores will be more useful to me.
20258 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
20261 - Wrote a man page. It lists commonly used options.
20264 - Change default loglevel to warn.
20265 - Make PidFile default to null rather than littering in your CWD.
20266 - OnionRouter config option is now obsolete. Instead it just checks
20268 - Moved to a single unified torrc file for both clients and servers.
20271 Changes in version 0.0.2pre14 - 2003-11-29
20272 o Robustness and bugfixes:
20273 - Force the admin to make the DataDirectory himself
20274 - to get ownership/permissions right
20275 - so clients no longer make a DataDirectory and then never use it
20276 - fix bug where a client who was offline for 45 minutes would never
20277 pull down a directory again
20278 - fix (or at least hide really well) the dns assert bug that was
20279 causing server crashes
20280 - warnings and improved robustness wrt clockskew for certs
20281 - use the native daemon(3) to daemonize, when available
20282 - exit if bind() fails
20283 - exit if neither socksport nor orport is defined
20284 - include our own tor_timegm (Win32 doesn't have its own)
20285 - bugfix for win32 with lots of connections
20286 - fix minor bias in PRNG
20287 - make dirserver more robust to corrupt cached directory
20290 - Wrote the design document (woo)
20292 o Circuit building and exit policies:
20293 - Circuits no longer try to use nodes that the directory has told them
20295 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
20296 bitcounts (18.0.0.0/8).
20297 - Make AP connections standby for a circuit if no suitable circuit
20298 exists, rather than failing
20299 - Circuits choose exit node based on addr/port, exit policies, and
20300 which AP connections are standing by
20301 - Bump min pathlen from 2 to 3
20302 - Relay end cells have a payload to describe why the stream ended.
20303 - If the stream failed because of exit policy, try again with a new
20305 - Clients have a dns cache to remember resolved addresses.
20306 - Notice more quickly when we have no working circuits
20309 - APPort is now called SocksPort
20310 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
20312 - RecommendedVersions is now a config variable rather than
20313 hardcoded (for dirservers)
20314 - Reloads config on HUP
20315 - Usage info on -h or --help
20316 - If you set User and Group config vars, it'll setu/gid to them.
20319 Changes in version 0.0.2pre13 - 2003-10-19
20320 o General stability:
20321 - SSL_write no longer fails when it returns WANTWRITE and the number
20322 of bytes in the buf has changed by the next SSL_write call.
20323 - Fix segfault fetching directory when network is down
20324 - Fix a variety of minor memory leaks
20325 - Dirservers reload the fingerprints file on HUP, so I don't have
20326 to take down the network when I approve a new router
20327 - Default server config file has explicit Address line to specify fqdn
20330 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
20331 - Make listener connections not ever alloc bufs
20333 o Autoconf improvements:
20334 - don't clobber an external CFLAGS in ./configure
20335 - Make install now works
20336 - create var/lib/tor on make install
20337 - autocreate a tor.sh initscript to help distribs
20338 - autocreate the torrc and sample-server-torrc with correct paths
20340 o Log files and Daemonizing now work:
20341 - If --DebugLogFile is specified, log to it at -l debug
20342 - If --LogFile is specified, use it instead of commandline
20343 - If --RunAsDaemon is set, tor forks and backgrounds on startup