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.19 - 2013-12-11
7 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
8 (1986-2013). Aaron worked on diverse projects including helping to guide
9 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
10 transparency to the U.S government's PACER documents, and contributing
11 design and development for Tor and Tor2Web. Aaron was one of the latest
12 martyrs in our collective fight for civil liberties and human rights,
13 and his death is all the more painful because he was one of us.
15 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16 a new circuit handshake and link encryption that use ECC to provide
17 better security and efficiency; makes relays better manage circuit
18 creation requests; uses "directory guards" to reduce client enumeration
19 risks; makes bridges collect and report statistics about the pluggable
20 transports they support; cleans up and improves our geoip database;
21 gets much closer to IPv6 support for clients, bridges, and relays; makes
22 directory authorities use measured bandwidths rather than advertised
23 ones when computing flags and thresholds; disables client-side DNS
24 caching to reduce tracking risks; and fixes a big bug in bridge
25 reachability testing. This release introduces two new design
26 abstractions in the code: a new "channel" abstraction between circuits
27 and or_connections to allow for implementing alternate relay-to-relay
28 transports, and a new "circuitmux" abstraction storing the queue of
29 circuits for a channel. The release also includes many stability,
30 security, and privacy fixes.
32 o Major features (new circuit handshake):
33 - Tor now supports a new circuit extension handshake designed by Ian
34 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
35 circuit extension handshake, later called "TAP", was a bit slow
36 (especially on the relay side), had a fragile security proof, and
37 used weaker keys than we'd now prefer. The new circuit handshake
38 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
39 function, making it significantly more secure than the older
40 handshake, and significantly faster. Tor can use one of two built-in
41 pure-C curve25519-donna implementations by Adam Langley, or it
42 can link against the "nacl" library for a tuned version if present.
44 The built-in version is very fast for 64-bit systems when building
45 with GCC. The built-in 32-bit version is still faster than the
46 old TAP protocol, but using libnacl is better on most such hosts.
48 Implements proposal 216; closes ticket 7202.
50 o Major features (better link encryption):
51 - Relays can now enable the ECDHE TLS ciphersuites when available
52 and appropriate. These ciphersuites let us negotiate forward-secure
53 TLS secret keys more safely and more efficiently than with our
54 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
55 public relays prefer the (faster) P224 group, and bridges prefer
56 the (more common) P256 group; you can override this with the
59 This feature requires clients running 0.2.3.17-beta or later,
60 and requires both sides to be running OpenSSL 1.0.0 or later
61 with ECC support. OpenSSL 1.0.1, with the compile-time option
62 "enable-ec_nistp_64_gcc_128", is highly recommended.
64 Implements the relay side of proposal 198; closes ticket 7200.
66 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
67 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
68 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
69 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
70 them to solve bug 6033.)
72 o Major features (relay performance):
73 - Instead of limiting the number of queued onionskins (aka circuit
74 create requests) to a fixed, hard-to-configure number, we limit
75 the size of the queue based on how many we expect to be able to
76 process in a given amount of time. We estimate the time it will
77 take to process an onionskin based on average processing time
78 of previous onionskins. Closes ticket 7291. You'll never have to
79 configure MaxOnionsPending again.
80 - Relays process the new "NTor" circuit-level handshake requests
81 with higher priority than the old "TAP" circuit-level handshake
82 requests. We still process some TAP requests to not totally starve
83 0.2.3 clients when NTor becomes popular. A new consensus parameter
84 "NumNTorsPerTAP" lets us tune the balance later if we need to.
85 Implements ticket 9574.
87 o Major features (client bootstrapping resilience):
88 - Add a new "FallbackDir" torrc option to use when we can't use
89 a directory mirror from the consensus (either because we lack a
90 consensus, or because they're all down). Currently, all authorities
91 are fallbacks by default, and there are no other default fallbacks,
92 but that will change. This option will allow us to give clients a
93 longer list of servers to try to get a consensus from when first
94 connecting to the Tor network, and thereby reduce load on the
95 directory authorities. Implements proposal 206, "Preconfigured
96 directory sources for bootstrapping". We also removed the old
97 "FallbackNetworkstatus" option, since we never got it working well
98 enough to use it. Closes bug 572.
99 - If we have no circuits open, use a relaxed timeout (the
100 95th-percentile cutoff) until a circuit succeeds. This heuristic
101 should allow Tor to succeed at building circuits even when the
102 network connection drastically changes. Should help with bug 3443.
104 o Major features (use of guards):
105 - Support directory guards (proposal 207): when possible, clients now
106 use their entry guards for non-anonymous directory requests. This
107 can help prevent client enumeration. Note that this behavior only
108 works when we have a usable consensus directory, and when options
109 about what to download are more or less standard. In the future we
110 should re-bootstrap from our guards, rather than re-bootstrapping
111 from the preconfigured list of directory sources that ships with
112 Tor. Resolves ticket 6526.
113 - Raise the default time that a client keeps an entry guard from
114 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
115 2012 paper. (We would make it even longer, but we need better client
116 load balancing first.) Also, make the guard lifetime controllable
117 via a new GuardLifetime torrc option and a GuardLifetime consensus
118 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
120 o Major features (bridges with pluggable transports):
121 - Bridges now report the pluggable transports they support to the
122 bridge authority, so it can pass the supported transports on to
123 bridgedb and/or eventually do reachability testing. Implements
125 - Automatically forward the TCP ports of pluggable transport
126 proxies using tor-fw-helper if PortForwarding is enabled. Implements
129 o Major features (geoip database):
130 - Maxmind began labelling Tor relays as being in country "A1",
131 which breaks by-country node selection inside Tor. Now we use a
132 script to replace "A1" ("Anonymous Proxy") entries in our geoip
133 file with real country codes. This script fixes about 90% of "A1"
134 entries automatically and uses manual country code assignments to
135 fix the remaining 10%. See src/config/README.geoip for details.
137 - Add GeoIP database for IPv6 addresses. The new config option
139 - Update to the October 2 2013 Maxmind GeoLite Country database.
141 o Major features (IPv6):
142 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
143 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
144 to happen. Implements ticket 5535.
145 - All kind of relays, not just bridges, can now advertise an IPv6
146 OR port. Implements ticket 6362.
147 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
148 connectivity, then set the IPv6Exit flag to 1. Also make sure your
149 exit policy reads as you would like: the address * applies to all
150 address families, whereas *4 is IPv4 address only, and *6 is IPv6
151 addresses only. On the client side, you'll need to wait for enough
152 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
153 and use Socks5. Closes ticket 5547, implements proposal 117 as
154 revised in proposal 208.
155 - Bridge authorities now accept IPv6 bridge addresses and include
156 them in network status documents. Implements ticket 5534.
157 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
159 o Major features (directory authorities):
160 - Directory authorities now prefer using measured bandwidths to
161 advertised ones when computing flags and thresholds. Resolves
163 - Directory authorities that vote measured bandwidths about more
164 than a threshold number of relays now treat relays with
165 unmeasured bandwidths as having bandwidth 0 when computing their
166 flags. Resolves ticket 8435.
167 - Directory authorities now support a new consensus method (17)
168 where they cap the published bandwidth of relays for which
169 insufficient bandwidth measurements exist. Fixes part of bug 2286.
170 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
171 serve any v2 directory information. Now we can test disabling the
172 old deprecated v2 directory format, and see whether doing so has
173 any effect on network load. Begins to fix bug 6783.
175 o Major features (build and portability):
176 - Switch to a nonrecursive Makefile structure. Now instead of each
177 Makefile.am invoking other Makefile.am's, there is a master
178 Makefile.am that includes the others. This change makes our build
179 process slightly more maintainable, and improves parallelism for
180 building with make -j. Original patch by Stewart Smith; various
181 fixes by Jim Meyering.
182 - Where available, we now use automake's "silent" make rules by
183 default, so that warnings are easier to spot. You can get the old
184 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
185 - Resume building correctly with MSVC and Makefile.nmake. This patch
186 resolves numerous bugs and fixes reported by ultramage, including
187 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
190 - Switch to a completely time-invariant approach for picking nodes
191 weighted by bandwidth. Our old approach would run through the
192 part of the loop after it had made its choice slightly slower
193 than it ran through the part of the loop before it had made its
194 choice. Addresses ticket 6538.
195 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
196 by tor2web clients allows hidden services to identify tor2web
197 clients through their repeated selection of the same rendezvous
198 and introduction point circuit endpoints (their guards). Resolves
201 o Major bugfixes (relay denial of service):
202 - When we have too much memory queued in circuits (according to a new
203 MaxMemInCellQueues option), close the circuits that have the oldest
204 queued cells, on the theory that those are most responsible for
205 us running low on memory. This prevents us from running out of
206 memory as a relay if circuits fill up faster than they can be
207 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
208 Tor. This bug is a further fix beyond bug 6252, whose fix was
209 merged into 0.2.3.21-rc.
210 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
211 ID: these could be used to create unexpected streams and circuits
212 which would count as "present" to some parts of Tor but "absent"
213 to others, leading to zombie circuits and streams or to a bandwidth
214 denial-of-service. Fixes bug 7889; bugfix on every released version
215 of Tor. Reported by "oftc_must_be_destroyed".
216 - Avoid a bug where our response to TLS renegotiation under certain
217 network conditions could lead to a busy-loop, with 100% CPU
218 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
220 o Major bugfixes (asserts, crashes, leaks):
221 - Prevent the get_freelists() function from running off the end of
222 the list of freelists if it somehow gets an unrecognized
223 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
225 - Avoid a memory leak where we would leak a consensus body when we
226 find that a consensus which we couldn't previously verify due to
227 missing certificates is now verifiable. Fixes bug 8719; bugfix
229 - If we are unable to save a microdescriptor to the journal, do not
230 drop it from memory and then reattempt downloading it. Fixes bug
231 9645; bugfix on 0.2.2.6-alpha.
232 - Fix an assertion failure that would occur when disabling the
233 ORPort setting on a running Tor process while accounting was
234 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
235 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
236 when an exit connection with optimistic data succeeds immediately
237 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
239 - Fix a memory leak that would occur whenever a configuration
240 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
242 o Major bugfixes (relay rate limiting):
243 - When a TLS write is partially successful but incomplete, remember
244 that the flushed part has been flushed, and notice that bytes were
245 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
246 bugfix on Tor 0.1.0.5-rc.
247 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
248 to 1GB/1GB. The previous defaults were intended to be "basically
249 infinite", but it turns out they're now limiting our 100mbit+
250 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
251 last time we raised it).
252 - No longer stop reading or writing on cpuworker connections when
253 our rate limiting buckets go empty. Now we should handle circuit
254 handshake requests more promptly. Resolves bug 9731.
256 o Major bugfixes (client-side privacy):
257 - When we mark a circuit as unusable for new circuits, have it
258 continue to be unusable for new circuits even if MaxCircuitDirtiness
259 is increased too much at the wrong time, or the system clock jumps
260 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
261 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
262 which have resolved to internal addresses") is set, apply that
263 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
264 - When an exit relay rejects a stream with reason "exit policy", but
265 we only know an exit policy summary (e.g. from the microdesc
266 consensus) for it, do not mark the relay as useless for all exiting.
267 Instead, mark just the circuit as unsuitable for that particular
268 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
270 o Major bugfixes (stream isolation):
271 - Allow applications to get proper stream isolation with
272 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
273 username/password authentication also offer "no authentication". Tor
274 had previously preferred "no authentication", so the applications
275 never actually sent Tor their auth details. Now Tor selects
276 username/password authentication if it's offered. You can disable
277 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
278 bug 8117; bugfix on 0.2.3.3-alpha.
279 - Follow the socks5 protocol when offering username/password
280 authentication. The fix for bug 8117 exposed this bug, and it
281 turns out real-world applications like Pidgin do care. Bugfix on
282 0.2.3.2-alpha; fixes bug 8879.
284 o Major bugfixes (client circuit building):
285 - Alter circuit build timeout measurement to start at the point
286 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
287 initialization). This should make our timeout measurements more
288 uniform. Previously, we were sometimes including ORconn setup time
289 in our circuit build time measurements. Should resolve bug 3443.
290 - If the circuit build timeout logic is disabled (via the consensus,
291 or because we are an authority), then don't build testing circuits.
292 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
294 o Major bugfixes (client-side DNS):
295 - Turn off the client-side DNS cache by default. Updating and using
296 the DNS cache is now configurable on a per-client-port
297 level. SOCKSPort, DNSPort, etc lines may now contain
298 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
299 cache these types of DNS answers when we receive them from an
300 exit node in response to an application request on this port, and
301 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
302 cached DNS answers of these types, we shouldn't use them. It's
303 potentially risky to use cached DNS answers at the client, since
304 doing so can indicate to one exit what answers we've gotten
305 for DNS lookups in the past. With IPv6, this becomes especially
306 problematic. Using cached DNS answers for requests on the same
307 circuit would present less linkability risk, since all traffic
308 on a circuit is already linkable, but it would also provide
309 little performance benefit: the exit node caches DNS replies
310 too. Implements a simplified version of Proposal 205. Implements
313 o Major bugfixes (hidden service privacy):
314 - Limit hidden service descriptors to at most ten introduction
315 points, to slow one kind of guard enumeration. Fixes bug 9002;
316 bugfix on 0.1.1.11-alpha.
318 o Major bugfixes (directory fetching):
319 - If the time to download the next old-style networkstatus is in
320 the future, do not decline to consider whether to download the
321 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
323 - We used to always request authority certificates by identity digest,
324 meaning we'd get the newest one even when we wanted one with a
325 different signing key. Then we would complain about being given
326 a certificate we already had, and never get the one we really
327 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
328 resource to request the one we want. Fixes bug 5595; bugfix on
331 o Major bugfixes (bridge reachability):
332 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
333 previously they did not, which prevented them from receiving
334 successful connections from relays for self-test or bandwidth
335 testing. Also, when a relay is extending a circuit to a bridge,
336 it needs to send a NETINFO cell, even when the bridge hasn't sent
337 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
339 o Major bugfixes (control interface):
340 - When receiving a new configuration file via the control port's
341 LOADCONF command, do not treat the defaults file as absent.
342 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
344 o Major bugfixes (directory authorities):
345 - Stop marking every relay as having been down for one hour every
346 time we restart a directory authority. These artificial downtimes
347 were messing with our Stable and Guard flag calculations. Fixes
348 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
349 - When computing directory thresholds, ignore any rejected-as-sybil
350 nodes during the computation so that they can't influence Fast,
351 Guard, etc. (We should have done this for proposal 109.) Fixes
353 - When marking a node as a likely sybil, reset its uptime metrics
354 to zero, so that it cannot time towards getting marked as Guard,
355 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
357 - Fix a bug in the voting algorithm that could yield incorrect results
358 when a non-naming authority declared too many flags. Fixes bug 9200;
359 bugfix on 0.2.0.3-alpha.
361 o Internal abstraction features:
362 - Introduce new channel_t abstraction between circuits and
363 or_connection_t to allow for implementing alternate OR-to-OR
364 transports. A channel_t is an abstract object which can either be a
365 cell-bearing channel, which is responsible for authenticating and
366 handshaking with the remote OR and transmitting cells to and from
367 it, or a listening channel, which spawns new cell-bearing channels
368 at the request of remote ORs. Implements part of ticket 6465.
369 - Make a channel_tls_t subclass of channel_t, adapting it to the
370 existing or_connection_t code. The V2/V3 protocol handshaking
371 code which formerly resided in command.c has been moved below the
372 channel_t abstraction layer and may be found in channeltls.c now.
373 Implements the rest of ticket 6465.
374 - Introduce new circuitmux_t storing the queue of circuits for
375 a channel; this encapsulates and abstracts the queue logic and
376 circuit selection policy, and allows the latter to be overridden
377 easily by switching out a policy object. The existing EWMA behavior
378 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
380 o New build requirements:
381 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
382 strongly recommended.
383 - Tor maintainers now require Automake version 1.9 or later to build
384 Tor from the Git repository. (Automake is not required when building
385 from a source distribution.)
387 o Minor features (protocol):
388 - No longer include the "opt" prefix when generating routerinfos
389 or v2 directories: it has been needless since Tor 0.1.2. Closes
391 - Reject EXTEND cells sent to nonexistent streams. According to the
392 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
393 we were only checking for stream IDs that were currently in use.
394 Found while hunting for more instances of bug 6271. Bugfix on
395 0.0.2pre8, which introduced incremental circuit construction.
396 - Tor relays and clients now support a better CREATE/EXTEND cell
397 format, allowing the sender to specify multiple address, identity,
398 and handshake types. Implements Robert Ransom's proposal 200;
400 - Reject as invalid most directory objects containing a NUL.
401 Belt-and-suspender fix for bug 8037.
403 o Minor features (security):
404 - Clear keys and key-derived material left on the stack in
405 rendservice.c and rendclient.c. Check return value of
406 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
407 These fixes should make us more forward-secure against cold-boot
408 attacks and the like. Fixes bug 2385.
409 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
410 Irix's random() only return 15 bits; Solaris's random() returns more
411 bits but its RAND_MAX says it only returns 15, and so on. Motivated
412 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
414 o Minor features (control protocol):
415 - Add a "GETINFO signal/names" control port command. Implements
417 - Provide default values for all options via "GETINFO config/defaults".
418 Implements ticket 4971.
419 - Allow an optional $ before the node identity digest in the
420 controller command GETINFO ns/id/<identity>, for consistency with
421 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
422 - Add CACHED keyword to ADDRMAP events in the control protocol
423 to indicate whether a DNS result will be cached or not. Resolves
425 - Generate bootstrapping status update events correctly when fetching
426 microdescriptors. Fixes bug 9927.
428 o Minor features (path selection):
429 - When deciding whether we have enough descriptors to build circuits,
430 instead of looking at raw relay counts, look at which fraction
431 of (bandwidth-weighted) paths we're able to build. This approach
432 keeps clients from building circuits if their paths are likely to
433 stand out statistically. The default fraction of paths needed is
434 taken from the consensus directory; you can override it with the
435 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
436 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
437 and we have GeoIP information, also exclude all nodes with unknown
438 countries "??" and "A1". This behavior is controlled by the
439 new GeoIPExcludeUnknown option: you can make such nodes always
440 excluded with "GeoIPExcludeUnknown 1", and disable the feature
441 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
442 gets you the default behavior. Implements feature 7706.
444 o Minor features (hidden services):
445 - Improve circuit build timeout handling for hidden services.
446 In particular: adjust build timeouts more accurately depending
447 upon the number of hop-RTTs that a particular circuit type
448 undergoes. Additionally, launch intro circuits in parallel
449 if they timeout, and take the first one to reply as valid.
450 - The Tor client now ignores sub-domain components of a .onion
451 address. This change makes HTTP "virtual" hosting
452 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
453 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
454 hosted on the same hidden service. Implements proposal 204.
455 - Enable Tor to read configuration, state, and key information from
456 a FIFO. Previously Tor would only read from files with a positive
457 stat.st_size. Code from meejah; fixes bug 6044.
459 o Minor features (clients):
460 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
461 microdescriptor-related dir requests, and only fall back to normal
462 descriptors if none of their bridges can handle microdescriptors
463 (as opposed to the fix in ticket 4013, which caused them to fall
464 back to normal descriptors if *any* of their bridges preferred
465 them). Resolves ticket 4994.
466 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
467 TCP ports to forward. In the past it only accepted two ports:
468 the ORPort and the DirPort.
470 o Minor features (protecting client timestamps):
471 - Clients no longer send timestamps in their NETINFO cells. These were
472 not used for anything, and they provided one small way for clients
473 to be distinguished from each other as they moved from network to
474 network or behind NAT. Implements part of proposal 222.
475 - Clients now round timestamps in INTRODUCE cells down to the nearest
476 10 minutes. If a new Support022HiddenServices option is set to 0, or
477 if it's set to "auto" and the feature is disabled in the consensus,
478 the timestamp is sent as 0 instead. Implements part of proposal 222.
479 - Stop sending timestamps in AUTHENTICATE cells. This is not such
480 a big deal from a security point of view, but it achieves no actual
481 good purpose, and isn't needed. Implements part of proposal 222.
482 - Reduce down accuracy of timestamps in hidden service descriptors.
483 Implements part of proposal 222.
485 o Minor features (bridges):
486 - Make bridge relays check once a minute for whether their IP
487 address has changed, rather than only every 15 minutes. Resolves
489 - Bridge statistics now count bridge clients connecting over IPv6:
490 bridge statistics files now list "bridge-ip-versions" and
491 extra-info documents list "geoip6-db-digest". The control protocol
492 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
493 implementation by "shkoo", addressing ticket 5055.
494 - Add a new torrc option "ServerTransportListenAddr" to let bridge
495 operators select the address where their pluggable transports will
496 listen for connections. Resolves ticket 7013.
497 - Randomize the lifetime of our SSL link certificate, so censors can't
498 use the static value for filtering Tor flows. Resolves ticket 8443;
499 related to ticket 4014 which was included in 0.2.2.33.
501 o Minor features (relays):
502 - Option OutboundBindAddress can be specified multiple times and
503 accepts IPv6 addresses. Resolves ticket 6876.
505 o Minor features (IPv6, client side):
506 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
507 prefer to hand out virtual IPv6 addresses, since there are more of
508 them and we can't run out. To override this behavior and make IPv4
509 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
510 or DNSPort you're using for resolving. Implements ticket 7571.
511 - AutomapHostsOnResolve responses are now randomized, to avoid
512 annoying situations where Tor is restarted and applications
513 connect to the wrong addresses.
514 - Never try more than 1000 times to pick a new virtual address when
515 AutomapHostsOnResolve is set. That's good enough so long as we
516 aren't close to handing out our entire virtual address space;
517 if you're getting there, it's best to switch to IPv6 virtual
520 o Minor features (IPv6, relay/authority side):
521 - New config option "AuthDirHasIPv6Connectivity 1" that directory
522 authorities should set if they have IPv6 connectivity and want to
523 do reachability tests for IPv6 relays. Implements feature 5974.
524 - A relay with an IPv6 OR port now sends that address in NETINFO
525 cells (in addition to its other address). Implements ticket 6364.
527 o Minor features (directory authorities):
528 - Directory authorities no long accept descriptors for any version of
529 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
530 These versions are insecure, unsupported, or both. Implements
532 - When directory authorities are computing thresholds for flags,
533 never let the threshold for the Fast flag fall below 4096
534 bytes. Also, do not consider nodes with extremely low bandwidths
535 when deciding thresholds for various directory flags. This change
536 should raise our threshold for Fast relays, possibly in turn
537 improving overall network performance; see ticket 1854. Resolves
539 - Directory authorities now include inside each vote a statement of
540 the performance thresholds they used when assigning flags.
541 Implements ticket 8151.
542 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
543 in directory authority votes to describe whether they have enough
544 measured bandwidths to ignore advertised (relay descriptor)
545 bandwidth claims. Resolves ticket 8711.
547 o Minor features (path bias detection):
548 - Path Use Bias: Perform separate accounting for successful circuit
549 use. Keep separate statistics on stream attempt rates versus stream
550 success rates for each guard. Provide configurable thresholds to
551 determine when to emit log messages or disable use of guards that
552 fail too many stream attempts. Resolves ticket 7802.
553 - Create three levels of Path Bias log messages, as opposed to just
554 two. These are configurable via consensus as well as via the torrc
555 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
556 The default values are 0.70, 0.50, and 0.30 respectively.
557 - Separate the log message levels from the decision to drop guards,
558 which also is available via torrc option PathBiasDropGuards.
559 PathBiasDropGuards still defaults to 0 (off).
560 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
561 in combination with PathBiasExtremeRate.
562 - Increase the default values for PathBiasScaleThreshold and
563 PathBiasCircThreshold from (200, 20) to (300, 150).
564 - Add in circuit usage accounting to path bias. If we try to use a
565 built circuit but fail for any reason, it counts as path bias.
566 Certain classes of circuits where the adversary gets to pick your
567 destination node are exempt from this accounting. Usage accounting
568 can be specifically disabled via consensus parameter or torrc.
569 - Convert all internal path bias state to double-precision floating
570 point, to avoid roundoff error and other issues.
571 - Only record path bias information for circuits that have completed
572 *two* hops. Assuming end-to-end tagging is the attack vector, this
573 makes us more resilient to ambient circuit failure without any
574 detection capability loss.
576 o Minor features (build):
577 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
578 dhill. Resolves ticket 6982.
579 - Compile on win64 using mingw64. Fixes bug 7260; patches from
581 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
582 separate error codes; or at least, don't break for that reason.
583 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
585 o Build improvements (autotools):
586 - Warn if building on a platform with an unsigned time_t: there
587 are too many places where Tor currently assumes that time_t can
588 hold negative values. We'd like to fix them all, but probably
590 - Do not report status verbosely from autogen.sh unless the -v flag
591 is specified. Fixes issue 4664. Patch from Onizuka.
592 - Detect and reject attempts to build Tor with threading support
593 when OpenSSL has been compiled without threading support.
595 - Try to detect if we are ever building on a platform where
596 memset(...,0,...) does not set the value of a double to 0.0. Such
597 platforms are permitted by the C standard, though in practice
598 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
599 currently support them, but it's better to detect them and fail
600 than to perform erroneously.
601 - We no longer warn so much when generating manpages from their
603 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
604 the signs of types during autoconf. This is better than our old
605 approach, which didn't work when cross-compiling.
607 o Minor features (log messages, warnings):
608 - Detect when we're running with a version of OpenSSL other than the
609 one we compiled with. This conflict has occasionally given people
610 hard-to-track-down errors.
611 - Warn users who run hidden services on a Tor client with
612 UseEntryGuards disabled that their hidden services will be
613 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
614 attack which motivated Tor to support entry guards in the first
615 place). Resolves ticket 6889.
616 - Warn when we are binding low ports when hibernation is enabled;
617 previously we had warned when we were _advertising_ low ports with
618 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
619 - Issue a warning when running with the bufferevents backend enabled.
620 It's still not stable, and people should know that they're likely
621 to hit unexpected problems. Closes ticket 9147.
623 o Minor features (log messages, notices):
624 - Refactor resolve_my_address() so it returns the method by which we
625 decided our public IP address (explicitly configured, resolved from
626 explicit hostname, guessed from interfaces, learned by gethostname).
627 Now we can provide more helpful log messages when a relay guesses
628 its IP address incorrectly (e.g. due to unexpected lines in
629 /etc/hosts). Resolves ticket 2267.
630 - Track how many "TAP" and "NTor" circuit handshake requests we get,
631 and how many we complete, and log it every hour to help relay
632 operators follow trends in network load. Addresses ticket 9658.
634 o Minor features (log messages, diagnostics):
635 - If we fail to free a microdescriptor because of bug 7164, log
636 the filename and line number from which we tried to free it.
637 - We compute the overhead from passing onionskins back and forth to
638 cpuworkers, and report it when dumping statistics in response to
639 SIGUSR1. Supports ticket 7291.
640 - Add another diagnostic to the heartbeat message: track and log
641 overhead that TLS is adding to the data we write. If this is
642 high, we are sending too little data to SSL_write at a time.
643 Diagnostic for bug 7707.
644 - Log packaged cell fullness as part of the heartbeat message.
645 Diagnosis to try to determine the extent of bug 7743.
646 - Add more detail to a log message about relaxed timeouts, to help
648 - When learning a fingerprint for a bridge, log its corresponding
649 transport type. Implements ticket 7896.
650 - Warn more aggressively when flushing microdescriptors to a
651 microdescriptor cache fails, in an attempt to mitigate bug 8031,
652 or at least make it more diagnosable.
653 - Improve the log message when "Bug/attack: unexpected sendme cell
654 from client" occurs, to help us track bug 8093.
655 - Improve debugging output to help track down bug 8185 ("Bug:
656 outgoing relay cell has n_chan==NULL. Dropping.")
658 o Minor features (log messages, quieter bootstrapping):
659 - Log fewer lines at level "notice" about our OpenSSL and Libevent
660 versions and capabilities when everything is going right. Resolves
662 - Omit the first heartbeat log message, because it never has anything
663 useful to say, and it clutters up the bootstrapping messages.
664 Resolves ticket 6758.
665 - Don't log about reloading the microdescriptor cache at startup. Our
666 bootstrap warnings are supposed to tell the user when there's a
667 problem, and our bootstrap notices say when there isn't. Resolves
668 ticket 6759; bugfix on 0.2.2.6-alpha.
669 - Don't log "I learned some more directory information" when we're
670 reading cached directory information. Reserve it for when new
671 directory information arrives in response to a fetch. Resolves
673 - Don't complain about bootstrapping problems while hibernating.
674 These complaints reflect a general code problem, but not one
675 with any problematic effects (no connections are actually
676 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
678 o Minor features (testing):
679 - In our testsuite, create temporary directories with a bit more
680 entropy in their name to make name collisions less likely. Fixes
682 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
683 (P-256) Diffie-Hellman handshakes to src/or/bench.
684 - Add benchmark functions to test onion handshake performance.
687 - The DirServer option is now DirAuthority, for consistency with
688 current naming patterns. You can still use the old DirServer form.
690 o Minor bugfixes (protocol):
691 - Fix the handling of a TRUNCATE cell when it arrives while the
692 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
693 - When a Tor client gets a "truncated" relay cell, the first byte of
694 its payload specifies why the circuit was truncated. We were
695 ignoring this 'reason' byte when tearing down the circuit, resulting
696 in the controller not being told why the circuit closed. Now we
697 pass the reason from the truncated cell to the controller. Bugfix
698 on 0.1.2.3-alpha; fixes bug 7039.
699 - Fix a misframing issue when reading the version numbers in a
700 VERSIONS cell. Previously we would recognize [00 01 00 02] as
701 'version 1, version 2, and version 0x100', when it should have
702 only included versions 1 and 2. Fixes bug 8059; bugfix on
703 0.2.0.10-alpha. Reported pseudonymously.
704 - Make the format and order of STREAM events for DNS lookups
705 consistent among the various ways to launch DNS lookups. Fixes
706 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
708 o Minor bugfixes (syscalls and disk interaction):
709 - Always check the return values of functions fcntl() and
710 setsockopt(). We don't believe these are ever actually failing in
711 practice, but better safe than sorry. Also, checking these return
712 values should please analysis tools like Coverity. Patch from
713 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
714 - Avoid double-closing the listener socket in our socketpair()
715 replacement (used on Windows) in the case where the addresses on
716 our opened sockets don't match what we expected. Fixes bug 9400;
717 bugfix on 0.0.2pre7. Found by Coverity.
718 - Correctly store microdescriptors and extrainfo descriptors that
719 include an internal NUL byte. Fixes bug 8037; bugfix on
720 0.2.0.1-alpha. Bug reported by "cypherpunks".
721 - If for some reason we fail to write a microdescriptor while
722 rebuilding the cache, do not let the annotations from that
723 microdescriptor linger in the cache file, and do not let the
724 microdescriptor stay recorded as present in its old location.
725 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
726 - Use direct writes rather than stdio when building microdescriptor
727 caches, in an attempt to mitigate bug 8031, or at least make it
730 o Minor fixes (config options):
731 - Warn and fail if a server is configured not to advertise any
732 ORPorts at all. (We need *something* to put in our descriptor,
733 or we just won't work.)
734 - Behave correctly when the user disables LearnCircuitBuildTimeout
735 but doesn't tell us what they would like the timeout to be. Fixes
736 bug 6304; bugfix on 0.2.2.14-alpha.
737 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
738 to start with a triple-underscore so the controller won't touch it.
739 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
740 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
741 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
742 - When autodetecting the number of CPUs, use the number of available
743 CPUs in preference to the number of configured CPUs. Inform the
744 user if this reduces the number of available CPUs. Fixes bug 8002;
745 bugfix on 0.2.3.1-alpha.
746 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
747 - Make it an error when you set EntryNodes but disable UseGuardNodes,
748 since it will (surprisingly to some users) ignore EntryNodes. Fixes
749 bug 8180; bugfix on 0.2.3.11-alpha.
750 - Avoid overflows when the user sets MaxCircuitDirtiness to a
751 ridiculously high value, by imposing a (ridiculously high) 30-day
752 maximum on MaxCircuitDirtiness.
754 o Minor bugfixes (control protocol):
755 - Stop sending a stray "(null)" in some cases for the server status
756 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
758 - The ADDRMAP command can no longer generate an ill-formed error
759 code on a failed MAPADDRESS. It now says "internal" rather than
760 an English sentence fragment with spaces in the middle. Bugfix on
763 o Minor bugfixes (clients / edges):
764 - When we receive a RELAY_END cell with the reason DONE, or with no
765 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
766 status as "connection refused". Previously we reported these cases
767 as success but then immediately closed the connection. Fixes bug
768 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
769 - If the guard we choose first doesn't answer, we would try the
770 second guard, but once we connected to the second guard we would
771 abandon it and retry the first one, slowing down bootstrapping.
772 The fix is to treat all our initially chosen guards as acceptable
773 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
774 - When choosing which stream on a formerly stalled circuit to wake
775 first, make better use of the platform's weak RNG. Previously,
776 we had been using the % ("modulo") operator to try to generate a
777 1/N chance of picking each stream, but this behaves badly with
778 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
781 o Minor bugfixes (path bias detection):
782 - If the state file's path bias counts are invalid (presumably from a
783 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
784 additional checks and log messages to the scaling of Path Bias
785 counts, in case there still are remaining issues with scaling.
786 Should help resolve bug 8235.
787 - Prevent rounding error in path bias counts when scaling
788 them down, and use the correct scale factor default. Also demote
789 some path bias related log messages down a level and make others
790 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
791 - Remove a source of rounding error during path bias count scaling;
792 don't count cannibalized circuits as used for path bias until we
793 actually try to use them; and fix a circuit_package_relay_cell()
794 warning message about n_chan==NULL. Fixes bug 7802.
795 - Paste the description for PathBias parameters from the man
796 page into or.h, so the code documents them too. Fixes bug 7982;
797 bugfix on 0.2.3.17-beta.
799 o Minor bugfixes (relays):
800 - Stop trying to resolve our hostname so often (e.g. every time we
801 think about doing a directory fetch). Now we reuse the cached
802 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
803 and 2410 (bugfix on 0.1.2.2-alpha).
804 - When examining the list of network interfaces to find our address,
805 do not consider non-running or disabled network interfaces. Fixes
806 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
808 o Minor bugfixes (blocking resistance):
809 - Only disable TLS session ticket support when running as a TLS
810 server. Now clients will blend better with regular Firefox
811 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
813 o Minor bugfixes (IPv6):
814 - Use square brackets around IPv6 addresses in numerous places
815 that needed them, including log messages, HTTPS CONNECT proxy
816 requests, TransportProxy statefile entries, and pluggable transport
817 extra-info lines. Fixes bug 7011; patch by David Fifield.
819 o Minor bugfixes (directory authorities):
820 - Reject consensus votes with more than 64 known-flags. We aren't even
821 close to that limit yet, and our code doesn't handle it correctly.
822 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
823 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
824 bugfix on 0.2.0.3-alpha.
826 o Minor bugfixes (memory leaks):
827 - Avoid leaking memory if we fail to compute a consensus signature
828 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
829 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
830 on 0.2.1.1-alpha; fixes bug 7816.
831 - Fix a memory leak during safe-cookie controller authentication.
832 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
833 - Free some more still-in-use memory at exit, to make hunting for
834 memory leaks easier. Resolves bug 7029.
836 o Minor bugfixes (code correctness):
837 - Increase the width of the field used to remember a connection's
838 link protocol version to two bytes. Harmless for now, since the
839 only currently recognized versions are one byte long. Reported
840 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
841 - Fix a crash when debugging unit tests on Windows: deallocate a
842 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
843 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
844 - When detecting the largest possible file descriptor (in order to
845 close all file descriptors when launching a new program), actually
846 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
847 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
849 - Avoid a crash if we fail to generate an extrainfo descriptor.
850 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
852 - Avoid an off-by-one error when checking buffer boundaries when
853 formatting the exit status of a pluggable transport helper.
854 This is probably not an exploitable bug, but better safe than
855 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
857 - Get rid of a couple of harmless clang warnings, where we compared
858 enums to ints. These warnings are newly introduced in clang 3.2.
860 o Minor bugfixes (code cleanliness):
861 - Avoid use of reserved identifiers in our C code. The C standard
862 doesn't like us declaring anything that starts with an
863 underscore, so let's knock it off before we get in trouble. Fix
864 for bug 1031; bugfix on the first Tor commit.
865 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
866 with large values. This situation was untriggered, but nevertheless
867 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
868 - Fix an impossible buffer overrun in the AES unit tests. Fixes
869 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
870 - Fix handling of rendezvous client authorization types over 8.
871 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
872 - Remove a couple of extraneous semicolons that were upsetting the
873 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
874 bugfix on 0.2.2.1-alpha.
875 - When complaining about a client port on a public address, log
876 which address we're complaining about. Fixes bug 4020; bugfix on
877 0.2.3.3-alpha. Patch by Tom Fitzhenry.
879 o Minor bugfixes (log messages, warnings):
880 - If we encounter a write failure on a SOCKS connection before we
881 finish our SOCKS handshake, don't warn that we closed the
882 connection before we could send a SOCKS reply. Fixes bug 8427;
883 bugfix on 0.1.0.1-rc.
884 - Fix a directory authority warn caused when we have a large amount
885 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
886 - Downgrade "Failed to hand off onionskin" messages to "debug"
887 severity, since they're typically redundant with the "Your computer
888 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
889 - Avoid spurious warnings when configuring multiple client ports of
890 which only some are nonlocal. Previously, we had claimed that some
891 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
894 o Minor bugfixes (log messages, other):
895 - Fix log messages and comments to avoid saying "GMT" when we mean
896 "UTC". Fixes bug 6113.
897 - When rejecting a configuration because we were unable to parse a
898 quoted string, log an actual error message. Fixes bug 7950; bugfix
900 - Correctly recognize that [::1] is a loopback address. Fixes
901 bug 8377; bugfix on 0.2.1.3-alpha.
902 - Don't log inappropriate heartbeat messages when hibernating: a
903 hibernating node is _expected_ to drop out of the consensus,
904 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
905 bugfix on 0.2.3.1-alpha.
906 - Eliminate several instances where we use "Nickname=ID" to refer to
907 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
908 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
911 o Minor bugfixes (build):
912 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
913 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
914 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
916 o Documentation fixes:
917 - Make the torify manpage no longer refer to tsocks; torify hasn't
918 supported tsocks since 0.2.3.14-alpha.
919 - Make the tor manpage no longer reference tsocks.
920 - Fix the GeoIPExcludeUnknown documentation to refer to
921 ExcludeExitNodes rather than the currently nonexistent
922 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
923 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
925 - Say "KBytes" rather than "KB" in the man page (for various values
926 of K), to further reduce confusion about whether Tor counts in
927 units of memory or fractions of units of memory. Resolves ticket 7054.
928 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
929 names match. Fixes bug 7768.
930 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
931 message is logged at notice, not at info.
932 - Clarify the usage and risks of setting the ContactInfo torrc line
933 for your relay or bridge. Resolves ticket 9854.
934 - Add anchors to the manpage so we can link to the html version of
935 the documentation for specific options. Resolves ticket 9866.
936 - Replace remaining references to DirServer in man page and
937 log entries. Resolves ticket 10124.
940 - Stop exporting estimates of v2 and v3 directory traffic shares
941 in extrainfo documents. They were unneeded and sometimes inaccurate.
942 Also stop exporting any v2 directory request statistics. Resolves
944 - Drop support for detecting and warning about versions of Libevent
945 before 1.3e. Nothing reasonable ships with them any longer; warning
946 the user about them shouldn't be needed. Resolves ticket 6826.
947 - Now that all versions before 0.2.2.x are disallowed, we no longer
948 need to work around their missing features. Remove a bunch of
952 - The tor-tsocks.conf is no longer distributed or installed. We
953 recommend that tsocks users use torsocks instead. Resolves
955 - Remove some of the older contents of doc/ as obsolete; move others
956 to torspec.git. Fixes bug 8965.
958 o Code simplification:
959 - Avoid using character buffers when constructing most directory
960 objects: this approach was unwieldy and error-prone. Instead,
961 build smartlists of strings, and concatenate them when done.
962 - Rename "isin" functions to "contains", for grammar. Resolves
964 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
965 with the natural logarithm function from the system libm. Resolves
967 - Start using OpenBSD's implementation of queue.h, so that we don't
968 need to hand-roll our own pointer and list structures whenever we
969 need them. (We can't rely on a sys/queue.h, since some operating
970 systems don't have them, and the ones that do have them don't all
971 present the same extensions.)
972 - Start using OpenBSD's implementation of queue.h (originally by
974 - Enhance our internal sscanf replacement so that we can eliminate
975 the last remaining uses of the system sscanf. (Though those uses
976 of sscanf were safe, sscanf itself is generally error prone, so
977 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
979 - Replace all calls to snprintf() outside of src/ext with
980 tor_snprintf(). Also remove the #define to replace snprintf with
981 _snprintf on Windows; they have different semantics, and all of
982 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
985 - Add a wrapper function for the common "log a message with a
987 - Split the onion.c file into separate modules for the onion queue
988 and the different handshakes it supports.
989 - Move the client-side address-map/virtual-address/DNS-cache code
990 out of connection_edge.c into a new addressmap.c module.
991 - Move the entry node code from circuitbuild.c to its own file.
992 - Move the circuit build timeout tracking code from circuitbuild.c
994 - Source files taken from other packages now reside in src/ext;
995 previously they were scattered around the rest of Tor.
996 - Move the generic "config" code into a new file, and have "config.c"
997 hold only torrc- and state-related code. Resolves ticket 6823.
998 - Move the core of our "choose a weighted element at random" logic
999 into its own function, and give it unit tests. Now the logic is
1000 testable, and a little less fragile too.
1001 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1002 - Move last_reachable and testing_since from routerinfo_t to node_t.
1003 Implements ticket 5529.
1004 - Add replaycache_t structure, functions and unit tests, then refactor
1005 rend_service_introduce() to be more clear to read, improve, debug,
1006 and test. Resolves bug 6177.
1009 - Remove some now-needless code that tried to aggressively flush
1010 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1011 cell queue logic has saved us from the failure mode that this code
1012 was supposed to prevent. Removing this code will limit the number
1013 of baroque control flow paths through Tor's network logic. Reported
1014 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1015 - Remove unused code for parsing v1 directories and "running routers"
1016 documents. Fixes bug 6887.
1017 - Remove the marshalling/unmarshalling code for sending requests to
1018 cpuworkers over a socket, and instead just send structs. The
1019 recipient will always be the same Tor binary as the sender, so
1020 any encoding is overkill.
1021 - Remove the testing_since field of node_t, which hasn't been used
1022 for anything since 0.2.0.9-alpha.
1023 - Finally remove support for malloc_good_size and malloc_usable_size.
1024 We had hoped that these functions would let us eke a little more
1025 memory out of our malloc implementation. Unfortunately, the only
1026 implementations that provided these functions are also ones that
1027 are already efficient about not overallocation: they never got us
1028 more than 7 or so bytes per allocation. Removing them saves us a
1029 little code complexity and a nontrivial amount of build complexity.
1032 Changes in version 0.2.3.25 - 2012-11-19
1033 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1034 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1035 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1036 programmer, and friend. Unstinting in his dedication to the cause of
1037 freedom, he inspired and helped many of us as we began our work on
1038 anonymity, and inspires us still. Please honor his memory by writing
1039 software to protect people's freedoms, and by helping others to do so.
1041 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1042 significantly reduced directory overhead (via microdescriptors),
1043 enormous crypto performance improvements for fast relays on new
1044 enough hardware, a new v3 TLS handshake protocol that can better
1045 resist fingerprinting, support for protocol obfuscation plugins (aka
1046 pluggable transports), better scalability for hidden services, IPv6
1047 support for bridges, performance improvements like allowing clients
1048 to skip the first round-trip on the circuit ("optimistic data") and
1049 refilling token buckets more often, a new "stream isolation" design
1050 to isolate different applications on different circuits, and many
1051 stability, security, and privacy fixes.
1053 Major features (v3 directory protocol):
1054 - Clients now use microdescriptors instead of regular descriptors
1055 to build circuits. Microdescriptors are authority-generated
1056 summaries of regular descriptors' contents, designed to change very
1057 rarely (see proposal 158 for details). This feature is designed
1058 to save bandwidth, especially for clients on slow internet
1059 connections. Use "UseMicrodescriptors 0" to disable it.
1060 - Caches now download, cache, and serve microdescriptors, as well
1061 as multiple "flavors" of the consensus, including a flavor that
1062 describes microdescriptors.
1064 o Major features (build hardening):
1065 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1067 o Major features (relay scaling):
1068 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
1069 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
1070 vectorized AES implementations as appropriate. These can be much,
1071 much faster than other AES implementations.
1072 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1073 implementation. It makes AES_CTR about 7% faster than our old one
1074 (which was about 10% faster than the one OpenSSL used to provide).
1075 Resolves ticket 4526.
1076 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1077 operations can use hardware acceleration (if present). Resolves
1079 - Unconditionally use OpenSSL's AES implementation instead of our
1080 old built-in one. OpenSSL's AES has been better for a while, and
1081 relatively few servers should still be on any version of OpenSSL
1082 that doesn't have good optimized assembly AES.
1084 o Major features (blocking resistance):
1085 - Update TLS cipher list to match Firefox 8 and later. Resolves
1087 - Remove support for clients falsely claiming to support standard
1088 ciphersuites that they can actually provide. As of modern OpenSSL
1089 versions, it's not necessary to fake any standard ciphersuite,
1090 and doing so prevents us from using better ciphersuites in the
1091 future, since servers can't know whether an advertised ciphersuite
1092 is really supported or not. Some hosts -- notably, ones with very
1093 old versions of OpenSSL or where OpenSSL has been built with ECC
1094 disabled -- will stand out because of this change; TBB users should
1095 not be affected. Implements the client side of proposal 198.
1096 - Implement a new handshake protocol (v3) for authenticating Tors to
1097 each other over TLS. It should be more resistant to fingerprinting
1098 than previous protocols, and should require less TLS hacking for
1099 future Tor implementations. Implements proposal 176.
1100 - Allow variable-length padding cells, to disguise the length of
1101 Tor's TLS records. Implements part of proposal 184.
1102 - While we're trying to bootstrap, record how many TLS connections
1103 fail in each state, and report which states saw the most failures
1104 in response to any bootstrap failures. This feature may speed up
1105 diagnosis of censorship events. Implements ticket 3116.
1107 o Major features (pluggable transports):
1108 - Clients and bridges can now be configured to use a separate
1109 "transport" proxy. This approach makes the censorship arms race
1110 easier by allowing bridges to use protocol obfuscation plugins.
1111 Implements proposal 180 (tickets 2841 and 3472).
1113 o Major features (DoS resistance):
1114 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1115 part of "Proposal 110: Avoiding infinite length circuits" by
1116 refusing all circuit-extend requests that do not use a relay_early
1117 cell. This change helps Tor resist a class of denial-of-service
1118 attacks by limiting the maximum circuit length.
1119 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1120 could use this trick to make their circuits receive cells faster
1121 than our flow control would have allowed, or to gum up the network,
1122 or possibly to do targeted memory denial-of-service attacks on
1123 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1124 from July 2002, before the release of Tor 0.0.0.
1126 o Major features (hidden services):
1127 - Adjust the number of introduction points that a hidden service
1128 will try to maintain based on how long its introduction points
1129 remain in use and how many introductions they handle. Fixes
1131 - Add a "tor2web mode" for clients that want to connect to hidden
1132 services non-anonymously (and possibly more quickly). As a safety
1133 measure to try to keep users from turning this on without knowing
1134 what they are doing, tor2web mode must be explicitly enabled at
1135 compile time, and a copy of Tor compiled to run in tor2web mode
1136 cannot be used as a normal Tor client. Implements feature 2553.
1138 o Major features (IPv6):
1139 - Clients can now connect to private bridges over IPv6. Bridges
1140 still need at least one IPv4 address in order to connect to
1141 other relays. Note that we don't yet handle the case where the
1142 user has two bridge lines for the same bridge (one IPv4, one
1143 IPv6). Implements parts of proposal 186.
1145 o Major features (directory authorities):
1146 - Use a more secure consensus parameter voting algorithm. Now at
1147 least three directory authorities or a majority of them must
1148 vote on a given parameter before it will be included in the
1149 consensus. Implements proposal 178.
1150 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1151 flag. In the past few years the average relay speed has picked
1152 up, and while the "top 7/8 of the network get the Fast flag" and
1153 "all relays with 20KB or more of capacity get the Fast flag" rules
1154 used to have the same result, now the top 7/8 of the network has
1155 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1157 o Major features (performance):
1158 - Exit nodes now accept and queue data on not-yet-connected streams.
1159 Previously, the client wasn't allowed to send data until the
1160 stream was connected, which slowed down all connections. This
1161 change will enable clients to perform a "fast-start" on streams
1162 and send data without having to wait for a confirmation that the
1163 stream has opened. Patch from Ian Goldberg; implements the server
1164 side of Proposal 174.
1165 - When using an exit relay running 0.2.3.x, clients can now
1166 "optimistically" send data before the exit relay reports that
1167 the stream has opened. This saves a round trip when starting
1168 connections where the client speaks first (such as web browsing).
1169 This behavior is controlled by a consensus parameter (currently
1170 disabled). To turn it on or off manually, use the "OptimisticData"
1171 torrc option. Implements proposal 181; code by Ian Goldberg.
1172 - Add a new TokenBucketRefillInterval option to refill token buckets
1173 more frequently than once per second. This should improve network
1174 performance, alleviate queueing problems, and make traffic less
1175 bursty. Implements proposal 183; closes ticket 3630. Design by
1176 Florian Tschorsch and Björn Scheuermann; implementation by
1178 - Raise the threshold of server descriptors needed (75%) and exit
1179 server descriptors needed (50%) before we will declare ourselves
1180 bootstrapped. This will make clients start building circuits a
1181 little later, but makes the initially constructed circuits less
1182 skewed and less in conflict with further directory fetches. Fixes
1185 o Major features (relays):
1186 - Relays now try regenerating and uploading their descriptor more
1187 frequently if they are not listed in the consensus, or if the
1188 version of their descriptor listed in the consensus is too
1189 old. This fix should prevent situations where a server declines
1190 to re-publish itself because it has done so too recently, even
1191 though the authorities decided not to list its recent-enough
1192 descriptor. Fix for bug 3327.
1194 o Major features (stream isolation):
1195 - You can now configure Tor so that streams from different
1196 applications are isolated on different circuits, to prevent an
1197 attacker who sees your streams as they leave an exit node from
1198 linking your sessions to one another. To do this, choose some way
1199 to distinguish the applications: have them connect to different
1200 SocksPorts, or have one of them use SOCKS4 while the other uses
1201 SOCKS5, or have them pass different authentication strings to the
1202 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1203 degree of isolation you need. This implements Proposal 171.
1204 - There's a new syntax for specifying multiple client ports (such as
1205 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1206 multiple *Port entries with full addr:port syntax on each.
1207 The old *ListenAddress format is still supported, but you can't
1208 mix it with the new *Port syntax.
1210 o Major features (bufferevents):
1211 - Tor can now optionally build with the "bufferevents" buffered IO
1212 backend provided by Libevent 2. To use this feature, make sure you
1213 have the latest possible version of Libevent, and pass the
1214 --enable-bufferevents flag to configure when building Tor from
1215 source. This feature will make our networking code more flexible,
1216 let us stack layers on each other, and let us use more efficient
1217 zero-copy transports where available.
1218 - Add experimental support for running on Windows with IOCP and no
1219 kernel-space socket buffers. This feature is controlled by a new
1220 "UserspaceIOCPBuffers" config option (off by default), which has
1221 no effect unless Tor has been built with bufferevents enabled,
1222 you're running on Windows, and you've set "DisableIOCP 0". In the
1223 long run, this may help solve or mitigate bug 98.
1225 o Major features (path selection):
1226 - The EntryNodes option can now include country codes like {de} or IP
1227 addresses or network masks. Previously we had disallowed these
1228 options because we didn't have an efficient way to keep the list up
1229 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
1232 o Major features (port forwarding):
1233 - Add support for automatic port mapping on the many home routers
1234 that support NAT-PMP or UPnP. To build the support code, you'll
1235 need to have the libnatpnp library and/or the libminiupnpc library,
1236 and you'll need to enable the feature specifically by passing
1237 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
1238 it on, use the new PortForwarding option.
1240 o Major features (logging):
1241 - Add a new 'Heartbeat' log message type to periodically log a message
1242 describing Tor's status at level Notice. This feature is meant for
1243 operators who log at notice, and want to make sure that their Tor
1244 server is still working. Implementation by George Kadianakis.
1245 - Make logging resolution configurable with a new LogTimeGranularity
1246 option, and change the default from 1 millisecond to 1 second.
1247 Implements enhancement 1668.
1249 o Major features (other):
1250 - New "DisableNetwork" config option to prevent Tor from launching any
1251 connections or accepting any connections except on a control port.
1252 Bundles and controllers can set this option before letting Tor talk
1253 to the rest of the network, for example to prevent any connections
1254 to a non-bridge address. Packages like Orbot can also use this
1255 option to instruct Tor to save power when the network is off.
1256 - Try to use system facilities for enumerating local interface
1257 addresses, before falling back to our old approach (which was
1258 binding a UDP socket, and calling getsockname() on it). That
1259 approach was scaring OS X users whose draconian firewall
1260 software warned about binding to UDP sockets regardless of
1261 whether packets were sent. Now we try to use getifaddrs(),
1262 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1263 system supports. Resolves ticket 1827.
1264 - Add experimental support for a "defaults" torrc file to be parsed
1265 before the regular torrc. Torrc options override the defaults file's
1266 options in the same way that the command line overrides the torrc.
1267 The SAVECONF controller command saves only those options which
1268 differ between the current configuration and the defaults file. HUP
1269 reloads both files. Implements task 4552.
1271 o New directory authorities:
1272 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1273 authority. Closes ticket 5749.
1275 o Security/privacy fixes:
1276 - Avoid read-from-freed-memory and double-free bugs that could occur
1277 when a DNS request fails while launching it. Fixes bug 6480;
1278 bugfix on 0.2.0.1-alpha.
1279 - Reject any attempt to extend to an internal address. Without
1280 this fix, a router could be used to probe addresses on an internal
1281 network to see whether they were accepting connections. Fixes bug
1282 6710; bugfix on 0.0.8pre1.
1283 - Close any connection that sends unrecognized junk before the TLS
1284 handshake. Solves an issue noted in bug 4369.
1285 - The advertised platform of a relay now includes only its operating
1286 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
1287 its service pack level (for Windows) or its CPU architecture
1288 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
1289 can insert an extra string in the platform line by setting the
1290 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
1291 - Disable TLS session tickets. OpenSSL's implementation was giving
1292 our TLS session keys the lifetime of our TLS context objects, when
1293 perfect forward secrecy would want us to discard anything that
1294 could decrypt a link connection as soon as the link connection
1295 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1296 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1297 - Tor tries to wipe potentially sensitive data after using it, so
1298 that if some subsequent security failure exposes Tor's memory,
1299 the damage will be limited. But we had a bug where the compiler
1300 was eliminating these wipe operations when it decided that the
1301 memory was no longer visible to a (correctly running) program,
1302 hence defeating our attempt at defense in depth. We fix that
1303 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1304 is unlikely to optimize away. Future versions of Tor may use
1305 a less ridiculously heavy approach for this. Fixes bug 7352.
1306 Reported in an article by Andrey Karpov.
1308 o Major bugfixes (crashes and asserts):
1309 - Avoid a pair of double-free and use-after-mark bugs that can
1310 occur with certain timings in canceled and re-received DNS
1311 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1312 - Fix a denial of service attack by which any directory authority
1313 could crash all the others, or by which a single v2 directory
1314 authority could crash everybody downloading v2 directory
1315 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1316 - Fix an assert that directory authorities could trigger on sighup
1317 during some configuration state transitions. We now don't treat
1318 it as a fatal error when the new descriptor we just generated in
1319 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1320 - Avoid segfault when starting up having run with an extremely old
1321 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1324 o Major bugfixes (clients):
1325 - If we are unable to find any exit that supports our predicted ports,
1326 stop calling them predicted, so that we don't loop and build
1327 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1328 which introduced predicted ports.
1329 - Check at each new consensus whether our entry guards were picked
1330 long enough ago that we should rotate them. Previously, we only
1331 did this check at startup, which could lead to us holding a guard
1332 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1333 - When fetching a bridge descriptor from a bridge authority,
1334 always do so anonymously, whether we have been able to open
1335 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1336 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1337 but we'll need to wait for bug 6010 before it's actually usable.
1339 o Major bugfixes (directory voting):
1340 - Check more thoroughly to prevent a rogue authority from
1341 double-voting on any consensus directory parameter. Previously,
1342 authorities would crash in this case if the total number of
1343 votes for any parameter exceeded the number of active voters,
1344 but would let it pass otherwise. Partially fixes bug 5786; bugfix
1346 - When computing weight parameters, behave more robustly in the
1347 presence of a bad bwweightscale value. Previously, the authorities
1348 would crash if they agreed on a sufficiently broken weight_scale
1349 value; now, they use a reasonable default and carry on. Fixes the
1350 rest of bug 5786; bugfix on 0.2.2.17-alpha.
1351 - If authorities are unable to get a v2 consensus document from other
1352 directory authorities, they no longer fall back to fetching
1353 them from regular directory caches. Fixes bug 5635; bugfix on
1354 0.2.2.26-beta, where routers stopped downloading v2 consensus
1357 o Major bugfixes (relays):
1358 - Fix a bug handling SENDME cells on nonexistent streams that could
1359 result in bizarre window values. Report and patch contributed
1360 pseudonymously. Fixes part of bug 6271. This bug was introduced
1361 before the first Tor release, in svn commit r152.
1362 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1363 tor gets started. This prevents a wrong average bandwidth
1364 estimate, which would cause relays to always start a new accounting
1365 interval at the earliest possible moment. Fixes bug 2003; bugfix
1366 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
1367 immensely in tracking this bug down.
1368 - Fix a possible crash bug when checking for deactivated circuits
1369 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1370 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1371 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1372 connections. This change should allow busy exit relays to stop
1373 running out of available sockets as quickly. Fixes bug 4950;
1374 bugfix on 0.2.2.26-beta.
1376 o Major bugfixes (blocking resistance):
1377 - Bridges no longer include their address in NETINFO cells on outgoing
1378 OR connections, to allow them to blend in better with clients.
1379 Removes another avenue for enumerating bridges. Reported by
1380 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1381 cells were introduced.
1382 - Warn the user when HTTPProxy, but no other proxy type, is
1383 configured. This can cause surprising behavior: it doesn't send
1384 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1385 directory traffic only. Resolves ticket 4663.
1387 o Major bugfixes (hidden services):
1388 - Improve hidden service robustness: when an attempt to connect to
1389 a hidden service ends, be willing to refetch its hidden service
1390 descriptors from each of the HSDir relays responsible for them
1391 immediately. Previously, we would not consider refetching the
1392 service's descriptors from each HSDir for 15 minutes after the last
1393 fetch, which was inconvenient if the hidden service was not running
1394 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1395 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1396 They used to check that the timestamp was within 30 minutes
1397 of their system clock, so they could cap the size of their
1398 replay-detection cache, but that approach unnecessarily refused
1399 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1400 the v3 intro-point protocol (the first one which sent a timestamp
1401 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1402 - When one of a hidden service's introduction points appears to be
1403 unreachable, stop trying it. Previously, we would keep trying
1404 to build circuits to the introduction point until we lost the
1405 descriptor, usually because the user gave up and restarted Tor.
1406 Fixes part of bug 3825.
1408 o Changes to default torrc file:
1409 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1410 port on 9050 by default anyway, so this should not change anything
1412 - Stop mentioning the deprecated *ListenAddress options in
1413 torrc.sample. Fixes bug 5438.
1414 - Document unit of bandwidth-related options in sample torrc.
1416 - Fix broken URLs in the sample torrc file, and tell readers about
1417 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1418 PublishServerDescriptor options. Addresses bug 4652.
1420 o Minor features (directory authorities):
1421 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1422 change when the authority is deciding whether to accept a newly
1423 uploaded descriptor. Implements ticket 6423.
1424 - Directory authorities are now a little more lenient at accepting
1425 older router descriptors, or newer router descriptors that don't
1426 make big changes. This should help ameliorate past and future
1427 issues where routers think they have uploaded valid descriptors,
1428 but the authorities don't think so. Fix for ticket 2479.
1429 - Authority operators can now vote for all relays in a given
1430 set of countries to be BadDir/BadExit/Invalid/Rejected.
1431 - Provide two consensus parameters (FastFlagMinThreshold and
1432 FastFlagMaxThreshold) to control the range of allowable bandwidths
1433 for the Fast directory flag. These allow authorities to run
1434 experiments on appropriate requirements for being a "Fast" node.
1435 The AuthDirFastGuarantee config value still applies. Implements
1438 o Minor features (bridges / bridge authorities):
1439 - Make bridge SSL certificates a bit more stealthy by using random
1440 serial numbers, in the same fashion as OpenSSL when generating
1441 self-signed certificates. Implements ticket 4584.
1442 - Tag a bridge's descriptor as "never to be sent unencrypted".
1443 This shouldn't matter, since bridges don't open non-anonymous
1444 connections to the bridge authority and don't allow unencrypted
1445 directory connections from clients, but we might as well make
1446 sure. Closes bug 5139.
1447 - The Bridge Authority now writes statistics on how many bridge
1448 descriptors it gave out in total, and how many unique descriptors
1449 it gave out. It also lists how often the most and least commonly
1450 fetched descriptors were given out, as well as the median and
1451 25th/75th percentile. Implements tickets 4200 and 4294.
1453 o Minor features (IPv6):
1454 - Make the code that clients use to detect an address change be
1455 IPv6-aware, so that it won't fill clients' logs with error
1456 messages when trying to get the IPv4 address of an IPv6
1457 connection. Implements ticket 5537.
1458 - Relays now understand an IPv6 address when they get one from a
1459 directory server. Resolves ticket 4875.
1461 o Minor features (hidden services):
1462 - Expire old or over-used hidden service introduction points.
1463 Required by fix for bug 3460.
1464 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1465 public key replay-detection cache from 60 minutes to 5 minutes. This
1466 replay-detection cache is now used only to detect multiple
1467 INTRODUCE2 cells specifying the same rendezvous point, so we can
1468 avoid launching multiple simultaneous attempts to connect to it.
1469 - When a hidden service's introduction point times out, consider
1470 trying it again during the next attempt to connect to the
1471 HS. Previously, we would not try it again unless a newly fetched
1472 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1474 o Minor features (relays):
1475 - Relays now include a reason for regenerating their descriptors
1476 in an HTTP header when uploading to the authorities. This will
1477 make it easier to debug descriptor-upload issues in the future.
1478 - Turn on directory request statistics by default and include them in
1479 extra-info descriptors. Don't break if we have no GeoIP database.
1480 - Replace files in stats/ rather than appending to them. Now that we
1481 include statistics in extra-info descriptors, it makes no sense to
1482 keep old statistics forever. Implements ticket 2930.
1483 - Relays that set "ConnDirectionStatistics 1" write statistics on the
1484 bidirectional use of connections to disk every 24 hours.
1485 - Add a GeoIP file digest to the extra-info descriptor. Implements
1488 o Minor features (new config options):
1489 - New config option "DynamicDHGroups" (disabled by default) provides
1490 each bridge with a unique prime DH modulus to be used during
1491 SSL handshakes. This option attempts to help against censors
1492 who might use the Apache DH modulus as a static identifier for
1493 bridges. Addresses ticket 4548.
1494 - New config option "DisableDebuggerAttachment" (on by default)
1495 to prevent basic debugging attachment attempts by other processes.
1496 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1497 - Ordinarily, Tor does not count traffic from private addresses (like
1498 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
1499 There is now a new option, CountPrivateBandwidth, to disable this
1500 behavior. Patch from Daniel Cagara.
1502 o Minor features (different behavior for old config options):
1503 - Allow MapAddress directives to specify matches against super-domains,
1504 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1505 Implements issue 933.
1506 - Don't disable the DirPort when we cannot exceed our AccountingMax
1507 limit during this interval because the effective bandwidthrate is
1508 low enough. This is useful in a situation where AccountMax is only
1509 used as an additional safeguard or to provide statistics.
1510 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1511 implements ticket 3439.
1512 - When configuring a large set of nodes in EntryNodes, and there are
1513 enough of them listed as Guard so that we don't need to consider
1514 the non-guard entries, prefer the ones listed with the Guard flag.
1515 - If you set the NumCPUs option to 0, Tor will now try to detect how
1516 many CPUs you have. This is the new default behavior.
1517 - The NodeFamily option -- which let you declare that you want to
1518 consider nodes to be part of a family whether they list themselves
1519 that way or not -- now allows IP address ranges and country codes.
1521 o Minor features (new command-line config behavior):
1522 - Slightly change behavior of "list" options (that is, config
1523 options that can appear more than once) when they appear both in
1524 torrc and on the command line. Previously, the command-line options
1525 would be appended to the ones from torrc. Now, the command-line
1526 options override the torrc options entirely. This new behavior
1527 allows the user to override list options (like exit policies and
1528 ports to listen on) from the command line, rather than simply
1529 appending to the list.
1530 - You can get the old (appending) command-line behavior for "list"
1531 options by prefixing the option name with a "+".
1532 - You can remove all the values for a "list" option from the command
1533 line without adding any new ones by prefixing the option name
1536 o Minor features (controller, new events):
1537 - Extend the control protocol to report flags that control a circuit's
1538 path selection in CIRC events and in replies to 'GETINFO
1539 circuit-status'. Implements part of ticket 2411.
1540 - Extend the control protocol to report the hidden service address
1541 and current state of a hidden-service-related circuit in CIRC
1542 events and in replies to 'GETINFO circuit-status'. Implements part
1544 - Include the creation time of a circuit in CIRC and CIRC2
1545 control-port events and the list produced by the 'GETINFO
1546 circuit-status' control-port command.
1547 - Add a new CONF_CHANGED event so that controllers can be notified
1548 of any configuration changes made by other controllers, or by the
1549 user. Implements ticket 1692.
1550 - Add a new SIGNAL event to the controller interface so that
1551 controllers can be notified when Tor handles a signal. Resolves
1552 issue 1955. Patch by John Brooks.
1554 o Minor features (controller, new getinfo options):
1555 - Expose our view of whether we have gone dormant to the controller,
1556 via a new "GETINFO dormant" value. Torbutton and other controllers
1557 can use this to avoid doing periodic requests through Tor while
1558 it's dormant (bug 4718). Resolves ticket 5954.
1559 - Add a new GETINFO option to get total bytes read and written. Patch
1560 from pipe, revised by atagar. Resolves ticket 2345.
1561 - Implement new GETINFO controller fields to provide information about
1562 the Tor process's pid, euid, username, and resource limits.
1564 o Minor features (controller, other):
1565 - Allow controllers to request an event notification whenever a
1566 circuit is cannibalized or its purpose is changed. Implements
1567 part of ticket 3457.
1568 - Use absolute path names when reporting the torrc filename in the
1569 control protocol, so a controller can more easily find the torrc
1570 file. Resolves bug 1101.
1571 - When reporting the path to the cookie file to the controller,
1572 give an absolute path. Resolves ticket 4881.
1574 o Minor features (log messages):
1575 - Add more information to a log statement that might help track down
1576 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1577 non-IP address" messages (or any Bug messages, for that matter!),
1578 please let us know about it.
1579 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1580 EntryNodes will have no effect. Resolves issue 2571.
1581 - Try to make the introductory warning message that Tor prints on
1582 startup more useful for actually finding help and information.
1583 Resolves ticket 2474.
1584 - When the system call to create a listener socket fails, log the
1585 error message explaining why. This may help diagnose bug 4027.
1587 o Minor features (other):
1588 - When we fail to initialize Libevent, retry with IOCP disabled so we
1589 don't need to turn on multi-threading support in Libevent, which in
1590 turn requires a working socketpair(). This is a workaround for bug
1591 4457, which affects Libevent versions from 2.0.1-alpha through
1593 - When starting as root and then changing our UID via the User
1594 control option, and we have a ControlSocket configured, make sure
1595 that the ControlSocket is owned by the same account that Tor will
1596 run under. Implements ticket 3421; fix by Jérémy Bobbio.
1597 - Accept attempts to include a password authenticator in the
1598 handshake, as supported by SOCKS5. This handles SOCKS clients that
1599 don't know how to omit a password when authenticating. Resolves
1601 - Check for and recover from inconsistency in the microdescriptor
1602 cache. This will make it harder for us to accidentally free a
1603 microdescriptor without removing it from the appropriate data
1604 structures. Fixes issue 3135; issue noted by "wanoskarnet".
1605 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1607 o Minor bugfixes (code security):
1608 - Prevent a null-pointer dereference when receiving a data cell
1609 for a nonexistent stream when the circuit in question has an
1610 empty deliver window. We don't believe this is triggerable,
1611 since we don't currently allow deliver windows to become empty,
1612 but the logic is tricky enough that it's better to make the code
1613 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1614 - Fix a (harmless) integer overflow in cell statistics reported by
1615 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1616 - Fix our implementation of crypto_random_hostname() so it can't
1617 overflow on ridiculously large inputs. (No Tor version has ever
1618 provided this kind of bad inputs, but let's be correct in depth.)
1619 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1620 - Add a (probably redundant) memory clear between iterations of
1621 the router status voting loop, to prevent future coding errors
1622 where data might leak between iterations of the loop. Resolves
1625 o Minor bugfixes (wrapper functions):
1626 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
1627 utility function used in the control-port code). This shouldn't
1628 ever happen unless Tor is completely out of memory, but if it did
1629 happen and Tor somehow recovered from it, Tor could have sent a log
1630 message to a control port in the middle of a reply to a controller
1631 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1632 - Fix some (not actually triggerable) buffer size checks in usage of
1633 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1635 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1636 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1637 - Enforce correct return behavior of tor_vsscanf() when the '%%'
1638 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
1639 - Make our replacement implementation of strtok_r() compatible with
1640 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1641 bugfix on 0.2.2.1-alpha.
1642 - Find more places in the code that should have been testing for
1643 invalid sockets using the SOCKET_OK macro. Required for a fix
1644 for bug 4533. Bugfix on 0.2.2.28-beta.
1646 o Minor bugfixes (code correctness):
1647 - Check return value of fputs() when writing authority certificate
1648 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1649 - When building Tor on Windows with -DUNICODE (not default), ensure
1650 that error messages, filenames, and DNS server names are always
1651 NUL-terminated when we convert them to a single-byte encoding.
1652 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1653 - Fix a memory leak when trying to launch a DNS request when the
1654 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
1656 - Correct file sizes when reading binary files on Cygwin, to avoid
1657 a bug where Tor would fail to read its state file. Fixes bug 6844;
1658 bugfix on 0.1.2.7-alpha.
1659 - Make sure to set *socket_error in all error cases in
1660 connection_connect(), so it can't produce a warning about
1661 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1662 0.2.1.1-alpha; resolves ticket 6028.
1663 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1664 bug 4532; found by "troll_un".
1666 o Minor bugfixes (clients):
1667 - Allow one-hop directory-fetching circuits the full "circuit build
1668 timeout" period, rather than just half of it, before failing them
1669 and marking the relay down. This fix should help reduce cases where
1670 clients declare relays (or worse, bridges) unreachable because
1671 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1672 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1674 - Ensure we don't cannibalize circuits that are longer than three hops
1675 already, so we don't end up making circuits with 5 or more
1676 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1677 0.1.0.1-rc which introduced cannibalization.
1679 o Minor bugfixes (relays):
1680 - Don't publish a new relay descriptor when we reload our onion key,
1681 unless the onion key has actually changed. Fixes bug 3263 and
1682 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
1683 - When relays refuse a "create" cell because their queue of pending
1684 create cells is too big (typically because their cpu can't keep up
1685 with the arrival rate), send back reason "resource limit" rather
1686 than reason "internal", so network measurement scripts can get a
1687 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1688 - Exit nodes don't need to fetch certificates for authorities that
1689 they don't recognize; only directory authorities, bridges,
1690 and caches need to do that. Fixes part of bug 2297; bugfix on
1693 o Minor bugfixes (directory authority / mirrors):
1694 - Avoid O(n^2) performance characteristics when parsing a large
1695 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1696 - Authorities no longer include any router in their microdescriptor
1697 consensuses for which they couldn't generate or agree on a
1698 microdescriptor. Fixes the second piece of bug 6404; fix on
1700 - When checking for requested signatures on the latest consensus
1701 before serving it to a client, make sure to check the right
1702 consensus flavor. Bugfix on 0.2.2.6-alpha.
1703 - Fix an edge case where TestingTorNetwork is set but the authorities
1704 and relays all have an uptime of zero, so the private Tor network
1705 could briefly lack support for hidden services. Fixes bug 3886;
1706 bugfix on 0.2.2.18-alpha.
1707 - Directory caches no longer refuse to clean out descriptors because
1708 of missing v2 networkstatus documents, unless they're configured
1709 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1710 0.2.2.26-beta. Patch by Daniel Bryg.
1711 - Don't serve or accept v2 hidden service descriptors over a relay's
1712 DirPort. It's never correct to do so, and disabling it might
1713 make it more annoying to exploit any bugs that turn up in the
1714 descriptor-parsing code. Fixes bug 7149.
1716 o Minor bugfixes (hidden services, client-side):
1717 - Assert that hidden-service-related operations are not performed
1718 using single-hop circuits. Previously, Tor would assert that
1719 client-side streams are not attached to single-hop circuits,
1720 but not that other sensitive operations on the client and service
1721 side are not performed using single-hop circuits. Fixes bug 3332;
1723 - Avoid undefined behaviour when parsing the list of supported
1724 rendezvous/introduction protocols in a hidden service descriptor.
1725 Previously, Tor would have confused (as-yet-unused) protocol version
1726 numbers greater than 32 with lower ones on many platforms. Fixes
1727 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1728 - Don't close hidden service client circuits which have almost
1729 finished connecting to their destination when they reach
1730 the normal circuit-build timeout. Previously, we would close
1731 introduction circuits which are waiting for an acknowledgement
1732 from the introduction point, and rendezvous circuits which have
1733 been specified in an INTRODUCE1 cell sent to a hidden service,
1734 after the normal CBT. Now, we mark them as 'timed out', and launch
1735 another rendezvous attempt in parallel. This behavior change can
1736 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1737 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1739 o Minor bugfixes (hidden services, service-side):
1740 - Don't close hidden-service-side rendezvous circuits when they
1741 reach the normal circuit-build timeout. This behaviour change can
1742 be disabled using the new
1743 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1744 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1745 - Don't launch more than 10 service-side introduction-point circuits
1746 for a hidden service in five minutes. Previously, we would consider
1747 launching more introduction-point circuits if at least one second
1748 had passed without any introduction-point circuits failing. Fixes
1749 bug 4607; bugfix on 0.0.7pre1.
1751 o Minor bugfixes (config option behavior):
1752 - If the user tries to set MyFamily on a bridge, refuse to
1753 do so, and warn about the security implications. Fixes bug 4657;
1754 bugfix on 0.2.0.3-alpha.
1755 - The "--quiet" and "--hush" options now apply not only to Tor's
1756 behavior before logs are configured, but also to Tor's behavior in
1757 the absense of configured logs. Fixes bug 3550; bugfix on
1759 - Change the AllowDotExit rules so they should actually work.
1760 We now enforce AllowDotExit only immediately after receiving an
1761 address via SOCKS or DNSPort: other sources are free to provide
1762 .exit addresses after the resolution occurs. Fixes bug 3940;
1763 bugfix on 0.2.2.1-alpha.
1764 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
1765 don't depend on the consensus parameters or compute adaptive
1766 timeouts when it is disabled. Fixes bug 5049; bugfix on
1768 - After we pick a directory mirror, we would refuse to use it if
1769 it's in our ExcludeExitNodes list, resulting in mysterious failures
1770 to bootstrap for people who just wanted to avoid exiting from
1771 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1772 - When told to add a bridge with the same digest as a preexisting
1773 bridge but a different addr:port, change the addr:port as
1774 requested. Previously we would not notice the change. Fixes half
1775 of bug 5603; fix on 0.2.2.26-beta.
1777 o Minor bugfixes (controller):
1778 - Allow manual 'authenticate' commands to the controller interface
1779 from netcat (nc) as well as telnet. We were rejecting them because
1780 they didn't come with the expected whitespace at the end of the
1781 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1782 - Report a real bootstrap problem to the controller on router
1783 identity mismatch. Previously we just said "foo", which probably
1784 made a lot of sense at the time. Fixes bug 4169; bugfix on
1786 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1787 option is set to 0 (which Vidalia version 0.2.16 now does when
1788 a SAVECONF attempt fails), perform other actions that SIGHUP
1789 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1791 - Correctly handle checking the permissions on the parent
1792 directory of a control socket in the root directory. Bug found
1793 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
1795 - End AUTHCHALLENGE error messages (in the control protocol) with
1796 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
1798 o Minor bugfixes (network reading/writing):
1799 - Disable writing on marked-for-close connections when they are
1800 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1801 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1802 case for flushing marked connections.
1803 - Make sure that there are no unhandled pending TLS errors before
1804 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1805 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1806 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1807 - Detect SSL handshake even when the initial attempt to write the
1808 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1809 - If the client fails to set a reasonable set of ciphersuites
1810 during its v2 handshake renegotiation, allow the renegotiation to
1811 continue nevertheless (i.e. send all the required certificates).
1812 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1814 o Minor bugfixes (other):
1815 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1816 resource exhaustion, so that clients can adjust their load to
1817 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1818 started using END_STREAM_REASON_RESOURCELIMIT.
1819 - Don't check for whether the address we're using for outbound
1820 connections has changed until after the outbound connection has
1821 completed. On Windows, getsockname() doesn't succeed until the
1822 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1823 - Don't hold a Windows file handle open for every file mapping;
1824 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1826 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1827 bugfix on 0.2.1.10-alpha.
1828 - If we fail to write a microdescriptor to the disk cache, do not
1829 continue replacing the old microdescriptor file. Fixes bug 2954;
1830 bugfix on 0.2.2.6-alpha.
1832 o Minor bugfixes (log messages, path selection):
1833 - Downgrade "set buildtimeout to low value" messages to "info"
1834 severity; they were never an actual problem, there was never
1835 anything reasonable to do about them, and they tended to spam logs
1836 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1837 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1838 more information to it, so that we can track it down in case it
1839 returns again. Mitigates bug 5235.
1840 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
1841 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
1842 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
1843 - Issue a log message if a guard completes less than 40% of your
1844 circuits. Threshold is configurable by torrc option
1845 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
1846 additional, off-by-default code to disable guards which fail too
1847 many circuits. Addresses ticket 5458.
1849 o Minor bugfixes (log messages, client):
1850 - Downgrade "Got a certificate, but we already have it" log messages
1851 from warning to info, except when we're a dirauth. Fixes bug 5238;
1852 bugfix on 0.2.1.7-alpha.
1853 - Fix the log message describing how we work around discovering
1854 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1855 4837; bugfix on 0.2.2.9-alpha.
1856 - When logging about a disallowed .exit name, do not also call it
1857 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1858 - Fix a log message suggesting that people contact a non-existent
1859 email address. Fixes bug 3448.
1860 - Rephrase the log message emitted if the TestSocks check is
1861 successful. Patch from Fabian Keil; fixes bug 4094.
1862 - Log (at debug level) whenever a circuit's purpose is changed.
1863 - Log SSL state transitions at log level DEBUG, log domain
1864 HANDSHAKE. This can be useful for debugging censorship events.
1865 Implements ticket 3264.
1866 - We now log which torrc file we're using on startup. Implements
1868 - Rate-limit log messages when asked to connect anonymously to
1869 a private address. When these hit, they tended to hit fast and
1870 often. Also, don't bother trying to connect to addresses that we
1871 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1872 reply makes us think we have been lied to, even when the address the
1873 client tried to connect to was "localhost." Resolves ticket 2822.
1875 o Minor bugfixes (log messages, non-client):
1876 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1877 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1878 - Don't log that we have "decided to publish new relay descriptor"
1879 unless we are actually publishing a descriptor. Fixes bug 3942;
1880 bugfix on 0.2.2.28-beta.
1881 - Log which authority we're missing votes from when we go to fetch
1882 them from the other auths.
1883 - Replace "Sending publish request" log messages with "Launching
1884 upload", so that they no longer confusingly imply that we're
1885 sending something to a directory we might not even be connected
1886 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1887 - Warn when Tor is configured to use accounting in a way that can
1888 link a hidden service to some other hidden service or public
1889 address. Resolves ticket 6490.
1890 - Fix a minor formatting issue in one of tor-gencert's error messages.
1894 - Update to the latest version of the tinytest unit testing framework.
1895 This includes a couple of bugfixes that can be relevant for
1896 running forked unit tests on Windows, and removes all reserved
1898 - Avoid a false positive in the util/threads unit test by increasing
1899 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1900 - Make it possible to set the TestingTorNetwork configuration
1901 option using AlternateDirAuthority and AlternateBridgeAuthority
1902 as an alternative to setting DirServer. Addresses ticket 6377.
1903 - Add a unit test for the environment_variable_names_equal() function.
1904 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1905 - Numerous new unit tests for functions in util.c and address.c by
1907 - The long-disabled benchmark tests are now split into their own
1908 ./src/test/bench binary.
1909 - The benchmark tests can now use more accurate timers than
1910 gettimeofday() when such timers are available.
1911 - Use tt_assert(), not tor_assert(), for checking for test failures.
1912 This makes the unit tests more able to go on in the event that
1915 o Build improvements:
1916 - Use the dead_strip option when building Tor on OS X. This reduces
1917 binary size by almost 19% when linking openssl and libevent
1918 statically, which we do for Tor Browser Bundle.
1919 - Provide a better error message about possible OSX Asciidoc failure
1920 reasons. Fixes bug 6436.
1921 - Detect attempts to build Tor on (as yet hypothetical) versions
1922 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1923 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1924 - On Windows, we now define the _WIN32_WINNT macros only if they
1925 are not already defined. This lets the person building Tor decide,
1926 if they want, to require a later version of Windows.
1927 - Our autogen.sh script now uses autoreconf to launch autoconf,
1928 automake, and so on. This is more robust against some of the failure
1929 modes associated with running the autotools pieces on their own.
1930 - Running "make version" now displays the version of Tor that
1931 we're about to build. Idea from katmagic; resolves issue 4400.
1932 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
1933 on 0.2.2.4-alpha; fixes bug 3427.
1934 - New --enable-static-tor configure option for building Tor as
1935 statically as possible. Idea, general hackery and thoughts from
1936 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
1938 - Limited, experimental support for building with nmake and MSVC.
1940 o Build requirements:
1941 - Building Tor with bufferevent support now requires Libevent
1942 2.0.13-stable or later. Previous versions of Libevent had bugs in
1943 SSL-related bufferevents and related issues that would make Tor
1944 work badly with bufferevents. Requiring 2.0.13-stable also allows
1945 Tor with bufferevents to take advantage of Libevent APIs
1946 introduced after 2.0.8-rc.
1947 - Our build system requires automake 1.6 or later to create the
1948 Makefile.in files. Previously, you could have used 1.4.
1949 This only affects developers and people building Tor from git;
1950 people who build Tor from the source distribution without changing
1951 the Makefile.am files should be fine.
1952 - Detect when we try to build on a platform that doesn't define
1953 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1955 o Build fixes (compile/link):
1956 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1957 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1959 - When building with --enable-static-tor on OpenBSD, do not
1960 erroneously attempt to link -lrt. Fixes bug 5103.
1961 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1962 that IPv6 stuff will compile on MSVC, and compilation issues
1963 will be easier to track down. Fixes bug 5861.
1964 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1965 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1966 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1967 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1969 o Build fixes (other):
1970 - Use the _WIN32 macro throughout our code to detect Windows.
1971 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1973 - Properly handle the case where the build-tree is not the same
1974 as the source tree when generating src/common/common_sha1.i,
1975 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1976 bugfix on 0.2.0.1-alpha.
1977 - During configure, search for library containing cos function as
1978 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1979 against libm was hard-coded before. Fixes the first part of bug
1980 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1982 - Prevent a false positive from the check-spaces script, by disabling
1983 the "whitespace between function name and (" check for functions
1986 o Packaging (RPM) changes:
1987 - Update our default RPM spec files to work with mock and rpmbuild
1988 on RHEL/Fedora. They have an updated set of dependencies and
1989 conflicts, a fix for an ancient typo when creating the "_tor"
1990 user, and better instructions. Thanks to Ondrej Mikle for the
1991 patch series. Fixes bug 6043.
1992 - On OpenSUSE, create the /var/run/tor directory on startup if it
1993 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
1995 o Code refactoring (safety):
1996 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1997 10 lines. Also, don't nest them. Doing so in the past has
1998 led to hard-to-debug code. The new style is to use the
1999 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2000 - Use macros to indicate OpenSSL versions, so we don't need to worry
2001 about accidental hexadecimal bit shifts.
2002 - Use tor_sscanf() in place of scanf() in more places through the
2003 code. This makes us a little more locale-independent, and
2004 should help shut up code-analysis tools that can't tell
2005 a safe sscanf string from a dangerous one.
2006 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2007 - Use the smartlist_add_asprintf() alias more consistently.
2009 o Code refactoring (consolidate):
2010 - A major revision to our internal node-selecting and listing logic.
2011 Tor already had at least two major ways to look at the question of
2012 "which Tor servers do we know about": a list of router descriptors,
2013 and a list of entries in the current consensus. With
2014 microdescriptors, we're adding a third. Having so many systems
2015 without an abstraction layer over them was hurting the codebase.
2016 Now, we have a new "node_t" abstraction that presents a consistent
2017 interface to a client's view of a Tor node, and holds (nearly) all
2018 of the mutable state formerly in routerinfo_t and routerstatus_t.
2019 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2020 Libevent's notion of cached time when possible.
2021 - Remove duplicate code for invoking getrlimit() from control.c.
2022 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2023 own homebrewed ssl_state_to_string() replacement. Patch from
2024 Emile Snyder. Fixes bug 4653.
2025 - Change the symmetric cipher interface so that creating and
2026 initializing a stream cipher are no longer separate functions.
2028 o Code refactoring (separate):
2029 - Make a new "entry connection" struct as an internal subtype of "edge
2030 connection", to simplify the code and make exit connections smaller.
2031 - Split connection_about_to_close() into separate functions for each
2033 - Rewrite the listener-selection logic so that parsing which ports
2034 we want to listen on is now separate from binding to the ports
2037 o Code refactoring (name changes):
2038 - Rename a handful of old identifiers, mostly related to crypto
2039 structures and crypto functions. By convention, our "create an
2040 object" functions are called "type_new()", our "free an object"
2041 functions are called "type_free()", and our types indicate that
2042 they are types only with a final "_t". But a handful of older
2043 types and functions broke these rules, with function names like
2044 "type_create" or "subsystem_op_type", or with type names like
2046 - Rename Tor functions that turn strings into addresses, so that
2047 "parse" indicates that no hostname resolution occurs, and
2048 "lookup" indicates that hostname resolution may occur. This
2049 should help prevent mistakes in the future. Fixes bug 3512.
2050 - Use the name "CERTS" consistently to refer to the new cell type;
2051 we were calling it CERT in some places and CERTS in others.
2052 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2053 invalid value, rather than just -1.
2054 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2055 can pick them up when the tests aren't disabled. Bugfix on
2056 0.2.2.4-alpha which introduced tinytest.
2058 o Code refactoring (other):
2059 - Defensively refactor rend_mid_rendezvous() so that protocol
2060 violations and length checks happen in the beginning. Fixes
2062 - Remove the pure attribute from all functions that used it
2063 previously. In many cases we assigned it incorrectly, because the
2064 functions might assert or call impure functions, and we don't have
2065 evidence that keeping the pure attribute is worthwhile. Implements
2066 changes suggested in ticket 4421.
2067 - Move the replay-detection cache for the RSA-encrypted parts of
2068 INTRODUCE2 cells to the introduction point data structures.
2069 Previously, we would use one replay-detection cache per hidden
2070 service. Required by fix for bug 3460.
2071 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2072 no longer link against Libevent: they never used it, but
2073 our library structure used to force them to link it.
2075 o Removed features and files:
2076 - Remove all internal support for unpadded RSA. We never used it, and
2077 it would be a bad idea to start.
2078 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2080 - Remove some redundant #include directives throughout the code.
2081 Patch from Andrea Gelmini.
2082 - Remove some old code to remember statistics about which descriptors
2083 we've served as a directory mirror. The feature wasn't used and
2084 is outdated now that microdescriptors are around.
2085 - Remove some old code to work around even older versions of Tor that
2086 used forked processes to handle DNS requests. Such versions of Tor
2087 are no longer in use as relays.
2088 - The "torify" script no longer supports the "tsocks" socksifier
2089 tool, since tsocks doesn't support DNS and UDP right for Tor.
2090 Everyone should be using torsocks instead. Fixes bugs 3530 and
2091 5180. Based on a patch by "ugh".
2092 - Remove the torrc.bridge file: we don't use it for anything, and
2093 it had become badly desynchronized from torrc.sample. Resolves
2097 - Begin a doc/state-contents.txt file to explain the contents of
2098 the Tor state file. Fixes bug 2987.
2099 - Clarify the documentation for the Alternate*Authority options.
2101 - Document the --defaults-torrc option, and the new semantics for
2102 overriding, extending, and clearing lists of options. Closes
2104 - Add missing man page documentation for consensus and microdesc
2105 files. Resolves ticket 6732.
2106 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2108 o Documentation fixes:
2109 - Improve the manual's documentation for the NT Service command-line
2110 options. Addresses ticket 3964.
2111 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2112 - Document the changes to the ORPort and DirPort options, and the
2113 fact that {OR/Dir}ListenAddress is now unnecessary (and
2114 therefore deprecated). Resolves ticket 5597.
2115 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2116 - Clarify that hidden services are TCP only. Fixes bug 6024.
2119 Changes in version 0.2.2.39 - 2012-09-11
2120 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
2124 - Fix an assertion failure in tor_timegm() that could be triggered
2125 by a badly formatted directory object. Bug found by fuzzing with
2126 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
2127 - Do not crash when comparing an address with port value 0 to an
2128 address policy. This bug could have been used to cause a remote
2129 assertion failure by or against directory authorities, or to
2130 allow some applications to crash clients. Fixes bug 6690; bugfix
2134 Changes in version 0.2.2.38 - 2012-08-12
2135 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
2136 attack that could in theory leak path information.
2139 - Avoid an uninitialized memory read when reading a vote or consensus
2140 document that has an unrecognized flavor name. This read could
2141 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
2142 - Try to leak less information about what relays a client is
2143 choosing to a side-channel attacker. Previously, a Tor client would
2144 stop iterating through the list of available relays as soon as it
2145 had chosen one, thus finishing a little earlier when it picked
2146 a router earlier in the list. If an attacker can recover this
2147 timing information (nontrivial but not proven to be impossible),
2148 they could learn some coarse-grained information about which relays
2149 a client was picking (middle nodes in particular are likelier to
2150 be affected than exits). The timing attack might be mitigated by
2151 other factors (see bug 6537 for some discussion), but it's best
2152 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2155 Changes in version 0.2.2.37 - 2012-06-06
2156 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2157 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2161 - Work around a bug in OpenSSL that broke renegotiation with TLS
2162 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2163 the v2 Tor connection protocol when both sides were using OpenSSL
2164 1.0.1 would fail. Resolves ticket 6033.
2165 - When waiting for a client to renegotiate, don't allow it to add
2166 any bytes to the input buffer. This fixes a potential DoS issue.
2167 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2168 - Fix an edge case where if we fetch or publish a hidden service
2169 descriptor, we might build a 4-hop circuit and then use that circuit
2170 for exiting afterwards -- even if the new last hop doesn't obey our
2171 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2174 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2175 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2178 - Tell GCC and Clang to check for any errors in format strings passed
2179 to the tor_v*(print|scan)f functions.
2182 Changes in version 0.2.2.36 - 2012-05-24
2183 Tor 0.2.2.36 updates the addresses for two of the eight directory
2184 authorities, fixes some potential anonymity and security issues,
2185 and fixes several crash bugs.
2187 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2188 known flaws, and nobody should be using them. You should upgrade. If
2189 you're using a Linux or BSD and its packages are obsolete, stop using
2190 those packages and upgrade anyway.
2192 o Directory authority changes:
2193 - Change IP address for maatuska (v3 directory authority).
2194 - Change IP address for ides (v3 directory authority), and rename
2198 - When building or running with any version of OpenSSL earlier
2199 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2200 versions have a bug (CVE-2011-4576) in which their block cipher
2201 padding includes uninitialized data, potentially leaking sensitive
2202 information to any peer with whom they make a SSLv3 connection. Tor
2203 does not use SSL v3 by default, but a hostile client or server
2204 could force an SSLv3 connection in order to gain information that
2205 they shouldn't have been able to get. The best solution here is to
2206 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2207 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2208 to make sure that the bug can't happen.
2209 - Never use a bridge or a controller-supplied node as an exit, even
2210 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2211 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2212 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2213 - Only build circuits if we have a sufficient threshold of the total
2214 descriptors that are marked in the consensus with the "Exit"
2215 flag. This mitigates an attack proposed by wanoskarnet, in which
2216 all of a client's bridges collude to restrict the exit nodes that
2217 the client knows about. Fixes bug 5343.
2218 - Provide controllers with a safer way to implement the cookie
2219 authentication mechanism. With the old method, if another locally
2220 running program could convince a controller that it was the Tor
2221 process, then that program could trick the controller into telling
2222 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2223 authentication method uses a challenge-response approach to prevent
2224 this attack. Fixes bug 5185; implements proposal 193.
2227 - Avoid logging uninitialized data when unable to decode a hidden
2228 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2229 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2230 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2232 - Fix builds when the path to sed, openssl, or sha1sum contains
2233 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2235 - Correct our replacements for the timeradd() and timersub() functions
2236 on platforms that lack them (for example, Windows). The timersub()
2237 function is used when expiring circuits, while timeradd() is
2238 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2239 bugfix on 0.2.2.24-alpha.
2240 - Fix the SOCKET_OK test that we use to tell when socket
2241 creation fails so that it works on Win64. Fixes part of bug 4533;
2242 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2245 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2246 Fixes bug 5346; bugfix on 0.0.8pre3.
2247 - Make our number-parsing functions always treat too-large values
2248 as an error, even when those values exceed the width of the
2249 underlying type. Previously, if the caller provided these
2250 functions with minima or maxima set to the extreme values of the
2251 underlying integer type, these functions would return those
2252 values on overflow rather than treating overflow as an error.
2253 Fixes part of bug 5786; bugfix on 0.0.9.
2254 - Older Linux kernels erroneously respond to strange nmap behavior
2255 by having accept() return successfully with a zero-length
2256 socket. When this happens, just close the connection. Previously,
2257 we would try harder to learn the remote address: but there was
2258 no such remote address to learn, and our method for trying to
2259 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2260 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2261 - Correct parsing of certain date types in parse_http_time().
2262 Without this patch, If-Modified-Since would behave
2263 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2264 Esteban Manchado Velázques.
2265 - Change the BridgePassword feature (part of the "bridge community"
2266 design, which is not yet implemented) to use a time-independent
2267 comparison. The old behavior might have allowed an adversary
2268 to use timing to guess the BridgePassword value. Fixes bug 5543;
2269 bugfix on 0.2.0.14-alpha.
2270 - Detect and reject certain misformed escape sequences in
2271 configuration values. Previously, these values would cause us
2272 to crash if received in a torrc file or over an authenticated
2273 control port. Bug found by Esteban Manchado Velázquez, and
2274 independently by Robert Connolly from Matta Consulting who further
2275 noted that it allows a post-authentication heap overflow. Patch
2276 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2277 bugfix on 0.2.0.16-alpha.
2278 - Fix a compile warning when using the --enable-openbsd-malloc
2279 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2280 - During configure, detect when we're building with clang version
2281 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2282 CFLAGS. clang doesn't support them yet.
2283 - When sending an HTTP/1.1 proxy request, include a Host header.
2284 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2285 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2286 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2287 - If we hit the error case where routerlist_insert() replaces an
2288 existing (old) server descriptor, make sure to remove that
2289 server descriptor from the old_routers list. Fix related to bug
2290 1776. Bugfix on 0.2.2.18-alpha.
2292 o Minor bugfixes (documentation and log messages):
2293 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2294 Fixes bug 4856; bugfix on Tor 0.0.6.
2295 - Update "ClientOnly" man page entry to explain that there isn't
2296 really any point to messing with it. Resolves ticket 5005.
2297 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2298 directory authority option (introduced in Tor 0.2.2.34).
2299 - Downgrade the "We're missing a certificate" message from notice
2300 to info: people kept mistaking it for a real problem, whereas it
2301 is seldom the problem even when we are failing to bootstrap. Fixes
2302 bug 5067; bugfix on 0.2.0.10-alpha.
2303 - Correctly spell "connect" in a log message on failure to create a
2304 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2305 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2306 circuits. Fixes issue 5259.
2309 - Directory authorities now reject versions of Tor older than
2310 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2311 inclusive. These versions accounted for only a small fraction of
2312 the Tor network, and have numerous known security issues. Resolves
2314 - Update to the May 1 2012 Maxmind GeoLite Country database.
2317 - When sending or relaying a RELAY_EARLY cell, we used to convert
2318 it to a RELAY cell if the connection was using the v1 link
2319 protocol. This was a workaround for older versions of Tor, which
2320 didn't handle RELAY_EARLY cells properly. Now that all supported
2321 versions can handle RELAY_EARLY cells, and now that we're enforcing
2322 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2323 remove this workaround. Addresses bug 4786.
2326 Changes in version 0.2.2.35 - 2011-12-16
2327 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2328 buffers code. Absolutely everybody should upgrade.
2330 The bug relied on an incorrect calculation when making data continuous
2331 in one of our IO buffers, if the first chunk of the buffer was
2332 misaligned by just the wrong amount. The miscalculation would allow an
2333 attacker to overflow a piece of heap-allocated memory. To mount this
2334 attack, the attacker would need to either open a SOCKS connection to
2335 Tor's SocksPort (usually restricted to localhost), or target a Tor
2336 instance configured to make its connections through a SOCKS proxy
2337 (which Tor does not do by default).
2339 Good security practice requires that all heap-overflow bugs should be
2340 presumed to be exploitable until proven otherwise, so we are treating
2341 this as a potential code execution attack. Please upgrade immediately!
2342 This bug does not affect bufferevents-based builds of Tor. Special
2343 thanks to "Vektor" for reporting this issue to us!
2345 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2346 crash bugs for unusual configurations, and a long-term bug that
2347 would prevent Tor from starting on Windows machines with draconian
2350 With this release, we remind everyone that 0.2.0.x has reached its
2351 formal end-of-life. Those Tor versions have many known flaws, and
2352 nobody should be using them. You should upgrade -- ideally to the
2353 0.2.2.x series. If you're using a Linux or BSD and its packages are
2354 obsolete, stop using those packages and upgrade anyway.
2356 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2357 longer receive support after some time in early 2012.
2360 - Fix a heap overflow bug that could occur when trying to pull
2361 data into the first chunk of a buffer, when that chunk had
2362 already had some data drained from it. Fixes CVE-2011-2778;
2363 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2364 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2365 that it doesn't attempt to allocate a socketpair. This could cause
2366 some problems on Windows systems with overzealous firewalls. Fix for
2367 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2369 - If we mark an OR connection for close based on a cell we process,
2370 don't process any further cells on it. We already avoid further
2371 reads on marked-for-close connections, but now we also discard the
2372 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2373 which was the first version where we might mark a connection for
2374 close based on processing a cell on it.
2375 - Correctly sanity-check that we don't underflow on a memory
2376 allocation (and then assert) for hidden service introduction
2377 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2378 bugfix on 0.2.1.5-alpha.
2379 - Fix a memory leak when we check whether a hidden service
2380 descriptor has any usable introduction points left. Fixes bug
2381 4424. Bugfix on 0.2.2.25-alpha.
2382 - Don't crash when we're running as a relay and don't have a GeoIP
2383 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2384 we've had in the 0.2.3.x branch already.
2385 - When running as a client, do not print a misleading (and plain
2386 wrong) log message that we're collecting "directory request"
2387 statistics: clients don't collect statistics. Also don't create a
2388 useless (because empty) stats file in the stats/ directory. Fixes
2389 bug 4353; bugfix on 0.2.2.34.
2392 - Detect failure to initialize Libevent. This fix provides better
2393 detection for future instances of bug 4457.
2394 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2395 function. This was eating up hideously large amounts of time on some
2396 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2397 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2398 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2400 - Don't warn about unused log_mutex in log.c when building with
2401 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2402 0.1.0.6-rc which introduced --disable-threads.
2403 - When configuring, starting, or stopping an NT service, stop
2404 immediately after the service configuration attempt has succeeded
2405 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2406 - When sending a NETINFO cell, include the original address
2407 received for the other side, not its canonical address. Found
2408 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2409 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2410 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2411 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2412 occurred when a client tried to fetch a descriptor for a bridge
2413 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2414 - Backport fixes for a pair of compilation warnings on Windows.
2415 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2416 - If we had ever tried to call tor_addr_to_str on an address of
2417 unknown type, we would have done a strdup on an uninitialized
2418 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2419 Reported by "troll_un".
2420 - Correctly detect and handle transient lookup failures from
2421 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2422 Reported by "troll_un".
2423 - Fix null-pointer access that could occur if TLS allocation failed.
2424 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2425 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2426 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2429 - Add two new config options for directory authorities:
2430 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2431 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2432 that is always sufficient to satisfy the bandwidth requirement for
2433 the Guard flag. Now it will be easier for researchers to simulate
2434 Tor networks with different values. Resolves ticket 4484.
2435 - When Tor ignores a hidden service specified in its configuration,
2436 include the hidden service's directory in the warning message.
2437 Previously, we would only tell the user that some hidden service
2438 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2439 - Update to the December 6 2011 Maxmind GeoLite Country database.
2441 o Packaging changes:
2442 - Make it easier to automate expert package builds on Windows,
2443 by removing an absolute path from makensis.exe command.
2446 Changes in version 0.2.1.32 - 2011-12-16
2447 Tor 0.2.1.32 backports important security and privacy fixes for
2448 oldstable. This release is intended only for package maintainers and
2449 others who cannot use the 0.2.2 stable series. All others should be
2450 using Tor 0.2.2.x or newer.
2452 The Tor 0.2.1.x series will reach formal end-of-life some time in
2453 early 2012; we will stop releasing patches for it then.
2455 o Major bugfixes (also included in 0.2.2.x):
2456 - Correctly sanity-check that we don't underflow on a memory
2457 allocation (and then assert) for hidden service introduction
2458 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2459 bugfix on 0.2.1.5-alpha.
2460 - Fix a heap overflow bug that could occur when trying to pull
2461 data into the first chunk of a buffer, when that chunk had
2462 already had some data drained from it. Fixes CVE-2011-2778;
2463 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2466 - Update to the December 6 2011 Maxmind GeoLite Country database.
2469 Changes in version 0.2.2.34 - 2011-10-26
2470 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2471 can deanonymize Tor users. Everybody should upgrade.
2473 The attack relies on four components: 1) Clients reuse their TLS cert
2474 when talking to different relays, so relays can recognize a user by
2475 the identity key in her cert. 2) An attacker who knows the client's
2476 identity key can probe each guard relay to see if that identity key
2477 is connected to that guard relay right now. 3) A variety of active
2478 attacks in the literature (starting from "Low-Cost Traffic Analysis
2479 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2480 discover the guard relays that a Tor user visiting the website is using.
2481 4) Clients typically pick three guards at random, so the set of guards
2482 for a given user could well be a unique fingerprint for her. This
2483 release fixes components #1 and #2, which is enough to block the attack;
2484 the other two remain as open research problems. Special thanks to
2485 "frosty_un" for reporting the issue to us!
2487 Clients should upgrade so they are no longer recognizable by the TLS
2488 certs they present. Relays should upgrade so they no longer allow a
2489 remote attacker to probe them to test whether unpatched clients are
2490 currently connected to them.
2492 This release also fixes several vulnerabilities that allow an attacker
2493 to enumerate bridge relays. Some bridge enumeration attacks still
2494 remain; see for example proposal 188.
2496 o Privacy/anonymity fixes (clients):
2497 - Clients and bridges no longer send TLS certificate chains on
2498 outgoing OR connections. Previously, each client or bridge would
2499 use the same cert chain for all outgoing OR connections until
2500 its IP address changes, which allowed any relay that the client
2501 or bridge contacted to determine which entry guards it is using.
2502 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2503 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2504 no longer considers that connection as suitable for satisfying a
2505 circuit EXTEND request. Now relays can protect clients from the
2506 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2507 - Directory authorities no longer assign the Guard flag to relays
2508 that haven't upgraded to the above "refuse EXTEND requests
2509 to client connections" fix. Now directory authorities can
2510 protect clients from the CVE-2011-2768 issue even if neither
2511 the clients nor the relays have upgraded yet. There's a new
2512 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2513 to let us transition smoothly, else tomorrow there would be no
2516 o Privacy/anonymity fixes (bridge enumeration):
2517 - Bridge relays now do their directory fetches inside Tor TLS
2518 connections, like all the other clients do, rather than connecting
2519 directly to the DirPort like public relays do. Removes another
2520 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2521 - Bridges relays now build circuits for themselves in a more similar
2522 way to how clients build them. Removes another avenue for
2523 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2524 when bridges were introduced.
2525 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2526 that they initiated. Relays could distinguish incoming bridge
2527 connections from client connections, creating another avenue for
2528 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2529 Found by "frosty_un".
2532 - Fix a crash bug when changing node restrictions while a DNS lookup
2533 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2535 - Don't launch a useless circuit after failing to use one of a
2536 hidden service's introduction points. Previously, we would
2537 launch a new introduction circuit, but not set the hidden service
2538 which that circuit was intended to connect to, so it would never
2539 actually be used. A different piece of code would then create a
2540 new introduction circuit correctly. Bug reported by katmagic and
2541 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2544 - Change an integer overflow check in the OpenBSD_Malloc code so
2545 that GCC is less likely to eliminate it as impossible. Patch
2546 from Mansour Moufid. Fixes bug 4059.
2547 - When a hidden service turns an extra service-side introduction
2548 circuit into a general-purpose circuit, free the rend_data and
2549 intro_key fields first, so we won't leak memory if the circuit
2550 is cannibalized for use as another service-side introduction
2551 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2552 - Bridges now skip DNS self-tests, to act a little more stealthily.
2553 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2554 bridges. Patch by "warms0x".
2555 - Fix internal bug-checking logic that was supposed to catch
2556 failures in digest generation so that it will fail more robustly
2557 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2558 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2559 - Report any failure in init_keys() calls launched because our
2560 IP address has changed. Spotted by Coverity Scan. Bugfix on
2561 0.1.1.4-alpha; fixes CID 484.
2563 o Minor bugfixes (log messages and documentation):
2564 - Remove a confusing dollar sign from the example fingerprint in the
2565 man page, and also make the example fingerprint a valid one. Fixes
2566 bug 4309; bugfix on 0.2.1.3-alpha.
2567 - The next version of Windows will be called Windows 8, and it has
2568 a major version of 6, minor version of 2. Correctly identify that
2569 version instead of calling it "Very recent version". Resolves
2570 ticket 4153; reported by funkstar.
2571 - Downgrade log messages about circuit timeout calibration from
2572 "notice" to "info": they don't require or suggest any human
2573 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2574 bugfix on 0.2.2.14-alpha.
2577 - Turn on directory request statistics by default and include them in
2578 extra-info descriptors. Don't break if we have no GeoIP database.
2579 Backported from 0.2.3.1-alpha; implements ticket 3951.
2580 - Update to the October 4 2011 Maxmind GeoLite Country database.
2583 Changes in version 0.2.1.31 - 2011-10-26
2584 Tor 0.2.1.31 backports important security and privacy fixes for
2585 oldstable. This release is intended only for package maintainers and
2586 others who cannot use the 0.2.2 stable series. All others should be
2587 using Tor 0.2.2.x or newer.
2589 o Security fixes (also included in 0.2.2.x):
2590 - Replace all potentially sensitive memory comparison operations
2591 with versions whose runtime does not depend on the data being
2592 compared. This will help resist a class of attacks where an
2593 adversary can use variations in timing information to learn
2594 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2595 implementation by Robert Ransom based partially on code by DJB.)
2596 - Fix an assert in parsing router descriptors containing IPv6
2597 addresses. This one took down the directory authorities when
2598 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2600 o Privacy/anonymity fixes (also included in 0.2.2.x):
2601 - Clients and bridges no longer send TLS certificate chains on
2602 outgoing OR connections. Previously, each client or bridge would
2603 use the same cert chain for all outgoing OR connections until
2604 its IP address changes, which allowed any relay that the client
2605 or bridge contacted to determine which entry guards it is using.
2606 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2607 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2608 no longer considers that connection as suitable for satisfying a
2609 circuit EXTEND request. Now relays can protect clients from the
2610 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2611 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2612 that they initiated. Relays could distinguish incoming bridge
2613 connections from client connections, creating another avenue for
2614 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2615 Found by "frosty_un".
2616 - When receiving a hidden service descriptor, check that it is for
2617 the hidden service we wanted. Previously, Tor would store any
2618 hidden service descriptors that a directory gave it, whether it
2619 wanted them or not. This wouldn't have let an attacker impersonate
2620 a hidden service, but it did let directories pre-seed a client
2621 with descriptors that it didn't want. Bugfix on 0.0.6.
2622 - Avoid linkability based on cached hidden service descriptors: forget
2623 all hidden service descriptors cached as a client when processing a
2624 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2625 - Make the bridge directory authority refuse to answer directory
2626 requests for "all" descriptors. It used to include bridge
2627 descriptors in its answer, which was a major information leak.
2628 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2629 - Don't attach new streams to old rendezvous circuits after SIGNAL
2630 NEWNYM. Previously, we would keep using an existing rendezvous
2631 circuit if it remained open (i.e. if it were kept open by a
2632 long-lived stream, or if a new stream were attached to it before
2633 Tor could notice that it was old and no longer in use). Bugfix on
2634 0.1.1.15-rc; fixes bug 3375.
2636 o Minor bugfixes (also included in 0.2.2.x):
2637 - When we restart our relay, we might get a successful connection
2638 from the outside before we've started our reachability tests,
2639 triggering a warning: "ORPort found reachable, but I have no
2640 routerinfo yet. Failing to inform controller of success." This
2641 bug was harmless unless Tor is running under a controller
2642 like Vidalia, in which case the controller would never get a
2643 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2645 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2646 enabled. Fixes bug 1526.
2647 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2648 anything since 0.2.1.16-rc.
2649 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2650 None of the cases where we did this before were wrong, but by making
2651 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2652 - Fix a rare crash bug that could occur when a client was configured
2653 with a large number of bridges. Fixes bug 2629; bugfix on
2654 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2655 - Correct the warning displayed when a rendezvous descriptor exceeds
2656 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2658 - Fix an uncommon assertion failure when running with DNSPort under
2659 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2660 - When warning about missing zlib development packages during compile,
2661 give the correct package names. Bugfix on 0.2.0.1-alpha.
2662 - Require that introduction point keys and onion keys have public
2663 exponent 65537. Bugfix on 0.2.0.10-alpha.
2664 - Do not crash when our configuration file becomes unreadable, for
2665 example due to a permissions change, between when we start up
2666 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2668 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2670 - Always NUL-terminate the sun_path field of a sockaddr_un before
2671 passing it to the kernel. (Not a security issue: kernels are
2672 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2673 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2674 - Don't stack-allocate the list of supplementary GIDs when we're
2675 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2676 could take up to 256K, which is way too much stack. Found by
2677 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2679 o Minor bugfixes (only in 0.2.1.x):
2680 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2681 rely on them. Bugfix on 0.2.1.30.
2682 - Use git revisions instead of svn revisions when generating our
2683 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2685 o Minor features (also included in 0.2.2.x):
2686 - Adjust the expiration time on our SSL session certificates to
2687 better match SSL certs seen in the wild. Resolves ticket 4014.
2688 - Allow nameservers with IPv6 address. Resolves bug 2574.
2689 - Update to the October 4 2011 Maxmind GeoLite Country database.
2692 Changes in version 0.2.2.33 - 2011-09-13
2693 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2694 TLS handshake that makes relays and bridges that run this new version
2695 reachable from Iran again.
2698 - Avoid an assertion failure when reloading a configuration with
2699 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2700 3923; bugfix on 0.2.2.25-alpha.
2702 o Minor features (security):
2703 - Check for replays of the public-key encrypted portion of an
2704 INTRODUCE1 cell, in addition to the current check for replays of
2705 the g^x value. This prevents a possible class of active attacks
2706 by an attacker who controls both an introduction point and a
2707 rendezvous point, and who uses the malleability of AES-CTR to
2708 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2709 that these attacks are infeasible (requiring the attacker to send
2710 on the order of zettabytes of altered cells in a short interval),
2711 but we'd rather block them off in case there are any classes of
2712 this attack that we missed. Reported by Willem Pinckaers.
2715 - Adjust the expiration time on our SSL session certificates to
2716 better match SSL certs seen in the wild. Resolves ticket 4014.
2717 - Change the default required uptime for a relay to be accepted as
2718 a HSDir (hidden service directory) from 24 hours to 25 hours.
2719 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2720 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2721 authorities to abstain from voting on assignment of the HSDir
2722 consensus flag. Related to bug 2649.
2723 - Update to the September 6 2011 Maxmind GeoLite Country database.
2725 o Minor bugfixes (documentation and log messages):
2726 - Correct the man page to explain that HashedControlPassword and
2727 CookieAuthentication can both be set, in which case either method
2728 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2729 when we decided to allow these config options to both be set. Issue
2731 - Demote the 'replay detected' log message emitted when a hidden
2732 service receives the same Diffie-Hellman public key in two different
2733 INTRODUCE2 cells to info level. A normal Tor client can cause that
2734 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2735 fixes part of bug 2442.
2736 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2737 level. There is nothing that a hidden service's operator can do
2738 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2740 - Clarify a log message specifying the characters permitted in
2741 HiddenServiceAuthorizeClient client names. Previously, the log
2742 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2743 given the impression that every ASCII character between "+" and "_"
2744 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2747 - Provide a substitute implementation of lround() for MSVC, which
2748 apparently lacks it. Patch from Gisle Vanem.
2749 - Clean up some code issues that prevented Tor from building on older
2750 BSDs. Fixes bug 3894; reported by "grarpamp".
2751 - Search for a platform-specific version of "ar" when cross-compiling.
2752 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2755 Changes in version 0.2.2.32 - 2011-08-27
2756 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2757 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2758 a founder of the PETS community, a leader in our field, a mentor,
2759 and a friend. He left us with these words: "I had the possibility
2760 to contribute to this world that is not as it should be. I hope I
2761 could help in some areas to make the world a better place, and that
2762 I could also encourage other people to be engaged in improving the
2763 world. Please, stay engaged. This world needs you, your love, your
2764 initiative -- now I cannot be part of that anymore."
2766 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2767 ready. More than two years in the making, this release features improved
2768 client performance and hidden service reliability, better compatibility
2769 for Android, correct behavior for bridges that listen on more than
2770 one address, more extensible and flexible directory object handling,
2771 better reporting of network statistics, improved code security, and
2772 many many other features and bugfixes.
2774 o Major features (client performance):
2775 - When choosing which cells to relay first, relays now favor circuits
2776 that have been quiet recently, to provide lower latency for
2777 low-volume circuits. By default, relays enable or disable this
2778 feature based on a setting in the consensus. They can override
2779 this default by using the new "CircuitPriorityHalflife" config
2780 option. Design and code by Ian Goldberg, Can Tang, and Chris
2782 - Directory authorities now compute consensus weightings that instruct
2783 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
2784 and no flag. Clients use these weightings to distribute network load
2785 more evenly across these different relay types. The weightings are
2786 in the consensus so we can change them globally in the future. Extra
2787 thanks to "outofwords" for finding some nasty security bugs in
2788 the first implementation of this feature.
2790 o Major features (client performance, circuit build timeout):
2791 - Tor now tracks how long it takes to build client-side circuits
2792 over time, and adapts its timeout to local network performance.
2793 Since a circuit that takes a long time to build will also provide
2794 bad performance, we get significant latency improvements by
2795 discarding the slowest 20% of circuits. Specifically, Tor creates
2796 circuits more aggressively than usual until it has enough data
2797 points for a good timeout estimate. Implements proposal 151.
2798 - Circuit build timeout constants can be controlled by consensus
2799 parameters. We set good defaults for these parameters based on
2800 experimentation on broadband and simulated high-latency links.
2801 - Circuit build time learning can be disabled via consensus parameter
2802 or by the client via a LearnCircuitBuildTimeout config option. We
2803 also automatically disable circuit build time calculation if either
2804 AuthoritativeDirectory is set, or if we fail to write our state
2805 file. Implements ticket 1296.
2807 o Major features (relays use their capacity better):
2808 - Set SO_REUSEADDR socket option on all sockets, not just
2809 listeners. This should help busy exit nodes avoid running out of
2810 useable ports just because all the ports have been used in the
2811 near past. Resolves issue 2850.
2812 - Relays now save observed peak bandwidth throughput rates to their
2813 state file (along with total usage, which was already saved),
2814 so that they can determine their correct estimated bandwidth on
2815 restart. Resolves bug 1863, where Tor relays would reset their
2816 estimated bandwidth to 0 after restarting.
2817 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
2818 should give us approximately 40-50% more Guard-flagged nodes,
2819 improving the anonymity the Tor network can provide and also
2820 decreasing the dropoff in throughput that relays experience when
2821 they first get the Guard flag.
2822 - Directory authorities now take changes in router IP address and
2823 ORPort into account when determining router stability. Previously,
2824 if a router changed its IP or ORPort, the authorities would not
2825 treat it as having any downtime for the purposes of stability
2826 calculation, whereas clients would experience downtime since the
2827 change would take a while to propagate to them. Resolves issue 1035.
2828 - New AccelName and AccelDir options add support for dynamic OpenSSL
2829 hardware crypto acceleration engines.
2831 o Major features (relays control their load better):
2832 - Exit relays now try harder to block exit attempts from unknown
2833 relays, to make it harder for people to use them as one-hop proxies
2834 a la tortunnel. Controlled by the refuseunknownexits consensus
2835 parameter (currently enabled), or you can override it on your
2836 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
2837 based on a variant of proposal 163.
2838 - Add separate per-conn write limiting to go with the per-conn read
2839 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
2840 but never per-conn write limits.
2841 - New consensus params "bwconnrate" and "bwconnburst" to let us
2842 rate-limit client connections as they enter the network. It's
2843 controlled in the consensus so we can turn it on and off for
2844 experiments. It's starting out off. Based on proposal 163.
2846 o Major features (controllers):
2847 - Export GeoIP information on bridge usage to controllers even if we
2848 have not yet been running for 24 hours. Now Vidalia bridge operators
2849 can get more accurate and immediate feedback about their
2850 contributions to the network.
2851 - Add an __OwningControllerProcess configuration option and a
2852 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2853 that when it exits, Tor will shut down. Implements feature 3049.
2855 o Major features (directory authorities):
2856 - Directory authorities now create, vote on, and serve multiple
2857 parallel formats of directory data as part of their voting process.
2858 Partially implements Proposal 162: "Publish the consensus in
2860 - Directory authorities now agree on and publish small summaries
2861 of router information that clients can use in place of regular
2862 server descriptors. This transition will allow Tor 0.2.3 clients
2863 to use far less bandwidth for downloading information about the
2864 network. Begins the implementation of Proposal 158: "Clients
2865 download consensus + microdescriptors".
2866 - The directory voting system is now extensible to use multiple hash
2867 algorithms for signatures and resource selection. Newer formats
2868 are signed with SHA256, with a possibility for moving to a better
2869 hash algorithm in the future.
2870 - Directory authorities can now vote on arbitary integer values as
2871 part of the consensus process. This is designed to help set
2872 network-wide parameters. Implements proposal 167.
2874 o Major features and bugfixes (node selection):
2875 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2876 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
2877 options. Previously, we had been ambiguous in describing what
2878 counted as an "exit" node, and what operations exactly "StrictNodes
2879 0" would permit. This created confusion when people saw nodes built
2880 through unexpected circuits, and made it hard to tell real bugs from
2881 surprises. Now the intended behavior is:
2882 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2883 a node that delivers user traffic outside the Tor network.
2884 . "Entry", in the context of EntryNodes, means a node used as the
2885 first hop of a multihop circuit. It doesn't include direct
2886 connections to directory servers.
2887 . "ExcludeNodes" applies to all nodes.
2888 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2889 StrictNodes is set, Tor should avoid all nodes listed in
2890 ExcludeNodes, even when it will make user requests fail. When
2891 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2892 whenever it can, except when it must use an excluded node to
2893 perform self-tests, connect to a hidden service, provide a
2894 hidden service, fulfill a .exit request, upload directory
2895 information, or fetch directory information.
2896 Collectively, the changes to implement the behavior fix bug 1090.
2897 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
2898 change during a config reload, mark and discard all our origin
2899 circuits. This fix should address edge cases where we change the
2900 config options and but then choose a circuit that we created before
2902 - Make EntryNodes config option much more aggressive even when
2903 StrictNodes is not set. Before it would prepend your requested
2904 entrynodes to your list of guard nodes, but feel free to use others
2905 after that. Now it chooses only from your EntryNodes if any of
2906 those are available, and only falls back to others if a) they're
2907 all down and b) StrictNodes is not set.
2908 - Now we refresh your entry guards from EntryNodes at each consensus
2909 fetch -- rather than just at startup and then they slowly rot as
2910 the network changes.
2911 - Add support for the country code "{??}" in torrc options like
2912 ExcludeNodes, to indicate all routers of unknown country. Closes
2914 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2915 a node is listed in both, it's treated as excluded.
2916 - ExcludeNodes now applies to directory nodes -- as a preference if
2917 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2918 Don't exclude all the directory authorities and set StrictNodes to 1
2919 unless you really want your Tor to break.
2920 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2921 - ExcludeExitNodes now overrides .exit requests.
2922 - We don't use bridges listed in ExcludeNodes.
2923 - When StrictNodes is 1:
2924 . We now apply ExcludeNodes to hidden service introduction points
2925 and to rendezvous points selected by hidden service users. This
2926 can make your hidden service less reliable: use it with caution!
2927 . If we have used ExcludeNodes on ourself, do not try relay
2928 reachability self-tests.
2929 . If we have excluded all the directory authorities, we will not
2930 even try to upload our descriptor if we're a relay.
2931 . Do not honor .exit requests to an excluded node.
2932 - When the set of permitted nodes changes, we now remove any mappings
2933 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2935 - We never cannibalize a circuit that had excluded nodes on it, even
2936 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
2937 - Improve log messages related to excluded nodes.
2939 o Major features (misc):
2940 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
2941 to help Tor build correctly for Android phones.
2942 - The options SocksPort, ControlPort, and so on now all accept a
2943 value "auto" that opens a socket on an OS-selected port. A
2944 new ControlPortWriteToFile option tells Tor to write its
2945 actual control port or ports to a chosen file. If the option
2946 ControlPortFileGroupReadable is set, the file is created as
2947 group-readable. Now users can run two Tor clients on the same
2948 system without needing to manually mess with parameters. Resolves
2949 part of ticket 3076.
2950 - Tor now supports tunneling all of its outgoing connections over
2951 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
2952 configuration options. Code by Christopher Davis.
2954 o Code security improvements:
2955 - Replace all potentially sensitive memory comparison operations
2956 with versions whose runtime does not depend on the data being
2957 compared. This will help resist a class of attacks where an
2958 adversary can use variations in timing information to learn
2959 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2960 implementation by Robert Ransom based partially on code by DJB.)
2961 - Enable Address Space Layout Randomization (ASLR) and Data Execution
2962 Prevention (DEP) by default on Windows to make it harder for
2963 attackers to exploit vulnerabilities. Patch from John Brooks.
2964 - New "--enable-gcc-hardening" ./configure flag (off by default)
2965 to turn on gcc compile time hardening options. It ensures
2966 that signed ints have defined behavior (-fwrapv), enables
2967 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
2968 with canaries (-fstack-protector-all), turns on ASLR protection if
2969 supported by the kernel (-fPIE, -pie), and adds additional security
2970 related warnings. Verified to work on Mac OS X and Debian Lenny.
2971 - New "--enable-linker-hardening" ./configure flag (off by default)
2972 to turn on ELF specific hardening features (relro, now). This does
2973 not work with Mac OS X or any other non-ELF binary format.
2974 - Always search the Windows system directory for system DLLs, and
2975 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
2976 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
2977 current and future memory pages via mlockall(). On supported
2978 platforms (modern Linux and probably BSD but not Windows or OS X),
2979 this should effectively disable any and all attempts to page out
2980 memory. This option requires that you start your Tor as root --
2981 if you use DisableAllSwap, please consider using the User option
2982 to properly reduce the privileges of your Tor.
2984 o Major bugfixes (crashes):
2985 - Fix crash bug on platforms where gmtime and localtime can return
2986 NULL. Windows 7 users were running into this one. Fixes part of bug
2987 2077. Bugfix on all versions of Tor. Found by boboper.
2988 - Introduce minimum/maximum values that clients will believe
2989 from the consensus. Now we'll have a better chance to avoid crashes
2990 or worse when a consensus param has a weird value.
2991 - Fix a rare crash bug that could occur when a client was configured
2992 with a large number of bridges. Fixes bug 2629; bugfix on
2993 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2994 - Do not crash when our configuration file becomes unreadable, for
2995 example due to a permissions change, between when we start up
2996 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2998 - If we're in the pathological case where there's no exit bandwidth
2999 but there is non-exit bandwidth, or no guard bandwidth but there
3000 is non-guard bandwidth, don't crash during path selection. Bugfix
3002 - Fix a crash bug when trying to initialize the evdns module in
3003 Libevent 2. Bugfix on 0.2.1.16-rc.
3005 o Major bugfixes (stability):
3006 - Fix an assert in parsing router descriptors containing IPv6
3007 addresses. This one took down the directory authorities when
3008 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3009 - Fix an uncommon assertion failure when running with DNSPort under
3010 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3011 - Treat an unset $HOME like an empty $HOME rather than triggering an
3012 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
3013 - More gracefully handle corrupt state files, removing asserts
3014 in favor of saving a backup and resetting state.
3015 - Instead of giving an assertion failure on an internal mismatch
3016 on estimated freelist size, just log a BUG warning and try later.
3017 Mitigates but does not fix bug 1125.
3018 - Fix an assert that got triggered when using the TestingTorNetwork
3019 configuration option and then issuing a GETINFO config-text control
3020 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3021 - If the cached cert file is unparseable, warn but don't exit.
3023 o Privacy fixes (relays/bridges):
3024 - Don't list Windows capabilities in relay descriptors. We never made
3025 use of them, and maybe it's a bad idea to publish them. Bugfix
3027 - If the Nickname configuration option isn't given, Tor would pick a
3028 nickname based on the local hostname as the nickname for a relay.
3029 Because nicknames are not very important in today's Tor and the
3030 "Unnamed" nickname has been implemented, this is now problematic
3031 behavior: It leaks information about the hostname without being
3032 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3033 introduced the Unnamed nickname. Reported by tagnaq.
3034 - Maintain separate TLS contexts and certificates for incoming and
3035 outgoing connections in bridge relays. Previously we would use the
3036 same TLS contexts and certs for incoming and outgoing connections.
3037 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3038 - Maintain separate identity keys for incoming and outgoing TLS
3039 contexts in bridge relays. Previously we would use the same
3040 identity keys for incoming and outgoing TLS contexts. Bugfix on
3041 0.2.0.3-alpha; addresses the other half of bug 988.
3042 - Make the bridge directory authority refuse to answer directory
3043 requests for "all descriptors". It used to include bridge
3044 descriptors in its answer, which was a major information leak.
3045 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3047 o Privacy fixes (clients):
3048 - When receiving a hidden service descriptor, check that it is for
3049 the hidden service we wanted. Previously, Tor would store any
3050 hidden service descriptors that a directory gave it, whether it
3051 wanted them or not. This wouldn't have let an attacker impersonate
3052 a hidden service, but it did let directories pre-seed a client
3053 with descriptors that it didn't want. Bugfix on 0.0.6.
3054 - Start the process of disabling ".exit" address notation, since it
3055 can be used for a variety of esoteric application-level attacks
3056 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
3058 - Reject attempts at the client side to open connections to private
3059 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3060 a randomly chosen exit node. Attempts to do so are always
3061 ill-defined, generally prevented by exit policies, and usually
3062 in error. This will also help to detect loops in transparent
3063 proxy configurations. You can disable this feature by setting
3064 "ClientRejectInternalAddresses 0" in your torrc.
3065 - Log a notice when we get a new control connection. Now it's easier
3066 for security-conscious users to recognize when a local application
3067 is knocking on their controller door. Suggested by bug 1196.
3069 o Privacy fixes (newnym):
3070 - Avoid linkability based on cached hidden service descriptors: forget
3071 all hidden service descriptors cached as a client when processing a
3072 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3073 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3074 DNS cache entries, and virtual address mappings: that's what
3075 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3076 - Don't attach new streams to old rendezvous circuits after SIGNAL
3077 NEWNYM. Previously, we would keep using an existing rendezvous
3078 circuit if it remained open (i.e. if it were kept open by a
3079 long-lived stream, or if a new stream were attached to it before
3080 Tor could notice that it was old and no longer in use). Bugfix on
3081 0.1.1.15-rc; fixes bug 3375.
3083 o Major bugfixes (relay bandwidth accounting):
3084 - Fix a bug that could break accounting on 64-bit systems with large
3085 time_t values, making them hibernate for impossibly long intervals.
3086 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3087 - Fix a bug in bandwidth accounting that could make us use twice
3088 the intended bandwidth when our interval start changes due to
3089 daylight saving time. Now we tolerate skew in stored vs computed
3090 interval starts: if the start of the period changes by no more than
3091 50% of the period's duration, we remember bytes that we transferred
3092 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3094 o Major bugfixes (bridges):
3095 - Bridges now use "reject *:*" as their default exit policy. Bugfix
3096 on 0.2.0.3-alpha. Fixes bug 1113.
3097 - If you configure your bridge with a known identity fingerprint,
3098 and the bridge authority is unreachable (as it is in at least
3099 one country now), fall back to directly requesting the descriptor
3100 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3102 - Fix a bug where bridge users who configure the non-canonical
3103 address of a bridge automatically switch to its canonical
3104 address. If a bridge listens at more than one address, it
3105 should be able to advertise those addresses independently and
3106 any non-blocked addresses should continue to work. Bugfix on Tor
3107 0.2.0.3-alpha. Fixes bug 2510.
3108 - If you configure Tor to use bridge A, and then quit and
3109 configure Tor to use bridge B instead (or if you change Tor
3110 to use bridge B via the controller), it would happily continue
3111 to use bridge A if it's still reachable. While this behavior is
3112 a feature if your goal is connectivity, in some scenarios it's a
3113 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3114 - When the controller configures a new bridge, don't wait 10 to 60
3115 seconds before trying to fetch its descriptor. Bugfix on
3116 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3118 o Major bugfixes (directory authorities):
3119 - Many relays have been falling out of the consensus lately because
3120 not enough authorities know about their descriptor for them to get
3121 a majority of votes. When we deprecated the v2 directory protocol,
3122 we got rid of the only way that v3 authorities can hear from each
3123 other about other descriptors. Now authorities examine every v3
3124 vote for new descriptors, and fetch them from that authority. Bugfix
3126 - Authorities could be tricked into giving out the Exit flag to relays
3127 that didn't allow exiting to any ports. This bug could screw
3128 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
3129 1238. Bug discovered by Martin Kowalczyk.
3130 - If all authorities restart at once right before a consensus vote,
3131 nobody will vote about "Running", and clients will get a consensus
3132 with no usable relays. Instead, authorities refuse to build a
3133 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
3135 o Major bugfixes (stream-level fairness):
3136 - When receiving a circuit-level SENDME for a blocked circuit, try
3137 to package cells fairly from all the streams that had previously
3138 been blocked on that circuit. Previously, we had started with the
3139 oldest stream, and allowed each stream to potentially exhaust
3140 the circuit's package window. This gave older streams on any
3141 given circuit priority over newer ones. Fixes bug 1937. Detected
3142 originally by Camilo Viecco. This bug was introduced before the
3143 first Tor release, in svn commit r152: it is the new winner of
3144 the longest-lived bug prize.
3145 - Fix a stream fairness bug that would cause newer streams on a given
3146 circuit to get preference when reading bytes from the origin or
3147 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3148 introduced before the first Tor release, in svn revision r152.
3149 - When the exit relay got a circuit-level sendme cell, it started
3150 reading on the exit streams, even if had 500 cells queued in the
3151 circuit queue already, so the circuit queue just grew and grew in
3152 some cases. We fix this by not re-enabling reading on receipt of a
3153 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3154 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3156 - Newly created streams were allowed to read cells onto circuits,
3157 even if the circuit's cell queue was blocked and waiting to drain.
3158 This created potential unfairness, as older streams would be
3159 blocked, but newer streams would gladly fill the queue completely.
3160 We add code to detect this situation and prevent any stream from
3161 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3164 o Major bugfixes (hidden services):
3165 - Apply circuit timeouts to opened hidden-service-related circuits
3166 based on the correct start time. Previously, we would apply the
3167 circuit build timeout based on time since the circuit's creation;
3168 it was supposed to be applied based on time since the circuit
3169 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3170 - Improve hidden service robustness: When we find that we have
3171 extended a hidden service's introduction circuit to a relay not
3172 listed as an introduction point in the HS descriptor we currently
3173 have, retry with an introduction point from the current
3174 descriptor. Previously we would just give up. Fixes bugs 1024 and
3175 1930; bugfix on 0.2.0.10-alpha.
3176 - Directory authorities now use data collected from their own
3177 uptime observations when choosing whether to assign the HSDir flag
3178 to relays, instead of trusting the uptime value the relay reports in
3179 its descriptor. This change helps prevent an attack where a small
3180 set of nodes with frequently-changing identity keys can blackhole
3181 a hidden service. (Only authorities need upgrade; others will be
3182 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3183 - Stop assigning the HSDir flag to relays that disable their
3184 DirPort (and thus will refuse to answer directory requests). This
3185 fix should dramatically improve the reachability of hidden services:
3186 hidden services and hidden service clients pick six HSDir relays
3187 to store and retrieve the hidden service descriptor, and currently
3188 about half of the HSDir relays will refuse to work. Bugfix on
3189 0.2.0.10-alpha; fixes part of bug 1693.
3191 o Major bugfixes (misc):
3192 - Clients now stop trying to use an exit node associated with a given
3193 destination by TrackHostExits if they fail to reach that exit node.
3194 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3195 - Fix a regression that caused Tor to rebind its ports if it receives
3196 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3197 - Remove an extra pair of quotation marks around the error
3198 message in control-port STATUS_GENERAL BUG events. Bugfix on
3199 0.1.2.6-alpha; fixes bug 3732.
3201 o Minor features (relays):
3202 - Ensure that no empty [dirreq-](read|write)-history lines are added
3203 to an extrainfo document. Implements ticket 2497.
3204 - When bandwidth accounting is enabled, be more generous with how
3205 much bandwidth we'll use up before entering "soft hibernation".
3206 Previously, we'd refuse new connections and circuits once we'd
3207 used up 95% of our allotment. Now, we use up 95% of our allotment,
3208 AND make sure that we have no more than 500MB (or 3 hours of
3209 expected traffic, whichever is lower) remaining before we enter
3211 - Relays now log the reason for publishing a new relay descriptor,
3212 so we have a better chance of hunting down instances of bug 1810.
3213 Resolves ticket 3252.
3214 - Log a little more clearly about the times at which we're no longer
3215 accepting new connections (e.g. due to hibernating). Resolves
3217 - When AllowSingleHopExits is set, print a warning to explain to the
3218 relay operator why most clients are avoiding her relay.
3219 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3220 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3221 clients are already deprecated because of security bugs.
3223 o Minor features (network statistics):
3224 - Directory mirrors that set "DirReqStatistics 1" write statistics
3225 about directory requests to disk every 24 hours. As compared to the
3226 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
3227 improvements: 1) stats are written to disk exactly every 24 hours;
3228 2) estimated shares of v2 and v3 requests are determined as mean
3229 values, not at the end of a measurement period; 3) unresolved
3230 requests are listed with country code '??'; 4) directories also
3231 measure download times.
3232 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
3233 number of exit streams and transferred bytes per port to disk every
3235 - Relays that set "CellStatistics 1" write statistics on how long
3236 cells spend in their circuit queues to disk every 24 hours.
3237 - Entry nodes that set "EntryStatistics 1" write statistics on the
3238 rough number and origins of connecting clients to disk every 24
3240 - Relays that write any of the above statistics to disk and set
3241 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
3242 their extra-info documents. Implements proposal 166.
3244 o Minor features (GeoIP and statistics):
3245 - Provide a log message stating which geoip file we're parsing
3246 instead of just stating that we're parsing the geoip file.
3247 Implements ticket 2432.
3248 - Make sure every relay writes a state file at least every 12 hours.
3249 Previously, a relay could go for weeks without writing its state
3250 file, and on a crash could lose its bandwidth history, capacity
3251 estimates, client country statistics, and so on. Addresses bug 3012.
3252 - Relays report the number of bytes spent on answering directory
3253 requests in extra-info descriptors similar to {read,write}-history.
3254 Implements enhancement 1790.
3255 - Report only the top 10 ports in exit-port stats in order not to
3256 exceed the maximum extra-info descriptor length of 50 KB. Implements
3258 - If writing the state file to disk fails, wait up to an hour before
3259 retrying again, rather than trying again each second. Fixes bug
3260 2346; bugfix on Tor 0.1.1.3-alpha.
3261 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3262 when we switch from being a public relay to a bridge. Otherwise
3263 there will still be clients that see the relay in their consensus,
3264 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
3266 - Update to the August 2 2011 Maxmind GeoLite Country database.
3268 o Minor features (clients):
3269 - When expiring circuits, use microsecond timers rather than
3270 one-second timers. This can avoid an unpleasant situation where a
3271 circuit is launched near the end of one second and expired right
3272 near the beginning of the next, and prevent fluctuations in circuit
3274 - If we've configured EntryNodes and our network goes away and/or all
3275 our entrynodes get marked down, optimistically retry them all when
3276 a new socks application request appears. Fixes bug 1882.
3277 - Always perform router selections using weighted relay bandwidth,
3278 even if we don't need a high capacity circuit at the time. Non-fast
3279 circuits now only differ from fast ones in that they can use relays
3280 not marked with the Fast flag. This "feature" could turn out to
3281 be a horrible bug; we should investigate more before it goes into
3283 - When we run out of directory information such that we can't build
3284 circuits, but then get enough that we can build circuits, log when
3285 we actually construct a circuit, so the user has a better chance of
3286 knowing what's going on. Fixes bug 1362.
3287 - Log SSL state transitions at debug level during handshake, and
3288 include SSL states in error messages. This may help debug future
3289 SSL handshake issues.
3291 o Minor features (directory authorities):
3292 - When a router changes IP address or port, authorities now launch
3293 a new reachability test for it. Implements ticket 1899.
3294 - Directory authorities now reject relays running any versions of
3295 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3296 known bugs that keep RELAY_EARLY cells from working on rendezvous
3297 circuits. Followup to fix for bug 2081.
3298 - Directory authorities now reject relays running any version of Tor
3299 older than 0.2.0.26-rc. That version is the earliest that fetches
3300 current directory information correctly. Fixes bug 2156.
3301 - Directory authorities now do an immediate reachability check as soon
3302 as they hear about a new relay. This change should slightly reduce
3303 the time between setting up a relay and getting listed as running
3304 in the consensus. It should also improve the time between setting
3305 up a bridge and seeing use by bridge users.
3306 - Directory authorities no longer launch a TLS connection to every
3307 relay as they startup. Now that we have 2k+ descriptors cached,
3308 the resulting network hiccup is becoming a burden. Besides,
3309 authorities already avoid voting about Running for the first half
3310 hour of their uptime.
3311 - Directory authorities now log the source of a rejected POSTed v3
3312 networkstatus vote, so we can track failures better.
3313 - Backport code from 0.2.3.x that allows directory authorities to
3314 clean their microdescriptor caches. Needed to resolve bug 2230.
3316 o Minor features (hidden services):
3317 - Use computed circuit-build timeouts to decide when to launch
3318 parallel introduction circuits for hidden services. (Previously,
3319 we would retry after 15 seconds.)
3320 - Don't allow v0 hidden service authorities to act as clients.
3321 Required by fix for bug 3000.
3322 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3323 by fix for bug 3000.
3324 - Make hidden services work better in private Tor networks by not
3325 requiring any uptime to join the hidden service descriptor
3326 DHT. Implements ticket 2088.
3327 - Log (at info level) when purging pieces of hidden-service-client
3328 state because of SIGNAL NEWNYM.
3330 o Minor features (controller interface):
3331 - New "GETINFO net/listeners/(type)" controller command to return
3332 a list of addresses and ports that are bound for listeners for a
3333 given connection type. This is useful when the user has configured
3334 "SocksPort auto" and the controller needs to know which port got
3335 chosen. Resolves another part of ticket 3076.
3336 - Have the controller interface give a more useful message than
3337 "Internal Error" in response to failed GETINFO requests.
3338 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3339 event, to give information on the current rate of circuit timeouts
3340 over our stored history.
3341 - The 'EXTENDCIRCUIT' control port command can now be used with
3342 a circ id of 0 and no path. This feature will cause Tor to build
3343 a new 'fast' general purpose circuit using its own path selection
3345 - Added a BUILDTIMEOUT_SET controller event to describe changes
3346 to the circuit build timeout.
3347 - New controller command "getinfo config-text". It returns the
3348 contents that Tor would write if you send it a SAVECONF command,
3349 so the controller can write the file to disk itself.
3351 o Minor features (controller protocol):
3352 - Add a new ControlSocketsGroupWritable configuration option: when
3353 it is turned on, ControlSockets are group-writeable by the default
3354 group of the current user. Patch by Jérémy Bobbio; implements
3356 - Tor now refuses to create a ControlSocket in a directory that is
3357 world-readable (or group-readable if ControlSocketsGroupWritable
3358 is 0). This is necessary because some operating systems do not
3359 enforce permissions on an AF_UNIX sockets. Permissions on the
3360 directory holding the socket, however, seems to work everywhere.
3361 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3362 not. This would lead to a cookie that is still not group readable.
3363 Closes bug 1843. Suggested by katmagic.
3364 - Future-proof the controller protocol a bit by ignoring keyword
3365 arguments we do not recognize.
3367 o Minor features (more useful logging):
3368 - Revise most log messages that refer to nodes by nickname to
3369 instead use the "$key=nickname at address" format. This should be
3370 more useful, especially since nicknames are less and less likely
3371 to be unique. Resolves ticket 3045.
3372 - When an HTTPS proxy reports "403 Forbidden", we now explain
3373 what it means rather than calling it an unexpected status code.
3374 Closes bug 2503. Patch from Michael Yakubovich.
3375 - Rate-limit a warning about failures to download v2 networkstatus
3376 documents. Resolves part of bug 1352.
3377 - Rate-limit the "your application is giving Tor only an IP address"
3378 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3379 - Rate-limit "Failed to hand off onionskin" warnings.
3380 - When logging a rate-limited warning, we now mention how many messages
3381 got suppressed since the last warning.
3382 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3383 2 no signature, 4 required" messages about consensus signatures
3384 easier to read, and make sure they get logged at the same severity
3385 as the messages explaining which keys are which. Fixes bug 1290.
3386 - Don't warn when we have a consensus that we can't verify because
3387 of missing certificates, unless those certificates are ones
3388 that we have been trying and failing to download. Fixes bug 1145.
3390 o Minor features (log domains):
3391 - Add documentation for configuring logging at different severities in
3392 different log domains. We've had this feature since 0.2.1.1-alpha,
3393 but for some reason it never made it into the manpage. Fixes
3395 - Make it simpler to specify "All log domains except for A and B".
3396 Previously you needed to say "[*,~A,~B]". Now you can just say
3398 - Add a "LogMessageDomains 1" option to include the domains of log
3399 messages along with the messages. Without this, there's no way
3400 to use log domains without reading the source or doing a lot
3402 - Add a new "Handshake" log domain for activities that happen
3403 during the TLS handshake.
3405 o Minor features (build process):
3406 - Make compilation with clang possible when using
3407 "--enable-gcc-warnings" by removing two warning options that clang
3408 hasn't implemented yet and by fixing a few warnings. Resolves
3410 - Detect platforms that brokenly use a signed size_t, and refuse to
3411 build there. Found and analyzed by doorss and rransom.
3412 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3414 - Add support for statically linking zlib by specifying
3415 "--enable-static-zlib", to go with our support for statically
3416 linking openssl and libevent. Resolves bug 1358.
3417 - Instead of adding the svn revision to the Tor version string, report
3418 the git commit (when we're building from a git checkout).
3419 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3421 - New --digests command-line switch to output the digests of the
3422 source files Tor was built with.
3423 - Generate our manpage and HTML documentation using Asciidoc. This
3424 change should make it easier to maintain the documentation, and
3425 produce nicer HTML. The build process fails if asciidoc cannot
3426 be found and building with asciidoc isn't disabled (via the
3427 "--disable-asciidoc" argument to ./configure. Skipping the manpage
3428 speeds up the build considerably.
3430 o Minor features (options / torrc):
3431 - Warn when the same option is provided more than once in a torrc
3432 file, on the command line, or in a single SETCONF statement, and
3433 the option is one that only accepts a single line. Closes bug 1384.
3434 - Warn when the user configures two HiddenServiceDir lines that point
3435 to the same directory. Bugfix on 0.0.6 (the version introducing
3436 HiddenServiceDir); fixes bug 3289.
3437 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3438 do individual connection-level rate limiting of clients. The torrc
3439 config options with the same names trump the consensus params, if
3440 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3441 consensus params which were broken from 0.2.2.7-alpha through
3442 0.2.2.14-alpha. Closes bug 1947.
3443 - New config option "WarnUnsafeSocks 0" disables the warning that
3444 occurs whenever Tor receives a socks handshake using a version of
3445 the socks protocol that can only provide an IP address (rather
3446 than a hostname). Setups that do DNS locally over Tor are fine,
3447 and we shouldn't spam the logs in that case.
3448 - New config option "CircuitStreamTimeout" to override our internal
3449 timeout schedule for how many seconds until we detach a stream from
3450 a circuit and try a new circuit. If your network is particularly
3451 slow, you might want to set this to a number like 60.
3452 - New options for SafeLogging to allow scrubbing only log messages
3453 generated while acting as a relay. Specify "SafeLogging relay" if
3454 you want to ensure that only messages known to originate from
3455 client use of the Tor process will be logged unsafely.
3456 - Time and memory units in the configuration file can now be set to
3457 fractional units. For example, "2.5 GB" is now a valid value for
3459 - Support line continuations in the torrc config file. If a line
3460 ends with a single backslash character, the newline is ignored, and
3461 the configuration value is treated as continuing on the next line.
3464 o Minor features (unit tests):
3465 - Revise our unit tests to use the "tinytest" framework, so we
3466 can run tests in their own processes, have smarter setup/teardown
3467 code, and so on. The unit test code has moved to its own
3468 subdirectory, and has been split into multiple modules.
3469 - Add a unit test for cross-platform directory-listing code.
3470 - Add some forgotten return value checks during unit tests. Found
3472 - Use GetTempDir to find the proper temporary directory location on
3473 Windows when generating temporary files for the unit tests. Patch
3476 o Minor features (misc):
3477 - The "torify" script now uses torsocks where available.
3478 - Make Libevent log messages get delivered to controllers later,
3479 and not from inside the Libevent log handler. This prevents unsafe
3480 reentrant Libevent calls while still letting the log messages
3482 - Certain Tor clients (such as those behind check.torproject.org) may
3483 want to fetch the consensus in an extra early manner. To enable this
3484 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
3485 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
3486 as only certain clients who must have this information sooner should
3488 - Expand homedirs passed to tor-checkkey. This should silence a
3489 coverity complaint about passing a user-supplied string into
3490 open() without checking it.
3491 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3492 used on bridges, and it makes bridge scanning somewhat easier.
3493 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3494 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3496 o Minor bugfixes (relays):
3497 - When a relay decides that its DNS is too broken for it to serve
3498 as an exit server, it advertised itself as a non-exit, but
3499 continued to act as an exit. This could create accidental
3500 partitioning opportunities for users. Instead, if a relay is
3501 going to advertise reject *:* as its exit policy, it should
3502 really act with exit policy "reject *:*". Fixes bug 2366.
3503 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3504 - Publish a router descriptor even if generating an extra-info
3505 descriptor fails. Previously we would not publish a router
3506 descriptor without an extra-info descriptor; this can cause fast
3507 exit relays collecting exit-port statistics to drop from the
3508 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3509 - When we're trying to guess whether we know our IP address as
3510 a relay, we would log various ways that we failed to guess
3511 our address, but never log that we ended up guessing it
3512 successfully. Now add a log line to help confused and anxious
3513 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3514 - For bandwidth accounting, calculate our expected bandwidth rate
3515 based on the time during which we were active and not in
3516 soft-hibernation during the last interval. Previously, we were
3517 also considering the time spent in soft-hibernation. If this
3518 was a long time, we would wind up underestimating our bandwidth
3519 by a lot, and skewing our wakeup time towards the start of the
3520 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3521 - Demote a confusing TLS warning that relay operators might get when
3522 someone tries to talk to their ORPort. It is not the operator's
3523 fault, nor can they do anything about it. Fixes bug 1364; bugfix
3525 - Change "Application request when we're believed to be offline."
3526 notice to "Application request when we haven't used client
3527 functionality lately.", to clarify that it's not an error. Bugfix
3528 on 0.0.9.3; fixes bug 1222.
3530 o Minor bugfixes (bridges):
3531 - When a client starts or stops using bridges, never use a circuit
3532 that was built before the configuration change. This behavior could
3533 put at risk a user who uses bridges to ensure that her traffic
3534 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3536 - Do not reset the bridge descriptor download status every time we
3537 re-parse our configuration or get a configuration change. Fixes
3538 bug 3019; bugfix on 0.2.0.3-alpha.
3539 - Users couldn't configure a regular relay to be their bridge. It
3540 didn't work because when Tor fetched the bridge descriptor, it found
3541 that it already had it, and didn't realize that the purpose of the
3542 descriptor had changed. Now we replace routers with a purpose other
3543 than bridge with bridge descriptors when fetching them. Bugfix on
3544 0.1.1.9-alpha. Fixes bug 1776.
3545 - In the special case where you configure a public exit relay as your
3546 bridge, Tor would be willing to use that exit relay as the last
3547 hop in your circuit as well. Now we fail that circuit instead.
3548 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3550 o Minor bugfixes (clients):
3551 - We now ask the other side of a stream (the client or the exit)
3552 for more data on that stream when the amount of queued data on
3553 that stream dips low enough. Previously, we wouldn't ask the
3554 other side for more data until either it sent us more data (which
3555 it wasn't supposed to do if it had exhausted its window!) or we
3556 had completely flushed all our queued data. This flow control fix
3557 should improve throughput. Fixes bug 2756; bugfix on the earliest
3558 released versions of Tor (svn commit r152).
3559 - When a client finds that an origin circuit has run out of 16-bit
3560 stream IDs, we now mark it as unusable for new streams. Previously,
3561 we would try to close the entire circuit. Bugfix on 0.0.6.
3562 - Make it explicit that we don't cannibalize one-hop circuits. This
3563 happens in the wild, but doesn't turn out to be a problem because
3564 we fortunately don't use those circuits. Many thanks to outofwords
3565 for the initial analysis and to swissknife who confirmed that
3566 two-hop circuits are actually created.
3567 - Resolve an edge case in path weighting that could make us misweight
3568 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
3569 - Make the DNSPort option work with libevent 2.x. Don't alter the
3570 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
3572 o Minor bugfixes (directory authorities):
3573 - Make directory authorities more accurate at recording when
3574 relays that have failed several reachability tests became
3575 unreachable, so we can provide more accuracy at assigning Stable,
3576 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3577 - Directory authorities are now more robust to hops back in time
3578 when calculating router stability. Previously, if a run of uptime
3579 or downtime appeared to be negative, the calculation could give
3580 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3582 - Directory authorities will now attempt to download consensuses
3583 if their own efforts to make a live consensus have failed. This
3584 change means authorities that restart will fetch a valid
3585 consensus, and it means authorities that didn't agree with the
3586 current consensus will still fetch and serve it if it has enough
3587 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
3588 - Never vote for a server as "Running" if we have a descriptor for
3589 it claiming to be hibernating, and that descriptor was published
3590 more recently than our last contact with the server. Bugfix on
3591 0.2.0.3-alpha; fixes bug 911.
3592 - Directory authorities no longer change their opinion of, or vote on,
3593 whether a router is Running, unless they have themselves been
3594 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
3597 o Minor bugfixes (hidden services):
3598 - Log malformed requests for rendezvous descriptors as protocol
3599 warnings, not warnings. Also, use a more informative log message
3600 in case someone sees it at log level warning without prior
3601 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
3602 - Accept hidden service descriptors if we think we might be a hidden
3603 service directory, regardless of what our consensus says. This
3604 helps robustness, since clients and hidden services can sometimes
3605 have a more up-to-date view of the network consensus than we do,
3606 and if they think that the directory authorities list us a HSDir,
3607 we might actually be one. Related to bug 2732; bugfix on
3609 - Correct the warning displayed when a rendezvous descriptor exceeds
3610 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3612 - Clients and hidden services now use HSDir-flagged relays for hidden
3613 service descriptor downloads and uploads even if the relays have no
3614 DirPort set and the client has disabled TunnelDirConns. This will
3615 eventually allow us to give the HSDir flag to relays with no
3616 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3617 - Only limit the lengths of single HS descriptors, even when multiple
3618 HS descriptors are published to an HSDir relay in a single POST
3619 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3621 o Minor bugfixes (controllers):
3622 - Allow GETINFO fingerprint to return a fingerprint even when
3623 we have not yet built a router descriptor. Fixes bug 3577;
3624 bugfix on 0.2.0.1-alpha.
3625 - Send a SUCCEEDED stream event to the controller when a reverse
3626 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3627 discovered by katmagic.
3628 - Remove a trailing asterisk from "exit-policy/default" in the
3629 output of the control port command "GETINFO info/names". Bugfix
3631 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
3632 2917. Bugfix on 0.1.1.1-alpha.
3633 - When we restart our relay, we might get a successful connection
3634 from the outside before we've started our reachability tests,
3635 triggering a warning: "ORPort found reachable, but I have no
3636 routerinfo yet. Failing to inform controller of success." This
3637 bug was harmless unless Tor is running under a controller
3638 like Vidalia, in which case the controller would never get a
3639 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3641 - When a controller changes TrackHostExits, remove mappings for
3642 hosts that should no longer have their exits tracked. Bugfix on
3644 - When a controller changes VirtualAddrNetwork, remove any mappings
3645 for hosts that were automapped to the old network. Bugfix on
3647 - When a controller changes one of the AutomapHosts* options, remove
3648 any mappings for hosts that should no longer be automapped. Bugfix
3650 - Fix an off-by-one error in calculating some controller command
3651 argument lengths. Fortunately, this mistake is harmless since
3652 the controller code does redundant NUL termination too. Found by
3653 boboper. Bugfix on 0.1.1.1-alpha.
3654 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
3655 would return "551 Internal error" rather than "552 Unrecognized key
3656 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
3657 - Don't spam the controller with events when we have no file
3658 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
3659 for log messages was already solved from bug 748.)
3660 - Emit a GUARD DROPPED controller event for a case we missed.
3661 - Ensure DNS requests launched by "RESOLVE" commands from the
3662 controller respect the __LeaveStreamsUnattached setconf options. The
3663 same goes for requests launched via DNSPort or transparent
3664 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3666 o Minor bugfixes (config options):
3667 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3668 Change the limit to 512 characters by removing base64 newlines.
3669 Fixes bug 2752. Fix by Michael Yakubovich.
3670 - Complain if PublishServerDescriptor is given multiple arguments that
3671 include 0 or 1. This configuration will be rejected in the future.
3672 Bugfix on 0.2.0.1-alpha; closes bug 1107.
3673 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
3674 Bugfix on 0.2.0.13-alpha; closes bug 928.
3676 o Minor bugfixes (log subsystem fixes):
3677 - When unable to format an address as a string, report its value
3678 as "???" rather than reusing the last formatted address. Bugfix
3680 - Be more consistent in our treatment of file system paths. "~" should
3681 get expanded to the user's home directory in the Log config option.
3682 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3683 feature for the -f and --DataDirectory options.
3685 o Minor bugfixes (memory management):
3686 - Don't stack-allocate the list of supplementary GIDs when we're
3687 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3688 could take up to 256K, which is way too much stack. Found by
3689 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3690 - Save a couple bytes in memory allocation every time we escape
3691 certain characters in a string. Patch from Florian Zumbiehl.
3693 o Minor bugfixes (protocol correctness):
3694 - When checking for 1024-bit keys, check for 1024 bits, not 128
3695 bytes. This allows Tor to correctly discard keys of length 1017
3696 through 1023. Bugfix on 0.0.9pre5.
3697 - Require that introduction point keys and onion handshake keys
3698 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3700 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3701 than waiting forever for them to finish. Fixes bug 2330; bugfix
3702 on 0.2.0.16-alpha. Found by doorss.
3703 - Never relay a cell for a circuit we have already destroyed.
3704 Between marking a circuit as closeable and finally closing it,
3705 it may have been possible for a few queued cells to get relayed,
3706 even though they would have been immediately dropped by the next
3707 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3708 - Never queue a cell for a circuit that's already been marked
3710 - Fix a spec conformance issue: the network-status-version token
3711 must be the first token in a v3 consensus or vote. Discovered by
3712 "parakeep". Bugfix on 0.2.0.3-alpha.
3713 - A networkstatus vote must contain exactly one signature. Spec
3714 conformance issue. Bugfix on 0.2.0.3-alpha.
3715 - When asked about a DNS record type we don't support via a
3716 client DNSPort, reply with NOTIMPL rather than an empty
3717 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
3718 - Make more fields in the controller protocol case-insensitive, since
3719 control-spec.txt said they were.
3721 o Minor bugfixes (log messages):
3722 - Fix a log message that said "bits" while displaying a value in
3723 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
3725 - Downgrade "no current certificates known for authority" message from
3726 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3727 - Correctly describe errors that occur when generating a TLS object.
3728 Previously we would attribute them to a failure while generating a
3729 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3731 - Fix an instance where a Tor directory mirror might accidentally
3732 log the IP address of a misbehaving Tor client. Bugfix on
3734 - Stop logging at severity 'warn' when some other Tor client tries
3735 to establish a circuit with us using weak DH keys. It's a protocol
3736 violation, but that doesn't mean ordinary users need to hear about
3737 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
3738 - If your relay can't keep up with the number of incoming create
3739 cells, it would log one warning per failure into your logs. Limit
3740 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
3742 o Minor bugfixes (build fixes):
3743 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3744 - When warning about missing zlib development packages during compile,
3745 give the correct package names. Bugfix on 0.2.0.1-alpha.
3746 - Fix warnings that newer versions of autoconf produce during
3747 ./autogen.sh. These warnings appear to be harmless in our case,
3748 but they were extremely verbose. Fixes bug 2020.
3749 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3752 o Minor bugfixes (portability):
3753 - Write several files in text mode, on OSes that distinguish text
3754 mode from binary mode (namely, Windows). These files are:
3755 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3756 that collect those statistics; 'client_keys' and 'hostname' for
3757 hidden services that use authentication; and (in the tor-gencert
3758 utility) newly generated identity and signing keys. Previously,
3759 we wouldn't specify text mode or binary mode, leading to an
3760 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3761 the DirRecordUsageByCountry option which would have triggered
3762 the assertion failure was added), although this assertion failure
3763 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3764 - Selectively disable deprecation warnings on OS X because Lion
3765 started deprecating the shipped copy of openssl. Fixes bug 3643.
3766 - Use a wide type to hold sockets when built for 64-bit Windows.
3768 - Fix an issue that prevented static linking of libevent on
3769 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
3770 where we introduced the "--with-static-libevent" configure option.
3771 - Fix a bug with our locking implementation on Windows that couldn't
3772 correctly detect when a file was already locked. Fixes bug 2504,
3773 bugfix on 0.2.1.6-alpha.
3774 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3776 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3777 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3780 o Minor bugfixes (code correctness):
3781 - Always NUL-terminate the sun_path field of a sockaddr_un before
3782 passing it to the kernel. (Not a security issue: kernels are
3783 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3784 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3785 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3786 expect it to emit a CRLF iff the format string ends with CRLF;
3787 it actually emitted a CRLF iff (a) the format string ended with
3788 CRLF or (b) the resulting string was over 1023 characters long or
3789 (c) the format string did not end with CRLF *and* the resulting
3790 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3791 fixes part of bug 3407.
3792 - Make send_control_event_impl()'s behaviour sane. Its callers
3793 expect it to always emit a CRLF at the end of the string; it
3794 might have emitted extra control characters as well. Bugfix on
3795 0.1.1.9-alpha; fixes another part of bug 3407.
3796 - Make crypto_rand_int() check the value of its input correctly.
3797 Previously, it accepted values up to UINT_MAX, but could return a
3798 negative number if given a value above INT_MAX+1. Found by George
3799 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3800 - Fix a potential null-pointer dereference while computing a
3801 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3803 - If we fail to compute the identity digest of a v3 legacy keypair,
3804 warn, and don't use a buffer-full of junk instead. Bugfix on
3805 0.2.1.1-alpha; fixes bug 3106.
3806 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3807 where if the function had ever in the future been used to check
3808 for the presence of a too-large number, it would have given an
3809 incorrect result. (Fortunately, we only used it for 16-bit
3810 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3811 - Be more careful about reporting the correct error from a failed
3812 connect() system call. Under some circumstances, it was possible to
3813 look at an incorrect value for errno when sending the end reason.
3814 Bugfix on 0.1.0.1-rc.
3815 - Correctly handle an "impossible" overflow cases in connection byte
3816 counting, where we write or read more than 4GB on an edge connection
3817 in a single second. Bugfix on 0.1.2.8-beta.
3818 - Avoid a double mark-for-free warning when failing to attach a
3819 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3821 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3822 found by "cypherpunks". This bug was introduced before the first
3823 Tor release, in svn commit r110.
3824 - Fix a bug in bandwidth history state parsing that could have been
3825 triggered if a future version of Tor ever changed the timing
3826 granularity at which bandwidth history is measured. Bugfix on
3828 - Add assertions to check for overflow in arguments to
3829 base32_encode() and base32_decode(); fix a signed-unsigned
3830 comparison there too. These bugs are not actually reachable in Tor,
3831 but it's good to prevent future errors too. Found by doorss.
3832 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
3834 - Set target port in get_interface_address6() correctly. Bugfix
3835 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3836 - Fix an impossible-to-actually-trigger buffer overflow in relay
3837 descriptor generation. Bugfix on 0.1.0.15.
3838 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
3840 o Minor bugfixes (code improvements):
3841 - After we free an internal connection structure, overwrite it
3842 with a different memory value than we use for overwriting a freed
3843 internal circuit structure. Should help with debugging. Suggested
3845 - If OpenSSL fails to make a duplicate of a private or public key, log
3846 an error message and try to exit cleanly. May help with debugging
3847 if bug 1209 ever remanifests.
3848 - Some options used different conventions for uppercasing of acronyms
3849 when comparing manpage and source. Fix those in favor of the
3850 manpage, as it makes sense to capitalize acronyms.
3851 - Take a first step towards making or.h smaller by splitting out
3852 function definitions for all source files in src/or/. Leave
3853 structures and defines in or.h for now.
3854 - Remove a few dead assignments during router parsing. Found by
3856 - Don't use 1-bit wide signed bit fields. Found by coverity.
3857 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3858 None of the cases where we did this before were wrong, but by making
3859 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3860 - The memarea code now uses a sentinel value at the end of each area
3861 to make sure nothing writes beyond the end of an area. This might
3862 help debug some conceivable causes of bug 930.
3863 - Always treat failure to allocate an RSA key as an unrecoverable
3865 - Add some more defensive programming for architectures that can't
3866 handle unaligned integer accesses. We don't know of any actual bugs
3867 right now, but that's the best time to fix them. Fixes bug 1943.
3869 o Minor bugfixes (misc):
3870 - Fix a rare bug in rend_fn unit tests: we would fail a test when
3871 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
3872 on 0.2.0.10-alpha; fixes bug 1808.
3873 - Where available, use Libevent 2.0's periodic timers so that our
3874 once-per-second cleanup code gets called even more closely to
3875 once per second than it would otherwise. Fixes bug 943.
3876 - Ignore OutboundBindAddress when connecting to localhost.
3877 Connections to localhost need to come _from_ localhost, or else
3878 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
3880 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
3882 - If any of the v3 certs we download are unparseable, we should
3883 actually notice the failure so we don't retry indefinitely. Bugfix
3884 on 0.2.0.x; reported by "rotator".
3885 - When Tor fails to parse a descriptor of any kind, dump it to disk.
3886 Might help diagnosing bug 1051.
3887 - Make our 'torify' script more portable; if we have only one of
3888 'torsocks' or 'tsocks' installed, don't complain to the user;
3889 and explain our warning about tsocks better.
3890 - Fix some urls in the exit notice file and make it XHTML1.1 strict
3891 compliant. Based on a patch from Christian Kujau.
3893 o Documentation changes:
3894 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3895 - Resolve all doxygen warnings except those for missing documentation.
3897 - Add doxygen documentation for more functions, fields, and types.
3898 - Convert the HACKING file to asciidoc, and add a few new sections
3899 to it, explaining how we use Git, how we make changelogs, and
3900 what should go in a patch.
3901 - Document the default socks host and port (127.0.0.1:9050) for
3903 - Removed some unnecessary files from the source distribution. The
3904 AUTHORS file has now been merged into the people page on the
3905 website. The roadmaps and design doc can now be found in the
3906 projects directory in svn.
3908 o Deprecated and removed features (config):
3909 - Remove the torrc.complete file. It hasn't been kept up to date
3910 and users will have better luck checking out the manpage.
3911 - Remove the HSAuthorityRecordStats option that version 0 hidden
3912 service authorities could use to track statistics of overall v0
3913 hidden service usage.
3914 - Remove the obsolete "NoPublish" option; it has been flagged
3915 as obsolete and has produced a warning since 0.1.1.18-rc.
3916 - Caches no longer download and serve v2 networkstatus documents
3917 unless FetchV2Networkstatus flag is set: these documents haven't
3918 haven't been used by clients or relays since 0.2.0.x. Resolves
3921 o Deprecated and removed features (controller):
3922 - The controller no longer accepts the old obsolete "addr-mappings/"
3923 or "unregistered-servers-" GETINFO values.
3924 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
3925 always on; using them is necessary for correct forward-compatible
3928 o Deprecated and removed features (misc):
3929 - Hidden services no longer publish version 0 descriptors, and clients
3930 do not request or use version 0 descriptors. However, the old hidden
3931 service authorities still accept and serve version 0 descriptors
3932 when contacted by older hidden services/clients.
3933 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3934 anything since 0.2.1.16-rc.
3935 - Remove everything related to building the expert bundle for OS X.
3936 It has confused many users, doesn't work right on OS X 10.6,
3937 and is hard to get rid of once installed. Resolves bug 1274.
3938 - Remove support for .noconnect style addresses. Nobody was using
3939 them, and they provided another avenue for detecting Tor users
3940 via application-level web tricks.
3941 - When we fixed bug 1038 we had to put in a restriction not to send
3942 RELAY_EARLY cells on rend circuits. This was necessary as long
3943 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3944 active. Now remove this obsolete check. Resolves bug 2081.
3945 - Remove workaround code to handle directory responses from servers
3946 that had bug 539 (they would send HTTP status 503 responses _and_
3947 send a body too). Since only server versions before
3948 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3949 keep the workaround in place.
3950 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3951 handling calculations where we have a known amount of clock skew and
3952 an allowed amount of unknown skew. But we only used it in three
3953 places, and we never adjusted the known/unknown skew values. This is
3954 still something we might want to do someday, but if we do, we'll
3955 want to do it differently.
3956 - Remove the "--enable-iphone" option to ./configure. According to
3957 reports from Marco Bonetti, Tor builds fine without any special
3958 tweaking on recent iPhone SDK versions.
3961 Changes in version 0.2.1.30 - 2011-02-23
3962 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3963 change is a slight tweak to Tor's TLS handshake that makes relays
3964 and bridges that run this new version reachable from Iran again.
3965 We don't expect this tweak will win the arms race long-term, but it
3966 buys us time until we roll out a better solution.
3969 - Stop sending a CLOCK_SKEW controller status event whenever
3970 we fetch directory information from a relay that has a wrong clock.
3971 Instead, only inform the controller when it's a trusted authority
3972 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3973 the rest of bug 1074.
3974 - Fix a bounds-checking error that could allow an attacker to
3975 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3977 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3978 Tor would ignore their RelayBandwidthBurst setting,
3979 potentially using more bandwidth than expected. Bugfix on
3980 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3981 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3982 hidserv" in her torrc. The 'hidserv' argument never controlled
3983 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3986 - Adjust our TLS Diffie-Hellman parameters to match those used by
3988 - Update to the February 1 2011 Maxmind GeoLite Country database.
3991 - Check for and reject overly long directory certificates and
3992 directory tokens before they have a chance to hit any assertions.
3993 Bugfix on 0.2.1.28. Found by "doorss".
3994 - Bring the logic that gathers routerinfos and assesses the
3995 acceptability of circuits into line. This prevents a Tor OP from
3996 getting locked in a cycle of choosing its local OR as an exit for a
3997 path (due to a .exit request) and then rejecting the circuit because
3998 its OR is not listed yet. It also prevents Tor clients from using an
3999 OR running in the same instance as an exit (due to a .exit request)
4000 if the OR does not meet the same requirements expected of an OR
4001 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4003 o Packaging changes:
4004 - Stop shipping the Tor specs files and development proposal documents
4005 in the tarball. They are now in a separate git repository at
4006 git://git.torproject.org/torspec.git
4007 - Do not include Git version tags as though they are SVN tags when
4008 generating a tarball from inside a repository that has switched
4009 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4012 Changes in version 0.2.1.29 - 2011-01-15
4013 Tor 0.2.1.29 continues our recent code security audit work. The main
4014 fix resolves a remote heap overflow vulnerability that can allow remote
4015 code execution. Other fixes address a variety of assert and crash bugs,
4016 most of which we think are hard to exploit remotely.
4018 o Major bugfixes (security):
4019 - Fix a heap overflow bug where an adversary could cause heap
4020 corruption. This bug probably allows remote code execution
4021 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4023 - Prevent a denial-of-service attack by disallowing any
4024 zlib-compressed data whose compression factor is implausibly
4025 high. Fixes part of bug 2324; reported by "doorss".
4026 - Zero out a few more keys in memory before freeing them. Fixes
4027 bug 2384 and part of bug 2385. These key instances found by
4028 "cypherpunks", based on Andrew Case's report about being able
4029 to find sensitive data in Tor's memory space if you have enough
4030 permissions. Bugfix on 0.0.2pre9.
4032 o Major bugfixes (crashes):
4033 - Prevent calls to Libevent from inside Libevent log handlers.
4034 This had potential to cause a nasty set of crashes, especially
4035 if running Libevent with debug logging enabled, and running
4036 Tor with a controller watching for low-severity log messages.
4037 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4038 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4039 underflow errors there too. Fixes the other part of bug 2324.
4040 - Fix a bug where we would assert if we ever had a
4041 cached-descriptors.new file (or another file read directly into
4042 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4043 on 0.2.1.25. Found by doorss.
4044 - Fix some potential asserts and parsing issues with grossly
4045 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4048 o Minor bugfixes (other):
4049 - Fix a bug with handling misformed replies to reverse DNS lookup
4050 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4051 bug reported by doorss.
4052 - Fix compilation on mingw when a pthreads compatibility library
4053 has been installed. (We don't want to use it, so we shouldn't
4054 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4055 - Fix a bug where we would declare that we had run out of virtual
4056 addresses when the address space was only half-exhausted. Bugfix
4058 - Correctly handle the case where AutomapHostsOnResolve is set but
4059 no virtual addresses are available. Fixes bug 2328; bugfix on
4060 0.1.2.1-alpha. Bug found by doorss.
4061 - Correctly handle wrapping around when we run out of virtual
4062 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4065 - Update to the January 1 2011 Maxmind GeoLite Country database.
4066 - Introduce output size checks on all of our decryption functions.
4069 - Tor does not build packages correctly with Automake 1.6 and earlier;
4070 added a check to Makefile.am to make sure that we're building with
4071 Automake 1.7 or later.
4072 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4073 because we built it with a too-old version of automake. Thus that
4074 release broke ./configure --enable-openbsd-malloc, which is popular
4075 among really fast exit relays on Linux.
4078 Changes in version 0.2.1.28 - 2010-12-17
4079 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4080 exploitable bugs. We also took this opportunity to change the IP address
4081 for one of our directory authorities, and to update the geoip database
4085 - Fix a remotely exploitable bug that could be used to crash instances
4086 of Tor remotely by overflowing on the heap. Remote-code execution
4087 hasn't been confirmed, but can't be ruled out. Everyone should
4088 upgrade. Bugfix on the 0.1.1 series and later.
4090 o Directory authority changes:
4091 - Change IP address and ports for gabelmoo (v3 directory authority).
4094 - Update to the December 1 2010 Maxmind GeoLite Country database.
4097 Changes in version 0.2.1.27 - 2010-11-23
4098 Yet another OpenSSL security patch broke its compatibility with Tor:
4099 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4100 also took this opportunity to fix several crash bugs, integrate a new
4101 directory authority, and update the bundled GeoIP database.
4104 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4105 No longer set the tlsext_host_name extension on server SSL objects;
4106 but continue to set it on client SSL objects. Our goal in setting
4107 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4108 bugfix on 0.2.1.1-alpha.
4109 - Do not log messages to the controller while shrinking buffer
4110 freelists. Doing so would sometimes make the controller connection
4111 try to allocate a buffer chunk, which would mess up the internals
4112 of the freelist and cause an assertion failure. Fixes bug 1125;
4113 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4114 - Learn our external IP address when we're a relay or bridge, even if
4115 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4116 where we introduced bridge relays that don't need to publish to
4117 be useful. Fixes bug 2050.
4118 - Do even more to reject (and not just ignore) annotations on
4119 router descriptors received anywhere but from the cache. Previously
4120 we would ignore such annotations at first, but cache them to disk
4121 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4122 - When you're using bridges and your network goes away and your
4123 bridges get marked as down, recover when you attempt a new socks
4124 connection (if the network is back), rather than waiting up to an
4125 hour to try fetching new descriptors for your bridges. Bugfix on
4126 0.2.0.3-alpha; fixes bug 1981.
4129 - Move to the November 2010 Maxmind GeoLite country db (rather
4130 than the June 2009 ip-to-country GeoIP db) for our statistics that
4131 count how many users relays are seeing from each country. Now we'll
4132 have more accurate data, especially for many African countries.
4134 o New directory authorities:
4135 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4139 - Fix an assertion failure that could occur in directory caches or
4140 bridge users when using a very short voting interval on a testing
4141 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4143 - Enforce multiplicity rules when parsing annotations. Bugfix on
4144 0.2.0.8-alpha. Found by piebeer.
4145 - Allow handshaking OR connections to take a full KeepalivePeriod
4146 seconds to handshake. Previously, we would close them after
4147 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4148 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4150 - When building with --enable-gcc-warnings on OpenBSD, disable
4151 warnings in system headers. This makes --enable-gcc-warnings
4152 pass on OpenBSD 4.8.
4155 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4156 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4157 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4158 Servers can start sending this code when enough clients recognize
4159 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4160 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4161 Patch from mingw-san.
4164 - Remove the old debian/ directory from the main Tor distribution.
4165 The official Tor-for-debian git repository lives at the URL
4166 https://git.torproject.org/debian/tor.git
4167 - Stop shipping the old doc/website/ directory in the tarball. We
4168 changed the website format in late 2010, and what we shipped in
4169 0.2.1.26 really wasn't that useful anyway.
4172 Changes in version 0.2.1.26 - 2010-05-02
4173 Tor 0.2.1.26 addresses the recent connection and memory overload
4174 problems we've been seeing on relays, especially relays with their
4175 DirPort open. If your relay has been crashing, or you turned it off
4176 because it used too many resources, give this release a try.
4178 This release also fixes yet another instance of broken OpenSSL libraries
4179 that was causing some relays to drop out of the consensus.
4182 - Teach relays to defend themselves from connection overload. Relays
4183 now close idle circuits early if it looks like they were intended
4184 for directory fetches. Relays are also more aggressive about closing
4185 TLS connections that have no circuits on them. Such circuits are
4186 unlikely to be re-used, and tens of thousands of them were piling
4187 up at the fast relays, causing the relays to run out of sockets
4188 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4189 their directory fetches over TLS).
4190 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4191 that claim to be earlier than 0.9.8m, but which have in reality
4192 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4193 behavior. Possible fix for some cases of bug 1346.
4194 - Directory mirrors were fetching relay descriptors only from v2
4195 directory authorities, rather than v3 authorities like they should.
4196 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4197 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4200 - Finally get rid of the deprecated and now harmful notion of "clique
4201 mode", where directory authorities maintain TLS connections to
4205 - In the util/threads test, no longer free the test_mutex before all
4206 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4207 - The master thread could starve the worker threads quite badly on
4208 certain systems, causing them to run only partially in the allowed
4209 window. This resulted in test failures. Now the master thread sleeps
4210 occasionally for a few microseconds while the two worker-threads
4211 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4214 Changes in version 0.2.1.25 - 2010-03-16
4215 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4216 prevent relays from guessing their IP address correctly. It also fixes
4217 several minor potential security bugs.
4220 - Fix a regression from our patch for bug 1244 that caused relays
4221 to guess their IP address incorrectly if they didn't set Address
4222 in their torrc and/or their address fails to resolve. Bugfix on
4223 0.2.1.23; fixes bug 1269.
4224 - When freeing a session key, zero it out completely. We only zeroed
4225 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4226 patched by ekir. Fixes bug 1254.
4229 - Fix a dereference-then-NULL-check sequence when publishing
4230 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4232 - Fix another dereference-then-NULL-check sequence. Bugfix on
4233 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4234 - Make sure we treat potentially not NUL-terminated strings correctly.
4235 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4238 Changes in version 0.2.1.24 - 2010-02-21
4239 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4243 - Work correctly out-of-the-box with even more vendor-patched versions
4244 of OpenSSL. In particular, make it so Debian and OS X don't need
4245 customized patches to run/build.
4248 Changes in version 0.2.1.23 - 2010-02-13
4249 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4250 again on the latest OS X, and updates the location of a directory
4253 o Major bugfixes (performance):
4254 - We were selecting our guards uniformly at random, and then weighting
4255 which of our guards we'd use uniformly at random. This imbalance
4256 meant that Tor clients were severely limited on throughput (and
4257 probably latency too) by the first hop in their circuit. Now we
4258 select guards weighted by currently advertised bandwidth. We also
4259 automatically discard guards picked using the old algorithm. Fixes
4260 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4263 - Make Tor work again on the latest OS X: when deciding whether to
4264 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4265 version at run-time, not compile time. We need to do this because
4266 Apple doesn't update its dev-tools headers when it updates its
4267 libraries in a security patch.
4268 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4269 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4270 a memory leak when requesting a hidden service descriptor we've
4271 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4275 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4276 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4279 - Avoid a mad rush at the beginning of each month when each client
4280 rotates half of its guards. Instead we spread the rotation out
4281 throughout the month, but we still avoid leaving a precise timestamp
4282 in the state file about when we first picked the guard. Improves
4283 over the behavior introduced in 0.1.2.17.
4286 Changes in version 0.2.1.22 - 2010-01-19
4287 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4288 authorities -- it would tell you its whole history of bridge descriptors
4289 if you make the right directory request. This stable update also
4290 rotates two of the seven v3 directory authority keys and locations.
4292 o Directory authority changes:
4293 - Rotate keys (both v3 identity and relay identity) for moria1
4297 - Stop bridge directory authorities from answering dbg-stability.txt
4298 directory queries, which would let people fetch a list of all
4299 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4302 Changes in version 0.2.1.21 - 2009-12-21
4303 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4304 library. If you use Tor on Linux / Unix and you're getting SSL
4305 renegotiation errors, upgrading should help. We also recommend an
4306 upgrade if you're an exit relay.
4309 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4310 handshake from working unless we explicitly tell OpenSSL that we
4311 are using SSL renegotiation safely. We are, of course, but OpenSSL
4312 0.9.8l won't work unless we say we are.
4313 - Avoid crashing if the client is trying to upload many bytes and the
4314 circuit gets torn down at the same time, or if the flip side
4315 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4318 - Do not refuse to learn about authority certs and v2 networkstatus
4319 documents that are older than the latest consensus. This bug might
4320 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4321 Spotted and fixed by xmux.
4322 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4323 trigger platform-specific option misparsing case found by Coverity
4325 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4326 trigger assert. Fixes bug 1173.
4329 Changes in version 0.2.1.20 - 2009-10-15
4330 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4331 services at once, prepares for more performance improvements, and
4332 fixes a bunch of smaller bugs.
4334 The Windows and OS X bundles also include a more recent Vidalia,
4335 and switch from Privoxy to Polipo.
4337 The OS X installers are now drag and drop. It's best to un-install
4338 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4339 you want to upgrade, you'll need to update the paths for Tor and Polipo
4340 in the Vidalia Settings window.
4343 - Send circuit or stream sendme cells when our window has decreased
4344 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4345 by Karsten when testing the "reduce circuit window" performance
4346 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4347 before the release of Tor 0.0.0. This is the new winner of the
4349 - Fix a remotely triggerable memory leak when a consensus document
4350 contains more than one signature from the same voter. Bugfix on
4352 - Avoid segfault in rare cases when finishing an introduction circuit
4353 as a client and finding out that we don't have an introduction key
4354 for it. Fixes bug 1073. Reported by Aaron Swartz.
4357 - Tor now reads the "circwindow" parameter out of the consensus,
4358 and uses that value for its circuit package window rather than the
4359 default of 1000 cells. Begins the implementation of proposal 168.
4361 o New directory authorities:
4362 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4364 - Move moria1 and tonga to alternate IP addresses.
4367 - Fix a signed/unsigned compile warning in 0.2.1.19.
4368 - Fix possible segmentation fault on directory authorities. Bugfix on
4370 - Fix an extremely rare infinite recursion bug that could occur if
4371 we tried to log a message after shutting down the log subsystem.
4372 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4373 - Fix an obscure bug where hidden services on 64-bit big-endian
4374 systems might mis-read the timestamp in v3 introduce cells, and
4375 refuse to connect back to the client. Discovered by "rotor".
4376 Bugfix on 0.2.1.6-alpha.
4377 - We were triggering a CLOCK_SKEW controller status event whenever
4378 we connect via the v2 connection protocol to any relay that has
4379 a wrong clock. Instead, we should only inform the controller when
4380 it's a trusted authority that claims our clock is wrong. Bugfix
4381 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4382 - We were telling the controller about CHECKING_REACHABILITY and
4383 REACHABILITY_FAILED status events whenever we launch a testing
4384 circuit or notice that one has failed. Instead, only tell the
4385 controller when we want to inform the user of overall success or
4386 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4388 - Don't warn when we're using a circuit that ends with a node
4389 excluded in ExcludeExitNodes, but the circuit is not used to access
4390 the outside world. This should help fix bug 1090. Bugfix on
4392 - Work around a small memory leak in some versions of OpenSSL that
4393 stopped the memory used by the hostname TLS extension from being
4397 - Add a "getinfo status/accepted-server-descriptor" controller
4398 command, which is the recommended way for controllers to learn
4399 whether our server descriptor has been successfully received by at
4400 least on directory authority. Un-recommend good-server-descriptor
4401 getinfo and status events until we have a better design for them.
4404 Changes in version 0.2.1.19 - 2009-07-28
4405 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4409 - Make accessing hidden services on 0.2.1.x work right again.
4410 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4411 part of patch provided by "optimist".
4414 - When a relay/bridge is writing out its identity key fingerprint to
4415 the "fingerprint" file and to its logs, write it without spaces. Now
4416 it will look like the fingerprints in our bridges documentation,
4417 and confuse fewer users.
4420 - Relays no longer publish a new server descriptor if they change
4421 their MaxAdvertisedBandwidth config option but it doesn't end up
4422 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4423 fixes bug 1026. Patch from Sebastian.
4424 - Avoid leaking memory every time we get a create cell but we have
4425 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4426 fixes bug 1034. Reported by BarkerJr.
4429 Changes in version 0.2.1.18 - 2009-07-24
4430 Tor 0.2.1.18 lays the foundations for performance improvements,
4431 adds status events to help users diagnose bootstrap problems, adds
4432 optional authentication/authorization for hidden services, fixes a
4433 variety of potential anonymity problems, and includes a huge pile of
4434 other features and bug fixes.
4436 o Major features (clients):
4437 - Start sending "bootstrap phase" status events to the controller,
4438 so it can keep the user informed of progress fetching directory
4439 information and establishing circuits. Also inform the controller
4440 if we think we're stuck at a particular bootstrap phase. Implements
4442 - Clients replace entry guards that were chosen more than a few months
4443 ago. This change should significantly improve client performance,
4444 especially once more people upgrade, since relays that have been
4445 a guard for a long time are currently overloaded.
4446 - Network status consensus documents and votes now contain bandwidth
4447 information for each relay. Clients use the bandwidth values
4448 in the consensus, rather than the bandwidth values in each
4449 relay descriptor. This approach opens the door to more accurate
4450 bandwidth estimates once the directory authorities start doing
4451 active measurements. Implements part of proposal 141.
4453 o Major features (relays):
4454 - Disable and refactor some debugging checks that forced a linear scan
4455 over the whole server-side DNS cache. These accounted for over 50%
4456 of CPU time on a relatively busy exit node's gprof profile. Also,
4457 disable some debugging checks that appeared in exit node profile
4458 data. Found by Jacob.
4459 - New DirPortFrontPage option that takes an html file and publishes
4460 it as "/" on the DirPort. Now relay operators can provide a
4461 disclaimer without needing to set up a separate webserver. There's
4462 a sample disclaimer in contrib/tor-exit-notice.html.
4464 o Major features (hidden services):
4465 - Make it possible to build hidden services that only certain clients
4466 are allowed to connect to. This is enforced at several points,
4467 so that unauthorized clients are unable to send INTRODUCE cells
4468 to the service, or even (depending on the type of authentication)
4469 to learn introduction points. This feature raises the bar for
4470 certain kinds of active attacks against hidden services. Design
4471 and code by Karsten Loesing. Implements proposal 121.
4472 - Relays now store and serve v2 hidden service descriptors by default,
4473 i.e., the new default value for HidServDirectoryV2 is 1. This is
4474 the last step in proposal 114, which aims to make hidden service
4475 lookups more reliable.
4477 o Major features (path selection):
4478 - ExitNodes and Exclude*Nodes config options now allow you to restrict
4479 by country code ("{US}") or IP address or address pattern
4480 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
4481 refinement to decide what config options should take priority if
4482 you ask to both use a particular node and exclude it.
4484 o Major features (misc):
4485 - When building a consensus, do not include routers that are down.
4486 This cuts down 30% to 40% on consensus size. Implements proposal
4488 - New TestingTorNetwork config option to allow adjustment of
4489 previously constant values that could slow bootstrapping. Implements
4490 proposal 135. Patch from Karsten.
4491 - Convert many internal address representations to optionally hold
4492 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
4493 elements. Make resolver code handle nameservers located at IPv6
4495 - More work on making our TLS handshake blend in: modify the list
4496 of ciphers advertised by OpenSSL in client mode to even more
4497 closely resemble a common web browser. We cheat a little so that
4498 we can advertise ciphers that the locally installed OpenSSL doesn't
4500 - Use the TLS1 hostname extension to more closely resemble browser
4503 o Security fixes (anonymity/entropy):
4504 - Never use a connection with a mismatched address to extend a
4505 circuit, unless that connection is canonical. A canonical
4506 connection is one whose address is authenticated by the router's
4507 identity key, either in a NETINFO cell or in a router descriptor.
4508 - Implement most of proposal 110: The first K cells to be sent
4509 along a circuit are marked as special "early" cells; only K "early"
4510 cells will be allowed. Once this code is universal, we can block
4511 certain kinds of denial-of-service attack by requiring that EXTEND
4512 commands must be sent using an "early" cell.
4513 - Resume using OpenSSL's RAND_poll() for better (and more portable)
4514 cross-platform entropy collection again. We used to use it, then
4515 stopped using it because of a bug that could crash systems that
4516 called RAND_poll when they had a lot of fds open. It looks like the
4517 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
4518 at startup, and to call RAND_poll() when we reseed later only if
4519 we have a non-buggy OpenSSL version.
4520 - When the client is choosing entry guards, now it selects at most
4521 one guard from a given relay family. Otherwise we could end up with
4522 all of our entry points into the network run by the same operator.
4523 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
4524 - Do not use or believe expired v3 authority certificates. Patch
4525 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
4526 - Drop begin cells to a hidden service if they come from the middle
4527 of a circuit. Patch from lark.
4528 - When we erroneously receive two EXTEND cells for the same circuit
4529 ID on the same connection, drop the second. Patch from lark.
4530 - Authorities now vote for the Stable flag for any router whose
4531 weighted MTBF is at least 5 days, regardless of the mean MTBF.
4532 - Clients now never report any stream end reason except 'MISC'.
4533 Implements proposal 148.
4535 o Major bugfixes (crashes):
4536 - Parse dates and IPv4 addresses in a locale- and libc-independent
4537 manner, to avoid platform-dependent behavior on malformed input.
4538 - Fix a crash that occurs on exit nodes when a nameserver request
4539 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
4540 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
4542 - Do not assume that a stack-allocated character array will be
4543 64-bit aligned on platforms that demand that uint64_t access is
4544 aligned. Possible fix for bug 604.
4545 - Resolve a very rare crash bug that could occur when the user forced
4546 a nameserver reconfiguration during the middle of a nameserver
4547 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
4548 - Avoid a "0 divided by 0" calculation when calculating router uptime
4549 at directory authorities. Bugfix on 0.2.0.8-alpha.
4550 - Fix an assertion bug in parsing policy-related options; possible fix
4552 - Rate-limit too-many-sockets messages: when they happen, they happen
4553 a lot and end up filling up the disk. Resolves bug 748.
4554 - Fix a race condition that could cause crashes or memory corruption
4555 when running as a server with a controller listening for log
4557 - Avoid crashing when we have a policy specified in a DirPolicy or
4558 SocksPolicy or ReachableAddresses option with ports set on it,
4559 and we re-load the policy. May fix bug 996.
4560 - Fix an assertion failure on 64-bit platforms when we allocated
4561 memory right up to the end of a memarea, then realigned the memory
4562 one step beyond the end. Fixes a possible cause of bug 930.
4563 - Protect the count of open sockets with a mutex, so we can't
4564 corrupt it when two threads are closing or opening sockets at once.
4565 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
4567 o Major bugfixes (clients):
4568 - Discard router descriptors as we load them if they are more than
4569 five days old. Otherwise if Tor is off for a long time and then
4570 starts with cached descriptors, it will try to use the onion keys
4571 in those obsolete descriptors when building circuits. Fixes bug 887.
4572 - When we choose to abandon a new entry guard because we think our
4573 older ones might be better, close any circuits pending on that
4574 new entry guard connection. This fix should make us recover much
4575 faster when our network is down and then comes back. Bugfix on
4576 0.1.2.8-beta; found by lodger.
4577 - When Tor clients restart after 1-5 days, they discard all their
4578 cached descriptors as too old, but they still use the cached
4579 consensus document. This approach is good for robustness, but
4580 bad for performance: since they don't know any bandwidths, they
4581 end up choosing at random rather than weighting their choice by
4582 speed. Fixed by the above feature of putting bandwidths in the
4585 o Major bugfixes (relays):
4586 - Relays were falling out of the networkstatus consensus for
4587 part of a day if they changed their local config but the
4588 authorities discarded their new descriptor as "not sufficiently
4589 different". Now directory authorities accept a descriptor as changed
4590 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
4592 - Ensure that two circuits can never exist on the same connection
4593 with the same circuit ID, even if one is marked for close. This
4594 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
4595 - Directory authorities were neglecting to mark relays down in their
4596 internal histories if the relays fall off the routerlist without
4597 ever being found unreachable. So there were relays in the histories
4598 that haven't been seen for eight months, and are listed as being
4599 up for eight months. This wreaked havoc on the "median wfu" and
4600 "median mtbf" calculations, in turn making Guard and Stable flags
4601 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
4604 o Major bugfixes (hidden services):
4605 - When establishing a hidden service, introduction points that
4606 originate from cannibalized circuits were completely ignored
4607 and not included in rendezvous service descriptors. This might
4608 have been another reason for delay in making a hidden service
4609 available. Bugfix from long ago (0.0.9.x?)
4611 o Major bugfixes (memory and resource management):
4612 - Fixed some memory leaks -- some quite frequent, some almost
4613 impossible to trigger -- based on results from Coverity.
4614 - Speed up parsing and cut down on memory fragmentation by using
4615 stack-style allocations for parsing directory objects. Previously,
4616 this accounted for over 40% of allocations from within Tor's code
4617 on a typical directory cache.
4618 - Use a Bloom filter rather than a digest-based set to track which
4619 descriptors we need to keep around when we're cleaning out old
4620 router descriptors. This speeds up the computation significantly,
4621 and may reduce fragmentation.
4623 o New/changed config options:
4624 - Now NodeFamily and MyFamily config options allow spaces in
4625 identity fingerprints, so it's easier to paste them in.
4626 Suggested by Lucky Green.
4627 - Allow ports 465 and 587 in the default exit policy again. We had
4628 rejected them in 0.1.0.15, because back in 2005 they were commonly
4629 misconfigured and ended up as spam targets. We hear they are better
4630 locked down these days.
4631 - Make TrackHostExit mappings expire a while after their last use, not
4632 after their creation. Patch from Robert Hogan.
4633 - Add an ExcludeExitNodes option so users can list a set of nodes
4634 that should be be excluded from the exit node position, but
4635 allowed elsewhere. Implements proposal 151.
4636 - New --hush command-line option similar to --quiet. While --quiet
4637 disables all logging to the console on startup, --hush limits the
4638 output to messages of warning and error severity.
4639 - New configure/torrc options (--enable-geoip-stats,
4640 DirRecordUsageByCountry) to record how many IPs we've served
4641 directory info to in each country code, how many status documents
4642 total we've sent to each country code, and what share of the total
4643 directory requests we should expect to see.
4644 - Make outbound DNS packets respect the OutboundBindAddress setting.
4645 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
4646 - Allow separate log levels to be configured for different logging
4647 domains. For example, this allows one to log all notices, warnings,
4648 or errors, plus all memory management messages of level debug or
4649 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
4650 - Update to the "June 3 2009" ip-to-country file.
4652 o Minor features (relays):
4653 - Raise the minimum rate limiting to be a relay from 20000 bytes
4654 to 20480 bytes (aka 20KB/s), to match our documentation. Also
4655 update directory authorities so they always assign the Fast flag
4656 to relays with 20KB/s of capacity. Now people running relays won't
4657 suddenly find themselves not seeing any use, if the network gets
4659 - If we're a relay and we change our IP address, be more verbose
4660 about the reason that made us change. Should help track down
4661 further bugs for relays on dynamic IP addresses.
4662 - Exit servers can now answer resolve requests for ip6.arpa addresses.
4663 - Implement most of Proposal 152: allow specialized servers to permit
4664 single-hop circuits, and clients to use those servers to build
4665 single-hop circuits when using a specialized controller. Patch
4666 from Josh Albrecht. Resolves feature request 768.
4667 - When relays do their initial bandwidth measurement, don't limit
4668 to just our entry guards for the test circuits. Otherwise we tend
4669 to have multiple test circuits going through a single entry guard,
4670 which makes our bandwidth test less accurate. Fixes part of bug 654;
4671 patch contributed by Josh Albrecht.
4673 o Minor features (directory authorities):
4674 - Try not to open more than one descriptor-downloading connection
4675 to an authority at once. This should reduce load on directory
4676 authorities. Fixes bug 366.
4677 - Add cross-certification to newly generated certificates, so that
4678 a signing key is enough information to look up a certificate. Start
4679 serving certificates by <identity digest, signing key digest>
4680 pairs. Implements proposal 157.
4681 - When a directory authority downloads a descriptor that it then
4682 immediately rejects, do not retry downloading it right away. Should
4683 save some bandwidth on authorities. Fix for bug 888. Patch by
4685 - Directory authorities now serve a /tor/dbg-stability.txt URL to
4686 help debug WFU and MTBF calculations.
4687 - In directory authorities' approved-routers files, allow
4688 fingerprints with or without space.
4690 o Minor features (directory mirrors):
4691 - When a download gets us zero good descriptors, do not notify
4692 Tor that new directory information has arrived.
4693 - Servers support a new URL scheme for consensus downloads that
4694 allows the client to specify which authorities are trusted.
4695 The server then only sends the consensus if the client will trust
4696 it. Otherwise a 404 error is sent back. Clients use this
4697 new scheme when the server supports it (meaning it's running
4698 0.2.1.1-alpha or later). Implements proposal 134.
4700 o Minor features (bridges):
4701 - If the bridge config line doesn't specify a port, assume 443.
4702 This makes bridge lines a bit smaller and easier for users to
4704 - If we're using bridges and our network goes away, be more willing
4705 to forgive our bridges and try again when we get an application
4708 o Minor features (hidden services):
4709 - When the client launches an introduction circuit, retry with a
4710 new circuit after 30 seconds rather than 60 seconds.
4711 - Launch a second client-side introduction circuit in parallel
4712 after a delay of 15 seconds (based on work by Christian Wilms).
4713 - Hidden services start out building five intro circuits rather
4714 than three, and when the first three finish they publish a service
4715 descriptor using those. Now we publish our service descriptor much
4716 faster after restart.
4717 - Drop the requirement to have an open dir port for storing and
4718 serving v2 hidden service descriptors.
4720 o Minor features (build and packaging):
4721 - On Linux, use the prctl call to re-enable core dumps when the User
4723 - Try to make sure that the version of Libevent we're running with
4724 is binary-compatible with the one we built with. May address bug
4726 - Add a new --enable-local-appdata configuration switch to change
4727 the default location of the datadir on win32 from APPDATA to
4728 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
4729 entirely. Patch from coderman.
4730 - Build correctly against versions of OpenSSL 0.9.8 or later that
4731 are built without support for deprecated functions.
4732 - On platforms with a maximum syslog string length, truncate syslog
4733 messages to that length ourselves, rather than relying on the
4734 system to do it for us.
4735 - Automatically detect MacOSX versions earlier than 10.4.0, and
4736 disable kqueue from inside Tor when running with these versions.
4737 We previously did this from the startup script, but that was no
4738 help to people who didn't use the startup script. Resolves bug 863.
4739 - Build correctly when configured to build outside the main source
4740 path. Patch from Michael Gold.
4741 - Disable GCC's strict alias optimization by default, to avoid the
4742 likelihood of its introducing subtle bugs whenever our code violates
4743 the letter of C99's alias rules.
4744 - Change the contrib/tor.logrotate script so it makes the new
4745 logs as "_tor:_tor" rather than the default, which is generally
4746 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
4747 - Change our header file guard macros to be less likely to conflict
4748 with system headers. Adam Langley noticed that we were conflicting
4749 with log.h on Android.
4750 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
4751 and stop using a warning that had become unfixably verbose under
4753 - Use a lockfile to make sure that two Tor processes are not
4754 simultaneously running with the same datadir.
4755 - Allow OpenSSL to use dynamic locks if it wants.
4756 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
4758 o Minor features (controllers):
4759 - When generating circuit events with verbose nicknames for
4760 controllers, try harder to look up nicknames for routers on a
4761 circuit. (Previously, we would look in the router descriptors we had
4762 for nicknames, but not in the consensus.) Partial fix for bug 941.
4763 - New controller event NEWCONSENSUS that lists the networkstatus
4764 lines for every recommended relay. Now controllers like Torflow
4765 can keep up-to-date on which relays they should be using.
4766 - New controller event "clients_seen" to report a geoip-based summary
4767 of which countries we've seen clients from recently. Now controllers
4768 like Vidalia can show bridge operators that they're actually making
4770 - Add a 'getinfo status/clients-seen' controller command, in case
4771 controllers want to hear clients_seen events but connect late.
4772 - New CONSENSUS_ARRIVED event to note when a new consensus has
4773 been fetched and validated.
4774 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
4775 controllers to prevent SIGHUP from reloading the configuration.
4777 - Return circuit purposes in response to GETINFO circuit-status.
4779 - Serve the latest v3 networkstatus consensus via the control
4780 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
4781 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
4782 controller can query our current bootstrap state in case it attaches
4783 partway through and wants to catch up.
4784 - Provide circuit purposes along with circuit events to the controller.
4786 o Minor features (tools):
4787 - Do not have tor-resolve automatically refuse all .onion addresses;
4788 if AutomapHostsOnResolve is set in your torrc, this will work fine.
4789 - Add a -p option to tor-resolve for specifying the SOCKS port: some
4790 people find host:port too confusing.
4791 - Print the SOCKS5 error message string as well as the error code
4792 when a tor-resolve request fails. Patch from Jacob.
4794 o Minor bugfixes (memory and resource management):
4795 - Clients no longer cache certificates for authorities they do not
4796 recognize. Bugfix on 0.2.0.9-alpha.
4797 - Do not use C's stdio library for writing to log files. This will
4798 improve logging performance by a minute amount, and will stop
4799 leaking fds when our disk is full. Fixes bug 861.
4800 - Stop erroneous use of O_APPEND in cases where we did not in fact
4801 want to re-seek to the end of a file before every last write().
4802 - Fix a small alignment and memory-wasting bug on buffer chunks.
4804 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
4805 to avoid unused RAM in buffer chunks and memory pools.
4806 - Reduce the default smartlist size from 32 to 16; it turns out that
4807 most smartlists hold around 8-12 elements tops.
4808 - Make dumpstats() log the fullness and size of openssl-internal
4810 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
4811 patch to their OpenSSL, turn it on to save memory on servers. This
4812 patch will (with any luck) get included in a mainline distribution
4814 - Fix a memory leak when v3 directory authorities load their keys
4815 and cert from disk. Bugfix on 0.2.0.1-alpha.
4816 - Stop using malloc_usable_size() to use more area than we had
4817 actually allocated: it was safe, but made valgrind really unhappy.
4818 - Make the assert_circuit_ok() function work correctly on circuits that
4819 have already been marked for close.
4820 - Fix uninitialized size field for memory area allocation: may improve
4821 memory performance during directory parsing.
4823 o Minor bugfixes (clients):
4824 - Stop reloading the router list from disk for no reason when we
4825 run out of reachable directory mirrors. Once upon a time reloading
4826 it would set the 'is_running' flag back to 1 for them. It hasn't
4827 done that for a long time.
4828 - When we had picked an exit node for a connection, but marked it as
4829 "optional", and it turned out we had no onion key for the exit,
4830 stop wanting that exit and try again. This situation may not
4831 be possible now, but will probably become feasible with proposal
4832 158. Spotted by rovv. Fixes another case of bug 752.
4833 - Fix a bug in address parsing that was preventing bridges or hidden
4834 service targets from being at IPv6 addresses.
4835 - Do not remove routers as too old if we do not have any consensus
4836 document. Bugfix on 0.2.0.7-alpha.
4837 - When an exit relay resolves a stream address to a local IP address,
4838 do not just keep retrying that same exit relay over and
4839 over. Instead, just close the stream. Addresses bug 872. Bugfix
4840 on 0.2.0.32. Patch from rovv.
4841 - Made Tor a little less aggressive about deleting expired
4842 certificates. Partial fix for bug 854.
4843 - Treat duplicate certificate fetches as failures, so that we do
4844 not try to re-fetch an expired certificate over and over and over.
4845 - Do not say we're fetching a certificate when we'll in fact skip it
4846 because of a pending download.
4847 - If we have correct permissions on $datadir, we complain to stdout
4848 and fail to start. But dangerous permissions on
4849 $datadir/cached-status/ would cause us to open a log and complain
4850 there. Now complain to stdout and fail to start in both cases. Fixes
4851 bug 820, reported by seeess.
4853 o Minor bugfixes (bridges):
4854 - When we made bridge authorities stop serving bridge descriptors over
4855 unencrypted links, we also broke DirPort reachability testing for
4856 bridges. So bridges with a non-zero DirPort were printing spurious
4857 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
4858 - Don't allow a bridge to publish its router descriptor to a
4859 non-bridge directory authority. Fixes part of bug 932.
4860 - When we change to or from being a bridge, reset our counts of
4861 client usage by country. Fixes bug 932.
4863 o Minor bugfixes (relays):
4864 - Log correct error messages for DNS-related network errors on
4866 - Actually return -1 in the error case for read_bandwidth_usage().
4867 Harmless bug, since we currently don't care about the return value
4868 anywhere. Bugfix on 0.2.0.9-alpha.
4869 - Provide a more useful log message if bug 977 (related to buffer
4870 freelists) ever reappears, and do not crash right away.
4871 - We were already rejecting relay begin cells with destination port
4872 of 0. Now also reject extend cells with destination port or address
4873 of 0. Suggested by lark.
4874 - When we can't transmit a DNS request due to a network error, retry
4875 it after a while, and eventually transmit a failing response to
4876 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
4877 - Solve a bug that kept hardware crypto acceleration from getting
4878 enabled when accounting was turned on. Fixes bug 907. Bugfix on
4880 - When a canonical connection appears later in our internal list
4881 than a noncanonical one for a given OR ID, always use the
4882 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
4884 - Avoid some nasty corner cases in the logic for marking connections
4885 as too old or obsolete or noncanonical for circuits. Partial
4887 - Fix another interesting corner-case of bug 891 spotted by rovv:
4888 Previously, if two hosts had different amounts of clock drift, and
4889 one of them created a new connection with just the wrong timing,
4890 the other might decide to deprecate the new connection erroneously.
4891 Bugfix on 0.1.1.13-alpha.
4892 - If one win32 nameserver fails to get added, continue adding the
4893 rest, and don't automatically fail.
4894 - Fix a bug where an unreachable relay would establish enough
4895 reachability testing circuits to do a bandwidth test -- if
4896 we already have a connection to the middle hop of the testing
4897 circuit, then it could establish the last hop by using the existing
4898 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
4899 circuits no longer use entry guards in 0.2.1.3-alpha.
4901 o Minor bugfixes (directory authorities):
4902 - Limit uploaded directory documents to be 16M rather than 500K.
4903 The directory authorities were refusing v3 consensus votes from
4904 other authorities, since the votes are now 504K. Fixes bug 959;
4905 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
4906 - Directory authorities should never send a 503 "busy" response to
4907 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
4909 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
4910 headers. Bugfix on 0.2.0.10-alpha.
4912 o Minor bugfixes (hidden services):
4913 - When we can't find an intro key for a v2 hidden service descriptor,
4914 fall back to the v0 hidden service descriptor and log a bug message.
4915 Workaround for bug 1024.
4916 - In very rare situations new hidden service descriptors were
4917 published earlier than 30 seconds after the last change to the
4918 service. (We currently think that a hidden service descriptor
4919 that's been stable for 30 seconds is worth publishing.)
4920 - If a hidden service sends us an END cell, do not consider
4921 retrying the connection; just close it. Patch from rovv.
4922 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
4923 service directories if they have no advertised dir port. Bugfix
4926 o Minor bugfixes (tools):
4927 - In the torify(1) manpage, mention that tsocks will leak your
4930 o Minor bugfixes (controllers):
4931 - If the controller claimed responsibility for a stream, but that
4932 stream never finished making its connection, it would live
4933 forever in circuit_wait state. Now we close it after SocksTimeout
4934 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
4935 - Make DNS resolved controller events into "CLOSED", not
4936 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
4938 - The control port would close the connection before flushing long
4939 replies, such as the network consensus, if a QUIT command was issued
4940 before the reply had completed. Now, the control port flushes all
4941 pending replies before closing the connection. Also fix a spurious
4942 warning when a QUIT command is issued after a malformed or rejected
4943 AUTHENTICATE command, but before the connection was closed. Patch
4944 by Marcus Griep. Fixes bugs 1015 and 1016.
4945 - Fix a bug that made stream bandwidth get misreported to the
4948 o Deprecated and removed features:
4949 - The old "tor --version --version" command, which would print out
4950 the subversion "Id" of most of the source files, is now removed. It
4951 turned out to be less useful than we'd expected, and harder to
4953 - RedirectExits has been removed. It was deprecated since
4955 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
4956 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
4957 - Cell pools are now always enabled; --disable-cell-pools is ignored.
4958 - Directory mirrors no longer fetch the v1 directory or
4959 running-routers files. They are obsolete, and nobody asks for them
4960 anymore. This is the first step to making v1 authorities obsolete.
4961 - Take out the TestVia config option, since it was a workaround for
4962 a bug that was fixed in Tor 0.1.1.21.
4963 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
4964 HiddenServiceExcludeNodes as obsolete: they never worked properly,
4965 and nobody seems to be using them. Fixes bug 754. Bugfix on
4966 0.1.0.1-rc. Patch from Christian Wilms.
4967 - Remove all backward-compatibility code for relays running
4968 versions of Tor so old that they no longer work at all on the
4971 o Code simplifications and refactoring:
4972 - Tool-assisted documentation cleanup. Nearly every function or
4973 static variable in Tor should have its own documentation now.
4974 - Rename the confusing or_is_obsolete field to the more appropriate
4975 is_bad_for_new_circs, and move it to or_connection_t where it
4977 - Move edge-only flags from connection_t to edge_connection_t: not
4978 only is this better coding, but on machines of plausible alignment,
4979 it should save 4-8 bytes per connection_t. "Every little bit helps."
4980 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
4981 for consistency; keep old option working for backward compatibility.
4982 - Simplify the code for finding connections to use for a circuit.
4983 - Revise the connection_new functions so that a more typesafe variant
4984 exists. This will work better with Coverity, and let us find any
4985 actual mistakes we're making here.
4986 - Refactor unit testing logic so that dmalloc can be used sensibly
4987 with unit tests to check for memory leaks.
4988 - Move all hidden-service related fields from connection and circuit
4989 structure to substructures: this way they won't eat so much memory.
4990 - Squeeze 2-5% out of client performance (according to oprofile) by
4991 improving the implementation of some policy-manipulation functions.
4992 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
4993 be more efficient. Formerly it was quadratic in the number of
4994 servers; now it should be linear. Fixes bug 509.
4995 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
4996 and n_conn_id_digest fields into a separate structure that's
4997 only needed when the circuit has not yet attached to an n_conn.
4998 - Optimize out calls to time(NULL) that occur for every IO operation,
4999 or for every cell. On systems like Windows where time() is a
5000 slow syscall, this fix will be slightly helpful.
5003 Changes in version 0.2.0.35 - 2009-06-24
5005 - Avoid crashing in the presence of certain malformed descriptors.
5006 Found by lark, and by automated fuzzing.
5007 - Fix an edge case where a malicious exit relay could convince a
5008 controller that the client's DNS question resolves to an internal IP
5009 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5012 - Finally fix the bug where dynamic-IP relays disappear when their
5013 IP address changes: directory mirrors were mistakenly telling
5014 them their old address if they asked via begin_dir, so they
5015 never got an accurate answer about their new address, so they
5016 just vanished after a day. For belt-and-suspenders, relays that
5017 don't set Address in their config now avoid using begin_dir for
5018 all direct connections. Should fix bugs 827, 883, and 900.
5019 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5020 that would occur on some exit nodes when DNS failures and timeouts
5021 occurred in certain patterns. Fix for bug 957.
5024 - When starting with a cache over a few days old, do not leak
5025 memory for the obsolete router descriptors in it. Bugfix on
5026 0.2.0.33; fixes bug 672.
5027 - Hidden service clients didn't use a cached service descriptor that
5028 was older than 15 minutes, but wouldn't fetch a new one either,
5029 because there was already one in the cache. Now, fetch a v2
5030 descriptor unless the same descriptor was added to the cache within
5031 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5034 Changes in version 0.2.0.34 - 2009-02-08
5035 Tor 0.2.0.34 features several more security-related fixes. You should
5036 upgrade, especially if you run an exit relay (remote crash) or a
5037 directory authority (remote infinite loop), or you're on an older
5038 (pre-XP) or not-recently-patched Windows (remote exploit).
5040 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5041 have many known flaws, and nobody should be using them. You should
5042 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5043 stop using those packages and upgrade anyway.
5046 - Fix an infinite-loop bug on handling corrupt votes under certain
5047 circumstances. Bugfix on 0.2.0.8-alpha.
5048 - Fix a temporary DoS vulnerability that could be performed by
5049 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5050 - Avoid a potential crash on exit nodes when processing malformed
5051 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5052 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5053 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5056 - Fix compilation on systems where time_t is a 64-bit integer.
5057 Patch from Matthias Drochner.
5058 - Don't consider expiring already-closed client connections. Fixes
5059 bug 893. Bugfix on 0.0.2pre20.
5062 Changes in version 0.2.0.33 - 2009-01-21
5063 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5064 useful to users. It also finally fixes a bug where a relay or client
5065 that's been off for many days would take a long time to bootstrap.
5067 This update also fixes an important security-related bug reported by
5068 Ilja van Sprundel. You should upgrade. (We'll send out more details
5069 about the bug once people have had some time to upgrade.)
5072 - Fix a heap-corruption bug that may be remotely triggerable on
5073 some platforms. Reported by Ilja van Sprundel.
5076 - When a stream at an exit relay is in state "resolving" or
5077 "connecting" and it receives an "end" relay cell, the exit relay
5078 would silently ignore the end cell and not close the stream. If
5079 the client never closes the circuit, then the exit relay never
5080 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5082 - When sending CREATED cells back for a given circuit, use a 64-bit
5083 connection ID to find the right connection, rather than an addr:port
5084 combination. Now that we can have multiple OR connections between
5085 the same ORs, it is no longer possible to use addr:port to uniquely
5086 identify a connection.
5087 - Bridge relays that had DirPort set to 0 would stop fetching
5088 descriptors shortly after startup, and then briefly resume
5089 after a new bandwidth test and/or after publishing a new bridge
5090 descriptor. Bridge users that try to bootstrap from them would
5091 get a recent networkstatus but would get descriptors from up to
5092 18 hours earlier, meaning most of the descriptors were obsolete
5093 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5094 - Prevent bridge relays from serving their 'extrainfo' document
5095 to anybody who asks, now that extrainfo docs include potentially
5096 sensitive aggregated client geoip summaries. Bugfix on
5098 - If the cached networkstatus consensus is more than five days old,
5099 discard it rather than trying to use it. In theory it could be
5100 useful because it lists alternate directory mirrors, but in practice
5101 it just means we spend many minutes trying directory mirrors that
5102 are long gone from the network. Also discard router descriptors as
5103 we load them if they are more than five days old, since the onion
5104 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5107 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5108 could make gcc generate non-functional binary search code. Bugfix
5110 - Build correctly on platforms without socklen_t.
5111 - Compile without warnings on solaris.
5112 - Avoid potential crash on internal error during signature collection.
5113 Fixes bug 864. Patch from rovv.
5114 - Correct handling of possible malformed authority signing key
5115 certificates with internal signature types. Fixes bug 880.
5116 Bugfix on 0.2.0.3-alpha.
5117 - Fix a hard-to-trigger resource leak when logging credential status.
5119 - When we can't initialize DNS because the network is down, do not
5120 automatically stop Tor from starting. Instead, we retry failed
5121 dns_init() every 10 minutes, and change the exit policy to reject
5122 *:* until one succeeds. Fixes bug 691.
5123 - Use 64 bits instead of 32 bits for connection identifiers used with
5124 the controller protocol, to greatly reduce risk of identifier reuse.
5125 - When we're choosing an exit node for a circuit, and we have
5126 no pending streams, choose a good general exit rather than one that
5127 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5128 - Fix another case of assuming, when a specific exit is requested,
5129 that we know more than the user about what hosts it allows.
5130 Fixes one case of bug 752. Patch from rovv.
5131 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5132 seconds. Warn the user if lower values are given in the
5133 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5134 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5135 user if lower values are given in the configuration. Bugfix on
5136 0.1.1.17-rc. Patch by Sebastian.
5137 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5138 the cache because we already had a v0 descriptor with the same ID.
5139 Bugfix on 0.2.0.18-alpha.
5140 - Fix a race condition when freeing keys shared between main thread
5141 and CPU workers that could result in a memory leak. Bugfix on
5142 0.1.0.1-rc. Fixes bug 889.
5143 - Send a valid END cell back when a client tries to connect to a
5144 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5145 840. Patch from rovv.
5146 - Check which hops rendezvous stream cells are associated with to
5147 prevent possible guess-the-streamid injection attacks from
5148 intermediate hops. Fixes another case of bug 446. Based on patch
5150 - If a broken client asks a non-exit router to connect somewhere,
5151 do not even do the DNS lookup before rejecting the connection.
5152 Fixes another case of bug 619. Patch from rovv.
5153 - When a relay gets a create cell it can't decrypt (e.g. because it's
5154 using the wrong onion key), we were dropping it and letting the
5155 client time out. Now actually answer with a destroy cell. Fixes
5156 bug 904. Bugfix on 0.0.2pre8.
5158 o Minor bugfixes (hidden services):
5159 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5160 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5163 - Report the case where all signatures in a detached set are rejected
5164 differently than the case where there is an error handling the
5166 - When we realize that another process has modified our cached
5167 descriptors, print out a more useful error message rather than
5168 triggering an assertion. Fixes bug 885. Patch from Karsten.
5169 - Implement the 0x20 hack to better resist DNS poisoning: set the
5170 case on outgoing DNS requests randomly, and reject responses that do
5171 not match the case correctly. This logic can be disabled with the
5172 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5173 of servers that do not reliably preserve case in replies. See
5174 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5176 - Check DNS replies for more matching fields to better resist DNS
5178 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5179 compress cells, which are basically all encrypted, compressed, or
5183 Changes in version 0.2.0.32 - 2008-11-20
5184 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5185 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5186 a smaller security flaw that might allow an attacker to access local
5187 services, further improves hidden service performance, and fixes a
5188 variety of other issues.
5191 - The "User" and "Group" config options did not clear the
5192 supplementary group entries for the Tor process. The "User" option
5193 is now more robust, and we now set the groups to the specified
5194 user's primary group. The "Group" option is now ignored. For more
5195 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5196 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5197 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5198 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5199 consistently obeyed: if an exit relay refuses a stream because its
5200 exit policy doesn't allow it, we would remember what IP address
5201 the relay said the destination address resolves to, even if it's
5202 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5205 - Fix a DOS opportunity during the voting signature collection process
5206 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5208 o Major bugfixes (hidden services):
5209 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5210 we were failing the whole hidden service request when the v0
5211 descriptor fetch fails, even if the v2 fetch is still pending and
5212 might succeed. Similarly, if the last v2 fetch fails, we were
5213 failing the whole hidden service request even if a v0 fetch is
5214 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5215 - When extending a circuit to a hidden service directory to upload a
5216 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5217 requests failed, because the router descriptor has not been
5218 downloaded yet. In these cases, do not attempt to upload the
5219 rendezvous descriptor, but wait until the router descriptor is
5220 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5221 descriptor from a hidden service directory for which the router
5222 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5226 - Fix several infrequent memory leaks spotted by Coverity.
5227 - When testing for libevent functions, set the LDFLAGS variable
5228 correctly. Found by Riastradh.
5229 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5230 bootstrapping with tunneled directory connections. Bugfix on
5231 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5232 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5233 and we know that server B rejects most-but-not all connections to
5234 port 80, we would previously reject the connection. Now, we assume
5235 the user knows what they were asking for. Fixes bug 752. Bugfix
5236 on 0.0.9rc5. Diagnosed by BarkerJr.
5237 - If we overrun our per-second write limits a little, count this as
5238 having used up our write allocation for the second, and choke
5239 outgoing directory writes. Previously, we had only counted this when
5240 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5241 Bugfix on 0.2.0.x (??).
5242 - Remove the old v2 directory authority 'lefkada' from the default
5243 list. It has been gone for many months.
5244 - Stop doing unaligned memory access that generated bus errors on
5245 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5246 - Make USR2 log-level switch take effect immediately. Bugfix on
5249 o Minor bugfixes (controller):
5250 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5251 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5254 Changes in version 0.2.0.31 - 2008-09-03
5255 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5256 a big bug we're seeing where in rare cases traffic from one Tor stream
5257 gets mixed into another stream, and fixes a variety of smaller issues.
5260 - Make sure that two circuits can never exist on the same connection
5261 with the same circuit ID, even if one is marked for close. This
5262 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5263 - Relays now reject risky extend cells: if the extend cell includes
5264 a digest of all zeroes, or asks to extend back to the relay that
5265 sent the extend cell, tear down the circuit. Ideas suggested
5267 - If not enough of our entry guards are available so we add a new
5268 one, we might use the new one even if it overlapped with the
5269 current circuit's exit relay (or its family). Anonymity bugfix
5270 pointed out by rovv.
5273 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5274 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5275 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5276 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5277 - Pick size of default geoip filename string correctly on windows.
5278 Fixes bug 806. Bugfix on 0.2.0.30.
5279 - Make the autoconf script accept the obsolete --with-ssl-dir
5280 option as an alias for the actually-working --with-openssl-dir
5281 option. Fix the help documentation to recommend --with-openssl-dir.
5282 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5283 - When using the TransPort option on OpenBSD, and using the User
5284 option to change UID and drop privileges, make sure to open
5285 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5286 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5287 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5288 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5289 on the client side when connecting to a hidden service. Bugfix
5290 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5291 - When closing an application-side connection because its circuit is
5292 getting torn down, generate the stream event correctly. Bugfix on
5293 0.1.2.x. Anonymous patch.
5296 Changes in version 0.2.0.30 - 2008-07-15
5297 This new stable release switches to a more efficient directory
5298 distribution design, adds features to make connections to the Tor
5299 network harder to block, allows Tor to act as a DNS proxy, adds separate
5300 rate limiting for relayed traffic to make it easier for clients to
5301 become relays, fixes a variety of potential anonymity problems, and
5302 includes the usual huge pile of other features and bug fixes.
5304 o New v3 directory design:
5305 - Tor now uses a new way to learn about and distribute information
5306 about the network: the directory authorities vote on a common
5307 network status document rather than each publishing their own
5308 opinion. Now clients and caches download only one networkstatus
5309 document to bootstrap, rather than downloading one for each
5310 authority. Clients only download router descriptors listed in
5311 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
5313 - Set up moria1, tor26, and dizum as v3 directory authorities
5314 in addition to being v2 authorities. Also add three new ones:
5315 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
5316 dannenberg (run by CCC).
5317 - Switch to multi-level keys for directory authorities: now their
5318 long-term identity key can be kept offline, and they periodically
5319 generate a new signing key. Clients fetch the "key certificates"
5320 to keep up to date on the right keys. Add a standalone tool
5321 "tor-gencert" to generate key certificates. Implements proposal 103.
5322 - Add a new V3AuthUseLegacyKey config option to make it easier for
5323 v3 authorities to change their identity keys if another bug like
5324 Debian's OpenSSL RNG flaw appears.
5325 - Authorities and caches fetch the v2 networkstatus documents
5326 less often, now that v3 is recommended.
5328 o Make Tor connections stand out less on the wire:
5329 - Use an improved TLS handshake designed by Steven Murdoch in proposal
5330 124, as revised in proposal 130. The new handshake is meant to
5331 be harder for censors to fingerprint, and it adds the ability
5332 to detect certain kinds of man-in-the-middle traffic analysis
5333 attacks. The new handshake format includes version negotiation for
5334 OR connections as described in proposal 105, which will allow us
5335 to improve Tor's link protocol more safely in the future.
5336 - Enable encrypted directory connections by default for non-relays,
5337 so censor tools that block Tor directory connections based on their
5338 plaintext patterns will no longer work. This means Tor works in
5339 certain censored countries by default again.
5340 - Stop including recognizeable strings in the commonname part of
5341 Tor's x509 certificates.
5343 o Implement bridge relays:
5344 - Bridge relays (or "bridges" for short) are Tor relays that aren't
5345 listed in the main Tor directory. Since there is no complete public
5346 list of them, even an ISP that is filtering connections to all the
5347 known Tor relays probably won't be able to block all the bridges.
5348 See doc/design-paper/blocking.pdf and proposal 125 for details.
5349 - New config option BridgeRelay that specifies you want to be a
5350 bridge relay rather than a normal relay. When BridgeRelay is set
5351 to 1, then a) you cache dir info even if your DirPort ins't on,
5352 and b) the default for PublishServerDescriptor is now "bridge"
5353 rather than "v2,v3".
5354 - New config option "UseBridges 1" for clients that want to use bridge
5355 relays instead of ordinary entry guards. Clients then specify
5356 bridge relays by adding "Bridge" lines to their config file. Users
5357 can learn about a bridge relay either manually through word of
5358 mouth, or by one of our rate-limited mechanisms for giving out
5359 bridge addresses without letting an attacker easily enumerate them
5360 all. See https://www.torproject.org/bridges for details.
5361 - Bridge relays behave like clients with respect to time intervals
5362 for downloading new v3 consensus documents -- otherwise they
5363 stand out. Bridge users now wait until the end of the interval,
5364 so their bridge relay will be sure to have a new consensus document.
5366 o Implement bridge directory authorities:
5367 - Bridge authorities are like normal directory authorities, except
5368 they don't serve a list of known bridges. Therefore users that know
5369 a bridge's fingerprint can fetch a relay descriptor for that bridge,
5370 including fetching updates e.g. if the bridge changes IP address,
5371 yet an attacker can't just fetch a list of all the bridges.
5372 - Set up Tonga as the default bridge directory authority.
5373 - Bridge authorities refuse to serve bridge descriptors or other
5374 bridge information over unencrypted connections (that is, when
5375 responding to direct DirPort requests rather than begin_dir cells.)
5376 - Bridge directory authorities do reachability testing on the
5377 bridges they know. They provide router status summaries to the
5378 controller via "getinfo ns/purpose/bridge", and also dump summaries
5379 to a file periodically, so we can keep internal stats about which
5380 bridges are functioning.
5381 - If bridge users set the UpdateBridgesFromAuthority config option,
5382 but the digest they ask for is a 404 on the bridge authority,
5383 they fall back to contacting the bridge directly.
5384 - Bridges always use begin_dir to publish their server descriptor to
5385 the bridge authority using an anonymous encrypted tunnel.
5386 - Early work on a "bridge community" design: if bridge authorities set
5387 the BridgePassword config option, they will serve a snapshot of
5388 known bridge routerstatuses from their DirPort to anybody who
5389 knows that password. Unset by default.
5390 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
5391 report sanitized aggregated summaries in their extra-info documents
5392 privately to the bridge authority, listing which countries are
5393 able to reach them. We hope this mechanism will let us learn when
5394 certain countries start trying to block bridges.
5395 - Bridge authorities write bridge descriptors to disk, so they can
5396 reload them after a reboot. They can also export the descriptors
5397 to other programs, so we can distribute them to blocked users via
5398 the BridgeDB interface, e.g. via https://bridges.torproject.org/
5399 and bridges@torproject.org.
5401 o Tor can be a DNS proxy:
5402 - The new client-side DNS proxy feature replaces the need for
5403 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
5404 for DNS requests on port 9999, use the Tor network to resolve them
5405 anonymously, and send the reply back like a regular DNS server.
5406 The code still only implements a subset of DNS.
5407 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5408 resolve request for hosts matching a given pattern causes Tor to
5409 generate an internal virtual address mapping for that host. This
5410 allows DNSPort to work sensibly with hidden service users. By
5411 default, .exit and .onion addresses are remapped; the list of
5412 patterns can be reconfigured with AutomapHostsSuffixes.
5413 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5414 address. Thanks to the AutomapHostsOnResolve option, this is no
5415 longer a completely silly thing to do.
5417 o Major features (relay usability):
5418 - New config options RelayBandwidthRate and RelayBandwidthBurst:
5419 a separate set of token buckets for relayed traffic. Right now
5420 relayed traffic is defined as answers to directory requests, and
5421 OR connections that don't have any local circuits on them. See
5422 proposal 111 for details.
5423 - Create listener connections before we setuid to the configured
5424 User and Group. Now non-Windows users can choose port values
5425 under 1024, start Tor as root, and have Tor bind those ports
5426 before it changes to another UID. (Windows users could already
5428 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
5429 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
5430 on "vserver" accounts. Patch from coderman.
5432 o Major features (directory authorities):
5433 - Directory authorities track weighted fractional uptime and weighted
5434 mean-time-between failures for relays. WFU is suitable for deciding
5435 whether a node is "usually up", while MTBF is suitable for deciding
5436 whether a node is "likely to stay up." We need both, because
5437 "usually up" is a good requirement for guards, while "likely to
5438 stay up" is a good requirement for long-lived connections.
5439 - Directory authorities use a new formula for selecting which relays
5440 to advertise as Guards: they must be in the top 7/8 in terms of
5441 how long we have known about them, and above the median of those
5442 nodes in terms of weighted fractional uptime.
5443 - Directory authorities use a new formula for selecting which relays
5444 to advertise as Stable: when we have 4 or more days of data, use
5445 median measured MTBF rather than median declared uptime. Implements
5447 - Directory authorities accept and serve "extra info" documents for
5448 routers. Routers now publish their bandwidth-history lines in the
5449 extra-info docs rather than the main descriptor. This step saves
5450 60% (!) on compressed router descriptor downloads. Servers upload
5451 extra-info docs to any authority that accepts them; directory
5452 authorities now allow multiple router descriptors and/or extra
5453 info documents to be uploaded in a single go. Authorities, and
5454 caches that have been configured to download extra-info documents,
5455 download them as needed. Implements proposal 104.
5456 - Authorities now list relays who have the same nickname as
5457 a different named relay, but list them with a new flag:
5458 "Unnamed". Now we can make use of relays that happen to pick the
5459 same nickname as a server that registered two years ago and then
5460 disappeared. Implements proposal 122.
5461 - Store routers in a file called cached-descriptors instead of in
5462 cached-routers. Initialize cached-descriptors from cached-routers
5463 if the old format is around. The new format allows us to store
5464 annotations along with descriptors, to record the time we received
5465 each descriptor, its source, and its purpose: currently one of
5466 general, controller, or bridge.
5468 o Major features (other):
5469 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
5470 Tor can warn and/or refuse connections to ports commonly used with
5471 vulnerable-plaintext protocols. Currently we warn on ports 23,
5472 109, 110, and 143, but we don't reject any. Based on proposal 129
5473 by Kevin Bauer and Damon McCoy.
5474 - Integrate Karsten Loesing's Google Summer of Code project to publish
5475 hidden service descriptors on a set of redundant relays that are a
5476 function of the hidden service address. Now we don't have to rely
5477 on three central hidden service authorities for publishing and
5478 fetching every hidden service descriptor. Implements proposal 114.
5479 - Allow tunnelled directory connections to ask for an encrypted
5480 "begin_dir" connection or an anonymized "uses a full Tor circuit"
5481 connection independently. Now we can make anonymized begin_dir
5482 connections for (e.g.) more secure hidden service posting and
5485 o Major bugfixes (crashes and assert failures):
5486 - Stop imposing an arbitrary maximum on the number of file descriptors
5487 used for busy servers. Bug reported by Olaf Selke; patch from
5489 - Avoid possible failures when generating a directory with routers
5490 with over-long versions strings, or too many flags set.
5491 - Fix a rare assert error when we're closing one of our threads:
5492 use a mutex to protect the list of logs, so we never write to the
5493 list as it's being freed. Fixes the very rare bug 575, which is
5494 kind of the revenge of bug 222.
5495 - Avoid segfault in the case where a badly behaved v2 versioning
5496 directory sends a signed networkstatus with missing client-versions.
5497 - When we hit an EOF on a log (probably because we're shutting down),
5498 don't try to remove the log from the list: just mark it as
5499 unusable. (Bulletproofs against bug 222.)
5501 o Major bugfixes (code security fixes):
5502 - Detect size overflow in zlib code. Reported by Justin Ferguson and
5504 - Rewrite directory tokenization code to never run off the end of
5505 a string. Fixes bug 455. Patch from croup.
5506 - Be more paranoid about overwriting sensitive memory on free(),
5507 as a defensive programming tactic to ensure forward secrecy.
5509 o Major bugfixes (anonymity fixes):
5510 - Reject requests for reverse-dns lookup of names that are in
5511 a private address space. Patch from lodger.
5512 - Never report that we've used more bandwidth than we're willing to
5513 relay: it leaks how much non-relay traffic we're using. Resolves
5515 - As a client, do not believe any server that tells us that an
5516 address maps to an internal address space.
5517 - Warn about unsafe ControlPort configurations.
5518 - Directory authorities now call routers Fast if their bandwidth is
5519 at least 100KB/s, and consider their bandwidth adequate to be a
5520 Guard if it is at least 250KB/s, no matter the medians. This fix
5521 complements proposal 107.
5522 - Directory authorities now never mark more than 2 servers per IP as
5523 Valid and Running (or 5 on addresses shared by authorities).
5524 Implements proposal 109, by Kevin Bauer and Damon McCoy.
5525 - If we're a relay, avoid picking ourselves as an introduction point,
5526 a rendezvous point, or as the final hop for internal circuits. Bug
5527 reported by taranis and lodger.
5528 - Exit relays that are used as a client can now reach themselves
5529 using the .exit notation, rather than just launching an infinite
5530 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
5531 - Fix a bug where, when we were choosing the 'end stream reason' to
5532 put in our relay end cell that we send to the exit relay, Tor
5533 clients on Windows were sometimes sending the wrong 'reason'. The
5534 anonymity problem is that exit relays may be able to guess whether
5535 the client is running Windows, thus helping partition the anonymity
5536 set. Down the road we should stop sending reasons to exit relays,
5537 or otherwise prevent future versions of this bug.
5538 - Only update guard status (usable / not usable) once we have
5539 enough directory information. This was causing us to discard all our
5540 guards on startup if we hadn't been running for a few weeks. Fixes
5542 - When our directory information has been expired for a while, stop
5543 being willing to build circuits using it. Fixes bug 401.
5545 o Major bugfixes (peace of mind for relay operators)
5546 - Non-exit relays no longer answer "resolve" relay cells, so they
5547 can't be induced to do arbitrary DNS requests. (Tor clients already
5548 avoid using non-exit relays for resolve cells, but now servers
5549 enforce this too.) Fixes bug 619. Patch from lodger.
5550 - When we setconf ClientOnly to 1, close any current OR and Dir
5551 listeners. Reported by mwenge.
5553 o Major bugfixes (other):
5554 - If we only ever used Tor for hidden service lookups or posts, we
5555 would stop building circuits and start refusing connections after
5556 24 hours, since we falsely believed that Tor was dormant. Reported
5558 - Add a new __HashedControlSessionPassword option for controllers
5559 to use for one-off session password hashes that shouldn't get
5560 saved to disk by SAVECONF --- Vidalia users were accumulating a
5561 pile of HashedControlPassword lines in their torrc files, one for
5562 each time they had restarted Tor and then clicked Save. Make Tor
5563 automatically convert "HashedControlPassword" to this new option but
5564 only when it's given on the command line. Partial fix for bug 586.
5565 - Patch from "Andrew S. Lists" to catch when we contact a directory
5566 mirror at IP address X and he says we look like we're coming from
5567 IP address X. Otherwise this would screw up our address detection.
5568 - Reject uploaded descriptors and extrainfo documents if they're
5569 huge. Otherwise we'll cache them all over the network and it'll
5570 clog everything up. Suggested by Aljosha Judmayer.
5571 - When a hidden service was trying to establish an introduction point,
5572 and Tor *did* manage to reuse one of the preemptively built
5573 circuits, it didn't correctly remember which one it used,
5574 so it asked for another one soon after, until there were no
5575 more preemptive circuits, at which point it launched one from
5576 scratch. Bugfix on 0.0.9.x.
5578 o Rate limiting and load balancing improvements:
5579 - When we add data to a write buffer in response to the data on that
5580 write buffer getting low because of a flush, do not consider the
5581 newly added data as a candidate for immediate flushing, but rather
5582 make it wait until the next round of writing. Otherwise, we flush
5583 and refill recursively, and a single greedy TLS connection can
5584 eat all of our bandwidth.
5585 - When counting the number of bytes written on a TLS connection,
5586 look at the BIO actually used for writing to the network, not
5587 at the BIO used (sometimes) to buffer data for the network.
5588 Looking at different BIOs could result in write counts on the
5589 order of ULONG_MAX. Fixes bug 614.
5590 - If we change our MaxAdvertisedBandwidth and then reload torrc,
5591 Tor won't realize it should publish a new relay descriptor. Fixes
5592 bug 688, reported by mfr.
5593 - Avoid using too little bandwidth when our clock skips a few seconds.
5594 - Choose which bridge to use proportional to its advertised bandwidth,
5595 rather than uniformly at random. This should speed up Tor for
5596 bridge users. Also do this for people who set StrictEntryNodes.
5598 o Bootstrapping faster and building circuits more intelligently:
5599 - Fix bug 660 that was preventing us from knowing that we should
5600 preemptively build circuits to handle expected directory requests.
5601 - When we're checking if we have enough dir info for each relay
5602 to begin establishing circuits, make sure that we actually have
5603 the descriptor listed in the consensus, not just any descriptor.
5604 - Correctly notify one-hop connections when a circuit build has
5605 failed. Possible fix for bug 669. Found by lodger.
5606 - Clients now hold circuitless TLS connections open for 1.5 times
5607 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
5608 rebuild a new circuit over them within that timeframe. Previously,
5609 they held them open only for KeepalivePeriod (5 minutes).
5611 o Performance improvements (memory):
5612 - Add OpenBSD malloc code from "phk" as an optional malloc
5613 replacement on Linux: some glibc libraries do very poorly with
5614 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
5615 ./configure to get the replacement malloc code.
5616 - Switch our old ring buffer implementation for one more like that
5617 used by free Unix kernels. The wasted space in a buffer with 1mb
5618 of data will now be more like 8k than 1mb. The new implementation
5619 also avoids realloc();realloc(); patterns that can contribute to
5620 memory fragmentation.
5621 - Change the way that Tor buffers data that it is waiting to write.
5622 Instead of queueing data cells in an enormous ring buffer for each
5623 client->OR or OR->OR connection, we now queue cells on a separate
5624 queue for each circuit. This lets us use less slack memory, and
5625 will eventually let us be smarter about prioritizing different kinds
5627 - Reference-count and share copies of address policy entries; only 5%
5628 of them were actually distinct.
5629 - Tune parameters for cell pool allocation to minimize amount of
5631 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
5632 for every single inactive connection_t. Free items from the
5633 4k/16k-buffer free lists when they haven't been used for a while.
5634 - Make memory debugging information describe more about history
5635 of cell allocation, so we can help reduce our memory use.
5636 - Be even more aggressive about releasing RAM from small
5637 empty buffers. Thanks to our free-list code, this shouldn't be too
5638 performance-intensive.
5639 - Log malloc statistics from mallinfo() on platforms where it exists.
5640 - Use memory pools to allocate cells with better speed and memory
5641 efficiency, especially on platforms where malloc() is inefficient.
5642 - Add a --with-tcmalloc option to the configure script to link
5643 against tcmalloc (if present). Does not yet search for non-system
5646 o Performance improvements (socket management):
5647 - Count the number of open sockets separately from the number of
5648 active connection_t objects. This will let us avoid underusing
5649 our allocated connection limit.
5650 - We no longer use socket pairs to link an edge connection to an
5651 anonymous directory connection or a DirPort test connection.
5652 Instead, we track the link internally and transfer the data
5653 in-process. This saves two sockets per "linked" connection (at the
5654 client and at the server), and avoids the nasty Windows socketpair()
5656 - We were leaking a file descriptor if Tor started with a zero-length
5657 cached-descriptors file. Patch by "freddy77".
5659 o Performance improvements (CPU use):
5660 - Never walk through the list of logs if we know that no log target
5661 is interested in a given message.
5662 - Call routerlist_remove_old_routers() much less often. This should
5663 speed startup, especially on directory caches.
5664 - Base64 decoding was actually showing up on our profile when parsing
5665 the initial descriptor file; switch to an in-process all-at-once
5666 implementation that's about 3.5x times faster than calling out to
5668 - Use a slightly simpler string hashing algorithm (copying Python's
5669 instead of Java's) and optimize our digest hashing algorithm to take
5670 advantage of 64-bit platforms and to remove some possibly-costly
5672 - When implementing AES counter mode, update only the portions of the
5673 counter buffer that need to change, and don't keep separate
5674 network-order and host-order counters on big-endian hosts (where
5676 - Add an in-place version of aes_crypt() so that we can avoid doing a
5677 needless memcpy() call on each cell payload.
5678 - Use Critical Sections rather than Mutexes for synchronizing threads
5679 on win32; Mutexes are heavier-weight, and designed for synchronizing
5682 o Performance improvements (bandwidth use):
5683 - Don't try to launch new descriptor downloads quite so often when we
5684 already have enough directory information to build circuits.
5685 - Version 1 directories are no longer generated in full. Instead,
5686 authorities generate and serve "stub" v1 directories that list
5687 no servers. This will stop Tor versions 0.1.0.x and earlier from
5688 working, but (for security reasons) nobody should be running those
5690 - Avoid going directly to the directory authorities even if you're a
5691 relay, if you haven't found yourself reachable yet or if you've
5692 decided not to advertise your dirport yet. Addresses bug 556.
5693 - If we've gone 12 hours since our last bandwidth check, and we
5694 estimate we have less than 50KB bandwidth capacity but we could
5695 handle more, do another bandwidth test.
5696 - Support "If-Modified-Since" when answering HTTP requests for
5697 directories, running-routers documents, and v2 and v3 networkstatus
5698 documents. (There's no need to support it for router descriptors,
5699 since those are downloaded by descriptor digest.)
5700 - Stop fetching directory info so aggressively if your DirPort is
5701 on but your ORPort is off; stop fetching v2 dir info entirely.
5702 You can override these choices with the new FetchDirInfoEarly
5705 o Changed config option behavior (features):
5706 - Configuration files now accept C-style strings as values. This
5707 helps encode characters not allowed in the current configuration
5708 file format, such as newline or #. Addresses bug 557.
5709 - Add hidden services and DNSPorts to the list of things that make
5710 Tor accept that it has running ports. Change starting Tor with no
5711 ports from a fatal error to a warning; we might change it back if
5712 this turns out to confuse anybody. Fixes bug 579.
5713 - Make PublishServerDescriptor default to 1, so the default doesn't
5714 have to change as we invent new directory protocol versions.
5715 - Allow people to say PreferTunnelledDirConns rather than
5716 PreferTunneledDirConns, for those alternate-spellers out there.
5717 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
5718 accommodate the growing number of servers that use the default
5719 and are reaching it.
5720 - Make it possible to enable HashedControlPassword and
5721 CookieAuthentication at the same time.
5722 - When a TrackHostExits-chosen exit fails too many times in a row,
5723 stop using it. Fixes bug 437.
5725 o Changed config option behavior (bugfixes):
5726 - Do not read the configuration file when we've only been told to
5727 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
5728 based on patch from Sebastian Hahn.
5729 - Actually validate the options passed to AuthDirReject,
5730 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
5731 - Make "ClientOnly 1" config option disable directory ports too.
5732 - Don't stop fetching descriptors when FetchUselessDescriptors is
5733 set, even if we stop asking for circuits. Bug reported by tup
5735 - Servers used to decline to publish their DirPort if their
5736 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
5737 they look only at BandwidthRate and RelayBandwidthRate.
5738 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
5739 minus 1 byte: the actual maximum declared bandwidth.
5740 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
5741 - Make the NodeFamilies config option work. (Reported by
5742 lodger -- it has never actually worked, even though we added it
5744 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
5745 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
5747 o New config options:
5748 - New configuration options AuthDirMaxServersPerAddr and
5749 AuthDirMaxServersperAuthAddr to override default maximum number
5750 of servers allowed on a single IP address. This is important for
5751 running a test network on a single host.
5752 - Three new config options (AlternateDirAuthority,
5753 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
5754 user selectively replace the default directory authorities by type,
5755 rather than the all-or-nothing replacement that DirServer offers.
5756 - New config options AuthDirBadDir and AuthDirListBadDirs for
5757 authorities to mark certain relays as "bad directories" in the
5758 networkstatus documents. Also supports the "!baddir" directive in
5759 the approved-routers file.
5760 - New config option V2AuthoritativeDirectory that all v2 directory
5761 authorities must set. This lets v3 authorities choose not to serve
5762 v2 directory information.
5764 o Minor features (other):
5765 - When we're not serving v2 directory information, there is no reason
5766 to actually keep any around. Remove the obsolete files and directory
5767 on startup if they are very old and we aren't going to serve them.
5768 - When we negotiate a v2 link-layer connection (not yet implemented),
5769 accept RELAY_EARLY cells and turn them into RELAY cells if we've
5770 negotiated a v1 connection for their next step. Initial steps for
5772 - When we have no consensus, check FallbackNetworkstatusFile (defaults
5773 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
5774 we can start out knowing some directory caches. We don't ship with
5775 a fallback consensus by default though, because it was making
5776 bootstrapping take too long while we tried many down relays.
5777 - Authorities send back an X-Descriptor-Not-New header in response to
5778 an accepted-but-discarded descriptor upload. Partially implements
5780 - If we find a cached-routers file that's been sitting around for more
5781 than 28 days unmodified, then most likely it's a leftover from
5782 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
5784 - When we (as a cache) download a descriptor because it was listed
5785 in a consensus, remember when the consensus was supposed to expire,
5786 and don't expire the descriptor until then.
5787 - Optionally (if built with -DEXPORTMALLINFO) export the output
5788 of mallinfo via http, as tor/mallinfo.txt. Only accessible
5790 - Tag every guard node in our state file with the version that
5791 we believe added it, or with our own version if we add it. This way,
5792 if a user temporarily runs an old version of Tor and then switches
5793 back to a new one, she doesn't automatically lose her guards.
5794 - When somebody requests a list of statuses or servers, and we have
5795 none of those, return a 404 rather than an empty 200.
5796 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
5798 - Add an HSAuthorityRecordStats option that hidden service authorities
5799 can use to track statistics of overall hidden service usage without
5800 logging information that would be as useful to an attacker.
5801 - Allow multiple HiddenServicePort directives with the same virtual
5802 port; when they occur, the user is sent round-robin to one
5803 of the target ports chosen at random. Partially fixes bug 393 by
5804 adding limited ad-hoc round-robining.
5805 - Revamp file-writing logic so we don't need to have the entire
5806 contents of a file in memory at once before we write to disk. Tor,
5809 o Minor bugfixes (other):
5810 - Alter the code that tries to recover from unhandled write
5811 errors, to not try to flush onto a socket that's given us
5813 - Directory mirrors no longer include a guess at the client's IP
5814 address if the connection appears to be coming from the same /24
5815 network; it was producing too many wrong guesses.
5816 - If we're trying to flush the last bytes on a connection (for
5817 example, when answering a directory request), reset the
5818 time-to-give-up timeout every time we manage to write something
5820 - Reject router descriptors with out-of-range bandwidthcapacity or
5821 bandwidthburst values.
5822 - If we can't expand our list of entry guards (e.g. because we're
5823 using bridges or we have StrictEntryNodes set), don't mark relays
5824 down when they fail a directory request. Otherwise we're too quick
5825 to mark all our entry points down.
5826 - Authorities no longer send back "400 you're unreachable please fix
5827 it" errors to Tor servers that aren't online all the time. We're
5828 supposed to tolerate these servers now.
5829 - Let directory authorities startup even when they can't generate
5830 a descriptor immediately, e.g. because they don't know their
5832 - Correctly enforce that elements of directory objects do not appear
5833 more often than they are allowed to appear.
5834 - Stop allowing hibernating servers to be "stable" or "fast".
5835 - On Windows, we were preventing other processes from reading
5836 cached-routers while Tor was running. (Reported by janbar)
5837 - Check return values from pthread_mutex functions.
5838 - When opening /dev/null in finish_daemonize(), do not pass the
5839 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
5840 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
5842 o Controller features:
5843 - The GETCONF command now escapes and quotes configuration values
5844 that don't otherwise fit into the torrc file.
5845 - The SETCONF command now handles quoted values correctly.
5846 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
5847 ask about source, timestamp of arrival, purpose, etc. We need
5848 something like this to help Vidalia not do GeoIP lookups on bridge
5850 - Allow multiple HashedControlPassword config lines, to support
5851 multiple controller passwords.
5852 - Accept LF instead of CRLF on controller, since some software has a
5853 hard time generating real Internet newlines.
5854 - Add GETINFO values for the server status events
5855 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
5857 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
5858 GETINFO for Torstat to use until it can switch to using extrainfos.
5859 - New config option CookieAuthFile to choose a new location for the
5860 cookie authentication file, and config option
5861 CookieAuthFileGroupReadable to make it group-readable.
5862 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
5863 match requests to applications. Patch from Robert Hogan.
5864 - Add a RESOLVE command to launch hostname lookups. Original patch
5866 - Add GETINFO status/enough-dir-info to let controllers tell whether
5867 Tor has downloaded sufficient directory information. Patch from Tup.
5868 - You can now use the ControlSocket option to tell Tor to listen for
5869 controller connections on Unix domain sockets on systems that
5870 support them. Patch from Peter Palfrader.
5871 - New "GETINFO address-mappings/*" command to get address mappings
5872 with expiry information. "addr-mappings/*" is now deprecated.
5874 - Add a new config option __DisablePredictedCircuits designed for
5875 use by the controller, when we don't want Tor to build any circuits
5877 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
5878 so we can exit from the middle of the circuit.
5879 - Implement "getinfo status/circuit-established".
5880 - Implement "getinfo status/version/..." so a controller can tell
5881 whether the current version is recommended, and whether any versions
5882 are good, and how many authorities agree. Patch from "shibz".
5883 - Controllers should now specify cache=no or cache=yes when using
5884 the +POSTDESCRIPTOR command.
5885 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
5886 Robert Hogan. Fixes the first part of bug 681.
5887 - When reporting clock skew, and we know that the clock is _at least
5888 as skewed_ as some value, but we don't know the actual value,
5889 report the value as a "minimum skew."
5891 o Controller bugfixes:
5892 - Generate "STATUS_SERVER" events rather than misspelled
5893 "STATUS_SEVER" events. Caught by mwenge.
5894 - Reject controller commands over 1MB in length, so rogue
5895 processes can't run us out of memory.
5896 - Change the behavior of "getinfo status/good-server-descriptor"
5897 so it doesn't return failure when any authority disappears.
5898 - Send NAMESERVER_STATUS messages for a single failed nameserver
5900 - When the DANGEROUS_VERSION controller status event told us we're
5901 running an obsolete version, it used the string "OLD" to describe
5902 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
5903 "OBSOLETE" in both cases.
5904 - Respond to INT and TERM SIGNAL commands before we execute the
5905 signal, in case the signal shuts us down. We had a patch in
5906 0.1.2.1-alpha that tried to do this by queueing the response on
5907 the connection's buffer before shutting down, but that really
5908 isn't the same thing at all. Bug located by Matt Edman.
5909 - Provide DNS expiry times in GMT, not in local time. For backward
5910 compatibility, ADDRMAP events only provide GMT expiry in an extended
5911 field. "GETINFO address-mappings" always does the right thing.
5912 - Use CRLF line endings properly in NS events.
5913 - Make 'getinfo fingerprint' return a 551 error if we're not a
5914 server, so we match what the control spec claims we do. Reported
5916 - Fix a typo in an error message when extendcircuit fails that
5917 caused us to not follow the \r\n-based delimiter protocol. Reported
5919 - When tunneling an encrypted directory connection, and its first
5920 circuit fails, do not leave it unattached and ask the controller
5921 to deal. Fixes the second part of bug 681.
5922 - Treat some 403 responses from directory servers as INFO rather than
5923 WARN-severity events.
5925 o Portability / building / compiling:
5926 - When building with --enable-gcc-warnings, check for whether Apple's
5927 warning "-Wshorten-64-to-32" is available.
5928 - Support compilation to target iPhone; patch from cjacker huang.
5929 To build for iPhone, pass the --enable-iphone option to configure.
5930 - Port Tor to build and run correctly on Windows CE systems, using
5931 the wcecompat library. Contributed by Valerio Lupi.
5932 - Detect non-ASCII platforms (if any still exist) and refuse to
5933 build there: some of our code assumes that 'A' is 65 and so on.
5934 - Clear up some MIPSPro compiler warnings.
5935 - Make autoconf search for libevent, openssl, and zlib consistently.
5936 - Update deprecated macros in configure.in.
5937 - When warning about missing headers, tell the user to let us
5938 know if the compile succeeds anyway, so we can downgrade the
5940 - Include the current subversion revision as part of the version
5941 string: either fetch it directly if we're in an SVN checkout, do
5942 some magic to guess it if we're in an SVK checkout, or use
5943 the last-detected version if we're building from a .tar.gz.
5944 Use this version consistently in log messages.
5945 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
5946 - Read resolv.conf files correctly on platforms where read() returns
5947 partial results on small file reads.
5948 - Build without verbose warnings even on gcc 4.2 and 4.3.
5949 - On Windows, correctly detect errors when listing the contents of
5950 a directory. Fix from lodger.
5951 - Run 'make test' as part of 'make dist', so we stop releasing so
5952 many development snapshots that fail their unit tests.
5953 - Add support to detect Libevent versions in the 1.4.x series
5955 - Add command-line arguments to unit-test executable so that we can
5956 invoke any chosen test from the command line rather than having
5957 to run the whole test suite at once; and so that we can turn on
5958 logging for the unit tests.
5959 - Do not automatically run configure from autogen.sh. This
5960 non-standard behavior tended to annoy people who have built other
5962 - Fix a macro/CPP interaction that was confusing some compilers:
5963 some GCCs don't like #if/#endif pairs inside macro arguments.
5965 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
5966 Fixes bug 704; fix from Steven Murdoch.
5967 - Correctly detect transparent proxy support on Linux hosts that
5968 require in.h to be included before netfilter_ipv4.h. Patch
5971 o Logging improvements:
5972 - When we haven't had any application requests lately, don't bother
5973 logging that we have expired a bunch of descriptors.
5974 - When attempting to open a logfile fails, tell us why.
5975 - Only log guard node status when guard node status has changed.
5976 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
5977 make "INFO" 75% less verbose.
5978 - When SafeLogging is disabled, log addresses along with all TLS
5980 - Report TLS "zero return" case as a "clean close" and "IO error"
5981 as a "close". Stop calling closes "unexpected closes": existing
5982 Tors don't use SSL_close(), so having a connection close without
5983 the TLS shutdown handshake is hardly unexpected.
5984 - When we receive a consensus from the future, warn about skew.
5985 - Make "not enough dir info yet" warnings describe *why* Tor feels
5986 it doesn't have enough directory info yet.
5987 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
5988 consumers. (We already do this on HUP.)
5989 - Give more descriptive well-formedness errors for out-of-range
5990 hidden service descriptor/protocol versions.
5991 - Stop recommending that every server operator send mail to tor-ops.
5992 Resolves bug 597. Bugfix on 0.1.2.x.
5993 - Improve skew reporting: try to give the user a better log message
5994 about how skewed they are, and how much this matters.
5995 - New --quiet command-line option to suppress the default console log.
5996 Good in combination with --hash-password.
5997 - Don't complain that "your server has not managed to confirm that its
5998 ports are reachable" if we haven't been able to build any circuits
6000 - Detect the reason for failing to mmap a descriptor file we just
6001 wrote, and give a more useful log message. Fixes bug 533.
6002 - Always prepend "Bug: " to any log message about a bug.
6003 - When dumping memory usage, list bytes used in buffer memory
6005 - When running with dmalloc, dump more stats on hup and on exit.
6006 - Put a platform string (e.g. "Linux i686") in the startup log
6007 message, so when people paste just their logs, we know if it's
6008 OpenBSD or Windows or what.
6009 - When logging memory usage, break down memory used in buffers by
6011 - When we are reporting the DirServer line we just parsed, we were
6012 logging the second stanza of the key fingerprint, not the first.
6013 - Even though Windows is equally happy with / and \ as path separators,
6014 try to use \ consistently on Windows and / consistently on Unix: it
6015 makes the log messages nicer.
6016 - On OSX, stop warning the user that kqueue support in libevent is
6017 "experimental", since it seems to have worked fine for ages.
6019 o Contributed scripts and tools:
6020 - Update linux-tor-prio.sh script to allow QoS based on the uid of
6021 the Tor process. Patch from Marco Bonetti with tweaks from Mike
6023 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
6024 Unix users an easy way to script their Tor process (e.g. by
6025 adjusting bandwidth based on the time of the day).
6026 - In the exitlist script, only consider the most recently published
6027 server descriptor for each server. Also, when the user requests
6028 a list of servers that _reject_ connections to a given address,
6029 explicitly exclude the IPs that also have servers that accept
6030 connections to that address. Resolves bug 405.
6031 - Include a new contrib/tor-exit-notice.html file that exit relay
6032 operators can put on their website to help reduce abuse queries.
6034 o Newly deprecated features:
6035 - The status/version/num-versioning and status/version/num-concurring
6036 GETINFO controller options are no longer useful in the v3 directory
6037 protocol: treat them as deprecated, and warn when they're used.
6038 - The RedirectExits config option is now deprecated.
6041 - Drop the old code to choke directory connections when the
6042 corresponding OR connections got full: thanks to the cell queue
6043 feature, OR conns don't get full any more.
6044 - Remove the old "dns worker" server DNS code: it hasn't been default
6045 since 0.1.2.2-alpha, and all the servers are using the new
6047 - Remove the code to generate the oldest (v1) directory format.
6048 - Remove support for the old bw_accounting file: we've been storing
6049 bandwidth accounting information in the state file since
6050 0.1.2.5-alpha. This may result in bandwidth accounting errors
6051 if you try to upgrade from 0.1.1.x or earlier, or if you try to
6052 downgrade to 0.1.1.x or earlier.
6053 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
6054 it, it had no AES, and it hasn't seen any security patches since
6056 - Stop overloading the circuit_t.onionskin field for both "onionskin
6057 from a CREATE cell that we are waiting for a cpuworker to be
6058 assigned" and "onionskin from an EXTEND cell that we are going to
6059 send to an OR as soon as we are connected". Might help with bug 600.
6060 - Remove the tor_strpartition() function: its logic was confused,
6061 and it was only used for one thing that could be implemented far
6063 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
6064 and TorControl.py, as they use the old v0 controller protocol,
6065 and are obsoleted by TorFlow anyway.
6066 - Drop support for v1 rendezvous descriptors, since we never used
6067 them anyway, and the code has probably rotted by now. Based on
6068 patch from Karsten Loesing.
6069 - Stop allowing address masks that do not correspond to bit prefixes.
6070 We have warned about these for a really long time; now it's time
6071 to reject them. (Patch from croup.)
6072 - Remove an optimization in the AES counter-mode code that assumed
6073 that the counter never exceeded 2^68. When the counter can be set
6074 arbitrarily as an IV (as it is by Karsten's new hidden services
6075 code), this assumption no longer holds.
6076 - Disable the SETROUTERPURPOSE controller command: it is now
6080 Changes in version 0.1.2.19 - 2008-01-17
6081 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
6082 exit policy a little bit more conservative so it's safer to run an
6083 exit relay on a home system, and fixes a variety of smaller issues.
6086 - Exit policies now reject connections that are addressed to a
6087 relay's public (external) IP address too, unless
6088 ExitPolicyRejectPrivate is turned off. We do this because too
6089 many relays are running nearby to services that trust them based
6093 - When the clock jumps forward a lot, do not allow the bandwidth
6094 buckets to become negative. Fixes bug 544.
6095 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6096 on every successful resolve. Reported by Mike Perry.
6097 - Purge old entries from the "rephist" database and the hidden
6098 service descriptor database even when DirPort is zero.
6099 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6100 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6101 crashing or mis-answering these requests.
6102 - When we decide to send a 503 response to a request for servers, do
6103 not then also send the server descriptors: this defeats the whole
6104 purpose. Fixes bug 539.
6107 - Changing the ExitPolicyRejectPrivate setting should cause us to
6108 rebuild our server descriptor.
6109 - Fix handling of hex nicknames when answering controller requests for
6110 networkstatus by name, or when deciding whether to warn about
6111 unknown routers in a config option. (Patch from mwenge.)
6112 - Fix a couple of hard-to-trigger autoconf problems that could result
6113 in really weird results on platforms whose sys/types.h files define
6114 nonstandard integer types.
6115 - Don't try to create the datadir when running --verify-config or
6116 --hash-password. Resolves bug 540.
6117 - If we were having problems getting a particular descriptor from the
6118 directory caches, and then we learned about a new descriptor for
6119 that router, we weren't resetting our failure count. Reported
6121 - Although we fixed bug 539 (where servers would send HTTP status 503
6122 responses _and_ send a body too), there are still servers out there
6123 that haven't upgraded. Therefore, make clients parse such bodies
6124 when they receive them.
6125 - Run correctly on systems where rlim_t is larger than unsigned long.
6126 This includes some 64-bit systems.
6127 - Run correctly on platforms (like some versions of OS X 10.5) where
6128 the real limit for number of open files is OPEN_FILES, not rlim_max
6129 from getrlimit(RLIMIT_NOFILES).
6130 - Avoid a spurious free on base64 failure.
6131 - Avoid segfaults on certain complex invocations of
6132 router_get_by_hexdigest().
6133 - Fix rare bug on REDIRECTSTREAM control command when called with no
6134 port set: it could erroneously report an error when none had
6138 Changes in version 0.1.2.18 - 2007-10-28
6139 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
6140 hidden service introduction that were causing huge delays, and a big
6141 bug that was causing some servers to disappear from the network status
6142 lists for a few hours each day.
6144 o Major bugfixes (crashes):
6145 - If a connection is shut down abruptly because of something that
6146 happened inside connection_flushed_some(), do not call
6147 connection_finished_flushing(). Should fix bug 451:
6148 "connection_stop_writing: Assertion conn->write_event failed"
6149 Bugfix on 0.1.2.7-alpha.
6150 - Fix possible segfaults in functions called from
6151 rend_process_relay_cell().
6153 o Major bugfixes (hidden services):
6154 - Hidden services were choosing introduction points uniquely by
6155 hexdigest, but when constructing the hidden service descriptor
6156 they merely wrote the (potentially ambiguous) nickname.
6157 - Clients now use the v2 intro format for hidden service
6158 connections: they specify their chosen rendezvous point by identity
6159 digest rather than by (potentially ambiguous) nickname. These
6160 changes could speed up hidden service connections dramatically.
6162 o Major bugfixes (other):
6163 - Stop publishing a new server descriptor just because we get a
6164 HUP signal. This led (in a roundabout way) to some servers getting
6165 dropped from the networkstatus lists for a few hours each day.
6166 - When looking for a circuit to cannibalize, consider family as well
6167 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6168 circuit cannibalization).
6169 - When a router wasn't listed in a new networkstatus, we were leaving
6170 the flags for that router alone -- meaning it remained Named,
6171 Running, etc -- even though absence from the networkstatus means
6172 that it shouldn't be considered to exist at all anymore. Now we
6173 clear all the flags for routers that fall out of the networkstatus
6174 consensus. Fixes bug 529.
6177 - Don't try to access (or alter) the state file when running
6178 --list-fingerprint or --verify-config or --hash-password. Resolves
6180 - When generating information telling us how to extend to a given
6181 router, do not try to include the nickname if it is
6182 absent. Resolves bug 467.
6183 - Fix a user-triggerable segfault in expand_filename(). (There isn't
6184 a way to trigger this remotely.)
6185 - When sending a status event to the controller telling it that an
6186 OR address is reachable, set the port correctly. (Previously we
6187 were reporting the dir port.)
6188 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
6189 command. Bugfix on 0.1.2.17.
6190 - When loading bandwidth history, do not believe any information in
6191 the future. Fixes bug 434.
6192 - When loading entry guard information, do not believe any information
6194 - When we have our clock set far in the future and generate an
6195 onion key, then re-set our clock to be correct, we should not stop
6196 the onion key from getting rotated.
6197 - On some platforms, accept() can return a broken address. Detect
6198 this more quietly, and deal accordingly. Fixes bug 483.
6199 - It's not actually an error to find a non-pending entry in the DNS
6200 cache when canceling a pending resolve. Don't log unless stuff
6201 is fishy. Resolves bug 463.
6202 - Don't reset trusted dir server list when we set a configuration
6203 option. Patch from Robert Hogan.
6206 Changes in version 0.1.2.17 - 2007-08-30
6207 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
6208 X bundles. Vidalia 0.0.14 makes authentication required for the
6209 ControlPort in the default configuration, which addresses important
6210 security risks. Everybody who uses Vidalia (or another controller)
6213 In addition, this Tor update fixes major load balancing problems with
6214 path selection, which should speed things up a lot once many people
6217 o Major bugfixes (security):
6218 - We removed support for the old (v0) control protocol. It has been
6219 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
6220 become more of a headache than it's worth.
6222 o Major bugfixes (load balancing):
6223 - When choosing nodes for non-guard positions, weight guards
6224 proportionally less, since they already have enough load. Patch
6226 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
6227 will allow fast Tor servers to get more attention.
6228 - When we're upgrading from an old Tor version, forget our current
6229 guards and pick new ones according to the new weightings. These
6230 three load balancing patches could raise effective network capacity
6231 by a factor of four. Thanks to Mike Perry for measurements.
6233 o Major bugfixes (stream expiration):
6234 - Expire not-yet-successful application streams in all cases if
6235 they've been around longer than SocksTimeout. Right now there are
6236 some cases where the stream will live forever, demanding a new
6237 circuit every 15 seconds. Fixes bug 454; reported by lodger.
6239 o Minor features (controller):
6240 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
6241 is valid before any authentication has been received. It tells
6242 a controller what kind of authentication is expected, and what
6243 protocol is spoken. Implements proposal 119.
6245 o Minor bugfixes (performance):
6246 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
6247 greatly speeding up loading cached-routers from disk on startup.
6248 - Disable sentinel-based debugging for buffer code: we squashed all
6249 the bugs that this was supposed to detect a long time ago, and now
6250 its only effect is to change our buffer sizes from nice powers of
6251 two (which platform mallocs tend to like) to values slightly over
6252 powers of two (which make some platform mallocs sad).
6254 o Minor bugfixes (misc):
6255 - If exit bandwidth ever exceeds one third of total bandwidth, then
6256 use the correct formula to weight exit nodes when choosing paths.
6257 Based on patch from Mike Perry.
6258 - Choose perfectly fairly among routers when choosing by bandwidth and
6259 weighting by fraction of bandwidth provided by exits. Previously, we
6260 would choose with only approximate fairness, and correct ourselves
6261 if we ran off the end of the list.
6262 - If we require CookieAuthentication but we fail to write the
6263 cookie file, we would warn but not exit, and end up in a state
6264 where no controller could authenticate. Now we exit.
6265 - If we require CookieAuthentication, stop generating a new cookie
6266 every time we change any piece of our config.
6267 - Refuse to start with certain directory authority keys, and
6268 encourage people using them to stop.
6269 - Terminate multi-line control events properly. Original patch
6271 - Fix a minor memory leak when we fail to find enough suitable
6272 servers to choose a circuit.
6273 - Stop leaking part of the descriptor when we run into a particularly
6274 unparseable piece of it.
6277 Changes in version 0.1.2.16 - 2007-08-01
6278 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
6279 remote attacker in certain situations to rewrite the user's torrc
6280 configuration file. This can completely compromise anonymity of users
6281 in most configurations, including those running the Vidalia bundles,
6282 TorK, etc. Or worse.
6284 o Major security fixes:
6285 - Close immediately after missing authentication on control port;
6286 do not allow multiple authentication attempts.
6289 Changes in version 0.1.2.15 - 2007-07-17
6290 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
6291 problems, fixes compilation on BSD, and fixes a variety of other
6292 bugs. Everybody should upgrade.
6294 o Major bugfixes (compilation):
6295 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
6297 o Major bugfixes (crashes):
6298 - Try even harder not to dereference the first character after
6299 an mmap(). Reported by lodger.
6300 - Fix a crash bug in directory authorities when we re-number the
6301 routerlist while inserting a new router.
6302 - When the cached-routers file is an even multiple of the page size,
6303 don't run off the end and crash. (Fixes bug 455; based on idea
6305 - Fix eventdns.c behavior on Solaris: It is critical to include
6306 orconfig.h _before_ sys/types.h, so that we can get the expected
6307 definition of _FILE_OFFSET_BITS.
6309 o Major bugfixes (security):
6310 - Fix a possible buffer overrun when using BSD natd support. Bug
6312 - When sending destroy cells from a circuit's origin, don't include
6313 the reason for tearing down the circuit. The spec says we didn't,
6314 and now we actually don't. Reported by lodger.
6315 - Keep streamids from different exits on a circuit separate. This
6316 bug may have allowed other routers on a given circuit to inject
6317 cells into streams. Reported by lodger; fixes bug 446.
6318 - If there's a never-before-connected-to guard node in our list,
6319 never choose any guards past it. This way we don't expand our
6320 guard list unless we need to.
6322 o Minor bugfixes (guard nodes):
6323 - Weight guard selection by bandwidth, so that low-bandwidth nodes
6324 don't get overused as guards.
6326 o Minor bugfixes (directory):
6327 - Correctly count the number of authorities that recommend each
6328 version. Previously, we were under-counting by 1.
6329 - Fix a potential crash bug when we load many server descriptors at
6330 once and some of them make others of them obsolete. Fixes bug 458.
6332 o Minor bugfixes (hidden services):
6333 - Stop tearing down the whole circuit when the user asks for a
6334 connection to a port that the hidden service didn't configure.
6337 o Minor bugfixes (misc):
6338 - On Windows, we were preventing other processes from reading
6339 cached-routers while Tor was running. Reported by janbar.
6340 - Fix a possible (but very unlikely) bug in picking routers by
6341 bandwidth. Add a log message to confirm that it is in fact
6342 unlikely. Patch from lodger.
6343 - Backport a couple of memory leak fixes.
6344 - Backport miscellaneous cosmetic bugfixes.
6347 Changes in version 0.1.2.14 - 2007-05-25
6348 Tor 0.1.2.14 changes the addresses of two directory authorities (this
6349 change especially affects those who serve or use hidden services),
6350 and fixes several other crash- and security-related bugs.
6352 o Directory authority changes:
6353 - Two directory authorities (moria1 and moria2) just moved to new
6354 IP addresses. This change will particularly affect those who serve
6355 or use hidden services.
6357 o Major bugfixes (crashes):
6358 - If a directory server runs out of space in the connection table
6359 as it's processing a begin_dir request, it will free the exit stream
6360 but leave it attached to the circuit, leading to unpredictable
6361 behavior. (Reported by seeess, fixes bug 425.)
6362 - Fix a bug in dirserv_remove_invalid() that would cause authorities
6363 to corrupt memory under some really unlikely scenarios.
6364 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
6365 - Avoid segfaults when reading from mmaped descriptor file. (Reported
6368 o Major bugfixes (security):
6369 - When choosing an entry guard for a circuit, avoid using guards
6370 that are in the same family as the chosen exit -- not just guards
6371 that are exactly the chosen exit. (Reported by lodger.)
6373 o Major bugfixes (resource management):
6374 - If a directory authority is down, skip it when deciding where to get
6375 networkstatus objects or descriptors. Otherwise we keep asking
6376 every 10 seconds forever. Fixes bug 384.
6377 - Count it as a failure if we fetch a valid network-status but we
6378 don't want to keep it. Otherwise we'll keep fetching it and keep
6379 not wanting to keep it. Fixes part of bug 422.
6380 - If all of our dirservers have given us bad or no networkstatuses
6381 lately, then stop hammering them once per minute even when we
6382 think they're failed. Fixes another part of bug 422.
6385 - Actually set the purpose correctly for descriptors inserted with
6387 - When we have k non-v2 authorities in our DirServer config,
6388 we ignored the last k authorities in the list when updating our
6390 - Correctly back-off from requesting router descriptors that we are
6391 having a hard time downloading.
6392 - Read resolv.conf files correctly on platforms where read() returns
6393 partial results on small file reads.
6394 - Don't rebuild the entire router store every time we get 32K of
6395 routers: rebuild it when the journal gets very large, or when
6396 the gaps in the store get very large.
6399 - When routers publish SVN revisions in their router descriptors,
6400 authorities now include those versions correctly in networkstatus
6402 - Warn when using a version of libevent before 1.3b to run a server on
6403 OSX or BSD: these versions interact badly with userspace threads.
6406 Changes in version 0.1.2.13 - 2007-04-24
6407 This release features some major anonymity fixes, such as safer path
6408 selection; better client performance; faster bootstrapping, better
6409 address detection, and better DNS support for servers; write limiting as
6410 well as read limiting to make servers easier to run; and a huge pile of
6411 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
6413 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
6414 of the Freenode IRC network, remembering his patience and vision for
6415 free speech on the Internet.
6417 o Major features, client performance:
6418 - Weight directory requests by advertised bandwidth. Now we can
6419 let servers enable write limiting but still allow most clients to
6420 succeed at their directory requests. (We still ignore weights when
6421 choosing a directory authority; I hope this is a feature.)
6422 - Stop overloading exit nodes -- avoid choosing them for entry or
6423 middle hops when the total bandwidth available from non-exit nodes
6424 is much higher than the total bandwidth available from exit nodes.
6425 - Rather than waiting a fixed amount of time between retrying
6426 application connections, we wait only 10 seconds for the first,
6427 10 seconds for the second, and 15 seconds for each retry after
6428 that. Hopefully this will improve the expected user experience.
6429 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
6430 to open a stream fails; now we do in more cases. This should
6431 make clients able to find a good exit faster in some cases, since
6432 unhandleable requests will now get an error rather than timing out.
6434 o Major features, client functionality:
6435 - Implement BEGIN_DIR cells, so we can connect to a directory
6436 server via TLS to do encrypted directory requests rather than
6437 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
6438 config options if you like. For now, this feature only works if
6439 you already have a descriptor for the destination dirserver.
6440 - Add support for transparent application connections: this basically
6441 bundles the functionality of trans-proxy-tor into the Tor
6442 mainline. Now hosts with compliant pf/netfilter implementations
6443 can redirect TCP connections straight to Tor without diverting
6444 through SOCKS. (Based on patch from tup.)
6445 - Add support for using natd; this allows FreeBSDs earlier than
6446 5.1.2 to have ipfw send connections through Tor without using
6447 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
6449 o Major features, servers:
6450 - Setting up a dyndns name for your server is now optional: servers
6451 with no hostname or IP address will learn their IP address by
6452 asking the directory authorities. This code only kicks in when you
6453 would normally have exited with a "no address" error. Nothing's
6454 authenticated, so use with care.
6455 - Directory servers now spool server descriptors, v1 directories,
6456 and v2 networkstatus objects to buffers as needed rather than en
6457 masse. They also mmap the cached-routers files. These steps save
6459 - Stop requiring clients to have well-formed certificates, and stop
6460 checking nicknames in certificates. (Clients have certificates so
6461 that they can look like Tor servers, but in the future we might want
6462 to allow them to look like regular TLS clients instead. Nicknames
6463 in certificates serve no purpose other than making our protocol
6464 easier to recognize on the wire.) Implements proposal 106.
6466 o Improvements on DNS support:
6467 - Add "eventdns" asynchronous dns library originally based on code
6468 from Adam Langley. Now we can discard the old rickety dnsworker
6469 concept, and support a wider variety of DNS functions. Allows
6470 multithreaded builds on NetBSD and OpenBSD again.
6471 - Add server-side support for "reverse" DNS lookups (using PTR
6472 records so clients can determine the canonical hostname for a given
6473 IPv4 address). Only supported by servers using eventdns; servers
6474 now announce in their descriptors if they don't support eventdns.
6475 - Workaround for name servers (like Earthlink's) that hijack failing
6476 DNS requests and replace the no-such-server answer with a "helpful"
6477 redirect to an advertising-driven search portal. Also work around
6478 DNS hijackers who "helpfully" decline to hijack known-invalid
6479 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
6480 lets you turn it off.
6481 - Servers now check for the case when common DNS requests are going to
6482 wildcarded addresses (i.e. all getting the same answer), and change
6483 their exit policy to reject *:* if it's happening.
6484 - When asked to resolve a hostname, don't use non-exit servers unless
6485 requested to do so. This allows servers with broken DNS to be
6486 useful to the network.
6487 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6488 useless IPv6 DNS resolves.
6489 - Specify and implement client-side SOCKS5 interface for reverse DNS
6490 lookups (see doc/socks-extensions.txt). Also cache them.
6491 - When we change nameservers or IP addresses, reset and re-launch
6492 our tests for DNS hijacking.
6494 o Improvements on reachability testing:
6495 - Servers send out a burst of long-range padding cells once they've
6496 established that they're reachable. Spread them over 4 circuits,
6497 so hopefully a few will be fast. This exercises bandwidth and
6498 bootstraps them into the directory more quickly.
6499 - When we find our DirPort to be reachable, publish a new descriptor
6500 so we'll tell the world (reported by pnx).
6501 - Directory authorities now only decide that routers are reachable
6502 if their identity keys are as expected.
6503 - Do DirPort reachability tests less often, since a single test
6504 chews through many circuits before giving up.
6505 - Avoid some false positives during reachability testing: don't try
6506 to test via a server that's on the same /24 network as us.
6507 - Start publishing one minute or so after we find our ORPort
6508 to be reachable. This will help reduce the number of descriptors
6509 we have for ourselves floating around, since it's quite likely
6510 other things (e.g. DirPort) will change during that minute too.
6511 - Routers no longer try to rebuild long-term connections to directory
6512 authorities, and directory authorities no longer try to rebuild
6513 long-term connections to all servers. We still don't hang up
6514 connections in these two cases though -- we need to look at it
6515 more carefully to avoid flapping, and we likely need to wait til
6516 0.1.1.x is obsolete.
6518 o Improvements on rate limiting:
6519 - Enable write limiting as well as read limiting. Now we sacrifice
6520 capacity if we're pushing out lots of directory traffic, rather
6521 than overrunning the user's intended bandwidth limits.
6522 - Include TLS overhead when counting bandwidth usage; previously, we
6523 would count only the bytes sent over TLS, but not the bytes used
6525 - Servers decline directory requests much more aggressively when
6526 they're low on bandwidth. Otherwise they end up queueing more and
6527 more directory responses, which can't be good for latency.
6528 - But never refuse directory requests from local addresses.
6529 - Be willing to read or write on local connections (e.g. controller
6530 connections) even when the global rate limiting buckets are empty.
6531 - Flush local controller connection buffers periodically as we're
6532 writing to them, so we avoid queueing 4+ megabytes of data before
6534 - Revise and clean up the torrc.sample that we ship with; add
6535 a section for BandwidthRate and BandwidthBurst.
6537 o Major features, NT services:
6538 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
6539 command-line flag so that admins can override the default by saying
6540 "tor --service install --user "SomeUser"". This will not affect
6541 existing installed services. Also, warn the user that the service
6542 will look for its configuration file in the service user's
6543 %appdata% directory. (We can't do the "hardwire the user's appdata
6544 directory" trick any more, since we may not have read access to that
6546 - Support running the Tor service with a torrc not in the same
6547 directory as tor.exe and default to using the torrc located in
6548 the %appdata%\Tor\ of the user who installed the service. Patch
6550 - Add an --ignore-missing-torrc command-line option so that we can
6551 get the "use sensible defaults if the configuration file doesn't
6552 exist" behavior even when specifying a torrc location on the
6554 - When stopping an NT service, wait up to 10 sec for it to actually
6555 stop. (Patch from Matt Edman; resolves bug 295.)
6557 o Directory authority improvements:
6558 - Stop letting hibernating or obsolete servers affect uptime and
6560 - Stop listing hibernating servers in the v1 directory.
6561 - Authorities no longer recommend exits as guards if this would shift
6562 too much load to the exit nodes.
6563 - Authorities now specify server versions in networkstatus. This adds
6564 about 2% to the size of compressed networkstatus docs, and allows
6565 clients to tell which servers support BEGIN_DIR and which don't.
6566 The implementation is forward-compatible with a proposed future
6567 protocol version scheme not tied to Tor versions.
6568 - DirServer configuration lines now have an orport= option so
6569 clients can open encrypted tunnels to the authorities without
6570 having downloaded their descriptors yet. Enabled for moria1,
6571 moria2, tor26, and lefkada now in the default configuration.
6572 - Add a BadDirectory flag to network status docs so that authorities
6573 can (eventually) tell clients about caches they believe to be
6574 broken. Not used yet.
6575 - Allow authorities to list nodes as bad exits in their
6576 approved-routers file by fingerprint or by address. If most
6577 authorities set a BadExit flag for a server, clients don't think
6578 of it as a general-purpose exit. Clients only consider authorities
6579 that advertise themselves as listing bad exits.
6580 - Patch from Steve Hildrey: Generate network status correctly on
6581 non-versioning dirservers.
6582 - Have directory authorities allow larger amounts of drift in uptime
6583 without replacing the server descriptor: previously, a server that
6584 restarted every 30 minutes could have 48 "interesting" descriptors
6586 - Reserve the nickname "Unnamed" for routers that can't pick
6587 a hostname: any router can call itself Unnamed; directory
6588 authorities will never allocate Unnamed to any particular router;
6589 clients won't believe that any router is the canonical Unnamed.
6591 o Directory mirrors and clients:
6592 - Discard any v1 directory info that's over 1 month old (for
6593 directories) or over 1 week old (for running-routers lists).
6594 - Clients track responses with status 503 from dirservers. After a
6595 dirserver has given us a 503, we try not to use it until an hour has
6596 gone by, or until we have no dirservers that haven't given us a 503.
6597 - When we get a 503 from a directory, and we're not a server, we no
6598 longer count the failure against the total number of failures
6599 allowed for the object we're trying to download.
6600 - Prepare for servers to publish descriptors less often: never
6601 discard a descriptor simply for being too old until either it is
6602 recommended by no authorities, or until we get a better one for
6603 the same router. Make caches consider retaining old recommended
6604 routers for even longer.
6605 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
6606 headers for content, so that we can work better in the presence of
6607 caching HTTP proxies.
6608 - Stop fetching descriptors if you're not a dir mirror and you
6609 haven't tried to establish any circuits lately. (This currently
6610 causes some dangerous behavior, because when you start up again
6611 you'll use your ancient server descriptors.)
6613 o Major fixes, crashes:
6614 - Stop crashing when the controller asks us to resetconf more than
6615 one config option at once. (Vidalia 0.0.11 does this.)
6616 - Fix a longstanding obscure crash bug that could occur when we run
6617 out of DNS worker processes, if we're not using eventdns. (Resolves
6619 - Fix an assert that could trigger if a controller quickly set then
6620 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
6621 - Avoid crash when telling controller about stream-status and a
6623 - Avoid sending junk to controllers or segfaulting when a controller
6624 uses EVENT_NEW_DESC with verbose nicknames.
6625 - Stop triggering asserts if the controller tries to extend hidden
6626 service circuits (reported by mwenge).
6627 - If we start a server with ClientOnly 1, then set ClientOnly to 0
6628 and hup, stop triggering an assert based on an empty onion_key.
6629 - Mask out all signals in sub-threads; only the libevent signal
6630 handler should be processing them. This should prevent some crashes
6631 on some machines using pthreads. (Patch from coderman.)
6632 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
6634 o Major fixes, anonymity/security:
6635 - Automatically avoid picking more than one node from the same
6636 /16 network when constructing a circuit. Add an
6637 "EnforceDistinctSubnets" option to let people disable it if they
6638 want to operate private test networks on a single subnet.
6639 - When generating bandwidth history, round down to the nearest
6640 1k. When storing accounting data, round up to the nearest 1k.
6641 - When we're running as a server, remember when we last rotated onion
6642 keys, so that we will rotate keys once they're a week old even if
6643 we never stay up for a week ourselves.
6644 - If a client asked for a server by name, and there's a named server
6645 in our network-status but we don't have its descriptor yet, we
6646 could return an unnamed server instead.
6647 - Reject (most) attempts to use Tor circuits with length one. (If
6648 many people start using Tor as a one-hop proxy, exit nodes become
6649 a more attractive target for compromise.)
6650 - Just because your DirPort is open doesn't mean people should be
6651 able to remotely teach you about hidden service descriptors. Now
6652 only accept rendezvous posts if you've got HSAuthoritativeDir set.
6653 - Fix a potential race condition in the rpm installer. Found by
6655 - Do not log IPs with TLS failures for incoming TLS
6656 connections. (Fixes bug 382.)
6658 o Major fixes, other:
6659 - If our system clock jumps back in time, don't publish a negative
6660 uptime in the descriptor.
6661 - When we start during an accounting interval before it's time to wake
6662 up, remember to wake up at the correct time. (May fix bug 342.)
6663 - Previously, we would cache up to 16 old networkstatus documents
6664 indefinitely, if they came from nontrusted authorities. Now we
6665 discard them if they are more than 10 days old.
6666 - When we have a state file we cannot parse, tell the user and
6667 move it aside. Now we avoid situations where the user starts
6668 Tor in 1904, Tor writes a state file with that timestamp in it,
6669 the user fixes her clock, and Tor refuses to start.
6670 - Publish a new descriptor after we hup/reload. This is important
6671 if our config has changed such that we'll want to start advertising
6672 our DirPort now, etc.
6673 - If we are using an exit enclave and we can't connect, e.g. because
6674 its webserver is misconfigured to not listen on localhost, then
6675 back off and try connecting from somewhere else before we fail.
6677 o New config options or behaviors:
6678 - When EntryNodes are configured, rebuild the guard list to contain,
6679 in order: the EntryNodes that were guards before; the rest of the
6680 EntryNodes; the nodes that were guards before.
6681 - Do not warn when individual nodes in the configuration's EntryNodes,
6682 ExitNodes, etc are down: warn only when all possible nodes
6683 are down. (Fixes bug 348.)
6684 - Put a lower-bound on MaxAdvertisedBandwidth.
6685 - Start using the state file to store bandwidth accounting data:
6686 the bw_accounting file is now obsolete. We'll keep generating it
6687 for a while for people who are still using 0.1.2.4-alpha.
6688 - Try to batch changes to the state file so that we do as few
6689 disk writes as possible while still storing important things in
6691 - The state file and the bw_accounting file get saved less often when
6692 the AvoidDiskWrites config option is set.
6693 - Make PIDFile work on Windows.
6694 - Add internal descriptions for a bunch of configuration options:
6695 accessible via controller interface and in comments in saved
6697 - Reject *:563 (NNTPS) in the default exit policy. We already reject
6698 NNTP by default, so this seems like a sensible addition.
6699 - Clients now reject hostnames with invalid characters. This should
6700 avoid some inadvertent info leaks. Add an option
6701 AllowNonRFC953Hostnames to disable this behavior, in case somebody
6702 is running a private network with hosts called @, !, and #.
6703 - Check for addresses with invalid characters at the exit as well,
6704 and warn less verbosely when they fail. You can override this by
6705 setting ServerDNSAllowNonRFC953Addresses to 1.
6706 - Remove some options that have been deprecated since at least
6707 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
6708 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
6709 to set log options. Mark PathlenCoinWeight as obsolete.
6710 - Stop accepting certain malformed ports in configured exit policies.
6711 - When the user uses bad syntax in the Log config line, stop
6712 suggesting other bad syntax as a replacement.
6713 - Add new config option "ResolvConf" to let the server operator
6714 choose an alternate resolve.conf file when using eventdns.
6715 - If one of our entry guards is on the ExcludeNodes list, or the
6716 directory authorities don't think it's a good guard, treat it as
6717 if it were unlisted: stop using it as a guard, and throw it off
6718 the guards list if it stays that way for a long time.
6719 - Allow directory authorities to be marked separately as authorities
6720 for the v1 directory protocol, the v2 directory protocol, and
6721 as hidden service directories, to make it easier to retire old
6722 authorities. V1 authorities should set "HSAuthoritativeDir 1"
6723 to continue being hidden service authorities too.
6724 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
6725 - Make TrackExitHosts case-insensitive, and fix the behavior of
6726 ".suffix" TrackExitHosts items to avoid matching in the middle of
6728 - New DirPort behavior: if you have your dirport set, you download
6729 descriptors aggressively like a directory mirror, whether or not
6733 - Create a new file ReleaseNotes which was the old ChangeLog. The
6734 new ChangeLog file now includes the notes for all development
6736 - Add a new address-spec.txt document to describe our special-case
6737 addresses: .exit, .onion, and .noconnnect.
6738 - Fork the v1 directory protocol into its own spec document,
6739 and mark dir-spec.txt as the currently correct (v2) spec.
6741 o Packaging, porting, and contrib
6742 - "tor --verify-config" now exits with -1(255) or 0 depending on
6743 whether the config options are bad or good.
6744 - The Debian package now uses --verify-config when (re)starting,
6745 to distinguish configuration errors from other errors.
6746 - Adapt a patch from goodell to let the contrib/exitlist script
6747 take arguments rather than require direct editing.
6748 - Prevent the contrib/exitlist script from printing the same
6749 result more than once.
6750 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
6751 - In the hidden service example in torrc.sample, stop recommending
6752 esoteric and discouraged hidden service options.
6753 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
6754 values before failing, and always enables eventdns.
6755 - Try to detect Windows correctly when cross-compiling.
6756 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
6757 Try to fix this in configure.in by checking for most functions
6758 before we check for libevent.
6759 - Update RPMs to require libevent 1.2.
6760 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6761 or later. Log when we are doing this, so we can diagnose it when
6762 it fails. (Also, recommend libevent 1.1b for kqueue and
6763 win32 methods; deprecate libevent 1.0b harder; make libevent
6764 recommendation system saner.)
6765 - Build with recent (1.3+) libevents on platforms that do not
6766 define the nonstandard types "u_int8_t" and friends.
6767 - Remove architecture from OS X builds. The official builds are
6768 now universal binaries.
6769 - Run correctly on OS X platforms with case-sensitive filesystems.
6770 - Correctly set maximum connection limit on Cygwin. (This time
6772 - Start compiling on MinGW on Windows (patches from Mike Chiussi
6774 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6775 - Finally fix the openssl warnings from newer gccs that believe that
6776 ignoring a return value is okay, but casting a return value and
6777 then ignoring it is a sign of madness.
6778 - On architectures where sizeof(int)>4, still clamp declarable
6779 bandwidth to INT32_MAX.
6781 o Minor features, controller:
6782 - Warn the user when an application uses the obsolete binary v0
6783 control protocol. We're planning to remove support for it during
6784 the next development series, so it's good to give people some
6786 - Add STREAM_BW events to report per-entry-stream bandwidth
6787 use. (Patch from Robert Hogan.)
6788 - Rate-limit SIGNEWNYM signals in response to controllers that
6789 impolitely generate them for every single stream. (Patch from
6790 mwenge; closes bug 394.)
6791 - Add a REMAP status to stream events to note that a stream's
6792 address has changed because of a cached address or a MapAddress
6794 - Make REMAP stream events have a SOURCE (cache or exit), and
6795 make them generated in every case where we get a successful
6796 connected or resolved cell.
6797 - Track reasons for OR connection failure; make these reasons
6798 available via the controller interface. (Patch from Mike Perry.)
6799 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
6800 can learn when clients are sending malformed hostnames to Tor.
6801 - Specify and implement some of the controller status events.
6802 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
6803 - Reimplement GETINFO so that info/names stays in sync with the
6805 - Implement "GETINFO fingerprint".
6806 - Implement "SETEVENTS GUARD" so controllers can get updates on
6807 entry guard status as it changes.
6808 - Make all connections to addresses of the form ".noconnect"
6809 immediately get closed. This lets application/controller combos
6810 successfully test whether they're talking to the same Tor by
6811 watching for STREAM events.
6812 - Add a REASON field to CIRC events; for backward compatibility, this
6813 field is sent only to controllers that have enabled the extended
6814 event format. Also, add additional reason codes to explain why
6815 a given circuit has been destroyed or truncated. (Patches from
6817 - Add a REMOTE_REASON field to extended CIRC events to tell the
6818 controller why a remote OR told us to close a circuit.
6819 - Stream events also now have REASON and REMOTE_REASON fields,
6820 working much like those for circuit events.
6821 - There's now a GETINFO ns/... field so that controllers can ask Tor
6822 about the current status of a router.
6823 - A new event type "NS" to inform a controller when our opinion of
6824 a router's status has changed.
6825 - Add a GETINFO events/names and GETINFO features/names so controllers
6826 can tell which events and features are supported.
6827 - A new CLEARDNSCACHE signal to allow controllers to clear the
6828 client-side DNS cache without expiring circuits.
6829 - Fix CIRC controller events so that controllers can learn the
6830 identity digests of non-Named servers used in circuit paths.
6831 - Let controllers ask for more useful identifiers for servers. Instead
6832 of learning identity digests for un-Named servers and nicknames
6833 for Named servers, the new identifiers include digest, nickname,
6834 and indication of Named status. Off by default; see control-spec.txt
6835 for more information.
6836 - Add a "getinfo address" controller command so it can display Tor's
6837 best guess to the user.
6838 - New controller event to alert the controller when our server
6839 descriptor has changed.
6840 - Give more meaningful errors on controller authentication failure.
6841 - Export the default exit policy via the control port, so controllers
6842 don't need to guess what it is / will be later.
6844 o Minor bugfixes, controller:
6845 - When creating a circuit via the controller, send a 'launched'
6846 event when we're done, so we follow the spec better.
6847 - Correct the control spec to match how the code actually responds
6848 to 'getinfo addr-mappings/*'. Reported by daejees.
6849 - The control spec described a GUARDS event, but the code
6850 implemented a GUARD event. Standardize on GUARD, but let people
6851 ask for GUARDS too. Reported by daejees.
6852 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
6853 clear the corresponding on_circuit variable, and remember later
6854 that we don't need to send a redundant CLOSED event. (Resolves part
6856 - Report events where a resolve succeeded or where we got a socks
6857 protocol error correctly, rather than calling both of them
6859 - Change reported stream target addresses to IP consistently when
6860 we finally get the IP from an exit node.
6861 - Send log messages to the controller even if they happen to be very
6863 - Flush ERR-level controller status events just like we currently
6864 flush ERR-level log events, so that a Tor shutdown doesn't prevent
6865 the controller from learning about current events.
6866 - Report the circuit number correctly in STREAM CLOSED events. Bug
6867 reported by Mike Perry.
6868 - Do not report bizarre values for results of accounting GETINFOs
6869 when the last second's write or read exceeds the allotted bandwidth.
6870 - Report "unrecognized key" rather than an empty string when the
6871 controller tries to fetch a networkstatus that doesn't exist.
6872 - When the controller does a "GETINFO network-status", tell it
6873 about even those routers whose descriptors are very old, and use
6874 long nicknames where appropriate.
6875 - Fix handling of verbose nicknames with ORCONN controller events:
6876 make them show up exactly when requested, rather than exactly when
6878 - Controller signals now work on non-Unix platforms that don't define
6879 SIGUSR1 and SIGUSR2 the way we expect.
6880 - Respond to SIGNAL command before we execute the signal, in case
6881 the signal shuts us down. Suggested by Karsten Loesing.
6882 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6884 o Minor features, code performance:
6885 - Major performance improvement on inserting descriptors: change
6886 algorithm from O(n^2) to O(n).
6887 - Do not rotate onion key immediately after setting it for the first
6889 - Call router_have_min_dir_info half as often. (This is showing up in
6890 some profiles, but not others.)
6891 - When using GCC, make log_debug never get called at all, and its
6892 arguments never get evaluated, when no debug logs are configured.
6893 (This is showing up in some profiles, but not others.)
6894 - Statistics dumped by -USR2 now include a breakdown of public key
6895 operations, for profiling.
6896 - Make the common memory allocation path faster on machines where
6897 malloc(0) returns a pointer.
6898 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6899 split connection_t into edge, or, dir, control, and base structs.
6900 These will save quite a bit of memory on busy servers, and they'll
6901 also help us track down bugs in the code and bugs in the spec.
6902 - Use OpenSSL's AES implementation on platforms where it's faster.
6903 This could save us as much as 10% CPU usage.
6905 o Minor features, descriptors and descriptor handling:
6906 - Avoid duplicate entries on MyFamily line in server descriptor.
6907 - When Tor receives a router descriptor that it asked for, but
6908 no longer wants (because it has received fresh networkstatuses
6909 in the meantime), do not warn the user. Cache the descriptor if
6910 we're a cache; drop it if we aren't.
6911 - Servers no longer ever list themselves in their "family" line,
6912 even if configured to do so. This makes it easier to configure
6913 family lists conveniently.
6915 o Minor fixes, confusing/misleading log messages:
6916 - Display correct results when reporting which versions are
6917 recommended, and how recommended they are. (Resolves bug 383.)
6918 - Inform the server operator when we decide not to advertise a
6919 DirPort due to AccountingMax enabled or a low BandwidthRate.
6920 - Only include function names in log messages for info/debug messages.
6921 For notice/warn/err, the content of the message should be clear on
6922 its own, and printing the function name only confuses users.
6923 - Remove even more protocol-related warnings from Tor server logs,
6924 such as bad TLS handshakes and malformed begin cells.
6925 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6926 when the IP address is mapped through MapAddress to a hostname.
6927 - Fix misleading log messages: an entry guard that is "unlisted",
6928 as well as not known to be "down" (because we've never heard
6929 of it), is not therefore "up".
6931 o Minor fixes, old/obsolete behavior:
6932 - Start assuming we can use a create_fast cell if we don't know
6933 what version a router is running.
6934 - We no longer look for identity and onion keys in "identity.key" and
6935 "onion.key" -- these were replaced by secret_id_key and
6936 secret_onion_key in 0.0.8pre1.
6937 - We no longer require unrecognized directory entries to be
6939 - Drop compatibility with obsolete Tors that permit create cells
6940 to have the wrong circ_id_type.
6941 - Remove code to special-case "-cvs" ending, since it has not
6942 actually mattered since 0.0.9.
6943 - Don't re-write the fingerprint file every restart, unless it has
6946 o Minor fixes, misc client-side behavior:
6947 - Always remove expired routers and networkstatus docs before checking
6948 whether we have enough information to build circuits. (Fixes
6950 - When computing clock skew from directory HTTP headers, consider what
6951 time it was when we finished asking for the directory, not what
6953 - Make our socks5 handling more robust to broken socks clients:
6954 throw out everything waiting on the buffer in between socks
6955 handshake phases, since they can't possibly (so the theory
6956 goes) have predicted what we plan to respond to them.
6957 - Expire socks connections if they spend too long waiting for the
6958 handshake to finish. Previously we would let them sit around for
6959 days, if the connecting application didn't close them either.
6960 - And if the socks handshake hasn't started, don't send a
6961 "DNS resolve socks failed" handshake reply; just close it.
6962 - If the user asks to use invalid exit nodes, be willing to use
6964 - Track unreachable entry guards correctly: don't conflate
6965 'unreachable by us right now' with 'listed as down by the directory
6966 authorities'. With the old code, if a guard was unreachable by us
6967 but listed as running, it would clog our guard list forever.
6968 - Behave correctly in case we ever have a network with more than
6969 2GB/s total advertised capacity.
6970 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6971 - Fix a memory leak when we ask for "all" networkstatuses and we
6972 get one we don't recognize.
6975 Changes in version 0.1.1.26 - 2006-12-14
6976 o Security bugfixes:
6977 - Stop sending the HttpProxyAuthenticator string to directory
6978 servers when directory connections are tunnelled through Tor.
6979 - Clients no longer store bandwidth history in the state file.
6980 - Do not log introduction points for hidden services if SafeLogging
6984 - Fix an assert failure when a directory authority sets
6985 AuthDirRejectUnlisted and then receives a descriptor from an
6986 unlisted router (reported by seeess).
6989 Changes in version 0.1.1.25 - 2006-11-04
6991 - When a client asks us to resolve (rather than connect to)
6992 an address, and we have a cached answer, give them the cached
6993 answer. Previously, we would give them no answer at all.
6994 - We were building exactly the wrong circuits when we predict
6995 hidden service requirements, meaning Tor would have to build all
6996 its circuits on demand.
6997 - If none of our live entry guards have a high uptime, but we
6998 require a guard with a high uptime, try adding a new guard before
6999 we give up on the requirement. This patch should make long-lived
7000 connections more stable on average.
7001 - When testing reachability of our DirPort, don't launch new
7002 tests when there's already one in progress -- unreachable
7003 servers were stacking up dozens of testing streams.
7005 o Security bugfixes:
7006 - When the user sends a NEWNYM signal, clear the client-side DNS
7007 cache too. Otherwise we continue to act on previous information.
7010 - Avoid a memory corruption bug when creating a hash table for
7012 - Avoid possibility of controller-triggered crash when misusing
7013 certain commands from a v0 controller on platforms that do not
7014 handle printf("%s",NULL) gracefully.
7015 - Avoid infinite loop on unexpected controller input.
7016 - Don't log spurious warnings when we see a circuit close reason we
7017 don't recognize; it's probably just from a newer version of Tor.
7018 - Add Vidalia to the OS X uninstaller script, so when we uninstall
7019 Tor/Privoxy we also uninstall Vidalia.
7022 Changes in version 0.1.1.24 - 2006-09-29
7024 - Allow really slow clients to not hang up five minutes into their
7025 directory downloads (suggested by Adam J. Richter).
7026 - Fix major performance regression from 0.1.0.x: instead of checking
7027 whether we have enough directory information every time we want to
7028 do something, only check when the directory information has changed.
7029 This should improve client CPU usage by 25-50%.
7030 - Don't crash if, after a server has been running for a while,
7031 it can't resolve its hostname.
7032 - When a client asks us to resolve (not connect to) an address,
7033 and we have a cached answer, give them the cached answer.
7034 Previously, we would give them no answer at all.
7037 - Allow Tor to start when RunAsDaemon is set but no logs are set.
7038 - Don't crash when the controller receives a third argument to an
7039 "extendcircuit" request.
7040 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
7041 response; fix error code when "getinfo dir/status/" fails.
7042 - Fix configure.in to not produce broken configure files with
7043 more recent versions of autoconf. Thanks to Clint for his auto*
7045 - Fix security bug on NetBSD that could allow someone to force
7046 uninitialized RAM to be sent to a server's DNS resolver. This
7047 only affects NetBSD and other platforms that do not bounds-check
7049 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
7050 methods: these are known to be buggy.
7051 - If we're a directory mirror and we ask for "all" network status
7052 documents, we would discard status documents from authorities
7056 Changes in version 0.1.1.23 - 2006-07-30
7058 - Fast Tor servers, especially exit nodes, were triggering asserts
7059 due to a bug in handling the list of pending DNS resolves. Some
7060 bugs still remain here; we're hunting them.
7061 - Entry guards could crash clients by sending unexpected input.
7062 - More fixes on reachability testing: if you find yourself reachable,
7063 then don't ever make any client requests (so you stop predicting
7064 circuits), then hup or have your clock jump, then later your IP
7065 changes, you won't think circuits are working, so you won't try to
7066 test reachability, so you won't publish.
7069 - Avoid a crash if the controller does a resetconf firewallports
7070 and then a setconf fascistfirewall=1.
7071 - Avoid an integer underflow when the dir authority decides whether
7072 a router is stable: we might wrongly label it stable, and compute
7073 a slightly wrong median stability, when a descriptor is published
7075 - Fix a place where we might trigger an assert if we can't build our
7076 own server descriptor yet.
7079 Changes in version 0.1.1.22 - 2006-07-05
7081 - Fix a big bug that was causing servers to not find themselves
7082 reachable if they changed IP addresses. Since only 0.1.1.22+
7083 servers can do reachability testing correctly, now we automatically
7084 make sure to test via one of these.
7085 - Fix to allow clients and mirrors to learn directory info from
7086 descriptor downloads that get cut off partway through.
7087 - Directory authorities had a bug in deciding if a newly published
7088 descriptor was novel enough to make everybody want a copy -- a few
7089 servers seem to be publishing new descriptors many times a minute.
7091 - Fix a rare bug that was causing some servers to complain about
7092 "closing wedged cpuworkers" and skip some circuit create requests.
7093 - Make the Exit flag in directory status documents actually work.
7096 Changes in version 0.1.1.21 - 2006-06-10
7097 o Crash and assert fixes from 0.1.1.20:
7098 - Fix a rare crash on Tor servers that have enabled hibernation.
7099 - Fix a seg fault on startup for Tor networks that use only one
7100 directory authority.
7101 - Fix an assert from a race condition that occurs on Tor servers
7102 while exiting, where various threads are trying to log that they're
7103 exiting, and delete the logs, at the same time.
7104 - Make our unit tests pass again on certain obscure platforms.
7107 - Add support for building SUSE RPM packages.
7108 - Speed up initial bootstrapping for clients: if we are making our
7109 first ever connection to any entry guard, then don't mark it down
7111 - When only one Tor server in the network is labelled as a guard,
7112 and we've already picked him, we would cycle endlessly picking him
7113 again, being unhappy about it, etc. Now we specifically exclude
7114 current guards when picking a new guard.
7115 - Servers send create cells more reliably after the TLS connection
7116 is established: we were sometimes forgetting to send half of them
7117 when we had more than one pending.
7118 - If we get a create cell that asks us to extend somewhere, but the
7119 Tor server there doesn't match the expected digest, we now send
7120 a destroy cell back, rather than silently doing nothing.
7121 - Make options->RedirectExit work again.
7122 - Make cookie authentication for the controller work again.
7123 - Stop being picky about unusual characters in the arguments to
7124 mapaddress. It's none of our business.
7125 - Add a new config option "TestVia" that lets you specify preferred
7126 middle hops to use for test circuits. Perhaps this will let me
7127 debug the reachability problems better.
7129 o Log / documentation fixes:
7130 - If we're a server and some peer has a broken TLS certificate, don't
7131 log about it unless ProtocolWarnings is set, i.e., we want to hear
7132 about protocol violations by others.
7133 - Fix spelling of VirtualAddrNetwork in man page.
7134 - Add a better explanation at the top of the autogenerated torrc file
7135 about what happened to our old torrc.
7138 Changes in version 0.1.1.20 - 2006-05-23
7139 o Crash and assert fixes from 0.1.0.17:
7140 - Fix assert bug in close_logs() on exit: when we close and delete
7141 logs, remove them all from the global "logfiles" list.
7142 - Fix an assert error when we're out of space in the connection_list
7143 and we try to post a hidden service descriptor (reported by Peter
7145 - Fix a rare assert error when we've tried all intro points for
7146 a hidden service and we try fetching the service descriptor again:
7147 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
7148 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
7149 out and refuse the setconf if it would fail.
7150 - If you specify a relative torrc path and you set RunAsDaemon in
7151 your torrc, then it chdir()'s to the new directory. If you then
7152 HUP, it tries to load the new torrc location, fails, and exits.
7153 The fix: no longer allow a relative path to torrc when using -f.
7154 - Check for integer overflows in more places, when adding elements
7155 to smartlists. This could possibly prevent a buffer overflow
7156 on malicious huge inputs.
7158 o Security fixes, major:
7159 - When we're printing strings from the network, don't try to print
7160 non-printable characters. Now we're safer against shell escape
7161 sequence exploits, and also against attacks to fool users into
7162 misreading their logs.
7163 - Implement entry guards: automatically choose a handful of entry
7164 nodes and stick with them for all circuits. Only pick new guards
7165 when the ones you have are unsuitable, and if the old guards
7166 become suitable again, switch back. This will increase security
7167 dramatically against certain end-point attacks. The EntryNodes
7168 config option now provides some hints about which entry guards you
7169 want to use most; and StrictEntryNodes means to only use those.
7170 Fixes CVE-2006-0414.
7171 - Implement exit enclaves: if we know an IP address for the
7172 destination, and there's a running Tor server at that address
7173 which allows exit to the destination, then extend the circuit to
7174 that exit first. This provides end-to-end encryption and end-to-end
7175 authentication. Also, if the user wants a .exit address or enclave,
7176 use 4 hops rather than 3, and cannibalize a general circ for it
7178 - Obey our firewall options more faithfully:
7179 . If we can't get to a dirserver directly, try going via Tor.
7180 . Don't ever try to connect (as a client) to a place our
7181 firewall options forbid.
7182 . If we specify a proxy and also firewall options, obey the
7183 firewall options even when we're using the proxy: some proxies
7184 can only proxy to certain destinations.
7185 - Make clients regenerate their keys when their IP address changes.
7186 - For the OS X package's modified privoxy config file, comment
7187 out the "logfile" line so we don't log everything passed
7189 - Our TLS handshakes were generating a single public/private
7190 keypair for the TLS context, rather than making a new one for
7191 each new connection. Oops. (But we were still rotating them
7192 periodically, so it's not so bad.)
7193 - When we were cannibalizing a circuit with a particular exit
7194 node in mind, we weren't checking to see if that exit node was
7195 already present earlier in the circuit. Now we are.
7196 - Require server descriptors to list IPv4 addresses -- hostnames
7197 are no longer allowed. This also fixes potential vulnerabilities
7198 to servers providing hostnames as their address and then
7199 preferentially resolving them so they can partition users.
7200 - Our logic to decide if the OR we connected to was the right guy
7201 was brittle and maybe open to a mitm for invalid routers.
7203 o Security fixes, minor:
7204 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
7205 Ian Goldberg can prove things about our handshake protocol more
7207 - Make directory authorities generate a separate "guard" flag to
7208 mean "would make a good entry guard". Clients now honor the
7209 is_guard flag rather than looking at is_fast or is_stable.
7210 - Try to list MyFamily elements by key, not by nickname, and warn
7211 if we've not heard of a server.
7212 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7213 OpenSSL. Also, reseed our entropy every hour, not just at
7214 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
7215 - Refuse server descriptors where the fingerprint line doesn't match
7216 the included identity key. Tor doesn't care, but other apps (and
7217 humans) might actually be trusting the fingerprint line.
7218 - We used to kill the circuit when we receive a relay command we
7219 don't recognize. Now we just drop that cell.
7220 - Fix a bug found by Lasse Overlier: when we were making internal
7221 circuits (intended to be cannibalized later for rendezvous and
7222 introduction circuits), we were picking them so that they had
7223 useful exit nodes. There was no need for this, and it actually
7224 aids some statistical attacks.
7225 - Start treating internal circuits and exit circuits separately.
7226 It's important to keep them separate because internal circuits
7227 have their last hops picked like middle hops, rather than like
7228 exit hops. So exiting on them will break the user's expectations.
7229 - Fix a possible way to DoS dirservers.
7230 - When the client asked for a rendezvous port that the hidden
7231 service didn't want to provide, we were sending an IP address
7232 back along with the end cell. Fortunately, it was zero. But stop
7235 o Packaging improvements:
7236 - Implement --with-libevent-dir option to ./configure. Improve
7237 search techniques to find libevent, and use those for openssl too.
7238 - Fix a couple of bugs in OpenSSL detection. Deal better when
7239 there are multiple SSLs installed with different versions.
7240 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
7241 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
7243 - Make unit tests (and other invocations that aren't the real Tor)
7244 run without launching listeners, creating subdirectories, and so on.
7245 - The OS X installer was adding a symlink for tor_resolve but
7246 the binary was called tor-resolve (reported by Thomas Hardly).
7247 - Now we can target arch and OS in rpm builds (contributed by
7248 Phobos). Also make the resulting dist-rpm filename match the
7250 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
7251 if you log to syslog and want something other than LOG_DAEMON.
7252 - Fix the torify (tsocks) config file to not use Tor for localhost
7254 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7255 tor-doc-server.html, and stylesheet.css in the tarball.
7256 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
7257 They are useless now.
7258 - Add Peter Palfrader's contributed check-tor script. It lets you
7259 easily check whether a given server (referenced by nickname)
7260 is reachable by you.
7261 - Add BSD-style contributed startup script "rc.subr" from Peter
7264 o Directory improvements -- new directory protocol:
7265 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
7266 - Authorities and caches publish individual descriptors (by
7267 digest, by fingerprint, by "all", and by "tell me yours").
7268 - Clients don't download or use the old directory anymore. Now they
7269 download network-statuses from the directory authorities, and
7270 fetch individual server descriptors as needed from mirrors.
7271 - Clients don't download descriptors of non-running servers.
7272 - Download descriptors by digest, not by fingerprint. Caches try to
7273 download all listed digests from authorities; clients try to
7274 download "best" digests from caches. This avoids partitioning
7275 and isolating attacks better.
7276 - Only upload a new server descriptor when options change, 18
7277 hours have passed, uptime is reset, or bandwidth changes a lot.
7278 - Directory authorities silently throw away new descriptors that
7279 haven't changed much if the timestamps are similar. We do this to
7280 tolerate older Tor servers that upload a new descriptor every 15
7281 minutes. (It seemed like a good idea at the time.)
7282 - Clients choose directory servers from the network status lists,
7283 not from their internal list of router descriptors. Now they can
7284 go to caches directly rather than needing to go to authorities
7285 to bootstrap the first set of descriptors.
7286 - When picking a random directory, prefer non-authorities if any
7288 - Add a new flag to network-status indicating whether the server
7289 can answer v2 directory requests too.
7290 - Directory mirrors now cache up to 16 unrecognized network-status
7291 docs, so new directory authorities will be cached too.
7292 - Stop parsing, storing, or using running-routers output (but
7293 mirrors still cache and serve it).
7294 - Clients consider a threshold of "versioning" directory authorities
7295 before deciding whether to warn the user that he's obsolete.
7296 - Authorities publish separate sorted lists of recommended versions
7297 for clients and for servers.
7298 - Change DirServers config line to note which dirs are v1 authorities.
7299 - Put nicknames on the DirServer line, so we can refer to them
7300 without requiring all our users to memorize their IP addresses.
7301 - Remove option when getting directory cache to see whether they
7302 support running-routers; they all do now. Replace it with one
7303 to see whether caches support v2 stuff.
7304 - Stop listing down or invalid nodes in the v1 directory. This
7305 reduces its bulk by about 1/3, and reduces load on mirrors.
7306 - Mirrors no longer cache the v1 directory as often.
7307 - If we as a directory mirror don't know of any v1 directory
7308 authorities, then don't try to cache any v1 directories.
7310 o Other directory improvements:
7311 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
7312 fifth authoritative directory servers.
7313 - Directory authorities no longer require an open connection from
7314 a server to consider him "reachable". We need this change because
7315 when we add new directory authorities, old servers won't know not
7317 - Dir authorities now do their own external reachability testing
7318 of each server, and only list as running the ones they found to
7319 be reachable. We also send back warnings to the server's logs if
7320 it uploads a descriptor that we already believe is unreachable.
7321 - Spread the directory authorities' reachability testing over the
7322 entire testing interval, so we don't try to do 500 TLS's at once
7324 - Make the "stable" router flag in network-status be the median of
7325 the uptimes of running valid servers, and make clients pay
7326 attention to the network-status flags. Thus the cutoff adapts
7327 to the stability of the network as a whole, making IRC, IM, etc
7328 connections more reliable.
7329 - Make the v2 dir's "Fast" flag based on relative capacity, just
7330 like "Stable" is based on median uptime. Name everything in the
7331 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
7332 - Retry directory requests if we fail to get an answer we like
7333 from a given dirserver (we were retrying before, but only if
7334 we fail to connect).
7335 - Return a robots.txt on our dirport to discourage google indexing.
7337 o Controller protocol improvements:
7338 - Revised controller protocol (version 1) that uses ascii rather
7339 than binary: tor/doc/control-spec.txt. Add supporting libraries
7340 in python and java and c# so you can use the controller from your
7341 applications without caring how our protocol works.
7342 - Allow the DEBUG controller event to work again. Mark certain log
7343 entries as "don't tell this to controllers", so we avoid cycles.
7344 - New controller function "getinfo accounting", to ask how
7345 many bytes we've used in this time period.
7346 - Add a "resetconf" command so you can set config options like
7347 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7348 a config option in the torrc with no value, then it clears it
7349 entirely (rather than setting it to its default).
7350 - Add a "getinfo config-file" to tell us where torrc is. Also
7351 expose guard nodes, config options/names.
7352 - Add a "quit" command (when when using the controller manually).
7353 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
7354 stop using any currently-dirty circuits for new streams, so we
7355 don't link new actions to old actions. This also occurs on HUP
7357 - If we would close a stream early (e.g. it asks for a .exit that
7358 we know would refuse it) but the LeaveStreamsUnattached config
7359 option is set by the controller, then don't close it.
7360 - Add a new controller event type "authdir_newdescs" that allows
7361 controllers to get all server descriptors that were uploaded to
7362 a router in its role as directory authority.
7363 - New controller option "getinfo desc/all-recent" to fetch the
7364 latest server descriptor for every router that Tor knows about.
7365 - Fix the controller's "attachstream 0" command to treat conn like
7366 it just connected, doing address remapping, handling .exit and
7367 .onion idioms, and so on. Now we're more uniform in making sure
7368 that the controller hears about new and closing connections.
7369 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
7370 the controller. Also, rotate dns and cpu workers if the controller
7371 changes options that will affect them; and initialize the dns
7372 worker cache tree whether or not we start out as a server.
7373 - Add a new circuit purpose 'controller' to let the controller ask
7374 for a circuit that Tor won't try to use. Extend the "extendcircuit"
7375 controller command to let you specify the purpose if you're starting
7376 a new circuit. Add a new "setcircuitpurpose" controller command to
7377 let you change a circuit's purpose after it's been created.
7378 - Let the controller ask for "getinfo dir/server/foo" so it can ask
7379 directly rather than connecting to the dir port. "getinfo
7380 dir/status/foo" also works, but currently only if your DirPort
7382 - Let the controller tell us about certain router descriptors
7383 that it doesn't want Tor to use in circuits. Implement
7384 "setrouterpurpose" and modify "+postdescriptor" to do this.
7385 - If the controller's *setconf commands fail, collect an error
7386 message in a string and hand it back to the controller -- don't
7387 just tell them to go read their logs.
7389 o Scalability, resource management, and performance:
7390 - Fix a major load balance bug: we were round-robin reading in 16 KB
7391 chunks, and servers with bandwidthrate of 20 KB, while downloading
7392 a 600 KB directory, would starve their other connections. Now we
7393 try to be a bit more fair.
7394 - Be more conservative about whether to advertise our DirPort.
7395 The main change is to not advertise if we're running at capacity
7396 and either a) we could hibernate ever or b) our capacity is low
7397 and we're using a default DirPort.
7398 - We weren't cannibalizing circuits correctly for
7399 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7400 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7401 build those from scratch. This should make hidden services faster.
7402 - Predict required circuits better, with an eye toward making hidden
7403 services faster on the service end.
7404 - Compress exit policies even more: look for duplicate lines and
7406 - Generate 18.0.0.0/8 address policy format in descs when we can;
7407 warn when the mask is not reducible to a bit-prefix.
7408 - There used to be two ways to specify your listening ports in a
7409 server descriptor: on the "router" line and with a separate "ports"
7410 line. Remove support for the "ports" line.
7411 - Reduce memory requirements in our structs by changing the order
7412 of fields. Replace balanced trees with hash tables. Inline
7413 bottleneck smartlist functions. Add a "Map from digest to void*"
7414 abstraction so we can do less hex encoding/decoding, and use it
7415 in router_get_by_digest(). Many other CPU and memory improvements.
7416 - Allow tor_gzip_uncompress to extract as much as possible from
7417 truncated compressed data. Try to extract as many
7418 descriptors as possible from truncated http responses (when
7419 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
7420 - Make circ->onionskin a pointer, not a static array. moria2 was using
7421 125000 circuit_t's after it had been up for a few weeks, which
7422 translates to 20+ megs of wasted space.
7423 - The private half of our EDH handshake keys are now chosen out
7424 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7425 - Stop doing the complex voodoo overkill checking for insecure
7426 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
7427 - Do round-robin writes for TLS of at most 16 kB per write. This
7428 might be more fair on loaded Tor servers.
7429 - Do not use unaligned memory access on alpha, mips, or mipsel.
7430 It *works*, but is very slow, so we treat them as if it doesn't.
7432 o Other bugfixes and improvements:
7433 - Start storing useful information to $DATADIR/state, so we can
7434 remember things across invocations of Tor. Retain unrecognized
7435 lines so we can be forward-compatible, and write a TorVersion line
7436 so we can be backward-compatible.
7437 - If ORPort is set, Address is not explicitly set, and our hostname
7438 resolves to a private IP address, try to use an interface address
7439 if it has a public address. Now Windows machines that think of
7440 themselves as localhost can guess their address.
7441 - Regenerate our local descriptor if it's dirty and we try to use
7442 it locally (e.g. if it changes during reachability detection).
7443 This was causing some Tor servers to keep publishing the same
7444 initial descriptor forever.
7445 - Tor servers with dynamic IP addresses were needing to wait 18
7446 hours before they could start doing reachability testing using
7447 the new IP address and ports. This is because they were using
7448 the internal descriptor to learn what to test, yet they were only
7449 rebuilding the descriptor once they decided they were reachable.
7450 - It turns out we couldn't bootstrap a network since we added
7451 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7452 has never gone down. Add an AssumeReachable config option to let
7453 servers and authorities bootstrap. When we're trying to build a
7454 high-uptime or high-bandwidth circuit but there aren't enough
7455 suitable servers, try being less picky rather than simply failing.
7456 - Newly bootstrapped Tor networks couldn't establish hidden service
7457 circuits until they had nodes with high uptime. Be more tolerant.
7458 - Really busy servers were keeping enough circuits open on stable
7459 connections that they were wrapping around the circuit_id
7460 space. (It's only two bytes.) This exposed a bug where we would
7461 feel free to reuse a circuit_id even if it still exists but has
7462 been marked for close. Try to fix this bug. Some bug remains.
7463 - When we fail to bind or listen on an incoming or outgoing
7464 socket, we now close it before refusing, rather than just
7465 leaking it. (Thanks to Peter Palfrader for finding.)
7466 - Fix a file descriptor leak in start_daemon().
7467 - On Windows, you can't always reopen a port right after you've
7468 closed it. So change retry_listeners() to only close and re-open
7469 ports that have changed.
7470 - Workaround a problem with some http proxies that refuse GET
7471 requests that specify "Content-Length: 0". Reported by Adrian.
7472 - Recover better from TCP connections to Tor servers that are
7473 broken but don't tell you (it happens!); and rotate TLS
7474 connections once a week.
7475 - Fix a scary-looking but apparently harmless bug where circuits
7476 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
7477 servers, and never switch to state CIRCUIT_STATE_OPEN.
7478 - Check for even more Windows version flags when writing the platform
7479 string in server descriptors, and note any we don't recognize.
7480 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
7481 get a better idea of why their circuits failed. Not used yet.
7482 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7483 We don't use them yet, but maybe one day our DNS resolver will be
7484 able to discover them.
7485 - Let people type "tor --install" as well as "tor -install" when they
7486 want to make it an NT service.
7487 - Looks like we were never delivering deflated (i.e. compressed)
7488 running-routers lists, even when asked. Oops.
7489 - We were leaking some memory every time the client changed IPs.
7490 - Clean up more of the OpenSSL memory when exiting, so we can detect
7491 memory leaks better.
7492 - Never call free() on tor_malloc()d memory. This will help us
7493 use dmalloc to detect memory leaks.
7494 - Some Tor servers process billions of cells per day. These
7495 statistics are now uint64_t's.
7496 - Check [X-]Forwarded-For headers in HTTP requests when generating
7497 log messages. This lets people run dirservers (and caches) behind
7498 Apache but still know which IP addresses are causing warnings.
7499 - Fix minor integer overflow in calculating when we expect to use up
7500 our bandwidth allocation before hibernating.
7501 - Lower the minimum required number of file descriptors to 1000,
7502 so we can have some overhead for Valgrind on Linux, where the
7503 default ulimit -n is 1024.
7504 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
7505 and its existence is confusing some users.
7507 o Config option fixes:
7508 - Add a new config option ExitPolicyRejectPrivate which defaults
7509 to on. Now all exit policies will begin with rejecting private
7510 addresses, unless the server operator explicitly turns it off.
7511 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
7512 - Add new ReachableORAddresses and ReachableDirAddresses options
7513 that understand address policies. FascistFirewall is now a synonym
7514 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
7515 - Start calling it FooListenAddress rather than FooBindAddress,
7516 since few of our users know what it means to bind an address
7518 - If the user gave Tor an odd number of command-line arguments,
7519 we were silently ignoring the last one. Now we complain and fail.
7520 This wins the oldest-bug prize -- this bug has been present since
7521 November 2002, as released in Tor 0.0.0.
7522 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7523 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7524 it would silently ignore the 6668.
7525 - If we get a linelist or linelist_s config option from the torrc,
7526 e.g. ExitPolicy, and it has no value, warn and skip rather than
7527 silently resetting it to its default.
7528 - Setconf was appending items to linelists, not clearing them.
7529 - Add MyFamily to torrc.sample in the server section, so operators
7530 will be more likely to learn that it exists.
7531 - Make ContactInfo mandatory for authoritative directory servers.
7532 - MaxConn has been obsolete for a while now. Document the ConnLimit
7533 config option, which is a *minimum* number of file descriptors
7534 that must be available else Tor refuses to start.
7535 - Get rid of IgnoreVersion undocumented config option, and make us
7536 only warn, never exit, when we're running an obsolete version.
7537 - Make MonthlyAccountingStart config option truly obsolete now.
7538 - Correct the man page entry on TrackHostExitsExpire.
7539 - Let directory authorities start even if they don't specify an
7540 Address config option.
7541 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
7542 reflect the updated flags in our v2 dir protocol.
7544 o Config option features:
7545 - Add a new config option FastFirstHopPK (on by default) so clients
7546 do a trivial crypto handshake for their first hop, since TLS has
7547 already taken care of confidentiality and authentication.
7548 - Let the user set ControlListenAddress in the torrc. This can be
7549 dangerous, but there are some cases (like a secured LAN) where it
7551 - New config options to help controllers: FetchServerDescriptors
7552 and FetchHidServDescriptors for whether to fetch server
7553 info and hidserv info or let the controller do it, and
7554 PublishServerDescriptor and PublishHidServDescriptors.
7555 - Also let the controller set the __AllDirActionsPrivate config
7556 option if you want all directory fetches/publishes to happen via
7557 Tor (it assumes your controller bootstraps your circuits).
7558 - Add "HardwareAccel" config option: support for crypto hardware
7559 accelerators via OpenSSL. Off by default, until we find somebody
7560 smart who can test it for us. (It appears to produce seg faults
7561 in at least some cases.)
7562 - New config option "AuthDirRejectUnlisted" for directory authorities
7563 as a panic button: if we get flooded with unusable servers we can
7564 revert to only listing servers in the approved-routers file.
7565 - Directory authorities can now reject/invalidate by key and IP,
7566 with the config options "AuthDirInvalid" and "AuthDirReject", or
7567 by marking a fingerprint as "!reject" or "!invalid" (as its
7568 nickname) in the approved-routers file. This is useful since
7569 currently we automatically list servers as running and usable
7570 even if we know they're jerks.
7571 - Add a new config option TestSocks so people can see whether their
7572 applications are using socks4, socks4a, socks5-with-ip, or
7573 socks5-with-fqdn. This way they don't have to keep mucking
7574 with tcpdump and wondering if something got cached somewhere.
7575 - Add "private:*" as an alias in configuration for policies. Now
7576 you can simplify your exit policy rather than needing to list
7577 every single internal or nonroutable network space.
7578 - Accept "private:*" in routerdesc exit policies; not generated yet
7579 because older Tors do not understand it.
7580 - Add configuration option "V1AuthoritativeDirectory 1" which
7581 moria1, moria2, and tor26 have set.
7582 - Implement an option, VirtualAddrMask, to set which addresses
7583 get handed out in response to mapaddress requests. This works
7584 around a bug in tsocks where 127.0.0.0/8 is never socksified.
7585 - Add a new config option FetchUselessDescriptors, off by default,
7586 for when you plan to run "exitlist" on your client and you want
7587 to know about even the non-running descriptors.
7588 - SocksTimeout: How long do we let a socks connection wait
7589 unattached before we fail it?
7590 - CircuitBuildTimeout: Cull non-open circuits that were born
7591 at least this many seconds ago.
7592 - CircuitIdleTimeout: Cull open clean circuits that were born
7593 at least this many seconds ago.
7594 - New config option SafeSocks to reject all application connections
7595 using unsafe socks protocols. Defaults to off.
7597 o Improved and clearer log messages:
7598 - Reduce clutter in server logs. We're going to try to make
7599 them actually usable now. New config option ProtocolWarnings that
7600 lets you hear about how _other Tors_ are breaking the protocol. Off
7602 - Divide log messages into logging domains. Once we put some sort
7603 of interface on this, it will let people looking at more verbose
7604 log levels specify the topics they want to hear more about.
7605 - Log server fingerprint on startup, so new server operators don't
7606 have to go hunting around their filesystem for it.
7607 - Provide dire warnings to any users who set DirServer manually;
7608 move it out of torrc.sample and into torrc.complete.
7609 - Make the log message less scary when all the dirservers are
7610 temporarily unreachable.
7611 - When tor_socketpair() fails in Windows, give a reasonable
7612 Windows-style errno back.
7613 - Improve tor_gettimeofday() granularity on windows.
7614 - We were printing the number of idle dns workers incorrectly when
7616 - Handle duplicate lines in approved-routers files without warning.
7617 - We were whining about using socks4 or socks5-with-local-lookup
7618 even when it's an IP address in the "virtual" range we designed
7619 exactly for this case.
7620 - Check for named servers when looking them up by nickname;
7621 warn when we're calling a non-named server by its nickname;
7622 don't warn twice about the same name.
7623 - Downgrade the dirserver log messages when whining about
7625 - Correct "your server is reachable" log entries to indicate that
7626 it was self-testing that told us so.
7627 - If we're trying to be a Tor server and running Windows 95/98/ME
7628 as a server, explain that we'll likely crash.
7629 - Provide a more useful warn message when our onion queue gets full:
7630 the CPU is too slow or the exit policy is too liberal.
7631 - Don't warn when we receive a 503 from a dirserver/cache -- this
7632 will pave the way for them being able to refuse if they're busy.
7633 - When we fail to bind a listener, try to provide a more useful
7634 log message: e.g., "Is Tor already running?"
7635 - Only start testing reachability once we've established a
7636 circuit. This will make startup on dir authorities less noisy.
7637 - Don't try to upload hidden service descriptors until we have
7638 established a circuit.
7639 - Tor didn't warn when it failed to open a log file.
7640 - Warn when listening on a public address for socks. We suspect a
7641 lot of people are setting themselves up as open socks proxies,
7642 and they have no idea that jerks on the Internet are using them,
7643 since they simply proxy the traffic into the Tor network.
7644 - Give a useful message when people run Tor as the wrong user,
7645 rather than telling them to start chowning random directories.
7646 - Fix a harmless bug that was causing Tor servers to log
7647 "Got an end because of misc error, but we're not an AP. Closing."
7648 - Fix wrong log message when you add a "HiddenServiceNodes" config
7649 line without any HiddenServiceDir line (reported by Chris Thomas).
7650 - Directory authorities now stop whining so loudly about bad
7651 descriptors that they fetch from other dirservers. So when there's
7652 a log complaint, it's for sure from a freshly uploaded descriptor.
7653 - When logging via syslog, include the pid whenever we provide
7654 a log entry. Suggested by Todd Fries.
7655 - When we're shutting down and we do something like try to post a
7656 server descriptor or rendezvous descriptor, don't complain that
7657 we seem to be unreachable. Of course we are, we're shutting down.
7658 - Change log line for unreachability to explicitly suggest /etc/hosts
7659 as the culprit. Also make it clearer what IP address and ports we're
7660 testing for reachability.
7661 - Put quotes around user-supplied strings when logging so users are
7662 more likely to realize if they add bad characters (like quotes)
7664 - NT service patch from Matt Edman to improve error messages on Win32.
7667 Changes in version 0.1.0.17 - 2006-02-17
7668 o Crash bugfixes on 0.1.0.x:
7669 - When servers with a non-zero DirPort came out of hibernation,
7670 sometimes they would trigger an assert.
7672 o Other important bugfixes:
7673 - On platforms that don't have getrlimit (like Windows), we were
7674 artificially constraining ourselves to a max of 1024
7675 connections. Now just assume that we can handle as many as 15000
7676 connections. Hopefully this won't cause other problems.
7678 o Backported features:
7679 - When we're a server, a client asks for an old-style directory,
7680 and our write bucket is empty, don't give it to him. This way
7681 small servers can continue to serve the directory *sometimes*,
7682 without getting overloaded.
7683 - Whenever you get a 503 in response to a directory fetch, try
7684 once more. This will become important once servers start sending
7685 503's whenever they feel busy.
7686 - Fetch a new directory every 120 minutes, not every 40 minutes.
7687 Now that we have hundreds of thousands of users running the old
7688 directory algorithm, it's starting to hurt a lot.
7689 - Bump up the period for forcing a hidden service descriptor upload
7690 from 20 minutes to 1 hour.
7693 Changes in version 0.1.0.16 - 2006-01-02
7694 o Crash bugfixes on 0.1.0.x:
7695 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7696 corrupting the heap, losing FDs, or crashing when we need to resize
7697 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7698 - It turns out sparc64 platforms crash on unaligned memory access
7699 too -- so detect and avoid this.
7700 - Handle truncated compressed data correctly (by detecting it and
7702 - Fix possible-but-unlikely free(NULL) in control.c.
7703 - When we were closing connections, there was a rare case that
7704 stomped on memory, triggering seg faults and asserts.
7705 - Avoid potential infinite recursion when building a descriptor. (We
7706 don't know that it ever happened, but better to fix it anyway.)
7707 - We were neglecting to unlink marked circuits from soon-to-close OR
7708 connections, which caused some rare scribbling on freed memory.
7709 - Fix a memory stomping race bug when closing the joining point of two
7710 rendezvous circuits.
7711 - Fix an assert in time parsing found by Steven Murdoch.
7713 o Other bugfixes on 0.1.0.x:
7714 - When we're doing reachability testing, provide more useful log
7715 messages so the operator knows what to expect.
7716 - Do not check whether DirPort is reachable when we are suppressing
7717 advertising it because of hibernation.
7718 - When building with -static or on Solaris, we sometimes needed -ldl.
7719 - One of the dirservers (tor26) changed its IP address.
7720 - When we're deciding whether a stream has enough circuits around
7721 that can handle it, count the freshly dirty ones and not the ones
7722 that are so dirty they won't be able to handle it.
7723 - When we're expiring old circuits, we had a logic error that caused
7724 us to close new rendezvous circuits rather than old ones.
7725 - Give a more helpful log message when you try to change ORPort via
7726 the controller: you should upgrade Tor if you want that to work.
7727 - We were failing to parse Tor versions that start with "Tor ".
7728 - Tolerate faulty streams better: when a stream fails for reason
7729 exitpolicy, stop assuming that the router is lying about his exit
7730 policy. When a stream fails for reason misc, allow it to retry just
7731 as if it was resolvefailed. When a stream has failed three times,
7732 reset its failure count so we can try again and get all three tries.
7735 Changes in version 0.1.0.15 - 2005-09-23
7736 o Bugfixes on 0.1.0.x:
7737 - Reject ports 465 and 587 (spam targets) in default exit policy.
7738 - Don't crash when we don't have any spare file descriptors and we
7739 try to spawn a dns or cpu worker.
7740 - Get rid of IgnoreVersion undocumented config option, and make us
7741 only warn, never exit, when we're running an obsolete version.
7742 - Don't try to print a null string when your server finds itself to
7743 be unreachable and the Address config option is empty.
7744 - Make the numbers in read-history and write-history into uint64s,
7745 so they don't overflow and publish negatives in the descriptor.
7746 - Fix a minor memory leak in smartlist_string_remove().
7747 - We were only allowing ourselves to upload a server descriptor at
7748 most every 20 minutes, even if it changed earlier than that.
7749 - Clean up log entries that pointed to old URLs.
7752 Changes in version 0.1.0.14 - 2005-08-08
7753 o Bugfixes on 0.1.0.x:
7754 - Fix the other half of the bug with crypto handshakes
7756 - Fix an assert trigger if you send a 'signal term' via the
7757 controller when it's listening for 'event info' messages.
7760 Changes in version 0.1.0.13 - 2005-08-04
7761 o Bugfixes on 0.1.0.x:
7762 - Fix a critical bug in the security of our crypto handshakes.
7763 - Fix a size_t underflow in smartlist_join_strings2() that made
7764 it do bad things when you hand it an empty smartlist.
7765 - Fix Windows installer to ship Tor license (thanks to Aphex for
7766 pointing out this oversight) and put a link to the doc directory
7768 - Explicitly set no-unaligned-access for sparc: it turns out the
7769 new gcc's let you compile broken code, but that doesn't make it
7773 Changes in version 0.1.0.12 - 2005-07-18
7774 o New directory servers:
7775 - tor26 has changed IP address.
7777 o Bugfixes on 0.1.0.x:
7778 - Fix a possible double-free in tor_gzip_uncompress().
7779 - When --disable-threads is set, do not search for or link against
7781 - Don't trigger an assert if an authoritative directory server
7782 claims its dirport is 0.
7783 - Fix bug with removing Tor as an NT service: some people were
7784 getting "The service did not return an error." Thanks to Matt
7788 Changes in version 0.1.0.11 - 2005-06-30
7789 o Bugfixes on 0.1.0.x:
7790 - Fix major security bug: servers were disregarding their
7791 exit policies if clients behaved unexpectedly.
7792 - Make OS X init script check for missing argument, so we don't
7793 confuse users who invoke it incorrectly.
7794 - Fix a seg fault in "tor --hash-password foo".
7795 - The MAPADDRESS control command was broken.
7798 Changes in version 0.1.0.10 - 2005-06-14
7800 - Make NT services work and start on startup on Win32 (based on
7801 patch by Matt Edman). See the FAQ entry for details.
7802 - Make 'platform' string in descriptor more accurate for Win32
7803 servers, so it's not just "unknown platform".
7804 - REUSEADDR on normal platforms means you can rebind to the port
7805 right after somebody else has let it go. But REUSEADDR on Win32
7806 means you can bind to the port _even when somebody else already
7807 has it bound_! So, don't do that on Win32.
7808 - Clean up the log messages when starting on Win32 with no config
7810 - Allow seeding the RNG on Win32 even when you're not running as
7811 Administrator. If seeding the RNG on Win32 fails, quit.
7813 o Assert / crash bugs:
7814 - Refuse relay cells that claim to have a length larger than the
7815 maximum allowed. This prevents a potential attack that could read
7816 arbitrary memory (e.g. keys) from an exit server's process
7818 - If unofficial Tor clients connect and send weird TLS certs, our
7819 Tor server triggers an assert. Stop asserting, and start handling
7820 TLS errors better in other situations too.
7821 - Fix a race condition that can trigger an assert when we have a
7822 pending create cell and an OR connection attempt fails.
7825 - Use pthreads for worker processes rather than forking. This was
7826 forced because when we forked, we ended up wasting a lot of
7827 duplicate ram over time.
7828 - Also switch to foo_r versions of some library calls to allow
7829 reentry and threadsafeness.
7830 - Implement --disable-threads configure option. Disable threads on
7831 netbsd and openbsd by default, because they have no reentrant
7832 resolver functions (!), and on solaris since it has other
7834 - Fix possible bug on threading platforms (e.g. win32) which was
7835 leaking a file descriptor whenever a cpuworker or dnsworker died.
7836 - Fix a minor memory leak when somebody establishes an introduction
7837 point at your Tor server.
7838 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
7840 - Add ./configure --with-dmalloc option, to track memory leaks.
7841 - And try to free all memory on closing, so we can detect what
7844 o Protocol correctness:
7845 - When we've connected to an OR and handshaked but didn't like
7846 the result, we were closing the conn without sending destroy
7847 cells back for pending circuits. Now send those destroys.
7848 - Start sending 'truncated' cells back rather than destroy cells
7849 if the circuit closes in front of you. This means we won't have
7850 to abandon partially built circuits.
7851 - Handle changed router status correctly when dirserver reloads
7852 fingerprint file. We used to be dropping all unverified descriptors
7853 right then. The bug was hidden because we would immediately
7854 fetch a directory from another dirserver, which would include the
7855 descriptors we just dropped.
7856 - Revise tor-spec to add more/better stream end reasons.
7857 - Revise all calls to connection_edge_end to avoid sending 'misc',
7858 and to take errno into account where possible.
7859 - Client now retries when streams end early for 'hibernating' or
7860 'resource limit' reasons, rather than failing them.
7861 - Try to be more zealous about calling connection_edge_end when
7862 things go bad with edge conns in connection.c.
7864 o Robustness improvements:
7865 - Better handling for heterogeneous / unreliable nodes:
7866 - Annotate circuits with whether they aim to contain high uptime
7867 nodes and/or high capacity nodes. When building circuits, choose
7869 - This means that every single node in an intro rend circuit,
7870 not just the last one, will have a minimum uptime.
7871 - New config option LongLivedPorts to indicate application streams
7872 that will want high uptime circuits.
7873 - Servers reset uptime when a dir fetch entirely fails. This
7874 hopefully reflects stability of the server's network connectivity.
7875 - If somebody starts his tor server in Jan 2004 and then fixes his
7876 clock, don't make his published uptime be a year.
7877 - Reset published uptime when we wake up from hibernation.
7878 - Introduce a notion of 'internal' circs, which are chosen without
7879 regard to the exit policy of the last hop. Intro and rendezvous
7880 circs must be internal circs, to avoid leaking information. Resolve
7881 and connect streams can use internal circs if they want.
7882 - New circuit pooling algorithm: keep track of what destination ports
7883 we've used recently (start out assuming we'll want to use 80), and
7884 make sure to have enough circs around to satisfy these ports. Also
7885 make sure to have 2 internal circs around if we've required internal
7886 circs lately (and with high uptime if we've seen that lately too).
7887 - Turn addr_policy_compare from a tristate to a quadstate; this should
7888 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7889 for google.com" problem.
7890 - When a client asks us for a dir mirror and we don't have one,
7891 launch an attempt to get a fresh one.
7892 - First cut at support for "create-fast" cells. Clients can use
7893 these when extending to their first hop, since the TLS already
7894 provides forward secrecy and authentication. Not enabled on
7897 o Reachability testing.
7898 - Your Tor server will automatically try to see if its ORPort and
7899 DirPort are reachable from the outside, and it won't upload its
7900 descriptor until it decides at least ORPort is reachable (when
7901 DirPort is not yet found reachable, publish it as zero).
7902 - When building testing circs for ORPort testing, use only
7903 high-bandwidth nodes, so fewer circuits fail.
7904 - Notice when our IP changes, and reset stats/uptime/reachability.
7905 - Authdirservers don't do ORPort reachability detection, since
7906 they're in clique mode, so it will be rare to find a server not
7907 already connected to them.
7908 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
7912 - Now we allow two unverified servers with the same nickname
7913 but different keys. But if a nickname is verified, only that
7914 nickname+key are allowed.
7915 - If you're an authdirserver connecting to an address:port,
7916 and it's not the OR you were expecting, forget about that
7917 descriptor. If he *was* the one you were expecting, then forget
7918 about all other descriptors for that address:port.
7919 - Allow servers to publish descriptors from 12 hours in the future.
7920 Corollary: only whine about clock skew from the dirserver if
7921 he's a trusted dirserver (since now even verified servers could
7922 have quite wrong clocks).
7923 - Require servers that use the default dirservers to have public IP
7924 addresses. We have too many servers that are configured with private
7925 IPs and their admins never notice the log entries complaining that
7926 their descriptors are being rejected.
7928 o Efficiency improvements:
7929 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
7930 and /dev/poll), and hopefully work better on Windows too.
7931 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
7932 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
7933 - Find libevent even if it's hiding in /usr/local/ and your
7934 CFLAGS and LDFLAGS don't tell you to look there.
7935 - Be able to link with libevent as a shared library (the default
7936 after 1.0d), even if it's hiding in /usr/local/lib and even
7937 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7938 assuming you're running gcc. Otherwise fail and give a useful
7940 - Switch to a new buffer management algorithm, which tries to avoid
7941 reallocing and copying quite as much. In first tests it looks like
7942 it uses *more* memory on average, but less cpu.
7943 - Switch our internal buffers implementation to use a ring buffer,
7944 to hopefully improve performance for fast servers a lot.
7945 - Reenable the part of the code that tries to flush as soon as an
7946 OR outbuf has a full TLS record available. Perhaps this will make
7947 OR outbufs not grow as huge except in rare cases, thus saving lots
7948 of CPU time plus memory.
7949 - Improve performance for dirservers: stop re-parsing the whole
7950 directory every time you regenerate it.
7951 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7952 it much faster to look up a circuit for each relay cell.
7953 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7954 since they're eating our cpu on exit nodes.
7955 - Stop wasting time doing a case insensitive comparison for every
7956 dns name every time we do any lookup. Canonicalize the names to
7957 lowercase when you first see them.
7960 - Handle unavailable hidden services better. Handle slow or busy
7961 hidden services better.
7962 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7963 circ as necessary, if there are any completed ones lying around
7964 when we try to launch one.
7965 - Make hidden services try to establish a rendezvous for 30 seconds
7966 after fetching the descriptor, rather than for n (where n=3)
7967 attempts to build a circuit.
7968 - Adjust maximum skew and age for rendezvous descriptors: let skew
7969 be 48 hours rather than 90 minutes.
7970 - Reject malformed .onion addresses rather then passing them on as
7971 normal web requests.
7974 - More Tor controller support. See
7975 http://tor.eff.org/doc/control-spec.txt for all the new features,
7976 including signals to emulate unix signals from any platform;
7977 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7978 closestream; closecircuit; etc.
7979 - Encode hashed controller passwords in hex instead of base64,
7980 to make it easier to write controllers.
7981 - Revise control spec and implementation to allow all log messages to
7982 be sent to controller with their severities intact (suggested by
7983 Matt Edman). Disable debug-level logs while delivering a debug-level
7984 log to the controller, to prevent loop. Update TorControl to handle
7985 new log event types.
7987 o New config options/defaults:
7988 - Begin scrubbing sensitive strings from logs by default. Turn off
7989 the config option SafeLogging if you need to do debugging.
7990 - New exit policy: accept most low-numbered ports, rather than
7991 rejecting most low-numbered ports.
7992 - Put a note in the torrc about abuse potential with the default
7994 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7996 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
7997 based on patch from Adam Langley (basic auth only).
7998 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7999 the fast servers that have been joining lately. (Clients are now
8000 willing to load balance over up to 2 MB of advertised bandwidth
8002 - New config option MaxAdvertisedBandwidth which lets you advertise
8003 a low bandwidthrate (to not attract as many circuits) while still
8004 allowing a higher bandwidthrate in reality.
8005 - Require BandwidthRate to be at least 20kB/s for servers.
8006 - Add a NoPublish config option, so you can be a server (e.g. for
8007 testing running Tor servers in other Tor networks) without
8008 publishing your descriptor to the primary dirservers.
8009 - Add a new AddressMap config directive to rewrite incoming socks
8010 addresses. This lets you, for example, declare an implicit
8011 required exit node for certain sites.
8012 - Add a new TrackHostExits config directive to trigger addressmaps
8013 for certain incoming socks addresses -- for sites that break when
8014 your exit keeps changing (based on patch from Mike Perry).
8015 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
8016 which describes how often we retry making new circuits if current
8017 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
8018 how long we're willing to make use of an already-dirty circuit.
8019 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
8020 a config option "ShutdownWaitLength" (when using kill -INT on
8022 - Fix an edge case in parsing config options: if they say "--"
8023 on the commandline, it's not a config option (thanks weasel).
8024 - New config option DirAllowPrivateAddresses for authdirservers.
8025 Now by default they refuse router descriptors that have non-IP or
8026 private-IP addresses.
8027 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
8028 smart" default value: low for servers and high for clients.
8029 - Some people were putting "Address " in their torrc, and they had
8030 a buggy resolver that resolved " " to 0.0.0.0. Oops.
8031 - If DataDir is ~/.tor, and that expands to /.tor, then default to
8032 LOCALSTATEDIR/tor instead.
8033 - Implement --verify-config command-line option to check if your torrc
8034 is valid without actually launching Tor.
8036 o Logging improvements:
8037 - When dirservers refuse a server descriptor, we now log its
8038 contactinfo, platform, and the poster's IP address.
8039 - Only warn once per nickname from add_nickname_list_to_smartlist()
8040 per failure, so an entrynode or exitnode choice that's down won't
8042 - When we're connecting to an OR and he's got a different nickname/key
8043 than we were expecting, only complain loudly if we're an OP or a
8044 dirserver. Complaining loudly to the OR admins just confuses them.
8045 - Whine at you if you're a server and you don't set your contactinfo.
8046 - Warn when exit policy implicitly allows local addresses.
8047 - Give a better warning when some other server advertises an
8048 ORPort that is actually an apache running ssl.
8049 - If we get an incredibly skewed timestamp from a dirserver mirror
8050 that isn't a verified OR, don't warn -- it's probably him that's
8052 - When a dirserver causes you to give a warn, mention which dirserver
8054 - Initialize libevent later in the startup process, so the logs are
8055 already established by the time we start logging libevent warns.
8056 - Use correct errno on win32 if libevent fails.
8057 - Check and warn about known-bad/slow libevent versions.
8058 - Stop warning about sigpipes in the logs. We're going to
8059 pretend that getting these occassionally is normal and fine.
8061 o New contrib scripts:
8062 - New experimental script tor/contrib/exitlist: a simple python
8063 script to parse directories and find Tor nodes that exit to listed
8065 - New experimental script tor/contrib/ExerciseServer.py (needs more
8066 work) that uses the controller interface to build circuits and
8067 fetch pages over them. This will help us bootstrap servers that
8068 have lots of capacity but haven't noticed it yet.
8069 - New experimental script tor/contrib/PathDemo.py (needs more work)
8070 that uses the controller interface to let you choose whole paths
8072 "<hostname>.<path,separated by dots>.<length of path>.path"
8073 - New contributed script "privoxy-tor-toggle" to toggle whether
8074 Privoxy uses Tor. Seems to be configured for Debian by default.
8075 - Have torctl.in/tor.sh.in check for location of su binary (needed
8079 - chdir() to your datadirectory at the *end* of the daemonize process,
8080 not the beginning. This was a problem because the first time you
8081 run tor, if your datadir isn't there, and you have runasdaemon set
8082 to 1, it will try to chdir to it before it tries to create it. Oops.
8083 - Fix several double-mark-for-close bugs, e.g. where we were finding
8084 a conn for a cell even if that conn is already marked for close.
8085 - Stop most cases of hanging up on a socks connection without sending
8087 - Fix a bug in the RPM package: set home directory for _tor to
8088 something more reasonable when first installing.
8089 - Stop putting nodename in the Platform string in server descriptors.
8090 It doesn't actually help, and it is confusing/upsetting some people.
8091 - When using preferred entry or exit nodes, ignore whether the
8092 circuit wants uptime or capacity. They asked for the nodes, they
8094 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
8095 artificially capped at 500kB.
8096 - Cache local dns resolves correctly even when they're .exit
8098 - If we're hibernating and we get a SIGINT, exit immediately.
8099 - tor-resolve requests were ignoring .exit if there was a working circuit
8100 they could use instead.
8101 - Pay more attention to the ClientOnly config option.
8102 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
8103 installer screens; and don't put stuff into StartupItems unless
8104 the user asks you to.
8107 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
8108 rather than just rejecting it.
8109 - If our clock jumps forward by 100 seconds or more, assume something
8110 has gone wrong with our network and abandon all not-yet-used circs.
8111 - When an application is using socks5, give him the whole variety of
8112 potential socks5 responses (connect refused, host unreachable, etc),
8113 rather than just "success" or "failure".
8114 - A more sane version numbering system. See
8115 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
8116 - Change version parsing logic: a version is "obsolete" if it is not
8117 recommended and (1) there is a newer recommended version in the
8118 same series, or (2) there are no recommended versions in the same
8119 series, but there are some recommended versions in a newer series.
8120 A version is "new" if it is newer than any recommended version in
8122 - Report HTTP reasons to client when getting a response from directory
8123 servers -- so you can actually know what went wrong.
8124 - Reject odd-looking addresses at the client (e.g. addresses that
8125 contain a colon), rather than having the server drop them because
8127 - Stop publishing socksport in the directory, since it's not
8128 actually meant to be public. For compatibility, publish a 0 there
8130 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8131 cookies to disk and doesn't log each web request to disk. (Thanks
8132 to Brett Carrington for pointing this out.)
8133 - Add OSX uninstall instructions. An actual uninstall script will
8135 - Add "opt hibernating 1" to server descriptor to make it clearer
8136 whether the server is hibernating.
8139 Changes in version 0.0.9.10 - 2005-06-16
8140 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
8141 - Refuse relay cells that claim to have a length larger than the
8142 maximum allowed. This prevents a potential attack that could read
8143 arbitrary memory (e.g. keys) from an exit server's process
8147 Changes in version 0.0.9.9 - 2005-04-23
8148 o Bugfixes on 0.0.9.x:
8149 - If unofficial Tor clients connect and send weird TLS certs, our
8150 Tor server triggers an assert. This release contains a minimal
8151 backport from the broader fix that we put into 0.1.0.4-rc.
8154 Changes in version 0.0.9.8 - 2005-04-07
8155 o Bugfixes on 0.0.9.x:
8156 - We have a bug that I haven't found yet. Sometimes, very rarely,
8157 cpuworkers get stuck in the 'busy' state, even though the cpuworker
8158 thinks of itself as idle. This meant that no new circuits ever got
8159 established. Here's a workaround to kill any cpuworker that's been
8160 busy for more than 100 seconds.
8163 Changes in version 0.0.9.7 - 2005-04-01
8164 o Bugfixes on 0.0.9.x:
8165 - Fix another race crash bug (thanks to Glenn Fink for reporting).
8166 - Compare identity to identity, not to nickname, when extending to
8167 a router not already in the directory. This was preventing us from
8168 extending to unknown routers. Oops.
8169 - Make sure to create OS X Tor user in <500 range, so we aren't
8170 creating actual system users.
8171 - Note where connection-that-hasn't-sent-end was marked, and fix
8172 a few really loud instances of this harmless bug (it's fixed more
8176 Changes in version 0.0.9.6 - 2005-03-24
8177 o Bugfixes on 0.0.9.x (crashes and asserts):
8178 - Add new end stream reasons to maintainance branch. Fix bug where
8179 reason (8) could trigger an assert. Prevent bug from recurring.
8180 - Apparently win32 stat wants paths to not end with a slash.
8181 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8182 blowing away the circuit that conn->cpath_layer points to, then
8183 checking to see if the circ is well-formed. Backport check to make
8184 sure we dont use the cpath on a closed connection.
8185 - Prevent circuit_resume_edge_reading_helper() from trying to package
8186 inbufs for marked-for-close streams.
8187 - Don't crash on hup if your options->address has become unresolvable.
8188 - Some systems (like OS X) sometimes accept() a connection and tell
8189 you the remote host is 0.0.0.0:0. If this happens, due to some
8190 other mis-features, we get confused; so refuse the conn for now.
8192 o Bugfixes on 0.0.9.x (other):
8193 - Fix harmless but scary "Unrecognized content encoding" warn message.
8194 - Add new stream error reason: TORPROTOCOL reason means "you are not
8195 speaking a version of Tor I understand; say bye-bye to your stream."
8196 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8197 into the future, now that we are more tolerant of skew. This
8198 resolves a bug where a Tor server would refuse to cache a directory
8199 because all the directories it gets are too far in the future;
8200 yet the Tor server never logs any complaints about clock skew.
8201 - Mac packaging magic: make man pages useable, and do not overwrite
8202 existing torrc files.
8203 - Make OS X log happily to /var/log/tor/tor.log
8206 Changes in version 0.0.9.5 - 2005-02-22
8207 o Bugfixes on 0.0.9.x:
8208 - Fix an assert race at exit nodes when resolve requests fail.
8209 - Stop picking unverified dir mirrors--it only leads to misery.
8210 - Patch from Matt Edman to make NT services work better. Service
8211 support is still not compiled into the executable by default.
8212 - Patch from Dmitri Bely so the Tor service runs better under
8213 the win32 SYSTEM account.
8214 - Make tor-resolve actually work (?) on Win32.
8215 - Fix a sign bug when getrlimit claims to have 4+ billion
8216 file descriptors available.
8217 - Stop refusing to start when bandwidthburst == bandwidthrate.
8218 - When create cells have been on the onion queue more than five
8219 seconds, just send back a destroy and take them off the list.
8222 Changes in version 0.0.9.4 - 2005-02-03
8223 o Bugfixes on 0.0.9:
8224 - Fix an assert bug that took down most of our servers: when
8225 a server claims to have 1 GB of bandwidthburst, don't
8227 - Don't crash as badly if we have spawned the max allowed number
8228 of dnsworkers, or we're out of file descriptors.
8229 - Block more file-sharing ports in the default exit policy.
8230 - MaxConn is now automatically set to the hard limit of max
8231 file descriptors we're allowed (ulimit -n), minus a few for
8233 - Give a clearer message when servers need to raise their
8234 ulimit -n when they start running out of file descriptors.
8235 - SGI Compatibility patches from Jan Schaumann.
8236 - Tolerate a corrupt cached directory better.
8237 - When a dirserver hasn't approved your server, list which one.
8238 - Go into soft hibernation after 95% of the bandwidth is used,
8239 not 99%. This is especially important for daily hibernators who
8240 have a small accounting max. Hopefully it will result in fewer
8241 cut connections when the hard hibernation starts.
8242 - Load-balance better when using servers that claim more than
8243 800kB/s of capacity.
8244 - Make NT services work (experimental, only used if compiled in).
8247 Changes in version 0.0.9.3 - 2005-01-21
8248 o Bugfixes on 0.0.9:
8249 - Backport the cpu use fixes from main branch, so busy servers won't
8250 need as much processor time.
8251 - Work better when we go offline and then come back, or when we
8252 run Tor at boot before the network is up. We do this by
8253 optimistically trying to fetch a new directory whenever an
8254 application request comes in and we think we're offline -- the
8255 human is hopefully a good measure of when the network is back.
8256 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8257 long as you keep using them; actually publish hidserv descriptors
8258 shortly after they change, rather than waiting 20-40 minutes.
8259 - Enable Mac startup script by default.
8260 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8261 - When you update AllowUnverifiedNodes or FirewallPorts via the
8262 controller's setconf feature, we were always appending, never
8264 - When you update HiddenServiceDir via setconf, it was screwing up
8265 the order of reading the lines, making it fail.
8266 - Do not rewrite a cached directory back to the cache; otherwise we
8267 will think it is recent and not fetch a newer one on startup.
8268 - Workaround for webservers that lie about Content-Encoding: Tor
8269 now tries to autodetect compressed directories and compression
8270 itself. This lets us Proxypass dir fetches through apache.
8273 Changes in version 0.0.9.2 - 2005-01-04
8274 o Bugfixes on 0.0.9 (crashes and asserts):
8275 - Fix an assert on startup when the disk is full and you're logging
8277 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8278 style address, then we'd crash.
8279 - Fix an assert trigger when the running-routers string we get from
8280 a dirserver is broken.
8281 - Make worker threads start and run on win32. Now win32 servers
8283 - Bandaid (not actually fix, but now it doesn't crash) an assert
8284 where the dns worker dies mysteriously and the main Tor process
8285 doesn't remember anything about the address it was resolving.
8287 o Bugfixes on 0.0.9 (Win32):
8288 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8289 name out of the warning/assert messages.
8290 - Fix a superficial "unhandled error on read" bug on win32.
8291 - The win32 installer no longer requires a click-through for our
8292 license, since our Free Software license grants rights but does not
8294 - Win32: When connecting to a dirserver fails, try another one
8295 immediately. (This was already working for non-win32 Tors.)
8296 - Stop trying to parse $HOME on win32 when hunting for default
8298 - Make tor-resolve.c work on win32 by calling network_init().
8300 o Bugfixes on 0.0.9 (other):
8301 - Make 0.0.9.x build on Solaris again.
8302 - Due to a fencepost error, we were blowing away the \n when reporting
8303 confvalue items in the controller. So asking for multiple config
8304 values at once couldn't work.
8305 - When listing circuits that are pending on an opening OR connection,
8306 if we're an OR we were listing circuits that *end* at us as
8307 being pending on every listener, dns/cpu worker, etc. Stop that.
8308 - Dirservers were failing to create 'running-routers' or 'directory'
8309 strings if we had more than some threshold of routers. Fix them so
8310 they can handle any number of routers.
8311 - Fix a superficial "Duplicate mark for close" bug.
8312 - Stop checking for clock skew for OR connections, even for servers.
8313 - Fix a fencepost error that was chopping off the last letter of any
8314 nickname that is the maximum allowed nickname length.
8315 - Update URLs in log messages so they point to the new website.
8316 - Fix a potential problem in mangling server private keys while
8317 writing to disk (not triggered yet, as far as we know).
8318 - Include the licenses for other free software we include in Tor,
8319 now that we're shipping binary distributions more regularly.
8322 Changes in version 0.0.9.1 - 2004-12-15
8323 o Bugfixes on 0.0.9:
8324 - Make hibernation actually work.
8325 - Make HashedControlPassword config option work.
8326 - When we're reporting event circuit status to a controller,
8327 don't use the stream status code.
8330 Changes in version 0.0.9 - 2004-12-12
8331 o Bugfixes on 0.0.8.1 (Crashes and asserts):
8332 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8333 write() call will fail and we handle it there.
8334 - When we run out of disk space, or other log writing error, don't
8335 crash. Just stop logging to that log and continue.
8336 - Fix isspace() and friends so they still make Solaris happy
8337 but also so they don't trigger asserts on win32.
8338 - Fix assert failure on malformed socks4a requests.
8339 - Fix an assert bug where a hidden service provider would fail if
8340 the first hop of his rendezvous circuit was down.
8341 - Better handling of size_t vs int, so we're more robust on 64
8344 o Bugfixes on 0.0.8.1 (Win32):
8345 - Make windows sockets actually non-blocking (oops), and handle
8346 win32 socket errors better.
8347 - Fix parse_iso_time on platforms without strptime (eg win32).
8348 - win32: when being multithreaded, leave parent fdarray open.
8349 - Better handling of winsock includes on non-MSV win32 compilers.
8350 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8352 - Make unit tests work on win32.
8354 o Bugfixes on 0.0.8.1 (Path selection and streams):
8355 - Calculate timeout for waiting for a connected cell from the time
8356 we sent the begin cell, not from the time the stream started. If
8357 it took a long time to establish the circuit, we would time out
8358 right after sending the begin cell.
8359 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8360 of * as always matching, so we were picking reject *:* nodes as
8361 exit nodes too. Oops.
8362 - When read() failed on a stream, we would close it without sending
8363 back an end. So 'connection refused' would simply be ignored and
8364 the user would get no response.
8365 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8366 we shouldn't hold-open-until-flush if the eof arrived first.
8367 - Let resolve conns retry/expire also, rather than sticking around
8369 - Fix more dns related bugs: send back resolve_failed and end cells
8370 more reliably when the resolve fails, rather than closing the
8371 circuit and then trying to send the cell. Also attach dummy resolve
8372 connections to a circuit *before* calling dns_resolve(), to fix
8373 a bug where cached answers would never be sent in RESOLVED cells.
8375 o Bugfixes on 0.0.8.1 (Circuits):
8376 - Finally fix a bug that's been plaguing us for a year:
8377 With high load, circuit package window was reaching 0. Whenever
8378 we got a circuit-level sendme, we were reading a lot on each
8379 socket, but only writing out a bit. So we would eventually reach
8380 eof. This would be noticed and acted on even when there were still
8381 bytes sitting in the inbuf.
8382 - Use identity comparison, not nickname comparison, to choose which
8383 half of circuit-ID-space each side gets to use. This is needed
8384 because sometimes we think of a router as a nickname, and sometimes
8385 as a hex ID, and we can't predict what the other side will do.
8387 o Bugfixes on 0.0.8.1 (Other):
8388 - Fix a whole slew of memory leaks.
8389 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8390 - If we are using select, make sure we stay within FD_SETSIZE.
8391 - When poll() is interrupted, we shouldn't believe the revents values.
8392 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8393 and smartlist_len, which are two major profiling offenders.
8394 - If do_hup fails, actually notice.
8395 - Flush the log file descriptor after we print "Tor opening log file",
8396 so we don't see those messages days later.
8397 - Hidden service operators now correctly handle version 1 style
8398 INTRODUCE1 cells (nobody generates them still, so not a critical
8400 - Handle more errnos from accept() without closing the listener.
8401 Some OpenBSD machines were closing their listeners because
8402 they ran out of file descriptors.
8403 - Some people had wrapped their tor client/server in a script
8404 that would restart it whenever it died. This did not play well
8405 with our "shut down if your version is obsolete" code. Now people
8406 don't fetch a new directory if their local cached version is
8408 - Make our autogen.sh work on ksh as well as bash.
8409 - Better torrc example lines for dirbindaddress and orbindaddress.
8410 - Improved bounds checking on parsed ints (e.g. config options and
8411 the ones we find in directories.)
8412 - Stop using separate defaults for no-config-file and
8413 empty-config-file. Now you have to explicitly turn off SocksPort,
8414 if you don't want it open.
8415 - We were starting to daemonize before we opened our logs, so if
8416 there were any problems opening logs, we would complain to stderr,
8417 which wouldn't work, and then mysteriously exit.
8418 - If a verified OR connects to us before he's uploaded his descriptor,
8419 or we verify him and hup but he still has the original TLS
8420 connection, then conn->nickname is still set like he's unverified.
8422 o Code security improvements, inspired by Ilja:
8423 - tor_snprintf wrapper over snprintf with consistent (though not C99)
8425 - Replace sprintf with tor_snprintf. (I think they were all safe, but
8427 - Replace strcpy/strncpy with strlcpy in more places.
8428 - Avoid strcat; use tor_snprintf or strlcat instead.
8430 o Features (circuits and streams):
8431 - New circuit building strategy: keep a list of ports that we've
8432 used in the past 6 hours, and always try to have 2 circuits open
8433 or on the way that will handle each such port. Seed us with port
8434 80 so web users won't complain that Tor is "slow to start up".
8435 - Make kill -USR1 dump more useful stats about circuits.
8436 - When warning about retrying or giving up, print the address, so
8437 the user knows which one it's talking about.
8438 - If you haven't used a clean circuit in an hour, throw it away,
8439 just to be on the safe side. (This means after 6 hours a totally
8440 unused Tor client will have no circuits open.)
8441 - Support "foo.nickname.exit" addresses, to let Alice request the
8442 address "foo" as viewed by exit node "nickname". Based on a patch
8444 - If your requested entry or exit node has advertised bandwidth 0,
8446 - Be more greedy about filling up relay cells -- we try reading again
8447 once we've processed the stuff we read, in case enough has arrived
8448 to fill the last cell completely.
8449 - Refuse application socks connections to port 0.
8450 - Use only 0.0.9pre1 and later servers for resolve cells.
8452 o Features (bandwidth):
8453 - Hibernation: New config option "AccountingMax" lets you
8454 set how many bytes per month (in each direction) you want to
8455 allow your server to consume. Rather than spreading those
8456 bytes out evenly over the month, we instead hibernate for some
8457 of the month and pop up at a deterministic time, work until
8458 the bytes are consumed, then hibernate again. Config option
8459 "MonthlyAccountingStart" lets you specify which day of the month
8460 your billing cycle starts on.
8461 - Implement weekly/monthly/daily accounting: now you specify your
8462 hibernation properties by
8463 AccountingMax N bytes|KB|MB|GB|TB
8464 AccountingStart day|week|month [day] HH:MM
8465 Defaults to "month 1 0:00".
8466 - Let bandwidth and interval config options be specified as 5 bytes,
8467 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8469 o Features (directories):
8470 - New "router-status" line in directory, to better bind each verified
8471 nickname to its identity key.
8472 - Clients can ask dirservers for /dir.z to get a compressed version
8473 of the directory. Only works for servers running 0.0.9, of course.
8474 - Make clients cache directories and use them to seed their router
8475 lists at startup. This means clients have a datadir again.
8476 - Respond to content-encoding headers by trying to uncompress as
8478 - Clients and servers now fetch running-routers; cache
8479 running-routers; compress running-routers; serve compressed
8481 - Make moria2 advertise a dirport of 80, so people behind firewalls
8482 will be able to get a directory.
8483 - Http proxy support
8484 - Dirservers translate requests for http://%s:%d/x to /x
8485 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8486 be routed through this host.
8487 - Clients ask for /tor/x rather than /x for new enough dirservers.
8488 This way we can one day coexist peacefully with apache.
8489 - Clients specify a "Host: %s%d" http header, to be compatible
8490 with more proxies, and so running squid on an exit node can work.
8491 - Protect dirservers from overzealous descriptor uploading -- wait
8492 10 seconds after directory gets dirty, before regenerating.
8494 o Features (packages and install):
8495 - Add NSI installer contributed by J Doe.
8496 - Apply NT service patch from Osamu Fujino. Still needs more work.
8497 - Commit VC6 and VC7 workspace/project files.
8498 - Commit a tor.spec for making RPM files, with help from jbash.
8499 - Add contrib/torctl.in contributed by Glenn Fink.
8500 - Make expand_filename handle ~ and ~username.
8501 - Use autoconf to enable largefile support where necessary. Use
8502 ftello where available, since ftell can fail at 2GB.
8503 - Ship src/win32/ in the tarball, so people can use it to build.
8504 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8507 o Features (ui controller):
8508 - Control interface: a separate program can now talk to your
8509 client/server over a socket, and get/set config options, receive
8510 notifications of circuits and streams starting/finishing/dying,
8511 bandwidth used, etc. The next step is to get some GUIs working.
8512 Let us know if you want to help out. See doc/control-spec.txt .
8513 - Ship a contrib/tor-control.py as an example script to interact
8514 with the control port.
8515 - "tor --hash-password zzyxz" will output a salted password for
8516 use in authenticating to the control interface.
8517 - Implement the control-spec's SAVECONF command, to write your
8518 configuration to torrc.
8519 - Get cookie authentication for the controller closer to working.
8520 - When set_conf changes our server descriptor, upload a new copy.
8521 But don't upload it too often if there are frequent changes.
8523 o Features (config and command-line):
8524 - Deprecate unofficial config option abbreviations, and abbreviations
8525 not on the command line.
8526 - Configuration infrastructure support for warning on obsolete
8528 - Give a slightly more useful output for "tor -h".
8529 - Break DirFetchPostPeriod into:
8530 - DirFetchPeriod for fetching full directory,
8531 - StatusFetchPeriod for fetching running-routers,
8532 - DirPostPeriod for posting server descriptor,
8533 - RendPostPeriod for posting hidden service descriptors.
8534 - New log format in config:
8535 "Log minsev[-maxsev] stdout|stderr|syslog" or
8536 "Log minsev[-maxsev] file /var/foo"
8537 - DirPolicy config option, to let people reject incoming addresses
8538 from their dirserver.
8539 - "tor --list-fingerprint" will list your identity key fingerprint
8541 - Make tor --version --version dump the cvs Id of every file.
8542 - New 'MyFamily nick1,...' config option for a server to
8543 specify other servers that shouldn't be used in the same circuit
8544 with it. Only believed if nick1 also specifies us.
8545 - New 'NodeFamily nick1,nick2,...' config option for a client to
8546 specify nodes that it doesn't want to use in the same circuit.
8547 - New 'Redirectexit pattern address:port' config option for a
8548 server to redirect exit connections, e.g. to a local squid.
8549 - Add "pass" target for RedirectExit, to make it easier to break
8550 out of a sequence of RedirectExit rules.
8551 - Make the dirservers file obsolete.
8552 - Include a dir-signing-key token in directories to tell the
8553 parsing entity which key is being used to sign.
8554 - Remove the built-in bulky default dirservers string.
8555 - New config option "Dirserver %s:%d [fingerprint]", which can be
8556 repeated as many times as needed. If no dirservers specified,
8557 default to moria1,moria2,tor26.
8558 - Make 'Routerfile' config option obsolete.
8559 - Discourage people from setting their dirfetchpostperiod more often
8560 than once per minute.
8563 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8564 get back to normal.)
8565 - Accept *:706 (silc) in default exit policy.
8566 - Implement new versioning format for post 0.1.
8567 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8568 log more informatively.
8569 - Check clock skew for verified servers, but allow unverified
8570 servers and clients to have any clock skew.
8571 - Make sure the hidden service descriptors are at a random offset
8572 from each other, to hinder linkability.
8573 - Clients now generate a TLS cert too, in preparation for having
8574 them act more like real nodes.
8575 - Add a pure-C tor-resolve implementation.
8576 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8577 1024) file descriptors.
8578 - Raise the max dns workers from 50 to 100.
8581 Changes in version 0.0.8.1 - 2004-10-13
8583 - Fix a seg fault that can be triggered remotely for Tor
8584 clients/servers with an open dirport.
8585 - Fix a rare assert trigger, where routerinfos for entries in
8586 our cpath would expire while we're building the path.
8587 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8588 - Fix a rare seg fault for people running hidden services on
8589 intermittent connections.
8590 - Fix a bug in parsing opt keywords with objects.
8591 - Fix a stale pointer assert bug when a stream detaches and
8593 - Fix a string format vulnerability (probably not exploitable)
8594 in reporting stats locally.
8595 - Fix an assert trigger: sometimes launching circuits can fail
8596 immediately, e.g. because too many circuits have failed recently.
8597 - Fix a compile warning on 64 bit platforms.
8600 Changes in version 0.0.8 - 2004-08-25
8602 - Made our unit tests compile again on OpenBSD 3.5, and tor
8603 itself compile again on OpenBSD on a sparc64.
8604 - We were neglecting milliseconds when logging on win32, so
8605 everything appeared to happen at the beginning of each second.
8606 - Check directory signature _before_ you decide whether you're
8607 you're running an obsolete version and should exit.
8608 - Check directory signature _before_ you parse the running-routers
8609 list to decide who's running.
8610 - Check return value of fclose while writing to disk, so we don't
8611 end up with broken files when servers run out of disk space.
8612 - Port it to SunOS 5.9 / Athena
8613 - Fix two bugs in saving onion keys to disk when rotating, so
8614 hopefully we'll get fewer people using old onion keys.
8615 - Remove our mostly unused -- and broken -- hex_encode()
8616 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8617 for pointing out this bug.)
8618 - Only pick and establish intro points after we've gotten a
8620 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8621 don't put it into the client dns cache.
8622 - If a begin failed due to exit policy, but we believe the IP
8623 address should have been allowed, switch that router to exitpolicy
8624 reject *:* until we get our next directory.
8627 - 'Extend' relay cell payloads now include the digest of the
8628 intended next hop's identity key. Now we can verify that we're
8629 extending to the right router, and also extend to routers we
8630 hadn't heard of before.
8633 - Tor nodes can now act as relays (with an advertised ORPort)
8634 without being manually verified by the dirserver operators.
8635 - Uploaded descriptors of unverified routers are now accepted
8636 by the dirservers, and included in the directory.
8637 - Verified routers are listed by nickname in the running-routers
8638 list; unverified routers are listed as "$<fingerprint>".
8639 - We now use hash-of-identity-key in most places rather than
8640 nickname or addr:port, for improved security/flexibility.
8641 - AllowUnverifiedNodes config option to let circuits choose no-name
8642 routers in entry,middle,exit,introduction,rendezvous positions.
8643 Allow middle and rendezvous positions by default.
8644 - When picking unverified routers, skip those with low uptime and/or
8645 low bandwidth, depending on what properties you care about.
8646 - ClientOnly option for nodes that never want to become servers.
8647 - Directory caching.
8648 - "AuthoritativeDir 1" option for the official dirservers.
8649 - Now other nodes (clients and servers) will cache the latest
8650 directory they've pulled down.
8651 - They can enable their DirPort to serve it to others.
8652 - Clients will pull down a directory from any node with an open
8653 DirPort, and check the signature/timestamp correctly.
8654 - Authoritative dirservers now fetch directories from other
8655 authdirservers, to stay better synced.
8656 - Running-routers list tells who's down also, along with noting
8657 if they're verified (listed by nickname) or unverified (listed
8659 - Allow dirservers to serve running-router list separately.
8660 This isn't used yet.
8661 - You can now fetch $DIRURL/running-routers to get just the
8662 running-routers line, not the whole descriptor list. (But
8663 clients don't use this yet.)
8664 - Clients choose nodes proportional to advertised bandwidth.
8665 - Clients avoid using nodes with low uptime as introduction points.
8666 - Handle servers with dynamic IP addresses: don't just replace
8667 options->Address with the resolved one at startup, and
8668 detect our address right before we make a routerinfo each time.
8669 - 'FascistFirewall' option to pick dirservers and ORs on specific
8670 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8671 which ports are open. (Defaults to 80,443)
8672 - Try other dirservers immediately if the one you try is down. This
8673 should tolerate down dirservers better now.
8674 - ORs connect-on-demand to other ORs
8675 - If you get an extend cell to an OR you're not connected to,
8676 connect, handshake, and forward the create cell.
8677 - The authoritative dirservers stay connected to everybody,
8678 and everybody stays connected to 0.0.7 servers, but otherwise
8679 clients/servers expire unused connections after 5 minutes.
8680 - When servers get a sigint, they delay 30 seconds (refusing new
8681 connections) then exit. A second sigint causes immediate exit.
8682 - File and name management:
8683 - Look for .torrc if no CONFDIR "torrc" is found.
8684 - If no datadir is defined, then choose, make, and secure ~/.tor
8686 - If torrc not found, exitpolicy reject *:*.
8687 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8688 - If no nickname is defined, derive default from hostname.
8689 - Rename secret key files, e.g. identity.key -> secret_id_key,
8690 to discourage people from mailing their identity key to tor-ops.
8691 - Refuse to build a circuit before the directory has arrived --
8692 it won't work anyway, since you won't know the right onion keys
8694 - Parse tor version numbers so we can do an is-newer-than check
8695 rather than an is-in-the-list check.
8696 - New socks command 'resolve', to let us shim gethostbyname()
8698 - A 'tor_resolve' script to access the socks resolve functionality.
8699 - A new socks-extensions.txt doc file to describe our
8700 interpretation and extensions to the socks protocols.
8701 - Add a ContactInfo option, which gets published in descriptor.
8702 - Write tor version at the top of each log file
8703 - New docs in the tarball:
8705 - Document that you should proxy your SSL traffic too.
8706 - Log a warning if the user uses an unsafe socks variant, so people
8707 are more likely to learn about privoxy or socat.
8708 - Log a warning if you're running an unverified server, to let you
8709 know you might want to get it verified.
8710 - Change the default exit policy to reject the default edonkey,
8711 kazaa, gnutella ports.
8712 - Add replace_file() to util.[ch] to handle win32's rename().
8713 - Publish OR uptime in descriptor (and thus in directory) too.
8714 - Remember used bandwidth (both in and out), and publish 15-minute
8715 snapshots for the past day into our descriptor.
8716 - Be more aggressive about trying to make circuits when the network
8717 has changed (e.g. when you unsuspend your laptop).
8718 - Check for time skew on http headers; report date in response to
8720 - If the entrynode config line has only one node, don't pick it as
8722 - Add strict{entry|exit}nodes config options. If set to 1, then
8723 we refuse to build circuits that don't include the specified entry
8725 - OutboundBindAddress config option, to bind to a specific
8726 IP address for outgoing connect()s.
8727 - End truncated log entries (e.g. directories) with "[truncated]".
8730 Changes in version 0.0.7.3 - 2004-08-12
8731 o Stop dnsworkers from triggering an assert failure when you
8732 ask them to resolve the host "".
8735 Changes in version 0.0.7.2 - 2004-07-07
8736 o A better fix for the 0.0.0.0 problem, that will hopefully
8737 eliminate the remaining related assertion failures.
8740 Changes in version 0.0.7.1 - 2004-07-04
8741 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8742 since internally we use 0.0.0.0 to signify "not yet resolved".
8745 Changes in version 0.0.7 - 2004-06-07
8746 o Fixes for crashes and other obnoxious bugs:
8747 - Fix an epipe bug: sometimes when directory connections failed
8748 to connect, we would give them a chance to flush before closing
8750 - When we detached from a circuit because of resolvefailed, we
8751 would immediately try the same circuit twice more, and then
8752 give up on the resolve thinking we'd tried three different
8754 - Limit the number of intro circuits we'll attempt to build for a
8755 hidden service per 15-minute period.
8756 - Check recommended-software string *early*, before actually parsing
8757 the directory. Thus we can detect an obsolete version and exit,
8758 even if the new directory format doesn't parse.
8759 o Fixes for security bugs:
8760 - Remember which nodes are dirservers when you startup, and if a
8761 random OR enables his dirport, don't automatically assume he's
8762 a trusted dirserver.
8764 - Directory connections were asking the wrong poll socket to
8765 start writing, and not asking themselves to start writing.
8766 - When we detached from a circuit because we sent a begin but
8767 didn't get a connected, we would use it again the first time;
8768 but after that we would correctly switch to a different one.
8769 - Stop warning when the first onion decrypt attempt fails; they
8770 will sometimes legitimately fail now that we rotate keys.
8771 - Override unaligned-access-ok check when $host_cpu is ia64 or
8772 arm. Apparently they allow it but the kernel whines.
8773 - Dirservers try to reconnect periodically too, in case connections
8775 - Fix some memory leaks in directory servers.
8776 - Allow backslash in Win32 filenames.
8777 - Made Tor build complain-free on FreeBSD, hopefully without
8778 breaking other BSD builds. We'll see.
8779 - Check directory signatures based on name of signer, not on whom
8780 we got the directory from. This will let us cache directories more
8782 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8785 - Doxygen markup on all functions and global variables.
8786 - Make directory functions update routerlist, not replace it. So
8787 now directory disagreements are not so critical a problem.
8788 - Remove the upper limit on number of descriptors in a dirserver's
8789 directory (not that we were anywhere close).
8790 - Allow multiple logfiles at different severity ranges.
8791 - Allow *BindAddress to specify ":port" rather than setting *Port
8792 separately. Allow multiple instances of each BindAddress config
8793 option, so you can bind to multiple interfaces if you want.
8794 - Allow multiple exit policy lines, which are processed in order.
8795 Now we don't need that huge line with all the commas in it.
8796 - Enable accept/reject policies on SOCKS connections, so you can bind
8797 to 0.0.0.0 but still control who can use your OP.
8798 - Updated the man page to reflect these features.
8801 Changes in version 0.0.6.2 - 2004-05-16
8802 o Our integrity-checking digest was checking only the most recent cell,
8803 not the previous cells like we'd thought.
8804 Thanks to Stefan Mark for finding the flaw!
8807 Changes in version 0.0.6.1 - 2004-05-06
8808 o Fix two bugs in our AES counter-mode implementation (this affected
8809 onion-level stream encryption, but not TLS-level). It turns
8810 out we were doing something much more akin to a 16-character
8811 polyalphabetic cipher. Oops.
8812 Thanks to Stefan Mark for finding the flaw!
8813 o Retire moria3 as a directory server, and add tor26 as a directory
8817 Changes in version 0.0.6 - 2004-05-02
8819 - Hidden services and rendezvous points are implemented. Go to
8820 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8821 hidden services. (This only works via a socks4a proxy such as
8822 Privoxy, and currently it's quite slow.)
8823 - We now rotate link (tls context) keys and onion keys.
8824 - CREATE cells now include oaep padding, so you can tell
8825 if you decrypted them correctly.
8826 - Retry stream correctly when we fail to connect because of
8827 exit-policy-reject (should try another) or can't-resolve-address.
8828 - When we hup a dirserver and we've *removed* a server from the
8829 approved-routers list, now we remove that server from the
8830 in-memory directories too.
8831 - Add bandwidthburst to server descriptor.
8832 - Directories now say which dirserver signed them.
8833 - Use a tor_assert macro that logs failed assertions too.
8834 - Since we don't support truncateds much, don't bother sending them;
8835 just close the circ.
8836 - Fetch randomness from /dev/urandom better (not via fopen/fread)
8837 - Better debugging for tls errors
8838 - Set Content-Type on the directory and hidserv descriptor.
8839 - Remove IVs from cipher code, since AES-ctr has none.
8841 - Fix an assert trigger for exit nodes that's been plaguing us since
8842 the days of 0.0.2prexx (thanks weasel!)
8843 - Fix a bug where we were closing tls connections intermittently.
8844 It turns out openssl keeps its errors around -- so if an error
8845 happens, and you don't ask about it, and then another openssl
8846 operation happens and succeeds, and you ask if there was an error,
8847 it tells you about the first error.
8848 - Fix a bug that's been lurking since 27 may 03 (!)
8849 When passing back a destroy cell, we would use the wrong circ id.
8850 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
8851 - Some versions of openssl have an SSL_pending function that erroneously
8852 returns bytes when there is a non-application record pending.
8853 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8854 o We were using an array of length zero in a few places.
8855 o Win32's gethostbyname can't resolve an IP to an IP.
8856 o Win32's close can't close a socket.
8857 o Handle windows socket errors correctly.
8859 - check for <sys/limits.h> so we build on FreeBSD again, and
8860 <machine/limits.h> for NetBSD.
8863 Changes in version 0.0.5 - 2004-03-30
8864 o Install torrc as torrc.sample -- we no longer clobber your
8866 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8867 o Only build circuits after we've fetched the directory: clients were
8868 using only the directory servers before they'd fetched a directory.
8869 This also means longer startup time; so it goes.
8870 o Fix an assert trigger where an OP would fail to handshake, and we'd
8871 expect it to have a nickname.
8872 o Work around a tsocks bug: do a socks reject when AP connection dies
8873 early, else tsocks goes into an infinite loop.
8874 o Hold socks connection open until reply is flushed (if possible)
8875 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8876 the dns farm to do it.
8877 o Fix c99 aliasing warnings in rephist.c
8878 o Don't include server descriptors that are older than 24 hours in the
8880 o Give socks 'reject' replies their whole 15s to attempt to flush,
8881 rather than seeing the 60s timeout and assuming the flush had failed.
8882 o Clean automake droppings from the cvs repository
8883 o Add in a 'notice' log level for things the operator should hear
8884 but that aren't warnings
8887 Changes in version 0.0.4 - 2004-03-26
8888 o When connecting to a dirserver or OR and the network is down,
8892 Changes in version 0.0.3 - 2004-03-26
8893 o Warn and fail if server chose a nickname with illegal characters
8894 o Port to Solaris and Sparc:
8895 - include missing header fcntl.h
8896 - have autoconf find -lsocket -lnsl automatically
8897 - deal with hardware word alignment
8898 - make uname() work (solaris has a different return convention)
8899 - switch from using signal() to sigaction()
8900 o Preliminary work on reputation system:
8901 - Keep statistics on success/fail of connect attempts; they're published
8902 by kill -USR1 currently.
8903 - Add a RunTesting option to try to learn link state by creating test
8904 circuits, even when SocksPort is off.
8905 - Remove unused open circuits when there are too many.
8908 Changes in version 0.0.2 - 2004-03-19
8909 - Include strlcpy and strlcat for safer string ops
8910 - define INADDR_NONE so we compile (but still not run) on solaris
8913 Changes in version 0.0.2pre27 - 2004-03-14
8915 - Allow internal tor networks (we were rejecting internal IPs,
8916 now we allow them if they're set explicitly).
8917 - And fix a few endian issues.
8920 Changes in version 0.0.2pre26 - 2004-03-14
8922 - If a stream times out after 15s without a connected cell, don't
8923 try that circuit again: try a new one.
8924 - Retry streams at most 4 times. Then give up.
8925 - When a dirserver gets a descriptor from an unknown router, it
8926 logs its fingerprint (so the dirserver operator can choose to
8927 accept it even without mail from the server operator).
8928 - Inform unapproved servers when we reject their descriptors.
8929 - Make tor build on Windows again. It works as a client, who knows
8931 - Clearer instructions in the torrc for how to set up a server.
8932 - Be more efficient about reading fd's when our global token bucket
8933 (used for rate limiting) becomes empty.
8935 - Stop asserting that computers always go forward in time. It's
8937 - When we sent a cell (e.g. destroy) and then marked an OR connection
8938 expired, we might close it before finishing a flush if the other
8939 side isn't reading right then.
8940 - Don't allow dirservers to start if they haven't defined
8942 - We were caching transient dns failures. Oops.
8943 - Prevent servers from publishing an internal IP as their address.
8944 - Address a strcat vulnerability in circuit.c
8947 Changes in version 0.0.2pre25 - 2004-03-04
8949 - Put the OR's IP in its router descriptor, not its fqdn. That way
8950 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8953 - If the user typed in an address that didn't resolve, the server
8957 Changes in version 0.0.2pre24 - 2004-03-03
8959 - Fix an assertion failure in dns.c, where we were trying to dequeue
8960 a pending dns resolve even if it wasn't pending
8961 - Fix a spurious socks5 warning about still trying to write after the
8962 connection is finished.
8963 - Hold certain marked_for_close connections open until they're finished
8964 flushing, rather than losing bytes by closing them too early.
8965 - Correctly report the reason for ending a stream
8966 - Remove some duplicate calls to connection_mark_for_close
8967 - Put switch_id and start_daemon earlier in the boot sequence, so it
8968 will actually try to chdir() to options.DataDirectory
8969 - Make 'make test' exit(1) if a test fails; fix some unit tests
8970 - Make tor fail when you use a config option it doesn't know about,
8971 rather than warn and continue.
8972 - Make --version work
8973 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8976 Changes in version 0.0.2pre23 - 2004-02-29
8978 - Print a statement when the first circ is finished, so the user
8980 - If a relay cell is unrecognized at the end of the circuit,
8981 send back a destroy. (So attacks to mutate cells are more
8983 - New config option 'excludenodes' to avoid certain nodes for circuits.
8984 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8985 so you can collect coredumps there.
8987 - Fix a bug in tls flushing where sometimes data got wedged and
8988 didn't flush until more data got sent. Hopefully this bug was
8989 a big factor in the random delays we were seeing.
8990 - Make 'connected' cells include the resolved IP, so the client
8991 dns cache actually gets populated.
8992 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8993 - When we time-out on a stream and detach from the circuit, send an
8994 end cell down it first.
8995 - Only warn about an unknown router (in exitnodes, entrynodes,
8996 excludenodes) after we've fetched a directory.
8999 Changes in version 0.0.2pre22 - 2004-02-26
9001 - Servers publish less revealing uname information in descriptors.
9002 - More memory tracking and assertions, to crash more usefully when
9004 - If the default torrc isn't there, just use some default defaults.
9005 Plus provide an internal dirservers file if they don't have one.
9006 - When the user tries to use Tor as an http proxy, give them an http
9007 501 failure explaining that we're a socks proxy.
9008 - Dump a new router.desc on hup, to help confused people who change
9009 their exit policies and then wonder why router.desc doesn't reflect
9011 - Clean up the generic tor.sh init script that we ship with.
9013 - If the exit stream is pending on the resolve, and a destroy arrives,
9014 then the stream wasn't getting removed from the pending list. I
9015 think this was the one causing recent server crashes.
9016 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9017 - When it couldn't resolve any dirservers, it was useless from then on.
9018 Now it reloads the RouterFile (or default dirservers) if it has no
9020 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9021 many users don't even *have* a /usr/local/sbin/.
9024 Changes in version 0.0.2pre21 - 2004-02-18
9026 - There's a ChangeLog file that actually reflects the changelog.
9027 - There's a 'torify' wrapper script, with an accompanying
9028 tor-tsocks.conf, that simplifies the process of using tsocks for
9029 tor. It even has a man page.
9030 - The tor binary gets installed to sbin rather than bin now.
9031 - Retry streams where the connected cell hasn't arrived in 15 seconds
9032 - Clean up exit policy handling -- get the default out of the torrc,
9033 so we can update it without forcing each server operator to fix
9035 - Allow imaps and pop3s in default exit policy
9037 - Prevent picking middleman nodes as the last node in the circuit
9040 Changes in version 0.0.2pre20 - 2004-01-30
9042 - We now have a deb package, and it's in debian unstable. Go to
9044 - I've split the TotalBandwidth option into BandwidthRate (how many
9045 bytes per second you want to allow, long-term) and
9046 BandwidthBurst (how many bytes you will allow at once before the cap
9047 kicks in). This better token bucket approach lets you, say, set
9048 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9049 performance while not exceeding your monthly bandwidth quota.
9050 - Push out a tls record's worth of data once you've got it, rather
9051 than waiting until you've read everything waiting to be read. This
9052 may improve performance by pipelining better. We'll see.
9053 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9054 from failed circuits (if they haven't been connected yet) and attach
9056 - Expire old streams that haven't managed to connect. Some day we'll
9057 have them reattach to new circuits instead.
9060 - Fix several memory leaks that were causing servers to become bloated
9062 - Fix a few very rare assert triggers. A few more remain.
9063 - Setuid to User _before_ complaining about running as root.
9066 Changes in version 0.0.2pre19 - 2004-01-07
9068 - Fix deadlock condition in dns farm. We were telling a child to die by
9069 closing the parent's file descriptor to him. But newer children were
9070 inheriting the open file descriptor from the parent, and since they
9071 weren't closing it, the socket never closed, so the child never read
9072 eof, so he never knew to exit. Similarly, dns workers were holding
9073 open other sockets, leading to all sorts of chaos.
9074 - New cleaner daemon() code for forking and backgrounding.
9075 - If you log to a file, it now prints an entry at the top of the
9076 logfile so you know it's working.
9077 - The onionskin challenge length was 30 bytes longer than necessary.
9078 - Started to patch up the spec so it's not quite so out of date.
9081 Changes in version 0.0.2pre18 - 2004-01-02
9083 - Fix endian issues with the 'integrity' field in the relay header.
9084 - Fix a potential bug where connections in state
9085 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9088 Changes in version 0.0.2pre17 - 2003-12-30
9090 - Made --debuglogfile (or any second log file, actually) work.
9091 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9092 adversary could force us into an infinite loop.
9095 - Each onionskin handshake now includes a hash of the computed key,
9096 to prove the server's identity and help perfect forward secrecy.
9097 - Changed cell size from 256 to 512 bytes (working toward compatibility
9099 - Changed cell length to 2 bytes, and moved it to the relay header.
9100 - Implemented end-to-end integrity checking for the payloads of
9102 - Separated streamid from 'recognized' (otherwise circuits will get
9103 messed up when we try to have streams exit from the middle). We
9104 use the integrity-checking to confirm that a cell is addressed to
9106 - Randomize the initial circid and streamid values, so an adversary who
9107 breaks into a node can't learn how many circuits or streams have
9111 Changes in version 0.0.2pre16 - 2003-12-14
9113 - Fixed a bug that made HUP trigger an assert
9114 - Fixed a bug where a circuit that immediately failed wasn't being
9115 counted as a failed circuit in counting retries.
9118 - Now we close the circuit when we get a truncated cell: otherwise we're
9119 open to an anonymity attack where a bad node in the path truncates
9120 the circuit and then we open streams at him.
9121 - Add port ranges to exit policies
9122 - Add a conservative default exit policy
9123 - Warn if you're running tor as root
9124 - on HUP, retry OR connections and close/rebind listeners
9125 - options.EntryNodes: try these nodes first when picking the first node
9126 - options.ExitNodes: if your best choices happen to include any of
9127 your preferred exit nodes, you choose among just those preferred
9129 - options.ExcludedNodes: nodes that are never picked in path building
9132 Changes in version 0.0.2pre15 - 2003-12-03
9133 o Robustness and bugfixes:
9134 - Sometimes clients would cache incorrect DNS resolves, which would
9135 really screw things up.
9136 - An OP that goes offline would slowly leak all its sockets and stop
9138 - A wide variety of bugfixes in exit node selection, exit policy
9139 handling, and processing pending streams when a new circuit is
9141 - Pick nodes for a path only from those the directory says are up
9142 - Choose randomly from all running dirservers, not always the first one
9143 - Increase allowed http header size for directory fetch.
9144 - Stop writing to stderr (if we're daemonized it will be closed).
9145 - Enable -g always, so cores will be more useful to me.
9146 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9149 - Wrote a man page. It lists commonly used options.
9152 - Change default loglevel to warn.
9153 - Make PidFile default to null rather than littering in your CWD.
9154 - OnionRouter config option is now obsolete. Instead it just checks
9156 - Moved to a single unified torrc file for both clients and servers.
9159 Changes in version 0.0.2pre14 - 2003-11-29
9160 o Robustness and bugfixes:
9161 - Force the admin to make the DataDirectory himself
9162 - to get ownership/permissions right
9163 - so clients no longer make a DataDirectory and then never use it
9164 - fix bug where a client who was offline for 45 minutes would never
9165 pull down a directory again
9166 - fix (or at least hide really well) the dns assert bug that was
9167 causing server crashes
9168 - warnings and improved robustness wrt clockskew for certs
9169 - use the native daemon(3) to daemonize, when available
9170 - exit if bind() fails
9171 - exit if neither socksport nor orport is defined
9172 - include our own tor_timegm (Win32 doesn't have its own)
9173 - bugfix for win32 with lots of connections
9174 - fix minor bias in PRNG
9175 - make dirserver more robust to corrupt cached directory
9178 - Wrote the design document (woo)
9180 o Circuit building and exit policies:
9181 - Circuits no longer try to use nodes that the directory has told them
9183 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9184 bitcounts (18.0.0.0/8).
9185 - Make AP connections standby for a circuit if no suitable circuit
9186 exists, rather than failing
9187 - Circuits choose exit node based on addr/port, exit policies, and
9188 which AP connections are standing by
9189 - Bump min pathlen from 2 to 3
9190 - Relay end cells have a payload to describe why the stream ended.
9191 - If the stream failed because of exit policy, try again with a new
9193 - Clients have a dns cache to remember resolved addresses.
9194 - Notice more quickly when we have no working circuits
9197 - APPort is now called SocksPort
9198 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9200 - RecommendedVersions is now a config variable rather than
9201 hardcoded (for dirservers)
9202 - Reloads config on HUP
9203 - Usage info on -h or --help
9204 - If you set User and Group config vars, it'll setu/gid to them.
9206 Changes in version 0.0.2pre13 - 2003-10-19
9207 o General stability:
9208 - SSL_write no longer fails when it returns WANTWRITE and the number
9209 of bytes in the buf has changed by the next SSL_write call.
9210 - Fix segfault fetching directory when network is down
9211 - Fix a variety of minor memory leaks
9212 - Dirservers reload the fingerprints file on HUP, so I don't have
9213 to take down the network when I approve a new router
9214 - Default server config file has explicit Address line to specify fqdn
9217 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9218 - Make listener connections not ever alloc bufs
9220 o Autoconf improvements:
9221 - don't clobber an external CFLAGS in ./configure
9222 - Make install now works
9223 - create var/lib/tor on make install
9224 - autocreate a tor.sh initscript to help distribs
9225 - autocreate the torrc and sample-server-torrc with correct paths
9227 o Log files and Daemonizing now work:
9228 - If --DebugLogFile is specified, log to it at -l debug
9229 - If --LogFile is specified, use it instead of commandline
9230 - If --RunAsDaemon is set, tor forks and backgrounds on startup