1 Changes in version 0.2.4.11-alpha - 2013-03-11
2 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3 more robust, makes hidden service authentication work again, and
4 resolves a DPI fingerprint for Tor's SSL transport.
6 o Major features (directory authorities):
7 - Directory authorities now support a new consensus method (17)
8 where they cap the published bandwidth of servers for which
9 insufficient bandwidth measurements exist. Fixes part of bug 2286.
10 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
11 serve any v2 directory information. Now we can test disabling the
12 old deprecated v2 directory format, and see whether doing so has
13 any effect on network load. Begins to fix bug 6783.
14 - Directory authorities now include inside each vote a statement of
15 the performance thresholds they used when assigning flags.
16 Implements ticket 8151.
18 o Major bugfixes (directory authorities):
19 - Stop marking every relay as having been down for one hour every
20 time we restart a directory authority. These artificial downtimes
21 were messing with our Stable and Guard flag calculations. Fixes
22 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
24 o Major bugfixes (hidden services):
25 - Allow hidden service authentication to succeed again. When we
26 refactored the hidden service introduction code back
27 in 0.2.4.1-alpha, we didn't update the code that checks
28 whether authentication information is present, causing all
29 authentication checks to return "false". Fix for bug 8207; bugfix
30 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
32 o Minor features (relays, bridges):
33 - Make bridge relays check once a minute for whether their IP
34 address has changed, rather than only every 15 minutes. Resolves
36 - Refactor resolve_my_address() so it returns the method by which we
37 decided our public IP address (explicitly configured, resolved from
38 explicit hostname, guessed from interfaces, learned by gethostname).
39 Now we can provide more helpful log messages when a relay guesses
40 its IP address incorrectly (e.g. due to unexpected lines in
41 /etc/hosts). Resolves ticket 2267.
42 - Teach bridge-using clients to avoid 0.2.2 bridges when making
43 microdescriptor-related dir requests, and only fall back to normal
44 descriptors if none of their bridges can handle microdescriptors
45 (as opposed to the fix in ticket 4013, which caused them to fall
46 back to normal descriptors if *any* of their bridges preferred
47 them). Resolves ticket 4994.
48 - Randomize the lifetime of our SSL link certificate, so censors can't
49 use the static value for filtering Tor flows. Resolves ticket 8443;
50 related to ticket 4014 which was included in 0.2.2.33.
52 o Minor features (portability):
53 - Tweak the curve25519-donna*.c implementations to tolerate systems
54 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
55 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
56 the signs of types during autoconf. This is better than our old
57 approach, which didn't work when cross-compiling.
58 - Detect the sign of enum values, rather than assuming that MSC is the
59 only compiler where enum types are all signed. Fixes bug 7727;
60 bugfix on 0.2.4.10-alpha.
62 o Minor features (other):
63 - Say "KBytes" rather than "KB" in the man page (for various values
64 of K), to further reduce confusion about whether Tor counts in
65 units of memory or fractions of units of memory. Resolves ticket 7054.
66 - Clear the high bit on curve25519 public keys before passing them to
67 our backend, in case we ever wind up using a backend that doesn't do
68 so itself. If we used such a backend, and *didn't* clear the high bit,
69 we could wind up in a situation where users with such backends would
70 be distinguishable from users without. Fixes bug 8121; bugfix on
72 - Update to the February 6 2013 Maxmind GeoLite Country database.
74 o Minor bugfixes (clients):
75 - When we receive a RELAY_END cell with the reason DONE, or with no
76 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
77 status as "connection refused". Previously we reported these cases
78 as success but then immediately closed the connection. Fixes bug
79 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
80 - Downgrade an assertion in connection_ap_expire_beginning to an
81 LD_BUG message. The fix for bug 8024 should prevent this message
82 from displaying, but just in case, a warn that we can diagnose
83 is better than more assert crashes. Fixes bug 8065; bugfix on
85 - Lower path use bias thresholds to .80 for notice and .60 for warn.
86 Also make the rate limiting flags for the path use bias log messages
87 independent from the original path bias flags. Fixes bug 8161;
88 bugfix on 0.2.4.10-alpha.
90 o Minor bugfixes (relays):
91 - Stop trying to resolve our hostname so often (e.g. every time we
92 think about doing a directory fetch). Now we reuse the cached
93 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
94 and 2410 (bugfix on 0.1.2.2-alpha).
95 - Stop sending a stray "(null)" in some cases for the server status
96 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
98 - When choosing which stream on a formerly stalled circuit to wake
99 first, make better use of the platform's weak RNG. Previously,
100 we had been using the % ("modulo") operator to try to generate a
101 1/N chance of picking each stream, but this behaves badly with
102 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
104 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
105 Irix's random() only return 15 bits; Solaris's random() returns more
106 bits but its RAND_MAX says it only returns 15, and so on. Motivated
107 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
109 o Minor bugfixes (directory authorities):
110 - Directory authorities now use less space when formatting identical
111 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
114 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
115 - Avoid leaking memory if we fail to compute a consensus signature
116 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
117 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
119 - Fix a memory leak during safe-cookie controller authentication.
120 Bugfix on 0.2.3.13-alpha.
121 - Avoid memory leak of IPv6 policy content if we fail to format it into
122 a router descriptor. Bugfix on 0.2.4.7-alpha.
124 o Minor bugfixes (other code correctness issues):
125 - Avoid a crash if we fail to generate an extrainfo descriptor.
126 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
128 - When detecting the largest possible file descriptor (in order to
129 close all file descriptors when launching a new program), actually
130 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
131 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
133 - Fix a copy-and-paste error when adding a missing A1 to a routerset
134 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
135 Bugfix on 0.2.4.10-alpha.
136 - Fix an impossible-to-trigger integer overflow when estimating how
137 long our onionskin queue would take. (This overflow would require us
138 to accept 4 million onionskins before processing 100 of them.) Fixes
139 bug 8210; bugfix on 0.2.4.10-alpha.
141 o Code simplification and refactoring:
142 - Add a wrapper function for the common "log a message with a
146 Changes in version 0.2.4.10-alpha - 2013-02-04
147 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
148 certain attacks that flood the network with relays; changes the queue
149 for circuit create requests from a sized-based limit to a time-based
150 limit; resumes building with MSVC on Windows; and fixes a wide variety
153 o Major bugfixes (directory authority):
154 - When computing directory thresholds, ignore any rejected-as-sybil
155 nodes during the computation so that they can't influence Fast,
156 Guard, etc. (We should have done this for proposal 109.) Fixes
158 - When marking a node as a likely sybil, reset its uptime metrics
159 to zero, so that it cannot time towards getting marked as Guard,
160 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
164 - When a TLS write is partially successful but incomplete, remember
165 that the flushed part has been flushed, and notice that bytes were
166 actually written. Reported and fixed pseudonymously. Fixes bug
167 7708; bugfix on Tor 0.1.0.5-rc.
168 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
169 ID: these could be used to create unexpected streams and circuits
170 which would count as "present" to some parts of Tor but "absent"
171 to others, leading to zombie circuits and streams or to a bandwidth
172 denial-of-service. Fixes bug 7889; bugfix on every released version
173 of Tor. Reported by "oftc_must_be_destroyed".
174 - Rename all macros in our local copy of queue.h to begin with "TOR_".
175 This change seems the only good way to permanently prevent conflicts
176 with queue.h on various operating systems. Fixes bug 8107; bugfix
179 o Major features (relay):
180 - Instead of limiting the number of queued onionskins (aka circuit
181 create requests) to a fixed, hard-to-configure number, we limit
182 the size of the queue based on how many we expect to be able to
183 process in a given amount of time. We estimate the time it will
184 take to process an onionskin based on average processing time
185 of previous onionskins. Closes ticket 7291. You'll never have to
186 configure MaxOnionsPending again.
188 o Major features (portability):
189 - Resume building correctly with MSVC and Makefile.nmake. This patch
190 resolves numerous bugs and fixes reported by ultramage, including
191 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
192 - Make the ntor and curve25519 code build correctly with MSVC.
193 Fix on 0.2.4.8-alpha.
196 - When directory authorities are computing thresholds for flags,
197 never let the threshold for the Fast flag fall below 4096
198 bytes. Also, do not consider nodes with extremely low bandwidths
199 when deciding thresholds for various directory flags. This change
200 should raise our threshold for Fast relays, possibly in turn
201 improving overall network performance; see ticket 1854. Resolves
203 - The Tor client now ignores sub-domain components of a .onion
204 address. This change makes HTTP "virtual" hosting
205 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
206 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
207 hosted on the same hidden service. Implements proposal 204.
208 - We compute the overhead from passing onionskins back and forth to
209 cpuworkers, and report it when dumping statistics in response to
210 SIGUSR1. Supports ticket 7291.
212 o Minor features (path selection):
213 - When deciding whether we have enough descriptors to build circuits,
214 instead of looking at raw relay counts, look at which fraction
215 of (bandwidth-weighted) paths we're able to build. This approach
216 keeps clients from building circuits if their paths are likely to
217 stand out statistically. The default fraction of paths needed is
218 taken from the consensus directory; you can override it with the
219 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
220 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
221 and we have GeoIP information, also exclude all nodes with unknown
222 countries "??" and "A1". This behavior is controlled by the
223 new GeoIPExcludeUnknown option: you can make such nodes always
224 excluded with "GeoIPExcludeUnknown 1", and disable the feature
225 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
226 gets you the default behavior. Implements feature 7706.
227 - Path Use Bias: Perform separate accounting for successful circuit
228 use. Keep separate statistics on stream attempt rates versus stream
229 success rates for each guard. Provide configurable thresholds to
230 determine when to emit log messages or disable use of guards that
231 fail too many stream attempts. Resolves ticket 7802.
233 o Minor features (log messages):
234 - When learning a fingerprint for a bridge, log its corresponding
235 transport type. Implements ticket 7896.
236 - Improve the log message when "Bug/attack: unexpected sendme cell
237 from client" occurs, to help us track bug 8093.
240 - Remove a couple of extraneous semicolons that were upsetting the
241 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
242 bugfix on 0.2.2.1-alpha.
243 - Remove a source of rounding error during path bias count scaling;
244 don't count cannibalized circuits as used for path bias until we
245 actually try to use them; and fix a circuit_package_relay_cell()
246 warning message about n_chan==NULL. Fixes bug 7802.
247 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
248 actually link against nacl when we're configured to use it. Fixes
249 bug 7972; bugfix on 0.2.4.8-alpha.
250 - Compile correctly with the --disable-curve25519 option. Fixes
251 bug 8153; bugfix on 0.2.4.8-alpha.
253 o Build improvements:
254 - Do not report status verbosely from autogen.sh unless the -v flag
255 is specified. Fixes issue 4664. Patch from Onizuka.
256 - Replace all calls to snprintf() outside of src/ext with
257 tor_snprintf(). Also remove the #define to replace snprintf with
258 _snprintf on Windows; they have different semantics, and all of
259 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
260 - Try to detect if we are ever building on a platform where
261 memset(...,0,...) does not set the value of a double to 0.0. Such
262 platforms are permitted by the C standard, though in practice
263 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
264 currently support them, but it's better to detect them and fail
265 than to perform erroneously.
268 - Stop exporting estimates of v2 and v3 directory traffic shares
269 in extrainfo documents. They were unneeded and sometimes inaccurate.
270 Also stop exporting any v2 directory request statistics. Resolves
272 - Drop support for detecting and warning about versions of Libevent
273 before 1.3e. Nothing reasonable ships with them any longer;
274 warning the user about them shouldn't be needed. Resolves ticket
277 o Code simplifications and refactoring:
278 - Rename "isin" functions to "contains", for grammar. Resolves
280 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
281 with the natural logarithm function from the system libm. Resolves
285 Changes in version 0.2.4.9-alpha - 2013-01-15
286 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
290 - Fix backward compatibility logic when receiving an embedded ntor
291 handshake tunneled in a CREATE cell. This clears up the "Bug:
292 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
296 Changes in version 0.2.4.8-alpha - 2013-01-14
297 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
298 risks, adds a new stronger and faster circuit handshake, and offers
299 stronger and faster link encryption when both sides support it.
302 - Preliminary support for directory guards (proposal 207): when
303 possible, clients now use their entry guards for non-anonymous
304 directory requests. This can help prevent client enumeration. Note
305 that this behavior only works when we have a usable consensus
306 directory, and when options about what to download are more or less
307 standard. In the future we should re-bootstrap from our guards,
308 rather than re-bootstrapping from the preconfigured list of
309 directory sources that ships with Tor. Resolves ticket 6526.
310 - Tor relays and clients now support a better CREATE/EXTEND cell
311 format, allowing the sender to specify multiple address, identity,
312 and handshake types. Implements Robert Ransom's proposal 200;
315 o Major features (new circuit handshake):
316 - Tor now supports a new circuit extension handshake designed by Ian
317 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
318 circuit extension handshake, later called "TAP", was a bit slow
319 (especially on the relay side), had a fragile security proof, and
320 used weaker keys than we'd now prefer. The new circuit handshake
321 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
322 function, making it significantly more secure than the older
323 handshake, and significantly faster. Tor can use one of two built-in
324 pure-C curve25519-donna implementations by Adam Langley, or it
325 can link against the "nacl" library for a tuned version if present.
327 The built-in version is very fast for 64-bit systems when building
328 with GCC. The built-in 32-bit version is still faster than the
329 old TAP protocol, but using libnacl is better on most such hosts.
331 Clients don't currently use this protocol by default, since
332 comparatively few clients support it so far. To try it, set
333 UseNTorHandshake to 1.
335 Implements proposal 216; closes ticket 7202.
337 o Major features (better link encryption):
338 - Relays can now enable the ECDHE TLS ciphersuites when available
339 and appropriate. These ciphersuites let us negotiate forward-secure
340 TLS secret keys more safely and more efficiently than with our
341 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
342 public relays prefer the (faster) P224 group, and bridges prefer
343 the (more common) P256 group; you can override this with the
346 Enabling these ciphers was a little tricky, since for a long time,
347 clients had been claiming to support them without actually doing
348 so, in order to foil fingerprinting. But with the client-side
349 implementation of proposal 198 in 0.2.3.17-beta, clients can now
350 match the ciphers from recent Firefox versions *and* list the
351 ciphers they actually mean, so relays can believe such clients
352 when they advertise ECDHE support in their TLS ClientHello messages.
354 This feature requires clients running 0.2.3.17-beta or later,
355 and requires both sides to be running OpenSSL 1.0.0 or later
356 with ECC support. OpenSSL 1.0.1, with the compile-time option
357 "enable-ec_nistp_64_gcc_128", is highly recommended.
359 Implements the relay side of proposal 198; closes ticket 7200.
362 - Avoid crashing when, as a relay without IPv6-exit support, a
363 client insists on getting an IPv6 address or nothing. Fixes bug
364 7814; bugfix on 0.2.4.7-alpha.
367 - Improve circuit build timeout handling for hidden services.
368 In particular: adjust build timeouts more accurately depending
369 upon the number of hop-RTTs that a particular circuit type
370 undergoes. Additionally, launch intro circuits in parallel
371 if they timeout, and take the first one to reply as valid.
372 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
373 separate error codes; or at least, don't break for that reason.
374 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
375 - Update to the January 2 2013 Maxmind GeoLite Country database.
377 o Minor features (testing):
378 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
379 (P-256) Diffie-Hellman handshakes to src/or/bench.
380 - Add benchmark functions to test onion handshake performance.
382 o Minor features (path bias detection):
383 - Alter the Path Bias log messages to be more descriptive in terms
384 of reporting timeouts and other statistics.
385 - Create three levels of Path Bias log messages, as opposed to just
386 two. These are configurable via consensus as well as via the torrc
387 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
388 The default values are 0.70, 0.50, and 0.30 respectively.
389 - Separate the log message levels from the decision to drop guards,
390 which also is available via torrc option PathBiasDropGuards.
391 PathBiasDropGuards still defaults to 0 (off).
392 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
393 in combination with PathBiasExtremeRate.
394 - Increase the default values for PathBiasScaleThreshold and
395 PathBiasCircThreshold from (200, 20) to (300, 150).
396 - Add in circuit usage accounting to path bias. If we try to use a
397 built circuit but fail for any reason, it counts as path bias.
398 Certain classes of circuits where the adversary gets to pick your
399 destination node are exempt from this accounting. Usage accounting
400 can be specifically disabled via consensus parameter or torrc.
401 - Convert all internal path bias state to double-precision floating
402 point, to avoid roundoff error and other issues.
403 - Only record path bias information for circuits that have completed
404 *two* hops. Assuming end-to-end tagging is the attack vector, this
405 makes us more resilient to ambient circuit failure without any
406 detection capability loss.
408 o Minor bugfixes (log messages):
409 - Rate-limit the "No circuits are opened. Relaxed timeout for a
410 circuit with channel state open..." message to once per hour to
411 keep it from filling the notice logs. Mitigates bug 7799 but does
412 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
413 - Avoid spurious warnings when configuring multiple client ports of
414 which only some are nonlocal. Previously, we had claimed that some
415 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
418 o Code simplifications and refactoring:
419 - Get rid of a couple of harmless clang warnings, where we compared
420 enums to ints. These warnings are newly introduced in clang 3.2.
421 - Split the onion.c file into separate modules for the onion queue
422 and the different handshakes it supports.
423 - Remove the marshalling/unmarshalling code for sending requests to
424 cpuworkers over a socket, and instead just send structs. The
425 recipient will always be the same Tor binary as the sender, so
426 any encoding is overkill.
429 Changes in version 0.2.4.7-alpha - 2012-12-24
430 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
431 directory mirrors for more robust bootstrapping; fixes more issues where
432 clients with changing network conditions refuse to make any circuits;
433 adds initial support for exiting to IPv6 addresses; resumes being able
434 to update our GeoIP database, and includes the geoip6 file this time;
435 turns off the client-side DNS cache by default due to privacy risks;
436 and fixes a variety of other issues.
438 o Major features (client resilience):
439 - Add a new "FallbackDir" torrc option to use when we can't use
440 a directory mirror from the consensus (either because we lack a
441 consensus, or because they're all down). Currently, all authorities
442 are fallbacks by default, and there are no other default fallbacks,
443 but that will change. This option will allow us to give clients a
444 longer list of servers to try to get a consensus from when first
445 connecting to the Tor network, and thereby reduce load on the
446 directory authorities. Implements proposal 206, "Preconfigured
447 directory sources for bootstrapping". We also removed the old
448 "FallbackNetworkstatus" option, since we never got it working well
449 enough to use it. Closes bug 572.
450 - If we have no circuits open, use a relaxed timeout (the
451 95-percentile cutoff) until a circuit succeeds. This heuristic
452 should allow Tor to succeed at building circuits even when the
453 network connection drastically changes. Should help with bug 3443.
455 o Major features (IPv6):
456 - Tor now has (alpha) support for exiting to IPv6 addresses. To
457 enable it as an exit node, make sure that you have IPv6
458 connectivity, then set the IPv6Exit flag to 1. Also make sure your
459 exit policy reads as you would like: the address * applies to all
460 address families, whereas *4 is IPv4 address only, and *6 is IPv6
461 addresses only. On the client side, you'll need to wait until the
462 authorities have upgraded, wait for enough exits to support IPv6,
463 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
464 ticket 5547, implements proposal 117 as revised in proposal 208.
466 We DO NOT recommend that clients with actual anonymity needs start
467 using IPv6 over Tor yet, since not enough exits support it yet.
469 o Major features (geoip database):
470 - Maxmind began labelling Tor relays as being in country "A1",
471 which breaks by-country node selection inside Tor. Now we use a
472 script to replace "A1" ("Anonymous Proxy") entries in our geoip
473 file with real country codes. This script fixes about 90% of "A1"
474 entries automatically and uses manual country code assignments to
475 fix the remaining 10%. See src/config/README.geoip for details.
476 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
477 Country database, as modified above.
479 o Major bugfixes (client-side DNS):
480 - Turn off the client-side DNS cache by default. Updating and using
481 the DNS cache is now configurable on a per-client-port
482 level. SOCKSPort, DNSPort, etc lines may now contain
483 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
484 cache these types of DNS answers when we receive them from an
485 exit node in response to an application request on this port, and
486 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
487 cached DNS answers of these types, we shouldn't use them. It's
488 potentially risky to use cached DNS answers at the client, since
489 doing so can indicate to one exit what answers we've gotten
490 for DNS lookups in the past. With IPv6, this becomes especially
491 problematic. Using cached DNS answers for requests on the same
492 circuit would present less linkability risk, since all traffic
493 on a circuit is already linkable, but it would also provide
494 little performance benefit: the exit node caches DNS replies
495 too. Implements a simplified version of Proposal 205. Implements
498 o Major bugfixes (other):
499 - Alter circuit build timeout measurement to start at the point
500 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
501 initialization). This should make our timeout measurements more
502 uniform. Previously, we were sometimes including ORconn setup time
503 in our circuit build time measurements. Should resolve bug 3443.
504 - Fix an assertion that could trigger in hibernate_go_dormant() when
505 closing an or_connection_t: call channel_mark_for_close() rather
506 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
508 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
509 7655; bugfix on 0.2.4.6-alpha.
512 - Add a new torrc option "ServerTransportListenAddr" to let bridge
513 operators select the address where their pluggable transports will
514 listen for connections. Resolves ticket 7013.
515 - Allow an optional $ before the node identity digest in the
516 controller command GETINFO ns/id/<identity>, for consistency with
517 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
518 - Log packaged cell fullness as part of the heartbeat message.
519 Diagnosis to try to determine the extent of bug 7743.
521 o Minor features (IPv6):
522 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
523 prefer to hand out virtual IPv6 addresses, since there are more of
524 them and we can't run out. To override this behavior and make IPv4
525 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
526 or DNSPort you're using for resolving. Implements ticket 7571.
527 - AutomapHostsOnResolve responses are now randomized, to avoid
528 annoying situations where Tor is restarted and applications
529 connect to the wrong addresses.
530 - Never try more than 1000 times to pick a new virtual address when
531 AutomapHostsOnResolve is set. That's good enough so long as we
532 aren't close to handing out our entire virtual address space;
533 if you're getting there, it's best to switch to IPv6 virtual
537 - The ADDRMAP command can no longer generate an ill-formed error
538 code on a failed MAPADDRESS. It now says "internal" rather than
539 an English sentence fragment with spaces in the middle. Bugfix on
541 - Fix log messages and comments to avoid saying "GMT" when we mean
542 "UTC". Fixes bug 6113.
543 - Compile on win64 using mingw64. Fixes bug 7260; patches from
545 - Fix a crash when debugging unit tests on Windows: deallocate a
546 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
547 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
550 - The DirServer option is now DirAuthority, for consistency with
551 current naming patterns. You can still use the old DirServer form.
553 o Code simplification and refactoring:
554 - Move the client-side address-map/virtual-address/DNS-cache code
555 out of connection_edge.c into a new addressmap.c module.
556 - Remove unused code for parsing v1 directories and "running routers"
557 documents. Fixes bug 6887.
560 Changes in version 0.2.3.25 - 2012-11-19
561 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
562 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
563 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
564 programmer, and friend. Unstinting in his dedication to the cause of
565 freedom, he inspired and helped many of us as we began our work on
566 anonymity, and inspires us still. Please honor his memory by writing
567 software to protect people's freedoms, and by helping others to do so.
569 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
570 significantly reduced directory overhead (via microdescriptors),
571 enormous crypto performance improvements for fast relays on new
572 enough hardware, a new v3 TLS handshake protocol that can better
573 resist fingerprinting, support for protocol obfuscation plugins (aka
574 pluggable transports), better scalability for hidden services, IPv6
575 support for bridges, performance improvements like allowing clients
576 to skip the first round-trip on the circuit ("optimistic data") and
577 refilling token buckets more often, a new "stream isolation" design
578 to isolate different applications on different circuits, and many
579 stability, security, and privacy fixes.
582 - Tor tries to wipe potentially sensitive data after using it, so
583 that if some subsequent security failure exposes Tor's memory,
584 the damage will be limited. But we had a bug where the compiler
585 was eliminating these wipe operations when it decided that the
586 memory was no longer visible to a (correctly running) program,
587 hence defeating our attempt at defense in depth. We fix that
588 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
589 is unlikely to optimize away. Future versions of Tor may use
590 a less ridiculously heavy approach for this. Fixes bug 7352.
591 Reported in an article by Andrey Karpov.
594 - Fix a harmless bug when opting against publishing a relay descriptor
595 because DisableNetwork is set. Fixes bug 7464; bugfix on
599 Changes in version 0.2.4.6-alpha - 2012-11-13
600 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
601 makes our defense-in-depth memory wiping more reliable, and begins to
602 count IPv6 addresses in bridge statistics,
605 - Fix an assertion failure that could occur when closing a connection
606 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
608 - Tor tries to wipe potentially sensitive data after using it, so
609 that if some subsequent security failure exposes Tor's memory,
610 the damage will be limited. But we had a bug where the compiler
611 was eliminating these wipe operations when it decided that the
612 memory was no longer visible to a (correctly running) program,
613 hence defeating our attempt at defense in depth. We fix that
614 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
615 is unlikely to optimize away. Future versions of Tor may use
616 a less ridiculously heavy approach for this. Fixes bug 7352.
617 Reported in an article by Andrey Karpov.
620 - Add GeoIP database for IPv6 addresses. The new config option
622 - Bridge statistics now count bridge clients connecting over IPv6:
623 bridge statistics files now list "bridge-ip-versions" and
624 extra-info documents list "geoip6-db-digest". The control protocol
625 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
626 implementation by "shkoo", addressing ticket 5055.
629 - Warn when we are binding low ports when hibernation is enabled;
630 previously we had warned when we were _advertising_ low ports with
631 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
632 - Fix a harmless bug when opting against publishing a relay descriptor
633 because DisableNetwork is set. Fixes bug 7464; bugfix on
635 - Add warning message when a managed proxy dies during configuration.
636 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
637 - Fix a linking error when building tor-fw-helper without miniupnp.
638 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
639 - Check for closing an or_connection_t without going through correct
640 channel functions; emit a warning and then call
641 connection_or_close_for_error() so we don't assert as in bugs 7212
643 - Compile correctly on compilers without C99 designated initializer
644 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
645 - Avoid a possible assert that can occur when channel_send_destroy() is
646 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
647 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
648 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
649 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
650 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
652 o Code simplification and refactoring:
653 - Start using OpenBSD's implementation of queue.h, so that we don't
654 need to hand-roll our own pointer and list structures whenever we
655 need them. (We can't rely on a sys/queue.h, since some operating
656 systems don't have them, and the ones that do have them don't all
657 present the same extensions.)
660 Changes in version 0.2.4.5-alpha - 2012-10-25
661 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
662 two important security vulnerabilities that could lead to remotely
663 triggerable relay crashes, fix a major bug that was preventing clients
664 from choosing suitable exit nodes, and refactor some of our code.
666 o Major bugfixes (security, also in 0.2.3.24-rc):
667 - Fix a group of remotely triggerable assertion failures related to
668 incorrect link protocol negotiation. Found, diagnosed, and fixed
669 by "some guy from France". Fix for CVE-2012-2250; bugfix on
671 - Fix a denial of service attack by which any directory authority
672 could crash all the others, or by which a single v2 directory
673 authority could crash everybody downloading v2 directory
674 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
676 o Major bugfixes (also in 0.2.3.24-rc):
677 - When parsing exit policy summaries from microdescriptors, we had
678 previously been ignoring the last character in each one, so that
679 "accept 80,443,8080" would be treated by clients as indicating
680 a node that allows access to ports 80, 443, and 808. That would
681 lead to clients attempting connections that could never work,
682 and ignoring exit nodes that would support their connections. Now
683 clients parse these exit policy summaries correctly. Fixes bug 7192;
684 bugfix on 0.2.3.1-alpha.
686 o Minor bugfixes (also in 0.2.3.24-rc):
687 - Clients now consider the ClientRejectInternalAddresses config option
688 when using a microdescriptor consensus stanza to decide whether
689 an exit relay would allow exiting to an internal address. Fixes
690 bug 7190; bugfix on 0.2.3.1-alpha.
693 - Only disable TLS session ticket support when running as a TLS
694 server. Now clients will blend better with regular Firefox
695 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
697 o Code simplification and refactoring:
698 - Start using OpenBSD's implementation of queue.h (originally by
700 - Move the entry node code from circuitbuild.c to its own file.
701 - Move the circuit build timeout tracking code from circuitbuild.c
705 Changes in version 0.2.3.24-rc - 2012-10-25
706 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
707 could lead to remotely triggerable relay crashes, and fixes
708 a major bug that was preventing clients from choosing suitable exit
711 o Major bugfixes (security):
712 - Fix a group of remotely triggerable assertion failures related to
713 incorrect link protocol negotiation. Found, diagnosed, and fixed
714 by "some guy from France". Fix for CVE-2012-2250; bugfix on
716 - Fix a denial of service attack by which any directory authority
717 could crash all the others, or by which a single v2 directory
718 authority could crash everybody downloading v2 directory
719 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
722 - When parsing exit policy summaries from microdescriptors, we had
723 previously been ignoring the last character in each one, so that
724 "accept 80,443,8080" would be treated by clients as indicating
725 a node that allows access to ports 80, 443, and 808. That would
726 lead to clients attempting connections that could never work,
727 and ignoring exit nodes that would support their connections. Now
728 clients parse these exit policy summaries correctly. Fixes bug 7192;
729 bugfix on 0.2.3.1-alpha.
732 - Clients now consider the ClientRejectInternalAddresses config option
733 when using a microdescriptor consensus stanza to decide whether
734 an exit relay would allow exiting to an internal address. Fixes
735 bug 7190; bugfix on 0.2.3.1-alpha.
738 Changes in version 0.2.4.4-alpha - 2012-10-20
739 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
740 vulnerability introduced by a change in OpenSSL, fixes a remotely
741 triggerable assert, and adds new channel_t and circuitmux_t abstractions
742 that will make it easier to test new connection transport and cell
743 scheduling algorithms.
745 o New directory authorities (also in 0.2.3.23-rc):
746 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
747 authority. Closes ticket 5749.
749 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
750 - Disable TLS session tickets. OpenSSL's implementation was giving
751 our TLS session keys the lifetime of our TLS context objects, when
752 perfect forward secrecy would want us to discard anything that
753 could decrypt a link connection as soon as the link connection
754 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
755 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
756 - Discard extraneous renegotiation attempts once the V3 link
757 protocol has been initiated. Failure to do so left us open to
758 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
759 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
761 o Internal abstraction features:
762 - Introduce new channel_t abstraction between circuits and
763 or_connection_t to allow for implementing alternate OR-to-OR
764 transports. A channel_t is an abstract object which can either be a
765 cell-bearing channel, which is responsible for authenticating and
766 handshaking with the remote OR and transmitting cells to and from
767 it, or a listening channel, which spawns new cell-bearing channels
768 at the request of remote ORs. Implements part of ticket 6465.
769 - Also new is the channel_tls_t subclass of channel_t, adapting it
770 to the existing or_connection_t code. The V2/V3 protocol handshaking
771 code which formerly resided in command.c has been moved below the
772 channel_t abstraction layer and may be found in channeltls.c now.
773 Implements the rest of ticket 6465.
774 - Introduce new circuitmux_t storing the queue of circuits for
775 a channel; this encapsulates and abstracts the queue logic and
776 circuit selection policy, and allows the latter to be overridden
777 easily by switching out a policy object. The existing EWMA behavior
778 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
780 o Required libraries:
781 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
782 strongly recommended.
785 - Warn users who run hidden services on a Tor client with
786 UseEntryGuards disabled that their hidden services will be
787 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
788 attack which motivated Tor to support entry guards in the first
789 place). Resolves ticket 6889.
790 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
791 dhill. Resolves ticket 6982.
792 - Option OutboundBindAddress can be specified multiple times and
793 accepts IPv6 addresses. Resolves ticket 6876.
795 o Minor bugfixes (also in 0.2.3.23-rc):
796 - Don't serve or accept v2 hidden service descriptors over a
797 relay's DirPort. It's never correct to do so, and disabling it
798 might make it more annoying to exploit any bugs that turn up in the
799 descriptor-parsing code. Fixes bug 7149.
800 - Fix two cases in src/or/transports.c where we were calling
801 fmt_addr() twice in a parameter list. Bug found by David
802 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
803 - Fix memory leaks whenever we logged any message about the "path
804 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
805 - When relays refuse a "create" cell because their queue of pending
806 create cells is too big (typically because their cpu can't keep up
807 with the arrival rate), send back reason "resource limit" rather
808 than reason "internal", so network measurement scripts can get a
809 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
812 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
813 - Free some more still-in-use memory at exit, to make hunting for
814 memory leaks easier. Resolves bug 7029.
815 - When a Tor client gets a "truncated" relay cell, the first byte of
816 its payload specifies why the circuit was truncated. We were
817 ignoring this 'reason' byte when tearing down the circuit, resulting
818 in the controller not being told why the circuit closed. Now we
819 pass the reason from the truncated cell to the controller. Bugfix
820 on 0.1.2.3-alpha; fixes bug 7039.
821 - Downgrade "Failed to hand off onionskin" messages to "debug"
822 severity, since they're typically redundant with the "Your computer
823 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
824 - Make clients running with IPv6 bridges connect over IPv6 again,
825 even without setting new config options ClientUseIPv6 and
826 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
827 - Use square brackets around IPv6 addresses in numerous places
828 that needed them, including log messages, HTTPS CONNECT proxy
829 requests, TransportProxy statefile entries, and pluggable transport
830 extra-info lines. Fixes bug 7011; patch by David Fifield.
832 o Code refactoring and cleanup:
833 - Source files taken from other packages now reside in src/ext;
834 previously they were scattered around the rest of Tor.
835 - Avoid use of reserved identifiers in our C code. The C standard
836 doesn't like us declaring anything that starts with an
837 underscore, so let's knock it off before we get in trouble. Fix
838 for bug 1031; bugfix on the first Tor commit.
841 Changes in version 0.2.3.23-rc - 2012-10-20
842 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
843 vulnerability introduced by a change in OpenSSL, and fixes a variety
844 of smaller bugs in preparation for the release.
846 o New directory authorities:
847 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
848 authority. Closes ticket 5749.
850 o Major bugfixes (security/privacy):
851 - Disable TLS session tickets. OpenSSL's implementation was giving
852 our TLS session keys the lifetime of our TLS context objects, when
853 perfect forward secrecy would want us to discard anything that
854 could decrypt a link connection as soon as the link connection
855 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
856 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
857 - Discard extraneous renegotiation attempts once the V3 link
858 protocol has been initiated. Failure to do so left us open to
859 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
860 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
863 - Fix a possible crash bug when checking for deactivated circuits
864 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
865 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
867 o Minor bugfixes (on 0.2.3.x):
868 - Fix two cases in src/or/transports.c where we were calling
869 fmt_addr() twice in a parameter list. Bug found by David
870 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
871 - Convert an assert in the pathbias code to a log message. The assert
872 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
873 bugfix on 0.2.3.17-beta.
874 - Fix memory leaks whenever we logged any message about the "path
875 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
877 o Minor bugfixes (on 0.2.2.x and earlier):
878 - Don't serve or accept v2 hidden service descriptors over a relay's
879 DirPort. It's never correct to do so, and disabling it might
880 make it more annoying to exploit any bugs that turn up in the
881 descriptor-parsing code. Fixes bug 7149.
882 - When relays refuse a "create" cell because their queue of pending
883 create cells is too big (typically because their cpu can't keep up
884 with the arrival rate), send back reason "resource limit" rather
885 than reason "internal", so network measurement scripts can get a
886 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
887 - Correct file sizes when reading binary files on Cygwin, to avoid
888 a bug where Tor would fail to read its state file. Fixes bug 6844;
889 bugfix on 0.1.2.7-alpha.
890 - Avoid undefined behaviour when parsing the list of supported
891 rendezvous/introduction protocols in a hidden service descriptor.
892 Previously, Tor would have confused (as-yet-unused) protocol version
893 numbers greater than 32 with lower ones on many platforms. Fixes
894 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
896 o Documentation fixes:
897 - Clarify that hidden services are TCP only. Fixes bug 6024.
900 Changes in version 0.2.4.3-alpha - 2012-09-22
901 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
902 assertion, resumes letting relays test reachability of their DirPort,
903 and cleans up a bunch of smaller bugs.
906 - Fix an assertion failure in tor_timegm() that could be triggered
907 by a badly formatted directory object. Bug found by fuzzing with
908 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
911 - Fix a possible crash bug when checking for deactivated circuits
912 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
913 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
914 - Allow routers to detect that their own DirPorts are running. When
915 we removed support for versions_supports_begindir, we also
916 accidentally removed the mechanism we used to self-test our
917 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
918 bugfix on 0.2.4.2-alpha.
921 - Switch to a completely time-invariant approach for picking nodes
922 weighted by bandwidth. Our old approach would run through the
923 part of the loop after it had made its choice slightly slower
924 than it ran through the part of the loop before it had made its
925 choice. Addresses ticket 6538.
926 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
927 by tor2web clients allows hidden services to identity tor2web
928 clients through their repeated selection of the same rendezvous
929 and introduction point circuit endpoints (their guards). Resolves
933 - Enable Tor to read configuration, state, and key information from
934 a FIFO. Previously Tor would only read from files with a positive
935 stat.st_size. Code from meejah; fixes bug 6044.
938 - Correct file sizes when reading binary files on Cygwin, to avoid
939 a bug where Tor would fail to read its state file. Fixes bug 6844;
940 bugfix on 0.1.2.7-alpha.
941 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
942 bugfix on 0.2.0.3-alpha.
943 - When complaining about a client port on a public address, log
944 which address we're complaining about. Fixes bug 4020; bugfix on
945 0.2.3.3-alpha. Patch by Tom Fitzhenry.
946 - Convert an assert in the pathbias code to a log message. The assert
947 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
948 bugfix on 0.2.3.17-beta.
949 - Our new buildsystem was overzealous about rebuilding manpages: it
950 would rebuild them all whenever any one of them changed. Now our
951 dependency checking should be correct. Fixes bug 6843; bugfix on
953 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
954 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
955 - Correct log printout about which address family is preferred
956 when connecting to a bridge with both an IPv4 and IPv6 OR port.
957 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
959 o Minor bugfixes (code cleanliness):
960 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
961 with large values. This situation was untriggered, but nevertheless
962 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
963 - Reject consensus votes with more than 64 known-flags. We aren't even
964 close to that limit yet, and our code doesn't handle it correctly.
965 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
966 - Avoid undefined behaviour when parsing the list of supported
967 rendezvous/introduction protocols in a hidden service descriptor.
968 Previously, Tor would have confused (as-yet-unused) protocol version
969 numbers greater than 32 with lower ones on many platforms. Fixes
970 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
971 - Fix handling of rendezvous client authorization types over 8.
972 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
973 - Fix building with older versions of GCC (2.95, for one) that don't
974 like preprocessor directives inside macro arguments. Found by
975 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
976 - Switch weighted node selection rule from using a list of doubles
977 to using a list of int64_t. This change should make the process
978 slightly easier to debug and maintain. Needed to finish ticket 6538.
980 o Code simplification and refactoring:
981 - Move the generic "config" code into a new file, and have "config.c"
982 hold only torrc- and state-related code. Resolves ticket 6823.
983 - Move the core of our "choose a weighted element at random" logic
984 into its own function, and give it unit tests. Now the logic is
985 testable, and a little less fragile too.
986 - Removed the testing_since field of node_t, which hasn't been used
987 for anything since 0.2.0.9-alpha.
989 o Documentation fixes:
990 - Clarify that hidden services are TCP only. Fixes bug 6024.
991 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
995 Changes in version 0.2.3.22-rc - 2012-09-11
996 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1000 - Fix an assertion failure in tor_timegm() that could be triggered
1001 by a badly formatted directory object. Bug found by fuzzing with
1002 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1005 - Avoid segfault when starting up having run with an extremely old
1006 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1010 Changes in version 0.2.2.39 - 2012-09-11
1011 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1015 - Fix an assertion failure in tor_timegm() that could be triggered
1016 by a badly formatted directory object. Bug found by fuzzing with
1017 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1018 - Do not crash when comparing an address with port value 0 to an
1019 address policy. This bug could have been used to cause a remote
1020 assertion failure by or against directory authorities, or to
1021 allow some applications to crash clients. Fixes bug 6690; bugfix
1025 Changes in version 0.2.4.2-alpha - 2012-09-10
1026 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1027 raises the default rate limiting even more, and makes the bootstrapping
1028 log messages less noisy.
1031 - Automatically forward the TCP ports of pluggable transport
1032 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1036 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1037 to 1GB/1GB. The previous defaults were intended to be "basically
1038 infinite", but it turns out they're now limiting our 100mbit+
1039 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1040 last time we raised it).
1043 - Detect when we're running with a version of OpenSSL other than the
1044 one we compiled with. This has occasionally given people hard-to-
1046 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1047 versions and capabilities when everything is going right. Resolves
1048 part of ticket 6736.
1049 - Directory authorities no long accept descriptors for any version of
1050 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1051 These versions are insecure, unsupported, or both. Implements
1055 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1056 to start with a triple-underscore so the controller won't touch it.
1057 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1058 - Avoid segfault when starting up having run with an extremely old
1059 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1061 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1062 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1063 - Don't follow the NULL pointer if microdescriptor generation fails.
1064 (This does not appear to be triggerable, but it's best to be safe.)
1065 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1066 - Fix mis-declared dependencies on src/common/crypto.c and
1067 src/or/tor_main.c that could break out-of-tree builds under some
1068 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1069 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1070 6778; bugfix on 0.2.4.1-alpha.
1071 - Fix a harmless (in this case) build warning for implicitly
1072 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1075 - Now that all versions before 0.2.2.x are disallowed, we no longer
1076 need to work around their missing features. Thus we can remove a
1077 bunch of compatibility code.
1080 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1081 TCP ports to forward. In the past it only accepted two ports:
1082 the ORPort and the DirPort.
1085 Changes in version 0.2.4.1-alpha - 2012-09-05
1086 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1087 bridgedb; lets relays use IPv6 addresses and directory authorities
1088 advertise them; and switches to a cleaner build interface.
1090 This is the first alpha release in a new series, so expect there to
1091 be bugs. Users who would rather test out a more stable branch should
1092 stay with 0.2.3.x for now.
1094 o Major features (bridges):
1095 - Bridges now report the pluggable transports they support to the
1096 bridge authority, so it can pass the supported transports on to
1097 bridgedb and/or eventually do reachability testing. Implements
1100 o Major features (IPv6):
1101 - Bridge authorities now accept IPv6 bridge addresses and include
1102 them in network status documents. Implements ticket 5534.
1103 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1104 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1105 to happen. Implements ticket 5535.
1106 - All kind of relays, not just bridges, can now advertise an IPv6
1107 OR port. Implements ticket 6362.
1108 - Directory authorities vote on IPv6 OR ports using the new consensus
1109 method 14. Implements ticket 6363.
1111 o Major features (build):
1112 - Switch to a nonrecursive Makefile structure. Now instead of each
1113 Makefile.am invoking other Makefile.am's, there is a master
1114 Makefile.am that includes the others. This change makes our build
1115 process slightly more maintainable, and improves parallelism for
1116 building with make -j. Original patch by Stewart Smith; various
1117 fixes by Jim Meyering.
1118 - Where available, we now use automake's "silent" make rules by
1119 default, so that warnings are easier to spot. You can get the old
1120 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1122 o Minor features (code security and spec conformance):
1123 - Clear keys and key-derived material left on the stack in
1124 rendservice.c and rendclient.c. Check return value of
1125 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1126 These fixes should make us more forward-secure against cold-boot
1127 attacks and the like. Fixes bug 2385.
1128 - Reject EXTEND cells sent to nonexistent streams. According to the
1129 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1130 we were only checking for stream IDs that were currently in use.
1131 Found while hunting for more instances of bug 6271. Bugfix on
1132 0.0.2pre8, which introduced incremental circuit construction.
1134 o Minor features (streamlining);
1135 - No longer include the "opt" prefix when generating routerinfos
1136 or v2 directories: it has been needless since Tor 0.1.2. Closes
1138 - Remove some now-needless code that tried to aggressively flush
1139 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1140 cell queue logic has saved us from the failure mode that this code
1141 was supposed to prevent. Removing this code will limit the number
1142 of baroque control flow paths through Tor's network logic. Reported
1143 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1145 o Minor features (controller):
1146 - Add a "GETINFO signal/names" control port command. Implements
1148 - Provide default values for all options via "GETINFO config/defaults".
1149 Implements ticket 4971.
1151 o Minor features (IPv6):
1152 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1153 authorities should set if they have IPv6 connectivity and want to
1154 do reachability tests for IPv6 relays. Implements feature 5974.
1155 - A relay with an IPv6 OR port now sends that address in NETINFO
1156 cells (in addition to its other address). Implements ticket 6364.
1158 o Minor features (log messages):
1159 - Omit the first heartbeat log message, because it never has anything
1160 useful to say, and it clutters up the bootstrapping messages.
1161 Resolves ticket 6758.
1162 - Don't log about reloading the microdescriptor cache at startup. Our
1163 bootstrap warnings are supposed to tell the user when there's a
1164 problem, and our bootstrap notices say when there isn't. Resolves
1165 ticket 6759; bugfix on 0.2.2.6-alpha.
1166 - Don't log "I learned some more directory information" when we're
1167 reading cached directory information. Reserve it for when new
1168 directory information arrives in response to a fetch. Resolves
1170 - Prevent rounding error in path bias counts when scaling
1171 them down, and use the correct scale factor default. Also demote
1172 some path bias related log messages down a level and make others
1173 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1174 - We no longer warn so much when generating manpages from their
1177 o Code simplifications and refactoring:
1178 - Enhance our internal sscanf replacement so that we can eliminate
1179 the last remaining uses of the system sscanf. (Though those uses
1180 of sscanf were safe, sscanf itself is generally error prone, so
1181 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1183 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1184 - Move last_reachable and testing_since from routerinfo_t to node_t.
1185 Implements ticket 5529.
1186 - Add replaycache_t structure, functions and unit tests, then refactor
1187 rend_service_introduce() to be more clear to read, improve, debug,
1188 and test. Resolves bug 6177.
1189 - Finally remove support for malloc_good_size and malloc_usable_size.
1190 We had hoped that these functions would let us eke a little more
1191 memory out of our malloc implementation. Unfortunately, the only
1192 implementations that provided these functions are also ones that
1193 are already efficient about not overallocation: they never got us
1194 more than 7 or so bytes per allocation. Removing them saves us a
1195 little code complexity and a nontrivial amount of build complexity.
1198 - Tor maintainers now require Automake version 1.9 or later to build
1199 Tor from the Git repository. (Automake is not required when building
1200 from a source distribution.)
1203 Changes in version 0.2.3.21-rc - 2012-09-05
1204 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1205 series. It fixes a trio of potential security bugs, fixes a bug where
1206 we were leaving some of the fast relays out of the microdescriptor
1207 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1208 and cleans up other smaller issues.
1210 o Major bugfixes (security):
1211 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1212 could use this trick to make their circuits receive cells faster
1213 than our flow control would have allowed, or to gum up the network,
1214 or possibly to do targeted memory denial-of-service attacks on
1215 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1216 from July 2002, before the release of Tor 0.0.0. We had committed
1217 this patch previously, but we had to revert it because of bug 6271.
1218 Now that 6271 is fixed, this patch appears to work.
1219 - Reject any attempt to extend to an internal address. Without
1220 this fix, a router could be used to probe addresses on an internal
1221 network to see whether they were accepting connections. Fixes bug
1222 6710; bugfix on 0.0.8pre1.
1223 - Do not crash when comparing an address with port value 0 to an
1224 address policy. This bug could have been used to cause a remote
1225 assertion failure by or against directory authorities, or to
1226 allow some applications to crash clients. Fixes bug 6690; bugfix
1230 - Remove the upper bound on microdescriptor length. We were hitting
1231 the limit for routers with complex exit policies or family
1232 declarations, causing clients to not use them. Fixes the first
1233 piece of bug 6404; fix on 0.2.2.6-alpha.
1234 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1235 as a relay. Previously, some of our code would treat the presence
1236 of any ORPort line as meaning that we should act like a relay,
1237 even though our new listener code would correctly not open any
1238 ORPorts for ORPort 0. Similar bugs in other Port options are also
1239 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1242 - Avoid a pair of double-free and use-after-mark bugs that can
1243 occur with certain timings in canceled and re-received DNS
1244 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1245 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1246 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1247 - Allow one-hop directory fetching circuits the full "circuit build
1248 timeout" period, rather than just half of it, before failing them
1249 and marking the relay down. This fix should help reduce cases where
1250 clients declare relays (or worse, bridges) unreachable because
1251 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1252 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1254 - Authorities no longer include any router in their microdescriptor
1255 consensuses for which they couldn't generate or agree on a
1256 microdescriptor. Fixes the second piece of bug 6404; fix on
1258 - Detect and reject attempts to specify both "FooPort" and
1259 "FooPort 0" in the same configuration domain. (It's still okay
1260 to have a FooPort in your configuration file, and use "FooPort 0"
1261 on the command line to disable it.) Fixes the second half of bug
1262 6507; bugfix on 0.2.3.3-alpha.
1263 - Make wildcarded addresses (that is, ones beginning with "*.") work
1264 when provided via the controller's MapAddress command. Previously,
1265 they were accepted, but we never actually noticed that they were
1266 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1267 - Avoid crashing on a malformed state file where EntryGuardPathBias
1268 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1269 - Add a (probably redundant) memory clear between iterations of
1270 the router status voting loop, to prevent future coding errors
1271 where data might leak between iterations of the loop. Resolves
1274 o Minor bugfixes (log messages):
1275 - Downgrade "set buildtimeout to low value" messages to "info"
1276 severity; they were never an actual problem, there was never
1277 anything reasonable to do about them, and they tended to spam logs
1278 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1279 - Downgrade path-bias warning messages to "info". We'll try to get
1280 them working better in 0.2.4. Add internal circuit construction
1281 state to protect against the noisy warn message "Unexpectedly high
1282 circuit_successes". Also add some additional rate-limited notice
1283 messages to help determine the root cause of the warn. Fixes bug
1284 6475. Bugfix against 0.2.3.17-beta.
1285 - Move log message when unable to find a microdesc in a routerstatus
1286 entry to parse time. Previously we'd spam this warning every time
1287 we tried to figure out which microdescriptors to download. Fixes
1288 the third piece of bug 6404; fix on 0.2.3.18-rc.
1291 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1292 change when the authority is deciding whether to accept a newly
1293 uploaded descriptor. Implements ticket 6423.
1294 - Add missing documentation for consensus and microdesc files.
1295 Resolves ticket 6732.
1298 Changes in version 0.2.2.38 - 2012-08-12
1299 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1300 attack that could in theory leak path information.
1303 - Avoid an uninitialized memory read when reading a vote or consensus
1304 document that has an unrecognized flavor name. This read could
1305 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1306 - Try to leak less information about what relays a client is
1307 choosing to a side-channel attacker. Previously, a Tor client would
1308 stop iterating through the list of available relays as soon as it
1309 had chosen one, thus finishing a little earlier when it picked
1310 a router earlier in the list. If an attacker can recover this
1311 timing information (nontrivial but not proven to be impossible),
1312 they could learn some coarse-grained information about which relays
1313 a client was picking (middle nodes in particular are likelier to
1314 be affected than exits). The timing attack might be mitigated by
1315 other factors (see bug 6537 for some discussion), but it's best
1316 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1319 Changes in version 0.2.3.20-rc - 2012-08-05
1320 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1321 series. It fixes a pair of code security bugs and a potential anonymity
1322 issue, updates our RPM spec files, and cleans up other smaller issues.
1325 - Avoid read-from-freed-memory and double-free bugs that could occur
1326 when a DNS request fails while launching it. Fixes bug 6480;
1327 bugfix on 0.2.0.1-alpha.
1328 - Avoid an uninitialized memory read when reading a vote or consensus
1329 document that has an unrecognized flavor name. This read could
1330 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1331 - Try to leak less information about what relays a client is
1332 choosing to a side-channel attacker. Previously, a Tor client would
1333 stop iterating through the list of available relays as soon as it
1334 had chosen one, thus finishing a little earlier when it picked
1335 a router earlier in the list. If an attacker can recover this
1336 timing information (nontrivial but not proven to be impossible),
1337 they could learn some coarse-grained information about which relays
1338 a client was picking (middle nodes in particular are likelier to
1339 be affected than exits). The timing attack might be mitigated by
1340 other factors (see bug 6537 for some discussion), but it's best
1341 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1344 - Try to make the warning when giving an obsolete SOCKSListenAddress
1345 a little more useful.
1346 - Terminate active server managed proxies if Tor stops being a
1347 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1348 - Provide a better error message about possible OSX Asciidoc failure
1349 reasons. Fixes bug 6436.
1350 - Warn when Tor is configured to use accounting in a way that can
1351 link a hidden service to some other hidden service or public
1352 address. Resolves ticket 6490.
1355 - Check return value of fputs() when writing authority certificate
1356 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1357 - Ignore ServerTransportPlugin lines when Tor is not configured as
1358 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1359 - When disabling guards for having too high a proportion of failed
1360 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1364 - Update our default RPM spec files to work with mock and rpmbuild
1365 on RHEL/Fedora. They have an updated set of dependencies and
1366 conflicts, a fix for an ancient typo when creating the "_tor"
1367 user, and better instructions. Thanks to Ondrej Mikle for the
1368 patch series. Fixes bug 6043.
1371 - Make it possible to set the TestingTorNetwork configuration
1372 option using AlternateDirAuthority and AlternateBridgeAuthority
1373 as an alternative to setting DirServer. Addresses ticket 6377.
1376 - Clarify the documentation for the Alternate*Authority options.
1378 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1380 o Code simplification and refactoring:
1381 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1382 10 lines. Also, don't nest them. Doing so in the past has
1383 led to hard-to-debug code. The new style is to use the
1384 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1387 Changes in version 0.2.3.19-rc - 2012-07-06
1388 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1389 series. It fixes the compile on Windows, reverts to a GeoIP database
1390 that isn't as broken, and fixes a flow control bug that has been around
1391 since the beginning of Tor.
1394 - Fix a bug handling SENDME cells on nonexistent streams that could
1395 result in bizarre window values. Report and patch contributed
1396 pseudonymously. Fixes part of bug 6271. This bug was introduced
1397 before the first Tor release, in svn commit r152.
1398 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1399 June 2012 database, Maxmind marked many Tor relays as country "A1",
1400 which will cause risky behavior for clients that set EntryNodes
1401 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1402 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1403 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1406 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1407 bugfix on 0.2.1.10-alpha.
1410 Changes in version 0.2.3.18-rc - 2012-06-28
1411 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1412 series. It fixes a few smaller bugs, but generally appears stable.
1413 Please test it and let us know whether it is!
1416 - Allow wildcarded mapaddress targets to be specified on the
1417 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1418 - Make our linker option detection code more robust against linkers
1419 such as on FreeBSD 8, where a bad combination of options completes
1420 successfully but makes an unrunnable binary. Fixes bug 6173;
1421 bugfix on 0.2.3.17-beta.
1423 o Minor bugfixes (on 0.2.2.x and earlier):
1424 - Avoid a false positive in the util/threads unit test by increasing
1425 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1426 - Replace "Sending publish request" log messages with "Launching
1427 upload", so that they no longer confusingly imply that we're
1428 sending something to a directory we might not even be connected
1429 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1430 - Make sure to set *socket_error in all error cases in
1431 connection_connect(), so it can't produce a warning about
1432 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1433 0.2.1.1-alpha; resolves ticket 6028.
1434 - Downgrade "Got a certificate, but we already have it" log messages
1435 from warning to info, except when we're a dirauth. Fixes bug 5238;
1436 bugfix on 0.2.1.7-alpha.
1437 - When checking for requested signatures on the latest consensus
1438 before serving it to a client, make sure to check the right
1439 consensus flavor. Bugfix on 0.2.2.6-alpha.
1440 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1441 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1443 o Minor bugfixes (on 0.2.3.x):
1444 - Make format_helper_exit_status() avoid unnecessary space padding
1445 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1447 - Downgrade a message about cleaning the microdescriptor cache to
1448 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1449 - Log a BUG message at severity INFO if we have a networkstatus with
1450 a missing entry for some microdescriptor. Continues on a patch
1452 - Improve the log message when a managed proxy fails to launch. Fixes
1453 bug 5099; bugfix on 0.2.3.6-alpha.
1454 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1455 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1456 - When formatting wildcarded address mappings for the controller,
1457 be sure to include "*." as appropriate. Partially fixes bug 6244;
1458 bugfix on 0.2.3.9-alpha.
1459 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1460 Bugfix on 0.2.3.13-alpha.
1461 - Stop logging messages about running with circuit timeout learning
1462 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1463 - Disable a spurious warning about reading on a marked and flushing
1464 connection. We shouldn't be doing that, but apparently we
1465 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1466 - Fix a bug that stopped AllowDotExit from working on addresses
1467 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1470 o Code simplification, refactoring, unit tests:
1471 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1472 Libevent's notion of cached time when possible.
1473 - Remove duplicate code for invoking getrlimit() from control.c.
1474 - Add a unit test for the environment_variable_names_equal function.
1477 - Document the --defaults-torrc option, and the new (in 0.2.3)
1478 semantics for overriding, extending, and clearing lists of
1479 options. Closes bug 4748.
1482 Changes in version 0.2.3.17-beta - 2012-06-15
1483 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1484 gets our TLS handshake back on track for being able to blend in with
1485 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1486 with Vidalia, and otherwise continues to get us closer to a release
1490 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1491 - Update TLS cipher list to match Firefox 8 and later. Resolves
1493 - Implement the client side of proposal 198: remove support for
1494 clients falsely claiming to support standard ciphersuites that
1495 they can actually provide. As of modern OpenSSL versions, it's not
1496 necessary to fake any standard ciphersuite, and doing so prevents
1497 us from using better ciphersuites in the future, since servers
1498 can't know whether an advertised ciphersuite is really supported or
1499 not. Some hosts -- notably, ones with very old versions of OpenSSL
1500 or where OpenSSL has been built with ECC disabled -- will stand
1501 out because of this change; TBB users should not be affected.
1504 - Change the default value for DynamicDHGroups (introduced in
1505 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1506 identifiable by their use of the mod_ssl DH group, but at
1507 the cost of some usability (#4721) and bridge tracing (#6087)
1508 regressions. Resolves ticket 5598.
1509 - Send a CRLF at the end of each STATUS_* control protocol event. This
1510 bug tickled a bug in Vidalia which would make it freeze. Fixes
1511 bug 6094; bugfix on 0.2.3.16-alpha.
1514 - Disable writing on marked-for-close connections when they are
1515 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1516 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1517 case for flushing marked connections.
1518 - Detect SSL handshake even when the initial attempt to write the
1519 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1520 - Change the AllowDotExit rules so they should actually work.
1521 We now enforce AllowDotExit only immediately after receiving an
1522 address via SOCKS or DNSPort: other sources are free to provide
1523 .exit addresses after the resolution occurs. Fixes bug 3940;
1524 bugfix on 0.2.2.1-alpha.
1525 - Fix a (harmless) integer overflow in cell statistics reported by
1526 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1527 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
1528 right places and never depends on the consensus parameters or
1529 computes adaptive timeouts when it is disabled. Fixes bug 5049;
1530 bugfix on 0.2.2.14-alpha.
1531 - When building Tor on Windows with -DUNICODE (not default), ensure
1532 that error messages, filenames, and DNS server names are always
1533 NUL-terminated when we convert them to a single-byte encoding.
1534 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1535 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1536 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1537 - Fix an edge case where TestingTorNetwork is set but the authorities
1538 and relays all have an uptime of zero, where the private Tor network
1539 could briefly lack support for hidden services. Fixes bug 3886;
1540 bugfix on 0.2.2.18-alpha.
1541 - Correct the manpage's descriptions for the default values of
1542 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
1544 - Fix the documentation for the --hush and --quiet command line
1545 options, which changed their behavior back in 0.2.3.3-alpha.
1546 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
1550 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1551 more information to it, so that we can track it down in case it
1552 returns again. Mitigates bug 5235.
1553 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
1554 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
1555 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
1556 - Warn the user when HTTPProxy, but no other proxy type, is
1557 configured. This can cause surprising behavior: it doesn't send
1558 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1559 directory traffic only. Resolves ticket 4663.
1560 - Issue a notice if a guard completes less than 40% of your circuits.
1561 Threshold is configurable by torrc option PathBiasNoticeRate and
1562 consensus parameter pb_noticepct. There is additional, off-by-
1563 default code to disable guards which fail too many circuits.
1564 Addresses ticket 5458.
1565 - Update to the June 6 2012 Maxmind GeoLite Country database.
1567 o Code simplifications and refactoring:
1568 - Remove validate_pluggable_transports_config(): its warning
1569 message is now handled by connection_or_connect().
1572 Changes in version 0.2.2.37 - 2012-06-06
1573 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
1574 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1578 - Work around a bug in OpenSSL that broke renegotiation with TLS
1579 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1580 the v2 Tor connection protocol when both sides were using OpenSSL
1581 1.0.1 would fail. Resolves ticket 6033.
1582 - When waiting for a client to renegotiate, don't allow it to add
1583 any bytes to the input buffer. This fixes a potential DoS issue.
1584 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1585 - Fix an edge case where if we fetch or publish a hidden service
1586 descriptor, we might build a 4-hop circuit and then use that circuit
1587 for exiting afterwards -- even if the new last hop doesn't obey our
1588 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1591 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1592 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1595 - Tell GCC and Clang to check for any errors in format strings passed
1596 to the tor_v*(print|scan)f functions.
1599 Changes in version 0.2.3.16-alpha - 2012-06-05
1600 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
1601 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1602 currently). It also fixes a variety of smaller bugs and other cleanups
1603 that get us closer to a release candidate.
1605 o Major bugfixes (general):
1606 - Work around a bug in OpenSSL that broke renegotiation with TLS
1607 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1608 the v2 Tor connection protocol when both sides were using OpenSSL
1609 1.0.1 would fail. Resolves ticket 6033.
1610 - When waiting for a client to renegotiate, don't allow it to add
1611 any bytes to the input buffer. This fixes a potential DoS issue.
1612 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1613 - Pass correct OR address to managed proxies (like obfsproxy),
1614 even when ORListenAddress is used. Fixes bug 4865; bugfix on
1616 - The advertised platform of a router now includes only its operating
1617 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
1618 service pack level (for Windows) or its CPU architecture (for Unix).
1619 We also no longer include the "git-XYZ" tag in the version. Resolves
1622 o Major bugfixes (clients):
1623 - If we are unable to find any exit that supports our predicted ports,
1624 stop calling them predicted, so that we don't loop and build
1625 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1626 which introduced predicted ports.
1627 - Fix an edge case where if we fetch or publish a hidden service
1628 descriptor, we might build a 4-hop circuit and then use that circuit
1629 for exiting afterwards -- even if the new last hop doesn't obey our
1630 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1631 - Check at each new consensus whether our entry guards were picked
1632 long enough ago that we should rotate them. Previously, we only
1633 did this check at startup, which could lead to us holding a guard
1634 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1635 - When fetching a bridge descriptor from a bridge authority,
1636 always do so anonymously, whether we have been able to open
1637 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1638 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1639 but we'll need to wait for bug 6010 before it's actually usable.
1641 o Major bugfixes (directory authorities):
1642 - When computing weight parameters, behave more robustly in the
1643 presence of a bad bwweightscale value. Previously, the authorities
1644 would crash if they agreed on a sufficiently broken weight_scale
1645 value: now, they use a reasonable default and carry on. Partial
1646 fix for 5786; bugfix on 0.2.2.17-alpha.
1647 - Check more thoroughly to prevent a rogue authority from
1648 double-voting on any consensus directory parameter. Previously,
1649 authorities would crash in this case if the total number of
1650 votes for any parameter exceeded the number of active voters,
1651 but would let it pass otherwise. Partial fix for bug 5786; bugfix
1655 - Rate-limit log messages when asked to connect anonymously to
1656 a private address. When these hit, they tended to hit fast and
1657 often. Also, don't bother trying to connect to addresses that we
1658 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1659 reply makes us think we have been lied to, even when the address the
1660 client tried to connect to was "localhost." Resolves ticket 2822.
1661 - Allow packagers to insert an extra string in server descriptor
1662 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
1663 Resolves the rest of ticket 2988.
1664 - Raise the threshold of server descriptors needed (75%) and exit
1665 server descriptors needed (50%) before we will declare ourselves
1666 bootstrapped. This will make clients start building circuits a
1667 little later, but makes the initially constructed circuits less
1668 skewed and less in conflict with further directory fetches. Fixes
1670 - Close any connection that sends unrecognized junk before the
1671 handshake. Solves an issue noted in bug 4369.
1672 - Improve log messages about managed transports. Resolves ticket 5070.
1673 - Tag a bridge's descriptor as "never to be sent unencrypted".
1674 This shouldn't matter, since bridges don't open non-anonymous
1675 connections to the bridge authority and don't allow unencrypted
1676 directory connections from clients, but we might as well make
1677 sure. Closes bug 5139.
1678 - Expose our view of whether we have gone dormant to the controller,
1679 via a new "GETINFO dormant" value. Torbutton and other controllers
1680 can use this to avoid doing periodic requests through Tor while
1681 it's dormant (bug 4718). Fixes bug 5954.
1682 - Tell GCC and Clang to check for any errors in format strings passed
1683 to the tor_v*(print|scan)f functions.
1684 - Update to the May 1 2012 Maxmind GeoLite Country database.
1686 o Minor bugfixes (already included in 0.2.2.36):
1687 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1688 Fixes bug 5346; bugfix on 0.0.8pre3.
1689 - Correct parsing of certain date types in parse_http_time().
1690 Without this patch, If-Modified-Since would behave
1691 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1692 Esteban Manchado Velázques.
1693 - Make our number-parsing functions always treat too-large values
1694 as an error, even when those values exceed the width of the
1695 underlying type. Previously, if the caller provided these
1696 functions with minima or maxima set to the extreme values of the
1697 underlying integer type, these functions would return those
1698 values on overflow rather than treating overflow as an error.
1699 Fixes part of bug 5786; bugfix on 0.0.9.
1700 - If we hit the error case where routerlist_insert() replaces an
1701 existing (old) server descriptor, make sure to remove that
1702 server descriptor from the old_routers list. Fix related to bug
1703 1776. Bugfix on 0.2.2.18-alpha.
1704 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1705 circuits. Fixes issue 5259.
1707 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
1708 - Prevent a null-pointer dereference when receiving a data cell
1709 for a nonexistent stream when the circuit in question has an
1710 empty deliver window. We don't believe this is triggerable,
1711 since we don't currently allow deliver windows to become empty,
1712 but the logic is tricky enough that it's better to make the code
1713 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1714 - Fix a memory leak when trying to launch a DNS request when the
1715 network is disabled or the nameservers are unconfigurable. Fixes
1716 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
1717 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
1718 - Don't hold a Windows file handle open for every file mapping;
1719 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1721 - Avoid O(n^2) performance characteristics when parsing a large
1722 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1723 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1724 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1726 - Make our replacement implementation of strtok_r() compatible with
1727 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1728 bugfix on 0.2.2.1-alpha.
1729 - Fix a NULL-pointer dereference on a badly formed
1730 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
1731 bugfix on 0.2.2.9-alpha.
1732 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1733 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1734 - Defensively refactor rend_mid_rendezvous() so that protocol
1735 violations and length checks happen in the beginning. Fixes
1737 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1738 that IPv6 stuff will compile on MSVC, and compilation issues
1739 will be easier to track down. Fixes bug 5861.
1741 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
1742 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1743 resource exhaustion, so that clients can adjust their load to
1744 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1745 started using END_STREAM_REASON_RESOURCELIMIT.
1746 - Don't check for whether the address we're using for outbound
1747 connections has changed until after the outbound connection has
1748 completed. On Windows, getsockname() doesn't succeed until the
1749 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1750 - If the configuration tries to set MyFamily on a bridge, refuse to
1751 do so, and warn about the security implications. Fixes bug 4657;
1752 bugfix on 0.2.0.3-alpha.
1753 - If the client fails to set a reasonable set of ciphersuites
1754 during its v2 handshake renegotiation, allow the renegotiation to
1755 continue nevertheless (i.e. send all the required certificates).
1756 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1757 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1758 option is set to 0 (which Vidalia version 0.2.16 now does when
1759 a SAVECONF attempt fails), perform other actions that SIGHUP
1760 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1762 - If we fail to write a microdescriptor to the disk cache, do not
1763 continue replacing the old microdescriptor file. Fixes bug 2954;
1764 bugfix on 0.2.2.6-alpha.
1765 - Exit nodes don't need to fetch certificates for authorities that
1766 they don't recognize; only directory authorities, bridges,
1767 and caches need to do that. Fixes part of bug 2297; bugfix on
1769 - Correctly handle checking the permissions on the parent
1770 directory of a control socket in the root directory. Bug found
1771 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
1773 - When told to add a bridge with the same digest as a preexisting
1774 bridge but a different addr:port, change the addr:port as
1775 requested. Previously we would not notice the change. Fixes half
1776 of bug 5603; fix on 0.2.2.26-beta.
1777 - End AUTHCHALLENGE error messages (in the control protocol) with
1778 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
1780 o Minor bugfixes (on 0.2.3.x):
1781 - Turn an assertion (that the number of handshakes received as a
1782 server is not < 1) into a warning. Fixes bug 4873; bugfix on
1784 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
1785 we had reversed them when the answer was cached.) Fixes bug
1786 5723; bugfix on 0.2.3.1-alpha.
1787 - Work correctly on Linux systems with accept4 support advertised in
1788 their headers, but without accept4 support in the kernel. Fix
1789 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
1790 - When told to add a bridge with the same addr:port as a preexisting
1791 bridge but a different transport, change the transport as
1792 requested. Previously we would not notice the change. Fixes half
1793 of bug 5603; fix on 0.2.3.2-alpha.
1794 - Avoid a "double-reply" warning when replying to a SOCKS request
1795 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
1796 bugfix on 0.2.3.4-alpha.
1797 - Fix a bug where a bridge authority crashes if it has seen no
1798 directory requests when it's time to write statistics to disk.
1799 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
1801 - Don't try to open non-control listeners when DisableNetwork is set.
1802 Previously, we'd open all listeners, then immediately close them.
1803 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
1804 - Don't abort the managed proxy protocol if the managed proxy
1805 sends us an unrecognized line; ignore it instead. Fixes bug
1806 5910; bugfix on 0.2.3.9-alpha.
1807 - Fix a compile warning in crypto.c when compiling with clang 3.1.
1808 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
1809 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
1810 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
1811 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
1812 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
1813 - Resolve numerous small warnings and build issues with MSVC. Resolves
1816 o Documentation fixes:
1817 - Improve the manual's documentation for the NT Service command-line
1818 options. Addresses ticket 3964.
1819 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
1820 - Document the changes to the ORPort and DirPort options, and the
1821 fact that {OR/Dir}ListenAddress is now unnecessary (and
1822 therefore deprecated). Resolves ticket 5597.
1825 - Remove the torrc.bridge file: we don't use it for anything, and
1826 it had become badly desynchronized from torrc.sample. Resolves
1830 Changes in version 0.2.2.36 - 2012-05-24
1831 Tor 0.2.2.36 updates the addresses for two of the eight directory
1832 authorities, fixes some potential anonymity and security issues,
1833 and fixes several crash bugs.
1835 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
1836 known flaws, and nobody should be using them. You should upgrade. If
1837 you're using a Linux or BSD and its packages are obsolete, stop using
1838 those packages and upgrade anyway.
1840 o Directory authority changes:
1841 - Change IP address for maatuska (v3 directory authority).
1842 - Change IP address for ides (v3 directory authority), and rename
1846 - When building or running with any version of OpenSSL earlier
1847 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1848 versions have a bug (CVE-2011-4576) in which their block cipher
1849 padding includes uninitialized data, potentially leaking sensitive
1850 information to any peer with whom they make a SSLv3 connection. Tor
1851 does not use SSL v3 by default, but a hostile client or server
1852 could force an SSLv3 connection in order to gain information that
1853 they shouldn't have been able to get. The best solution here is to
1854 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1855 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1856 to make sure that the bug can't happen.
1857 - Never use a bridge or a controller-supplied node as an exit, even
1858 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1859 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1860 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1861 - Only build circuits if we have a sufficient threshold of the total
1862 descriptors that are marked in the consensus with the "Exit"
1863 flag. This mitigates an attack proposed by wanoskarnet, in which
1864 all of a client's bridges collude to restrict the exit nodes that
1865 the client knows about. Fixes bug 5343.
1866 - Provide controllers with a safer way to implement the cookie
1867 authentication mechanism. With the old method, if another locally
1868 running program could convince a controller that it was the Tor
1869 process, then that program could trick the controller into telling
1870 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1871 authentication method uses a challenge-response approach to prevent
1872 this attack. Fixes bug 5185; implements proposal 193.
1875 - Avoid logging uninitialized data when unable to decode a hidden
1876 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1877 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1878 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1880 - Fix builds when the path to sed, openssl, or sha1sum contains
1881 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1883 - Correct our replacements for the timeradd() and timersub() functions
1884 on platforms that lack them (for example, Windows). The timersub()
1885 function is used when expiring circuits, while timeradd() is
1886 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1887 bugfix on 0.2.2.24-alpha.
1888 - Fix the SOCKET_OK test that we use to tell when socket
1889 creation fails so that it works on Win64. Fixes part of bug 4533;
1890 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1893 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1894 Fixes bug 5346; bugfix on 0.0.8pre3.
1895 - Make our number-parsing functions always treat too-large values
1896 as an error, even when those values exceed the width of the
1897 underlying type. Previously, if the caller provided these
1898 functions with minima or maxima set to the extreme values of the
1899 underlying integer type, these functions would return those
1900 values on overflow rather than treating overflow as an error.
1901 Fixes part of bug 5786; bugfix on 0.0.9.
1902 - Older Linux kernels erroneously respond to strange nmap behavior
1903 by having accept() return successfully with a zero-length
1904 socket. When this happens, just close the connection. Previously,
1905 we would try harder to learn the remote address: but there was
1906 no such remote address to learn, and our method for trying to
1907 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1908 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1909 - Correct parsing of certain date types in parse_http_time().
1910 Without this patch, If-Modified-Since would behave
1911 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1912 Esteban Manchado Velázques.
1913 - Change the BridgePassword feature (part of the "bridge community"
1914 design, which is not yet implemented) to use a time-independent
1915 comparison. The old behavior might have allowed an adversary
1916 to use timing to guess the BridgePassword value. Fixes bug 5543;
1917 bugfix on 0.2.0.14-alpha.
1918 - Detect and reject certain misformed escape sequences in
1919 configuration values. Previously, these values would cause us
1920 to crash if received in a torrc file or over an authenticated
1921 control port. Bug found by Esteban Manchado Velázquez, and
1922 independently by Robert Connolly from Matta Consulting who further
1923 noted that it allows a post-authentication heap overflow. Patch
1924 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1925 bugfix on 0.2.0.16-alpha.
1926 - Fix a compile warning when using the --enable-openbsd-malloc
1927 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1928 - During configure, detect when we're building with clang version
1929 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1930 CFLAGS. clang doesn't support them yet.
1931 - When sending an HTTP/1.1 proxy request, include a Host header.
1932 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1933 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
1934 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
1935 - If we hit the error case where routerlist_insert() replaces an
1936 existing (old) server descriptor, make sure to remove that
1937 server descriptor from the old_routers list. Fix related to bug
1938 1776. Bugfix on 0.2.2.18-alpha.
1940 o Minor bugfixes (documentation and log messages):
1941 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1942 Fixes bug 4856; bugfix on Tor 0.0.6.
1943 - Update "ClientOnly" man page entry to explain that there isn't
1944 really any point to messing with it. Resolves ticket 5005.
1945 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1946 directory authority option (introduced in Tor 0.2.2.34).
1947 - Downgrade the "We're missing a certificate" message from notice
1948 to info: people kept mistaking it for a real problem, whereas it
1949 is seldom the problem even when we are failing to bootstrap. Fixes
1950 bug 5067; bugfix on 0.2.0.10-alpha.
1951 - Correctly spell "connect" in a log message on failure to create a
1952 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
1953 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1954 circuits. Fixes issue 5259.
1957 - Directory authorities now reject versions of Tor older than
1958 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1959 inclusive. These versions accounted for only a small fraction of
1960 the Tor network, and have numerous known security issues. Resolves
1962 - Update to the May 1 2012 Maxmind GeoLite Country database.
1965 - When sending or relaying a RELAY_EARLY cell, we used to convert
1966 it to a RELAY cell if the connection was using the v1 link
1967 protocol. This was a workaround for older versions of Tor, which
1968 didn't handle RELAY_EARLY cells properly. Now that all supported
1969 versions can handle RELAY_EARLY cells, and now that we're enforcing
1970 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1971 remove this workaround. Addresses bug 4786.
1974 Changes in version 0.2.3.15-alpha - 2012-04-30
1975 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
1976 the development branch build on Windows again.
1978 o Minor bugfixes (on 0.2.2.x and earlier):
1979 - Make sure that there are no unhandled pending TLS errors before
1980 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1981 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1982 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1983 - Fix an assert that directory authorities could trigger on sighup
1984 during some configuration state transitions. We now don't treat
1985 it as a fatal error when the new descriptor we just generated in
1986 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1987 - After we pick a directory mirror, we would refuse to use it if
1988 it's in our ExcludeExitNodes list, resulting in mysterious failures
1989 to bootstrap for people who just wanted to avoid exiting from
1990 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1991 - When building with --enable-static-tor on OpenBSD, do not
1992 erroneously attempt to link -lrt. Fixes bug 5103.
1994 o Minor bugfixes (on 0.2.3.x):
1995 - When Tor is built with kernel headers from a recent (last few
1996 years) Linux kernel, do not fail to run on older (pre-2.6.28
1997 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
1998 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2000 - Fix compilation with miniupnpc version 1.6; patch from
2001 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2002 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2003 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2004 - Fix compilation on platforms without unistd.h, or where environ
2005 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2008 - Directory authorities are now a little more lenient at accepting
2009 older router descriptors, or newer router descriptors that don't
2010 make big changes. This should help ameliorate past and future
2011 issues where routers think they have uploaded valid descriptors,
2012 but the authorities don't think so. Fix for ticket 2479.
2013 - Make the code that clients use to detect an address change be
2014 IPv6-aware, so that it won't fill clients' logs with error
2015 messages when trying to get the IPv4 address of an IPv6
2016 connection. Implements ticket 5537.
2019 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2020 authorities needed to use it for a while to keep the network working
2021 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2022 that was six months ago. As of now, it should no longer be needed
2026 Changes in version 0.2.3.14-alpha - 2012-04-23
2027 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2028 candidate. It also dramatically speeds up AES: fast relays should
2029 consider switching to the newer OpenSSL library.
2031 o Directory authority changes:
2032 - Change IP address for ides (v3 directory authority), and rename
2036 - Avoid logging uninitialized data when unable to decode a hidden
2037 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2038 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2039 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2041 - If authorities are unable to get a v2 consensus document from other
2042 directory authorities, they no longer fall back to fetching
2043 them from regular directory caches. Fixes bug 5635; bugfix on
2044 0.2.2.26-beta, where routers stopped downloading v2 consensus
2046 - When we start a Tor client with a normal consensus already cached,
2047 be willing to download a microdescriptor consensus. Fixes bug 4011;
2048 fix on 0.2.3.1-alpha.
2050 o Major features (performance):
2051 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2052 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2053 vectorized AES implementations as appropriate. These can be much,
2054 much faster than other AES implementations.
2056 o Minor bugfixes (0.2.2.x and earlier):
2057 - Don't launch more than 10 service-side introduction-point circuits
2058 for a hidden service in five minutes. Previously, we would consider
2059 launching more introduction-point circuits if at least one second
2060 had passed without any introduction-point circuits failing. Fixes
2061 bug 4607; bugfix on 0.0.7pre1.
2062 - Change the BridgePassword feature (part of the "bridge community"
2063 design, which is not yet implemented) to use a time-independent
2064 comparison. The old behavior might have allowed an adversary
2065 to use timing to guess the BridgePassword value. Fixes bug 5543;
2066 bugfix on 0.2.0.14-alpha.
2067 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2068 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2069 - When sending an HTTP/1.1 proxy request, include a Host header.
2070 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2071 - Don't log that we have "decided to publish new relay descriptor"
2072 unless we are actually publishing a descriptor. Fixes bug 3942;
2073 bugfix on 0.2.2.28-beta.
2075 o Minor bugfixes (0.2.3.x):
2076 - Fix a bug where a bridge authority crashes (on a failed assert)
2077 if it has seen no directory requests when it's time to write
2078 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2079 - Fix bug stomping on ORPort option NoListen and ignoring option
2080 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2081 - In the testsuite, provide a large enough buffer in the tor_sscanf
2082 unit test. Otherwise we'd overrun that buffer and crash during
2083 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2085 - Make sure we create the keys directory if it doesn't exist and we're
2086 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2087 5572; bugfix on 0.2.3.13-alpha.
2088 - Fix a small memory leak when trying to decode incorrect base16
2089 authenticator during SAFECOOKIE authentication. Found by
2090 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2093 - Add more information to a log statement that might help track down
2094 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2095 non-IP address" messages (or any Bug messages, for that matter!),
2096 please let us know about it.
2097 - Relays now understand an IPv6 address when they get one from a
2098 directory server. Resolves ticket 4875.
2099 - Resolve IPv6 addresses in bridge and entry statistics to country
2100 code "??" which means we at least count them. Resolves ticket 5053;
2101 improves on 0.2.3.9-alpha.
2102 - Update to the April 3 2012 Maxmind GeoLite Country database.
2103 - Begin a doc/state-contents.txt file to explain the contents of
2104 the Tor state file. Fixes bug 2987.
2106 o Default torrc changes:
2107 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2108 port on 9050 by default anyway, so this should not change anything
2110 - Stop mentioning the deprecated *ListenAddress options in
2111 torrc.sample. Fixes bug 5438.
2112 - Document unit of bandwidth related options in sample torrc.
2116 - The "torify" script no longer supports the "tsocks" socksifier
2117 tool, since tsocks doesn't support DNS and UDP right for Tor.
2118 Everyone should be using torsocks instead. Fixes bugs 3530 and
2119 5180. Based on a patch by "ugh".
2122 - Change the symmetric cipher interface so that creating and
2123 initializing a stream cipher are no longer separate functions.
2124 - Remove all internal support for unpadded RSA. We never used it, and
2125 it would be a bad idea to start.
2128 Changes in version 0.2.3.13-alpha - 2012-03-26
2129 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2130 in managed pluggable transports, as well as providing other cleanups
2131 that get us closer to a release candidate.
2133 o Directory authority changes:
2134 - Change IP address for maatuska (v3 directory authority).
2137 - Provide controllers with a safer way to implement the cookie
2138 authentication mechanism. With the old method, if another locally
2139 running program could convince a controller that it was the Tor
2140 process, then that program could trick the controller into telling
2141 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2142 authentication method uses a challenge-response approach to prevent
2143 this attack. Fixes bug 5185, implements proposal 193.
2144 - Never use a bridge or a controller-supplied node as an exit, even
2145 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2146 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2147 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2148 - Only build circuits if we have a sufficient threshold of the total
2149 descriptors that are marked in the consensus with the "Exit"
2150 flag. This mitigates an attack proposed by wanoskarnet, in which
2151 all of a client's bridges collude to restrict the exit nodes that
2152 the client knows about. Fixes bug 5343.
2154 o Major bugfixes (on Tor 0.2.3.x):
2155 - Avoid an assert when managed proxies like obfsproxy are configured,
2156 and we receive HUP signals or setconf attempts too rapidly. This
2157 situation happens most commonly when Vidalia tries to attach to
2158 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2159 bugfix on 0.2.3.6-alpha.
2160 - Fix a relay-side pluggable transports bug where managed proxies were
2161 unreachable from the Internet, because Tor asked them to bind on
2162 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2163 - Stop discarding command-line arguments when TestingTorNetwork
2164 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2165 0.2.3.9-alpha, where task 4552 added support for two layers of
2167 - Resume allowing the unit tests to run in gdb. This was accidentally
2168 made impossible when the DisableDebuggerAttachment option was
2169 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2170 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2171 0.2.3.11-alpha. Reported by Anthony G. Basile.
2173 o Minor bugfixes (on 0.2.2.x and earlier):
2174 - Ensure we don't cannibalize circuits that are longer than three hops
2175 already, so we don't end up making circuits with 5 or more
2176 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2177 0.1.0.1-rc which introduced cannibalization.
2178 - Detect and reject certain misformed escape sequences in
2179 configuration values. Previously, these values would cause us
2180 to crash if received in a torrc file or over an authenticated
2181 control port. Bug found by Esteban Manchado Velázquez, and
2182 independently by Robert Connolly from Matta Consulting who further
2183 noted that it allows a post-authentication heap overflow. Patch
2184 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2185 bugfix on 0.2.0.16-alpha.
2186 - Fix a compile warning when using the --enable-openbsd-malloc
2187 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2188 - Directory caches no longer refuse to clean out descriptors because
2189 of missing v2 networkstatus documents, unless they're configured
2190 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2191 0.2.2.26-beta. Patch by Daniel Bryg.
2192 - Update to the latest version of the tinytest unit testing framework.
2193 This includes a couple of bugfixes that can be relevant for
2194 running forked unit tests on Windows, and removes all reserved
2197 o Minor bugfixes (on 0.2.3.x):
2198 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2199 4296; bugfix on 0.2.3.1-alpha.
2200 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2201 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2202 on 0.2.3.6-alpha. Patch by "frosty".
2203 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2204 option, so that the IP stack doesn't decide to use it for IPv4
2205 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2206 - Ensure that variables set in Tor's environment cannot override
2207 environment variables that Tor passes to a managed
2208 pluggable-transport proxy. Previously, Tor would pass every
2209 variable in its environment to managed proxies along with the new
2210 ones, in such a way that on many operating systems, the inherited
2211 environment variables would override those which Tor tried to
2212 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2213 bugfix on 0.2.3.9-alpha for Windows.
2216 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2217 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2218 - Update to the March 6 2012 Maxmind GeoLite Country database.
2221 Changes in version 0.2.3.12-alpha - 2012-02-13
2222 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2223 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2224 when Tor is configured to use a pluggable transport like obfsproxy.
2227 - Fix builds when the path to sed, openssl, or sha1sum contains
2228 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2230 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2231 connections. This change should allow busy exit relays to stop
2232 running out of available sockets as quickly. Fixes bug 4950;
2233 bugfix on 0.2.2.26-beta.
2234 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2235 would ask the bridge for microdescriptors, which are only supported
2236 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2237 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2238 - Properly set up obfsproxy's environment when in managed mode. The
2239 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2240 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2241 5076 and 5082; bugfix on 0.2.3.6-alpha.
2244 - Use the dead_strip option when building Tor on OS X. This reduces
2245 binary size by almost 19% when linking openssl and libevent
2246 statically, which we do for Tor Browser Bundle.
2247 - Fix broken URLs in the sample torrc file, and tell readers about
2248 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2249 PublishServerDescriptor options. Addresses bug 4652.
2250 - Update to the February 7 2012 Maxmind GeoLite Country database.
2253 - Downgrade the "We're missing a certificate" message from notice
2254 to info: people kept mistaking it for a real problem, whereas it
2255 is seldom the problem even when we are failing to bootstrap. Fixes
2256 bug 5067; bugfix on 0.2.0.10-alpha.
2257 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2258 managed pluggable transport server proxy's environment.
2259 Previously, we would put it there, even though Tor doesn't
2260 implement an 'extended server port' yet, and even though Tor
2261 almost certainly isn't listening at that address. For now, we set
2262 it to an empty string to avoid crashing older obfsproxies. Bugfix
2264 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2265 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2266 0.2.3.1-alpha. Bug reported by Scott Bennett.
2267 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2268 bugfix on 0.2.3.11-alpha.
2269 - Update "ClientOnly" man page entry to explain that there isn't
2270 really any point to messing with it. Resolves ticket 5005.
2271 - Use the correct CVE number for CVE-2011-4576 in our comments and
2272 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2275 o Code simplifications and refactoring:
2276 - Use the _WIN32 macro throughout our code to detect Windows.
2277 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2281 Changes in version 0.2.3.11-alpha - 2012-01-22
2282 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2283 the last step of the plan to limit maximum circuit length, includes
2284 a wide variety of hidden service performance and correctness fixes,
2285 works around an OpenSSL security flaw if your distro is too stubborn
2286 to upgrade, and fixes a bunch of smaller issues.
2289 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2290 part of "Proposal 110: Avoiding infinite length circuits" by
2291 refusing all circuit-extend requests that do not use a relay_early
2292 cell. This change helps Tor resist a class of denial-of-service
2293 attacks by limiting the maximum circuit length.
2294 - Adjust the number of introduction points that a hidden service
2295 will try to maintain based on how long its introduction points
2296 remain in use and how many introductions they handle. Fixes
2298 - Try to use system facilities for enumerating local interface
2299 addresses, before falling back to our old approach (which was
2300 binding a UDP socket, and calling getsockname() on it). That
2301 approach was scaring OS X users whose draconian firewall
2302 software warned about binding to UDP sockets, regardless of
2303 whether packets were sent. Now we try to use getifaddrs(),
2304 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2305 system supports. Resolves ticket 1827.
2307 o Major security workaround:
2308 - When building or running with any version of OpenSSL earlier
2309 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2310 versions have a bug (CVE-2011-4576) in which their block cipher
2311 padding includes uninitialized data, potentially leaking sensitive
2312 information to any peer with whom they make a SSLv3 connection. Tor
2313 does not use SSL v3 by default, but a hostile client or server
2314 could force an SSLv3 connection in order to gain information that
2315 they shouldn't have been able to get. The best solution here is to
2316 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2317 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2318 to make sure that the bug can't happen.
2321 - Fix the SOCKET_OK test that we use to tell when socket
2322 creation fails so that it works on Win64. Fixes part of bug 4533;
2323 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2324 - Correct our replacements for the timeradd() and timersub() functions
2325 on platforms that lack them (for example, Windows). The timersub()
2326 function is used when expiring circuits, while timeradd() is
2327 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2328 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2329 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2330 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2331 bug at runtime, not compile time, because some distributions hack
2332 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2333 on 0.2.3.9-alpha. Found by Pascal.
2335 o Minor features (controller):
2336 - Use absolute path names when reporting the torrc filename in the
2337 control protocol, so a controller can more easily find the torrc
2338 file. Resolves bug 1101.
2339 - Extend the control protocol to report flags that control a circuit's
2340 path selection in CIRC events and in replies to 'GETINFO
2341 circuit-status'. Implements part of ticket 2411.
2342 - Extend the control protocol to report the hidden service address
2343 and current state of a hidden-service-related circuit in CIRC
2344 events and in replies to 'GETINFO circuit-status'. Implements part
2346 - When reporting the path to the cookie file to the controller,
2347 give an absolute path. Resolves ticket 4881.
2348 - Allow controllers to request an event notification whenever a
2349 circuit is cannibalized or its purpose is changed. Implements
2350 part of ticket 3457.
2351 - Include the creation time of a circuit in CIRC and CIRC2
2352 control-port events and the list produced by the 'GETINFO
2353 circuit-status' control-port command.
2355 o Minor features (directory authorities):
2356 - Directory authorities now reject versions of Tor older than
2357 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2358 inclusive. These versions accounted for only a small fraction of
2359 the Tor network, and have numerous known security issues. Resolves
2361 - Authority operators can now vote for all relays in a given
2362 set of countries to be BadDir/BadExit/Invalid/Rejected.
2363 - Provide two consensus parameters (FastFlagMinThreshold and
2364 FastFlagMaxThreshold) to control the range of allowable bandwidths
2365 for the Fast directory flag. These allow authorities to run
2366 experiments on appropriate requirements for being a "Fast" node.
2367 The AuthDirFastGuarantee config value still applies. Implements
2369 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2370 directory authority option (introduced in Tor 0.2.2.34).
2372 o Minor features (other):
2373 - Don't disable the DirPort when we cannot exceed our AccountingMax
2374 limit during this interval because the effective bandwidthrate is
2375 low enough. This is useful in a situation where AccountMax is only
2376 used as an additional safeguard or to provide statistics.
2377 - Prepend an informative header to generated dynamic_dh_params files.
2378 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2379 EntryNodes will have no effect. Resolves issue 2571.
2380 - Log more useful messages when we fail to disable debugger
2382 - Log which authority we're missing votes from when we go to fetch
2383 them from the other auths.
2384 - Log (at debug level) whenever a circuit's purpose is changed.
2385 - Add missing documentation for the MaxClientCircuitsPending,
2386 UseMicrodescriptors, UserspaceIOCPBuffers, and
2387 _UseFilteringSSLBufferevents options, all introduced during
2389 - Update to the January 3 2012 Maxmind GeoLite Country database.
2391 o Minor bugfixes (hidden services):
2392 - Don't close hidden service client circuits which have almost
2393 finished connecting to their destination when they reach
2394 the normal circuit-build timeout. Previously, we would close
2395 introduction circuits which are waiting for an acknowledgement
2396 from the introduction point, and rendezvous circuits which have
2397 been specified in an INTRODUCE1 cell sent to a hidden service,
2398 after the normal CBT. Now, we mark them as 'timed out', and launch
2399 another rendezvous attempt in parallel. This behavior change can
2400 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2401 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2402 - Don't close hidden-service-side rendezvous circuits when they
2403 reach the normal circuit-build timeout. This behaviour change can
2404 be disabled using the new
2405 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2406 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2407 - Make sure we never mark the wrong rendezvous circuit as having
2408 had its introduction cell acknowleged by the introduction-point
2409 relay. Previously, when we received an INTRODUCE_ACK cell on a
2410 client-side hidden-service introduction circuit, we might have
2411 marked a rendezvous circuit other than the one we specified in
2412 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2413 a warning message and interfered with the hidden service
2414 connection-establishment process. Fixes bug 4759; bugfix on
2415 0.2.3.3-alpha, when we added the stream-isolation feature which
2416 might cause Tor to open multiple rendezvous circuits for the same
2418 - Don't trigger an assertion failure when we mark a new client-side
2419 hidden-service introduction circuit for close during the process
2420 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2423 o Minor bugfixes (log messages):
2424 - Correctly spell "connect" in a log message on failure to create a
2425 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2427 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2428 Fixes bug 4856; bugfix on Tor 0.0.6.
2429 - Fix the log message describing how we work around discovering
2430 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2431 4837; bugfix on 0.2.2.9-alpha.
2432 - When logging about a disallowed .exit name, do not also call it
2433 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2435 o Minor bugfixes (build fixes):
2436 - During configure, detect when we're building with clang version
2437 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2438 CFLAGS. clang doesn't support them yet.
2439 - During configure, search for library containing cos function as
2440 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2441 against libm was hard-coded before. Fixes the first part of bug
2442 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2444 - Detect attempts to build Tor on (as yet hypothetical) versions
2445 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2446 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2447 - Preprocessor directives should not be put inside the arguments
2448 of a macro. This would break compilation with GCC releases prior
2449 to version 3.3. We would never recommend such an old GCC version,
2450 but it is apparently required for binary compatibility on some
2451 platforms (namely, certain builds of Haiku). Fixes the other part
2452 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2455 o Minor bugfixes (other):
2456 - Older Linux kernels erroneously respond to strange nmap behavior
2457 by having accept() return successfully with a zero-length
2458 socket. When this happens, just close the connection. Previously,
2459 we would try harder to learn the remote address: but there was
2460 no such remote address to learn, and our method for trying to
2461 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2462 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2463 - Fix null-pointer access that could occur if TLS allocation failed.
2464 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2465 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2466 accidentally been reverted.
2467 - Fix our implementation of crypto_random_hostname() so it can't
2468 overflow on ridiculously large inputs. (No Tor version has ever
2469 provided this kind of bad inputs, but let's be correct in depth.)
2470 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2471 - Find more places in the code that should have been testing for
2472 invalid sockets using the SOCKET_OK macro. Required for a fix
2473 for bug 4533. Bugfix on 0.2.2.28-beta.
2474 - Fix an assertion failure when, while running with bufferevents, a
2475 connection finishes connecting after it is marked for close, but
2476 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2477 - test_util_spawn_background_ok() hardcoded the expected value
2478 for ENOENT to 2. This isn't portable as error numbers are
2479 platform specific, and particularly the hurd has ENOENT at
2480 0x40000002. Construct expected string at runtime, using the correct
2481 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2482 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2483 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2484 - Use an appropriate-width type for sockets in tor-fw-helper on
2485 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2488 - When sending or relaying a RELAY_EARLY cell, we used to convert
2489 it to a RELAY cell if the connection was using the v1 link
2490 protocol. This was a workaround for older versions of Tor, which
2491 didn't handle RELAY_EARLY cells properly. Now that all supported
2492 versions can handle RELAY_EARLY cells, and now that we're enforcing
2493 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2494 remove this workaround. Addresses bug 4786.
2496 o Code simplifications and refactoring:
2497 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2498 own homebrewed ssl_state_to_string() replacement. Patch from
2499 Emile Snyder. Fixes bug 4653.
2500 - Use macros to indicate OpenSSL versions, so we don't need to worry
2501 about accidental hexadecimal bit shifts.
2502 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2504 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2505 - Use the smartlist_add_asprintf() alias more consistently.
2506 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2507 invalid value, rather than just -1.
2508 - Rename a handful of old identifiers, mostly related to crypto
2509 structures and crypto functions. By convention, our "create an
2510 object" functions are called "type_new()", our "free an object"
2511 functions are called "type_free()", and our types indicate that
2512 they are types only with a final "_t". But a handful of older
2513 types and functions broke these rules, with function names like
2514 "type_create" or "subsystem_op_type", or with type names like
2518 Changes in version 0.2.3.10-alpha - 2011-12-16
2519 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
2520 Tor's buffers code. Absolutely everybody should upgrade.
2522 The bug relied on an incorrect calculation when making data continuous
2523 in one of our IO buffers, if the first chunk of the buffer was
2524 misaligned by just the wrong amount. The miscalculation would allow an
2525 attacker to overflow a piece of heap-allocated memory. To mount this
2526 attack, the attacker would need to either open a SOCKS connection to
2527 Tor's SocksPort (usually restricted to localhost), or target a Tor
2528 instance configured to make its connections through a SOCKS proxy
2529 (which Tor does not do by default).
2531 Good security practice requires that all heap-overflow bugs should be
2532 presumed to be exploitable until proven otherwise, so we are treating
2533 this as a potential code execution attack. Please upgrade immediately!
2534 This bug does not affect bufferevents-based builds of Tor. Special
2535 thanks to "Vektor" for reporting this issue to us!
2537 This release also contains a few minor bugfixes for issues discovered
2541 - Fix a heap overflow bug that could occur when trying to pull
2542 data into the first chunk of a buffer, when that chunk had
2543 already had some data drained from it. Fixes CVE-2011-2778;
2544 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2547 - If we can't attach streams to a rendezvous circuit when we
2548 finish connecting to a hidden service, clear the rendezvous
2549 circuit's stream-isolation state and try to attach streams
2550 again. Previously, we cleared rendezvous circuits' isolation
2551 state either too early (if they were freshly built) or not at all
2552 (if they had been built earlier and were cannibalized). Bugfix on
2553 0.2.3.3-alpha; fixes bug 4655.
2554 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
2555 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
2556 - Fix an assertion failure when a relay with accounting enabled
2557 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
2560 - Update to the December 6 2011 Maxmind GeoLite Country database.
2563 Changes in version 0.2.2.35 - 2011-12-16
2564 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2565 buffers code. Absolutely everybody should upgrade.
2567 The bug relied on an incorrect calculation when making data continuous
2568 in one of our IO buffers, if the first chunk of the buffer was
2569 misaligned by just the wrong amount. The miscalculation would allow an
2570 attacker to overflow a piece of heap-allocated memory. To mount this
2571 attack, the attacker would need to either open a SOCKS connection to
2572 Tor's SocksPort (usually restricted to localhost), or target a Tor
2573 instance configured to make its connections through a SOCKS proxy
2574 (which Tor does not do by default).
2576 Good security practice requires that all heap-overflow bugs should be
2577 presumed to be exploitable until proven otherwise, so we are treating
2578 this as a potential code execution attack. Please upgrade immediately!
2579 This bug does not affect bufferevents-based builds of Tor. Special
2580 thanks to "Vektor" for reporting this issue to us!
2582 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2583 crash bugs for unusual configurations, and a long-term bug that
2584 would prevent Tor from starting on Windows machines with draconian
2587 With this release, we remind everyone that 0.2.0.x has reached its
2588 formal end-of-life. Those Tor versions have many known flaws, and
2589 nobody should be using them. You should upgrade -- ideally to the
2590 0.2.2.x series. If you're using a Linux or BSD and its packages are
2591 obsolete, stop using those packages and upgrade anyway.
2593 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2594 longer receive support after some time in early 2012.
2597 - Fix a heap overflow bug that could occur when trying to pull
2598 data into the first chunk of a buffer, when that chunk had
2599 already had some data drained from it. Fixes CVE-2011-2778;
2600 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2601 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2602 that it doesn't attempt to allocate a socketpair. This could cause
2603 some problems on Windows systems with overzealous firewalls. Fix for
2604 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2606 - If we mark an OR connection for close based on a cell we process,
2607 don't process any further cells on it. We already avoid further
2608 reads on marked-for-close connections, but now we also discard the
2609 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2610 which was the first version where we might mark a connection for
2611 close based on processing a cell on it.
2612 - Correctly sanity-check that we don't underflow on a memory
2613 allocation (and then assert) for hidden service introduction
2614 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2615 bugfix on 0.2.1.5-alpha.
2616 - Fix a memory leak when we check whether a hidden service
2617 descriptor has any usable introduction points left. Fixes bug
2618 4424. Bugfix on 0.2.2.25-alpha.
2619 - Don't crash when we're running as a relay and don't have a GeoIP
2620 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2621 we've had in the 0.2.3.x branch already.
2622 - When running as a client, do not print a misleading (and plain
2623 wrong) log message that we're collecting "directory request"
2624 statistics: clients don't collect statistics. Also don't create a
2625 useless (because empty) stats file in the stats/ directory. Fixes
2626 bug 4353; bugfix on 0.2.2.34.
2629 - Detect failure to initialize Libevent. This fix provides better
2630 detection for future instances of bug 4457.
2631 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2632 function. This was eating up hideously large amounts of time on some
2633 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2634 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2635 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2637 - Don't warn about unused log_mutex in log.c when building with
2638 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2639 0.1.0.6-rc which introduced --disable-threads.
2640 - When configuring, starting, or stopping an NT service, stop
2641 immediately after the service configuration attempt has succeeded
2642 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2643 - When sending a NETINFO cell, include the original address
2644 received for the other side, not its canonical address. Found
2645 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2646 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2647 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2648 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2649 occurred when a client tried to fetch a descriptor for a bridge
2650 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2651 - Backport fixes for a pair of compilation warnings on Windows.
2652 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2653 - If we had ever tried to call tor_addr_to_str on an address of
2654 unknown type, we would have done a strdup on an uninitialized
2655 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2656 Reported by "troll_un".
2657 - Correctly detect and handle transient lookup failures from
2658 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2659 Reported by "troll_un".
2660 - Fix null-pointer access that could occur if TLS allocation failed.
2661 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2662 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2663 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2666 - Add two new config options for directory authorities:
2667 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2668 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2669 that is always sufficient to satisfy the bandwidth requirement for
2670 the Guard flag. Now it will be easier for researchers to simulate
2671 Tor networks with different values. Resolves ticket 4484.
2672 - When Tor ignores a hidden service specified in its configuration,
2673 include the hidden service's directory in the warning message.
2674 Previously, we would only tell the user that some hidden service
2675 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2676 - Update to the December 6 2011 Maxmind GeoLite Country database.
2678 o Packaging changes:
2679 - Make it easier to automate expert package builds on Windows,
2680 by removing an absolute path from makensis.exe command.
2683 Changes in version 0.2.1.32 - 2011-12-16
2684 Tor 0.2.1.32 backports important security and privacy fixes for
2685 oldstable. This release is intended only for package maintainers and
2686 others who cannot use the 0.2.2 stable series. All others should be
2687 using Tor 0.2.2.x or newer.
2689 The Tor 0.2.1.x series will reach formal end-of-life some time in
2690 early 2012; we will stop releasing patches for it then.
2692 o Major bugfixes (also included in 0.2.2.x):
2693 - Correctly sanity-check that we don't underflow on a memory
2694 allocation (and then assert) for hidden service introduction
2695 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2696 bugfix on 0.2.1.5-alpha.
2697 - Fix a heap overflow bug that could occur when trying to pull
2698 data into the first chunk of a buffer, when that chunk had
2699 already had some data drained from it. Fixes CVE-2011-2778;
2700 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2703 - Update to the December 6 2011 Maxmind GeoLite Country database.
2706 Changes in version 0.2.3.9-alpha - 2011-12-08
2707 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
2708 a "DisableNetwork" security feature that bundles can use to avoid
2709 touching the network until bridges are configured, moves forward on
2710 the pluggable transport design, fixes a flaw in the hidden service
2711 design that unnecessarily prevented clients with wrong clocks from
2712 reaching hidden services, and fixes a wide variety of other issues.
2715 - Clients can now connect to private bridges over IPv6. Bridges
2716 still need at least one IPv4 address in order to connect to
2717 other relays. Note that we don't yet handle the case where the
2718 user has two bridge lines for the same bridge (one IPv4, one
2719 IPv6). Implements parts of proposal 186.
2720 - New "DisableNetwork" config option to prevent Tor from launching any
2721 connections or accepting any connections except on a control port.
2722 Bundles and controllers can set this option before letting Tor talk
2723 to the rest of the network, for example to prevent any connections
2724 to a non-bridge address. Packages like Orbot can also use this
2725 option to instruct Tor to save power when the network is off.
2726 - Clients and bridges can now be configured to use a separate
2727 "transport" proxy. This approach makes the censorship arms race
2728 easier by allowing bridges to use protocol obfuscation plugins. It
2729 implements the "managed proxy" part of proposal 180 (ticket 3472).
2730 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2731 implementation. It makes AES_CTR about 7% faster than our old one
2732 (which was about 10% faster than the one OpenSSL used to provide).
2733 Resolves ticket 4526.
2734 - Add a "tor2web mode" for clients that want to connect to hidden
2735 services non-anonymously (and possibly more quickly). As a safety
2736 measure to try to keep users from turning this on without knowing
2737 what they are doing, tor2web mode must be explicitly enabled at
2738 compile time, and a copy of Tor compiled to run in tor2web mode
2739 cannot be used as a normal Tor client. Implements feature 2553.
2740 - Add experimental support for running on Windows with IOCP and no
2741 kernel-space socket buffers. This feature is controlled by a new
2742 "UserspaceIOCPBuffers" config option (off by default), which has
2743 no effect unless Tor has been built with support for bufferevents,
2744 is running on Windows, and has enabled IOCP. This may, in the long
2745 run, help solve or mitigate bug 98.
2746 - Use a more secure consensus parameter voting algorithm. Now at
2747 least three directory authorities or a majority of them must
2748 vote on a given parameter before it will be included in the
2749 consensus. Implements proposal 178.
2752 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2753 They used to check that the timestamp was within 30 minutes
2754 of their system clock, so they could cap the size of their
2755 replay-detection cache, but that approach unnecessarily refused
2756 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2757 the v3 intro-point protocol (the first one which sent a timestamp
2758 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2759 - Only use the EVP interface when AES acceleration is enabled,
2760 to avoid a 5-7% performance regression. Resolves issue 4525;
2761 bugfix on 0.2.3.8-alpha.
2763 o Privacy/anonymity features (bridge detection):
2764 - Make bridge SSL certificates a bit more stealthy by using random
2765 serial numbers, in the same fashion as OpenSSL when generating
2766 self-signed certificates. Implements ticket 4584.
2767 - Introduce a new config option "DynamicDHGroups", enabled by
2768 default, which provides each bridge with a unique prime DH modulus
2769 to be used during SSL handshakes. This option attempts to help
2770 against censors who might use the Apache DH modulus as a static
2771 identifier for bridges. Addresses ticket 4548.
2773 o Minor features (new/different config options):
2774 - New configuration option "DisableDebuggerAttachment" (on by default)
2775 to prevent basic debugging attachment attempts by other processes.
2776 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
2777 - Allow MapAddress directives to specify matches against super-domains,
2778 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
2779 Implements issue 933.
2780 - Slightly change behavior of "list" options (that is, config
2781 options that can appear more than once) when they appear both in
2782 torrc and on the command line. Previously, the command-line options
2783 would be appended to the ones from torrc. Now, the command-line
2784 options override the torrc options entirely. This new behavior
2785 allows the user to override list options (like exit policies and
2786 ports to listen on) from the command line, rather than simply
2787 appending to the list.
2788 - You can get the old (appending) command-line behavior for "list"
2789 options by prefixing the option name with a "+".
2790 - You can remove all the values for a "list" option from the command
2791 line without adding any new ones by prefixing the option name
2793 - Add experimental support for a "defaults" torrc file to be parsed
2794 before the regular torrc. Torrc options override the defaults file's
2795 options in the same way that the command line overrides the torrc.
2796 The SAVECONF controller command saves only those options which
2797 differ between the current configuration and the defaults file. HUP
2798 reloads both files. (Note: This is an experimental feature; its
2799 behavior will probably be refined in future 0.2.3.x-alpha versions
2800 to better meet packagers' needs.) Implements task 4552.
2803 - Try to make the introductory warning message that Tor prints on
2804 startup more useful for actually finding help and information.
2805 Resolves ticket 2474.
2806 - Running "make version" now displays the version of Tor that
2807 we're about to build. Idea from katmagic; resolves issue 4400.
2808 - Expire old or over-used hidden service introduction points.
2809 Required by fix for bug 3460.
2810 - Move the replay-detection cache for the RSA-encrypted parts of
2811 INTRODUCE2 cells to the introduction point data structures.
2812 Previously, we would use one replay-detection cache per hidden
2813 service. Required by fix for bug 3460.
2814 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
2815 public key replay-detection cache from 60 minutes to 5 minutes. This
2816 replay-detection cache is now used only to detect multiple
2817 INTRODUCE2 cells specifying the same rendezvous point, so we can
2818 avoid launching multiple simultaneous attempts to connect to it.
2820 o Minor bugfixes (on Tor 0.2.2.x and earlier):
2821 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2822 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2824 - Fix a minor formatting issue in one of tor-gencert's error messages.
2826 - Prevent a false positive from the check-spaces script, by disabling
2827 the "whitespace between function name and (" check for functions
2829 - Fix a log message suggesting that people contact a non-existent
2830 email address. Fixes bug 3448.
2831 - Fix null-pointer access that could occur if TLS allocation failed.
2832 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2833 - Report a real bootstrap problem to the controller on router
2834 identity mismatch. Previously we just said "foo", which probably
2835 made a lot of sense at the time. Fixes bug 4169; bugfix on
2837 - If we had ever tried to call tor_addr_to_str() on an address of
2838 unknown type, we would have done a strdup() on an uninitialized
2839 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2840 Reported by "troll_un".
2841 - Correctly detect and handle transient lookup failures from
2842 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2843 Reported by "troll_un".
2844 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2845 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2846 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2847 bug 4532; found by "troll_un".
2849 o Minor bugfixes (on Tor 0.2.3.x):
2850 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
2852 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
2853 circuit for use as a hidden service client's rendezvous point.
2854 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
2855 with help from wanoskarnet.
2856 - Restore behavior of overriding SocksPort, ORPort, and similar
2857 options from the command line. Bugfix on 0.2.3.3-alpha.
2860 - Properly handle the case where the build-tree is not the same
2861 as the source tree when generating src/common/common_sha1.i,
2862 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
2863 bugfix on 0.2.0.1-alpha.
2865 o Code simplifications, cleanups, and refactorings:
2866 - Remove the pure attribute from all functions that used it
2867 previously. In many cases we assigned it incorrectly, because the
2868 functions might assert or call impure functions, and we don't have
2869 evidence that keeping the pure attribute is worthwhile. Implements
2870 changes suggested in ticket 4421.
2871 - Remove some dead code spotted by coverity. Fixes cid 432.
2872 Bugfix on 0.2.3.1-alpha, closes bug 4637.
2875 Changes in version 0.2.3.8-alpha - 2011-11-22
2876 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
2877 socketpair-related bug that has been bothering Windows users. It adds
2878 support to serve microdescriptors to controllers, so Vidalia's network
2879 map can resume listing relays (once Vidalia implements its side),
2880 and adds better support for hardware AES acceleration. Finally, it
2881 starts the process of adjusting the bandwidth cutoff for getting the
2882 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
2883 that tiny relays harm performance more than they help network capacity.
2886 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2887 that it doesn't attempt to allocate a socketpair. This could cause
2888 some problems on Windows systems with overzealous firewalls. Fix for
2889 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2891 - Correctly sanity-check that we don't underflow on a memory
2892 allocation (and then assert) for hidden service introduction
2893 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2894 bugfix on 0.2.1.5-alpha.
2895 - Remove the artificially low cutoff of 20KB to guarantee the Fast
2896 flag. In the past few years the average relay speed has picked
2897 up, and while the "top 7/8 of the network get the Fast flag" and
2898 "all relays with 20KB or more of capacity get the Fast flag" rules
2899 used to have the same result, now the top 7/8 of the network has
2900 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
2901 - Fix a rare assertion failure when checking whether a v0 hidden
2902 service descriptor has any usable introduction points left, and
2903 we don't have enough information to build a circuit to the first
2904 intro point named in the descriptor. The HS client code in
2905 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
2906 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
2907 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
2908 - Make bridge authorities not crash when they are asked for their own
2909 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
2910 - When running as a client, do not print a misleading (and plain
2911 wrong) log message that we're collecting "directory request"
2912 statistics: clients don't collect statistics. Also don't create a
2913 useless (because empty) stats file in the stats/ directory. Fixes
2914 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
2917 - Allow Tor controllers like Vidalia to obtain the microdescriptor
2918 for a relay by identity digest or nickname. Previously,
2919 microdescriptors were only available by their own digests, so a
2920 controller would have to ask for and parse the whole microdescriptor
2921 consensus in order to look up a single relay's microdesc. Fixes
2922 bug 3832; bugfix on 0.2.3.1-alpha.
2923 - Use OpenSSL's EVP interface for AES encryption, so that all AES
2924 operations can use hardware acceleration (if present). Resolves
2927 o Minor bugfixes (on 0.2.2.x and earlier):
2928 - Detect failure to initialize Libevent. This fix provides better
2929 detection for future instances of bug 4457.
2930 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2931 function. This was eating up hideously large amounts of time on some
2932 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2933 - Don't warn about unused log_mutex in log.c when building with
2934 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2935 0.1.0.6-rc which introduced --disable-threads.
2936 - Allow manual 'authenticate' commands to the controller interface
2937 from netcat (nc) as well as telnet. We were rejecting them because
2938 they didn't come with the expected whitespace at the end of the
2939 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2940 - Fix some (not actually triggerable) buffer size checks in usage of
2941 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2943 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2944 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2945 - When configuring, starting, or stopping an NT service, stop
2946 immediately after the service configuration attempt has succeeded
2947 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2948 - When sending a NETINFO cell, include the original address
2949 received for the other side, not its canonical address. Found
2950 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2951 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2952 can pick them up when the tests aren't disabled. Bugfix on
2953 0.2.2.4-alpha which introduced tinytest.
2954 - Fix a memory leak when we check whether a hidden service
2955 descriptor has any usable introduction points left. Fixes bug
2956 4424. Bugfix on 0.2.2.25-alpha.
2957 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2958 occurred when a client tried to fetch a descriptor for a bridge
2959 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2961 o Minor bugfixes (on 0.2.3.x):
2962 - Make util unit tests build correctly with MSVC. Bugfix on
2963 0.2.3.3-alpha. Patch by Gisle Vanem.
2964 - Successfully detect AUTH_CHALLENGE cells with no recognized
2965 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
2967 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
2968 it should still send a NETINFO cell to allow the connection to
2969 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
2971 - Log less loudly when we get an invalid authentication certificate
2972 from a source other than a directory authority: it's not unusual
2973 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
2975 - Tolerate servers with more clock skew in their authentication
2976 certificates than previously. Fixes bug 4371; bugfix on
2978 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
2979 on 0.2.3.4-alpha and 0.2.3.6-alpha.
2982 - Add two new config options for directory authorities:
2983 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2984 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2985 that is always sufficient to satisfy the bandwidth requirement for
2986 the Guard flag. Now it will be easier for researchers to simulate
2987 Tor networks with different values. Resolves ticket 4484.
2988 - When Tor ignores a hidden service specified in its configuration,
2989 include the hidden service's directory in the warning message.
2990 Previously, we would only tell the user that some hidden service
2991 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2992 - When we fail to initialize Libevent, retry with IOCP disabled so we
2993 don't need to turn on multi-threading support in Libevent, which in
2994 turn requires a working socketpair(). This is a workaround for bug
2995 4457, which affects Libevent versions from 2.0.1-alpha through
2997 - Detect when we try to build on a platform that doesn't define
2998 AF_UNSPEC to 0. We don't work there, so refuse to compile.
2999 - Update to the November 1 2011 Maxmind GeoLite Country database.
3001 o Packaging changes:
3002 - Make it easier to automate expert package builds on Windows,
3003 by removing an absolute path from makensis.exe command.
3005 o Code simplifications and refactoring:
3006 - Remove some redundant #include directives throughout the code.
3007 Patch from Andrea Gelmini.
3008 - Unconditionally use OpenSSL's AES implementation instead of our
3009 old built-in one. OpenSSL's AES has been better for a while, and
3010 relatively few servers should still be on any version of OpenSSL
3011 that doesn't have good optimized assembly AES.
3012 - Use the name "CERTS" consistently to refer to the new cell type;
3013 we were calling it CERT in some places and CERTS in others.
3016 - Numerous new unit tests for functions in util.c and address.c by
3018 - The long-disabled benchmark tests are now split into their own
3019 ./src/test/bench binary.
3020 - The benchmark tests can now use more accurate timers than
3021 gettimeofday() when such timers are available.
3024 Changes in version 0.2.3.7-alpha - 2011-10-30
3025 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3026 the new v3 handshake. It also resolves yet another bridge address
3030 - If we mark an OR connection for close based on a cell we process,
3031 don't process any further cells on it. We already avoid further
3032 reads on marked-for-close connections, but now we also discard the
3033 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3034 which was the first version where we might mark a connection for
3035 close based on processing a cell on it.
3036 - Fix a double-free bug that would occur when we received an invalid
3037 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3038 bugfix on 0.2.3.6-alpha.
3039 - Bridges no longer include their address in NETINFO cells on outgoing
3040 OR connections, to allow them to blend in better with clients.
3041 Removes another avenue for enumerating bridges. Reported by
3042 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3043 cells were introduced.
3046 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3047 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3050 Changes in version 0.2.3.6-alpha - 2011-10-26
3051 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3052 anonymity vulnerability where an attacker can deanonymize Tor
3053 users. Everybody should upgrade.
3055 This release also features support for a new v3 connection handshake
3056 protocol, and fixes to make hidden service connections more robust.
3059 - Implement a new handshake protocol (v3) for authenticating Tors to
3060 each other over TLS. It should be more resistant to fingerprinting
3061 than previous protocols, and should require less TLS hacking for
3062 future Tor implementations. Implements proposal 176.
3063 - Allow variable-length padding cells to disguise the length of
3064 Tor's TLS records. Implements part of proposal 184.
3066 o Privacy/anonymity fixes (clients):
3067 - Clients and bridges no longer send TLS certificate chains on
3068 outgoing OR connections. Previously, each client or bridge would
3069 use the same cert chain for all outgoing OR connections until
3070 its IP address changes, which allowed any relay that the client
3071 or bridge contacted to determine which entry guards it is using.
3072 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3073 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3074 no longer considers that connection as suitable for satisfying a
3075 circuit EXTEND request. Now relays can protect clients from the
3076 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3077 - Directory authorities no longer assign the Guard flag to relays
3078 that haven't upgraded to the above "refuse EXTEND requests
3079 to client connections" fix. Now directory authorities can
3080 protect clients from the CVE-2011-2768 issue even if neither
3081 the clients nor the relays have upgraded yet. There's a new
3082 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3083 to let us transition smoothly, else tomorrow there would be no
3086 o Major bugfixes (hidden services):
3087 - Improve hidden service robustness: when an attempt to connect to
3088 a hidden service ends, be willing to refetch its hidden service
3089 descriptors from each of the HSDir relays responsible for them
3090 immediately. Previously, we would not consider refetching the
3091 service's descriptors from each HSDir for 15 minutes after the last
3092 fetch, which was inconvenient if the hidden service was not running
3093 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3094 - When one of a hidden service's introduction points appears to be
3095 unreachable, stop trying it. Previously, we would keep trying
3096 to build circuits to the introduction point until we lost the
3097 descriptor, usually because the user gave up and restarted Tor.
3098 Partly fixes bug 3825.
3099 - Don't launch a useless circuit after failing to use one of a
3100 hidden service's introduction points. Previously, we would
3101 launch a new introduction circuit, but not set the hidden service
3102 which that circuit was intended to connect to, so it would never
3103 actually be used. A different piece of code would then create a
3104 new introduction circuit correctly. Bug reported by katmagic and
3105 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3107 o Major bugfixes (other):
3108 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3109 that they initiated. Relays could distinguish incoming bridge
3110 connections from client connections, creating another avenue for
3111 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3112 Found by "frosty_un".
3113 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3114 tor gets started. This prevents a wrong average bandwidth
3115 estimate, which would cause relays to always start a new accounting
3116 interval at the earliest possible moment. Fixes bug 2003; bugfix
3117 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3118 immensely in tracking this bug down.
3119 - Fix a crash bug when changing node restrictions while a DNS lookup
3120 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3123 o Minor bugfixes (on 0.2.2.x and earlier):
3124 - When a hidden service turns an extra service-side introduction
3125 circuit into a general-purpose circuit, free the rend_data and
3126 intro_key fields first, so we won't leak memory if the circuit
3127 is cannibalized for use as another service-side introduction
3128 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3129 - Rephrase the log message emitted if the TestSocks check is
3130 successful. Patch from Fabian Keil; fixes bug 4094.
3131 - Bridges now skip DNS self-tests, to act a little more stealthily.
3132 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3133 bridges. Patch by "warms0x".
3134 - Remove a confusing dollar sign from the example fingerprint in the
3135 man page, and also make the example fingerprint a valid one. Fixes
3136 bug 4309; bugfix on 0.2.1.3-alpha.
3137 - Fix internal bug-checking logic that was supposed to catch
3138 failures in digest generation so that it will fail more robustly
3139 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3140 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3141 - Report any failure in init_keys() calls launched because our
3142 IP address has changed. Spotted by Coverity Scan. Bugfix on
3143 0.1.1.4-alpha; fixes CID 484.
3145 o Minor bugfixes (on 0.2.3.x):
3146 - Fix a bug in configure.in that kept it from building a configure
3147 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3148 bugfix on 0.2.3.1-alpha.
3149 - Don't warn users that they are exposing a client port to the
3150 Internet if they have specified an RFC1918 address. Previously,
3151 we would warn if the user had specified any non-loopback
3152 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3153 - Fix memory leaks in the failing cases of the new SocksPort and
3154 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3155 fixes coverity CIDs 485, 486, and 487.
3158 - When a hidden service's introduction point times out, consider
3159 trying it again during the next attempt to connect to the
3160 HS. Previously, we would not try it again unless a newly fetched
3161 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3162 - The next version of Windows will be called Windows 8, and it has
3163 a major version of 6, minor version of 2. Correctly identify that
3164 version instead of calling it "Very recent version". Resolves
3165 ticket 4153; reported by funkstar.
3166 - The Bridge Authority now writes statistics on how many bridge
3167 descriptors it gave out in total, and how many unique descriptors
3168 it gave out. It also lists how often the most and least commonly
3169 fetched descriptors were given out, as well as the median and
3170 25th/75th percentile. Implements tickets 4200 and 4294.
3171 - Update to the October 4 2011 Maxmind GeoLite Country database.
3173 o Code simplifications and refactoring:
3174 - Remove some old code to remember statistics about which descriptors
3175 we've served as a directory mirror. The feature wasn't used and
3176 is outdated now that microdescriptors are around.
3177 - Rename Tor functions that turn strings into addresses, so that
3178 "parse" indicates that no hostname resolution occurs, and
3179 "lookup" indicates that hostname resolution may occur. This
3180 should help prevent mistakes in the future. Fixes bug 3512.
3183 Changes in version 0.2.2.34 - 2011-10-26
3184 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3185 can deanonymize Tor users. Everybody should upgrade.
3187 The attack relies on four components: 1) Clients reuse their TLS cert
3188 when talking to different relays, so relays can recognize a user by
3189 the identity key in her cert. 2) An attacker who knows the client's
3190 identity key can probe each guard relay to see if that identity key
3191 is connected to that guard relay right now. 3) A variety of active
3192 attacks in the literature (starting from "Low-Cost Traffic Analysis
3193 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3194 discover the guard relays that a Tor user visiting the website is using.
3195 4) Clients typically pick three guards at random, so the set of guards
3196 for a given user could well be a unique fingerprint for her. This
3197 release fixes components #1 and #2, which is enough to block the attack;
3198 the other two remain as open research problems. Special thanks to
3199 "frosty_un" for reporting the issue to us!
3201 Clients should upgrade so they are no longer recognizable by the TLS
3202 certs they present. Relays should upgrade so they no longer allow a
3203 remote attacker to probe them to test whether unpatched clients are
3204 currently connected to them.
3206 This release also fixes several vulnerabilities that allow an attacker
3207 to enumerate bridge relays. Some bridge enumeration attacks still
3208 remain; see for example proposal 188.
3210 o Privacy/anonymity fixes (clients):
3211 - Clients and bridges no longer send TLS certificate chains on
3212 outgoing OR connections. Previously, each client or bridge would
3213 use the same cert chain for all outgoing OR connections until
3214 its IP address changes, which allowed any relay that the client
3215 or bridge contacted to determine which entry guards it is using.
3216 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3217 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3218 no longer considers that connection as suitable for satisfying a
3219 circuit EXTEND request. Now relays can protect clients from the
3220 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3221 - Directory authorities no longer assign the Guard flag to relays
3222 that haven't upgraded to the above "refuse EXTEND requests
3223 to client connections" fix. Now directory authorities can
3224 protect clients from the CVE-2011-2768 issue even if neither
3225 the clients nor the relays have upgraded yet. There's a new
3226 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3227 to let us transition smoothly, else tomorrow there would be no
3230 o Privacy/anonymity fixes (bridge enumeration):
3231 - Bridge relays now do their directory fetches inside Tor TLS
3232 connections, like all the other clients do, rather than connecting
3233 directly to the DirPort like public relays do. Removes another
3234 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3235 - Bridges relays now build circuits for themselves in a more similar
3236 way to how clients build them. Removes another avenue for
3237 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3238 when bridges were introduced.
3239 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3240 that they initiated. Relays could distinguish incoming bridge
3241 connections from client connections, creating another avenue for
3242 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3243 Found by "frosty_un".
3246 - Fix a crash bug when changing node restrictions while a DNS lookup
3247 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3249 - Don't launch a useless circuit after failing to use one of a
3250 hidden service's introduction points. Previously, we would
3251 launch a new introduction circuit, but not set the hidden service
3252 which that circuit was intended to connect to, so it would never
3253 actually be used. A different piece of code would then create a
3254 new introduction circuit correctly. Bug reported by katmagic and
3255 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3258 - Change an integer overflow check in the OpenBSD_Malloc code so
3259 that GCC is less likely to eliminate it as impossible. Patch
3260 from Mansour Moufid. Fixes bug 4059.
3261 - When a hidden service turns an extra service-side introduction
3262 circuit into a general-purpose circuit, free the rend_data and
3263 intro_key fields first, so we won't leak memory if the circuit
3264 is cannibalized for use as another service-side introduction
3265 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3266 - Bridges now skip DNS self-tests, to act a little more stealthily.
3267 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3268 bridges. Patch by "warms0x".
3269 - Fix internal bug-checking logic that was supposed to catch
3270 failures in digest generation so that it will fail more robustly
3271 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3272 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3273 - Report any failure in init_keys() calls launched because our
3274 IP address has changed. Spotted by Coverity Scan. Bugfix on
3275 0.1.1.4-alpha; fixes CID 484.
3277 o Minor bugfixes (log messages and documentation):
3278 - Remove a confusing dollar sign from the example fingerprint in the
3279 man page, and also make the example fingerprint a valid one. Fixes
3280 bug 4309; bugfix on 0.2.1.3-alpha.
3281 - The next version of Windows will be called Windows 8, and it has
3282 a major version of 6, minor version of 2. Correctly identify that
3283 version instead of calling it "Very recent version". Resolves
3284 ticket 4153; reported by funkstar.
3285 - Downgrade log messages about circuit timeout calibration from
3286 "notice" to "info": they don't require or suggest any human
3287 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3288 bugfix on 0.2.2.14-alpha.
3291 - Turn on directory request statistics by default and include them in
3292 extra-info descriptors. Don't break if we have no GeoIP database.
3293 Backported from 0.2.3.1-alpha; implements ticket 3951.
3294 - Update to the October 4 2011 Maxmind GeoLite Country database.
3297 Changes in version 0.2.1.31 - 2011-10-26
3298 Tor 0.2.1.31 backports important security and privacy fixes for
3299 oldstable. This release is intended only for package maintainers and
3300 others who cannot use the 0.2.2 stable series. All others should be
3301 using Tor 0.2.2.x or newer.
3303 o Security fixes (also included in 0.2.2.x):
3304 - Replace all potentially sensitive memory comparison operations
3305 with versions whose runtime does not depend on the data being
3306 compared. This will help resist a class of attacks where an
3307 adversary can use variations in timing information to learn
3308 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3309 implementation by Robert Ransom based partially on code by DJB.)
3310 - Fix an assert in parsing router descriptors containing IPv6
3311 addresses. This one took down the directory authorities when
3312 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3314 o Privacy/anonymity fixes (also included in 0.2.2.x):
3315 - Clients and bridges no longer send TLS certificate chains on
3316 outgoing OR connections. Previously, each client or bridge would
3317 use the same cert chain for all outgoing OR connections until
3318 its IP address changes, which allowed any relay that the client
3319 or bridge contacted to determine which entry guards it is using.
3320 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3321 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3322 no longer considers that connection as suitable for satisfying a
3323 circuit EXTEND request. Now relays can protect clients from the
3324 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3325 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3326 that they initiated. Relays could distinguish incoming bridge
3327 connections from client connections, creating another avenue for
3328 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3329 Found by "frosty_un".
3330 - When receiving a hidden service descriptor, check that it is for
3331 the hidden service we wanted. Previously, Tor would store any
3332 hidden service descriptors that a directory gave it, whether it
3333 wanted them or not. This wouldn't have let an attacker impersonate
3334 a hidden service, but it did let directories pre-seed a client
3335 with descriptors that it didn't want. Bugfix on 0.0.6.
3336 - Avoid linkability based on cached hidden service descriptors: forget
3337 all hidden service descriptors cached as a client when processing a
3338 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3339 - Make the bridge directory authority refuse to answer directory
3340 requests for "all" descriptors. It used to include bridge
3341 descriptors in its answer, which was a major information leak.
3342 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3343 - Don't attach new streams to old rendezvous circuits after SIGNAL
3344 NEWNYM. Previously, we would keep using an existing rendezvous
3345 circuit if it remained open (i.e. if it were kept open by a
3346 long-lived stream, or if a new stream were attached to it before
3347 Tor could notice that it was old and no longer in use). Bugfix on
3348 0.1.1.15-rc; fixes bug 3375.
3350 o Minor bugfixes (also included in 0.2.2.x):
3351 - When we restart our relay, we might get a successful connection
3352 from the outside before we've started our reachability tests,
3353 triggering a warning: "ORPort found reachable, but I have no
3354 routerinfo yet. Failing to inform controller of success." This
3355 bug was harmless unless Tor is running under a controller
3356 like Vidalia, in which case the controller would never get a
3357 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3359 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3360 enabled. Fixes bug 1526.
3361 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3362 anything since 0.2.1.16-rc.
3363 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3364 None of the cases where we did this before were wrong, but by making
3365 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3366 - Fix a rare crash bug that could occur when a client was configured
3367 with a large number of bridges. Fixes bug 2629; bugfix on
3368 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3369 - Correct the warning displayed when a rendezvous descriptor exceeds
3370 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3372 - Fix an uncommon assertion failure when running with DNSPort under
3373 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3374 - When warning about missing zlib development packages during compile,
3375 give the correct package names. Bugfix on 0.2.0.1-alpha.
3376 - Require that introduction point keys and onion keys have public
3377 exponent 65537. Bugfix on 0.2.0.10-alpha.
3378 - Do not crash when our configuration file becomes unreadable, for
3379 example due to a permissions change, between when we start up
3380 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3382 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3384 - Always NUL-terminate the sun_path field of a sockaddr_un before
3385 passing it to the kernel. (Not a security issue: kernels are
3386 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3387 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3388 - Don't stack-allocate the list of supplementary GIDs when we're
3389 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3390 could take up to 256K, which is way too much stack. Found by
3391 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3393 o Minor bugfixes (only in 0.2.1.x):
3394 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3395 rely on them. Bugfix on 0.2.1.30.
3396 - Use git revisions instead of svn revisions when generating our
3397 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3399 o Minor features (also included in 0.2.2.x):
3400 - Adjust the expiration time on our SSL session certificates to
3401 better match SSL certs seen in the wild. Resolves ticket 4014.
3402 - Allow nameservers with IPv6 address. Resolves bug 2574.
3403 - Update to the October 4 2011 Maxmind GeoLite Country database.
3406 Changes in version 0.2.3.5-alpha - 2011-09-28
3407 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3408 bridge relays; fixes an assertion error that many users started hitting
3409 today; and adds the ability to refill token buckets more often than
3410 once per second, allowing significant performance improvements.
3413 - Bridge relays now do their directory fetches inside Tor TLS
3414 connections, like all the other clients do, rather than connecting
3415 directly to the DirPort like public relays do. Removes another
3416 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3417 - Bridges relays now build circuits for themselves in a more similar
3418 way to how clients build them. Removes another avenue for
3419 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3420 when bridges were introduced.
3423 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3424 occur when the same microdescriptor was referenced by two node_t
3425 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3427 o Major features (networking):
3428 - Add a new TokenBucketRefillInterval option to refill token buckets
3429 more frequently than once per second. This should improve network
3430 performance, alleviate queueing problems, and make traffic less
3431 bursty. Implements proposal 183; closes ticket 3630. Design by
3432 Florian Tschorsch and Björn Scheuermann; implementation by
3436 - Change an integer overflow check in the OpenBSD_Malloc code so
3437 that GCC is less likely to eliminate it as impossible. Patch
3438 from Mansour Moufid. Fixes bug 4059.
3440 o Minor bugfixes (usability):
3441 - Downgrade log messages about circuit timeout calibration from
3442 "notice" to "info": they don't require or suggest any human
3443 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3444 bugfix on 0.2.2.14-alpha.
3446 o Minor features (diagnostics):
3447 - When the system call to create a listener socket fails, log the
3448 error message explaining why. This may help diagnose bug 4027.
3451 Changes in version 0.2.3.4-alpha - 2011-09-13
3452 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3453 tweak to Tor's TLS handshake that makes relays and bridges that run
3454 this new version reachable from Iran again. It also fixes a few new
3455 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3456 listed in the network consensus and republish.
3458 o Major bugfixes (also part of 0.2.2.33):
3459 - Avoid an assertion failure when reloading a configuration with
3460 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3461 3923; bugfix on 0.2.2.25-alpha.
3463 o Minor features (security, also part of 0.2.2.33):
3464 - Check for replays of the public-key encrypted portion of an
3465 INTRODUCE1 cell, in addition to the current check for replays of
3466 the g^x value. This prevents a possible class of active attacks
3467 by an attacker who controls both an introduction point and a
3468 rendezvous point, and who uses the malleability of AES-CTR to
3469 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3470 that these attacks is infeasible (requiring the attacker to send
3471 on the order of zettabytes of altered cells in a short interval),
3472 but we'd rather block them off in case there are any classes of
3473 this attack that we missed. Reported by Willem Pinckaers.
3475 o Minor features (also part of 0.2.2.33):
3476 - Adjust the expiration time on our SSL session certificates to
3477 better match SSL certs seen in the wild. Resolves ticket 4014.
3478 - Change the default required uptime for a relay to be accepted as
3479 a HSDir (hidden service directory) from 24 hours to 25 hours.
3480 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3481 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3482 authorities to abstain from voting on assignment of the HSDir
3483 consensus flag. Related to bug 2649.
3484 - Update to the September 6 2011 Maxmind GeoLite Country database.
3486 o Minor bugfixes (also part of 0.2.2.33):
3487 - Demote the 'replay detected' log message emitted when a hidden
3488 service receives the same Diffie-Hellman public key in two different
3489 INTRODUCE2 cells to info level. A normal Tor client can cause that
3490 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3491 fixes part of bug 2442.
3492 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3493 level. There is nothing that a hidden service's operator can do
3494 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3496 - Clarify a log message specifying the characters permitted in
3497 HiddenServiceAuthorizeClient client names. Previously, the log
3498 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3499 given the impression that every ASCII character between "+" and "_"
3500 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3502 o Build fixes (also part of 0.2.2.33):
3503 - Clean up some code issues that prevented Tor from building on older
3504 BSDs. Fixes bug 3894; reported by "grarpamp".
3505 - Search for a platform-specific version of "ar" when cross-compiling.
3506 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3509 - Fix a bug where the SocksPort option (for example) would get
3510 ignored and replaced by the default if a SocksListenAddress
3511 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3515 - Relays now try regenerating and uploading their descriptor more
3516 frequently if they are not listed in the consensus, or if the
3517 version of their descriptor listed in the consensus is too
3518 old. This fix should prevent situations where a server declines
3519 to re-publish itself because it has done so too recently, even
3520 though the authorities decided not to list its recent-enough
3521 descriptor. Fix for bug 3327.
3524 - Relays now include a reason for regenerating their descriptors
3525 in an HTTP header when uploading to the authorities. This will
3526 make it easier to debug descriptor-upload issues in the future.
3527 - When starting as root and then changing our UID via the User
3528 control option, and we have a ControlSocket configured, make sure
3529 that the ControlSocket is owned by the same account that Tor will
3530 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3533 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
3534 utility function used in the control-port code). This shouldn't
3535 ever happen unless Tor is completely out of memory, but if it did
3536 happen and Tor somehow recovered from it, Tor could have sent a log
3537 message to a control port in the middle of a reply to a controller
3538 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3539 - Make 'FetchUselessDescriptors' cause all descriptor types and
3540 all consensus types (including microdescriptors) to get fetched.
3541 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
3544 - Make a new "entry connection" struct as an internal subtype of "edge
3545 connection", to simplify the code and make exit connections smaller.
3548 Changes in version 0.2.2.33 - 2011-09-13
3549 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3550 TLS handshake that makes relays and bridges that run this new version
3551 reachable from Iran again.
3554 - Avoid an assertion failure when reloading a configuration with
3555 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3556 3923; bugfix on 0.2.2.25-alpha.
3558 o Minor features (security):
3559 - Check for replays of the public-key encrypted portion of an
3560 INTRODUCE1 cell, in addition to the current check for replays of
3561 the g^x value. This prevents a possible class of active attacks
3562 by an attacker who controls both an introduction point and a
3563 rendezvous point, and who uses the malleability of AES-CTR to
3564 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3565 that these attacks are infeasible (requiring the attacker to send
3566 on the order of zettabytes of altered cells in a short interval),
3567 but we'd rather block them off in case there are any classes of
3568 this attack that we missed. Reported by Willem Pinckaers.
3571 - Adjust the expiration time on our SSL session certificates to
3572 better match SSL certs seen in the wild. Resolves ticket 4014.
3573 - Change the default required uptime for a relay to be accepted as
3574 a HSDir (hidden service directory) from 24 hours to 25 hours.
3575 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3576 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3577 authorities to abstain from voting on assignment of the HSDir
3578 consensus flag. Related to bug 2649.
3579 - Update to the September 6 2011 Maxmind GeoLite Country database.
3581 o Minor bugfixes (documentation and log messages):
3582 - Correct the man page to explain that HashedControlPassword and
3583 CookieAuthentication can both be set, in which case either method
3584 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3585 when we decided to allow these config options to both be set. Issue
3587 - Demote the 'replay detected' log message emitted when a hidden
3588 service receives the same Diffie-Hellman public key in two different
3589 INTRODUCE2 cells to info level. A normal Tor client can cause that
3590 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3591 fixes part of bug 2442.
3592 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3593 level. There is nothing that a hidden service's operator can do
3594 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3596 - Clarify a log message specifying the characters permitted in
3597 HiddenServiceAuthorizeClient client names. Previously, the log
3598 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3599 given the impression that every ASCII character between "+" and "_"
3600 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3603 - Provide a substitute implementation of lround() for MSVC, which
3604 apparently lacks it. Patch from Gisle Vanem.
3605 - Clean up some code issues that prevented Tor from building on older
3606 BSDs. Fixes bug 3894; reported by "grarpamp".
3607 - Search for a platform-specific version of "ar" when cross-compiling.
3608 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3611 Changes in version 0.2.3.3-alpha - 2011-09-01
3612 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
3613 security, and provides client-side support for the microdescriptor
3614 and optimistic data features introduced earlier in the 0.2.3.x
3615 series. It also includes numerous critical bugfixes in the (optional)
3616 bufferevent-based networking backend.
3618 o Major features (stream isolation):
3619 - You can now configure Tor so that streams from different
3620 applications are isolated on different circuits, to prevent an
3621 attacker who sees your streams as they leave an exit node from
3622 linking your sessions to one another. To do this, choose some way
3623 to distinguish the applications: have them connect to different
3624 SocksPorts, or have one of them use SOCKS4 while the other uses
3625 SOCKS5, or have them pass different authentication strings to the
3626 SOCKS proxy. Then, use the new SocksPort syntax to configure the
3627 degree of isolation you need. This implements Proposal 171.
3628 - There's a new syntax for specifying multiple client ports (such as
3629 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
3630 multiple *Port entries with full addr:port syntax on each.
3631 The old *ListenAddress format is still supported, but you can't
3632 mix it with the new *Port syntax.
3634 o Major features (other):
3635 - Enable microdescriptor fetching by default for clients. This allows
3636 clients to download a much smaller amount of directory information.
3637 To disable it (and go back to the old-style consensus and
3638 descriptors), set "UseMicrodescriptors 0" in your torrc file.
3639 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
3640 "PortForwarding" config option), now supports Windows.
3641 - When using an exit relay running 0.2.3.x, clients can now
3642 "optimistically" send data before the exit relay reports that
3643 the stream has opened. This saves a round trip when starting
3644 connections where the client speaks first (such as web browsing).
3645 This behavior is controlled by a consensus parameter (currently
3646 disabled). To turn it on or off manually, use the "OptimisticData"
3647 torrc option. Implements proposal 181; code by Ian Goldberg.
3649 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
3650 - When using IOCP on Windows, we need to enable Libevent windows
3652 - The IOCP backend now works even when the user has not specified
3653 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
3654 Fixes part of bug 3752.
3655 - Correctly record the bytes we've read and written when using
3656 bufferevents, so that we can include them in our bandwidth history
3657 and advertised bandwidth. Fixes bug 3803.
3658 - Apply rate-limiting only at the bottom of a chain of filtering
3659 bufferevents. This prevents us from filling up internal read
3660 buffers and violating rate-limits when filtering bufferevents
3661 are enabled. Fixes part of bug 3804.
3662 - Add high-watermarks to the output buffers for filtered
3663 bufferevents. This prevents us from filling up internal write
3664 buffers and wasting CPU cycles when filtering bufferevents are
3665 enabled. Fixes part of bug 3804.
3666 - Correctly notice when data has been written from a bufferevent
3667 without flushing it completely. Fixes bug 3805.
3668 - Fix a bug where server-side tunneled bufferevent-based directory
3669 streams would get closed prematurely. Fixes bug 3814.
3670 - Fix a use-after-free error with per-connection rate-limiting
3671 buckets. Fixes bug 3888.
3673 o Major bugfixes (also part of 0.2.2.31-rc):
3674 - If we're configured to write our ControlPorts to disk, only write
3675 them after switching UID and creating the data directory. This way,
3676 we don't fail when starting up with a nonexistent DataDirectory
3677 and a ControlPortWriteToFile setting based on that directory. Fixes
3678 bug 3747; bugfix on Tor 0.2.2.26-beta.
3681 - Added a new CONF_CHANGED event so that controllers can be notified
3682 of any configuration changes made by other controllers, or by the
3683 user. Implements ticket 1692.
3684 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
3685 leak when using bufferevents, and lets Libevent worry about how to
3686 best copy data out of a buffer.
3687 - Replace files in stats/ rather than appending to them. Now that we
3688 include statistics in extra-info descriptors, it makes no sense to
3689 keep old statistics forever. Implements ticket 2930.
3691 o Minor features (build compatibility):
3692 - Limited, experimental support for building with nmake and MSVC.
3693 - Provide a substitute implementation of lround() for MSVC, which
3694 apparently lacks it. Patch from Gisle Vanem.
3696 o Minor features (also part of 0.2.2.31-rc):
3697 - Update to the August 2 2011 Maxmind GeoLite Country database.
3699 o Minor bugfixes (on 0.2.3.x-alpha):
3700 - Fix a spurious warning when parsing SOCKS requests with
3701 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
3702 - Get rid of a harmless warning that could happen on relays running
3703 with bufferevents. The warning was caused by someone doing an http
3704 request to a relay's orport. Also don't warn for a few related
3705 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
3707 o Minor bugfixes (on 2.2.x and earlier):
3708 - Correct the man page to explain that HashedControlPassword and
3709 CookieAuthentication can both be set, in which case either method
3710 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3711 when we decided to allow these config options to both be set. Issue
3713 - The "--quiet" and "--hush" options now apply not only to Tor's
3714 behavior before logs are configured, but also to Tor's behavior in
3715 the absense of configured logs. Fixes bug 3550; bugfix on
3718 o Minor bugfixes (also part of 0.2.2.31-rc):
3719 - Write several files in text mode, on OSes that distinguish text
3720 mode from binary mode (namely, Windows). These files are:
3721 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3722 that collect those statistics; 'client_keys' and 'hostname' for
3723 hidden services that use authentication; and (in the tor-gencert
3724 utility) newly generated identity and signing keys. Previously,
3725 we wouldn't specify text mode or binary mode, leading to an
3726 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3727 the DirRecordUsageByCountry option which would have triggered
3728 the assertion failure was added), although this assertion failure
3729 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3730 - Selectively disable deprecation warnings on OS X because Lion
3731 started deprecating the shipped copy of openssl. Fixes bug 3643.
3732 - Remove an extra pair of quotation marks around the error
3733 message in control-port STATUS_GENERAL BUG events. Bugfix on
3734 0.1.2.6-alpha; fixes bug 3732.
3735 - When unable to format an address as a string, report its value
3736 as "???" rather than reusing the last formatted address. Bugfix
3739 o Code simplifications and refactoring:
3740 - Rewrite the listener-selection logic so that parsing which ports
3741 we want to listen on is now separate from binding to the ports
3745 - Building Tor with bufferevent support now requires Libevent
3746 2.0.13-stable or later. Previous versions of Libevent had bugs in
3747 SSL-related bufferevents and related issues that would make Tor
3748 work badly with bufferevents. Requiring 2.0.13-stable also allows
3749 Tor with bufferevents to take advantage of Libevent APIs
3750 introduced after 2.0.8-rc.
3753 Changes in version 0.2.2.32 - 2011-08-27
3754 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3755 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3756 a founder of the PETS community, a leader in our field, a mentor,
3757 and a friend. He left us with these words: "I had the possibility
3758 to contribute to this world that is not as it should be. I hope I
3759 could help in some areas to make the world a better place, and that
3760 I could also encourage other people to be engaged in improving the
3761 world. Please, stay engaged. This world needs you, your love, your
3762 initiative -- now I cannot be part of that anymore."
3764 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3765 ready. More than two years in the making, this release features improved
3766 client performance and hidden service reliability, better compatibility
3767 for Android, correct behavior for bridges that listen on more than
3768 one address, more extensible and flexible directory object handling,
3769 better reporting of network statistics, improved code security, and
3770 many many other features and bugfixes.
3773 Changes in version 0.2.2.31-rc - 2011-08-17
3774 Tor 0.2.2.31-rc is the second and hopefully final release candidate
3775 for the Tor 0.2.2.x series.
3778 - Remove an extra pair of quotation marks around the error
3779 message in control-port STATUS_GENERAL BUG events. Bugfix on
3780 0.1.2.6-alpha; fixes bug 3732.
3781 - If we're configured to write our ControlPorts to disk, only write
3782 them after switching UID and creating the data directory. This way,
3783 we don't fail when starting up with a nonexistent DataDirectory
3784 and a ControlPortWriteToFile setting based on that directory. Fixes
3785 bug 3747; bugfix on Tor 0.2.2.26-beta.
3788 - Update to the August 2 2011 Maxmind GeoLite Country database.
3791 - Allow GETINFO fingerprint to return a fingerprint even when
3792 we have not yet built a router descriptor. Fixes bug 3577;
3793 bugfix on 0.2.0.1-alpha.
3794 - Write several files in text mode, on OSes that distinguish text
3795 mode from binary mode (namely, Windows). These files are:
3796 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3797 that collect those statistics; 'client_keys' and 'hostname' for
3798 hidden services that use authentication; and (in the tor-gencert
3799 utility) newly generated identity and signing keys. Previously,
3800 we wouldn't specify text mode or binary mode, leading to an
3801 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3802 the DirRecordUsageByCountry option which would have triggered
3803 the assertion failure was added), although this assertion failure
3804 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3805 - Selectively disable deprecation warnings on OS X because Lion
3806 started deprecating the shipped copy of openssl. Fixes bug 3643.
3807 - When unable to format an address as a string, report its value
3808 as "???" rather than reusing the last formatted address. Bugfix
3812 Changes in version 0.2.3.2-alpha - 2011-07-18
3813 Tor 0.2.3.2-alpha introduces two new experimental features:
3814 microdescriptors and pluggable transports. It also continues cleaning
3815 up a variety of recently introduced features.
3818 - Clients can now use microdescriptors instead of regular descriptors
3819 to build circuits. Microdescriptors are authority-generated
3820 summaries of regular descriptors' contents, designed to change
3821 very rarely (see proposal 158 for details). This feature is
3822 designed to save bandwidth, especially for clients on slow internet
3823 connections. It's off by default for now, since nearly no caches
3824 support it, but it will be on-by-default for clients in a future
3825 version. You can use the UseMicrodescriptors option to turn it on.
3826 - Tor clients using bridges can now be configured to use a separate
3827 'transport' proxy for each bridge. This approach helps to resist
3828 censorship by allowing bridges to use protocol obfuscation
3829 plugins. It implements part of proposal 180. Implements ticket 2841.
3830 - While we're trying to bootstrap, record how many TLS connections
3831 fail in each state, and report which states saw the most failures
3832 in response to any bootstrap failures. This feature may speed up
3833 diagnosis of censorship events. Implements ticket 3116.
3835 o Major bugfixes (on 0.2.3.1-alpha):
3836 - When configuring a large set of nodes in EntryNodes (as with
3837 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
3838 random subset to be guards, and choose them in random
3839 order. Fixes bug 2798.
3840 - Tor could crash when remembering a consensus in a non-used consensus
3841 flavor without having a current consensus set. Fixes bug 3361.
3842 - Comparing an unknown address to a microdescriptor's shortened exit
3843 policy would always give a "rejected" result. Fixes bug 3599.
3844 - Using microdescriptors as a client no longer prevents Tor from
3845 uploading and downloading hidden service descriptors. Fixes
3849 - Allow nameservers with IPv6 address. Resolves bug 2574.
3850 - Accept attempts to include a password authenticator in the
3851 handshake, as supported by SOCKS5. This handles SOCKS clients that
3852 don't know how to omit a password when authenticating. Resolves
3854 - When configuring a large set of nodes in EntryNodes, and there are
3855 enough of them listed as Guard so that we don't need to consider
3856 the non-guard entries, prefer the ones listed with the Guard flag.
3857 - Check for and recover from inconsistency in the microdescriptor
3858 cache. This will make it harder for us to accidentally free a
3859 microdescriptor without removing it from the appropriate data
3860 structures. Fixes issue 3135; issue noted by "wanoskarnet".
3861 - Log SSL state transitions at log level DEBUG, log domain
3862 HANDSHAKE. This can be useful for debugging censorship events.
3863 Implements ticket 3264.
3864 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
3865 implements ticket 3439.
3867 o Minor bugfixes (on 0.2.3.1-alpha):
3868 - Do not free all general-purpose regular descriptors just
3869 because microdescriptor use is enabled. Fixes bug 3113.
3870 - Correctly link libevent_openssl when --enable-static-libevent
3871 is passed to configure. Fixes bug 3118.
3872 - Bridges should not complain during their heartbeat log messages that
3873 they are unlisted in the consensus: that's more or less the point
3874 of being a bridge. Fixes bug 3183.
3875 - Report a SIGNAL event to controllers when acting on a delayed
3876 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
3877 event to the controller if we acted on a SIGNAL NEWNYM command
3878 immediately, and otherwise not report a SIGNAL event for the
3879 command at all. Fixes bug 3349.
3880 - Fix a crash when handling the SIGNAL controller command or
3881 reporting ERR-level status events with bufferevents enabled. Found
3882 by Robert Ransom. Fixes bug 3367.
3883 - Always ship the tor-fw-helper manpage in our release tarballs.
3884 Fixes bug 3389. Reported by Stephen Walker.
3885 - Fix a class of double-mark-for-close bugs when bufferevents
3886 are enabled. Fixes bug 3403.
3887 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
3888 - Add SIGNAL to the list returned by the 'GETINFO events/names'
3889 control-port command. Fixes part of bug 3465.
3890 - Prevent using negative indices during unit test runs when read_all()
3891 fails. Spotted by coverity.
3892 - Fix a rare memory leak when checking the nodelist without it being
3893 present. Found by coverity.
3894 - Only try to download a microdescriptor-flavored consensus from
3895 a directory cache that provides them.
3897 o Minor bugfixes (on 0.2.2.x and earlier):
3898 - Assert that hidden-service-related operations are not performed
3899 using single-hop circuits. Previously, Tor would assert that
3900 client-side streams are not attached to single-hop circuits,
3901 but not that other sensitive operations on the client and service
3902 side are not performed using single-hop circuits. Fixes bug 3332;
3904 - Don't publish a new relay descriptor when we reload our onion key,
3905 unless the onion key has actually changed. Fixes bug 3263 and
3906 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
3907 - Allow GETINFO fingerprint to return a fingerprint even when
3908 we have not yet built a router descriptor. Fixes bug 3577;
3909 bugfix on 0.2.0.1-alpha.
3910 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
3911 on 0.2.2.4-alpha; fixes bug 3427.
3913 o Code simplification and refactoring:
3914 - Use tor_sscanf() in place of scanf() in more places through the
3915 code. This makes us a little more locale-independent, and
3916 should help shut up code-analysis tools that can't tell
3917 a safe sscanf string from a dangerous one.
3918 - Use tt_assert(), not tor_assert(), for checking for test failures.
3919 This makes the unit tests more able to go on in the event that
3921 - Split connection_about_to_close() into separate functions for each
3925 - On Windows, we now define the _WIN32_WINNT macros only if they
3926 are not already defined. This lets the person building Tor decide,
3927 if they want, to require a later version of Windows.
3930 Changes in version 0.2.2.30-rc - 2011-07-07
3931 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
3932 series. It fixes a few smaller bugs, but generally appears stable.
3933 Please test it and let us know whether it is!
3936 - Send a SUCCEEDED stream event to the controller when a reverse
3937 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3938 discovered by katmagic.
3939 - Always NUL-terminate the sun_path field of a sockaddr_un before
3940 passing it to the kernel. (Not a security issue: kernels are
3941 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3942 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3943 - Don't stack-allocate the list of supplementary GIDs when we're
3944 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3945 could take up to 256K, which is way too much stack. Found by
3946 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3947 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
3948 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
3949 fixes part of bug 3465.
3950 - Fix a memory leak when receiving a descriptor for a hidden
3951 service we didn't ask for. Found by Coverity; CID #30. Bugfix
3955 - Update to the July 1 2011 Maxmind GeoLite Country database.
3958 Changes in version 0.2.2.29-beta - 2011-06-20
3959 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
3960 have bridge lines in their torrc but don't want to use them; gets
3961 us closer to having the control socket feature working on Debian;
3962 and fixes a variety of smaller bugs.
3965 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
3966 When we changed the default behavior to "use bridges if any
3967 are listed in the torrc", we surprised users who had bridges
3968 in their torrc files but who didn't actually want to use them.
3969 Partial resolution for bug 3354.
3972 - Don't attach new streams to old rendezvous circuits after SIGNAL
3973 NEWNYM. Previously, we would keep using an existing rendezvous
3974 circuit if it remained open (i.e. if it were kept open by a
3975 long-lived stream, or if a new stream were attached to it before
3976 Tor could notice that it was old and no longer in use). Bugfix on
3977 0.1.1.15-rc; fixes bug 3375.
3980 - Fix a bug when using ControlSocketsGroupWritable with User. The
3981 directory's group would be checked against the current group, not
3982 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
3983 bugfix on 0.2.2.26-beta.
3984 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3985 expect it to emit a CRLF iff the format string ends with CRLF;
3986 it actually emitted a CRLF iff (a) the format string ended with
3987 CRLF or (b) the resulting string was over 1023 characters long or
3988 (c) the format string did not end with CRLF *and* the resulting
3989 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3990 fixes part of bug 3407.
3991 - Make send_control_event_impl()'s behaviour sane. Its callers
3992 expect it to always emit a CRLF at the end of the string; it
3993 might have emitted extra control characters as well. Bugfix on
3994 0.1.1.9-alpha; fixes another part of bug 3407.
3995 - Make crypto_rand_int() check the value of its input correctly.
3996 Previously, it accepted values up to UINT_MAX, but could return a
3997 negative number if given a value above INT_MAX+1. Found by George
3998 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3999 - Avoid a segfault when reading a malformed circuit build state
4000 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4002 - When asked about a DNS record type we don't support via a
4003 client DNSPort, reply with NOTIMPL rather than an empty
4004 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4005 - Fix a rare memory leak during stats writing. Found by coverity.
4008 - Update to the June 1 2011 Maxmind GeoLite Country database.
4010 o Code simplifications and refactoring:
4011 - Remove some dead code as indicated by coverity.
4012 - Remove a few dead assignments during router parsing. Found by
4014 - Add some forgotten return value checks during unit tests. Found
4016 - Don't use 1-bit wide signed bit fields. Found by coverity.
4019 Changes in version 0.2.2.28-beta - 2011-06-04
4020 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4021 fixed a big bug in whether relays stay in the consensus consistently,
4022 we moved closer to handling bridges and hidden services correctly,
4023 and we started the process of better handling the dreaded "my Vidalia
4024 died, and now my Tor demands a password when I try to reconnect to it"
4028 - Don't decide to make a new descriptor when receiving a HUP signal.
4029 This bug has caused a lot of 0.2.2.x relays to disappear from the
4030 consensus periodically. Fixes the most common case of triggering
4031 bug 1810; bugfix on 0.2.2.7-alpha.
4032 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4033 - Don't try to build descriptors if "ORPort auto" is set and we
4034 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4036 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4037 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4038 - Apply circuit timeouts to opened hidden-service-related circuits
4039 based on the correct start time. Previously, we would apply the
4040 circuit build timeout based on time since the circuit's creation;
4041 it was supposed to be applied based on time since the circuit
4042 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4043 - Use the same circuit timeout for client-side introduction
4044 circuits as for other four-hop circuits, rather than the timeout
4045 for single-hop directory-fetch circuits; the shorter timeout may
4046 have been appropriate with the static circuit build timeout in
4047 0.2.1.x and earlier, but caused many hidden service access attempts
4048 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4049 on 0.2.2.2-alpha; fixes another part of bug 1297.
4050 - In ticket 2511 we fixed a case where you could use an unconfigured
4051 bridge if you had configured it as a bridge the last time you ran
4052 Tor. Now fix another edge case: if you had configured it as a bridge
4053 but then switched to a different bridge via the controller, you
4054 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4058 - Add an __OwningControllerProcess configuration option and a
4059 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4060 that when it exits, Tor will shut down. Implements feature 3049.
4061 - If "UseBridges 1" is set and no bridges are configured, Tor will
4062 now refuse to build any circuits until some bridges are set.
4063 If "UseBridges auto" is set, Tor will use bridges if they are
4064 configured and we are not running as a server, but otherwise will
4065 make circuits as usual. The new default is "auto". Patch by anonym,
4066 so the Tails LiveCD can stop automatically revealing you as a Tor
4070 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4071 - Remove a trailing asterisk from "exit-policy/default" in the
4072 output of the control port command "GETINFO info/names". Bugfix
4074 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4076 - Warn when the user configures two HiddenServiceDir lines that point
4077 to the same directory. Bugfix on 0.0.6 (the version introducing
4078 HiddenServiceDir); fixes bug 3289.
4079 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4080 part of bug 2748; bugfix on 0.2.0.10-alpha.
4081 - Log malformed requests for rendezvous descriptors as protocol
4082 warnings, not warnings. Also, use a more informative log message
4083 in case someone sees it at log level warning without prior
4084 info-level messages. Fixes the other part of bug 2748; bugfix
4086 - Clear the table recording the time of the last request for each
4087 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4088 Previously, we would clear our HS descriptor cache on SIGNAL
4089 NEWNYM, but if we had previously retrieved a descriptor (or tried
4090 to) from every directory responsible for it, we would refuse to
4091 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4093 - Fix a log message that said "bits" while displaying a value in
4094 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4096 - When checking for 1024-bit keys, check for 1024 bits, not 128
4097 bytes. This allows Tor to correctly discard keys of length 1017
4098 through 1023. Bugfix on 0.0.9pre5.
4101 - Relays now log the reason for publishing a new relay descriptor,
4102 so we have a better chance of hunting down instances of bug 1810.
4103 Resolves ticket 3252.
4104 - Revise most log messages that refer to nodes by nickname to
4105 instead use the "$key=nickname at address" format. This should be
4106 more useful, especially since nicknames are less and less likely
4107 to be unique. Resolves ticket 3045.
4108 - Log (at info level) when purging pieces of hidden-service-client
4109 state because of SIGNAL NEWNYM.
4112 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4113 anything since 0.2.1.16-rc.
4116 Changes in version 0.2.2.27-beta - 2011-05-18
4117 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4118 release, and also adds a few more general bugfixes.
4121 - Fix a crash bug when changing bridges in a running Tor process.
4122 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4123 - When the controller configures a new bridge, don't wait 10 to 60
4124 seconds before trying to fetch its descriptor. Bugfix on
4125 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4128 - Require that onion keys have exponent 65537 in microdescriptors too.
4129 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4130 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4131 Changed the limit to 512 characters by removing base64 newlines.
4132 Fixes bug 2752. Fix by Michael Yakubovich.
4133 - When a client starts or stops using bridges, never use a circuit
4134 that was built before the configuration change. This behavior could
4135 put at risk a user who uses bridges to ensure that her traffic
4136 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4140 Changes in version 0.2.2.26-beta - 2011-05-17
4141 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4142 also introduces a new "socksport auto" approach that should make it
4143 easier to run multiple Tors on the same system, and does a lot of
4144 cleanup to get us closer to a release candidate.
4146 o Security/privacy fixes:
4147 - Replace all potentially sensitive memory comparison operations
4148 with versions whose runtime does not depend on the data being
4149 compared. This will help resist a class of attacks where an
4150 adversary can use variations in timing information to learn
4151 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4152 implementation by Robert Ransom based partially on code by DJB.)
4153 - When receiving a hidden service descriptor, check that it is for
4154 the hidden service we wanted. Previously, Tor would store any
4155 hidden service descriptors that a directory gave it, whether it
4156 wanted them or not. This wouldn't have let an attacker impersonate
4157 a hidden service, but it did let directories pre-seed a client
4158 with descriptors that it didn't want. Bugfix on 0.0.6.
4159 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4160 DNS cache entries, and virtual address mappings: that's what
4161 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4164 - The options SocksPort, ControlPort, and so on now all accept a
4165 value "auto" that opens a socket on an OS-selected port. A
4166 new ControlPortWriteToFile option tells Tor to write its
4167 actual control port or ports to a chosen file. If the option
4168 ControlPortFileGroupReadable is set, the file is created as
4169 group-readable. Now users can run two Tor clients on the same
4170 system without needing to manually mess with parameters. Resolves
4171 part of ticket 3076.
4172 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4173 help busy exit nodes avoid running out of useable ports just
4174 because all the ports have been used in the near past. Resolves
4178 - New "GETINFO net/listeners/(type)" controller command to return
4179 a list of addresses and ports that are bound for listeners for a
4180 given connection type. This is useful when the user has configured
4181 "SocksPort auto" and the controller needs to know which port got
4182 chosen. Resolves another part of ticket 3076.
4183 - Add a new ControlSocketsGroupWritable configuration option: when
4184 it is turned on, ControlSockets are group-writeable by the default
4185 group of the current user. Patch by Jérémy Bobbio; implements
4187 - Tor now refuses to create a ControlSocket in a directory that is
4188 world-readable (or group-readable if ControlSocketsGroupWritable
4189 is 0). This is necessary because some operating systems do not
4190 enforce permissions on an AF_UNIX sockets. Permissions on the
4191 directory holding the socket, however, seems to work everywhere.
4192 - Rate-limit a warning about failures to download v2 networkstatus
4193 documents. Resolves part of bug 1352.
4194 - Backport code from 0.2.3.x that allows directory authorities to
4195 clean their microdescriptor caches. Needed to resolve bug 2230.
4196 - When an HTTPS proxy reports "403 Forbidden", we now explain
4197 what it means rather than calling it an unexpected status code.
4198 Closes bug 2503. Patch from Michael Yakubovich.
4199 - Update to the May 1 2011 Maxmind GeoLite Country database.
4202 - Authorities now clean their microdesc cache periodically and when
4203 reading from disk initially, not only when adding new descriptors.
4204 This prevents a bug where we could lose microdescriptors. Bugfix
4205 on 0.2.2.6-alpha. Fixes bug 2230.
4206 - Do not crash when our configuration file becomes unreadable, for
4207 example due to a permissions change, between when we start up
4208 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4210 - Avoid a bug that would keep us from replacing a microdescriptor
4211 cache on Windows. (We would try to replace the file while still
4212 holding it open. That's fine on Unix, but Windows doesn't let us
4213 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4214 - Add missing explanations for the authority-related torrc options
4215 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4216 man page. Resolves issue 2379.
4217 - As an authority, do not upload our own vote or signature set to
4218 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4219 it would get flagged as a duplicate. Resolves bug 3026.
4220 - Accept hidden service descriptors if we think we might be a hidden
4221 service directory, regardless of what our consensus says. This
4222 helps robustness, since clients and hidden services can sometimes
4223 have a more up-to-date view of the network consensus than we do,
4224 and if they think that the directory authorities list us a HSDir,
4225 we might actually be one. Related to bug 2732; bugfix on
4227 - When a controller changes TrackHostExits, remove mappings for
4228 hosts that should no longer have their exits tracked. Bugfix on
4230 - When a controller changes VirtualAddrNetwork, remove any mappings
4231 for hosts that were automapped to the old network. Bugfix on
4233 - When a controller changes one of the AutomapHosts* options, remove
4234 any mappings for hosts that should no longer be automapped. Bugfix
4236 - Do not reset the bridge descriptor download status every time we
4237 re-parse our configuration or get a configuration change. Fixes
4238 bug 3019; bugfix on 0.2.0.3-alpha.
4240 o Minor bugfixes (code cleanup):
4241 - When loading the microdesc journal, remember its current size.
4242 In 0.2.2, this helps prevent the microdesc journal from growing
4243 without limit on authorities (who are the only ones to use it in
4244 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4245 Fix posted by "cypherpunks."
4246 - The microdesc journal is supposed to get rebuilt only if it is
4247 at least _half_ the length of the store, not _twice_ the length
4248 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4249 - Fix a potential null-pointer dereference while computing a
4250 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4252 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4253 cache without actually having any descriptors to cache. Bugfix on
4254 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4255 - If we fail to compute the identity digest of a v3 legacy keypair,
4256 warn, and don't use a buffer-full of junk instead. Bugfix on
4257 0.2.1.1-alpha; fixes bug 3106.
4258 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4259 where if the function had ever in the future been used to check
4260 for the presence of a too-large number, it would have given an
4261 incorrect result. (Fortunately, we only used it for 16-bit
4262 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4263 - Require that introduction point keys and onion handshake keys
4264 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4268 - Caches no longer download and serve v2 networkstatus documents
4269 unless FetchV2Networkstatus flag is set: these documents haven't
4270 haven't been used by clients or relays since 0.2.0.x. Resolves
4274 Changes in version 0.2.3.1-alpha - 2011-05-05
4275 Tor 0.2.3.1-alpha adds some new experimental features, including support
4276 for an improved network IO backend, IOCP networking on Windows,
4277 microdescriptor caching, "fast-start" support for streams, and automatic
4278 home router configuration. There are also numerous internal improvements
4279 to try to make the code easier for developers to work with.
4281 This is the first alpha release in a new series, so expect there to be
4282 bugs. Users who would rather test out a more stable branch should
4283 stay with 0.2.2.x for now.
4286 - Tor can now optionally build with the "bufferevents" buffered IO
4287 backend provided by Libevent 2. To use this feature, make sure you
4288 have the latest possible version of Libevent, and pass the
4289 --enable-bufferevents flag to configure when building Tor from
4290 source. This feature will make our networking code more flexible,
4291 let us stack layers on each other, and let us use more efficient
4292 zero-copy transports where available.
4293 - As an experimental feature, Tor can use IOCP for networking on Windows.
4294 Once this code is tuned and optimized, it promises much better
4295 performance than the select-based backend we've used in the past. To
4296 try this feature, you must build Tor with Libevent 2, configure Tor
4297 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4298 your torrc. There are known bugs here: only try this if you can help
4299 debug it as it breaks.
4300 - The EntryNodes option can now include country codes like {de} or IP
4301 addresses or network masks. Previously we had disallowed these options
4302 because we didn't have an efficient way to keep the list up to
4303 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4304 - Exit nodes now accept and queue data on not-yet-connected streams.
4305 Previously, the client wasn't allowed to send data until the stream was
4306 connected, which slowed down all connections. This change will enable
4307 clients to perform a "fast-start" on streams and send data without
4308 having to wait for a confirmation that the stream has opened. (Patch
4309 from Ian Goldberg; implements the server side of Proposal 174.)
4310 - Tor now has initial support for automatic port mapping on the many
4311 home routers that support NAT-PMP or UPnP. (Not yet supported on
4312 Windows). To build the support code, you'll need to have libnatpnp
4313 library and/or the libminiupnpc library, and you'll need to enable the
4314 feature specifically by passing "--enable-upnp" and/or
4315 "--enable-natpnp" to configure. To turn it on, use the new
4316 PortForwarding option.
4317 - Caches now download, cache, and serve multiple "flavors" of the
4318 consensus, including a flavor that describes microdescriptors.
4319 - Caches now download, cache, and serve microdescriptors -- small
4320 summaries of router descriptors that are authenticated by all of the
4321 directory authorities. Once enough caches are running this code,
4322 clients will be able to save significant amounts of directory bandwidth
4323 by downloading microdescriptors instead of router descriptors.
4326 - Make logging resolution configurable with a new LogTimeGranularity
4327 option, and change the default from 1 millisecond to 1 second.
4328 Implements enhancement 1668.
4329 - We log which torrc file we're using on startup. Implements ticket
4331 - Ordinarily, Tor does not count traffic from private addresses (like
4332 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4333 There is now a new option, CountPrivateBandwidth, to disable this
4334 behavior. Patch from Daniel Cagara.
4335 - New --enable-static-tor configure option for building Tor as
4336 statically as possible. Idea, general hackery and thoughts from
4337 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4339 - If you set the NumCPUs option to 0, Tor will now try to detect how
4340 many CPUs you have. This is the new default behavior.
4341 - Turn on directory request statistics by default and include them in
4342 extra-info descriptors. Don't break if we have no GeoIP database.
4343 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4344 bidirectional use of connections to disk every 24 hours.
4345 - Add a GeoIP file digest to the extra-info descriptor. Implements
4347 - The NodeFamily option -- which let you declare that you want to
4348 consider nodes to be part of a family whether they list themselves
4349 that way or not -- now allows IP address ranges and country codes.
4350 - Add a new 'Heartbeat' log message type to periodically log a message
4351 describing Tor's status at level Notice. This feature is meant for
4352 operators who log at notice, and want to make sure that their Tor
4353 server is still working. Implementation by George Kadianakis.
4355 o Minor bugfixes (on 0.2.2.25-alpha):
4356 - When loading the microdesc journal, remember its current size.
4357 In 0.2.2, this helps prevent the microdesc journal from growing
4358 without limit on authorities (who are the only ones to use it in
4359 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4360 Fix posted by "cypherpunks."
4361 - The microdesc journal is supposed to get rebuilt only if it is
4362 at least _half_ the length of the store, not _twice_ the length
4363 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4364 - If as an authority we fail to compute the identity digest of a v3
4365 legacy keypair, warn, and don't use a buffer-full of junk instead.
4366 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4367 - Authorities now clean their microdesc cache periodically and when
4368 reading from disk initially, not only when adding new descriptors.
4369 This prevents a bug where we could lose microdescriptors. Bugfix
4372 o Minor features (controller):
4373 - Add a new SIGNAL event to the controller interface so that
4374 controllers can be notified when Tor handles a signal. Resolves
4375 issue 1955. Patch by John Brooks.
4376 - Add a new GETINFO option to get total bytes read and written. Patch
4377 from pipe, revised by atagar. Resolves ticket 2345.
4378 - Implement some GETINFO controller fields to provide information about
4379 the Tor process's pid, euid, username, and resource limits.
4382 - Our build system requires automake 1.6 or later to create the
4383 Makefile.in files. Previously, you could have used 1.4.
4384 This only affects developers and people building Tor from git;
4385 people who build Tor from the source distribution without changing
4386 the Makefile.am files should be fine.
4387 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4388 so on. This is more robust against some of the failure modes
4389 associated with running the autotools pieces on their own.
4391 o Minor packaging issues:
4392 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4393 already created. Patch from Andreas Stieger. Fixes bug 2573.
4395 o Code simplifications and refactoring:
4396 - A major revision to our internal node-selecting and listing logic.
4397 Tor already had at least two major ways to look at the question of
4398 "which Tor servers do we know about": a list of router descriptors,
4399 and a list of entries in the current consensus. With
4400 microdescriptors, we're adding a third. Having so many systems
4401 without an abstraction layer over them was hurting the codebase.
4402 Now, we have a new "node_t" abstraction that presents a consistent
4403 interface to a client's view of a Tor node, and holds (nearly) all
4404 of the mutable state formerly in routerinfo_t and routerstatus_t.
4405 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4406 no longer link against Libevent: they never used it, but
4407 our library structure used to force them to link it.
4410 - Remove some old code to work around even older versions of Tor that
4411 used forked processes to handle DNS requests. Such versions of Tor
4412 are no longer in use as servers.
4414 o Documentation fixes:
4415 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4416 - Add missing documentation for the authority-related torrc options
4417 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4421 Changes in version 0.2.2.25-alpha - 2011-04-29
4422 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4423 robust, routers no longer overreport their bandwidth, Win7 should crash
4424 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4425 now prevents hidden service-related activity from being linkable. It
4426 provides more information to Vidalia so you can see if your bridge is
4427 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4428 StrictNodes configuration options to make them more reliable, more
4429 understandable, and more regularly applied. If you use those options,
4430 please see the revised documentation for them in the manual page.
4433 - Relays were publishing grossly inflated bandwidth values because
4434 they were writing their state files wrong--now they write the
4435 correct value. Also, resume reading bandwidth history from the
4436 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4437 - Improve hidden service robustness: When we find that we have
4438 extended a hidden service's introduction circuit to a relay not
4439 listed as an introduction point in the HS descriptor we currently
4440 have, retry with an introduction point from the current
4441 descriptor. Previously we would just give up. Fixes bugs 1024 and
4442 1930; bugfix on 0.2.0.10-alpha.
4443 - Clients now stop trying to use an exit node associated with a given
4444 destination by TrackHostExits if they fail to reach that exit node.
4445 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4446 - Fix crash bug on platforms where gmtime and localtime can return
4447 NULL. Windows 7 users were running into this one. Fixes part of bug
4448 2077. Bugfix on all versions of Tor. Found by boboper.
4450 o Security and stability fixes:
4451 - Don't double-free a parsable, but invalid, microdescriptor, even if
4452 it is followed in the blob we're parsing by an unparsable
4453 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4454 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4455 - If the Nickname configuration option isn't given, Tor would pick a
4456 nickname based on the local hostname as the nickname for a relay.
4457 Because nicknames are not very important in today's Tor and the
4458 "Unnamed" nickname has been implemented, this is now problematic
4459 behavior: It leaks information about the hostname without being
4460 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4461 introduced the Unnamed nickname. Reported by tagnaq.
4462 - Fix an uncommon assertion failure when running with DNSPort under
4463 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4464 - Avoid linkability based on cached hidden service descriptors: forget
4465 all hidden service descriptors cached as a client when processing a
4466 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4469 - Export GeoIP information on bridge usage to controllers even if we
4470 have not yet been running for 24 hours. Now Vidalia bridge operators
4471 can get more accurate and immediate feedback about their
4472 contributions to the network.
4474 o Major features and bugfixes (node selection):
4475 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4476 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4477 options. Previously, we had been ambiguous in describing what
4478 counted as an "exit" node, and what operations exactly "StrictNodes
4479 0" would permit. This created confusion when people saw nodes built
4480 through unexpected circuits, and made it hard to tell real bugs from
4481 surprises. Now the intended behavior is:
4482 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4483 a node that delivers user traffic outside the Tor network.
4484 . "Entry", in the context of EntryNodes, means a node used as the
4485 first hop of a multihop circuit. It doesn't include direct
4486 connections to directory servers.
4487 . "ExcludeNodes" applies to all nodes.
4488 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4489 StrictNodes is set, Tor should avoid all nodes listed in
4490 ExcludeNodes, even when it will make user requests fail. When
4491 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4492 whenever it can, except when it must use an excluded node to
4493 perform self-tests, connect to a hidden service, provide a
4494 hidden service, fulfill a .exit request, upload directory
4495 information, or fetch directory information.
4496 Collectively, the changes to implement the behavior fix bug 1090.
4497 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4498 a node is listed in both, it's treated as excluded.
4499 - ExcludeNodes now applies to directory nodes -- as a preference if
4500 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4501 Don't exclude all the directory authorities and set StrictNodes to 1
4502 unless you really want your Tor to break.
4503 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4504 - ExcludeExitNodes now overrides .exit requests.
4505 - We don't use bridges listed in ExcludeNodes.
4506 - When StrictNodes is 1:
4507 . We now apply ExcludeNodes to hidden service introduction points
4508 and to rendezvous points selected by hidden service users. This
4509 can make your hidden service less reliable: use it with caution!
4510 . If we have used ExcludeNodes on ourself, do not try relay
4511 reachability self-tests.
4512 . If we have excluded all the directory authorities, we will not
4513 even try to upload our descriptor if we're a relay.
4514 . Do not honor .exit requests to an excluded node.
4515 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4516 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4517 - When the set of permitted nodes changes, we now remove any mappings
4518 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4520 - We never cannibalize a circuit that had excluded nodes on it, even
4521 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4522 - Revert a change where we would be laxer about attaching streams to
4523 circuits than when building the circuits. This was meant to prevent
4524 a set of bugs where streams were never attachable, but our improved
4525 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
4526 - Keep track of how many times we launch a new circuit to handle a
4527 given stream. Too many launches could indicate an inconsistency
4528 between our "launch a circuit to handle this stream" logic and our
4529 "attach this stream to one of the available circuits" logic.
4530 - Improve log messages related to excluded nodes.
4533 - Fix a spurious warning when moving from a short month to a long
4534 month on relays with month-based BandwidthAccounting. Bugfix on
4535 0.2.2.17-alpha; fixes bug 3020.
4536 - When a client finds that an origin circuit has run out of 16-bit
4537 stream IDs, we now mark it as unusable for new streams. Previously,
4538 we would try to close the entire circuit. Bugfix on 0.0.6.
4539 - Add a forgotten cast that caused a compile warning on OS X 10.6.
4540 Bugfix on 0.2.2.24-alpha.
4541 - Be more careful about reporting the correct error from a failed
4542 connect() system call. Under some circumstances, it was possible to
4543 look at an incorrect value for errno when sending the end reason.
4544 Bugfix on 0.1.0.1-rc.
4545 - Correctly handle an "impossible" overflow cases in connection byte
4546 counting, where we write or read more than 4GB on an edge connection
4547 in a single second. Bugfix on 0.1.2.8-beta.
4548 - Correct the warning displayed when a rendezvous descriptor exceeds
4549 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4551 - Clients and hidden services now use HSDir-flagged relays for hidden
4552 service descriptor downloads and uploads even if the relays have no
4553 DirPort set and the client has disabled TunnelDirConns. This will
4554 eventually allow us to give the HSDir flag to relays with no
4555 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4556 - Downgrade "no current certificates known for authority" message from
4557 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
4558 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
4559 2917. Bugfix on 0.1.1.1-alpha.
4560 - Only limit the lengths of single HS descriptors, even when multiple
4561 HS descriptors are published to an HSDir relay in a single POST
4562 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4563 - Write the current time into the LastWritten line in our state file,
4564 rather than the time from the previous write attempt. Also, stop
4565 trying to use a time of -1 in our log statements. Fixes bug 3039;
4566 bugfix on 0.2.2.14-alpha.
4567 - Be more consistent in our treatment of file system paths. "~" should
4568 get expanded to the user's home directory in the Log config option.
4569 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4570 feature for the -f and --DataDirectory options.
4573 - Make sure every relay writes a state file at least every 12 hours.
4574 Previously, a relay could go for weeks without writing its state
4575 file, and on a crash could lose its bandwidth history, capacity
4576 estimates, client country statistics, and so on. Addresses bug 3012.
4577 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4578 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4579 clients are already deprecated because of security bugs.
4580 - Don't allow v0 hidden service authorities to act as clients.
4581 Required by fix for bug 3000.
4582 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4583 by fix for bug 3000.
4584 - Ensure that no empty [dirreq-](read|write)-history lines are added
4585 to an extrainfo document. Implements ticket 2497.
4587 o Code simplification and refactoring:
4588 - Remove workaround code to handle directory responses from servers
4589 that had bug 539 (they would send HTTP status 503 responses _and_
4590 send a body too). Since only server versions before
4591 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
4592 keep the workaround in place.
4593 - Remove the old 'fuzzy time' logic. It was supposed to be used for
4594 handling calculations where we have a known amount of clock skew and
4595 an allowed amount of unknown skew. But we only used it in three
4596 places, and we never adjusted the known/unknown skew values. This is
4597 still something we might want to do someday, but if we do, we'll
4598 want to do it differently.
4599 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4600 None of the cases where we did this before were wrong, but by making
4601 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4602 - Use GetTempDir to find the proper temporary directory location on
4603 Windows when generating temporary files for the unit tests. Patch by
4607 Changes in version 0.2.2.24-alpha - 2011-04-08
4608 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
4609 prevented Tor clients from effectively using "multihomed" bridges,
4610 that is, bridges that listen on multiple ports or IP addresses so users
4611 can continue to use some of their addresses even if others get blocked.
4614 - Fix a bug where bridge users who configure the non-canonical
4615 address of a bridge automatically switch to its canonical
4616 address. If a bridge listens at more than one address, it should be
4617 able to advertise those addresses independently and any non-blocked
4618 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
4620 - If you configured Tor to use bridge A, and then quit and
4621 configured Tor to use bridge B instead, it would happily continue
4622 to use bridge A if it's still reachable. While this behavior is
4623 a feature if your goal is connectivity, in some scenarios it's a
4624 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4625 - Directory authorities now use data collected from their own
4626 uptime observations when choosing whether to assign the HSDir flag
4627 to relays, instead of trusting the uptime value the relay reports in
4628 its descriptor. This change helps prevent an attack where a small
4629 set of nodes with frequently-changing identity keys can blackhole
4630 a hidden service. (Only authorities need upgrade; others will be
4631 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4634 - When we restart our relay, we might get a successful connection
4635 from the outside before we've started our reachability tests,
4636 triggering a warning: "ORPort found reachable, but I have no
4637 routerinfo yet. Failing to inform controller of success." This
4638 bug was harmless unless Tor is running under a controller
4639 like Vidalia, in which case the controller would never get a
4640 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4642 - Make directory authorities more accurate at recording when
4643 relays that have failed several reachability tests became
4644 unreachable, so we can provide more accuracy at assigning Stable,
4645 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4646 - Fix an issue that prevented static linking of libevent on
4647 some platforms (notably Linux). Fixes bug 2698; bugfix on
4648 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
4649 the --with-static-libevent configure option).
4650 - We now ask the other side of a stream (the client or the exit)
4651 for more data on that stream when the amount of queued data on
4652 that stream dips low enough. Previously, we wouldn't ask the
4653 other side for more data until either it sent us more data (which
4654 it wasn't supposed to do if it had exhausted its window!) or we
4655 had completely flushed all our queued data. This flow control fix
4656 should improve throughput. Fixes bug 2756; bugfix on the earliest
4657 released versions of Tor (svn commit r152).
4658 - Avoid a double-mark-for-free warning when failing to attach a
4659 transparent proxy connection. (We thought we had fixed this in
4660 0.2.2.23-alpha, but it turns out our fix was checking the wrong
4661 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
4662 bug) and 0.2.2.23-alpha (the incorrect fix).
4663 - When warning about missing zlib development packages during compile,
4664 give the correct package names. Bugfix on 0.2.0.1-alpha.
4667 - Directory authorities now log the source of a rejected POSTed v3
4669 - Make compilation with clang possible when using
4670 --enable-gcc-warnings by removing two warning options that clang
4671 hasn't implemented yet and by fixing a few warnings. Implements
4673 - When expiring circuits, use microsecond timers rather than
4674 one-second timers. This can avoid an unpleasant situation where a
4675 circuit is launched near the end of one second and expired right
4676 near the beginning of the next, and prevent fluctuations in circuit
4678 - Use computed circuit-build timeouts to decide when to launch
4679 parallel introduction circuits for hidden services. (Previously,
4680 we would retry after 15 seconds.)
4681 - Update to the April 1 2011 Maxmind GeoLite Country database.
4684 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4685 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4687 o Documentation changes:
4688 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
4689 - Resolve all doxygen warnings except those for missing documentation.
4691 - Add doxygen documentation for more functions, fields, and types.
4694 Changes in version 0.2.2.23-alpha - 2011-03-08
4695 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
4696 they restart they don't lose their bandwidth capacity estimate. This
4697 release also fixes a diverse set of user-facing bugs, ranging from
4698 relays overrunning their rate limiting to clients falsely warning about
4699 clock skew to bridge descriptor leaks by our bridge directory authority.
4702 - Stop sending a CLOCK_SKEW controller status event whenever
4703 we fetch directory information from a relay that has a wrong clock.
4704 Instead, only inform the controller when it's a trusted authority
4705 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4706 the rest of bug 1074.
4707 - Fix an assert in parsing router descriptors containing IPv6
4708 addresses. This one took down the directory authorities when
4709 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4710 - Make the bridge directory authority refuse to answer directory
4711 requests for "all" descriptors. It used to include bridge
4712 descriptors in its answer, which was a major information leak.
4713 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4714 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4715 Tor would ignore their RelayBandwidthBurst setting,
4716 potentially using more bandwidth than expected. Bugfix on
4717 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4718 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4719 hidserv" in her torrc. The 'hidserv' argument never controlled
4720 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4723 - Relays now save observed peak bandwidth throughput rates to their
4724 state file (along with total usage, which was already saved)
4725 so that they can determine their correct estimated bandwidth on
4726 restart. Resolves bug 1863, where Tor relays would reset their
4727 estimated bandwidth to 0 after restarting.
4728 - Directory authorities now take changes in router IP address and
4729 ORPort into account when determining router stability. Previously,
4730 if a router changed its IP or ORPort, the authorities would not
4731 treat it as having any downtime for the purposes of stability
4732 calculation, whereas clients would experience downtime since the
4733 change could take a while to propagate to them. Resolves issue 1035.
4734 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4735 Prevention (DEP) by default on Windows to make it harder for
4736 attackers to exploit vulnerabilities. Patch from John Brooks.
4738 o Minor bugfixes (on 0.2.1.x and earlier):
4739 - Fix a rare crash bug that could occur when a client was configured
4740 with a large number of bridges. Fixes bug 2629; bugfix on
4741 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4742 - Avoid a double mark-for-free warning when failing to attach a
4743 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4745 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4746 found by "cypherpunks". This bug was introduced before the first
4747 Tor release, in svn commit r110.
4748 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
4749 don't mention them in the manpage. Fixes bug 2450; issue
4750 spotted by keb and G-Lo.
4751 - Fix a bug in bandwidth history state parsing that could have been
4752 triggered if a future version of Tor ever changed the timing
4753 granularity at which bandwidth history is measured. Bugfix on
4755 - When a relay decides that its DNS is too broken for it to serve
4756 as an exit server, it advertised itself as a non-exit, but
4757 continued to act as an exit. This could create accidental
4758 partitioning opportunities for users. Instead, if a relay is
4759 going to advertise reject *:* as its exit policy, it should
4760 really act with exit policy "reject *:*". Fixes bug 2366.
4761 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4762 - In the special case where you configure a public exit relay as your
4763 bridge, Tor would be willing to use that exit relay as the last
4764 hop in your circuit as well. Now we fail that circuit instead.
4765 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4766 - Fix a bug with our locking implementation on Windows that couldn't
4767 correctly detect when a file was already locked. Fixes bug 2504,
4768 bugfix on 0.2.1.6-alpha.
4769 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4770 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
4772 - Set target port in get_interface_address6() correctly. Bugfix
4773 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
4774 - Directory authorities are now more robust to hops back in time
4775 when calculating router stability. Previously, if a run of uptime
4776 or downtime appeared to be negative, the calculation could give
4777 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4779 - Fix an assert that got triggered when using the TestingTorNetwork
4780 configuration option and then issuing a GETINFO config-text control
4781 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
4783 o Minor bugfixes (on 0.2.2.x):
4784 - Clients should not weight BadExit nodes as Exits in their node
4785 selection. Similarly, directory authorities should not count BadExit
4786 bandwidth as Exit bandwidth when computing bandwidth-weights.
4787 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
4788 - Correctly clear our dir_read/dir_write history when there is an
4789 error parsing any bw history value from the state file. Bugfix on
4791 - Resolve a bug in verifying signatures of directory objects
4792 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
4793 Fixes bug 2409. Found by "piebeer".
4794 - Bridge authorities no longer crash on SIGHUP when they try to
4795 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
4799 - Log less aggressively about circuit timeout changes, and improve
4800 some other circuit timeout messages. Resolves bug 2004.
4801 - Log a little more clearly about the times at which we're no longer
4802 accepting new connections. Resolves bug 2181.
4803 - Reject attempts at the client side to open connections to private
4804 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
4805 a randomly chosen exit node. Attempts to do so are always
4806 ill-defined, generally prevented by exit policies, and usually
4807 in error. This will also help to detect loops in transparent
4808 proxy configurations. You can disable this feature by setting
4809 "ClientRejectInternalAddresses 0" in your torrc.
4810 - Always treat failure to allocate an RSA key as an unrecoverable
4812 - Update to the March 1 2011 Maxmind GeoLite Country database.
4814 o Minor features (log subsystem):
4815 - Add documentation for configuring logging at different severities in
4816 different log domains. We've had this feature since 0.2.1.1-alpha,
4817 but for some reason it never made it into the manpage. Fixes
4819 - Make it simpler to specify "All log domains except for A and B".
4820 Previously you needed to say "[*,~A,~B]". Now you can just say
4822 - Add a "LogMessageDomains 1" option to include the domains of log
4823 messages along with the messages. Without this, there's no way
4824 to use log domains without reading the source or doing a lot
4827 o Packaging changes:
4828 - Stop shipping the Tor specs files and development proposal documents
4829 in the tarball. They are now in a separate git repository at
4830 git://git.torproject.org/torspec.git
4833 Changes in version 0.2.1.30 - 2011-02-23
4834 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
4835 change is a slight tweak to Tor's TLS handshake that makes relays
4836 and bridges that run this new version reachable from Iran again.
4837 We don't expect this tweak will win the arms race long-term, but it
4838 buys us time until we roll out a better solution.
4841 - Stop sending a CLOCK_SKEW controller status event whenever
4842 we fetch directory information from a relay that has a wrong clock.
4843 Instead, only inform the controller when it's a trusted authority
4844 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4845 the rest of bug 1074.
4846 - Fix a bounds-checking error that could allow an attacker to
4847 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4849 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4850 Tor would ignore their RelayBandwidthBurst setting,
4851 potentially using more bandwidth than expected. Bugfix on
4852 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4853 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4854 hidserv" in her torrc. The 'hidserv' argument never controlled
4855 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4858 - Adjust our TLS Diffie-Hellman parameters to match those used by
4860 - Update to the February 1 2011 Maxmind GeoLite Country database.
4863 - Check for and reject overly long directory certificates and
4864 directory tokens before they have a chance to hit any assertions.
4865 Bugfix on 0.2.1.28. Found by "doorss".
4866 - Bring the logic that gathers routerinfos and assesses the
4867 acceptability of circuits into line. This prevents a Tor OP from
4868 getting locked in a cycle of choosing its local OR as an exit for a
4869 path (due to a .exit request) and then rejecting the circuit because
4870 its OR is not listed yet. It also prevents Tor clients from using an
4871 OR running in the same instance as an exit (due to a .exit request)
4872 if the OR does not meet the same requirements expected of an OR
4873 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4875 o Packaging changes:
4876 - Stop shipping the Tor specs files and development proposal documents
4877 in the tarball. They are now in a separate git repository at
4878 git://git.torproject.org/torspec.git
4879 - Do not include Git version tags as though they are SVN tags when
4880 generating a tarball from inside a repository that has switched
4881 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4884 Changes in version 0.2.2.22-alpha - 2011-01-25
4885 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
4886 main other change is a slight tweak to Tor's TLS handshake that makes
4887 relays and bridges that run this new version reachable from Iran again.
4888 We don't expect this tweak will win the arms race long-term, but it
4889 will buy us a bit more time until we roll out a better solution.
4892 - Fix a bounds-checking error that could allow an attacker to
4893 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4895 - Don't assert when changing from bridge to relay or vice versa
4896 via the controller. The assert happened because we didn't properly
4897 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
4898 bug 2433. Reported by bastik.
4901 - Adjust our TLS Diffie-Hellman parameters to match those used by
4903 - Provide a log message stating which geoip file we're parsing
4904 instead of just stating that we're parsing the geoip file.
4905 Implements ticket 2432.
4908 - Check for and reject overly long directory certificates and
4909 directory tokens before they have a chance to hit any assertions.
4910 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
4913 Changes in version 0.2.2.21-alpha - 2011-01-15
4914 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
4915 continues our recent code security audit work. The main fix resolves
4916 a remote heap overflow vulnerability that can allow remote code
4917 execution (CVE-2011-0427). Other fixes address a variety of assert
4918 and crash bugs, most of which we think are hard to exploit remotely.
4920 o Major bugfixes (security), also included in 0.2.1.29:
4921 - Fix a heap overflow bug where an adversary could cause heap
4922 corruption. This bug probably allows remote code execution
4923 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4925 - Prevent a denial-of-service attack by disallowing any
4926 zlib-compressed data whose compression factor is implausibly
4927 high. Fixes part of bug 2324; reported by "doorss".
4928 - Zero out a few more keys in memory before freeing them. Fixes
4929 bug 2384 and part of bug 2385. These key instances found by
4930 "cypherpunks", based on Andrew Case's report about being able
4931 to find sensitive data in Tor's memory space if you have enough
4932 permissions. Bugfix on 0.0.2pre9.
4934 o Major bugfixes (crashes), also included in 0.2.1.29:
4935 - Prevent calls to Libevent from inside Libevent log handlers.
4936 This had potential to cause a nasty set of crashes, especially
4937 if running Libevent with debug logging enabled, and running
4938 Tor with a controller watching for low-severity log messages.
4939 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4940 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4941 underflow errors there too. Fixes the other part of bug 2324.
4942 - Fix a bug where we would assert if we ever had a
4943 cached-descriptors.new file (or another file read directly into
4944 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4945 on 0.2.1.25. Found by doorss.
4946 - Fix some potential asserts and parsing issues with grossly
4947 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4950 o Minor bugfixes (other), also included in 0.2.1.29:
4951 - Fix a bug with handling misformed replies to reverse DNS lookup
4952 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4953 bug reported by doorss.
4954 - Fix compilation on mingw when a pthreads compatibility library
4955 has been installed. (We don't want to use it, so we shouldn't
4956 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4957 - Fix a bug where we would declare that we had run out of virtual
4958 addresses when the address space was only half-exhausted. Bugfix
4960 - Correctly handle the case where AutomapHostsOnResolve is set but
4961 no virtual addresses are available. Fixes bug 2328; bugfix on
4962 0.1.2.1-alpha. Bug found by doorss.
4963 - Correctly handle wrapping around when we run out of virtual
4964 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4966 o Minor features, also included in 0.2.1.29:
4967 - Update to the January 1 2011 Maxmind GeoLite Country database.
4968 - Introduce output size checks on all of our decryption functions.
4970 o Build changes, also included in 0.2.1.29:
4971 - Tor does not build packages correctly with Automake 1.6 and earlier;
4972 added a check to Makefile.am to make sure that we're building with
4973 Automake 1.7 or later.
4974 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4975 because we built it with a too-old version of automake. Thus that
4976 release broke ./configure --enable-openbsd-malloc, which is popular
4977 among really fast exit relays on Linux.
4979 o Major bugfixes, new in 0.2.2.21-alpha:
4980 - Prevent crash/heap corruption when the cbtnummodes consensus
4981 parameter is set to 0 or large values. Fixes bug 2317; bugfix
4984 o Major features, new in 0.2.2.21-alpha:
4985 - Introduce minimum/maximum values that clients will believe
4986 from the consensus. Now we'll have a better chance to avoid crashes
4987 or worse when a consensus param has a weird value.
4989 o Minor features, new in 0.2.2.21-alpha:
4990 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4991 used on bridges, and it makes bridge scanning somewhat easier.
4992 - If writing the state file to disk fails, wait up to an hour before
4993 retrying again, rather than trying again each second. Fixes bug
4994 2346; bugfix on Tor 0.1.1.3-alpha.
4995 - Make Libevent log messages get delivered to controllers later,
4996 and not from inside the Libevent log handler. This prevents unsafe
4997 reentrant Libevent calls while still letting the log messages
4999 - Detect platforms that brokenly use a signed size_t, and refuse to
5000 build there. Found and analyzed by doorss and rransom.
5001 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5004 o Minor bugfixes, new in 0.2.2.21-alpha:
5005 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5006 than waiting forever for them to finish. Fixes bug 2330; bugfix
5007 on 0.2.0.16-alpha. Found by doorss.
5008 - Add assertions to check for overflow in arguments to
5009 base32_encode() and base32_decode(); fix a signed-unsigned
5010 comparison there too. These bugs are not actually reachable in Tor,
5011 but it's good to prevent future errors too. Found by doorss.
5012 - Correctly detect failures to create DNS requests when using Libevent
5013 versions before v2. (Before Libevent 2, we used our own evdns
5014 implementation. Its return values for Libevent's evdns_resolve_*()
5015 functions are not consistent with those from Libevent.) Fixes bug
5016 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5018 o Documentation, new in 0.2.2.21-alpha:
5019 - Document the default socks host and port (127.0.0.1:9050) for
5023 Changes in version 0.2.1.29 - 2011-01-15
5024 Tor 0.2.1.29 continues our recent code security audit work. The main
5025 fix resolves a remote heap overflow vulnerability that can allow remote
5026 code execution. Other fixes address a variety of assert and crash bugs,
5027 most of which we think are hard to exploit remotely.
5029 o Major bugfixes (security):
5030 - Fix a heap overflow bug where an adversary could cause heap
5031 corruption. This bug probably allows remote code execution
5032 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5034 - Prevent a denial-of-service attack by disallowing any
5035 zlib-compressed data whose compression factor is implausibly
5036 high. Fixes part of bug 2324; reported by "doorss".
5037 - Zero out a few more keys in memory before freeing them. Fixes
5038 bug 2384 and part of bug 2385. These key instances found by
5039 "cypherpunks", based on Andrew Case's report about being able
5040 to find sensitive data in Tor's memory space if you have enough
5041 permissions. Bugfix on 0.0.2pre9.
5043 o Major bugfixes (crashes):
5044 - Prevent calls to Libevent from inside Libevent log handlers.
5045 This had potential to cause a nasty set of crashes, especially
5046 if running Libevent with debug logging enabled, and running
5047 Tor with a controller watching for low-severity log messages.
5048 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5049 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5050 underflow errors there too. Fixes the other part of bug 2324.
5051 - Fix a bug where we would assert if we ever had a
5052 cached-descriptors.new file (or another file read directly into
5053 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5054 on 0.2.1.25. Found by doorss.
5055 - Fix some potential asserts and parsing issues with grossly
5056 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5059 o Minor bugfixes (other):
5060 - Fix a bug with handling misformed replies to reverse DNS lookup
5061 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5062 bug reported by doorss.
5063 - Fix compilation on mingw when a pthreads compatibility library
5064 has been installed. (We don't want to use it, so we shouldn't
5065 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5066 - Fix a bug where we would declare that we had run out of virtual
5067 addresses when the address space was only half-exhausted. Bugfix
5069 - Correctly handle the case where AutomapHostsOnResolve is set but
5070 no virtual addresses are available. Fixes bug 2328; bugfix on
5071 0.1.2.1-alpha. Bug found by doorss.
5072 - Correctly handle wrapping around to when we run out of virtual
5073 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5074 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5075 because we built it with a too-old version of automake. Thus that
5076 release broke ./configure --enable-openbsd-malloc, which is popular
5077 among really fast exit relays on Linux.
5080 - Update to the January 1 2011 Maxmind GeoLite Country database.
5081 - Introduce output size checks on all of our decryption functions.
5084 - Tor does not build packages correctly with Automake 1.6 and earlier;
5085 added a check to Makefile.am to make sure that we're building with
5086 Automake 1.7 or later.
5089 Changes in version 0.2.2.20-alpha - 2010-12-17
5090 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5091 exploitable bugs. We also fix a variety of other significant bugs,
5092 change the IP address for one of our directory authorities, and update
5093 the minimum version that Tor relays must run to join the network.
5096 - Fix a remotely exploitable bug that could be used to crash instances
5097 of Tor remotely by overflowing on the heap. Remote-code execution
5098 hasn't been confirmed, but can't be ruled out. Everyone should
5099 upgrade. Bugfix on the 0.1.1 series and later.
5100 - Fix a bug that could break accounting on 64-bit systems with large
5101 time_t values, making them hibernate for impossibly long intervals.
5102 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5103 - Fix a logic error in directory_fetches_from_authorities() that
5104 would cause all _non_-exits refusing single-hop-like circuits
5105 to fetch from authorities, when we wanted to have _exits_ fetch
5106 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5108 - Fix a stream fairness bug that would cause newer streams on a given
5109 circuit to get preference when reading bytes from the origin or
5110 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5111 introduced before the first Tor release, in svn revision r152.
5113 o Directory authority changes:
5114 - Change IP address and ports for gabelmoo (v3 directory authority).
5117 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5118 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5119 - Fix an off-by-one error in calculating some controller command
5120 argument lengths. Fortunately, this mistake is harmless since
5121 the controller code does redundant NUL termination too. Found by
5122 boboper. Bugfix on 0.1.1.1-alpha.
5123 - Do not dereference NULL if a bridge fails to build its
5124 extra-info descriptor. Found by an anonymous commenter on
5125 Trac. Bugfix on 0.2.2.19-alpha.
5128 - Update to the December 1 2010 Maxmind GeoLite Country database.
5129 - Directory authorities now reject relays running any versions of
5130 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5131 known bugs that keep RELAY_EARLY cells from working on rendezvous
5132 circuits. Followup to fix for bug 2081.
5133 - Directory authorities now reject relays running any version of Tor
5134 older than 0.2.0.26-rc. That version is the earliest that fetches
5135 current directory information correctly. Fixes bug 2156.
5136 - Report only the top 10 ports in exit-port stats in order not to
5137 exceed the maximum extra-info descriptor length of 50 KB. Implements
5141 Changes in version 0.2.1.28 - 2010-12-17
5142 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5143 exploitable bugs. We also took this opportunity to change the IP address
5144 for one of our directory authorities, and to update the geoip database
5148 - Fix a remotely exploitable bug that could be used to crash instances
5149 of Tor remotely by overflowing on the heap. Remote-code execution
5150 hasn't been confirmed, but can't be ruled out. Everyone should
5151 upgrade. Bugfix on the 0.1.1 series and later.
5153 o Directory authority changes:
5154 - Change IP address and ports for gabelmoo (v3 directory authority).
5157 - Update to the December 1 2010 Maxmind GeoLite Country database.
5160 Changes in version 0.2.1.27 - 2010-11-23
5161 Yet another OpenSSL security patch broke its compatibility with Tor:
5162 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5163 also took this opportunity to fix several crash bugs, integrate a new
5164 directory authority, and update the bundled GeoIP database.
5167 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5168 No longer set the tlsext_host_name extension on server SSL objects;
5169 but continue to set it on client SSL objects. Our goal in setting
5170 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5171 bugfix on 0.2.1.1-alpha.
5172 - Do not log messages to the controller while shrinking buffer
5173 freelists. Doing so would sometimes make the controller connection
5174 try to allocate a buffer chunk, which would mess up the internals
5175 of the freelist and cause an assertion failure. Fixes bug 1125;
5176 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5177 - Learn our external IP address when we're a relay or bridge, even if
5178 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5179 where we introduced bridge relays that don't need to publish to
5180 be useful. Fixes bug 2050.
5181 - Do even more to reject (and not just ignore) annotations on
5182 router descriptors received anywhere but from the cache. Previously
5183 we would ignore such annotations at first, but cache them to disk
5184 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5185 - When you're using bridges and your network goes away and your
5186 bridges get marked as down, recover when you attempt a new socks
5187 connection (if the network is back), rather than waiting up to an
5188 hour to try fetching new descriptors for your bridges. Bugfix on
5189 0.2.0.3-alpha; fixes bug 1981.
5192 - Move to the November 2010 Maxmind GeoLite country db (rather
5193 than the June 2009 ip-to-country GeoIP db) for our statistics that
5194 count how many users relays are seeing from each country. Now we'll
5195 have more accurate data, especially for many African countries.
5197 o New directory authorities:
5198 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5202 - Fix an assertion failure that could occur in directory caches or
5203 bridge users when using a very short voting interval on a testing
5204 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5206 - Enforce multiplicity rules when parsing annotations. Bugfix on
5207 0.2.0.8-alpha. Found by piebeer.
5208 - Allow handshaking OR connections to take a full KeepalivePeriod
5209 seconds to handshake. Previously, we would close them after
5210 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5211 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5213 - When building with --enable-gcc-warnings on OpenBSD, disable
5214 warnings in system headers. This makes --enable-gcc-warnings
5215 pass on OpenBSD 4.8.
5218 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5219 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5220 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5221 Servers can start sending this code when enough clients recognize
5222 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5223 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5224 Patch from mingw-san.
5227 - Remove the old debian/ directory from the main Tor distribution.
5228 The official Tor-for-debian git repository lives at the URL
5229 https://git.torproject.org/debian/tor.git
5230 - Stop shipping the old doc/website/ directory in the tarball. We
5231 changed the website format in late 2010, and what we shipped in
5232 0.2.1.26 really wasn't that useful anyway.
5235 Changes in version 0.2.2.19-alpha - 2010-11-22
5236 Yet another OpenSSL security patch broke its compatibility with Tor:
5237 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5240 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5241 No longer set the tlsext_host_name extension on server SSL objects;
5242 but continue to set it on client SSL objects. Our goal in setting
5243 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5244 bugfix on 0.2.1.1-alpha.
5247 - Try harder not to exceed the maximum length of 50 KB when writing
5248 statistics to extra-info descriptors. This bug was triggered by very
5249 fast relays reporting exit-port, entry, and dirreq statistics.
5250 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5251 - Publish a router descriptor even if generating an extra-info
5252 descriptor fails. Previously we would not publish a router
5253 descriptor without an extra-info descriptor; this can cause fast
5254 exit relays collecting exit-port statistics to drop from the
5255 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5258 Changes in version 0.2.2.18-alpha - 2010-11-16
5259 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5260 us lately, makes unpublished bridge relays able to detect their IP
5261 address, and fixes a wide variety of other bugs to get us much closer
5262 to a stable release.
5265 - Do even more to reject (and not just ignore) annotations on
5266 router descriptors received anywhere but from the cache. Previously
5267 we would ignore such annotations at first, but cache them to disk
5268 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5269 - Do not log messages to the controller while shrinking buffer
5270 freelists. Doing so would sometimes make the controller connection
5271 try to allocate a buffer chunk, which would mess up the internals
5272 of the freelist and cause an assertion failure. Fixes bug 1125;
5273 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5274 - Learn our external IP address when we're a relay or bridge, even if
5275 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5276 where we introduced bridge relays that don't need to publish to
5277 be useful. Fixes bug 2050.
5278 - Maintain separate TLS contexts and certificates for incoming and
5279 outgoing connections in bridge relays. Previously we would use the
5280 same TLS contexts and certs for incoming and outgoing connections.
5281 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5282 - Maintain separate identity keys for incoming and outgoing TLS
5283 contexts in bridge relays. Previously we would use the same
5284 identity keys for incoming and outgoing TLS contexts. Bugfix on
5285 0.2.0.3-alpha; addresses the other half of bug 988.
5286 - Avoid an assertion failure when we as an authority receive a
5287 duplicate upload of a router descriptor that we already have,
5288 but which we previously considered an obsolete descriptor.
5289 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5290 - Avoid a crash bug triggered by looking at a dangling pointer while
5291 setting the network status consensus. Found by Robert Ransom.
5292 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5293 - Fix a logic error where servers that _didn't_ act as exits would
5294 try to keep their server lists more aggressively up to date than
5295 exits, when it was supposed to be the other way around. Bugfix
5298 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5299 - When we're trying to guess whether we know our IP address as
5300 a relay, we would log various ways that we failed to guess
5301 our address, but never log that we ended up guessing it
5302 successfully. Now add a log line to help confused and anxious
5303 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5304 - Bring the logic that gathers routerinfos and assesses the
5305 acceptability of circuits into line. This prevents a Tor OP from
5306 getting locked in a cycle of choosing its local OR as an exit for a
5307 path (due to a .exit request) and then rejecting the circuit because
5308 its OR is not listed yet. It also prevents Tor clients from using an
5309 OR running in the same instance as an exit (due to a .exit request)
5310 if the OR does not meet the same requirements expected of an OR
5311 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5312 - Correctly describe errors that occur when generating a TLS object.
5313 Previously we would attribute them to a failure while generating a
5314 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5316 - Enforce multiplicity rules when parsing annotations. Bugfix on
5317 0.2.0.8-alpha. Found by piebeer.
5318 - Fix warnings that newer versions of autoconf produced during
5319 ./autogen.sh. These warnings appear to be harmless in our case,
5320 but they were extremely verbose. Fixes bug 2020.
5322 o Minor bugfixes (on Tor 0.2.2.x):
5323 - Enable protection of small arrays whenever we build with gcc
5324 hardening features, not only when also building with warnings
5325 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5328 - Make hidden services work better in private Tor networks by not
5329 requiring any uptime to join the hidden service descriptor
5330 DHT. Implements ticket 2088.
5331 - Rate-limit the "your application is giving Tor only an IP address"
5332 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5333 - When AllowSingleHopExits is set, print a warning to explain to the
5334 relay operator why most clients are avoiding her relay.
5335 - Update to the November 1 2010 Maxmind GeoLite Country database.
5337 o Code simplifications and refactoring:
5338 - When we fixed bug 1038 we had to put in a restriction not to send
5339 RELAY_EARLY cells on rend circuits. This was necessary as long
5340 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5341 active. Now remove this obsolete check. Resolves bug 2081.
5342 - Some options used different conventions for uppercasing of acronyms
5343 when comparing manpage and source. Fix those in favor of the
5344 manpage, as it makes sense to capitalize acronyms.
5345 - Remove the torrc.complete file. It hasn't been kept up to date
5346 and users will have better luck checking out the manpage.
5347 - Remove the obsolete "NoPublish" option; it has been flagged
5348 as obsolete and has produced a warning since 0.1.1.18-rc.
5349 - Remove everything related to building the expert bundle for OS X.
5350 It has confused many users, doesn't work right on OS X 10.6,
5351 and is hard to get rid of once installed. Resolves bug 1274.
5354 Changes in version 0.2.2.17-alpha - 2010-09-30
5355 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5356 to use one-hop circuits (which can put the exit relays at higher risk,
5357 plus unbalance the network); fixes a big bug in bandwidth accounting
5358 for relays that want to limit their monthly bandwidth use; fixes a
5359 big pile of bugs in how clients tolerate temporary network failure;
5360 and makes our adaptive circuit build timeout feature (which improves
5361 client performance if your network is fast while not breaking things
5362 if your network is slow) better handle bad networks.
5365 - Exit relays now try harder to block exit attempts from unknown
5366 relays, to make it harder for people to use them as one-hop proxies
5367 a la tortunnel. Controlled by the refuseunknownexits consensus
5368 parameter (currently enabled), or you can override it on your
5369 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5371 o Major bugfixes (0.2.1.x and earlier):
5372 - Fix a bug in bandwidth accounting that could make us use twice
5373 the intended bandwidth when our interval start changes due to
5374 daylight saving time. Now we tolerate skew in stored vs computed
5375 interval starts: if the start of the period changes by no more than
5376 50% of the period's duration, we remember bytes that we transferred
5377 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5378 - Always search the Windows system directory for system DLLs, and
5379 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5380 - When you're using bridges and your network goes away and your
5381 bridges get marked as down, recover when you attempt a new socks
5382 connection (if the network is back), rather than waiting up to an
5383 hour to try fetching new descriptors for your bridges. Bugfix on
5384 0.2.0.3-alpha; fixes bug 1981.
5386 o Major bugfixes (on 0.2.2.x):
5387 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5389 - Fix a segfault that could happen when operating a bridge relay with
5390 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5391 - The consensus bandwidth-weights (used by clients to choose fast
5392 relays) entered an unexpected edge case in September where
5393 Exits were much scarcer than Guards, resulting in bad weight
5394 recommendations. Now we compute them using new constraints that
5395 should succeed in all cases. Also alter directory authorities to
5396 not include the bandwidth-weights line if they fail to produce
5397 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5398 - When weighting bridges during path selection, we used to trust
5399 the bandwidths they provided in their descriptor, only capping them
5400 at 10MB/s. This turned out to be problematic for two reasons:
5401 Bridges could claim to handle a lot more traffic then they
5402 actually would, thus making more clients pick them and have a
5403 pretty effective DoS attack. The other issue is that new bridges
5404 that might not have a good estimate for their bw capacity yet
5405 would not get used at all unless no other bridges are available
5406 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5408 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5409 - Ignore cannibalized circuits when recording circuit build times.
5410 This should provide for a minor performance improvement for hidden
5411 service users using 0.2.2.14-alpha, and should remove two spurious
5412 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5413 - Simplify the logic that causes us to decide if the network is
5414 unavailable for purposes of recording circuit build times. If we
5415 receive no cells whatsoever for the entire duration of a circuit's
5416 full measured lifetime, the network is probably down. Also ignore
5417 one-hop directory fetching circuit timeouts when calculating our
5418 circuit build times. These changes should hopefully reduce the
5419 cases where we see ridiculous circuit build timeouts for people
5420 with spotty wireless connections. Fixes part of bug 1772; bugfix
5422 - Prevent the circuit build timeout from becoming larger than
5423 the maximum build time we have ever seen. Also, prevent the time
5424 period for measurement circuits from becoming larger than twice that
5425 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5428 - When we run out of directory information such that we can't build
5429 circuits, but then get enough that we can build circuits, log when
5430 we actually construct a circuit, so the user has a better chance of
5431 knowing what's going on. Fixes bug 1362.
5432 - Be more generous with how much bandwidth we'd use up (with
5433 accounting enabled) before entering "soft hibernation". Previously,
5434 we'd refuse new connections and circuits once we'd used up 95% of
5435 our allotment. Now, we use up 95% of our allotment, AND make sure
5436 that we have no more than 500MB (or 3 hours of expected traffic,
5437 whichever is lower) remaining before we enter soft hibernation.
5438 - If we've configured EntryNodes and our network goes away and/or all
5439 our entrynodes get marked down, optimistically retry them all when
5440 a new socks application request appears. Fixes bug 1882.
5441 - Add some more defensive programming for architectures that can't
5442 handle unaligned integer accesses. We don't know of any actual bugs
5443 right now, but that's the best time to fix them. Fixes bug 1943.
5444 - Support line continuations in the torrc config file. If a line
5445 ends with a single backslash character, the newline is ignored, and
5446 the configuration value is treated as continuing on the next line.
5449 o Minor bugfixes (on 0.2.1.x and earlier):
5450 - For bandwidth accounting, calculate our expected bandwidth rate
5451 based on the time during which we were active and not in
5452 soft-hibernation during the last interval. Previously, we were
5453 also considering the time spent in soft-hibernation. If this
5454 was a long time, we would wind up underestimating our bandwidth
5455 by a lot, and skewing our wakeup time towards the start of the
5456 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5458 o Minor bugfixes (on 0.2.2.x):
5459 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5460 which were disabled by the circuit build timeout changes in
5461 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5462 - Make sure we don't warn about missing bandwidth weights when
5463 choosing bridges or other relays not in the consensus. Bugfix on
5464 0.2.2.10-alpha; fixes bug 1805.
5465 - In our logs, do not double-report signatures from unrecognized
5466 authorities both as "from unknown authority" and "not
5467 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5470 Changes in version 0.2.2.16-alpha - 2010-09-17
5471 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5472 evident at exit relays), and also continues to resolve all the little
5473 bugs that have been filling up trac lately.
5475 o Major bugfixes (stream-level fairness):
5476 - When receiving a circuit-level SENDME for a blocked circuit, try
5477 to package cells fairly from all the streams that had previously
5478 been blocked on that circuit. Previously, we had started with the
5479 oldest stream, and allowed each stream to potentially exhaust
5480 the circuit's package window. This gave older streams on any
5481 given circuit priority over newer ones. Fixes bug 1937. Detected
5482 originally by Camilo Viecco. This bug was introduced before the
5483 first Tor release, in svn commit r152: it is the new winner of
5484 the longest-lived bug prize.
5485 - When the exit relay got a circuit-level sendme cell, it started
5486 reading on the exit streams, even if had 500 cells queued in the
5487 circuit queue already, so the circuit queue just grew and grew in
5488 some cases. We fix this by not re-enabling reading on receipt of a
5489 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5490 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5492 - Newly created streams were allowed to read cells onto circuits,
5493 even if the circuit's cell queue was blocked and waiting to drain.
5494 This created potential unfairness, as older streams would be
5495 blocked, but newer streams would gladly fill the queue completely.
5496 We add code to detect this situation and prevent any stream from
5497 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5501 - Update to the September 1 2010 Maxmind GeoLite Country database.
5502 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5503 not. This would lead to a cookie that is still not group readable.
5504 Closes bug 1843. Suggested by katmagic.
5505 - When logging a rate-limited warning, we now mention how many messages
5506 got suppressed since the last warning.
5507 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5508 do individual connection-level rate limiting of clients. The torrc
5509 config options with the same names trump the consensus params, if
5510 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5511 consensus params which were broken from 0.2.2.7-alpha through
5512 0.2.2.14-alpha. Closes bug 1947.
5513 - When a router changes IP address or port, authorities now launch
5514 a new reachability test for it. Implements ticket 1899.
5515 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5516 2 no signature, 4 required" messages about consensus signatures
5517 easier to read, and make sure they get logged at the same severity
5518 as the messages explaining which keys are which. Fixes bug 1290.
5519 - Don't warn when we have a consensus that we can't verify because
5520 of missing certificates, unless those certificates are ones
5521 that we have been trying and failing to download. Fixes bug 1145.
5522 - If you configure your bridge with a known identity fingerprint,
5523 and the bridge authority is unreachable (as it is in at least
5524 one country now), fall back to directly requesting the descriptor
5525 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5527 - When building with --enable-gcc-warnings on OpenBSD, disable
5528 warnings in system headers. This makes --enable-gcc-warnings
5529 pass on OpenBSD 4.8.
5531 o Minor bugfixes (on 0.2.1.x and earlier):
5532 - Authorities will now attempt to download consensuses if their
5533 own efforts to make a live consensus have failed. This change
5534 means authorities that restart will fetch a valid consensus, and
5535 it means authorities that didn't agree with the current consensus
5536 will still fetch and serve it if it has enough signatures. Bugfix
5537 on 0.2.0.9-alpha; fixes bug 1300.
5538 - Ensure DNS requests launched by "RESOLVE" commands from the
5539 controller respect the __LeaveStreamsUnattached setconf options. The
5540 same goes for requests launched via DNSPort or transparent
5541 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
5542 - Allow handshaking OR connections to take a full KeepalivePeriod
5543 seconds to handshake. Previously, we would close them after
5544 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5545 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5547 - Rate-limit "Failed to hand off onionskin" warnings.
5548 - Never relay a cell for a circuit we have already destroyed.
5549 Between marking a circuit as closeable and finally closing it,
5550 it may have been possible for a few queued cells to get relayed,
5551 even though they would have been immediately dropped by the next
5552 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
5553 - Never queue a cell for a circuit that's already been marked
5555 - Never vote for a server as "Running" if we have a descriptor for
5556 it claiming to be hibernating, and that descriptor was published
5557 more recently than our last contact with the server. Bugfix on
5558 0.2.0.3-alpha; fixes bug 911.
5559 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
5562 o Minor bugfixes (on 0.2.2.x):
5563 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
5564 down if a directory fetch fails and you've configured either
5565 bridges or EntryNodes. The intent was to mark the relay as down
5566 _unless_ you're using bridges or EntryNodes, since if you are
5567 then you could quickly run out of entry points.
5568 - Fix the Windows directory-listing code. A bug introduced in
5569 0.2.2.14-alpha could make Windows directory servers forget to load
5570 some of their cached v2 networkstatus files.
5571 - Really allow clients to use relays as bridges. Fixes bug 1776;
5572 bugfix on 0.2.2.15-alpha.
5573 - Demote a warn to info that happens when the CellStatistics option
5574 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
5575 Reported by Moritz Bartl.
5576 - On Windows, build correctly either with or without Unicode support.
5577 This is necessary so that Tor can support fringe platforms like
5578 Windows 98 (which has no Unicode), or Windows CE (which has no
5579 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
5582 - Add a unit test for cross-platform directory-listing code.
5585 Changes in version 0.2.2.15-alpha - 2010-08-18
5586 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
5587 fixes a variety of other bugs that were preventing performance
5588 experiments from moving forward, fixes several bothersome memory leaks,
5589 and generally closes a lot of smaller bugs that have been filling up
5593 - Stop assigning the HSDir flag to relays that disable their
5594 DirPort (and thus will refuse to answer directory requests). This
5595 fix should dramatically improve the reachability of hidden services:
5596 hidden services and hidden service clients pick six HSDir relays
5597 to store and retrieve the hidden service descriptor, and currently
5598 about half of the HSDir relays will refuse to work. Bugfix on
5599 0.2.0.10-alpha; fixes part of bug 1693.
5600 - The PerConnBWRate and Burst config options, along with the
5601 bwconnrate and bwconnburst consensus params, initialized each conn's
5602 token bucket values only when the connection is established. Now we
5603 update them if the config options change, and update them every time
5604 we get a new consensus. Otherwise we can encounter an ugly edge
5605 case where we initialize an OR conn to client-level bandwidth,
5606 but then later the relay joins the consensus and we leave it
5607 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
5608 - Fix a regression that caused Tor to rebind its ports if it receives
5609 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
5612 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
5613 should give us approximately 40-50% more Guard-flagged nodes,
5614 improving the anonymity the Tor network can provide and also
5615 decreasing the dropoff in throughput that relays experience when
5616 they first get the Guard flag.
5617 - Allow enabling or disabling the *Statistics config options while
5621 - Update to the August 1 2010 Maxmind GeoLite Country database.
5622 - Have the controller interface give a more useful message than
5623 "Internal Error" in response to failed GETINFO requests.
5624 - Warn when the same option is provided more than once in a torrc
5625 file, on the command line, or in a single SETCONF statement, and
5626 the option is one that only accepts a single line. Closes bug 1384.
5627 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5628 Patch from mingw-san.
5629 - Add support for the country code "{??}" in torrc options like
5630 ExcludeNodes, to indicate all routers of unknown country. Closes
5632 - Relays report the number of bytes spent on answering directory
5633 requests in extra-info descriptors similar to {read,write}-history.
5634 Implements enhancement 1790.
5636 o Minor bugfixes (on 0.2.1.x and earlier):
5637 - Complain if PublishServerDescriptor is given multiple arguments that
5638 include 0 or 1. This configuration will be rejected in the future.
5639 Bugfix on 0.2.0.1-alpha; closes bug 1107.
5640 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
5641 Bugfix on 0.2.0.13-alpha; closes bug 928.
5642 - Change "Application request when we're believed to be offline."
5643 notice to "Application request when we haven't used client
5644 functionality lately.", to clarify that it's not an error. Bugfix
5645 on 0.0.9.3; fixes bug 1222.
5646 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
5647 would return "551 Internal error" rather than "552 Unrecognized key
5648 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
5649 - Users can't configure a regular relay to be their bridge. It didn't
5650 work because when Tor fetched the bridge descriptor, it found
5651 that it already had it, and didn't realize that the purpose of the
5652 descriptor had changed. Now we replace routers with a purpose other
5653 than bridge with bridge descriptors when fetching them. Bugfix on
5654 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
5655 refetch the descriptor with router purpose 'general', disabling
5657 - Fix a rare bug in rend_fn unit tests: we would fail a test when
5658 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5659 on 0.2.0.10-alpha; fixes bug 1808.
5660 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5661 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5662 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5663 Servers can start sending this code when enough clients recognize
5664 it. Also update the spec to reflect this new reason. Bugfix on
5665 0.1.0.1-rc; fixes part of bug 1793.
5666 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
5667 when we switch from being a public relay to a bridge. Otherwise
5668 there will still be clients that see the relay in their consensus,
5669 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
5671 - Instead of giving an assertion failure on an internal mismatch
5672 on estimated freelist size, just log a BUG warning and try later.
5673 Mitigates but does not fix bug 1125.
5674 - Fix an assertion failure that could occur in caches or bridge users
5675 when using a very short voting interval on a testing network.
5676 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
5678 o Minor bugfixes (on 0.2.2.x):
5679 - Alter directory authorities to always consider Exit-flagged nodes
5680 as potential Guard nodes in their votes. The actual decision to
5681 use Exits as Guards is done in the consensus bandwidth weights.
5682 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
5683 - When the controller is reporting the purpose of circuits that
5684 didn't finish building before the circuit build timeout, it was
5685 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
5686 - Our libevent version parsing code couldn't handle versions like
5687 1.4.14b-stable and incorrectly warned the user about using an
5688 old and broken version of libevent. Treat 1.4.14b-stable like
5689 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
5691 - Don't use substitution references like $(VAR:MOD) when
5692 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
5693 '$(:x)' to 'x' rather than the empty string. This bites us in
5694 doc/ when configured with --disable-asciidoc. Bugfix on
5695 0.2.2.9-alpha; fixes bug 1773.
5696 - Remove a spurious hidden service server-side log notice about
5697 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
5699 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
5701 - Correctly report written bytes on linked connections. Found while
5702 implementing 1790. Bugfix on 0.2.2.4-alpha.
5703 - Fix three memory leaks: one in circuit_build_times_parse_state(),
5704 one in dirvote_add_signatures_to_pending_consensus(), and one every
5705 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
5706 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
5708 o Code simplifications and refactoring:
5709 - Take a first step towards making or.h smaller by splitting out
5710 function definitions for all source files in src/or/. Leave
5711 structures and defines in or.h for now.
5712 - Remove a bunch of unused function declarations as well as a block of
5713 #if 0'd code from the unit tests. Closes bug 1824.
5714 - New unit tests for exit-port history statistics; refactored exit
5715 statistics code to be more easily tested.
5716 - Remove the old debian/ directory from the main Tor distribution.
5717 The official Tor-for-debian git repository lives at the URL
5718 https://git.torproject.org/debian/tor.git
5721 Changes in version 0.2.2.14-alpha - 2010-07-12
5722 Tor 0.2.2.14-alpha greatly improves client-side handling of
5723 circuit build timeouts, which are used to estimate speed and improve
5724 performance. We also move to a much better GeoIP database, port Tor to
5725 Windows CE, introduce new compile flags that improve code security,
5726 add an eighth v3 directory authority, and address a lot of more
5730 - Tor directory authorities no longer crash when started with a
5731 cached-microdesc-consensus file in their data directory. Bugfix
5732 on 0.2.2.6-alpha; fixes bug 1532.
5733 - Treat an unset $HOME like an empty $HOME rather than triggering an
5734 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
5735 - Ignore negative and large circuit build timeout values that can
5736 happen during a suspend or hibernate. These values caused various
5737 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
5738 - Alter calculation of Pareto distribution parameter 'Xm' for
5739 Circuit Build Timeout learning to use the weighted average of the
5740 top N=3 modes (because we have three entry guards). Considering
5741 multiple modes should improve the timeout calculation in some cases,
5742 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
5744 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
5745 right censored distribution model. This approach improves over the
5746 synthetic timeout generation approach that was producing insanely
5747 high timeout values. Now we calculate build timeouts using truncated
5748 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
5749 - Do not close circuits that are under construction when they reach
5750 the circuit build timeout. Instead, leave them building (but do not
5751 use them) for up until the time corresponding to the 95th percentile
5752 on the Pareto CDF or 60 seconds, whichever is greater. This is done
5753 to provide better data for the new Pareto model. This percentile
5754 can be controlled by the consensus.
5757 - Move to the June 2010 Maxmind GeoLite country db (rather than the
5758 June 2009 ip-to-country GeoIP db) for our statistics that count
5759 how many users relays are seeing from each country. Now we have
5760 more accurate data for many African countries.
5761 - Port Tor to build and run correctly on Windows CE systems, using
5762 the wcecompat library. Contributed by Valerio Lupi.
5763 - New "--enable-gcc-hardening" ./configure flag (off by default)
5764 to turn on gcc compile time hardening options. It ensures
5765 that signed ints have defined behavior (-fwrapv), enables
5766 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
5767 with canaries (-fstack-protector-all), turns on ASLR protection if
5768 supported by the kernel (-fPIE, -pie), and adds additional security
5769 related warnings. Verified to work on Mac OS X and Debian Lenny.
5770 - New "--enable-linker-hardening" ./configure flag (off by default)
5771 to turn on ELF specific hardening features (relro, now). This does
5772 not work with Mac OS X or any other non-ELF binary format.
5774 o New directory authorities:
5775 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5779 - New config option "WarnUnsafeSocks 0" disables the warning that
5780 occurs whenever Tor receives a socks handshake using a version of
5781 the socks protocol that can only provide an IP address (rather
5782 than a hostname). Setups that do DNS locally over Tor are fine,
5783 and we shouldn't spam the logs in that case.
5784 - Convert the HACKING file to asciidoc, and add a few new sections
5785 to it, explaining how we use Git, how we make changelogs, and
5786 what should go in a patch.
5787 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
5788 event, to give information on the current rate of circuit timeouts
5789 over our stored history.
5790 - Add ability to disable circuit build time learning via consensus
5791 parameter and via a LearnCircuitBuildTimeout config option. Also
5792 automatically disable circuit build time calculation if we are
5793 either a AuthoritativeDirectory, or if we fail to write our state
5794 file. Fixes bug 1296.
5795 - More gracefully handle corrupt state files, removing asserts
5796 in favor of saving a backup and resetting state.
5797 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
5801 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5803 - When a2x fails, mention that the user could disable manpages instead
5804 of trying to fix their asciidoc installation.
5805 - Where available, use Libevent 2.0's periodic timers so that our
5806 once-per-second cleanup code gets called even more closely to
5807 once per second than it would otherwise. Fixes bug 943.
5808 - If you run a bridge that listens on multiple IP addresses, and
5809 some user configures a bridge address that uses a different IP
5810 address than your bridge writes in its router descriptor, and the
5811 user doesn't specify an identity key, their Tor would discard the
5812 descriptor because "it isn't one of our configured bridges", and
5813 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
5814 Bugfix on 0.2.0.3-alpha.
5815 - If OpenSSL fails to make a duplicate of a private or public key, log
5816 an error message and try to exit cleanly. May help with debugging
5817 if bug 1209 ever remanifests.
5818 - Save a couple bytes in memory allocation every time we escape
5819 certain characters in a string. Patch from Florian Zumbiehl.
5820 - Make it explicit that we don't cannibalize one-hop circuits. This
5821 happens in the wild, but doesn't turn out to be a problem because
5822 we fortunately don't use those circuits. Many thanks to outofwords
5823 for the initial analysis and to swissknife who confirmed that
5824 two-hop circuits are actually created.
5825 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
5826 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
5827 - Eliminate a case where a circuit build time warning was displayed
5828 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
5831 Changes in version 0.2.1.26 - 2010-05-02
5832 Tor 0.2.1.26 addresses the recent connection and memory overload
5833 problems we've been seeing on relays, especially relays with their
5834 DirPort open. If your relay has been crashing, or you turned it off
5835 because it used too many resources, give this release a try.
5837 This release also fixes yet another instance of broken OpenSSL libraries
5838 that was causing some relays to drop out of the consensus.
5841 - Teach relays to defend themselves from connection overload. Relays
5842 now close idle circuits early if it looks like they were intended
5843 for directory fetches. Relays are also more aggressive about closing
5844 TLS connections that have no circuits on them. Such circuits are
5845 unlikely to be re-used, and tens of thousands of them were piling
5846 up at the fast relays, causing the relays to run out of sockets
5847 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5848 their directory fetches over TLS).
5849 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5850 that claim to be earlier than 0.9.8m, but which have in reality
5851 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5852 behavior. Possible fix for some cases of bug 1346.
5853 - Directory mirrors were fetching relay descriptors only from v2
5854 directory authorities, rather than v3 authorities like they should.
5855 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5856 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5859 - Finally get rid of the deprecated and now harmful notion of "clique
5860 mode", where directory authorities maintain TLS connections to
5864 - In the util/threads test, no longer free the test_mutex before all
5865 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5866 - The master thread could starve the worker threads quite badly on
5867 certain systems, causing them to run only partially in the allowed
5868 window. This resulted in test failures. Now the master thread sleeps
5869 occasionally for a few microseconds while the two worker-threads
5870 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5873 Changes in version 0.2.2.13-alpha - 2010-04-24
5874 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
5875 problems we've been seeing on relays, especially relays with their
5876 DirPort open. If your relay has been crashing, or you turned it off
5877 because it used too many resources, give this release a try.
5880 - Teach relays to defend themselves from connection overload. Relays
5881 now close idle circuits early if it looks like they were intended
5882 for directory fetches. Relays are also more aggressive about closing
5883 TLS connections that have no circuits on them. Such circuits are
5884 unlikely to be re-used, and tens of thousands of them were piling
5885 up at the fast relays, causing the relays to run out of sockets
5886 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5887 their directory fetches over TLS).
5890 - Finally get rid of the deprecated and now harmful notion of "clique
5891 mode", where directory authorities maintain TLS connections to
5893 - Directory authorities now do an immediate reachability check as soon
5894 as they hear about a new relay. This change should slightly reduce
5895 the time between setting up a relay and getting listed as running
5896 in the consensus. It should also improve the time between setting
5897 up a bridge and seeing use by bridge users.
5898 - Directory authorities no longer launch a TLS connection to every
5899 relay as they startup. Now that we have 2k+ descriptors cached,
5900 the resulting network hiccup is becoming a burden. Besides,
5901 authorities already avoid voting about Running for the first half
5902 hour of their uptime.
5905 Changes in version 0.2.2.12-alpha - 2010-04-20
5906 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
5907 handle and vote on descriptors. It was causing relays to drop out of
5911 - Many relays have been falling out of the consensus lately because
5912 not enough authorities know about their descriptor for them to get
5913 a majority of votes. When we deprecated the v2 directory protocol,
5914 we got rid of the only way that v3 authorities can hear from each
5915 other about other descriptors. Now authorities examine every v3
5916 vote for new descriptors, and fetch them from that authority. Bugfix
5918 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
5919 and a warning in or.h related to bandwidth_weight_rule_t that
5920 prevented clean compile on OS X. Fixes bug 1363; bugfix on
5922 - Fix a segfault on relays when DirReqStatistics is enabled
5923 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
5927 - Demote a confusing TLS warning that relay operators might get when
5928 someone tries to talk to their OrPort. It is neither the operator's
5929 fault nor can they do anything about it. Fixes bug 1364; bugfix
5933 Changes in version 0.2.2.11-alpha - 2010-04-15
5934 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
5935 libraries that was causing some relays to drop out of the consensus.
5938 - Directory mirrors were fetching relay descriptors only from v2
5939 directory authorities, rather than v3 authorities like they should.
5940 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5941 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5942 - Fix a parsing error that made every possible value of
5943 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
5944 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
5945 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
5946 about the option without breaking older ones.
5947 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5948 that claim to be earlier than 0.9.8m, but which have in reality
5949 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5950 behavior. Possible fix for some cases of bug 1346.
5953 - Experiment with a more aggressive approach to preventing clients
5954 from making one-hop exit streams. Exit relays who want to try it
5955 out can set "RefuseUnknownExits 1" in their torrc, and then look
5956 for "Attempt by %s to open a stream" log messages. Let us know
5958 - Add support for statically linking zlib by specifying
5959 --enable-static-zlib, to go with our support for statically linking
5960 openssl and libevent. Resolves bug 1358.
5963 - Fix a segfault that happens whenever a Tor client that is using
5964 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
5966 - When we cleaned up the contrib/tor-exit-notice.html file, we left
5967 out the first line. Fixes bug 1295.
5968 - When building the manpage from a tarball, we required asciidoc, but
5969 the asciidoc -> roff/html conversion was already done for the
5970 tarball. Make 'make' complain only when we need asciidoc (either
5971 because we're compiling directly from git, or because we altered
5972 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
5973 - When none of the directory authorities vote on any params, Tor
5974 segfaulted when trying to make the consensus from the votes. We
5975 didn't trigger the bug in practice, because authorities do include
5976 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
5979 - In the util/threads test, no longer free the test_mutex before all
5980 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5981 - The master thread could starve the worker threads quite badly on
5982 certain systems, causing them to run only partially in the allowed
5983 window. This resulted in test failures. Now the master thread sleeps
5984 occasionally for a few microseconds while the two worker-threads
5985 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5988 Changes in version 0.2.2.10-alpha - 2010-03-07
5989 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
5990 could prevent relays from guessing their IP address correctly. It also
5991 starts the groundwork for another client-side performance boost, since
5992 currently we're not making efficient use of relays that have both the
5993 Guard flag and the Exit flag.
5996 - Fix a regression from our patch for bug 1244 that caused relays
5997 to guess their IP address incorrectly if they didn't set Address
5998 in their torrc and/or their address fails to resolve. Bugfix on
5999 0.2.2.9-alpha; fixes bug 1269.
6001 o Major features (performance):
6002 - Directory authorities now compute consensus weightings that instruct
6003 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6004 and no flag. Clients that use these weightings will distribute
6005 network load more evenly across these different relay types. The
6006 weightings are in the consensus so we can change them globally in
6007 the future. Extra thanks to "outofwords" for finding some nasty
6008 security bugs in the first implementation of this feature.
6010 o Minor features (performance):
6011 - Always perform router selections using weighted relay bandwidth,
6012 even if we don't need a high capacity circuit at the time. Non-fast
6013 circuits now only differ from fast ones in that they can use relays
6014 not marked with the Fast flag. This "feature" could turn out to
6015 be a horrible bug; we should investigate more before it goes into
6019 - Allow disabling building of the manpages. Skipping the manpage
6020 speeds up the build considerably.
6022 o Minor bugfixes (on 0.2.2.x):
6023 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6024 Bugfix on 0.2.2.9-alpha.
6025 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6026 config option. Bugfix on 0.2.2.7-alpha.
6027 - Ship the asciidoc-helper file in the tarball, so that people can
6028 build from source if they want to, and touching the .1.txt files
6029 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6031 o Minor bugfixes (on 0.2.1.x or earlier):
6032 - Fix a dereference-then-NULL-check sequence when publishing
6033 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6035 - Fix another dereference-then-NULL-check sequence. Bugfix on
6036 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6037 - Make sure we treat potentially not NUL-terminated strings correctly.
6038 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6040 o Code simplifications and refactoring:
6041 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6042 compliant. Based on a patch from Christian Kujau.
6043 - Don't use sed in asciidoc-helper anymore.
6044 - Make the build process fail if asciidoc cannot be found and
6045 building with asciidoc isn't disabled.
6048 Changes in version 0.2.2.9-alpha - 2010-02-22
6049 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6050 location of a directory authority, and cleans up a bunch of small bugs.
6052 o Directory authority changes:
6053 - Change IP address for dannenberg (v3 directory authority), and
6054 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6055 service directory authority) from the list.
6058 - Make Tor work again on the latest OS X: when deciding whether to
6059 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6060 version at run-time, not compile time. We need to do this because
6061 Apple doesn't update its dev-tools headers when it updates its
6062 libraries in a security patch.
6063 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6064 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6065 a memory leak when requesting a hidden service descriptor we've
6066 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6068 - Authorities could be tricked into giving out the Exit flag to relays
6069 that didn't allow exiting to any ports. This bug could screw
6070 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6071 1238. Bug discovered by Martin Kowalczyk.
6072 - When freeing a session key, zero it out completely. We only zeroed
6073 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6074 patched by ekir. Fixes bug 1254.
6077 - Fix static compilation by listing the openssl libraries in the right
6078 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6079 - Resume handling .exit hostnames in a special way: originally we
6080 stripped the .exit part and used the requested exit relay. In
6081 0.2.2.1-alpha we stopped treating them in any special way, meaning
6082 if you use a .exit address then Tor will pass it on to the exit
6083 relay. Now we reject the .exit stream outright, since that behavior
6084 might be more expected by the user. Found and diagnosed by Scott
6085 Bennett and Downie on or-talk.
6086 - Don't spam the controller with events when we have no file
6087 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6088 for log messages was already solved from bug 748.)
6089 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6091 - Make the DNSPort option work with libevent 2.x. Don't alter the
6092 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6093 - Emit a GUARD DROPPED controller event for a case we missed.
6094 - Make more fields in the controller protocol case-insensitive, since
6095 control-spec.txt said they were.
6096 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6097 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6098 - Fix a spec conformance issue: the network-status-version token
6099 must be the first token in a v3 consensus or vote. Discovered by
6100 parakeep. Bugfix on 0.2.0.3-alpha.
6102 o Code simplifications and refactoring:
6103 - Generate our manpage and HTML documentation using Asciidoc. This
6104 change should make it easier to maintain the documentation, and
6106 - Remove the --enable-iphone option. According to reports from Marco
6107 Bonetti, Tor builds fine without any special tweaking on recent
6108 iPhone SDK versions.
6109 - Removed some unnecessary files from the source distribution. The
6110 AUTHORS file has now been merged into the people page on the
6111 website. The roadmaps and design doc can now be found in the
6112 projects directory in svn.
6113 - Enabled various circuit build timeout constants to be controlled
6114 by consensus parameters. Also set better defaults for these
6115 parameters based on experimentation on broadband and simulated
6119 - The 'EXTENDCIRCUIT' control port command can now be used with
6120 a circ id of 0 and no path. This feature will cause Tor to build
6121 a new 'fast' general purpose circuit using its own path selection
6123 - Added a BUILDTIMEOUT_SET controller event to describe changes
6124 to the circuit build timeout.
6125 - Future-proof the controller protocol a bit by ignoring keyword
6126 arguments we do not recognize.
6127 - Expand homedirs passed to tor-checkkey. This should silence a
6128 coverity complaint about passing a user-supplied string into
6129 open() without checking it.
6132 Changes in version 0.2.1.25 - 2010-03-16
6133 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6134 prevent relays from guessing their IP address correctly. It also fixes
6135 several minor potential security bugs.
6138 - Fix a regression from our patch for bug 1244 that caused relays
6139 to guess their IP address incorrectly if they didn't set Address
6140 in their torrc and/or their address fails to resolve. Bugfix on
6141 0.2.1.23; fixes bug 1269.
6142 - When freeing a session key, zero it out completely. We only zeroed
6143 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6144 patched by ekir. Fixes bug 1254.
6147 - Fix a dereference-then-NULL-check sequence when publishing
6148 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6150 - Fix another dereference-then-NULL-check sequence. Bugfix on
6151 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6152 - Make sure we treat potentially not NUL-terminated strings correctly.
6153 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6157 Changes in version 0.2.1.24 - 2010-02-21
6158 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6162 - Work correctly out-of-the-box with even more vendor-patched versions
6163 of OpenSSL. In particular, make it so Debian and OS X don't need
6164 customized patches to run/build.
6167 Changes in version 0.2.1.23 - 2010-02-13
6168 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6169 again on the latest OS X, and updates the location of a directory
6172 o Major bugfixes (performance):
6173 - We were selecting our guards uniformly at random, and then weighting
6174 which of our guards we'd use uniformly at random. This imbalance
6175 meant that Tor clients were severely limited on throughput (and
6176 probably latency too) by the first hop in their circuit. Now we
6177 select guards weighted by currently advertised bandwidth. We also
6178 automatically discard guards picked using the old algorithm. Fixes
6179 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6182 - Make Tor work again on the latest OS X: when deciding whether to
6183 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6184 version at run-time, not compile time. We need to do this because
6185 Apple doesn't update its dev-tools headers when it updates its
6186 libraries in a security patch.
6187 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6188 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6189 a memory leak when requesting a hidden service descriptor we've
6190 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6193 o Directory authority changes:
6194 - Change IP address for dannenberg (v3 directory authority), and
6195 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6196 service directory authority) from the list.
6199 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6200 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6203 - Avoid a mad rush at the beginning of each month when each client
6204 rotates half of its guards. Instead we spread the rotation out
6205 throughout the month, but we still avoid leaving a precise timestamp
6206 in the state file about when we first picked the guard. Improves
6207 over the behavior introduced in 0.1.2.17.
6210 Changes in version 0.2.2.8-alpha - 2010-01-26
6211 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6212 causing bridge relays to disappear. If you're running a bridge,
6216 - Fix a memory corruption bug on bridges that occured during the
6217 inclusion of stats data in extra-info descriptors. Also fix the
6218 interface for geoip_get_bridge_stats* to prevent similar bugs in
6219 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6220 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6223 - Ignore OutboundBindAddress when connecting to localhost.
6224 Connections to localhost need to come _from_ localhost, or else
6225 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6229 Changes in version 0.2.2.7-alpha - 2010-01-19
6230 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6231 as laying the groundwork for further relay-side performance fixes. It
6232 also starts cleaning up client behavior with respect to the EntryNodes,
6233 ExitNodes, and StrictNodes config options.
6235 This release also rotates two directory authority keys, due to a
6236 security breach of some of the Torproject servers.
6238 o Directory authority changes:
6239 - Rotate keys (both v3 identity and relay identity) for moria1
6242 o Major features (performance):
6243 - We were selecting our guards uniformly at random, and then weighting
6244 which of our guards we'd use uniformly at random. This imbalance
6245 meant that Tor clients were severely limited on throughput (and
6246 probably latency too) by the first hop in their circuit. Now we
6247 select guards weighted by currently advertised bandwidth. We also
6248 automatically discard guards picked using the old algorithm. Fixes
6249 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6250 - When choosing which cells to relay first, relays can now favor
6251 circuits that have been quiet recently, to provide lower latency
6252 for low-volume circuits. By default, relays enable or disable this
6253 feature based on a setting in the consensus. You can override
6254 this default by using the new "CircuitPriorityHalflife" config
6255 option. Design and code by Ian Goldberg, Can Tang, and Chris
6257 - Add separate per-conn write limiting to go with the per-conn read
6258 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6259 but never per-conn write limits.
6260 - New consensus params "bwconnrate" and "bwconnburst" to let us
6261 rate-limit client connections as they enter the network. It's
6262 controlled in the consensus so we can turn it on and off for
6263 experiments. It's starting out off. Based on proposal 163.
6265 o Major features (relay selection options):
6266 - Switch to a StrictNodes config option, rather than the previous
6267 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6268 "StrictExcludeNodes" option.
6269 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6270 change during a config reload, mark and discard all our origin
6271 circuits. This fix should address edge cases where we change the
6272 config options and but then choose a circuit that we created before
6274 - If EntryNodes or ExitNodes are set, be more willing to use an
6275 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6277 - Make EntryNodes config option much more aggressive even when
6278 StrictNodes is not set. Before it would prepend your requested
6279 entrynodes to your list of guard nodes, but feel free to use others
6280 after that. Now it chooses only from your EntryNodes if any of
6281 those are available, and only falls back to others if a) they're
6282 all down and b) StrictNodes is not set.
6283 - Now we refresh your entry guards from EntryNodes at each consensus
6284 fetch -- rather than just at startup and then they slowly rot as
6285 the network changes.
6288 - Stop bridge directory authorities from answering dbg-stability.txt
6289 directory queries, which would let people fetch a list of all
6290 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6293 - Log a notice when we get a new control connection. Now it's easier
6294 for security-conscious users to recognize when a local application
6295 is knocking on their controller door. Suggested by bug 1196.
6296 - New config option "CircuitStreamTimeout" to override our internal
6297 timeout schedule for how many seconds until we detach a stream from
6298 a circuit and try a new circuit. If your network is particularly
6299 slow, you might want to set this to a number like 60.
6300 - New controller command "getinfo config-text". It returns the
6301 contents that Tor would write if you send it a SAVECONF command,
6302 so the controller can write the file to disk itself.
6303 - New options for SafeLogging to allow scrubbing only log messages
6304 generated while acting as a relay.
6305 - Ship the bridges spec file in the tarball too.
6306 - Avoid a mad rush at the beginning of each month when each client
6307 rotates half of its guards. Instead we spread the rotation out
6308 throughout the month, but we still avoid leaving a precise timestamp
6309 in the state file about when we first picked the guard. Improves
6310 over the behavior introduced in 0.1.2.17.
6312 o Minor bugfixes (compiling):
6313 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6314 hides it. Bugfix on 0.2.2.6-alpha.
6315 - Fix compilation on Solaris by removing support for the
6316 DisableAllSwap config option. Solaris doesn't have an rlimit for
6317 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6320 o Minor bugfixes (crashes):
6321 - Do not segfault when writing buffer stats when we haven't observed
6322 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6324 - If we're in the pathological case where there's no exit bandwidth
6325 but there is non-exit bandwidth, or no guard bandwidth but there
6326 is non-guard bandwidth, don't crash during path selection. Bugfix
6328 - Fix an impossible-to-actually-trigger buffer overflow in relay
6329 descriptor generation. Bugfix on 0.1.0.15.
6331 o Minor bugfixes (privacy):
6332 - Fix an instance where a Tor directory mirror might accidentally
6333 log the IP address of a misbehaving Tor client. Bugfix on
6335 - Don't list Windows capabilities in relay descriptors. We never made
6336 use of them, and maybe it's a bad idea to publish them. Bugfix
6339 o Minor bugfixes (other):
6340 - Resolve an edge case in path weighting that could make us misweight
6341 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6342 - Fix statistics on client numbers by country as seen by bridges that
6343 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6344 intervals instead of variable 12-to-48-hour intervals.
6345 - After we free an internal connection structure, overwrite it
6346 with a different memory value than we use for overwriting a freed
6347 internal circuit structure. Should help with debugging. Suggested
6349 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6353 - Remove the HSAuthorityRecordStats option that version 0 hidden
6354 service authorities could have used to track statistics of overall
6355 hidden service usage.
6358 Changes in version 0.2.1.22 - 2010-01-19
6359 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6360 authorities -- it would tell you its whole history of bridge descriptors
6361 if you make the right directory request. This stable update also
6362 rotates two of the seven v3 directory authority keys and locations.
6364 o Directory authority changes:
6365 - Rotate keys (both v3 identity and relay identity) for moria1
6369 - Stop bridge directory authorities from answering dbg-stability.txt
6370 directory queries, which would let people fetch a list of all
6371 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6374 Changes in version 0.2.1.21 - 2009-12-21
6375 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6376 library. If you use Tor on Linux / Unix and you're getting SSL
6377 renegotiation errors, upgrading should help. We also recommend an
6378 upgrade if you're an exit relay.
6381 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6382 handshake from working unless we explicitly tell OpenSSL that we
6383 are using SSL renegotiation safely. We are, of course, but OpenSSL
6384 0.9.8l won't work unless we say we are.
6385 - Avoid crashing if the client is trying to upload many bytes and the
6386 circuit gets torn down at the same time, or if the flip side
6387 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6390 - Do not refuse to learn about authority certs and v2 networkstatus
6391 documents that are older than the latest consensus. This bug might
6392 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6393 Spotted and fixed by xmux.
6394 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6395 trigger platform-specific option misparsing case found by Coverity
6397 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6398 trigger assert. Fixes bug 1173.
6401 Changes in version 0.2.2.6-alpha - 2009-11-19
6402 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6403 support for the new lower-footprint "microdescriptor" directory design,
6404 future-proofing our consensus format against new hash functions or
6405 other changes, and an Android port. It also makes Tor compatible with
6406 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6409 - Directory authorities can now create, vote on, and serve multiple
6410 parallel formats of directory data as part of their voting process.
6411 Partially implements Proposal 162: "Publish the consensus in
6413 - Directory authorities can now agree on and publish small summaries
6414 of router information that clients can use in place of regular
6415 server descriptors. This transition will eventually allow clients
6416 to use far less bandwidth for downloading information about the
6417 network. Begins the implementation of Proposal 158: "Clients
6418 download consensus + microdescriptors".
6419 - The directory voting system is now extensible to use multiple hash
6420 algorithms for signatures and resource selection. Newer formats
6421 are signed with SHA256, with a possibility for moving to a better
6422 hash algorithm in the future.
6423 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6424 current and future memory pages via mlockall(). On supported
6425 platforms (modern Linux and probably BSD but not Windows or OS X),
6426 this should effectively disable any and all attempts to page out
6427 memory. This option requires that you start your Tor as root --
6428 if you use DisableAllSwap, please consider using the User option
6429 to properly reduce the privileges of your Tor.
6430 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6431 to help Tor build correctly for Android phones.
6434 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6435 handshake from working unless we explicitly tell OpenSSL that we
6436 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6437 won't work unless we say we are.
6440 - Fix a crash bug when trying to initialize the evdns module in
6441 Libevent 2. Bugfix on 0.2.1.16-rc.
6442 - Stop logging at severity 'warn' when some other Tor client tries
6443 to establish a circuit with us using weak DH keys. It's a protocol
6444 violation, but that doesn't mean ordinary users need to hear about
6445 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6446 - Do not refuse to learn about authority certs and v2 networkstatus
6447 documents that are older than the latest consensus. This bug might
6448 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6449 Spotted and fixed by xmux.
6450 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6451 - If all authorities restart at once right before a consensus vote,
6452 nobody will vote about "Running", and clients will get a consensus
6453 with no usable relays. Instead, authorities refuse to build a
6454 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6455 - If your relay can't keep up with the number of incoming create
6456 cells, it would log one warning per failure into your logs. Limit
6457 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6458 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6459 on 0.2.0.3-alpha; fixes bug 1113.
6460 - Fix a memory leak on directory authorities during voting that was
6461 introduced in 0.2.2.1-alpha. Found via valgrind.
6464 Changes in version 0.2.1.20 - 2009-10-15
6465 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6466 services at once, prepares for more performance improvements, and
6467 fixes a bunch of smaller bugs.
6469 The Windows and OS X bundles also include a more recent Vidalia,
6470 and switch from Privoxy to Polipo.
6472 The OS X installers are now drag and drop. It's best to un-install
6473 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6474 you want to upgrade, you'll need to update the paths for Tor and Polipo
6475 in the Vidalia Settings window.
6478 - Send circuit or stream sendme cells when our window has decreased
6479 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6480 by Karsten when testing the "reduce circuit window" performance
6481 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6482 before the release of Tor 0.0.0. This is the new winner of the
6484 - Fix a remotely triggerable memory leak when a consensus document
6485 contains more than one signature from the same voter. Bugfix on
6487 - Avoid segfault in rare cases when finishing an introduction circuit
6488 as a client and finding out that we don't have an introduction key
6489 for it. Fixes bug 1073. Reported by Aaron Swartz.
6492 - Tor now reads the "circwindow" parameter out of the consensus,
6493 and uses that value for its circuit package window rather than the
6494 default of 1000 cells. Begins the implementation of proposal 168.
6496 o New directory authorities:
6497 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6499 - Move moria1 and tonga to alternate IP addresses.
6502 - Fix a signed/unsigned compile warning in 0.2.1.19.
6503 - Fix possible segmentation fault on directory authorities. Bugfix on
6505 - Fix an extremely rare infinite recursion bug that could occur if
6506 we tried to log a message after shutting down the log subsystem.
6507 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6508 - Fix an obscure bug where hidden services on 64-bit big-endian
6509 systems might mis-read the timestamp in v3 introduce cells, and
6510 refuse to connect back to the client. Discovered by "rotor".
6511 Bugfix on 0.2.1.6-alpha.
6512 - We were triggering a CLOCK_SKEW controller status event whenever
6513 we connect via the v2 connection protocol to any relay that has
6514 a wrong clock. Instead, we should only inform the controller when
6515 it's a trusted authority that claims our clock is wrong. Bugfix
6516 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6517 - We were telling the controller about CHECKING_REACHABILITY and
6518 REACHABILITY_FAILED status events whenever we launch a testing
6519 circuit or notice that one has failed. Instead, only tell the
6520 controller when we want to inform the user of overall success or
6521 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6523 - Don't warn when we're using a circuit that ends with a node
6524 excluded in ExcludeExitNodes, but the circuit is not used to access
6525 the outside world. This should help fix bug 1090. Bugfix on
6527 - Work around a small memory leak in some versions of OpenSSL that
6528 stopped the memory used by the hostname TLS extension from being
6532 - Add a "getinfo status/accepted-server-descriptor" controller
6533 command, which is the recommended way for controllers to learn
6534 whether our server descriptor has been successfully received by at
6535 least on directory authority. Un-recommend good-server-descriptor
6536 getinfo and status events until we have a better design for them.
6539 Changes in version 0.2.2.5-alpha - 2009-10-11
6540 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
6543 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
6545 o Directory authorities:
6546 - Temporarily (just for this release) move dizum to an alternate
6550 Changes in version 0.2.2.4-alpha - 2009-10-10
6551 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
6552 introduces a new unit test framework, shifts directry authority
6553 addresses around to reduce the impact from recent blocking events,
6554 and fixes a few smaller bugs.
6557 - Fix several more asserts in the circuit_build_times code, for
6558 example one that causes Tor to fail to start once we have
6559 accumulated 5000 build times in the state file. Bugfixes on
6560 0.2.2.2-alpha; fixes bug 1108.
6562 o New directory authorities:
6563 - Move moria1 and Tonga to alternate IP addresses.
6566 - Log SSL state transitions at debug level during handshake, and
6567 include SSL states in error messages. This may help debug future
6568 SSL handshake issues.
6569 - Add a new "Handshake" log domain for activities that happen
6570 during the TLS handshake.
6571 - Revert to the "June 3 2009" ip-to-country file. The September one
6572 seems to have removed most US IP addresses.
6573 - Directory authorities now reject Tor relays with versions less than
6574 0.1.2.14. This step cuts out four relays from the current network,
6575 none of which are very big.
6578 - Fix a couple of smaller issues with gathering statistics. Bugfixes
6580 - Fix two memory leaks in the error case of
6581 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
6582 - Don't count one-hop circuits when we're estimating how long it
6583 takes circuits to build on average. Otherwise we'll set our circuit
6584 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
6585 - Directory authorities no longer change their opinion of, or vote on,
6586 whether a router is Running, unless they have themselves been
6587 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
6590 o Code simplifications and refactoring:
6591 - Revise our unit tests to use the "tinytest" framework, so we
6592 can run tests in their own processes, have smarter setup/teardown
6593 code, and so on. The unit test code has moved to its own
6594 subdirectory, and has been split into multiple modules.
6597 Changes in version 0.2.2.3-alpha - 2009-09-23
6598 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
6601 - Fix an overzealous assert in our new circuit build timeout code.
6602 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
6605 - If the networkstatus consensus tells us that we should use a
6606 negative circuit package window, ignore it. Otherwise we'll
6607 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
6610 Changes in version 0.2.2.2-alpha - 2009-09-21
6611 Tor 0.2.2.2-alpha introduces our latest performance improvement for
6612 clients: Tor tracks the average time it takes to build a circuit, and
6613 avoids using circuits that take too long to build. For fast connections,
6614 this feature can cut your expected latency in half. For slow or flaky
6615 connections, it could ruin your Tor experience. Let us know if it does!
6618 - Tor now tracks how long it takes to build client-side circuits
6619 over time, and adapts its timeout to local network performance.
6620 Since a circuit that takes a long time to build will also provide
6621 bad performance, we get significant latency improvements by
6622 discarding the slowest 20% of circuits. Specifically, Tor creates
6623 circuits more aggressively than usual until it has enough data
6624 points for a good timeout estimate. Implements proposal 151.
6625 We are especially looking for reports (good and bad) from users with
6626 both EDGE and broadband connections that can move from broadband
6627 to EDGE and find out if the build-time data in the .tor/state gets
6628 reset without loss of Tor usability. You should also see a notice
6629 log message telling you that Tor has reset its timeout.
6630 - Directory authorities can now vote on arbitary integer values as
6631 part of the consensus process. This is designed to help set
6632 network-wide parameters. Implements proposal 167.
6633 - Tor now reads the "circwindow" parameter out of the consensus,
6634 and uses that value for its circuit package window rather than the
6635 default of 1000 cells. Begins the implementation of proposal 168.
6638 - Fix a remotely triggerable memory leak when a consensus document
6639 contains more than one signature from the same voter. Bugfix on
6643 - Fix an extremely rare infinite recursion bug that could occur if
6644 we tried to log a message after shutting down the log subsystem.
6645 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6646 - Fix parsing for memory or time units given without a space between
6647 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
6648 - A networkstatus vote must contain exactly one signature. Spec
6649 conformance issue. Bugfix on 0.2.0.3-alpha.
6650 - Fix an obscure bug where hidden services on 64-bit big-endian
6651 systems might mis-read the timestamp in v3 introduce cells, and
6652 refuse to connect back to the client. Discovered by "rotor".
6653 Bugfix on 0.2.1.6-alpha.
6654 - We were triggering a CLOCK_SKEW controller status event whenever
6655 we connect via the v2 connection protocol to any relay that has
6656 a wrong clock. Instead, we should only inform the controller when
6657 it's a trusted authority that claims our clock is wrong. Bugfix
6658 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6659 - We were telling the controller about CHECKING_REACHABILITY and
6660 REACHABILITY_FAILED status events whenever we launch a testing
6661 circuit or notice that one has failed. Instead, only tell the
6662 controller when we want to inform the user of overall success or
6663 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6665 - Don't warn when we're using a circuit that ends with a node
6666 excluded in ExcludeExitNodes, but the circuit is not used to access
6667 the outside world. This should help fix bug 1090, but more problems
6668 remain. Bugfix on 0.2.1.6-alpha.
6669 - Work around a small memory leak in some versions of OpenSSL that
6670 stopped the memory used by the hostname TLS extension from being
6672 - Make our 'torify' script more portable; if we have only one of
6673 'torsocks' or 'tsocks' installed, don't complain to the user;
6674 and explain our warning about tsocks better.
6677 - Add a "getinfo status/accepted-server-descriptor" controller
6678 command, which is the recommended way for controllers to learn
6679 whether our server descriptor has been successfully received by at
6680 least on directory authority. Un-recommend good-server-descriptor
6681 getinfo and status events until we have a better design for them.
6682 - Update to the "September 4 2009" ip-to-country file.
6685 Changes in version 0.2.2.1-alpha - 2009-08-26
6686 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
6687 Tor clients to bootstrap on networks where only port 80 is reachable,
6688 makes it more straightforward to support hardware crypto accelerators,
6689 and starts the groundwork for gathering stats safely at relays.
6692 - Start the process of disabling ".exit" address notation, since it
6693 can be used for a variety of esoteric application-level attacks
6694 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
6697 o New directory authorities:
6698 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6702 - New AccelName and AccelDir options add support for dynamic OpenSSL
6703 hardware crypto acceleration engines.
6704 - Tor now supports tunneling all of its outgoing connections over
6705 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
6706 configuration options. Code by Christopher Davis.
6709 - Send circuit or stream sendme cells when our window has decreased
6710 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6711 by Karsten when testing the "reduce circuit window" performance
6712 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6713 before the release of Tor 0.0.0. This is the new winner of the
6716 o New options for gathering stats safely:
6717 - Directory mirrors that set "DirReqStatistics 1" write statistics
6718 about directory requests to disk every 24 hours. As compared to the
6719 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
6720 1) stats are written to disk exactly every 24 hours; 2) estimated
6721 shares of v2 and v3 requests are determined as mean values, not at
6722 the end of a measurement period; 3) unresolved requests are listed
6723 with country code '??'; 4) directories also measure download times.
6724 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
6725 number of exit streams and transferred bytes per port to disk every
6727 - Relays that set "CellStatistics 1" write statistics on how long
6728 cells spend in their circuit queues to disk every 24 hours.
6729 - Entry nodes that set "EntryStatistics 1" write statistics on the
6730 rough number and origins of connecting clients to disk every 24
6732 - Relays that write any of the above statistics to disk and set
6733 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
6734 their extra-info documents.
6737 - New --digests command-line switch to output the digests of the
6738 source files Tor was built with.
6739 - The "torify" script now uses torsocks where available.
6740 - The memarea code now uses a sentinel value at the end of each area
6741 to make sure nothing writes beyond the end of an area. This might
6742 help debug some conceivable causes of bug 930.
6743 - Time and memory units in the configuration file can now be set to
6744 fractional units. For example, "2.5 GB" is now a valid value for
6746 - Certain Tor clients (such as those behind check.torproject.org) may
6747 want to fetch the consensus in an extra early manner. To enable this
6748 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
6749 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
6750 as only certain clients who must have this information sooner should
6752 - Instead of adding the svn revision to the Tor version string, report
6753 the git commit (when we're building from a git checkout).
6756 - If any of the v3 certs we download are unparseable, we should
6757 actually notice the failure so we don't retry indefinitely. Bugfix
6758 on 0.2.0.x; reported by "rotator".
6759 - If the cached cert file is unparseable, warn but don't exit.
6760 - Fix possible segmentation fault on directory authorities. Bugfix on
6762 - When Tor fails to parse a descriptor of any kind, dump it to disk.
6763 Might help diagnosing bug 1051.
6765 o Deprecated and removed features:
6766 - The controller no longer accepts the old obsolete "addr-mappings/"
6767 or "unregistered-servers-" GETINFO values.
6768 - Hidden services no longer publish version 0 descriptors, and clients
6769 do not request or use version 0 descriptors. However, the old hidden
6770 service authorities still accept and serve version 0 descriptors
6771 when contacted by older hidden services/clients.
6772 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
6773 always on; using them is necessary for correct forward-compatible
6775 - Remove support for .noconnect style addresses. Nobody was using
6776 them, and they provided another avenue for detecting Tor users
6777 via application-level web tricks.
6779 o Packaging changes:
6780 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
6781 installer bundles. See
6782 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
6783 for details of what's new in Vidalia 0.2.3.
6784 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
6785 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
6786 configuration file, rather than the old Privoxy.
6787 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
6788 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
6789 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
6790 better compatibility with OS X 10.6, aka Snow Leopard.
6791 - OS X Vidalia Bundle: The multi-package installer is now replaced
6792 by a simple drag and drop to the /Applications folder. This change
6793 occurred with the upgrade to Vidalia 0.2.3.
6796 Changes in version 0.2.1.19 - 2009-07-28
6797 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
6798 services on Tor 0.2.1.3-alpha through 0.2.1.18.
6801 - Make accessing hidden services on 0.2.1.x work right again.
6802 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
6803 part of patch provided by "optimist".
6806 - When a relay/bridge is writing out its identity key fingerprint to
6807 the "fingerprint" file and to its logs, write it without spaces. Now
6808 it will look like the fingerprints in our bridges documentation,
6809 and confuse fewer users.
6812 - Relays no longer publish a new server descriptor if they change
6813 their MaxAdvertisedBandwidth config option but it doesn't end up
6814 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
6815 fixes bug 1026. Patch from Sebastian.
6816 - Avoid leaking memory every time we get a create cell but we have
6817 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
6818 fixes bug 1034. Reported by BarkerJr.
6821 Changes in version 0.2.1.18 - 2009-07-24
6822 Tor 0.2.1.18 lays the foundations for performance improvements,
6823 adds status events to help users diagnose bootstrap problems, adds
6824 optional authentication/authorization for hidden services, fixes a
6825 variety of potential anonymity problems, and includes a huge pile of
6826 other features and bug fixes.
6829 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
6832 Changes in version 0.2.1.17-rc - 2009-07-07
6833 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
6834 candidate for the 0.2.1.x series. It lays the groundwork for further
6835 client performance improvements, and also fixes a big bug with directory
6836 authorities that were causing them to assign Guard and Stable flags
6839 The Windows bundles also finally include the geoip database that we
6840 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
6841 should actually install Torbutton rather than giving you a cryptic
6842 failure message (oops).
6845 - Clients now use the bandwidth values in the consensus, rather than
6846 the bandwidth values in each relay descriptor. This approach opens
6847 the door to more accurate bandwidth estimates once the directory
6848 authorities start doing active measurements. Implements more of
6852 - When Tor clients restart after 1-5 days, they discard all their
6853 cached descriptors as too old, but they still use the cached
6854 consensus document. This approach is good for robustness, but
6855 bad for performance: since they don't know any bandwidths, they
6856 end up choosing at random rather than weighting their choice by
6857 speed. Fixed by the above feature of putting bandwidths in the
6858 consensus. Bugfix on 0.2.0.x.
6859 - Directory authorities were neglecting to mark relays down in their
6860 internal histories if the relays fall off the routerlist without
6861 ever being found unreachable. So there were relays in the histories
6862 that haven't been seen for eight months, and are listed as being
6863 up for eight months. This wreaked havoc on the "median wfu"
6864 and "median mtbf" calculations, in turn making Guard and Stable
6865 flags very wrong, hurting network performance. Fixes bugs 696 and
6866 969. Bugfix on 0.2.0.6-alpha.
6869 - Serve the DirPortFrontPage page even when we have been approaching
6870 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
6871 - The control port would close the connection before flushing long
6872 replies, such as the network consensus, if a QUIT command was issued
6873 before the reply had completed. Now, the control port flushes all
6874 pending replies before closing the connection. Also fixed a spurious
6875 warning when a QUIT command is issued after a malformed or rejected
6876 AUTHENTICATE command, but before the connection was closed. Patch
6877 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
6878 - When we can't find an intro key for a v2 hidden service descriptor,
6879 fall back to the v0 hidden service descriptor and log a bug message.
6880 Workaround for bug 1024.
6881 - Fix a log message that did not respect the SafeLogging option.
6885 - If we're a relay and we change our IP address, be more verbose
6886 about the reason that made us change. Should help track down
6887 further bugs for relays on dynamic IP addresses.
6890 Changes in version 0.2.0.35 - 2009-06-24
6892 - Avoid crashing in the presence of certain malformed descriptors.
6893 Found by lark, and by automated fuzzing.
6894 - Fix an edge case where a malicious exit relay could convince a
6895 controller that the client's DNS question resolves to an internal IP
6896 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6899 - Finally fix the bug where dynamic-IP relays disappear when their
6900 IP address changes: directory mirrors were mistakenly telling
6901 them their old address if they asked via begin_dir, so they
6902 never got an accurate answer about their new address, so they
6903 just vanished after a day. For belt-and-suspenders, relays that
6904 don't set Address in their config now avoid using begin_dir for
6905 all direct connections. Should fix bugs 827, 883, and 900.
6906 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6907 that would occur on some exit nodes when DNS failures and timeouts
6908 occurred in certain patterns. Fix for bug 957.
6911 - When starting with a cache over a few days old, do not leak
6912 memory for the obsolete router descriptors in it. Bugfix on
6913 0.2.0.33; fixes bug 672.
6914 - Hidden service clients didn't use a cached service descriptor that
6915 was older than 15 minutes, but wouldn't fetch a new one either,
6916 because there was already one in the cache. Now, fetch a v2
6917 descriptor unless the same descriptor was added to the cache within
6918 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6921 Changes in version 0.2.1.16-rc - 2009-06-20
6922 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
6923 a bunch of minor bugs.
6926 - Fix an edge case where a malicious exit relay could convince a
6927 controller that the client's DNS question resolves to an internal IP
6928 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6930 o Major performance improvements (on 0.2.0.x):
6931 - Disable and refactor some debugging checks that forced a linear scan
6932 over the whole server-side DNS cache. These accounted for over 50%
6933 of CPU time on a relatively busy exit node's gprof profile. Found
6935 - Disable some debugging checks that appeared in exit node profile
6939 - Update to the "June 3 2009" ip-to-country file.
6940 - Do not have tor-resolve automatically refuse all .onion addresses;
6941 if AutomapHostsOnResolve is set in your torrc, this will work fine.
6943 o Minor bugfixes (on 0.2.0.x):
6944 - Log correct error messages for DNS-related network errors on
6946 - Fix a race condition that could cause crashes or memory corruption
6947 when running as a server with a controller listening for log
6949 - Avoid crashing when we have a policy specified in a DirPolicy or
6950 SocksPolicy or ReachableAddresses option with ports set on it,
6951 and we re-load the policy. May fix bug 996.
6952 - Hidden service clients didn't use a cached service descriptor that
6953 was older than 15 minutes, but wouldn't fetch a new one either,
6954 because there was already one in the cache. Now, fetch a v2
6955 descriptor unless the same descriptor was added to the cache within
6956 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6958 o Minor bugfixes (on 0.2.1.x):
6959 - Don't warn users about low port and hibernation mix when they
6960 provide a *ListenAddress directive to fix that. Bugfix on
6962 - When switching back and forth between bridge mode, do not start
6963 gathering GeoIP data until two hours have passed.
6964 - Do not complain that the user has requested an excluded node as
6965 an exit when the node is not really an exit. This could happen
6966 because the circuit was for testing, or an introduction point.
6970 Changes in version 0.2.1.15-rc - 2009-05-25
6971 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
6972 series. It fixes a major bug on fast exit relays, as well as a variety
6975 o Major bugfixes (on 0.2.0.x):
6976 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6977 that would occur on some exit nodes when DNS failures and timeouts
6978 occurred in certain patterns. Fix for bug 957.
6980 o Minor bugfixes (on 0.2.0.x):
6981 - Actually return -1 in the error case for read_bandwidth_usage().
6982 Harmless bug, since we currently don't care about the return value
6983 anywhere. Bugfix on 0.2.0.9-alpha.
6984 - Provide a more useful log message if bug 977 (related to buffer
6985 freelists) ever reappears, and do not crash right away.
6986 - Fix an assertion failure on 64-bit platforms when we allocated
6987 memory right up to the end of a memarea, then realigned the memory
6988 one step beyond the end. Fixes a possible cause of bug 930.
6989 - Protect the count of open sockets with a mutex, so we can't
6990 corrupt it when two threads are closing or opening sockets at once.
6991 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
6992 - Don't allow a bridge to publish its router descriptor to a
6993 non-bridge directory authority. Fixes part of bug 932.
6994 - When we change to or from being a bridge, reset our counts of
6995 client usage by country. Fixes bug 932.
6996 - Fix a bug that made stream bandwidth get misreported to the
6998 - Stop using malloc_usable_size() to use more area than we had
6999 actually allocated: it was safe, but made valgrind really unhappy.
7000 - Fix a memory leak when v3 directory authorities load their keys
7001 and cert from disk. Bugfix on 0.2.0.1-alpha.
7003 o Minor bugfixes (on 0.2.1.x):
7004 - Fix use of freed memory when deciding to mark a non-addable
7005 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7008 Changes in version 0.2.1.14-rc - 2009-04-12
7009 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7010 series. It begins fixing some major performance problems, and also
7011 finally addresses the bug that was causing relays on dynamic IP
7012 addresses to fall out of the directory.
7015 - Clients replace entry guards that were chosen more than a few months
7016 ago. This change should significantly improve client performance,
7017 especially once more people upgrade, since relays that have been
7018 a guard for a long time are currently overloaded.
7020 o Major bugfixes (on 0.2.0):
7021 - Finally fix the bug where dynamic-IP relays disappear when their
7022 IP address changes: directory mirrors were mistakenly telling
7023 them their old address if they asked via begin_dir, so they
7024 never got an accurate answer about their new address, so they
7025 just vanished after a day. For belt-and-suspenders, relays that
7026 don't set Address in their config now avoid using begin_dir for
7027 all direct connections. Should fix bugs 827, 883, and 900.
7028 - Relays were falling out of the networkstatus consensus for
7029 part of a day if they changed their local config but the
7030 authorities discarded their new descriptor as "not sufficiently
7031 different". Now directory authorities accept a descriptor as changed
7032 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7034 - Avoid crashing in the presence of certain malformed descriptors.
7035 Found by lark, and by automated fuzzing.
7038 - When generating circuit events with verbose nicknames for
7039 controllers, try harder to look up nicknames for routers on a
7040 circuit. (Previously, we would look in the router descriptors we had
7041 for nicknames, but not in the consensus.) Partial fix for bug 941.
7042 - If the bridge config line doesn't specify a port, assume 443.
7043 This makes bridge lines a bit smaller and easier for users to
7045 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7046 bytes (aka 20KB/s), to match our documentation. Also update
7047 directory authorities so they always assign the Fast flag to relays
7048 with 20KB/s of capacity. Now people running relays won't suddenly
7049 find themselves not seeing any use, if the network gets faster
7051 - Update to the "April 3 2009" ip-to-country file.
7054 - Avoid trying to print raw memory to the logs when we decide to
7055 give up on downloading a given relay descriptor. Bugfix on
7057 - In tor-resolve, when the Tor client to use is specified by
7058 <hostname>:<port>, actually use the specified port rather than
7059 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7060 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7061 - When starting with a cache over a few days old, do not leak
7062 memory for the obsolete router descriptors in it. Bugfix on
7064 - Avoid double-free on list of successfully uploaded hidden
7065 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7066 - Change memarea_strndup() implementation to work even when
7067 duplicating a string at the end of a page. This bug was
7068 harmless for now, but could have meant crashes later. Fix by
7069 lark. Bugfix on 0.2.1.1-alpha.
7070 - Limit uploaded directory documents to be 16M rather than 500K.
7071 The directory authorities were refusing v3 consensus votes from
7072 other authorities, since the votes are now 504K. Fixes bug 959;
7073 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7074 - Directory authorities should never send a 503 "busy" response to
7075 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7079 Changes in version 0.2.1.13-alpha - 2009-03-09
7080 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7081 cleanups. We're finally getting close to a release candidate.
7084 - Correctly update the list of which countries we exclude as
7085 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7086 lark. Bugfix on 0.2.1.6-alpha.
7088 o Minor bugfixes (on 0.2.0.x and earlier):
7089 - Automatically detect MacOSX versions earlier than 10.4.0, and
7090 disable kqueue from inside Tor when running with these versions.
7091 We previously did this from the startup script, but that was no
7092 help to people who didn't use the startup script. Resolves bug 863.
7093 - When we had picked an exit node for a connection, but marked it as
7094 "optional", and it turned out we had no onion key for the exit,
7095 stop wanting that exit and try again. This situation may not
7096 be possible now, but will probably become feasible with proposal
7097 158. Spotted by rovv. Fixes another case of bug 752.
7098 - Clients no longer cache certificates for authorities they do not
7099 recognize. Bugfix on 0.2.0.9-alpha.
7100 - When we can't transmit a DNS request due to a network error, retry
7101 it after a while, and eventually transmit a failing response to
7102 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7103 - If the controller claimed responsibility for a stream, but that
7104 stream never finished making its connection, it would live
7105 forever in circuit_wait state. Now we close it after SocksTimeout
7106 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7107 - Drop begin cells to a hidden service if they come from the middle
7108 of a circuit. Patch from lark.
7109 - When we erroneously receive two EXTEND cells for the same circuit
7110 ID on the same connection, drop the second. Patch from lark.
7111 - Fix a crash that occurs on exit nodes when a nameserver request
7112 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7113 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7115 - Do not assume that a stack-allocated character array will be
7116 64-bit aligned on platforms that demand that uint64_t access is
7117 aligned. Possible fix for bug 604.
7118 - Parse dates and IPv4 addresses in a locale- and libc-independent
7119 manner, to avoid platform-dependent behavior on malformed input.
7120 - Build correctly when configured to build outside the main source
7121 path. Patch from Michael Gold.
7122 - We were already rejecting relay begin cells with destination port
7123 of 0. Now also reject extend cells with destination port or address
7124 of 0. Suggested by lark.
7126 o Minor bugfixes (on 0.2.1.x):
7127 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7128 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7129 - If we're an exit node, scrub the IP address to which we are exiting
7130 in the logs. Bugfix on 0.2.1.8-alpha.
7133 - On Linux, use the prctl call to re-enable core dumps when the user
7135 - New controller event NEWCONSENSUS that lists the networkstatus
7136 lines for every recommended relay. Now controllers like Torflow
7137 can keep up-to-date on which relays they should be using.
7138 - Update to the "February 26 2009" ip-to-country file.
7141 Changes in version 0.2.0.34 - 2009-02-08
7142 Tor 0.2.0.34 features several more security-related fixes. You should
7143 upgrade, especially if you run an exit relay (remote crash) or a
7144 directory authority (remote infinite loop), or you're on an older
7145 (pre-XP) or not-recently-patched Windows (remote exploit).
7147 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7148 have many known flaws, and nobody should be using them. You should
7149 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7150 stop using those packages and upgrade anyway.
7153 - Fix an infinite-loop bug on handling corrupt votes under certain
7154 circumstances. Bugfix on 0.2.0.8-alpha.
7155 - Fix a temporary DoS vulnerability that could be performed by
7156 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7157 - Avoid a potential crash on exit nodes when processing malformed
7158 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7159 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7160 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7163 - Fix compilation on systems where time_t is a 64-bit integer.
7164 Patch from Matthias Drochner.
7165 - Don't consider expiring already-closed client connections. Fixes
7166 bug 893. Bugfix on 0.0.2pre20.
7169 Changes in version 0.2.1.12-alpha - 2009-02-08
7170 Tor 0.2.1.12-alpha features several more security-related fixes. You
7171 should upgrade, especially if you run an exit relay (remote crash) or
7172 a directory authority (remote infinite loop), or you're on an older
7173 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7174 includes a big pile of minor bugfixes and cleanups.
7177 - Fix an infinite-loop bug on handling corrupt votes under certain
7178 circumstances. Bugfix on 0.2.0.8-alpha.
7179 - Fix a temporary DoS vulnerability that could be performed by
7180 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7181 - Avoid a potential crash on exit nodes when processing malformed
7182 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7185 - Let controllers actually ask for the "clients_seen" event for
7186 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7187 reported by Matt Edman.
7188 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7190 - Fix a bug in address parsing that was preventing bridges or hidden
7191 service targets from being at IPv6 addresses.
7192 - Solve a bug that kept hardware crypto acceleration from getting
7193 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7195 - Remove a bash-ism from configure.in to build properly on non-Linux
7196 platforms. Bugfix on 0.2.1.1-alpha.
7197 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7198 headers. Bugfix on 0.2.0.10-alpha.
7199 - Don't consider expiring already-closed client connections. Fixes
7200 bug 893. Bugfix on 0.0.2pre20.
7201 - Fix another interesting corner-case of bug 891 spotted by rovv:
7202 Previously, if two hosts had different amounts of clock drift, and
7203 one of them created a new connection with just the wrong timing,
7204 the other might decide to deprecate the new connection erroneously.
7205 Bugfix on 0.1.1.13-alpha.
7206 - Resolve a very rare crash bug that could occur when the user forced
7207 a nameserver reconfiguration during the middle of a nameserver
7208 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7209 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7210 Bugfix on 0.2.1.7-alpha.
7211 - If we're using bridges and our network goes away, be more willing
7212 to forgive our bridges and try again when we get an application
7213 request. Bugfix on 0.2.0.x.
7216 - Support platforms where time_t is 64 bits long. (Congratulations,
7217 NetBSD!) Patch from Matthias Drochner.
7218 - Add a 'getinfo status/clients-seen' controller command, in case
7219 controllers want to hear clients_seen events but connect late.
7222 - Disable GCC's strict alias optimization by default, to avoid the
7223 likelihood of its introducing subtle bugs whenever our code violates
7224 the letter of C99's alias rules.
7227 Changes in version 0.2.0.33 - 2009-01-21
7228 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7229 useful to users. It also finally fixes a bug where a relay or client
7230 that's been off for many days would take a long time to bootstrap.
7232 This update also fixes an important security-related bug reported by
7233 Ilja van Sprundel. You should upgrade. (We'll send out more details
7234 about the bug once people have had some time to upgrade.)
7237 - Fix a heap-corruption bug that may be remotely triggerable on
7238 some platforms. Reported by Ilja van Sprundel.
7241 - When a stream at an exit relay is in state "resolving" or
7242 "connecting" and it receives an "end" relay cell, the exit relay
7243 would silently ignore the end cell and not close the stream. If
7244 the client never closes the circuit, then the exit relay never
7245 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7247 - When sending CREATED cells back for a given circuit, use a 64-bit
7248 connection ID to find the right connection, rather than an addr:port
7249 combination. Now that we can have multiple OR connections between
7250 the same ORs, it is no longer possible to use addr:port to uniquely
7251 identify a connection.
7252 - Bridge relays that had DirPort set to 0 would stop fetching
7253 descriptors shortly after startup, and then briefly resume
7254 after a new bandwidth test and/or after publishing a new bridge
7255 descriptor. Bridge users that try to bootstrap from them would
7256 get a recent networkstatus but would get descriptors from up to
7257 18 hours earlier, meaning most of the descriptors were obsolete
7258 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7259 - Prevent bridge relays from serving their 'extrainfo' document
7260 to anybody who asks, now that extrainfo docs include potentially
7261 sensitive aggregated client geoip summaries. Bugfix on
7263 - If the cached networkstatus consensus is more than five days old,
7264 discard it rather than trying to use it. In theory it could be
7265 useful because it lists alternate directory mirrors, but in practice
7266 it just means we spend many minutes trying directory mirrors that
7267 are long gone from the network. Also discard router descriptors as
7268 we load them if they are more than five days old, since the onion
7269 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7272 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7273 could make gcc generate non-functional binary search code. Bugfix
7275 - Build correctly on platforms without socklen_t.
7276 - Compile without warnings on solaris.
7277 - Avoid potential crash on internal error during signature collection.
7278 Fixes bug 864. Patch from rovv.
7279 - Correct handling of possible malformed authority signing key
7280 certificates with internal signature types. Fixes bug 880.
7281 Bugfix on 0.2.0.3-alpha.
7282 - Fix a hard-to-trigger resource leak when logging credential status.
7284 - When we can't initialize DNS because the network is down, do not
7285 automatically stop Tor from starting. Instead, we retry failed
7286 dns_init() every 10 minutes, and change the exit policy to reject
7287 *:* until one succeeds. Fixes bug 691.
7288 - Use 64 bits instead of 32 bits for connection identifiers used with
7289 the controller protocol, to greatly reduce risk of identifier reuse.
7290 - When we're choosing an exit node for a circuit, and we have
7291 no pending streams, choose a good general exit rather than one that
7292 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7293 - Fix another case of assuming, when a specific exit is requested,
7294 that we know more than the user about what hosts it allows.
7295 Fixes one case of bug 752. Patch from rovv.
7296 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7297 seconds. Warn the user if lower values are given in the
7298 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7299 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7300 user if lower values are given in the configuration. Bugfix on
7301 0.1.1.17-rc. Patch by Sebastian.
7302 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7303 the cache because we already had a v0 descriptor with the same ID.
7304 Bugfix on 0.2.0.18-alpha.
7305 - Fix a race condition when freeing keys shared between main thread
7306 and CPU workers that could result in a memory leak. Bugfix on
7307 0.1.0.1-rc. Fixes bug 889.
7308 - Send a valid END cell back when a client tries to connect to a
7309 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7310 840. Patch from rovv.
7311 - Check which hops rendezvous stream cells are associated with to
7312 prevent possible guess-the-streamid injection attacks from
7313 intermediate hops. Fixes another case of bug 446. Based on patch
7315 - If a broken client asks a non-exit router to connect somewhere,
7316 do not even do the DNS lookup before rejecting the connection.
7317 Fixes another case of bug 619. Patch from rovv.
7318 - When a relay gets a create cell it can't decrypt (e.g. because it's
7319 using the wrong onion key), we were dropping it and letting the
7320 client time out. Now actually answer with a destroy cell. Fixes
7321 bug 904. Bugfix on 0.0.2pre8.
7323 o Minor bugfixes (hidden services):
7324 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7325 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7328 - Report the case where all signatures in a detached set are rejected
7329 differently than the case where there is an error handling the
7331 - When we realize that another process has modified our cached
7332 descriptors, print out a more useful error message rather than
7333 triggering an assertion. Fixes bug 885. Patch from Karsten.
7334 - Implement the 0x20 hack to better resist DNS poisoning: set the
7335 case on outgoing DNS requests randomly, and reject responses that do
7336 not match the case correctly. This logic can be disabled with the
7337 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7338 of servers that do not reliably preserve case in replies. See
7339 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7341 - Check DNS replies for more matching fields to better resist DNS
7343 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7344 compress cells, which are basically all encrypted, compressed, or
7348 Changes in version 0.2.1.11-alpha - 2009-01-20
7349 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7350 week it will take a long time to bootstrap again" bug. It also fixes
7351 an important security-related bug reported by Ilja van Sprundel. You
7352 should upgrade. (We'll send out more details about the bug once people
7353 have had some time to upgrade.)
7356 - Fix a heap-corruption bug that may be remotely triggerable on
7357 some platforms. Reported by Ilja van Sprundel.
7360 - Discard router descriptors as we load them if they are more than
7361 five days old. Otherwise if Tor is off for a long time and then
7362 starts with cached descriptors, it will try to use the onion
7363 keys in those obsolete descriptors when building circuits. Bugfix
7364 on 0.2.0.x. Fixes bug 887.
7367 - Try to make sure that the version of Libevent we're running with
7368 is binary-compatible with the one we built with. May address bug
7370 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7371 for bug 905. Bugfix on 0.2.1.7-alpha.
7372 - Add a new --enable-local-appdata configuration switch to change
7373 the default location of the datadir on win32 from APPDATA to
7374 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7375 entirely. Patch from coderman.
7378 - Make outbound DNS packets respect the OutboundBindAddress setting.
7379 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7380 - When our circuit fails at the first hop (e.g. we get a destroy
7381 cell back), avoid using that OR connection anymore, and also
7382 tell all the one-hop directory requests waiting for it that they
7383 should fail. Bugfix on 0.2.1.3-alpha.
7384 - In the torify(1) manpage, mention that tsocks will leak your
7388 Changes in version 0.2.1.10-alpha - 2009-01-06
7389 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7390 would make the bridge relay not so useful if it had DirPort set to 0,
7391 and one that could let an attacker learn a little bit of information
7392 about the bridge's users), and a bug that would cause your Tor relay
7393 to ignore a circuit create request it can't decrypt (rather than reply
7394 with an error). It also fixes a wide variety of other bugs.
7397 - If the cached networkstatus consensus is more than five days old,
7398 discard it rather than trying to use it. In theory it could
7399 be useful because it lists alternate directory mirrors, but in
7400 practice it just means we spend many minutes trying directory
7401 mirrors that are long gone from the network. Helps bug 887 a bit;
7403 - Bridge relays that had DirPort set to 0 would stop fetching
7404 descriptors shortly after startup, and then briefly resume
7405 after a new bandwidth test and/or after publishing a new bridge
7406 descriptor. Bridge users that try to bootstrap from them would
7407 get a recent networkstatus but would get descriptors from up to
7408 18 hours earlier, meaning most of the descriptors were obsolete
7409 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7410 - Prevent bridge relays from serving their 'extrainfo' document
7411 to anybody who asks, now that extrainfo docs include potentially
7412 sensitive aggregated client geoip summaries. Bugfix on
7416 - New controller event "clients_seen" to report a geoip-based summary
7417 of which countries we've seen clients from recently. Now controllers
7418 like Vidalia can show bridge operators that they're actually making
7420 - Build correctly against versions of OpenSSL 0.9.8 or later built
7421 without support for deprecated functions.
7422 - Update to the "December 19 2008" ip-to-country file.
7424 o Minor bugfixes (on 0.2.0.x):
7425 - Authorities now vote for the Stable flag for any router whose
7426 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7427 - Do not remove routers as too old if we do not have any consensus
7428 document. Bugfix on 0.2.0.7-alpha.
7429 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7430 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7431 - When an exit relay resolves a stream address to a local IP address,
7432 do not just keep retrying that same exit relay over and
7433 over. Instead, just close the stream. Addresses bug 872. Bugfix
7434 on 0.2.0.32. Patch from rovv.
7435 - If a hidden service sends us an END cell, do not consider
7436 retrying the connection; just close it. Patch from rovv.
7437 - When we made bridge authorities stop serving bridge descriptors over
7438 unencrypted links, we also broke DirPort reachability testing for
7439 bridges. So bridges with a non-zero DirPort were printing spurious
7440 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7441 - When a relay gets a create cell it can't decrypt (e.g. because it's
7442 using the wrong onion key), we were dropping it and letting the
7443 client time out. Now actually answer with a destroy cell. Fixes
7444 bug 904. Bugfix on 0.0.2pre8.
7445 - Squeeze 2-5% out of client performance (according to oprofile) by
7446 improving the implementation of some policy-manipulation functions.
7448 o Minor bugfixes (on 0.2.1.x):
7449 - Make get_interface_address() function work properly again; stop
7450 guessing the wrong parts of our address as our address.
7451 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7452 send on that circuit. Otherwise we might violate the proposal-110
7453 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7455 - When we're sending non-EXTEND cells to the first hop in a circuit,
7456 for example to use an encrypted directory connection, we don't need
7457 to use RELAY_EARLY cells: the first hop knows what kind of cell
7458 it is, and nobody else can even see the cell type. Conserving
7459 RELAY_EARLY cells makes it easier to cannibalize circuits like
7461 - Stop logging nameserver addresses in reverse order.
7462 - If we are retrying a directory download slowly over and over, do
7463 not automatically give up after the 254th failure. Bugfix on
7465 - Resume reporting accurate "stream end" reasons to the local control
7466 port. They were lost in the changes for Proposal 148. Bugfix on
7469 o Deprecated and removed features:
7470 - The old "tor --version --version" command, which would print out
7471 the subversion "Id" of most of the source files, is now removed. It
7472 turned out to be less useful than we'd expected, and harder to
7475 o Code simplifications and refactoring:
7476 - Change our header file guard macros to be less likely to conflict
7477 with system headers. Adam Langley noticed that we were conflicting
7478 with log.h on Android.
7479 - Tool-assisted documentation cleanup. Nearly every function or
7480 static variable in Tor should have its own documentation now.
7483 Changes in version 0.2.1.9-alpha - 2008-12-25
7484 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7486 o New directory authorities:
7487 - gabelmoo (the authority run by Karsten Loesing) now has a new
7491 - Never use a connection with a mismatched address to extend a
7492 circuit, unless that connection is canonical. A canonical
7493 connection is one whose address is authenticated by the router's
7494 identity key, either in a NETINFO cell or in a router descriptor.
7495 - Avoid a possible memory corruption bug when receiving hidden service
7496 descriptors. Bugfix on 0.2.1.6-alpha.
7499 - Fix a logic error that would automatically reject all but the first
7500 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7501 part of bug 813/868. Bug spotted by coderman.
7502 - When a stream at an exit relay is in state "resolving" or
7503 "connecting" and it receives an "end" relay cell, the exit relay
7504 would silently ignore the end cell and not close the stream. If
7505 the client never closes the circuit, then the exit relay never
7506 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7508 - When we can't initialize DNS because the network is down, do not
7509 automatically stop Tor from starting. Instead, retry failed
7510 dns_init() every 10 minutes, and change the exit policy to reject
7511 *:* until one succeeds. Fixes bug 691.
7514 - Give a better error message when an overzealous init script says
7515 "sudo -u username tor --user username". Makes Bug 882 easier for
7517 - When a directory authority gives us a new guess for our IP address,
7518 log which authority we used. Hopefully this will help us debug
7519 the recent complaints about bad IP address guesses.
7520 - Detect svn revision properly when we're using git-svn.
7521 - Try not to open more than one descriptor-downloading connection
7522 to an authority at once. This should reduce load on directory
7523 authorities. Fixes bug 366.
7524 - Add cross-certification to newly generated certificates, so that
7525 a signing key is enough information to look up a certificate.
7526 Partial implementation of proposal 157.
7527 - Start serving certificates by <identity digest, signing key digest>
7528 pairs. Partial implementation of proposal 157.
7529 - Clients now never report any stream end reason except 'MISC'.
7530 Implements proposal 148.
7531 - On platforms with a maximum syslog string length, truncate syslog
7532 messages to that length ourselves, rather than relying on the
7533 system to do it for us.
7534 - Optimize out calls to time(NULL) that occur for every IO operation,
7535 or for every cell. On systems where time() is a slow syscall,
7536 this fix will be slightly helpful.
7537 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7538 - When we download a descriptor that we then immediately (as
7539 a directory authority) reject, do not retry downloading it right
7540 away. Should save some bandwidth on authorities. Fix for bug
7541 888. Patch by Sebastian Hahn.
7542 - When a download gets us zero good descriptors, do not notify
7543 Tor that new directory information has arrived.
7544 - Avoid some nasty corner cases in the logic for marking connections
7545 as too old or obsolete or noncanonical for circuits. Partial
7548 o Minor features (controller):
7549 - New CONSENSUS_ARRIVED event to note when a new consensus has
7550 been fetched and validated.
7551 - When we realize that another process has modified our cached
7552 descriptors file, print out a more useful error message rather
7553 than triggering an assertion. Fixes bug 885. Patch from Karsten.
7554 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
7555 controllers to prevent SIGHUP from reloading the
7556 configuration. Fixes bug 856.
7559 - Resume using the correct "REASON=" stream when telling the
7560 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
7561 - When a canonical connection appears later in our internal list
7562 than a noncanonical one for a given OR ID, always use the
7563 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
7565 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7566 seconds. Warn the user if lower values are given in the
7567 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7568 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7569 user if lower values are given in the configuration. Bugfix on
7570 0.1.1.17-rc. Patch by Sebastian.
7571 - Fix a race condition when freeing keys shared between main thread
7572 and CPU workers that could result in a memory leak. Bugfix on
7573 0.1.0.1-rc. Fixes bug 889.
7575 o Minor bugfixes (hidden services):
7576 - Do not throw away existing introduction points on SIGHUP (bugfix on
7577 0.0.6pre1); also, do not stall hidden services because we're
7578 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
7579 by John Brooks. Patch by Karsten. Fixes bug 874.
7580 - Fix a memory leak when we decline to add a v2 rendezvous
7581 descriptor to the cache because we already had a v0 descriptor
7582 with the same ID. Bugfix on 0.2.0.18-alpha.
7584 o Deprecated and removed features:
7585 - RedirectExits has been removed. It was deprecated since
7587 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
7588 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
7589 - Cell pools are now always enabled; --disable-cell-pools is ignored.
7591 o Code simplifications and refactoring:
7592 - Rename the confusing or_is_obsolete field to the more appropriate
7593 is_bad_for_new_circs, and move it to or_connection_t where it
7595 - Move edge-only flags from connection_t to edge_connection_t: not
7596 only is this better coding, but on machines of plausible alignment,
7597 it should save 4-8 bytes per connection_t. "Every little bit helps."
7598 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
7599 for consistency; keep old option working for backward compatibility.
7600 - Simplify the code for finding connections to use for a circuit.
7603 Changes in version 0.2.1.8-alpha - 2008-12-08
7604 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
7605 builds better on unusual platforms like Solaris and old OS X, and
7606 fixes a variety of other issues.
7609 - New DirPortFrontPage option that takes an html file and publishes
7610 it as "/" on the DirPort. Now relay operators can provide a
7611 disclaimer without needing to set up a separate webserver. There's
7612 a sample disclaimer in contrib/tor-exit-notice.html.
7615 - When the client is choosing entry guards, now it selects at most
7616 one guard from a given relay family. Otherwise we could end up with
7617 all of our entry points into the network run by the same operator.
7618 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
7621 - Fix a DOS opportunity during the voting signature collection process
7622 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7623 - Fix a possible segfault when establishing an exit connection. Bugfix
7627 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
7629 - Made Tor a little less aggressive about deleting expired
7630 certificates. Partial fix for bug 854.
7631 - Stop doing unaligned memory access that generated bus errors on
7632 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
7633 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
7634 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
7635 - Make USR2 log-level switch take effect immediately. Bugfix on
7637 - If one win32 nameserver fails to get added, continue adding the
7638 rest, and don't automatically fail.
7639 - Use fcntl() for locking when flock() is not available. Should fix
7640 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
7641 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7642 could make gcc generate non-functional binary search code. Bugfix
7644 - Build correctly on platforms without socklen_t.
7645 - Avoid potential crash on internal error during signature collection.
7646 Fixes bug 864. Patch from rovv.
7647 - Do not use C's stdio library for writing to log files. This will
7648 improve logging performance by a minute amount, and will stop
7649 leaking fds when our disk is full. Fixes bug 861.
7650 - Stop erroneous use of O_APPEND in cases where we did not in fact
7651 want to re-seek to the end of a file before every last write().
7652 - Correct handling of possible malformed authority signing key
7653 certificates with internal signature types. Fixes bug 880. Bugfix
7655 - Fix a hard-to-trigger resource leak when logging credential status.
7659 - Directory mirrors no longer fetch the v1 directory or
7660 running-routers files. They are obsolete, and nobody asks for them
7661 anymore. This is the first step to making v1 authorities obsolete.
7663 o Minor features (controller):
7664 - Return circuit purposes in response to GETINFO circuit-status. Fixes
7668 Changes in version 0.2.0.32 - 2008-11-20
7669 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
7670 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7671 a smaller security flaw that might allow an attacker to access local
7672 services, further improves hidden service performance, and fixes a
7673 variety of other issues.
7676 - The "User" and "Group" config options did not clear the
7677 supplementary group entries for the Tor process. The "User" option
7678 is now more robust, and we now set the groups to the specified
7679 user's primary group. The "Group" option is now ignored. For more
7680 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7681 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7682 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
7683 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7684 consistently obeyed: if an exit relay refuses a stream because its
7685 exit policy doesn't allow it, we would remember what IP address
7686 the relay said the destination address resolves to, even if it's
7687 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7690 - Fix a DOS opportunity during the voting signature collection process
7691 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7693 o Major bugfixes (hidden services):
7694 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7695 we were failing the whole hidden service request when the v0
7696 descriptor fetch fails, even if the v2 fetch is still pending and
7697 might succeed. Similarly, if the last v2 fetch fails, we were
7698 failing the whole hidden service request even if a v0 fetch is
7699 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7700 - When extending a circuit to a hidden service directory to upload a
7701 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7702 requests failed, because the router descriptor has not been
7703 downloaded yet. In these cases, do not attempt to upload the
7704 rendezvous descriptor, but wait until the router descriptor is
7705 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
7706 descriptor from a hidden service directory for which the router
7707 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
7711 - Fix several infrequent memory leaks spotted by Coverity.
7712 - When testing for libevent functions, set the LDFLAGS variable
7713 correctly. Found by Riastradh.
7714 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7715 bootstrapping with tunneled directory connections. Bugfix on
7716 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7717 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7718 and we know that server B rejects most-but-not all connections to
7719 port 80, we would previously reject the connection. Now, we assume
7720 the user knows what they were asking for. Fixes bug 752. Bugfix
7721 on 0.0.9rc5. Diagnosed by BarkerJr.
7722 - If we overrun our per-second write limits a little, count this as
7723 having used up our write allocation for the second, and choke
7724 outgoing directory writes. Previously, we had only counted this when
7725 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
7726 Bugfix on 0.2.0.x (??).
7727 - Remove the old v2 directory authority 'lefkada' from the default
7728 list. It has been gone for many months.
7729 - Stop doing unaligned memory access that generated bus errors on
7730 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
7731 - Make USR2 log-level switch take effect immediately. Bugfix on
7734 o Minor bugfixes (controller):
7735 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
7736 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
7739 Changes in version 0.2.1.7-alpha - 2008-11-08
7740 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
7741 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7742 a smaller security flaw that might allow an attacker to access local
7743 services, adds better defense against DNS poisoning attacks on exit
7744 relays, further improves hidden service performance, and fixes a
7745 variety of other issues.
7748 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7749 consistently obeyed: if an exit relay refuses a stream because its
7750 exit policy doesn't allow it, we would remember what IP address
7751 the relay said the destination address resolves to, even if it's
7752 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7753 - The "User" and "Group" config options did not clear the
7754 supplementary group entries for the Tor process. The "User" option
7755 is now more robust, and we now set the groups to the specified
7756 user's primary group. The "Group" option is now ignored. For more
7757 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7758 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7759 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
7760 - Do not use or believe expired v3 authority certificates. Patch
7761 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
7764 - Now NodeFamily and MyFamily config options allow spaces in
7765 identity fingerprints, so it's easier to paste them in.
7766 Suggested by Lucky Green.
7767 - Implement the 0x20 hack to better resist DNS poisoning: set the
7768 case on outgoing DNS requests randomly, and reject responses that do
7769 not match the case correctly. This logic can be disabled with the
7770 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
7771 of servers that do not reliably preserve case in replies. See
7772 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7774 - Preserve case in replies to DNSPort requests in order to support
7775 the 0x20 hack for resisting DNS poisoning attacks.
7777 o Hidden service performance improvements:
7778 - When the client launches an introduction circuit, retry with a
7779 new circuit after 30 seconds rather than 60 seconds.
7780 - Launch a second client-side introduction circuit in parallel
7781 after a delay of 15 seconds (based on work by Christian Wilms).
7782 - Hidden services start out building five intro circuits rather
7783 than three, and when the first three finish they publish a service
7784 descriptor using those. Now we publish our service descriptor much
7785 faster after restart.
7788 - Minor fix in the warning messages when you're having problems
7789 bootstrapping; also, be more forgiving of bootstrap problems when
7790 we're still making incremental progress on a given bootstrap phase.
7791 - When we're choosing an exit node for a circuit, and we have
7792 no pending streams, choose a good general exit rather than one that
7793 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7794 - Send a valid END cell back when a client tries to connect to a
7795 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7796 840. Patch from rovv.
7797 - If a broken client asks a non-exit router to connect somewhere,
7798 do not even do the DNS lookup before rejecting the connection.
7799 Fixes another case of bug 619. Patch from rovv.
7800 - Fix another case of assuming, when a specific exit is requested,
7801 that we know more than the user about what hosts it allows.
7802 Fixes another case of bug 752. Patch from rovv.
7803 - Check which hops rendezvous stream cells are associated with to
7804 prevent possible guess-the-streamid injection attacks from
7805 intermediate hops. Fixes another case of bug 446. Based on patch
7807 - Avoid using a negative right-shift when comparing 32-bit
7808 addresses. Possible fix for bug 845 and bug 811.
7809 - Make the assert_circuit_ok() function work correctly on circuits that
7810 have already been marked for close.
7811 - Fix read-off-the-end-of-string error in unit tests when decoding
7812 introduction points.
7813 - Fix uninitialized size field for memory area allocation: may improve
7814 memory performance during directory parsing.
7815 - Treat duplicate certificate fetches as failures, so that we do
7816 not try to re-fetch an expired certificate over and over and over.
7817 - Do not say we're fetching a certificate when we'll in fact skip it
7818 because of a pending download.
7821 Changes in version 0.2.1.6-alpha - 2008-09-30
7822 Tor 0.2.1.6-alpha further improves performance and robustness of
7823 hidden services, starts work on supporting per-country relay selection,
7824 and fixes a variety of smaller issues.
7827 - Implement proposal 121: make it possible to build hidden services
7828 that only certain clients are allowed to connect to. This is
7829 enforced at several points, so that unauthorized clients are unable
7830 to send INTRODUCE cells to the service, or even (depending on the
7831 type of authentication) to learn introduction points. This feature
7832 raises the bar for certain kinds of active attacks against hidden
7833 services. Code by Karsten Loesing.
7834 - Relays now store and serve v2 hidden service descriptors by default,
7835 i.e., the new default value for HidServDirectoryV2 is 1. This is
7836 the last step in proposal 114, which aims to make hidden service
7837 lookups more reliable.
7838 - Start work to allow node restrictions to include country codes. The
7839 syntax to exclude nodes in a country with country code XX is
7840 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
7841 refinement to decide what config options should take priority if
7842 you ask to both use a particular node and exclude it.
7843 - Allow ExitNodes list to include IP ranges and country codes, just
7844 like the Exclude*Nodes lists. Patch from Robert Hogan.
7847 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
7848 Tor to fail to start if you had it configured to use a bridge
7849 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
7850 - When extending a circuit to a hidden service directory to upload a
7851 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7852 requests failed, because the router descriptor had not been
7853 downloaded yet. In these cases, we now wait until the router
7854 descriptor is downloaded, and then retry. Likewise, clients
7855 now skip over a hidden service directory if they don't yet have
7856 its router descriptor, rather than futilely requesting it and
7857 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
7859 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7860 we were failing the whole hidden service request when the v0
7861 descriptor fetch fails, even if the v2 fetch is still pending and
7862 might succeed. Similarly, if the last v2 fetch fails, we were
7863 failing the whole hidden service request even if a v0 fetch is
7864 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7865 - DNS replies need to have names matching their requests, but
7866 these names should be in the questions section, not necessarily
7867 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
7870 - Update to the "September 1 2008" ip-to-country file.
7871 - Allow ports 465 and 587 in the default exit policy again. We had
7872 rejected them in 0.1.0.15, because back in 2005 they were commonly
7873 misconfigured and ended up as spam targets. We hear they are better
7874 locked down these days.
7875 - Use a lockfile to make sure that two Tor processes are not
7876 simultaneously running with the same datadir.
7877 - Serve the latest v3 networkstatus consensus via the control
7878 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
7879 - Better logging about stability/reliability calculations on directory
7881 - Drop the requirement to have an open dir port for storing and
7882 serving v2 hidden service descriptors.
7883 - Directory authorities now serve a /tor/dbg-stability.txt URL to
7884 help debug WFU and MTBF calculations.
7885 - Implement most of Proposal 152: allow specialized servers to permit
7886 single-hop circuits, and clients to use those servers to build
7887 single-hop circuits when using a specialized controller. Patch
7888 from Josh Albrecht. Resolves feature request 768.
7889 - Add a -p option to tor-resolve for specifying the SOCKS port: some
7890 people find host:port too confusing.
7891 - Make TrackHostExit mappings expire a while after their last use, not
7892 after their creation. Patch from Robert Hogan.
7893 - Provide circuit purposes along with circuit events to the controller.
7896 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
7898 - Fixed some memory leaks -- some quite frequent, some almost
7899 impossible to trigger -- based on results from Coverity.
7900 - When testing for libevent functions, set the LDFLAGS variable
7901 correctly. Found by Riastradh.
7902 - Fix an assertion bug in parsing policy-related options; possible fix
7904 - Catch and report a few more bootstrapping failure cases when Tor
7905 fails to establish a TCP connection. Cleanup on 0.2.1.x.
7906 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7907 bootstrapping with tunneled directory connections. Bugfix on
7908 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7909 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7910 and we know that server B rejects most-but-not all connections to
7911 port 80, we would previously reject the connection. Now, we assume
7912 the user knows what they were asking for. Fixes bug 752. Bugfix
7913 on 0.0.9rc5. Diagnosed by BarkerJr.
7914 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
7915 service directories if they have no advertised dir port. Bugfix
7917 - If we overrun our per-second write limits a little, count this as
7918 having used up our write allocation for the second, and choke
7919 outgoing directory writes. Previously, we had only counted this when
7920 we had met our limits precisely. Fixes bug 824. Patch by rovv.
7921 Bugfix on 0.2.0.x (??).
7922 - Avoid a "0 divided by 0" calculation when calculating router uptime
7923 at directory authorities. Bugfix on 0.2.0.8-alpha.
7924 - Make DNS resolved controller events into "CLOSED", not
7925 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
7927 - Fix a bug where an unreachable relay would establish enough
7928 reachability testing circuits to do a bandwidth test -- if
7929 we already have a connection to the middle hop of the testing
7930 circuit, then it could establish the last hop by using the existing
7931 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
7932 circuits no longer use entry guards in 0.2.1.3-alpha.
7933 - If we have correct permissions on $datadir, we complain to stdout
7934 and fail to start. But dangerous permissions on
7935 $datadir/cached-status/ would cause us to open a log and complain
7936 there. Now complain to stdout and fail to start in both cases. Fixes
7937 bug 820, reported by seeess.
7938 - Remove the old v2 directory authority 'lefkada' from the default
7939 list. It has been gone for many months.
7941 o Code simplifications and refactoring:
7942 - Revise the connection_new functions so that a more typesafe variant
7943 exists. This will work better with Coverity, and let us find any
7944 actual mistakes we're making here.
7945 - Refactor unit testing logic so that dmalloc can be used sensibly
7946 with unit tests to check for memory leaks.
7947 - Move all hidden-service related fields from connection and circuit
7948 structure to substructures: this way they won't eat so much memory.
7951 Changes in version 0.2.0.31 - 2008-09-03
7952 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
7953 a big bug we're seeing where in rare cases traffic from one Tor stream
7954 gets mixed into another stream, and fixes a variety of smaller issues.
7957 - Make sure that two circuits can never exist on the same connection
7958 with the same circuit ID, even if one is marked for close. This
7959 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
7960 - Relays now reject risky extend cells: if the extend cell includes
7961 a digest of all zeroes, or asks to extend back to the relay that
7962 sent the extend cell, tear down the circuit. Ideas suggested
7964 - If not enough of our entry guards are available so we add a new
7965 one, we might use the new one even if it overlapped with the
7966 current circuit's exit relay (or its family). Anonymity bugfix
7967 pointed out by rovv.
7970 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7971 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7972 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7973 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7974 - Pick size of default geoip filename string correctly on windows.
7975 Fixes bug 806. Bugfix on 0.2.0.30.
7976 - Make the autoconf script accept the obsolete --with-ssl-dir
7977 option as an alias for the actually-working --with-openssl-dir
7978 option. Fix the help documentation to recommend --with-openssl-dir.
7979 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7980 - When using the TransPort option on OpenBSD, and using the User
7981 option to change UID and drop privileges, make sure to open
7982 /dev/pf before dropping privileges. Fixes bug 782. Patch from
7983 Christopher Davis. Bugfix on 0.1.2.1-alpha.
7984 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7985 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7986 on the client side when connecting to a hidden service. Bugfix
7987 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7988 - When closing an application-side connection because its circuit is
7989 getting torn down, generate the stream event correctly. Bugfix on
7990 0.1.2.x. Anonymous patch.
7993 Changes in version 0.2.1.5-alpha - 2008-08-31
7994 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
7995 in a lot of the infrastructure for adding authorization to hidden
7996 services, lays the groundwork for having clients read their load
7997 balancing information out of the networkstatus consensus rather than
7998 the individual router descriptors, addresses two potential anonymity
7999 issues, and fixes a variety of smaller issues.
8002 - Convert many internal address representations to optionally hold
8004 - Generate and accept IPv6 addresses in many protocol elements.
8005 - Make resolver code handle nameservers located at ipv6 addresses.
8006 - Begin implementation of proposal 121 ("Client authorization for
8007 hidden services"): configure hidden services with client
8008 authorization, publish descriptors for them, and configure
8009 authorization data for hidden services at clients. The next
8010 step is to actually access hidden services that perform client
8012 - More progress toward proposal 141: Network status consensus
8013 documents and votes now contain bandwidth information for each
8014 router and a summary of that router's exit policy. Eventually this
8015 will be used by clients so that they do not have to download every
8016 known descriptor before building circuits.
8018 o Major bugfixes (on 0.2.0.x and before):
8019 - When sending CREATED cells back for a given circuit, use a 64-bit
8020 connection ID to find the right connection, rather than an addr:port
8021 combination. Now that we can have multiple OR connections between
8022 the same ORs, it is no longer possible to use addr:port to uniquely
8023 identify a connection.
8024 - Relays now reject risky extend cells: if the extend cell includes
8025 a digest of all zeroes, or asks to extend back to the relay that
8026 sent the extend cell, tear down the circuit. Ideas suggested
8028 - If not enough of our entry guards are available so we add a new
8029 one, we might use the new one even if it overlapped with the
8030 current circuit's exit relay (or its family). Anonymity bugfix
8031 pointed out by rovv.
8034 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8035 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8036 - When using the TransPort option on OpenBSD, and using the User
8037 option to change UID and drop privileges, make sure to open /dev/pf
8038 before dropping privileges. Fixes bug 782. Patch from Christopher
8039 Davis. Bugfix on 0.1.2.1-alpha.
8040 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8041 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8042 - Add a missing safe_str() call for a debug log message.
8043 - Use 64 bits instead of 32 bits for connection identifiers used with
8044 the controller protocol, to greatly reduce risk of identifier reuse.
8045 - Make the autoconf script accept the obsolete --with-ssl-dir
8046 option as an alias for the actually-working --with-openssl-dir
8047 option. Fix the help documentation to recommend --with-openssl-dir.
8048 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8051 - Rate-limit too-many-sockets messages: when they happen, they happen
8052 a lot. Resolves bug 748.
8053 - Resist DNS poisoning a little better by making sure that names in
8054 answer sections match.
8055 - Print the SOCKS5 error message string as well as the error code
8056 when a tor-resolve request fails. Patch from Jacob.
8059 Changes in version 0.2.1.4-alpha - 2008-08-04
8060 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8063 - The address part of exit policies was not correctly written
8064 to router descriptors. This generated router descriptors that failed
8065 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8067 - Tor triggered a false assert when extending a circuit to a relay
8068 but we already have a connection open to that relay. Noticed by
8069 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8072 - Fix a hidden service logging bug: in some edge cases, the router
8073 descriptor of a previously picked introduction point becomes
8074 obsolete and we need to give up on it rather than continually
8075 complaining that it has become obsolete. Observed by xiando. Bugfix
8079 - Take out the TestVia config option, since it was a workaround for
8080 a bug that was fixed in Tor 0.1.1.21.
8083 Changes in version 0.2.1.3-alpha - 2008-08-03
8084 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8085 infinite-length circuit attacks (see proposal 110); fixes a bug that
8086 might cause exit relays to corrupt streams they send back; allows
8087 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8088 ExcludeExitNodes config options; and fixes a big pile of bugs.
8090 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8091 - Send a bootstrap problem "warn" event on the first problem if the
8092 reason is NO_ROUTE (that is, our network is down).
8095 - Implement most of proposal 110: The first K cells to be sent
8096 along a circuit are marked as special "early" cells; only K "early"
8097 cells will be allowed. Once this code is universal, we can block
8098 certain kinds of DOS attack by requiring that EXTEND commands must
8099 be sent using an "early" cell.
8102 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8103 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8104 on the client side when connecting to a hidden service. Bugfix
8105 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8106 - Ensure that two circuits can never exist on the same connection
8107 with the same circuit ID, even if one is marked for close. This
8108 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8111 - When relays do their initial bandwidth measurement, don't limit
8112 to just our entry guards for the test circuits. Otherwise we tend
8113 to have multiple test circuits going through a single entry guard,
8114 which makes our bandwidth test less accurate. Fixes part of bug 654;
8115 patch contributed by Josh Albrecht.
8116 - Add an ExcludeExitNodes option so users can list a set of nodes
8117 that should be be excluded from the exit node position, but
8118 allowed elsewhere. Implements proposal 151.
8119 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8120 ExcludeNodes and ExcludeExitNodes lists.
8121 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8122 be more efficient. Formerly it was quadratic in the number of
8123 servers; now it should be linear. Fixes bug 509.
8124 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8125 and n_conn_id_digest fields into a separate structure that's
8126 only needed when the circuit has not yet attached to an n_conn.
8129 - Change the contrib/tor.logrotate script so it makes the new
8130 logs as "_tor:_tor" rather than the default, which is generally
8131 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8132 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8133 warnings (occasionally), but it can also cause the compiler to
8134 eliminate error-checking code. Suggested by Peter Gutmann.
8135 - When a hidden service is giving up on an introduction point candidate
8136 that was not included in the last published rendezvous descriptor,
8137 don't reschedule publication of the next descriptor. Fixes bug 763.
8139 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8140 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8141 and nobody claims to be using them. Fixes bug 754. Bugfix on
8142 0.1.0.1-rc. Patch from Christian Wilms.
8143 - Fix a small alignment and memory-wasting bug on buffer chunks.
8146 o Minor bugfixes (controller):
8147 - When closing an application-side connection because its circuit
8148 is getting torn down, generate the stream event correctly.
8149 Bugfix on 0.1.2.x. Anonymous patch.
8152 - Remove all backward-compatibility code to support relays running
8153 versions of Tor so old that they no longer work at all on the
8157 Changes in version 0.2.0.30 - 2008-07-15
8159 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8160 warnings (occasionally), but it can also cause the compiler to
8161 eliminate error-checking code. Suggested by Peter Gutmann.
8164 Changes in version 0.2.0.29-rc - 2008-07-08
8165 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8166 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8169 - If you have more than one bridge but don't know their keys,
8170 you would only launch a request for the descriptor of the first one
8171 on your list. (Tor considered launching requests for the others, but
8172 found that it already had a connection on the way for $0000...0000
8173 so it didn't open another.) Bugfix on 0.2.0.x.
8174 - If you have more than one bridge but don't know their keys, and the
8175 connection to one of the bridges failed, you would cancel all
8176 pending bridge connections. (After all, they all have the same
8177 digest.) Bugfix on 0.2.0.x.
8178 - When a hidden service was trying to establish an introduction point,
8179 and Tor had built circuits preemptively for such purposes, we
8180 were ignoring all the preemptive circuits and launching a new one
8181 instead. Bugfix on 0.2.0.14-alpha.
8182 - When a hidden service was trying to establish an introduction point,
8183 and Tor *did* manage to reuse one of the preemptively built
8184 circuits, it didn't correctly remember which one it used,
8185 so it asked for another one soon after, until there were no
8186 more preemptive circuits, at which point it launched one from
8187 scratch. Bugfix on 0.0.9.x.
8188 - Make directory servers include the X-Your-Address-Is: http header in
8189 their responses even for begin_dir conns. Now clients who only
8190 ever use begin_dir connections still have a way to learn their IP
8191 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8194 - Fix a macro/CPP interaction that was confusing some compilers:
8195 some GCCs don't like #if/#endif pairs inside macro arguments.
8197 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8198 Fixes bug 704; fix from Steven Murdoch.
8199 - When opening /dev/null in finish_daemonize(), do not pass the
8200 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8201 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8202 - Correctly detect transparent proxy support on Linux hosts that
8203 require in.h to be included before netfilter_ipv4.h. Patch
8205 - Disallow session resumption attempts during the renegotiation
8206 stage of the v2 handshake protocol. Clients should never be trying
8207 session resumption at this point, but apparently some did, in
8208 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8209 found by Geoff Goodell.
8212 Changes in version 0.2.1.2-alpha - 2008-06-20
8213 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8214 make it easier to set up your own private Tor network; fixes several
8215 big bugs with using more than one bridge relay; fixes a big bug with
8216 offering hidden services quickly after Tor starts; and uses a better
8217 API for reporting potential bootstrapping problems to the controller.
8220 - New TestingTorNetwork config option to allow adjustment of
8221 previously constant values that, while reasonable, could slow
8222 bootstrapping. Implements proposal 135. Patch from Karsten.
8225 - If you have more than one bridge but don't know their digests,
8226 you would only learn a request for the descriptor of the first one
8227 on your list. (Tor considered launching requests for the others, but
8228 found that it already had a connection on the way for $0000...0000
8229 so it didn't open another.) Bugfix on 0.2.0.x.
8230 - If you have more than one bridge but don't know their digests,
8231 and the connection to one of the bridges failed, you would cancel
8232 all pending bridge connections. (After all, they all have the
8233 same digest.) Bugfix on 0.2.0.x.
8234 - When establishing a hidden service, introduction points that
8235 originate from cannibalized circuits are completely ignored and not
8236 included in rendezvous service descriptors. This might be another
8237 reason for delay in making a hidden service available. Bugfix
8238 from long ago (0.0.9.x?)
8241 - Allow OpenSSL to use dynamic locks if it wants.
8242 - When building a consensus, do not include routers that are down.
8243 This will cut down 30% to 40% on consensus size. Implements
8245 - In directory authorities' approved-routers files, allow
8246 fingerprints with or without space.
8247 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8248 controller can query our current bootstrap state in case it attaches
8249 partway through and wants to catch up.
8250 - Send an initial "Starting" bootstrap status event, so we have a
8251 state to start out in.
8254 - Asking for a conditional consensus at .../consensus/<fingerprints>
8255 would crash a dirserver if it did not already have a
8256 consensus. Bugfix on 0.2.1.1-alpha.
8257 - Clean up some macro/CPP interactions: some GCC versions don't like
8258 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8261 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8262 - Directory authorities shouldn't complain about bootstrapping
8263 problems just because they do a lot of reachability testing and
8264 some of the connection attempts fail.
8265 - Start sending "count" and "recommendation" key/value pairs in
8266 bootstrap problem status events, so the controller can hear about
8267 problems even before Tor decides they're worth reporting for sure.
8268 - If you're using bridges, generate "bootstrap problem" warnings
8269 as soon as you run out of working bridges, rather than waiting
8270 for ten failures -- which will never happen if you have less than
8272 - If we close our OR connection because there's been a circuit
8273 pending on it for too long, we were telling our bootstrap status
8274 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8277 Changes in version 0.2.1.1-alpha - 2008-06-13
8278 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8279 were making the Tor process bloat especially on Linux; makes our TLS
8280 handshake blend in better; sends "bootstrap phase" status events to
8281 the controller, so it can keep the user informed of progress (and
8282 problems) fetching directory information and establishing circuits;
8283 and adds a variety of smaller features.
8286 - More work on making our TLS handshake blend in: modify the list
8287 of ciphers advertised by OpenSSL in client mode to even more
8288 closely resemble a common web browser. We cheat a little so that
8289 we can advertise ciphers that the locally installed OpenSSL doesn't
8291 - Start sending "bootstrap phase" status events to the controller,
8292 so it can keep the user informed of progress fetching directory
8293 information and establishing circuits. Also inform the controller
8294 if we think we're stuck at a particular bootstrap phase. Implements
8296 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8297 cross-platform entropy collection again. We used to use it, then
8298 stopped using it because of a bug that could crash systems that
8299 called RAND_poll when they had a lot of fds open. It looks like the
8300 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8301 at startup, and to call RAND_poll() when we reseed later only if
8302 we have a non-buggy OpenSSL version.
8305 - When we choose to abandon a new entry guard because we think our
8306 older ones might be better, close any circuits pending on that
8307 new entry guard connection. This fix should make us recover much
8308 faster when our network is down and then comes back. Bugfix on
8309 0.1.2.8-beta; found by lodger.
8311 o Memory fixes and improvements:
8312 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8313 to avoid unused RAM in buffer chunks and memory pools.
8314 - Speed up parsing and cut down on memory fragmentation by using
8315 stack-style allocations for parsing directory objects. Previously,
8316 this accounted for over 40% of allocations from within Tor's code
8317 on a typical directory cache.
8318 - Use a Bloom filter rather than a digest-based set to track which
8319 descriptors we need to keep around when we're cleaning out old
8320 router descriptors. This speeds up the computation significantly,
8321 and may reduce fragmentation.
8322 - Reduce the default smartlist size from 32 to 16; it turns out that
8323 most smartlists hold around 8-12 elements tops.
8324 - Make dumpstats() log the fullness and size of openssl-internal
8326 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8327 patch to their OpenSSL, turn it on to save memory on servers. This
8328 patch will (with any luck) get included in a mainline distribution
8330 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8331 compress cells, which are basically all encrypted, compressed,
8335 - Stop reloading the router list from disk for no reason when we
8336 run out of reachable directory mirrors. Once upon a time reloading
8337 it would set the 'is_running' flag back to 1 for them. It hasn't
8338 done that for a long time.
8339 - In very rare situations new hidden service descriptors were
8340 published earlier than 30 seconds after the last change to the
8341 service. (We currently think that a hidden service descriptor
8342 that's been stable for 30 seconds is worth publishing.)
8345 - Allow separate log levels to be configured for different logging
8346 domains. For example, this allows one to log all notices, warnings,
8347 or errors, plus all memory management messages of level debug or
8348 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8349 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8350 and stop using a warning that had become unfixably verbose under
8352 - New --hush command-line option similar to --quiet. While --quiet
8353 disables all logging to the console on startup, --hush limits the
8354 output to messages of warning and error severity.
8355 - Servers support a new URL scheme for consensus downloads that
8356 allows the client to specify which authorities are trusted.
8357 The server then only sends the consensus if the client will trust
8358 it. Otherwise a 404 error is sent back. Clients use this
8359 new scheme when the server supports it (meaning it's running
8360 0.2.1.1-alpha or later). Implements proposal 134.
8361 - New configure/torrc options (--enable-geoip-stats,
8362 DirRecordUsageByCountry) to record how many IPs we've served
8363 directory info to in each country code, how many status documents
8364 total we've sent to each country code, and what share of the total
8365 directory requests we should expect to see.
8366 - Use the TLS1 hostname extension to more closely resemble browser
8368 - Lots of new unit tests.
8369 - Add a macro to implement the common pattern of iterating through
8370 two parallel lists in lockstep.
8373 Changes in version 0.2.0.28-rc - 2008-06-13
8374 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8375 performance bug, and fixes a bunch of smaller bugs.
8378 - Fix a bug where, when we were choosing the 'end stream reason' to
8379 put in our relay end cell that we send to the exit relay, Tor
8380 clients on Windows were sometimes sending the wrong 'reason'. The
8381 anonymity problem is that exit relays may be able to guess whether
8382 the client is running Windows, thus helping partition the anonymity
8383 set. Down the road we should stop sending reasons to exit relays,
8384 or otherwise prevent future versions of this bug.
8387 - While setting up a hidden service, some valid introduction circuits
8388 were overlooked and abandoned. This might be the reason for
8389 the long delay in making a hidden service available. Bugfix on
8393 - Update to the "June 9 2008" ip-to-country file.
8394 - Run 'make test' as part of 'make dist', so we stop releasing so
8395 many development snapshots that fail their unit tests.
8398 - When we're checking if we have enough dir info for each relay
8399 to begin establishing circuits, make sure that we actually have
8400 the descriptor listed in the consensus, not just any descriptor.
8402 - Bridge relays no longer print "xx=0" in their extrainfo document
8403 for every single country code in the geoip db. Bugfix on
8405 - Only warn when we fail to load the geoip file if we were planning to
8406 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8407 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8408 Tor won't realize it should publish a new relay descriptor. Fixes
8409 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8410 - When we haven't had any application requests lately, don't bother
8411 logging that we have expired a bunch of descriptors. Bugfix
8413 - Make relay cells written on a connection count as non-padding when
8414 tracking how long a connection has been in use. Bugfix on
8415 0.2.0.1-alpha. Spotted by lodger.
8416 - Fix unit tests in 0.2.0.27-rc.
8417 - Fix compile on Windows.
8420 Changes in version 0.2.0.27-rc - 2008-06-03
8421 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8422 release candidates. In particular, we now include an IP-to-country
8423 GeoIP database, so controllers can easily look up what country a
8424 given relay is in, and so bridge relays can give us some sanitized
8425 summaries about which countries are making use of bridges. (See proposal
8426 126-geoip-fetching.txt for details.)
8429 - Include an IP-to-country GeoIP file in the tarball, so bridge
8430 relays can report sanitized summaries of the usage they're seeing.
8433 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8434 Robert Hogan. Fixes the first part of bug 681.
8435 - Make bridge authorities never serve extrainfo docs.
8436 - Add support to detect Libevent versions in the 1.4.x series
8438 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8439 - Include a new contrib/tor-exit-notice.html file that exit relay
8440 operators can put on their website to help reduce abuse queries.
8443 - When tunneling an encrypted directory connection, and its first
8444 circuit fails, do not leave it unattached and ask the controller
8445 to deal. Fixes the second part of bug 681.
8446 - Make bridge authorities correctly expire old extrainfo documents
8450 Changes in version 0.2.0.26-rc - 2008-05-13
8451 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8452 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8453 should upgrade, whether they're running Debian or not.
8455 o Major security fixes:
8456 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8457 moria1 V3 directory authorities. The old keys were generated with
8458 a vulnerable version of Debian's OpenSSL package, and must be
8459 considered compromised. Other authorities' keys were not generated
8460 with an affected version of OpenSSL.
8463 - List authority signatures as "unrecognized" based on DirServer
8464 lines, not on cert cache. Bugfix on 0.2.0.x.
8467 - Add a new V3AuthUseLegacyKey option to make it easier for
8468 authorities to change their identity keys if they have to.
8471 Changes in version 0.2.0.25-rc - 2008-04-23
8472 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8475 - Remember to initialize threading before initializing logging.
8476 Otherwise, many BSD-family implementations will crash hard on
8477 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8480 - Authorities correctly free policies on bad servers on
8481 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8484 Changes in version 0.2.0.24-rc - 2008-04-22
8485 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8486 v3 directory authority, makes relays with dynamic IP addresses and no
8487 DirPort notice more quickly when their IP address changes, fixes a few
8488 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8490 o New directory authorities:
8491 - Take lefkada out of the list of v3 directory authorities, since
8492 it has been down for months.
8493 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8497 - Detect address changes more quickly on non-directory mirror
8498 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8500 o Minor features (security):
8501 - Reject requests for reverse-dns lookup of names that are in
8502 a private address space. Patch from lodger.
8503 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8506 o Minor bugfixes (crashes):
8507 - Avoid a rare assert that can trigger when Tor doesn't have much
8508 directory information yet and it tries to fetch a v2 hidden
8509 service descriptor. Fixes bug 651, reported by nwf.
8510 - Initialize log mutex before initializing dmalloc. Otherwise,
8511 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8512 - Use recursive pthread mutexes in order to avoid deadlock when
8513 logging debug-level messages to a controller. Bug spotted by nwf,
8514 bugfix on 0.2.0.16-alpha.
8516 o Minor bugfixes (resource management):
8517 - Keep address policies from leaking memory: start their refcount
8518 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8519 - Free authority certificates on exit, so they don't look like memory
8520 leaks. Bugfix on 0.2.0.19-alpha.
8521 - Free static hashtables for policy maps and for TLS connections on
8522 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
8523 - Avoid allocating extra space when computing consensuses on 64-bit
8524 platforms. Bug spotted by aakova.
8526 o Minor bugfixes (misc):
8527 - Do not read the configuration file when we've only been told to
8528 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8529 based on patch from Sebastian Hahn.
8530 - Exit relays that are used as a client can now reach themselves
8531 using the .exit notation, rather than just launching an infinite
8532 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8533 - When attempting to open a logfile fails, tell us why.
8534 - Fix a dumb bug that was preventing us from knowing that we should
8535 preemptively build circuits to handle expected directory requests.
8536 Fixes bug 660. Bugfix on 0.1.2.x.
8537 - Warn less verbosely about clock skew from netinfo cells from
8538 untrusted sources. Fixes bug 663.
8539 - Make controller stream events for DNS requests more consistent,
8540 by adding "new stream" events for DNS requests, and removing
8541 spurious "stream closed" events" for cached reverse resolves.
8542 Patch from mwenge. Fixes bug 646.
8543 - Correctly notify one-hop connections when a circuit build has
8544 failed. Possible fix for bug 669. Found by lodger.
8547 Changes in version 0.2.0.23-rc - 2008-03-24
8548 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
8549 makes bootstrapping faster if the first directory mirror you contact
8550 is down. The bundles also include the new Vidalia 0.1.2 release.
8553 - When a tunneled directory request is made to a directory server
8554 that's down, notice after 30 seconds rather than 120 seconds. Also,
8555 fail any begindir streams that are pending on it, so they can
8556 retry elsewhere. This was causing multi-minute delays on bootstrap.
8559 Changes in version 0.2.0.22-rc - 2008-03-18
8560 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
8561 enables encrypted directory connections by default for non-relays, fixes
8562 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
8563 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
8566 - Enable encrypted directory connections by default for non-relays,
8567 so censor tools that block Tor directory connections based on their
8568 plaintext patterns will no longer work. This means Tor works in
8569 certain censored countries by default again.
8572 - Make sure servers always request certificates from clients during
8573 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
8574 - Do not enter a CPU-eating loop when a connection is closed in
8575 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
8576 diagnosed by lodger; bugfix on 0.2.0.20-rc.
8577 - Fix assertion failure that could occur when a blocked circuit
8578 became unblocked, and it had pending client DNS requests. Bugfix
8579 on 0.2.0.1-alpha. Fixes bug 632.
8581 o Minor bugfixes (on 0.1.2.x):
8582 - Generate "STATUS_SERVER" events rather than misspelled
8583 "STATUS_SEVER" events. Caught by mwenge.
8584 - When counting the number of bytes written on a TLS connection,
8585 look at the BIO actually used for writing to the network, not
8586 at the BIO used (sometimes) to buffer data for the network.
8587 Looking at different BIOs could result in write counts on the
8588 order of ULONG_MAX. Fixes bug 614.
8589 - On Windows, correctly detect errors when listing the contents of
8590 a directory. Fix from lodger.
8592 o Minor bugfixes (on 0.2.0.x):
8593 - Downgrade "sslv3 alert handshake failure" message to INFO.
8594 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
8595 left BandwidthRate and BandwidthBurst at the default, we would be
8596 silently limited by those defaults. Now raise them to match the
8597 RelayBandwidth* values.
8598 - Fix the SVK version detection logic to work correctly on a branch.
8599 - Make --enable-openbsd-malloc work correctly on Linux with alpha
8600 CPUs. Fixes bug 625.
8601 - Logging functions now check that the passed severity is sane.
8602 - Use proper log levels in the testsuite call of
8603 get_interface_address6().
8604 - When using a nonstandard malloc, do not use the platform values for
8605 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
8606 - Make the openbsd malloc code use 8k pages on alpha CPUs and
8608 - Detect mismatched page sizes when using --enable-openbsd-malloc.
8609 - Avoid double-marked-for-close warning when certain kinds of invalid
8610 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
8611 for bug 617. Bugfix on 0.2.0.1-alpha.
8612 - Make sure that the "NULL-means-reject *:*" convention is followed by
8613 all the policy manipulation functions, avoiding some possible crash
8614 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
8615 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
8616 actually works, and doesn't warn about every single reverse lookup.
8617 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
8620 - Only log guard node status when guard node status has changed.
8621 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
8622 make "INFO" 75% less verbose.
8625 Changes in version 0.2.0.21-rc - 2008-03-02
8626 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
8627 makes Tor work well with Vidalia again, fixes a rare assert bug,
8628 and fixes a pair of more minor bugs. The bundles also include Vidalia
8629 0.1.0 and Torbutton 1.1.16.
8632 - The control port should declare that it requires password auth
8633 when HashedControlSessionPassword is set too. Patch from Matt Edman;
8634 bugfix on 0.2.0.20-rc. Fixes bug 615.
8635 - Downgrade assert in connection_buckets_decrement() to a log message.
8636 This may help us solve bug 614, and in any case will make its
8637 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
8638 - We were sometimes miscounting the number of bytes read from the
8639 network, causing our rate limiting to not be followed exactly.
8640 Bugfix on 0.2.0.16-alpha. Reported by lodger.
8643 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
8644 OpenSSL versions should have been working fine. Diagnosis and patch
8645 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
8646 Bugfix on 0.2.0.20-rc.
8649 Changes in version 0.2.0.20-rc - 2008-02-24
8650 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
8651 makes more progress towards normalizing Tor's TLS handshake, makes
8652 hidden services work better again, helps relays bootstrap if they don't
8653 know their IP address, adds optional support for linking in openbsd's
8654 allocator or tcmalloc, allows really fast relays to scale past 15000
8655 sockets, and fixes a bunch of minor bugs reported by Veracode.
8658 - Enable the revised TLS handshake based on the one designed by
8659 Steven Murdoch in proposal 124, as revised in proposal 130. It
8660 includes version negotiation for OR connections as described in
8661 proposal 105. The new handshake is meant to be harder for censors
8662 to fingerprint, and it adds the ability to detect certain kinds of
8663 man-in-the-middle traffic analysis attacks. The version negotiation
8664 feature will allow us to improve Tor's link protocol more safely
8666 - Choose which bridge to use proportional to its advertised bandwidth,
8667 rather than uniformly at random. This should speed up Tor for
8668 bridge users. Also do this for people who set StrictEntryNodes.
8669 - When a TrackHostExits-chosen exit fails too many times in a row,
8670 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
8673 - Resolved problems with (re-)fetching hidden service descriptors.
8674 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
8676 - If we only ever used Tor for hidden service lookups or posts, we
8677 would stop building circuits and start refusing connections after
8678 24 hours, since we falsely believed that Tor was dormant. Reported
8679 by nwf; bugfix on 0.1.2.x.
8680 - Servers that don't know their own IP address should go to the
8681 authorities for their first directory fetch, even if their DirPort
8682 is off or if they don't know they're reachable yet. This will help
8683 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
8684 - When counting the number of open sockets, count not only the number
8685 of sockets we have received from the socket() call, but also
8686 the number we've gotten from accept() and socketpair(). This bug
8687 made us fail to count all sockets that we were using for incoming
8688 connections. Bugfix on 0.2.0.x.
8689 - Fix code used to find strings within buffers, when those strings
8690 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
8691 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
8692 - Add a new __HashedControlSessionPassword option for controllers
8693 to use for one-off session password hashes that shouldn't get
8694 saved to disk by SAVECONF --- Vidalia users were accumulating a
8695 pile of HashedControlPassword lines in their torrc files, one for
8696 each time they had restarted Tor and then clicked Save. Make Tor
8697 automatically convert "HashedControlPassword" to this new option but
8698 only when it's given on the command line. Partial fix for bug 586.
8700 o Minor features (performance):
8701 - Tune parameters for cell pool allocation to minimize amount of
8703 - Add OpenBSD malloc code from phk as an optional malloc
8704 replacement on Linux: some glibc libraries do very poorly
8705 with Tor's memory allocation patterns. Pass
8706 --enable-openbsd-malloc to get the replacement malloc code.
8707 - Add a --with-tcmalloc option to the configure script to link
8708 against tcmalloc (if present). Does not yet search for
8709 non-system include paths.
8710 - Stop imposing an arbitrary maximum on the number of file descriptors
8711 used for busy servers. Bug reported by Olaf Selke; patch from
8714 o Minor features (other):
8715 - When SafeLogging is disabled, log addresses along with all TLS
8717 - When building with --enable-gcc-warnings, check for whether Apple's
8718 warning "-Wshorten-64-to-32" is available.
8719 - Add a --passphrase-fd argument to the tor-gencert command for
8722 o Minor bugfixes (memory leaks and code problems):
8723 - We were leaking a file descriptor if Tor started with a zero-length
8724 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
8725 - Detect size overflow in zlib code. Reported by Justin Ferguson and
8727 - We were comparing the raw BridgePassword entry with a base64'ed
8728 version of it, when handling a "/tor/networkstatus-bridges"
8729 directory request. Now compare correctly. Noticed by Veracode.
8730 - Recover from bad tracked-since value in MTBF-history file.
8732 - Alter the code that tries to recover from unhandled write
8733 errors, to not try to flush onto a socket that's given us
8734 unhandled errors. Bugfix on 0.1.2.x.
8735 - Make Unix controlsockets work correctly on OpenBSD. Patch from
8736 tup. Bugfix on 0.2.0.3-alpha.
8738 o Minor bugfixes (other):
8739 - If we have an extra-info document for our server, always make
8740 it available on the control port, even if we haven't gotten
8741 a copy of it from an authority yet. Patch from mwenge.
8742 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
8743 - Directory mirrors no longer include a guess at the client's IP
8744 address if the connection appears to be coming from the same /24
8745 network; it was producing too many wrong guesses.
8746 - Make the new hidden service code respect the SafeLogging setting.
8747 Bugfix on 0.2.0.x. Patch from Karsten.
8748 - When starting as an authority, do not overwrite all certificates
8749 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
8750 - If we're trying to flush the last bytes on a connection (for
8751 example, when answering a directory request), reset the
8752 time-to-give-up timeout every time we manage to write something
8753 on the socket. Bugfix on 0.1.2.x.
8754 - Change the behavior of "getinfo status/good-server-descriptor"
8755 so it doesn't return failure when any authority disappears.
8756 - Even though the man page said that "TrackHostExits ." should
8757 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
8758 - Report TLS "zero return" case as a "clean close" and "IO error"
8759 as a "close". Stop calling closes "unexpected closes": existing
8760 Tors don't use SSL_close(), so having a connection close without
8761 the TLS shutdown handshake is hardly unexpected.
8762 - Send NAMESERVER_STATUS messages for a single failed nameserver
8765 o Code simplifications and refactoring:
8766 - Remove the tor_strpartition function: its logic was confused,
8767 and it was only used for one thing that could be implemented far
8771 Changes in version 0.2.0.19-alpha - 2008-02-09
8772 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
8773 handshake, makes path selection for relays more secure and IP address
8774 guessing more robust, and generally fixes a lot of bugs in preparation
8775 for calling the 0.2.0 branch stable.
8778 - Do not include recognizeable strings in the commonname part of
8779 Tor's x509 certificates.
8782 - If we're a relay, avoid picking ourselves as an introduction point,
8783 a rendezvous point, or as the final hop for internal circuits. Bug
8784 reported by taranis and lodger. Bugfix on 0.1.2.x.
8785 - Patch from "Andrew S. Lists" to catch when we contact a directory
8786 mirror at IP address X and he says we look like we're coming from
8787 IP address X. Bugfix on 0.1.2.x.
8789 o Minor features (security):
8790 - Be more paranoid about overwriting sensitive memory on free(),
8791 as a defensive programming tactic to ensure forward secrecy.
8793 o Minor features (directory authority):
8794 - Actually validate the options passed to AuthDirReject,
8795 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
8796 - Reject router descriptors with out-of-range bandwidthcapacity or
8797 bandwidthburst values.
8799 o Minor features (controller):
8800 - Reject controller commands over 1MB in length. This keeps rogue
8801 processes from running us out of memory.
8803 o Minor features (misc):
8804 - Give more descriptive well-formedness errors for out-of-range
8805 hidden service descriptor/protocol versions.
8806 - Make memory debugging information describe more about history
8807 of cell allocation, so we can help reduce our memory use.
8809 o Deprecated features (controller):
8810 - The status/version/num-versioning and status/version/num-concurring
8811 GETINFO options are no longer useful in the v3 directory protocol:
8812 treat them as deprecated, and warn when they're used.
8815 - When our consensus networkstatus has been expired for a while, stop
8816 being willing to build circuits using it. Fixes bug 401. Bugfix
8818 - Directory caches now fetch certificates from all authorities
8819 listed in a networkstatus consensus, even when they do not
8820 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
8821 - When connecting to a bridge without specifying its key, insert
8822 the connection into the identity-to-connection map as soon as
8823 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
8824 - Detect versions of OS X where malloc_good_size() is present in the
8825 library but never actually declared. Resolves bug 587. Bugfix
8827 - Stop incorrectly truncating zlib responses to directory authority
8828 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
8829 - Stop recommending that every server operator send mail to tor-ops.
8830 Resolves bug 597. Bugfix on 0.1.2.x.
8831 - Don't trigger an assert if we start a directory authority with a
8832 private IP address (like 127.0.0.1).
8833 - Avoid possible failures when generating a directory with routers
8834 with over-long versions strings, or too many flags set. Bugfix
8836 - If an attempt to launch a DNS resolve request over the control
8837 port fails because we have overrun the limit on the number of
8838 connections, tell the controller that the request has failed.
8839 - Avoid using too little bandwidth when our clock skips a few
8840 seconds. Bugfix on 0.1.2.x.
8841 - Fix shell error when warning about missing packages in configure
8842 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
8843 - Do not become confused when receiving a spurious VERSIONS-like
8844 cell from a confused v1 client. Bugfix on 0.2.0.x.
8845 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
8846 introduction points for a hidden service have failed. Patch from
8847 Karsten Loesing. Bugfix on 0.2.0.x.
8849 o Code simplifications and refactoring:
8850 - Remove some needless generality from cpuworker code, for improved
8852 - Stop overloading the circuit_t.onionskin field for both "onionskin
8853 from a CREATE cell that we are waiting for a cpuworker to be
8854 assigned" and "onionskin from an EXTEND cell that we are going to
8855 send to an OR as soon as we are connected". Might help with bug 600.
8856 - Add an in-place version of aes_crypt() so that we can avoid doing a
8857 needless memcpy() call on each cell payload.
8860 Changes in version 0.2.0.18-alpha - 2008-01-25
8861 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
8862 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
8863 that can warn or reject connections to ports generally associated with
8864 vulnerable-plaintext protocols.
8866 o New directory authorities:
8867 - Set up dannenberg (run by CCC) as the sixth v3 directory
8871 - Fix a major memory leak when attempting to use the v2 TLS
8872 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
8873 - We accidentally enabled the under-development v2 TLS handshake
8874 code, which was causing log entries like "TLS error while
8875 renegotiating handshake". Disable it again. Resolves bug 590.
8876 - We were computing the wrong Content-Length: header for directory
8877 responses that need to be compressed on the fly, causing clients
8878 asking for those items to always fail. Bugfix on 0.2.0.x; partially
8882 - Avoid going directly to the directory authorities even if you're a
8883 relay, if you haven't found yourself reachable yet or if you've
8884 decided not to advertise your dirport yet. Addresses bug 556.
8885 - If we've gone 12 hours since our last bandwidth check, and we
8886 estimate we have less than 50KB bandwidth capacity but we could
8887 handle more, do another bandwidth test.
8888 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
8889 Tor can warn and/or refuse connections to ports commonly used with
8890 vulnerable-plaintext protocols. Currently we warn on ports 23,
8891 109, 110, and 143, but we don't reject any.
8894 - When we setconf ClientOnly to 1, close any current OR and Dir
8895 listeners. Reported by mwenge.
8896 - When we get a consensus that's been signed by more people than
8897 we expect, don't log about it; it's not a big deal. Reported
8901 - Don't answer "/tor/networkstatus-bridges" directory requests if
8902 the request isn't encrypted.
8903 - Make "ClientOnly 1" config option disable directory ports too.
8904 - Patches from Karsten Loesing to make v2 hidden services more
8905 robust: work even when there aren't enough HSDir relays available;
8906 retry when a v2 rend desc fetch fails; but don't retry if we
8907 already have a usable v0 rend desc.
8910 Changes in version 0.2.0.17-alpha - 2008-01-17
8911 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
8914 - Make the tor-gencert man page get included correctly in the tarball.
8917 Changes in version 0.2.0.16-alpha - 2008-01-17
8918 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
8919 Loesing, and generally cleans up a lot of features and minor bugs.
8921 o New directory authorities:
8922 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
8925 o Major performance improvements:
8926 - Switch our old ring buffer implementation for one more like that
8927 used by free Unix kernels. The wasted space in a buffer with 1mb
8928 of data will now be more like 8k than 1mb. The new implementation
8929 also avoids realloc();realloc(); patterns that can contribute to
8930 memory fragmentation.
8933 - Configuration files now accept C-style strings as values. This
8934 helps encode characters not allowed in the current configuration
8935 file format, such as newline or #. Addresses bug 557.
8936 - Although we fixed bug 539 (where servers would send HTTP status 503
8937 responses _and_ send a body too), there are still servers out
8938 there that haven't upgraded. Therefore, make clients parse such
8939 bodies when they receive them.
8940 - When we're not serving v2 directory information, there is no reason
8941 to actually keep any around. Remove the obsolete files and directory
8942 on startup if they are very old and we aren't going to serve them.
8944 o Minor performance improvements:
8945 - Reference-count and share copies of address policy entries; only 5%
8946 of them were actually distinct.
8947 - Never walk through the list of logs if we know that no log is
8948 interested in a given message.
8951 - When an authority has not signed a consensus, do not try to
8952 download a nonexistent "certificate with key 00000000". Bugfix
8953 on 0.2.0.x. Fixes bug 569.
8954 - Fix a rare assert error when we're closing one of our threads:
8955 use a mutex to protect the list of logs, so we never write to the
8956 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
8957 bug 575, which is kind of the revenge of bug 222.
8958 - Patch from Karsten Loesing to complain less at both the client
8959 and the relay when a relay used to have the HSDir flag but doesn't
8960 anymore, and we try to upload a hidden service descriptor.
8961 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
8963 - Do not try to download missing certificates until we have tried
8964 to check our fallback consensus. Fixes bug 583.
8965 - Make bridges round reported GeoIP stats info up to the nearest
8966 estimate, not down. Now we can distinguish between "0 people from
8967 this country" and "1 person from this country".
8968 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
8969 - Avoid possible segfault if key generation fails in
8970 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
8971 - Avoid segfault in the case where a badly behaved v2 versioning
8972 directory sends a signed networkstatus with missing client-versions.
8974 - Avoid segfaults on certain complex invocations of
8975 router_get_by_hexdigest(). Bugfix on 0.1.2.
8976 - Correct bad index on array access in parse_http_time(). Bugfix
8978 - Fix possible bug in vote generation when server versions are present
8979 but client versions are not.
8980 - Fix rare bug on REDIRECTSTREAM control command when called with no
8981 port set: it could erroneously report an error when none had
8983 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
8984 compressing large objects and find ourselves with more than 4k
8985 left over. Bugfix on 0.2.0.
8986 - Fix a small memory leak when setting up a hidden service.
8987 - Fix a few memory leaks that could in theory happen under bizarre
8989 - Fix an assert if we post a general-purpose descriptor via the
8990 control port but that descriptor isn't mentioned in our current
8991 network consensus. Bug reported by Jon McLachlan; bugfix on
8994 o Minor features (controller):
8995 - Get NS events working again. Patch from tup.
8996 - The GETCONF command now escapes and quotes configuration values
8997 that don't otherwise fit into the torrc file.
8998 - The SETCONF command now handles quoted values correctly.
9000 o Minor features (directory authorities):
9001 - New configuration options to override default maximum number of
9002 servers allowed on a single IP address. This is important for
9003 running a test network on a single host.
9004 - Actually implement the -s option to tor-gencert.
9005 - Add a manual page for tor-gencert.
9007 o Minor features (bridges):
9008 - Bridge authorities no longer serve bridge descriptors over
9009 unencrypted connections.
9011 o Minor features (other):
9012 - Add hidden services and DNSPorts to the list of things that make
9013 Tor accept that it has running ports. Change starting Tor with no
9014 ports from a fatal error to a warning; we might change it back if
9015 this turns out to confuse anybody. Fixes bug 579.
9018 Changes in version 0.1.2.19 - 2008-01-17
9019 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9020 exit policy a little bit more conservative so it's safer to run an
9021 exit relay on a home system, and fixes a variety of smaller issues.
9024 - Exit policies now reject connections that are addressed to a
9025 relay's public (external) IP address too, unless
9026 ExitPolicyRejectPrivate is turned off. We do this because too
9027 many relays are running nearby to services that trust them based
9031 - When the clock jumps forward a lot, do not allow the bandwidth
9032 buckets to become negative. Fixes bug 544.
9033 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9034 on every successful resolve. Reported by Mike Perry.
9035 - Purge old entries from the "rephist" database and the hidden
9036 service descriptor database even when DirPort is zero.
9037 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9038 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9039 crashing or mis-answering these requests.
9040 - When we decide to send a 503 response to a request for servers, do
9041 not then also send the server descriptors: this defeats the whole
9042 purpose. Fixes bug 539.
9045 - Changing the ExitPolicyRejectPrivate setting should cause us to
9046 rebuild our server descriptor.
9047 - Fix handling of hex nicknames when answering controller requests for
9048 networkstatus by name, or when deciding whether to warn about
9049 unknown routers in a config option. (Patch from mwenge.)
9050 - Fix a couple of hard-to-trigger autoconf problems that could result
9051 in really weird results on platforms whose sys/types.h files define
9052 nonstandard integer types.
9053 - Don't try to create the datadir when running --verify-config or
9054 --hash-password. Resolves bug 540.
9055 - If we were having problems getting a particular descriptor from the
9056 directory caches, and then we learned about a new descriptor for
9057 that router, we weren't resetting our failure count. Reported
9059 - Although we fixed bug 539 (where servers would send HTTP status 503
9060 responses _and_ send a body too), there are still servers out there
9061 that haven't upgraded. Therefore, make clients parse such bodies
9062 when they receive them.
9063 - Run correctly on systems where rlim_t is larger than unsigned long.
9064 This includes some 64-bit systems.
9065 - Run correctly on platforms (like some versions of OS X 10.5) where
9066 the real limit for number of open files is OPEN_FILES, not rlim_max
9067 from getrlimit(RLIMIT_NOFILES).
9068 - Avoid a spurious free on base64 failure.
9069 - Avoid segfaults on certain complex invocations of
9070 router_get_by_hexdigest().
9071 - Fix rare bug on REDIRECTSTREAM control command when called with no
9072 port set: it could erroneously report an error when none had
9076 Changes in version 0.2.0.15-alpha - 2007-12-25
9077 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9078 features added in 0.2.0.13-alpha.
9081 - Fix several remotely triggerable asserts based on DirPort requests
9082 for a v2 or v3 networkstatus object before we were prepared. This
9083 was particularly bad for 0.2.0.13 and later bridge relays, who
9084 would never have a v2 networkstatus and would thus always crash
9085 when used. Bugfixes on 0.2.0.x.
9086 - Estimate the v3 networkstatus size more accurately, rather than
9087 estimating it at zero bytes and giving it artificially high priority
9088 compared to other directory requests. Bugfix on 0.2.0.x.
9091 - Fix configure.in logic for cross-compilation.
9092 - When we load a bridge descriptor from the cache, and it was
9093 previously unreachable, mark it as retriable so we won't just
9094 ignore it. Also, try fetching a new copy immediately. Bugfixes
9096 - The bridge GeoIP stats were counting other relays, for example
9097 self-reachability and authority-reachability tests.
9100 - Support compilation to target iPhone; patch from cjacker huang.
9101 To build for iPhone, pass the --enable-iphone option to configure.
9104 Changes in version 0.2.0.14-alpha - 2007-12-23
9106 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9107 without a datadirectory from a previous Tor install. Reported
9109 - Fix a crash when we fetch a descriptor that turns out to be
9110 unexpected (it used to be in our networkstatus when we started
9111 fetching it, but it isn't in our current networkstatus), and we
9112 aren't using bridges. Bugfix on 0.2.0.x.
9113 - Fix a crash when accessing hidden services: it would work the first
9114 time you use a given introduction point for your service, but
9115 on subsequent requests we'd be using garbage memory. Fixed by
9116 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9117 - Fix a crash when we load a bridge descriptor from disk but we don't
9118 currently have a Bridge line for it in our torrc. Bugfix on
9122 - If bridge authorities set BridgePassword, they will serve a
9123 snapshot of known bridge routerstatuses from their DirPort to
9124 anybody who knows that password. Unset by default.
9127 - Make the unit tests build again.
9128 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9129 - Make PublishServerDescriptor default to 1, so the default doesn't
9130 have to change as we invent new directory protocol versions.
9131 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9132 be included unless sys/time.h is already included. Fixes
9133 bug 553. Bugfix on 0.2.0.x.
9134 - If we receive a general-purpose descriptor and then receive an
9135 identical bridge-purpose descriptor soon after, don't discard
9136 the next one as a duplicate.
9139 - If BridgeRelay is set to 1, then the default for
9140 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9141 - If the user sets RelayBandwidthRate but doesn't set
9142 RelayBandwidthBurst, then make them equal rather than erroring out.
9145 Changes in version 0.2.0.13-alpha - 2007-12-21
9146 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9147 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9150 o New directory authorities:
9151 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9155 - Only update guard status (usable / not usable) once we have
9156 enough directory information. This was causing us to always pick
9157 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9158 causing us to discard all our guards on startup if we hadn't been
9159 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9160 - Purge old entries from the "rephist" database and the hidden
9161 service descriptor databases even when DirPort is zero. Bugfix
9163 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9164 after opening a circuit -- even a relayed circuit. Bugfix on
9166 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9167 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9168 crashing or mis-answering these types of requests.
9169 - Relays were publishing their server descriptor to v1 and v2
9170 directory authorities, but they didn't try publishing to v3-only
9171 authorities. Fix this; and also stop publishing to v1 authorities.
9173 - When we were reading router descriptors from cache, we were ignoring
9174 the annotations -- so for example we were reading in bridge-purpose
9175 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9176 - When we decided to send a 503 response to a request for servers, we
9177 were then also sending the server descriptors: this defeats the
9178 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9181 - Bridge relays now behave like clients with respect to time
9182 intervals for downloading new consensus documents -- otherwise they
9183 stand out. Bridge users now wait until the end of the interval,
9184 so their bridge relay will be sure to have a new consensus document.
9185 - Three new config options (AlternateDirAuthority,
9186 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9187 user selectively replace the default directory authorities by type,
9188 rather than the all-or-nothing replacement that DirServer offers.
9189 - Tor can now be configured to read a GeoIP file from disk in one
9190 of two formats. This can be used by controllers to map IP addresses
9191 to countries. Eventually, it may support exit-by-country.
9192 - When possible, bridge relays remember which countries users
9193 are coming from, and report aggregate information in their
9194 extra-info documents, so that the bridge authorities can learn
9195 where Tor is blocked.
9196 - Bridge directory authorities now do reachability testing on the
9197 bridges they know. They provide router status summaries to the
9198 controller via "getinfo ns/purpose/bridge", and also dump summaries
9199 to a file periodically.
9200 - Stop fetching directory info so aggressively if your DirPort is
9201 on but your ORPort is off; stop fetching v2 dir info entirely.
9202 You can override these choices with the new FetchDirInfoEarly
9206 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9207 consensus documents when there are too many relays at a single
9208 IP address. Now clear it in v2 network status documents too, and
9209 also clear it in routerinfo_t when the relay is no longer listed
9210 in the relevant networkstatus document.
9211 - Don't crash if we get an unexpected value for the
9212 PublishServerDescriptor config option. Reported by Matt Edman;
9213 bugfix on 0.2.0.9-alpha.
9214 - Our new v2 hidden service descriptor format allows descriptors
9215 that have no introduction points. But Tor crashed when we tried
9216 to build a descriptor with no intro points (and it would have
9217 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9219 - Fix building with dmalloc 5.5.2 with glibc.
9220 - Reject uploaded descriptors and extrainfo documents if they're
9221 huge. Otherwise we'll cache them all over the network and it'll
9222 clog everything up. Reported by Aljosha Judmayer.
9223 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9224 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9225 - When the DANGEROUS_VERSION controller status event told us we're
9226 running an obsolete version, it used the string "OLD" to describe
9227 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9228 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9229 - If we can't expand our list of entry guards (e.g. because we're
9230 using bridges or we have StrictEntryNodes set), don't mark relays
9231 down when they fail a directory request. Otherwise we're too quick
9232 to mark all our entry points down. Bugfix on 0.1.2.x.
9233 - Fix handling of hex nicknames when answering controller requests for
9234 networkstatus by name, or when deciding whether to warn about unknown
9235 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9236 - Fix a couple of hard-to-trigger autoconf problems that could result
9237 in really weird results on platforms whose sys/types.h files define
9238 nonstandard integer types. Bugfix on 0.1.2.x.
9239 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9240 - Don't crash on name lookup when we have no current consensus. Fixes
9241 bug 538; bugfix on 0.2.0.x.
9242 - Only Tors that want to mirror the v2 directory info should
9243 create the "cached-status" directory in their datadir. (All Tors
9244 used to create it.) Bugfix on 0.2.0.9-alpha.
9245 - Directory authorities should only automatically download Extra Info
9246 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9249 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9250 consumers. (We already do this on HUP.)
9251 - Authorities and caches fetch the v2 networkstatus documents
9252 less often, now that v3 is encouraged.
9253 - Add a new config option BridgeRelay that specifies you want to
9254 be a bridge relay. Right now the only difference is that it makes
9255 you answer begin_dir requests, and it makes you cache dir info,
9256 even if your DirPort isn't on.
9257 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9258 ask about source, timestamp of arrival, purpose, etc. We need
9259 something like this to help Vidalia not do GeoIP lookups on bridge
9261 - Allow multiple HashedControlPassword config lines, to support
9262 multiple controller passwords.
9263 - Authorities now decide whether they're authoritative for a given
9264 router based on the router's purpose.
9265 - New config options AuthDirBadDir and AuthDirListBadDirs for
9266 authorities to mark certain relays as "bad directories" in the
9267 networkstatus documents. Also supports the "!baddir" directive in
9268 the approved-routers file.
9271 Changes in version 0.2.0.12-alpha - 2007-11-16
9272 This twelfth development snapshot fixes some more build problems as
9273 well as a few minor bugs.
9276 - Make it build on OpenBSD again. Patch from tup.
9277 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9278 package-building for Red Hat, OS X, etc.
9280 o Minor bugfixes (on 0.1.2.x):
9281 - Changing the ExitPolicyRejectPrivate setting should cause us to
9282 rebuild our server descriptor.
9284 o Minor bugfixes (on 0.2.0.x):
9285 - When we're lacking a consensus, don't try to perform rendezvous
9286 operations. Reported by Karsten Loesing.
9287 - Fix a small memory leak whenever we decide against using a
9288 newly picked entry guard. Reported by Mike Perry.
9289 - When authorities detected more than two relays running on the same
9290 IP address, they were clearing all the status flags but forgetting
9291 to clear the "hsdir" flag. So clients were being told that a
9292 given relay was the right choice for a v2 hsdir lookup, yet they
9293 never had its descriptor because it was marked as 'not running'
9295 - If we're trying to fetch a bridge descriptor and there's no way
9296 the bridge authority could help us (for example, we don't know
9297 a digest, or there is no bridge authority), don't be so eager to
9298 fall back to asking the bridge authority.
9299 - If we're using bridges or have strictentrynodes set, and our
9300 chosen exit is in the same family as all our bridges/entry guards,
9301 then be flexible about families.
9304 - When we negotiate a v2 link-layer connection (not yet implemented),
9305 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9306 negotiated a v1 connection for their next step. Initial code for
9310 Changes in version 0.2.0.11-alpha - 2007-11-12
9311 This eleventh development snapshot fixes some build problems with
9312 the previous snapshot. It also includes a more secure-by-default exit
9313 policy for relays, fixes an enormous memory leak for exit relays, and
9314 fixes another bug where servers were falling out of the directory list.
9317 - Exit policies now reject connections that are addressed to a
9318 relay's public (external) IP address too, unless
9319 ExitPolicyRejectPrivate is turned off. We do this because too
9320 many relays are running nearby to services that trust them based
9321 on network address. Bugfix on 0.1.2.x.
9324 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9325 on every successful resolve. Reported by Mike Perry; bugfix
9327 - On authorities, never downgrade to old router descriptors simply
9328 because they're listed in the consensus. This created a catch-22
9329 where we wouldn't list a new descriptor because there was an
9330 old one in the consensus, and we couldn't get the new one in the
9331 consensus because we wouldn't list it. Possible fix for bug 548.
9332 Also, this might cause bug 543 to appear on authorities; if so,
9333 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9335 o Packaging fixes on 0.2.0.10-alpha:
9336 - We were including instructions about what to do with the
9337 src/config/fallback-consensus file, but we weren't actually
9338 including it in the tarball. Disable all of that for now.
9341 - Allow people to say PreferTunnelledDirConns rather than
9342 PreferTunneledDirConns, for those alternate-spellers out there.
9345 - Don't reevaluate all the information from our consensus document
9346 just because we've downloaded a v2 networkstatus that we intend
9347 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9350 Changes in version 0.2.0.10-alpha - 2007-11-10
9351 This tenth development snapshot adds a third v3 directory authority
9352 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9353 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9354 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9355 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9356 addresses many more minor issues.
9358 o New directory authorities:
9359 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9362 - Allow tunnelled directory connections to ask for an encrypted
9363 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9364 connection independently. Now we can make anonymized begin_dir
9365 connections for (e.g.) more secure hidden service posting and
9367 - More progress on proposal 114: code from Karsten Loesing to
9368 implement new hidden service descriptor format.
9369 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9370 accommodate the growing number of servers that use the default
9371 and are reaching it.
9372 - Directory authorities use a new formula for selecting which nodes
9373 to advertise as Guards: they must be in the top 7/8 in terms of
9374 how long we have known about them, and above the median of those
9375 nodes in terms of weighted fractional uptime.
9376 - Make "not enough dir info yet" warnings describe *why* Tor feels
9377 it doesn't have enough directory info yet.
9380 - Stop servers from crashing if they set a Family option (or
9381 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9383 - Make bridge users work again -- the move to v3 directories in
9384 0.2.0.9-alpha had introduced a number of bugs that made bridges
9385 no longer work for clients.
9386 - When the clock jumps forward a lot, do not allow the bandwidth
9387 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9389 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9390 - When the consensus lists a router descriptor that we previously were
9391 mirroring, but that we considered non-canonical, reload the
9392 descriptor as canonical. This fixes bug 543 where Tor servers
9393 would start complaining after a few days that they don't have
9394 enough directory information to build a circuit.
9395 - Consider replacing the current consensus when certificates arrive
9396 that make the pending consensus valid. Previously, we were only
9397 considering replacement when the new certs _didn't_ help.
9398 - Fix an assert error on startup if we didn't already have the
9399 consensus and certs cached in our datadirectory: we were caching
9400 the consensus in consensus_waiting_for_certs but then free'ing it
9402 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9403 Request) if we need more v3 certs but we've already got pending
9404 requests for all of them.
9405 - Correctly back off from failing certificate downloads. Fixes
9407 - Authorities don't vote on the Running flag if they have been running
9408 for less than 30 minutes themselves. Fixes bug 547, where a newly
9409 started authority would vote that everyone was down.
9412 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9413 it, it had no AES, and it hasn't seen any security patches since
9417 - Clients now hold circuitless TLS connections open for 1.5 times
9418 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9419 rebuild a new circuit over them within that timeframe. Previously,
9420 they held them open only for KeepalivePeriod (5 minutes).
9421 - Use "If-Modified-Since" to avoid retrieving consensus
9422 networkstatuses that we already have.
9423 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9424 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9425 we start knowing some directory caches.
9426 - When we receive a consensus from the future, warn about skew.
9427 - Improve skew reporting: try to give the user a better log message
9428 about how skewed they are, and how much this matters.
9429 - When we have a certificate for an authority, believe that
9430 certificate's claims about the authority's IP address.
9431 - New --quiet command-line option to suppress the default console log.
9432 Good in combination with --hash-password.
9433 - Authorities send back an X-Descriptor-Not-New header in response to
9434 an accepted-but-discarded descriptor upload. Partially implements
9436 - Make the log message for "tls error. breaking." more useful.
9437 - Better log messages about certificate downloads, to attempt to
9438 track down the second incarnation of bug 546.
9440 o Minor features (bridges):
9441 - If bridge users set UpdateBridgesFromAuthority, but the digest
9442 they ask for is a 404 from the bridge authority, they now fall
9443 back to trying the bridge directly.
9444 - Bridges now use begin_dir to publish their server descriptor to
9445 the bridge authority, even when they haven't set TunnelDirConns.
9447 o Minor features (controller):
9448 - When reporting clock skew, and we know that the clock is _at least
9449 as skewed_ as some value, but we don't know the actual value,
9450 report the value as a "minimum skew."
9453 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9454 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9458 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9459 on 0.2.0.x, suggested by Matt Edman.
9460 - Don't stop fetching descriptors when FetchUselessDescriptors is
9461 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9462 reported by tup and ioerror.
9463 - Better log message on vote from unknown authority.
9464 - Don't log "Launching 0 request for 0 router" message.
9466 o Minor bugfixes (memory leaks):
9467 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9469 - Stop leaking memory every time we load a v3 certificate. Bugfix
9470 on 0.2.0.1-alpha. Fixes bug 536.
9471 - Stop leaking a cached networkstatus on exit. Bugfix on
9473 - Stop leaking voter information every time we free a consensus.
9474 Bugfix on 0.2.0.3-alpha.
9475 - Stop leaking signed data every time we check a voter signature.
9476 Bugfix on 0.2.0.3-alpha.
9477 - Stop leaking a signature every time we fail to parse a consensus or
9478 a vote. Bugfix on 0.2.0.3-alpha.
9479 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9481 - Stop leaking conn->nickname every time we make a connection to a
9482 Tor relay without knowing its expected identity digest (e.g. when
9483 using bridges). Bugfix on 0.2.0.3-alpha.
9485 - Minor bugfixes (portability):
9486 - Run correctly on platforms where rlim_t is larger than unsigned
9487 long, and/or where the real limit for number of open files is
9488 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9489 particular, these may be needed for OS X 10.5.
9492 Changes in version 0.1.2.18 - 2007-10-28
9493 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9494 hidden service introduction that were causing huge delays, and a big
9495 bug that was causing some servers to disappear from the network status
9496 lists for a few hours each day.
9498 o Major bugfixes (crashes):
9499 - If a connection is shut down abruptly because of something that
9500 happened inside connection_flushed_some(), do not call
9501 connection_finished_flushing(). Should fix bug 451:
9502 "connection_stop_writing: Assertion conn->write_event failed"
9503 Bugfix on 0.1.2.7-alpha.
9504 - Fix possible segfaults in functions called from
9505 rend_process_relay_cell().
9507 o Major bugfixes (hidden services):
9508 - Hidden services were choosing introduction points uniquely by
9509 hexdigest, but when constructing the hidden service descriptor
9510 they merely wrote the (potentially ambiguous) nickname.
9511 - Clients now use the v2 intro format for hidden service
9512 connections: they specify their chosen rendezvous point by identity
9513 digest rather than by (potentially ambiguous) nickname. These
9514 changes could speed up hidden service connections dramatically.
9516 o Major bugfixes (other):
9517 - Stop publishing a new server descriptor just because we get a
9518 HUP signal. This led (in a roundabout way) to some servers getting
9519 dropped from the networkstatus lists for a few hours each day.
9520 - When looking for a circuit to cannibalize, consider family as well
9521 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9522 circuit cannibalization).
9523 - When a router wasn't listed in a new networkstatus, we were leaving
9524 the flags for that router alone -- meaning it remained Named,
9525 Running, etc -- even though absence from the networkstatus means
9526 that it shouldn't be considered to exist at all anymore. Now we
9527 clear all the flags for routers that fall out of the networkstatus
9528 consensus. Fixes bug 529.
9531 - Don't try to access (or alter) the state file when running
9532 --list-fingerprint or --verify-config or --hash-password. Resolves
9534 - When generating information telling us how to extend to a given
9535 router, do not try to include the nickname if it is
9536 absent. Resolves bug 467.
9537 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9538 a way to trigger this remotely.)
9539 - When sending a status event to the controller telling it that an
9540 OR address is reachable, set the port correctly. (Previously we
9541 were reporting the dir port.)
9542 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9543 command. Bugfix on 0.1.2.17.
9544 - When loading bandwidth history, do not believe any information in
9545 the future. Fixes bug 434.
9546 - When loading entry guard information, do not believe any information
9548 - When we have our clock set far in the future and generate an
9549 onion key, then re-set our clock to be correct, we should not stop
9550 the onion key from getting rotated.
9551 - On some platforms, accept() can return a broken address. Detect
9552 this more quietly, and deal accordingly. Fixes bug 483.
9553 - It's not actually an error to find a non-pending entry in the DNS
9554 cache when canceling a pending resolve. Don't log unless stuff
9555 is fishy. Resolves bug 463.
9556 - Don't reset trusted dir server list when we set a configuration
9557 option. Patch from Robert Hogan.
9558 - Don't try to create the datadir when running --verify-config or
9559 --hash-password. Resolves bug 540.
9562 Changes in version 0.2.0.9-alpha - 2007-10-24
9563 This ninth development snapshot switches clients to the new v3 directory
9564 system; allows servers to be listed in the network status even when they
9565 have the same nickname as a registered server; and fixes many other
9566 bugs including a big one that was causing some servers to disappear
9567 from the network status lists for a few hours each day.
9569 o Major features (directory system):
9570 - Clients now download v3 consensus networkstatus documents instead
9571 of v2 networkstatus documents. Clients and caches now base their
9572 opinions about routers on these consensus documents. Clients only
9573 download router descriptors listed in the consensus.
9574 - Authorities now list servers who have the same nickname as
9575 a different named server, but list them with a new flag,
9576 "Unnamed". Now we can list servers that happen to pick the same
9577 nickname as a server that registered two years ago and then
9578 disappeared. Partially implements proposal 122.
9579 - If the consensus lists a router as "Unnamed", the name is assigned
9580 to a different router: do not identify the router by that name.
9581 Partially implements proposal 122.
9582 - Authorities can now come to a consensus on which method to use to
9583 compute the consensus. This gives us forward compatibility.
9586 - Stop publishing a new server descriptor just because we HUP or
9587 when we find our DirPort to be reachable but won't actually publish
9588 it. New descriptors without any real changes are dropped by the
9589 authorities, and can screw up our "publish every 18 hours" schedule.
9591 - When a router wasn't listed in a new networkstatus, we were leaving
9592 the flags for that router alone -- meaning it remained Named,
9593 Running, etc -- even though absence from the networkstatus means
9594 that it shouldn't be considered to exist at all anymore. Now we
9595 clear all the flags for routers that fall out of the networkstatus
9596 consensus. Fixes bug 529; bugfix on 0.1.2.x.
9597 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
9598 extrainfo documents and then discard them immediately for not
9599 matching the latest router. Bugfix on 0.2.0.1-alpha.
9601 o Minor features (v3 directory protocol):
9602 - Allow tor-gencert to generate a new certificate without replacing
9604 - Allow certificates to include an address.
9605 - When we change our directory-cache settings, reschedule all voting
9606 and download operations.
9607 - Reattempt certificate downloads immediately on failure, as long as
9608 we haven't failed a threshold number of times yet.
9609 - Delay retrying consensus downloads while we're downloading
9610 certificates to verify the one we just got. Also, count getting a
9611 consensus that we already have (or one that isn't valid) as a failure,
9612 and count failing to get the certificates after 20 minutes as a
9614 - Build circuits and download descriptors even if our consensus is a
9615 little expired. (This feature will go away once authorities are
9618 o Minor features (router descriptor cache):
9619 - If we find a cached-routers file that's been sitting around for more
9620 than 28 days unmodified, then most likely it's a leftover from
9621 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
9623 - When we (as a cache) download a descriptor because it was listed
9624 in a consensus, remember when the consensus was supposed to expire,
9625 and don't expire the descriptor until then.
9627 o Minor features (performance):
9628 - Call routerlist_remove_old_routers() much less often. This should
9629 speed startup, especially on directory caches.
9630 - Don't try to launch new descriptor downloads quite so often when we
9631 already have enough directory information to build circuits.
9632 - Base64 decoding was actually showing up on our profile when parsing
9633 the initial descriptor file; switch to an in-process all-at-once
9634 implementation that's about 3.5x times faster than calling out to
9637 o Minor features (compilation):
9638 - Detect non-ASCII platforms (if any still exist) and refuse to
9639 build there: some of our code assumes that 'A' is 65 and so on.
9641 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
9642 - Make the "next period" votes into "current period" votes immediately
9643 after publishing the consensus; avoid a heisenbug that made them
9644 stick around indefinitely.
9645 - When we discard a vote as a duplicate, do not report this as
9647 - Treat missing v3 keys or certificates as an error when running as a
9648 v3 directory authority.
9649 - When we're configured to be a v3 authority, but we're only listed
9650 as a non-v3 authority in our DirServer line for ourself, correct
9652 - If an authority doesn't have a qualified hostname, just put
9653 its address in the vote. This fixes the problem where we referred to
9654 "moria on moria:9031."
9655 - Distinguish between detached signatures for the wrong period, and
9656 detached signatures for a divergent vote.
9657 - Fix a small memory leak when computing a consensus.
9658 - When there's no concensus, we were forming a vote every 30
9659 minutes, but writing the "valid-after" line in our vote based
9660 on our configured V3AuthVotingInterval: so unless the intervals
9661 matched up, we immediately rejected our own vote because it didn't
9662 start at the voting interval that caused us to construct a vote.
9664 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
9665 - Delete unverified-consensus when the real consensus is set.
9666 - Consider retrying a consensus networkstatus fetch immediately
9667 after one fails: don't wait 60 seconds to notice.
9668 - When fetching a consensus as a cache, wait until a newer consensus
9669 should exist before trying to replace the current one.
9670 - Use a more forgiving schedule for retrying failed consensus
9671 downloads than for other types.
9673 o Minor bugfixes (other directory issues):
9674 - Correct the implementation of "download votes by digest." Bugfix on
9676 - Authorities no longer send back "400 you're unreachable please fix
9677 it" errors to Tor servers that aren't online all the time. We're
9678 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
9680 o Minor bugfixes (controller):
9681 - Don't reset trusted dir server list when we set a configuration
9682 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
9683 - Respond to INT and TERM SIGNAL commands before we execute the
9684 signal, in case the signal shuts us down. We had a patch in
9685 0.1.2.1-alpha that tried to do this by queueing the response on
9686 the connection's buffer before shutting down, but that really
9687 isn't the same thing at all. Bug located by Matt Edman.
9689 o Minor bugfixes (misc):
9690 - Correctly check for bad options to the "PublishServerDescriptor"
9691 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
9692 - Stop leaking memory on failing case of base32_decode, and make
9693 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
9694 - Don't try to download extrainfo documents when we're trying to
9695 fetch enough directory info to build a circuit: having enough
9696 info should get priority. Bugfix on 0.2.0.x.
9697 - Don't complain that "your server has not managed to confirm that its
9698 ports are reachable" if we haven't been able to build any circuits
9699 yet. Bug found by spending four hours without a v3 consensus. Bugfix
9701 - Detect the reason for failing to mmap a descriptor file we just
9702 wrote, and give a more useful log message. Fixes bug 533. Bugfix
9705 o Code simplifications and refactoring:
9706 - Remove support for the old bw_accounting file: we've been storing
9707 bandwidth accounting information in the state file since
9708 0.1.2.5-alpha. This may result in bandwidth accounting errors
9709 if you try to upgrade from 0.1.1.x or earlier, or if you try to
9710 downgrade to 0.1.1.x or earlier.
9711 - New convenience code to locate a file within the DataDirectory.
9712 - Move non-authority functionality out of dirvote.c.
9713 - Refactor the arguments for router_pick_{directory_|trusteddir}server
9714 so that they all take the same named flags.
9717 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
9718 Unix users an easy way to script their Tor process (e.g. by
9719 adjusting bandwidth based on the time of the day).
9722 Changes in version 0.2.0.8-alpha - 2007-10-12
9723 This eighth development snapshot fixes a crash bug that's been bothering
9724 us since February 2007, lets bridge authorities store a list of bridge
9725 descriptors they've seen, gets v3 directory voting closer to working,
9726 starts caching v3 directory consensus documents on directory mirrors,
9727 and fixes a variety of smaller issues including some minor memory leaks.
9729 o Major features (router descriptor cache):
9730 - Store routers in a file called cached-descriptors instead of in
9731 cached-routers. Initialize cached-descriptors from cached-routers
9732 if the old format is around. The new format allows us to store
9733 annotations along with descriptors.
9734 - Use annotations to record the time we received each descriptor, its
9735 source, and its purpose.
9736 - Disable the SETROUTERPURPOSE controller command: it is now
9738 - Controllers should now specify cache=no or cache=yes when using
9739 the +POSTDESCRIPTOR command.
9740 - Bridge authorities now write bridge descriptors to disk, meaning
9741 we can export them to other programs and begin distributing them
9744 o Major features (directory authorities):
9745 - When a v3 authority is missing votes or signatures, it now tries
9747 - Directory authorities track weighted fractional uptime as well as
9748 weighted mean-time-between failures. WFU is suitable for deciding
9749 whether a node is "usually up", while MTBF is suitable for deciding
9750 whether a node is "likely to stay up." We need both, because
9751 "usually up" is a good requirement for guards, while "likely to
9752 stay up" is a good requirement for long-lived connections.
9754 o Major features (v3 directory system):
9755 - Caches now download v3 network status documents as needed,
9756 and download the descriptors listed in them.
9757 - All hosts now attempt to download and keep fresh v3 authority
9758 certificates, and re-attempt after failures.
9759 - More internal-consistency checks for vote parsing.
9761 o Major bugfixes (crashes):
9762 - If a connection is shut down abruptly because of something that
9763 happened inside connection_flushed_some(), do not call
9764 connection_finished_flushing(). Should fix bug 451. Bugfix on
9767 o Major bugfixes (performance):
9768 - Fix really bad O(n^2) performance when parsing a long list of
9769 routers: Instead of searching the entire list for an "extra-info "
9770 string which usually wasn't there, once for every routerinfo
9771 we read, just scan lines forward until we find one we like.
9773 - When we add data to a write buffer in response to the data on that
9774 write buffer getting low because of a flush, do not consider the
9775 newly added data as a candidate for immediate flushing, but rather
9776 make it wait until the next round of writing. Otherwise, we flush
9777 and refill recursively, and a single greedy TLS connection can
9778 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
9780 o Minor features (v3 authority system):
9781 - Add more ways for tools to download the votes that lead to the
9783 - Send a 503 when low on bandwidth and a vote, consensus, or
9784 certificate is requested.
9785 - If-modified-since is now implemented properly for all kinds of
9786 certificate requests.
9788 o Minor bugfixes (network statuses):
9789 - Tweak the implementation of proposal 109 slightly: allow at most
9790 two Tor servers on the same IP address, except if it's the location
9791 of a directory authority, in which case allow five. Bugfix on
9794 o Minor bugfixes (controller):
9795 - When sending a status event to the controller telling it that an
9796 OR address is reachable, set the port correctly. (Previously we
9797 were reporting the dir port.) Bugfix on 0.1.2.x.
9799 o Minor bugfixes (v3 directory system):
9800 - Fix logic to look up a cert by its signing key digest. Bugfix on
9802 - Only change the reply to a vote to "OK" if it's not already
9803 set. This gets rid of annoying "400 OK" log messages, which may
9804 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
9805 - When we get a valid consensus, recompute the voting schedule.
9806 - Base the valid-after time of a vote on the consensus voting
9807 schedule, not on our preferred schedule.
9808 - Make the return values and messages from signature uploads and
9809 downloads more sensible.
9810 - Fix a memory leak when serving votes and consensus documents, and
9811 another when serving certificates.
9813 o Minor bugfixes (performance):
9814 - Use a slightly simpler string hashing algorithm (copying Python's
9815 instead of Java's) and optimize our digest hashing algorithm to take
9816 advantage of 64-bit platforms and to remove some possibly-costly
9818 - Fix a minor memory leak whenever we parse guards from our state
9819 file. Bugfix on 0.2.0.7-alpha.
9820 - Fix a minor memory leak whenever we write out a file. Bugfix on
9822 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9823 command. Bugfix on 0.2.0.5-alpha.
9825 o Minor bugfixes (portability):
9826 - On some platforms, accept() can return a broken address. Detect
9827 this more quietly, and deal accordingly. Fixes bug 483.
9828 - Stop calling tor_strlower() on uninitialized memory in some cases.
9829 Bugfix in 0.2.0.7-alpha.
9831 o Minor bugfixes (usability):
9832 - Treat some 403 responses from directory servers as INFO rather than
9833 WARN-severity events.
9834 - It's not actually an error to find a non-pending entry in the DNS
9835 cache when canceling a pending resolve. Don't log unless stuff is
9836 fishy. Resolves bug 463.
9838 o Minor bugfixes (anonymity):
9839 - Never report that we've used more bandwidth than we're willing to
9840 relay: it leaks how much non-relay traffic we're using. Resolves
9842 - When looking for a circuit to cannibalize, consider family as well
9843 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9844 circuit cannibalization).
9846 o Code simplifications and refactoring:
9847 - Make a bunch of functions static. Remove some dead code.
9848 - Pull out about a third of the really big routerlist.c; put it in a
9849 new module, networkstatus.c.
9850 - Merge the extra fields in local_routerstatus_t back into
9851 routerstatus_t: we used to need one routerstatus_t for each
9852 authority's opinion, plus a local_routerstatus_t for the locally
9853 computed consensus opinion. To save space, we put the locally
9854 modified fields into local_routerstatus_t, and only the common
9855 stuff into routerstatus_t. But once v3 directories are in use,
9856 clients and caches will no longer need to hold authority opinions;
9857 thus, the rationale for keeping the types separate is now gone.
9858 - Make the code used to reschedule and reattempt downloads more
9860 - Turn all 'Are we a directory server/mirror?' logic into a call to
9862 - Remove the code to generate the oldest (v1) directory format.
9863 The code has been disabled since 0.2.0.5-alpha.
9866 Changes in version 0.2.0.7-alpha - 2007-09-21
9867 This seventh development snapshot makes bridges work again, makes bridge
9868 authorities work for the first time, fixes two huge performance flaws
9869 in hidden services, and fixes a variety of minor issues.
9871 o New directory authorities:
9872 - Set up moria1 and tor26 as the first v3 directory authorities. See
9873 doc/spec/dir-spec.txt for details on the new directory design.
9875 o Major bugfixes (crashes):
9876 - Fix possible segfaults in functions called from
9877 rend_process_relay_cell(). Bugfix on 0.1.2.x.
9879 o Major bugfixes (bridges):
9880 - Fix a bug that made servers send a "404 Not found" in response to
9881 attempts to fetch their server descriptor. This caused Tor servers
9882 to take many minutes to establish reachability for their DirPort,
9883 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
9884 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
9885 users configure that and specify a bridge with an identity
9886 fingerprint, now they will lookup the bridge descriptor at the
9887 default bridge authority via a one-hop tunnel, but once circuits
9888 are established they will switch to a three-hop tunnel for later
9889 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
9891 o Major bugfixes (hidden services):
9892 - Hidden services were choosing introduction points uniquely by
9893 hexdigest, but when constructing the hidden service descriptor
9894 they merely wrote the (potentially ambiguous) nickname.
9895 - Clients now use the v2 intro format for hidden service
9896 connections: they specify their chosen rendezvous point by identity
9897 digest rather than by (potentially ambiguous) nickname. Both
9898 are bugfixes on 0.1.2.x, and they could speed up hidden service
9899 connections dramatically. Thanks to Karsten Loesing.
9901 o Minor features (security):
9902 - As a client, do not believe any server that tells us that an
9903 address maps to an internal address space.
9904 - Make it possible to enable HashedControlPassword and
9905 CookieAuthentication at the same time.
9907 o Minor features (guard nodes):
9908 - Tag every guard node in our state file with the version that
9909 we believe added it, or with our own version if we add it. This way,
9910 if a user temporarily runs an old version of Tor and then switches
9911 back to a new one, she doesn't automatically lose her guards.
9913 o Minor features (speed):
9914 - When implementing AES counter mode, update only the portions of the
9915 counter buffer that need to change, and don't keep separate
9916 network-order and host-order counters when they are the same (i.e.,
9917 on big-endian hosts.)
9919 o Minor features (controller):
9920 - Accept LF instead of CRLF on controller, since some software has a
9921 hard time generating real Internet newlines.
9922 - Add GETINFO values for the server status events
9923 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
9927 - Routers no longer include bandwidth-history lines in their
9928 descriptors; this information is already available in extra-info
9929 documents, and including it in router descriptors took up 60%
9930 (!) of compressed router descriptor downloads. Completes
9931 implementation of proposal 104.
9932 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
9933 and TorControl.py, as they use the old v0 controller protocol,
9934 and are obsoleted by TorFlow anyway.
9935 - Drop support for v1 rendezvous descriptors, since we never used
9936 them anyway, and the code has probably rotted by now. Based on
9937 patch from Karsten Loesing.
9938 - On OSX, stop warning the user that kqueue support in libevent is
9939 "experimental", since it seems to have worked fine for ages.
9942 - When generating information telling us how to extend to a given
9943 router, do not try to include the nickname if it is absent. Fixes
9944 bug 467. Bugfix on 0.2.0.3-alpha.
9945 - Fix a user-triggerable (but not remotely-triggerable) segfault
9946 in expand_filename(). Bugfix on 0.1.2.x.
9947 - Fix a memory leak when freeing incomplete requests from DNSPort.
9948 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
9949 - Don't try to access (or alter) the state file when running
9950 --list-fingerprint or --verify-config or --hash-password. (Resolves
9951 bug 499.) Bugfix on 0.1.2.x.
9952 - Servers used to decline to publish their DirPort if their
9953 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
9954 were below a threshold. Now they only look at BandwidthRate and
9955 RelayBandwidthRate. Bugfix on 0.1.2.x.
9956 - Remove an optimization in the AES counter-mode code that assumed
9957 that the counter never exceeded 2^68. When the counter can be set
9958 arbitrarily as an IV (as it is by Karsten's new hidden services
9959 code), this assumption no longer holds. Bugfix on 0.1.2.x.
9960 - Resume listing "AUTHORITY" flag for authorities in network status.
9961 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
9963 o Code simplifications and refactoring:
9964 - Revamp file-writing logic so we don't need to have the entire
9965 contents of a file in memory at once before we write to disk. Tor,
9967 - Turn "descriptor store" into a full-fledged type.
9968 - Move all NT services code into a separate source file.
9969 - Unify all code that computes medians, percentile elements, etc.
9970 - Get rid of a needless malloc when parsing address policies.
9973 Changes in version 0.1.2.17 - 2007-08-30
9974 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
9975 X bundles. Vidalia 0.0.14 makes authentication required for the
9976 ControlPort in the default configuration, which addresses important
9977 security risks. Everybody who uses Vidalia (or another controller)
9980 In addition, this Tor update fixes major load balancing problems with
9981 path selection, which should speed things up a lot once many people
9984 o Major bugfixes (security):
9985 - We removed support for the old (v0) control protocol. It has been
9986 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
9987 become more of a headache than it's worth.
9989 o Major bugfixes (load balancing):
9990 - When choosing nodes for non-guard positions, weight guards
9991 proportionally less, since they already have enough load. Patch
9993 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9994 will allow fast Tor servers to get more attention.
9995 - When we're upgrading from an old Tor version, forget our current
9996 guards and pick new ones according to the new weightings. These
9997 three load balancing patches could raise effective network capacity
9998 by a factor of four. Thanks to Mike Perry for measurements.
10000 o Major bugfixes (stream expiration):
10001 - Expire not-yet-successful application streams in all cases if
10002 they've been around longer than SocksTimeout. Right now there are
10003 some cases where the stream will live forever, demanding a new
10004 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10006 o Minor features (controller):
10007 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10008 is valid before any authentication has been received. It tells
10009 a controller what kind of authentication is expected, and what
10010 protocol is spoken. Implements proposal 119.
10012 o Minor bugfixes (performance):
10013 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10014 greatly speeding up loading cached-routers from disk on startup.
10015 - Disable sentinel-based debugging for buffer code: we squashed all
10016 the bugs that this was supposed to detect a long time ago, and now
10017 its only effect is to change our buffer sizes from nice powers of
10018 two (which platform mallocs tend to like) to values slightly over
10019 powers of two (which make some platform mallocs sad).
10021 o Minor bugfixes (misc):
10022 - If exit bandwidth ever exceeds one third of total bandwidth, then
10023 use the correct formula to weight exit nodes when choosing paths.
10024 Based on patch from Mike Perry.
10025 - Choose perfectly fairly among routers when choosing by bandwidth and
10026 weighting by fraction of bandwidth provided by exits. Previously, we
10027 would choose with only approximate fairness, and correct ourselves
10028 if we ran off the end of the list.
10029 - If we require CookieAuthentication but we fail to write the
10030 cookie file, we would warn but not exit, and end up in a state
10031 where no controller could authenticate. Now we exit.
10032 - If we require CookieAuthentication, stop generating a new cookie
10033 every time we change any piece of our config.
10034 - Refuse to start with certain directory authority keys, and
10035 encourage people using them to stop.
10036 - Terminate multi-line control events properly. Original patch
10038 - Fix a minor memory leak when we fail to find enough suitable
10039 servers to choose a circuit.
10040 - Stop leaking part of the descriptor when we run into a particularly
10041 unparseable piece of it.
10044 Changes in version 0.2.0.6-alpha - 2007-08-26
10045 This sixth development snapshot features a new Vidalia version in the
10046 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10047 the ControlPort in the default configuration, which addresses important
10050 In addition, this snapshot fixes major load balancing problems
10051 with path selection, which should speed things up a lot once many
10052 people have upgraded. The directory authorities also use a new
10053 mean-time-between-failure approach to tracking which servers are stable,
10054 rather than just looking at the most recent uptime.
10056 o New directory authorities:
10057 - Set up Tonga as the default bridge directory authority.
10060 - Directory authorities now track servers by weighted
10061 mean-times-between-failures. When we have 4 or more days of data,
10062 use measured MTBF rather than declared uptime to decide whether
10063 to call a router Stable. Implements proposal 108.
10065 o Major bugfixes (load balancing):
10066 - When choosing nodes for non-guard positions, weight guards
10067 proportionally less, since they already have enough load. Patch
10069 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10070 will allow fast Tor servers to get more attention.
10071 - When we're upgrading from an old Tor version, forget our current
10072 guards and pick new ones according to the new weightings. These
10073 three load balancing patches could raise effective network capacity
10074 by a factor of four. Thanks to Mike Perry for measurements.
10076 o Major bugfixes (descriptor parsing):
10077 - Handle unexpected whitespace better in malformed descriptors. Bug
10078 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10081 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10082 GETINFO for Torstat to use until it can switch to using extrainfos.
10083 - Optionally (if built with -DEXPORTMALLINFO) export the output
10084 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10088 - Do not intermix bridge routers with controller-added
10089 routers. (Bugfix on 0.2.0.x)
10090 - Do not fail with an assert when accept() returns an unexpected
10091 address family. Addresses but does not wholly fix bug 483. (Bugfix
10093 - Let directory authorities startup even when they can't generate
10094 a descriptor immediately, e.g. because they don't know their
10096 - Stop putting the authentication cookie in a file called "0"
10097 in your working directory if you don't specify anything for the
10098 new CookieAuthFile option. Reported by Matt Edman.
10099 - Make it possible to read the PROTOCOLINFO response in a way that
10100 conforms to our control-spec. Reported by Matt Edman.
10101 - Fix a minor memory leak when we fail to find enough suitable
10102 servers to choose a circuit. Bugfix on 0.1.2.x.
10103 - Stop leaking part of the descriptor when we run into a particularly
10104 unparseable piece of it. Bugfix on 0.1.2.x.
10105 - Unmap the extrainfo cache file on exit.
10108 Changes in version 0.2.0.5-alpha - 2007-08-19
10109 This fifth development snapshot fixes compilation on Windows again;
10110 fixes an obnoxious client-side bug that slowed things down and put
10111 extra load on the network; gets us closer to using the v3 directory
10112 voting scheme; makes it easier for Tor controllers to use cookie-based
10113 authentication; and fixes a variety of other bugs.
10115 o Removed features:
10116 - Version 1 directories are no longer generated in full. Instead,
10117 authorities generate and serve "stub" v1 directories that list
10118 no servers. This will stop Tor versions 0.1.0.x and earlier from
10119 working, but (for security reasons) nobody should be running those
10122 o Major bugfixes (compilation, 0.2.0.x):
10123 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10124 - Try to fix MSVC compilation: build correctly on platforms that do
10125 not define s6_addr16 or s6_addr32.
10126 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10129 o Major bugfixes (stream expiration):
10130 - Expire not-yet-successful application streams in all cases if
10131 they've been around longer than SocksTimeout. Right now there are
10132 some cases where the stream will live forever, demanding a new
10133 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10134 reported by lodger.
10136 o Minor features (directory servers):
10137 - When somebody requests a list of statuses or servers, and we have
10138 none of those, return a 404 rather than an empty 200.
10140 o Minor features (directory voting):
10141 - Store v3 consensus status consensuses on disk, and reload them
10144 o Minor features (security):
10145 - Warn about unsafe ControlPort configurations.
10146 - Refuse to start with certain directory authority keys, and
10147 encourage people using them to stop.
10149 o Minor features (controller):
10150 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10151 is valid before any authentication has been received. It tells
10152 a controller what kind of authentication is expected, and what
10153 protocol is spoken. Implements proposal 119.
10154 - New config option CookieAuthFile to choose a new location for the
10155 cookie authentication file, and config option
10156 CookieAuthFileGroupReadable to make it group-readable.
10158 o Minor features (unit testing):
10159 - Add command-line arguments to unit-test executable so that we can
10160 invoke any chosen test from the command line rather than having
10161 to run the whole test suite at once; and so that we can turn on
10162 logging for the unit tests.
10164 o Minor bugfixes (on 0.1.2.x):
10165 - If we require CookieAuthentication but we fail to write the
10166 cookie file, we would warn but not exit, and end up in a state
10167 where no controller could authenticate. Now we exit.
10168 - If we require CookieAuthentication, stop generating a new cookie
10169 every time we change any piece of our config.
10170 - When loading bandwidth history, do not believe any information in
10171 the future. Fixes bug 434.
10172 - When loading entry guard information, do not believe any information
10174 - When we have our clock set far in the future and generate an
10175 onion key, then re-set our clock to be correct, we should not stop
10176 the onion key from getting rotated.
10177 - Clean up torrc sample config file.
10178 - Do not automatically run configure from autogen.sh. This
10179 non-standard behavior tended to annoy people who have built other
10182 o Minor bugfixes (on 0.2.0.x):
10183 - Fix a bug with AutomapHostsOnResolve that would always cause
10184 the second request to fail. Bug reported by Kate. Bugfix on
10186 - Fix a bug in ADDRMAP controller replies that would sometimes
10187 try to print a NULL. Patch from tup.
10188 - Read v3 directory authority keys from the right location.
10189 - Numerous bugfixes to directory voting code.
10192 Changes in version 0.1.2.16 - 2007-08-01
10193 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10194 remote attacker in certain situations to rewrite the user's torrc
10195 configuration file. This can completely compromise anonymity of users
10196 in most configurations, including those running the Vidalia bundles,
10197 TorK, etc. Or worse.
10199 o Major security fixes:
10200 - Close immediately after missing authentication on control port;
10201 do not allow multiple authentication attempts.
10204 Changes in version 0.2.0.4-alpha - 2007-08-01
10205 This fourth development snapshot fixes a critical security vulnerability
10206 for most users, specifically those running Vidalia, TorK, etc. Everybody
10207 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10209 o Major security fixes:
10210 - Close immediately after missing authentication on control port;
10211 do not allow multiple authentication attempts.
10213 o Major bugfixes (compilation):
10214 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10217 o Minor features (performance):
10218 - Be even more aggressive about releasing RAM from small
10219 empty buffers. Thanks to our free-list code, this shouldn't be too
10220 performance-intensive.
10221 - Disable sentinel-based debugging for buffer code: we squashed all
10222 the bugs that this was supposed to detect a long time ago, and
10223 now its only effect is to change our buffer sizes from nice
10224 powers of two (which platform mallocs tend to like) to values
10225 slightly over powers of two (which make some platform mallocs sad).
10226 - Log malloc statistics from mallinfo() on platforms where it
10230 Changes in version 0.2.0.3-alpha - 2007-07-29
10231 This third development snapshot introduces new experimental
10232 blocking-resistance features and a preliminary version of the v3
10233 directory voting design, and includes many other smaller features
10237 - The first pieces of our "bridge" design for blocking-resistance
10238 are implemented. People can run bridge directory authorities;
10239 people can run bridges; and people can configure their Tor clients
10240 with a set of bridges to use as the first hop into the Tor network.
10241 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10243 - Create listener connections before we setuid to the configured
10244 User and Group. Now non-Windows users can choose port values
10245 under 1024, start Tor as root, and have Tor bind those ports
10246 before it changes to another UID. (Windows users could already
10248 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10249 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10250 on "vserver" accounts. (Patch from coderman.)
10251 - Be even more aggressive about separating local traffic from relayed
10252 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10254 o Major features (experimental):
10255 - First cut of code for "v3 dir voting": directory authorities will
10256 vote on a common network status document rather than each publishing
10257 their own opinion. This code needs more testing and more corner-case
10258 handling before it's ready for use.
10261 - Directory authorities now call routers Fast if their bandwidth is
10262 at least 100KB/s, and consider their bandwidth adequate to be a
10263 Guard if it is at least 250KB/s, no matter the medians. This fix
10264 complements proposal 107. [Bugfix on 0.1.2.x]
10265 - Directory authorities now never mark more than 3 servers per IP as
10266 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10268 - Minor change to organizationName and commonName generation
10269 procedures in TLS certificates during Tor handshakes, to invalidate
10270 some earlier censorware approaches. This is not a long-term
10271 solution, but applying it will give us a bit of time to look into
10272 the epidemiology of countermeasures as they spread.
10274 o Major bugfixes (directory):
10275 - Rewrite directory tokenization code to never run off the end of
10276 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10278 o Minor features (controller):
10279 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10280 match requests to applications. (Patch from Robert Hogan.)
10281 - Report address and port correctly on connections to DNSPort. (Patch
10282 from Robert Hogan.)
10283 - Add a RESOLVE command to launch hostname lookups. (Original patch
10284 from Robert Hogan.)
10285 - Add GETINFO status/enough-dir-info to let controllers tell whether
10286 Tor has downloaded sufficient directory information. (Patch
10288 - You can now use the ControlSocket option to tell Tor to listen for
10289 controller connections on Unix domain sockets on systems that
10290 support them. (Patch from Peter Palfrader.)
10291 - STREAM NEW events are generated for DNSPort requests and for
10292 tunneled directory connections. (Patch from Robert Hogan.)
10293 - New "GETINFO address-mappings/*" command to get address mappings
10294 with expiry information. "addr-mappings/*" is now deprecated.
10297 o Minor features (misc):
10298 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10300 - The tor-gencert tool for v3 directory authorities now creates all
10301 files as readable to the file creator only, and write-protects
10302 the authority identity key.
10303 - When dumping memory usage, list bytes used in buffer memory
10305 - When running with dmalloc, dump more stats on hup and on exit.
10306 - Directory authorities now fail quickly and (relatively) harmlessly
10307 if they generate a network status document that is somehow
10310 o Traffic load balancing improvements:
10311 - If exit bandwidth ever exceeds one third of total bandwidth, then
10312 use the correct formula to weight exit nodes when choosing paths.
10313 (Based on patch from Mike Perry.)
10314 - Choose perfectly fairly among routers when choosing by bandwidth and
10315 weighting by fraction of bandwidth provided by exits. Previously, we
10316 would choose with only approximate fairness, and correct ourselves
10317 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10319 o Performance improvements:
10320 - Be more aggressive with freeing buffer RAM or putting it on the
10322 - Use Critical Sections rather than Mutexes for synchronizing threads
10323 on win32; Mutexes are heavier-weight, and designed for synchronizing
10326 o Deprecated and removed features:
10327 - RedirectExits is now deprecated.
10328 - Stop allowing address masks that do not correspond to bit prefixes.
10329 We have warned about these for a really long time; now it's time
10330 to reject them. (Patch from croup.)
10332 o Minor bugfixes (directory):
10333 - Fix another crash bug related to extra-info caching. (Bug found by
10334 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10335 - Directories no longer return a "304 not modified" when they don't
10336 have the networkstatus the client asked for. Also fix a memory
10337 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10338 - We had accidentally labelled 0.1.2.x directory servers as not
10339 suitable for begin_dir requests, and had labelled no directory
10340 servers as suitable for uploading extra-info documents. [Bugfix
10343 o Minor bugfixes (dns):
10344 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10345 Hogan.) [Bugfix on 0.2.0.2-alpha]
10346 - Add DNSPort connections to the global connection list, so that we
10347 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10349 - Fix a dangling reference that could lead to a crash when DNSPort is
10350 changed or closed (Patch from Robert Hogan.) [Bugfix on
10353 o Minor bugfixes (controller):
10354 - Provide DNS expiry times in GMT, not in local time. For backward
10355 compatibility, ADDRMAP events only provide GMT expiry in an extended
10356 field. "GETINFO address-mappings" always does the right thing.
10357 - Use CRLF line endings properly in NS events.
10358 - Terminate multi-line control events properly. (Original patch
10359 from tup.) [Bugfix on 0.1.2.x-alpha]
10360 - Do not include spaces in SOURCE_ADDR fields in STREAM
10361 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10364 Changes in version 0.1.2.15 - 2007-07-17
10365 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10366 problems, fixes compilation on BSD, and fixes a variety of other
10367 bugs. Everybody should upgrade.
10369 o Major bugfixes (compilation):
10370 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10372 o Major bugfixes (crashes):
10373 - Try even harder not to dereference the first character after
10374 an mmap(). Reported by lodger.
10375 - Fix a crash bug in directory authorities when we re-number the
10376 routerlist while inserting a new router.
10377 - When the cached-routers file is an even multiple of the page size,
10378 don't run off the end and crash. (Fixes bug 455; based on idea
10380 - Fix eventdns.c behavior on Solaris: It is critical to include
10381 orconfig.h _before_ sys/types.h, so that we can get the expected
10382 definition of _FILE_OFFSET_BITS.
10384 o Major bugfixes (security):
10385 - Fix a possible buffer overrun when using BSD natd support. Bug
10387 - When sending destroy cells from a circuit's origin, don't include
10388 the reason for tearing down the circuit. The spec says we didn't,
10389 and now we actually don't. Reported by lodger.
10390 - Keep streamids from different exits on a circuit separate. This
10391 bug may have allowed other routers on a given circuit to inject
10392 cells into streams. Reported by lodger; fixes bug 446.
10393 - If there's a never-before-connected-to guard node in our list,
10394 never choose any guards past it. This way we don't expand our
10395 guard list unless we need to.
10397 o Minor bugfixes (guard nodes):
10398 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10399 don't get overused as guards.
10401 o Minor bugfixes (directory):
10402 - Correctly count the number of authorities that recommend each
10403 version. Previously, we were under-counting by 1.
10404 - Fix a potential crash bug when we load many server descriptors at
10405 once and some of them make others of them obsolete. Fixes bug 458.
10407 o Minor bugfixes (hidden services):
10408 - Stop tearing down the whole circuit when the user asks for a
10409 connection to a port that the hidden service didn't configure.
10412 o Minor bugfixes (misc):
10413 - On Windows, we were preventing other processes from reading
10414 cached-routers while Tor was running. Reported by janbar.
10415 - Fix a possible (but very unlikely) bug in picking routers by
10416 bandwidth. Add a log message to confirm that it is in fact
10417 unlikely. Patch from lodger.
10418 - Backport a couple of memory leak fixes.
10419 - Backport miscellaneous cosmetic bugfixes.
10422 Changes in version 0.2.0.2-alpha - 2007-06-02
10423 o Major bugfixes on 0.2.0.1-alpha:
10424 - Fix an assertion failure related to servers without extra-info digests.
10425 Resolves bugs 441 and 442.
10427 o Minor features (directory):
10428 - Support "If-Modified-Since" when answering HTTP requests for
10429 directories, running-routers documents, and network-status documents.
10430 (There's no need to support it for router descriptors, since those
10431 are downloaded by descriptor digest.)
10433 o Minor build issues:
10434 - Clear up some MIPSPro compiler warnings.
10435 - When building from a tarball on a machine that happens to have SVK
10436 installed, report the micro-revision as whatever version existed
10437 in the tarball, not as "x".
10440 Changes in version 0.2.0.1-alpha - 2007-06-01
10441 This early development snapshot provides new features for people running
10442 Tor as both a client and a server (check out the new RelayBandwidth
10443 config options); lets Tor run as a DNS proxy; and generally moves us
10444 forward on a lot of fronts.
10446 o Major features, server usability:
10447 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10448 a separate set of token buckets for relayed traffic. Right now
10449 relayed traffic is defined as answers to directory requests, and
10450 OR connections that don't have any local circuits on them.
10452 o Major features, client usability:
10453 - A client-side DNS proxy feature to replace the need for
10454 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10455 for DNS requests on port 9999, use the Tor network to resolve them
10456 anonymously, and send the reply back like a regular DNS server.
10457 The code still only implements a subset of DNS.
10458 - Make PreferTunneledDirConns and TunnelDirConns work even when
10459 we have no cached directory info. This means Tor clients can now
10460 do all of their connections protected by TLS.
10462 o Major features, performance and efficiency:
10463 - Directory authorities accept and serve "extra info" documents for
10464 routers. These documents contain fields from router descriptors
10465 that aren't usually needed, and that use a lot of excess
10466 bandwidth. Once these fields are removed from router descriptors,
10467 the bandwidth savings should be about 60%. [Partially implements
10469 - Servers upload extra-info documents to any authority that accepts
10470 them. Authorities (and caches that have been configured to download
10471 extra-info documents) download them as needed. [Partially implements
10473 - Change the way that Tor buffers data that it is waiting to write.
10474 Instead of queueing data cells in an enormous ring buffer for each
10475 client->OR or OR->OR connection, we now queue cells on a separate
10476 queue for each circuit. This lets us use less slack memory, and
10477 will eventually let us be smarter about prioritizing different kinds
10479 - Use memory pools to allocate cells with better speed and memory
10480 efficiency, especially on platforms where malloc() is inefficient.
10481 - Stop reading on edge connections when their corresponding circuit
10482 buffers are full; start again as the circuits empty out.
10484 o Major features, other:
10485 - Add an HSAuthorityRecordStats option that hidden service authorities
10486 can use to track statistics of overall hidden service usage without
10487 logging information that would be very useful to an attacker.
10488 - Start work implementing multi-level keys for directory authorities:
10489 Add a standalone tool to generate key certificates. (Proposal 103.)
10492 - Directory authorities now call routers Stable if they have an
10493 uptime of at least 30 days, even if that's not the median uptime
10494 in the network. Implements proposal 107, suggested by Kevin Bauer
10497 o Minor fixes (resource management):
10498 - Count the number of open sockets separately from the number
10499 of active connection_t objects. This will let us avoid underusing
10500 our allocated connection limit.
10501 - We no longer use socket pairs to link an edge connection to an
10502 anonymous directory connection or a DirPort test connection.
10503 Instead, we track the link internally and transfer the data
10504 in-process. This saves two sockets per "linked" connection (at the
10505 client and at the server), and avoids the nasty Windows socketpair()
10507 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10508 for every single inactive connection_t. Free items from the
10509 4k/16k-buffer free lists when they haven't been used for a while.
10511 o Minor features (build):
10512 - Make autoconf search for libevent, openssl, and zlib consistently.
10513 - Update deprecated macros in configure.in.
10514 - When warning about missing headers, tell the user to let us
10515 know if the compile succeeds anyway, so we can downgrade the
10517 - Include the current subversion revision as part of the version
10518 string: either fetch it directly if we're in an SVN checkout, do
10519 some magic to guess it if we're in an SVK checkout, or use
10520 the last-detected version if we're building from a .tar.gz.
10521 Use this version consistently in log messages.
10523 o Minor features (logging):
10524 - Always prepend "Bug: " to any log message about a bug.
10525 - Put a platform string (e.g. "Linux i686") in the startup log
10526 message, so when people paste just their logs, we know if it's
10527 OpenBSD or Windows or what.
10528 - When logging memory usage, break down memory used in buffers by
10531 o Minor features (directory system):
10532 - New config option V2AuthoritativeDirectory that all directory
10533 authorities should set. This will let future authorities choose
10534 not to serve V2 directory information.
10535 - Directory authorities allow multiple router descriptors and/or extra
10536 info documents to be uploaded in a single go. This will make
10537 implementing proposal 104 simpler.
10539 o Minor features (controller):
10540 - Add a new config option __DisablePredictedCircuits designed for
10541 use by the controller, when we don't want Tor to build any circuits
10543 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10544 so we can exit from the middle of the circuit.
10545 - Implement "getinfo status/circuit-established".
10546 - Implement "getinfo status/version/..." so a controller can tell
10547 whether the current version is recommended, and whether any versions
10548 are good, and how many authorities agree. (Patch from shibz.)
10550 o Minor features (hidden services):
10551 - Allow multiple HiddenServicePort directives with the same virtual
10552 port; when they occur, the user is sent round-robin to one
10553 of the target ports chosen at random. Partially fixes bug 393 by
10554 adding limited ad-hoc round-robining.
10556 o Minor features (other):
10558 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10559 resolve request for hosts matching a given pattern causes Tor to
10560 generate an internal virtual address mapping for that host. This
10561 allows DNSPort to work sensibly with hidden service users. By
10562 default, .exit and .onion addresses are remapped; the list of
10563 patterns can be reconfigured with AutomapHostsSuffixes.
10564 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10565 address. Thanks to the AutomapHostsOnResolve option, this is no
10566 longer a completely silly thing to do.
10567 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
10568 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
10569 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
10570 minus 1 byte: the actual maximum declared bandwidth.
10572 o Removed features:
10573 - Removed support for the old binary "version 0" controller protocol.
10574 This has been deprecated since 0.1.1, and warnings have been issued
10575 since 0.1.2. When we encounter a v0 control message, we now send
10576 back an error and close the connection.
10577 - Remove the old "dns worker" server DNS code: it hasn't been default
10578 since 0.1.2.2-alpha, and all the servers seem to be using the new
10581 o Minor bugfixes (portability):
10582 - Even though Windows is equally happy with / and \ as path separators,
10583 try to use \ consistently on Windows and / consistently on Unix: it
10584 makes the log messages nicer.
10585 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
10586 - Read resolv.conf files correctly on platforms where read() returns
10587 partial results on small file reads.
10589 o Minor bugfixes (directory):
10590 - Correctly enforce that elements of directory objects do not appear
10591 more often than they are allowed to appear.
10592 - When we are reporting the DirServer line we just parsed, we were
10593 logging the second stanza of the key fingerprint, not the first.
10595 o Minor bugfixes (logging):
10596 - When we hit an EOF on a log (probably because we're shutting down),
10597 don't try to remove the log from the list: just mark it as
10598 unusable. (Bulletproofs against bug 222.)
10600 o Minor bugfixes (other):
10601 - In the exitlist script, only consider the most recently published
10602 server descriptor for each server. Also, when the user requests
10603 a list of servers that _reject_ connections to a given address,
10604 explicitly exclude the IPs that also have servers that accept
10605 connections to that address. (Resolves bug 405.)
10606 - Stop allowing hibernating servers to be "stable" or "fast".
10607 - On Windows, we were preventing other processes from reading
10608 cached-routers while Tor was running. (Reported by janbar)
10609 - Make the NodeFamilies config option work. (Reported by
10610 lodger -- it has never actually worked, even though we added it
10612 - Check return values from pthread_mutex functions.
10613 - Don't save non-general-purpose router descriptors to the disk cache,
10614 because we have no way of remembering what their purpose was when
10616 - Add even more asserts to hunt down bug 417.
10617 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
10618 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
10619 Add a log message to confirm that it is in fact unlikely.
10621 o Minor bugfixes (controller):
10622 - Make 'getinfo fingerprint' return a 551 error if we're not a
10623 server, so we match what the control spec claims we do. Reported
10625 - Fix a typo in an error message when extendcircuit fails that
10626 caused us to not follow the \r\n-based delimiter protocol. Reported
10629 o Code simplifications and refactoring:
10630 - Stop passing around circuit_t and crypt_path_t pointers that are
10631 implicit in other procedure arguments.
10632 - Drop the old code to choke directory connections when the
10633 corresponding OR connections got full: thanks to the cell queue
10634 feature, OR conns don't get full any more.
10635 - Make dns_resolve() handle attaching connections to circuits
10636 properly, so the caller doesn't have to.
10637 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
10638 - Keep the connection array as a dynamic smartlist_t, rather than as
10639 a fixed-sized array. This is important, as the number of connections
10640 is becoming increasingly decoupled from the number of sockets.
10643 Changes in version 0.1.2.14 - 2007-05-25
10644 Tor 0.1.2.14 changes the addresses of two directory authorities (this
10645 change especially affects those who serve or use hidden services),
10646 and fixes several other crash- and security-related bugs.
10648 o Directory authority changes:
10649 - Two directory authorities (moria1 and moria2) just moved to new
10650 IP addresses. This change will particularly affect those who serve
10651 or use hidden services.
10653 o Major bugfixes (crashes):
10654 - If a directory server runs out of space in the connection table
10655 as it's processing a begin_dir request, it will free the exit stream
10656 but leave it attached to the circuit, leading to unpredictable
10657 behavior. (Reported by seeess, fixes bug 425.)
10658 - Fix a bug in dirserv_remove_invalid() that would cause authorities
10659 to corrupt memory under some really unlikely scenarios.
10660 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
10661 - Avoid segfaults when reading from mmaped descriptor file. (Reported
10664 o Major bugfixes (security):
10665 - When choosing an entry guard for a circuit, avoid using guards
10666 that are in the same family as the chosen exit -- not just guards
10667 that are exactly the chosen exit. (Reported by lodger.)
10669 o Major bugfixes (resource management):
10670 - If a directory authority is down, skip it when deciding where to get
10671 networkstatus objects or descriptors. Otherwise we keep asking
10672 every 10 seconds forever. Fixes bug 384.
10673 - Count it as a failure if we fetch a valid network-status but we
10674 don't want to keep it. Otherwise we'll keep fetching it and keep
10675 not wanting to keep it. Fixes part of bug 422.
10676 - If all of our dirservers have given us bad or no networkstatuses
10677 lately, then stop hammering them once per minute even when we
10678 think they're failed. Fixes another part of bug 422.
10681 - Actually set the purpose correctly for descriptors inserted with
10682 purpose=controller.
10683 - When we have k non-v2 authorities in our DirServer config,
10684 we ignored the last k authorities in the list when updating our
10686 - Correctly back-off from requesting router descriptors that we are
10687 having a hard time downloading.
10688 - Read resolv.conf files correctly on platforms where read() returns
10689 partial results on small file reads.
10690 - Don't rebuild the entire router store every time we get 32K of
10691 routers: rebuild it when the journal gets very large, or when
10692 the gaps in the store get very large.
10695 - When routers publish SVN revisions in their router descriptors,
10696 authorities now include those versions correctly in networkstatus
10698 - Warn when using a version of libevent before 1.3b to run a server on
10699 OSX or BSD: these versions interact badly with userspace threads.
10702 Changes in version 0.1.2.13 - 2007-04-24
10703 This release features some major anonymity fixes, such as safer path
10704 selection; better client performance; faster bootstrapping, better
10705 address detection, and better DNS support for servers; write limiting as
10706 well as read limiting to make servers easier to run; and a huge pile of
10707 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
10709 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
10710 of the Freenode IRC network, remembering his patience and vision for
10711 free speech on the Internet.
10714 - Fix a memory leak when we ask for "all" networkstatuses and we
10715 get one we don't recognize.
10716 - Add more asserts to hunt down bug 417.
10717 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
10720 Changes in version 0.1.2.12-rc - 2007-03-16
10722 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
10723 directory information requested inside Tor connections (i.e. via
10724 begin_dir cells). It only triggered when the same connection was
10725 serving other data at the same time. Reported by seeess.
10728 - When creating a circuit via the controller, send a 'launched'
10729 event when we're done, so we follow the spec better.
10732 Changes in version 0.1.2.11-rc - 2007-03-15
10733 o Minor bugfixes (controller), reported by daejees:
10734 - Correct the control spec to match how the code actually responds
10735 to 'getinfo addr-mappings/*'.
10736 - The control spec described a GUARDS event, but the code
10737 implemented a GUARD event. Standardize on GUARD, but let people
10738 ask for GUARDS too.
10741 Changes in version 0.1.2.10-rc - 2007-03-07
10742 o Major bugfixes (Windows):
10743 - Do not load the NT services library functions (which may not exist)
10744 just to detect if we're a service trying to shut down. Now we run
10745 on Win98 and friends again.
10747 o Minor bugfixes (other):
10748 - Clarify a couple of log messages.
10749 - Fix a misleading socks5 error number.
10752 Changes in version 0.1.2.9-rc - 2007-03-02
10753 o Major bugfixes (Windows):
10754 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
10755 of the usual GCC "%llu". This prevents a bug when saving 64-bit
10756 int configuration values: the high-order 32 bits would get
10757 truncated. In particular, we were being bitten by the default
10758 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
10759 and maybe also bug 397.)
10761 o Minor bugfixes (performance):
10762 - Use OpenSSL's AES implementation on platforms where it's faster.
10763 This could save us as much as 10% CPU usage.
10765 o Minor bugfixes (server):
10766 - Do not rotate onion key immediately after setting it for the first
10769 o Minor bugfixes (directory authorities):
10770 - Stop calling servers that have been hibernating for a long time
10771 "stable". Also, stop letting hibernating or obsolete servers affect
10772 uptime and bandwidth cutoffs.
10773 - Stop listing hibernating servers in the v1 directory.
10775 o Minor bugfixes (hidden services):
10776 - Upload hidden service descriptors slightly less often, to reduce
10777 load on authorities.
10779 o Minor bugfixes (other):
10780 - Fix an assert that could trigger if a controller quickly set then
10781 cleared EntryNodes. Bug found by Udo van den Heuvel.
10782 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
10784 - Fix a potential race condition in the rpm installer. Found by
10786 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
10787 of 2 as indicating that the server is completely bad; it sometimes
10788 means that the server is just bad for the request in question. (may fix
10789 the last of bug 326.)
10790 - Disable encrypted directory connections when we don't have a server
10791 descriptor for the destination. We'll get this working again in
10795 Changes in version 0.1.2.8-beta - 2007-02-26
10796 o Major bugfixes (crashes):
10797 - Stop crashing when the controller asks us to resetconf more than
10798 one config option at once. (Vidalia 0.0.11 does this.)
10799 - Fix a crash that happened on Win98 when we're given command-line
10800 arguments: don't try to load NT service functions from advapi32.dll
10801 except when we need them. (Bug introduced in 0.1.2.7-alpha;
10803 - Fix a longstanding obscure crash bug that could occur when
10804 we run out of DNS worker processes. (Resolves bug 390.)
10806 o Major bugfixes (hidden services):
10807 - Correctly detect whether hidden service descriptor downloads are
10808 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
10810 o Major bugfixes (accounting):
10811 - When we start during an accounting interval before it's time to wake
10812 up, remember to wake up at the correct time. (May fix bug 342.)
10814 o Minor bugfixes (controller):
10815 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
10816 clear the corresponding on_circuit variable, and remember later
10817 that we don't need to send a redundant CLOSED event. Resolves part
10819 - Report events where a resolve succeeded or where we got a socks
10820 protocol error correctly, rather than calling both of them
10822 - Change reported stream target addresses to IP consistently when
10823 we finally get the IP from an exit node.
10824 - Send log messages to the controller even if they happen to be very
10827 o Minor bugfixes (other):
10828 - Display correct results when reporting which versions are
10829 recommended, and how recommended they are. (Resolves bug 383.)
10830 - Improve our estimates for directory bandwidth to be less random:
10831 guess that an unrecognized directory will have the average bandwidth
10832 from all known directories, not that it will have the average
10833 bandwidth from those directories earlier than it on the list.
10834 - If we start a server with ClientOnly 1, then set ClientOnly to 0
10835 and hup, stop triggering an assert based on an empty onion_key.
10836 - On platforms with no working mmap() equivalent, don't warn the
10837 user when cached-routers doesn't exist.
10838 - Warn the user when mmap() [or its equivalent] fails for some reason
10839 other than file-not-found.
10840 - Don't warn the user when cached-routers.new doesn't exist: that's
10841 perfectly fine when starting up for the first time.
10842 - When EntryNodes are configured, rebuild the guard list to contain,
10843 in order: the EntryNodes that were guards before; the rest of the
10844 EntryNodes; the nodes that were guards before.
10845 - Mask out all signals in sub-threads; only the libevent signal
10846 handler should be processing them. This should prevent some crashes
10847 on some machines using pthreads. (Patch from coderman.)
10848 - Fix switched arguments on memset in the implementation of
10849 tor_munmap() for systems with no mmap() call.
10850 - When Tor receives a router descriptor that it asked for, but
10851 no longer wants (because it has received fresh networkstatuses
10852 in the meantime), do not warn the user. Cache the descriptor if
10853 we're a cache; drop it if we aren't.
10854 - Make earlier entry guards _really_ get retried when the network
10856 - On a malformed DNS reply, always give an error to the corresponding
10858 - Build with recent libevents on platforms that do not define the
10859 nonstandard types "u_int8_t" and friends.
10861 o Minor features (controller):
10862 - Warn the user when an application uses the obsolete binary v0
10863 control protocol. We're planning to remove support for it during
10864 the next development series, so it's good to give people some
10866 - Add STREAM_BW events to report per-entry-stream bandwidth
10867 use. (Patch from Robert Hogan.)
10868 - Rate-limit SIGNEWNYM signals in response to controllers that
10869 impolitely generate them for every single stream. (Patch from
10870 mwenge; closes bug 394.)
10871 - Make REMAP stream events have a SOURCE (cache or exit), and
10872 make them generated in every case where we get a successful
10873 connected or resolved cell.
10875 o Minor bugfixes (performance):
10876 - Call router_have_min_dir_info half as often. (This is showing up in
10877 some profiles, but not others.)
10878 - When using GCC, make log_debug never get called at all, and its
10879 arguments never get evaluated, when no debug logs are configured.
10880 (This is showing up in some profiles, but not others.)
10883 - Remove some never-implemented options. Mark PathlenCoinWeight as
10885 - Implement proposal 106: Stop requiring clients to have well-formed
10886 certificates; stop checking nicknames in certificates. (Clients
10887 have certificates so that they can look like Tor servers, but in
10888 the future we might want to allow them to look like regular TLS
10889 clients instead. Nicknames in certificates serve no purpose other
10890 than making our protocol easier to recognize on the wire.)
10891 - Revise messages on handshake failure again to be even more clear about
10892 which are incoming connections and which are outgoing.
10893 - Discard any v1 directory info that's over 1 month old (for
10894 directories) or over 1 week old (for running-routers lists).
10895 - Do not warn when individual nodes in the configuration's EntryNodes,
10896 ExitNodes, etc are down: warn only when all possible nodes
10897 are down. (Fixes bug 348.)
10898 - Always remove expired routers and networkstatus docs before checking
10899 whether we have enough information to build circuits. (Fixes
10901 - Put a lower-bound on MaxAdvertisedBandwidth.
10904 Changes in version 0.1.2.7-alpha - 2007-02-06
10905 o Major bugfixes (rate limiting):
10906 - Servers decline directory requests much more aggressively when
10907 they're low on bandwidth. Otherwise they end up queueing more and
10908 more directory responses, which can't be good for latency.
10909 - But never refuse directory requests from local addresses.
10910 - Fix a memory leak when sending a 503 response for a networkstatus
10912 - Be willing to read or write on local connections (e.g. controller
10913 connections) even when the global rate limiting buckets are empty.
10914 - If our system clock jumps back in time, don't publish a negative
10915 uptime in the descriptor. Also, don't let the global rate limiting
10916 buckets go absurdly negative.
10917 - Flush local controller connection buffers periodically as we're
10918 writing to them, so we avoid queueing 4+ megabytes of data before
10921 o Major bugfixes (NT services):
10922 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
10923 command-line flag so that admins can override the default by saying
10924 "tor --service install --user "SomeUser"". This will not affect
10925 existing installed services. Also, warn the user that the service
10926 will look for its configuration file in the service user's
10927 %appdata% directory. (We can't do the 'hardwire the user's appdata
10928 directory' trick any more, since we may not have read access to that
10931 o Major bugfixes (other):
10932 - Previously, we would cache up to 16 old networkstatus documents
10933 indefinitely, if they came from nontrusted authorities. Now we
10934 discard them if they are more than 10 days old.
10935 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
10937 - Detect and reject malformed DNS responses containing circular
10939 - If exits are rare enough that we're not marking exits as guards,
10940 ignore exit bandwidth when we're deciding the required bandwidth
10942 - When we're handling a directory connection tunneled over Tor,
10943 don't fill up internal memory buffers with all the data we want
10944 to tunnel; instead, only add it if the OR connection that will
10945 eventually receive it has some room for it. (This can lead to
10946 slowdowns in tunneled dir connections; a better solution will have
10947 to wait for 0.2.0.)
10949 o Minor bugfixes (dns):
10950 - Add some defensive programming to eventdns.c in an attempt to catch
10951 possible memory-stomping bugs.
10952 - Detect and reject DNS replies containing IPv4 or IPv6 records with
10953 an incorrect number of bytes. (Previously, we would ignore the
10955 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
10956 in the correct order, and doesn't crash.
10957 - Free memory held in recently-completed DNS lookup attempts on exit.
10958 This was not a memory leak, but may have been hiding memory leaks.
10959 - Handle TTL values correctly on reverse DNS lookups.
10960 - Treat failure to parse resolv.conf as an error.
10962 o Minor bugfixes (other):
10963 - Fix crash with "tor --list-fingerprint" (reported by seeess).
10964 - When computing clock skew from directory HTTP headers, consider what
10965 time it was when we finished asking for the directory, not what
10967 - Expire socks connections if they spend too long waiting for the
10968 handshake to finish. Previously we would let them sit around for
10969 days, if the connecting application didn't close them either.
10970 - And if the socks handshake hasn't started, don't send a
10971 "DNS resolve socks failed" handshake reply; just close it.
10972 - Stop using C functions that OpenBSD's linker doesn't like.
10973 - Don't launch requests for descriptors unless we have networkstatuses
10974 from at least half of the authorities. This delays the first
10975 download slightly under pathological circumstances, but can prevent
10976 us from downloading a bunch of descriptors we don't need.
10977 - Do not log IPs with TLS failures for incoming TLS
10978 connections. (Fixes bug 382.)
10979 - If the user asks to use invalid exit nodes, be willing to use
10981 - Stop using the reserved ac_cv namespace in our configure script.
10982 - Call stat() slightly less often; use fstat() when possible.
10983 - Refactor the way we handle pending circuits when an OR connection
10984 completes or fails, in an attempt to fix a rare crash bug.
10985 - Only rewrite a conn's address based on X-Forwarded-For: headers
10986 if it's a parseable public IP address; and stop adding extra quotes
10987 to the resulting address.
10990 - Weight directory requests by advertised bandwidth. Now we can
10991 let servers enable write limiting but still allow most clients to
10992 succeed at their directory requests. (We still ignore weights when
10993 choosing a directory authority; I hope this is a feature.)
10996 - Create a new file ReleaseNotes which was the old ChangeLog. The
10997 new ChangeLog file now includes the summaries for all development
10999 - Check for addresses with invalid characters at the exit as well
11000 as at the client, and warn less verbosely when they fail. You can
11001 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11002 - Adapt a patch from goodell to let the contrib/exitlist script
11003 take arguments rather than require direct editing.
11004 - Inform the server operator when we decide not to advertise a
11005 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11006 was confusing Zax, so now we're hopefully more helpful.
11007 - Bring us one step closer to being able to establish an encrypted
11008 directory tunnel without knowing a descriptor first. Still not
11009 ready yet. As part of the change, now assume we can use a
11010 create_fast cell if we don't know anything about a router.
11011 - Allow exit nodes to use nameservers running on ports other than 53.
11012 - Servers now cache reverse DNS replies.
11013 - Add an --ignore-missing-torrc command-line option so that we can
11014 get the "use sensible defaults if the configuration file doesn't
11015 exist" behavior even when specifying a torrc location on the command
11018 o Minor features (controller):
11019 - Track reasons for OR connection failure; make these reasons
11020 available via the controller interface. (Patch from Mike Perry.)
11021 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11022 can learn when clients are sending malformed hostnames to Tor.
11023 - Clean up documentation for controller status events.
11024 - Add a REMAP status to stream events to note that a stream's
11025 address has changed because of a cached address or a MapAddress
11029 Changes in version 0.1.2.6-alpha - 2007-01-09
11031 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11032 connection handles more than 4 gigs in either direction, we crash.
11033 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11034 advertised exit node, somebody might try to exit from us when
11035 we're bootstrapping and before we've built our descriptor yet.
11036 Refuse the connection rather than crashing.
11039 - Warn if we (as a server) find that we've resolved an address that we
11040 weren't planning to resolve.
11041 - Warn that using select() on any libevent version before 1.1 will be
11042 unnecessarily slow (even for select()).
11043 - Flush ERR-level controller status events just like we currently
11044 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11045 the controller from learning about current events.
11047 o Minor features (more controller status events):
11048 - Implement EXTERNAL_ADDRESS server status event so controllers can
11049 learn when our address changes.
11050 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11051 can learn when directories reject our descriptor.
11052 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11053 can learn when a client application is speaking a non-socks protocol
11055 - Implement DANGEROUS_SOCKS client status event so controllers
11056 can learn when a client application is leaking DNS addresses.
11057 - Implement BUG general status event so controllers can learn when
11058 Tor is unhappy about its internal invariants.
11059 - Implement CLOCK_SKEW general status event so controllers can learn
11060 when Tor thinks the system clock is set incorrectly.
11061 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11062 server status events so controllers can learn when their descriptors
11063 are accepted by a directory.
11064 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11065 server status events so controllers can learn about Tor's progress in
11066 deciding whether it's reachable from the outside.
11067 - Implement BAD_LIBEVENT general status event so controllers can learn
11068 when we have a version/method combination in libevent that needs to
11070 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11071 and DNS_USELESS server status events so controllers can learn
11072 about changes to DNS server status.
11074 o Minor features (directory):
11075 - Authorities no longer recommend exits as guards if this would shift
11076 too much load to the exit nodes.
11079 Changes in version 0.1.2.5-alpha - 2007-01-06
11081 - Enable write limiting as well as read limiting. Now we sacrifice
11082 capacity if we're pushing out lots of directory traffic, rather
11083 than overrunning the user's intended bandwidth limits.
11084 - Include TLS overhead when counting bandwidth usage; previously, we
11085 would count only the bytes sent over TLS, but not the bytes used
11087 - Support running the Tor service with a torrc not in the same
11088 directory as tor.exe and default to using the torrc located in
11089 the %appdata%\Tor\ of the user who installed the service. Patch
11091 - Servers now check for the case when common DNS requests are going to
11092 wildcarded addresses (i.e. all getting the same answer), and change
11093 their exit policy to reject *:* if it's happening.
11094 - Implement BEGIN_DIR cells, so we can connect to the directory
11095 server via TLS to do encrypted directory requests rather than
11096 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11097 config options if you like.
11099 o Minor features (config and docs):
11100 - Start using the state file to store bandwidth accounting data:
11101 the bw_accounting file is now obsolete. We'll keep generating it
11102 for a while for people who are still using 0.1.2.4-alpha.
11103 - Try to batch changes to the state file so that we do as few
11104 disk writes as possible while still storing important things in
11106 - The state file and the bw_accounting file get saved less often when
11107 the AvoidDiskWrites config option is set.
11108 - Make PIDFile work on Windows (untested).
11109 - Add internal descriptions for a bunch of configuration options:
11110 accessible via controller interface and in comments in saved
11112 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11113 NNTP by default, so this seems like a sensible addition.
11114 - Clients now reject hostnames with invalid characters. This should
11115 avoid some inadvertent info leaks. Add an option
11116 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11117 is running a private network with hosts called @, !, and #.
11118 - Add a maintainer script to tell us which options are missing
11119 documentation: "make check-docs".
11120 - Add a new address-spec.txt document to describe our special-case
11121 addresses: .exit, .onion, and .noconnnect.
11123 o Minor features (DNS):
11124 - Ongoing work on eventdns infrastructure: now it has dns server
11125 and ipv6 support. One day Tor will make use of it.
11126 - Add client-side caching for reverse DNS lookups.
11127 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11128 - When we change nameservers or IP addresses, reset and re-launch
11129 our tests for DNS hijacking.
11131 o Minor features (directory):
11132 - Authorities now specify server versions in networkstatus. This adds
11133 about 2% to the size of compressed networkstatus docs, and allows
11134 clients to tell which servers support BEGIN_DIR and which don't.
11135 The implementation is forward-compatible with a proposed future
11136 protocol version scheme not tied to Tor versions.
11137 - DirServer configuration lines now have an orport= option so
11138 clients can open encrypted tunnels to the authorities without
11139 having downloaded their descriptors yet. Enabled for moria1,
11140 moria2, tor26, and lefkada now in the default configuration.
11141 - Directory servers are more willing to send a 503 "busy" if they
11142 are near their write limit, especially for v1 directory requests.
11143 Now they can use their limited bandwidth for actual Tor traffic.
11144 - Clients track responses with status 503 from dirservers. After a
11145 dirserver has given us a 503, we try not to use it until an hour has
11146 gone by, or until we have no dirservers that haven't given us a 503.
11147 - When we get a 503 from a directory, and we're not a server, we don't
11148 count the failure against the total number of failures allowed
11149 for the thing we're trying to download.
11150 - Report X-Your-Address-Is correctly from tunneled directory
11151 connections; don't report X-Your-Address-Is when it's an internal
11152 address; and never believe reported remote addresses when they're
11154 - Protect against an unlikely DoS attack on directory servers.
11155 - Add a BadDirectory flag to network status docs so that authorities
11156 can (eventually) tell clients about caches they believe to be
11159 o Minor features (controller):
11160 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11161 - Reimplement GETINFO so that info/names stays in sync with the
11163 - Implement "GETINFO fingerprint".
11164 - Implement "SETEVENTS GUARD" so controllers can get updates on
11165 entry guard status as it changes.
11167 o Minor features (clean up obsolete pieces):
11168 - Remove some options that have been deprecated since at least
11169 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11170 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11171 to set log options.
11172 - We no longer look for identity and onion keys in "identity.key" and
11173 "onion.key" -- these were replaced by secret_id_key and
11174 secret_onion_key in 0.0.8pre1.
11175 - We no longer require unrecognized directory entries to be
11178 o Major bugfixes (security):
11179 - Stop sending the HttpProxyAuthenticator string to directory
11180 servers when directory connections are tunnelled through Tor.
11181 - Clients no longer store bandwidth history in the state file.
11182 - Do not log introduction points for hidden services if SafeLogging
11184 - When generating bandwidth history, round down to the nearest
11185 1k. When storing accounting data, round up to the nearest 1k.
11186 - When we're running as a server, remember when we last rotated onion
11187 keys, so that we will rotate keys once they're a week old even if
11188 we never stay up for a week ourselves.
11190 o Major bugfixes (other):
11191 - Fix a longstanding bug in eventdns that prevented the count of
11192 timed-out resolves from ever being reset. This bug caused us to
11193 give up on a nameserver the third time it timed out, and try it
11194 10 seconds later... and to give up on it every time it timed out
11196 - Take out the '5 second' timeout from the connection retry
11197 schedule. Now the first connect attempt will wait a full 10
11198 seconds before switching to a new circuit. Perhaps this will help
11199 a lot. Based on observations from Mike Perry.
11200 - Fix a bug on the Windows implementation of tor_mmap_file() that
11201 would prevent the cached-routers file from ever loading. Reported
11205 - Fix an assert failure when a directory authority sets
11206 AuthDirRejectUnlisted and then receives a descriptor from an
11207 unlisted router. Reported by seeess.
11208 - Avoid a double-free when parsing malformed DirServer lines.
11209 - Fix a bug when a BSD-style PF socket is first used. Patch from
11211 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11212 to resolve an address at a given exit node even when they ask for
11214 - Servers no longer ever list themselves in their "family" line,
11215 even if configured to do so. This makes it easier to configure
11216 family lists conveniently.
11217 - When running as a server, don't fall back to 127.0.0.1 when no
11218 nameservers are configured in /etc/resolv.conf; instead, make the
11219 user fix resolv.conf or specify nameservers explicitly. (Resolves
11221 - Stop accepting certain malformed ports in configured exit policies.
11222 - Don't re-write the fingerprint file every restart, unless it has
11224 - Stop warning when a single nameserver fails: only warn when _all_ of
11225 our nameservers have failed. Also, when we only have one nameserver,
11226 raise the threshold for deciding that the nameserver is dead.
11227 - Directory authorities now only decide that routers are reachable
11228 if their identity keys are as expected.
11229 - When the user uses bad syntax in the Log config line, stop
11230 suggesting other bad syntax as a replacement.
11231 - Correctly detect ipv6 DNS capability on OpenBSD.
11233 o Minor bugfixes (controller):
11234 - Report the circuit number correctly in STREAM CLOSED events. Bug
11235 reported by Mike Perry.
11236 - Do not report bizarre values for results of accounting GETINFOs
11237 when the last second's write or read exceeds the allotted bandwidth.
11238 - Report "unrecognized key" rather than an empty string when the
11239 controller tries to fetch a networkstatus that doesn't exist.
11242 Changes in version 0.1.1.26 - 2006-12-14
11243 o Security bugfixes:
11244 - Stop sending the HttpProxyAuthenticator string to directory
11245 servers when directory connections are tunnelled through Tor.
11246 - Clients no longer store bandwidth history in the state file.
11247 - Do not log introduction points for hidden services if SafeLogging
11251 - Fix an assert failure when a directory authority sets
11252 AuthDirRejectUnlisted and then receives a descriptor from an
11253 unlisted router (reported by seeess).
11256 Changes in version 0.1.2.4-alpha - 2006-12-03
11258 - Add support for using natd; this allows FreeBSDs earlier than
11259 5.1.2 to have ipfw send connections through Tor without using
11260 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11263 - Make all connections to addresses of the form ".noconnect"
11264 immediately get closed. This lets application/controller combos
11265 successfully test whether they're talking to the same Tor by
11266 watching for STREAM events.
11267 - Make cross.sh cross-compilation script work even when autogen.sh
11268 hasn't been run. (Patch from Michael Mohr.)
11269 - Statistics dumped by -USR2 now include a breakdown of public key
11270 operations, for profiling.
11273 - Fix a major leak when directory authorities parse their
11274 approved-routers list, a minor memory leak when we fail to pick
11275 an exit node, and a few rare leaks on errors.
11276 - Handle TransPort connections even when the server sends data before
11277 the client sends data. Previously, the connection would just hang
11278 until the client sent data. (Patch from tup based on patch from
11280 - Avoid assert failure when our cached-routers file is empty on
11284 - Don't log spurious warnings when we see a circuit close reason we
11285 don't recognize; it's probably just from a newer version of Tor.
11286 - Have directory authorities allow larger amounts of drift in uptime
11287 without replacing the server descriptor: previously, a server that
11288 restarted every 30 minutes could have 48 "interesting" descriptors
11290 - Start linking to the Tor specification and Tor reference manual
11291 correctly in the Windows installer.
11292 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11293 Tor/Privoxy we also uninstall Vidalia.
11294 - Resume building on Irix64, and fix a lot of warnings from its
11295 MIPSpro C compiler.
11296 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11297 when we're running as a client.
11300 Changes in version 0.1.1.25 - 2006-11-04
11302 - When a client asks us to resolve (rather than connect to)
11303 an address, and we have a cached answer, give them the cached
11304 answer. Previously, we would give them no answer at all.
11305 - We were building exactly the wrong circuits when we predict
11306 hidden service requirements, meaning Tor would have to build all
11307 its circuits on demand.
11308 - If none of our live entry guards have a high uptime, but we
11309 require a guard with a high uptime, try adding a new guard before
11310 we give up on the requirement. This patch should make long-lived
11311 connections more stable on average.
11312 - When testing reachability of our DirPort, don't launch new
11313 tests when there's already one in progress -- unreachable
11314 servers were stacking up dozens of testing streams.
11316 o Security bugfixes:
11317 - When the user sends a NEWNYM signal, clear the client-side DNS
11318 cache too. Otherwise we continue to act on previous information.
11321 - Avoid a memory corruption bug when creating a hash table for
11323 - Avoid possibility of controller-triggered crash when misusing
11324 certain commands from a v0 controller on platforms that do not
11325 handle printf("%s",NULL) gracefully.
11326 - Avoid infinite loop on unexpected controller input.
11327 - Don't log spurious warnings when we see a circuit close reason we
11328 don't recognize; it's probably just from a newer version of Tor.
11329 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11330 Tor/Privoxy we also uninstall Vidalia.
11333 Changes in version 0.1.2.3-alpha - 2006-10-29
11335 - Prepare for servers to publish descriptors less often: never
11336 discard a descriptor simply for being too old until either it is
11337 recommended by no authorities, or until we get a better one for
11338 the same router. Make caches consider retaining old recommended
11339 routers for even longer.
11340 - If most authorities set a BadExit flag for a server, clients
11341 don't think of it as a general-purpose exit. Clients only consider
11342 authorities that advertise themselves as listing bad exits.
11343 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11344 headers for content, so that we can work better in the presence of
11345 caching HTTP proxies.
11346 - Allow authorities to list nodes as bad exits by fingerprint or by
11349 o Minor features, controller:
11350 - Add a REASON field to CIRC events; for backward compatibility, this
11351 field is sent only to controllers that have enabled the extended
11352 event format. Also, add additional reason codes to explain why
11353 a given circuit has been destroyed or truncated. (Patches from
11355 - Add a REMOTE_REASON field to extended CIRC events to tell the
11356 controller about why a remote OR told us to close a circuit.
11357 - Stream events also now have REASON and REMOTE_REASON fields,
11358 working much like those for circuit events.
11359 - There's now a GETINFO ns/... field so that controllers can ask Tor
11360 about the current status of a router.
11361 - A new event type "NS" to inform a controller when our opinion of
11362 a router's status has changed.
11363 - Add a GETINFO events/names and GETINFO features/names so controllers
11364 can tell which events and features are supported.
11365 - A new CLEARDNSCACHE signal to allow controllers to clear the
11366 client-side DNS cache without expiring circuits.
11368 o Security bugfixes:
11369 - When the user sends a NEWNYM signal, clear the client-side DNS
11370 cache too. Otherwise we continue to act on previous information.
11373 - Avoid sending junk to controllers or segfaulting when a controller
11374 uses EVENT_NEW_DESC with verbose nicknames.
11375 - Stop triggering asserts if the controller tries to extend hidden
11376 service circuits (reported by mwenge).
11377 - Avoid infinite loop on unexpected controller input.
11378 - When the controller does a "GETINFO network-status", tell it
11379 about even those routers whose descriptors are very old, and use
11380 long nicknames where appropriate.
11381 - Change NT service functions to be loaded on demand. This lets us
11382 build with MinGW without breaking Tor for Windows 98 users.
11383 - Do DirPort reachability tests less often, since a single test
11384 chews through many circuits before giving up.
11385 - In the hidden service example in torrc.sample, stop recommending
11386 esoteric and discouraged hidden service options.
11387 - When stopping an NT service, wait up to 10 sec for it to actually
11388 stop. Patch from Matt Edman; resolves bug 295.
11389 - Fix handling of verbose nicknames with ORCONN controller events:
11390 make them show up exactly when requested, rather than exactly when
11392 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11393 printing a duplicate "$" in the keys we send (reported by mwenge).
11394 - Correctly set maximum connection limit on Cygwin. (This time
11396 - Try to detect Windows correctly when cross-compiling.
11397 - Detect the size of the routers file correctly even if it is
11398 corrupted (on systems without mmap) or not page-aligned (on systems
11399 with mmap). This bug was harmless.
11400 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11401 to open a stream fails; now we do in more cases. This should
11402 make clients able to find a good exit faster in some cases, since
11403 unhandleable requests will now get an error rather than timing out.
11404 - Resolve two memory leaks when rebuilding the on-disk router cache
11405 (reported by fookoowa).
11406 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11407 and reported by some Centos users.
11408 - Controller signals now work on non-Unix platforms that don't define
11409 SIGUSR1 and SIGUSR2 the way we expect.
11410 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11411 values before failing, and always enables eventdns.
11412 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11413 Try to fix this in configure.in by checking for most functions
11414 before we check for libevent.
11417 Changes in version 0.1.2.2-alpha - 2006-10-07
11419 - Make our async eventdns library on-by-default for Tor servers,
11420 and plan to deprecate the separate dnsworker threads.
11421 - Add server-side support for "reverse" DNS lookups (using PTR
11422 records so clients can determine the canonical hostname for a given
11423 IPv4 address). Only supported by servers using eventdns; servers
11424 now announce in their descriptors whether they support eventdns.
11425 - Specify and implement client-side SOCKS5 interface for reverse DNS
11426 lookups (see doc/socks-extensions.txt).
11427 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11428 connect to directory servers through Tor. Previously, clients needed
11429 to find Tor exits to make private connections to directory servers.
11430 - Avoid choosing Exit nodes for entry or middle hops when the
11431 total bandwidth available from non-Exit nodes is much higher than
11432 the total bandwidth available from Exit nodes.
11433 - Workaround for name servers (like Earthlink's) that hijack failing
11434 DNS requests and replace the no-such-server answer with a "helpful"
11435 redirect to an advertising-driven search portal. Also work around
11436 DNS hijackers who "helpfully" decline to hijack known-invalid
11437 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11438 lets you turn it off.
11439 - Send out a burst of long-range padding cells once we've established
11440 that we're reachable. Spread them over 4 circuits, so hopefully
11441 a few will be fast. This exercises our bandwidth and bootstraps
11442 us into the directory more quickly.
11444 o New/improved config options:
11445 - Add new config option "ResolvConf" to let the server operator
11446 choose an alternate resolve.conf file when using eventdns.
11447 - Add an "EnforceDistinctSubnets" option to control our "exclude
11448 servers on the same /16" behavior. It's still on by default; this
11449 is mostly for people who want to operate private test networks with
11450 all the machines on the same subnet.
11451 - If one of our entry guards is on the ExcludeNodes list, or the
11452 directory authorities don't think it's a good guard, treat it as
11453 if it were unlisted: stop using it as a guard, and throw it off
11454 the guards list if it stays that way for a long time.
11455 - Allow directory authorities to be marked separately as authorities
11456 for the v1 directory protocol, the v2 directory protocol, and
11457 as hidden service directories, to make it easier to retire old
11458 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11459 to continue being hidden service authorities too.
11460 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11462 o Minor features, controller:
11463 - Fix CIRC controller events so that controllers can learn the
11464 identity digests of non-Named servers used in circuit paths.
11465 - Let controllers ask for more useful identifiers for servers. Instead
11466 of learning identity digests for un-Named servers and nicknames
11467 for Named servers, the new identifiers include digest, nickname,
11468 and indication of Named status. Off by default; see control-spec.txt
11469 for more information.
11470 - Add a "getinfo address" controller command so it can display Tor's
11471 best guess to the user.
11472 - New controller event to alert the controller when our server
11473 descriptor has changed.
11474 - Give more meaningful errors on controller authentication failure.
11476 o Minor features, other:
11477 - When asked to resolve a hostname, don't use non-exit servers unless
11478 requested to do so. This allows servers with broken DNS to be
11479 useful to the network.
11480 - Divide eventdns log messages into warn and info messages.
11481 - Reserve the nickname "Unnamed" for routers that can't pick
11482 a hostname: any router can call itself Unnamed; directory
11483 authorities will never allocate Unnamed to any particular router;
11484 clients won't believe that any router is the canonical Unnamed.
11485 - Only include function names in log messages for info/debug messages.
11486 For notice/warn/err, the content of the message should be clear on
11487 its own, and printing the function name only confuses users.
11488 - Avoid some false positives during reachability testing: don't try
11489 to test via a server that's on the same /24 as us.
11490 - If we fail to build a circuit to an intended enclave, and it's
11491 not mandatory that we use that enclave, stop wanting it.
11492 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11493 OpenBSD. (We had previously disabled threads on these platforms
11494 because they didn't have working thread-safe resolver functions.)
11496 o Major bugfixes, anonymity/security:
11497 - If a client asked for a server by name, and there's a named server
11498 in our network-status but we don't have its descriptor yet, we
11499 could return an unnamed server instead.
11500 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11501 to be sent to a server's DNS resolver. This only affects NetBSD
11502 and other platforms that do not bounds-check tolower().
11503 - Reject (most) attempts to use Tor circuits with length one. (If
11504 many people start using Tor as a one-hop proxy, exit nodes become
11505 a more attractive target for compromise.)
11506 - Just because your DirPort is open doesn't mean people should be
11507 able to remotely teach you about hidden service descriptors. Now
11508 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11510 o Major bugfixes, other:
11511 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11512 - When a client asks the server to resolve (not connect to)
11513 an address, and it has a cached answer, give them the cached answer.
11514 Previously, the server would give them no answer at all.
11515 - Allow really slow clients to not hang up five minutes into their
11516 directory downloads (suggested by Adam J. Richter).
11517 - We were building exactly the wrong circuits when we anticipated
11518 hidden service requirements, meaning Tor would have to build all
11519 its circuits on demand.
11520 - Avoid crashing when we mmap a router cache file of size 0.
11521 - When testing reachability of our DirPort, don't launch new
11522 tests when there's already one in progress -- unreachable
11523 servers were stacking up dozens of testing streams.
11525 o Minor bugfixes, correctness:
11526 - If we're a directory mirror and we ask for "all" network status
11527 documents, we would discard status documents from authorities
11528 we don't recognize.
11529 - Avoid a memory corruption bug when creating a hash table for
11531 - Avoid controller-triggered crash when misusing certain commands
11532 from a v0 controller on platforms that do not handle
11533 printf("%s",NULL) gracefully.
11534 - Don't crash when a controller sends a third argument to an
11535 "extendcircuit" request.
11536 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11537 response; fix error code when "getinfo dir/status/" fails.
11538 - Avoid crash when telling controller stream-status and a stream
11540 - Patch from Adam Langley to fix assert() in eventdns.c.
11541 - Fix a debug log message in eventdns to say "X resolved to Y"
11542 instead of "X resolved to X".
11543 - Make eventdns give strings for DNS errors, not just error numbers.
11544 - Track unreachable entry guards correctly: don't conflate
11545 'unreachable by us right now' with 'listed as down by the directory
11546 authorities'. With the old code, if a guard was unreachable by
11547 us but listed as running, it would clog our guard list forever.
11548 - Behave correctly in case we ever have a network with more than
11549 2GB/s total advertised capacity.
11550 - Make TrackExitHosts case-insensitive, and fix the behavior of
11551 ".suffix" TrackExitHosts items to avoid matching in the middle of
11553 - Finally fix the openssl warnings from newer gccs that believe that
11554 ignoring a return value is okay, but casting a return value and
11555 then ignoring it is a sign of madness.
11556 - Prevent the contrib/exitlist script from printing the same
11557 result more than once.
11558 - Patch from Steve Hildrey: Generate network status correctly on
11559 non-versioning dirservers.
11560 - Don't listen to the X-Your-Address-Is hint if you did the lookup
11561 via Tor; otherwise you'll think you're the exit node's IP address.
11563 o Minor bugfixes, performance:
11564 - Two small performance improvements on parsing descriptors.
11565 - Major performance improvement on inserting descriptors: change
11566 algorithm from O(n^2) to O(n).
11567 - Make the common memory allocation path faster on machines where
11568 malloc(0) returns a pointer.
11569 - Start remembering X-Your-Address-Is directory hints even if you're
11570 a client, so you can become a server more smoothly.
11571 - Avoid duplicate entries on MyFamily line in server descriptor.
11573 o Packaging, features:
11574 - Remove architecture from OS X builds. The official builds are
11575 now universal binaries.
11576 - The Debian package now uses --verify-config when (re)starting,
11577 to distinguish configuration errors from other errors.
11578 - Update RPMs to require libevent 1.1b.
11580 o Packaging, bugfixes:
11581 - Patches so Tor builds with MinGW on Windows.
11582 - Patches so Tor might run on Cygwin again.
11583 - Resume building on non-gcc compilers and ancient gcc. Resume
11584 building with the -O0 compile flag. Resume building cleanly on
11586 - Run correctly on OS X platforms with case-sensitive filesystems.
11587 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
11588 - Add autoconf checks so Tor can build on Solaris x86 again.
11591 - Documented (and renamed) ServerDNSSearchDomains and
11592 ServerDNSResolvConfFile options.
11593 - Be clearer that the *ListenAddress directives can be repeated
11597 Changes in version 0.1.1.24 - 2006-09-29
11599 - Allow really slow clients to not hang up five minutes into their
11600 directory downloads (suggested by Adam J. Richter).
11601 - Fix major performance regression from 0.1.0.x: instead of checking
11602 whether we have enough directory information every time we want to
11603 do something, only check when the directory information has changed.
11604 This should improve client CPU usage by 25-50%.
11605 - Don't crash if, after a server has been running for a while,
11606 it can't resolve its hostname.
11609 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11610 - Don't crash when the controller receives a third argument to an
11611 "extendcircuit" request.
11612 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11613 response; fix error code when "getinfo dir/status/" fails.
11614 - Fix configure.in to not produce broken configure files with
11615 more recent versions of autoconf. Thanks to Clint for his auto*
11617 - Fix security bug on NetBSD that could allow someone to force
11618 uninitialized RAM to be sent to a server's DNS resolver. This
11619 only affects NetBSD and other platforms that do not bounds-check
11621 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
11622 methods: these are known to be buggy.
11623 - If we're a directory mirror and we ask for "all" network status
11624 documents, we would discard status documents from authorities
11625 we don't recognize.
11628 Changes in version 0.1.2.1-alpha - 2006-08-27
11630 - Add "eventdns" async dns library from Adam Langley, tweaked to
11631 build on OSX and Windows. Only enabled if you pass the
11632 --enable-eventdns argument to configure.
11633 - Allow servers with no hostname or IP address to learn their
11634 IP address by asking the directory authorities. This code only
11635 kicks in when you would normally have exited with a "no address"
11636 error. Nothing's authenticated, so use with care.
11637 - Rather than waiting a fixed amount of time between retrying
11638 application connections, we wait only 5 seconds for the first,
11639 10 seconds for the second, and 15 seconds for each retry after
11640 that. Hopefully this will improve the expected user experience.
11641 - Patch from Tup to add support for transparent AP connections:
11642 this basically bundles the functionality of trans-proxy-tor
11643 into the Tor mainline. Now hosts with compliant pf/netfilter
11644 implementations can redirect TCP connections straight to Tor
11645 without diverting through SOCKS. Needs docs.
11646 - Busy directory servers save lots of memory by spooling server
11647 descriptors, v1 directories, and v2 networkstatus docs to buffers
11648 as needed rather than en masse. Also mmap the cached-routers
11649 files, so we don't need to keep the whole thing in memory too.
11650 - Automatically avoid picking more than one node from the same
11651 /16 network when constructing a circuit.
11652 - Revise and clean up the torrc.sample that we ship with; add
11653 a section for BandwidthRate and BandwidthBurst.
11656 - Split circuit_t into origin_circuit_t and or_circuit_t, and
11657 split connection_t into edge, or, dir, control, and base structs.
11658 These will save quite a bit of memory on busy servers, and they'll
11659 also help us track down bugs in the code and bugs in the spec.
11660 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
11661 or later. Log when we are doing this, so we can diagnose it when
11662 it fails. (Also, recommend libevent 1.1b for kqueue and
11663 win32 methods; deprecate libevent 1.0b harder; make libevent
11664 recommendation system saner.)
11665 - Start being able to build universal binaries on OS X (thanks
11667 - Export the default exit policy via the control port, so controllers
11668 don't need to guess what it is / will be later.
11669 - Add a man page entry for ProtocolWarnings.
11670 - Add TestVia config option to the man page.
11671 - Remove even more protocol-related warnings from Tor server logs,
11672 such as bad TLS handshakes and malformed begin cells.
11673 - Stop fetching descriptors if you're not a dir mirror and you
11674 haven't tried to establish any circuits lately. [This currently
11675 causes some dangerous behavior, because when you start up again
11676 you'll use your ancient server descriptors.]
11677 - New DirPort behavior: if you have your dirport set, you download
11678 descriptors aggressively like a directory mirror, whether or not
11679 your ORPort is set.
11680 - Get rid of the router_retry_connections notion. Now routers
11681 no longer try to rebuild long-term connections to directory
11682 authorities, and directory authorities no longer try to rebuild
11683 long-term connections to all servers. We still don't hang up
11684 connections in these two cases though -- we need to look at it
11685 more carefully to avoid flapping, and we likely need to wait til
11686 0.1.1.x is obsolete.
11687 - Drop compatibility with obsolete Tors that permit create cells
11688 to have the wrong circ_id_type.
11689 - Re-enable per-connection rate limiting. Get rid of the "OP
11690 bandwidth" concept. Lay groundwork for "bandwidth classes" --
11691 separate global buckets that apply depending on what sort of conn
11693 - Start publishing one minute or so after we find our ORPort
11694 to be reachable. This will help reduce the number of descriptors
11695 we have for ourselves floating around, since it's quite likely
11696 other things (e.g. DirPort) will change during that minute too.
11697 - Fork the v1 directory protocol into its own spec document,
11698 and mark dir-spec.txt as the currently correct (v2) spec.
11701 - When we find our DirPort to be reachable, publish a new descriptor
11702 so we'll tell the world (reported by pnx).
11703 - Publish a new descriptor after we hup/reload. This is important
11704 if our config has changed such that we'll want to start advertising
11705 our DirPort now, etc.
11706 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11707 - When we have a state file we cannot parse, tell the user and
11708 move it aside. Now we avoid situations where the user starts
11709 Tor in 1904, Tor writes a state file with that timestamp in it,
11710 the user fixes her clock, and Tor refuses to start.
11711 - Fix configure.in to not produce broken configure files with
11712 more recent versions of autoconf. Thanks to Clint for his auto*
11714 - "tor --verify-config" now exits with -1(255) or 0 depending on
11715 whether the config options are bad or good.
11716 - Resolve bug 321 when using dnsworkers: append a period to every
11717 address we resolve at the exit node, so that we do not accidentally
11718 pick up local addresses, and so that failing searches are retried
11719 in the resolver search domains. (This is already solved for
11720 eventdns.) (This breaks Blossom servers for now.)
11721 - If we are using an exit enclave and we can't connect, e.g. because
11722 its webserver is misconfigured to not listen on localhost, then
11723 back off and try connecting from somewhere else before we fail.
11726 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
11727 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
11728 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
11729 when the IP address is mapped through MapAddress to a hostname.
11730 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11731 useless IPv6 DNS resolves.
11732 - Patch suggested by Karsten Loesing: respond to SIGNAL command
11733 before we execute the signal, in case the signal shuts us down.
11734 - Clean up AllowInvalidNodes man page entry.
11735 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
11736 - Add more asserts to track down an assert error on a windows Tor
11737 server with connection_add being called with socket == -1.
11738 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
11739 - Fix misleading log messages: an entry guard that is "unlisted",
11740 as well as not known to be "down" (because we've never heard
11741 of it), is not therefore "up".
11742 - Remove code to special-case "-cvs" ending, since it has not
11743 actually mattered since 0.0.9.
11744 - Make our socks5 handling more robust to broken socks clients:
11745 throw out everything waiting on the buffer in between socks
11746 handshake phases, since they can't possibly (so the theory
11747 goes) have predicted what we plan to respond to them.
11750 Changes in version 0.1.1.23 - 2006-07-30
11752 - Fast Tor servers, especially exit nodes, were triggering asserts
11753 due to a bug in handling the list of pending DNS resolves. Some
11754 bugs still remain here; we're hunting them.
11755 - Entry guards could crash clients by sending unexpected input.
11756 - More fixes on reachability testing: if you find yourself reachable,
11757 then don't ever make any client requests (so you stop predicting
11758 circuits), then hup or have your clock jump, then later your IP
11759 changes, you won't think circuits are working, so you won't try to
11760 test reachability, so you won't publish.
11763 - Avoid a crash if the controller does a resetconf firewallports
11764 and then a setconf fascistfirewall=1.
11765 - Avoid an integer underflow when the dir authority decides whether
11766 a router is stable: we might wrongly label it stable, and compute
11767 a slightly wrong median stability, when a descriptor is published
11769 - Fix a place where we might trigger an assert if we can't build our
11770 own server descriptor yet.
11773 Changes in version 0.1.1.22 - 2006-07-05
11775 - Fix a big bug that was causing servers to not find themselves
11776 reachable if they changed IP addresses. Since only 0.1.1.22+
11777 servers can do reachability testing correctly, now we automatically
11778 make sure to test via one of these.
11779 - Fix to allow clients and mirrors to learn directory info from
11780 descriptor downloads that get cut off partway through.
11781 - Directory authorities had a bug in deciding if a newly published
11782 descriptor was novel enough to make everybody want a copy -- a few
11783 servers seem to be publishing new descriptors many times a minute.
11785 - Fix a rare bug that was causing some servers to complain about
11786 "closing wedged cpuworkers" and skip some circuit create requests.
11787 - Make the Exit flag in directory status documents actually work.
11790 Changes in version 0.1.1.21 - 2006-06-10
11791 o Crash and assert fixes from 0.1.1.20:
11792 - Fix a rare crash on Tor servers that have enabled hibernation.
11793 - Fix a seg fault on startup for Tor networks that use only one
11794 directory authority.
11795 - Fix an assert from a race condition that occurs on Tor servers
11796 while exiting, where various threads are trying to log that they're
11797 exiting, and delete the logs, at the same time.
11798 - Make our unit tests pass again on certain obscure platforms.
11801 - Add support for building SUSE RPM packages.
11802 - Speed up initial bootstrapping for clients: if we are making our
11803 first ever connection to any entry guard, then don't mark it down
11805 - When only one Tor server in the network is labelled as a guard,
11806 and we've already picked him, we would cycle endlessly picking him
11807 again, being unhappy about it, etc. Now we specifically exclude
11808 current guards when picking a new guard.
11809 - Servers send create cells more reliably after the TLS connection
11810 is established: we were sometimes forgetting to send half of them
11811 when we had more than one pending.
11812 - If we get a create cell that asks us to extend somewhere, but the
11813 Tor server there doesn't match the expected digest, we now send
11814 a destroy cell back, rather than silently doing nothing.
11815 - Make options->RedirectExit work again.
11816 - Make cookie authentication for the controller work again.
11817 - Stop being picky about unusual characters in the arguments to
11818 mapaddress. It's none of our business.
11819 - Add a new config option "TestVia" that lets you specify preferred
11820 middle hops to use for test circuits. Perhaps this will let me
11821 debug the reachability problems better.
11823 o Log / documentation fixes:
11824 - If we're a server and some peer has a broken TLS certificate, don't
11825 log about it unless ProtocolWarnings is set, i.e., we want to hear
11826 about protocol violations by others.
11827 - Fix spelling of VirtualAddrNetwork in man page.
11828 - Add a better explanation at the top of the autogenerated torrc file
11829 about what happened to our old torrc.
11832 Changes in version 0.1.1.20 - 2006-05-23
11834 - Downgrade a log severity where servers complain that they're
11836 - Avoid a compile warning on FreeBSD.
11837 - Remove string size limit on NEWDESC messages; solve bug 291.
11838 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
11839 more thoroughly when we're running on windows.
11842 Changes in version 0.1.1.19-rc - 2006-05-03
11844 - Regenerate our local descriptor if it's dirty and we try to use
11845 it locally (e.g. if it changes during reachability detection).
11846 - If we setconf our ORPort to 0, we continued to listen on the
11847 old ORPort and receive connections.
11848 - Avoid a second warning about machine/limits.h on Debian
11850 - Be willing to add our own routerinfo into the routerlist.
11851 Now authorities will include themselves in their directories
11852 and network-statuses.
11853 - Stop trying to upload rendezvous descriptors to every
11854 directory authority: only try the v1 authorities.
11855 - Servers no longer complain when they think they're not
11856 registered with the directory authorities. There were too many
11858 - Backport dist-rpm changes so rpms can be built without errors.
11861 - Implement an option, VirtualAddrMask, to set which addresses
11862 get handed out in response to mapaddress requests. This works
11863 around a bug in tsocks where 127.0.0.0/8 is never socksified.
11866 Changes in version 0.1.1.18-rc - 2006-04-10
11868 - Work harder to download live network-statuses from all the
11869 directory authorities we know about. Improve the threshold
11870 decision logic so we're more robust to edge cases.
11871 - When fetching rendezvous descriptors, we were willing to ask
11872 v2 authorities too, which would always return 404.
11875 - Stop listing down or invalid nodes in the v1 directory. This will
11876 reduce its bulk by about 1/3, and reduce load on directory
11878 - When deciding whether a router is Fast or Guard-worthy, consider
11879 his advertised BandwidthRate and not just the BandwidthCapacity.
11880 - No longer ship INSTALL and README files -- they are useless now.
11881 - Force rpmbuild to behave and honor target_cpu.
11882 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
11883 - Start to include translated versions of the tor-doc-*.html
11884 files, along with the screenshots. Still needs more work.
11885 - Start sending back 512 and 451 errors if mapaddress fails,
11886 rather than not sending anything back at all.
11887 - When we fail to bind or listen on an incoming or outgoing
11888 socket, we should close it before failing. otherwise we just
11889 leak it. (thanks to weasel for finding.)
11890 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
11891 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
11892 - Make NoPublish (even though deprecated) work again.
11893 - Fix a minor security flaw where a versioning auth dirserver
11894 could list a recommended version many times in a row to make
11895 clients more convinced that it's recommended.
11896 - Fix crash bug if there are two unregistered servers running
11897 with the same nickname, one of them is down, and you ask for
11898 them by nickname in your EntryNodes or ExitNodes. Also, try
11899 to pick the one that's running rather than an arbitrary one.
11900 - Fix an infinite loop we could hit if we go offline for too long.
11901 - Complain when we hit WSAENOBUFS on recv() or write() too.
11902 Perhaps this will help us hunt the bug.
11903 - If you're not a versioning dirserver, don't put the string
11904 "client-versions \nserver-versions \n" in your network-status.
11905 - Lower the minimum required number of file descriptors to 1000,
11906 so we can have some overhead for Valgrind on Linux, where the
11907 default ulimit -n is 1024.
11910 - Add tor.dizum.com as the fifth authoritative directory server.
11911 - Add a new config option FetchUselessDescriptors, off by default,
11912 for when you plan to run "exitlist" on your client and you want
11913 to know about even the non-running descriptors.
11916 Changes in version 0.1.1.17-rc - 2006-03-28
11918 - Clients and servers since 0.1.1.10-alpha have been expiring
11919 connections whenever they are idle for 5 minutes and they *do*
11920 have circuits on them. Oops. With this new version, clients will
11921 discard their previous entry guard choices and avoid choosing
11922 entry guards running these flawed versions.
11923 - Fix memory leak when uncompressing concatenated zlib streams. This
11924 was causing substantial leaks over time on Tor servers.
11925 - The v1 directory was including servers as much as 48 hours old,
11926 because that's how the new routerlist->routers works. Now only
11927 include them if they're 20 hours old or less.
11930 - Resume building on irix64, netbsd 2.0, etc.
11931 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
11933 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
11934 and it is confusing some users.
11935 - Mirrors stop caching the v1 directory so often.
11936 - Make the max number of old descriptors that a cache will hold
11937 rise with the number of directory authorities, so we can scale.
11938 - Change our win32 uname() hack to be more forgiving about what
11939 win32 versions it thinks it's found.
11942 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
11944 - When the controller's *setconf commands fail, collect an error
11945 message in a string and hand it back to the controller.
11946 - Make the v2 dir's "Fast" flag based on relative capacity, just
11947 like "Stable" is based on median uptime. Name everything in the
11948 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
11949 - Log server fingerprint on startup, so new server operators don't
11950 have to go hunting around their filesystem for it.
11951 - Return a robots.txt on our dirport to discourage google indexing.
11952 - Let the controller ask for GETINFO dir/status/foo so it can ask
11953 directly rather than connecting to the dir port. Only works when
11954 dirport is set for now.
11956 o New config options rather than constants in the code:
11957 - SocksTimeout: How long do we let a socks connection wait
11958 unattached before we fail it?
11959 - CircuitBuildTimeout: Cull non-open circuits that were born
11960 at least this many seconds ago.
11961 - CircuitIdleTimeout: Cull open clean circuits that were born
11962 at least this many seconds ago.
11965 Changes in version 0.1.1.16-rc - 2006-03-18
11966 o Bugfixes on 0.1.1.15-rc:
11967 - Fix assert when the controller asks to attachstream a connect-wait
11968 or resolve-wait stream.
11969 - Now do address rewriting when the controller asks us to attach
11970 to a particular circuit too. This will let Blossom specify
11971 "moria2.exit" without having to learn what moria2's IP address is.
11972 - Make the "tor --verify-config" command-line work again, so people
11973 can automatically check if their torrc will parse.
11974 - Authoritative dirservers no longer require an open connection from
11975 a server to consider him "reachable". We need this change because
11976 when we add new auth dirservers, old servers won't know not to
11978 - Let Tor build on Sun CC again.
11979 - Fix an off-by-one buffer size in dirserv.c that magically never
11980 hit our three authorities but broke sjmurdoch's own tor network.
11981 - If we as a directory mirror don't know of any v1 directory
11982 authorities, then don't try to cache any v1 directories.
11983 - Stop warning about unknown servers in our family when they are
11984 given as hex digests.
11985 - Stop complaining as quickly to the server operator that he
11986 hasn't registered his nickname/key binding.
11987 - Various cleanups so we can add new V2 Auth Dirservers.
11988 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
11989 reflect the updated flags in our v2 dir protocol.
11990 - Resume allowing non-printable characters for exit streams (both
11991 for connecting and for resolving). Now we tolerate applications
11992 that don't follow the RFCs. But continue to block malformed names
11995 o Bugfixes on 0.1.0.x:
11996 - Fix assert bug in close_logs(): when we close and delete logs,
11997 remove them all from the global "logfiles" list.
11998 - Fix minor integer overflow in calculating when we expect to use up
11999 our bandwidth allocation before hibernating.
12000 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12001 there are multiple SSLs installed with different versions.
12002 - When we try to be a server and Address is not explicitly set and
12003 our hostname resolves to a private IP address, try to use an
12004 interface address if it has a public address. Now Windows machines
12005 that think of themselves as localhost can work by default.
12008 - Let the controller ask for GETINFO dir/server/foo so it can ask
12009 directly rather than connecting to the dir port.
12010 - Let the controller tell us about certain router descriptors
12011 that it doesn't want Tor to use in circuits. Implement
12012 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12013 - New config option SafeSocks to reject all application connections
12014 using unsafe socks protocols. Defaults to off.
12017 Changes in version 0.1.1.15-rc - 2006-03-11
12018 o Bugfixes and cleanups:
12019 - When we're printing strings from the network, don't try to print
12020 non-printable characters. This protects us against shell escape
12021 sequence exploits, and also against attacks to fool humans into
12022 misreading their logs.
12023 - Fix a bug where Tor would fail to establish any connections if you
12024 left it off for 24 hours and then started it: we were happy with
12025 the obsolete network statuses, but they all referred to router
12026 descriptors that were too old to fetch, so we ended up with no
12027 valid router descriptors.
12028 - Fix a seg fault in the controller's "getinfo orconn-status"
12029 command while listing status on incoming handshaking connections.
12030 Introduce a status name "NEW" for these connections.
12031 - If we get a linelist or linelist_s config option from the torrc
12032 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12033 silently resetting it to its default.
12034 - Don't abandon entry guards until they've been down or gone for
12036 - Cleaner and quieter log messages.
12039 - New controller signal NEWNYM that makes new application requests
12040 use clean circuits.
12041 - Add a new circuit purpose 'controller' to let the controller ask
12042 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12043 controller command to let you specify the purpose if you're
12044 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12045 command to let you change a circuit's purpose after it's been
12047 - Accept "private:*" in routerdesc exit policies; not generated yet
12048 because older Tors do not understand it.
12049 - Add BSD-style contributed startup script "rc.subr" from Peter
12053 Changes in version 0.1.1.14-alpha - 2006-02-20
12054 o Bugfixes on 0.1.1.x:
12055 - Don't die if we ask for a stdout or stderr log (even implicitly)
12056 and we're set to RunAsDaemon -- just warn.
12057 - We still had a few bugs in the OR connection rotation code that
12058 caused directory servers to slowly aggregate connections to other
12059 fast Tor servers. This time for sure!
12060 - Make log entries on Win32 include the name of the function again.
12061 - We were treating a pair of exit policies if they were equal even
12062 if one said accept and the other said reject -- causing us to
12063 not always publish a new descriptor since we thought nothing
12065 - Retry pending server downloads as well as pending networkstatus
12066 downloads when we unexpectedly get a socks request.
12067 - We were ignoring the IS_FAST flag in the directory status,
12068 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12070 - If the controller's SAVECONF command fails (e.g. due to file
12071 permissions), let the controller know that it failed.
12074 - If we're trying to be a Tor server and running Windows 95/98/ME
12075 as a server, explain that we'll likely crash.
12076 - When we're a server, a client asks for an old-style directory,
12077 and our write bucket is empty, don't give it to him. This way
12078 small servers can continue to serve the directory *sometimes*,
12079 without getting overloaded.
12080 - Compress exit policies even more -- look for duplicate lines
12082 - Clients now honor the "guard" flag in the router status when
12083 picking entry guards, rather than looking at is_fast or is_stable.
12084 - Retain unrecognized lines in $DATADIR/state file, so that we can
12085 be forward-compatible.
12086 - Generate 18.0.0.0/8 address policy format in descs when we can;
12087 warn when the mask is not reducible to a bit-prefix.
12088 - Let the user set ControlListenAddress in the torrc. This can be
12089 dangerous, but there are some cases (like a secured LAN) where it
12091 - Split ReachableAddresses into ReachableDirAddresses and
12092 ReachableORAddresses, so we can restrict Dir conns to port 80
12093 and OR conns to port 443.
12094 - Now we can target arch and OS in rpm builds (contributed by
12095 Phobos). Also make the resulting dist-rpm filename match the
12097 - New config options to help controllers: FetchServerDescriptors
12098 and FetchHidServDescriptors for whether to fetch server
12099 info and hidserv info or let the controller do it, and
12100 PublishServerDescriptor and PublishHidServDescriptors.
12101 - Also let the controller set the __AllDirActionsPrivate config
12102 option if you want all directory fetches/publishes to happen via
12103 Tor (it assumes your controller bootstraps your circuits).
12106 Changes in version 0.1.0.17 - 2006-02-17
12107 o Crash bugfixes on 0.1.0.x:
12108 - When servers with a non-zero DirPort came out of hibernation,
12109 sometimes they would trigger an assert.
12111 o Other important bugfixes:
12112 - On platforms that don't have getrlimit (like Windows), we were
12113 artificially constraining ourselves to a max of 1024
12114 connections. Now just assume that we can handle as many as 15000
12115 connections. Hopefully this won't cause other problems.
12117 o Backported features:
12118 - When we're a server, a client asks for an old-style directory,
12119 and our write bucket is empty, don't give it to him. This way
12120 small servers can continue to serve the directory *sometimes*,
12121 without getting overloaded.
12122 - Whenever you get a 503 in response to a directory fetch, try
12123 once more. This will become important once servers start sending
12124 503's whenever they feel busy.
12125 - Fetch a new directory every 120 minutes, not every 40 minutes.
12126 Now that we have hundreds of thousands of users running the old
12127 directory algorithm, it's starting to hurt a lot.
12128 - Bump up the period for forcing a hidden service descriptor upload
12129 from 20 minutes to 1 hour.
12132 Changes in version 0.1.1.13-alpha - 2006-02-09
12133 o Crashes in 0.1.1.x:
12134 - When you tried to setconf ORPort via the controller, Tor would
12135 crash. So people using TorCP to become a server were sad.
12136 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12137 servers. The problem appears to be something do with OpenSSL's
12138 random number generation, or how we call it, or something. Let me
12139 know if the crashes continue.
12140 - Turn crypto hardware acceleration off by default, until we find
12141 somebody smart who can test it for us. (It appears to produce
12142 seg faults in at least some cases.)
12143 - Fix a rare assert error when we've tried all intro points for
12144 a hidden service and we try fetching the service descriptor again:
12145 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12148 - Fix a major load balance bug: we were round-robining in 16 KB
12149 chunks, and servers with bandwidthrate of 20 KB, while downloading
12150 a 600 KB directory, would starve their other connections. Now we
12151 try to be a bit more fair.
12152 - Dir authorities and mirrors were never expiring the newest
12153 descriptor for each server, causing memory and directory bloat.
12154 - Fix memory-bloating and connection-bloating bug on servers: We
12155 were never closing any connection that had ever had a circuit on
12156 it, because we were checking conn->n_circuits == 0, yet we had a
12157 bug that let it go negative.
12158 - Make Tor work using squid as your http proxy again -- squid
12159 returns an error if you ask for a URL that's too long, and it uses
12160 a really generic error message. Plus, many people are behind a
12161 transparent squid so they don't even realize it.
12162 - On platforms that don't have getrlimit (like Windows), we were
12163 artificially constraining ourselves to a max of 1024
12164 connections. Now just assume that we can handle as many as 15000
12165 connections. Hopefully this won't cause other problems.
12166 - Add a new config option ExitPolicyRejectPrivate which defaults to
12167 1. This means all exit policies will begin with rejecting private
12168 addresses, unless the server operator explicitly turns it off.
12171 - Clients no longer download descriptors for non-running
12173 - Before we add new directory authorities, we should make it
12174 clear that only v1 authorities should receive/publish hidden
12175 service descriptors.
12178 - As soon as we've fetched some more directory info, immediately
12179 try to download more server descriptors. This way we don't have
12180 a 10 second pause during initial bootstrapping.
12181 - Remove even more loud log messages that the server operator can't
12183 - When we're running an obsolete or un-recommended version, make
12184 the log message more clear about what the problem is and what
12185 versions *are* still recommended.
12186 - Provide a more useful warn message when our onion queue gets full:
12187 the CPU is too slow or the exit policy is too liberal.
12188 - Don't warn when we receive a 503 from a dirserver/cache -- this
12189 will pave the way for them being able to refuse if they're busy.
12190 - When we fail to bind a listener, try to provide a more useful
12191 log message: e.g., "Is Tor already running?"
12192 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12193 Goldberg can prove things about our handshake protocol more
12195 - MaxConn has been obsolete for a while now. Document the ConnLimit
12196 config option, which is a *minimum* number of file descriptors
12197 that must be available else Tor refuses to start.
12198 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12199 if you log to syslog and want something other than LOG_DAEMON.
12200 - Make dirservers generate a separate "guard" flag to mean,
12201 "would make a good entry guard". Make clients parse it and vote
12202 on it. Not used by clients yet.
12203 - Implement --with-libevent-dir option to ./configure. Also, improve
12204 search techniques to find libevent, and use those for openssl too.
12205 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12206 - Only start testing reachability once we've established a
12207 circuit. This will make startup on dirservers less noisy.
12208 - Don't try to upload hidden service descriptors until we have
12209 established a circuit.
12210 - Fix the controller's "attachstream 0" command to treat conn like
12211 it just connected, doing address remapping, handling .exit and
12212 .onion idioms, and so on. Now we're more uniform in making sure
12213 that the controller hears about new and closing connections.
12216 Changes in version 0.1.1.12-alpha - 2006-01-11
12217 o Bugfixes on 0.1.1.x:
12218 - The fix to close duplicate server connections was closing all
12219 Tor client connections if they didn't establish a circuit
12220 quickly enough. Oops.
12221 - Fix minor memory issue (double-free) that happened on exit.
12223 o Bugfixes on 0.1.0.x:
12224 - Tor didn't warn when it failed to open a log file.
12227 Changes in version 0.1.1.11-alpha - 2006-01-10
12228 o Crashes in 0.1.1.x:
12229 - Include all the assert/crash fixes from 0.1.0.16.
12230 - If you start Tor and then quit very quickly, there were some
12231 races that tried to free things that weren't allocated yet.
12232 - Fix a rare memory stomp if you're running hidden services.
12233 - Fix segfault when specifying DirServer in config without nickname.
12234 - Fix a seg fault when you finish connecting to a server but at
12235 that moment you dump his server descriptor.
12236 - Extendcircuit and Attachstream controller commands would
12237 assert/crash if you don't give them enough arguments.
12238 - Fix an assert error when we're out of space in the connection_list
12239 and we try to post a hidden service descriptor (reported by weasel).
12240 - If you specify a relative torrc path and you set RunAsDaemon in
12241 your torrc, then it chdir()'s to the new directory. If you HUP,
12242 it tries to load the new torrc location, fails, and exits.
12243 The fix: no longer allow a relative path to torrc using -f.
12246 - Implement "entry guards": automatically choose a handful of entry
12247 nodes and stick with them for all circuits. Only pick new guards
12248 when the ones you have are unsuitable, and if the old guards
12249 become suitable again, switch back. This will increase security
12250 dramatically against certain end-point attacks. The EntryNodes
12251 config option now provides some hints about which entry guards you
12252 want to use most; and StrictEntryNodes means to only use those.
12253 - New directory logic: download by descriptor digest, not by
12254 fingerprint. Caches try to download all listed digests from
12255 authorities; clients try to download "best" digests from caches.
12256 This avoids partitioning and isolating attacks better.
12257 - Make the "stable" router flag in network-status be the median of
12258 the uptimes of running valid servers, and make clients pay
12259 attention to the network-status flags. Thus the cutoff adapts
12260 to the stability of the network as a whole, making IRC, IM, etc
12261 connections more reliable.
12264 - Tor servers with dynamic IP addresses were needing to wait 18
12265 hours before they could start doing reachability testing using
12266 the new IP address and ports. This is because they were using
12267 the internal descriptor to learn what to test, yet they were only
12268 rebuilding the descriptor once they decided they were reachable.
12269 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12270 to download certain server descriptors, throw them away, and then
12271 fetch them again after 30 minutes. Now mirrors throw away these
12272 server descriptors so clients can't get them.
12273 - We were leaving duplicate connections to other ORs open for a week,
12274 rather than closing them once we detect a duplicate. This only
12275 really affected authdirservers, but it affected them a lot.
12276 - Spread the authdirservers' reachability testing over the entire
12277 testing interval, so we don't try to do 500 TLS's at once every
12281 - If the network is down, and we try to connect to a conn because
12282 we have a circuit in mind, and we timeout (30 seconds) because the
12283 network never answers, we were expiring the circuit, but we weren't
12284 obsoleting the connection or telling the entry_guards functions.
12285 - Some Tor servers process billions of cells per day. These statistics
12286 need to be uint64_t's.
12287 - Check for integer overflows in more places, when adding elements
12288 to smartlists. This could possibly prevent a buffer overflow
12289 on malicious huge inputs. I don't see any, but I haven't looked
12291 - ReachableAddresses kept growing new "reject *:*" lines on every
12293 - When you "setconf log" via the controller, it should remove all
12294 logs. We were automatically adding back in a "log notice stdout".
12295 - Newly bootstrapped Tor networks couldn't establish hidden service
12296 circuits until they had nodes with high uptime. Be more tolerant.
12297 - We were marking servers down when they could not answer every piece
12298 of the directory request we sent them. This was far too harsh.
12299 - Fix the torify (tsocks) config file to not use Tor for localhost
12301 - Directory authorities now go to the proper authority when asking for
12302 a networkstatus, even when they want a compressed one.
12303 - Fix a harmless bug that was causing Tor servers to log
12304 "Got an end because of misc error, but we're not an AP. Closing."
12305 - Authorities were treating their own descriptor changes as cosmetic,
12306 meaning the descriptor available in the network-status and the
12307 descriptor that clients downloaded were different.
12308 - The OS X installer was adding a symlink for tor_resolve but
12309 the binary was called tor-resolve (reported by Thomas Hardly).
12310 - Workaround a problem with some http proxies where they refuse GET
12311 requests that specify "Content-Length: 0" (reported by Adrian).
12312 - Fix wrong log message when you add a "HiddenServiceNodes" config
12313 line without any HiddenServiceDir line (reported by Chris Thomas).
12316 - Write the TorVersion into the state file so we have a prayer of
12317 keeping forward and backward compatibility.
12318 - Revive the FascistFirewall config option rather than eliminating it:
12319 now it's a synonym for ReachableAddresses *:80,*:443.
12320 - Clients choose directory servers from the network status lists,
12321 not from their internal list of router descriptors. Now they can
12322 go to caches directly rather than needing to go to authorities
12324 - Directory authorities ignore router descriptors that have only
12325 cosmetic differences: do this for 0.1.0.x servers now too.
12326 - Add a new flag to network-status indicating whether the server
12327 can answer v2 directory requests too.
12328 - Authdirs now stop whining so loudly about bad descriptors that
12329 they fetch from other dirservers. So when there's a log complaint,
12330 it's for sure from a freshly uploaded descriptor.
12331 - Reduce memory requirements in our structs by changing the order
12333 - There used to be two ways to specify your listening ports in a
12334 server descriptor: on the "router" line and with a separate "ports"
12335 line. Remove support for the "ports" line.
12336 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12337 a panic button: if we get flooded with unusable servers we can
12338 revert to only listing servers in the approved-routers file.
12339 - Auth dir servers can now mark a fingerprint as "!reject" or
12340 "!invalid" in the approved-routers file (as its nickname), to
12341 refuse descriptors outright or include them but marked as invalid.
12342 - Servers store bandwidth history across restarts/crashes.
12343 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12344 get a better idea of why their circuits failed. Not used yet.
12345 - Directory mirrors now cache up to 16 unrecognized network-status
12346 docs. Now we can add new authdirservers and they'll be cached too.
12347 - When picking a random directory, prefer non-authorities if any
12349 - New controller option "getinfo desc/all-recent" to fetch the
12350 latest server descriptor for every router that Tor knows about.
12353 Changes in version 0.1.0.16 - 2006-01-02
12354 o Crash bugfixes on 0.1.0.x:
12355 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12356 corrupting the heap, losing FDs, or crashing when we need to resize
12357 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12358 - It turns out sparc64 platforms crash on unaligned memory access
12359 too -- so detect and avoid this.
12360 - Handle truncated compressed data correctly (by detecting it and
12362 - Fix possible-but-unlikely free(NULL) in control.c.
12363 - When we were closing connections, there was a rare case that
12364 stomped on memory, triggering seg faults and asserts.
12365 - Avoid potential infinite recursion when building a descriptor. (We
12366 don't know that it ever happened, but better to fix it anyway.)
12367 - We were neglecting to unlink marked circuits from soon-to-close OR
12368 connections, which caused some rare scribbling on freed memory.
12369 - Fix a memory stomping race bug when closing the joining point of two
12370 rendezvous circuits.
12371 - Fix an assert in time parsing found by Steven Murdoch.
12373 o Other bugfixes on 0.1.0.x:
12374 - When we're doing reachability testing, provide more useful log
12375 messages so the operator knows what to expect.
12376 - Do not check whether DirPort is reachable when we are suppressing
12377 advertising it because of hibernation.
12378 - When building with -static or on Solaris, we sometimes needed -ldl.
12379 - When we're deciding whether a stream has enough circuits around
12380 that can handle it, count the freshly dirty ones and not the ones
12381 that are so dirty they won't be able to handle it.
12382 - When we're expiring old circuits, we had a logic error that caused
12383 us to close new rendezvous circuits rather than old ones.
12384 - Give a more helpful log message when you try to change ORPort via
12385 the controller: you should upgrade Tor if you want that to work.
12386 - We were failing to parse Tor versions that start with "Tor ".
12387 - Tolerate faulty streams better: when a stream fails for reason
12388 exitpolicy, stop assuming that the router is lying about his exit
12389 policy. When a stream fails for reason misc, allow it to retry just
12390 as if it was resolvefailed. When a stream has failed three times,
12391 reset its failure count so we can try again and get all three tries.
12394 Changes in version 0.1.1.10-alpha - 2005-12-11
12395 o Correctness bugfixes on 0.1.0.x:
12396 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12397 corrupting the heap, losing FDs, or crashing when we need to resize
12398 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12399 - Stop doing the complex voodoo overkill checking for insecure
12400 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12401 - When we were closing connections, there was a rare case that
12402 stomped on memory, triggering seg faults and asserts.
12403 - We were neglecting to unlink marked circuits from soon-to-close OR
12404 connections, which caused some rare scribbling on freed memory.
12405 - When we're deciding whether a stream has enough circuits around
12406 that can handle it, count the freshly dirty ones and not the ones
12407 that are so dirty they won't be able to handle it.
12408 - Recover better from TCP connections to Tor servers that are
12409 broken but don't tell you (it happens!); and rotate TLS
12410 connections once a week.
12411 - When we're expiring old circuits, we had a logic error that caused
12412 us to close new rendezvous circuits rather than old ones.
12413 - Fix a scary-looking but apparently harmless bug where circuits
12414 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12415 servers, and never switch to state CIRCUIT_STATE_OPEN.
12416 - When building with -static or on Solaris, we sometimes needed to
12418 - Give a useful message when people run Tor as the wrong user,
12419 rather than telling them to start chowning random directories.
12420 - We were failing to inform the controller about new .onion streams.
12422 o Security bugfixes on 0.1.0.x:
12423 - Refuse server descriptors if the fingerprint line doesn't match
12424 the included identity key. Tor doesn't care, but other apps (and
12425 humans) might actually be trusting the fingerprint line.
12426 - We used to kill the circuit when we receive a relay command we
12427 don't recognize. Now we just drop it.
12428 - Start obeying our firewall options more rigorously:
12429 . If we can't get to a dirserver directly, try going via Tor.
12430 . Don't ever try to connect (as a client) to a place our
12431 firewall options forbid.
12432 . If we specify a proxy and also firewall options, obey the
12433 firewall options even when we're using the proxy: some proxies
12434 can only proxy to certain destinations.
12435 - Fix a bug found by Lasse Overlier: when we were making internal
12436 circuits (intended to be cannibalized later for rendezvous and
12437 introduction circuits), we were picking them so that they had
12438 useful exit nodes. There was no need for this, and it actually
12439 aids some statistical attacks.
12440 - Start treating internal circuits and exit circuits separately.
12441 It's important to keep them separate because internal circuits
12442 have their last hops picked like middle hops, rather than like
12443 exit hops. So exiting on them will break the user's expectations.
12445 o Bugfixes on 0.1.1.x:
12446 - Take out the mis-feature where we tried to detect IP address
12447 flapping for people with DynDNS, and chose not to upload a new
12448 server descriptor sometimes.
12449 - Try to be compatible with OpenSSL 0.9.6 again.
12450 - Log fix: when the controller is logging about .onion addresses,
12451 sometimes it didn't include the ".onion" part of the address.
12452 - Don't try to modify options->DirServers internally -- if the
12453 user didn't specify any, just add the default ones directly to
12454 the trusted dirserver list. This fixes a bug where people running
12455 controllers would use SETCONF on some totally unrelated config
12456 option, and Tor would start yelling at them about changing their
12458 - Let the controller's redirectstream command specify a port, in
12459 case the controller wants to change that too.
12460 - When we requested a pile of server descriptors, we sometimes
12461 accidentally launched a duplicate request for the first one.
12462 - Bugfix for trackhostexits: write down the fingerprint of the
12463 chosen exit, not its nickname, because the chosen exit might not
12465 - When parsing foo.exit, if foo is unknown, and we are leaving
12466 circuits unattached, set the chosen_exit field and leave the
12467 address empty. This matters because controllers got confused
12469 - Directory authorities no longer try to download server
12470 descriptors that they know they will reject.
12472 o Features and updates:
12473 - Replace balanced trees with hash tables: this should make stuff
12474 significantly faster.
12475 - Resume using the AES counter-mode implementation that we ship,
12476 rather than OpenSSL's. Ours is significantly faster.
12477 - Many other CPU and memory improvements.
12478 - Add a new config option FastFirstHopPK (on by default) so clients
12479 do a trivial crypto handshake for their first hop, since TLS has
12480 already taken care of confidentiality and authentication.
12481 - Add a new config option TestSocks so people can see if their
12482 applications are using socks4, socks4a, socks5-with-ip, or
12483 socks5-with-hostname. This way they don't have to keep mucking
12484 with tcpdump and wondering if something got cached somewhere.
12485 - Warn when listening on a public address for socks. I suspect a
12486 lot of people are setting themselves up as open socks proxies,
12487 and they have no idea that jerks on the Internet are using them,
12488 since they simply proxy the traffic into the Tor network.
12489 - Add "private:*" as an alias in configuration for policies. Now
12490 you can simplify your exit policy rather than needing to list
12491 every single internal or nonroutable network space.
12492 - Add a new controller event type that allows controllers to get
12493 all server descriptors that were uploaded to a router in its role
12494 as authoritative dirserver.
12495 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12496 tor-doc-server.html, and stylesheet.css in the tarball.
12497 - Stop shipping tor-doc.html in the tarball.
12500 Changes in version 0.1.1.9-alpha - 2005-11-15
12501 o Usability improvements:
12502 - Start calling it FooListenAddress rather than FooBindAddress,
12503 since few of our users know what it means to bind an address
12505 - Reduce clutter in server logs. We're going to try to make
12506 them actually usable now. New config option ProtocolWarnings that
12507 lets you hear about how _other Tors_ are breaking the protocol. Off
12509 - Divide log messages into logging domains. Once we put some sort
12510 of interface on this, it will let people looking at more verbose
12511 log levels specify the topics they want to hear more about.
12512 - Make directory servers return better http 404 error messages
12513 instead of a generic "Servers unavailable".
12514 - Check for even more Windows version flags when writing the platform
12515 string in server descriptors, and note any we don't recognize.
12516 - Clean up more of the OpenSSL memory when exiting, so we can detect
12517 memory leaks better.
12518 - Make directory authorities be non-versioning, non-naming by
12519 default. Now we can add new directory servers without requiring
12520 their operators to pay close attention.
12521 - When logging via syslog, include the pid whenever we provide
12522 a log entry. Suggested by Todd Fries.
12524 o Performance improvements:
12525 - Directory servers now silently throw away new descriptors that
12526 haven't changed much if the timestamps are similar. We do this to
12527 tolerate older Tor servers that upload a new descriptor every 15
12528 minutes. (It seemed like a good idea at the time.)
12529 - Inline bottleneck smartlist functions; use fast versions by default.
12530 - Add a "Map from digest to void*" abstraction digestmap_t so we
12531 can do less hex encoding/decoding. Use it in router_get_by_digest()
12532 to resolve a performance bottleneck.
12533 - Allow tor_gzip_uncompress to extract as much as possible from
12534 truncated compressed data. Try to extract as many
12535 descriptors as possible from truncated http responses (when
12536 DIR_PURPOSE_FETCH_ROUTERDESC).
12537 - Make circ->onionskin a pointer, not a static array. moria2 was using
12538 125000 circuit_t's after it had been up for a few weeks, which
12539 translates to 20+ megs of wasted space.
12540 - The private half of our EDH handshake keys are now chosen out
12541 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12543 o Security improvements:
12544 - Start making directory caches retain old routerinfos, so soon
12545 clients can start asking by digest of descriptor rather than by
12546 fingerprint of server.
12547 - Add half our entropy from RAND_poll in OpenSSL. This knows how
12548 to use egd (if present), openbsd weirdness (if present), vms/os2
12549 weirdness (if we ever port there), and more in the future.
12551 o Bugfixes on 0.1.0.x:
12552 - Do round-robin writes of at most 16 kB per write. This might be
12553 more fair on loaded Tor servers, and it might resolve our Windows
12554 crash bug. It might also slow things down.
12555 - Our TLS handshakes were generating a single public/private
12556 keypair for the TLS context, rather than making a new one for
12557 each new connections. Oops. (But we were still rotating them
12558 periodically, so it's not so bad.)
12559 - When we were cannibalizing a circuit with a particular exit
12560 node in mind, we weren't checking to see if that exit node was
12561 already present earlier in the circuit. Oops.
12562 - When a Tor server's IP changes (e.g. from a dyndns address),
12563 upload a new descriptor so clients will learn too.
12564 - Really busy servers were keeping enough circuits open on stable
12565 connections that they were wrapping around the circuit_id
12566 space. (It's only two bytes.) This exposed a bug where we would
12567 feel free to reuse a circuit_id even if it still exists but has
12568 been marked for close. Try to fix this bug. Some bug remains.
12569 - If we would close a stream early (e.g. it asks for a .exit that
12570 we know would refuse it) but the LeaveStreamsUnattached config
12571 option is set by the controller, then don't close it.
12573 o Bugfixes on 0.1.1.8-alpha:
12574 - Fix a big pile of memory leaks, some of them serious.
12575 - Do not try to download a routerdesc if we would immediately reject
12577 - Resume inserting a newline between all router descriptors when
12578 generating (old style) signed directories, since our spec says
12580 - When providing content-type application/octet-stream for
12581 server descriptors using .z, we were leaving out the
12582 content-encoding header. Oops. (Everything tolerated this just
12583 fine, but that doesn't mean we need to be part of the problem.)
12584 - Fix a potential seg fault in getconf and getinfo using version 1
12585 of the controller protocol.
12586 - Avoid crash: do not check whether DirPort is reachable when we
12587 are suppressing it because of hibernation.
12588 - Make --hash-password not crash on exit.
12591 Changes in version 0.1.1.8-alpha - 2005-10-07
12592 o New features (major):
12593 - Clients don't download or use the directory anymore. Now they
12594 download and use network-statuses from the trusted dirservers,
12595 and fetch individual server descriptors as needed from mirrors.
12596 See dir-spec.txt for all the gory details.
12597 - Be more conservative about whether to advertise our DirPort.
12598 The main change is to not advertise if we're running at capacity
12599 and either a) we could hibernate or b) our capacity is low and
12600 we're using a default DirPort.
12601 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
12603 o New features (minor):
12604 - Try to be smart about when to retry network-status and
12605 server-descriptor fetches. Still needs some tuning.
12606 - Stop parsing, storing, or using running-routers output (but
12607 mirrors still cache and serve it).
12608 - Consider a threshold of versioning dirservers (dirservers who have
12609 an opinion about which Tor versions are still recommended) before
12610 deciding whether to warn the user that he's obsolete.
12611 - Dirservers can now reject/invalidate by key and IP, with the
12612 config options "AuthDirInvalid" and "AuthDirReject". This is
12613 useful since currently we automatically list servers as running
12614 and usable even if we know they're jerks.
12615 - Provide dire warnings to any users who set DirServer; move it out
12616 of torrc.sample and into torrc.complete.
12617 - Add MyFamily to torrc.sample in the server section.
12618 - Add nicknames to the DirServer line, so we can refer to them
12619 without requiring all our users to memorize their IP addresses.
12620 - When we get an EOF or a timeout on a directory connection, note
12621 how many bytes of serverdesc we are dropping. This will help
12622 us determine whether it is smart to parse incomplete serverdesc
12624 - Add a new function to "change pseudonyms" -- that is, to stop
12625 using any currently-dirty circuits for new streams, so we don't
12626 link new actions to old actions. Currently it's only called on
12627 HUP (or SIGNAL RELOAD).
12628 - On sighup, if UseHelperNodes changed to 1, use new circuits.
12629 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12630 OpenSSL. Also, reseed our entropy every hour, not just at
12631 startup. And entropy in 512-bit chunks, not 160-bit chunks.
12633 o Fixes on 0.1.1.7-alpha:
12634 - Nobody ever implemented EVENT_ADDRMAP for control protocol
12635 version 0, so don't let version 0 controllers ask for it.
12636 - If you requested something with too many newlines via the
12637 v1 controller protocol, you could crash tor.
12638 - Fix a number of memory leaks, including some pretty serious ones.
12639 - Re-enable DirPort testing again, so Tor servers will be willing
12640 to advertise their DirPort if it's reachable.
12641 - On TLS handshake, only check the other router's nickname against
12642 its expected nickname if is_named is set.
12644 o Fixes forward-ported from 0.1.0.15:
12645 - Don't crash when we don't have any spare file descriptors and we
12646 try to spawn a dns or cpu worker.
12647 - Make the numbers in read-history and write-history into uint64s,
12648 so they don't overflow and publish negatives in the descriptor.
12650 o Fixes on 0.1.0.x:
12651 - For the OS X package's modified privoxy config file, comment
12652 out the "logfile" line so we don't log everything passed
12654 - We were whining about using socks4 or socks5-with-local-lookup
12655 even when it's an IP in the "virtual" range we designed exactly
12657 - We were leaking some memory every time the client changes IPs.
12658 - Never call free() on tor_malloc()d memory. This will help us
12659 use dmalloc to detect memory leaks.
12660 - Check for named servers when looking them up by nickname;
12661 warn when we'recalling a non-named server by its nickname;
12662 don't warn twice about the same name.
12663 - Try to list MyFamily elements by key, not by nickname, and warn
12664 if we've not heard of the server.
12665 - Make windows platform detection (uname equivalent) smarter.
12666 - It turns out sparc64 doesn't like unaligned access either.
12669 Changes in version 0.1.0.15 - 2005-09-23
12670 o Bugfixes on 0.1.0.x:
12671 - Reject ports 465 and 587 (spam targets) in default exit policy.
12672 - Don't crash when we don't have any spare file descriptors and we
12673 try to spawn a dns or cpu worker.
12674 - Get rid of IgnoreVersion undocumented config option, and make us
12675 only warn, never exit, when we're running an obsolete version.
12676 - Don't try to print a null string when your server finds itself to
12677 be unreachable and the Address config option is empty.
12678 - Make the numbers in read-history and write-history into uint64s,
12679 so they don't overflow and publish negatives in the descriptor.
12680 - Fix a minor memory leak in smartlist_string_remove().
12681 - We were only allowing ourselves to upload a server descriptor at
12682 most every 20 minutes, even if it changed earlier than that.
12683 - Clean up log entries that pointed to old URLs.
12686 Changes in version 0.1.1.7-alpha - 2005-09-14
12687 o Fixes on 0.1.1.6-alpha:
12688 - Exit servers were crashing when people asked them to make a
12689 connection to an address not in their exit policy.
12690 - Looking up a non-existent stream for a v1 control connection would
12692 - Fix a seg fault if we ask a dirserver for a descriptor by
12693 fingerprint but he doesn't know about him.
12694 - SETCONF was appending items to linelists, not clearing them.
12695 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
12696 out and refuse the setconf if it would fail.
12697 - Downgrade the dirserver log messages when whining about
12701 - Add Peter Palfrader's check-tor script to tor/contrib/
12702 It lets you easily check whether a given server (referenced by
12703 nickname) is reachable by you.
12704 - Numerous changes to move towards client-side v2 directories. Not
12707 o Fixes on 0.1.0.x:
12708 - If the user gave tor an odd number of command-line arguments,
12709 we were silently ignoring the last one. Now we complain and fail.
12710 [This wins the oldest-bug prize -- this bug has been present since
12711 November 2002, as released in Tor 0.0.0.]
12712 - Do not use unaligned memory access on alpha, mips, or mipsel.
12713 It *works*, but is very slow, so we treat them as if it doesn't.
12714 - Retry directory requests if we fail to get an answer we like
12715 from a given dirserver (we were retrying before, but only if
12716 we fail to connect).
12717 - When writing the RecommendedVersions line, sort them first.
12718 - When the client asked for a rendezvous port that the hidden
12719 service didn't want to provide, we were sending an IP address
12720 back along with the end cell. Fortunately, it was zero. But stop
12722 - Correct "your server is reachable" log entries to indicate that
12723 it was self-testing that told us so.
12726 Changes in version 0.1.1.6-alpha - 2005-09-09
12727 o Fixes on 0.1.1.5-alpha:
12728 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
12729 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
12730 - Fix bug with tor_memmem finding a match at the end of the string.
12731 - Make unit tests run without segfaulting.
12732 - Resolve some solaris x86 compile warnings.
12733 - Handle duplicate lines in approved-routers files without warning.
12734 - Fix bug where as soon as a server refused any requests due to his
12735 exit policy (e.g. when we ask for localhost and he tells us that's
12736 127.0.0.1 and he won't do it), we decided he wasn't obeying his
12737 exit policy using him for any exits.
12738 - Only do openssl hardware accelerator stuff if openssl version is
12741 o New controller features/fixes:
12742 - Add a "RESETCONF" command so you can set config options like
12743 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12744 a config option in the torrc with no value, then it clears it
12745 entirely (rather than setting it to its default).
12746 - Add a "GETINFO config-file" to tell us where torrc is.
12747 - Avoid sending blank lines when GETINFO replies should be empty.
12748 - Add a QUIT command for the controller (for using it manually).
12749 - Fix a bug in SAVECONF that was adding default dirservers and
12750 other redundant entries to the torrc file.
12752 o Start on the new directory design:
12753 - Generate, publish, cache, serve new network-status format.
12754 - Publish individual descriptors (by fingerprint, by "all", and by
12756 - Publish client and server recommended versions separately.
12757 - Allow tor_gzip_uncompress() to handle multiple concatenated
12758 compressed strings. Serve compressed groups of router
12759 descriptors. The compression logic here could be more
12761 - Distinguish v1 authorities (all currently trusted directories)
12762 from v2 authorities (all trusted directories).
12763 - Change DirServers config line to note which dirs are v1 authorities.
12764 - Add configuration option "V1AuthoritativeDirectory 1" which
12765 moria1, moria2, and tor26 should set.
12766 - Remove option when getting directory cache to see whether they
12767 support running-routers; they all do now. Replace it with one
12768 to see whether caches support v2 stuff.
12771 - Dirservers now do their own external reachability testing of each
12772 Tor server, and only list them as running if they've been found to
12773 be reachable. We also send back warnings to the server's logs if
12774 it uploads a descriptor that we already believe is unreachable.
12775 - Implement exit enclaves: if we know an IP address for the
12776 destination, and there's a running Tor server at that address
12777 which allows exit to the destination, then extend the circuit to
12778 that exit first. This provides end-to-end encryption and end-to-end
12779 authentication. Also, if the user wants a .exit address or enclave,
12780 use 4 hops rather than 3, and cannibalize a general circ for it
12782 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
12783 controller. Also, rotate dns and cpu workers if the controller
12784 changes options that will affect them; and initialize the dns
12785 worker cache tree whether or not we start out as a server.
12786 - Only upload a new server descriptor when options change, 18
12787 hours have passed, uptime is reset, or bandwidth changes a lot.
12788 - Check [X-]Forwarded-For headers in HTTP requests when generating
12789 log messages. This lets people run dirservers (and caches) behind
12790 Apache but still know which IP addresses are causing warnings.
12792 o Config option changes:
12793 - Replace (Fascist)Firewall* config options with a new
12794 ReachableAddresses option that understands address policies.
12795 For example, "ReachableAddresses *:80,*:443"
12796 - Get rid of IgnoreVersion undocumented config option, and make us
12797 only warn, never exit, when we're running an obsolete version.
12798 - Make MonthlyAccountingStart config option truly obsolete now.
12800 o Fixes on 0.1.0.x:
12801 - Reject ports 465 and 587 in the default exit policy, since
12802 people have started using them for spam too.
12803 - It turns out we couldn't bootstrap a network since we added
12804 reachability detection in 0.1.0.1-rc. Good thing the Tor network
12805 has never gone down. Add an AssumeReachable config option to let
12806 servers and dirservers bootstrap. When we're trying to build a
12807 high-uptime or high-bandwidth circuit but there aren't enough
12808 suitable servers, try being less picky rather than simply failing.
12809 - Our logic to decide if the OR we connected to was the right guy
12810 was brittle and maybe open to a mitm for unverified routers.
12811 - We weren't cannibalizing circuits correctly for
12812 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
12813 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
12814 build those from scratch. This should make hidden services faster.
12815 - Predict required circuits better, with an eye toward making hidden
12816 services faster on the service end.
12817 - Retry streams if the exit node sends back a 'misc' failure. This
12818 should result in fewer random failures. Also, after failing
12819 from resolve failed or misc, reset the num failures, so we give
12820 it a fair shake next time we try.
12821 - Clean up the rendezvous warn log msgs, and downgrade some to info.
12822 - Reduce severity on logs about dns worker spawning and culling.
12823 - When we're shutting down and we do something like try to post a
12824 server descriptor or rendezvous descriptor, don't complain that
12825 we seem to be unreachable. Of course we are, we're shutting down.
12826 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
12827 We don't use them yet, but maybe one day our DNS resolver will be
12828 able to discover them.
12829 - Make ContactInfo mandatory for authoritative directory servers.
12830 - Require server descriptors to list IPv4 addresses -- hostnames
12831 are no longer allowed. This also fixes some potential security
12832 problems with people providing hostnames as their address and then
12833 preferentially resolving them to partition users.
12834 - Change log line for unreachability to explicitly suggest /etc/hosts
12835 as the culprit. Also make it clearer what IP address and ports we're
12836 testing for reachability.
12837 - Put quotes around user-supplied strings when logging so users are
12838 more likely to realize if they add bad characters (like quotes)
12840 - Let auth dir servers start without specifying an Address config
12842 - Make unit tests (and other invocations that aren't the real Tor)
12843 run without launching listeners, creating subdirectories, and so on.
12846 Changes in version 0.1.1.5-alpha - 2005-08-08
12847 o Bugfixes included in 0.1.0.14.
12849 o Bugfixes on 0.1.0.x:
12850 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
12851 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
12852 it would silently using ignore the 6668.
12855 Changes in version 0.1.0.14 - 2005-08-08
12856 o Bugfixes on 0.1.0.x:
12857 - Fix the other half of the bug with crypto handshakes
12859 - Fix an assert trigger if you send a 'signal term' via the
12860 controller when it's listening for 'event info' messages.
12863 Changes in version 0.1.1.4-alpha - 2005-08-04
12864 o Bugfixes included in 0.1.0.13.
12867 - Improve tor_gettimeofday() granularity on windows.
12868 - Make clients regenerate their keys when their IP address changes.
12869 - Implement some more GETINFO goodness: expose helper nodes, config
12870 options, getinfo keys.
12873 Changes in version 0.1.0.13 - 2005-08-04
12874 o Bugfixes on 0.1.0.x:
12875 - Fix a critical bug in the security of our crypto handshakes.
12876 - Fix a size_t underflow in smartlist_join_strings2() that made
12877 it do bad things when you hand it an empty smartlist.
12878 - Fix Windows installer to ship Tor license (thanks to Aphex for
12879 pointing out this oversight) and put a link to the doc directory
12881 - Explicitly set no-unaligned-access for sparc: it turns out the
12882 new gcc's let you compile broken code, but that doesn't make it
12886 Changes in version 0.1.1.3-alpha - 2005-07-23
12887 o Bugfixes on 0.1.1.2-alpha:
12888 - Fix a bug in handling the controller's "post descriptor"
12890 - Fix several bugs in handling the controller's "extend circuit"
12892 - Fix a bug in handling the controller's "stream status" event.
12893 - Fix an assert failure if we have a controller listening for
12894 circuit events and we go offline.
12895 - Re-allow hidden service descriptors to publish 0 intro points.
12896 - Fix a crash when generating your hidden service descriptor if
12897 you don't have enough intro points already.
12899 o New features on 0.1.1.2-alpha:
12900 - New controller function "getinfo accounting", to ask how
12901 many bytes we've used in this time period.
12902 - Experimental support for helper nodes: a lot of the risk from
12903 a small static adversary comes because users pick new random
12904 nodes every time they rebuild a circuit. Now users will try to
12905 stick to the same small set of entry nodes if they can. Not
12906 enabled by default yet.
12908 o Bugfixes on 0.1.0.12:
12909 - If you're an auth dir server, always publish your dirport,
12910 even if you haven't yet found yourself to be reachable.
12911 - Fix a size_t underflow in smartlist_join_strings2() that made
12912 it do bad things when you hand it an empty smartlist.
12915 Changes in version 0.1.0.12 - 2005-07-18
12916 o New directory servers:
12917 - tor26 has changed IP address.
12919 o Bugfixes on 0.1.0.x:
12920 - Fix a possible double-free in tor_gzip_uncompress().
12921 - When --disable-threads is set, do not search for or link against
12922 pthreads libraries.
12923 - Don't trigger an assert if an authoritative directory server
12924 claims its dirport is 0.
12925 - Fix bug with removing Tor as an NT service: some people were
12926 getting "The service did not return an error." Thanks to Matt
12930 Changes in version 0.1.1.2-alpha - 2005-07-15
12931 o New directory servers:
12932 - tor26 has changed IP address.
12934 o Bugfixes on 0.1.0.x, crashes/leaks:
12935 - Port the servers-not-obeying-their-exit-policies fix from
12937 - Fix an fd leak in start_daemon().
12938 - On Windows, you can't always reopen a port right after you've
12939 closed it. So change retry_listeners() to only close and re-open
12940 ports that have changed.
12941 - Fix a possible double-free in tor_gzip_uncompress().
12943 o Bugfixes on 0.1.0.x, usability:
12944 - When tor_socketpair() fails in Windows, give a reasonable
12945 Windows-style errno back.
12946 - Let people type "tor --install" as well as "tor -install" when
12948 want to make it an NT service.
12949 - NT service patch from Matt Edman to improve error messages.
12950 - When the controller asks for a config option with an abbreviated
12951 name, give the full name in our response.
12952 - Correct the man page entry on TrackHostExitsExpire.
12953 - Looks like we were never delivering deflated (i.e. compressed)
12954 running-routers lists, even when asked. Oops.
12955 - When --disable-threads is set, do not search for or link against
12956 pthreads libraries.
12958 o Bugfixes on 0.1.1.x:
12959 - Fix a seg fault with autodetecting which controller version is
12963 - New hidden service descriptor format: put a version in it, and
12964 let people specify introduction/rendezvous points that aren't
12965 in "the directory" (which is subjective anyway).
12966 - Allow the DEBUG controller event to work again. Mark certain log
12967 entries as "don't tell this to controllers", so we avoid cycles.
12970 Changes in version 0.1.0.11 - 2005-06-30
12971 o Bugfixes on 0.1.0.x:
12972 - Fix major security bug: servers were disregarding their
12973 exit policies if clients behaved unexpectedly.
12974 - Make OS X init script check for missing argument, so we don't
12975 confuse users who invoke it incorrectly.
12976 - Fix a seg fault in "tor --hash-password foo".
12977 - The MAPADDRESS control command was broken.
12980 Changes in version 0.1.1.1-alpha - 2005-06-29
12982 - Make OS X init script check for missing argument, so we don't
12983 confuse users who invoke it incorrectly.
12984 - Fix a seg fault in "tor --hash-password foo".
12985 - Fix a possible way to DoS dirservers.
12986 - When we complain that your exit policy implicitly allows local or
12987 private address spaces, name them explicitly so operators can
12989 - Make the log message less scary when all the dirservers are
12990 temporarily unreachable.
12991 - We were printing the number of idle dns workers incorrectly when
12995 - Revised controller protocol (version 1) that uses ascii rather
12996 than binary. Add supporting libraries in python and java so you
12997 can use the controller from your applications without caring how
12998 our protocol works.
12999 - Spiffy new support for crypto hardware accelerators. Can somebody
13003 Changes in version 0.0.9.10 - 2005-06-16
13004 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13005 - Refuse relay cells that claim to have a length larger than the
13006 maximum allowed. This prevents a potential attack that could read
13007 arbitrary memory (e.g. keys) from an exit server's process
13011 Changes in version 0.1.0.10 - 2005-06-14
13012 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13013 libevent before 1.1a.
13016 Changes in version 0.1.0.9-rc - 2005-06-09
13018 - Reset buf->highwater every time buf_shrink() is called, not just on
13019 a successful shrink. This was causing significant memory bloat.
13020 - Fix buffer overflow when checking hashed passwords.
13021 - Security fix: if seeding the RNG on Win32 fails, quit.
13022 - Allow seeding the RNG on Win32 even when you're not running as
13024 - Disable threading on Solaris too. Something is wonky with it,
13025 cpuworkers, and reentrant libs.
13026 - Reenable the part of the code that tries to flush as soon as an
13027 OR outbuf has a full TLS record available. Perhaps this will make
13028 OR outbufs not grow as huge except in rare cases, thus saving lots
13029 of CPU time plus memory.
13030 - Reject malformed .onion addresses rather then passing them on as
13031 normal web requests.
13032 - Adapt patch from Adam Langley: fix possible memory leak in
13033 tor_lookup_hostname().
13034 - Initialize libevent later in the startup process, so the logs are
13035 already established by the time we start logging libevent warns.
13036 - Use correct errno on win32 if libevent fails.
13037 - Check and warn about known-bad/slow libevent versions.
13038 - Pay more attention to the ClientOnly config option.
13039 - Have torctl.in/tor.sh.in check for location of su binary (needed
13041 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13042 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13043 HttpProxyAuthenticator
13044 - Stop warning about sigpipes in the logs. We're going to
13045 pretend that getting these occassionally is normal and fine.
13046 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13048 installer screens; and don't put stuff into StartupItems unless
13049 the user asks you to.
13050 - Require servers that use the default dirservers to have public IP
13051 addresses. We have too many servers that are configured with private
13052 IPs and their admins never notice the log entries complaining that
13053 their descriptors are being rejected.
13054 - Add OSX uninstall instructions. An actual uninstall script will
13058 Changes in version 0.1.0.8-rc - 2005-05-23
13060 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13061 panics. Disable kqueue on all OS X Tors.
13062 - Fix RPM: remove duplicate line accidentally added to the rpm
13064 - Disable threads on openbsd too, since its gethostaddr is not
13066 - Tolerate libevent 0.8 since it still works, even though it's
13068 - Enable building on Red Hat 9.0 again.
13069 - Allow the middle hop of the testing circuit to be running any
13070 version, now that most of them have the bugfix to let them connect
13071 to unknown servers. This will allow reachability testing to work
13072 even when 0.0.9.7-0.0.9.9 become obsolete.
13073 - Handle relay cells with rh.length too large. This prevents
13074 a potential attack that could read arbitrary memory (maybe even
13075 keys) from the exit server's process.
13076 - We screwed up the dirport reachability testing when we don't yet
13077 have a cached version of the directory. Hopefully now fixed.
13078 - Clean up router_load_single_router() (used by the controller),
13079 so it doesn't seg fault on error.
13080 - Fix a minor memory leak when somebody establishes an introduction
13081 point at your Tor server.
13082 - If a socks connection ends because read fails, don't warn that
13083 you're not sending a socks reply back.
13086 - Add HttpProxyAuthenticator config option too, that works like
13087 the HttpsProxyAuthenticator config option.
13088 - Encode hashed controller passwords in hex instead of base64,
13089 to make it easier to write controllers.
13092 Changes in version 0.1.0.7-rc - 2005-05-17
13094 - Fix a bug in the OS X package installer that prevented it from
13095 installing on Tiger.
13096 - Fix a script bug in the OS X package installer that made it
13097 complain during installation.
13098 - Find libevent even if it's hiding in /usr/local/ and your
13099 CFLAGS and LDFLAGS don't tell you to look there.
13100 - Be able to link with libevent as a shared library (the default
13101 after 1.0d), even if it's hiding in /usr/local/lib and even
13102 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13103 assuming you're running gcc. Otherwise fail and give a useful
13105 - Fix a bug in the RPM packager: set home directory for _tor to
13106 something more reasonable when first installing.
13107 - Free a minor amount of memory that is still reachable on exit.
13110 Changes in version 0.1.0.6-rc - 2005-05-14
13112 - Implement --disable-threads configure option. Disable threads on
13113 netbsd by default, because it appears to have no reentrant resolver
13115 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13116 release (1.1) detects and disables kqueue if it's broken.
13117 - Append default exit policy before checking for implicit internal
13118 addresses. Now we don't log a bunch of complaints on startup
13119 when using the default exit policy.
13120 - Some people were putting "Address " in their torrc, and they had
13121 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13122 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13123 LOCALSTATEDIR/tor instead.
13124 - Fix fragmented-message bug in TorControl.py.
13125 - Resolve a minor bug which would prevent unreachable dirports
13126 from getting suppressed in the published descriptor.
13127 - When the controller gave us a new descriptor, we weren't resolving
13128 it immediately, so Tor would think its address was 0.0.0.0 until
13129 we fetched a new directory.
13130 - Fix an uppercase/lowercase case error in suppressing a bogus
13131 libevent warning on some Linuxes.
13134 - Begin scrubbing sensitive strings from logs by default. Turn off
13135 the config option SafeLogging if you need to do debugging.
13136 - Switch to a new buffer management algorithm, which tries to avoid
13137 reallocing and copying quite as much. In first tests it looks like
13138 it uses *more* memory on average, but less cpu.
13139 - First cut at support for "create-fast" cells. Clients can use
13140 these when extending to their first hop, since the TLS already
13141 provides forward secrecy and authentication. Not enabled on
13143 - When dirservers refuse a router descriptor, we now log its
13144 contactinfo, platform, and the poster's IP address.
13145 - Call tor_free_all instead of connections_free_all after forking, to
13146 save memory on systems that need to fork.
13147 - Whine at you if you're a server and you don't set your contactinfo.
13148 - Implement --verify-config command-line option to check if your torrc
13149 is valid without actually launching Tor.
13150 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13151 rather than just rejecting it.
13154 Changes in version 0.1.0.5-rc - 2005-04-27
13156 - Stop trying to print a null pointer if an OR conn fails because
13157 we didn't like its cert.
13159 - Switch our internal buffers implementation to use a ring buffer,
13160 to hopefully improve performance for fast servers a lot.
13161 - Add HttpsProxyAuthenticator support (basic auth only), based
13162 on patch from Adam Langley.
13163 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13164 the fast servers that have been joining lately.
13165 - Give hidden service accesses extra time on the first attempt,
13166 since 60 seconds is often only barely enough. This might improve
13168 - Improve performance for dirservers: stop re-parsing the whole
13169 directory every time you regenerate it.
13170 - Add more debugging info to help us find the weird dns freebsd
13171 pthreads bug; cleaner debug messages to help track future issues.
13174 Changes in version 0.0.9.9 - 2005-04-23
13175 o Bugfixes on 0.0.9.x:
13176 - If unofficial Tor clients connect and send weird TLS certs, our
13177 Tor server triggers an assert. This release contains a minimal
13178 backport from the broader fix that we put into 0.1.0.4-rc.
13181 Changes in version 0.1.0.4-rc - 2005-04-23
13183 - If unofficial Tor clients connect and send weird TLS certs, our
13184 Tor server triggers an assert. Stop asserting, and start handling
13185 TLS errors better in other situations too.
13186 - When the controller asks us to tell it about all the debug-level
13187 logs, it turns out we were generating debug-level logs while
13188 telling it about them, which turns into a bad loop. Now keep
13189 track of whether you're sending a debug log to the controller,
13190 and don't log when you are.
13191 - Fix the "postdescriptor" feature of the controller interface: on
13192 non-complete success, only say "done" once.
13194 - Clients are now willing to load balance over up to 2mB, not 1mB,
13195 of advertised bandwidth capacity.
13196 - Add a NoPublish config option, so you can be a server (e.g. for
13197 testing running Tor servers in other Tor networks) without
13198 publishing your descriptor to the primary dirservers.
13201 Changes in version 0.1.0.3-rc - 2005-04-08
13202 o Improvements on 0.1.0.2-rc:
13203 - Client now retries when streams end early for 'hibernating' or
13204 'resource limit' reasons, rather than failing them.
13205 - More automated handling for dirserver operators:
13206 - Automatically approve nodes running 0.1.0.2-rc or later,
13207 now that the the reachability detection stuff is working.
13208 - Now we allow two unverified servers with the same nickname
13209 but different keys. But if a nickname is verified, only that
13210 nickname+key are allowed.
13211 - If you're an authdirserver connecting to an address:port,
13212 and it's not the OR you were expecting, forget about that
13213 descriptor. If he *was* the one you were expecting, then forget
13214 about all other descriptors for that address:port.
13215 - Allow servers to publish descriptors from 12 hours in the future.
13216 Corollary: only whine about clock skew from the dirserver if
13217 he's a trusted dirserver (since now even verified servers could
13218 have quite wrong clocks).
13219 - Adjust maximum skew and age for rendezvous descriptors: let skew
13220 be 48 hours rather than 90 minutes.
13221 - Efficiency improvements:
13222 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13223 it much faster to look up a circuit for each relay cell.
13224 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13225 since they're eating our cpu on exit nodes.
13226 - Stop wasting time doing a case insensitive comparison for every
13227 dns name every time we do any lookup. Canonicalize the names to
13228 lowercase and be done with it.
13229 - Start sending 'truncated' cells back rather than destroy cells,
13230 if the circuit closes in front of you. This means we won't have
13231 to abandon partially built circuits.
13232 - Only warn once per nickname from add_nickname_list_to_smartlist
13233 per failure, so an entrynode or exitnode choice that's down won't
13235 - Put a note in the torrc about abuse potential with the default
13237 - Revise control spec and implementation to allow all log messages to
13238 be sent to controller with their severities intact (suggested by
13239 Matt Edman). Update TorControl to handle new log event types.
13240 - Provide better explanation messages when controller's POSTDESCRIPTOR
13242 - Stop putting nodename in the Platform string in server descriptors.
13243 It doesn't actually help, and it is confusing/upsetting some people.
13245 o Bugfixes on 0.1.0.2-rc:
13246 - We were printing the host mask wrong in exit policies in server
13247 descriptors. This isn't a critical bug though, since we were still
13248 obeying the exit policy internally.
13249 - Fix Tor when compiled with libevent but without pthreads: move
13250 connection_unregister() from _connection_free() to
13252 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13253 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13254 when we look through the connection array, we'll find any of the
13255 cpu/dnsworkers. This is no good.
13257 o Bugfixes on 0.0.9.8:
13258 - Fix possible bug on threading platforms (e.g. win32) which was
13259 leaking a file descriptor whenever a cpuworker or dnsworker died.
13260 - When using preferred entry or exit nodes, ignore whether the
13261 circuit wants uptime or capacity. They asked for the nodes, they
13263 - chdir() to your datadirectory at the *end* of the daemonize process,
13264 not the beginning. This was a problem because the first time you
13265 run tor, if your datadir isn't there, and you have runasdaemon set
13266 to 1, it will try to chdir to it before it tries to create it. Oops.
13267 - Handle changed router status correctly when dirserver reloads
13268 fingerprint file. We used to be dropping all unverified descriptors
13269 right then. The bug was hidden because we would immediately
13270 fetch a directory from another dirserver, which would include the
13271 descriptors we just dropped.
13272 - When we're connecting to an OR and he's got a different nickname/key
13273 than we were expecting, only complain loudly if we're an OP or a
13274 dirserver. Complaining loudly to the OR admins just confuses them.
13275 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13276 artificially capped at 500kB.
13279 Changes in version 0.0.9.8 - 2005-04-07
13280 o Bugfixes on 0.0.9.x:
13281 - We have a bug that I haven't found yet. Sometimes, very rarely,
13282 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13283 thinks of itself as idle. This meant that no new circuits ever got
13284 established. Here's a workaround to kill any cpuworker that's been
13285 busy for more than 100 seconds.
13288 Changes in version 0.1.0.2-rc - 2005-04-01
13289 o Bugfixes on 0.1.0.1-rc:
13290 - Fixes on reachability detection:
13291 - Don't check for reachability while hibernating.
13292 - If ORPort is reachable but DirPort isn't, still publish the
13293 descriptor, but zero out DirPort until it's found reachable.
13294 - When building testing circs for ORPort testing, use only
13295 high-bandwidth nodes, so fewer circuits fail.
13296 - Complain about unreachable ORPort separately from unreachable
13297 DirPort, so the user knows what's going on.
13298 - Make sure we only conclude ORPort reachability if we didn't
13299 initiate the conn. Otherwise we could falsely conclude that
13300 we're reachable just because we connected to the guy earlier
13301 and he used that same pipe to extend to us.
13302 - Authdirservers shouldn't do ORPort reachability detection,
13303 since they're in clique mode, so it will be rare to find a
13304 server not already connected to them.
13305 - When building testing circuits, always pick middle hops running
13306 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13307 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13309 - When we decide we're reachable, actually publish our descriptor
13311 - Fix bug in redirectstream in the controller.
13312 - Fix the state descriptor strings so logs don't claim edge streams
13313 are in a different state than they actually are.
13314 - Use recent libevent features when possible (this only really affects
13315 win32 and osx right now, because the new libevent with these
13316 features hasn't been released yet). Add code to suppress spurious
13318 - Prevent possible segfault in connection_close_unattached_ap().
13319 - Fix newlines on torrc in win32.
13320 - Improve error msgs when tor-resolve fails.
13322 o Improvements on 0.0.9.x:
13323 - New experimental script tor/contrib/ExerciseServer.py (needs more
13324 work) that uses the controller interface to build circuits and
13325 fetch pages over them. This will help us bootstrap servers that
13326 have lots of capacity but haven't noticed it yet.
13327 - New experimental script tor/contrib/PathDemo.py (needs more work)
13328 that uses the controller interface to let you choose whole paths
13330 "<hostname>.<path,separated by dots>.<length of path>.path"
13331 - When we've connected to an OR and handshaked but didn't like
13332 the result, we were closing the conn without sending destroy
13333 cells back for pending circuits. Now send those destroys.
13336 Changes in version 0.0.9.7 - 2005-04-01
13337 o Bugfixes on 0.0.9.x:
13338 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13339 - Compare identity to identity, not to nickname, when extending to
13340 a router not already in the directory. This was preventing us from
13341 extending to unknown routers. Oops.
13342 - Make sure to create OS X Tor user in <500 range, so we aren't
13343 creating actual system users.
13344 - Note where connection-that-hasn't-sent-end was marked, and fix
13345 a few really loud instances of this harmless bug (it's fixed more
13349 Changes in version 0.1.0.1-rc - 2005-03-28
13351 - Add reachability testing. Your Tor server will automatically try
13352 to see if its ORPort and DirPort are reachable from the outside,
13353 and it won't upload its descriptor until it decides they are.
13354 - Handle unavailable hidden services better. Handle slow or busy
13355 hidden services better.
13356 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13358 - New exit policy: accept most low-numbered ports, rather than
13359 rejecting most low-numbered ports.
13360 - More Tor controller support (still experimental). See
13361 http://tor.eff.org/doc/control-spec.txt for all the new features,
13362 including signals to emulate unix signals from any platform;
13363 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13364 closestream; closecircuit; etc.
13365 - Make nt services work and start on startup on win32 (based on
13366 patch by Matt Edman).
13367 - Add a new AddressMap config directive to rewrite incoming socks
13368 addresses. This lets you, for example, declare an implicit
13369 required exit node for certain sites.
13370 - Add a new TrackHostExits config directive to trigger addressmaps
13371 for certain incoming socks addresses -- for sites that break when
13372 your exit keeps changing (based on patch by Mike Perry).
13373 - Redo the client-side dns cache so it's just an addressmap too.
13374 - Notice when our IP changes, and reset stats/uptime/reachability.
13375 - When an application is using socks5, give him the whole variety of
13376 potential socks5 responses (connect refused, host unreachable, etc),
13377 rather than just "success" or "failure".
13378 - A more sane version numbering system. See
13379 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13380 - New contributed script "exitlist": a simple python script to
13381 parse directories and find Tor nodes that exit to listed
13383 - New contributed script "privoxy-tor-toggle" to toggle whether
13384 Privoxy uses Tor. Seems to be configured for Debian by default.
13385 - Report HTTP reasons to client when getting a response from directory
13386 servers -- so you can actually know what went wrong.
13387 - New config option MaxAdvertisedBandwidth which lets you advertise
13388 a low bandwidthrate (to not attract as many circuits) while still
13389 allowing a higher bandwidthrate in reality.
13391 o Robustness/stability fixes:
13392 - Make Tor use Niels Provos's libevent instead of its current
13393 poll-but-sometimes-select mess. This will let us use faster async
13394 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13396 - pthread support now too. This was forced because when we forked,
13397 we ended up wasting a lot of duplicate ram over time. Also switch
13398 to foo_r versions of some library calls to allow reentry and
13400 - Better handling for heterogeneous / unreliable nodes:
13401 - Annotate circuits w/ whether they aim to contain high uptime nodes
13402 and/or high capacity nodes. When building circuits, choose
13404 - This means that every single node in an intro rend circuit,
13405 not just the last one, will have a minimum uptime.
13406 - New config option LongLivedPorts to indicate application streams
13407 that will want high uptime circuits.
13408 - Servers reset uptime when a dir fetch entirely fails. This
13409 hopefully reflects stability of the server's network connectivity.
13410 - If somebody starts his tor server in Jan 2004 and then fixes his
13411 clock, don't make his published uptime be a year.
13412 - Reset published uptime when you wake up from hibernation.
13413 - Introduce a notion of 'internal' circs, which are chosen without
13414 regard to the exit policy of the last hop. Intro and rendezvous
13415 circs must be internal circs, to avoid leaking information. Resolve
13416 and connect streams can use internal circs if they want.
13417 - New circuit pooling algorithm: make sure to have enough circs around
13418 to satisfy any predicted ports, and also make sure to have 2 internal
13419 circs around if we've required internal circs lately (and with high
13420 uptime if we've seen that lately too).
13421 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13422 which describes how often we retry making new circuits if current
13423 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13424 how long we're willing to make use of an already-dirty circuit.
13425 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13426 circ as necessary, if there are any completed ones lying around
13427 when we try to launch one.
13428 - Make hidden services try to establish a rendezvous for 30 seconds,
13429 rather than for n (where n=3) attempts to build a circuit.
13430 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13431 "ShutdownWaitLength".
13432 - Try to be more zealous about calling connection_edge_end when
13433 things go bad with edge conns in connection.c.
13434 - Revise tor-spec to add more/better stream end reasons.
13435 - Revise all calls to connection_edge_end to avoid sending "misc",
13436 and to take errno into account where possible.
13439 - Fix a race condition that can trigger an assert, when we have a
13440 pending create cell and an OR connection fails right then.
13441 - Fix several double-mark-for-close bugs, e.g. where we were finding
13442 a conn for a cell even if that conn is already marked for close.
13443 - Make sequence of log messages when starting on win32 with no config
13444 file more reasonable.
13445 - When choosing an exit node for a new non-internal circ, don't take
13446 into account whether it'll be useful for any pending x.onion
13447 addresses -- it won't.
13448 - Turn addr_policy_compare from a tristate to a quadstate; this should
13449 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13450 for google.com" problem.
13451 - Make "platform" string in descriptor more accurate for Win32 servers,
13452 so it's not just "unknown platform".
13453 - Fix an edge case in parsing config options (thanks weasel).
13454 If they say "--" on the commandline, it's not an option.
13455 - Reject odd-looking addresses at the client (e.g. addresses that
13456 contain a colon), rather than having the server drop them because
13458 - tor-resolve requests were ignoring .exit if there was a working circuit
13459 they could use instead.
13460 - REUSEADDR on normal platforms means you can rebind to the port
13461 right after somebody else has let it go. But REUSEADDR on win32
13462 means to let you bind to the port _even when somebody else
13463 already has it bound_! So, don't do that on Win32.
13464 - Change version parsing logic: a version is "obsolete" if it is not
13465 recommended and (1) there is a newer recommended version in the
13466 same series, or (2) there are no recommended versions in the same
13467 series, but there are some recommended versions in a newer series.
13468 A version is "new" if it is newer than any recommended version in
13470 - Stop most cases of hanging up on a socks connection without sending
13474 - Require BandwidthRate to be at least 20kB/s for servers.
13475 - When a dirserver causes you to give a warn, mention which dirserver
13477 - New config option DirAllowPrivateAddresses for authdirservers.
13478 Now by default they refuse router descriptors that have non-IP or
13479 private-IP addresses.
13480 - Stop publishing socksport in the directory, since it's not
13481 actually meant to be public. For compatibility, publish a 0 there
13483 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13484 smart" value, that is low for servers and high for clients.
13485 - If our clock jumps forward by 100 seconds or more, assume something
13486 has gone wrong with our network and abandon all not-yet-used circs.
13487 - Warn when exit policy implicitly allows local addresses.
13488 - If we get an incredibly skewed timestamp from a dirserver mirror
13489 that isn't a verified OR, don't warn -- it's probably him that's
13491 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13492 cookies to disk and doesn't log each web request to disk. (Thanks
13493 to Brett Carrington for pointing this out.)
13494 - When a client asks us for a dir mirror and we don't have one,
13495 launch an attempt to get a fresh one.
13496 - If we're hibernating and we get a SIGINT, exit immediately.
13497 - Add --with-dmalloc ./configure option, to track memory leaks.
13498 - And try to free all memory on closing, so we can detect what
13500 - Cache local dns resolves correctly even when they're .exit
13502 - Give a better warning when some other server advertises an
13503 ORPort that is actually an apache running ssl.
13504 - Add "opt hibernating 1" to server descriptor to make it clearer
13505 whether the server is hibernating.
13508 Changes in version 0.0.9.6 - 2005-03-24
13509 o Bugfixes on 0.0.9.x (crashes and asserts):
13510 - Add new end stream reasons to maintainance branch. Fix bug where
13511 reason (8) could trigger an assert. Prevent bug from recurring.
13512 - Apparently win32 stat wants paths to not end with a slash.
13513 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13514 blowing away the circuit that conn->cpath_layer points to, then
13515 checking to see if the circ is well-formed. Backport check to make
13516 sure we dont use the cpath on a closed connection.
13517 - Prevent circuit_resume_edge_reading_helper() from trying to package
13518 inbufs for marked-for-close streams.
13519 - Don't crash on hup if your options->address has become unresolvable.
13520 - Some systems (like OS X) sometimes accept() a connection and tell
13521 you the remote host is 0.0.0.0:0. If this happens, due to some
13522 other mis-features, we get confused; so refuse the conn for now.
13524 o Bugfixes on 0.0.9.x (other):
13525 - Fix harmless but scary "Unrecognized content encoding" warn message.
13526 - Add new stream error reason: TORPROTOCOL reason means "you are not
13527 speaking a version of Tor I understand; say bye-bye to your stream."
13528 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13529 into the future, now that we are more tolerant of skew. This
13530 resolves a bug where a Tor server would refuse to cache a directory
13531 because all the directories it gets are too far in the future;
13532 yet the Tor server never logs any complaints about clock skew.
13533 - Mac packaging magic: make man pages useable, and do not overwrite
13534 existing torrc files.
13535 - Make OS X log happily to /var/log/tor/tor.log
13538 Changes in version 0.0.9.5 - 2005-02-22
13539 o Bugfixes on 0.0.9.x:
13540 - Fix an assert race at exit nodes when resolve requests fail.
13541 - Stop picking unverified dir mirrors--it only leads to misery.
13542 - Patch from Matt Edman to make NT services work better. Service
13543 support is still not compiled into the executable by default.
13544 - Patch from Dmitri Bely so the Tor service runs better under
13545 the win32 SYSTEM account.
13546 - Make tor-resolve actually work (?) on Win32.
13547 - Fix a sign bug when getrlimit claims to have 4+ billion
13548 file descriptors available.
13549 - Stop refusing to start when bandwidthburst == bandwidthrate.
13550 - When create cells have been on the onion queue more than five
13551 seconds, just send back a destroy and take them off the list.
13554 Changes in version 0.0.9.4 - 2005-02-03
13555 o Bugfixes on 0.0.9:
13556 - Fix an assert bug that took down most of our servers: when
13557 a server claims to have 1 GB of bandwidthburst, don't
13559 - Don't crash as badly if we have spawned the max allowed number
13560 of dnsworkers, or we're out of file descriptors.
13561 - Block more file-sharing ports in the default exit policy.
13562 - MaxConn is now automatically set to the hard limit of max
13563 file descriptors we're allowed (ulimit -n), minus a few for
13565 - Give a clearer message when servers need to raise their
13566 ulimit -n when they start running out of file descriptors.
13567 - SGI Compatibility patches from Jan Schaumann.
13568 - Tolerate a corrupt cached directory better.
13569 - When a dirserver hasn't approved your server, list which one.
13570 - Go into soft hibernation after 95% of the bandwidth is used,
13571 not 99%. This is especially important for daily hibernators who
13572 have a small accounting max. Hopefully it will result in fewer
13573 cut connections when the hard hibernation starts.
13574 - Load-balance better when using servers that claim more than
13575 800kB/s of capacity.
13576 - Make NT services work (experimental, only used if compiled in).
13579 Changes in version 0.0.9.3 - 2005-01-21
13580 o Bugfixes on 0.0.9:
13581 - Backport the cpu use fixes from main branch, so busy servers won't
13582 need as much processor time.
13583 - Work better when we go offline and then come back, or when we
13584 run Tor at boot before the network is up. We do this by
13585 optimistically trying to fetch a new directory whenever an
13586 application request comes in and we think we're offline -- the
13587 human is hopefully a good measure of when the network is back.
13588 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13589 long as you keep using them; actually publish hidserv descriptors
13590 shortly after they change, rather than waiting 20-40 minutes.
13591 - Enable Mac startup script by default.
13592 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13593 - When you update AllowUnverifiedNodes or FirewallPorts via the
13594 controller's setconf feature, we were always appending, never
13596 - When you update HiddenServiceDir via setconf, it was screwing up
13597 the order of reading the lines, making it fail.
13598 - Do not rewrite a cached directory back to the cache; otherwise we
13599 will think it is recent and not fetch a newer one on startup.
13600 - Workaround for webservers that lie about Content-Encoding: Tor
13601 now tries to autodetect compressed directories and compression
13602 itself. This lets us Proxypass dir fetches through apache.
13605 Changes in version 0.0.9.2 - 2005-01-04
13606 o Bugfixes on 0.0.9 (crashes and asserts):
13607 - Fix an assert on startup when the disk is full and you're logging
13609 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13610 style address, then we'd crash.
13611 - Fix an assert trigger when the running-routers string we get from
13612 a dirserver is broken.
13613 - Make worker threads start and run on win32. Now win32 servers
13615 - Bandaid (not actually fix, but now it doesn't crash) an assert
13616 where the dns worker dies mysteriously and the main Tor process
13617 doesn't remember anything about the address it was resolving.
13619 o Bugfixes on 0.0.9 (Win32):
13620 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13621 name out of the warning/assert messages.
13622 - Fix a superficial "unhandled error on read" bug on win32.
13623 - The win32 installer no longer requires a click-through for our
13624 license, since our Free Software license grants rights but does not
13626 - Win32: When connecting to a dirserver fails, try another one
13627 immediately. (This was already working for non-win32 Tors.)
13628 - Stop trying to parse $HOME on win32 when hunting for default
13630 - Make tor-resolve.c work on win32 by calling network_init().
13632 o Bugfixes on 0.0.9 (other):
13633 - Make 0.0.9.x build on Solaris again.
13634 - Due to a fencepost error, we were blowing away the \n when reporting
13635 confvalue items in the controller. So asking for multiple config
13636 values at once couldn't work.
13637 - When listing circuits that are pending on an opening OR connection,
13638 if we're an OR we were listing circuits that *end* at us as
13639 being pending on every listener, dns/cpu worker, etc. Stop that.
13640 - Dirservers were failing to create 'running-routers' or 'directory'
13641 strings if we had more than some threshold of routers. Fix them so
13642 they can handle any number of routers.
13643 - Fix a superficial "Duplicate mark for close" bug.
13644 - Stop checking for clock skew for OR connections, even for servers.
13645 - Fix a fencepost error that was chopping off the last letter of any
13646 nickname that is the maximum allowed nickname length.
13647 - Update URLs in log messages so they point to the new website.
13648 - Fix a potential problem in mangling server private keys while
13649 writing to disk (not triggered yet, as far as we know).
13650 - Include the licenses for other free software we include in Tor,
13651 now that we're shipping binary distributions more regularly.
13654 Changes in version 0.0.9.1 - 2004-12-15
13655 o Bugfixes on 0.0.9:
13656 - Make hibernation actually work.
13657 - Make HashedControlPassword config option work.
13658 - When we're reporting event circuit status to a controller,
13659 don't use the stream status code.
13662 Changes in version 0.0.9 - 2004-12-12
13664 - Clean up manpage and torrc.sample file.
13665 - Clean up severities and text of log warnings.
13667 - Make servers trigger an assert when they enter hibernation.
13670 Changes in version 0.0.9rc7 - 2004-12-08
13671 o Bugfixes on 0.0.9rc:
13672 - Fix a stack-trashing crash when an exit node begins hibernating.
13673 - Avoid looking at unallocated memory while considering which
13674 ports we need to build circuits to cover.
13675 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13676 we shouldn't hold-open-until-flush if the eof arrived first.
13677 - Fix a bug with init_cookie_authentication() in the controller.
13678 - When recommending new-format log lines, if the upper bound is
13679 LOG_ERR, leave it implicit.
13681 o Bugfixes on 0.0.8.1:
13682 - Fix a whole slew of memory leaks.
13683 - Fix isspace() and friends so they still make Solaris happy
13684 but also so they don't trigger asserts on win32.
13685 - Fix parse_iso_time on platforms without strptime (eg win32).
13686 - win32: tolerate extra "readable" events better.
13687 - win32: when being multithreaded, leave parent fdarray open.
13688 - Make unit tests work on win32.
13691 Changes in version 0.0.9rc6 - 2004-12-06
13692 o Bugfixes on 0.0.9pre:
13693 - Clean up some more integer underflow opportunities (not exploitable
13695 - While hibernating, hup should not regrow our listeners.
13696 - Send an end to the streams we close when we hibernate, rather
13697 than just chopping them off.
13698 - React to eof immediately on non-open edge connections.
13700 o Bugfixes on 0.0.8.1:
13701 - Calculate timeout for waiting for a connected cell from the time
13702 we sent the begin cell, not from the time the stream started. If
13703 it took a long time to establish the circuit, we would time out
13704 right after sending the begin cell.
13705 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13706 of * as always matching, so we were picking reject *:* nodes as
13707 exit nodes too. Oops.
13710 - New circuit building strategy: keep a list of ports that we've
13711 used in the past 6 hours, and always try to have 2 circuits open
13712 or on the way that will handle each such port. Seed us with port
13713 80 so web users won't complain that Tor is "slow to start up".
13714 - Make kill -USR1 dump more useful stats about circuits.
13715 - When warning about retrying or giving up, print the address, so
13716 the user knows which one it's talking about.
13717 - If you haven't used a clean circuit in an hour, throw it away,
13718 just to be on the safe side. (This means after 6 hours a totally
13719 unused Tor client will have no circuits open.)
13722 Changes in version 0.0.9rc5 - 2004-12-01
13723 o Bugfixes on 0.0.8.1:
13724 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13725 - Let resolve conns retry/expire also, rather than sticking around
13727 - If we are using select, make sure we stay within FD_SETSIZE.
13729 o Bugfixes on 0.0.9pre:
13730 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
13731 but doesn't seem to be currently; thanks to Ilja van Sprundel for
13733 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
13734 instead. Impose minima and maxima for all *Period options; impose
13735 even tighter maxima for fetching if we are a caching dirserver.
13736 Clip rather than rejecting.
13737 - Fetch cached running-routers from servers that serve it (that is,
13738 authdirservers and servers running 0.0.9rc5-cvs or later.)
13741 - Accept *:706 (silc) in default exit policy.
13742 - Implement new versioning format for post 0.1.
13743 - Support "foo.nickname.exit" addresses, to let Alice request the
13744 address "foo" as viewed by exit node "nickname". Based on a patch
13746 - Make tor --version --version dump the cvs Id of every file.
13749 Changes in version 0.0.9rc4 - 2004-11-28
13750 o Bugfixes on 0.0.8.1:
13751 - Make windows sockets actually non-blocking (oops), and handle
13752 win32 socket errors better.
13754 o Bugfixes on 0.0.9rc1:
13755 - Actually catch the -USR2 signal.
13758 Changes in version 0.0.9rc3 - 2004-11-25
13759 o Bugfixes on 0.0.8.1:
13760 - Flush the log file descriptor after we print "Tor opening log file",
13761 so we don't see those messages days later.
13763 o Bugfixes on 0.0.9rc1:
13764 - Make tor-resolve work again.
13765 - Avoid infinite loop in tor-resolve if tor hangs up on it.
13766 - Fix an assert trigger for clients/servers handling resolves.
13769 Changes in version 0.0.9rc2 - 2004-11-24
13770 o Bugfixes on 0.0.9rc1:
13771 - I broke socks5 support while fixing the eof bug.
13772 - Allow unitless bandwidths and intervals; they default to bytes
13774 - New servers don't start out hibernating; they are active until
13775 they run out of bytes, so they have a better estimate of how
13776 long it takes, and so their operators can know they're working.
13779 Changes in version 0.0.9rc1 - 2004-11-23
13780 o Bugfixes on 0.0.8.1:
13781 - Finally fix a bug that's been plaguing us for a year:
13782 With high load, circuit package window was reaching 0. Whenever
13783 we got a circuit-level sendme, we were reading a lot on each
13784 socket, but only writing out a bit. So we would eventually reach
13785 eof. This would be noticed and acted on even when there were still
13786 bytes sitting in the inbuf.
13787 - When poll() is interrupted, we shouldn't believe the revents values.
13789 o Bugfixes on 0.0.9pre6:
13790 - Fix hibernate bug that caused pre6 to be broken.
13791 - Don't keep rephist info for routers that haven't had activity for
13792 24 hours. (This matters now that clients have keys, since we track
13794 - Never call close_temp_logs while validating log options.
13795 - Fix backslash-escaping on tor.sh.in and torctl.in.
13798 - Implement weekly/monthly/daily accounting: now you specify your
13799 hibernation properties by
13800 AccountingMax N bytes|KB|MB|GB|TB
13801 AccountingStart day|week|month [day] HH:MM
13802 Defaults to "month 1 0:00".
13803 - Let bandwidth and interval config options be specified as 5 bytes,
13804 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
13805 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
13806 get back to normal.)
13807 - If your requested entry or exit node has advertised bandwidth 0,
13809 - Be more greedy about filling up relay cells -- we try reading again
13810 once we've processed the stuff we read, in case enough has arrived
13811 to fill the last cell completely.
13812 - Apply NT service patch from Osamu Fujino. Still needs more work.
13815 Changes in version 0.0.9pre6 - 2004-11-15
13816 o Bugfixes on 0.0.8.1:
13817 - Fix assert failure on malformed socks4a requests.
13818 - Use identity comparison, not nickname comparison, to choose which
13819 half of circuit-ID-space each side gets to use. This is needed
13820 because sometimes we think of a router as a nickname, and sometimes
13821 as a hex ID, and we can't predict what the other side will do.
13822 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
13823 write() call will fail and we handle it there.
13824 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
13825 and smartlist_len, which are two major profiling offenders.
13827 o Bugfixes on 0.0.9pre5:
13828 - Fix a bug in read_all that was corrupting config files on windows.
13829 - When we're raising the max number of open file descriptors to
13830 'unlimited', don't log that we just raised it to '-1'.
13831 - Include event code with events, as required by control-spec.txt.
13832 - Don't give a fingerprint when clients do --list-fingerprint:
13833 it's misleading, because it will never be the same again.
13834 - Stop using strlcpy in tor_strndup, since it was slowing us
13836 - Remove warn on startup about missing cached-directory file.
13837 - Make kill -USR1 work again.
13838 - Hibernate if we start tor during the "wait for wakeup-time" phase
13839 of an accounting interval. Log our hibernation plans better.
13840 - Authoritative dirservers now also cache their directory, so they
13841 have it on start-up.
13844 - Fetch running-routers; cache running-routers; compress
13845 running-routers; serve compressed running-routers.z
13846 - Add NSI installer script contributed by J Doe.
13847 - Commit VC6 and VC7 workspace/project files.
13848 - Commit a tor.spec for making RPM files, with help from jbash.
13849 - Add contrib/torctl.in contributed by Glenn Fink.
13850 - Implement the control-spec's SAVECONF command, to write your
13851 configuration to torrc.
13852 - Get cookie authentication for the controller closer to working.
13853 - Include control-spec.txt in the tarball.
13854 - When set_conf changes our server descriptor, upload a new copy.
13855 But don't upload it too often if there are frequent changes.
13856 - Document authentication config in man page, and document signals
13858 - Clean up confusing parts of man page and torrc.sample.
13859 - Make expand_filename handle ~ and ~username.
13860 - Use autoconf to enable largefile support where necessary. Use
13861 ftello where available, since ftell can fail at 2GB.
13862 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
13863 log more informatively.
13864 - Give a slightly more useful output for "tor -h".
13865 - Refuse application socks connections to port 0.
13866 - Check clock skew for verified servers, but allow unverified
13867 servers and clients to have any clock skew.
13868 - Break DirFetchPostPeriod into:
13869 - DirFetchPeriod for fetching full directory,
13870 - StatusFetchPeriod for fetching running-routers,
13871 - DirPostPeriod for posting server descriptor,
13872 - RendPostPeriod for posting hidden service descriptors.
13873 - Make sure the hidden service descriptors are at a random offset
13874 from each other, to hinder linkability.
13877 Changes in version 0.0.9pre5 - 2004-11-09
13878 o Bugfixes on 0.0.9pre4:
13879 - Fix a seg fault in unit tests (doesn't affect main program).
13880 - Fix an assert bug where a hidden service provider would fail if
13881 the first hop of his rendezvous circuit was down.
13882 - Hidden service operators now correctly handle version 1 style
13883 INTRODUCE1 cells (nobody generates them still, so not a critical
13885 - If do_hup fails, actually notice.
13886 - Handle more errnos from accept() without closing the listener.
13887 Some OpenBSD machines were closing their listeners because
13888 they ran out of file descriptors.
13889 - Send resolve cells to exit routers that are running a new
13890 enough version of the resolve code to work right.
13891 - Better handling of winsock includes on non-MSV win32 compilers.
13892 - Some people had wrapped their tor client/server in a script
13893 that would restart it whenever it died. This did not play well
13894 with our "shut down if your version is obsolete" code. Now people
13895 don't fetch a new directory if their local cached version is
13897 - Make our autogen.sh work on ksh as well as bash.
13900 - Hibernation: New config option "AccountingMaxKB" lets you
13901 set how many KBytes per month you want to allow your server to
13902 consume. Rather than spreading those bytes out evenly over the
13903 month, we instead hibernate for some of the month and pop up
13904 at a deterministic time, work until the bytes are consumed, then
13905 hibernate again. Config option "MonthlyAccountingStart" lets you
13906 specify which day of the month your billing cycle starts on.
13907 - Control interface: a separate program can now talk to your
13908 client/server over a socket, and get/set config options, receive
13909 notifications of circuits and streams starting/finishing/dying,
13910 bandwidth used, etc. The next step is to get some GUIs working.
13911 Let us know if you want to help out. See doc/control-spec.txt .
13912 - Ship a contrib/tor-control.py as an example script to interact
13913 with the control port.
13914 - "tor --hash-password zzyxz" will output a salted password for
13915 use in authenticating to the control interface.
13916 - New log format in config:
13917 "Log minsev[-maxsev] stdout|stderr|syslog" or
13918 "Log minsev[-maxsev] file /var/foo"
13921 - DirPolicy config option, to let people reject incoming addresses
13922 from their dirserver.
13923 - "tor --list-fingerprint" will list your identity key fingerprint
13925 - Add "pass" target for RedirectExit, to make it easier to break
13926 out of a sequence of RedirectExit rules.
13927 - Clients now generate a TLS cert too, in preparation for having
13928 them act more like real nodes.
13929 - Ship src/win32/ in the tarball, so people can use it to build.
13930 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
13932 - New "router-status" line in directory, to better bind each verified
13933 nickname to its identity key.
13934 - Deprecate unofficial config option abbreviations, and abbreviations
13935 not on the command line.
13936 - Add a pure-C tor-resolve implementation.
13937 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13938 1024) file descriptors.
13940 o Code security improvements, inspired by Ilja:
13941 - Replace sprintf with snprintf. (I think they were all safe, but
13943 - Replace strcpy/strncpy with strlcpy in more places.
13944 - Avoid strcat; use snprintf or strlcat instead.
13945 - snprintf wrapper with consistent (though not C99) overflow behavior.
13948 Changes in version 0.0.9pre4 - 2004-10-17
13949 o Bugfixes on 0.0.9pre3:
13950 - If the server doesn't specify an exit policy, use the real default
13951 exit policy, not reject *:*.
13952 - Ignore fascistfirewall when uploading/downloading hidden service
13953 descriptors, since we go through Tor for those; and when using
13954 an HttpProxy, since we assume it can reach them all.
13955 - When looking for an authoritative dirserver, use only the ones
13956 configured at boot. Don't bother looking in the directory.
13957 - The rest of the fix for get_default_conf_file() on older win32.
13958 - Make 'Routerfile' config option obsolete.
13961 - New 'MyFamily nick1,...' config option for a server to
13962 specify other servers that shouldn't be used in the same circuit
13963 with it. Only believed if nick1 also specifies us.
13964 - New 'NodeFamily nick1,nick2,...' config option for a client to
13965 specify nodes that it doesn't want to use in the same circuit.
13966 - New 'Redirectexit pattern address:port' config option for a
13967 server to redirect exit connections, e.g. to a local squid.
13970 Changes in version 0.0.9pre3 - 2004-10-13
13971 o Bugfixes on 0.0.8.1:
13972 - Better torrc example lines for dirbindaddress and orbindaddress.
13973 - Improved bounds checking on parsed ints (e.g. config options and
13974 the ones we find in directories.)
13975 - Better handling of size_t vs int, so we're more robust on 64
13977 - Fix the rest of the bug where a newly started OR would appear
13978 as unverified even after we've added his fingerprint and hupped
13980 - Fix a bug from 0.0.7: when read() failed on a stream, we would
13981 close it without sending back an end. So 'connection refused'
13982 would simply be ignored and the user would get no response.
13984 o Bugfixes on 0.0.9pre2:
13985 - Serving the cached-on-disk directory to people is bad. We now
13986 provide no directory until we've fetched a fresh one.
13987 - Workaround for bug on windows where cached-directories get crlf
13989 - Make get_default_conf_file() work on older windows too.
13990 - If we write a *:* exit policy line in the descriptor, don't write
13991 any more exit policy lines.
13994 - Use only 0.0.9pre1 and later servers for resolve cells.
13995 - Make the dirservers file obsolete.
13996 - Include a dir-signing-key token in directories to tell the
13997 parsing entity which key is being used to sign.
13998 - Remove the built-in bulky default dirservers string.
13999 - New config option "Dirserver %s:%d [fingerprint]", which can be
14000 repeated as many times as needed. If no dirservers specified,
14001 default to moria1,moria2,tor26.
14002 - Make moria2 advertise a dirport of 80, so people behind firewalls
14003 will be able to get a directory.
14004 - Http proxy support
14005 - Dirservers translate requests for http://%s:%d/x to /x
14006 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14007 be routed through this host.
14008 - Clients ask for /tor/x rather than /x for new enough dirservers.
14009 This way we can one day coexist peacefully with apache.
14010 - Clients specify a "Host: %s%d" http header, to be compatible
14011 with more proxies, and so running squid on an exit node can work.
14014 Changes in version 0.0.8.1 - 2004-10-13
14016 - Fix a seg fault that can be triggered remotely for Tor
14017 clients/servers with an open dirport.
14018 - Fix a rare assert trigger, where routerinfos for entries in
14019 our cpath would expire while we're building the path.
14020 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14021 - Fix a rare seg fault for people running hidden services on
14022 intermittent connections.
14023 - Fix a bug in parsing opt keywords with objects.
14024 - Fix a stale pointer assert bug when a stream detaches and
14026 - Fix a string format vulnerability (probably not exploitable)
14027 in reporting stats locally.
14028 - Fix an assert trigger: sometimes launching circuits can fail
14029 immediately, e.g. because too many circuits have failed recently.
14030 - Fix a compile warning on 64 bit platforms.
14033 Changes in version 0.0.9pre2 - 2004-10-03
14035 - Make fetching a cached directory work for 64-bit platforms too.
14036 - Make zlib.h a required header, not an optional header.
14039 Changes in version 0.0.9pre1 - 2004-10-01
14041 - Stop using separate defaults for no-config-file and
14042 empty-config-file. Now you have to explicitly turn off SocksPort,
14043 if you don't want it open.
14044 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14045 - Improve man page to mention more of the 0.0.8 features.
14046 - Fix a rare seg fault for people running hidden services on
14047 intermittent connections.
14048 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14050 - Fix more dns related bugs: send back resolve_failed and end cells
14051 more reliably when the resolve fails, rather than closing the
14052 circuit and then trying to send the cell. Also attach dummy resolve
14053 connections to a circuit *before* calling dns_resolve(), to fix
14054 a bug where cached answers would never be sent in RESOLVED cells.
14055 - When we run out of disk space, or other log writing error, don't
14056 crash. Just stop logging to that log and continue.
14057 - We were starting to daemonize before we opened our logs, so if
14058 there were any problems opening logs, we would complain to stderr,
14059 which wouldn't work, and then mysteriously exit.
14060 - Fix a rare bug where sometimes a verified OR would connect to us
14061 before he'd uploaded his descriptor, which would cause us to
14062 assign conn->nickname as though he's unverified. Now we look through
14063 the fingerprint list to see if he's there.
14064 - Fix a rare assert trigger, where routerinfos for entries in
14065 our cpath would expire while we're building the path.
14068 - Clients can ask dirservers for /dir.z to get a compressed version
14069 of the directory. Only works for servers running 0.0.9, of course.
14070 - Make clients cache directories and use them to seed their router
14071 lists at startup. This means clients have a datadir again.
14072 - Configuration infrastructure support for warning on obsolete
14074 - Respond to content-encoding headers by trying to uncompress as
14076 - Reply with a deflated directory when a client asks for "dir.z".
14077 We could use allow-encodings instead, but allow-encodings isn't
14078 specified in HTTP 1.0.
14079 - Raise the max dns workers from 50 to 100.
14080 - Discourage people from setting their dirfetchpostperiod more often
14081 than once per minute.
14082 - Protect dirservers from overzealous descriptor uploading -- wait
14083 10 seconds after directory gets dirty, before regenerating.
14086 Changes in version 0.0.8 - 2004-08-25
14087 o Port it to SunOS 5.9 / Athena
14090 Changes in version 0.0.8rc2 - 2004-08-20
14091 o Make it compile on cygwin again.
14092 o When picking unverified routers, skip those with low uptime and/or
14093 low bandwidth, depending on what properties you care about.
14096 Changes in version 0.0.8rc1 - 2004-08-18
14097 o Changes from 0.0.7.3:
14099 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14100 don't put it into the client dns cache.
14101 - If a begin failed due to exit policy, but we believe the IP address
14102 should have been allowed, switch that router to exitpolicy reject *:*
14103 until we get our next directory.
14105 - Clients choose nodes proportional to advertised bandwidth.
14106 - Avoid using nodes with low uptime as introduction points.
14107 - Handle servers with dynamic IP addresses: don't replace
14108 options->Address with the resolved one at startup, and
14109 detect our address right before we make a routerinfo each time.
14110 - 'FascistFirewall' option to pick dirservers and ORs on specific
14111 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14112 which ports are open. (Defaults to 80,443)
14113 - Be more aggressive about trying to make circuits when the network
14114 has changed (e.g. when you unsuspend your laptop).
14115 - Check for time skew on http headers; report date in response to
14117 - If the entrynode config line has only one node, don't pick it as
14119 - Add strict{entry|exit}nodes config options. If set to 1, then
14120 we refuse to build circuits that don't include the specified entry
14122 - OutboundBindAddress config option, to bind to a specific
14123 IP address for outgoing connect()s.
14124 - End truncated log entries (e.g. directories) with "[truncated]".
14126 o Patches to 0.0.8preX:
14128 - Patches to compile and run on win32 again (maybe)?
14129 - Fix crash when looking for ~/.torrc with no $HOME set.
14130 - Fix a race bug in the unit tests.
14131 - Handle verified/unverified name collisions better when new
14132 routerinfo's arrive in a directory.
14133 - Sometimes routers were getting entered into the stats before
14134 we'd assigned their identity_digest. Oops.
14135 - Only pick and establish intro points after we've gotten a
14138 - AllowUnverifiedNodes config option to let circuits choose no-name
14139 routers in entry,middle,exit,introduction,rendezvous positions.
14140 Allow middle and rendezvous positions by default.
14141 - Add a man page for tor-resolve.
14144 Changes in version 0.0.7.3 - 2004-08-12
14145 o Stop dnsworkers from triggering an assert failure when you
14146 ask them to resolve the host "".
14149 Changes in version 0.0.8pre3 - 2004-08-09
14150 o Changes from 0.0.7.2:
14151 - Allow multiple ORs with same nickname in routerlist -- now when
14152 people give us one identity key for a nickname, then later
14153 another, we don't constantly complain until the first expires.
14154 - Remember used bandwidth (both in and out), and publish 15-minute
14155 snapshots for the past day into our descriptor.
14156 - You can now fetch $DIRURL/running-routers to get just the
14157 running-routers line, not the whole descriptor list. (But
14158 clients don't use this yet.)
14159 - When people mistakenly use Tor as an http proxy, point them
14160 at the tor-doc.html rather than the INSTALL.
14161 - Remove our mostly unused -- and broken -- hex_encode()
14162 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14163 for pointing out this bug.)
14164 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14165 fewer problems with people using the wrong key.
14166 - Change the default exit policy to reject the default edonkey,
14167 kazaa, gnutella ports.
14168 - Add replace_file() to util.[ch] to handle win32's rename().
14170 o Changes from 0.0.8preX:
14171 - Fix two bugs in saving onion keys to disk when rotating, so
14172 hopefully we'll get fewer people using old onion keys.
14173 - Fix an assert error that was making SocksPolicy not work.
14174 - Be willing to expire routers that have an open dirport -- it's
14175 just the authoritative dirservers we want to not forget.
14176 - Reject tor-resolve requests for .onion addresses early, so we
14177 don't build a whole rendezvous circuit and then fail.
14178 - When you're warning a server that he's unverified, don't cry
14179 wolf unpredictably.
14180 - Fix a race condition: don't try to extend onto a connection
14181 that's still handshaking.
14182 - For servers in clique mode, require the conn to be open before
14183 you'll choose it for your path.
14184 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14185 end relay cell, etc.
14186 - Measure bandwidth capacity over the last 24 hours, not just 12
14187 - Bugfix: authoritative dirservers were making and signing a new
14188 directory for each client, rather than reusing the cached one.
14191 Changes in version 0.0.8pre2 - 2004-08-04
14192 o Changes from 0.0.7.2:
14194 - Check directory signature _before_ you decide whether you're
14195 you're running an obsolete version and should exit.
14196 - Check directory signature _before_ you parse the running-routers
14197 list to decide who's running or verified.
14198 - Bugfixes and features:
14199 - Check return value of fclose while writing to disk, so we don't
14200 end up with broken files when servers run out of disk space.
14201 - Log a warning if the user uses an unsafe socks variant, so people
14202 are more likely to learn about privoxy or socat.
14203 - Dirservers now include RFC1123-style dates in the HTTP headers,
14204 which one day we will use to better detect clock skew.
14206 o Changes from 0.0.8pre1:
14207 - Make it compile without warnings again on win32.
14208 - Log a warning if you're running an unverified server, to let you
14209 know you might want to get it verified.
14210 - Only pick a default nickname if you plan to be a server.
14213 Changes in version 0.0.8pre1 - 2004-07-23
14215 - Made our unit tests compile again on OpenBSD 3.5, and tor
14216 itself compile again on OpenBSD on a sparc64.
14217 - We were neglecting milliseconds when logging on win32, so
14218 everything appeared to happen at the beginning of each second.
14220 o Protocol changes:
14221 - 'Extend' relay cell payloads now include the digest of the
14222 intended next hop's identity key. Now we can verify that we're
14223 extending to the right router, and also extend to routers we
14224 hadn't heard of before.
14227 - Tor nodes can now act as relays (with an advertised ORPort)
14228 without being manually verified by the dirserver operators.
14229 - Uploaded descriptors of unverified routers are now accepted
14230 by the dirservers, and included in the directory.
14231 - Verified routers are listed by nickname in the running-routers
14232 list; unverified routers are listed as "$<fingerprint>".
14233 - We now use hash-of-identity-key in most places rather than
14234 nickname or addr:port, for improved security/flexibility.
14235 - To avoid Sybil attacks, paths still use only verified servers.
14236 But now we have a chance to play around with hybrid approaches.
14237 - Nodes track bandwidth usage to estimate capacity (not used yet).
14238 - ClientOnly option for nodes that never want to become servers.
14239 - Directory caching.
14240 - "AuthoritativeDir 1" option for the official dirservers.
14241 - Now other nodes (clients and servers) will cache the latest
14242 directory they've pulled down.
14243 - They can enable their DirPort to serve it to others.
14244 - Clients will pull down a directory from any node with an open
14245 DirPort, and check the signature/timestamp correctly.
14246 - Authoritative dirservers now fetch directories from other
14247 authdirservers, to stay better synced.
14248 - Running-routers list tells who's down also, along with noting
14249 if they're verified (listed by nickname) or unverified (listed
14251 - Allow dirservers to serve running-router list separately.
14252 This isn't used yet.
14253 - ORs connect-on-demand to other ORs
14254 - If you get an extend cell to an OR you're not connected to,
14255 connect, handshake, and forward the create cell.
14256 - The authoritative dirservers stay connected to everybody,
14257 and everybody stays connected to 0.0.7 servers, but otherwise
14258 clients/servers expire unused connections after 5 minutes.
14259 - When servers get a sigint, they delay 30 seconds (refusing new
14260 connections) then exit. A second sigint causes immediate exit.
14261 - File and name management:
14262 - Look for .torrc if no CONFDIR "torrc" is found.
14263 - If no datadir is defined, then choose, make, and secure ~/.tor
14265 - If torrc not found, exitpolicy reject *:*.
14266 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14267 - If no nickname is defined, derive default from hostname.
14268 - Rename secret key files, e.g. identity.key -> secret_id_key,
14269 to discourage people from mailing their identity key to tor-ops.
14270 - Refuse to build a circuit before the directory has arrived --
14271 it won't work anyway, since you won't know the right onion keys
14273 - Try other dirservers immediately if the one you try is down. This
14274 should tolerate down dirservers better now.
14275 - Parse tor version numbers so we can do an is-newer-than check
14276 rather than an is-in-the-list check.
14277 - New socks command 'resolve', to let us shim gethostbyname()
14279 - A 'tor_resolve' script to access the socks resolve functionality.
14280 - A new socks-extensions.txt doc file to describe our
14281 interpretation and extensions to the socks protocols.
14282 - Add a ContactInfo option, which gets published in descriptor.
14283 - Publish OR uptime in descriptor (and thus in directory) too.
14284 - Write tor version at the top of each log file
14285 - New docs in the tarball:
14287 - Document that you should proxy your SSL traffic too.
14290 Changes in version 0.0.7.2 - 2004-07-07
14291 o A better fix for the 0.0.0.0 problem, that will hopefully
14292 eliminate the remaining related assertion failures.
14295 Changes in version 0.0.7.1 - 2004-07-04
14296 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14297 since internally we use 0.0.0.0 to signify "not yet resolved".
14300 Changes in version 0.0.7 - 2004-06-07
14301 o Updated the man page to reflect the new features.
14304 Changes in version 0.0.7rc2 - 2004-06-06
14305 o Changes from 0.0.7rc1:
14306 - Make it build on Win32 again.
14307 o Changes from 0.0.6.2:
14308 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14312 Changes in version 0.0.7rc1 - 2004-06-02
14314 - On sighup, we were adding another log without removing the first
14315 one. So log messages would get duplicated n times for n sighups.
14316 - Several cases of using a connection after we'd freed it. The
14317 problem was that connections that are pending resolve are in both
14318 the pending_resolve tree, and also the circuit's resolving_streams
14319 list. When you want to remove one, you must remove it from both.
14320 - Fix a double-mark-for-close where an end cell arrived for a
14321 resolving stream, and then the resolve failed.
14322 - Check directory signatures based on name of signer, not on whom
14323 we got the directory from. This will let us cache directories more
14326 - Crank up some of our constants to handle more users.
14329 Changes in version 0.0.7pre1 - 2004-06-02
14330 o Fixes for crashes and other obnoxious bugs:
14331 - Fix an epipe bug: sometimes when directory connections failed
14332 to connect, we would give them a chance to flush before closing
14334 - When we detached from a circuit because of resolvefailed, we
14335 would immediately try the same circuit twice more, and then
14336 give up on the resolve thinking we'd tried three different
14338 - Limit the number of intro circuits we'll attempt to build for a
14339 hidden service per 15-minute period.
14340 - Check recommended-software string *early*, before actually parsing
14341 the directory. Thus we can detect an obsolete version and exit,
14342 even if the new directory format doesn't parse.
14343 o Fixes for security bugs:
14344 - Remember which nodes are dirservers when you startup, and if a
14345 random OR enables his dirport, don't automatically assume he's
14346 a trusted dirserver.
14348 - Directory connections were asking the wrong poll socket to
14349 start writing, and not asking themselves to start writing.
14350 - When we detached from a circuit because we sent a begin but
14351 didn't get a connected, we would use it again the first time;
14352 but after that we would correctly switch to a different one.
14353 - Stop warning when the first onion decrypt attempt fails; they
14354 will sometimes legitimately fail now that we rotate keys.
14355 - Override unaligned-access-ok check when $host_cpu is ia64 or
14356 arm. Apparently they allow it but the kernel whines.
14357 - Dirservers try to reconnect periodically too, in case connections
14359 - Fix some memory leaks in directory servers.
14360 - Allow backslash in Win32 filenames.
14361 - Made Tor build complain-free on FreeBSD, hopefully without
14362 breaking other BSD builds. We'll see.
14364 - Doxygen markup on all functions and global variables.
14365 - Make directory functions update routerlist, not replace it. So
14366 now directory disagreements are not so critical a problem.
14367 - Remove the upper limit on number of descriptors in a dirserver's
14368 directory (not that we were anywhere close).
14369 - Allow multiple logfiles at different severity ranges.
14370 - Allow *BindAddress to specify ":port" rather than setting *Port
14371 separately. Allow multiple instances of each BindAddress config
14372 option, so you can bind to multiple interfaces if you want.
14373 - Allow multiple exit policy lines, which are processed in order.
14374 Now we don't need that huge line with all the commas in it.
14375 - Enable accept/reject policies on SOCKS connections, so you can bind
14376 to 0.0.0.0 but still control who can use your OP.
14379 Changes in version 0.0.6.2 - 2004-05-16
14380 o Our integrity-checking digest was checking only the most recent cell,
14381 not the previous cells like we'd thought.
14382 Thanks to Stefan Mark for finding the flaw!
14385 Changes in version 0.0.6.1 - 2004-05-06
14386 o Fix two bugs in our AES counter-mode implementation (this affected
14387 onion-level stream encryption, but not TLS-level). It turns
14388 out we were doing something much more akin to a 16-character
14389 polyalphabetic cipher. Oops.
14390 Thanks to Stefan Mark for finding the flaw!
14391 o Retire moria3 as a directory server, and add tor26 as a directory
14395 Changes in version 0.0.6 - 2004-05-02
14396 [version bump only]
14399 Changes in version 0.0.6rc4 - 2004-05-01
14400 o Update the built-in dirservers list to use the new directory format
14401 o Fix a rare seg fault: if a node offering a hidden service attempts
14402 to build a circuit to Alice's rendezvous point and fails before it
14403 reaches the last hop, it retries with a different circuit, but
14405 o Handle windows socket errors correctly.
14408 Changes in version 0.0.6rc3 - 2004-04-28
14409 o Don't expire non-general excess circuits (if we had enough
14410 circuits open, we were expiring rendezvous circuits -- even
14411 when they had a stream attached. oops.)
14412 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14413 o Better debugging for tls errors
14414 o Some versions of openssl have an SSL_pending function that erroneously
14415 returns bytes when there is a non-application record pending.
14416 o Set Content-Type on the directory and hidserv descriptor.
14417 o Remove IVs from cipher code, since AES-ctr has none.
14418 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14419 o We were using an array of length zero in a few places.
14420 o win32's gethostbyname can't resolve an IP to an IP.
14421 o win32's close can't close a socket.
14424 Changes in version 0.0.6rc2 - 2004-04-26
14425 o Fix a bug where we were closing tls connections intermittently.
14426 It turns out openssl keeps its errors around -- so if an error
14427 happens, and you don't ask about it, and then another openssl
14428 operation happens and succeeds, and you ask if there was an error,
14429 it tells you about the first error. Fun fun.
14430 o Fix a bug that's been lurking since 27 may 03 (!)
14431 When passing back a destroy cell, we would use the wrong circ id.
14432 'Mostly harmless', but still worth fixing.
14433 o Since we don't support truncateds much, don't bother sending them;
14434 just close the circ.
14435 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14436 o don't crash if a conn that sent a begin has suddenly lost its circuit
14437 (this was quite rare).
14440 Changes in version 0.0.6rc1 - 2004-04-25
14441 o We now rotate link (tls context) keys and onion keys.
14442 o CREATE cells now include oaep padding, so you can tell
14443 if you decrypted them correctly.
14444 o Add bandwidthburst to server descriptor.
14445 o Directories now say which dirserver signed them.
14446 o Use a tor_assert macro that logs failed assertions too.
14449 Changes in version 0.0.6pre5 - 2004-04-18
14450 o changes from 0.0.6pre4:
14451 - make tor build on broken freebsd 5.2 installs
14452 - fix a failed assert when you try an intro point, get a nack, and try
14453 a second one and it works.
14454 - when alice uses a port that the hidden service doesn't accept,
14455 it now sends back an end cell (denied by exit policy). otherwise
14456 alice would just have to wait to time out.
14457 - fix another rare bug: when we had tried all the intro
14458 points for a hidden service, we fetched the descriptor
14459 again, but we left our introcirc thinking it had already
14460 sent an intro, so it kept waiting for a response...
14461 - bugfix: when you sleep your hidden-service laptop, as soon
14462 as it wakes up it tries to upload a service descriptor, but
14463 socketpair fails for some reason (localhost not up yet?).
14464 now we simply give up on that upload, and we'll try again later.
14465 i'd still like to find the bug though.
14466 - if an intro circ waiting for an ack dies before getting one, then
14468 - we were reusing stale service descriptors and refetching usable
14472 Changes in version 0.0.6pre4 - 2004-04-14
14473 o changes from 0.0.6pre3:
14474 - when bob fails to connect to the rendezvous point, and his
14475 circ didn't fail because of the rendezvous point itself, then
14476 he retries a couple of times
14477 - we expire introduction and rendezvous circs more thoroughly
14478 (sometimes they were hanging around forever)
14479 - we expire unattached rendezvous streams that have been around
14480 too long (they were sticking around forever).
14481 - fix a measly fencepost error that was crashing everybody with
14485 Changes in version 0.0.6pre3 - 2004-04-14
14486 o changes from 0.0.6pre2:
14487 - make hup work again
14488 - fix some memory leaks for dirservers
14489 - allow more skew in rendezvous descriptor timestamps, to help
14490 handle people like blanu who don't know what time it is
14491 - normal circs are 3 hops, but some rend/intro circs are 4, if
14492 the initiator doesn't get to choose the last hop
14493 - send acks for introductions, so alice can know whether to try
14495 - bob publishes intro points more correctly
14496 o changes from 0.0.5:
14497 - fix an assert trigger that's been plaguing us since the days
14498 of 0.0.2prexx (thanks weasel!)
14499 - retry stream correctly when we fail to connect because of
14500 exit-policy-reject (should try another) or can't-resolve-address
14501 (also should try another, because dns on random internet servers
14503 - when we hup a dirserver and we've *removed* a server from the
14504 approved-routers list, now we remove that server from the
14505 in-memory directories too
14508 Changes in version 0.0.6pre2 - 2004-04-08
14509 o We fixed our base32 implementation. Now it works on all architectures.
14512 Changes in version 0.0.6pre1 - 2004-04-08
14514 - Hidden services and rendezvous points are implemented. Go to
14515 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14516 hidden services. (This only works via a socks4a proxy such as
14517 Privoxy, and currently it's quite slow.)
14520 Changes in version 0.0.5 - 2004-03-30
14521 [version bump only]
14524 Changes in version 0.0.5rc3 - 2004-03-29
14525 o Install torrc as torrc.sample -- we no longer clobber your
14527 o Re-enable recommendedversion checking (we broke it in rc2, oops)
14528 o Add in a 'notice' log level for things the operator should hear
14529 but that aren't warnings
14532 Changes in version 0.0.5rc2 - 2004-03-29
14533 o Hold socks connection open until reply is flushed (if possible)
14534 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14535 the dns farm to do it.
14536 o Fix c99 aliasing warnings in rephist.c
14537 o Don't include server descriptors that are older than 24 hours in the
14539 o Give socks 'reject' replies their whole 15s to attempt to flush,
14540 rather than seeing the 60s timeout and assuming the flush had failed.
14541 o Clean automake droppings from the cvs repository
14544 Changes in version 0.0.5rc1 - 2004-03-28
14545 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14546 o Only build circuits after we've fetched the directory: clients were
14547 using only the directory servers before they'd fetched a directory.
14548 This also means longer startup time; so it goes.
14549 o Fix an assert trigger where an OP would fail to handshake, and we'd
14550 expect it to have a nickname.
14551 o Work around a tsocks bug: do a socks reject when AP connection dies
14552 early, else tsocks goes into an infinite loop.
14555 Changes in version 0.0.4 - 2004-03-26
14556 o When connecting to a dirserver or OR and the network is down,
14560 Changes in version 0.0.3 - 2004-03-26
14561 o Warn and fail if server chose a nickname with illegal characters
14562 o Port to Solaris and Sparc:
14563 - include missing header fcntl.h
14564 - have autoconf find -lsocket -lnsl automatically
14565 - deal with hardware word alignment
14566 - make uname() work (solaris has a different return convention)
14567 - switch from using signal() to sigaction()
14568 o Preliminary work on reputation system:
14569 - Keep statistics on success/fail of connect attempts; they're published
14570 by kill -USR1 currently.
14571 - Add a RunTesting option to try to learn link state by creating test
14572 circuits, even when SocksPort is off.
14573 - Remove unused open circuits when there are too many.
14576 Changes in version 0.0.2 - 2004-03-19
14577 - Include strlcpy and strlcat for safer string ops
14578 - define INADDR_NONE so we compile (but still not run) on solaris
14581 Changes in version 0.0.2pre27 - 2004-03-14
14583 - Allow internal tor networks (we were rejecting internal IPs,
14584 now we allow them if they're set explicitly).
14585 - And fix a few endian issues.
14588 Changes in version 0.0.2pre26 - 2004-03-14
14590 - If a stream times out after 15s without a connected cell, don't
14591 try that circuit again: try a new one.
14592 - Retry streams at most 4 times. Then give up.
14593 - When a dirserver gets a descriptor from an unknown router, it
14594 logs its fingerprint (so the dirserver operator can choose to
14595 accept it even without mail from the server operator).
14596 - Inform unapproved servers when we reject their descriptors.
14597 - Make tor build on Windows again. It works as a client, who knows
14599 - Clearer instructions in the torrc for how to set up a server.
14600 - Be more efficient about reading fd's when our global token bucket
14601 (used for rate limiting) becomes empty.
14603 - Stop asserting that computers always go forward in time. It's
14605 - When we sent a cell (e.g. destroy) and then marked an OR connection
14606 expired, we might close it before finishing a flush if the other
14607 side isn't reading right then.
14608 - Don't allow dirservers to start if they haven't defined
14609 RecommendedVersions
14610 - We were caching transient dns failures. Oops.
14611 - Prevent servers from publishing an internal IP as their address.
14612 - Address a strcat vulnerability in circuit.c
14615 Changes in version 0.0.2pre25 - 2004-03-04
14617 - Put the OR's IP in its router descriptor, not its fqdn. That way
14618 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14621 - If the user typed in an address that didn't resolve, the server
14625 Changes in version 0.0.2pre24 - 2004-03-03
14627 - Fix an assertion failure in dns.c, where we were trying to dequeue
14628 a pending dns resolve even if it wasn't pending
14629 - Fix a spurious socks5 warning about still trying to write after the
14630 connection is finished.
14631 - Hold certain marked_for_close connections open until they're finished
14632 flushing, rather than losing bytes by closing them too early.
14633 - Correctly report the reason for ending a stream
14634 - Remove some duplicate calls to connection_mark_for_close
14635 - Put switch_id and start_daemon earlier in the boot sequence, so it
14636 will actually try to chdir() to options.DataDirectory
14637 - Make 'make test' exit(1) if a test fails; fix some unit tests
14638 - Make tor fail when you use a config option it doesn't know about,
14639 rather than warn and continue.
14640 - Make --version work
14641 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14644 Changes in version 0.0.2pre23 - 2004-02-29
14646 - Print a statement when the first circ is finished, so the user
14647 knows it's working.
14648 - If a relay cell is unrecognized at the end of the circuit,
14649 send back a destroy. (So attacks to mutate cells are more
14651 - New config option 'excludenodes' to avoid certain nodes for circuits.
14652 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
14653 so you can collect coredumps there.
14655 - Fix a bug in tls flushing where sometimes data got wedged and
14656 didn't flush until more data got sent. Hopefully this bug was
14657 a big factor in the random delays we were seeing.
14658 - Make 'connected' cells include the resolved IP, so the client
14659 dns cache actually gets populated.
14660 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14661 - When we time-out on a stream and detach from the circuit, send an
14662 end cell down it first.
14663 - Only warn about an unknown router (in exitnodes, entrynodes,
14664 excludenodes) after we've fetched a directory.
14667 Changes in version 0.0.2pre22 - 2004-02-26
14669 - Servers publish less revealing uname information in descriptors.
14670 - More memory tracking and assertions, to crash more usefully when
14672 - If the default torrc isn't there, just use some default defaults.
14673 Plus provide an internal dirservers file if they don't have one.
14674 - When the user tries to use Tor as an http proxy, give them an http
14675 501 failure explaining that we're a socks proxy.
14676 - Dump a new router.desc on hup, to help confused people who change
14677 their exit policies and then wonder why router.desc doesn't reflect
14679 - Clean up the generic tor.sh init script that we ship with.
14681 - If the exit stream is pending on the resolve, and a destroy arrives,
14682 then the stream wasn't getting removed from the pending list. I
14683 think this was the one causing recent server crashes.
14684 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14685 - When it couldn't resolve any dirservers, it was useless from then on.
14686 Now it reloads the RouterFile (or default dirservers) if it has no
14688 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14689 many users don't even *have* a /usr/local/sbin/.
14692 Changes in version 0.0.2pre21 - 2004-02-18
14694 - There's a ChangeLog file that actually reflects the changelog.
14695 - There's a 'torify' wrapper script, with an accompanying
14696 tor-tsocks.conf, that simplifies the process of using tsocks for
14697 tor. It even has a man page.
14698 - The tor binary gets installed to sbin rather than bin now.
14699 - Retry streams where the connected cell hasn't arrived in 15 seconds
14700 - Clean up exit policy handling -- get the default out of the torrc,
14701 so we can update it without forcing each server operator to fix
14703 - Allow imaps and pop3s in default exit policy
14705 - Prevent picking middleman nodes as the last node in the circuit
14708 Changes in version 0.0.2pre20 - 2004-01-30
14710 - We now have a deb package, and it's in debian unstable. Go to
14711 it, apt-getters. :)
14712 - I've split the TotalBandwidth option into BandwidthRate (how many
14713 bytes per second you want to allow, long-term) and
14714 BandwidthBurst (how many bytes you will allow at once before the cap
14715 kicks in). This better token bucket approach lets you, say, set
14716 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14717 performance while not exceeding your monthly bandwidth quota.
14718 - Push out a tls record's worth of data once you've got it, rather
14719 than waiting until you've read everything waiting to be read. This
14720 may improve performance by pipelining better. We'll see.
14721 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14722 from failed circuits (if they haven't been connected yet) and attach
14724 - Expire old streams that haven't managed to connect. Some day we'll
14725 have them reattach to new circuits instead.
14728 - Fix several memory leaks that were causing servers to become bloated
14730 - Fix a few very rare assert triggers. A few more remain.
14731 - Setuid to User _before_ complaining about running as root.
14734 Changes in version 0.0.2pre19 - 2004-01-07
14736 - Fix deadlock condition in dns farm. We were telling a child to die by
14737 closing the parent's file descriptor to him. But newer children were
14738 inheriting the open file descriptor from the parent, and since they
14739 weren't closing it, the socket never closed, so the child never read
14740 eof, so he never knew to exit. Similarly, dns workers were holding
14741 open other sockets, leading to all sorts of chaos.
14742 - New cleaner daemon() code for forking and backgrounding.
14743 - If you log to a file, it now prints an entry at the top of the
14744 logfile so you know it's working.
14745 - The onionskin challenge length was 30 bytes longer than necessary.
14746 - Started to patch up the spec so it's not quite so out of date.
14749 Changes in version 0.0.2pre18 - 2004-01-02
14751 - Fix endian issues with the 'integrity' field in the relay header.
14752 - Fix a potential bug where connections in state
14753 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14756 Changes in version 0.0.2pre17 - 2003-12-30
14758 - Made --debuglogfile (or any second log file, actually) work.
14759 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14760 adversary could force us into an infinite loop.
14763 - Each onionskin handshake now includes a hash of the computed key,
14764 to prove the server's identity and help perfect forward secrecy.
14765 - Changed cell size from 256 to 512 bytes (working toward compatibility
14767 - Changed cell length to 2 bytes, and moved it to the relay header.
14768 - Implemented end-to-end integrity checking for the payloads of
14770 - Separated streamid from 'recognized' (otherwise circuits will get
14771 messed up when we try to have streams exit from the middle). We
14772 use the integrity-checking to confirm that a cell is addressed to
14774 - Randomize the initial circid and streamid values, so an adversary who
14775 breaks into a node can't learn how many circuits or streams have
14779 Changes in version 0.0.2pre16 - 2003-12-14
14781 - Fixed a bug that made HUP trigger an assert
14782 - Fixed a bug where a circuit that immediately failed wasn't being
14783 counted as a failed circuit in counting retries.
14786 - Now we close the circuit when we get a truncated cell: otherwise we're
14787 open to an anonymity attack where a bad node in the path truncates
14788 the circuit and then we open streams at him.
14789 - Add port ranges to exit policies
14790 - Add a conservative default exit policy
14791 - Warn if you're running tor as root
14792 - on HUP, retry OR connections and close/rebind listeners
14793 - options.EntryNodes: try these nodes first when picking the first node
14794 - options.ExitNodes: if your best choices happen to include any of
14795 your preferred exit nodes, you choose among just those preferred
14797 - options.ExcludedNodes: nodes that are never picked in path building
14800 Changes in version 0.0.2pre15 - 2003-12-03
14801 o Robustness and bugfixes:
14802 - Sometimes clients would cache incorrect DNS resolves, which would
14803 really screw things up.
14804 - An OP that goes offline would slowly leak all its sockets and stop
14806 - A wide variety of bugfixes in exit node selection, exit policy
14807 handling, and processing pending streams when a new circuit is
14809 - Pick nodes for a path only from those the directory says are up
14810 - Choose randomly from all running dirservers, not always the first one
14811 - Increase allowed http header size for directory fetch.
14812 - Stop writing to stderr (if we're daemonized it will be closed).
14813 - Enable -g always, so cores will be more useful to me.
14814 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
14817 - Wrote a man page. It lists commonly used options.
14820 - Change default loglevel to warn.
14821 - Make PidFile default to null rather than littering in your CWD.
14822 - OnionRouter config option is now obsolete. Instead it just checks
14824 - Moved to a single unified torrc file for both clients and servers.
14827 Changes in version 0.0.2pre14 - 2003-11-29
14828 o Robustness and bugfixes:
14829 - Force the admin to make the DataDirectory himself
14830 - to get ownership/permissions right
14831 - so clients no longer make a DataDirectory and then never use it
14832 - fix bug where a client who was offline for 45 minutes would never
14833 pull down a directory again
14834 - fix (or at least hide really well) the dns assert bug that was
14835 causing server crashes
14836 - warnings and improved robustness wrt clockskew for certs
14837 - use the native daemon(3) to daemonize, when available
14838 - exit if bind() fails
14839 - exit if neither socksport nor orport is defined
14840 - include our own tor_timegm (Win32 doesn't have its own)
14841 - bugfix for win32 with lots of connections
14842 - fix minor bias in PRNG
14843 - make dirserver more robust to corrupt cached directory
14846 - Wrote the design document (woo)
14848 o Circuit building and exit policies:
14849 - Circuits no longer try to use nodes that the directory has told them
14851 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
14852 bitcounts (18.0.0.0/8).
14853 - Make AP connections standby for a circuit if no suitable circuit
14854 exists, rather than failing
14855 - Circuits choose exit node based on addr/port, exit policies, and
14856 which AP connections are standing by
14857 - Bump min pathlen from 2 to 3
14858 - Relay end cells have a payload to describe why the stream ended.
14859 - If the stream failed because of exit policy, try again with a new
14861 - Clients have a dns cache to remember resolved addresses.
14862 - Notice more quickly when we have no working circuits
14865 - APPort is now called SocksPort
14866 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
14868 - RecommendedVersions is now a config variable rather than
14869 hardcoded (for dirservers)
14870 - Reloads config on HUP
14871 - Usage info on -h or --help
14872 - If you set User and Group config vars, it'll setu/gid to them.
14875 Changes in version 0.0.2pre13 - 2003-10-19
14876 o General stability:
14877 - SSL_write no longer fails when it returns WANTWRITE and the number
14878 of bytes in the buf has changed by the next SSL_write call.
14879 - Fix segfault fetching directory when network is down
14880 - Fix a variety of minor memory leaks
14881 - Dirservers reload the fingerprints file on HUP, so I don't have
14882 to take down the network when I approve a new router
14883 - Default server config file has explicit Address line to specify fqdn
14886 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
14887 - Make listener connections not ever alloc bufs
14889 o Autoconf improvements:
14890 - don't clobber an external CFLAGS in ./configure
14891 - Make install now works
14892 - create var/lib/tor on make install
14893 - autocreate a tor.sh initscript to help distribs
14894 - autocreate the torrc and sample-server-torrc with correct paths
14896 o Log files and Daemonizing now work:
14897 - If --DebugLogFile is specified, log to it at -l debug
14898 - If --LogFile is specified, use it instead of commandline
14899 - If --RunAsDaemon is set, tor forks and backgrounds on startup