2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.4.x - 2013-11-xx
7 The Tor 0.2.4 release series is dedicated to [...]
9 Tor 0.2.4.x, the first stable release in the 0.2.4 branch, features
12 o Major features (new circuit handshake):
13 - Tor now supports a new circuit extension handshake designed by Ian
14 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
15 circuit extension handshake, later called "TAP", was a bit slow
16 (especially on the relay side), had a fragile security proof, and
17 used weaker keys than we'd now prefer. The new circuit handshake
18 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
19 function, making it significantly more secure than the older
20 handshake, and significantly faster. Tor can use one of two built-in
21 pure-C curve25519-donna implementations by Adam Langley, or it
22 can link against the "nacl" library for a tuned version if present.
24 The built-in version is very fast for 64-bit systems when building
25 with GCC. The built-in 32-bit version is still faster than the
26 old TAP protocol, but using libnacl is better on most such hosts.
28 Implements proposal 216; closes ticket 7202.
30 o Major features (better link encryption):
31 - Relays can now enable the ECDHE TLS ciphersuites when available
32 and appropriate. These ciphersuites let us negotiate forward-secure
33 TLS secret keys more safely and more efficiently than with our
34 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
35 public relays prefer the (faster) P224 group, and bridges prefer
36 the (more common) P256 group; you can override this with the
39 This feature requires clients running 0.2.3.17-beta or later,
40 and requires both sides to be running OpenSSL 1.0.0 or later
41 with ECC support. OpenSSL 1.0.1, with the compile-time option
42 "enable-ec_nistp_64_gcc_128", is highly recommended.
44 Implements the relay side of proposal 198; closes ticket 7200.
46 o Major features (relay performance):
47 - Instead of limiting the number of queued onionskins (aka circuit
48 create requests) to a fixed, hard-to-configure number, we limit
49 the size of the queue based on how many we expect to be able to
50 process in a given amount of time. We estimate the time it will
51 take to process an onionskin based on average processing time
52 of previous onionskins. Closes ticket 7291. You'll never have to
53 configure MaxOnionsPending again.
54 - Relays process the new "NTor" circuit-level handshake requests
55 with higher priority than the old "TAP" circuit-level handshake
56 requests. We still process some TAP requests to not totally starve
57 0.2.3 clients when NTor becomes popular. A new consensus parameter
58 "NumNTorsPerTAP" lets us tune the balance later if we need to.
59 Implements ticket 9574.
61 o Major features (client bootstrapping resilience):
62 - Add a new "FallbackDir" torrc option to use when we can't use
63 a directory mirror from the consensus (either because we lack a
64 consensus, or because they're all down). Currently, all authorities
65 are fallbacks by default, and there are no other default fallbacks,
66 but that will change. This option will allow us to give clients a
67 longer list of servers to try to get a consensus from when first
68 connecting to the Tor network, and thereby reduce load on the
69 directory authorities. Implements proposal 206, "Preconfigured
70 directory sources for bootstrapping". We also removed the old
71 "FallbackNetworkstatus" option, since we never got it working well
72 enough to use it. Closes bug 572.
73 - If we have no circuits open, use a relaxed timeout (the
74 95-percentile cutoff) until a circuit succeeds. This heuristic
75 should allow Tor to succeed at building circuits even when the
76 network connection drastically changes. Should help with bug 3443.
78 o Major features (use of guards):
79 - Preliminary support for directory guards (proposal 207): when
80 possible, clients now use their entry guards for non-anonymous
81 directory requests. This can help prevent client enumeration. Note
82 that this behavior only works when we have a usable consensus
83 directory, and when options about what to download are more or less
84 standard. In the future we should re-bootstrap from our guards,
85 rather than re-bootstrapping from the preconfigured list of
86 directory sources that ships with Tor. Resolves ticket 6526.
87 - Raise the default time that a client keeps an entry guard from
88 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
89 2012 paper. (We would make it even longer, but we need better client
90 load balancing first.) Also, make the guard lifetime controllable
91 via a new GuardLifetime torrc option and a GuardLifetime consensus
92 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
94 o Major features (bridges with pluggable transports):
95 - Bridges now report the pluggable transports they support to the
96 bridge authority, so it can pass the supported transports on to
97 bridgedb and/or eventually do reachability testing. Implements
99 - Automatically forward the TCP ports of pluggable transport
100 proxies using tor-fw-helper if PortForwarding is enabled. Implements
103 o Major features (geoip database):
104 - Maxmind began labelling Tor relays as being in country "A1",
105 which breaks by-country node selection inside Tor. Now we use a
106 script to replace "A1" ("Anonymous Proxy") entries in our geoip
107 file with real country codes. This script fixes about 90% of "A1"
108 entries automatically and uses manual country code assignments to
109 fix the remaining 10%. See src/config/README.geoip for details.
111 - Add GeoIP database for IPv6 addresses. The new config option
113 - Update to the August 7 2013 Maxmind GeoLite Country database.
115 o Major features (IPv6):
116 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
117 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
118 to happen. Implements ticket 5535.
119 - All kind of relays, not just bridges, can now advertise an IPv6
120 OR port. Implements ticket 6362.
121 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
122 connectivity, then set the IPv6Exit flag to 1. Also make sure your
123 exit policy reads as you would like: the address * applies to all
124 address families, whereas *4 is IPv4 address only, and *6 is IPv6
125 addresses only. On the client side, you'll need to wait for enough
126 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
127 and use Socks5. Closes ticket 5547, implements proposal 117 as
128 revised in proposal 208.
129 - Bridge authorities now accept IPv6 bridge addresses and include
130 them in network status documents. Implements ticket 5534.
131 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
133 o Major features (directory authorities):
134 - Directory authorities now prefer using measured bandwidths to
135 advertised ones when computing flags and thresholds. Resolves
137 - Directory authorities that vote measured bandwidths about more
138 than a threshold number of relays now treat relays with
139 unmeasured bandwidths as having bandwidth 0 when computing their
140 flags. Resolves ticket 8435.
141 - Directory authorities now support a new consensus method (17)
142 where they cap the published bandwidth of relays for which
143 insufficient bandwidth measurements exist. Fixes part of bug 2286.
144 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
145 serve any v2 directory information. Now we can test disabling the
146 old deprecated v2 directory format, and see whether doing so has
147 any effect on network load. Begins to fix bug 6783.
149 o Major features (build and portability):
150 - Switch to a nonrecursive Makefile structure. Now instead of each
151 Makefile.am invoking other Makefile.am's, there is a master
152 Makefile.am that includes the others. This change makes our build
153 process slightly more maintainable, and improves parallelism for
154 building with make -j. Original patch by Stewart Smith; various
155 fixes by Jim Meyering.
156 - Where available, we now use automake's "silent" make rules by
157 default, so that warnings are easier to spot. You can get the old
158 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
159 - Resume building correctly with MSVC and Makefile.nmake. This patch
160 resolves numerous bugs and fixes reported by ultramage, including
161 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
164 - Switch to a completely time-invariant approach for picking nodes
165 weighted by bandwidth. Our old approach would run through the
166 part of the loop after it had made its choice slightly slower
167 than it ran through the part of the loop before it had made its
168 choice. Addresses ticket 6538.
169 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
170 by tor2web clients allows hidden services to identify tor2web
171 clients through their repeated selection of the same rendezvous
172 and introduction point circuit endpoints (their guards). Resolves
175 o Major bugfixes (relay denial of service):
176 - When we have too much memory queued in circuits (according to a new
177 MaxMemInCellQueues option), close the circuits consuming the most
178 memory. This prevents us from running out of memory as a relay if
179 circuits fill up faster than they can be drained. Fixes bug 9063;
180 bugfix on the 54th commit of Tor. This bug is a further fix beyond
181 bug 6252, whose fix was merged into 0.2.3.21-rc.
182 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
183 ID: these could be used to create unexpected streams and circuits
184 which would count as "present" to some parts of Tor but "absent"
185 to others, leading to zombie circuits and streams or to a bandwidth
186 denial-of-service. Fixes bug 7889; bugfix on every released version
187 of Tor. Reported by "oftc_must_be_destroyed".
188 - Avoid a bug where our response to TLS renegotiation under certain
189 network conditions could lead to a busy-loop, with 100% CPU
190 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
192 o Major bugfixes (asserts, crashes, leaks):
193 - Avoid a memory leak where we would leak a consensus body when we
194 find that a consensus which we couldn't previously verify due to
195 missing certificates is now verifiable. Fixes bug 8719; bugfix
197 - Fix a memory leak that would occur whenever a configuration
198 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
199 - Prevent the get_freelists() function from running off the end of
200 the list of freelists if it somehow gets an unrecognized
201 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
203 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
204 when an exit connection with optimistic data succeeds immediately
205 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
208 o Major bugfixes (relay rate limiting):
209 - When a TLS write is partially successful but incomplete, remember
210 that the flushed part has been flushed, and notice that bytes were
211 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
212 bugfix on Tor 0.1.0.5-rc.
213 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
214 to 1GB/1GB. The previous defaults were intended to be "basically
215 infinite", but it turns out they're now limiting our 100mbit+
216 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
217 last time we raised it).
219 o Major bugfixes (client-side privacy):
220 - When we mark a circuit as unusable for new circuits, have it
221 continue to be unusable for new circuits even if MaxCircuitDirtiness
222 is increased too much at the wrong time, or the system clock jumps
223 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
224 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
225 which have resolved to internal addresses") is set, apply that
226 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
227 - When an exit relay rejects a stream with reason "exit policy", but
228 we only know an exit policy summary (e.g. from the microdesc
229 consensus) for it, do not mark the relay as useless for all exiting.
230 Instead, mark just the circuit as unsuitable for that particular
231 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
233 o Major bugfixes (stream isolation):
234 - Allow applications to get proper stream isolation with
235 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
236 username/password authentication also offer "no authentication". Tor
237 had previously preferred "no authentication", so the applications
238 never actually sent Tor their auth details. Now Tor selects
239 username/password authentication if it's offered. You can disable
240 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
241 bug 8117; bugfix on 0.2.3.3-alpha.
242 - Follow the socks5 protocol when offering username/password
243 authentication. The fix for bug 8117 exposed this bug, and it
244 turns out real-world applications like Pidgin do care. Bugfix on
245 0.2.3.2-alpha; fixes bug 8879.
247 o Major bugfixes (client circuit building):
248 - Alter circuit build timeout measurement to start at the point
249 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
250 initialization). This should make our timeout measurements more
251 uniform. Previously, we were sometimes including ORconn setup time
252 in our circuit build time measurements. Should resolve bug 3443.
253 - If the circuit build timeout logic is disabled (via the consensus,
254 or because we are an authority), then don't build testing circuits.
255 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
257 o Major bugfixes (client-side DNS):
258 - Turn off the client-side DNS cache by default. Updating and using
259 the DNS cache is now configurable on a per-client-port
260 level. SOCKSPort, DNSPort, etc lines may now contain
261 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
262 cache these types of DNS answers when we receive them from an
263 exit node in response to an application request on this port, and
264 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
265 cached DNS answers of these types, we shouldn't use them. It's
266 potentially risky to use cached DNS answers at the client, since
267 doing so can indicate to one exit what answers we've gotten
268 for DNS lookups in the past. With IPv6, this becomes especially
269 problematic. Using cached DNS answers for requests on the same
270 circuit would present less linkability risk, since all traffic
271 on a circuit is already linkable, but it would also provide
272 little performance benefit: the exit node caches DNS replies
273 too. Implements a simplified version of Proposal 205. Implements
276 o Major bugfixes (hidden service privacy):
277 - Limit hidden service descriptors to at most ten introduction
278 points, to slow one kind of guard enumeration. Fixes bug 9002;
279 bugfix on 0.1.1.11-alpha.
281 o Major bugfixes (directory fetching):
282 - If the time to download the next old-style networkstatus is in
283 the future, do not decline to consider whether to download the
284 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
286 - We used to always request authority certificates by identity digest,
287 meaning we'd get the newest one even when we wanted one with a
288 different signing key. Then we would complain about being given
289 a certificate we already had, and never get the one we really
290 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
291 resource to request the one we want. Fixes bug 5595; bugfix on
294 o Major bugfixes (bridge reachability):
295 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
296 previously they did not, which prevented them from receiving
297 successful connections from relays for self-test or bandwidth
298 testing. Also, when a relay is extending a circuit to a bridge,
299 it needs to send a NETINFO cell, even when the bridge hasn't sent
300 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
302 o Major bugfixes (control interface):
303 - When receiving a new configuration file via the control port's
304 LOADCONF command, do not treat the defaults file as absent.
305 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
307 o Major bugfixes (directory authorities):
308 - Stop marking every relay as having been down for one hour every
309 time we restart a directory authority. These artificial downtimes
310 were messing with our Stable and Guard flag calculations. Fixes
311 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
312 - When computing directory thresholds, ignore any rejected-as-sybil
313 nodes during the computation so that they can't influence Fast,
314 Guard, etc. (We should have done this for proposal 109.) Fixes
316 - When marking a node as a likely sybil, reset its uptime metrics
317 to zero, so that it cannot time towards getting marked as Guard,
318 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
320 - Fix a bug in the voting algorithm that could yield incorrect results
321 when a non-naming authority declared too many flags. Fixes bug 9200;
322 bugfix on 0.2.0.3-alpha.
324 o Internal abstraction features:
325 - Introduce new channel_t abstraction between circuits and
326 or_connection_t to allow for implementing alternate OR-to-OR
327 transports. A channel_t is an abstract object which can either be a
328 cell-bearing channel, which is responsible for authenticating and
329 handshaking with the remote OR and transmitting cells to and from
330 it, or a listening channel, which spawns new cell-bearing channels
331 at the request of remote ORs. Implements part of ticket 6465.
332 - Make a channel_tls_t subclass of channel_t, adapting it to the
333 existing or_connection_t code. The V2/V3 protocol handshaking
334 code which formerly resided in command.c has been moved below the
335 channel_t abstraction layer and may be found in channeltls.c now.
336 Implements the rest of ticket 6465.
337 - Introduce new circuitmux_t storing the queue of circuits for
338 a channel; this encapsulates and abstracts the queue logic and
339 circuit selection policy, and allows the latter to be overridden
340 easily by switching out a policy object. The existing EWMA behavior
341 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
343 o New build requirements:
344 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
345 strongly recommended.
346 - Tor maintainers now require Automake version 1.9 or later to build
347 Tor from the Git repository. (Automake is not required when building
348 from a source distribution.)
350 o Minor features (protocol):
351 - No longer include the "opt" prefix when generating routerinfos
352 or v2 directories: it has been needless since Tor 0.1.2. Closes
354 - Tor relays and clients now support a better CREATE/EXTEND cell
355 format, allowing the sender to specify multiple address, identity,
356 and handshake types. Implements Robert Ransom's proposal 200;
358 - Reject as invalid most directory objects containing a NUL.
359 Belt-and-suspender fix for bug 8037.
360 - Reject EXTEND cells sent to nonexistent streams. According to the
361 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
362 we were only checking for stream IDs that were currently in use.
363 Found while hunting for more instances of bug 6271. Bugfix on
364 0.0.2pre8, which introduced incremental circuit construction.
366 o Minor features (security):
367 - Clear keys and key-derived material left on the stack in
368 rendservice.c and rendclient.c. Check return value of
369 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
370 These fixes should make us more forward-secure against cold-boot
371 attacks and the like. Fixes bug 2385.
372 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
373 Irix's random() only return 15 bits; Solaris's random() returns more
374 bits but its RAND_MAX says it only returns 15, and so on. Motivated
375 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
377 o Minor features (control protocol):
378 - Add CACHED keyword to ADDRMAP events in the control protocol
379 to indicate whether a DNS result will be cached or not. Resolves
381 - Allow an optional $ before the node identity digest in the
382 controller command GETINFO ns/id/<identity>, for consistency with
383 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
384 - Add a "GETINFO signal/names" control port command. Implements
386 - Provide default values for all options via "GETINFO config/defaults".
387 Implements ticket 4971.
389 o Minor features (path selection):
390 - When deciding whether we have enough descriptors to build circuits,
391 instead of looking at raw relay counts, look at which fraction
392 of (bandwidth-weighted) paths we're able to build. This approach
393 keeps clients from building circuits if their paths are likely to
394 stand out statistically. The default fraction of paths needed is
395 taken from the consensus directory; you can override it with the
396 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
397 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
398 and we have GeoIP information, also exclude all nodes with unknown
399 countries "??" and "A1". This behavior is controlled by the
400 new GeoIPExcludeUnknown option: you can make such nodes always
401 excluded with "GeoIPExcludeUnknown 1", and disable the feature
402 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
403 gets you the default behavior. Implements feature 7706.
405 o Minor features (hidden services):
406 - Improve circuit build timeout handling for hidden services.
407 In particular: adjust build timeouts more accurately depending
408 upon the number of hop-RTTs that a particular circuit type
409 undergoes. Additionally, launch intro circuits in parallel
410 if they timeout, and take the first one to reply as valid.
411 - The Tor client now ignores sub-domain components of a .onion
412 address. This change makes HTTP "virtual" hosting
413 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
414 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
415 hosted on the same hidden service. Implements proposal 204.
416 - Enable Tor to read configuration, state, and key information from
417 a FIFO. Previously Tor would only read from files with a positive
418 stat.st_size. Code from meejah; fixes bug 6044.
420 o Minor features (clients):
421 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
422 microdescriptor-related dir requests, and only fall back to normal
423 descriptors if none of their bridges can handle microdescriptors
424 (as opposed to the fix in ticket 4013, which caused them to fall
425 back to normal descriptors if *any* of their bridges preferred
426 them). Resolves ticket 4994.
427 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
428 TCP ports to forward. In the past it only accepted two ports:
429 the ORPort and the DirPort.
431 o Minor features (bridges):
432 - Add a new torrc option "ServerTransportListenAddr" to let bridge
433 operators select the address where their pluggable transports will
434 listen for connections. Resolves ticket 7013.
435 - Make bridge relays check once a minute for whether their IP
436 address has changed, rather than only every 15 minutes. Resolves
438 - Randomize the lifetime of our SSL link certificate, so censors can't
439 use the static value for filtering Tor flows. Resolves ticket 8443;
440 related to ticket 4014 which was included in 0.2.2.33.
441 - Bridge statistics now count bridge clients connecting over IPv6:
442 bridge statistics files now list "bridge-ip-versions" and
443 extra-info documents list "geoip6-db-digest". The control protocol
444 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
445 implementation by "shkoo", addressing ticket 5055.
447 o Minor features (relays):
448 - Option OutboundBindAddress can be specified multiple times and
449 accepts IPv6 addresses. Resolves ticket 6876.
451 o Minor features (IPv6, client side):
452 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
453 prefer to hand out virtual IPv6 addresses, since there are more of
454 them and we can't run out. To override this behavior and make IPv4
455 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
456 or DNSPort you're using for resolving. Implements ticket 7571.
457 - AutomapHostsOnResolve responses are now randomized, to avoid
458 annoying situations where Tor is restarted and applications
459 connect to the wrong addresses.
460 - Never try more than 1000 times to pick a new virtual address when
461 AutomapHostsOnResolve is set. That's good enough so long as we
462 aren't close to handing out our entire virtual address space;
463 if you're getting there, it's best to switch to IPv6 virtual
466 o Minor features (IPv6, relay/authority side):
467 - New config option "AuthDirHasIPv6Connectivity 1" that directory
468 authorities should set if they have IPv6 connectivity and want to
469 do reachability tests for IPv6 relays. Implements feature 5974.
470 - A relay with an IPv6 OR port now sends that address in NETINFO
471 cells (in addition to its other address). Implements ticket 6364.
473 o Minor features (directory authorities):
474 - Directory authorities now include inside each vote a statement of
475 the performance thresholds they used when assigning flags.
476 Implements ticket 8151.
477 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
478 in directory authority votes to describe whether they have enough
479 measured bandwidths to ignore advertised (relay descriptor)
480 bandwidth claims. Resolves ticket 8711.
481 - When directory authorities are computing thresholds for flags,
482 never let the threshold for the Fast flag fall below 4096
483 bytes. Also, do not consider nodes with extremely low bandwidths
484 when deciding thresholds for various directory flags. This change
485 should raise our threshold for Fast relays, possibly in turn
486 improving overall network performance; see ticket 1854. Resolves
488 - Directory authorities no long accept descriptors for any version of
489 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
490 These versions are insecure, unsupported, or both. Implements
493 o Minor features (path bias detection):
494 - Path Use Bias: Perform separate accounting for successful circuit
495 use. Keep separate statistics on stream attempt rates versus stream
496 success rates for each guard. Provide configurable thresholds to
497 determine when to emit log messages or disable use of guards that
498 fail too many stream attempts. Resolves ticket 7802.
499 - Create three levels of Path Bias log messages, as opposed to just
500 two. These are configurable via consensus as well as via the torrc
501 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
502 The default values are 0.70, 0.50, and 0.30 respectively.
503 - Separate the log message levels from the decision to drop guards,
504 which also is available via torrc option PathBiasDropGuards.
505 PathBiasDropGuards still defaults to 0 (off).
506 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
507 in combination with PathBiasExtremeRate.
508 - Increase the default values for PathBiasScaleThreshold and
509 PathBiasCircThreshold from (200, 20) to (300, 150).
510 - Add in circuit usage accounting to path bias. If we try to use a
511 built circuit but fail for any reason, it counts as path bias.
512 Certain classes of circuits where the adversary gets to pick your
513 destination node are exempt from this accounting. Usage accounting
514 can be specifically disabled via consensus parameter or torrc.
515 - Convert all internal path bias state to double-precision floating
516 point, to avoid roundoff error and other issues.
517 - Only record path bias information for circuits that have completed
518 *two* hops. Assuming end-to-end tagging is the attack vector, this
519 makes us more resilient to ambient circuit failure without any
520 detection capability loss.
522 o Minor features (build):
523 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
524 dhill. Resolves ticket 6982.
525 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
526 separate error codes; or at least, don't break for that reason.
527 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
528 - Compile on win64 using mingw64. Fixes bug 7260; patches from
531 o Build improvements (autotools):
532 - Warn if building on a platform with an unsigned time_t: there
533 are too many places where Tor currently assumes that time_t can
534 hold negative values. We'd like to fix them all, but probably
536 - Detect and reject attempts to build Tor with threading support
537 when OpenSSL has been compiled without threading support.
539 - Do not report status verbosely from autogen.sh unless the -v flag
540 is specified. Fixes issue 4664. Patch from Onizuka.
541 - Try to detect if we are ever building on a platform where
542 memset(...,0,...) does not set the value of a double to 0.0. Such
543 platforms are permitted by the C standard, though in practice
544 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
545 currently support them, but it's better to detect them and fail
546 than to perform erroneously.
547 - We no longer warn so much when generating manpages from their
549 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
550 the signs of types during autoconf. This is better than our old
551 approach, which didn't work when cross-compiling.
553 o Minor features (log messages, warnings):
554 - Detect when we're running with a version of OpenSSL other than the
555 one we compiled with. This conflict has occasionally given people
556 hard-to-track-down errors.
557 - Warn users who run hidden services on a Tor client with
558 UseEntryGuards disabled that their hidden services will be
559 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
560 attack which motivated Tor to support entry guards in the first
561 place). Resolves ticket 6889.
562 - Warn when we are binding low ports when hibernation is enabled;
563 previously we had warned when we were _advertising_ low ports with
564 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
565 - Issue a warning when running with the bufferevents backend enabled.
566 It's still not stable, and people should know that they're likely
567 to hit unexpected problems. Closes ticket 9147.
569 o Minor features (log messages, notices):
570 - Refactor resolve_my_address() so it returns the method by which we
571 decided our public IP address (explicitly configured, resolved from
572 explicit hostname, guessed from interfaces, learned by gethostname).
573 Now we can provide more helpful log messages when a relay guesses
574 its IP address incorrectly (e.g. due to unexpected lines in
575 /etc/hosts). Resolves ticket 2267.
576 - Track how many "TAP" and "NTor" circuit handshake requests we get,
577 and how many we complete, and log it every hour to help relay
578 operators follow trends in network load. Addresses ticket 9658.
580 o Minor features (log messages, diagnostics):
581 - If we fail to free a microdescriptor because of bug 7164, log
582 the filename and line number from which we tried to free it.
583 - We compute the overhead from passing onionskins back and forth to
584 cpuworkers, and report it when dumping statistics in response to
585 SIGUSR1. Supports ticket 7291.
586 - Add another diagnostic to the heartbeat message: track and log
587 overhead that TLS is adding to the data we write. If this is
588 high, we are sending too little data to SSL_write at a time.
589 Diagnostic for bug 7707.
590 - Log packaged cell fullness as part of the heartbeat message.
591 Diagnosis to try to determine the extent of bug 7743.
592 - Add more detail to a log message about relaxed timeouts, to help
594 - When learning a fingerprint for a bridge, log its corresponding
595 transport type. Implements ticket 7896.
596 - Warn more aggressively when flushing microdescriptors to a
597 microdescriptor cache fails, in an attempt to mitigate bug 8031,
598 or at least make it more diagnosable.
599 - Improve the log message when "Bug/attack: unexpected sendme cell
600 from client" occurs, to help us track bug 8093.
601 - Improve debugging output to help track down bug 8185 ("Bug:
602 outgoing relay cell has n_chan==NULL. Dropping.")
604 o Minor features (log messages, quieter bootstrapping):
605 - Log fewer lines at level "notice" about our OpenSSL and Libevent
606 versions and capabilities when everything is going right. Resolves
608 - Omit the first heartbeat log message, because it never has anything
609 useful to say, and it clutters up the bootstrapping messages.
610 Resolves ticket 6758.
611 - Don't log about reloading the microdescriptor cache at startup. Our
612 bootstrap warnings are supposed to tell the user when there's a
613 problem, and our bootstrap notices say when there isn't. Resolves
614 ticket 6759; bugfix on 0.2.2.6-alpha.
615 - Don't log "I learned some more directory information" when we're
616 reading cached directory information. Reserve it for when new
617 directory information arrives in response to a fetch. Resolves
619 - Don't complain about bootstrapping problems while hibernating.
620 These complaints reflect a general code problem, but not one
621 with any problematic effects (no connections are actually
622 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
624 o Minor features (testing):
625 - In our testsuite, create temporary directories with a bit more
626 entropy in their name to make name collisions less likely. Fixes
628 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
629 (P-256) Diffie-Hellman handshakes to src/or/bench.
630 - Add benchmark functions to test onion handshake performance.
633 - The DirServer option is now DirAuthority, for consistency with
634 current naming patterns. You can still use the old DirServer form.
636 o Minor bugfixes (protocol):
637 - Fix the handling of a TRUNCATE cell when it arrives while the
638 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
639 - Fix a misframing issue when reading the version numbers in a
640 VERSIONS cell. Previously we would recognize [00 01 00 02] as
641 'version 1, version 2, and version 0x100', when it should have
642 only included versions 1 and 2. Fixes bug 8059; bugfix on
643 0.2.0.10-alpha. Reported pseudonymously.
644 - Make the format and order of STREAM events for DNS lookups
645 consistent among the various ways to launch DNS lookups. Fixes
646 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
647 - When a Tor client gets a "truncated" relay cell, the first byte of
648 its payload specifies why the circuit was truncated. We were
649 ignoring this 'reason' byte when tearing down the circuit, resulting
650 in the controller not being told why the circuit closed. Now we
651 pass the reason from the truncated cell to the controller. Bugfix
652 on 0.1.2.3-alpha; fixes bug 7039.
654 o Minor bugfixes (syscalls and disk interaction):
655 - Always check the return values of functions fcntl() and
656 setsockopt(). We don't believe these are ever actually failing in
657 practice, but better safe than sorry. Also, checking these return
658 values should please analysis tools like Coverity. Patch from
659 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
660 - Avoid double-closing the listener socket in our socketpair()
661 replacement (used on Windows) in the case where the addresses on
662 our opened sockets don't match what we expected. Fixes bug 9400;
663 bugfix on 0.0.2pre7. Found by Coverity.
664 - Correctly store microdescriptors and extrainfo descriptors that
665 include an internal NUL byte. Fixes bug 8037; bugfix on
666 0.2.0.1-alpha. Bug reported by "cypherpunks".
667 - If for some reason we fail to write a microdescriptor while
668 rebuilding the cache, do not let the annotations from that
669 microdescriptor linger in the cache file, and do not let the
670 microdescriptor stay recorded as present in its old location.
671 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
672 - Use direct writes rather than stdio when building microdescriptor
673 caches, in an attempt to mitigate bug 8031, or at least make it
676 o Minor fixes (config options):
677 - Warn and fail if a server is configured not to advertise any
678 ORPorts at all. (We need *something* to put in our descriptor,
679 or we just won't work.)
680 - Behave correctly when the user disables LearnCircuitBuildTimeout
681 but doesn't tell us what they would like the timeout to be. Fixes
682 bug 6304; bugfix on 0.2.2.14-alpha.
683 - When autodetecting the number of CPUs, use the number of available
684 CPUs in preference to the number of configured CPUs. Inform the
685 user if this reduces the number of available CPUs. Fixes bug 8002;
686 bugfix on 0.2.3.1-alpha.
687 - Make it an error when you set EntryNodes but disable UseGuardNodes,
688 since it will (surprisingly to some users) ignore EntryNodes. Fixes
689 bug 8180; bugfix on 0.2.3.11-alpha.
690 - Avoid overflows when the user sets MaxCircuitDirtiness to a
691 ridiculously high value, by imposing a (ridiculously high) 30-day
692 maximum on MaxCircuitDirtiness.
693 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
694 to start with a triple-underscore so the controller won't touch it.
695 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
696 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
697 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
698 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
700 o Minor bugfixes (control protocol):
701 - Stop sending a stray "(null)" in some cases for the server status
702 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
704 - The ADDRMAP command can no longer generate an ill-formed error
705 code on a failed MAPADDRESS. It now says "internal" rather than
706 an English sentence fragment with spaces in the middle. Bugfix on
709 o Minor bugfixes (clients / edges):
710 - When we receive a RELAY_END cell with the reason DONE, or with no
711 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
712 status as "connection refused". Previously we reported these cases
713 as success but then immediately closed the connection. Fixes bug
714 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
715 - When choosing which stream on a formerly stalled circuit to wake
716 first, make better use of the platform's weak RNG. Previously,
717 we had been using the % ("modulo") operator to try to generate a
718 1/N chance of picking each stream, but this behaves badly with
719 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
722 o Minor bugfixes (path bias detection):
723 - If the state file's path bias counts are invalid (presumably from a
724 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
725 additional checks and log messages to the scaling of Path Bias
726 counts, in case there still are remaining issues with scaling.
727 Should help resolve bug 8235.
728 - Prevent rounding error in path bias counts when scaling
729 them down, and use the correct scale factor default. Also demote
730 some path bias related log messages down a level and make others
731 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
732 - Remove a source of rounding error during path bias count scaling;
733 don't count cannibalized circuits as used for path bias until we
734 actually try to use them; and fix a circuit_package_relay_cell()
735 warning message about n_chan==NULL. Fixes bug 7802.
736 - Paste the description for PathBias parameters from the man
737 page into or.h, so the code documents them too. Fixes bug 7982;
738 bugfix on 0.2.3.17-beta.
740 o Minor bugfixes (relays):
741 - Stop trying to resolve our hostname so often (e.g. every time we
742 think about doing a directory fetch). Now we reuse the cached
743 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
744 and 2410 (bugfix on 0.1.2.2-alpha).
746 o Minor bugfixes (blocking resistance):
747 - Only disable TLS session ticket support when running as a TLS
748 server. Now clients will blend better with regular Firefox
749 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
751 o Minor bugfixes (IPv6):
752 - Use square brackets around IPv6 addresses in numerous places
753 that needed them, including log messages, HTTPS CONNECT proxy
754 requests, TransportProxy statefile entries, and pluggable transport
755 extra-info lines. Fixes bug 7011; patch by David Fifield.
757 o Minor bugfixes (directory authorities):
758 - Reject consensus votes with more than 64 known-flags. We aren't even
759 close to that limit yet, and our code doesn't handle it correctly.
760 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
761 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
762 bugfix on 0.2.0.3-alpha.
764 o Minor bugfixes (memory leaks):
765 - Avoid leaking memory if we fail to compute a consensus signature
766 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
767 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
768 on 0.2.1.1-alpha; fixes bug 7816.
769 - Fix a memory leak during safe-cookie controller authentication.
770 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
771 - Free some more still-in-use memory at exit, to make hunting for
772 memory leaks easier. Resolves bug 7029.
774 o Minor bugfixes (code correctness):
775 - Increase the width of the field used to remember a connection's
776 link protocol version to two bytes. Harmless for now, since the
777 only currently recognized versions are one byte long. Reported
778 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
779 - Fix a crash when debugging unit tests on Windows: deallocate a
780 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
781 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
782 - When detecting the largest possible file descriptor (in order to
783 close all file descriptors when launching a new program), actually
784 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
785 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
787 - Avoid a crash if we fail to generate an extrainfo descriptor.
788 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
790 - Get rid of a couple of harmless clang warnings, where we compared
791 enums to ints. These warnings are newly introduced in clang 3.2.
793 o Minor bugfixes (code cleanliness):
794 - Avoid use of reserved identifiers in our C code. The C standard
795 doesn't like us declaring anything that starts with an
796 underscore, so let's knock it off before we get in trouble. Fix
797 for bug 1031; bugfix on the first Tor commit.
798 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
799 with large values. This situation was untriggered, but nevertheless
800 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
801 - Fix an impossible buffer overrun in the AES unit tests. Fixes
802 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
803 - Fix handling of rendezvous client authorization types over 8.
804 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
805 - Remove a couple of extraneous semicolons that were upsetting the
806 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
807 bugfix on 0.2.2.1-alpha.
809 - When complaining about a client port on a public address, log
810 which address we're complaining about. Fixes bug 4020; bugfix on
811 0.2.3.3-alpha. Patch by Tom Fitzhenry.
813 o Minor bugfixes (log messages, warnings):
814 - If we encounter a write failure on a SOCKS connection before we
815 finish our SOCKS handshake, don't warn that we closed the
816 connection before we could send a SOCKS reply. Fixes bug 8427;
817 bugfix on 0.1.0.1-rc.
818 - Fix a directory authority warn caused when we have a large amount
819 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
820 - Downgrade "Failed to hand off onionskin" messages to "debug"
821 severity, since they're typically redundant with the "Your computer
822 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
823 - Avoid spurious warnings when configuring multiple client ports of
824 which only some are nonlocal. Previously, we had claimed that some
825 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
828 o Minor bugfixes (log messages, other):
829 - Fix log messages and comments to avoid saying "GMT" when we mean
830 "UTC". Fixes bug 6113.
831 - When rejecting a configuration because we were unable to parse a
832 quoted string, log an actual error message. Fixes bug 7950; bugfix
834 - Correctly recognize that [::1] is a loopback address. Fixes
835 bug 8377; bugfix on 0.2.1.3-alpha.
836 - Don't log inappropriate heartbeat messages when hibernating: a
837 hibernating node is _expected_ to drop out of the consensus,
838 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
839 bugfix on 0.2.3.1-alpha.
840 - Eliminate several instances where we use "Nickname=ID" to refer to
841 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
842 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
845 o Minor bugfixes (build):
846 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
847 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
848 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
850 o Documentation fixes:
851 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
852 names match. Fixes bug 7768.
853 - Make the torify manpage no longer refer to tsocks; torify hasn't
854 supported tsocks since 0.2.3.14-alpha.
855 - Make the tor manpage no longer reference tsocks.
856 - Fix the GeoIPExcludeUnknown documentation to refer to
857 ExcludeExitNodes rather than the currently nonexistent
858 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
859 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
861 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
862 message is logged at notice, not at info.
863 - Say "KBytes" rather than "KB" in the man page (for various values
864 of K), to further reduce confusion about whether Tor counts in
865 units of memory or fractions of units of memory. Resolves ticket 7054.
868 - Stop exporting estimates of v2 and v3 directory traffic shares
869 in extrainfo documents. They were unneeded and sometimes inaccurate.
870 Also stop exporting any v2 directory request statistics. Resolves
872 - Drop support for detecting and warning about versions of Libevent
873 before 1.3e. Nothing reasonable ships with them any longer; warning
874 the user about them shouldn't be needed. Resolves ticket 6826.
875 - Now that all versions before 0.2.2.x are disallowed, we no longer
876 need to work around their missing features. Remove a bunch of
880 - The tor-tsocks.conf is no longer distributed or installed. We
881 recommend that tsocks users use torsocks instead. Resolves
883 - Remove some of the older contents of doc/ as obsolete; move others
884 to torspec.git. Fixes bug 8965.
886 o Code simplification:
887 - Avoid using character buffers when constructing most directory
888 objects: this approach was unwieldy and error-prone. Instead,
889 build smartlists of strings, and concatenate them when done.
890 - Rename "isin" functions to "contains", for grammar. Resolves
892 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
893 with the natural logarithm function from the system libm. Resolves
895 - Start using OpenBSD's implementation of queue.h, so that we don't
896 need to hand-roll our own pointer and list structures whenever we
897 need them. (We can't rely on a sys/queue.h, since some operating
898 systems don't have them, and the ones that do have them don't all
899 present the same extensions.)
900 - Start using OpenBSD's implementation of queue.h (originally by
902 - Enhance our internal sscanf replacement so that we can eliminate
903 the last remaining uses of the system sscanf. (Though those uses
904 of sscanf were safe, sscanf itself is generally error prone, so
905 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
907 - Replace all calls to snprintf() outside of src/ext with
908 tor_snprintf(). Also remove the #define to replace snprintf with
909 _snprintf on Windows; they have different semantics, and all of
910 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
914 - Add a wrapper function for the common "log a message with a
916 - Split the onion.c file into separate modules for the onion queue
917 and the different handshakes it supports.
918 - Move the client-side address-map/virtual-address/DNS-cache code
919 out of connection_edge.c into a new addressmap.c module.
920 - Move the entry node code from circuitbuild.c to its own file.
921 - Move the circuit build timeout tracking code from circuitbuild.c
923 - Source files taken from other packages now reside in src/ext;
924 previously they were scattered around the rest of Tor.
925 - Move the generic "config" code into a new file, and have "config.c"
926 hold only torrc- and state-related code. Resolves ticket 6823.
927 - Move the core of our "choose a weighted element at random" logic
928 into its own function, and give it unit tests. Now the logic is
929 testable, and a little less fragile too.
930 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
931 - Move last_reachable and testing_since from routerinfo_t to node_t.
932 Implements ticket 5529.
933 - Add replaycache_t structure, functions and unit tests, then refactor
934 rend_service_introduce() to be more clear to read, improve, debug,
935 and test. Resolves bug 6177.
938 - Remove some now-needless code that tried to aggressively flush
939 OR connections as data was added to them. Since 0.2.0.1-alpha, our
940 cell queue logic has saved us from the failure mode that this code
941 was supposed to prevent. Removing this code will limit the number
942 of baroque control flow paths through Tor's network logic. Reported
943 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
944 - Remove unused code for parsing v1 directories and "running routers"
945 documents. Fixes bug 6887.
946 - Remove the marshalling/unmarshalling code for sending requests to
947 cpuworkers over a socket, and instead just send structs. The
948 recipient will always be the same Tor binary as the sender, so
949 any encoding is overkill.
950 - Remove the testing_since field of node_t, which hasn't been used
951 for anything since 0.2.0.9-alpha.
952 - Finally remove support for malloc_good_size and malloc_usable_size.
953 We had hoped that these functions would let us eke a little more
954 memory out of our malloc implementation. Unfortunately, the only
955 implementations that provided these functions are also ones that
956 are already efficient about not overallocation: they never got us
957 more than 7 or so bytes per allocation. Removing them saves us a
958 little code complexity and a nontrivial amount of build complexity.
961 Changes in version 0.2.3.25 - 2012-11-19
962 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
963 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
964 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
965 programmer, and friend. Unstinting in his dedication to the cause of
966 freedom, he inspired and helped many of us as we began our work on
967 anonymity, and inspires us still. Please honor his memory by writing
968 software to protect people's freedoms, and by helping others to do so.
970 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
971 significantly reduced directory overhead (via microdescriptors),
972 enormous crypto performance improvements for fast relays on new
973 enough hardware, a new v3 TLS handshake protocol that can better
974 resist fingerprinting, support for protocol obfuscation plugins (aka
975 pluggable transports), better scalability for hidden services, IPv6
976 support for bridges, performance improvements like allowing clients
977 to skip the first round-trip on the circuit ("optimistic data") and
978 refilling token buckets more often, a new "stream isolation" design
979 to isolate different applications on different circuits, and many
980 stability, security, and privacy fixes.
982 Major features (v3 directory protocol):
983 - Clients now use microdescriptors instead of regular descriptors
984 to build circuits. Microdescriptors are authority-generated
985 summaries of regular descriptors' contents, designed to change very
986 rarely (see proposal 158 for details). This feature is designed
987 to save bandwidth, especially for clients on slow internet
988 connections. Use "UseMicrodescriptors 0" to disable it.
989 - Caches now download, cache, and serve microdescriptors, as well
990 as multiple "flavors" of the consensus, including a flavor that
991 describes microdescriptors.
993 o Major features (build hardening):
994 - Enable gcc and ld hardening by default. Resolves ticket 5210.
996 o Major features (relay scaling):
997 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
998 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
999 vectorized AES implementations as appropriate. These can be much,
1000 much faster than other AES implementations.
1001 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1002 implementation. It makes AES_CTR about 7% faster than our old one
1003 (which was about 10% faster than the one OpenSSL used to provide).
1004 Resolves ticket 4526.
1005 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1006 operations can use hardware acceleration (if present). Resolves
1008 - Unconditionally use OpenSSL's AES implementation instead of our
1009 old built-in one. OpenSSL's AES has been better for a while, and
1010 relatively few servers should still be on any version of OpenSSL
1011 that doesn't have good optimized assembly AES.
1013 o Major features (blocking resistance):
1014 - Update TLS cipher list to match Firefox 8 and later. Resolves
1016 - Remove support for clients falsely claiming to support standard
1017 ciphersuites that they can actually provide. As of modern OpenSSL
1018 versions, it's not necessary to fake any standard ciphersuite,
1019 and doing so prevents us from using better ciphersuites in the
1020 future, since servers can't know whether an advertised ciphersuite
1021 is really supported or not. Some hosts -- notably, ones with very
1022 old versions of OpenSSL or where OpenSSL has been built with ECC
1023 disabled -- will stand out because of this change; TBB users should
1024 not be affected. Implements the client side of proposal 198.
1025 - Implement a new handshake protocol (v3) for authenticating Tors to
1026 each other over TLS. It should be more resistant to fingerprinting
1027 than previous protocols, and should require less TLS hacking for
1028 future Tor implementations. Implements proposal 176.
1029 - Allow variable-length padding cells, to disguise the length of
1030 Tor's TLS records. Implements part of proposal 184.
1031 - While we're trying to bootstrap, record how many TLS connections
1032 fail in each state, and report which states saw the most failures
1033 in response to any bootstrap failures. This feature may speed up
1034 diagnosis of censorship events. Implements ticket 3116.
1036 o Major features (pluggable transports):
1037 - Clients and bridges can now be configured to use a separate
1038 "transport" proxy. This approach makes the censorship arms race
1039 easier by allowing bridges to use protocol obfuscation plugins.
1040 Implements proposal 180 (tickets 2841 and 3472).
1042 o Major features (DoS resistance):
1043 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1044 part of "Proposal 110: Avoiding infinite length circuits" by
1045 refusing all circuit-extend requests that do not use a relay_early
1046 cell. This change helps Tor resist a class of denial-of-service
1047 attacks by limiting the maximum circuit length.
1048 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1049 could use this trick to make their circuits receive cells faster
1050 than our flow control would have allowed, or to gum up the network,
1051 or possibly to do targeted memory denial-of-service attacks on
1052 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1053 from July 2002, before the release of Tor 0.0.0.
1055 o Major features (hidden services):
1056 - Adjust the number of introduction points that a hidden service
1057 will try to maintain based on how long its introduction points
1058 remain in use and how many introductions they handle. Fixes
1060 - Add a "tor2web mode" for clients that want to connect to hidden
1061 services non-anonymously (and possibly more quickly). As a safety
1062 measure to try to keep users from turning this on without knowing
1063 what they are doing, tor2web mode must be explicitly enabled at
1064 compile time, and a copy of Tor compiled to run in tor2web mode
1065 cannot be used as a normal Tor client. Implements feature 2553.
1067 o Major features (IPv6):
1068 - Clients can now connect to private bridges over IPv6. Bridges
1069 still need at least one IPv4 address in order to connect to
1070 other relays. Note that we don't yet handle the case where the
1071 user has two bridge lines for the same bridge (one IPv4, one
1072 IPv6). Implements parts of proposal 186.
1074 o Major features (directory authorities):
1075 - Use a more secure consensus parameter voting algorithm. Now at
1076 least three directory authorities or a majority of them must
1077 vote on a given parameter before it will be included in the
1078 consensus. Implements proposal 178.
1079 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1080 flag. In the past few years the average relay speed has picked
1081 up, and while the "top 7/8 of the network get the Fast flag" and
1082 "all relays with 20KB or more of capacity get the Fast flag" rules
1083 used to have the same result, now the top 7/8 of the network has
1084 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1086 o Major features (performance):
1087 - Exit nodes now accept and queue data on not-yet-connected streams.
1088 Previously, the client wasn't allowed to send data until the
1089 stream was connected, which slowed down all connections. This
1090 change will enable clients to perform a "fast-start" on streams
1091 and send data without having to wait for a confirmation that the
1092 stream has opened. Patch from Ian Goldberg; implements the server
1093 side of Proposal 174.
1094 - When using an exit relay running 0.2.3.x, clients can now
1095 "optimistically" send data before the exit relay reports that
1096 the stream has opened. This saves a round trip when starting
1097 connections where the client speaks first (such as web browsing).
1098 This behavior is controlled by a consensus parameter (currently
1099 disabled). To turn it on or off manually, use the "OptimisticData"
1100 torrc option. Implements proposal 181; code by Ian Goldberg.
1101 - Add a new TokenBucketRefillInterval option to refill token buckets
1102 more frequently than once per second. This should improve network
1103 performance, alleviate queueing problems, and make traffic less
1104 bursty. Implements proposal 183; closes ticket 3630. Design by
1105 Florian Tschorsch and Björn Scheuermann; implementation by
1107 - Raise the threshold of server descriptors needed (75%) and exit
1108 server descriptors needed (50%) before we will declare ourselves
1109 bootstrapped. This will make clients start building circuits a
1110 little later, but makes the initially constructed circuits less
1111 skewed and less in conflict with further directory fetches. Fixes
1114 o Major features (relays):
1115 - Relays now try regenerating and uploading their descriptor more
1116 frequently if they are not listed in the consensus, or if the
1117 version of their descriptor listed in the consensus is too
1118 old. This fix should prevent situations where a server declines
1119 to re-publish itself because it has done so too recently, even
1120 though the authorities decided not to list its recent-enough
1121 descriptor. Fix for bug 3327.
1123 o Major features (stream isolation):
1124 - You can now configure Tor so that streams from different
1125 applications are isolated on different circuits, to prevent an
1126 attacker who sees your streams as they leave an exit node from
1127 linking your sessions to one another. To do this, choose some way
1128 to distinguish the applications: have them connect to different
1129 SocksPorts, or have one of them use SOCKS4 while the other uses
1130 SOCKS5, or have them pass different authentication strings to the
1131 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1132 degree of isolation you need. This implements Proposal 171.
1133 - There's a new syntax for specifying multiple client ports (such as
1134 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1135 multiple *Port entries with full addr:port syntax on each.
1136 The old *ListenAddress format is still supported, but you can't
1137 mix it with the new *Port syntax.
1139 o Major features (bufferevents):
1140 - Tor can now optionally build with the "bufferevents" buffered IO
1141 backend provided by Libevent 2. To use this feature, make sure you
1142 have the latest possible version of Libevent, and pass the
1143 --enable-bufferevents flag to configure when building Tor from
1144 source. This feature will make our networking code more flexible,
1145 let us stack layers on each other, and let us use more efficient
1146 zero-copy transports where available.
1147 - Add experimental support for running on Windows with IOCP and no
1148 kernel-space socket buffers. This feature is controlled by a new
1149 "UserspaceIOCPBuffers" config option (off by default), which has
1150 no effect unless Tor has been built with bufferevents enabled,
1151 you're running on Windows, and you've set "DisableIOCP 0". In the
1152 long run, this may help solve or mitigate bug 98.
1154 o Major features (path selection):
1155 - The EntryNodes option can now include country codes like {de} or IP
1156 addresses or network masks. Previously we had disallowed these
1157 options because we didn't have an efficient way to keep the list up
1158 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
1161 o Major features (port forwarding):
1162 - Add support for automatic port mapping on the many home routers
1163 that support NAT-PMP or UPnP. To build the support code, you'll
1164 need to have the libnatpnp library and/or the libminiupnpc library,
1165 and you'll need to enable the feature specifically by passing
1166 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
1167 it on, use the new PortForwarding option.
1169 o Major features (logging):
1170 - Add a new 'Heartbeat' log message type to periodically log a message
1171 describing Tor's status at level Notice. This feature is meant for
1172 operators who log at notice, and want to make sure that their Tor
1173 server is still working. Implementation by George Kadianakis.
1174 - Make logging resolution configurable with a new LogTimeGranularity
1175 option, and change the default from 1 millisecond to 1 second.
1176 Implements enhancement 1668.
1178 o Major features (other):
1179 - New "DisableNetwork" config option to prevent Tor from launching any
1180 connections or accepting any connections except on a control port.
1181 Bundles and controllers can set this option before letting Tor talk
1182 to the rest of the network, for example to prevent any connections
1183 to a non-bridge address. Packages like Orbot can also use this
1184 option to instruct Tor to save power when the network is off.
1185 - Try to use system facilities for enumerating local interface
1186 addresses, before falling back to our old approach (which was
1187 binding a UDP socket, and calling getsockname() on it). That
1188 approach was scaring OS X users whose draconian firewall
1189 software warned about binding to UDP sockets regardless of
1190 whether packets were sent. Now we try to use getifaddrs(),
1191 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1192 system supports. Resolves ticket 1827.
1193 - Add experimental support for a "defaults" torrc file to be parsed
1194 before the regular torrc. Torrc options override the defaults file's
1195 options in the same way that the command line overrides the torrc.
1196 The SAVECONF controller command saves only those options which
1197 differ between the current configuration and the defaults file. HUP
1198 reloads both files. Implements task 4552.
1200 o New directory authorities:
1201 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1202 authority. Closes ticket 5749.
1204 o Security/privacy fixes:
1205 - Avoid read-from-freed-memory and double-free bugs that could occur
1206 when a DNS request fails while launching it. Fixes bug 6480;
1207 bugfix on 0.2.0.1-alpha.
1208 - Reject any attempt to extend to an internal address. Without
1209 this fix, a router could be used to probe addresses on an internal
1210 network to see whether they were accepting connections. Fixes bug
1211 6710; bugfix on 0.0.8pre1.
1212 - Close any connection that sends unrecognized junk before the TLS
1213 handshake. Solves an issue noted in bug 4369.
1214 - The advertised platform of a relay now includes only its operating
1215 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
1216 its service pack level (for Windows) or its CPU architecture
1217 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
1218 can insert an extra string in the platform line by setting the
1219 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
1220 - Disable TLS session tickets. OpenSSL's implementation was giving
1221 our TLS session keys the lifetime of our TLS context objects, when
1222 perfect forward secrecy would want us to discard anything that
1223 could decrypt a link connection as soon as the link connection
1224 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1225 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1226 - Tor tries to wipe potentially sensitive data after using it, so
1227 that if some subsequent security failure exposes Tor's memory,
1228 the damage will be limited. But we had a bug where the compiler
1229 was eliminating these wipe operations when it decided that the
1230 memory was no longer visible to a (correctly running) program,
1231 hence defeating our attempt at defense in depth. We fix that
1232 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1233 is unlikely to optimize away. Future versions of Tor may use
1234 a less ridiculously heavy approach for this. Fixes bug 7352.
1235 Reported in an article by Andrey Karpov.
1237 o Major bugfixes (crashes and asserts):
1238 - Avoid a pair of double-free and use-after-mark bugs that can
1239 occur with certain timings in canceled and re-received DNS
1240 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1241 - Fix a denial of service attack by which any directory authority
1242 could crash all the others, or by which a single v2 directory
1243 authority could crash everybody downloading v2 directory
1244 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1245 - Fix an assert that directory authorities could trigger on sighup
1246 during some configuration state transitions. We now don't treat
1247 it as a fatal error when the new descriptor we just generated in
1248 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1249 - Avoid segfault when starting up having run with an extremely old
1250 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1253 o Major bugfixes (clients):
1254 - If we are unable to find any exit that supports our predicted ports,
1255 stop calling them predicted, so that we don't loop and build
1256 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1257 which introduced predicted ports.
1258 - Check at each new consensus whether our entry guards were picked
1259 long enough ago that we should rotate them. Previously, we only
1260 did this check at startup, which could lead to us holding a guard
1261 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1262 - When fetching a bridge descriptor from a bridge authority,
1263 always do so anonymously, whether we have been able to open
1264 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1265 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1266 but we'll need to wait for bug 6010 before it's actually usable.
1268 o Major bugfixes (directory voting):
1269 - Check more thoroughly to prevent a rogue authority from
1270 double-voting on any consensus directory parameter. Previously,
1271 authorities would crash in this case if the total number of
1272 votes for any parameter exceeded the number of active voters,
1273 but would let it pass otherwise. Partially fixes bug 5786; bugfix
1275 - When computing weight parameters, behave more robustly in the
1276 presence of a bad bwweightscale value. Previously, the authorities
1277 would crash if they agreed on a sufficiently broken weight_scale
1278 value; now, they use a reasonable default and carry on. Fixes the
1279 rest of bug 5786; bugfix on 0.2.2.17-alpha.
1280 - If authorities are unable to get a v2 consensus document from other
1281 directory authorities, they no longer fall back to fetching
1282 them from regular directory caches. Fixes bug 5635; bugfix on
1283 0.2.2.26-beta, where routers stopped downloading v2 consensus
1286 o Major bugfixes (relays):
1287 - Fix a bug handling SENDME cells on nonexistent streams that could
1288 result in bizarre window values. Report and patch contributed
1289 pseudonymously. Fixes part of bug 6271. This bug was introduced
1290 before the first Tor release, in svn commit r152.
1291 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1292 tor gets started. This prevents a wrong average bandwidth
1293 estimate, which would cause relays to always start a new accounting
1294 interval at the earliest possible moment. Fixes bug 2003; bugfix
1295 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
1296 immensely in tracking this bug down.
1297 - Fix a possible crash bug when checking for deactivated circuits
1298 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1299 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1300 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1301 connections. This change should allow busy exit relays to stop
1302 running out of available sockets as quickly. Fixes bug 4950;
1303 bugfix on 0.2.2.26-beta.
1305 o Major bugfixes (blocking resistance):
1306 - Bridges no longer include their address in NETINFO cells on outgoing
1307 OR connections, to allow them to blend in better with clients.
1308 Removes another avenue for enumerating bridges. Reported by
1309 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1310 cells were introduced.
1311 - Warn the user when HTTPProxy, but no other proxy type, is
1312 configured. This can cause surprising behavior: it doesn't send
1313 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1314 directory traffic only. Resolves ticket 4663.
1316 o Major bugfixes (hidden services):
1317 - Improve hidden service robustness: when an attempt to connect to
1318 a hidden service ends, be willing to refetch its hidden service
1319 descriptors from each of the HSDir relays responsible for them
1320 immediately. Previously, we would not consider refetching the
1321 service's descriptors from each HSDir for 15 minutes after the last
1322 fetch, which was inconvenient if the hidden service was not running
1323 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1324 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1325 They used to check that the timestamp was within 30 minutes
1326 of their system clock, so they could cap the size of their
1327 replay-detection cache, but that approach unnecessarily refused
1328 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1329 the v3 intro-point protocol (the first one which sent a timestamp
1330 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1331 - When one of a hidden service's introduction points appears to be
1332 unreachable, stop trying it. Previously, we would keep trying
1333 to build circuits to the introduction point until we lost the
1334 descriptor, usually because the user gave up and restarted Tor.
1335 Fixes part of bug 3825.
1337 o Changes to default torrc file:
1338 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1339 port on 9050 by default anyway, so this should not change anything
1341 - Stop mentioning the deprecated *ListenAddress options in
1342 torrc.sample. Fixes bug 5438.
1343 - Document unit of bandwidth-related options in sample torrc.
1345 - Fix broken URLs in the sample torrc file, and tell readers about
1346 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1347 PublishServerDescriptor options. Addresses bug 4652.
1349 o Minor features (directory authorities):
1350 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1351 change when the authority is deciding whether to accept a newly
1352 uploaded descriptor. Implements ticket 6423.
1353 - Directory authorities are now a little more lenient at accepting
1354 older router descriptors, or newer router descriptors that don't
1355 make big changes. This should help ameliorate past and future
1356 issues where routers think they have uploaded valid descriptors,
1357 but the authorities don't think so. Fix for ticket 2479.
1358 - Authority operators can now vote for all relays in a given
1359 set of countries to be BadDir/BadExit/Invalid/Rejected.
1360 - Provide two consensus parameters (FastFlagMinThreshold and
1361 FastFlagMaxThreshold) to control the range of allowable bandwidths
1362 for the Fast directory flag. These allow authorities to run
1363 experiments on appropriate requirements for being a "Fast" node.
1364 The AuthDirFastGuarantee config value still applies. Implements
1367 o Minor features (bridges / bridge authorities):
1368 - Make bridge SSL certificates a bit more stealthy by using random
1369 serial numbers, in the same fashion as OpenSSL when generating
1370 self-signed certificates. Implements ticket 4584.
1371 - Tag a bridge's descriptor as "never to be sent unencrypted".
1372 This shouldn't matter, since bridges don't open non-anonymous
1373 connections to the bridge authority and don't allow unencrypted
1374 directory connections from clients, but we might as well make
1375 sure. Closes bug 5139.
1376 - The Bridge Authority now writes statistics on how many bridge
1377 descriptors it gave out in total, and how many unique descriptors
1378 it gave out. It also lists how often the most and least commonly
1379 fetched descriptors were given out, as well as the median and
1380 25th/75th percentile. Implements tickets 4200 and 4294.
1382 o Minor features (IPv6):
1383 - Make the code that clients use to detect an address change be
1384 IPv6-aware, so that it won't fill clients' logs with error
1385 messages when trying to get the IPv4 address of an IPv6
1386 connection. Implements ticket 5537.
1387 - Relays now understand an IPv6 address when they get one from a
1388 directory server. Resolves ticket 4875.
1390 o Minor features (hidden services):
1391 - Expire old or over-used hidden service introduction points.
1392 Required by fix for bug 3460.
1393 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1394 public key replay-detection cache from 60 minutes to 5 minutes. This
1395 replay-detection cache is now used only to detect multiple
1396 INTRODUCE2 cells specifying the same rendezvous point, so we can
1397 avoid launching multiple simultaneous attempts to connect to it.
1398 - When a hidden service's introduction point times out, consider
1399 trying it again during the next attempt to connect to the
1400 HS. Previously, we would not try it again unless a newly fetched
1401 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1403 o Minor features (relays):
1404 - Relays now include a reason for regenerating their descriptors
1405 in an HTTP header when uploading to the authorities. This will
1406 make it easier to debug descriptor-upload issues in the future.
1407 - Turn on directory request statistics by default and include them in
1408 extra-info descriptors. Don't break if we have no GeoIP database.
1409 - Replace files in stats/ rather than appending to them. Now that we
1410 include statistics in extra-info descriptors, it makes no sense to
1411 keep old statistics forever. Implements ticket 2930.
1412 - Relays that set "ConnDirectionStatistics 1" write statistics on the
1413 bidirectional use of connections to disk every 24 hours.
1414 - Add a GeoIP file digest to the extra-info descriptor. Implements
1417 o Minor features (new config options):
1418 - New config option "DynamicDHGroups" (disabled by default) provides
1419 each bridge with a unique prime DH modulus to be used during
1420 SSL handshakes. This option attempts to help against censors
1421 who might use the Apache DH modulus as a static identifier for
1422 bridges. Addresses ticket 4548.
1423 - New config option "DisableDebuggerAttachment" (on by default)
1424 to prevent basic debugging attachment attempts by other processes.
1425 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1426 - Ordinarily, Tor does not count traffic from private addresses (like
1427 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
1428 There is now a new option, CountPrivateBandwidth, to disable this
1429 behavior. Patch from Daniel Cagara.
1431 o Minor features (different behavior for old config options):
1432 - Allow MapAddress directives to specify matches against super-domains,
1433 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1434 Implements issue 933.
1435 - Don't disable the DirPort when we cannot exceed our AccountingMax
1436 limit during this interval because the effective bandwidthrate is
1437 low enough. This is useful in a situation where AccountMax is only
1438 used as an additional safeguard or to provide statistics.
1439 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1440 implements ticket 3439.
1441 - When configuring a large set of nodes in EntryNodes, and there are
1442 enough of them listed as Guard so that we don't need to consider
1443 the non-guard entries, prefer the ones listed with the Guard flag.
1444 - If you set the NumCPUs option to 0, Tor will now try to detect how
1445 many CPUs you have. This is the new default behavior.
1446 - The NodeFamily option -- which let you declare that you want to
1447 consider nodes to be part of a family whether they list themselves
1448 that way or not -- now allows IP address ranges and country codes.
1450 o Minor features (new command-line config behavior):
1451 - Slightly change behavior of "list" options (that is, config
1452 options that can appear more than once) when they appear both in
1453 torrc and on the command line. Previously, the command-line options
1454 would be appended to the ones from torrc. Now, the command-line
1455 options override the torrc options entirely. This new behavior
1456 allows the user to override list options (like exit policies and
1457 ports to listen on) from the command line, rather than simply
1458 appending to the list.
1459 - You can get the old (appending) command-line behavior for "list"
1460 options by prefixing the option name with a "+".
1461 - You can remove all the values for a "list" option from the command
1462 line without adding any new ones by prefixing the option name
1465 o Minor features (controller, new events):
1466 - Extend the control protocol to report flags that control a circuit's
1467 path selection in CIRC events and in replies to 'GETINFO
1468 circuit-status'. Implements part of ticket 2411.
1469 - Extend the control protocol to report the hidden service address
1470 and current state of a hidden-service-related circuit in CIRC
1471 events and in replies to 'GETINFO circuit-status'. Implements part
1473 - Include the creation time of a circuit in CIRC and CIRC2
1474 control-port events and the list produced by the 'GETINFO
1475 circuit-status' control-port command.
1476 - Add a new CONF_CHANGED event so that controllers can be notified
1477 of any configuration changes made by other controllers, or by the
1478 user. Implements ticket 1692.
1479 - Add a new SIGNAL event to the controller interface so that
1480 controllers can be notified when Tor handles a signal. Resolves
1481 issue 1955. Patch by John Brooks.
1483 o Minor features (controller, new getinfo options):
1484 - Expose our view of whether we have gone dormant to the controller,
1485 via a new "GETINFO dormant" value. Torbutton and other controllers
1486 can use this to avoid doing periodic requests through Tor while
1487 it's dormant (bug 4718). Resolves ticket 5954.
1488 - Add a new GETINFO option to get total bytes read and written. Patch
1489 from pipe, revised by atagar. Resolves ticket 2345.
1490 - Implement new GETINFO controller fields to provide information about
1491 the Tor process's pid, euid, username, and resource limits.
1493 o Minor features (controller, other):
1494 - Allow controllers to request an event notification whenever a
1495 circuit is cannibalized or its purpose is changed. Implements
1496 part of ticket 3457.
1497 - Use absolute path names when reporting the torrc filename in the
1498 control protocol, so a controller can more easily find the torrc
1499 file. Resolves bug 1101.
1500 - When reporting the path to the cookie file to the controller,
1501 give an absolute path. Resolves ticket 4881.
1503 o Minor features (log messages):
1504 - Add more information to a log statement that might help track down
1505 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1506 non-IP address" messages (or any Bug messages, for that matter!),
1507 please let us know about it.
1508 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1509 EntryNodes will have no effect. Resolves issue 2571.
1510 - Try to make the introductory warning message that Tor prints on
1511 startup more useful for actually finding help and information.
1512 Resolves ticket 2474.
1513 - When the system call to create a listener socket fails, log the
1514 error message explaining why. This may help diagnose bug 4027.
1516 o Minor features (other):
1517 - When we fail to initialize Libevent, retry with IOCP disabled so we
1518 don't need to turn on multi-threading support in Libevent, which in
1519 turn requires a working socketpair(). This is a workaround for bug
1520 4457, which affects Libevent versions from 2.0.1-alpha through
1522 - When starting as root and then changing our UID via the User
1523 control option, and we have a ControlSocket configured, make sure
1524 that the ControlSocket is owned by the same account that Tor will
1525 run under. Implements ticket 3421; fix by Jérémy Bobbio.
1526 - Accept attempts to include a password authenticator in the
1527 handshake, as supported by SOCKS5. This handles SOCKS clients that
1528 don't know how to omit a password when authenticating. Resolves
1530 - Check for and recover from inconsistency in the microdescriptor
1531 cache. This will make it harder for us to accidentally free a
1532 microdescriptor without removing it from the appropriate data
1533 structures. Fixes issue 3135; issue noted by "wanoskarnet".
1534 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1536 o Minor bugfixes (code security):
1537 - Prevent a null-pointer dereference when receiving a data cell
1538 for a nonexistent stream when the circuit in question has an
1539 empty deliver window. We don't believe this is triggerable,
1540 since we don't currently allow deliver windows to become empty,
1541 but the logic is tricky enough that it's better to make the code
1542 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1543 - Fix a (harmless) integer overflow in cell statistics reported by
1544 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1545 - Fix our implementation of crypto_random_hostname() so it can't
1546 overflow on ridiculously large inputs. (No Tor version has ever
1547 provided this kind of bad inputs, but let's be correct in depth.)
1548 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1549 - Add a (probably redundant) memory clear between iterations of
1550 the router status voting loop, to prevent future coding errors
1551 where data might leak between iterations of the loop. Resolves
1554 o Minor bugfixes (wrapper functions):
1555 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
1556 utility function used in the control-port code). This shouldn't
1557 ever happen unless Tor is completely out of memory, but if it did
1558 happen and Tor somehow recovered from it, Tor could have sent a log
1559 message to a control port in the middle of a reply to a controller
1560 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1561 - Fix some (not actually triggerable) buffer size checks in usage of
1562 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1564 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1565 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1566 - Enforce correct return behavior of tor_vsscanf() when the '%%'
1567 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
1568 - Make our replacement implementation of strtok_r() compatible with
1569 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1570 bugfix on 0.2.2.1-alpha.
1571 - Find more places in the code that should have been testing for
1572 invalid sockets using the SOCKET_OK macro. Required for a fix
1573 for bug 4533. Bugfix on 0.2.2.28-beta.
1575 o Minor bugfixes (code correctness):
1576 - Check return value of fputs() when writing authority certificate
1577 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1578 - When building Tor on Windows with -DUNICODE (not default), ensure
1579 that error messages, filenames, and DNS server names are always
1580 NUL-terminated when we convert them to a single-byte encoding.
1581 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1582 - Fix a memory leak when trying to launch a DNS request when the
1583 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
1585 - Correct file sizes when reading binary files on Cygwin, to avoid
1586 a bug where Tor would fail to read its state file. Fixes bug 6844;
1587 bugfix on 0.1.2.7-alpha.
1588 - Make sure to set *socket_error in all error cases in
1589 connection_connect(), so it can't produce a warning about
1590 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1591 0.2.1.1-alpha; resolves ticket 6028.
1592 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1593 bug 4532; found by "troll_un".
1595 o Minor bugfixes (clients):
1596 - Allow one-hop directory-fetching circuits the full "circuit build
1597 timeout" period, rather than just half of it, before failing them
1598 and marking the relay down. This fix should help reduce cases where
1599 clients declare relays (or worse, bridges) unreachable because
1600 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1601 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1603 - Ensure we don't cannibalize circuits that are longer than three hops
1604 already, so we don't end up making circuits with 5 or more
1605 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1606 0.1.0.1-rc which introduced cannibalization.
1608 o Minor bugfixes (relays):
1609 - Don't publish a new relay descriptor when we reload our onion key,
1610 unless the onion key has actually changed. Fixes bug 3263 and
1611 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
1612 - When relays refuse a "create" cell because their queue of pending
1613 create cells is too big (typically because their cpu can't keep up
1614 with the arrival rate), send back reason "resource limit" rather
1615 than reason "internal", so network measurement scripts can get a
1616 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1617 - Exit nodes don't need to fetch certificates for authorities that
1618 they don't recognize; only directory authorities, bridges,
1619 and caches need to do that. Fixes part of bug 2297; bugfix on
1622 o Minor bugfixes (directory authority / mirrors):
1623 - Avoid O(n^2) performance characteristics when parsing a large
1624 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1625 - Authorities no longer include any router in their microdescriptor
1626 consensuses for which they couldn't generate or agree on a
1627 microdescriptor. Fixes the second piece of bug 6404; fix on
1629 - When checking for requested signatures on the latest consensus
1630 before serving it to a client, make sure to check the right
1631 consensus flavor. Bugfix on 0.2.2.6-alpha.
1632 - Fix an edge case where TestingTorNetwork is set but the authorities
1633 and relays all have an uptime of zero, so the private Tor network
1634 could briefly lack support for hidden services. Fixes bug 3886;
1635 bugfix on 0.2.2.18-alpha.
1636 - Directory caches no longer refuse to clean out descriptors because
1637 of missing v2 networkstatus documents, unless they're configured
1638 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1639 0.2.2.26-beta. Patch by Daniel Bryg.
1640 - Don't serve or accept v2 hidden service descriptors over a relay's
1641 DirPort. It's never correct to do so, and disabling it might
1642 make it more annoying to exploit any bugs that turn up in the
1643 descriptor-parsing code. Fixes bug 7149.
1645 o Minor bugfixes (hidden services, client-side):
1646 - Assert that hidden-service-related operations are not performed
1647 using single-hop circuits. Previously, Tor would assert that
1648 client-side streams are not attached to single-hop circuits,
1649 but not that other sensitive operations on the client and service
1650 side are not performed using single-hop circuits. Fixes bug 3332;
1652 - Avoid undefined behaviour when parsing the list of supported
1653 rendezvous/introduction protocols in a hidden service descriptor.
1654 Previously, Tor would have confused (as-yet-unused) protocol version
1655 numbers greater than 32 with lower ones on many platforms. Fixes
1656 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1657 - Don't close hidden service client circuits which have almost
1658 finished connecting to their destination when they reach
1659 the normal circuit-build timeout. Previously, we would close
1660 introduction circuits which are waiting for an acknowledgement
1661 from the introduction point, and rendezvous circuits which have
1662 been specified in an INTRODUCE1 cell sent to a hidden service,
1663 after the normal CBT. Now, we mark them as 'timed out', and launch
1664 another rendezvous attempt in parallel. This behavior change can
1665 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1666 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1668 o Minor bugfixes (hidden services, service-side):
1669 - Don't close hidden-service-side rendezvous circuits when they
1670 reach the normal circuit-build timeout. This behaviour change can
1671 be disabled using the new
1672 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1673 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1674 - Don't launch more than 10 service-side introduction-point circuits
1675 for a hidden service in five minutes. Previously, we would consider
1676 launching more introduction-point circuits if at least one second
1677 had passed without any introduction-point circuits failing. Fixes
1678 bug 4607; bugfix on 0.0.7pre1.
1680 o Minor bugfixes (config option behavior):
1681 - If the user tries to set MyFamily on a bridge, refuse to
1682 do so, and warn about the security implications. Fixes bug 4657;
1683 bugfix on 0.2.0.3-alpha.
1684 - The "--quiet" and "--hush" options now apply not only to Tor's
1685 behavior before logs are configured, but also to Tor's behavior in
1686 the absense of configured logs. Fixes bug 3550; bugfix on
1688 - Change the AllowDotExit rules so they should actually work.
1689 We now enforce AllowDotExit only immediately after receiving an
1690 address via SOCKS or DNSPort: other sources are free to provide
1691 .exit addresses after the resolution occurs. Fixes bug 3940;
1692 bugfix on 0.2.2.1-alpha.
1693 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
1694 don't depend on the consensus parameters or compute adaptive
1695 timeouts when it is disabled. Fixes bug 5049; bugfix on
1697 - After we pick a directory mirror, we would refuse to use it if
1698 it's in our ExcludeExitNodes list, resulting in mysterious failures
1699 to bootstrap for people who just wanted to avoid exiting from
1700 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1701 - When told to add a bridge with the same digest as a preexisting
1702 bridge but a different addr:port, change the addr:port as
1703 requested. Previously we would not notice the change. Fixes half
1704 of bug 5603; fix on 0.2.2.26-beta.
1706 o Minor bugfixes (controller):
1707 - Allow manual 'authenticate' commands to the controller interface
1708 from netcat (nc) as well as telnet. We were rejecting them because
1709 they didn't come with the expected whitespace at the end of the
1710 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1711 - Report a real bootstrap problem to the controller on router
1712 identity mismatch. Previously we just said "foo", which probably
1713 made a lot of sense at the time. Fixes bug 4169; bugfix on
1715 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1716 option is set to 0 (which Vidalia version 0.2.16 now does when
1717 a SAVECONF attempt fails), perform other actions that SIGHUP
1718 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1720 - Correctly handle checking the permissions on the parent
1721 directory of a control socket in the root directory. Bug found
1722 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
1724 - End AUTHCHALLENGE error messages (in the control protocol) with
1725 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
1727 o Minor bugfixes (network reading/writing):
1728 - Disable writing on marked-for-close connections when they are
1729 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1730 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1731 case for flushing marked connections.
1732 - Make sure that there are no unhandled pending TLS errors before
1733 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1734 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1735 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1736 - Detect SSL handshake even when the initial attempt to write the
1737 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1738 - If the client fails to set a reasonable set of ciphersuites
1739 during its v2 handshake renegotiation, allow the renegotiation to
1740 continue nevertheless (i.e. send all the required certificates).
1741 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1743 o Minor bugfixes (other):
1744 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1745 resource exhaustion, so that clients can adjust their load to
1746 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1747 started using END_STREAM_REASON_RESOURCELIMIT.
1748 - Don't check for whether the address we're using for outbound
1749 connections has changed until after the outbound connection has
1750 completed. On Windows, getsockname() doesn't succeed until the
1751 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1752 - Don't hold a Windows file handle open for every file mapping;
1753 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1755 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1756 bugfix on 0.2.1.10-alpha.
1757 - If we fail to write a microdescriptor to the disk cache, do not
1758 continue replacing the old microdescriptor file. Fixes bug 2954;
1759 bugfix on 0.2.2.6-alpha.
1761 o Minor bugfixes (log messages, path selection):
1762 - Downgrade "set buildtimeout to low value" messages to "info"
1763 severity; they were never an actual problem, there was never
1764 anything reasonable to do about them, and they tended to spam logs
1765 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1766 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1767 more information to it, so that we can track it down in case it
1768 returns again. Mitigates bug 5235.
1769 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
1770 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
1771 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
1772 - Issue a log message if a guard completes less than 40% of your
1773 circuits. Threshold is configurable by torrc option
1774 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
1775 additional, off-by-default code to disable guards which fail too
1776 many circuits. Addresses ticket 5458.
1778 o Minor bugfixes (log messages, client):
1779 - Downgrade "Got a certificate, but we already have it" log messages
1780 from warning to info, except when we're a dirauth. Fixes bug 5238;
1781 bugfix on 0.2.1.7-alpha.
1782 - Fix the log message describing how we work around discovering
1783 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1784 4837; bugfix on 0.2.2.9-alpha.
1785 - When logging about a disallowed .exit name, do not also call it
1786 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1787 - Fix a log message suggesting that people contact a non-existent
1788 email address. Fixes bug 3448.
1789 - Rephrase the log message emitted if the TestSocks check is
1790 successful. Patch from Fabian Keil; fixes bug 4094.
1791 - Log (at debug level) whenever a circuit's purpose is changed.
1792 - Log SSL state transitions at log level DEBUG, log domain
1793 HANDSHAKE. This can be useful for debugging censorship events.
1794 Implements ticket 3264.
1795 - We now log which torrc file we're using on startup. Implements
1797 - Rate-limit log messages when asked to connect anonymously to
1798 a private address. When these hit, they tended to hit fast and
1799 often. Also, don't bother trying to connect to addresses that we
1800 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1801 reply makes us think we have been lied to, even when the address the
1802 client tried to connect to was "localhost." Resolves ticket 2822.
1804 o Minor bugfixes (log messages, non-client):
1805 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1806 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1807 - Don't log that we have "decided to publish new relay descriptor"
1808 unless we are actually publishing a descriptor. Fixes bug 3942;
1809 bugfix on 0.2.2.28-beta.
1810 - Log which authority we're missing votes from when we go to fetch
1811 them from the other auths.
1812 - Replace "Sending publish request" log messages with "Launching
1813 upload", so that they no longer confusingly imply that we're
1814 sending something to a directory we might not even be connected
1815 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1816 - Warn when Tor is configured to use accounting in a way that can
1817 link a hidden service to some other hidden service or public
1818 address. Resolves ticket 6490.
1819 - Fix a minor formatting issue in one of tor-gencert's error messages.
1823 - Update to the latest version of the tinytest unit testing framework.
1824 This includes a couple of bugfixes that can be relevant for
1825 running forked unit tests on Windows, and removes all reserved
1827 - Avoid a false positive in the util/threads unit test by increasing
1828 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1829 - Make it possible to set the TestingTorNetwork configuration
1830 option using AlternateDirAuthority and AlternateBridgeAuthority
1831 as an alternative to setting DirServer. Addresses ticket 6377.
1832 - Add a unit test for the environment_variable_names_equal() function.
1833 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1834 - Numerous new unit tests for functions in util.c and address.c by
1836 - The long-disabled benchmark tests are now split into their own
1837 ./src/test/bench binary.
1838 - The benchmark tests can now use more accurate timers than
1839 gettimeofday() when such timers are available.
1840 - Use tt_assert(), not tor_assert(), for checking for test failures.
1841 This makes the unit tests more able to go on in the event that
1844 o Build improvements:
1845 - Use the dead_strip option when building Tor on OS X. This reduces
1846 binary size by almost 19% when linking openssl and libevent
1847 statically, which we do for Tor Browser Bundle.
1848 - Provide a better error message about possible OSX Asciidoc failure
1849 reasons. Fixes bug 6436.
1850 - Detect attempts to build Tor on (as yet hypothetical) versions
1851 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1852 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1853 - On Windows, we now define the _WIN32_WINNT macros only if they
1854 are not already defined. This lets the person building Tor decide,
1855 if they want, to require a later version of Windows.
1856 - Our autogen.sh script now uses autoreconf to launch autoconf,
1857 automake, and so on. This is more robust against some of the failure
1858 modes associated with running the autotools pieces on their own.
1859 - Running "make version" now displays the version of Tor that
1860 we're about to build. Idea from katmagic; resolves issue 4400.
1861 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
1862 on 0.2.2.4-alpha; fixes bug 3427.
1863 - New --enable-static-tor configure option for building Tor as
1864 statically as possible. Idea, general hackery and thoughts from
1865 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
1867 - Limited, experimental support for building with nmake and MSVC.
1869 o Build requirements:
1870 - Building Tor with bufferevent support now requires Libevent
1871 2.0.13-stable or later. Previous versions of Libevent had bugs in
1872 SSL-related bufferevents and related issues that would make Tor
1873 work badly with bufferevents. Requiring 2.0.13-stable also allows
1874 Tor with bufferevents to take advantage of Libevent APIs
1875 introduced after 2.0.8-rc.
1876 - Our build system requires automake 1.6 or later to create the
1877 Makefile.in files. Previously, you could have used 1.4.
1878 This only affects developers and people building Tor from git;
1879 people who build Tor from the source distribution without changing
1880 the Makefile.am files should be fine.
1881 - Detect when we try to build on a platform that doesn't define
1882 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1884 o Build fixes (compile/link):
1885 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1886 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1888 - When building with --enable-static-tor on OpenBSD, do not
1889 erroneously attempt to link -lrt. Fixes bug 5103.
1890 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1891 that IPv6 stuff will compile on MSVC, and compilation issues
1892 will be easier to track down. Fixes bug 5861.
1893 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1894 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1895 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1896 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1898 o Build fixes (other):
1899 - Use the _WIN32 macro throughout our code to detect Windows.
1900 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1902 - Properly handle the case where the build-tree is not the same
1903 as the source tree when generating src/common/common_sha1.i,
1904 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1905 bugfix on 0.2.0.1-alpha.
1906 - During configure, search for library containing cos function as
1907 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1908 against libm was hard-coded before. Fixes the first part of bug
1909 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1911 - Prevent a false positive from the check-spaces script, by disabling
1912 the "whitespace between function name and (" check for functions
1915 o Packaging (RPM) changes:
1916 - Update our default RPM spec files to work with mock and rpmbuild
1917 on RHEL/Fedora. They have an updated set of dependencies and
1918 conflicts, a fix for an ancient typo when creating the "_tor"
1919 user, and better instructions. Thanks to Ondrej Mikle for the
1920 patch series. Fixes bug 6043.
1921 - On OpenSUSE, create the /var/run/tor directory on startup if it
1922 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
1924 o Code refactoring (safety):
1925 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1926 10 lines. Also, don't nest them. Doing so in the past has
1927 led to hard-to-debug code. The new style is to use the
1928 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1929 - Use macros to indicate OpenSSL versions, so we don't need to worry
1930 about accidental hexadecimal bit shifts.
1931 - Use tor_sscanf() in place of scanf() in more places through the
1932 code. This makes us a little more locale-independent, and
1933 should help shut up code-analysis tools that can't tell
1934 a safe sscanf string from a dangerous one.
1935 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1936 - Use the smartlist_add_asprintf() alias more consistently.
1938 o Code refactoring (consolidate):
1939 - A major revision to our internal node-selecting and listing logic.
1940 Tor already had at least two major ways to look at the question of
1941 "which Tor servers do we know about": a list of router descriptors,
1942 and a list of entries in the current consensus. With
1943 microdescriptors, we're adding a third. Having so many systems
1944 without an abstraction layer over them was hurting the codebase.
1945 Now, we have a new "node_t" abstraction that presents a consistent
1946 interface to a client's view of a Tor node, and holds (nearly) all
1947 of the mutable state formerly in routerinfo_t and routerstatus_t.
1948 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1949 Libevent's notion of cached time when possible.
1950 - Remove duplicate code for invoking getrlimit() from control.c.
1951 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1952 own homebrewed ssl_state_to_string() replacement. Patch from
1953 Emile Snyder. Fixes bug 4653.
1954 - Change the symmetric cipher interface so that creating and
1955 initializing a stream cipher are no longer separate functions.
1957 o Code refactoring (separate):
1958 - Make a new "entry connection" struct as an internal subtype of "edge
1959 connection", to simplify the code and make exit connections smaller.
1960 - Split connection_about_to_close() into separate functions for each
1962 - Rewrite the listener-selection logic so that parsing which ports
1963 we want to listen on is now separate from binding to the ports
1966 o Code refactoring (name changes):
1967 - Rename a handful of old identifiers, mostly related to crypto
1968 structures and crypto functions. By convention, our "create an
1969 object" functions are called "type_new()", our "free an object"
1970 functions are called "type_free()", and our types indicate that
1971 they are types only with a final "_t". But a handful of older
1972 types and functions broke these rules, with function names like
1973 "type_create" or "subsystem_op_type", or with type names like
1975 - Rename Tor functions that turn strings into addresses, so that
1976 "parse" indicates that no hostname resolution occurs, and
1977 "lookup" indicates that hostname resolution may occur. This
1978 should help prevent mistakes in the future. Fixes bug 3512.
1979 - Use the name "CERTS" consistently to refer to the new cell type;
1980 we were calling it CERT in some places and CERTS in others.
1981 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1982 invalid value, rather than just -1.
1983 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1984 can pick them up when the tests aren't disabled. Bugfix on
1985 0.2.2.4-alpha which introduced tinytest.
1987 o Code refactoring (other):
1988 - Defensively refactor rend_mid_rendezvous() so that protocol
1989 violations and length checks happen in the beginning. Fixes
1991 - Remove the pure attribute from all functions that used it
1992 previously. In many cases we assigned it incorrectly, because the
1993 functions might assert or call impure functions, and we don't have
1994 evidence that keeping the pure attribute is worthwhile. Implements
1995 changes suggested in ticket 4421.
1996 - Move the replay-detection cache for the RSA-encrypted parts of
1997 INTRODUCE2 cells to the introduction point data structures.
1998 Previously, we would use one replay-detection cache per hidden
1999 service. Required by fix for bug 3460.
2000 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2001 no longer link against Libevent: they never used it, but
2002 our library structure used to force them to link it.
2004 o Removed features and files:
2005 - Remove all internal support for unpadded RSA. We never used it, and
2006 it would be a bad idea to start.
2007 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2009 - Remove some redundant #include directives throughout the code.
2010 Patch from Andrea Gelmini.
2011 - Remove some old code to remember statistics about which descriptors
2012 we've served as a directory mirror. The feature wasn't used and
2013 is outdated now that microdescriptors are around.
2014 - Remove some old code to work around even older versions of Tor that
2015 used forked processes to handle DNS requests. Such versions of Tor
2016 are no longer in use as relays.
2017 - The "torify" script no longer supports the "tsocks" socksifier
2018 tool, since tsocks doesn't support DNS and UDP right for Tor.
2019 Everyone should be using torsocks instead. Fixes bugs 3530 and
2020 5180. Based on a patch by "ugh".
2021 - Remove the torrc.bridge file: we don't use it for anything, and
2022 it had become badly desynchronized from torrc.sample. Resolves
2026 - Begin a doc/state-contents.txt file to explain the contents of
2027 the Tor state file. Fixes bug 2987.
2028 - Clarify the documentation for the Alternate*Authority options.
2030 - Document the --defaults-torrc option, and the new semantics for
2031 overriding, extending, and clearing lists of options. Closes
2033 - Add missing man page documentation for consensus and microdesc
2034 files. Resolves ticket 6732.
2035 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2037 o Documentation fixes:
2038 - Improve the manual's documentation for the NT Service command-line
2039 options. Addresses ticket 3964.
2040 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2041 - Document the changes to the ORPort and DirPort options, and the
2042 fact that {OR/Dir}ListenAddress is now unnecessary (and
2043 therefore deprecated). Resolves ticket 5597.
2044 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2045 - Clarify that hidden services are TCP only. Fixes bug 6024.
2048 Changes in version 0.2.2.39 - 2012-09-11
2049 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2053 - Fix an assertion failure in tor_timegm() that could be triggered
2054 by a badly formatted directory object. Bug found by fuzzing with
2055 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2056 - Do not crash when comparing an address with port value 0 to an
2057 address policy. This bug could have been used to cause a remote
2058 assertion failure by or against directory authorities, or to
2059 allow some applications to crash clients. Fixes bug 6690; bugfix
2063 Changes in version 0.2.2.38 - 2012-08-12
2064 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2065 attack that could in theory leak path information.
2068 - Avoid an uninitialized memory read when reading a vote or consensus
2069 document that has an unrecognized flavor name. This read could
2070 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2071 - Try to leak less information about what relays a client is
2072 choosing to a side-channel attacker. Previously, a Tor client would
2073 stop iterating through the list of available relays as soon as it
2074 had chosen one, thus finishing a little earlier when it picked
2075 a router earlier in the list. If an attacker can recover this
2076 timing information (nontrivial but not proven to be impossible),
2077 they could learn some coarse-grained information about which relays
2078 a client was picking (middle nodes in particular are likelier to
2079 be affected than exits). The timing attack might be mitigated by
2080 other factors (see bug 6537 for some discussion), but it's best
2081 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2084 Changes in version 0.2.2.37 - 2012-06-06
2085 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2086 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2090 - Work around a bug in OpenSSL that broke renegotiation with TLS
2091 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2092 the v2 Tor connection protocol when both sides were using OpenSSL
2093 1.0.1 would fail. Resolves ticket 6033.
2094 - When waiting for a client to renegotiate, don't allow it to add
2095 any bytes to the input buffer. This fixes a potential DoS issue.
2096 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2097 - Fix an edge case where if we fetch or publish a hidden service
2098 descriptor, we might build a 4-hop circuit and then use that circuit
2099 for exiting afterwards -- even if the new last hop doesn't obey our
2100 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2103 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2104 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2107 - Tell GCC and Clang to check for any errors in format strings passed
2108 to the tor_v*(print|scan)f functions.
2111 Changes in version 0.2.2.36 - 2012-05-24
2112 Tor 0.2.2.36 updates the addresses for two of the eight directory
2113 authorities, fixes some potential anonymity and security issues,
2114 and fixes several crash bugs.
2116 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2117 known flaws, and nobody should be using them. You should upgrade. If
2118 you're using a Linux or BSD and its packages are obsolete, stop using
2119 those packages and upgrade anyway.
2121 o Directory authority changes:
2122 - Change IP address for maatuska (v3 directory authority).
2123 - Change IP address for ides (v3 directory authority), and rename
2127 - When building or running with any version of OpenSSL earlier
2128 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2129 versions have a bug (CVE-2011-4576) in which their block cipher
2130 padding includes uninitialized data, potentially leaking sensitive
2131 information to any peer with whom they make a SSLv3 connection. Tor
2132 does not use SSL v3 by default, but a hostile client or server
2133 could force an SSLv3 connection in order to gain information that
2134 they shouldn't have been able to get. The best solution here is to
2135 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2136 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2137 to make sure that the bug can't happen.
2138 - Never use a bridge or a controller-supplied node as an exit, even
2139 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2140 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2141 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2142 - Only build circuits if we have a sufficient threshold of the total
2143 descriptors that are marked in the consensus with the "Exit"
2144 flag. This mitigates an attack proposed by wanoskarnet, in which
2145 all of a client's bridges collude to restrict the exit nodes that
2146 the client knows about. Fixes bug 5343.
2147 - Provide controllers with a safer way to implement the cookie
2148 authentication mechanism. With the old method, if another locally
2149 running program could convince a controller that it was the Tor
2150 process, then that program could trick the controller into telling
2151 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2152 authentication method uses a challenge-response approach to prevent
2153 this attack. Fixes bug 5185; implements proposal 193.
2156 - Avoid logging uninitialized data when unable to decode a hidden
2157 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2158 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2159 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2161 - Fix builds when the path to sed, openssl, or sha1sum contains
2162 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2164 - Correct our replacements for the timeradd() and timersub() functions
2165 on platforms that lack them (for example, Windows). The timersub()
2166 function is used when expiring circuits, while timeradd() is
2167 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2168 bugfix on 0.2.2.24-alpha.
2169 - Fix the SOCKET_OK test that we use to tell when socket
2170 creation fails so that it works on Win64. Fixes part of bug 4533;
2171 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2174 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2175 Fixes bug 5346; bugfix on 0.0.8pre3.
2176 - Make our number-parsing functions always treat too-large values
2177 as an error, even when those values exceed the width of the
2178 underlying type. Previously, if the caller provided these
2179 functions with minima or maxima set to the extreme values of the
2180 underlying integer type, these functions would return those
2181 values on overflow rather than treating overflow as an error.
2182 Fixes part of bug 5786; bugfix on 0.0.9.
2183 - Older Linux kernels erroneously respond to strange nmap behavior
2184 by having accept() return successfully with a zero-length
2185 socket. When this happens, just close the connection. Previously,
2186 we would try harder to learn the remote address: but there was
2187 no such remote address to learn, and our method for trying to
2188 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2189 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2190 - Correct parsing of certain date types in parse_http_time().
2191 Without this patch, If-Modified-Since would behave
2192 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2193 Esteban Manchado Velázques.
2194 - Change the BridgePassword feature (part of the "bridge community"
2195 design, which is not yet implemented) to use a time-independent
2196 comparison. The old behavior might have allowed an adversary
2197 to use timing to guess the BridgePassword value. Fixes bug 5543;
2198 bugfix on 0.2.0.14-alpha.
2199 - Detect and reject certain misformed escape sequences in
2200 configuration values. Previously, these values would cause us
2201 to crash if received in a torrc file or over an authenticated
2202 control port. Bug found by Esteban Manchado Velázquez, and
2203 independently by Robert Connolly from Matta Consulting who further
2204 noted that it allows a post-authentication heap overflow. Patch
2205 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2206 bugfix on 0.2.0.16-alpha.
2207 - Fix a compile warning when using the --enable-openbsd-malloc
2208 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2209 - During configure, detect when we're building with clang version
2210 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2211 CFLAGS. clang doesn't support them yet.
2212 - When sending an HTTP/1.1 proxy request, include a Host header.
2213 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2214 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2215 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2216 - If we hit the error case where routerlist_insert() replaces an
2217 existing (old) server descriptor, make sure to remove that
2218 server descriptor from the old_routers list. Fix related to bug
2219 1776. Bugfix on 0.2.2.18-alpha.
2221 o Minor bugfixes (documentation and log messages):
2222 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2223 Fixes bug 4856; bugfix on Tor 0.0.6.
2224 - Update "ClientOnly" man page entry to explain that there isn't
2225 really any point to messing with it. Resolves ticket 5005.
2226 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2227 directory authority option (introduced in Tor 0.2.2.34).
2228 - Downgrade the "We're missing a certificate" message from notice
2229 to info: people kept mistaking it for a real problem, whereas it
2230 is seldom the problem even when we are failing to bootstrap. Fixes
2231 bug 5067; bugfix on 0.2.0.10-alpha.
2232 - Correctly spell "connect" in a log message on failure to create a
2233 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2234 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2235 circuits. Fixes issue 5259.
2238 - Directory authorities now reject versions of Tor older than
2239 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2240 inclusive. These versions accounted for only a small fraction of
2241 the Tor network, and have numerous known security issues. Resolves
2243 - Update to the May 1 2012 Maxmind GeoLite Country database.
2246 - When sending or relaying a RELAY_EARLY cell, we used to convert
2247 it to a RELAY cell if the connection was using the v1 link
2248 protocol. This was a workaround for older versions of Tor, which
2249 didn't handle RELAY_EARLY cells properly. Now that all supported
2250 versions can handle RELAY_EARLY cells, and now that we're enforcing
2251 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2252 remove this workaround. Addresses bug 4786.
2255 Changes in version 0.2.2.35 - 2011-12-16
2256 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2257 buffers code. Absolutely everybody should upgrade.
2259 The bug relied on an incorrect calculation when making data continuous
2260 in one of our IO buffers, if the first chunk of the buffer was
2261 misaligned by just the wrong amount. The miscalculation would allow an
2262 attacker to overflow a piece of heap-allocated memory. To mount this
2263 attack, the attacker would need to either open a SOCKS connection to
2264 Tor's SocksPort (usually restricted to localhost), or target a Tor
2265 instance configured to make its connections through a SOCKS proxy
2266 (which Tor does not do by default).
2268 Good security practice requires that all heap-overflow bugs should be
2269 presumed to be exploitable until proven otherwise, so we are treating
2270 this as a potential code execution attack. Please upgrade immediately!
2271 This bug does not affect bufferevents-based builds of Tor. Special
2272 thanks to "Vektor" for reporting this issue to us!
2274 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2275 crash bugs for unusual configurations, and a long-term bug that
2276 would prevent Tor from starting on Windows machines with draconian
2279 With this release, we remind everyone that 0.2.0.x has reached its
2280 formal end-of-life. Those Tor versions have many known flaws, and
2281 nobody should be using them. You should upgrade -- ideally to the
2282 0.2.2.x series. If you're using a Linux or BSD and its packages are
2283 obsolete, stop using those packages and upgrade anyway.
2285 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2286 longer receive support after some time in early 2012.
2289 - Fix a heap overflow bug that could occur when trying to pull
2290 data into the first chunk of a buffer, when that chunk had
2291 already had some data drained from it. Fixes CVE-2011-2778;
2292 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2293 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2294 that it doesn't attempt to allocate a socketpair. This could cause
2295 some problems on Windows systems with overzealous firewalls. Fix for
2296 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2298 - If we mark an OR connection for close based on a cell we process,
2299 don't process any further cells on it. We already avoid further
2300 reads on marked-for-close connections, but now we also discard the
2301 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2302 which was the first version where we might mark a connection for
2303 close based on processing a cell on it.
2304 - Correctly sanity-check that we don't underflow on a memory
2305 allocation (and then assert) for hidden service introduction
2306 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2307 bugfix on 0.2.1.5-alpha.
2308 - Fix a memory leak when we check whether a hidden service
2309 descriptor has any usable introduction points left. Fixes bug
2310 4424. Bugfix on 0.2.2.25-alpha.
2311 - Don't crash when we're running as a relay and don't have a GeoIP
2312 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2313 we've had in the 0.2.3.x branch already.
2314 - When running as a client, do not print a misleading (and plain
2315 wrong) log message that we're collecting "directory request"
2316 statistics: clients don't collect statistics. Also don't create a
2317 useless (because empty) stats file in the stats/ directory. Fixes
2318 bug 4353; bugfix on 0.2.2.34.
2321 - Detect failure to initialize Libevent. This fix provides better
2322 detection for future instances of bug 4457.
2323 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2324 function. This was eating up hideously large amounts of time on some
2325 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2326 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2327 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2329 - Don't warn about unused log_mutex in log.c when building with
2330 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2331 0.1.0.6-rc which introduced --disable-threads.
2332 - When configuring, starting, or stopping an NT service, stop
2333 immediately after the service configuration attempt has succeeded
2334 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2335 - When sending a NETINFO cell, include the original address
2336 received for the other side, not its canonical address. Found
2337 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2338 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2339 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2340 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2341 occurred when a client tried to fetch a descriptor for a bridge
2342 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2343 - Backport fixes for a pair of compilation warnings on Windows.
2344 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2345 - If we had ever tried to call tor_addr_to_str on an address of
2346 unknown type, we would have done a strdup on an uninitialized
2347 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2348 Reported by "troll_un".
2349 - Correctly detect and handle transient lookup failures from
2350 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2351 Reported by "troll_un".
2352 - Fix null-pointer access that could occur if TLS allocation failed.
2353 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2354 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2355 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2358 - Add two new config options for directory authorities:
2359 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2360 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2361 that is always sufficient to satisfy the bandwidth requirement for
2362 the Guard flag. Now it will be easier for researchers to simulate
2363 Tor networks with different values. Resolves ticket 4484.
2364 - When Tor ignores a hidden service specified in its configuration,
2365 include the hidden service's directory in the warning message.
2366 Previously, we would only tell the user that some hidden service
2367 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2368 - Update to the December 6 2011 Maxmind GeoLite Country database.
2370 o Packaging changes:
2371 - Make it easier to automate expert package builds on Windows,
2372 by removing an absolute path from makensis.exe command.
2375 Changes in version 0.2.1.32 - 2011-12-16
2376 Tor 0.2.1.32 backports important security and privacy fixes for
2377 oldstable. This release is intended only for package maintainers and
2378 others who cannot use the 0.2.2 stable series. All others should be
2379 using Tor 0.2.2.x or newer.
2381 The Tor 0.2.1.x series will reach formal end-of-life some time in
2382 early 2012; we will stop releasing patches for it then.
2384 o Major bugfixes (also included in 0.2.2.x):
2385 - Correctly sanity-check that we don't underflow on a memory
2386 allocation (and then assert) for hidden service introduction
2387 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2388 bugfix on 0.2.1.5-alpha.
2389 - Fix a heap overflow bug that could occur when trying to pull
2390 data into the first chunk of a buffer, when that chunk had
2391 already had some data drained from it. Fixes CVE-2011-2778;
2392 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2395 - Update to the December 6 2011 Maxmind GeoLite Country database.
2398 Changes in version 0.2.2.34 - 2011-10-26
2399 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2400 can deanonymize Tor users. Everybody should upgrade.
2402 The attack relies on four components: 1) Clients reuse their TLS cert
2403 when talking to different relays, so relays can recognize a user by
2404 the identity key in her cert. 2) An attacker who knows the client's
2405 identity key can probe each guard relay to see if that identity key
2406 is connected to that guard relay right now. 3) A variety of active
2407 attacks in the literature (starting from "Low-Cost Traffic Analysis
2408 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2409 discover the guard relays that a Tor user visiting the website is using.
2410 4) Clients typically pick three guards at random, so the set of guards
2411 for a given user could well be a unique fingerprint for her. This
2412 release fixes components #1 and #2, which is enough to block the attack;
2413 the other two remain as open research problems. Special thanks to
2414 "frosty_un" for reporting the issue to us!
2416 Clients should upgrade so they are no longer recognizable by the TLS
2417 certs they present. Relays should upgrade so they no longer allow a
2418 remote attacker to probe them to test whether unpatched clients are
2419 currently connected to them.
2421 This release also fixes several vulnerabilities that allow an attacker
2422 to enumerate bridge relays. Some bridge enumeration attacks still
2423 remain; see for example proposal 188.
2425 o Privacy/anonymity fixes (clients):
2426 - Clients and bridges no longer send TLS certificate chains on
2427 outgoing OR connections. Previously, each client or bridge would
2428 use the same cert chain for all outgoing OR connections until
2429 its IP address changes, which allowed any relay that the client
2430 or bridge contacted to determine which entry guards it is using.
2431 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2432 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2433 no longer considers that connection as suitable for satisfying a
2434 circuit EXTEND request. Now relays can protect clients from the
2435 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2436 - Directory authorities no longer assign the Guard flag to relays
2437 that haven't upgraded to the above "refuse EXTEND requests
2438 to client connections" fix. Now directory authorities can
2439 protect clients from the CVE-2011-2768 issue even if neither
2440 the clients nor the relays have upgraded yet. There's a new
2441 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2442 to let us transition smoothly, else tomorrow there would be no
2445 o Privacy/anonymity fixes (bridge enumeration):
2446 - Bridge relays now do their directory fetches inside Tor TLS
2447 connections, like all the other clients do, rather than connecting
2448 directly to the DirPort like public relays do. Removes another
2449 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2450 - Bridges relays now build circuits for themselves in a more similar
2451 way to how clients build them. Removes another avenue for
2452 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2453 when bridges were introduced.
2454 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2455 that they initiated. Relays could distinguish incoming bridge
2456 connections from client connections, creating another avenue for
2457 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2458 Found by "frosty_un".
2461 - Fix a crash bug when changing node restrictions while a DNS lookup
2462 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2464 - Don't launch a useless circuit after failing to use one of a
2465 hidden service's introduction points. Previously, we would
2466 launch a new introduction circuit, but not set the hidden service
2467 which that circuit was intended to connect to, so it would never
2468 actually be used. A different piece of code would then create a
2469 new introduction circuit correctly. Bug reported by katmagic and
2470 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2473 - Change an integer overflow check in the OpenBSD_Malloc code so
2474 that GCC is less likely to eliminate it as impossible. Patch
2475 from Mansour Moufid. Fixes bug 4059.
2476 - When a hidden service turns an extra service-side introduction
2477 circuit into a general-purpose circuit, free the rend_data and
2478 intro_key fields first, so we won't leak memory if the circuit
2479 is cannibalized for use as another service-side introduction
2480 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2481 - Bridges now skip DNS self-tests, to act a little more stealthily.
2482 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2483 bridges. Patch by "warms0x".
2484 - Fix internal bug-checking logic that was supposed to catch
2485 failures in digest generation so that it will fail more robustly
2486 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2487 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2488 - Report any failure in init_keys() calls launched because our
2489 IP address has changed. Spotted by Coverity Scan. Bugfix on
2490 0.1.1.4-alpha; fixes CID 484.
2492 o Minor bugfixes (log messages and documentation):
2493 - Remove a confusing dollar sign from the example fingerprint in the
2494 man page, and also make the example fingerprint a valid one. Fixes
2495 bug 4309; bugfix on 0.2.1.3-alpha.
2496 - The next version of Windows will be called Windows 8, and it has
2497 a major version of 6, minor version of 2. Correctly identify that
2498 version instead of calling it "Very recent version". Resolves
2499 ticket 4153; reported by funkstar.
2500 - Downgrade log messages about circuit timeout calibration from
2501 "notice" to "info": they don't require or suggest any human
2502 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2503 bugfix on 0.2.2.14-alpha.
2506 - Turn on directory request statistics by default and include them in
2507 extra-info descriptors. Don't break if we have no GeoIP database.
2508 Backported from 0.2.3.1-alpha; implements ticket 3951.
2509 - Update to the October 4 2011 Maxmind GeoLite Country database.
2512 Changes in version 0.2.1.31 - 2011-10-26
2513 Tor 0.2.1.31 backports important security and privacy fixes for
2514 oldstable. This release is intended only for package maintainers and
2515 others who cannot use the 0.2.2 stable series. All others should be
2516 using Tor 0.2.2.x or newer.
2518 o Security fixes (also included in 0.2.2.x):
2519 - Replace all potentially sensitive memory comparison operations
2520 with versions whose runtime does not depend on the data being
2521 compared. This will help resist a class of attacks where an
2522 adversary can use variations in timing information to learn
2523 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2524 implementation by Robert Ransom based partially on code by DJB.)
2525 - Fix an assert in parsing router descriptors containing IPv6
2526 addresses. This one took down the directory authorities when
2527 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2529 o Privacy/anonymity fixes (also included in 0.2.2.x):
2530 - Clients and bridges no longer send TLS certificate chains on
2531 outgoing OR connections. Previously, each client or bridge would
2532 use the same cert chain for all outgoing OR connections until
2533 its IP address changes, which allowed any relay that the client
2534 or bridge contacted to determine which entry guards it is using.
2535 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2536 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2537 no longer considers that connection as suitable for satisfying a
2538 circuit EXTEND request. Now relays can protect clients from the
2539 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2540 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2541 that they initiated. Relays could distinguish incoming bridge
2542 connections from client connections, creating another avenue for
2543 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2544 Found by "frosty_un".
2545 - When receiving a hidden service descriptor, check that it is for
2546 the hidden service we wanted. Previously, Tor would store any
2547 hidden service descriptors that a directory gave it, whether it
2548 wanted them or not. This wouldn't have let an attacker impersonate
2549 a hidden service, but it did let directories pre-seed a client
2550 with descriptors that it didn't want. Bugfix on 0.0.6.
2551 - Avoid linkability based on cached hidden service descriptors: forget
2552 all hidden service descriptors cached as a client when processing a
2553 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2554 - Make the bridge directory authority refuse to answer directory
2555 requests for "all" descriptors. It used to include bridge
2556 descriptors in its answer, which was a major information leak.
2557 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2558 - Don't attach new streams to old rendezvous circuits after SIGNAL
2559 NEWNYM. Previously, we would keep using an existing rendezvous
2560 circuit if it remained open (i.e. if it were kept open by a
2561 long-lived stream, or if a new stream were attached to it before
2562 Tor could notice that it was old and no longer in use). Bugfix on
2563 0.1.1.15-rc; fixes bug 3375.
2565 o Minor bugfixes (also included in 0.2.2.x):
2566 - When we restart our relay, we might get a successful connection
2567 from the outside before we've started our reachability tests,
2568 triggering a warning: "ORPort found reachable, but I have no
2569 routerinfo yet. Failing to inform controller of success." This
2570 bug was harmless unless Tor is running under a controller
2571 like Vidalia, in which case the controller would never get a
2572 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2574 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2575 enabled. Fixes bug 1526.
2576 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2577 anything since 0.2.1.16-rc.
2578 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2579 None of the cases where we did this before were wrong, but by making
2580 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2581 - Fix a rare crash bug that could occur when a client was configured
2582 with a large number of bridges. Fixes bug 2629; bugfix on
2583 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2584 - Correct the warning displayed when a rendezvous descriptor exceeds
2585 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2587 - Fix an uncommon assertion failure when running with DNSPort under
2588 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2589 - When warning about missing zlib development packages during compile,
2590 give the correct package names. Bugfix on 0.2.0.1-alpha.
2591 - Require that introduction point keys and onion keys have public
2592 exponent 65537. Bugfix on 0.2.0.10-alpha.
2593 - Do not crash when our configuration file becomes unreadable, for
2594 example due to a permissions change, between when we start up
2595 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2597 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2599 - Always NUL-terminate the sun_path field of a sockaddr_un before
2600 passing it to the kernel. (Not a security issue: kernels are
2601 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2602 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2603 - Don't stack-allocate the list of supplementary GIDs when we're
2604 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2605 could take up to 256K, which is way too much stack. Found by
2606 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2608 o Minor bugfixes (only in 0.2.1.x):
2609 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2610 rely on them. Bugfix on 0.2.1.30.
2611 - Use git revisions instead of svn revisions when generating our
2612 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2614 o Minor features (also included in 0.2.2.x):
2615 - Adjust the expiration time on our SSL session certificates to
2616 better match SSL certs seen in the wild. Resolves ticket 4014.
2617 - Allow nameservers with IPv6 address. Resolves bug 2574.
2618 - Update to the October 4 2011 Maxmind GeoLite Country database.
2621 Changes in version 0.2.2.33 - 2011-09-13
2622 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2623 TLS handshake that makes relays and bridges that run this new version
2624 reachable from Iran again.
2627 - Avoid an assertion failure when reloading a configuration with
2628 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2629 3923; bugfix on 0.2.2.25-alpha.
2631 o Minor features (security):
2632 - Check for replays of the public-key encrypted portion of an
2633 INTRODUCE1 cell, in addition to the current check for replays of
2634 the g^x value. This prevents a possible class of active attacks
2635 by an attacker who controls both an introduction point and a
2636 rendezvous point, and who uses the malleability of AES-CTR to
2637 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2638 that these attacks are infeasible (requiring the attacker to send
2639 on the order of zettabytes of altered cells in a short interval),
2640 but we'd rather block them off in case there are any classes of
2641 this attack that we missed. Reported by Willem Pinckaers.
2644 - Adjust the expiration time on our SSL session certificates to
2645 better match SSL certs seen in the wild. Resolves ticket 4014.
2646 - Change the default required uptime for a relay to be accepted as
2647 a HSDir (hidden service directory) from 24 hours to 25 hours.
2648 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2649 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2650 authorities to abstain from voting on assignment of the HSDir
2651 consensus flag. Related to bug 2649.
2652 - Update to the September 6 2011 Maxmind GeoLite Country database.
2654 o Minor bugfixes (documentation and log messages):
2655 - Correct the man page to explain that HashedControlPassword and
2656 CookieAuthentication can both be set, in which case either method
2657 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2658 when we decided to allow these config options to both be set. Issue
2660 - Demote the 'replay detected' log message emitted when a hidden
2661 service receives the same Diffie-Hellman public key in two different
2662 INTRODUCE2 cells to info level. A normal Tor client can cause that
2663 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2664 fixes part of bug 2442.
2665 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2666 level. There is nothing that a hidden service's operator can do
2667 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2669 - Clarify a log message specifying the characters permitted in
2670 HiddenServiceAuthorizeClient client names. Previously, the log
2671 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2672 given the impression that every ASCII character between "+" and "_"
2673 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2676 - Provide a substitute implementation of lround() for MSVC, which
2677 apparently lacks it. Patch from Gisle Vanem.
2678 - Clean up some code issues that prevented Tor from building on older
2679 BSDs. Fixes bug 3894; reported by "grarpamp".
2680 - Search for a platform-specific version of "ar" when cross-compiling.
2681 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2684 Changes in version 0.2.2.32 - 2011-08-27
2685 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2686 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2687 a founder of the PETS community, a leader in our field, a mentor,
2688 and a friend. He left us with these words: "I had the possibility
2689 to contribute to this world that is not as it should be. I hope I
2690 could help in some areas to make the world a better place, and that
2691 I could also encourage other people to be engaged in improving the
2692 world. Please, stay engaged. This world needs you, your love, your
2693 initiative -- now I cannot be part of that anymore."
2695 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2696 ready. More than two years in the making, this release features improved
2697 client performance and hidden service reliability, better compatibility
2698 for Android, correct behavior for bridges that listen on more than
2699 one address, more extensible and flexible directory object handling,
2700 better reporting of network statistics, improved code security, and
2701 many many other features and bugfixes.
2703 o Major features (client performance):
2704 - When choosing which cells to relay first, relays now favor circuits
2705 that have been quiet recently, to provide lower latency for
2706 low-volume circuits. By default, relays enable or disable this
2707 feature based on a setting in the consensus. They can override
2708 this default by using the new "CircuitPriorityHalflife" config
2709 option. Design and code by Ian Goldberg, Can Tang, and Chris
2711 - Directory authorities now compute consensus weightings that instruct
2712 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
2713 and no flag. Clients use these weightings to distribute network load
2714 more evenly across these different relay types. The weightings are
2715 in the consensus so we can change them globally in the future. Extra
2716 thanks to "outofwords" for finding some nasty security bugs in
2717 the first implementation of this feature.
2719 o Major features (client performance, circuit build timeout):
2720 - Tor now tracks how long it takes to build client-side circuits
2721 over time, and adapts its timeout to local network performance.
2722 Since a circuit that takes a long time to build will also provide
2723 bad performance, we get significant latency improvements by
2724 discarding the slowest 20% of circuits. Specifically, Tor creates
2725 circuits more aggressively than usual until it has enough data
2726 points for a good timeout estimate. Implements proposal 151.
2727 - Circuit build timeout constants can be controlled by consensus
2728 parameters. We set good defaults for these parameters based on
2729 experimentation on broadband and simulated high-latency links.
2730 - Circuit build time learning can be disabled via consensus parameter
2731 or by the client via a LearnCircuitBuildTimeout config option. We
2732 also automatically disable circuit build time calculation if either
2733 AuthoritativeDirectory is set, or if we fail to write our state
2734 file. Implements ticket 1296.
2736 o Major features (relays use their capacity better):
2737 - Set SO_REUSEADDR socket option on all sockets, not just
2738 listeners. This should help busy exit nodes avoid running out of
2739 useable ports just because all the ports have been used in the
2740 near past. Resolves issue 2850.
2741 - Relays now save observed peak bandwidth throughput rates to their
2742 state file (along with total usage, which was already saved),
2743 so that they can determine their correct estimated bandwidth on
2744 restart. Resolves bug 1863, where Tor relays would reset their
2745 estimated bandwidth to 0 after restarting.
2746 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
2747 should give us approximately 40-50% more Guard-flagged nodes,
2748 improving the anonymity the Tor network can provide and also
2749 decreasing the dropoff in throughput that relays experience when
2750 they first get the Guard flag.
2751 - Directory authorities now take changes in router IP address and
2752 ORPort into account when determining router stability. Previously,
2753 if a router changed its IP or ORPort, the authorities would not
2754 treat it as having any downtime for the purposes of stability
2755 calculation, whereas clients would experience downtime since the
2756 change would take a while to propagate to them. Resolves issue 1035.
2757 - New AccelName and AccelDir options add support for dynamic OpenSSL
2758 hardware crypto acceleration engines.
2760 o Major features (relays control their load better):
2761 - Exit relays now try harder to block exit attempts from unknown
2762 relays, to make it harder for people to use them as one-hop proxies
2763 a la tortunnel. Controlled by the refuseunknownexits consensus
2764 parameter (currently enabled), or you can override it on your
2765 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
2766 based on a variant of proposal 163.
2767 - Add separate per-conn write limiting to go with the per-conn read
2768 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2769 but never per-conn write limits.
2770 - New consensus params "bwconnrate" and "bwconnburst" to let us
2771 rate-limit client connections as they enter the network. It's
2772 controlled in the consensus so we can turn it on and off for
2773 experiments. It's starting out off. Based on proposal 163.
2775 o Major features (controllers):
2776 - Export GeoIP information on bridge usage to controllers even if we
2777 have not yet been running for 24 hours. Now Vidalia bridge operators
2778 can get more accurate and immediate feedback about their
2779 contributions to the network.
2780 - Add an __OwningControllerProcess configuration option and a
2781 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2782 that when it exits, Tor will shut down. Implements feature 3049.
2784 o Major features (directory authorities):
2785 - Directory authorities now create, vote on, and serve multiple
2786 parallel formats of directory data as part of their voting process.
2787 Partially implements Proposal 162: "Publish the consensus in
2789 - Directory authorities now agree on and publish small summaries
2790 of router information that clients can use in place of regular
2791 server descriptors. This transition will allow Tor 0.2.3 clients
2792 to use far less bandwidth for downloading information about the
2793 network. Begins the implementation of Proposal 158: "Clients
2794 download consensus + microdescriptors".
2795 - The directory voting system is now extensible to use multiple hash
2796 algorithms for signatures and resource selection. Newer formats
2797 are signed with SHA256, with a possibility for moving to a better
2798 hash algorithm in the future.
2799 - Directory authorities can now vote on arbitary integer values as
2800 part of the consensus process. This is designed to help set
2801 network-wide parameters. Implements proposal 167.
2803 o Major features and bugfixes (node selection):
2804 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2805 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
2806 options. Previously, we had been ambiguous in describing what
2807 counted as an "exit" node, and what operations exactly "StrictNodes
2808 0" would permit. This created confusion when people saw nodes built
2809 through unexpected circuits, and made it hard to tell real bugs from
2810 surprises. Now the intended behavior is:
2811 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2812 a node that delivers user traffic outside the Tor network.
2813 . "Entry", in the context of EntryNodes, means a node used as the
2814 first hop of a multihop circuit. It doesn't include direct
2815 connections to directory servers.
2816 . "ExcludeNodes" applies to all nodes.
2817 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2818 StrictNodes is set, Tor should avoid all nodes listed in
2819 ExcludeNodes, even when it will make user requests fail. When
2820 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2821 whenever it can, except when it must use an excluded node to
2822 perform self-tests, connect to a hidden service, provide a
2823 hidden service, fulfill a .exit request, upload directory
2824 information, or fetch directory information.
2825 Collectively, the changes to implement the behavior fix bug 1090.
2826 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2827 change during a config reload, mark and discard all our origin
2828 circuits. This fix should address edge cases where we change the
2829 config options and but then choose a circuit that we created before
2831 - Make EntryNodes config option much more aggressive even when
2832 StrictNodes is not set. Before it would prepend your requested
2833 entrynodes to your list of guard nodes, but feel free to use others
2834 after that. Now it chooses only from your EntryNodes if any of
2835 those are available, and only falls back to others if a) they're
2836 all down and b) StrictNodes is not set.
2837 - Now we refresh your entry guards from EntryNodes at each consensus
2838 fetch -- rather than just at startup and then they slowly rot as
2839 the network changes.
2840 - Add support for the country code "{??}" in torrc options like
2841 ExcludeNodes, to indicate all routers of unknown country. Closes
2843 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2844 a node is listed in both, it's treated as excluded.
2845 - ExcludeNodes now applies to directory nodes -- as a preference if
2846 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2847 Don't exclude all the directory authorities and set StrictNodes to 1
2848 unless you really want your Tor to break.
2849 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2850 - ExcludeExitNodes now overrides .exit requests.
2851 - We don't use bridges listed in ExcludeNodes.
2852 - When StrictNodes is 1:
2853 . We now apply ExcludeNodes to hidden service introduction points
2854 and to rendezvous points selected by hidden service users. This
2855 can make your hidden service less reliable: use it with caution!
2856 . If we have used ExcludeNodes on ourself, do not try relay
2857 reachability self-tests.
2858 . If we have excluded all the directory authorities, we will not
2859 even try to upload our descriptor if we're a relay.
2860 . Do not honor .exit requests to an excluded node.
2861 - When the set of permitted nodes changes, we now remove any mappings
2862 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2864 - We never cannibalize a circuit that had excluded nodes on it, even
2865 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
2866 - Improve log messages related to excluded nodes.
2868 o Major features (misc):
2869 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
2870 to help Tor build correctly for Android phones.
2871 - The options SocksPort, ControlPort, and so on now all accept a
2872 value "auto" that opens a socket on an OS-selected port. A
2873 new ControlPortWriteToFile option tells Tor to write its
2874 actual control port or ports to a chosen file. If the option
2875 ControlPortFileGroupReadable is set, the file is created as
2876 group-readable. Now users can run two Tor clients on the same
2877 system without needing to manually mess with parameters. Resolves
2878 part of ticket 3076.
2879 - Tor now supports tunneling all of its outgoing connections over
2880 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
2881 configuration options. Code by Christopher Davis.
2883 o Code security improvements:
2884 - Replace all potentially sensitive memory comparison operations
2885 with versions whose runtime does not depend on the data being
2886 compared. This will help resist a class of attacks where an
2887 adversary can use variations in timing information to learn
2888 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2889 implementation by Robert Ransom based partially on code by DJB.)
2890 - Enable Address Space Layout Randomization (ASLR) and Data Execution
2891 Prevention (DEP) by default on Windows to make it harder for
2892 attackers to exploit vulnerabilities. Patch from John Brooks.
2893 - New "--enable-gcc-hardening" ./configure flag (off by default)
2894 to turn on gcc compile time hardening options. It ensures
2895 that signed ints have defined behavior (-fwrapv), enables
2896 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
2897 with canaries (-fstack-protector-all), turns on ASLR protection if
2898 supported by the kernel (-fPIE, -pie), and adds additional security
2899 related warnings. Verified to work on Mac OS X and Debian Lenny.
2900 - New "--enable-linker-hardening" ./configure flag (off by default)
2901 to turn on ELF specific hardening features (relro, now). This does
2902 not work with Mac OS X or any other non-ELF binary format.
2903 - Always search the Windows system directory for system DLLs, and
2904 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
2905 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
2906 current and future memory pages via mlockall(). On supported
2907 platforms (modern Linux and probably BSD but not Windows or OS X),
2908 this should effectively disable any and all attempts to page out
2909 memory. This option requires that you start your Tor as root --
2910 if you use DisableAllSwap, please consider using the User option
2911 to properly reduce the privileges of your Tor.
2913 o Major bugfixes (crashes):
2914 - Fix crash bug on platforms where gmtime and localtime can return
2915 NULL. Windows 7 users were running into this one. Fixes part of bug
2916 2077. Bugfix on all versions of Tor. Found by boboper.
2917 - Introduce minimum/maximum values that clients will believe
2918 from the consensus. Now we'll have a better chance to avoid crashes
2919 or worse when a consensus param has a weird value.
2920 - Fix a rare crash bug that could occur when a client was configured
2921 with a large number of bridges. Fixes bug 2629; bugfix on
2922 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2923 - Do not crash when our configuration file becomes unreadable, for
2924 example due to a permissions change, between when we start up
2925 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2927 - If we're in the pathological case where there's no exit bandwidth
2928 but there is non-exit bandwidth, or no guard bandwidth but there
2929 is non-guard bandwidth, don't crash during path selection. Bugfix
2931 - Fix a crash bug when trying to initialize the evdns module in
2932 Libevent 2. Bugfix on 0.2.1.16-rc.
2934 o Major bugfixes (stability):
2935 - Fix an assert in parsing router descriptors containing IPv6
2936 addresses. This one took down the directory authorities when
2937 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2938 - Fix an uncommon assertion failure when running with DNSPort under
2939 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2940 - Treat an unset $HOME like an empty $HOME rather than triggering an
2941 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
2942 - More gracefully handle corrupt state files, removing asserts
2943 in favor of saving a backup and resetting state.
2944 - Instead of giving an assertion failure on an internal mismatch
2945 on estimated freelist size, just log a BUG warning and try later.
2946 Mitigates but does not fix bug 1125.
2947 - Fix an assert that got triggered when using the TestingTorNetwork
2948 configuration option and then issuing a GETINFO config-text control
2949 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
2950 - If the cached cert file is unparseable, warn but don't exit.
2952 o Privacy fixes (relays/bridges):
2953 - Don't list Windows capabilities in relay descriptors. We never made
2954 use of them, and maybe it's a bad idea to publish them. Bugfix
2956 - If the Nickname configuration option isn't given, Tor would pick a
2957 nickname based on the local hostname as the nickname for a relay.
2958 Because nicknames are not very important in today's Tor and the
2959 "Unnamed" nickname has been implemented, this is now problematic
2960 behavior: It leaks information about the hostname without being
2961 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2962 introduced the Unnamed nickname. Reported by tagnaq.
2963 - Maintain separate TLS contexts and certificates for incoming and
2964 outgoing connections in bridge relays. Previously we would use the
2965 same TLS contexts and certs for incoming and outgoing connections.
2966 Bugfix on 0.2.0.3-alpha; addresses bug 988.
2967 - Maintain separate identity keys for incoming and outgoing TLS
2968 contexts in bridge relays. Previously we would use the same
2969 identity keys for incoming and outgoing TLS contexts. Bugfix on
2970 0.2.0.3-alpha; addresses the other half of bug 988.
2971 - Make the bridge directory authority refuse to answer directory
2972 requests for "all descriptors". It used to include bridge
2973 descriptors in its answer, which was a major information leak.
2974 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2976 o Privacy fixes (clients):
2977 - When receiving a hidden service descriptor, check that it is for
2978 the hidden service we wanted. Previously, Tor would store any
2979 hidden service descriptors that a directory gave it, whether it
2980 wanted them or not. This wouldn't have let an attacker impersonate
2981 a hidden service, but it did let directories pre-seed a client
2982 with descriptors that it didn't want. Bugfix on 0.0.6.
2983 - Start the process of disabling ".exit" address notation, since it
2984 can be used for a variety of esoteric application-level attacks
2985 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
2987 - Reject attempts at the client side to open connections to private
2988 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
2989 a randomly chosen exit node. Attempts to do so are always
2990 ill-defined, generally prevented by exit policies, and usually
2991 in error. This will also help to detect loops in transparent
2992 proxy configurations. You can disable this feature by setting
2993 "ClientRejectInternalAddresses 0" in your torrc.
2994 - Log a notice when we get a new control connection. Now it's easier
2995 for security-conscious users to recognize when a local application
2996 is knocking on their controller door. Suggested by bug 1196.
2998 o Privacy fixes (newnym):
2999 - Avoid linkability based on cached hidden service descriptors: forget
3000 all hidden service descriptors cached as a client when processing a
3001 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3002 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3003 DNS cache entries, and virtual address mappings: that's what
3004 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3005 - Don't attach new streams to old rendezvous circuits after SIGNAL
3006 NEWNYM. Previously, we would keep using an existing rendezvous
3007 circuit if it remained open (i.e. if it were kept open by a
3008 long-lived stream, or if a new stream were attached to it before
3009 Tor could notice that it was old and no longer in use). Bugfix on
3010 0.1.1.15-rc; fixes bug 3375.
3012 o Major bugfixes (relay bandwidth accounting):
3013 - Fix a bug that could break accounting on 64-bit systems with large
3014 time_t values, making them hibernate for impossibly long intervals.
3015 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3016 - Fix a bug in bandwidth accounting that could make us use twice
3017 the intended bandwidth when our interval start changes due to
3018 daylight saving time. Now we tolerate skew in stored vs computed
3019 interval starts: if the start of the period changes by no more than
3020 50% of the period's duration, we remember bytes that we transferred
3021 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3023 o Major bugfixes (bridges):
3024 - Bridges now use "reject *:*" as their default exit policy. Bugfix
3025 on 0.2.0.3-alpha. Fixes bug 1113.
3026 - If you configure your bridge with a known identity fingerprint,
3027 and the bridge authority is unreachable (as it is in at least
3028 one country now), fall back to directly requesting the descriptor
3029 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3031 - Fix a bug where bridge users who configure the non-canonical
3032 address of a bridge automatically switch to its canonical
3033 address. If a bridge listens at more than one address, it
3034 should be able to advertise those addresses independently and
3035 any non-blocked addresses should continue to work. Bugfix on Tor
3036 0.2.0.3-alpha. Fixes bug 2510.
3037 - If you configure Tor to use bridge A, and then quit and
3038 configure Tor to use bridge B instead (or if you change Tor
3039 to use bridge B via the controller), it would happily continue
3040 to use bridge A if it's still reachable. While this behavior is
3041 a feature if your goal is connectivity, in some scenarios it's a
3042 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3043 - When the controller configures a new bridge, don't wait 10 to 60
3044 seconds before trying to fetch its descriptor. Bugfix on
3045 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3047 o Major bugfixes (directory authorities):
3048 - Many relays have been falling out of the consensus lately because
3049 not enough authorities know about their descriptor for them to get
3050 a majority of votes. When we deprecated the v2 directory protocol,
3051 we got rid of the only way that v3 authorities can hear from each
3052 other about other descriptors. Now authorities examine every v3
3053 vote for new descriptors, and fetch them from that authority. Bugfix
3055 - Authorities could be tricked into giving out the Exit flag to relays
3056 that didn't allow exiting to any ports. This bug could screw
3057 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
3058 1238. Bug discovered by Martin Kowalczyk.
3059 - If all authorities restart at once right before a consensus vote,
3060 nobody will vote about "Running", and clients will get a consensus
3061 with no usable relays. Instead, authorities refuse to build a
3062 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
3064 o Major bugfixes (stream-level fairness):
3065 - When receiving a circuit-level SENDME for a blocked circuit, try
3066 to package cells fairly from all the streams that had previously
3067 been blocked on that circuit. Previously, we had started with the
3068 oldest stream, and allowed each stream to potentially exhaust
3069 the circuit's package window. This gave older streams on any
3070 given circuit priority over newer ones. Fixes bug 1937. Detected
3071 originally by Camilo Viecco. This bug was introduced before the
3072 first Tor release, in svn commit r152: it is the new winner of
3073 the longest-lived bug prize.
3074 - Fix a stream fairness bug that would cause newer streams on a given
3075 circuit to get preference when reading bytes from the origin or
3076 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3077 introduced before the first Tor release, in svn revision r152.
3078 - When the exit relay got a circuit-level sendme cell, it started
3079 reading on the exit streams, even if had 500 cells queued in the
3080 circuit queue already, so the circuit queue just grew and grew in
3081 some cases. We fix this by not re-enabling reading on receipt of a
3082 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3083 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3085 - Newly created streams were allowed to read cells onto circuits,
3086 even if the circuit's cell queue was blocked and waiting to drain.
3087 This created potential unfairness, as older streams would be
3088 blocked, but newer streams would gladly fill the queue completely.
3089 We add code to detect this situation and prevent any stream from
3090 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3093 o Major bugfixes (hidden services):
3094 - Apply circuit timeouts to opened hidden-service-related circuits
3095 based on the correct start time. Previously, we would apply the
3096 circuit build timeout based on time since the circuit's creation;
3097 it was supposed to be applied based on time since the circuit
3098 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3099 - Improve hidden service robustness: When we find that we have
3100 extended a hidden service's introduction circuit to a relay not
3101 listed as an introduction point in the HS descriptor we currently
3102 have, retry with an introduction point from the current
3103 descriptor. Previously we would just give up. Fixes bugs 1024 and
3104 1930; bugfix on 0.2.0.10-alpha.
3105 - Directory authorities now use data collected from their own
3106 uptime observations when choosing whether to assign the HSDir flag
3107 to relays, instead of trusting the uptime value the relay reports in
3108 its descriptor. This change helps prevent an attack where a small
3109 set of nodes with frequently-changing identity keys can blackhole
3110 a hidden service. (Only authorities need upgrade; others will be
3111 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3112 - Stop assigning the HSDir flag to relays that disable their
3113 DirPort (and thus will refuse to answer directory requests). This
3114 fix should dramatically improve the reachability of hidden services:
3115 hidden services and hidden service clients pick six HSDir relays
3116 to store and retrieve the hidden service descriptor, and currently
3117 about half of the HSDir relays will refuse to work. Bugfix on
3118 0.2.0.10-alpha; fixes part of bug 1693.
3120 o Major bugfixes (misc):
3121 - Clients now stop trying to use an exit node associated with a given
3122 destination by TrackHostExits if they fail to reach that exit node.
3123 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3124 - Fix a regression that caused Tor to rebind its ports if it receives
3125 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3126 - Remove an extra pair of quotation marks around the error
3127 message in control-port STATUS_GENERAL BUG events. Bugfix on
3128 0.1.2.6-alpha; fixes bug 3732.
3130 o Minor features (relays):
3131 - Ensure that no empty [dirreq-](read|write)-history lines are added
3132 to an extrainfo document. Implements ticket 2497.
3133 - When bandwidth accounting is enabled, be more generous with how
3134 much bandwidth we'll use up before entering "soft hibernation".
3135 Previously, we'd refuse new connections and circuits once we'd
3136 used up 95% of our allotment. Now, we use up 95% of our allotment,
3137 AND make sure that we have no more than 500MB (or 3 hours of
3138 expected traffic, whichever is lower) remaining before we enter
3140 - Relays now log the reason for publishing a new relay descriptor,
3141 so we have a better chance of hunting down instances of bug 1810.
3142 Resolves ticket 3252.
3143 - Log a little more clearly about the times at which we're no longer
3144 accepting new connections (e.g. due to hibernating). Resolves
3146 - When AllowSingleHopExits is set, print a warning to explain to the
3147 relay operator why most clients are avoiding her relay.
3148 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3149 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3150 clients are already deprecated because of security bugs.
3152 o Minor features (network statistics):
3153 - Directory mirrors that set "DirReqStatistics 1" write statistics
3154 about directory requests to disk every 24 hours. As compared to the
3155 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
3156 improvements: 1) stats are written to disk exactly every 24 hours;
3157 2) estimated shares of v2 and v3 requests are determined as mean
3158 values, not at the end of a measurement period; 3) unresolved
3159 requests are listed with country code '??'; 4) directories also
3160 measure download times.
3161 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
3162 number of exit streams and transferred bytes per port to disk every
3164 - Relays that set "CellStatistics 1" write statistics on how long
3165 cells spend in their circuit queues to disk every 24 hours.
3166 - Entry nodes that set "EntryStatistics 1" write statistics on the
3167 rough number and origins of connecting clients to disk every 24
3169 - Relays that write any of the above statistics to disk and set
3170 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
3171 their extra-info documents. Implements proposal 166.
3173 o Minor features (GeoIP and statistics):
3174 - Provide a log message stating which geoip file we're parsing
3175 instead of just stating that we're parsing the geoip file.
3176 Implements ticket 2432.
3177 - Make sure every relay writes a state file at least every 12 hours.
3178 Previously, a relay could go for weeks without writing its state
3179 file, and on a crash could lose its bandwidth history, capacity
3180 estimates, client country statistics, and so on. Addresses bug 3012.
3181 - Relays report the number of bytes spent on answering directory
3182 requests in extra-info descriptors similar to {read,write}-history.
3183 Implements enhancement 1790.
3184 - Report only the top 10 ports in exit-port stats in order not to
3185 exceed the maximum extra-info descriptor length of 50 KB. Implements
3187 - If writing the state file to disk fails, wait up to an hour before
3188 retrying again, rather than trying again each second. Fixes bug
3189 2346; bugfix on Tor 0.1.1.3-alpha.
3190 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3191 when we switch from being a public relay to a bridge. Otherwise
3192 there will still be clients that see the relay in their consensus,
3193 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
3195 - Update to the August 2 2011 Maxmind GeoLite Country database.
3197 o Minor features (clients):
3198 - When expiring circuits, use microsecond timers rather than
3199 one-second timers. This can avoid an unpleasant situation where a
3200 circuit is launched near the end of one second and expired right
3201 near the beginning of the next, and prevent fluctuations in circuit
3203 - If we've configured EntryNodes and our network goes away and/or all
3204 our entrynodes get marked down, optimistically retry them all when
3205 a new socks application request appears. Fixes bug 1882.
3206 - Always perform router selections using weighted relay bandwidth,
3207 even if we don't need a high capacity circuit at the time. Non-fast
3208 circuits now only differ from fast ones in that they can use relays
3209 not marked with the Fast flag. This "feature" could turn out to
3210 be a horrible bug; we should investigate more before it goes into
3212 - When we run out of directory information such that we can't build
3213 circuits, but then get enough that we can build circuits, log when
3214 we actually construct a circuit, so the user has a better chance of
3215 knowing what's going on. Fixes bug 1362.
3216 - Log SSL state transitions at debug level during handshake, and
3217 include SSL states in error messages. This may help debug future
3218 SSL handshake issues.
3220 o Minor features (directory authorities):
3221 - When a router changes IP address or port, authorities now launch
3222 a new reachability test for it. Implements ticket 1899.
3223 - Directory authorities now reject relays running any versions of
3224 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3225 known bugs that keep RELAY_EARLY cells from working on rendezvous
3226 circuits. Followup to fix for bug 2081.
3227 - Directory authorities now reject relays running any version of Tor
3228 older than 0.2.0.26-rc. That version is the earliest that fetches
3229 current directory information correctly. Fixes bug 2156.
3230 - Directory authorities now do an immediate reachability check as soon
3231 as they hear about a new relay. This change should slightly reduce
3232 the time between setting up a relay and getting listed as running
3233 in the consensus. It should also improve the time between setting
3234 up a bridge and seeing use by bridge users.
3235 - Directory authorities no longer launch a TLS connection to every
3236 relay as they startup. Now that we have 2k+ descriptors cached,
3237 the resulting network hiccup is becoming a burden. Besides,
3238 authorities already avoid voting about Running for the first half
3239 hour of their uptime.
3240 - Directory authorities now log the source of a rejected POSTed v3
3241 networkstatus vote, so we can track failures better.
3242 - Backport code from 0.2.3.x that allows directory authorities to
3243 clean their microdescriptor caches. Needed to resolve bug 2230.
3245 o Minor features (hidden services):
3246 - Use computed circuit-build timeouts to decide when to launch
3247 parallel introduction circuits for hidden services. (Previously,
3248 we would retry after 15 seconds.)
3249 - Don't allow v0 hidden service authorities to act as clients.
3250 Required by fix for bug 3000.
3251 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3252 by fix for bug 3000.
3253 - Make hidden services work better in private Tor networks by not
3254 requiring any uptime to join the hidden service descriptor
3255 DHT. Implements ticket 2088.
3256 - Log (at info level) when purging pieces of hidden-service-client
3257 state because of SIGNAL NEWNYM.
3259 o Minor features (controller interface):
3260 - New "GETINFO net/listeners/(type)" controller command to return
3261 a list of addresses and ports that are bound for listeners for a
3262 given connection type. This is useful when the user has configured
3263 "SocksPort auto" and the controller needs to know which port got
3264 chosen. Resolves another part of ticket 3076.
3265 - Have the controller interface give a more useful message than
3266 "Internal Error" in response to failed GETINFO requests.
3267 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3268 event, to give information on the current rate of circuit timeouts
3269 over our stored history.
3270 - The 'EXTENDCIRCUIT' control port command can now be used with
3271 a circ id of 0 and no path. This feature will cause Tor to build
3272 a new 'fast' general purpose circuit using its own path selection
3274 - Added a BUILDTIMEOUT_SET controller event to describe changes
3275 to the circuit build timeout.
3276 - New controller command "getinfo config-text". It returns the
3277 contents that Tor would write if you send it a SAVECONF command,
3278 so the controller can write the file to disk itself.
3280 o Minor features (controller protocol):
3281 - Add a new ControlSocketsGroupWritable configuration option: when
3282 it is turned on, ControlSockets are group-writeable by the default
3283 group of the current user. Patch by Jérémy Bobbio; implements
3285 - Tor now refuses to create a ControlSocket in a directory that is
3286 world-readable (or group-readable if ControlSocketsGroupWritable
3287 is 0). This is necessary because some operating systems do not
3288 enforce permissions on an AF_UNIX sockets. Permissions on the
3289 directory holding the socket, however, seems to work everywhere.
3290 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3291 not. This would lead to a cookie that is still not group readable.
3292 Closes bug 1843. Suggested by katmagic.
3293 - Future-proof the controller protocol a bit by ignoring keyword
3294 arguments we do not recognize.
3296 o Minor features (more useful logging):
3297 - Revise most log messages that refer to nodes by nickname to
3298 instead use the "$key=nickname at address" format. This should be
3299 more useful, especially since nicknames are less and less likely
3300 to be unique. Resolves ticket 3045.
3301 - When an HTTPS proxy reports "403 Forbidden", we now explain
3302 what it means rather than calling it an unexpected status code.
3303 Closes bug 2503. Patch from Michael Yakubovich.
3304 - Rate-limit a warning about failures to download v2 networkstatus
3305 documents. Resolves part of bug 1352.
3306 - Rate-limit the "your application is giving Tor only an IP address"
3307 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3308 - Rate-limit "Failed to hand off onionskin" warnings.
3309 - When logging a rate-limited warning, we now mention how many messages
3310 got suppressed since the last warning.
3311 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3312 2 no signature, 4 required" messages about consensus signatures
3313 easier to read, and make sure they get logged at the same severity
3314 as the messages explaining which keys are which. Fixes bug 1290.
3315 - Don't warn when we have a consensus that we can't verify because
3316 of missing certificates, unless those certificates are ones
3317 that we have been trying and failing to download. Fixes bug 1145.
3319 o Minor features (log domains):
3320 - Add documentation for configuring logging at different severities in
3321 different log domains. We've had this feature since 0.2.1.1-alpha,
3322 but for some reason it never made it into the manpage. Fixes
3324 - Make it simpler to specify "All log domains except for A and B".
3325 Previously you needed to say "[*,~A,~B]". Now you can just say
3327 - Add a "LogMessageDomains 1" option to include the domains of log
3328 messages along with the messages. Without this, there's no way
3329 to use log domains without reading the source or doing a lot
3331 - Add a new "Handshake" log domain for activities that happen
3332 during the TLS handshake.
3334 o Minor features (build process):
3335 - Make compilation with clang possible when using
3336 "--enable-gcc-warnings" by removing two warning options that clang
3337 hasn't implemented yet and by fixing a few warnings. Resolves
3339 - Detect platforms that brokenly use a signed size_t, and refuse to
3340 build there. Found and analyzed by doorss and rransom.
3341 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3343 - Add support for statically linking zlib by specifying
3344 "--enable-static-zlib", to go with our support for statically
3345 linking openssl and libevent. Resolves bug 1358.
3346 - Instead of adding the svn revision to the Tor version string, report
3347 the git commit (when we're building from a git checkout).
3348 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3350 - New --digests command-line switch to output the digests of the
3351 source files Tor was built with.
3352 - Generate our manpage and HTML documentation using Asciidoc. This
3353 change should make it easier to maintain the documentation, and
3354 produce nicer HTML. The build process fails if asciidoc cannot
3355 be found and building with asciidoc isn't disabled (via the
3356 "--disable-asciidoc" argument to ./configure. Skipping the manpage
3357 speeds up the build considerably.
3359 o Minor features (options / torrc):
3360 - Warn when the same option is provided more than once in a torrc
3361 file, on the command line, or in a single SETCONF statement, and
3362 the option is one that only accepts a single line. Closes bug 1384.
3363 - Warn when the user configures two HiddenServiceDir lines that point
3364 to the same directory. Bugfix on 0.0.6 (the version introducing
3365 HiddenServiceDir); fixes bug 3289.
3366 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3367 do individual connection-level rate limiting of clients. The torrc
3368 config options with the same names trump the consensus params, if
3369 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3370 consensus params which were broken from 0.2.2.7-alpha through
3371 0.2.2.14-alpha. Closes bug 1947.
3372 - New config option "WarnUnsafeSocks 0" disables the warning that
3373 occurs whenever Tor receives a socks handshake using a version of
3374 the socks protocol that can only provide an IP address (rather
3375 than a hostname). Setups that do DNS locally over Tor are fine,
3376 and we shouldn't spam the logs in that case.
3377 - New config option "CircuitStreamTimeout" to override our internal
3378 timeout schedule for how many seconds until we detach a stream from
3379 a circuit and try a new circuit. If your network is particularly
3380 slow, you might want to set this to a number like 60.
3381 - New options for SafeLogging to allow scrubbing only log messages
3382 generated while acting as a relay. Specify "SafeLogging relay" if
3383 you want to ensure that only messages known to originate from
3384 client use of the Tor process will be logged unsafely.
3385 - Time and memory units in the configuration file can now be set to
3386 fractional units. For example, "2.5 GB" is now a valid value for
3388 - Support line continuations in the torrc config file. If a line
3389 ends with a single backslash character, the newline is ignored, and
3390 the configuration value is treated as continuing on the next line.
3393 o Minor features (unit tests):
3394 - Revise our unit tests to use the "tinytest" framework, so we
3395 can run tests in their own processes, have smarter setup/teardown
3396 code, and so on. The unit test code has moved to its own
3397 subdirectory, and has been split into multiple modules.
3398 - Add a unit test for cross-platform directory-listing code.
3399 - Add some forgotten return value checks during unit tests. Found
3401 - Use GetTempDir to find the proper temporary directory location on
3402 Windows when generating temporary files for the unit tests. Patch
3405 o Minor features (misc):
3406 - The "torify" script now uses torsocks where available.
3407 - Make Libevent log messages get delivered to controllers later,
3408 and not from inside the Libevent log handler. This prevents unsafe
3409 reentrant Libevent calls while still letting the log messages
3411 - Certain Tor clients (such as those behind check.torproject.org) may
3412 want to fetch the consensus in an extra early manner. To enable this
3413 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
3414 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
3415 as only certain clients who must have this information sooner should
3417 - Expand homedirs passed to tor-checkkey. This should silence a
3418 coverity complaint about passing a user-supplied string into
3419 open() without checking it.
3420 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3421 used on bridges, and it makes bridge scanning somewhat easier.
3422 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3423 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3425 o Minor bugfixes (relays):
3426 - When a relay decides that its DNS is too broken for it to serve
3427 as an exit server, it advertised itself as a non-exit, but
3428 continued to act as an exit. This could create accidental
3429 partitioning opportunities for users. Instead, if a relay is
3430 going to advertise reject *:* as its exit policy, it should
3431 really act with exit policy "reject *:*". Fixes bug 2366.
3432 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3433 - Publish a router descriptor even if generating an extra-info
3434 descriptor fails. Previously we would not publish a router
3435 descriptor without an extra-info descriptor; this can cause fast
3436 exit relays collecting exit-port statistics to drop from the
3437 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3438 - When we're trying to guess whether we know our IP address as
3439 a relay, we would log various ways that we failed to guess
3440 our address, but never log that we ended up guessing it
3441 successfully. Now add a log line to help confused and anxious
3442 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3443 - For bandwidth accounting, calculate our expected bandwidth rate
3444 based on the time during which we were active and not in
3445 soft-hibernation during the last interval. Previously, we were
3446 also considering the time spent in soft-hibernation. If this
3447 was a long time, we would wind up underestimating our bandwidth
3448 by a lot, and skewing our wakeup time towards the start of the
3449 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3450 - Demote a confusing TLS warning that relay operators might get when
3451 someone tries to talk to their ORPort. It is not the operator's
3452 fault, nor can they do anything about it. Fixes bug 1364; bugfix
3454 - Change "Application request when we're believed to be offline."
3455 notice to "Application request when we haven't used client
3456 functionality lately.", to clarify that it's not an error. Bugfix
3457 on 0.0.9.3; fixes bug 1222.
3459 o Minor bugfixes (bridges):
3460 - When a client starts or stops using bridges, never use a circuit
3461 that was built before the configuration change. This behavior could
3462 put at risk a user who uses bridges to ensure that her traffic
3463 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3465 - Do not reset the bridge descriptor download status every time we
3466 re-parse our configuration or get a configuration change. Fixes
3467 bug 3019; bugfix on 0.2.0.3-alpha.
3468 - Users couldn't configure a regular relay to be their bridge. It
3469 didn't work because when Tor fetched the bridge descriptor, it found
3470 that it already had it, and didn't realize that the purpose of the
3471 descriptor had changed. Now we replace routers with a purpose other
3472 than bridge with bridge descriptors when fetching them. Bugfix on
3473 0.1.1.9-alpha. Fixes bug 1776.
3474 - In the special case where you configure a public exit relay as your
3475 bridge, Tor would be willing to use that exit relay as the last
3476 hop in your circuit as well. Now we fail that circuit instead.
3477 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3479 o Minor bugfixes (clients):
3480 - We now ask the other side of a stream (the client or the exit)
3481 for more data on that stream when the amount of queued data on
3482 that stream dips low enough. Previously, we wouldn't ask the
3483 other side for more data until either it sent us more data (which
3484 it wasn't supposed to do if it had exhausted its window!) or we
3485 had completely flushed all our queued data. This flow control fix
3486 should improve throughput. Fixes bug 2756; bugfix on the earliest
3487 released versions of Tor (svn commit r152).
3488 - When a client finds that an origin circuit has run out of 16-bit
3489 stream IDs, we now mark it as unusable for new streams. Previously,
3490 we would try to close the entire circuit. Bugfix on 0.0.6.
3491 - Make it explicit that we don't cannibalize one-hop circuits. This
3492 happens in the wild, but doesn't turn out to be a problem because
3493 we fortunately don't use those circuits. Many thanks to outofwords
3494 for the initial analysis and to swissknife who confirmed that
3495 two-hop circuits are actually created.
3496 - Resolve an edge case in path weighting that could make us misweight
3497 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
3498 - Make the DNSPort option work with libevent 2.x. Don't alter the
3499 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
3501 o Minor bugfixes (directory authorities):
3502 - Make directory authorities more accurate at recording when
3503 relays that have failed several reachability tests became
3504 unreachable, so we can provide more accuracy at assigning Stable,
3505 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3506 - Directory authorities are now more robust to hops back in time
3507 when calculating router stability. Previously, if a run of uptime
3508 or downtime appeared to be negative, the calculation could give
3509 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3511 - Directory authorities will now attempt to download consensuses
3512 if their own efforts to make a live consensus have failed. This
3513 change means authorities that restart will fetch a valid
3514 consensus, and it means authorities that didn't agree with the
3515 current consensus will still fetch and serve it if it has enough
3516 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
3517 - Never vote for a server as "Running" if we have a descriptor for
3518 it claiming to be hibernating, and that descriptor was published
3519 more recently than our last contact with the server. Bugfix on
3520 0.2.0.3-alpha; fixes bug 911.
3521 - Directory authorities no longer change their opinion of, or vote on,
3522 whether a router is Running, unless they have themselves been
3523 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
3526 o Minor bugfixes (hidden services):
3527 - Log malformed requests for rendezvous descriptors as protocol
3528 warnings, not warnings. Also, use a more informative log message
3529 in case someone sees it at log level warning without prior
3530 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
3531 - Accept hidden service descriptors if we think we might be a hidden
3532 service directory, regardless of what our consensus says. This
3533 helps robustness, since clients and hidden services can sometimes
3534 have a more up-to-date view of the network consensus than we do,
3535 and if they think that the directory authorities list us a HSDir,
3536 we might actually be one. Related to bug 2732; bugfix on
3538 - Correct the warning displayed when a rendezvous descriptor exceeds
3539 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3541 - Clients and hidden services now use HSDir-flagged relays for hidden
3542 service descriptor downloads and uploads even if the relays have no
3543 DirPort set and the client has disabled TunnelDirConns. This will
3544 eventually allow us to give the HSDir flag to relays with no
3545 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3546 - Only limit the lengths of single HS descriptors, even when multiple
3547 HS descriptors are published to an HSDir relay in a single POST
3548 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3550 o Minor bugfixes (controllers):
3551 - Allow GETINFO fingerprint to return a fingerprint even when
3552 we have not yet built a router descriptor. Fixes bug 3577;
3553 bugfix on 0.2.0.1-alpha.
3554 - Send a SUCCEEDED stream event to the controller when a reverse
3555 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3556 discovered by katmagic.
3557 - Remove a trailing asterisk from "exit-policy/default" in the
3558 output of the control port command "GETINFO info/names". Bugfix
3560 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
3561 2917. Bugfix on 0.1.1.1-alpha.
3562 - When we restart our relay, we might get a successful connection
3563 from the outside before we've started our reachability tests,
3564 triggering a warning: "ORPort found reachable, but I have no
3565 routerinfo yet. Failing to inform controller of success." This
3566 bug was harmless unless Tor is running under a controller
3567 like Vidalia, in which case the controller would never get a
3568 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3570 - When a controller changes TrackHostExits, remove mappings for
3571 hosts that should no longer have their exits tracked. Bugfix on
3573 - When a controller changes VirtualAddrNetwork, remove any mappings
3574 for hosts that were automapped to the old network. Bugfix on
3576 - When a controller changes one of the AutomapHosts* options, remove
3577 any mappings for hosts that should no longer be automapped. Bugfix
3579 - Fix an off-by-one error in calculating some controller command
3580 argument lengths. Fortunately, this mistake is harmless since
3581 the controller code does redundant NUL termination too. Found by
3582 boboper. Bugfix on 0.1.1.1-alpha.
3583 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
3584 would return "551 Internal error" rather than "552 Unrecognized key
3585 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
3586 - Don't spam the controller with events when we have no file
3587 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
3588 for log messages was already solved from bug 748.)
3589 - Emit a GUARD DROPPED controller event for a case we missed.
3590 - Ensure DNS requests launched by "RESOLVE" commands from the
3591 controller respect the __LeaveStreamsUnattached setconf options. The
3592 same goes for requests launched via DNSPort or transparent
3593 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3595 o Minor bugfixes (config options):
3596 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3597 Change the limit to 512 characters by removing base64 newlines.
3598 Fixes bug 2752. Fix by Michael Yakubovich.
3599 - Complain if PublishServerDescriptor is given multiple arguments that
3600 include 0 or 1. This configuration will be rejected in the future.
3601 Bugfix on 0.2.0.1-alpha; closes bug 1107.
3602 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
3603 Bugfix on 0.2.0.13-alpha; closes bug 928.
3605 o Minor bugfixes (log subsystem fixes):
3606 - When unable to format an address as a string, report its value
3607 as "???" rather than reusing the last formatted address. Bugfix
3609 - Be more consistent in our treatment of file system paths. "~" should
3610 get expanded to the user's home directory in the Log config option.
3611 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3612 feature for the -f and --DataDirectory options.
3614 o Minor bugfixes (memory management):
3615 - Don't stack-allocate the list of supplementary GIDs when we're
3616 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3617 could take up to 256K, which is way too much stack. Found by
3618 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3619 - Save a couple bytes in memory allocation every time we escape
3620 certain characters in a string. Patch from Florian Zumbiehl.
3622 o Minor bugfixes (protocol correctness):
3623 - When checking for 1024-bit keys, check for 1024 bits, not 128
3624 bytes. This allows Tor to correctly discard keys of length 1017
3625 through 1023. Bugfix on 0.0.9pre5.
3626 - Require that introduction point keys and onion handshake keys
3627 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3629 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3630 than waiting forever for them to finish. Fixes bug 2330; bugfix
3631 on 0.2.0.16-alpha. Found by doorss.
3632 - Never relay a cell for a circuit we have already destroyed.
3633 Between marking a circuit as closeable and finally closing it,
3634 it may have been possible for a few queued cells to get relayed,
3635 even though they would have been immediately dropped by the next
3636 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3637 - Never queue a cell for a circuit that's already been marked
3639 - Fix a spec conformance issue: the network-status-version token
3640 must be the first token in a v3 consensus or vote. Discovered by
3641 "parakeep". Bugfix on 0.2.0.3-alpha.
3642 - A networkstatus vote must contain exactly one signature. Spec
3643 conformance issue. Bugfix on 0.2.0.3-alpha.
3644 - When asked about a DNS record type we don't support via a
3645 client DNSPort, reply with NOTIMPL rather than an empty
3646 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
3647 - Make more fields in the controller protocol case-insensitive, since
3648 control-spec.txt said they were.
3650 o Minor bugfixes (log messages):
3651 - Fix a log message that said "bits" while displaying a value in
3652 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
3654 - Downgrade "no current certificates known for authority" message from
3655 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3656 - Correctly describe errors that occur when generating a TLS object.
3657 Previously we would attribute them to a failure while generating a
3658 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3660 - Fix an instance where a Tor directory mirror might accidentally
3661 log the IP address of a misbehaving Tor client. Bugfix on
3663 - Stop logging at severity 'warn' when some other Tor client tries
3664 to establish a circuit with us using weak DH keys. It's a protocol
3665 violation, but that doesn't mean ordinary users need to hear about
3666 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
3667 - If your relay can't keep up with the number of incoming create
3668 cells, it would log one warning per failure into your logs. Limit
3669 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
3671 o Minor bugfixes (build fixes):
3672 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3673 - When warning about missing zlib development packages during compile,
3674 give the correct package names. Bugfix on 0.2.0.1-alpha.
3675 - Fix warnings that newer versions of autoconf produce during
3676 ./autogen.sh. These warnings appear to be harmless in our case,
3677 but they were extremely verbose. Fixes bug 2020.
3678 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3681 o Minor bugfixes (portability):
3682 - Write several files in text mode, on OSes that distinguish text
3683 mode from binary mode (namely, Windows). These files are:
3684 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3685 that collect those statistics; 'client_keys' and 'hostname' for
3686 hidden services that use authentication; and (in the tor-gencert
3687 utility) newly generated identity and signing keys. Previously,
3688 we wouldn't specify text mode or binary mode, leading to an
3689 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3690 the DirRecordUsageByCountry option which would have triggered
3691 the assertion failure was added), although this assertion failure
3692 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3693 - Selectively disable deprecation warnings on OS X because Lion
3694 started deprecating the shipped copy of openssl. Fixes bug 3643.
3695 - Use a wide type to hold sockets when built for 64-bit Windows.
3697 - Fix an issue that prevented static linking of libevent on
3698 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
3699 where we introduced the "--with-static-libevent" configure option.
3700 - Fix a bug with our locking implementation on Windows that couldn't
3701 correctly detect when a file was already locked. Fixes bug 2504,
3702 bugfix on 0.2.1.6-alpha.
3703 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3705 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3706 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3709 o Minor bugfixes (code correctness):
3710 - Always NUL-terminate the sun_path field of a sockaddr_un before
3711 passing it to the kernel. (Not a security issue: kernels are
3712 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3713 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3714 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3715 expect it to emit a CRLF iff the format string ends with CRLF;
3716 it actually emitted a CRLF iff (a) the format string ended with
3717 CRLF or (b) the resulting string was over 1023 characters long or
3718 (c) the format string did not end with CRLF *and* the resulting
3719 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3720 fixes part of bug 3407.
3721 - Make send_control_event_impl()'s behaviour sane. Its callers
3722 expect it to always emit a CRLF at the end of the string; it
3723 might have emitted extra control characters as well. Bugfix on
3724 0.1.1.9-alpha; fixes another part of bug 3407.
3725 - Make crypto_rand_int() check the value of its input correctly.
3726 Previously, it accepted values up to UINT_MAX, but could return a
3727 negative number if given a value above INT_MAX+1. Found by George
3728 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3729 - Fix a potential null-pointer dereference while computing a
3730 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3732 - If we fail to compute the identity digest of a v3 legacy keypair,
3733 warn, and don't use a buffer-full of junk instead. Bugfix on
3734 0.2.1.1-alpha; fixes bug 3106.
3735 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3736 where if the function had ever in the future been used to check
3737 for the presence of a too-large number, it would have given an
3738 incorrect result. (Fortunately, we only used it for 16-bit
3739 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3740 - Be more careful about reporting the correct error from a failed
3741 connect() system call. Under some circumstances, it was possible to
3742 look at an incorrect value for errno when sending the end reason.
3743 Bugfix on 0.1.0.1-rc.
3744 - Correctly handle an "impossible" overflow cases in connection byte
3745 counting, where we write or read more than 4GB on an edge connection
3746 in a single second. Bugfix on 0.1.2.8-beta.
3747 - Avoid a double mark-for-free warning when failing to attach a
3748 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3750 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3751 found by "cypherpunks". This bug was introduced before the first
3752 Tor release, in svn commit r110.
3753 - Fix a bug in bandwidth history state parsing that could have been
3754 triggered if a future version of Tor ever changed the timing
3755 granularity at which bandwidth history is measured. Bugfix on
3757 - Add assertions to check for overflow in arguments to
3758 base32_encode() and base32_decode(); fix a signed-unsigned
3759 comparison there too. These bugs are not actually reachable in Tor,
3760 but it's good to prevent future errors too. Found by doorss.
3761 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
3763 - Set target port in get_interface_address6() correctly. Bugfix
3764 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3765 - Fix an impossible-to-actually-trigger buffer overflow in relay
3766 descriptor generation. Bugfix on 0.1.0.15.
3767 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
3769 o Minor bugfixes (code improvements):
3770 - After we free an internal connection structure, overwrite it
3771 with a different memory value than we use for overwriting a freed
3772 internal circuit structure. Should help with debugging. Suggested
3774 - If OpenSSL fails to make a duplicate of a private or public key, log
3775 an error message and try to exit cleanly. May help with debugging
3776 if bug 1209 ever remanifests.
3777 - Some options used different conventions for uppercasing of acronyms
3778 when comparing manpage and source. Fix those in favor of the
3779 manpage, as it makes sense to capitalize acronyms.
3780 - Take a first step towards making or.h smaller by splitting out
3781 function definitions for all source files in src/or/. Leave
3782 structures and defines in or.h for now.
3783 - Remove a few dead assignments during router parsing. Found by
3785 - Don't use 1-bit wide signed bit fields. Found by coverity.
3786 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3787 None of the cases where we did this before were wrong, but by making
3788 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3789 - The memarea code now uses a sentinel value at the end of each area
3790 to make sure nothing writes beyond the end of an area. This might
3791 help debug some conceivable causes of bug 930.
3792 - Always treat failure to allocate an RSA key as an unrecoverable
3794 - Add some more defensive programming for architectures that can't
3795 handle unaligned integer accesses. We don't know of any actual bugs
3796 right now, but that's the best time to fix them. Fixes bug 1943.
3798 o Minor bugfixes (misc):
3799 - Fix a rare bug in rend_fn unit tests: we would fail a test when
3800 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
3801 on 0.2.0.10-alpha; fixes bug 1808.
3802 - Where available, use Libevent 2.0's periodic timers so that our
3803 once-per-second cleanup code gets called even more closely to
3804 once per second than it would otherwise. Fixes bug 943.
3805 - Ignore OutboundBindAddress when connecting to localhost.
3806 Connections to localhost need to come _from_ localhost, or else
3807 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
3809 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
3811 - If any of the v3 certs we download are unparseable, we should
3812 actually notice the failure so we don't retry indefinitely. Bugfix
3813 on 0.2.0.x; reported by "rotator".
3814 - When Tor fails to parse a descriptor of any kind, dump it to disk.
3815 Might help diagnosing bug 1051.
3816 - Make our 'torify' script more portable; if we have only one of
3817 'torsocks' or 'tsocks' installed, don't complain to the user;
3818 and explain our warning about tsocks better.
3819 - Fix some urls in the exit notice file and make it XHTML1.1 strict
3820 compliant. Based on a patch from Christian Kujau.
3822 o Documentation changes:
3823 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3824 - Resolve all doxygen warnings except those for missing documentation.
3826 - Add doxygen documentation for more functions, fields, and types.
3827 - Convert the HACKING file to asciidoc, and add a few new sections
3828 to it, explaining how we use Git, how we make changelogs, and
3829 what should go in a patch.
3830 - Document the default socks host and port (127.0.0.1:9050) for
3832 - Removed some unnecessary files from the source distribution. The
3833 AUTHORS file has now been merged into the people page on the
3834 website. The roadmaps and design doc can now be found in the
3835 projects directory in svn.
3837 o Deprecated and removed features (config):
3838 - Remove the torrc.complete file. It hasn't been kept up to date
3839 and users will have better luck checking out the manpage.
3840 - Remove the HSAuthorityRecordStats option that version 0 hidden
3841 service authorities could use to track statistics of overall v0
3842 hidden service usage.
3843 - Remove the obsolete "NoPublish" option; it has been flagged
3844 as obsolete and has produced a warning since 0.1.1.18-rc.
3845 - Caches no longer download and serve v2 networkstatus documents
3846 unless FetchV2Networkstatus flag is set: these documents haven't
3847 haven't been used by clients or relays since 0.2.0.x. Resolves
3850 o Deprecated and removed features (controller):
3851 - The controller no longer accepts the old obsolete "addr-mappings/"
3852 or "unregistered-servers-" GETINFO values.
3853 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
3854 always on; using them is necessary for correct forward-compatible
3857 o Deprecated and removed features (misc):
3858 - Hidden services no longer publish version 0 descriptors, and clients
3859 do not request or use version 0 descriptors. However, the old hidden
3860 service authorities still accept and serve version 0 descriptors
3861 when contacted by older hidden services/clients.
3862 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3863 anything since 0.2.1.16-rc.
3864 - Remove everything related to building the expert bundle for OS X.
3865 It has confused many users, doesn't work right on OS X 10.6,
3866 and is hard to get rid of once installed. Resolves bug 1274.
3867 - Remove support for .noconnect style addresses. Nobody was using
3868 them, and they provided another avenue for detecting Tor users
3869 via application-level web tricks.
3870 - When we fixed bug 1038 we had to put in a restriction not to send
3871 RELAY_EARLY cells on rend circuits. This was necessary as long
3872 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3873 active. Now remove this obsolete check. Resolves bug 2081.
3874 - Remove workaround code to handle directory responses from servers
3875 that had bug 539 (they would send HTTP status 503 responses _and_
3876 send a body too). Since only server versions before
3877 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3878 keep the workaround in place.
3879 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3880 handling calculations where we have a known amount of clock skew and
3881 an allowed amount of unknown skew. But we only used it in three
3882 places, and we never adjusted the known/unknown skew values. This is
3883 still something we might want to do someday, but if we do, we'll
3884 want to do it differently.
3885 - Remove the "--enable-iphone" option to ./configure. According to
3886 reports from Marco Bonetti, Tor builds fine without any special
3887 tweaking on recent iPhone SDK versions.
3890 Changes in version 0.2.1.30 - 2011-02-23
3891 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3892 change is a slight tweak to Tor's TLS handshake that makes relays
3893 and bridges that run this new version reachable from Iran again.
3894 We don't expect this tweak will win the arms race long-term, but it
3895 buys us time until we roll out a better solution.
3898 - Stop sending a CLOCK_SKEW controller status event whenever
3899 we fetch directory information from a relay that has a wrong clock.
3900 Instead, only inform the controller when it's a trusted authority
3901 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3902 the rest of bug 1074.
3903 - Fix a bounds-checking error that could allow an attacker to
3904 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3906 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3907 Tor would ignore their RelayBandwidthBurst setting,
3908 potentially using more bandwidth than expected. Bugfix on
3909 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3910 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3911 hidserv" in her torrc. The 'hidserv' argument never controlled
3912 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3915 - Adjust our TLS Diffie-Hellman parameters to match those used by
3917 - Update to the February 1 2011 Maxmind GeoLite Country database.
3920 - Check for and reject overly long directory certificates and
3921 directory tokens before they have a chance to hit any assertions.
3922 Bugfix on 0.2.1.28. Found by "doorss".
3923 - Bring the logic that gathers routerinfos and assesses the
3924 acceptability of circuits into line. This prevents a Tor OP from
3925 getting locked in a cycle of choosing its local OR as an exit for a
3926 path (due to a .exit request) and then rejecting the circuit because
3927 its OR is not listed yet. It also prevents Tor clients from using an
3928 OR running in the same instance as an exit (due to a .exit request)
3929 if the OR does not meet the same requirements expected of an OR
3930 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3932 o Packaging changes:
3933 - Stop shipping the Tor specs files and development proposal documents
3934 in the tarball. They are now in a separate git repository at
3935 git://git.torproject.org/torspec.git
3936 - Do not include Git version tags as though they are SVN tags when
3937 generating a tarball from inside a repository that has switched
3938 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3941 Changes in version 0.2.1.29 - 2011-01-15
3942 Tor 0.2.1.29 continues our recent code security audit work. The main
3943 fix resolves a remote heap overflow vulnerability that can allow remote
3944 code execution. Other fixes address a variety of assert and crash bugs,
3945 most of which we think are hard to exploit remotely.
3947 o Major bugfixes (security):
3948 - Fix a heap overflow bug where an adversary could cause heap
3949 corruption. This bug probably allows remote code execution
3950 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3952 - Prevent a denial-of-service attack by disallowing any
3953 zlib-compressed data whose compression factor is implausibly
3954 high. Fixes part of bug 2324; reported by "doorss".
3955 - Zero out a few more keys in memory before freeing them. Fixes
3956 bug 2384 and part of bug 2385. These key instances found by
3957 "cypherpunks", based on Andrew Case's report about being able
3958 to find sensitive data in Tor's memory space if you have enough
3959 permissions. Bugfix on 0.0.2pre9.
3961 o Major bugfixes (crashes):
3962 - Prevent calls to Libevent from inside Libevent log handlers.
3963 This had potential to cause a nasty set of crashes, especially
3964 if running Libevent with debug logging enabled, and running
3965 Tor with a controller watching for low-severity log messages.
3966 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3967 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3968 underflow errors there too. Fixes the other part of bug 2324.
3969 - Fix a bug where we would assert if we ever had a
3970 cached-descriptors.new file (or another file read directly into
3971 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3972 on 0.2.1.25. Found by doorss.
3973 - Fix some potential asserts and parsing issues with grossly
3974 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3977 o Minor bugfixes (other):
3978 - Fix a bug with handling misformed replies to reverse DNS lookup
3979 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3980 bug reported by doorss.
3981 - Fix compilation on mingw when a pthreads compatibility library
3982 has been installed. (We don't want to use it, so we shouldn't
3983 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3984 - Fix a bug where we would declare that we had run out of virtual
3985 addresses when the address space was only half-exhausted. Bugfix
3987 - Correctly handle the case where AutomapHostsOnResolve is set but
3988 no virtual addresses are available. Fixes bug 2328; bugfix on
3989 0.1.2.1-alpha. Bug found by doorss.
3990 - Correctly handle wrapping around when we run out of virtual
3991 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3994 - Update to the January 1 2011 Maxmind GeoLite Country database.
3995 - Introduce output size checks on all of our decryption functions.
3998 - Tor does not build packages correctly with Automake 1.6 and earlier;
3999 added a check to Makefile.am to make sure that we're building with
4000 Automake 1.7 or later.
4001 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4002 because we built it with a too-old version of automake. Thus that
4003 release broke ./configure --enable-openbsd-malloc, which is popular
4004 among really fast exit relays on Linux.
4007 Changes in version 0.2.1.28 - 2010-12-17
4008 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4009 exploitable bugs. We also took this opportunity to change the IP address
4010 for one of our directory authorities, and to update the geoip database
4014 - Fix a remotely exploitable bug that could be used to crash instances
4015 of Tor remotely by overflowing on the heap. Remote-code execution
4016 hasn't been confirmed, but can't be ruled out. Everyone should
4017 upgrade. Bugfix on the 0.1.1 series and later.
4019 o Directory authority changes:
4020 - Change IP address and ports for gabelmoo (v3 directory authority).
4023 - Update to the December 1 2010 Maxmind GeoLite Country database.
4026 Changes in version 0.2.1.27 - 2010-11-23
4027 Yet another OpenSSL security patch broke its compatibility with Tor:
4028 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4029 also took this opportunity to fix several crash bugs, integrate a new
4030 directory authority, and update the bundled GeoIP database.
4033 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4034 No longer set the tlsext_host_name extension on server SSL objects;
4035 but continue to set it on client SSL objects. Our goal in setting
4036 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4037 bugfix on 0.2.1.1-alpha.
4038 - Do not log messages to the controller while shrinking buffer
4039 freelists. Doing so would sometimes make the controller connection
4040 try to allocate a buffer chunk, which would mess up the internals
4041 of the freelist and cause an assertion failure. Fixes bug 1125;
4042 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4043 - Learn our external IP address when we're a relay or bridge, even if
4044 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4045 where we introduced bridge relays that don't need to publish to
4046 be useful. Fixes bug 2050.
4047 - Do even more to reject (and not just ignore) annotations on
4048 router descriptors received anywhere but from the cache. Previously
4049 we would ignore such annotations at first, but cache them to disk
4050 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4051 - When you're using bridges and your network goes away and your
4052 bridges get marked as down, recover when you attempt a new socks
4053 connection (if the network is back), rather than waiting up to an
4054 hour to try fetching new descriptors for your bridges. Bugfix on
4055 0.2.0.3-alpha; fixes bug 1981.
4058 - Move to the November 2010 Maxmind GeoLite country db (rather
4059 than the June 2009 ip-to-country GeoIP db) for our statistics that
4060 count how many users relays are seeing from each country. Now we'll
4061 have more accurate data, especially for many African countries.
4063 o New directory authorities:
4064 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4068 - Fix an assertion failure that could occur in directory caches or
4069 bridge users when using a very short voting interval on a testing
4070 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4072 - Enforce multiplicity rules when parsing annotations. Bugfix on
4073 0.2.0.8-alpha. Found by piebeer.
4074 - Allow handshaking OR connections to take a full KeepalivePeriod
4075 seconds to handshake. Previously, we would close them after
4076 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4077 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4079 - When building with --enable-gcc-warnings on OpenBSD, disable
4080 warnings in system headers. This makes --enable-gcc-warnings
4081 pass on OpenBSD 4.8.
4084 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4085 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4086 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4087 Servers can start sending this code when enough clients recognize
4088 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4089 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4090 Patch from mingw-san.
4093 - Remove the old debian/ directory from the main Tor distribution.
4094 The official Tor-for-debian git repository lives at the URL
4095 https://git.torproject.org/debian/tor.git
4096 - Stop shipping the old doc/website/ directory in the tarball. We
4097 changed the website format in late 2010, and what we shipped in
4098 0.2.1.26 really wasn't that useful anyway.
4101 Changes in version 0.2.1.26 - 2010-05-02
4102 Tor 0.2.1.26 addresses the recent connection and memory overload
4103 problems we've been seeing on relays, especially relays with their
4104 DirPort open. If your relay has been crashing, or you turned it off
4105 because it used too many resources, give this release a try.
4107 This release also fixes yet another instance of broken OpenSSL libraries
4108 that was causing some relays to drop out of the consensus.
4111 - Teach relays to defend themselves from connection overload. Relays
4112 now close idle circuits early if it looks like they were intended
4113 for directory fetches. Relays are also more aggressive about closing
4114 TLS connections that have no circuits on them. Such circuits are
4115 unlikely to be re-used, and tens of thousands of them were piling
4116 up at the fast relays, causing the relays to run out of sockets
4117 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4118 their directory fetches over TLS).
4119 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4120 that claim to be earlier than 0.9.8m, but which have in reality
4121 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4122 behavior. Possible fix for some cases of bug 1346.
4123 - Directory mirrors were fetching relay descriptors only from v2
4124 directory authorities, rather than v3 authorities like they should.
4125 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4126 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4129 - Finally get rid of the deprecated and now harmful notion of "clique
4130 mode", where directory authorities maintain TLS connections to
4134 - In the util/threads test, no longer free the test_mutex before all
4135 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4136 - The master thread could starve the worker threads quite badly on
4137 certain systems, causing them to run only partially in the allowed
4138 window. This resulted in test failures. Now the master thread sleeps
4139 occasionally for a few microseconds while the two worker-threads
4140 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4143 Changes in version 0.2.1.25 - 2010-03-16
4144 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4145 prevent relays from guessing their IP address correctly. It also fixes
4146 several minor potential security bugs.
4149 - Fix a regression from our patch for bug 1244 that caused relays
4150 to guess their IP address incorrectly if they didn't set Address
4151 in their torrc and/or their address fails to resolve. Bugfix on
4152 0.2.1.23; fixes bug 1269.
4153 - When freeing a session key, zero it out completely. We only zeroed
4154 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4155 patched by ekir. Fixes bug 1254.
4158 - Fix a dereference-then-NULL-check sequence when publishing
4159 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4161 - Fix another dereference-then-NULL-check sequence. Bugfix on
4162 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4163 - Make sure we treat potentially not NUL-terminated strings correctly.
4164 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4167 Changes in version 0.2.1.24 - 2010-02-21
4168 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4172 - Work correctly out-of-the-box with even more vendor-patched versions
4173 of OpenSSL. In particular, make it so Debian and OS X don't need
4174 customized patches to run/build.
4177 Changes in version 0.2.1.23 - 2010-02-13
4178 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4179 again on the latest OS X, and updates the location of a directory
4182 o Major bugfixes (performance):
4183 - We were selecting our guards uniformly at random, and then weighting
4184 which of our guards we'd use uniformly at random. This imbalance
4185 meant that Tor clients were severely limited on throughput (and
4186 probably latency too) by the first hop in their circuit. Now we
4187 select guards weighted by currently advertised bandwidth. We also
4188 automatically discard guards picked using the old algorithm. Fixes
4189 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4192 - Make Tor work again on the latest OS X: when deciding whether to
4193 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4194 version at run-time, not compile time. We need to do this because
4195 Apple doesn't update its dev-tools headers when it updates its
4196 libraries in a security patch.
4197 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4198 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4199 a memory leak when requesting a hidden service descriptor we've
4200 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4204 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4205 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4208 - Avoid a mad rush at the beginning of each month when each client
4209 rotates half of its guards. Instead we spread the rotation out
4210 throughout the month, but we still avoid leaving a precise timestamp
4211 in the state file about when we first picked the guard. Improves
4212 over the behavior introduced in 0.1.2.17.
4215 Changes in version 0.2.1.22 - 2010-01-19
4216 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4217 authorities -- it would tell you its whole history of bridge descriptors
4218 if you make the right directory request. This stable update also
4219 rotates two of the seven v3 directory authority keys and locations.
4221 o Directory authority changes:
4222 - Rotate keys (both v3 identity and relay identity) for moria1
4226 - Stop bridge directory authorities from answering dbg-stability.txt
4227 directory queries, which would let people fetch a list of all
4228 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4231 Changes in version 0.2.1.21 - 2009-12-21
4232 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4233 library. If you use Tor on Linux / Unix and you're getting SSL
4234 renegotiation errors, upgrading should help. We also recommend an
4235 upgrade if you're an exit relay.
4238 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4239 handshake from working unless we explicitly tell OpenSSL that we
4240 are using SSL renegotiation safely. We are, of course, but OpenSSL
4241 0.9.8l won't work unless we say we are.
4242 - Avoid crashing if the client is trying to upload many bytes and the
4243 circuit gets torn down at the same time, or if the flip side
4244 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4247 - Do not refuse to learn about authority certs and v2 networkstatus
4248 documents that are older than the latest consensus. This bug might
4249 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4250 Spotted and fixed by xmux.
4251 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4252 trigger platform-specific option misparsing case found by Coverity
4254 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4255 trigger assert. Fixes bug 1173.
4258 Changes in version 0.2.1.20 - 2009-10-15
4259 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4260 services at once, prepares for more performance improvements, and
4261 fixes a bunch of smaller bugs.
4263 The Windows and OS X bundles also include a more recent Vidalia,
4264 and switch from Privoxy to Polipo.
4266 The OS X installers are now drag and drop. It's best to un-install
4267 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4268 you want to upgrade, you'll need to update the paths for Tor and Polipo
4269 in the Vidalia Settings window.
4272 - Send circuit or stream sendme cells when our window has decreased
4273 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4274 by Karsten when testing the "reduce circuit window" performance
4275 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4276 before the release of Tor 0.0.0. This is the new winner of the
4278 - Fix a remotely triggerable memory leak when a consensus document
4279 contains more than one signature from the same voter. Bugfix on
4281 - Avoid segfault in rare cases when finishing an introduction circuit
4282 as a client and finding out that we don't have an introduction key
4283 for it. Fixes bug 1073. Reported by Aaron Swartz.
4286 - Tor now reads the "circwindow" parameter out of the consensus,
4287 and uses that value for its circuit package window rather than the
4288 default of 1000 cells. Begins the implementation of proposal 168.
4290 o New directory authorities:
4291 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4293 - Move moria1 and tonga to alternate IP addresses.
4296 - Fix a signed/unsigned compile warning in 0.2.1.19.
4297 - Fix possible segmentation fault on directory authorities. Bugfix on
4299 - Fix an extremely rare infinite recursion bug that could occur if
4300 we tried to log a message after shutting down the log subsystem.
4301 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4302 - Fix an obscure bug where hidden services on 64-bit big-endian
4303 systems might mis-read the timestamp in v3 introduce cells, and
4304 refuse to connect back to the client. Discovered by "rotor".
4305 Bugfix on 0.2.1.6-alpha.
4306 - We were triggering a CLOCK_SKEW controller status event whenever
4307 we connect via the v2 connection protocol to any relay that has
4308 a wrong clock. Instead, we should only inform the controller when
4309 it's a trusted authority that claims our clock is wrong. Bugfix
4310 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4311 - We were telling the controller about CHECKING_REACHABILITY and
4312 REACHABILITY_FAILED status events whenever we launch a testing
4313 circuit or notice that one has failed. Instead, only tell the
4314 controller when we want to inform the user of overall success or
4315 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4317 - Don't warn when we're using a circuit that ends with a node
4318 excluded in ExcludeExitNodes, but the circuit is not used to access
4319 the outside world. This should help fix bug 1090. Bugfix on
4321 - Work around a small memory leak in some versions of OpenSSL that
4322 stopped the memory used by the hostname TLS extension from being
4326 - Add a "getinfo status/accepted-server-descriptor" controller
4327 command, which is the recommended way for controllers to learn
4328 whether our server descriptor has been successfully received by at
4329 least on directory authority. Un-recommend good-server-descriptor
4330 getinfo and status events until we have a better design for them.
4333 Changes in version 0.2.1.19 - 2009-07-28
4334 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4338 - Make accessing hidden services on 0.2.1.x work right again.
4339 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4340 part of patch provided by "optimist".
4343 - When a relay/bridge is writing out its identity key fingerprint to
4344 the "fingerprint" file and to its logs, write it without spaces. Now
4345 it will look like the fingerprints in our bridges documentation,
4346 and confuse fewer users.
4349 - Relays no longer publish a new server descriptor if they change
4350 their MaxAdvertisedBandwidth config option but it doesn't end up
4351 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4352 fixes bug 1026. Patch from Sebastian.
4353 - Avoid leaking memory every time we get a create cell but we have
4354 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4355 fixes bug 1034. Reported by BarkerJr.
4358 Changes in version 0.2.1.18 - 2009-07-24
4359 Tor 0.2.1.18 lays the foundations for performance improvements,
4360 adds status events to help users diagnose bootstrap problems, adds
4361 optional authentication/authorization for hidden services, fixes a
4362 variety of potential anonymity problems, and includes a huge pile of
4363 other features and bug fixes.
4365 o Major features (clients):
4366 - Start sending "bootstrap phase" status events to the controller,
4367 so it can keep the user informed of progress fetching directory
4368 information and establishing circuits. Also inform the controller
4369 if we think we're stuck at a particular bootstrap phase. Implements
4371 - Clients replace entry guards that were chosen more than a few months
4372 ago. This change should significantly improve client performance,
4373 especially once more people upgrade, since relays that have been
4374 a guard for a long time are currently overloaded.
4375 - Network status consensus documents and votes now contain bandwidth
4376 information for each relay. Clients use the bandwidth values
4377 in the consensus, rather than the bandwidth values in each
4378 relay descriptor. This approach opens the door to more accurate
4379 bandwidth estimates once the directory authorities start doing
4380 active measurements. Implements part of proposal 141.
4382 o Major features (relays):
4383 - Disable and refactor some debugging checks that forced a linear scan
4384 over the whole server-side DNS cache. These accounted for over 50%
4385 of CPU time on a relatively busy exit node's gprof profile. Also,
4386 disable some debugging checks that appeared in exit node profile
4387 data. Found by Jacob.
4388 - New DirPortFrontPage option that takes an html file and publishes
4389 it as "/" on the DirPort. Now relay operators can provide a
4390 disclaimer without needing to set up a separate webserver. There's
4391 a sample disclaimer in contrib/tor-exit-notice.html.
4393 o Major features (hidden services):
4394 - Make it possible to build hidden services that only certain clients
4395 are allowed to connect to. This is enforced at several points,
4396 so that unauthorized clients are unable to send INTRODUCE cells
4397 to the service, or even (depending on the type of authentication)
4398 to learn introduction points. This feature raises the bar for
4399 certain kinds of active attacks against hidden services. Design
4400 and code by Karsten Loesing. Implements proposal 121.
4401 - Relays now store and serve v2 hidden service descriptors by default,
4402 i.e., the new default value for HidServDirectoryV2 is 1. This is
4403 the last step in proposal 114, which aims to make hidden service
4404 lookups more reliable.
4406 o Major features (path selection):
4407 - ExitNodes and Exclude*Nodes config options now allow you to restrict
4408 by country code ("{US}") or IP address or address pattern
4409 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
4410 refinement to decide what config options should take priority if
4411 you ask to both use a particular node and exclude it.
4413 o Major features (misc):
4414 - When building a consensus, do not include routers that are down.
4415 This cuts down 30% to 40% on consensus size. Implements proposal
4417 - New TestingTorNetwork config option to allow adjustment of
4418 previously constant values that could slow bootstrapping. Implements
4419 proposal 135. Patch from Karsten.
4420 - Convert many internal address representations to optionally hold
4421 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
4422 elements. Make resolver code handle nameservers located at IPv6
4424 - More work on making our TLS handshake blend in: modify the list
4425 of ciphers advertised by OpenSSL in client mode to even more
4426 closely resemble a common web browser. We cheat a little so that
4427 we can advertise ciphers that the locally installed OpenSSL doesn't
4429 - Use the TLS1 hostname extension to more closely resemble browser
4432 o Security fixes (anonymity/entropy):
4433 - Never use a connection with a mismatched address to extend a
4434 circuit, unless that connection is canonical. A canonical
4435 connection is one whose address is authenticated by the router's
4436 identity key, either in a NETINFO cell or in a router descriptor.
4437 - Implement most of proposal 110: The first K cells to be sent
4438 along a circuit are marked as special "early" cells; only K "early"
4439 cells will be allowed. Once this code is universal, we can block
4440 certain kinds of denial-of-service attack by requiring that EXTEND
4441 commands must be sent using an "early" cell.
4442 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4443 cross-platform entropy collection again. We used to use it, then
4444 stopped using it because of a bug that could crash systems that
4445 called RAND_poll when they had a lot of fds open. It looks like the
4446 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4447 at startup, and to call RAND_poll() when we reseed later only if
4448 we have a non-buggy OpenSSL version.
4449 - When the client is choosing entry guards, now it selects at most
4450 one guard from a given relay family. Otherwise we could end up with
4451 all of our entry points into the network run by the same operator.
4452 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
4453 - Do not use or believe expired v3 authority certificates. Patch
4454 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
4455 - Drop begin cells to a hidden service if they come from the middle
4456 of a circuit. Patch from lark.
4457 - When we erroneously receive two EXTEND cells for the same circuit
4458 ID on the same connection, drop the second. Patch from lark.
4459 - Authorities now vote for the Stable flag for any router whose
4460 weighted MTBF is at least 5 days, regardless of the mean MTBF.
4461 - Clients now never report any stream end reason except 'MISC'.
4462 Implements proposal 148.
4464 o Major bugfixes (crashes):
4465 - Parse dates and IPv4 addresses in a locale- and libc-independent
4466 manner, to avoid platform-dependent behavior on malformed input.
4467 - Fix a crash that occurs on exit nodes when a nameserver request
4468 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
4469 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
4471 - Do not assume that a stack-allocated character array will be
4472 64-bit aligned on platforms that demand that uint64_t access is
4473 aligned. Possible fix for bug 604.
4474 - Resolve a very rare crash bug that could occur when the user forced
4475 a nameserver reconfiguration during the middle of a nameserver
4476 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
4477 - Avoid a "0 divided by 0" calculation when calculating router uptime
4478 at directory authorities. Bugfix on 0.2.0.8-alpha.
4479 - Fix an assertion bug in parsing policy-related options; possible fix
4481 - Rate-limit too-many-sockets messages: when they happen, they happen
4482 a lot and end up filling up the disk. Resolves bug 748.
4483 - Fix a race condition that could cause crashes or memory corruption
4484 when running as a server with a controller listening for log
4486 - Avoid crashing when we have a policy specified in a DirPolicy or
4487 SocksPolicy or ReachableAddresses option with ports set on it,
4488 and we re-load the policy. May fix bug 996.
4489 - Fix an assertion failure on 64-bit platforms when we allocated
4490 memory right up to the end of a memarea, then realigned the memory
4491 one step beyond the end. Fixes a possible cause of bug 930.
4492 - Protect the count of open sockets with a mutex, so we can't
4493 corrupt it when two threads are closing or opening sockets at once.
4494 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
4496 o Major bugfixes (clients):
4497 - Discard router descriptors as we load them if they are more than
4498 five days old. Otherwise if Tor is off for a long time and then
4499 starts with cached descriptors, it will try to use the onion keys
4500 in those obsolete descriptors when building circuits. Fixes bug 887.
4501 - When we choose to abandon a new entry guard because we think our
4502 older ones might be better, close any circuits pending on that
4503 new entry guard connection. This fix should make us recover much
4504 faster when our network is down and then comes back. Bugfix on
4505 0.1.2.8-beta; found by lodger.
4506 - When Tor clients restart after 1-5 days, they discard all their
4507 cached descriptors as too old, but they still use the cached
4508 consensus document. This approach is good for robustness, but
4509 bad for performance: since they don't know any bandwidths, they
4510 end up choosing at random rather than weighting their choice by
4511 speed. Fixed by the above feature of putting bandwidths in the
4514 o Major bugfixes (relays):
4515 - Relays were falling out of the networkstatus consensus for
4516 part of a day if they changed their local config but the
4517 authorities discarded their new descriptor as "not sufficiently
4518 different". Now directory authorities accept a descriptor as changed
4519 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
4521 - Ensure that two circuits can never exist on the same connection
4522 with the same circuit ID, even if one is marked for close. This
4523 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
4524 - Directory authorities were neglecting to mark relays down in their
4525 internal histories if the relays fall off the routerlist without
4526 ever being found unreachable. So there were relays in the histories
4527 that haven't been seen for eight months, and are listed as being
4528 up for eight months. This wreaked havoc on the "median wfu" and
4529 "median mtbf" calculations, in turn making Guard and Stable flags
4530 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
4533 o Major bugfixes (hidden services):
4534 - When establishing a hidden service, introduction points that
4535 originate from cannibalized circuits were completely ignored
4536 and not included in rendezvous service descriptors. This might
4537 have been another reason for delay in making a hidden service
4538 available. Bugfix from long ago (0.0.9.x?)
4540 o Major bugfixes (memory and resource management):
4541 - Fixed some memory leaks -- some quite frequent, some almost
4542 impossible to trigger -- based on results from Coverity.
4543 - Speed up parsing and cut down on memory fragmentation by using
4544 stack-style allocations for parsing directory objects. Previously,
4545 this accounted for over 40% of allocations from within Tor's code
4546 on a typical directory cache.
4547 - Use a Bloom filter rather than a digest-based set to track which
4548 descriptors we need to keep around when we're cleaning out old
4549 router descriptors. This speeds up the computation significantly,
4550 and may reduce fragmentation.
4552 o New/changed config options:
4553 - Now NodeFamily and MyFamily config options allow spaces in
4554 identity fingerprints, so it's easier to paste them in.
4555 Suggested by Lucky Green.
4556 - Allow ports 465 and 587 in the default exit policy again. We had
4557 rejected them in 0.1.0.15, because back in 2005 they were commonly
4558 misconfigured and ended up as spam targets. We hear they are better
4559 locked down these days.
4560 - Make TrackHostExit mappings expire a while after their last use, not
4561 after their creation. Patch from Robert Hogan.
4562 - Add an ExcludeExitNodes option so users can list a set of nodes
4563 that should be be excluded from the exit node position, but
4564 allowed elsewhere. Implements proposal 151.
4565 - New --hush command-line option similar to --quiet. While --quiet
4566 disables all logging to the console on startup, --hush limits the
4567 output to messages of warning and error severity.
4568 - New configure/torrc options (--enable-geoip-stats,
4569 DirRecordUsageByCountry) to record how many IPs we've served
4570 directory info to in each country code, how many status documents
4571 total we've sent to each country code, and what share of the total
4572 directory requests we should expect to see.
4573 - Make outbound DNS packets respect the OutboundBindAddress setting.
4574 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
4575 - Allow separate log levels to be configured for different logging
4576 domains. For example, this allows one to log all notices, warnings,
4577 or errors, plus all memory management messages of level debug or
4578 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4579 - Update to the "June 3 2009" ip-to-country file.
4581 o Minor features (relays):
4582 - Raise the minimum rate limiting to be a relay from 20000 bytes
4583 to 20480 bytes (aka 20KB/s), to match our documentation. Also
4584 update directory authorities so they always assign the Fast flag
4585 to relays with 20KB/s of capacity. Now people running relays won't
4586 suddenly find themselves not seeing any use, if the network gets
4588 - If we're a relay and we change our IP address, be more verbose
4589 about the reason that made us change. Should help track down
4590 further bugs for relays on dynamic IP addresses.
4591 - Exit servers can now answer resolve requests for ip6.arpa addresses.
4592 - Implement most of Proposal 152: allow specialized servers to permit
4593 single-hop circuits, and clients to use those servers to build
4594 single-hop circuits when using a specialized controller. Patch
4595 from Josh Albrecht. Resolves feature request 768.
4596 - When relays do their initial bandwidth measurement, don't limit
4597 to just our entry guards for the test circuits. Otherwise we tend
4598 to have multiple test circuits going through a single entry guard,
4599 which makes our bandwidth test less accurate. Fixes part of bug 654;
4600 patch contributed by Josh Albrecht.
4602 o Minor features (directory authorities):
4603 - Try not to open more than one descriptor-downloading connection
4604 to an authority at once. This should reduce load on directory
4605 authorities. Fixes bug 366.
4606 - Add cross-certification to newly generated certificates, so that
4607 a signing key is enough information to look up a certificate. Start
4608 serving certificates by <identity digest, signing key digest>
4609 pairs. Implements proposal 157.
4610 - When a directory authority downloads a descriptor that it then
4611 immediately rejects, do not retry downloading it right away. Should
4612 save some bandwidth on authorities. Fix for bug 888. Patch by
4614 - Directory authorities now serve a /tor/dbg-stability.txt URL to
4615 help debug WFU and MTBF calculations.
4616 - In directory authorities' approved-routers files, allow
4617 fingerprints with or without space.
4619 o Minor features (directory mirrors):
4620 - When a download gets us zero good descriptors, do not notify
4621 Tor that new directory information has arrived.
4622 - Servers support a new URL scheme for consensus downloads that
4623 allows the client to specify which authorities are trusted.
4624 The server then only sends the consensus if the client will trust
4625 it. Otherwise a 404 error is sent back. Clients use this
4626 new scheme when the server supports it (meaning it's running
4627 0.2.1.1-alpha or later). Implements proposal 134.
4629 o Minor features (bridges):
4630 - If the bridge config line doesn't specify a port, assume 443.
4631 This makes bridge lines a bit smaller and easier for users to
4633 - If we're using bridges and our network goes away, be more willing
4634 to forgive our bridges and try again when we get an application
4637 o Minor features (hidden services):
4638 - When the client launches an introduction circuit, retry with a
4639 new circuit after 30 seconds rather than 60 seconds.
4640 - Launch a second client-side introduction circuit in parallel
4641 after a delay of 15 seconds (based on work by Christian Wilms).
4642 - Hidden services start out building five intro circuits rather
4643 than three, and when the first three finish they publish a service
4644 descriptor using those. Now we publish our service descriptor much
4645 faster after restart.
4646 - Drop the requirement to have an open dir port for storing and
4647 serving v2 hidden service descriptors.
4649 o Minor features (build and packaging):
4650 - On Linux, use the prctl call to re-enable core dumps when the User
4652 - Try to make sure that the version of Libevent we're running with
4653 is binary-compatible with the one we built with. May address bug
4655 - Add a new --enable-local-appdata configuration switch to change
4656 the default location of the datadir on win32 from APPDATA to
4657 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
4658 entirely. Patch from coderman.
4659 - Build correctly against versions of OpenSSL 0.9.8 or later that
4660 are built without support for deprecated functions.
4661 - On platforms with a maximum syslog string length, truncate syslog
4662 messages to that length ourselves, rather than relying on the
4663 system to do it for us.
4664 - Automatically detect MacOSX versions earlier than 10.4.0, and
4665 disable kqueue from inside Tor when running with these versions.
4666 We previously did this from the startup script, but that was no
4667 help to people who didn't use the startup script. Resolves bug 863.
4668 - Build correctly when configured to build outside the main source
4669 path. Patch from Michael Gold.
4670 - Disable GCC's strict alias optimization by default, to avoid the
4671 likelihood of its introducing subtle bugs whenever our code violates
4672 the letter of C99's alias rules.
4673 - Change the contrib/tor.logrotate script so it makes the new
4674 logs as "_tor:_tor" rather than the default, which is generally
4675 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
4676 - Change our header file guard macros to be less likely to conflict
4677 with system headers. Adam Langley noticed that we were conflicting
4678 with log.h on Android.
4679 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4680 and stop using a warning that had become unfixably verbose under
4682 - Use a lockfile to make sure that two Tor processes are not
4683 simultaneously running with the same datadir.
4684 - Allow OpenSSL to use dynamic locks if it wants.
4685 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
4687 o Minor features (controllers):
4688 - When generating circuit events with verbose nicknames for
4689 controllers, try harder to look up nicknames for routers on a
4690 circuit. (Previously, we would look in the router descriptors we had
4691 for nicknames, but not in the consensus.) Partial fix for bug 941.
4692 - New controller event NEWCONSENSUS that lists the networkstatus
4693 lines for every recommended relay. Now controllers like Torflow
4694 can keep up-to-date on which relays they should be using.
4695 - New controller event "clients_seen" to report a geoip-based summary
4696 of which countries we've seen clients from recently. Now controllers
4697 like Vidalia can show bridge operators that they're actually making
4699 - Add a 'getinfo status/clients-seen' controller command, in case
4700 controllers want to hear clients_seen events but connect late.
4701 - New CONSENSUS_ARRIVED event to note when a new consensus has
4702 been fetched and validated.
4703 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
4704 controllers to prevent SIGHUP from reloading the configuration.
4706 - Return circuit purposes in response to GETINFO circuit-status.
4708 - Serve the latest v3 networkstatus consensus via the control
4709 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
4710 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4711 controller can query our current bootstrap state in case it attaches
4712 partway through and wants to catch up.
4713 - Provide circuit purposes along with circuit events to the controller.
4715 o Minor features (tools):
4716 - Do not have tor-resolve automatically refuse all .onion addresses;
4717 if AutomapHostsOnResolve is set in your torrc, this will work fine.
4718 - Add a -p option to tor-resolve for specifying the SOCKS port: some
4719 people find host:port too confusing.
4720 - Print the SOCKS5 error message string as well as the error code
4721 when a tor-resolve request fails. Patch from Jacob.
4723 o Minor bugfixes (memory and resource management):
4724 - Clients no longer cache certificates for authorities they do not
4725 recognize. Bugfix on 0.2.0.9-alpha.
4726 - Do not use C's stdio library for writing to log files. This will
4727 improve logging performance by a minute amount, and will stop
4728 leaking fds when our disk is full. Fixes bug 861.
4729 - Stop erroneous use of O_APPEND in cases where we did not in fact
4730 want to re-seek to the end of a file before every last write().
4731 - Fix a small alignment and memory-wasting bug on buffer chunks.
4733 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4734 to avoid unused RAM in buffer chunks and memory pools.
4735 - Reduce the default smartlist size from 32 to 16; it turns out that
4736 most smartlists hold around 8-12 elements tops.
4737 - Make dumpstats() log the fullness and size of openssl-internal
4739 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4740 patch to their OpenSSL, turn it on to save memory on servers. This
4741 patch will (with any luck) get included in a mainline distribution
4743 - Fix a memory leak when v3 directory authorities load their keys
4744 and cert from disk. Bugfix on 0.2.0.1-alpha.
4745 - Stop using malloc_usable_size() to use more area than we had
4746 actually allocated: it was safe, but made valgrind really unhappy.
4747 - Make the assert_circuit_ok() function work correctly on circuits that
4748 have already been marked for close.
4749 - Fix uninitialized size field for memory area allocation: may improve
4750 memory performance during directory parsing.
4752 o Minor bugfixes (clients):
4753 - Stop reloading the router list from disk for no reason when we
4754 run out of reachable directory mirrors. Once upon a time reloading
4755 it would set the 'is_running' flag back to 1 for them. It hasn't
4756 done that for a long time.
4757 - When we had picked an exit node for a connection, but marked it as
4758 "optional", and it turned out we had no onion key for the exit,
4759 stop wanting that exit and try again. This situation may not
4760 be possible now, but will probably become feasible with proposal
4761 158. Spotted by rovv. Fixes another case of bug 752.
4762 - Fix a bug in address parsing that was preventing bridges or hidden
4763 service targets from being at IPv6 addresses.
4764 - Do not remove routers as too old if we do not have any consensus
4765 document. Bugfix on 0.2.0.7-alpha.
4766 - When an exit relay resolves a stream address to a local IP address,
4767 do not just keep retrying that same exit relay over and
4768 over. Instead, just close the stream. Addresses bug 872. Bugfix
4769 on 0.2.0.32. Patch from rovv.
4770 - Made Tor a little less aggressive about deleting expired
4771 certificates. Partial fix for bug 854.
4772 - Treat duplicate certificate fetches as failures, so that we do
4773 not try to re-fetch an expired certificate over and over and over.
4774 - Do not say we're fetching a certificate when we'll in fact skip it
4775 because of a pending download.
4776 - If we have correct permissions on $datadir, we complain to stdout
4777 and fail to start. But dangerous permissions on
4778 $datadir/cached-status/ would cause us to open a log and complain
4779 there. Now complain to stdout and fail to start in both cases. Fixes
4780 bug 820, reported by seeess.
4782 o Minor bugfixes (bridges):
4783 - When we made bridge authorities stop serving bridge descriptors over
4784 unencrypted links, we also broke DirPort reachability testing for
4785 bridges. So bridges with a non-zero DirPort were printing spurious
4786 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
4787 - Don't allow a bridge to publish its router descriptor to a
4788 non-bridge directory authority. Fixes part of bug 932.
4789 - When we change to or from being a bridge, reset our counts of
4790 client usage by country. Fixes bug 932.
4792 o Minor bugfixes (relays):
4793 - Log correct error messages for DNS-related network errors on
4795 - Actually return -1 in the error case for read_bandwidth_usage().
4796 Harmless bug, since we currently don't care about the return value
4797 anywhere. Bugfix on 0.2.0.9-alpha.
4798 - Provide a more useful log message if bug 977 (related to buffer
4799 freelists) ever reappears, and do not crash right away.
4800 - We were already rejecting relay begin cells with destination port
4801 of 0. Now also reject extend cells with destination port or address
4802 of 0. Suggested by lark.
4803 - When we can't transmit a DNS request due to a network error, retry
4804 it after a while, and eventually transmit a failing response to
4805 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
4806 - Solve a bug that kept hardware crypto acceleration from getting
4807 enabled when accounting was turned on. Fixes bug 907. Bugfix on
4809 - When a canonical connection appears later in our internal list
4810 than a noncanonical one for a given OR ID, always use the
4811 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
4813 - Avoid some nasty corner cases in the logic for marking connections
4814 as too old or obsolete or noncanonical for circuits. Partial
4816 - Fix another interesting corner-case of bug 891 spotted by rovv:
4817 Previously, if two hosts had different amounts of clock drift, and
4818 one of them created a new connection with just the wrong timing,
4819 the other might decide to deprecate the new connection erroneously.
4820 Bugfix on 0.1.1.13-alpha.
4821 - If one win32 nameserver fails to get added, continue adding the
4822 rest, and don't automatically fail.
4823 - Fix a bug where an unreachable relay would establish enough
4824 reachability testing circuits to do a bandwidth test -- if
4825 we already have a connection to the middle hop of the testing
4826 circuit, then it could establish the last hop by using the existing
4827 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
4828 circuits no longer use entry guards in 0.2.1.3-alpha.
4830 o Minor bugfixes (directory authorities):
4831 - Limit uploaded directory documents to be 16M rather than 500K.
4832 The directory authorities were refusing v3 consensus votes from
4833 other authorities, since the votes are now 504K. Fixes bug 959;
4834 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
4835 - Directory authorities should never send a 503 "busy" response to
4836 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
4838 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
4839 headers. Bugfix on 0.2.0.10-alpha.
4841 o Minor bugfixes (hidden services):
4842 - When we can't find an intro key for a v2 hidden service descriptor,
4843 fall back to the v0 hidden service descriptor and log a bug message.
4844 Workaround for bug 1024.
4845 - In very rare situations new hidden service descriptors were
4846 published earlier than 30 seconds after the last change to the
4847 service. (We currently think that a hidden service descriptor
4848 that's been stable for 30 seconds is worth publishing.)
4849 - If a hidden service sends us an END cell, do not consider
4850 retrying the connection; just close it. Patch from rovv.
4851 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
4852 service directories if they have no advertised dir port. Bugfix
4855 o Minor bugfixes (tools):
4856 - In the torify(1) manpage, mention that tsocks will leak your
4859 o Minor bugfixes (controllers):
4860 - If the controller claimed responsibility for a stream, but that
4861 stream never finished making its connection, it would live
4862 forever in circuit_wait state. Now we close it after SocksTimeout
4863 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
4864 - Make DNS resolved controller events into "CLOSED", not
4865 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
4867 - The control port would close the connection before flushing long
4868 replies, such as the network consensus, if a QUIT command was issued
4869 before the reply had completed. Now, the control port flushes all
4870 pending replies before closing the connection. Also fix a spurious
4871 warning when a QUIT command is issued after a malformed or rejected
4872 AUTHENTICATE command, but before the connection was closed. Patch
4873 by Marcus Griep. Fixes bugs 1015 and 1016.
4874 - Fix a bug that made stream bandwidth get misreported to the
4877 o Deprecated and removed features:
4878 - The old "tor --version --version" command, which would print out
4879 the subversion "Id" of most of the source files, is now removed. It
4880 turned out to be less useful than we'd expected, and harder to
4882 - RedirectExits has been removed. It was deprecated since
4884 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
4885 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
4886 - Cell pools are now always enabled; --disable-cell-pools is ignored.
4887 - Directory mirrors no longer fetch the v1 directory or
4888 running-routers files. They are obsolete, and nobody asks for them
4889 anymore. This is the first step to making v1 authorities obsolete.
4890 - Take out the TestVia config option, since it was a workaround for
4891 a bug that was fixed in Tor 0.1.1.21.
4892 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
4893 HiddenServiceExcludeNodes as obsolete: they never worked properly,
4894 and nobody seems to be using them. Fixes bug 754. Bugfix on
4895 0.1.0.1-rc. Patch from Christian Wilms.
4896 - Remove all backward-compatibility code for relays running
4897 versions of Tor so old that they no longer work at all on the
4900 o Code simplifications and refactoring:
4901 - Tool-assisted documentation cleanup. Nearly every function or
4902 static variable in Tor should have its own documentation now.
4903 - Rename the confusing or_is_obsolete field to the more appropriate
4904 is_bad_for_new_circs, and move it to or_connection_t where it
4906 - Move edge-only flags from connection_t to edge_connection_t: not
4907 only is this better coding, but on machines of plausible alignment,
4908 it should save 4-8 bytes per connection_t. "Every little bit helps."
4909 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
4910 for consistency; keep old option working for backward compatibility.
4911 - Simplify the code for finding connections to use for a circuit.
4912 - Revise the connection_new functions so that a more typesafe variant
4913 exists. This will work better with Coverity, and let us find any
4914 actual mistakes we're making here.
4915 - Refactor unit testing logic so that dmalloc can be used sensibly
4916 with unit tests to check for memory leaks.
4917 - Move all hidden-service related fields from connection and circuit
4918 structure to substructures: this way they won't eat so much memory.
4919 - Squeeze 2-5% out of client performance (according to oprofile) by
4920 improving the implementation of some policy-manipulation functions.
4921 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
4922 be more efficient. Formerly it was quadratic in the number of
4923 servers; now it should be linear. Fixes bug 509.
4924 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
4925 and n_conn_id_digest fields into a separate structure that's
4926 only needed when the circuit has not yet attached to an n_conn.
4927 - Optimize out calls to time(NULL) that occur for every IO operation,
4928 or for every cell. On systems like Windows where time() is a
4929 slow syscall, this fix will be slightly helpful.
4932 Changes in version 0.2.0.35 - 2009-06-24
4934 - Avoid crashing in the presence of certain malformed descriptors.
4935 Found by lark, and by automated fuzzing.
4936 - Fix an edge case where a malicious exit relay could convince a
4937 controller that the client's DNS question resolves to an internal IP
4938 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4941 - Finally fix the bug where dynamic-IP relays disappear when their
4942 IP address changes: directory mirrors were mistakenly telling
4943 them their old address if they asked via begin_dir, so they
4944 never got an accurate answer about their new address, so they
4945 just vanished after a day. For belt-and-suspenders, relays that
4946 don't set Address in their config now avoid using begin_dir for
4947 all direct connections. Should fix bugs 827, 883, and 900.
4948 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4949 that would occur on some exit nodes when DNS failures and timeouts
4950 occurred in certain patterns. Fix for bug 957.
4953 - When starting with a cache over a few days old, do not leak
4954 memory for the obsolete router descriptors in it. Bugfix on
4955 0.2.0.33; fixes bug 672.
4956 - Hidden service clients didn't use a cached service descriptor that
4957 was older than 15 minutes, but wouldn't fetch a new one either,
4958 because there was already one in the cache. Now, fetch a v2
4959 descriptor unless the same descriptor was added to the cache within
4960 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4963 Changes in version 0.2.0.34 - 2009-02-08
4964 Tor 0.2.0.34 features several more security-related fixes. You should
4965 upgrade, especially if you run an exit relay (remote crash) or a
4966 directory authority (remote infinite loop), or you're on an older
4967 (pre-XP) or not-recently-patched Windows (remote exploit).
4969 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
4970 have many known flaws, and nobody should be using them. You should
4971 upgrade. If you're using a Linux or BSD and its packages are obsolete,
4972 stop using those packages and upgrade anyway.
4975 - Fix an infinite-loop bug on handling corrupt votes under certain
4976 circumstances. Bugfix on 0.2.0.8-alpha.
4977 - Fix a temporary DoS vulnerability that could be performed by
4978 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
4979 - Avoid a potential crash on exit nodes when processing malformed
4980 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
4981 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
4982 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
4985 - Fix compilation on systems where time_t is a 64-bit integer.
4986 Patch from Matthias Drochner.
4987 - Don't consider expiring already-closed client connections. Fixes
4988 bug 893. Bugfix on 0.0.2pre20.
4991 Changes in version 0.2.0.33 - 2009-01-21
4992 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
4993 useful to users. It also finally fixes a bug where a relay or client
4994 that's been off for many days would take a long time to bootstrap.
4996 This update also fixes an important security-related bug reported by
4997 Ilja van Sprundel. You should upgrade. (We'll send out more details
4998 about the bug once people have had some time to upgrade.)
5001 - Fix a heap-corruption bug that may be remotely triggerable on
5002 some platforms. Reported by Ilja van Sprundel.
5005 - When a stream at an exit relay is in state "resolving" or
5006 "connecting" and it receives an "end" relay cell, the exit relay
5007 would silently ignore the end cell and not close the stream. If
5008 the client never closes the circuit, then the exit relay never
5009 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5011 - When sending CREATED cells back for a given circuit, use a 64-bit
5012 connection ID to find the right connection, rather than an addr:port
5013 combination. Now that we can have multiple OR connections between
5014 the same ORs, it is no longer possible to use addr:port to uniquely
5015 identify a connection.
5016 - Bridge relays that had DirPort set to 0 would stop fetching
5017 descriptors shortly after startup, and then briefly resume
5018 after a new bandwidth test and/or after publishing a new bridge
5019 descriptor. Bridge users that try to bootstrap from them would
5020 get a recent networkstatus but would get descriptors from up to
5021 18 hours earlier, meaning most of the descriptors were obsolete
5022 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5023 - Prevent bridge relays from serving their 'extrainfo' document
5024 to anybody who asks, now that extrainfo docs include potentially
5025 sensitive aggregated client geoip summaries. Bugfix on
5027 - If the cached networkstatus consensus is more than five days old,
5028 discard it rather than trying to use it. In theory it could be
5029 useful because it lists alternate directory mirrors, but in practice
5030 it just means we spend many minutes trying directory mirrors that
5031 are long gone from the network. Also discard router descriptors as
5032 we load them if they are more than five days old, since the onion
5033 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5036 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5037 could make gcc generate non-functional binary search code. Bugfix
5039 - Build correctly on platforms without socklen_t.
5040 - Compile without warnings on solaris.
5041 - Avoid potential crash on internal error during signature collection.
5042 Fixes bug 864. Patch from rovv.
5043 - Correct handling of possible malformed authority signing key
5044 certificates with internal signature types. Fixes bug 880.
5045 Bugfix on 0.2.0.3-alpha.
5046 - Fix a hard-to-trigger resource leak when logging credential status.
5048 - When we can't initialize DNS because the network is down, do not
5049 automatically stop Tor from starting. Instead, we retry failed
5050 dns_init() every 10 minutes, and change the exit policy to reject
5051 *:* until one succeeds. Fixes bug 691.
5052 - Use 64 bits instead of 32 bits for connection identifiers used with
5053 the controller protocol, to greatly reduce risk of identifier reuse.
5054 - When we're choosing an exit node for a circuit, and we have
5055 no pending streams, choose a good general exit rather than one that
5056 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5057 - Fix another case of assuming, when a specific exit is requested,
5058 that we know more than the user about what hosts it allows.
5059 Fixes one case of bug 752. Patch from rovv.
5060 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5061 seconds. Warn the user if lower values are given in the
5062 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5063 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5064 user if lower values are given in the configuration. Bugfix on
5065 0.1.1.17-rc. Patch by Sebastian.
5066 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5067 the cache because we already had a v0 descriptor with the same ID.
5068 Bugfix on 0.2.0.18-alpha.
5069 - Fix a race condition when freeing keys shared between main thread
5070 and CPU workers that could result in a memory leak. Bugfix on
5071 0.1.0.1-rc. Fixes bug 889.
5072 - Send a valid END cell back when a client tries to connect to a
5073 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5074 840. Patch from rovv.
5075 - Check which hops rendezvous stream cells are associated with to
5076 prevent possible guess-the-streamid injection attacks from
5077 intermediate hops. Fixes another case of bug 446. Based on patch
5079 - If a broken client asks a non-exit router to connect somewhere,
5080 do not even do the DNS lookup before rejecting the connection.
5081 Fixes another case of bug 619. Patch from rovv.
5082 - When a relay gets a create cell it can't decrypt (e.g. because it's
5083 using the wrong onion key), we were dropping it and letting the
5084 client time out. Now actually answer with a destroy cell. Fixes
5085 bug 904. Bugfix on 0.0.2pre8.
5087 o Minor bugfixes (hidden services):
5088 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5089 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5092 - Report the case where all signatures in a detached set are rejected
5093 differently than the case where there is an error handling the
5095 - When we realize that another process has modified our cached
5096 descriptors, print out a more useful error message rather than
5097 triggering an assertion. Fixes bug 885. Patch from Karsten.
5098 - Implement the 0x20 hack to better resist DNS poisoning: set the
5099 case on outgoing DNS requests randomly, and reject responses that do
5100 not match the case correctly. This logic can be disabled with the
5101 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5102 of servers that do not reliably preserve case in replies. See
5103 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5105 - Check DNS replies for more matching fields to better resist DNS
5107 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5108 compress cells, which are basically all encrypted, compressed, or
5112 Changes in version 0.2.0.32 - 2008-11-20
5113 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5114 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5115 a smaller security flaw that might allow an attacker to access local
5116 services, further improves hidden service performance, and fixes a
5117 variety of other issues.
5120 - The "User" and "Group" config options did not clear the
5121 supplementary group entries for the Tor process. The "User" option
5122 is now more robust, and we now set the groups to the specified
5123 user's primary group. The "Group" option is now ignored. For more
5124 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5125 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5126 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5127 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5128 consistently obeyed: if an exit relay refuses a stream because its
5129 exit policy doesn't allow it, we would remember what IP address
5130 the relay said the destination address resolves to, even if it's
5131 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5134 - Fix a DOS opportunity during the voting signature collection process
5135 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5137 o Major bugfixes (hidden services):
5138 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5139 we were failing the whole hidden service request when the v0
5140 descriptor fetch fails, even if the v2 fetch is still pending and
5141 might succeed. Similarly, if the last v2 fetch fails, we were
5142 failing the whole hidden service request even if a v0 fetch is
5143 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5144 - When extending a circuit to a hidden service directory to upload a
5145 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5146 requests failed, because the router descriptor has not been
5147 downloaded yet. In these cases, do not attempt to upload the
5148 rendezvous descriptor, but wait until the router descriptor is
5149 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5150 descriptor from a hidden service directory for which the router
5151 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5155 - Fix several infrequent memory leaks spotted by Coverity.
5156 - When testing for libevent functions, set the LDFLAGS variable
5157 correctly. Found by Riastradh.
5158 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5159 bootstrapping with tunneled directory connections. Bugfix on
5160 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5161 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5162 and we know that server B rejects most-but-not all connections to
5163 port 80, we would previously reject the connection. Now, we assume
5164 the user knows what they were asking for. Fixes bug 752. Bugfix
5165 on 0.0.9rc5. Diagnosed by BarkerJr.
5166 - If we overrun our per-second write limits a little, count this as
5167 having used up our write allocation for the second, and choke
5168 outgoing directory writes. Previously, we had only counted this when
5169 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5170 Bugfix on 0.2.0.x (??).
5171 - Remove the old v2 directory authority 'lefkada' from the default
5172 list. It has been gone for many months.
5173 - Stop doing unaligned memory access that generated bus errors on
5174 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5175 - Make USR2 log-level switch take effect immediately. Bugfix on
5178 o Minor bugfixes (controller):
5179 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5180 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5183 Changes in version 0.2.0.31 - 2008-09-03
5184 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5185 a big bug we're seeing where in rare cases traffic from one Tor stream
5186 gets mixed into another stream, and fixes a variety of smaller issues.
5189 - Make sure that two circuits can never exist on the same connection
5190 with the same circuit ID, even if one is marked for close. This
5191 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5192 - Relays now reject risky extend cells: if the extend cell includes
5193 a digest of all zeroes, or asks to extend back to the relay that
5194 sent the extend cell, tear down the circuit. Ideas suggested
5196 - If not enough of our entry guards are available so we add a new
5197 one, we might use the new one even if it overlapped with the
5198 current circuit's exit relay (or its family). Anonymity bugfix
5199 pointed out by rovv.
5202 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5203 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5204 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5205 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5206 - Pick size of default geoip filename string correctly on windows.
5207 Fixes bug 806. Bugfix on 0.2.0.30.
5208 - Make the autoconf script accept the obsolete --with-ssl-dir
5209 option as an alias for the actually-working --with-openssl-dir
5210 option. Fix the help documentation to recommend --with-openssl-dir.
5211 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5212 - When using the TransPort option on OpenBSD, and using the User
5213 option to change UID and drop privileges, make sure to open
5214 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5215 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5216 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5217 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5218 on the client side when connecting to a hidden service. Bugfix
5219 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5220 - When closing an application-side connection because its circuit is
5221 getting torn down, generate the stream event correctly. Bugfix on
5222 0.1.2.x. Anonymous patch.
5225 Changes in version 0.2.0.30 - 2008-07-15
5226 This new stable release switches to a more efficient directory
5227 distribution design, adds features to make connections to the Tor
5228 network harder to block, allows Tor to act as a DNS proxy, adds separate
5229 rate limiting for relayed traffic to make it easier for clients to
5230 become relays, fixes a variety of potential anonymity problems, and
5231 includes the usual huge pile of other features and bug fixes.
5233 o New v3 directory design:
5234 - Tor now uses a new way to learn about and distribute information
5235 about the network: the directory authorities vote on a common
5236 network status document rather than each publishing their own
5237 opinion. Now clients and caches download only one networkstatus
5238 document to bootstrap, rather than downloading one for each
5239 authority. Clients only download router descriptors listed in
5240 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
5242 - Set up moria1, tor26, and dizum as v3 directory authorities
5243 in addition to being v2 authorities. Also add three new ones:
5244 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
5245 dannenberg (run by CCC).
5246 - Switch to multi-level keys for directory authorities: now their
5247 long-term identity key can be kept offline, and they periodically
5248 generate a new signing key. Clients fetch the "key certificates"
5249 to keep up to date on the right keys. Add a standalone tool
5250 "tor-gencert" to generate key certificates. Implements proposal 103.
5251 - Add a new V3AuthUseLegacyKey config option to make it easier for
5252 v3 authorities to change their identity keys if another bug like
5253 Debian's OpenSSL RNG flaw appears.
5254 - Authorities and caches fetch the v2 networkstatus documents
5255 less often, now that v3 is recommended.
5257 o Make Tor connections stand out less on the wire:
5258 - Use an improved TLS handshake designed by Steven Murdoch in proposal
5259 124, as revised in proposal 130. The new handshake is meant to
5260 be harder for censors to fingerprint, and it adds the ability
5261 to detect certain kinds of man-in-the-middle traffic analysis
5262 attacks. The new handshake format includes version negotiation for
5263 OR connections as described in proposal 105, which will allow us
5264 to improve Tor's link protocol more safely in the future.
5265 - Enable encrypted directory connections by default for non-relays,
5266 so censor tools that block Tor directory connections based on their
5267 plaintext patterns will no longer work. This means Tor works in
5268 certain censored countries by default again.
5269 - Stop including recognizeable strings in the commonname part of
5270 Tor's x509 certificates.
5272 o Implement bridge relays:
5273 - Bridge relays (or "bridges" for short) are Tor relays that aren't
5274 listed in the main Tor directory. Since there is no complete public
5275 list of them, even an ISP that is filtering connections to all the
5276 known Tor relays probably won't be able to block all the bridges.
5277 See doc/design-paper/blocking.pdf and proposal 125 for details.
5278 - New config option BridgeRelay that specifies you want to be a
5279 bridge relay rather than a normal relay. When BridgeRelay is set
5280 to 1, then a) you cache dir info even if your DirPort ins't on,
5281 and b) the default for PublishServerDescriptor is now "bridge"
5282 rather than "v2,v3".
5283 - New config option "UseBridges 1" for clients that want to use bridge
5284 relays instead of ordinary entry guards. Clients then specify
5285 bridge relays by adding "Bridge" lines to their config file. Users
5286 can learn about a bridge relay either manually through word of
5287 mouth, or by one of our rate-limited mechanisms for giving out
5288 bridge addresses without letting an attacker easily enumerate them
5289 all. See https://www.torproject.org/bridges for details.
5290 - Bridge relays behave like clients with respect to time intervals
5291 for downloading new v3 consensus documents -- otherwise they
5292 stand out. Bridge users now wait until the end of the interval,
5293 so their bridge relay will be sure to have a new consensus document.
5295 o Implement bridge directory authorities:
5296 - Bridge authorities are like normal directory authorities, except
5297 they don't serve a list of known bridges. Therefore users that know
5298 a bridge's fingerprint can fetch a relay descriptor for that bridge,
5299 including fetching updates e.g. if the bridge changes IP address,
5300 yet an attacker can't just fetch a list of all the bridges.
5301 - Set up Tonga as the default bridge directory authority.
5302 - Bridge authorities refuse to serve bridge descriptors or other
5303 bridge information over unencrypted connections (that is, when
5304 responding to direct DirPort requests rather than begin_dir cells.)
5305 - Bridge directory authorities do reachability testing on the
5306 bridges they know. They provide router status summaries to the
5307 controller via "getinfo ns/purpose/bridge", and also dump summaries
5308 to a file periodically, so we can keep internal stats about which
5309 bridges are functioning.
5310 - If bridge users set the UpdateBridgesFromAuthority config option,
5311 but the digest they ask for is a 404 on the bridge authority,
5312 they fall back to contacting the bridge directly.
5313 - Bridges always use begin_dir to publish their server descriptor to
5314 the bridge authority using an anonymous encrypted tunnel.
5315 - Early work on a "bridge community" design: if bridge authorities set
5316 the BridgePassword config option, they will serve a snapshot of
5317 known bridge routerstatuses from their DirPort to anybody who
5318 knows that password. Unset by default.
5319 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
5320 report sanitized aggregated summaries in their extra-info documents
5321 privately to the bridge authority, listing which countries are
5322 able to reach them. We hope this mechanism will let us learn when
5323 certain countries start trying to block bridges.
5324 - Bridge authorities write bridge descriptors to disk, so they can
5325 reload them after a reboot. They can also export the descriptors
5326 to other programs, so we can distribute them to blocked users via
5327 the BridgeDB interface, e.g. via https://bridges.torproject.org/
5328 and bridges@torproject.org.
5330 o Tor can be a DNS proxy:
5331 - The new client-side DNS proxy feature replaces the need for
5332 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
5333 for DNS requests on port 9999, use the Tor network to resolve them
5334 anonymously, and send the reply back like a regular DNS server.
5335 The code still only implements a subset of DNS.
5336 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5337 resolve request for hosts matching a given pattern causes Tor to
5338 generate an internal virtual address mapping for that host. This
5339 allows DNSPort to work sensibly with hidden service users. By
5340 default, .exit and .onion addresses are remapped; the list of
5341 patterns can be reconfigured with AutomapHostsSuffixes.
5342 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5343 address. Thanks to the AutomapHostsOnResolve option, this is no
5344 longer a completely silly thing to do.
5346 o Major features (relay usability):
5347 - New config options RelayBandwidthRate and RelayBandwidthBurst:
5348 a separate set of token buckets for relayed traffic. Right now
5349 relayed traffic is defined as answers to directory requests, and
5350 OR connections that don't have any local circuits on them. See
5351 proposal 111 for details.
5352 - Create listener connections before we setuid to the configured
5353 User and Group. Now non-Windows users can choose port values
5354 under 1024, start Tor as root, and have Tor bind those ports
5355 before it changes to another UID. (Windows users could already
5357 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
5358 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
5359 on "vserver" accounts. Patch from coderman.
5361 o Major features (directory authorities):
5362 - Directory authorities track weighted fractional uptime and weighted
5363 mean-time-between failures for relays. WFU is suitable for deciding
5364 whether a node is "usually up", while MTBF is suitable for deciding
5365 whether a node is "likely to stay up." We need both, because
5366 "usually up" is a good requirement for guards, while "likely to
5367 stay up" is a good requirement for long-lived connections.
5368 - Directory authorities use a new formula for selecting which relays
5369 to advertise as Guards: they must be in the top 7/8 in terms of
5370 how long we have known about them, and above the median of those
5371 nodes in terms of weighted fractional uptime.
5372 - Directory authorities use a new formula for selecting which relays
5373 to advertise as Stable: when we have 4 or more days of data, use
5374 median measured MTBF rather than median declared uptime. Implements
5376 - Directory authorities accept and serve "extra info" documents for
5377 routers. Routers now publish their bandwidth-history lines in the
5378 extra-info docs rather than the main descriptor. This step saves
5379 60% (!) on compressed router descriptor downloads. Servers upload
5380 extra-info docs to any authority that accepts them; directory
5381 authorities now allow multiple router descriptors and/or extra
5382 info documents to be uploaded in a single go. Authorities, and
5383 caches that have been configured to download extra-info documents,
5384 download them as needed. Implements proposal 104.
5385 - Authorities now list relays who have the same nickname as
5386 a different named relay, but list them with a new flag:
5387 "Unnamed". Now we can make use of relays that happen to pick the
5388 same nickname as a server that registered two years ago and then
5389 disappeared. Implements proposal 122.
5390 - Store routers in a file called cached-descriptors instead of in
5391 cached-routers. Initialize cached-descriptors from cached-routers
5392 if the old format is around. The new format allows us to store
5393 annotations along with descriptors, to record the time we received
5394 each descriptor, its source, and its purpose: currently one of
5395 general, controller, or bridge.
5397 o Major features (other):
5398 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5399 Tor can warn and/or refuse connections to ports commonly used with
5400 vulnerable-plaintext protocols. Currently we warn on ports 23,
5401 109, 110, and 143, but we don't reject any. Based on proposal 129
5402 by Kevin Bauer and Damon McCoy.
5403 - Integrate Karsten Loesing's Google Summer of Code project to publish
5404 hidden service descriptors on a set of redundant relays that are a
5405 function of the hidden service address. Now we don't have to rely
5406 on three central hidden service authorities for publishing and
5407 fetching every hidden service descriptor. Implements proposal 114.
5408 - Allow tunnelled directory connections to ask for an encrypted
5409 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5410 connection independently. Now we can make anonymized begin_dir
5411 connections for (e.g.) more secure hidden service posting and
5414 o Major bugfixes (crashes and assert failures):
5415 - Stop imposing an arbitrary maximum on the number of file descriptors
5416 used for busy servers. Bug reported by Olaf Selke; patch from
5418 - Avoid possible failures when generating a directory with routers
5419 with over-long versions strings, or too many flags set.
5420 - Fix a rare assert error when we're closing one of our threads:
5421 use a mutex to protect the list of logs, so we never write to the
5422 list as it's being freed. Fixes the very rare bug 575, which is
5423 kind of the revenge of bug 222.
5424 - Avoid segfault in the case where a badly behaved v2 versioning
5425 directory sends a signed networkstatus with missing client-versions.
5426 - When we hit an EOF on a log (probably because we're shutting down),
5427 don't try to remove the log from the list: just mark it as
5428 unusable. (Bulletproofs against bug 222.)
5430 o Major bugfixes (code security fixes):
5431 - Detect size overflow in zlib code. Reported by Justin Ferguson and
5433 - Rewrite directory tokenization code to never run off the end of
5434 a string. Fixes bug 455. Patch from croup.
5435 - Be more paranoid about overwriting sensitive memory on free(),
5436 as a defensive programming tactic to ensure forward secrecy.
5438 o Major bugfixes (anonymity fixes):
5439 - Reject requests for reverse-dns lookup of names that are in
5440 a private address space. Patch from lodger.
5441 - Never report that we've used more bandwidth than we're willing to
5442 relay: it leaks how much non-relay traffic we're using. Resolves
5444 - As a client, do not believe any server that tells us that an
5445 address maps to an internal address space.
5446 - Warn about unsafe ControlPort configurations.
5447 - Directory authorities now call routers Fast if their bandwidth is
5448 at least 100KB/s, and consider their bandwidth adequate to be a
5449 Guard if it is at least 250KB/s, no matter the medians. This fix
5450 complements proposal 107.
5451 - Directory authorities now never mark more than 2 servers per IP as
5452 Valid and Running (or 5 on addresses shared by authorities).
5453 Implements proposal 109, by Kevin Bauer and Damon McCoy.
5454 - If we're a relay, avoid picking ourselves as an introduction point,
5455 a rendezvous point, or as the final hop for internal circuits. Bug
5456 reported by taranis and lodger.
5457 - Exit relays that are used as a client can now reach themselves
5458 using the .exit notation, rather than just launching an infinite
5459 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
5460 - Fix a bug where, when we were choosing the 'end stream reason' to
5461 put in our relay end cell that we send to the exit relay, Tor
5462 clients on Windows were sometimes sending the wrong 'reason'. The
5463 anonymity problem is that exit relays may be able to guess whether
5464 the client is running Windows, thus helping partition the anonymity
5465 set. Down the road we should stop sending reasons to exit relays,
5466 or otherwise prevent future versions of this bug.
5467 - Only update guard status (usable / not usable) once we have
5468 enough directory information. This was causing us to discard all our
5469 guards on startup if we hadn't been running for a few weeks. Fixes
5471 - When our directory information has been expired for a while, stop
5472 being willing to build circuits using it. Fixes bug 401.
5474 o Major bugfixes (peace of mind for relay operators)
5475 - Non-exit relays no longer answer "resolve" relay cells, so they
5476 can't be induced to do arbitrary DNS requests. (Tor clients already
5477 avoid using non-exit relays for resolve cells, but now servers
5478 enforce this too.) Fixes bug 619. Patch from lodger.
5479 - When we setconf ClientOnly to 1, close any current OR and Dir
5480 listeners. Reported by mwenge.
5482 o Major bugfixes (other):
5483 - If we only ever used Tor for hidden service lookups or posts, we
5484 would stop building circuits and start refusing connections after
5485 24 hours, since we falsely believed that Tor was dormant. Reported
5487 - Add a new __HashedControlSessionPassword option for controllers
5488 to use for one-off session password hashes that shouldn't get
5489 saved to disk by SAVECONF --- Vidalia users were accumulating a
5490 pile of HashedControlPassword lines in their torrc files, one for
5491 each time they had restarted Tor and then clicked Save. Make Tor
5492 automatically convert "HashedControlPassword" to this new option but
5493 only when it's given on the command line. Partial fix for bug 586.
5494 - Patch from "Andrew S. Lists" to catch when we contact a directory
5495 mirror at IP address X and he says we look like we're coming from
5496 IP address X. Otherwise this would screw up our address detection.
5497 - Reject uploaded descriptors and extrainfo documents if they're
5498 huge. Otherwise we'll cache them all over the network and it'll
5499 clog everything up. Suggested by Aljosha Judmayer.
5500 - When a hidden service was trying to establish an introduction point,
5501 and Tor *did* manage to reuse one of the preemptively built
5502 circuits, it didn't correctly remember which one it used,
5503 so it asked for another one soon after, until there were no
5504 more preemptive circuits, at which point it launched one from
5505 scratch. Bugfix on 0.0.9.x.
5507 o Rate limiting and load balancing improvements:
5508 - When we add data to a write buffer in response to the data on that
5509 write buffer getting low because of a flush, do not consider the
5510 newly added data as a candidate for immediate flushing, but rather
5511 make it wait until the next round of writing. Otherwise, we flush
5512 and refill recursively, and a single greedy TLS connection can
5513 eat all of our bandwidth.
5514 - When counting the number of bytes written on a TLS connection,
5515 look at the BIO actually used for writing to the network, not
5516 at the BIO used (sometimes) to buffer data for the network.
5517 Looking at different BIOs could result in write counts on the
5518 order of ULONG_MAX. Fixes bug 614.
5519 - If we change our MaxAdvertisedBandwidth and then reload torrc,
5520 Tor won't realize it should publish a new relay descriptor. Fixes
5521 bug 688, reported by mfr.
5522 - Avoid using too little bandwidth when our clock skips a few seconds.
5523 - Choose which bridge to use proportional to its advertised bandwidth,
5524 rather than uniformly at random. This should speed up Tor for
5525 bridge users. Also do this for people who set StrictEntryNodes.
5527 o Bootstrapping faster and building circuits more intelligently:
5528 - Fix bug 660 that was preventing us from knowing that we should
5529 preemptively build circuits to handle expected directory requests.
5530 - When we're checking if we have enough dir info for each relay
5531 to begin establishing circuits, make sure that we actually have
5532 the descriptor listed in the consensus, not just any descriptor.
5533 - Correctly notify one-hop connections when a circuit build has
5534 failed. Possible fix for bug 669. Found by lodger.
5535 - Clients now hold circuitless TLS connections open for 1.5 times
5536 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
5537 rebuild a new circuit over them within that timeframe. Previously,
5538 they held them open only for KeepalivePeriod (5 minutes).
5540 o Performance improvements (memory):
5541 - Add OpenBSD malloc code from "phk" as an optional malloc
5542 replacement on Linux: some glibc libraries do very poorly with
5543 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
5544 ./configure to get the replacement malloc code.
5545 - Switch our old ring buffer implementation for one more like that
5546 used by free Unix kernels. The wasted space in a buffer with 1mb
5547 of data will now be more like 8k than 1mb. The new implementation
5548 also avoids realloc();realloc(); patterns that can contribute to
5549 memory fragmentation.
5550 - Change the way that Tor buffers data that it is waiting to write.
5551 Instead of queueing data cells in an enormous ring buffer for each
5552 client->OR or OR->OR connection, we now queue cells on a separate
5553 queue for each circuit. This lets us use less slack memory, and
5554 will eventually let us be smarter about prioritizing different kinds
5556 - Reference-count and share copies of address policy entries; only 5%
5557 of them were actually distinct.
5558 - Tune parameters for cell pool allocation to minimize amount of
5560 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
5561 for every single inactive connection_t. Free items from the
5562 4k/16k-buffer free lists when they haven't been used for a while.
5563 - Make memory debugging information describe more about history
5564 of cell allocation, so we can help reduce our memory use.
5565 - Be even more aggressive about releasing RAM from small
5566 empty buffers. Thanks to our free-list code, this shouldn't be too
5567 performance-intensive.
5568 - Log malloc statistics from mallinfo() on platforms where it exists.
5569 - Use memory pools to allocate cells with better speed and memory
5570 efficiency, especially on platforms where malloc() is inefficient.
5571 - Add a --with-tcmalloc option to the configure script to link
5572 against tcmalloc (if present). Does not yet search for non-system
5575 o Performance improvements (socket management):
5576 - Count the number of open sockets separately from the number of
5577 active connection_t objects. This will let us avoid underusing
5578 our allocated connection limit.
5579 - We no longer use socket pairs to link an edge connection to an
5580 anonymous directory connection or a DirPort test connection.
5581 Instead, we track the link internally and transfer the data
5582 in-process. This saves two sockets per "linked" connection (at the
5583 client and at the server), and avoids the nasty Windows socketpair()
5585 - We were leaking a file descriptor if Tor started with a zero-length
5586 cached-descriptors file. Patch by "freddy77".
5588 o Performance improvements (CPU use):
5589 - Never walk through the list of logs if we know that no log target
5590 is interested in a given message.
5591 - Call routerlist_remove_old_routers() much less often. This should
5592 speed startup, especially on directory caches.
5593 - Base64 decoding was actually showing up on our profile when parsing
5594 the initial descriptor file; switch to an in-process all-at-once
5595 implementation that's about 3.5x times faster than calling out to
5597 - Use a slightly simpler string hashing algorithm (copying Python's
5598 instead of Java's) and optimize our digest hashing algorithm to take
5599 advantage of 64-bit platforms and to remove some possibly-costly
5601 - When implementing AES counter mode, update only the portions of the
5602 counter buffer that need to change, and don't keep separate
5603 network-order and host-order counters on big-endian hosts (where
5605 - Add an in-place version of aes_crypt() so that we can avoid doing a
5606 needless memcpy() call on each cell payload.
5607 - Use Critical Sections rather than Mutexes for synchronizing threads
5608 on win32; Mutexes are heavier-weight, and designed for synchronizing
5611 o Performance improvements (bandwidth use):
5612 - Don't try to launch new descriptor downloads quite so often when we
5613 already have enough directory information to build circuits.
5614 - Version 1 directories are no longer generated in full. Instead,
5615 authorities generate and serve "stub" v1 directories that list
5616 no servers. This will stop Tor versions 0.1.0.x and earlier from
5617 working, but (for security reasons) nobody should be running those
5619 - Avoid going directly to the directory authorities even if you're a
5620 relay, if you haven't found yourself reachable yet or if you've
5621 decided not to advertise your dirport yet. Addresses bug 556.
5622 - If we've gone 12 hours since our last bandwidth check, and we
5623 estimate we have less than 50KB bandwidth capacity but we could
5624 handle more, do another bandwidth test.
5625 - Support "If-Modified-Since" when answering HTTP requests for
5626 directories, running-routers documents, and v2 and v3 networkstatus
5627 documents. (There's no need to support it for router descriptors,
5628 since those are downloaded by descriptor digest.)
5629 - Stop fetching directory info so aggressively if your DirPort is
5630 on but your ORPort is off; stop fetching v2 dir info entirely.
5631 You can override these choices with the new FetchDirInfoEarly
5634 o Changed config option behavior (features):
5635 - Configuration files now accept C-style strings as values. This
5636 helps encode characters not allowed in the current configuration
5637 file format, such as newline or #. Addresses bug 557.
5638 - Add hidden services and DNSPorts to the list of things that make
5639 Tor accept that it has running ports. Change starting Tor with no
5640 ports from a fatal error to a warning; we might change it back if
5641 this turns out to confuse anybody. Fixes bug 579.
5642 - Make PublishServerDescriptor default to 1, so the default doesn't
5643 have to change as we invent new directory protocol versions.
5644 - Allow people to say PreferTunnelledDirConns rather than
5645 PreferTunneledDirConns, for those alternate-spellers out there.
5646 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5647 accommodate the growing number of servers that use the default
5648 and are reaching it.
5649 - Make it possible to enable HashedControlPassword and
5650 CookieAuthentication at the same time.
5651 - When a TrackHostExits-chosen exit fails too many times in a row,
5652 stop using it. Fixes bug 437.
5654 o Changed config option behavior (bugfixes):
5655 - Do not read the configuration file when we've only been told to
5656 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
5657 based on patch from Sebastian Hahn.
5658 - Actually validate the options passed to AuthDirReject,
5659 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
5660 - Make "ClientOnly 1" config option disable directory ports too.
5661 - Don't stop fetching descriptors when FetchUselessDescriptors is
5662 set, even if we stop asking for circuits. Bug reported by tup
5664 - Servers used to decline to publish their DirPort if their
5665 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
5666 they look only at BandwidthRate and RelayBandwidthRate.
5667 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
5668 minus 1 byte: the actual maximum declared bandwidth.
5669 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
5670 - Make the NodeFamilies config option work. (Reported by
5671 lodger -- it has never actually worked, even though we added it
5673 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
5674 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
5676 o New config options:
5677 - New configuration options AuthDirMaxServersPerAddr and
5678 AuthDirMaxServersperAuthAddr to override default maximum number
5679 of servers allowed on a single IP address. This is important for
5680 running a test network on a single host.
5681 - Three new config options (AlternateDirAuthority,
5682 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5683 user selectively replace the default directory authorities by type,
5684 rather than the all-or-nothing replacement that DirServer offers.
5685 - New config options AuthDirBadDir and AuthDirListBadDirs for
5686 authorities to mark certain relays as "bad directories" in the
5687 networkstatus documents. Also supports the "!baddir" directive in
5688 the approved-routers file.
5689 - New config option V2AuthoritativeDirectory that all v2 directory
5690 authorities must set. This lets v3 authorities choose not to serve
5691 v2 directory information.
5693 o Minor features (other):
5694 - When we're not serving v2 directory information, there is no reason
5695 to actually keep any around. Remove the obsolete files and directory
5696 on startup if they are very old and we aren't going to serve them.
5697 - When we negotiate a v2 link-layer connection (not yet implemented),
5698 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5699 negotiated a v1 connection for their next step. Initial steps for
5701 - When we have no consensus, check FallbackNetworkstatusFile (defaults
5702 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
5703 we can start out knowing some directory caches. We don't ship with
5704 a fallback consensus by default though, because it was making
5705 bootstrapping take too long while we tried many down relays.
5706 - Authorities send back an X-Descriptor-Not-New header in response to
5707 an accepted-but-discarded descriptor upload. Partially implements
5709 - If we find a cached-routers file that's been sitting around for more
5710 than 28 days unmodified, then most likely it's a leftover from
5711 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
5713 - When we (as a cache) download a descriptor because it was listed
5714 in a consensus, remember when the consensus was supposed to expire,
5715 and don't expire the descriptor until then.
5716 - Optionally (if built with -DEXPORTMALLINFO) export the output
5717 of mallinfo via http, as tor/mallinfo.txt. Only accessible
5719 - Tag every guard node in our state file with the version that
5720 we believe added it, or with our own version if we add it. This way,
5721 if a user temporarily runs an old version of Tor and then switches
5722 back to a new one, she doesn't automatically lose her guards.
5723 - When somebody requests a list of statuses or servers, and we have
5724 none of those, return a 404 rather than an empty 200.
5725 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
5727 - Add an HSAuthorityRecordStats option that hidden service authorities
5728 can use to track statistics of overall hidden service usage without
5729 logging information that would be as useful to an attacker.
5730 - Allow multiple HiddenServicePort directives with the same virtual
5731 port; when they occur, the user is sent round-robin to one
5732 of the target ports chosen at random. Partially fixes bug 393 by
5733 adding limited ad-hoc round-robining.
5734 - Revamp file-writing logic so we don't need to have the entire
5735 contents of a file in memory at once before we write to disk. Tor,
5738 o Minor bugfixes (other):
5739 - Alter the code that tries to recover from unhandled write
5740 errors, to not try to flush onto a socket that's given us
5742 - Directory mirrors no longer include a guess at the client's IP
5743 address if the connection appears to be coming from the same /24
5744 network; it was producing too many wrong guesses.
5745 - If we're trying to flush the last bytes on a connection (for
5746 example, when answering a directory request), reset the
5747 time-to-give-up timeout every time we manage to write something
5749 - Reject router descriptors with out-of-range bandwidthcapacity or
5750 bandwidthburst values.
5751 - If we can't expand our list of entry guards (e.g. because we're
5752 using bridges or we have StrictEntryNodes set), don't mark relays
5753 down when they fail a directory request. Otherwise we're too quick
5754 to mark all our entry points down.
5755 - Authorities no longer send back "400 you're unreachable please fix
5756 it" errors to Tor servers that aren't online all the time. We're
5757 supposed to tolerate these servers now.
5758 - Let directory authorities startup even when they can't generate
5759 a descriptor immediately, e.g. because they don't know their
5761 - Correctly enforce that elements of directory objects do not appear
5762 more often than they are allowed to appear.
5763 - Stop allowing hibernating servers to be "stable" or "fast".
5764 - On Windows, we were preventing other processes from reading
5765 cached-routers while Tor was running. (Reported by janbar)
5766 - Check return values from pthread_mutex functions.
5767 - When opening /dev/null in finish_daemonize(), do not pass the
5768 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
5769 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
5771 o Controller features:
5772 - The GETCONF command now escapes and quotes configuration values
5773 that don't otherwise fit into the torrc file.
5774 - The SETCONF command now handles quoted values correctly.
5775 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5776 ask about source, timestamp of arrival, purpose, etc. We need
5777 something like this to help Vidalia not do GeoIP lookups on bridge
5779 - Allow multiple HashedControlPassword config lines, to support
5780 multiple controller passwords.
5781 - Accept LF instead of CRLF on controller, since some software has a
5782 hard time generating real Internet newlines.
5783 - Add GETINFO values for the server status events
5784 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
5786 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
5787 GETINFO for Torstat to use until it can switch to using extrainfos.
5788 - New config option CookieAuthFile to choose a new location for the
5789 cookie authentication file, and config option
5790 CookieAuthFileGroupReadable to make it group-readable.
5791 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
5792 match requests to applications. Patch from Robert Hogan.
5793 - Add a RESOLVE command to launch hostname lookups. Original patch
5795 - Add GETINFO status/enough-dir-info to let controllers tell whether
5796 Tor has downloaded sufficient directory information. Patch from Tup.
5797 - You can now use the ControlSocket option to tell Tor to listen for
5798 controller connections on Unix domain sockets on systems that
5799 support them. Patch from Peter Palfrader.
5800 - New "GETINFO address-mappings/*" command to get address mappings
5801 with expiry information. "addr-mappings/*" is now deprecated.
5803 - Add a new config option __DisablePredictedCircuits designed for
5804 use by the controller, when we don't want Tor to build any circuits
5806 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
5807 so we can exit from the middle of the circuit.
5808 - Implement "getinfo status/circuit-established".
5809 - Implement "getinfo status/version/..." so a controller can tell
5810 whether the current version is recommended, and whether any versions
5811 are good, and how many authorities agree. Patch from "shibz".
5812 - Controllers should now specify cache=no or cache=yes when using
5813 the +POSTDESCRIPTOR command.
5814 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
5815 Robert Hogan. Fixes the first part of bug 681.
5816 - When reporting clock skew, and we know that the clock is _at least
5817 as skewed_ as some value, but we don't know the actual value,
5818 report the value as a "minimum skew."
5820 o Controller bugfixes:
5821 - Generate "STATUS_SERVER" events rather than misspelled
5822 "STATUS_SEVER" events. Caught by mwenge.
5823 - Reject controller commands over 1MB in length, so rogue
5824 processes can't run us out of memory.
5825 - Change the behavior of "getinfo status/good-server-descriptor"
5826 so it doesn't return failure when any authority disappears.
5827 - Send NAMESERVER_STATUS messages for a single failed nameserver
5829 - When the DANGEROUS_VERSION controller status event told us we're
5830 running an obsolete version, it used the string "OLD" to describe
5831 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5832 "OBSOLETE" in both cases.
5833 - Respond to INT and TERM SIGNAL commands before we execute the
5834 signal, in case the signal shuts us down. We had a patch in
5835 0.1.2.1-alpha that tried to do this by queueing the response on
5836 the connection's buffer before shutting down, but that really
5837 isn't the same thing at all. Bug located by Matt Edman.
5838 - Provide DNS expiry times in GMT, not in local time. For backward
5839 compatibility, ADDRMAP events only provide GMT expiry in an extended
5840 field. "GETINFO address-mappings" always does the right thing.
5841 - Use CRLF line endings properly in NS events.
5842 - Make 'getinfo fingerprint' return a 551 error if we're not a
5843 server, so we match what the control spec claims we do. Reported
5845 - Fix a typo in an error message when extendcircuit fails that
5846 caused us to not follow the \r\n-based delimiter protocol. Reported
5848 - When tunneling an encrypted directory connection, and its first
5849 circuit fails, do not leave it unattached and ask the controller
5850 to deal. Fixes the second part of bug 681.
5851 - Treat some 403 responses from directory servers as INFO rather than
5852 WARN-severity events.
5854 o Portability / building / compiling:
5855 - When building with --enable-gcc-warnings, check for whether Apple's
5856 warning "-Wshorten-64-to-32" is available.
5857 - Support compilation to target iPhone; patch from cjacker huang.
5858 To build for iPhone, pass the --enable-iphone option to configure.
5859 - Port Tor to build and run correctly on Windows CE systems, using
5860 the wcecompat library. Contributed by Valerio Lupi.
5861 - Detect non-ASCII platforms (if any still exist) and refuse to
5862 build there: some of our code assumes that 'A' is 65 and so on.
5863 - Clear up some MIPSPro compiler warnings.
5864 - Make autoconf search for libevent, openssl, and zlib consistently.
5865 - Update deprecated macros in configure.in.
5866 - When warning about missing headers, tell the user to let us
5867 know if the compile succeeds anyway, so we can downgrade the
5869 - Include the current subversion revision as part of the version
5870 string: either fetch it directly if we're in an SVN checkout, do
5871 some magic to guess it if we're in an SVK checkout, or use
5872 the last-detected version if we're building from a .tar.gz.
5873 Use this version consistently in log messages.
5874 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
5875 - Read resolv.conf files correctly on platforms where read() returns
5876 partial results on small file reads.
5877 - Build without verbose warnings even on gcc 4.2 and 4.3.
5878 - On Windows, correctly detect errors when listing the contents of
5879 a directory. Fix from lodger.
5880 - Run 'make test' as part of 'make dist', so we stop releasing so
5881 many development snapshots that fail their unit tests.
5882 - Add support to detect Libevent versions in the 1.4.x series
5884 - Add command-line arguments to unit-test executable so that we can
5885 invoke any chosen test from the command line rather than having
5886 to run the whole test suite at once; and so that we can turn on
5887 logging for the unit tests.
5888 - Do not automatically run configure from autogen.sh. This
5889 non-standard behavior tended to annoy people who have built other
5891 - Fix a macro/CPP interaction that was confusing some compilers:
5892 some GCCs don't like #if/#endif pairs inside macro arguments.
5894 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
5895 Fixes bug 704; fix from Steven Murdoch.
5896 - Correctly detect transparent proxy support on Linux hosts that
5897 require in.h to be included before netfilter_ipv4.h. Patch
5900 o Logging improvements:
5901 - When we haven't had any application requests lately, don't bother
5902 logging that we have expired a bunch of descriptors.
5903 - When attempting to open a logfile fails, tell us why.
5904 - Only log guard node status when guard node status has changed.
5905 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
5906 make "INFO" 75% less verbose.
5907 - When SafeLogging is disabled, log addresses along with all TLS
5909 - Report TLS "zero return" case as a "clean close" and "IO error"
5910 as a "close". Stop calling closes "unexpected closes": existing
5911 Tors don't use SSL_close(), so having a connection close without
5912 the TLS shutdown handshake is hardly unexpected.
5913 - When we receive a consensus from the future, warn about skew.
5914 - Make "not enough dir info yet" warnings describe *why* Tor feels
5915 it doesn't have enough directory info yet.
5916 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5917 consumers. (We already do this on HUP.)
5918 - Give more descriptive well-formedness errors for out-of-range
5919 hidden service descriptor/protocol versions.
5920 - Stop recommending that every server operator send mail to tor-ops.
5921 Resolves bug 597. Bugfix on 0.1.2.x.
5922 - Improve skew reporting: try to give the user a better log message
5923 about how skewed they are, and how much this matters.
5924 - New --quiet command-line option to suppress the default console log.
5925 Good in combination with --hash-password.
5926 - Don't complain that "your server has not managed to confirm that its
5927 ports are reachable" if we haven't been able to build any circuits
5929 - Detect the reason for failing to mmap a descriptor file we just
5930 wrote, and give a more useful log message. Fixes bug 533.
5931 - Always prepend "Bug: " to any log message about a bug.
5932 - When dumping memory usage, list bytes used in buffer memory
5934 - When running with dmalloc, dump more stats on hup and on exit.
5935 - Put a platform string (e.g. "Linux i686") in the startup log
5936 message, so when people paste just their logs, we know if it's
5937 OpenBSD or Windows or what.
5938 - When logging memory usage, break down memory used in buffers by
5940 - When we are reporting the DirServer line we just parsed, we were
5941 logging the second stanza of the key fingerprint, not the first.
5942 - Even though Windows is equally happy with / and \ as path separators,
5943 try to use \ consistently on Windows and / consistently on Unix: it
5944 makes the log messages nicer.
5945 - On OSX, stop warning the user that kqueue support in libevent is
5946 "experimental", since it seems to have worked fine for ages.
5948 o Contributed scripts and tools:
5949 - Update linux-tor-prio.sh script to allow QoS based on the uid of
5950 the Tor process. Patch from Marco Bonetti with tweaks from Mike
5952 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
5953 Unix users an easy way to script their Tor process (e.g. by
5954 adjusting bandwidth based on the time of the day).
5955 - In the exitlist script, only consider the most recently published
5956 server descriptor for each server. Also, when the user requests
5957 a list of servers that _reject_ connections to a given address,
5958 explicitly exclude the IPs that also have servers that accept
5959 connections to that address. Resolves bug 405.
5960 - Include a new contrib/tor-exit-notice.html file that exit relay
5961 operators can put on their website to help reduce abuse queries.
5963 o Newly deprecated features:
5964 - The status/version/num-versioning and status/version/num-concurring
5965 GETINFO controller options are no longer useful in the v3 directory
5966 protocol: treat them as deprecated, and warn when they're used.
5967 - The RedirectExits config option is now deprecated.
5970 - Drop the old code to choke directory connections when the
5971 corresponding OR connections got full: thanks to the cell queue
5972 feature, OR conns don't get full any more.
5973 - Remove the old "dns worker" server DNS code: it hasn't been default
5974 since 0.1.2.2-alpha, and all the servers are using the new
5976 - Remove the code to generate the oldest (v1) directory format.
5977 - Remove support for the old bw_accounting file: we've been storing
5978 bandwidth accounting information in the state file since
5979 0.1.2.5-alpha. This may result in bandwidth accounting errors
5980 if you try to upgrade from 0.1.1.x or earlier, or if you try to
5981 downgrade to 0.1.1.x or earlier.
5982 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
5983 it, it had no AES, and it hasn't seen any security patches since
5985 - Stop overloading the circuit_t.onionskin field for both "onionskin
5986 from a CREATE cell that we are waiting for a cpuworker to be
5987 assigned" and "onionskin from an EXTEND cell that we are going to
5988 send to an OR as soon as we are connected". Might help with bug 600.
5989 - Remove the tor_strpartition() function: its logic was confused,
5990 and it was only used for one thing that could be implemented far
5992 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
5993 and TorControl.py, as they use the old v0 controller protocol,
5994 and are obsoleted by TorFlow anyway.
5995 - Drop support for v1 rendezvous descriptors, since we never used
5996 them anyway, and the code has probably rotted by now. Based on
5997 patch from Karsten Loesing.
5998 - Stop allowing address masks that do not correspond to bit prefixes.
5999 We have warned about these for a really long time; now it's time
6000 to reject them. (Patch from croup.)
6001 - Remove an optimization in the AES counter-mode code that assumed
6002 that the counter never exceeded 2^68. When the counter can be set
6003 arbitrarily as an IV (as it is by Karsten's new hidden services
6004 code), this assumption no longer holds.
6005 - Disable the SETROUTERPURPOSE controller command: it is now
6009 Changes in version 0.1.2.19 - 2008-01-17
6010 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
6011 exit policy a little bit more conservative so it's safer to run an
6012 exit relay on a home system, and fixes a variety of smaller issues.
6015 - Exit policies now reject connections that are addressed to a
6016 relay's public (external) IP address too, unless
6017 ExitPolicyRejectPrivate is turned off. We do this because too
6018 many relays are running nearby to services that trust them based
6022 - When the clock jumps forward a lot, do not allow the bandwidth
6023 buckets to become negative. Fixes bug 544.
6024 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6025 on every successful resolve. Reported by Mike Perry.
6026 - Purge old entries from the "rephist" database and the hidden
6027 service descriptor database even when DirPort is zero.
6028 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6029 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6030 crashing or mis-answering these requests.
6031 - When we decide to send a 503 response to a request for servers, do
6032 not then also send the server descriptors: this defeats the whole
6033 purpose. Fixes bug 539.
6036 - Changing the ExitPolicyRejectPrivate setting should cause us to
6037 rebuild our server descriptor.
6038 - Fix handling of hex nicknames when answering controller requests for
6039 networkstatus by name, or when deciding whether to warn about
6040 unknown routers in a config option. (Patch from mwenge.)
6041 - Fix a couple of hard-to-trigger autoconf problems that could result
6042 in really weird results on platforms whose sys/types.h files define
6043 nonstandard integer types.
6044 - Don't try to create the datadir when running --verify-config or
6045 --hash-password. Resolves bug 540.
6046 - If we were having problems getting a particular descriptor from the
6047 directory caches, and then we learned about a new descriptor for
6048 that router, we weren't resetting our failure count. Reported
6050 - Although we fixed bug 539 (where servers would send HTTP status 503
6051 responses _and_ send a body too), there are still servers out there
6052 that haven't upgraded. Therefore, make clients parse such bodies
6053 when they receive them.
6054 - Run correctly on systems where rlim_t is larger than unsigned long.
6055 This includes some 64-bit systems.
6056 - Run correctly on platforms (like some versions of OS X 10.5) where
6057 the real limit for number of open files is OPEN_FILES, not rlim_max
6058 from getrlimit(RLIMIT_NOFILES).
6059 - Avoid a spurious free on base64 failure.
6060 - Avoid segfaults on certain complex invocations of
6061 router_get_by_hexdigest().
6062 - Fix rare bug on REDIRECTSTREAM control command when called with no
6063 port set: it could erroneously report an error when none had
6067 Changes in version 0.1.2.18 - 2007-10-28
6068 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
6069 hidden service introduction that were causing huge delays, and a big
6070 bug that was causing some servers to disappear from the network status
6071 lists for a few hours each day.
6073 o Major bugfixes (crashes):
6074 - If a connection is shut down abruptly because of something that
6075 happened inside connection_flushed_some(), do not call
6076 connection_finished_flushing(). Should fix bug 451:
6077 "connection_stop_writing: Assertion conn->write_event failed"
6078 Bugfix on 0.1.2.7-alpha.
6079 - Fix possible segfaults in functions called from
6080 rend_process_relay_cell().
6082 o Major bugfixes (hidden services):
6083 - Hidden services were choosing introduction points uniquely by
6084 hexdigest, but when constructing the hidden service descriptor
6085 they merely wrote the (potentially ambiguous) nickname.
6086 - Clients now use the v2 intro format for hidden service
6087 connections: they specify their chosen rendezvous point by identity
6088 digest rather than by (potentially ambiguous) nickname. These
6089 changes could speed up hidden service connections dramatically.
6091 o Major bugfixes (other):
6092 - Stop publishing a new server descriptor just because we get a
6093 HUP signal. This led (in a roundabout way) to some servers getting
6094 dropped from the networkstatus lists for a few hours each day.
6095 - When looking for a circuit to cannibalize, consider family as well
6096 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6097 circuit cannibalization).
6098 - When a router wasn't listed in a new networkstatus, we were leaving
6099 the flags for that router alone -- meaning it remained Named,
6100 Running, etc -- even though absence from the networkstatus means
6101 that it shouldn't be considered to exist at all anymore. Now we
6102 clear all the flags for routers that fall out of the networkstatus
6103 consensus. Fixes bug 529.
6106 - Don't try to access (or alter) the state file when running
6107 --list-fingerprint or --verify-config or --hash-password. Resolves
6109 - When generating information telling us how to extend to a given
6110 router, do not try to include the nickname if it is
6111 absent. Resolves bug 467.
6112 - Fix a user-triggerable segfault in expand_filename(). (There isn't
6113 a way to trigger this remotely.)
6114 - When sending a status event to the controller telling it that an
6115 OR address is reachable, set the port correctly. (Previously we
6116 were reporting the dir port.)
6117 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6118 command. Bugfix on 0.1.2.17.
6119 - When loading bandwidth history, do not believe any information in
6120 the future. Fixes bug 434.
6121 - When loading entry guard information, do not believe any information
6123 - When we have our clock set far in the future and generate an
6124 onion key, then re-set our clock to be correct, we should not stop
6125 the onion key from getting rotated.
6126 - On some platforms, accept() can return a broken address. Detect
6127 this more quietly, and deal accordingly. Fixes bug 483.
6128 - It's not actually an error to find a non-pending entry in the DNS
6129 cache when canceling a pending resolve. Don't log unless stuff
6130 is fishy. Resolves bug 463.
6131 - Don't reset trusted dir server list when we set a configuration
6132 option. Patch from Robert Hogan.
6135 Changes in version 0.1.2.17 - 2007-08-30
6136 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6137 X bundles. Vidalia 0.0.14 makes authentication required for the
6138 ControlPort in the default configuration, which addresses important
6139 security risks. Everybody who uses Vidalia (or another controller)
6142 In addition, this Tor update fixes major load balancing problems with
6143 path selection, which should speed things up a lot once many people
6146 o Major bugfixes (security):
6147 - We removed support for the old (v0) control protocol. It has been
6148 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6149 become more of a headache than it's worth.
6151 o Major bugfixes (load balancing):
6152 - When choosing nodes for non-guard positions, weight guards
6153 proportionally less, since they already have enough load. Patch
6155 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6156 will allow fast Tor servers to get more attention.
6157 - When we're upgrading from an old Tor version, forget our current
6158 guards and pick new ones according to the new weightings. These
6159 three load balancing patches could raise effective network capacity
6160 by a factor of four. Thanks to Mike Perry for measurements.
6162 o Major bugfixes (stream expiration):
6163 - Expire not-yet-successful application streams in all cases if
6164 they've been around longer than SocksTimeout. Right now there are
6165 some cases where the stream will live forever, demanding a new
6166 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6168 o Minor features (controller):
6169 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6170 is valid before any authentication has been received. It tells
6171 a controller what kind of authentication is expected, and what
6172 protocol is spoken. Implements proposal 119.
6174 o Minor bugfixes (performance):
6175 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6176 greatly speeding up loading cached-routers from disk on startup.
6177 - Disable sentinel-based debugging for buffer code: we squashed all
6178 the bugs that this was supposed to detect a long time ago, and now
6179 its only effect is to change our buffer sizes from nice powers of
6180 two (which platform mallocs tend to like) to values slightly over
6181 powers of two (which make some platform mallocs sad).
6183 o Minor bugfixes (misc):
6184 - If exit bandwidth ever exceeds one third of total bandwidth, then
6185 use the correct formula to weight exit nodes when choosing paths.
6186 Based on patch from Mike Perry.
6187 - Choose perfectly fairly among routers when choosing by bandwidth and
6188 weighting by fraction of bandwidth provided by exits. Previously, we
6189 would choose with only approximate fairness, and correct ourselves
6190 if we ran off the end of the list.
6191 - If we require CookieAuthentication but we fail to write the
6192 cookie file, we would warn but not exit, and end up in a state
6193 where no controller could authenticate. Now we exit.
6194 - If we require CookieAuthentication, stop generating a new cookie
6195 every time we change any piece of our config.
6196 - Refuse to start with certain directory authority keys, and
6197 encourage people using them to stop.
6198 - Terminate multi-line control events properly. Original patch
6200 - Fix a minor memory leak when we fail to find enough suitable
6201 servers to choose a circuit.
6202 - Stop leaking part of the descriptor when we run into a particularly
6203 unparseable piece of it.
6206 Changes in version 0.1.2.16 - 2007-08-01
6207 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6208 remote attacker in certain situations to rewrite the user's torrc
6209 configuration file. This can completely compromise anonymity of users
6210 in most configurations, including those running the Vidalia bundles,
6211 TorK, etc. Or worse.
6213 o Major security fixes:
6214 - Close immediately after missing authentication on control port;
6215 do not allow multiple authentication attempts.
6218 Changes in version 0.1.2.15 - 2007-07-17
6219 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6220 problems, fixes compilation on BSD, and fixes a variety of other
6221 bugs. Everybody should upgrade.
6223 o Major bugfixes (compilation):
6224 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6226 o Major bugfixes (crashes):
6227 - Try even harder not to dereference the first character after
6228 an mmap(). Reported by lodger.
6229 - Fix a crash bug in directory authorities when we re-number the
6230 routerlist while inserting a new router.
6231 - When the cached-routers file is an even multiple of the page size,
6232 don't run off the end and crash. (Fixes bug 455; based on idea
6234 - Fix eventdns.c behavior on Solaris: It is critical to include
6235 orconfig.h _before_ sys/types.h, so that we can get the expected
6236 definition of _FILE_OFFSET_BITS.
6238 o Major bugfixes (security):
6239 - Fix a possible buffer overrun when using BSD natd support. Bug
6241 - When sending destroy cells from a circuit's origin, don't include
6242 the reason for tearing down the circuit. The spec says we didn't,
6243 and now we actually don't. Reported by lodger.
6244 - Keep streamids from different exits on a circuit separate. This
6245 bug may have allowed other routers on a given circuit to inject
6246 cells into streams. Reported by lodger; fixes bug 446.
6247 - If there's a never-before-connected-to guard node in our list,
6248 never choose any guards past it. This way we don't expand our
6249 guard list unless we need to.
6251 o Minor bugfixes (guard nodes):
6252 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6253 don't get overused as guards.
6255 o Minor bugfixes (directory):
6256 - Correctly count the number of authorities that recommend each
6257 version. Previously, we were under-counting by 1.
6258 - Fix a potential crash bug when we load many server descriptors at
6259 once and some of them make others of them obsolete. Fixes bug 458.
6261 o Minor bugfixes (hidden services):
6262 - Stop tearing down the whole circuit when the user asks for a
6263 connection to a port that the hidden service didn't configure.
6266 o Minor bugfixes (misc):
6267 - On Windows, we were preventing other processes from reading
6268 cached-routers while Tor was running. Reported by janbar.
6269 - Fix a possible (but very unlikely) bug in picking routers by
6270 bandwidth. Add a log message to confirm that it is in fact
6271 unlikely. Patch from lodger.
6272 - Backport a couple of memory leak fixes.
6273 - Backport miscellaneous cosmetic bugfixes.
6276 Changes in version 0.1.2.14 - 2007-05-25
6277 Tor 0.1.2.14 changes the addresses of two directory authorities (this
6278 change especially affects those who serve or use hidden services),
6279 and fixes several other crash- and security-related bugs.
6281 o Directory authority changes:
6282 - Two directory authorities (moria1 and moria2) just moved to new
6283 IP addresses. This change will particularly affect those who serve
6284 or use hidden services.
6286 o Major bugfixes (crashes):
6287 - If a directory server runs out of space in the connection table
6288 as it's processing a begin_dir request, it will free the exit stream
6289 but leave it attached to the circuit, leading to unpredictable
6290 behavior. (Reported by seeess, fixes bug 425.)
6291 - Fix a bug in dirserv_remove_invalid() that would cause authorities
6292 to corrupt memory under some really unlikely scenarios.
6293 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
6294 - Avoid segfaults when reading from mmaped descriptor file. (Reported
6297 o Major bugfixes (security):
6298 - When choosing an entry guard for a circuit, avoid using guards
6299 that are in the same family as the chosen exit -- not just guards
6300 that are exactly the chosen exit. (Reported by lodger.)
6302 o Major bugfixes (resource management):
6303 - If a directory authority is down, skip it when deciding where to get
6304 networkstatus objects or descriptors. Otherwise we keep asking
6305 every 10 seconds forever. Fixes bug 384.
6306 - Count it as a failure if we fetch a valid network-status but we
6307 don't want to keep it. Otherwise we'll keep fetching it and keep
6308 not wanting to keep it. Fixes part of bug 422.
6309 - If all of our dirservers have given us bad or no networkstatuses
6310 lately, then stop hammering them once per minute even when we
6311 think they're failed. Fixes another part of bug 422.
6314 - Actually set the purpose correctly for descriptors inserted with
6316 - When we have k non-v2 authorities in our DirServer config,
6317 we ignored the last k authorities in the list when updating our
6319 - Correctly back-off from requesting router descriptors that we are
6320 having a hard time downloading.
6321 - Read resolv.conf files correctly on platforms where read() returns
6322 partial results on small file reads.
6323 - Don't rebuild the entire router store every time we get 32K of
6324 routers: rebuild it when the journal gets very large, or when
6325 the gaps in the store get very large.
6328 - When routers publish SVN revisions in their router descriptors,
6329 authorities now include those versions correctly in networkstatus
6331 - Warn when using a version of libevent before 1.3b to run a server on
6332 OSX or BSD: these versions interact badly with userspace threads.
6335 Changes in version 0.1.2.13 - 2007-04-24
6336 This release features some major anonymity fixes, such as safer path
6337 selection; better client performance; faster bootstrapping, better
6338 address detection, and better DNS support for servers; write limiting as
6339 well as read limiting to make servers easier to run; and a huge pile of
6340 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
6342 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
6343 of the Freenode IRC network, remembering his patience and vision for
6344 free speech on the Internet.
6346 o Major features, client performance:
6347 - Weight directory requests by advertised bandwidth. Now we can
6348 let servers enable write limiting but still allow most clients to
6349 succeed at their directory requests. (We still ignore weights when
6350 choosing a directory authority; I hope this is a feature.)
6351 - Stop overloading exit nodes -- avoid choosing them for entry or
6352 middle hops when the total bandwidth available from non-exit nodes
6353 is much higher than the total bandwidth available from exit nodes.
6354 - Rather than waiting a fixed amount of time between retrying
6355 application connections, we wait only 10 seconds for the first,
6356 10 seconds for the second, and 15 seconds for each retry after
6357 that. Hopefully this will improve the expected user experience.
6358 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
6359 to open a stream fails; now we do in more cases. This should
6360 make clients able to find a good exit faster in some cases, since
6361 unhandleable requests will now get an error rather than timing out.
6363 o Major features, client functionality:
6364 - Implement BEGIN_DIR cells, so we can connect to a directory
6365 server via TLS to do encrypted directory requests rather than
6366 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
6367 config options if you like. For now, this feature only works if
6368 you already have a descriptor for the destination dirserver.
6369 - Add support for transparent application connections: this basically
6370 bundles the functionality of trans-proxy-tor into the Tor
6371 mainline. Now hosts with compliant pf/netfilter implementations
6372 can redirect TCP connections straight to Tor without diverting
6373 through SOCKS. (Based on patch from tup.)
6374 - Add support for using natd; this allows FreeBSDs earlier than
6375 5.1.2 to have ipfw send connections through Tor without using
6376 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
6378 o Major features, servers:
6379 - Setting up a dyndns name for your server is now optional: servers
6380 with no hostname or IP address will learn their IP address by
6381 asking the directory authorities. This code only kicks in when you
6382 would normally have exited with a "no address" error. Nothing's
6383 authenticated, so use with care.
6384 - Directory servers now spool server descriptors, v1 directories,
6385 and v2 networkstatus objects to buffers as needed rather than en
6386 masse. They also mmap the cached-routers files. These steps save
6388 - Stop requiring clients to have well-formed certificates, and stop
6389 checking nicknames in certificates. (Clients have certificates so
6390 that they can look like Tor servers, but in the future we might want
6391 to allow them to look like regular TLS clients instead. Nicknames
6392 in certificates serve no purpose other than making our protocol
6393 easier to recognize on the wire.) Implements proposal 106.
6395 o Improvements on DNS support:
6396 - Add "eventdns" asynchronous dns library originally based on code
6397 from Adam Langley. Now we can discard the old rickety dnsworker
6398 concept, and support a wider variety of DNS functions. Allows
6399 multithreaded builds on NetBSD and OpenBSD again.
6400 - Add server-side support for "reverse" DNS lookups (using PTR
6401 records so clients can determine the canonical hostname for a given
6402 IPv4 address). Only supported by servers using eventdns; servers
6403 now announce in their descriptors if they don't support eventdns.
6404 - Workaround for name servers (like Earthlink's) that hijack failing
6405 DNS requests and replace the no-such-server answer with a "helpful"
6406 redirect to an advertising-driven search portal. Also work around
6407 DNS hijackers who "helpfully" decline to hijack known-invalid
6408 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
6409 lets you turn it off.
6410 - Servers now check for the case when common DNS requests are going to
6411 wildcarded addresses (i.e. all getting the same answer), and change
6412 their exit policy to reject *:* if it's happening.
6413 - When asked to resolve a hostname, don't use non-exit servers unless
6414 requested to do so. This allows servers with broken DNS to be
6415 useful to the network.
6416 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6417 useless IPv6 DNS resolves.
6418 - Specify and implement client-side SOCKS5 interface for reverse DNS
6419 lookups (see doc/socks-extensions.txt). Also cache them.
6420 - When we change nameservers or IP addresses, reset and re-launch
6421 our tests for DNS hijacking.
6423 o Improvements on reachability testing:
6424 - Servers send out a burst of long-range padding cells once they've
6425 established that they're reachable. Spread them over 4 circuits,
6426 so hopefully a few will be fast. This exercises bandwidth and
6427 bootstraps them into the directory more quickly.
6428 - When we find our DirPort to be reachable, publish a new descriptor
6429 so we'll tell the world (reported by pnx).
6430 - Directory authorities now only decide that routers are reachable
6431 if their identity keys are as expected.
6432 - Do DirPort reachability tests less often, since a single test
6433 chews through many circuits before giving up.
6434 - Avoid some false positives during reachability testing: don't try
6435 to test via a server that's on the same /24 network as us.
6436 - Start publishing one minute or so after we find our ORPort
6437 to be reachable. This will help reduce the number of descriptors
6438 we have for ourselves floating around, since it's quite likely
6439 other things (e.g. DirPort) will change during that minute too.
6440 - Routers no longer try to rebuild long-term connections to directory
6441 authorities, and directory authorities no longer try to rebuild
6442 long-term connections to all servers. We still don't hang up
6443 connections in these two cases though -- we need to look at it
6444 more carefully to avoid flapping, and we likely need to wait til
6445 0.1.1.x is obsolete.
6447 o Improvements on rate limiting:
6448 - Enable write limiting as well as read limiting. Now we sacrifice
6449 capacity if we're pushing out lots of directory traffic, rather
6450 than overrunning the user's intended bandwidth limits.
6451 - Include TLS overhead when counting bandwidth usage; previously, we
6452 would count only the bytes sent over TLS, but not the bytes used
6454 - Servers decline directory requests much more aggressively when
6455 they're low on bandwidth. Otherwise they end up queueing more and
6456 more directory responses, which can't be good for latency.
6457 - But never refuse directory requests from local addresses.
6458 - Be willing to read or write on local connections (e.g. controller
6459 connections) even when the global rate limiting buckets are empty.
6460 - Flush local controller connection buffers periodically as we're
6461 writing to them, so we avoid queueing 4+ megabytes of data before
6463 - Revise and clean up the torrc.sample that we ship with; add
6464 a section for BandwidthRate and BandwidthBurst.
6466 o Major features, NT services:
6467 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
6468 command-line flag so that admins can override the default by saying
6469 "tor --service install --user "SomeUser"". This will not affect
6470 existing installed services. Also, warn the user that the service
6471 will look for its configuration file in the service user's
6472 %appdata% directory. (We can't do the "hardwire the user's appdata
6473 directory" trick any more, since we may not have read access to that
6475 - Support running the Tor service with a torrc not in the same
6476 directory as tor.exe and default to using the torrc located in
6477 the %appdata%\Tor\ of the user who installed the service. Patch
6479 - Add an --ignore-missing-torrc command-line option so that we can
6480 get the "use sensible defaults if the configuration file doesn't
6481 exist" behavior even when specifying a torrc location on the
6483 - When stopping an NT service, wait up to 10 sec for it to actually
6484 stop. (Patch from Matt Edman; resolves bug 295.)
6486 o Directory authority improvements:
6487 - Stop letting hibernating or obsolete servers affect uptime and
6489 - Stop listing hibernating servers in the v1 directory.
6490 - Authorities no longer recommend exits as guards if this would shift
6491 too much load to the exit nodes.
6492 - Authorities now specify server versions in networkstatus. This adds
6493 about 2% to the size of compressed networkstatus docs, and allows
6494 clients to tell which servers support BEGIN_DIR and which don't.
6495 The implementation is forward-compatible with a proposed future
6496 protocol version scheme not tied to Tor versions.
6497 - DirServer configuration lines now have an orport= option so
6498 clients can open encrypted tunnels to the authorities without
6499 having downloaded their descriptors yet. Enabled for moria1,
6500 moria2, tor26, and lefkada now in the default configuration.
6501 - Add a BadDirectory flag to network status docs so that authorities
6502 can (eventually) tell clients about caches they believe to be
6503 broken. Not used yet.
6504 - Allow authorities to list nodes as bad exits in their
6505 approved-routers file by fingerprint or by address. If most
6506 authorities set a BadExit flag for a server, clients don't think
6507 of it as a general-purpose exit. Clients only consider authorities
6508 that advertise themselves as listing bad exits.
6509 - Patch from Steve Hildrey: Generate network status correctly on
6510 non-versioning dirservers.
6511 - Have directory authorities allow larger amounts of drift in uptime
6512 without replacing the server descriptor: previously, a server that
6513 restarted every 30 minutes could have 48 "interesting" descriptors
6515 - Reserve the nickname "Unnamed" for routers that can't pick
6516 a hostname: any router can call itself Unnamed; directory
6517 authorities will never allocate Unnamed to any particular router;
6518 clients won't believe that any router is the canonical Unnamed.
6520 o Directory mirrors and clients:
6521 - Discard any v1 directory info that's over 1 month old (for
6522 directories) or over 1 week old (for running-routers lists).
6523 - Clients track responses with status 503 from dirservers. After a
6524 dirserver has given us a 503, we try not to use it until an hour has
6525 gone by, or until we have no dirservers that haven't given us a 503.
6526 - When we get a 503 from a directory, and we're not a server, we no
6527 longer count the failure against the total number of failures
6528 allowed for the object we're trying to download.
6529 - Prepare for servers to publish descriptors less often: never
6530 discard a descriptor simply for being too old until either it is
6531 recommended by no authorities, or until we get a better one for
6532 the same router. Make caches consider retaining old recommended
6533 routers for even longer.
6534 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
6535 headers for content, so that we can work better in the presence of
6536 caching HTTP proxies.
6537 - Stop fetching descriptors if you're not a dir mirror and you
6538 haven't tried to establish any circuits lately. (This currently
6539 causes some dangerous behavior, because when you start up again
6540 you'll use your ancient server descriptors.)
6542 o Major fixes, crashes:
6543 - Stop crashing when the controller asks us to resetconf more than
6544 one config option at once. (Vidalia 0.0.11 does this.)
6545 - Fix a longstanding obscure crash bug that could occur when we run
6546 out of DNS worker processes, if we're not using eventdns. (Resolves
6548 - Fix an assert that could trigger if a controller quickly set then
6549 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
6550 - Avoid crash when telling controller about stream-status and a
6552 - Avoid sending junk to controllers or segfaulting when a controller
6553 uses EVENT_NEW_DESC with verbose nicknames.
6554 - Stop triggering asserts if the controller tries to extend hidden
6555 service circuits (reported by mwenge).
6556 - If we start a server with ClientOnly 1, then set ClientOnly to 0
6557 and hup, stop triggering an assert based on an empty onion_key.
6558 - Mask out all signals in sub-threads; only the libevent signal
6559 handler should be processing them. This should prevent some crashes
6560 on some machines using pthreads. (Patch from coderman.)
6561 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
6563 o Major fixes, anonymity/security:
6564 - Automatically avoid picking more than one node from the same
6565 /16 network when constructing a circuit. Add an
6566 "EnforceDistinctSubnets" option to let people disable it if they
6567 want to operate private test networks on a single subnet.
6568 - When generating bandwidth history, round down to the nearest
6569 1k. When storing accounting data, round up to the nearest 1k.
6570 - When we're running as a server, remember when we last rotated onion
6571 keys, so that we will rotate keys once they're a week old even if
6572 we never stay up for a week ourselves.
6573 - If a client asked for a server by name, and there's a named server
6574 in our network-status but we don't have its descriptor yet, we
6575 could return an unnamed server instead.
6576 - Reject (most) attempts to use Tor circuits with length one. (If
6577 many people start using Tor as a one-hop proxy, exit nodes become
6578 a more attractive target for compromise.)
6579 - Just because your DirPort is open doesn't mean people should be
6580 able to remotely teach you about hidden service descriptors. Now
6581 only accept rendezvous posts if you've got HSAuthoritativeDir set.
6582 - Fix a potential race condition in the rpm installer. Found by
6584 - Do not log IPs with TLS failures for incoming TLS
6585 connections. (Fixes bug 382.)
6587 o Major fixes, other:
6588 - If our system clock jumps back in time, don't publish a negative
6589 uptime in the descriptor.
6590 - When we start during an accounting interval before it's time to wake
6591 up, remember to wake up at the correct time. (May fix bug 342.)
6592 - Previously, we would cache up to 16 old networkstatus documents
6593 indefinitely, if they came from nontrusted authorities. Now we
6594 discard them if they are more than 10 days old.
6595 - When we have a state file we cannot parse, tell the user and
6596 move it aside. Now we avoid situations where the user starts
6597 Tor in 1904, Tor writes a state file with that timestamp in it,
6598 the user fixes her clock, and Tor refuses to start.
6599 - Publish a new descriptor after we hup/reload. This is important
6600 if our config has changed such that we'll want to start advertising
6601 our DirPort now, etc.
6602 - If we are using an exit enclave and we can't connect, e.g. because
6603 its webserver is misconfigured to not listen on localhost, then
6604 back off and try connecting from somewhere else before we fail.
6606 o New config options or behaviors:
6607 - When EntryNodes are configured, rebuild the guard list to contain,
6608 in order: the EntryNodes that were guards before; the rest of the
6609 EntryNodes; the nodes that were guards before.
6610 - Do not warn when individual nodes in the configuration's EntryNodes,
6611 ExitNodes, etc are down: warn only when all possible nodes
6612 are down. (Fixes bug 348.)
6613 - Put a lower-bound on MaxAdvertisedBandwidth.
6614 - Start using the state file to store bandwidth accounting data:
6615 the bw_accounting file is now obsolete. We'll keep generating it
6616 for a while for people who are still using 0.1.2.4-alpha.
6617 - Try to batch changes to the state file so that we do as few
6618 disk writes as possible while still storing important things in
6620 - The state file and the bw_accounting file get saved less often when
6621 the AvoidDiskWrites config option is set.
6622 - Make PIDFile work on Windows.
6623 - Add internal descriptions for a bunch of configuration options:
6624 accessible via controller interface and in comments in saved
6626 - Reject *:563 (NNTPS) in the default exit policy. We already reject
6627 NNTP by default, so this seems like a sensible addition.
6628 - Clients now reject hostnames with invalid characters. This should
6629 avoid some inadvertent info leaks. Add an option
6630 AllowNonRFC953Hostnames to disable this behavior, in case somebody
6631 is running a private network with hosts called @, !, and #.
6632 - Check for addresses with invalid characters at the exit as well,
6633 and warn less verbosely when they fail. You can override this by
6634 setting ServerDNSAllowNonRFC953Addresses to 1.
6635 - Remove some options that have been deprecated since at least
6636 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
6637 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
6638 to set log options. Mark PathlenCoinWeight as obsolete.
6639 - Stop accepting certain malformed ports in configured exit policies.
6640 - When the user uses bad syntax in the Log config line, stop
6641 suggesting other bad syntax as a replacement.
6642 - Add new config option "ResolvConf" to let the server operator
6643 choose an alternate resolve.conf file when using eventdns.
6644 - If one of our entry guards is on the ExcludeNodes list, or the
6645 directory authorities don't think it's a good guard, treat it as
6646 if it were unlisted: stop using it as a guard, and throw it off
6647 the guards list if it stays that way for a long time.
6648 - Allow directory authorities to be marked separately as authorities
6649 for the v1 directory protocol, the v2 directory protocol, and
6650 as hidden service directories, to make it easier to retire old
6651 authorities. V1 authorities should set "HSAuthoritativeDir 1"
6652 to continue being hidden service authorities too.
6653 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
6654 - Make TrackExitHosts case-insensitive, and fix the behavior of
6655 ".suffix" TrackExitHosts items to avoid matching in the middle of
6657 - New DirPort behavior: if you have your dirport set, you download
6658 descriptors aggressively like a directory mirror, whether or not
6662 - Create a new file ReleaseNotes which was the old ChangeLog. The
6663 new ChangeLog file now includes the notes for all development
6665 - Add a new address-spec.txt document to describe our special-case
6666 addresses: .exit, .onion, and .noconnnect.
6667 - Fork the v1 directory protocol into its own spec document,
6668 and mark dir-spec.txt as the currently correct (v2) spec.
6670 o Packaging, porting, and contrib
6671 - "tor --verify-config" now exits with -1(255) or 0 depending on
6672 whether the config options are bad or good.
6673 - The Debian package now uses --verify-config when (re)starting,
6674 to distinguish configuration errors from other errors.
6675 - Adapt a patch from goodell to let the contrib/exitlist script
6676 take arguments rather than require direct editing.
6677 - Prevent the contrib/exitlist script from printing the same
6678 result more than once.
6679 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
6680 - In the hidden service example in torrc.sample, stop recommending
6681 esoteric and discouraged hidden service options.
6682 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
6683 values before failing, and always enables eventdns.
6684 - Try to detect Windows correctly when cross-compiling.
6685 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
6686 Try to fix this in configure.in by checking for most functions
6687 before we check for libevent.
6688 - Update RPMs to require libevent 1.2.
6689 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6690 or later. Log when we are doing this, so we can diagnose it when
6691 it fails. (Also, recommend libevent 1.1b for kqueue and
6692 win32 methods; deprecate libevent 1.0b harder; make libevent
6693 recommendation system saner.)
6694 - Build with recent (1.3+) libevents on platforms that do not
6695 define the nonstandard types "u_int8_t" and friends.
6696 - Remove architecture from OS X builds. The official builds are
6697 now universal binaries.
6698 - Run correctly on OS X platforms with case-sensitive filesystems.
6699 - Correctly set maximum connection limit on Cygwin. (This time
6701 - Start compiling on MinGW on Windows (patches from Mike Chiussi
6703 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6704 - Finally fix the openssl warnings from newer gccs that believe that
6705 ignoring a return value is okay, but casting a return value and
6706 then ignoring it is a sign of madness.
6707 - On architectures where sizeof(int)>4, still clamp declarable
6708 bandwidth to INT32_MAX.
6710 o Minor features, controller:
6711 - Warn the user when an application uses the obsolete binary v0
6712 control protocol. We're planning to remove support for it during
6713 the next development series, so it's good to give people some
6715 - Add STREAM_BW events to report per-entry-stream bandwidth
6716 use. (Patch from Robert Hogan.)
6717 - Rate-limit SIGNEWNYM signals in response to controllers that
6718 impolitely generate them for every single stream. (Patch from
6719 mwenge; closes bug 394.)
6720 - Add a REMAP status to stream events to note that a stream's
6721 address has changed because of a cached address or a MapAddress
6723 - Make REMAP stream events have a SOURCE (cache or exit), and
6724 make them generated in every case where we get a successful
6725 connected or resolved cell.
6726 - Track reasons for OR connection failure; make these reasons
6727 available via the controller interface. (Patch from Mike Perry.)
6728 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
6729 can learn when clients are sending malformed hostnames to Tor.
6730 - Specify and implement some of the controller status events.
6731 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
6732 - Reimplement GETINFO so that info/names stays in sync with the
6734 - Implement "GETINFO fingerprint".
6735 - Implement "SETEVENTS GUARD" so controllers can get updates on
6736 entry guard status as it changes.
6737 - Make all connections to addresses of the form ".noconnect"
6738 immediately get closed. This lets application/controller combos
6739 successfully test whether they're talking to the same Tor by
6740 watching for STREAM events.
6741 - Add a REASON field to CIRC events; for backward compatibility, this
6742 field is sent only to controllers that have enabled the extended
6743 event format. Also, add additional reason codes to explain why
6744 a given circuit has been destroyed or truncated. (Patches from
6746 - Add a REMOTE_REASON field to extended CIRC events to tell the
6747 controller why a remote OR told us to close a circuit.
6748 - Stream events also now have REASON and REMOTE_REASON fields,
6749 working much like those for circuit events.
6750 - There's now a GETINFO ns/... field so that controllers can ask Tor
6751 about the current status of a router.
6752 - A new event type "NS" to inform a controller when our opinion of
6753 a router's status has changed.
6754 - Add a GETINFO events/names and GETINFO features/names so controllers
6755 can tell which events and features are supported.
6756 - A new CLEARDNSCACHE signal to allow controllers to clear the
6757 client-side DNS cache without expiring circuits.
6758 - Fix CIRC controller events so that controllers can learn the
6759 identity digests of non-Named servers used in circuit paths.
6760 - Let controllers ask for more useful identifiers for servers. Instead
6761 of learning identity digests for un-Named servers and nicknames
6762 for Named servers, the new identifiers include digest, nickname,
6763 and indication of Named status. Off by default; see control-spec.txt
6764 for more information.
6765 - Add a "getinfo address" controller command so it can display Tor's
6766 best guess to the user.
6767 - New controller event to alert the controller when our server
6768 descriptor has changed.
6769 - Give more meaningful errors on controller authentication failure.
6770 - Export the default exit policy via the control port, so controllers
6771 don't need to guess what it is / will be later.
6773 o Minor bugfixes, controller:
6774 - When creating a circuit via the controller, send a 'launched'
6775 event when we're done, so we follow the spec better.
6776 - Correct the control spec to match how the code actually responds
6777 to 'getinfo addr-mappings/*'. Reported by daejees.
6778 - The control spec described a GUARDS event, but the code
6779 implemented a GUARD event. Standardize on GUARD, but let people
6780 ask for GUARDS too. Reported by daejees.
6781 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
6782 clear the corresponding on_circuit variable, and remember later
6783 that we don't need to send a redundant CLOSED event. (Resolves part
6785 - Report events where a resolve succeeded or where we got a socks
6786 protocol error correctly, rather than calling both of them
6788 - Change reported stream target addresses to IP consistently when
6789 we finally get the IP from an exit node.
6790 - Send log messages to the controller even if they happen to be very
6792 - Flush ERR-level controller status events just like we currently
6793 flush ERR-level log events, so that a Tor shutdown doesn't prevent
6794 the controller from learning about current events.
6795 - Report the circuit number correctly in STREAM CLOSED events. Bug
6796 reported by Mike Perry.
6797 - Do not report bizarre values for results of accounting GETINFOs
6798 when the last second's write or read exceeds the allotted bandwidth.
6799 - Report "unrecognized key" rather than an empty string when the
6800 controller tries to fetch a networkstatus that doesn't exist.
6801 - When the controller does a "GETINFO network-status", tell it
6802 about even those routers whose descriptors are very old, and use
6803 long nicknames where appropriate.
6804 - Fix handling of verbose nicknames with ORCONN controller events:
6805 make them show up exactly when requested, rather than exactly when
6807 - Controller signals now work on non-Unix platforms that don't define
6808 SIGUSR1 and SIGUSR2 the way we expect.
6809 - Respond to SIGNAL command before we execute the signal, in case
6810 the signal shuts us down. Suggested by Karsten Loesing.
6811 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6813 o Minor features, code performance:
6814 - Major performance improvement on inserting descriptors: change
6815 algorithm from O(n^2) to O(n).
6816 - Do not rotate onion key immediately after setting it for the first
6818 - Call router_have_min_dir_info half as often. (This is showing up in
6819 some profiles, but not others.)
6820 - When using GCC, make log_debug never get called at all, and its
6821 arguments never get evaluated, when no debug logs are configured.
6822 (This is showing up in some profiles, but not others.)
6823 - Statistics dumped by -USR2 now include a breakdown of public key
6824 operations, for profiling.
6825 - Make the common memory allocation path faster on machines where
6826 malloc(0) returns a pointer.
6827 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6828 split connection_t into edge, or, dir, control, and base structs.
6829 These will save quite a bit of memory on busy servers, and they'll
6830 also help us track down bugs in the code and bugs in the spec.
6831 - Use OpenSSL's AES implementation on platforms where it's faster.
6832 This could save us as much as 10% CPU usage.
6834 o Minor features, descriptors and descriptor handling:
6835 - Avoid duplicate entries on MyFamily line in server descriptor.
6836 - When Tor receives a router descriptor that it asked for, but
6837 no longer wants (because it has received fresh networkstatuses
6838 in the meantime), do not warn the user. Cache the descriptor if
6839 we're a cache; drop it if we aren't.
6840 - Servers no longer ever list themselves in their "family" line,
6841 even if configured to do so. This makes it easier to configure
6842 family lists conveniently.
6844 o Minor fixes, confusing/misleading log messages:
6845 - Display correct results when reporting which versions are
6846 recommended, and how recommended they are. (Resolves bug 383.)
6847 - Inform the server operator when we decide not to advertise a
6848 DirPort due to AccountingMax enabled or a low BandwidthRate.
6849 - Only include function names in log messages for info/debug messages.
6850 For notice/warn/err, the content of the message should be clear on
6851 its own, and printing the function name only confuses users.
6852 - Remove even more protocol-related warnings from Tor server logs,
6853 such as bad TLS handshakes and malformed begin cells.
6854 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6855 when the IP address is mapped through MapAddress to a hostname.
6856 - Fix misleading log messages: an entry guard that is "unlisted",
6857 as well as not known to be "down" (because we've never heard
6858 of it), is not therefore "up".
6860 o Minor fixes, old/obsolete behavior:
6861 - Start assuming we can use a create_fast cell if we don't know
6862 what version a router is running.
6863 - We no longer look for identity and onion keys in "identity.key" and
6864 "onion.key" -- these were replaced by secret_id_key and
6865 secret_onion_key in 0.0.8pre1.
6866 - We no longer require unrecognized directory entries to be
6868 - Drop compatibility with obsolete Tors that permit create cells
6869 to have the wrong circ_id_type.
6870 - Remove code to special-case "-cvs" ending, since it has not
6871 actually mattered since 0.0.9.
6872 - Don't re-write the fingerprint file every restart, unless it has
6875 o Minor fixes, misc client-side behavior:
6876 - Always remove expired routers and networkstatus docs before checking
6877 whether we have enough information to build circuits. (Fixes
6879 - When computing clock skew from directory HTTP headers, consider what
6880 time it was when we finished asking for the directory, not what
6882 - Make our socks5 handling more robust to broken socks clients:
6883 throw out everything waiting on the buffer in between socks
6884 handshake phases, since they can't possibly (so the theory
6885 goes) have predicted what we plan to respond to them.
6886 - Expire socks connections if they spend too long waiting for the
6887 handshake to finish. Previously we would let them sit around for
6888 days, if the connecting application didn't close them either.
6889 - And if the socks handshake hasn't started, don't send a
6890 "DNS resolve socks failed" handshake reply; just close it.
6891 - If the user asks to use invalid exit nodes, be willing to use
6893 - Track unreachable entry guards correctly: don't conflate
6894 'unreachable by us right now' with 'listed as down by the directory
6895 authorities'. With the old code, if a guard was unreachable by us
6896 but listed as running, it would clog our guard list forever.
6897 - Behave correctly in case we ever have a network with more than
6898 2GB/s total advertised capacity.
6899 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6900 - Fix a memory leak when we ask for "all" networkstatuses and we
6901 get one we don't recognize.
6904 Changes in version 0.1.1.26 - 2006-12-14
6905 o Security bugfixes:
6906 - Stop sending the HttpProxyAuthenticator string to directory
6907 servers when directory connections are tunnelled through Tor.
6908 - Clients no longer store bandwidth history in the state file.
6909 - Do not log introduction points for hidden services if SafeLogging
6913 - Fix an assert failure when a directory authority sets
6914 AuthDirRejectUnlisted and then receives a descriptor from an
6915 unlisted router (reported by seeess).
6918 Changes in version 0.1.1.25 - 2006-11-04
6920 - When a client asks us to resolve (rather than connect to)
6921 an address, and we have a cached answer, give them the cached
6922 answer. Previously, we would give them no answer at all.
6923 - We were building exactly the wrong circuits when we predict
6924 hidden service requirements, meaning Tor would have to build all
6925 its circuits on demand.
6926 - If none of our live entry guards have a high uptime, but we
6927 require a guard with a high uptime, try adding a new guard before
6928 we give up on the requirement. This patch should make long-lived
6929 connections more stable on average.
6930 - When testing reachability of our DirPort, don't launch new
6931 tests when there's already one in progress -- unreachable
6932 servers were stacking up dozens of testing streams.
6934 o Security bugfixes:
6935 - When the user sends a NEWNYM signal, clear the client-side DNS
6936 cache too. Otherwise we continue to act on previous information.
6939 - Avoid a memory corruption bug when creating a hash table for
6941 - Avoid possibility of controller-triggered crash when misusing
6942 certain commands from a v0 controller on platforms that do not
6943 handle printf("%s",NULL) gracefully.
6944 - Avoid infinite loop on unexpected controller input.
6945 - Don't log spurious warnings when we see a circuit close reason we
6946 don't recognize; it's probably just from a newer version of Tor.
6947 - Add Vidalia to the OS X uninstaller script, so when we uninstall
6948 Tor/Privoxy we also uninstall Vidalia.
6951 Changes in version 0.1.1.24 - 2006-09-29
6953 - Allow really slow clients to not hang up five minutes into their
6954 directory downloads (suggested by Adam J. Richter).
6955 - Fix major performance regression from 0.1.0.x: instead of checking
6956 whether we have enough directory information every time we want to
6957 do something, only check when the directory information has changed.
6958 This should improve client CPU usage by 25-50%.
6959 - Don't crash if, after a server has been running for a while,
6960 it can't resolve its hostname.
6961 - When a client asks us to resolve (not connect to) an address,
6962 and we have a cached answer, give them the cached answer.
6963 Previously, we would give them no answer at all.
6966 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6967 - Don't crash when the controller receives a third argument to an
6968 "extendcircuit" request.
6969 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6970 response; fix error code when "getinfo dir/status/" fails.
6971 - Fix configure.in to not produce broken configure files with
6972 more recent versions of autoconf. Thanks to Clint for his auto*
6974 - Fix security bug on NetBSD that could allow someone to force
6975 uninitialized RAM to be sent to a server's DNS resolver. This
6976 only affects NetBSD and other platforms that do not bounds-check
6978 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
6979 methods: these are known to be buggy.
6980 - If we're a directory mirror and we ask for "all" network status
6981 documents, we would discard status documents from authorities
6985 Changes in version 0.1.1.23 - 2006-07-30
6987 - Fast Tor servers, especially exit nodes, were triggering asserts
6988 due to a bug in handling the list of pending DNS resolves. Some
6989 bugs still remain here; we're hunting them.
6990 - Entry guards could crash clients by sending unexpected input.
6991 - More fixes on reachability testing: if you find yourself reachable,
6992 then don't ever make any client requests (so you stop predicting
6993 circuits), then hup or have your clock jump, then later your IP
6994 changes, you won't think circuits are working, so you won't try to
6995 test reachability, so you won't publish.
6998 - Avoid a crash if the controller does a resetconf firewallports
6999 and then a setconf fascistfirewall=1.
7000 - Avoid an integer underflow when the dir authority decides whether
7001 a router is stable: we might wrongly label it stable, and compute
7002 a slightly wrong median stability, when a descriptor is published
7004 - Fix a place where we might trigger an assert if we can't build our
7005 own server descriptor yet.
7008 Changes in version 0.1.1.22 - 2006-07-05
7010 - Fix a big bug that was causing servers to not find themselves
7011 reachable if they changed IP addresses. Since only 0.1.1.22+
7012 servers can do reachability testing correctly, now we automatically
7013 make sure to test via one of these.
7014 - Fix to allow clients and mirrors to learn directory info from
7015 descriptor downloads that get cut off partway through.
7016 - Directory authorities had a bug in deciding if a newly published
7017 descriptor was novel enough to make everybody want a copy -- a few
7018 servers seem to be publishing new descriptors many times a minute.
7020 - Fix a rare bug that was causing some servers to complain about
7021 "closing wedged cpuworkers" and skip some circuit create requests.
7022 - Make the Exit flag in directory status documents actually work.
7025 Changes in version 0.1.1.21 - 2006-06-10
7026 o Crash and assert fixes from 0.1.1.20:
7027 - Fix a rare crash on Tor servers that have enabled hibernation.
7028 - Fix a seg fault on startup for Tor networks that use only one
7029 directory authority.
7030 - Fix an assert from a race condition that occurs on Tor servers
7031 while exiting, where various threads are trying to log that they're
7032 exiting, and delete the logs, at the same time.
7033 - Make our unit tests pass again on certain obscure platforms.
7036 - Add support for building SUSE RPM packages.
7037 - Speed up initial bootstrapping for clients: if we are making our
7038 first ever connection to any entry guard, then don't mark it down
7040 - When only one Tor server in the network is labelled as a guard,
7041 and we've already picked him, we would cycle endlessly picking him
7042 again, being unhappy about it, etc. Now we specifically exclude
7043 current guards when picking a new guard.
7044 - Servers send create cells more reliably after the TLS connection
7045 is established: we were sometimes forgetting to send half of them
7046 when we had more than one pending.
7047 - If we get a create cell that asks us to extend somewhere, but the
7048 Tor server there doesn't match the expected digest, we now send
7049 a destroy cell back, rather than silently doing nothing.
7050 - Make options->RedirectExit work again.
7051 - Make cookie authentication for the controller work again.
7052 - Stop being picky about unusual characters in the arguments to
7053 mapaddress. It's none of our business.
7054 - Add a new config option "TestVia" that lets you specify preferred
7055 middle hops to use for test circuits. Perhaps this will let me
7056 debug the reachability problems better.
7058 o Log / documentation fixes:
7059 - If we're a server and some peer has a broken TLS certificate, don't
7060 log about it unless ProtocolWarnings is set, i.e., we want to hear
7061 about protocol violations by others.
7062 - Fix spelling of VirtualAddrNetwork in man page.
7063 - Add a better explanation at the top of the autogenerated torrc file
7064 about what happened to our old torrc.
7067 Changes in version 0.1.1.20 - 2006-05-23
7068 o Crash and assert fixes from 0.1.0.17:
7069 - Fix assert bug in close_logs() on exit: when we close and delete
7070 logs, remove them all from the global "logfiles" list.
7071 - Fix an assert error when we're out of space in the connection_list
7072 and we try to post a hidden service descriptor (reported by Peter
7074 - Fix a rare assert error when we've tried all intro points for
7075 a hidden service and we try fetching the service descriptor again:
7076 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
7077 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
7078 out and refuse the setconf if it would fail.
7079 - If you specify a relative torrc path and you set RunAsDaemon in
7080 your torrc, then it chdir()'s to the new directory. If you then
7081 HUP, it tries to load the new torrc location, fails, and exits.
7082 The fix: no longer allow a relative path to torrc when using -f.
7083 - Check for integer overflows in more places, when adding elements
7084 to smartlists. This could possibly prevent a buffer overflow
7085 on malicious huge inputs.
7087 o Security fixes, major:
7088 - When we're printing strings from the network, don't try to print
7089 non-printable characters. Now we're safer against shell escape
7090 sequence exploits, and also against attacks to fool users into
7091 misreading their logs.
7092 - Implement entry guards: automatically choose a handful of entry
7093 nodes and stick with them for all circuits. Only pick new guards
7094 when the ones you have are unsuitable, and if the old guards
7095 become suitable again, switch back. This will increase security
7096 dramatically against certain end-point attacks. The EntryNodes
7097 config option now provides some hints about which entry guards you
7098 want to use most; and StrictEntryNodes means to only use those.
7099 Fixes CVE-2006-0414.
7100 - Implement exit enclaves: if we know an IP address for the
7101 destination, and there's a running Tor server at that address
7102 which allows exit to the destination, then extend the circuit to
7103 that exit first. This provides end-to-end encryption and end-to-end
7104 authentication. Also, if the user wants a .exit address or enclave,
7105 use 4 hops rather than 3, and cannibalize a general circ for it
7107 - Obey our firewall options more faithfully:
7108 . If we can't get to a dirserver directly, try going via Tor.
7109 . Don't ever try to connect (as a client) to a place our
7110 firewall options forbid.
7111 . If we specify a proxy and also firewall options, obey the
7112 firewall options even when we're using the proxy: some proxies
7113 can only proxy to certain destinations.
7114 - Make clients regenerate their keys when their IP address changes.
7115 - For the OS X package's modified privoxy config file, comment
7116 out the "logfile" line so we don't log everything passed
7118 - Our TLS handshakes were generating a single public/private
7119 keypair for the TLS context, rather than making a new one for
7120 each new connection. Oops. (But we were still rotating them
7121 periodically, so it's not so bad.)
7122 - When we were cannibalizing a circuit with a particular exit
7123 node in mind, we weren't checking to see if that exit node was
7124 already present earlier in the circuit. Now we are.
7125 - Require server descriptors to list IPv4 addresses -- hostnames
7126 are no longer allowed. This also fixes potential vulnerabilities
7127 to servers providing hostnames as their address and then
7128 preferentially resolving them so they can partition users.
7129 - Our logic to decide if the OR we connected to was the right guy
7130 was brittle and maybe open to a mitm for invalid routers.
7132 o Security fixes, minor:
7133 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
7134 Ian Goldberg can prove things about our handshake protocol more
7136 - Make directory authorities generate a separate "guard" flag to
7137 mean "would make a good entry guard". Clients now honor the
7138 is_guard flag rather than looking at is_fast or is_stable.
7139 - Try to list MyFamily elements by key, not by nickname, and warn
7140 if we've not heard of a server.
7141 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7142 OpenSSL. Also, reseed our entropy every hour, not just at
7143 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
7144 - Refuse server descriptors where the fingerprint line doesn't match
7145 the included identity key. Tor doesn't care, but other apps (and
7146 humans) might actually be trusting the fingerprint line.
7147 - We used to kill the circuit when we receive a relay command we
7148 don't recognize. Now we just drop that cell.
7149 - Fix a bug found by Lasse Overlier: when we were making internal
7150 circuits (intended to be cannibalized later for rendezvous and
7151 introduction circuits), we were picking them so that they had
7152 useful exit nodes. There was no need for this, and it actually
7153 aids some statistical attacks.
7154 - Start treating internal circuits and exit circuits separately.
7155 It's important to keep them separate because internal circuits
7156 have their last hops picked like middle hops, rather than like
7157 exit hops. So exiting on them will break the user's expectations.
7158 - Fix a possible way to DoS dirservers.
7159 - When the client asked for a rendezvous port that the hidden
7160 service didn't want to provide, we were sending an IP address
7161 back along with the end cell. Fortunately, it was zero. But stop
7164 o Packaging improvements:
7165 - Implement --with-libevent-dir option to ./configure. Improve
7166 search techniques to find libevent, and use those for openssl too.
7167 - Fix a couple of bugs in OpenSSL detection. Deal better when
7168 there are multiple SSLs installed with different versions.
7169 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
7170 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
7172 - Make unit tests (and other invocations that aren't the real Tor)
7173 run without launching listeners, creating subdirectories, and so on.
7174 - The OS X installer was adding a symlink for tor_resolve but
7175 the binary was called tor-resolve (reported by Thomas Hardly).
7176 - Now we can target arch and OS in rpm builds (contributed by
7177 Phobos). Also make the resulting dist-rpm filename match the
7179 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
7180 if you log to syslog and want something other than LOG_DAEMON.
7181 - Fix the torify (tsocks) config file to not use Tor for localhost
7183 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7184 tor-doc-server.html, and stylesheet.css in the tarball.
7185 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
7186 They are useless now.
7187 - Add Peter Palfrader's contributed check-tor script. It lets you
7188 easily check whether a given server (referenced by nickname)
7189 is reachable by you.
7190 - Add BSD-style contributed startup script "rc.subr" from Peter
7193 o Directory improvements -- new directory protocol:
7194 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
7195 - Authorities and caches publish individual descriptors (by
7196 digest, by fingerprint, by "all", and by "tell me yours").
7197 - Clients don't download or use the old directory anymore. Now they
7198 download network-statuses from the directory authorities, and
7199 fetch individual server descriptors as needed from mirrors.
7200 - Clients don't download descriptors of non-running servers.
7201 - Download descriptors by digest, not by fingerprint. Caches try to
7202 download all listed digests from authorities; clients try to
7203 download "best" digests from caches. This avoids partitioning
7204 and isolating attacks better.
7205 - Only upload a new server descriptor when options change, 18
7206 hours have passed, uptime is reset, or bandwidth changes a lot.
7207 - Directory authorities silently throw away new descriptors that
7208 haven't changed much if the timestamps are similar. We do this to
7209 tolerate older Tor servers that upload a new descriptor every 15
7210 minutes. (It seemed like a good idea at the time.)
7211 - Clients choose directory servers from the network status lists,
7212 not from their internal list of router descriptors. Now they can
7213 go to caches directly rather than needing to go to authorities
7214 to bootstrap the first set of descriptors.
7215 - When picking a random directory, prefer non-authorities if any
7217 - Add a new flag to network-status indicating whether the server
7218 can answer v2 directory requests too.
7219 - Directory mirrors now cache up to 16 unrecognized network-status
7220 docs, so new directory authorities will be cached too.
7221 - Stop parsing, storing, or using running-routers output (but
7222 mirrors still cache and serve it).
7223 - Clients consider a threshold of "versioning" directory authorities
7224 before deciding whether to warn the user that he's obsolete.
7225 - Authorities publish separate sorted lists of recommended versions
7226 for clients and for servers.
7227 - Change DirServers config line to note which dirs are v1 authorities.
7228 - Put nicknames on the DirServer line, so we can refer to them
7229 without requiring all our users to memorize their IP addresses.
7230 - Remove option when getting directory cache to see whether they
7231 support running-routers; they all do now. Replace it with one
7232 to see whether caches support v2 stuff.
7233 - Stop listing down or invalid nodes in the v1 directory. This
7234 reduces its bulk by about 1/3, and reduces load on mirrors.
7235 - Mirrors no longer cache the v1 directory as often.
7236 - If we as a directory mirror don't know of any v1 directory
7237 authorities, then don't try to cache any v1 directories.
7239 o Other directory improvements:
7240 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
7241 fifth authoritative directory servers.
7242 - Directory authorities no longer require an open connection from
7243 a server to consider him "reachable". We need this change because
7244 when we add new directory authorities, old servers won't know not
7246 - Dir authorities now do their own external reachability testing
7247 of each server, and only list as running the ones they found to
7248 be reachable. We also send back warnings to the server's logs if
7249 it uploads a descriptor that we already believe is unreachable.
7250 - Spread the directory authorities' reachability testing over the
7251 entire testing interval, so we don't try to do 500 TLS's at once
7253 - Make the "stable" router flag in network-status be the median of
7254 the uptimes of running valid servers, and make clients pay
7255 attention to the network-status flags. Thus the cutoff adapts
7256 to the stability of the network as a whole, making IRC, IM, etc
7257 connections more reliable.
7258 - Make the v2 dir's "Fast" flag based on relative capacity, just
7259 like "Stable" is based on median uptime. Name everything in the
7260 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
7261 - Retry directory requests if we fail to get an answer we like
7262 from a given dirserver (we were retrying before, but only if
7263 we fail to connect).
7264 - Return a robots.txt on our dirport to discourage google indexing.
7266 o Controller protocol improvements:
7267 - Revised controller protocol (version 1) that uses ascii rather
7268 than binary: tor/doc/control-spec.txt. Add supporting libraries
7269 in python and java and c# so you can use the controller from your
7270 applications without caring how our protocol works.
7271 - Allow the DEBUG controller event to work again. Mark certain log
7272 entries as "don't tell this to controllers", so we avoid cycles.
7273 - New controller function "getinfo accounting", to ask how
7274 many bytes we've used in this time period.
7275 - Add a "resetconf" command so you can set config options like
7276 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7277 a config option in the torrc with no value, then it clears it
7278 entirely (rather than setting it to its default).
7279 - Add a "getinfo config-file" to tell us where torrc is. Also
7280 expose guard nodes, config options/names.
7281 - Add a "quit" command (when when using the controller manually).
7282 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
7283 stop using any currently-dirty circuits for new streams, so we
7284 don't link new actions to old actions. This also occurs on HUP
7286 - If we would close a stream early (e.g. it asks for a .exit that
7287 we know would refuse it) but the LeaveStreamsUnattached config
7288 option is set by the controller, then don't close it.
7289 - Add a new controller event type "authdir_newdescs" that allows
7290 controllers to get all server descriptors that were uploaded to
7291 a router in its role as directory authority.
7292 - New controller option "getinfo desc/all-recent" to fetch the
7293 latest server descriptor for every router that Tor knows about.
7294 - Fix the controller's "attachstream 0" command to treat conn like
7295 it just connected, doing address remapping, handling .exit and
7296 .onion idioms, and so on. Now we're more uniform in making sure
7297 that the controller hears about new and closing connections.
7298 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
7299 the controller. Also, rotate dns and cpu workers if the controller
7300 changes options that will affect them; and initialize the dns
7301 worker cache tree whether or not we start out as a server.
7302 - Add a new circuit purpose 'controller' to let the controller ask
7303 for a circuit that Tor won't try to use. Extend the "extendcircuit"
7304 controller command to let you specify the purpose if you're starting
7305 a new circuit. Add a new "setcircuitpurpose" controller command to
7306 let you change a circuit's purpose after it's been created.
7307 - Let the controller ask for "getinfo dir/server/foo" so it can ask
7308 directly rather than connecting to the dir port. "getinfo
7309 dir/status/foo" also works, but currently only if your DirPort
7311 - Let the controller tell us about certain router descriptors
7312 that it doesn't want Tor to use in circuits. Implement
7313 "setrouterpurpose" and modify "+postdescriptor" to do this.
7314 - If the controller's *setconf commands fail, collect an error
7315 message in a string and hand it back to the controller -- don't
7316 just tell them to go read their logs.
7318 o Scalability, resource management, and performance:
7319 - Fix a major load balance bug: we were round-robin reading in 16 KB
7320 chunks, and servers with bandwidthrate of 20 KB, while downloading
7321 a 600 KB directory, would starve their other connections. Now we
7322 try to be a bit more fair.
7323 - Be more conservative about whether to advertise our DirPort.
7324 The main change is to not advertise if we're running at capacity
7325 and either a) we could hibernate ever or b) our capacity is low
7326 and we're using a default DirPort.
7327 - We weren't cannibalizing circuits correctly for
7328 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7329 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7330 build those from scratch. This should make hidden services faster.
7331 - Predict required circuits better, with an eye toward making hidden
7332 services faster on the service end.
7333 - Compress exit policies even more: look for duplicate lines and
7335 - Generate 18.0.0.0/8 address policy format in descs when we can;
7336 warn when the mask is not reducible to a bit-prefix.
7337 - There used to be two ways to specify your listening ports in a
7338 server descriptor: on the "router" line and with a separate "ports"
7339 line. Remove support for the "ports" line.
7340 - Reduce memory requirements in our structs by changing the order
7341 of fields. Replace balanced trees with hash tables. Inline
7342 bottleneck smartlist functions. Add a "Map from digest to void*"
7343 abstraction so we can do less hex encoding/decoding, and use it
7344 in router_get_by_digest(). Many other CPU and memory improvements.
7345 - Allow tor_gzip_uncompress to extract as much as possible from
7346 truncated compressed data. Try to extract as many
7347 descriptors as possible from truncated http responses (when
7348 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
7349 - Make circ->onionskin a pointer, not a static array. moria2 was using
7350 125000 circuit_t's after it had been up for a few weeks, which
7351 translates to 20+ megs of wasted space.
7352 - The private half of our EDH handshake keys are now chosen out
7353 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7354 - Stop doing the complex voodoo overkill checking for insecure
7355 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
7356 - Do round-robin writes for TLS of at most 16 kB per write. This
7357 might be more fair on loaded Tor servers.
7358 - Do not use unaligned memory access on alpha, mips, or mipsel.
7359 It *works*, but is very slow, so we treat them as if it doesn't.
7361 o Other bugfixes and improvements:
7362 - Start storing useful information to $DATADIR/state, so we can
7363 remember things across invocations of Tor. Retain unrecognized
7364 lines so we can be forward-compatible, and write a TorVersion line
7365 so we can be backward-compatible.
7366 - If ORPort is set, Address is not explicitly set, and our hostname
7367 resolves to a private IP address, try to use an interface address
7368 if it has a public address. Now Windows machines that think of
7369 themselves as localhost can guess their address.
7370 - Regenerate our local descriptor if it's dirty and we try to use
7371 it locally (e.g. if it changes during reachability detection).
7372 This was causing some Tor servers to keep publishing the same
7373 initial descriptor forever.
7374 - Tor servers with dynamic IP addresses were needing to wait 18
7375 hours before they could start doing reachability testing using
7376 the new IP address and ports. This is because they were using
7377 the internal descriptor to learn what to test, yet they were only
7378 rebuilding the descriptor once they decided they were reachable.
7379 - It turns out we couldn't bootstrap a network since we added
7380 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7381 has never gone down. Add an AssumeReachable config option to let
7382 servers and authorities bootstrap. When we're trying to build a
7383 high-uptime or high-bandwidth circuit but there aren't enough
7384 suitable servers, try being less picky rather than simply failing.
7385 - Newly bootstrapped Tor networks couldn't establish hidden service
7386 circuits until they had nodes with high uptime. Be more tolerant.
7387 - Really busy servers were keeping enough circuits open on stable
7388 connections that they were wrapping around the circuit_id
7389 space. (It's only two bytes.) This exposed a bug where we would
7390 feel free to reuse a circuit_id even if it still exists but has
7391 been marked for close. Try to fix this bug. Some bug remains.
7392 - When we fail to bind or listen on an incoming or outgoing
7393 socket, we now close it before refusing, rather than just
7394 leaking it. (Thanks to Peter Palfrader for finding.)
7395 - Fix a file descriptor leak in start_daemon().
7396 - On Windows, you can't always reopen a port right after you've
7397 closed it. So change retry_listeners() to only close and re-open
7398 ports that have changed.
7399 - Workaround a problem with some http proxies that refuse GET
7400 requests that specify "Content-Length: 0". Reported by Adrian.
7401 - Recover better from TCP connections to Tor servers that are
7402 broken but don't tell you (it happens!); and rotate TLS
7403 connections once a week.
7404 - Fix a scary-looking but apparently harmless bug where circuits
7405 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
7406 servers, and never switch to state CIRCUIT_STATE_OPEN.
7407 - Check for even more Windows version flags when writing the platform
7408 string in server descriptors, and note any we don't recognize.
7409 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
7410 get a better idea of why their circuits failed. Not used yet.
7411 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7412 We don't use them yet, but maybe one day our DNS resolver will be
7413 able to discover them.
7414 - Let people type "tor --install" as well as "tor -install" when they
7415 want to make it an NT service.
7416 - Looks like we were never delivering deflated (i.e. compressed)
7417 running-routers lists, even when asked. Oops.
7418 - We were leaking some memory every time the client changed IPs.
7419 - Clean up more of the OpenSSL memory when exiting, so we can detect
7420 memory leaks better.
7421 - Never call free() on tor_malloc()d memory. This will help us
7422 use dmalloc to detect memory leaks.
7423 - Some Tor servers process billions of cells per day. These
7424 statistics are now uint64_t's.
7425 - Check [X-]Forwarded-For headers in HTTP requests when generating
7426 log messages. This lets people run dirservers (and caches) behind
7427 Apache but still know which IP addresses are causing warnings.
7428 - Fix minor integer overflow in calculating when we expect to use up
7429 our bandwidth allocation before hibernating.
7430 - Lower the minimum required number of file descriptors to 1000,
7431 so we can have some overhead for Valgrind on Linux, where the
7432 default ulimit -n is 1024.
7433 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
7434 and its existence is confusing some users.
7436 o Config option fixes:
7437 - Add a new config option ExitPolicyRejectPrivate which defaults
7438 to on. Now all exit policies will begin with rejecting private
7439 addresses, unless the server operator explicitly turns it off.
7440 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
7441 - Add new ReachableORAddresses and ReachableDirAddresses options
7442 that understand address policies. FascistFirewall is now a synonym
7443 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
7444 - Start calling it FooListenAddress rather than FooBindAddress,
7445 since few of our users know what it means to bind an address
7447 - If the user gave Tor an odd number of command-line arguments,
7448 we were silently ignoring the last one. Now we complain and fail.
7449 This wins the oldest-bug prize -- this bug has been present since
7450 November 2002, as released in Tor 0.0.0.
7451 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7452 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7453 it would silently ignore the 6668.
7454 - If we get a linelist or linelist_s config option from the torrc,
7455 e.g. ExitPolicy, and it has no value, warn and skip rather than
7456 silently resetting it to its default.
7457 - Setconf was appending items to linelists, not clearing them.
7458 - Add MyFamily to torrc.sample in the server section, so operators
7459 will be more likely to learn that it exists.
7460 - Make ContactInfo mandatory for authoritative directory servers.
7461 - MaxConn has been obsolete for a while now. Document the ConnLimit
7462 config option, which is a *minimum* number of file descriptors
7463 that must be available else Tor refuses to start.
7464 - Get rid of IgnoreVersion undocumented config option, and make us
7465 only warn, never exit, when we're running an obsolete version.
7466 - Make MonthlyAccountingStart config option truly obsolete now.
7467 - Correct the man page entry on TrackHostExitsExpire.
7468 - Let directory authorities start even if they don't specify an
7469 Address config option.
7470 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
7471 reflect the updated flags in our v2 dir protocol.
7473 o Config option features:
7474 - Add a new config option FastFirstHopPK (on by default) so clients
7475 do a trivial crypto handshake for their first hop, since TLS has
7476 already taken care of confidentiality and authentication.
7477 - Let the user set ControlListenAddress in the torrc. This can be
7478 dangerous, but there are some cases (like a secured LAN) where it
7480 - New config options to help controllers: FetchServerDescriptors
7481 and FetchHidServDescriptors for whether to fetch server
7482 info and hidserv info or let the controller do it, and
7483 PublishServerDescriptor and PublishHidServDescriptors.
7484 - Also let the controller set the __AllDirActionsPrivate config
7485 option if you want all directory fetches/publishes to happen via
7486 Tor (it assumes your controller bootstraps your circuits).
7487 - Add "HardwareAccel" config option: support for crypto hardware
7488 accelerators via OpenSSL. Off by default, until we find somebody
7489 smart who can test it for us. (It appears to produce seg faults
7490 in at least some cases.)
7491 - New config option "AuthDirRejectUnlisted" for directory authorities
7492 as a panic button: if we get flooded with unusable servers we can
7493 revert to only listing servers in the approved-routers file.
7494 - Directory authorities can now reject/invalidate by key and IP,
7495 with the config options "AuthDirInvalid" and "AuthDirReject", or
7496 by marking a fingerprint as "!reject" or "!invalid" (as its
7497 nickname) in the approved-routers file. This is useful since
7498 currently we automatically list servers as running and usable
7499 even if we know they're jerks.
7500 - Add a new config option TestSocks so people can see whether their
7501 applications are using socks4, socks4a, socks5-with-ip, or
7502 socks5-with-fqdn. This way they don't have to keep mucking
7503 with tcpdump and wondering if something got cached somewhere.
7504 - Add "private:*" as an alias in configuration for policies. Now
7505 you can simplify your exit policy rather than needing to list
7506 every single internal or nonroutable network space.
7507 - Accept "private:*" in routerdesc exit policies; not generated yet
7508 because older Tors do not understand it.
7509 - Add configuration option "V1AuthoritativeDirectory 1" which
7510 moria1, moria2, and tor26 have set.
7511 - Implement an option, VirtualAddrMask, to set which addresses
7512 get handed out in response to mapaddress requests. This works
7513 around a bug in tsocks where 127.0.0.0/8 is never socksified.
7514 - Add a new config option FetchUselessDescriptors, off by default,
7515 for when you plan to run "exitlist" on your client and you want
7516 to know about even the non-running descriptors.
7517 - SocksTimeout: How long do we let a socks connection wait
7518 unattached before we fail it?
7519 - CircuitBuildTimeout: Cull non-open circuits that were born
7520 at least this many seconds ago.
7521 - CircuitIdleTimeout: Cull open clean circuits that were born
7522 at least this many seconds ago.
7523 - New config option SafeSocks to reject all application connections
7524 using unsafe socks protocols. Defaults to off.
7526 o Improved and clearer log messages:
7527 - Reduce clutter in server logs. We're going to try to make
7528 them actually usable now. New config option ProtocolWarnings that
7529 lets you hear about how _other Tors_ are breaking the protocol. Off
7531 - Divide log messages into logging domains. Once we put some sort
7532 of interface on this, it will let people looking at more verbose
7533 log levels specify the topics they want to hear more about.
7534 - Log server fingerprint on startup, so new server operators don't
7535 have to go hunting around their filesystem for it.
7536 - Provide dire warnings to any users who set DirServer manually;
7537 move it out of torrc.sample and into torrc.complete.
7538 - Make the log message less scary when all the dirservers are
7539 temporarily unreachable.
7540 - When tor_socketpair() fails in Windows, give a reasonable
7541 Windows-style errno back.
7542 - Improve tor_gettimeofday() granularity on windows.
7543 - We were printing the number of idle dns workers incorrectly when
7545 - Handle duplicate lines in approved-routers files without warning.
7546 - We were whining about using socks4 or socks5-with-local-lookup
7547 even when it's an IP address in the "virtual" range we designed
7548 exactly for this case.
7549 - Check for named servers when looking them up by nickname;
7550 warn when we're calling a non-named server by its nickname;
7551 don't warn twice about the same name.
7552 - Downgrade the dirserver log messages when whining about
7554 - Correct "your server is reachable" log entries to indicate that
7555 it was self-testing that told us so.
7556 - If we're trying to be a Tor server and running Windows 95/98/ME
7557 as a server, explain that we'll likely crash.
7558 - Provide a more useful warn message when our onion queue gets full:
7559 the CPU is too slow or the exit policy is too liberal.
7560 - Don't warn when we receive a 503 from a dirserver/cache -- this
7561 will pave the way for them being able to refuse if they're busy.
7562 - When we fail to bind a listener, try to provide a more useful
7563 log message: e.g., "Is Tor already running?"
7564 - Only start testing reachability once we've established a
7565 circuit. This will make startup on dir authorities less noisy.
7566 - Don't try to upload hidden service descriptors until we have
7567 established a circuit.
7568 - Tor didn't warn when it failed to open a log file.
7569 - Warn when listening on a public address for socks. We suspect a
7570 lot of people are setting themselves up as open socks proxies,
7571 and they have no idea that jerks on the Internet are using them,
7572 since they simply proxy the traffic into the Tor network.
7573 - Give a useful message when people run Tor as the wrong user,
7574 rather than telling them to start chowning random directories.
7575 - Fix a harmless bug that was causing Tor servers to log
7576 "Got an end because of misc error, but we're not an AP. Closing."
7577 - Fix wrong log message when you add a "HiddenServiceNodes" config
7578 line without any HiddenServiceDir line (reported by Chris Thomas).
7579 - Directory authorities now stop whining so loudly about bad
7580 descriptors that they fetch from other dirservers. So when there's
7581 a log complaint, it's for sure from a freshly uploaded descriptor.
7582 - When logging via syslog, include the pid whenever we provide
7583 a log entry. Suggested by Todd Fries.
7584 - When we're shutting down and we do something like try to post a
7585 server descriptor or rendezvous descriptor, don't complain that
7586 we seem to be unreachable. Of course we are, we're shutting down.
7587 - Change log line for unreachability to explicitly suggest /etc/hosts
7588 as the culprit. Also make it clearer what IP address and ports we're
7589 testing for reachability.
7590 - Put quotes around user-supplied strings when logging so users are
7591 more likely to realize if they add bad characters (like quotes)
7593 - NT service patch from Matt Edman to improve error messages on Win32.
7596 Changes in version 0.1.0.17 - 2006-02-17
7597 o Crash bugfixes on 0.1.0.x:
7598 - When servers with a non-zero DirPort came out of hibernation,
7599 sometimes they would trigger an assert.
7601 o Other important bugfixes:
7602 - On platforms that don't have getrlimit (like Windows), we were
7603 artificially constraining ourselves to a max of 1024
7604 connections. Now just assume that we can handle as many as 15000
7605 connections. Hopefully this won't cause other problems.
7607 o Backported features:
7608 - When we're a server, a client asks for an old-style directory,
7609 and our write bucket is empty, don't give it to him. This way
7610 small servers can continue to serve the directory *sometimes*,
7611 without getting overloaded.
7612 - Whenever you get a 503 in response to a directory fetch, try
7613 once more. This will become important once servers start sending
7614 503's whenever they feel busy.
7615 - Fetch a new directory every 120 minutes, not every 40 minutes.
7616 Now that we have hundreds of thousands of users running the old
7617 directory algorithm, it's starting to hurt a lot.
7618 - Bump up the period for forcing a hidden service descriptor upload
7619 from 20 minutes to 1 hour.
7622 Changes in version 0.1.0.16 - 2006-01-02
7623 o Crash bugfixes on 0.1.0.x:
7624 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7625 corrupting the heap, losing FDs, or crashing when we need to resize
7626 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7627 - It turns out sparc64 platforms crash on unaligned memory access
7628 too -- so detect and avoid this.
7629 - Handle truncated compressed data correctly (by detecting it and
7631 - Fix possible-but-unlikely free(NULL) in control.c.
7632 - When we were closing connections, there was a rare case that
7633 stomped on memory, triggering seg faults and asserts.
7634 - Avoid potential infinite recursion when building a descriptor. (We
7635 don't know that it ever happened, but better to fix it anyway.)
7636 - We were neglecting to unlink marked circuits from soon-to-close OR
7637 connections, which caused some rare scribbling on freed memory.
7638 - Fix a memory stomping race bug when closing the joining point of two
7639 rendezvous circuits.
7640 - Fix an assert in time parsing found by Steven Murdoch.
7642 o Other bugfixes on 0.1.0.x:
7643 - When we're doing reachability testing, provide more useful log
7644 messages so the operator knows what to expect.
7645 - Do not check whether DirPort is reachable when we are suppressing
7646 advertising it because of hibernation.
7647 - When building with -static or on Solaris, we sometimes needed -ldl.
7648 - One of the dirservers (tor26) changed its IP address.
7649 - When we're deciding whether a stream has enough circuits around
7650 that can handle it, count the freshly dirty ones and not the ones
7651 that are so dirty they won't be able to handle it.
7652 - When we're expiring old circuits, we had a logic error that caused
7653 us to close new rendezvous circuits rather than old ones.
7654 - Give a more helpful log message when you try to change ORPort via
7655 the controller: you should upgrade Tor if you want that to work.
7656 - We were failing to parse Tor versions that start with "Tor ".
7657 - Tolerate faulty streams better: when a stream fails for reason
7658 exitpolicy, stop assuming that the router is lying about his exit
7659 policy. When a stream fails for reason misc, allow it to retry just
7660 as if it was resolvefailed. When a stream has failed three times,
7661 reset its failure count so we can try again and get all three tries.
7664 Changes in version 0.1.0.15 - 2005-09-23
7665 o Bugfixes on 0.1.0.x:
7666 - Reject ports 465 and 587 (spam targets) in default exit policy.
7667 - Don't crash when we don't have any spare file descriptors and we
7668 try to spawn a dns or cpu worker.
7669 - Get rid of IgnoreVersion undocumented config option, and make us
7670 only warn, never exit, when we're running an obsolete version.
7671 - Don't try to print a null string when your server finds itself to
7672 be unreachable and the Address config option is empty.
7673 - Make the numbers in read-history and write-history into uint64s,
7674 so they don't overflow and publish negatives in the descriptor.
7675 - Fix a minor memory leak in smartlist_string_remove().
7676 - We were only allowing ourselves to upload a server descriptor at
7677 most every 20 minutes, even if it changed earlier than that.
7678 - Clean up log entries that pointed to old URLs.
7681 Changes in version 0.1.0.14 - 2005-08-08
7682 o Bugfixes on 0.1.0.x:
7683 - Fix the other half of the bug with crypto handshakes
7685 - Fix an assert trigger if you send a 'signal term' via the
7686 controller when it's listening for 'event info' messages.
7689 Changes in version 0.1.0.13 - 2005-08-04
7690 o Bugfixes on 0.1.0.x:
7691 - Fix a critical bug in the security of our crypto handshakes.
7692 - Fix a size_t underflow in smartlist_join_strings2() that made
7693 it do bad things when you hand it an empty smartlist.
7694 - Fix Windows installer to ship Tor license (thanks to Aphex for
7695 pointing out this oversight) and put a link to the doc directory
7697 - Explicitly set no-unaligned-access for sparc: it turns out the
7698 new gcc's let you compile broken code, but that doesn't make it
7702 Changes in version 0.1.0.12 - 2005-07-18
7703 o New directory servers:
7704 - tor26 has changed IP address.
7706 o Bugfixes on 0.1.0.x:
7707 - Fix a possible double-free in tor_gzip_uncompress().
7708 - When --disable-threads is set, do not search for or link against
7710 - Don't trigger an assert if an authoritative directory server
7711 claims its dirport is 0.
7712 - Fix bug with removing Tor as an NT service: some people were
7713 getting "The service did not return an error." Thanks to Matt
7717 Changes in version 0.1.0.11 - 2005-06-30
7718 o Bugfixes on 0.1.0.x:
7719 - Fix major security bug: servers were disregarding their
7720 exit policies if clients behaved unexpectedly.
7721 - Make OS X init script check for missing argument, so we don't
7722 confuse users who invoke it incorrectly.
7723 - Fix a seg fault in "tor --hash-password foo".
7724 - The MAPADDRESS control command was broken.
7727 Changes in version 0.1.0.10 - 2005-06-14
7729 - Make NT services work and start on startup on Win32 (based on
7730 patch by Matt Edman). See the FAQ entry for details.
7731 - Make 'platform' string in descriptor more accurate for Win32
7732 servers, so it's not just "unknown platform".
7733 - REUSEADDR on normal platforms means you can rebind to the port
7734 right after somebody else has let it go. But REUSEADDR on Win32
7735 means you can bind to the port _even when somebody else already
7736 has it bound_! So, don't do that on Win32.
7737 - Clean up the log messages when starting on Win32 with no config
7739 - Allow seeding the RNG on Win32 even when you're not running as
7740 Administrator. If seeding the RNG on Win32 fails, quit.
7742 o Assert / crash bugs:
7743 - Refuse relay cells that claim to have a length larger than the
7744 maximum allowed. This prevents a potential attack that could read
7745 arbitrary memory (e.g. keys) from an exit server's process
7747 - If unofficial Tor clients connect and send weird TLS certs, our
7748 Tor server triggers an assert. Stop asserting, and start handling
7749 TLS errors better in other situations too.
7750 - Fix a race condition that can trigger an assert when we have a
7751 pending create cell and an OR connection attempt fails.
7754 - Use pthreads for worker processes rather than forking. This was
7755 forced because when we forked, we ended up wasting a lot of
7756 duplicate ram over time.
7757 - Also switch to foo_r versions of some library calls to allow
7758 reentry and threadsafeness.
7759 - Implement --disable-threads configure option. Disable threads on
7760 netbsd and openbsd by default, because they have no reentrant
7761 resolver functions (!), and on solaris since it has other
7763 - Fix possible bug on threading platforms (e.g. win32) which was
7764 leaking a file descriptor whenever a cpuworker or dnsworker died.
7765 - Fix a minor memory leak when somebody establishes an introduction
7766 point at your Tor server.
7767 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
7769 - Add ./configure --with-dmalloc option, to track memory leaks.
7770 - And try to free all memory on closing, so we can detect what
7773 o Protocol correctness:
7774 - When we've connected to an OR and handshaked but didn't like
7775 the result, we were closing the conn without sending destroy
7776 cells back for pending circuits. Now send those destroys.
7777 - Start sending 'truncated' cells back rather than destroy cells
7778 if the circuit closes in front of you. This means we won't have
7779 to abandon partially built circuits.
7780 - Handle changed router status correctly when dirserver reloads
7781 fingerprint file. We used to be dropping all unverified descriptors
7782 right then. The bug was hidden because we would immediately
7783 fetch a directory from another dirserver, which would include the
7784 descriptors we just dropped.
7785 - Revise tor-spec to add more/better stream end reasons.
7786 - Revise all calls to connection_edge_end to avoid sending 'misc',
7787 and to take errno into account where possible.
7788 - Client now retries when streams end early for 'hibernating' or
7789 'resource limit' reasons, rather than failing them.
7790 - Try to be more zealous about calling connection_edge_end when
7791 things go bad with edge conns in connection.c.
7793 o Robustness improvements:
7794 - Better handling for heterogeneous / unreliable nodes:
7795 - Annotate circuits with whether they aim to contain high uptime
7796 nodes and/or high capacity nodes. When building circuits, choose
7798 - This means that every single node in an intro rend circuit,
7799 not just the last one, will have a minimum uptime.
7800 - New config option LongLivedPorts to indicate application streams
7801 that will want high uptime circuits.
7802 - Servers reset uptime when a dir fetch entirely fails. This
7803 hopefully reflects stability of the server's network connectivity.
7804 - If somebody starts his tor server in Jan 2004 and then fixes his
7805 clock, don't make his published uptime be a year.
7806 - Reset published uptime when we wake up from hibernation.
7807 - Introduce a notion of 'internal' circs, which are chosen without
7808 regard to the exit policy of the last hop. Intro and rendezvous
7809 circs must be internal circs, to avoid leaking information. Resolve
7810 and connect streams can use internal circs if they want.
7811 - New circuit pooling algorithm: keep track of what destination ports
7812 we've used recently (start out assuming we'll want to use 80), and
7813 make sure to have enough circs around to satisfy these ports. Also
7814 make sure to have 2 internal circs around if we've required internal
7815 circs lately (and with high uptime if we've seen that lately too).
7816 - Turn addr_policy_compare from a tristate to a quadstate; this should
7817 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7818 for google.com" problem.
7819 - When a client asks us for a dir mirror and we don't have one,
7820 launch an attempt to get a fresh one.
7821 - First cut at support for "create-fast" cells. Clients can use
7822 these when extending to their first hop, since the TLS already
7823 provides forward secrecy and authentication. Not enabled on
7826 o Reachability testing.
7827 - Your Tor server will automatically try to see if its ORPort and
7828 DirPort are reachable from the outside, and it won't upload its
7829 descriptor until it decides at least ORPort is reachable (when
7830 DirPort is not yet found reachable, publish it as zero).
7831 - When building testing circs for ORPort testing, use only
7832 high-bandwidth nodes, so fewer circuits fail.
7833 - Notice when our IP changes, and reset stats/uptime/reachability.
7834 - Authdirservers don't do ORPort reachability detection, since
7835 they're in clique mode, so it will be rare to find a server not
7836 already connected to them.
7837 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
7841 - Now we allow two unverified servers with the same nickname
7842 but different keys. But if a nickname is verified, only that
7843 nickname+key are allowed.
7844 - If you're an authdirserver connecting to an address:port,
7845 and it's not the OR you were expecting, forget about that
7846 descriptor. If he *was* the one you were expecting, then forget
7847 about all other descriptors for that address:port.
7848 - Allow servers to publish descriptors from 12 hours in the future.
7849 Corollary: only whine about clock skew from the dirserver if
7850 he's a trusted dirserver (since now even verified servers could
7851 have quite wrong clocks).
7852 - Require servers that use the default dirservers to have public IP
7853 addresses. We have too many servers that are configured with private
7854 IPs and their admins never notice the log entries complaining that
7855 their descriptors are being rejected.
7857 o Efficiency improvements:
7858 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
7859 and /dev/poll), and hopefully work better on Windows too.
7860 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
7861 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
7862 - Find libevent even if it's hiding in /usr/local/ and your
7863 CFLAGS and LDFLAGS don't tell you to look there.
7864 - Be able to link with libevent as a shared library (the default
7865 after 1.0d), even if it's hiding in /usr/local/lib and even
7866 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7867 assuming you're running gcc. Otherwise fail and give a useful
7869 - Switch to a new buffer management algorithm, which tries to avoid
7870 reallocing and copying quite as much. In first tests it looks like
7871 it uses *more* memory on average, but less cpu.
7872 - Switch our internal buffers implementation to use a ring buffer,
7873 to hopefully improve performance for fast servers a lot.
7874 - Reenable the part of the code that tries to flush as soon as an
7875 OR outbuf has a full TLS record available. Perhaps this will make
7876 OR outbufs not grow as huge except in rare cases, thus saving lots
7877 of CPU time plus memory.
7878 - Improve performance for dirservers: stop re-parsing the whole
7879 directory every time you regenerate it.
7880 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7881 it much faster to look up a circuit for each relay cell.
7882 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7883 since they're eating our cpu on exit nodes.
7884 - Stop wasting time doing a case insensitive comparison for every
7885 dns name every time we do any lookup. Canonicalize the names to
7886 lowercase when you first see them.
7889 - Handle unavailable hidden services better. Handle slow or busy
7890 hidden services better.
7891 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7892 circ as necessary, if there are any completed ones lying around
7893 when we try to launch one.
7894 - Make hidden services try to establish a rendezvous for 30 seconds
7895 after fetching the descriptor, rather than for n (where n=3)
7896 attempts to build a circuit.
7897 - Adjust maximum skew and age for rendezvous descriptors: let skew
7898 be 48 hours rather than 90 minutes.
7899 - Reject malformed .onion addresses rather then passing them on as
7900 normal web requests.
7903 - More Tor controller support. See
7904 http://tor.eff.org/doc/control-spec.txt for all the new features,
7905 including signals to emulate unix signals from any platform;
7906 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7907 closestream; closecircuit; etc.
7908 - Encode hashed controller passwords in hex instead of base64,
7909 to make it easier to write controllers.
7910 - Revise control spec and implementation to allow all log messages to
7911 be sent to controller with their severities intact (suggested by
7912 Matt Edman). Disable debug-level logs while delivering a debug-level
7913 log to the controller, to prevent loop. Update TorControl to handle
7914 new log event types.
7916 o New config options/defaults:
7917 - Begin scrubbing sensitive strings from logs by default. Turn off
7918 the config option SafeLogging if you need to do debugging.
7919 - New exit policy: accept most low-numbered ports, rather than
7920 rejecting most low-numbered ports.
7921 - Put a note in the torrc about abuse potential with the default
7923 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7925 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
7926 based on patch from Adam Langley (basic auth only).
7927 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7928 the fast servers that have been joining lately. (Clients are now
7929 willing to load balance over up to 2 MB of advertised bandwidth
7931 - New config option MaxAdvertisedBandwidth which lets you advertise
7932 a low bandwidthrate (to not attract as many circuits) while still
7933 allowing a higher bandwidthrate in reality.
7934 - Require BandwidthRate to be at least 20kB/s for servers.
7935 - Add a NoPublish config option, so you can be a server (e.g. for
7936 testing running Tor servers in other Tor networks) without
7937 publishing your descriptor to the primary dirservers.
7938 - Add a new AddressMap config directive to rewrite incoming socks
7939 addresses. This lets you, for example, declare an implicit
7940 required exit node for certain sites.
7941 - Add a new TrackHostExits config directive to trigger addressmaps
7942 for certain incoming socks addresses -- for sites that break when
7943 your exit keeps changing (based on patch from Mike Perry).
7944 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7945 which describes how often we retry making new circuits if current
7946 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7947 how long we're willing to make use of an already-dirty circuit.
7948 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
7949 a config option "ShutdownWaitLength" (when using kill -INT on
7951 - Fix an edge case in parsing config options: if they say "--"
7952 on the commandline, it's not a config option (thanks weasel).
7953 - New config option DirAllowPrivateAddresses for authdirservers.
7954 Now by default they refuse router descriptors that have non-IP or
7955 private-IP addresses.
7956 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7957 smart" default value: low for servers and high for clients.
7958 - Some people were putting "Address " in their torrc, and they had
7959 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7960 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7961 LOCALSTATEDIR/tor instead.
7962 - Implement --verify-config command-line option to check if your torrc
7963 is valid without actually launching Tor.
7965 o Logging improvements:
7966 - When dirservers refuse a server descriptor, we now log its
7967 contactinfo, platform, and the poster's IP address.
7968 - Only warn once per nickname from add_nickname_list_to_smartlist()
7969 per failure, so an entrynode or exitnode choice that's down won't
7971 - When we're connecting to an OR and he's got a different nickname/key
7972 than we were expecting, only complain loudly if we're an OP or a
7973 dirserver. Complaining loudly to the OR admins just confuses them.
7974 - Whine at you if you're a server and you don't set your contactinfo.
7975 - Warn when exit policy implicitly allows local addresses.
7976 - Give a better warning when some other server advertises an
7977 ORPort that is actually an apache running ssl.
7978 - If we get an incredibly skewed timestamp from a dirserver mirror
7979 that isn't a verified OR, don't warn -- it's probably him that's
7981 - When a dirserver causes you to give a warn, mention which dirserver
7983 - Initialize libevent later in the startup process, so the logs are
7984 already established by the time we start logging libevent warns.
7985 - Use correct errno on win32 if libevent fails.
7986 - Check and warn about known-bad/slow libevent versions.
7987 - Stop warning about sigpipes in the logs. We're going to
7988 pretend that getting these occassionally is normal and fine.
7990 o New contrib scripts:
7991 - New experimental script tor/contrib/exitlist: a simple python
7992 script to parse directories and find Tor nodes that exit to listed
7994 - New experimental script tor/contrib/ExerciseServer.py (needs more
7995 work) that uses the controller interface to build circuits and
7996 fetch pages over them. This will help us bootstrap servers that
7997 have lots of capacity but haven't noticed it yet.
7998 - New experimental script tor/contrib/PathDemo.py (needs more work)
7999 that uses the controller interface to let you choose whole paths
8001 "<hostname>.<path,separated by dots>.<length of path>.path"
8002 - New contributed script "privoxy-tor-toggle" to toggle whether
8003 Privoxy uses Tor. Seems to be configured for Debian by default.
8004 - Have torctl.in/tor.sh.in check for location of su binary (needed
8008 - chdir() to your datadirectory at the *end* of the daemonize process,
8009 not the beginning. This was a problem because the first time you
8010 run tor, if your datadir isn't there, and you have runasdaemon set
8011 to 1, it will try to chdir to it before it tries to create it. Oops.
8012 - Fix several double-mark-for-close bugs, e.g. where we were finding
8013 a conn for a cell even if that conn is already marked for close.
8014 - Stop most cases of hanging up on a socks connection without sending
8016 - Fix a bug in the RPM package: set home directory for _tor to
8017 something more reasonable when first installing.
8018 - Stop putting nodename in the Platform string in server descriptors.
8019 It doesn't actually help, and it is confusing/upsetting some people.
8020 - When using preferred entry or exit nodes, ignore whether the
8021 circuit wants uptime or capacity. They asked for the nodes, they
8023 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
8024 artificially capped at 500kB.
8025 - Cache local dns resolves correctly even when they're .exit
8027 - If we're hibernating and we get a SIGINT, exit immediately.
8028 - tor-resolve requests were ignoring .exit if there was a working circuit
8029 they could use instead.
8030 - Pay more attention to the ClientOnly config option.
8031 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
8032 installer screens; and don't put stuff into StartupItems unless
8033 the user asks you to.
8036 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
8037 rather than just rejecting it.
8038 - If our clock jumps forward by 100 seconds or more, assume something
8039 has gone wrong with our network and abandon all not-yet-used circs.
8040 - When an application is using socks5, give him the whole variety of
8041 potential socks5 responses (connect refused, host unreachable, etc),
8042 rather than just "success" or "failure".
8043 - A more sane version numbering system. See
8044 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
8045 - Change version parsing logic: a version is "obsolete" if it is not
8046 recommended and (1) there is a newer recommended version in the
8047 same series, or (2) there are no recommended versions in the same
8048 series, but there are some recommended versions in a newer series.
8049 A version is "new" if it is newer than any recommended version in
8051 - Report HTTP reasons to client when getting a response from directory
8052 servers -- so you can actually know what went wrong.
8053 - Reject odd-looking addresses at the client (e.g. addresses that
8054 contain a colon), rather than having the server drop them because
8056 - Stop publishing socksport in the directory, since it's not
8057 actually meant to be public. For compatibility, publish a 0 there
8059 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8060 cookies to disk and doesn't log each web request to disk. (Thanks
8061 to Brett Carrington for pointing this out.)
8062 - Add OSX uninstall instructions. An actual uninstall script will
8064 - Add "opt hibernating 1" to server descriptor to make it clearer
8065 whether the server is hibernating.
8068 Changes in version 0.0.9.10 - 2005-06-16
8069 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
8070 - Refuse relay cells that claim to have a length larger than the
8071 maximum allowed. This prevents a potential attack that could read
8072 arbitrary memory (e.g. keys) from an exit server's process
8076 Changes in version 0.0.9.9 - 2005-04-23
8077 o Bugfixes on 0.0.9.x:
8078 - If unofficial Tor clients connect and send weird TLS certs, our
8079 Tor server triggers an assert. This release contains a minimal
8080 backport from the broader fix that we put into 0.1.0.4-rc.
8083 Changes in version 0.0.9.8 - 2005-04-07
8084 o Bugfixes on 0.0.9.x:
8085 - We have a bug that I haven't found yet. Sometimes, very rarely,
8086 cpuworkers get stuck in the 'busy' state, even though the cpuworker
8087 thinks of itself as idle. This meant that no new circuits ever got
8088 established. Here's a workaround to kill any cpuworker that's been
8089 busy for more than 100 seconds.
8092 Changes in version 0.0.9.7 - 2005-04-01
8093 o Bugfixes on 0.0.9.x:
8094 - Fix another race crash bug (thanks to Glenn Fink for reporting).
8095 - Compare identity to identity, not to nickname, when extending to
8096 a router not already in the directory. This was preventing us from
8097 extending to unknown routers. Oops.
8098 - Make sure to create OS X Tor user in <500 range, so we aren't
8099 creating actual system users.
8100 - Note where connection-that-hasn't-sent-end was marked, and fix
8101 a few really loud instances of this harmless bug (it's fixed more
8105 Changes in version 0.0.9.6 - 2005-03-24
8106 o Bugfixes on 0.0.9.x (crashes and asserts):
8107 - Add new end stream reasons to maintainance branch. Fix bug where
8108 reason (8) could trigger an assert. Prevent bug from recurring.
8109 - Apparently win32 stat wants paths to not end with a slash.
8110 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8111 blowing away the circuit that conn->cpath_layer points to, then
8112 checking to see if the circ is well-formed. Backport check to make
8113 sure we dont use the cpath on a closed connection.
8114 - Prevent circuit_resume_edge_reading_helper() from trying to package
8115 inbufs for marked-for-close streams.
8116 - Don't crash on hup if your options->address has become unresolvable.
8117 - Some systems (like OS X) sometimes accept() a connection and tell
8118 you the remote host is 0.0.0.0:0. If this happens, due to some
8119 other mis-features, we get confused; so refuse the conn for now.
8121 o Bugfixes on 0.0.9.x (other):
8122 - Fix harmless but scary "Unrecognized content encoding" warn message.
8123 - Add new stream error reason: TORPROTOCOL reason means "you are not
8124 speaking a version of Tor I understand; say bye-bye to your stream."
8125 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8126 into the future, now that we are more tolerant of skew. This
8127 resolves a bug where a Tor server would refuse to cache a directory
8128 because all the directories it gets are too far in the future;
8129 yet the Tor server never logs any complaints about clock skew.
8130 - Mac packaging magic: make man pages useable, and do not overwrite
8131 existing torrc files.
8132 - Make OS X log happily to /var/log/tor/tor.log
8135 Changes in version 0.0.9.5 - 2005-02-22
8136 o Bugfixes on 0.0.9.x:
8137 - Fix an assert race at exit nodes when resolve requests fail.
8138 - Stop picking unverified dir mirrors--it only leads to misery.
8139 - Patch from Matt Edman to make NT services work better. Service
8140 support is still not compiled into the executable by default.
8141 - Patch from Dmitri Bely so the Tor service runs better under
8142 the win32 SYSTEM account.
8143 - Make tor-resolve actually work (?) on Win32.
8144 - Fix a sign bug when getrlimit claims to have 4+ billion
8145 file descriptors available.
8146 - Stop refusing to start when bandwidthburst == bandwidthrate.
8147 - When create cells have been on the onion queue more than five
8148 seconds, just send back a destroy and take them off the list.
8151 Changes in version 0.0.9.4 - 2005-02-03
8152 o Bugfixes on 0.0.9:
8153 - Fix an assert bug that took down most of our servers: when
8154 a server claims to have 1 GB of bandwidthburst, don't
8156 - Don't crash as badly if we have spawned the max allowed number
8157 of dnsworkers, or we're out of file descriptors.
8158 - Block more file-sharing ports in the default exit policy.
8159 - MaxConn is now automatically set to the hard limit of max
8160 file descriptors we're allowed (ulimit -n), minus a few for
8162 - Give a clearer message when servers need to raise their
8163 ulimit -n when they start running out of file descriptors.
8164 - SGI Compatibility patches from Jan Schaumann.
8165 - Tolerate a corrupt cached directory better.
8166 - When a dirserver hasn't approved your server, list which one.
8167 - Go into soft hibernation after 95% of the bandwidth is used,
8168 not 99%. This is especially important for daily hibernators who
8169 have a small accounting max. Hopefully it will result in fewer
8170 cut connections when the hard hibernation starts.
8171 - Load-balance better when using servers that claim more than
8172 800kB/s of capacity.
8173 - Make NT services work (experimental, only used if compiled in).
8176 Changes in version 0.0.9.3 - 2005-01-21
8177 o Bugfixes on 0.0.9:
8178 - Backport the cpu use fixes from main branch, so busy servers won't
8179 need as much processor time.
8180 - Work better when we go offline and then come back, or when we
8181 run Tor at boot before the network is up. We do this by
8182 optimistically trying to fetch a new directory whenever an
8183 application request comes in and we think we're offline -- the
8184 human is hopefully a good measure of when the network is back.
8185 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8186 long as you keep using them; actually publish hidserv descriptors
8187 shortly after they change, rather than waiting 20-40 minutes.
8188 - Enable Mac startup script by default.
8189 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8190 - When you update AllowUnverifiedNodes or FirewallPorts via the
8191 controller's setconf feature, we were always appending, never
8193 - When you update HiddenServiceDir via setconf, it was screwing up
8194 the order of reading the lines, making it fail.
8195 - Do not rewrite a cached directory back to the cache; otherwise we
8196 will think it is recent and not fetch a newer one on startup.
8197 - Workaround for webservers that lie about Content-Encoding: Tor
8198 now tries to autodetect compressed directories and compression
8199 itself. This lets us Proxypass dir fetches through apache.
8202 Changes in version 0.0.9.2 - 2005-01-04
8203 o Bugfixes on 0.0.9 (crashes and asserts):
8204 - Fix an assert on startup when the disk is full and you're logging
8206 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8207 style address, then we'd crash.
8208 - Fix an assert trigger when the running-routers string we get from
8209 a dirserver is broken.
8210 - Make worker threads start and run on win32. Now win32 servers
8212 - Bandaid (not actually fix, but now it doesn't crash) an assert
8213 where the dns worker dies mysteriously and the main Tor process
8214 doesn't remember anything about the address it was resolving.
8216 o Bugfixes on 0.0.9 (Win32):
8217 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8218 name out of the warning/assert messages.
8219 - Fix a superficial "unhandled error on read" bug on win32.
8220 - The win32 installer no longer requires a click-through for our
8221 license, since our Free Software license grants rights but does not
8223 - Win32: When connecting to a dirserver fails, try another one
8224 immediately. (This was already working for non-win32 Tors.)
8225 - Stop trying to parse $HOME on win32 when hunting for default
8227 - Make tor-resolve.c work on win32 by calling network_init().
8229 o Bugfixes on 0.0.9 (other):
8230 - Make 0.0.9.x build on Solaris again.
8231 - Due to a fencepost error, we were blowing away the \n when reporting
8232 confvalue items in the controller. So asking for multiple config
8233 values at once couldn't work.
8234 - When listing circuits that are pending on an opening OR connection,
8235 if we're an OR we were listing circuits that *end* at us as
8236 being pending on every listener, dns/cpu worker, etc. Stop that.
8237 - Dirservers were failing to create 'running-routers' or 'directory'
8238 strings if we had more than some threshold of routers. Fix them so
8239 they can handle any number of routers.
8240 - Fix a superficial "Duplicate mark for close" bug.
8241 - Stop checking for clock skew for OR connections, even for servers.
8242 - Fix a fencepost error that was chopping off the last letter of any
8243 nickname that is the maximum allowed nickname length.
8244 - Update URLs in log messages so they point to the new website.
8245 - Fix a potential problem in mangling server private keys while
8246 writing to disk (not triggered yet, as far as we know).
8247 - Include the licenses for other free software we include in Tor,
8248 now that we're shipping binary distributions more regularly.
8251 Changes in version 0.0.9.1 - 2004-12-15
8252 o Bugfixes on 0.0.9:
8253 - Make hibernation actually work.
8254 - Make HashedControlPassword config option work.
8255 - When we're reporting event circuit status to a controller,
8256 don't use the stream status code.
8259 Changes in version 0.0.9 - 2004-12-12
8260 o Bugfixes on 0.0.8.1 (Crashes and asserts):
8261 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8262 write() call will fail and we handle it there.
8263 - When we run out of disk space, or other log writing error, don't
8264 crash. Just stop logging to that log and continue.
8265 - Fix isspace() and friends so they still make Solaris happy
8266 but also so they don't trigger asserts on win32.
8267 - Fix assert failure on malformed socks4a requests.
8268 - Fix an assert bug where a hidden service provider would fail if
8269 the first hop of his rendezvous circuit was down.
8270 - Better handling of size_t vs int, so we're more robust on 64
8273 o Bugfixes on 0.0.8.1 (Win32):
8274 - Make windows sockets actually non-blocking (oops), and handle
8275 win32 socket errors better.
8276 - Fix parse_iso_time on platforms without strptime (eg win32).
8277 - win32: when being multithreaded, leave parent fdarray open.
8278 - Better handling of winsock includes on non-MSV win32 compilers.
8279 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8281 - Make unit tests work on win32.
8283 o Bugfixes on 0.0.8.1 (Path selection and streams):
8284 - Calculate timeout for waiting for a connected cell from the time
8285 we sent the begin cell, not from the time the stream started. If
8286 it took a long time to establish the circuit, we would time out
8287 right after sending the begin cell.
8288 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8289 of * as always matching, so we were picking reject *:* nodes as
8290 exit nodes too. Oops.
8291 - When read() failed on a stream, we would close it without sending
8292 back an end. So 'connection refused' would simply be ignored and
8293 the user would get no response.
8294 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8295 we shouldn't hold-open-until-flush if the eof arrived first.
8296 - Let resolve conns retry/expire also, rather than sticking around
8298 - Fix more dns related bugs: send back resolve_failed and end cells
8299 more reliably when the resolve fails, rather than closing the
8300 circuit and then trying to send the cell. Also attach dummy resolve
8301 connections to a circuit *before* calling dns_resolve(), to fix
8302 a bug where cached answers would never be sent in RESOLVED cells.
8304 o Bugfixes on 0.0.8.1 (Circuits):
8305 - Finally fix a bug that's been plaguing us for a year:
8306 With high load, circuit package window was reaching 0. Whenever
8307 we got a circuit-level sendme, we were reading a lot on each
8308 socket, but only writing out a bit. So we would eventually reach
8309 eof. This would be noticed and acted on even when there were still
8310 bytes sitting in the inbuf.
8311 - Use identity comparison, not nickname comparison, to choose which
8312 half of circuit-ID-space each side gets to use. This is needed
8313 because sometimes we think of a router as a nickname, and sometimes
8314 as a hex ID, and we can't predict what the other side will do.
8316 o Bugfixes on 0.0.8.1 (Other):
8317 - Fix a whole slew of memory leaks.
8318 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8319 - If we are using select, make sure we stay within FD_SETSIZE.
8320 - When poll() is interrupted, we shouldn't believe the revents values.
8321 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8322 and smartlist_len, which are two major profiling offenders.
8323 - If do_hup fails, actually notice.
8324 - Flush the log file descriptor after we print "Tor opening log file",
8325 so we don't see those messages days later.
8326 - Hidden service operators now correctly handle version 1 style
8327 INTRODUCE1 cells (nobody generates them still, so not a critical
8329 - Handle more errnos from accept() without closing the listener.
8330 Some OpenBSD machines were closing their listeners because
8331 they ran out of file descriptors.
8332 - Some people had wrapped their tor client/server in a script
8333 that would restart it whenever it died. This did not play well
8334 with our "shut down if your version is obsolete" code. Now people
8335 don't fetch a new directory if their local cached version is
8337 - Make our autogen.sh work on ksh as well as bash.
8338 - Better torrc example lines for dirbindaddress and orbindaddress.
8339 - Improved bounds checking on parsed ints (e.g. config options and
8340 the ones we find in directories.)
8341 - Stop using separate defaults for no-config-file and
8342 empty-config-file. Now you have to explicitly turn off SocksPort,
8343 if you don't want it open.
8344 - We were starting to daemonize before we opened our logs, so if
8345 there were any problems opening logs, we would complain to stderr,
8346 which wouldn't work, and then mysteriously exit.
8347 - If a verified OR connects to us before he's uploaded his descriptor,
8348 or we verify him and hup but he still has the original TLS
8349 connection, then conn->nickname is still set like he's unverified.
8351 o Code security improvements, inspired by Ilja:
8352 - tor_snprintf wrapper over snprintf with consistent (though not C99)
8354 - Replace sprintf with tor_snprintf. (I think they were all safe, but
8356 - Replace strcpy/strncpy with strlcpy in more places.
8357 - Avoid strcat; use tor_snprintf or strlcat instead.
8359 o Features (circuits and streams):
8360 - New circuit building strategy: keep a list of ports that we've
8361 used in the past 6 hours, and always try to have 2 circuits open
8362 or on the way that will handle each such port. Seed us with port
8363 80 so web users won't complain that Tor is "slow to start up".
8364 - Make kill -USR1 dump more useful stats about circuits.
8365 - When warning about retrying or giving up, print the address, so
8366 the user knows which one it's talking about.
8367 - If you haven't used a clean circuit in an hour, throw it away,
8368 just to be on the safe side. (This means after 6 hours a totally
8369 unused Tor client will have no circuits open.)
8370 - Support "foo.nickname.exit" addresses, to let Alice request the
8371 address "foo" as viewed by exit node "nickname". Based on a patch
8373 - If your requested entry or exit node has advertised bandwidth 0,
8375 - Be more greedy about filling up relay cells -- we try reading again
8376 once we've processed the stuff we read, in case enough has arrived
8377 to fill the last cell completely.
8378 - Refuse application socks connections to port 0.
8379 - Use only 0.0.9pre1 and later servers for resolve cells.
8381 o Features (bandwidth):
8382 - Hibernation: New config option "AccountingMax" lets you
8383 set how many bytes per month (in each direction) you want to
8384 allow your server to consume. Rather than spreading those
8385 bytes out evenly over the month, we instead hibernate for some
8386 of the month and pop up at a deterministic time, work until
8387 the bytes are consumed, then hibernate again. Config option
8388 "MonthlyAccountingStart" lets you specify which day of the month
8389 your billing cycle starts on.
8390 - Implement weekly/monthly/daily accounting: now you specify your
8391 hibernation properties by
8392 AccountingMax N bytes|KB|MB|GB|TB
8393 AccountingStart day|week|month [day] HH:MM
8394 Defaults to "month 1 0:00".
8395 - Let bandwidth and interval config options be specified as 5 bytes,
8396 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8398 o Features (directories):
8399 - New "router-status" line in directory, to better bind each verified
8400 nickname to its identity key.
8401 - Clients can ask dirservers for /dir.z to get a compressed version
8402 of the directory. Only works for servers running 0.0.9, of course.
8403 - Make clients cache directories and use them to seed their router
8404 lists at startup. This means clients have a datadir again.
8405 - Respond to content-encoding headers by trying to uncompress as
8407 - Clients and servers now fetch running-routers; cache
8408 running-routers; compress running-routers; serve compressed
8410 - Make moria2 advertise a dirport of 80, so people behind firewalls
8411 will be able to get a directory.
8412 - Http proxy support
8413 - Dirservers translate requests for http://%s:%d/x to /x
8414 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8415 be routed through this host.
8416 - Clients ask for /tor/x rather than /x for new enough dirservers.
8417 This way we can one day coexist peacefully with apache.
8418 - Clients specify a "Host: %s%d" http header, to be compatible
8419 with more proxies, and so running squid on an exit node can work.
8420 - Protect dirservers from overzealous descriptor uploading -- wait
8421 10 seconds after directory gets dirty, before regenerating.
8423 o Features (packages and install):
8424 - Add NSI installer contributed by J Doe.
8425 - Apply NT service patch from Osamu Fujino. Still needs more work.
8426 - Commit VC6 and VC7 workspace/project files.
8427 - Commit a tor.spec for making RPM files, with help from jbash.
8428 - Add contrib/torctl.in contributed by Glenn Fink.
8429 - Make expand_filename handle ~ and ~username.
8430 - Use autoconf to enable largefile support where necessary. Use
8431 ftello where available, since ftell can fail at 2GB.
8432 - Ship src/win32/ in the tarball, so people can use it to build.
8433 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8436 o Features (ui controller):
8437 - Control interface: a separate program can now talk to your
8438 client/server over a socket, and get/set config options, receive
8439 notifications of circuits and streams starting/finishing/dying,
8440 bandwidth used, etc. The next step is to get some GUIs working.
8441 Let us know if you want to help out. See doc/control-spec.txt .
8442 - Ship a contrib/tor-control.py as an example script to interact
8443 with the control port.
8444 - "tor --hash-password zzyxz" will output a salted password for
8445 use in authenticating to the control interface.
8446 - Implement the control-spec's SAVECONF command, to write your
8447 configuration to torrc.
8448 - Get cookie authentication for the controller closer to working.
8449 - When set_conf changes our server descriptor, upload a new copy.
8450 But don't upload it too often if there are frequent changes.
8452 o Features (config and command-line):
8453 - Deprecate unofficial config option abbreviations, and abbreviations
8454 not on the command line.
8455 - Configuration infrastructure support for warning on obsolete
8457 - Give a slightly more useful output for "tor -h".
8458 - Break DirFetchPostPeriod into:
8459 - DirFetchPeriod for fetching full directory,
8460 - StatusFetchPeriod for fetching running-routers,
8461 - DirPostPeriod for posting server descriptor,
8462 - RendPostPeriod for posting hidden service descriptors.
8463 - New log format in config:
8464 "Log minsev[-maxsev] stdout|stderr|syslog" or
8465 "Log minsev[-maxsev] file /var/foo"
8466 - DirPolicy config option, to let people reject incoming addresses
8467 from their dirserver.
8468 - "tor --list-fingerprint" will list your identity key fingerprint
8470 - Make tor --version --version dump the cvs Id of every file.
8471 - New 'MyFamily nick1,...' config option for a server to
8472 specify other servers that shouldn't be used in the same circuit
8473 with it. Only believed if nick1 also specifies us.
8474 - New 'NodeFamily nick1,nick2,...' config option for a client to
8475 specify nodes that it doesn't want to use in the same circuit.
8476 - New 'Redirectexit pattern address:port' config option for a
8477 server to redirect exit connections, e.g. to a local squid.
8478 - Add "pass" target for RedirectExit, to make it easier to break
8479 out of a sequence of RedirectExit rules.
8480 - Make the dirservers file obsolete.
8481 - Include a dir-signing-key token in directories to tell the
8482 parsing entity which key is being used to sign.
8483 - Remove the built-in bulky default dirservers string.
8484 - New config option "Dirserver %s:%d [fingerprint]", which can be
8485 repeated as many times as needed. If no dirservers specified,
8486 default to moria1,moria2,tor26.
8487 - Make 'Routerfile' config option obsolete.
8488 - Discourage people from setting their dirfetchpostperiod more often
8489 than once per minute.
8492 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8493 get back to normal.)
8494 - Accept *:706 (silc) in default exit policy.
8495 - Implement new versioning format for post 0.1.
8496 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8497 log more informatively.
8498 - Check clock skew for verified servers, but allow unverified
8499 servers and clients to have any clock skew.
8500 - Make sure the hidden service descriptors are at a random offset
8501 from each other, to hinder linkability.
8502 - Clients now generate a TLS cert too, in preparation for having
8503 them act more like real nodes.
8504 - Add a pure-C tor-resolve implementation.
8505 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8506 1024) file descriptors.
8507 - Raise the max dns workers from 50 to 100.
8510 Changes in version 0.0.8.1 - 2004-10-13
8512 - Fix a seg fault that can be triggered remotely for Tor
8513 clients/servers with an open dirport.
8514 - Fix a rare assert trigger, where routerinfos for entries in
8515 our cpath would expire while we're building the path.
8516 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8517 - Fix a rare seg fault for people running hidden services on
8518 intermittent connections.
8519 - Fix a bug in parsing opt keywords with objects.
8520 - Fix a stale pointer assert bug when a stream detaches and
8522 - Fix a string format vulnerability (probably not exploitable)
8523 in reporting stats locally.
8524 - Fix an assert trigger: sometimes launching circuits can fail
8525 immediately, e.g. because too many circuits have failed recently.
8526 - Fix a compile warning on 64 bit platforms.
8529 Changes in version 0.0.8 - 2004-08-25
8531 - Made our unit tests compile again on OpenBSD 3.5, and tor
8532 itself compile again on OpenBSD on a sparc64.
8533 - We were neglecting milliseconds when logging on win32, so
8534 everything appeared to happen at the beginning of each second.
8535 - Check directory signature _before_ you decide whether you're
8536 you're running an obsolete version and should exit.
8537 - Check directory signature _before_ you parse the running-routers
8538 list to decide who's running.
8539 - Check return value of fclose while writing to disk, so we don't
8540 end up with broken files when servers run out of disk space.
8541 - Port it to SunOS 5.9 / Athena
8542 - Fix two bugs in saving onion keys to disk when rotating, so
8543 hopefully we'll get fewer people using old onion keys.
8544 - Remove our mostly unused -- and broken -- hex_encode()
8545 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8546 for pointing out this bug.)
8547 - Only pick and establish intro points after we've gotten a
8549 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8550 don't put it into the client dns cache.
8551 - If a begin failed due to exit policy, but we believe the IP
8552 address should have been allowed, switch that router to exitpolicy
8553 reject *:* until we get our next directory.
8556 - 'Extend' relay cell payloads now include the digest of the
8557 intended next hop's identity key. Now we can verify that we're
8558 extending to the right router, and also extend to routers we
8559 hadn't heard of before.
8562 - Tor nodes can now act as relays (with an advertised ORPort)
8563 without being manually verified by the dirserver operators.
8564 - Uploaded descriptors of unverified routers are now accepted
8565 by the dirservers, and included in the directory.
8566 - Verified routers are listed by nickname in the running-routers
8567 list; unverified routers are listed as "$<fingerprint>".
8568 - We now use hash-of-identity-key in most places rather than
8569 nickname or addr:port, for improved security/flexibility.
8570 - AllowUnverifiedNodes config option to let circuits choose no-name
8571 routers in entry,middle,exit,introduction,rendezvous positions.
8572 Allow middle and rendezvous positions by default.
8573 - When picking unverified routers, skip those with low uptime and/or
8574 low bandwidth, depending on what properties you care about.
8575 - ClientOnly option for nodes that never want to become servers.
8576 - Directory caching.
8577 - "AuthoritativeDir 1" option for the official dirservers.
8578 - Now other nodes (clients and servers) will cache the latest
8579 directory they've pulled down.
8580 - They can enable their DirPort to serve it to others.
8581 - Clients will pull down a directory from any node with an open
8582 DirPort, and check the signature/timestamp correctly.
8583 - Authoritative dirservers now fetch directories from other
8584 authdirservers, to stay better synced.
8585 - Running-routers list tells who's down also, along with noting
8586 if they're verified (listed by nickname) or unverified (listed
8588 - Allow dirservers to serve running-router list separately.
8589 This isn't used yet.
8590 - You can now fetch $DIRURL/running-routers to get just the
8591 running-routers line, not the whole descriptor list. (But
8592 clients don't use this yet.)
8593 - Clients choose nodes proportional to advertised bandwidth.
8594 - Clients avoid using nodes with low uptime as introduction points.
8595 - Handle servers with dynamic IP addresses: don't just replace
8596 options->Address with the resolved one at startup, and
8597 detect our address right before we make a routerinfo each time.
8598 - 'FascistFirewall' option to pick dirservers and ORs on specific
8599 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8600 which ports are open. (Defaults to 80,443)
8601 - Try other dirservers immediately if the one you try is down. This
8602 should tolerate down dirservers better now.
8603 - ORs connect-on-demand to other ORs
8604 - If you get an extend cell to an OR you're not connected to,
8605 connect, handshake, and forward the create cell.
8606 - The authoritative dirservers stay connected to everybody,
8607 and everybody stays connected to 0.0.7 servers, but otherwise
8608 clients/servers expire unused connections after 5 minutes.
8609 - When servers get a sigint, they delay 30 seconds (refusing new
8610 connections) then exit. A second sigint causes immediate exit.
8611 - File and name management:
8612 - Look for .torrc if no CONFDIR "torrc" is found.
8613 - If no datadir is defined, then choose, make, and secure ~/.tor
8615 - If torrc not found, exitpolicy reject *:*.
8616 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8617 - If no nickname is defined, derive default from hostname.
8618 - Rename secret key files, e.g. identity.key -> secret_id_key,
8619 to discourage people from mailing their identity key to tor-ops.
8620 - Refuse to build a circuit before the directory has arrived --
8621 it won't work anyway, since you won't know the right onion keys
8623 - Parse tor version numbers so we can do an is-newer-than check
8624 rather than an is-in-the-list check.
8625 - New socks command 'resolve', to let us shim gethostbyname()
8627 - A 'tor_resolve' script to access the socks resolve functionality.
8628 - A new socks-extensions.txt doc file to describe our
8629 interpretation and extensions to the socks protocols.
8630 - Add a ContactInfo option, which gets published in descriptor.
8631 - Write tor version at the top of each log file
8632 - New docs in the tarball:
8634 - Document that you should proxy your SSL traffic too.
8635 - Log a warning if the user uses an unsafe socks variant, so people
8636 are more likely to learn about privoxy or socat.
8637 - Log a warning if you're running an unverified server, to let you
8638 know you might want to get it verified.
8639 - Change the default exit policy to reject the default edonkey,
8640 kazaa, gnutella ports.
8641 - Add replace_file() to util.[ch] to handle win32's rename().
8642 - Publish OR uptime in descriptor (and thus in directory) too.
8643 - Remember used bandwidth (both in and out), and publish 15-minute
8644 snapshots for the past day into our descriptor.
8645 - Be more aggressive about trying to make circuits when the network
8646 has changed (e.g. when you unsuspend your laptop).
8647 - Check for time skew on http headers; report date in response to
8649 - If the entrynode config line has only one node, don't pick it as
8651 - Add strict{entry|exit}nodes config options. If set to 1, then
8652 we refuse to build circuits that don't include the specified entry
8654 - OutboundBindAddress config option, to bind to a specific
8655 IP address for outgoing connect()s.
8656 - End truncated log entries (e.g. directories) with "[truncated]".
8659 Changes in version 0.0.7.3 - 2004-08-12
8660 o Stop dnsworkers from triggering an assert failure when you
8661 ask them to resolve the host "".
8664 Changes in version 0.0.7.2 - 2004-07-07
8665 o A better fix for the 0.0.0.0 problem, that will hopefully
8666 eliminate the remaining related assertion failures.
8669 Changes in version 0.0.7.1 - 2004-07-04
8670 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8671 since internally we use 0.0.0.0 to signify "not yet resolved".
8674 Changes in version 0.0.7 - 2004-06-07
8675 o Fixes for crashes and other obnoxious bugs:
8676 - Fix an epipe bug: sometimes when directory connections failed
8677 to connect, we would give them a chance to flush before closing
8679 - When we detached from a circuit because of resolvefailed, we
8680 would immediately try the same circuit twice more, and then
8681 give up on the resolve thinking we'd tried three different
8683 - Limit the number of intro circuits we'll attempt to build for a
8684 hidden service per 15-minute period.
8685 - Check recommended-software string *early*, before actually parsing
8686 the directory. Thus we can detect an obsolete version and exit,
8687 even if the new directory format doesn't parse.
8688 o Fixes for security bugs:
8689 - Remember which nodes are dirservers when you startup, and if a
8690 random OR enables his dirport, don't automatically assume he's
8691 a trusted dirserver.
8693 - Directory connections were asking the wrong poll socket to
8694 start writing, and not asking themselves to start writing.
8695 - When we detached from a circuit because we sent a begin but
8696 didn't get a connected, we would use it again the first time;
8697 but after that we would correctly switch to a different one.
8698 - Stop warning when the first onion decrypt attempt fails; they
8699 will sometimes legitimately fail now that we rotate keys.
8700 - Override unaligned-access-ok check when $host_cpu is ia64 or
8701 arm. Apparently they allow it but the kernel whines.
8702 - Dirservers try to reconnect periodically too, in case connections
8704 - Fix some memory leaks in directory servers.
8705 - Allow backslash in Win32 filenames.
8706 - Made Tor build complain-free on FreeBSD, hopefully without
8707 breaking other BSD builds. We'll see.
8708 - Check directory signatures based on name of signer, not on whom
8709 we got the directory from. This will let us cache directories more
8711 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8714 - Doxygen markup on all functions and global variables.
8715 - Make directory functions update routerlist, not replace it. So
8716 now directory disagreements are not so critical a problem.
8717 - Remove the upper limit on number of descriptors in a dirserver's
8718 directory (not that we were anywhere close).
8719 - Allow multiple logfiles at different severity ranges.
8720 - Allow *BindAddress to specify ":port" rather than setting *Port
8721 separately. Allow multiple instances of each BindAddress config
8722 option, so you can bind to multiple interfaces if you want.
8723 - Allow multiple exit policy lines, which are processed in order.
8724 Now we don't need that huge line with all the commas in it.
8725 - Enable accept/reject policies on SOCKS connections, so you can bind
8726 to 0.0.0.0 but still control who can use your OP.
8727 - Updated the man page to reflect these features.
8730 Changes in version 0.0.6.2 - 2004-05-16
8731 o Our integrity-checking digest was checking only the most recent cell,
8732 not the previous cells like we'd thought.
8733 Thanks to Stefan Mark for finding the flaw!
8736 Changes in version 0.0.6.1 - 2004-05-06
8737 o Fix two bugs in our AES counter-mode implementation (this affected
8738 onion-level stream encryption, but not TLS-level). It turns
8739 out we were doing something much more akin to a 16-character
8740 polyalphabetic cipher. Oops.
8741 Thanks to Stefan Mark for finding the flaw!
8742 o Retire moria3 as a directory server, and add tor26 as a directory
8746 Changes in version 0.0.6 - 2004-05-02
8748 - Hidden services and rendezvous points are implemented. Go to
8749 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8750 hidden services. (This only works via a socks4a proxy such as
8751 Privoxy, and currently it's quite slow.)
8752 - We now rotate link (tls context) keys and onion keys.
8753 - CREATE cells now include oaep padding, so you can tell
8754 if you decrypted them correctly.
8755 - Retry stream correctly when we fail to connect because of
8756 exit-policy-reject (should try another) or can't-resolve-address.
8757 - When we hup a dirserver and we've *removed* a server from the
8758 approved-routers list, now we remove that server from the
8759 in-memory directories too.
8760 - Add bandwidthburst to server descriptor.
8761 - Directories now say which dirserver signed them.
8762 - Use a tor_assert macro that logs failed assertions too.
8763 - Since we don't support truncateds much, don't bother sending them;
8764 just close the circ.
8765 - Fetch randomness from /dev/urandom better (not via fopen/fread)
8766 - Better debugging for tls errors
8767 - Set Content-Type on the directory and hidserv descriptor.
8768 - Remove IVs from cipher code, since AES-ctr has none.
8770 - Fix an assert trigger for exit nodes that's been plaguing us since
8771 the days of 0.0.2prexx (thanks weasel!)
8772 - Fix a bug where we were closing tls connections intermittently.
8773 It turns out openssl keeps its errors around -- so if an error
8774 happens, and you don't ask about it, and then another openssl
8775 operation happens and succeeds, and you ask if there was an error,
8776 it tells you about the first error.
8777 - Fix a bug that's been lurking since 27 may 03 (!)
8778 When passing back a destroy cell, we would use the wrong circ id.
8779 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
8780 - Some versions of openssl have an SSL_pending function that erroneously
8781 returns bytes when there is a non-application record pending.
8782 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8783 o We were using an array of length zero in a few places.
8784 o Win32's gethostbyname can't resolve an IP to an IP.
8785 o Win32's close can't close a socket.
8786 o Handle windows socket errors correctly.
8788 - check for <sys/limits.h> so we build on FreeBSD again, and
8789 <machine/limits.h> for NetBSD.
8792 Changes in version 0.0.5 - 2004-03-30
8793 o Install torrc as torrc.sample -- we no longer clobber your
8795 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8796 o Only build circuits after we've fetched the directory: clients were
8797 using only the directory servers before they'd fetched a directory.
8798 This also means longer startup time; so it goes.
8799 o Fix an assert trigger where an OP would fail to handshake, and we'd
8800 expect it to have a nickname.
8801 o Work around a tsocks bug: do a socks reject when AP connection dies
8802 early, else tsocks goes into an infinite loop.
8803 o Hold socks connection open until reply is flushed (if possible)
8804 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8805 the dns farm to do it.
8806 o Fix c99 aliasing warnings in rephist.c
8807 o Don't include server descriptors that are older than 24 hours in the
8809 o Give socks 'reject' replies their whole 15s to attempt to flush,
8810 rather than seeing the 60s timeout and assuming the flush had failed.
8811 o Clean automake droppings from the cvs repository
8812 o Add in a 'notice' log level for things the operator should hear
8813 but that aren't warnings
8816 Changes in version 0.0.4 - 2004-03-26
8817 o When connecting to a dirserver or OR and the network is down,
8821 Changes in version 0.0.3 - 2004-03-26
8822 o Warn and fail if server chose a nickname with illegal characters
8823 o Port to Solaris and Sparc:
8824 - include missing header fcntl.h
8825 - have autoconf find -lsocket -lnsl automatically
8826 - deal with hardware word alignment
8827 - make uname() work (solaris has a different return convention)
8828 - switch from using signal() to sigaction()
8829 o Preliminary work on reputation system:
8830 - Keep statistics on success/fail of connect attempts; they're published
8831 by kill -USR1 currently.
8832 - Add a RunTesting option to try to learn link state by creating test
8833 circuits, even when SocksPort is off.
8834 - Remove unused open circuits when there are too many.
8837 Changes in version 0.0.2 - 2004-03-19
8838 - Include strlcpy and strlcat for safer string ops
8839 - define INADDR_NONE so we compile (but still not run) on solaris
8842 Changes in version 0.0.2pre27 - 2004-03-14
8844 - Allow internal tor networks (we were rejecting internal IPs,
8845 now we allow them if they're set explicitly).
8846 - And fix a few endian issues.
8849 Changes in version 0.0.2pre26 - 2004-03-14
8851 - If a stream times out after 15s without a connected cell, don't
8852 try that circuit again: try a new one.
8853 - Retry streams at most 4 times. Then give up.
8854 - When a dirserver gets a descriptor from an unknown router, it
8855 logs its fingerprint (so the dirserver operator can choose to
8856 accept it even without mail from the server operator).
8857 - Inform unapproved servers when we reject their descriptors.
8858 - Make tor build on Windows again. It works as a client, who knows
8860 - Clearer instructions in the torrc for how to set up a server.
8861 - Be more efficient about reading fd's when our global token bucket
8862 (used for rate limiting) becomes empty.
8864 - Stop asserting that computers always go forward in time. It's
8866 - When we sent a cell (e.g. destroy) and then marked an OR connection
8867 expired, we might close it before finishing a flush if the other
8868 side isn't reading right then.
8869 - Don't allow dirservers to start if they haven't defined
8871 - We were caching transient dns failures. Oops.
8872 - Prevent servers from publishing an internal IP as their address.
8873 - Address a strcat vulnerability in circuit.c
8876 Changes in version 0.0.2pre25 - 2004-03-04
8878 - Put the OR's IP in its router descriptor, not its fqdn. That way
8879 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8882 - If the user typed in an address that didn't resolve, the server
8886 Changes in version 0.0.2pre24 - 2004-03-03
8888 - Fix an assertion failure in dns.c, where we were trying to dequeue
8889 a pending dns resolve even if it wasn't pending
8890 - Fix a spurious socks5 warning about still trying to write after the
8891 connection is finished.
8892 - Hold certain marked_for_close connections open until they're finished
8893 flushing, rather than losing bytes by closing them too early.
8894 - Correctly report the reason for ending a stream
8895 - Remove some duplicate calls to connection_mark_for_close
8896 - Put switch_id and start_daemon earlier in the boot sequence, so it
8897 will actually try to chdir() to options.DataDirectory
8898 - Make 'make test' exit(1) if a test fails; fix some unit tests
8899 - Make tor fail when you use a config option it doesn't know about,
8900 rather than warn and continue.
8901 - Make --version work
8902 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8905 Changes in version 0.0.2pre23 - 2004-02-29
8907 - Print a statement when the first circ is finished, so the user
8909 - If a relay cell is unrecognized at the end of the circuit,
8910 send back a destroy. (So attacks to mutate cells are more
8912 - New config option 'excludenodes' to avoid certain nodes for circuits.
8913 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8914 so you can collect coredumps there.
8916 - Fix a bug in tls flushing where sometimes data got wedged and
8917 didn't flush until more data got sent. Hopefully this bug was
8918 a big factor in the random delays we were seeing.
8919 - Make 'connected' cells include the resolved IP, so the client
8920 dns cache actually gets populated.
8921 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8922 - When we time-out on a stream and detach from the circuit, send an
8923 end cell down it first.
8924 - Only warn about an unknown router (in exitnodes, entrynodes,
8925 excludenodes) after we've fetched a directory.
8928 Changes in version 0.0.2pre22 - 2004-02-26
8930 - Servers publish less revealing uname information in descriptors.
8931 - More memory tracking and assertions, to crash more usefully when
8933 - If the default torrc isn't there, just use some default defaults.
8934 Plus provide an internal dirservers file if they don't have one.
8935 - When the user tries to use Tor as an http proxy, give them an http
8936 501 failure explaining that we're a socks proxy.
8937 - Dump a new router.desc on hup, to help confused people who change
8938 their exit policies and then wonder why router.desc doesn't reflect
8940 - Clean up the generic tor.sh init script that we ship with.
8942 - If the exit stream is pending on the resolve, and a destroy arrives,
8943 then the stream wasn't getting removed from the pending list. I
8944 think this was the one causing recent server crashes.
8945 - Use a more robust poll on OSX 10.3, since their poll is flaky.
8946 - When it couldn't resolve any dirservers, it was useless from then on.
8947 Now it reloads the RouterFile (or default dirservers) if it has no
8949 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
8950 many users don't even *have* a /usr/local/sbin/.
8953 Changes in version 0.0.2pre21 - 2004-02-18
8955 - There's a ChangeLog file that actually reflects the changelog.
8956 - There's a 'torify' wrapper script, with an accompanying
8957 tor-tsocks.conf, that simplifies the process of using tsocks for
8958 tor. It even has a man page.
8959 - The tor binary gets installed to sbin rather than bin now.
8960 - Retry streams where the connected cell hasn't arrived in 15 seconds
8961 - Clean up exit policy handling -- get the default out of the torrc,
8962 so we can update it without forcing each server operator to fix
8964 - Allow imaps and pop3s in default exit policy
8966 - Prevent picking middleman nodes as the last node in the circuit
8969 Changes in version 0.0.2pre20 - 2004-01-30
8971 - We now have a deb package, and it's in debian unstable. Go to
8973 - I've split the TotalBandwidth option into BandwidthRate (how many
8974 bytes per second you want to allow, long-term) and
8975 BandwidthBurst (how many bytes you will allow at once before the cap
8976 kicks in). This better token bucket approach lets you, say, set
8977 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
8978 performance while not exceeding your monthly bandwidth quota.
8979 - Push out a tls record's worth of data once you've got it, rather
8980 than waiting until you've read everything waiting to be read. This
8981 may improve performance by pipelining better. We'll see.
8982 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
8983 from failed circuits (if they haven't been connected yet) and attach
8985 - Expire old streams that haven't managed to connect. Some day we'll
8986 have them reattach to new circuits instead.
8989 - Fix several memory leaks that were causing servers to become bloated
8991 - Fix a few very rare assert triggers. A few more remain.
8992 - Setuid to User _before_ complaining about running as root.
8995 Changes in version 0.0.2pre19 - 2004-01-07
8997 - Fix deadlock condition in dns farm. We were telling a child to die by
8998 closing the parent's file descriptor to him. But newer children were
8999 inheriting the open file descriptor from the parent, and since they
9000 weren't closing it, the socket never closed, so the child never read
9001 eof, so he never knew to exit. Similarly, dns workers were holding
9002 open other sockets, leading to all sorts of chaos.
9003 - New cleaner daemon() code for forking and backgrounding.
9004 - If you log to a file, it now prints an entry at the top of the
9005 logfile so you know it's working.
9006 - The onionskin challenge length was 30 bytes longer than necessary.
9007 - Started to patch up the spec so it's not quite so out of date.
9010 Changes in version 0.0.2pre18 - 2004-01-02
9012 - Fix endian issues with the 'integrity' field in the relay header.
9013 - Fix a potential bug where connections in state
9014 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9017 Changes in version 0.0.2pre17 - 2003-12-30
9019 - Made --debuglogfile (or any second log file, actually) work.
9020 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9021 adversary could force us into an infinite loop.
9024 - Each onionskin handshake now includes a hash of the computed key,
9025 to prove the server's identity and help perfect forward secrecy.
9026 - Changed cell size from 256 to 512 bytes (working toward compatibility
9028 - Changed cell length to 2 bytes, and moved it to the relay header.
9029 - Implemented end-to-end integrity checking for the payloads of
9031 - Separated streamid from 'recognized' (otherwise circuits will get
9032 messed up when we try to have streams exit from the middle). We
9033 use the integrity-checking to confirm that a cell is addressed to
9035 - Randomize the initial circid and streamid values, so an adversary who
9036 breaks into a node can't learn how many circuits or streams have
9040 Changes in version 0.0.2pre16 - 2003-12-14
9042 - Fixed a bug that made HUP trigger an assert
9043 - Fixed a bug where a circuit that immediately failed wasn't being
9044 counted as a failed circuit in counting retries.
9047 - Now we close the circuit when we get a truncated cell: otherwise we're
9048 open to an anonymity attack where a bad node in the path truncates
9049 the circuit and then we open streams at him.
9050 - Add port ranges to exit policies
9051 - Add a conservative default exit policy
9052 - Warn if you're running tor as root
9053 - on HUP, retry OR connections and close/rebind listeners
9054 - options.EntryNodes: try these nodes first when picking the first node
9055 - options.ExitNodes: if your best choices happen to include any of
9056 your preferred exit nodes, you choose among just those preferred
9058 - options.ExcludedNodes: nodes that are never picked in path building
9061 Changes in version 0.0.2pre15 - 2003-12-03
9062 o Robustness and bugfixes:
9063 - Sometimes clients would cache incorrect DNS resolves, which would
9064 really screw things up.
9065 - An OP that goes offline would slowly leak all its sockets and stop
9067 - A wide variety of bugfixes in exit node selection, exit policy
9068 handling, and processing pending streams when a new circuit is
9070 - Pick nodes for a path only from those the directory says are up
9071 - Choose randomly from all running dirservers, not always the first one
9072 - Increase allowed http header size for directory fetch.
9073 - Stop writing to stderr (if we're daemonized it will be closed).
9074 - Enable -g always, so cores will be more useful to me.
9075 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9078 - Wrote a man page. It lists commonly used options.
9081 - Change default loglevel to warn.
9082 - Make PidFile default to null rather than littering in your CWD.
9083 - OnionRouter config option is now obsolete. Instead it just checks
9085 - Moved to a single unified torrc file for both clients and servers.
9088 Changes in version 0.0.2pre14 - 2003-11-29
9089 o Robustness and bugfixes:
9090 - Force the admin to make the DataDirectory himself
9091 - to get ownership/permissions right
9092 - so clients no longer make a DataDirectory and then never use it
9093 - fix bug where a client who was offline for 45 minutes would never
9094 pull down a directory again
9095 - fix (or at least hide really well) the dns assert bug that was
9096 causing server crashes
9097 - warnings and improved robustness wrt clockskew for certs
9098 - use the native daemon(3) to daemonize, when available
9099 - exit if bind() fails
9100 - exit if neither socksport nor orport is defined
9101 - include our own tor_timegm (Win32 doesn't have its own)
9102 - bugfix for win32 with lots of connections
9103 - fix minor bias in PRNG
9104 - make dirserver more robust to corrupt cached directory
9107 - Wrote the design document (woo)
9109 o Circuit building and exit policies:
9110 - Circuits no longer try to use nodes that the directory has told them
9112 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9113 bitcounts (18.0.0.0/8).
9114 - Make AP connections standby for a circuit if no suitable circuit
9115 exists, rather than failing
9116 - Circuits choose exit node based on addr/port, exit policies, and
9117 which AP connections are standing by
9118 - Bump min pathlen from 2 to 3
9119 - Relay end cells have a payload to describe why the stream ended.
9120 - If the stream failed because of exit policy, try again with a new
9122 - Clients have a dns cache to remember resolved addresses.
9123 - Notice more quickly when we have no working circuits
9126 - APPort is now called SocksPort
9127 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9129 - RecommendedVersions is now a config variable rather than
9130 hardcoded (for dirservers)
9131 - Reloads config on HUP
9132 - Usage info on -h or --help
9133 - If you set User and Group config vars, it'll setu/gid to them.
9135 Changes in version 0.0.2pre13 - 2003-10-19
9136 o General stability:
9137 - SSL_write no longer fails when it returns WANTWRITE and the number
9138 of bytes in the buf has changed by the next SSL_write call.
9139 - Fix segfault fetching directory when network is down
9140 - Fix a variety of minor memory leaks
9141 - Dirservers reload the fingerprints file on HUP, so I don't have
9142 to take down the network when I approve a new router
9143 - Default server config file has explicit Address line to specify fqdn
9146 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9147 - Make listener connections not ever alloc bufs
9149 o Autoconf improvements:
9150 - don't clobber an external CFLAGS in ./configure
9151 - Make install now works
9152 - create var/lib/tor on make install
9153 - autocreate a tor.sh initscript to help distribs
9154 - autocreate the torrc and sample-server-torrc with correct paths
9156 o Log files and Daemonizing now work:
9157 - If --DebugLogFile is specified, log to it at -l debug
9158 - If --LogFile is specified, use it instead of commandline
9159 - If --RunAsDaemon is set, tor forks and backgrounds on startup