1 Changes in version 0.2.4.12-alpha - 2013-04-18
3 - Raise the default time that a client keeps an entry guard from
4 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5 2012 paper. (We would make it even longer, but we need better client
6 load balancing first.) Also, make the guard lifetime controllable
7 via a new GuardLifetime torrc option and a GuardLifetime consensus
8 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9 - Directory authorities now prefer using measured bandwidths to
10 advertised ones when computing flags and thresholds. Resolves
12 - Directory authorities that have more than a threshold number
13 of relays with measured bandwidths now treat relays with unmeasured
14 bandwidths as having bandwidth 0. Resolves ticket 8435.
16 o Major bugfixes (assert / resource use):
17 - Avoid a bug where our response to TLS renegotation under certain
18 network conditions could lead to a busy-loop, with 100% CPU
19 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
20 - Avoid an assertion when we discover that we'd like to write a cell
21 onto a closing connection: just discard the cell. Fixes another
22 case of bug 7350; bugfix on 0.2.4.4-alpha.
24 o Major bugfixes (client-side privacy):
25 - When we mark a circuit as unusable for new circuits, have it
26 continue to be unusable for new circuits even if MaxCircuitDirtiness
27 is increased too much at the wrong time, or the system clock jumps
28 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
29 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
30 which have resolved to internal addresses") is set, apply that
31 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
32 - When an exit relay rejects a stream with reason "exit policy", but
33 we only know an exit policy summary (e.g. from the microdesc
34 consensus) for it, do not mark the relay as useless for all exiting.
35 Instead, mark just the circuit as unsuitable for that particular
36 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
37 - Allow applications to get proper stream isolation with
38 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
39 username/password authentication also offer "no authentication". Tor
40 had previously preferred "no authentication", so the applications
41 never actually sent Tor their auth details. Now Tor selects
42 username/password authentication if it's offered. You can disable
43 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
44 bug 8117; bugfix on 0.2.3.3-alpha.
46 o Major bugfixes (other):
47 - When unable to find any working directory nodes to use as a
48 directory guard, give up rather than adding the same non-working
49 nodes to the directory guard list over and over. Fixes bug 8231;
50 bugfix on 0.2.4.8-alpha.
53 - Reject as invalid most directory objects containing a NUL.
54 Belt-and-suspender fix for bug 8037.
55 - In our testsuite, create temporary directories with a bit more
56 entropy in their name to make name collisions less likely. Fixes
58 - Add CACHED keyword to ADDRMAP events in the control protocol
59 to indicate whether a DNS result will be cached or not. Resolves
61 - Eliminate several instances where we use "Nickname=ID" to refer to
62 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
63 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
64 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
65 - Update to the April 3 2013 Maxmind GeoLite Country database.
67 o Minor features (build):
68 - Detect and reject attempts to build Tor with threading support
69 when OpenSSL has been compiled without threading support.
71 - Clarify that when autoconf is checking for nacl, it is checking
72 specifically for nacl with a fast curve25519 implementation.
74 - Warn if building on a platform with an unsigned time_t: there
75 are too many places where Tor currently assumes that time_t can
76 hold negative values. We'd like to fix them all, but probably
79 o Minor bugfixes (build):
80 - Fix compilation warning with some versions of clang that would
81 prefer the -Wswitch-enum compiler flag to warn about switch
82 statements with missing enum values, even if those switch
83 statements have a "default:" statement. Fixes bug 8598; bugfix
85 - Build Tor correctly on 32-bit platforms where the compiler can build
86 but not run code using the "uint128_t" construction. Fixes bug 8587;
87 bugfix on 0.2.4.8-alpha.
88 - Add the old src/or/micro-revision.i filename to CLEANFILES.
89 On the off chance that somebody has one, it will go away as soon
90 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
91 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
92 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
93 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
95 o Minor bugfixes (protocol):
96 - Fix the handling of a TRUNCATE cell when it arrives while the
97 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
98 - Fix a misframing issue when reading the version numbers in a
99 VERSIONS cell. Previously we would recognize [00 01 00 02] as
100 'version 1, version 2, and version 0x100', when it should have
101 only included versions 1 and 2. Fixes bug 8059; bugfix on
102 0.2.0.10-alpha. Reported pseudonymously.
103 - Make the format and order of STREAM events for DNS lookups
104 consistent among the various ways to launch DNS lookups. Fixes
105 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
106 - Correct our check for which versions of Tor support the EXTEND2
107 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
108 later, when support was really added in version 0.2.4.8-alpha.
109 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
111 o Minor bugfixes (correctness):
112 - Correctly store microdescriptors and extrainfo descriptors with
113 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
114 Bug reported by "cypherpunks".
115 - Increase the width of the field used to remember a connection's
116 link protocol version to two bytes. Harmless for now, since the
117 only currently recognized versions are one byte long. Reported
118 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
119 - If the state file's path bias counts are invalid (presumably from a
120 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
121 additional checks and log messages to the scaling of Path Bias
122 counts, in case there still are remaining issues with scaling.
123 Should help resolve bug 8235.
125 o Minor bugfixes (syscalls):
126 - Always check the return values of functions fcntl() and
127 setsockopt(). We don't believe these are ever actually failing in
128 practice, but better safe than sorry. Also, checking these return
129 values should please analysis tools like Coverity. Patch from
130 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
131 - Use direct writes rather than stdio when building microdescriptor
132 caches, in an attempt to mitigate bug 8031, or at least make it
135 o Minor bugfixes (config):
136 - When rejecting a configuration because we were unable to parse a
137 quoted string, log an actual error message. Fix for bug 7950;
138 bugfix on 0.2.0.16-alpha.
139 - Behave correctly when the user disables LearnCircuitBuildTimeout
140 but doesn't tell us what they would like the timeout to be. Fixes
141 bug 6304; bugfix on 0.2.2.14-alpha.
142 - When autodetecting the number of CPUs, use the number of available
143 CPUs in preference to the number of configured CPUs. Inform the
144 user if this reduces the number of available CPUs. Fixes bug 8002.
145 Bugfix on 0.2.3.1-alpha.
146 - Elevate the severity of the warning message when setting
147 EntryNodes but disabling UseGuardNodes to an error. The outcome
148 of letting Tor proceed with those options enabled (which causes
149 EntryNodes to get ignored) is sufficiently different from what
150 was expected that it's best to just refuse to proceed. Fixes bug
151 8180; bugfix on 0.2.3.11-alpha.
152 - Allow TestingTorNetworks to override the 4096-byte minimum for
153 the Fast threshold. Otherwise they can't bootstrap until they've
154 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
155 - Fix some logic errors when the user manually overrides the
156 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
159 o Minor bugfixes (log messages to help diagnose bugs):
160 - If we fail to free a microdescriptor because of bug 7164, log
161 the filename and line number from which we tried to free it.
162 This should help us finally fix bug 7164.
163 - Add another diagnostic to the heartbeat message: track and log
164 overhead that TLS is adding to the data we write. If this is
165 high, we are sending too little data to SSL_write at a time.
166 Diagnostic for bug 7707.
167 - Add more detail to a log message about relaxed timeouts. Hopefully
168 this additional detail will allow us to diagnose the cause of
170 - Warn more aggressively when flushing microdescriptors to a
171 microdescriptor cache fails, in an attempt to mitigate bug 8031,
172 or at least make it more diagnosable.
173 - Improve debugging output to attempt to diagnose the underlying
175 - Log the purpose of a path-bias testing circuit correctly.
176 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
178 o Minor bugfixes (0.2.4.x log messages that were too noisy):
179 - Use circuit creation time for network liveness evaluation. This
180 should eliminate warning log messages about liveness caused
181 by changes in timeout evaluation. Fixes bug 6572; bugfix on
183 - Reduce a path bias length check notice log to info. The notice
184 is triggered when creating controller circuits. Fixes bug 8196;
185 bugfix on 0.2.4.8-alpha.
186 - Fix a path state issue that triggered a notice during relay startup.
187 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
188 - Reduce occurrences of warns about circuit purpose in
189 connection_ap_expire_building(). Fixes bug 8477; bugfix on
192 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
193 - If we encounter a write failure on a SOCKS connection before we
194 finish our SOCKS handshake, don't warn that we closed the
195 connection before we could send a SOCKS reply. Fixes bug 8427;
196 bugfix on 0.1.0.1-rc.
197 - Correctly recognize that [::1] is a loopback address. Fixes
198 bug 8377; bugfix on 0.2.1.3-alpha.
199 - Fix a directory authority warn caused when we have a large amount
200 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
201 - Don't attempt to relax the timeout of already opened 1-hop circuits.
202 They might never timeout. This should eliminate some/all cases of
203 the relaxed timeout log message.
204 - Don't log inappropriate heartbeat messages when hibernating: a
205 hibernating node is _expected_ to drop out of the consensus,
206 decide it isn't bootstrapped, and so forth. Fixes bug
207 7302; bugfix on 0.2.3.1-alpha.
208 - Don't complain about bootstrapping problems while hibernating.
209 These complaints reflect a general code problem, but not one
210 with any problematic effects. (No connections are actually
211 opened.) Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
213 o Documentation fixes:
214 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
215 names match. Fixes bug 7768.
216 - Make the torify manpage no longer refer to tsocks; torify hasn't
217 supported tsocks since 0.2.3.14-alpha.
218 - Make the tor manpage no longer reference tsocks.
219 - Fix the GeoIPExcludeUnknown documentation to refer to
220 ExcludeExitNodes rather than the currently nonexistent
221 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
224 - The tor-tsocks.conf is no longer distributed or installed. We
225 recommend that tsocks users use torsocks instead. Resolves
229 Changes in version 0.2.4.11-alpha - 2013-03-11
230 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
231 more robust, makes hidden service authentication work again, and
232 resolves a DPI fingerprint for Tor's SSL transport.
234 o Major features (directory authorities):
235 - Directory authorities now support a new consensus method (17)
236 where they cap the published bandwidth of servers for which
237 insufficient bandwidth measurements exist. Fixes part of bug 2286.
238 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
239 serve any v2 directory information. Now we can test disabling the
240 old deprecated v2 directory format, and see whether doing so has
241 any effect on network load. Begins to fix bug 6783.
242 - Directory authorities now include inside each vote a statement of
243 the performance thresholds they used when assigning flags.
244 Implements ticket 8151.
246 o Major bugfixes (directory authorities):
247 - Stop marking every relay as having been down for one hour every
248 time we restart a directory authority. These artificial downtimes
249 were messing with our Stable and Guard flag calculations. Fixes
250 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
252 o Major bugfixes (hidden services):
253 - Allow hidden service authentication to succeed again. When we
254 refactored the hidden service introduction code back
255 in 0.2.4.1-alpha, we didn't update the code that checks
256 whether authentication information is present, causing all
257 authentication checks to return "false". Fix for bug 8207; bugfix
258 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
260 o Minor features (relays, bridges):
261 - Make bridge relays check once a minute for whether their IP
262 address has changed, rather than only every 15 minutes. Resolves
264 - Refactor resolve_my_address() so it returns the method by which we
265 decided our public IP address (explicitly configured, resolved from
266 explicit hostname, guessed from interfaces, learned by gethostname).
267 Now we can provide more helpful log messages when a relay guesses
268 its IP address incorrectly (e.g. due to unexpected lines in
269 /etc/hosts). Resolves ticket 2267.
270 - Teach bridge-using clients to avoid 0.2.2 bridges when making
271 microdescriptor-related dir requests, and only fall back to normal
272 descriptors if none of their bridges can handle microdescriptors
273 (as opposed to the fix in ticket 4013, which caused them to fall
274 back to normal descriptors if *any* of their bridges preferred
275 them). Resolves ticket 4994.
276 - Randomize the lifetime of our SSL link certificate, so censors can't
277 use the static value for filtering Tor flows. Resolves ticket 8443;
278 related to ticket 4014 which was included in 0.2.2.33.
280 o Minor features (portability):
281 - Tweak the curve25519-donna*.c implementations to tolerate systems
282 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
283 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
284 the signs of types during autoconf. This is better than our old
285 approach, which didn't work when cross-compiling.
286 - Detect the sign of enum values, rather than assuming that MSC is the
287 only compiler where enum types are all signed. Fixes bug 7727;
288 bugfix on 0.2.4.10-alpha.
290 o Minor features (other):
291 - Say "KBytes" rather than "KB" in the man page (for various values
292 of K), to further reduce confusion about whether Tor counts in
293 units of memory or fractions of units of memory. Resolves ticket 7054.
294 - Clear the high bit on curve25519 public keys before passing them to
295 our backend, in case we ever wind up using a backend that doesn't do
296 so itself. If we used such a backend, and *didn't* clear the high bit,
297 we could wind up in a situation where users with such backends would
298 be distinguishable from users without. Fixes bug 8121; bugfix on
300 - Update to the March 6 2013 Maxmind GeoLite Country database.
302 o Minor bugfixes (clients):
303 - When we receive a RELAY_END cell with the reason DONE, or with no
304 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
305 status as "connection refused". Previously we reported these cases
306 as success but then immediately closed the connection. Fixes bug
307 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
308 - Downgrade an assertion in connection_ap_expire_beginning to an
309 LD_BUG message. The fix for bug 8024 should prevent this message
310 from displaying, but just in case, a warn that we can diagnose
311 is better than more assert crashes. Fixes bug 8065; bugfix on
313 - Lower path use bias thresholds to .80 for notice and .60 for warn.
314 Also make the rate limiting flags for the path use bias log messages
315 independent from the original path bias flags. Fixes bug 8161;
316 bugfix on 0.2.4.10-alpha.
318 o Minor bugfixes (relays):
319 - Stop trying to resolve our hostname so often (e.g. every time we
320 think about doing a directory fetch). Now we reuse the cached
321 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
322 and 2410 (bugfix on 0.1.2.2-alpha).
323 - Stop sending a stray "(null)" in some cases for the server status
324 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
326 - When choosing which stream on a formerly stalled circuit to wake
327 first, make better use of the platform's weak RNG. Previously,
328 we had been using the % ("modulo") operator to try to generate a
329 1/N chance of picking each stream, but this behaves badly with
330 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
332 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
333 Irix's random() only return 15 bits; Solaris's random() returns more
334 bits but its RAND_MAX says it only returns 15, and so on. Motivated
335 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
337 o Minor bugfixes (directory authorities):
338 - Directory authorities now use less space when formatting identical
339 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
342 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
343 - Avoid leaking memory if we fail to compute a consensus signature
344 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
345 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
347 - Fix a memory leak during safe-cookie controller authentication.
348 Bugfix on 0.2.3.13-alpha.
349 - Avoid memory leak of IPv6 policy content if we fail to format it into
350 a router descriptor. Bugfix on 0.2.4.7-alpha.
352 o Minor bugfixes (other code correctness issues):
353 - Avoid a crash if we fail to generate an extrainfo descriptor.
354 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
356 - When detecting the largest possible file descriptor (in order to
357 close all file descriptors when launching a new program), actually
358 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
359 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
361 - Fix a copy-and-paste error when adding a missing A1 to a routerset
362 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
363 Bugfix on 0.2.4.10-alpha.
364 - Fix an impossible-to-trigger integer overflow when estimating how
365 long our onionskin queue would take. (This overflow would require us
366 to accept 4 million onionskins before processing 100 of them.) Fixes
367 bug 8210; bugfix on 0.2.4.10-alpha.
369 o Code simplification and refactoring:
370 - Add a wrapper function for the common "log a message with a
374 Changes in version 0.2.4.10-alpha - 2013-02-04
375 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
376 certain attacks that flood the network with relays; changes the queue
377 for circuit create requests from a sized-based limit to a time-based
378 limit; resumes building with MSVC on Windows; and fixes a wide variety
381 o Major bugfixes (directory authority):
382 - When computing directory thresholds, ignore any rejected-as-sybil
383 nodes during the computation so that they can't influence Fast,
384 Guard, etc. (We should have done this for proposal 109.) Fixes
386 - When marking a node as a likely sybil, reset its uptime metrics
387 to zero, so that it cannot time towards getting marked as Guard,
388 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
392 - When a TLS write is partially successful but incomplete, remember
393 that the flushed part has been flushed, and notice that bytes were
394 actually written. Reported and fixed pseudonymously. Fixes bug
395 7708; bugfix on Tor 0.1.0.5-rc.
396 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
397 ID: these could be used to create unexpected streams and circuits
398 which would count as "present" to some parts of Tor but "absent"
399 to others, leading to zombie circuits and streams or to a bandwidth
400 denial-of-service. Fixes bug 7889; bugfix on every released version
401 of Tor. Reported by "oftc_must_be_destroyed".
402 - Rename all macros in our local copy of queue.h to begin with "TOR_".
403 This change seems the only good way to permanently prevent conflicts
404 with queue.h on various operating systems. Fixes bug 8107; bugfix
407 o Major features (relay):
408 - Instead of limiting the number of queued onionskins (aka circuit
409 create requests) to a fixed, hard-to-configure number, we limit
410 the size of the queue based on how many we expect to be able to
411 process in a given amount of time. We estimate the time it will
412 take to process an onionskin based on average processing time
413 of previous onionskins. Closes ticket 7291. You'll never have to
414 configure MaxOnionsPending again.
416 o Major features (portability):
417 - Resume building correctly with MSVC and Makefile.nmake. This patch
418 resolves numerous bugs and fixes reported by ultramage, including
419 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
420 - Make the ntor and curve25519 code build correctly with MSVC.
421 Fix on 0.2.4.8-alpha.
424 - When directory authorities are computing thresholds for flags,
425 never let the threshold for the Fast flag fall below 4096
426 bytes. Also, do not consider nodes with extremely low bandwidths
427 when deciding thresholds for various directory flags. This change
428 should raise our threshold for Fast relays, possibly in turn
429 improving overall network performance; see ticket 1854. Resolves
431 - The Tor client now ignores sub-domain components of a .onion
432 address. This change makes HTTP "virtual" hosting
433 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
434 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
435 hosted on the same hidden service. Implements proposal 204.
436 - We compute the overhead from passing onionskins back and forth to
437 cpuworkers, and report it when dumping statistics in response to
438 SIGUSR1. Supports ticket 7291.
440 o Minor features (path selection):
441 - When deciding whether we have enough descriptors to build circuits,
442 instead of looking at raw relay counts, look at which fraction
443 of (bandwidth-weighted) paths we're able to build. This approach
444 keeps clients from building circuits if their paths are likely to
445 stand out statistically. The default fraction of paths needed is
446 taken from the consensus directory; you can override it with the
447 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
448 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
449 and we have GeoIP information, also exclude all nodes with unknown
450 countries "??" and "A1". This behavior is controlled by the
451 new GeoIPExcludeUnknown option: you can make such nodes always
452 excluded with "GeoIPExcludeUnknown 1", and disable the feature
453 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
454 gets you the default behavior. Implements feature 7706.
455 - Path Use Bias: Perform separate accounting for successful circuit
456 use. Keep separate statistics on stream attempt rates versus stream
457 success rates for each guard. Provide configurable thresholds to
458 determine when to emit log messages or disable use of guards that
459 fail too many stream attempts. Resolves ticket 7802.
461 o Minor features (log messages):
462 - When learning a fingerprint for a bridge, log its corresponding
463 transport type. Implements ticket 7896.
464 - Improve the log message when "Bug/attack: unexpected sendme cell
465 from client" occurs, to help us track bug 8093.
468 - Remove a couple of extraneous semicolons that were upsetting the
469 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
470 bugfix on 0.2.2.1-alpha.
471 - Remove a source of rounding error during path bias count scaling;
472 don't count cannibalized circuits as used for path bias until we
473 actually try to use them; and fix a circuit_package_relay_cell()
474 warning message about n_chan==NULL. Fixes bug 7802.
475 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
476 actually link against nacl when we're configured to use it. Fixes
477 bug 7972; bugfix on 0.2.4.8-alpha.
478 - Compile correctly with the --disable-curve25519 option. Fixes
479 bug 8153; bugfix on 0.2.4.8-alpha.
481 o Build improvements:
482 - Do not report status verbosely from autogen.sh unless the -v flag
483 is specified. Fixes issue 4664. Patch from Onizuka.
484 - Replace all calls to snprintf() outside of src/ext with
485 tor_snprintf(). Also remove the #define to replace snprintf with
486 _snprintf on Windows; they have different semantics, and all of
487 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
488 - Try to detect if we are ever building on a platform where
489 memset(...,0,...) does not set the value of a double to 0.0. Such
490 platforms are permitted by the C standard, though in practice
491 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
492 currently support them, but it's better to detect them and fail
493 than to perform erroneously.
496 - Stop exporting estimates of v2 and v3 directory traffic shares
497 in extrainfo documents. They were unneeded and sometimes inaccurate.
498 Also stop exporting any v2 directory request statistics. Resolves
500 - Drop support for detecting and warning about versions of Libevent
501 before 1.3e. Nothing reasonable ships with them any longer;
502 warning the user about them shouldn't be needed. Resolves ticket
505 o Code simplifications and refactoring:
506 - Rename "isin" functions to "contains", for grammar. Resolves
508 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
509 with the natural logarithm function from the system libm. Resolves
513 Changes in version 0.2.4.9-alpha - 2013-01-15
514 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
518 - Fix backward compatibility logic when receiving an embedded ntor
519 handshake tunneled in a CREATE cell. This clears up the "Bug:
520 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
524 Changes in version 0.2.4.8-alpha - 2013-01-14
525 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
526 risks, adds a new stronger and faster circuit handshake, and offers
527 stronger and faster link encryption when both sides support it.
530 - Preliminary support for directory guards (proposal 207): when
531 possible, clients now use their entry guards for non-anonymous
532 directory requests. This can help prevent client enumeration. Note
533 that this behavior only works when we have a usable consensus
534 directory, and when options about what to download are more or less
535 standard. In the future we should re-bootstrap from our guards,
536 rather than re-bootstrapping from the preconfigured list of
537 directory sources that ships with Tor. Resolves ticket 6526.
538 - Tor relays and clients now support a better CREATE/EXTEND cell
539 format, allowing the sender to specify multiple address, identity,
540 and handshake types. Implements Robert Ransom's proposal 200;
543 o Major features (new circuit handshake):
544 - Tor now supports a new circuit extension handshake designed by Ian
545 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
546 circuit extension handshake, later called "TAP", was a bit slow
547 (especially on the relay side), had a fragile security proof, and
548 used weaker keys than we'd now prefer. The new circuit handshake
549 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
550 function, making it significantly more secure than the older
551 handshake, and significantly faster. Tor can use one of two built-in
552 pure-C curve25519-donna implementations by Adam Langley, or it
553 can link against the "nacl" library for a tuned version if present.
555 The built-in version is very fast for 64-bit systems when building
556 with GCC. The built-in 32-bit version is still faster than the
557 old TAP protocol, but using libnacl is better on most such hosts.
559 Clients don't currently use this protocol by default, since
560 comparatively few clients support it so far. To try it, set
561 UseNTorHandshake to 1.
563 Implements proposal 216; closes ticket 7202.
565 o Major features (better link encryption):
566 - Relays can now enable the ECDHE TLS ciphersuites when available
567 and appropriate. These ciphersuites let us negotiate forward-secure
568 TLS secret keys more safely and more efficiently than with our
569 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
570 public relays prefer the (faster) P224 group, and bridges prefer
571 the (more common) P256 group; you can override this with the
574 Enabling these ciphers was a little tricky, since for a long time,
575 clients had been claiming to support them without actually doing
576 so, in order to foil fingerprinting. But with the client-side
577 implementation of proposal 198 in 0.2.3.17-beta, clients can now
578 match the ciphers from recent Firefox versions *and* list the
579 ciphers they actually mean, so relays can believe such clients
580 when they advertise ECDHE support in their TLS ClientHello messages.
582 This feature requires clients running 0.2.3.17-beta or later,
583 and requires both sides to be running OpenSSL 1.0.0 or later
584 with ECC support. OpenSSL 1.0.1, with the compile-time option
585 "enable-ec_nistp_64_gcc_128", is highly recommended.
587 Implements the relay side of proposal 198; closes ticket 7200.
590 - Avoid crashing when, as a relay without IPv6-exit support, a
591 client insists on getting an IPv6 address or nothing. Fixes bug
592 7814; bugfix on 0.2.4.7-alpha.
595 - Improve circuit build timeout handling for hidden services.
596 In particular: adjust build timeouts more accurately depending
597 upon the number of hop-RTTs that a particular circuit type
598 undergoes. Additionally, launch intro circuits in parallel
599 if they timeout, and take the first one to reply as valid.
600 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
601 separate error codes; or at least, don't break for that reason.
602 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
603 - Update to the January 2 2013 Maxmind GeoLite Country database.
605 o Minor features (testing):
606 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
607 (P-256) Diffie-Hellman handshakes to src/or/bench.
608 - Add benchmark functions to test onion handshake performance.
610 o Minor features (path bias detection):
611 - Alter the Path Bias log messages to be more descriptive in terms
612 of reporting timeouts and other statistics.
613 - Create three levels of Path Bias log messages, as opposed to just
614 two. These are configurable via consensus as well as via the torrc
615 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
616 The default values are 0.70, 0.50, and 0.30 respectively.
617 - Separate the log message levels from the decision to drop guards,
618 which also is available via torrc option PathBiasDropGuards.
619 PathBiasDropGuards still defaults to 0 (off).
620 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
621 in combination with PathBiasExtremeRate.
622 - Increase the default values for PathBiasScaleThreshold and
623 PathBiasCircThreshold from (200, 20) to (300, 150).
624 - Add in circuit usage accounting to path bias. If we try to use a
625 built circuit but fail for any reason, it counts as path bias.
626 Certain classes of circuits where the adversary gets to pick your
627 destination node are exempt from this accounting. Usage accounting
628 can be specifically disabled via consensus parameter or torrc.
629 - Convert all internal path bias state to double-precision floating
630 point, to avoid roundoff error and other issues.
631 - Only record path bias information for circuits that have completed
632 *two* hops. Assuming end-to-end tagging is the attack vector, this
633 makes us more resilient to ambient circuit failure without any
634 detection capability loss.
636 o Minor bugfixes (log messages):
637 - Rate-limit the "No circuits are opened. Relaxed timeout for a
638 circuit with channel state open..." message to once per hour to
639 keep it from filling the notice logs. Mitigates bug 7799 but does
640 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
641 - Avoid spurious warnings when configuring multiple client ports of
642 which only some are nonlocal. Previously, we had claimed that some
643 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
646 o Code simplifications and refactoring:
647 - Get rid of a couple of harmless clang warnings, where we compared
648 enums to ints. These warnings are newly introduced in clang 3.2.
649 - Split the onion.c file into separate modules for the onion queue
650 and the different handshakes it supports.
651 - Remove the marshalling/unmarshalling code for sending requests to
652 cpuworkers over a socket, and instead just send structs. The
653 recipient will always be the same Tor binary as the sender, so
654 any encoding is overkill.
657 Changes in version 0.2.4.7-alpha - 2012-12-24
658 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
659 directory mirrors for more robust bootstrapping; fixes more issues where
660 clients with changing network conditions refuse to make any circuits;
661 adds initial support for exiting to IPv6 addresses; resumes being able
662 to update our GeoIP database, and includes the geoip6 file this time;
663 turns off the client-side DNS cache by default due to privacy risks;
664 and fixes a variety of other issues.
666 o Major features (client resilience):
667 - Add a new "FallbackDir" torrc option to use when we can't use
668 a directory mirror from the consensus (either because we lack a
669 consensus, or because they're all down). Currently, all authorities
670 are fallbacks by default, and there are no other default fallbacks,
671 but that will change. This option will allow us to give clients a
672 longer list of servers to try to get a consensus from when first
673 connecting to the Tor network, and thereby reduce load on the
674 directory authorities. Implements proposal 206, "Preconfigured
675 directory sources for bootstrapping". We also removed the old
676 "FallbackNetworkstatus" option, since we never got it working well
677 enough to use it. Closes bug 572.
678 - If we have no circuits open, use a relaxed timeout (the
679 95-percentile cutoff) until a circuit succeeds. This heuristic
680 should allow Tor to succeed at building circuits even when the
681 network connection drastically changes. Should help with bug 3443.
683 o Major features (IPv6):
684 - Tor now has (alpha) support for exiting to IPv6 addresses. To
685 enable it as an exit node, make sure that you have IPv6
686 connectivity, then set the IPv6Exit flag to 1. Also make sure your
687 exit policy reads as you would like: the address * applies to all
688 address families, whereas *4 is IPv4 address only, and *6 is IPv6
689 addresses only. On the client side, you'll need to wait until the
690 authorities have upgraded, wait for enough exits to support IPv6,
691 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
692 ticket 5547, implements proposal 117 as revised in proposal 208.
694 We DO NOT recommend that clients with actual anonymity needs start
695 using IPv6 over Tor yet, since not enough exits support it yet.
697 o Major features (geoip database):
698 - Maxmind began labelling Tor relays as being in country "A1",
699 which breaks by-country node selection inside Tor. Now we use a
700 script to replace "A1" ("Anonymous Proxy") entries in our geoip
701 file with real country codes. This script fixes about 90% of "A1"
702 entries automatically and uses manual country code assignments to
703 fix the remaining 10%. See src/config/README.geoip for details.
704 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
705 Country database, as modified above.
707 o Major bugfixes (client-side DNS):
708 - Turn off the client-side DNS cache by default. Updating and using
709 the DNS cache is now configurable on a per-client-port
710 level. SOCKSPort, DNSPort, etc lines may now contain
711 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
712 cache these types of DNS answers when we receive them from an
713 exit node in response to an application request on this port, and
714 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
715 cached DNS answers of these types, we shouldn't use them. It's
716 potentially risky to use cached DNS answers at the client, since
717 doing so can indicate to one exit what answers we've gotten
718 for DNS lookups in the past. With IPv6, this becomes especially
719 problematic. Using cached DNS answers for requests on the same
720 circuit would present less linkability risk, since all traffic
721 on a circuit is already linkable, but it would also provide
722 little performance benefit: the exit node caches DNS replies
723 too. Implements a simplified version of Proposal 205. Implements
726 o Major bugfixes (other):
727 - Alter circuit build timeout measurement to start at the point
728 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
729 initialization). This should make our timeout measurements more
730 uniform. Previously, we were sometimes including ORconn setup time
731 in our circuit build time measurements. Should resolve bug 3443.
732 - Fix an assertion that could trigger in hibernate_go_dormant() when
733 closing an or_connection_t: call channel_mark_for_close() rather
734 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
736 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
737 7655; bugfix on 0.2.4.6-alpha.
740 - Add a new torrc option "ServerTransportListenAddr" to let bridge
741 operators select the address where their pluggable transports will
742 listen for connections. Resolves ticket 7013.
743 - Allow an optional $ before the node identity digest in the
744 controller command GETINFO ns/id/<identity>, for consistency with
745 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
746 - Log packaged cell fullness as part of the heartbeat message.
747 Diagnosis to try to determine the extent of bug 7743.
749 o Minor features (IPv6):
750 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
751 prefer to hand out virtual IPv6 addresses, since there are more of
752 them and we can't run out. To override this behavior and make IPv4
753 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
754 or DNSPort you're using for resolving. Implements ticket 7571.
755 - AutomapHostsOnResolve responses are now randomized, to avoid
756 annoying situations where Tor is restarted and applications
757 connect to the wrong addresses.
758 - Never try more than 1000 times to pick a new virtual address when
759 AutomapHostsOnResolve is set. That's good enough so long as we
760 aren't close to handing out our entire virtual address space;
761 if you're getting there, it's best to switch to IPv6 virtual
765 - The ADDRMAP command can no longer generate an ill-formed error
766 code on a failed MAPADDRESS. It now says "internal" rather than
767 an English sentence fragment with spaces in the middle. Bugfix on
769 - Fix log messages and comments to avoid saying "GMT" when we mean
770 "UTC". Fixes bug 6113.
771 - Compile on win64 using mingw64. Fixes bug 7260; patches from
773 - Fix a crash when debugging unit tests on Windows: deallocate a
774 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
775 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
778 - The DirServer option is now DirAuthority, for consistency with
779 current naming patterns. You can still use the old DirServer form.
781 o Code simplification and refactoring:
782 - Move the client-side address-map/virtual-address/DNS-cache code
783 out of connection_edge.c into a new addressmap.c module.
784 - Remove unused code for parsing v1 directories and "running routers"
785 documents. Fixes bug 6887.
788 Changes in version 0.2.3.25 - 2012-11-19
789 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
790 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
791 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
792 programmer, and friend. Unstinting in his dedication to the cause of
793 freedom, he inspired and helped many of us as we began our work on
794 anonymity, and inspires us still. Please honor his memory by writing
795 software to protect people's freedoms, and by helping others to do so.
797 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
798 significantly reduced directory overhead (via microdescriptors),
799 enormous crypto performance improvements for fast relays on new
800 enough hardware, a new v3 TLS handshake protocol that can better
801 resist fingerprinting, support for protocol obfuscation plugins (aka
802 pluggable transports), better scalability for hidden services, IPv6
803 support for bridges, performance improvements like allowing clients
804 to skip the first round-trip on the circuit ("optimistic data") and
805 refilling token buckets more often, a new "stream isolation" design
806 to isolate different applications on different circuits, and many
807 stability, security, and privacy fixes.
810 - Tor tries to wipe potentially sensitive data after using it, so
811 that if some subsequent security failure exposes Tor's memory,
812 the damage will be limited. But we had a bug where the compiler
813 was eliminating these wipe operations when it decided that the
814 memory was no longer visible to a (correctly running) program,
815 hence defeating our attempt at defense in depth. We fix that
816 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
817 is unlikely to optimize away. Future versions of Tor may use
818 a less ridiculously heavy approach for this. Fixes bug 7352.
819 Reported in an article by Andrey Karpov.
822 - Fix a harmless bug when opting against publishing a relay descriptor
823 because DisableNetwork is set. Fixes bug 7464; bugfix on
827 Changes in version 0.2.4.6-alpha - 2012-11-13
828 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
829 makes our defense-in-depth memory wiping more reliable, and begins to
830 count IPv6 addresses in bridge statistics,
833 - Fix an assertion failure that could occur when closing a connection
834 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
836 - Tor tries to wipe potentially sensitive data after using it, so
837 that if some subsequent security failure exposes Tor's memory,
838 the damage will be limited. But we had a bug where the compiler
839 was eliminating these wipe operations when it decided that the
840 memory was no longer visible to a (correctly running) program,
841 hence defeating our attempt at defense in depth. We fix that
842 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
843 is unlikely to optimize away. Future versions of Tor may use
844 a less ridiculously heavy approach for this. Fixes bug 7352.
845 Reported in an article by Andrey Karpov.
848 - Add GeoIP database for IPv6 addresses. The new config option
850 - Bridge statistics now count bridge clients connecting over IPv6:
851 bridge statistics files now list "bridge-ip-versions" and
852 extra-info documents list "geoip6-db-digest". The control protocol
853 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
854 implementation by "shkoo", addressing ticket 5055.
857 - Warn when we are binding low ports when hibernation is enabled;
858 previously we had warned when we were _advertising_ low ports with
859 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
860 - Fix a harmless bug when opting against publishing a relay descriptor
861 because DisableNetwork is set. Fixes bug 7464; bugfix on
863 - Add warning message when a managed proxy dies during configuration.
864 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
865 - Fix a linking error when building tor-fw-helper without miniupnp.
866 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
867 - Check for closing an or_connection_t without going through correct
868 channel functions; emit a warning and then call
869 connection_or_close_for_error() so we don't assert as in bugs 7212
871 - Compile correctly on compilers without C99 designated initializer
872 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
873 - Avoid a possible assert that can occur when channel_send_destroy() is
874 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
875 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
876 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
877 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
878 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
880 o Code simplification and refactoring:
881 - Start using OpenBSD's implementation of queue.h, so that we don't
882 need to hand-roll our own pointer and list structures whenever we
883 need them. (We can't rely on a sys/queue.h, since some operating
884 systems don't have them, and the ones that do have them don't all
885 present the same extensions.)
888 Changes in version 0.2.4.5-alpha - 2012-10-25
889 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
890 two important security vulnerabilities that could lead to remotely
891 triggerable relay crashes, fix a major bug that was preventing clients
892 from choosing suitable exit nodes, and refactor some of our code.
894 o Major bugfixes (security, also in 0.2.3.24-rc):
895 - Fix a group of remotely triggerable assertion failures related to
896 incorrect link protocol negotiation. Found, diagnosed, and fixed
897 by "some guy from France". Fix for CVE-2012-2250; bugfix on
899 - Fix a denial of service attack by which any directory authority
900 could crash all the others, or by which a single v2 directory
901 authority could crash everybody downloading v2 directory
902 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
904 o Major bugfixes (also in 0.2.3.24-rc):
905 - When parsing exit policy summaries from microdescriptors, we had
906 previously been ignoring the last character in each one, so that
907 "accept 80,443,8080" would be treated by clients as indicating
908 a node that allows access to ports 80, 443, and 808. That would
909 lead to clients attempting connections that could never work,
910 and ignoring exit nodes that would support their connections. Now
911 clients parse these exit policy summaries correctly. Fixes bug 7192;
912 bugfix on 0.2.3.1-alpha.
914 o Minor bugfixes (also in 0.2.3.24-rc):
915 - Clients now consider the ClientRejectInternalAddresses config option
916 when using a microdescriptor consensus stanza to decide whether
917 an exit relay would allow exiting to an internal address. Fixes
918 bug 7190; bugfix on 0.2.3.1-alpha.
921 - Only disable TLS session ticket support when running as a TLS
922 server. Now clients will blend better with regular Firefox
923 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
925 o Code simplification and refactoring:
926 - Start using OpenBSD's implementation of queue.h (originally by
928 - Move the entry node code from circuitbuild.c to its own file.
929 - Move the circuit build timeout tracking code from circuitbuild.c
933 Changes in version 0.2.3.24-rc - 2012-10-25
934 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
935 could lead to remotely triggerable relay crashes, and fixes
936 a major bug that was preventing clients from choosing suitable exit
939 o Major bugfixes (security):
940 - Fix a group of remotely triggerable assertion failures related to
941 incorrect link protocol negotiation. Found, diagnosed, and fixed
942 by "some guy from France". Fix for CVE-2012-2250; bugfix on
944 - Fix a denial of service attack by which any directory authority
945 could crash all the others, or by which a single v2 directory
946 authority could crash everybody downloading v2 directory
947 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
950 - When parsing exit policy summaries from microdescriptors, we had
951 previously been ignoring the last character in each one, so that
952 "accept 80,443,8080" would be treated by clients as indicating
953 a node that allows access to ports 80, 443, and 808. That would
954 lead to clients attempting connections that could never work,
955 and ignoring exit nodes that would support their connections. Now
956 clients parse these exit policy summaries correctly. Fixes bug 7192;
957 bugfix on 0.2.3.1-alpha.
960 - Clients now consider the ClientRejectInternalAddresses config option
961 when using a microdescriptor consensus stanza to decide whether
962 an exit relay would allow exiting to an internal address. Fixes
963 bug 7190; bugfix on 0.2.3.1-alpha.
966 Changes in version 0.2.4.4-alpha - 2012-10-20
967 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
968 vulnerability introduced by a change in OpenSSL, fixes a remotely
969 triggerable assert, and adds new channel_t and circuitmux_t abstractions
970 that will make it easier to test new connection transport and cell
971 scheduling algorithms.
973 o New directory authorities (also in 0.2.3.23-rc):
974 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
975 authority. Closes ticket 5749.
977 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
978 - Disable TLS session tickets. OpenSSL's implementation was giving
979 our TLS session keys the lifetime of our TLS context objects, when
980 perfect forward secrecy would want us to discard anything that
981 could decrypt a link connection as soon as the link connection
982 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
983 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
984 - Discard extraneous renegotiation attempts once the V3 link
985 protocol has been initiated. Failure to do so left us open to
986 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
987 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
989 o Internal abstraction features:
990 - Introduce new channel_t abstraction between circuits and
991 or_connection_t to allow for implementing alternate OR-to-OR
992 transports. A channel_t is an abstract object which can either be a
993 cell-bearing channel, which is responsible for authenticating and
994 handshaking with the remote OR and transmitting cells to and from
995 it, or a listening channel, which spawns new cell-bearing channels
996 at the request of remote ORs. Implements part of ticket 6465.
997 - Also new is the channel_tls_t subclass of channel_t, adapting it
998 to the existing or_connection_t code. The V2/V3 protocol handshaking
999 code which formerly resided in command.c has been moved below the
1000 channel_t abstraction layer and may be found in channeltls.c now.
1001 Implements the rest of ticket 6465.
1002 - Introduce new circuitmux_t storing the queue of circuits for
1003 a channel; this encapsulates and abstracts the queue logic and
1004 circuit selection policy, and allows the latter to be overridden
1005 easily by switching out a policy object. The existing EWMA behavior
1006 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1008 o Required libraries:
1009 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1010 strongly recommended.
1013 - Warn users who run hidden services on a Tor client with
1014 UseEntryGuards disabled that their hidden services will be
1015 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1016 attack which motivated Tor to support entry guards in the first
1017 place). Resolves ticket 6889.
1018 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1019 dhill. Resolves ticket 6982.
1020 - Option OutboundBindAddress can be specified multiple times and
1021 accepts IPv6 addresses. Resolves ticket 6876.
1023 o Minor bugfixes (also in 0.2.3.23-rc):
1024 - Don't serve or accept v2 hidden service descriptors over a
1025 relay's DirPort. It's never correct to do so, and disabling it
1026 might make it more annoying to exploit any bugs that turn up in the
1027 descriptor-parsing code. Fixes bug 7149.
1028 - Fix two cases in src/or/transports.c where we were calling
1029 fmt_addr() twice in a parameter list. Bug found by David
1030 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1031 - Fix memory leaks whenever we logged any message about the "path
1032 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1033 - When relays refuse a "create" cell because their queue of pending
1034 create cells is too big (typically because their cpu can't keep up
1035 with the arrival rate), send back reason "resource limit" rather
1036 than reason "internal", so network measurement scripts can get a
1037 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1040 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1041 - Free some more still-in-use memory at exit, to make hunting for
1042 memory leaks easier. Resolves bug 7029.
1043 - When a Tor client gets a "truncated" relay cell, the first byte of
1044 its payload specifies why the circuit was truncated. We were
1045 ignoring this 'reason' byte when tearing down the circuit, resulting
1046 in the controller not being told why the circuit closed. Now we
1047 pass the reason from the truncated cell to the controller. Bugfix
1048 on 0.1.2.3-alpha; fixes bug 7039.
1049 - Downgrade "Failed to hand off onionskin" messages to "debug"
1050 severity, since they're typically redundant with the "Your computer
1051 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1052 - Make clients running with IPv6 bridges connect over IPv6 again,
1053 even without setting new config options ClientUseIPv6 and
1054 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1055 - Use square brackets around IPv6 addresses in numerous places
1056 that needed them, including log messages, HTTPS CONNECT proxy
1057 requests, TransportProxy statefile entries, and pluggable transport
1058 extra-info lines. Fixes bug 7011; patch by David Fifield.
1060 o Code refactoring and cleanup:
1061 - Source files taken from other packages now reside in src/ext;
1062 previously they were scattered around the rest of Tor.
1063 - Avoid use of reserved identifiers in our C code. The C standard
1064 doesn't like us declaring anything that starts with an
1065 underscore, so let's knock it off before we get in trouble. Fix
1066 for bug 1031; bugfix on the first Tor commit.
1069 Changes in version 0.2.3.23-rc - 2012-10-20
1070 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1071 vulnerability introduced by a change in OpenSSL, and fixes a variety
1072 of smaller bugs in preparation for the release.
1074 o New directory authorities:
1075 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1076 authority. Closes ticket 5749.
1078 o Major bugfixes (security/privacy):
1079 - Disable TLS session tickets. OpenSSL's implementation was giving
1080 our TLS session keys the lifetime of our TLS context objects, when
1081 perfect forward secrecy would want us to discard anything that
1082 could decrypt a link connection as soon as the link connection
1083 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1084 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1085 - Discard extraneous renegotiation attempts once the V3 link
1086 protocol has been initiated. Failure to do so left us open to
1087 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1088 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1091 - Fix a possible crash bug when checking for deactivated circuits
1092 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1093 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1095 o Minor bugfixes (on 0.2.3.x):
1096 - Fix two cases in src/or/transports.c where we were calling
1097 fmt_addr() twice in a parameter list. Bug found by David
1098 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1099 - Convert an assert in the pathbias code to a log message. The assert
1100 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1101 bugfix on 0.2.3.17-beta.
1102 - Fix memory leaks whenever we logged any message about the "path
1103 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1105 o Minor bugfixes (on 0.2.2.x and earlier):
1106 - Don't serve or accept v2 hidden service descriptors over a relay's
1107 DirPort. It's never correct to do so, and disabling it might
1108 make it more annoying to exploit any bugs that turn up in the
1109 descriptor-parsing code. Fixes bug 7149.
1110 - When relays refuse a "create" cell because their queue of pending
1111 create cells is too big (typically because their cpu can't keep up
1112 with the arrival rate), send back reason "resource limit" rather
1113 than reason "internal", so network measurement scripts can get a
1114 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1115 - Correct file sizes when reading binary files on Cygwin, to avoid
1116 a bug where Tor would fail to read its state file. Fixes bug 6844;
1117 bugfix on 0.1.2.7-alpha.
1118 - Avoid undefined behaviour when parsing the list of supported
1119 rendezvous/introduction protocols in a hidden service descriptor.
1120 Previously, Tor would have confused (as-yet-unused) protocol version
1121 numbers greater than 32 with lower ones on many platforms. Fixes
1122 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1124 o Documentation fixes:
1125 - Clarify that hidden services are TCP only. Fixes bug 6024.
1128 Changes in version 0.2.4.3-alpha - 2012-09-22
1129 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1130 assertion, resumes letting relays test reachability of their DirPort,
1131 and cleans up a bunch of smaller bugs.
1134 - Fix an assertion failure in tor_timegm() that could be triggered
1135 by a badly formatted directory object. Bug found by fuzzing with
1136 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1139 - Fix a possible crash bug when checking for deactivated circuits
1140 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1141 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1142 - Allow routers to detect that their own DirPorts are running. When
1143 we removed support for versions_supports_begindir, we also
1144 accidentally removed the mechanism we used to self-test our
1145 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1146 bugfix on 0.2.4.2-alpha.
1148 o Security features:
1149 - Switch to a completely time-invariant approach for picking nodes
1150 weighted by bandwidth. Our old approach would run through the
1151 part of the loop after it had made its choice slightly slower
1152 than it ran through the part of the loop before it had made its
1153 choice. Addresses ticket 6538.
1154 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1155 by tor2web clients allows hidden services to identity tor2web
1156 clients through their repeated selection of the same rendezvous
1157 and introduction point circuit endpoints (their guards). Resolves
1161 - Enable Tor to read configuration, state, and key information from
1162 a FIFO. Previously Tor would only read from files with a positive
1163 stat.st_size. Code from meejah; fixes bug 6044.
1166 - Correct file sizes when reading binary files on Cygwin, to avoid
1167 a bug where Tor would fail to read its state file. Fixes bug 6844;
1168 bugfix on 0.1.2.7-alpha.
1169 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1170 bugfix on 0.2.0.3-alpha.
1171 - When complaining about a client port on a public address, log
1172 which address we're complaining about. Fixes bug 4020; bugfix on
1173 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1174 - Convert an assert in the pathbias code to a log message. The assert
1175 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1176 bugfix on 0.2.3.17-beta.
1177 - Our new buildsystem was overzealous about rebuilding manpages: it
1178 would rebuild them all whenever any one of them changed. Now our
1179 dependency checking should be correct. Fixes bug 6843; bugfix on
1181 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1182 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1183 - Correct log printout about which address family is preferred
1184 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1185 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1187 o Minor bugfixes (code cleanliness):
1188 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1189 with large values. This situation was untriggered, but nevertheless
1190 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1191 - Reject consensus votes with more than 64 known-flags. We aren't even
1192 close to that limit yet, and our code doesn't handle it correctly.
1193 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1194 - Avoid undefined behaviour when parsing the list of supported
1195 rendezvous/introduction protocols in a hidden service descriptor.
1196 Previously, Tor would have confused (as-yet-unused) protocol version
1197 numbers greater than 32 with lower ones on many platforms. Fixes
1198 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1199 - Fix handling of rendezvous client authorization types over 8.
1200 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1201 - Fix building with older versions of GCC (2.95, for one) that don't
1202 like preprocessor directives inside macro arguments. Found by
1203 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1204 - Switch weighted node selection rule from using a list of doubles
1205 to using a list of int64_t. This change should make the process
1206 slightly easier to debug and maintain. Needed to finish ticket 6538.
1208 o Code simplification and refactoring:
1209 - Move the generic "config" code into a new file, and have "config.c"
1210 hold only torrc- and state-related code. Resolves ticket 6823.
1211 - Move the core of our "choose a weighted element at random" logic
1212 into its own function, and give it unit tests. Now the logic is
1213 testable, and a little less fragile too.
1214 - Removed the testing_since field of node_t, which hasn't been used
1215 for anything since 0.2.0.9-alpha.
1217 o Documentation fixes:
1218 - Clarify that hidden services are TCP only. Fixes bug 6024.
1219 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1223 Changes in version 0.2.3.22-rc - 2012-09-11
1224 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1228 - Fix an assertion failure in tor_timegm() that could be triggered
1229 by a badly formatted directory object. Bug found by fuzzing with
1230 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1233 - Avoid segfault when starting up having run with an extremely old
1234 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1238 Changes in version 0.2.2.39 - 2012-09-11
1239 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1243 - Fix an assertion failure in tor_timegm() that could be triggered
1244 by a badly formatted directory object. Bug found by fuzzing with
1245 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1246 - Do not crash when comparing an address with port value 0 to an
1247 address policy. This bug could have been used to cause a remote
1248 assertion failure by or against directory authorities, or to
1249 allow some applications to crash clients. Fixes bug 6690; bugfix
1253 Changes in version 0.2.4.2-alpha - 2012-09-10
1254 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1255 raises the default rate limiting even more, and makes the bootstrapping
1256 log messages less noisy.
1259 - Automatically forward the TCP ports of pluggable transport
1260 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1264 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1265 to 1GB/1GB. The previous defaults were intended to be "basically
1266 infinite", but it turns out they're now limiting our 100mbit+
1267 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1268 last time we raised it).
1271 - Detect when we're running with a version of OpenSSL other than the
1272 one we compiled with. This has occasionally given people hard-to-
1274 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1275 versions and capabilities when everything is going right. Resolves
1276 part of ticket 6736.
1277 - Directory authorities no long accept descriptors for any version of
1278 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1279 These versions are insecure, unsupported, or both. Implements
1283 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1284 to start with a triple-underscore so the controller won't touch it.
1285 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1286 - Avoid segfault when starting up having run with an extremely old
1287 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1289 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1290 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1291 - Don't follow the NULL pointer if microdescriptor generation fails.
1292 (This does not appear to be triggerable, but it's best to be safe.)
1293 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1294 - Fix mis-declared dependencies on src/common/crypto.c and
1295 src/or/tor_main.c that could break out-of-tree builds under some
1296 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1297 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1298 6778; bugfix on 0.2.4.1-alpha.
1299 - Fix a harmless (in this case) build warning for implicitly
1300 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1303 - Now that all versions before 0.2.2.x are disallowed, we no longer
1304 need to work around their missing features. Thus we can remove a
1305 bunch of compatibility code.
1308 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1309 TCP ports to forward. In the past it only accepted two ports:
1310 the ORPort and the DirPort.
1313 Changes in version 0.2.4.1-alpha - 2012-09-05
1314 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1315 bridgedb; lets relays use IPv6 addresses and directory authorities
1316 advertise them; and switches to a cleaner build interface.
1318 This is the first alpha release in a new series, so expect there to
1319 be bugs. Users who would rather test out a more stable branch should
1320 stay with 0.2.3.x for now.
1322 o Major features (bridges):
1323 - Bridges now report the pluggable transports they support to the
1324 bridge authority, so it can pass the supported transports on to
1325 bridgedb and/or eventually do reachability testing. Implements
1328 o Major features (IPv6):
1329 - Bridge authorities now accept IPv6 bridge addresses and include
1330 them in network status documents. Implements ticket 5534.
1331 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1332 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1333 to happen. Implements ticket 5535.
1334 - All kind of relays, not just bridges, can now advertise an IPv6
1335 OR port. Implements ticket 6362.
1336 - Directory authorities vote on IPv6 OR ports using the new consensus
1337 method 14. Implements ticket 6363.
1339 o Major features (build):
1340 - Switch to a nonrecursive Makefile structure. Now instead of each
1341 Makefile.am invoking other Makefile.am's, there is a master
1342 Makefile.am that includes the others. This change makes our build
1343 process slightly more maintainable, and improves parallelism for
1344 building with make -j. Original patch by Stewart Smith; various
1345 fixes by Jim Meyering.
1346 - Where available, we now use automake's "silent" make rules by
1347 default, so that warnings are easier to spot. You can get the old
1348 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1350 o Minor features (code security and spec conformance):
1351 - Clear keys and key-derived material left on the stack in
1352 rendservice.c and rendclient.c. Check return value of
1353 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1354 These fixes should make us more forward-secure against cold-boot
1355 attacks and the like. Fixes bug 2385.
1356 - Reject EXTEND cells sent to nonexistent streams. According to the
1357 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1358 we were only checking for stream IDs that were currently in use.
1359 Found while hunting for more instances of bug 6271. Bugfix on
1360 0.0.2pre8, which introduced incremental circuit construction.
1362 o Minor features (streamlining);
1363 - No longer include the "opt" prefix when generating routerinfos
1364 or v2 directories: it has been needless since Tor 0.1.2. Closes
1366 - Remove some now-needless code that tried to aggressively flush
1367 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1368 cell queue logic has saved us from the failure mode that this code
1369 was supposed to prevent. Removing this code will limit the number
1370 of baroque control flow paths through Tor's network logic. Reported
1371 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1373 o Minor features (controller):
1374 - Add a "GETINFO signal/names" control port command. Implements
1376 - Provide default values for all options via "GETINFO config/defaults".
1377 Implements ticket 4971.
1379 o Minor features (IPv6):
1380 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1381 authorities should set if they have IPv6 connectivity and want to
1382 do reachability tests for IPv6 relays. Implements feature 5974.
1383 - A relay with an IPv6 OR port now sends that address in NETINFO
1384 cells (in addition to its other address). Implements ticket 6364.
1386 o Minor features (log messages):
1387 - Omit the first heartbeat log message, because it never has anything
1388 useful to say, and it clutters up the bootstrapping messages.
1389 Resolves ticket 6758.
1390 - Don't log about reloading the microdescriptor cache at startup. Our
1391 bootstrap warnings are supposed to tell the user when there's a
1392 problem, and our bootstrap notices say when there isn't. Resolves
1393 ticket 6759; bugfix on 0.2.2.6-alpha.
1394 - Don't log "I learned some more directory information" when we're
1395 reading cached directory information. Reserve it for when new
1396 directory information arrives in response to a fetch. Resolves
1398 - Prevent rounding error in path bias counts when scaling
1399 them down, and use the correct scale factor default. Also demote
1400 some path bias related log messages down a level and make others
1401 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1402 - We no longer warn so much when generating manpages from their
1405 o Code simplifications and refactoring:
1406 - Enhance our internal sscanf replacement so that we can eliminate
1407 the last remaining uses of the system sscanf. (Though those uses
1408 of sscanf were safe, sscanf itself is generally error prone, so
1409 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1411 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1412 - Move last_reachable and testing_since from routerinfo_t to node_t.
1413 Implements ticket 5529.
1414 - Add replaycache_t structure, functions and unit tests, then refactor
1415 rend_service_introduce() to be more clear to read, improve, debug,
1416 and test. Resolves bug 6177.
1417 - Finally remove support for malloc_good_size and malloc_usable_size.
1418 We had hoped that these functions would let us eke a little more
1419 memory out of our malloc implementation. Unfortunately, the only
1420 implementations that provided these functions are also ones that
1421 are already efficient about not overallocation: they never got us
1422 more than 7 or so bytes per allocation. Removing them saves us a
1423 little code complexity and a nontrivial amount of build complexity.
1426 - Tor maintainers now require Automake version 1.9 or later to build
1427 Tor from the Git repository. (Automake is not required when building
1428 from a source distribution.)
1431 Changes in version 0.2.3.21-rc - 2012-09-05
1432 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1433 series. It fixes a trio of potential security bugs, fixes a bug where
1434 we were leaving some of the fast relays out of the microdescriptor
1435 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1436 and cleans up other smaller issues.
1438 o Major bugfixes (security):
1439 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1440 could use this trick to make their circuits receive cells faster
1441 than our flow control would have allowed, or to gum up the network,
1442 or possibly to do targeted memory denial-of-service attacks on
1443 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1444 from July 2002, before the release of Tor 0.0.0. We had committed
1445 this patch previously, but we had to revert it because of bug 6271.
1446 Now that 6271 is fixed, this patch appears to work.
1447 - Reject any attempt to extend to an internal address. Without
1448 this fix, a router could be used to probe addresses on an internal
1449 network to see whether they were accepting connections. Fixes bug
1450 6710; bugfix on 0.0.8pre1.
1451 - Do not crash when comparing an address with port value 0 to an
1452 address policy. This bug could have been used to cause a remote
1453 assertion failure by or against directory authorities, or to
1454 allow some applications to crash clients. Fixes bug 6690; bugfix
1458 - Remove the upper bound on microdescriptor length. We were hitting
1459 the limit for routers with complex exit policies or family
1460 declarations, causing clients to not use them. Fixes the first
1461 piece of bug 6404; fix on 0.2.2.6-alpha.
1462 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1463 as a relay. Previously, some of our code would treat the presence
1464 of any ORPort line as meaning that we should act like a relay,
1465 even though our new listener code would correctly not open any
1466 ORPorts for ORPort 0. Similar bugs in other Port options are also
1467 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1470 - Avoid a pair of double-free and use-after-mark bugs that can
1471 occur with certain timings in canceled and re-received DNS
1472 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1473 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1474 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1475 - Allow one-hop directory fetching circuits the full "circuit build
1476 timeout" period, rather than just half of it, before failing them
1477 and marking the relay down. This fix should help reduce cases where
1478 clients declare relays (or worse, bridges) unreachable because
1479 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1480 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1482 - Authorities no longer include any router in their microdescriptor
1483 consensuses for which they couldn't generate or agree on a
1484 microdescriptor. Fixes the second piece of bug 6404; fix on
1486 - Detect and reject attempts to specify both "FooPort" and
1487 "FooPort 0" in the same configuration domain. (It's still okay
1488 to have a FooPort in your configuration file, and use "FooPort 0"
1489 on the command line to disable it.) Fixes the second half of bug
1490 6507; bugfix on 0.2.3.3-alpha.
1491 - Make wildcarded addresses (that is, ones beginning with "*.") work
1492 when provided via the controller's MapAddress command. Previously,
1493 they were accepted, but we never actually noticed that they were
1494 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1495 - Avoid crashing on a malformed state file where EntryGuardPathBias
1496 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1497 - Add a (probably redundant) memory clear between iterations of
1498 the router status voting loop, to prevent future coding errors
1499 where data might leak between iterations of the loop. Resolves
1502 o Minor bugfixes (log messages):
1503 - Downgrade "set buildtimeout to low value" messages to "info"
1504 severity; they were never an actual problem, there was never
1505 anything reasonable to do about them, and they tended to spam logs
1506 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1507 - Downgrade path-bias warning messages to "info". We'll try to get
1508 them working better in 0.2.4. Add internal circuit construction
1509 state to protect against the noisy warn message "Unexpectedly high
1510 circuit_successes". Also add some additional rate-limited notice
1511 messages to help determine the root cause of the warn. Fixes bug
1512 6475. Bugfix against 0.2.3.17-beta.
1513 - Move log message when unable to find a microdesc in a routerstatus
1514 entry to parse time. Previously we'd spam this warning every time
1515 we tried to figure out which microdescriptors to download. Fixes
1516 the third piece of bug 6404; fix on 0.2.3.18-rc.
1519 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1520 change when the authority is deciding whether to accept a newly
1521 uploaded descriptor. Implements ticket 6423.
1522 - Add missing documentation for consensus and microdesc files.
1523 Resolves ticket 6732.
1526 Changes in version 0.2.2.38 - 2012-08-12
1527 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1528 attack that could in theory leak path information.
1531 - Avoid an uninitialized memory read when reading a vote or consensus
1532 document that has an unrecognized flavor name. This read could
1533 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1534 - Try to leak less information about what relays a client is
1535 choosing to a side-channel attacker. Previously, a Tor client would
1536 stop iterating through the list of available relays as soon as it
1537 had chosen one, thus finishing a little earlier when it picked
1538 a router earlier in the list. If an attacker can recover this
1539 timing information (nontrivial but not proven to be impossible),
1540 they could learn some coarse-grained information about which relays
1541 a client was picking (middle nodes in particular are likelier to
1542 be affected than exits). The timing attack might be mitigated by
1543 other factors (see bug 6537 for some discussion), but it's best
1544 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1547 Changes in version 0.2.3.20-rc - 2012-08-05
1548 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1549 series. It fixes a pair of code security bugs and a potential anonymity
1550 issue, updates our RPM spec files, and cleans up other smaller issues.
1553 - Avoid read-from-freed-memory and double-free bugs that could occur
1554 when a DNS request fails while launching it. Fixes bug 6480;
1555 bugfix on 0.2.0.1-alpha.
1556 - Avoid an uninitialized memory read when reading a vote or consensus
1557 document that has an unrecognized flavor name. This read could
1558 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1559 - Try to leak less information about what relays a client is
1560 choosing to a side-channel attacker. Previously, a Tor client would
1561 stop iterating through the list of available relays as soon as it
1562 had chosen one, thus finishing a little earlier when it picked
1563 a router earlier in the list. If an attacker can recover this
1564 timing information (nontrivial but not proven to be impossible),
1565 they could learn some coarse-grained information about which relays
1566 a client was picking (middle nodes in particular are likelier to
1567 be affected than exits). The timing attack might be mitigated by
1568 other factors (see bug 6537 for some discussion), but it's best
1569 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1572 - Try to make the warning when giving an obsolete SOCKSListenAddress
1573 a little more useful.
1574 - Terminate active server managed proxies if Tor stops being a
1575 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1576 - Provide a better error message about possible OSX Asciidoc failure
1577 reasons. Fixes bug 6436.
1578 - Warn when Tor is configured to use accounting in a way that can
1579 link a hidden service to some other hidden service or public
1580 address. Resolves ticket 6490.
1583 - Check return value of fputs() when writing authority certificate
1584 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1585 - Ignore ServerTransportPlugin lines when Tor is not configured as
1586 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1587 - When disabling guards for having too high a proportion of failed
1588 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1592 - Update our default RPM spec files to work with mock and rpmbuild
1593 on RHEL/Fedora. They have an updated set of dependencies and
1594 conflicts, a fix for an ancient typo when creating the "_tor"
1595 user, and better instructions. Thanks to Ondrej Mikle for the
1596 patch series. Fixes bug 6043.
1599 - Make it possible to set the TestingTorNetwork configuration
1600 option using AlternateDirAuthority and AlternateBridgeAuthority
1601 as an alternative to setting DirServer. Addresses ticket 6377.
1604 - Clarify the documentation for the Alternate*Authority options.
1606 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1608 o Code simplification and refactoring:
1609 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1610 10 lines. Also, don't nest them. Doing so in the past has
1611 led to hard-to-debug code. The new style is to use the
1612 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1615 Changes in version 0.2.3.19-rc - 2012-07-06
1616 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1617 series. It fixes the compile on Windows, reverts to a GeoIP database
1618 that isn't as broken, and fixes a flow control bug that has been around
1619 since the beginning of Tor.
1622 - Fix a bug handling SENDME cells on nonexistent streams that could
1623 result in bizarre window values. Report and patch contributed
1624 pseudonymously. Fixes part of bug 6271. This bug was introduced
1625 before the first Tor release, in svn commit r152.
1626 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1627 June 2012 database, Maxmind marked many Tor relays as country "A1",
1628 which will cause risky behavior for clients that set EntryNodes
1629 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1630 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1631 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1634 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1635 bugfix on 0.2.1.10-alpha.
1638 Changes in version 0.2.3.18-rc - 2012-06-28
1639 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1640 series. It fixes a few smaller bugs, but generally appears stable.
1641 Please test it and let us know whether it is!
1644 - Allow wildcarded mapaddress targets to be specified on the
1645 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1646 - Make our linker option detection code more robust against linkers
1647 such as on FreeBSD 8, where a bad combination of options completes
1648 successfully but makes an unrunnable binary. Fixes bug 6173;
1649 bugfix on 0.2.3.17-beta.
1651 o Minor bugfixes (on 0.2.2.x and earlier):
1652 - Avoid a false positive in the util/threads unit test by increasing
1653 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1654 - Replace "Sending publish request" log messages with "Launching
1655 upload", so that they no longer confusingly imply that we're
1656 sending something to a directory we might not even be connected
1657 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1658 - Make sure to set *socket_error in all error cases in
1659 connection_connect(), so it can't produce a warning about
1660 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1661 0.2.1.1-alpha; resolves ticket 6028.
1662 - Downgrade "Got a certificate, but we already have it" log messages
1663 from warning to info, except when we're a dirauth. Fixes bug 5238;
1664 bugfix on 0.2.1.7-alpha.
1665 - When checking for requested signatures on the latest consensus
1666 before serving it to a client, make sure to check the right
1667 consensus flavor. Bugfix on 0.2.2.6-alpha.
1668 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1669 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1671 o Minor bugfixes (on 0.2.3.x):
1672 - Make format_helper_exit_status() avoid unnecessary space padding
1673 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1675 - Downgrade a message about cleaning the microdescriptor cache to
1676 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1677 - Log a BUG message at severity INFO if we have a networkstatus with
1678 a missing entry for some microdescriptor. Continues on a patch
1680 - Improve the log message when a managed proxy fails to launch. Fixes
1681 bug 5099; bugfix on 0.2.3.6-alpha.
1682 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1683 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1684 - When formatting wildcarded address mappings for the controller,
1685 be sure to include "*." as appropriate. Partially fixes bug 6244;
1686 bugfix on 0.2.3.9-alpha.
1687 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1688 Bugfix on 0.2.3.13-alpha.
1689 - Stop logging messages about running with circuit timeout learning
1690 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1691 - Disable a spurious warning about reading on a marked and flushing
1692 connection. We shouldn't be doing that, but apparently we
1693 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1694 - Fix a bug that stopped AllowDotExit from working on addresses
1695 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1698 o Code simplification, refactoring, unit tests:
1699 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1700 Libevent's notion of cached time when possible.
1701 - Remove duplicate code for invoking getrlimit() from control.c.
1702 - Add a unit test for the environment_variable_names_equal function.
1705 - Document the --defaults-torrc option, and the new (in 0.2.3)
1706 semantics for overriding, extending, and clearing lists of
1707 options. Closes bug 4748.
1710 Changes in version 0.2.3.17-beta - 2012-06-15
1711 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1712 gets our TLS handshake back on track for being able to blend in with
1713 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1714 with Vidalia, and otherwise continues to get us closer to a release
1718 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1719 - Update TLS cipher list to match Firefox 8 and later. Resolves
1721 - Implement the client side of proposal 198: remove support for
1722 clients falsely claiming to support standard ciphersuites that
1723 they can actually provide. As of modern OpenSSL versions, it's not
1724 necessary to fake any standard ciphersuite, and doing so prevents
1725 us from using better ciphersuites in the future, since servers
1726 can't know whether an advertised ciphersuite is really supported or
1727 not. Some hosts -- notably, ones with very old versions of OpenSSL
1728 or where OpenSSL has been built with ECC disabled -- will stand
1729 out because of this change; TBB users should not be affected.
1732 - Change the default value for DynamicDHGroups (introduced in
1733 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1734 identifiable by their use of the mod_ssl DH group, but at
1735 the cost of some usability (#4721) and bridge tracing (#6087)
1736 regressions. Resolves ticket 5598.
1737 - Send a CRLF at the end of each STATUS_* control protocol event. This
1738 bug tickled a bug in Vidalia which would make it freeze. Fixes
1739 bug 6094; bugfix on 0.2.3.16-alpha.
1742 - Disable writing on marked-for-close connections when they are
1743 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1744 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1745 case for flushing marked connections.
1746 - Detect SSL handshake even when the initial attempt to write the
1747 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1748 - Change the AllowDotExit rules so they should actually work.
1749 We now enforce AllowDotExit only immediately after receiving an
1750 address via SOCKS or DNSPort: other sources are free to provide
1751 .exit addresses after the resolution occurs. Fixes bug 3940;
1752 bugfix on 0.2.2.1-alpha.
1753 - Fix a (harmless) integer overflow in cell statistics reported by
1754 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1755 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
1756 right places and never depends on the consensus parameters or
1757 computes adaptive timeouts when it is disabled. Fixes bug 5049;
1758 bugfix on 0.2.2.14-alpha.
1759 - When building Tor on Windows with -DUNICODE (not default), ensure
1760 that error messages, filenames, and DNS server names are always
1761 NUL-terminated when we convert them to a single-byte encoding.
1762 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1763 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1764 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1765 - Fix an edge case where TestingTorNetwork is set but the authorities
1766 and relays all have an uptime of zero, where the private Tor network
1767 could briefly lack support for hidden services. Fixes bug 3886;
1768 bugfix on 0.2.2.18-alpha.
1769 - Correct the manpage's descriptions for the default values of
1770 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
1772 - Fix the documentation for the --hush and --quiet command line
1773 options, which changed their behavior back in 0.2.3.3-alpha.
1774 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
1778 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
1779 more information to it, so that we can track it down in case it
1780 returns again. Mitigates bug 5235.
1781 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
1782 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
1783 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
1784 - Warn the user when HTTPProxy, but no other proxy type, is
1785 configured. This can cause surprising behavior: it doesn't send
1786 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
1787 directory traffic only. Resolves ticket 4663.
1788 - Issue a notice if a guard completes less than 40% of your circuits.
1789 Threshold is configurable by torrc option PathBiasNoticeRate and
1790 consensus parameter pb_noticepct. There is additional, off-by-
1791 default code to disable guards which fail too many circuits.
1792 Addresses ticket 5458.
1793 - Update to the June 6 2012 Maxmind GeoLite Country database.
1795 o Code simplifications and refactoring:
1796 - Remove validate_pluggable_transports_config(): its warning
1797 message is now handled by connection_or_connect().
1800 Changes in version 0.2.2.37 - 2012-06-06
1801 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
1802 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1806 - Work around a bug in OpenSSL that broke renegotiation with TLS
1807 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1808 the v2 Tor connection protocol when both sides were using OpenSSL
1809 1.0.1 would fail. Resolves ticket 6033.
1810 - When waiting for a client to renegotiate, don't allow it to add
1811 any bytes to the input buffer. This fixes a potential DoS issue.
1812 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1813 - Fix an edge case where if we fetch or publish a hidden service
1814 descriptor, we might build a 4-hop circuit and then use that circuit
1815 for exiting afterwards -- even if the new last hop doesn't obey our
1816 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1819 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1820 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1823 - Tell GCC and Clang to check for any errors in format strings passed
1824 to the tor_v*(print|scan)f functions.
1827 Changes in version 0.2.3.16-alpha - 2012-06-05
1828 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
1829 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
1830 currently). It also fixes a variety of smaller bugs and other cleanups
1831 that get us closer to a release candidate.
1833 o Major bugfixes (general):
1834 - Work around a bug in OpenSSL that broke renegotiation with TLS
1835 1.1 and TLS 1.2. Without this workaround, all attempts to speak
1836 the v2 Tor connection protocol when both sides were using OpenSSL
1837 1.0.1 would fail. Resolves ticket 6033.
1838 - When waiting for a client to renegotiate, don't allow it to add
1839 any bytes to the input buffer. This fixes a potential DoS issue.
1840 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
1841 - Pass correct OR address to managed proxies (like obfsproxy),
1842 even when ORListenAddress is used. Fixes bug 4865; bugfix on
1844 - The advertised platform of a router now includes only its operating
1845 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
1846 service pack level (for Windows) or its CPU architecture (for Unix).
1847 We also no longer include the "git-XYZ" tag in the version. Resolves
1850 o Major bugfixes (clients):
1851 - If we are unable to find any exit that supports our predicted ports,
1852 stop calling them predicted, so that we don't loop and build
1853 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
1854 which introduced predicted ports.
1855 - Fix an edge case where if we fetch or publish a hidden service
1856 descriptor, we might build a 4-hop circuit and then use that circuit
1857 for exiting afterwards -- even if the new last hop doesn't obey our
1858 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
1859 - Check at each new consensus whether our entry guards were picked
1860 long enough ago that we should rotate them. Previously, we only
1861 did this check at startup, which could lead to us holding a guard
1862 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
1863 - When fetching a bridge descriptor from a bridge authority,
1864 always do so anonymously, whether we have been able to open
1865 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
1866 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
1867 but we'll need to wait for bug 6010 before it's actually usable.
1869 o Major bugfixes (directory authorities):
1870 - When computing weight parameters, behave more robustly in the
1871 presence of a bad bwweightscale value. Previously, the authorities
1872 would crash if they agreed on a sufficiently broken weight_scale
1873 value: now, they use a reasonable default and carry on. Partial
1874 fix for 5786; bugfix on 0.2.2.17-alpha.
1875 - Check more thoroughly to prevent a rogue authority from
1876 double-voting on any consensus directory parameter. Previously,
1877 authorities would crash in this case if the total number of
1878 votes for any parameter exceeded the number of active voters,
1879 but would let it pass otherwise. Partial fix for bug 5786; bugfix
1883 - Rate-limit log messages when asked to connect anonymously to
1884 a private address. When these hit, they tended to hit fast and
1885 often. Also, don't bother trying to connect to addresses that we
1886 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1887 reply makes us think we have been lied to, even when the address the
1888 client tried to connect to was "localhost." Resolves ticket 2822.
1889 - Allow packagers to insert an extra string in server descriptor
1890 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
1891 Resolves the rest of ticket 2988.
1892 - Raise the threshold of server descriptors needed (75%) and exit
1893 server descriptors needed (50%) before we will declare ourselves
1894 bootstrapped. This will make clients start building circuits a
1895 little later, but makes the initially constructed circuits less
1896 skewed and less in conflict with further directory fetches. Fixes
1898 - Close any connection that sends unrecognized junk before the
1899 handshake. Solves an issue noted in bug 4369.
1900 - Improve log messages about managed transports. Resolves ticket 5070.
1901 - Tag a bridge's descriptor as "never to be sent unencrypted".
1902 This shouldn't matter, since bridges don't open non-anonymous
1903 connections to the bridge authority and don't allow unencrypted
1904 directory connections from clients, but we might as well make
1905 sure. Closes bug 5139.
1906 - Expose our view of whether we have gone dormant to the controller,
1907 via a new "GETINFO dormant" value. Torbutton and other controllers
1908 can use this to avoid doing periodic requests through Tor while
1909 it's dormant (bug 4718). Fixes bug 5954.
1910 - Tell GCC and Clang to check for any errors in format strings passed
1911 to the tor_v*(print|scan)f functions.
1912 - Update to the May 1 2012 Maxmind GeoLite Country database.
1914 o Minor bugfixes (already included in 0.2.2.36):
1915 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1916 Fixes bug 5346; bugfix on 0.0.8pre3.
1917 - Correct parsing of certain date types in parse_http_time().
1918 Without this patch, If-Modified-Since would behave
1919 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1920 Esteban Manchado Velázques.
1921 - Make our number-parsing functions always treat too-large values
1922 as an error, even when those values exceed the width of the
1923 underlying type. Previously, if the caller provided these
1924 functions with minima or maxima set to the extreme values of the
1925 underlying integer type, these functions would return those
1926 values on overflow rather than treating overflow as an error.
1927 Fixes part of bug 5786; bugfix on 0.0.9.
1928 - If we hit the error case where routerlist_insert() replaces an
1929 existing (old) server descriptor, make sure to remove that
1930 server descriptor from the old_routers list. Fix related to bug
1931 1776. Bugfix on 0.2.2.18-alpha.
1932 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1933 circuits. Fixes issue 5259.
1935 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
1936 - Prevent a null-pointer dereference when receiving a data cell
1937 for a nonexistent stream when the circuit in question has an
1938 empty deliver window. We don't believe this is triggerable,
1939 since we don't currently allow deliver windows to become empty,
1940 but the logic is tricky enough that it's better to make the code
1941 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1942 - Fix a memory leak when trying to launch a DNS request when the
1943 network is disabled or the nameservers are unconfigurable. Fixes
1944 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
1945 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
1946 - Don't hold a Windows file handle open for every file mapping;
1947 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1949 - Avoid O(n^2) performance characteristics when parsing a large
1950 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1951 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1952 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1954 - Make our replacement implementation of strtok_r() compatible with
1955 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1956 bugfix on 0.2.2.1-alpha.
1957 - Fix a NULL-pointer dereference on a badly formed
1958 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
1959 bugfix on 0.2.2.9-alpha.
1960 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1961 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1962 - Defensively refactor rend_mid_rendezvous() so that protocol
1963 violations and length checks happen in the beginning. Fixes
1965 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1966 that IPv6 stuff will compile on MSVC, and compilation issues
1967 will be easier to track down. Fixes bug 5861.
1969 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
1970 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1971 resource exhaustion, so that clients can adjust their load to
1972 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1973 started using END_STREAM_REASON_RESOURCELIMIT.
1974 - Don't check for whether the address we're using for outbound
1975 connections has changed until after the outbound connection has
1976 completed. On Windows, getsockname() doesn't succeed until the
1977 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1978 - If the configuration tries to set MyFamily on a bridge, refuse to
1979 do so, and warn about the security implications. Fixes bug 4657;
1980 bugfix on 0.2.0.3-alpha.
1981 - If the client fails to set a reasonable set of ciphersuites
1982 during its v2 handshake renegotiation, allow the renegotiation to
1983 continue nevertheless (i.e. send all the required certificates).
1984 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1985 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1986 option is set to 0 (which Vidalia version 0.2.16 now does when
1987 a SAVECONF attempt fails), perform other actions that SIGHUP
1988 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1990 - If we fail to write a microdescriptor to the disk cache, do not
1991 continue replacing the old microdescriptor file. Fixes bug 2954;
1992 bugfix on 0.2.2.6-alpha.
1993 - Exit nodes don't need to fetch certificates for authorities that
1994 they don't recognize; only directory authorities, bridges,
1995 and caches need to do that. Fixes part of bug 2297; bugfix on
1997 - Correctly handle checking the permissions on the parent
1998 directory of a control socket in the root directory. Bug found
1999 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2001 - When told to add a bridge with the same digest as a preexisting
2002 bridge but a different addr:port, change the addr:port as
2003 requested. Previously we would not notice the change. Fixes half
2004 of bug 5603; fix on 0.2.2.26-beta.
2005 - End AUTHCHALLENGE error messages (in the control protocol) with
2006 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2008 o Minor bugfixes (on 0.2.3.x):
2009 - Turn an assertion (that the number of handshakes received as a
2010 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2012 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2013 we had reversed them when the answer was cached.) Fixes bug
2014 5723; bugfix on 0.2.3.1-alpha.
2015 - Work correctly on Linux systems with accept4 support advertised in
2016 their headers, but without accept4 support in the kernel. Fix
2017 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2018 - When told to add a bridge with the same addr:port as a preexisting
2019 bridge but a different transport, change the transport as
2020 requested. Previously we would not notice the change. Fixes half
2021 of bug 5603; fix on 0.2.3.2-alpha.
2022 - Avoid a "double-reply" warning when replying to a SOCKS request
2023 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2024 bugfix on 0.2.3.4-alpha.
2025 - Fix a bug where a bridge authority crashes if it has seen no
2026 directory requests when it's time to write statistics to disk.
2027 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2029 - Don't try to open non-control listeners when DisableNetwork is set.
2030 Previously, we'd open all listeners, then immediately close them.
2031 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2032 - Don't abort the managed proxy protocol if the managed proxy
2033 sends us an unrecognized line; ignore it instead. Fixes bug
2034 5910; bugfix on 0.2.3.9-alpha.
2035 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2036 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2037 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2038 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2039 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2040 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2041 - Resolve numerous small warnings and build issues with MSVC. Resolves
2044 o Documentation fixes:
2045 - Improve the manual's documentation for the NT Service command-line
2046 options. Addresses ticket 3964.
2047 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2048 - Document the changes to the ORPort and DirPort options, and the
2049 fact that {OR/Dir}ListenAddress is now unnecessary (and
2050 therefore deprecated). Resolves ticket 5597.
2053 - Remove the torrc.bridge file: we don't use it for anything, and
2054 it had become badly desynchronized from torrc.sample. Resolves
2058 Changes in version 0.2.2.36 - 2012-05-24
2059 Tor 0.2.2.36 updates the addresses for two of the eight directory
2060 authorities, fixes some potential anonymity and security issues,
2061 and fixes several crash bugs.
2063 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2064 known flaws, and nobody should be using them. You should upgrade. If
2065 you're using a Linux or BSD and its packages are obsolete, stop using
2066 those packages and upgrade anyway.
2068 o Directory authority changes:
2069 - Change IP address for maatuska (v3 directory authority).
2070 - Change IP address for ides (v3 directory authority), and rename
2074 - When building or running with any version of OpenSSL earlier
2075 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2076 versions have a bug (CVE-2011-4576) in which their block cipher
2077 padding includes uninitialized data, potentially leaking sensitive
2078 information to any peer with whom they make a SSLv3 connection. Tor
2079 does not use SSL v3 by default, but a hostile client or server
2080 could force an SSLv3 connection in order to gain information that
2081 they shouldn't have been able to get. The best solution here is to
2082 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2083 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2084 to make sure that the bug can't happen.
2085 - Never use a bridge or a controller-supplied node as an exit, even
2086 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2087 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2088 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2089 - Only build circuits if we have a sufficient threshold of the total
2090 descriptors that are marked in the consensus with the "Exit"
2091 flag. This mitigates an attack proposed by wanoskarnet, in which
2092 all of a client's bridges collude to restrict the exit nodes that
2093 the client knows about. Fixes bug 5343.
2094 - Provide controllers with a safer way to implement the cookie
2095 authentication mechanism. With the old method, if another locally
2096 running program could convince a controller that it was the Tor
2097 process, then that program could trick the controller into telling
2098 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2099 authentication method uses a challenge-response approach to prevent
2100 this attack. Fixes bug 5185; implements proposal 193.
2103 - Avoid logging uninitialized data when unable to decode a hidden
2104 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2105 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2106 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2108 - Fix builds when the path to sed, openssl, or sha1sum contains
2109 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2111 - Correct our replacements for the timeradd() and timersub() functions
2112 on platforms that lack them (for example, Windows). The timersub()
2113 function is used when expiring circuits, while timeradd() is
2114 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2115 bugfix on 0.2.2.24-alpha.
2116 - Fix the SOCKET_OK test that we use to tell when socket
2117 creation fails so that it works on Win64. Fixes part of bug 4533;
2118 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2121 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2122 Fixes bug 5346; bugfix on 0.0.8pre3.
2123 - Make our number-parsing functions always treat too-large values
2124 as an error, even when those values exceed the width of the
2125 underlying type. Previously, if the caller provided these
2126 functions with minima or maxima set to the extreme values of the
2127 underlying integer type, these functions would return those
2128 values on overflow rather than treating overflow as an error.
2129 Fixes part of bug 5786; bugfix on 0.0.9.
2130 - Older Linux kernels erroneously respond to strange nmap behavior
2131 by having accept() return successfully with a zero-length
2132 socket. When this happens, just close the connection. Previously,
2133 we would try harder to learn the remote address: but there was
2134 no such remote address to learn, and our method for trying to
2135 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2136 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2137 - Correct parsing of certain date types in parse_http_time().
2138 Without this patch, If-Modified-Since would behave
2139 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2140 Esteban Manchado Velázques.
2141 - Change the BridgePassword feature (part of the "bridge community"
2142 design, which is not yet implemented) to use a time-independent
2143 comparison. The old behavior might have allowed an adversary
2144 to use timing to guess the BridgePassword value. Fixes bug 5543;
2145 bugfix on 0.2.0.14-alpha.
2146 - Detect and reject certain misformed escape sequences in
2147 configuration values. Previously, these values would cause us
2148 to crash if received in a torrc file or over an authenticated
2149 control port. Bug found by Esteban Manchado Velázquez, and
2150 independently by Robert Connolly from Matta Consulting who further
2151 noted that it allows a post-authentication heap overflow. Patch
2152 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2153 bugfix on 0.2.0.16-alpha.
2154 - Fix a compile warning when using the --enable-openbsd-malloc
2155 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2156 - During configure, detect when we're building with clang version
2157 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2158 CFLAGS. clang doesn't support them yet.
2159 - When sending an HTTP/1.1 proxy request, include a Host header.
2160 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2161 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2162 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2163 - If we hit the error case where routerlist_insert() replaces an
2164 existing (old) server descriptor, make sure to remove that
2165 server descriptor from the old_routers list. Fix related to bug
2166 1776. Bugfix on 0.2.2.18-alpha.
2168 o Minor bugfixes (documentation and log messages):
2169 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2170 Fixes bug 4856; bugfix on Tor 0.0.6.
2171 - Update "ClientOnly" man page entry to explain that there isn't
2172 really any point to messing with it. Resolves ticket 5005.
2173 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2174 directory authority option (introduced in Tor 0.2.2.34).
2175 - Downgrade the "We're missing a certificate" message from notice
2176 to info: people kept mistaking it for a real problem, whereas it
2177 is seldom the problem even when we are failing to bootstrap. Fixes
2178 bug 5067; bugfix on 0.2.0.10-alpha.
2179 - Correctly spell "connect" in a log message on failure to create a
2180 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2181 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2182 circuits. Fixes issue 5259.
2185 - Directory authorities now reject versions of Tor older than
2186 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2187 inclusive. These versions accounted for only a small fraction of
2188 the Tor network, and have numerous known security issues. Resolves
2190 - Update to the May 1 2012 Maxmind GeoLite Country database.
2193 - When sending or relaying a RELAY_EARLY cell, we used to convert
2194 it to a RELAY cell if the connection was using the v1 link
2195 protocol. This was a workaround for older versions of Tor, which
2196 didn't handle RELAY_EARLY cells properly. Now that all supported
2197 versions can handle RELAY_EARLY cells, and now that we're enforcing
2198 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2199 remove this workaround. Addresses bug 4786.
2202 Changes in version 0.2.3.15-alpha - 2012-04-30
2203 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2204 the development branch build on Windows again.
2206 o Minor bugfixes (on 0.2.2.x and earlier):
2207 - Make sure that there are no unhandled pending TLS errors before
2208 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2209 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2210 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2211 - Fix an assert that directory authorities could trigger on sighup
2212 during some configuration state transitions. We now don't treat
2213 it as a fatal error when the new descriptor we just generated in
2214 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2215 - After we pick a directory mirror, we would refuse to use it if
2216 it's in our ExcludeExitNodes list, resulting in mysterious failures
2217 to bootstrap for people who just wanted to avoid exiting from
2218 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2219 - When building with --enable-static-tor on OpenBSD, do not
2220 erroneously attempt to link -lrt. Fixes bug 5103.
2222 o Minor bugfixes (on 0.2.3.x):
2223 - When Tor is built with kernel headers from a recent (last few
2224 years) Linux kernel, do not fail to run on older (pre-2.6.28
2225 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2226 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2228 - Fix compilation with miniupnpc version 1.6; patch from
2229 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2230 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2231 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2232 - Fix compilation on platforms without unistd.h, or where environ
2233 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2236 - Directory authorities are now a little more lenient at accepting
2237 older router descriptors, or newer router descriptors that don't
2238 make big changes. This should help ameliorate past and future
2239 issues where routers think they have uploaded valid descriptors,
2240 but the authorities don't think so. Fix for ticket 2479.
2241 - Make the code that clients use to detect an address change be
2242 IPv6-aware, so that it won't fill clients' logs with error
2243 messages when trying to get the IPv4 address of an IPv6
2244 connection. Implements ticket 5537.
2247 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2248 authorities needed to use it for a while to keep the network working
2249 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2250 that was six months ago. As of now, it should no longer be needed
2254 Changes in version 0.2.3.14-alpha - 2012-04-23
2255 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2256 candidate. It also dramatically speeds up AES: fast relays should
2257 consider switching to the newer OpenSSL library.
2259 o Directory authority changes:
2260 - Change IP address for ides (v3 directory authority), and rename
2264 - Avoid logging uninitialized data when unable to decode a hidden
2265 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2266 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2267 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2269 - If authorities are unable to get a v2 consensus document from other
2270 directory authorities, they no longer fall back to fetching
2271 them from regular directory caches. Fixes bug 5635; bugfix on
2272 0.2.2.26-beta, where routers stopped downloading v2 consensus
2274 - When we start a Tor client with a normal consensus already cached,
2275 be willing to download a microdescriptor consensus. Fixes bug 4011;
2276 fix on 0.2.3.1-alpha.
2278 o Major features (performance):
2279 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2280 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2281 vectorized AES implementations as appropriate. These can be much,
2282 much faster than other AES implementations.
2284 o Minor bugfixes (0.2.2.x and earlier):
2285 - Don't launch more than 10 service-side introduction-point circuits
2286 for a hidden service in five minutes. Previously, we would consider
2287 launching more introduction-point circuits if at least one second
2288 had passed without any introduction-point circuits failing. Fixes
2289 bug 4607; bugfix on 0.0.7pre1.
2290 - Change the BridgePassword feature (part of the "bridge community"
2291 design, which is not yet implemented) to use a time-independent
2292 comparison. The old behavior might have allowed an adversary
2293 to use timing to guess the BridgePassword value. Fixes bug 5543;
2294 bugfix on 0.2.0.14-alpha.
2295 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2296 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2297 - When sending an HTTP/1.1 proxy request, include a Host header.
2298 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2299 - Don't log that we have "decided to publish new relay descriptor"
2300 unless we are actually publishing a descriptor. Fixes bug 3942;
2301 bugfix on 0.2.2.28-beta.
2303 o Minor bugfixes (0.2.3.x):
2304 - Fix a bug where a bridge authority crashes (on a failed assert)
2305 if it has seen no directory requests when it's time to write
2306 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2307 - Fix bug stomping on ORPort option NoListen and ignoring option
2308 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2309 - In the testsuite, provide a large enough buffer in the tor_sscanf
2310 unit test. Otherwise we'd overrun that buffer and crash during
2311 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2313 - Make sure we create the keys directory if it doesn't exist and we're
2314 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2315 5572; bugfix on 0.2.3.13-alpha.
2316 - Fix a small memory leak when trying to decode incorrect base16
2317 authenticator during SAFECOOKIE authentication. Found by
2318 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2321 - Add more information to a log statement that might help track down
2322 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2323 non-IP address" messages (or any Bug messages, for that matter!),
2324 please let us know about it.
2325 - Relays now understand an IPv6 address when they get one from a
2326 directory server. Resolves ticket 4875.
2327 - Resolve IPv6 addresses in bridge and entry statistics to country
2328 code "??" which means we at least count them. Resolves ticket 5053;
2329 improves on 0.2.3.9-alpha.
2330 - Update to the April 3 2012 Maxmind GeoLite Country database.
2331 - Begin a doc/state-contents.txt file to explain the contents of
2332 the Tor state file. Fixes bug 2987.
2334 o Default torrc changes:
2335 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2336 port on 9050 by default anyway, so this should not change anything
2338 - Stop mentioning the deprecated *ListenAddress options in
2339 torrc.sample. Fixes bug 5438.
2340 - Document unit of bandwidth related options in sample torrc.
2344 - The "torify" script no longer supports the "tsocks" socksifier
2345 tool, since tsocks doesn't support DNS and UDP right for Tor.
2346 Everyone should be using torsocks instead. Fixes bugs 3530 and
2347 5180. Based on a patch by "ugh".
2350 - Change the symmetric cipher interface so that creating and
2351 initializing a stream cipher are no longer separate functions.
2352 - Remove all internal support for unpadded RSA. We never used it, and
2353 it would be a bad idea to start.
2356 Changes in version 0.2.3.13-alpha - 2012-03-26
2357 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2358 in managed pluggable transports, as well as providing other cleanups
2359 that get us closer to a release candidate.
2361 o Directory authority changes:
2362 - Change IP address for maatuska (v3 directory authority).
2365 - Provide controllers with a safer way to implement the cookie
2366 authentication mechanism. With the old method, if another locally
2367 running program could convince a controller that it was the Tor
2368 process, then that program could trick the controller into telling
2369 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2370 authentication method uses a challenge-response approach to prevent
2371 this attack. Fixes bug 5185, implements proposal 193.
2372 - Never use a bridge or a controller-supplied node as an exit, even
2373 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2374 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2375 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2376 - Only build circuits if we have a sufficient threshold of the total
2377 descriptors that are marked in the consensus with the "Exit"
2378 flag. This mitigates an attack proposed by wanoskarnet, in which
2379 all of a client's bridges collude to restrict the exit nodes that
2380 the client knows about. Fixes bug 5343.
2382 o Major bugfixes (on Tor 0.2.3.x):
2383 - Avoid an assert when managed proxies like obfsproxy are configured,
2384 and we receive HUP signals or setconf attempts too rapidly. This
2385 situation happens most commonly when Vidalia tries to attach to
2386 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2387 bugfix on 0.2.3.6-alpha.
2388 - Fix a relay-side pluggable transports bug where managed proxies were
2389 unreachable from the Internet, because Tor asked them to bind on
2390 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2391 - Stop discarding command-line arguments when TestingTorNetwork
2392 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2393 0.2.3.9-alpha, where task 4552 added support for two layers of
2395 - Resume allowing the unit tests to run in gdb. This was accidentally
2396 made impossible when the DisableDebuggerAttachment option was
2397 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2398 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2399 0.2.3.11-alpha. Reported by Anthony G. Basile.
2401 o Minor bugfixes (on 0.2.2.x and earlier):
2402 - Ensure we don't cannibalize circuits that are longer than three hops
2403 already, so we don't end up making circuits with 5 or more
2404 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2405 0.1.0.1-rc which introduced cannibalization.
2406 - Detect and reject certain misformed escape sequences in
2407 configuration values. Previously, these values would cause us
2408 to crash if received in a torrc file or over an authenticated
2409 control port. Bug found by Esteban Manchado Velázquez, and
2410 independently by Robert Connolly from Matta Consulting who further
2411 noted that it allows a post-authentication heap overflow. Patch
2412 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2413 bugfix on 0.2.0.16-alpha.
2414 - Fix a compile warning when using the --enable-openbsd-malloc
2415 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2416 - Directory caches no longer refuse to clean out descriptors because
2417 of missing v2 networkstatus documents, unless they're configured
2418 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2419 0.2.2.26-beta. Patch by Daniel Bryg.
2420 - Update to the latest version of the tinytest unit testing framework.
2421 This includes a couple of bugfixes that can be relevant for
2422 running forked unit tests on Windows, and removes all reserved
2425 o Minor bugfixes (on 0.2.3.x):
2426 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2427 4296; bugfix on 0.2.3.1-alpha.
2428 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2429 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2430 on 0.2.3.6-alpha. Patch by "frosty".
2431 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2432 option, so that the IP stack doesn't decide to use it for IPv4
2433 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2434 - Ensure that variables set in Tor's environment cannot override
2435 environment variables that Tor passes to a managed
2436 pluggable-transport proxy. Previously, Tor would pass every
2437 variable in its environment to managed proxies along with the new
2438 ones, in such a way that on many operating systems, the inherited
2439 environment variables would override those which Tor tried to
2440 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2441 bugfix on 0.2.3.9-alpha for Windows.
2444 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2445 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2446 - Update to the March 6 2012 Maxmind GeoLite Country database.
2449 Changes in version 0.2.3.12-alpha - 2012-02-13
2450 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2451 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2452 when Tor is configured to use a pluggable transport like obfsproxy.
2455 - Fix builds when the path to sed, openssl, or sha1sum contains
2456 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2458 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2459 connections. This change should allow busy exit relays to stop
2460 running out of available sockets as quickly. Fixes bug 4950;
2461 bugfix on 0.2.2.26-beta.
2462 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2463 would ask the bridge for microdescriptors, which are only supported
2464 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2465 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2466 - Properly set up obfsproxy's environment when in managed mode. The
2467 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2468 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2469 5076 and 5082; bugfix on 0.2.3.6-alpha.
2472 - Use the dead_strip option when building Tor on OS X. This reduces
2473 binary size by almost 19% when linking openssl and libevent
2474 statically, which we do for Tor Browser Bundle.
2475 - Fix broken URLs in the sample torrc file, and tell readers about
2476 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2477 PublishServerDescriptor options. Addresses bug 4652.
2478 - Update to the February 7 2012 Maxmind GeoLite Country database.
2481 - Downgrade the "We're missing a certificate" message from notice
2482 to info: people kept mistaking it for a real problem, whereas it
2483 is seldom the problem even when we are failing to bootstrap. Fixes
2484 bug 5067; bugfix on 0.2.0.10-alpha.
2485 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2486 managed pluggable transport server proxy's environment.
2487 Previously, we would put it there, even though Tor doesn't
2488 implement an 'extended server port' yet, and even though Tor
2489 almost certainly isn't listening at that address. For now, we set
2490 it to an empty string to avoid crashing older obfsproxies. Bugfix
2492 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2493 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2494 0.2.3.1-alpha. Bug reported by Scott Bennett.
2495 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2496 bugfix on 0.2.3.11-alpha.
2497 - Update "ClientOnly" man page entry to explain that there isn't
2498 really any point to messing with it. Resolves ticket 5005.
2499 - Use the correct CVE number for CVE-2011-4576 in our comments and
2500 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2503 o Code simplifications and refactoring:
2504 - Use the _WIN32 macro throughout our code to detect Windows.
2505 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2509 Changes in version 0.2.3.11-alpha - 2012-01-22
2510 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2511 the last step of the plan to limit maximum circuit length, includes
2512 a wide variety of hidden service performance and correctness fixes,
2513 works around an OpenSSL security flaw if your distro is too stubborn
2514 to upgrade, and fixes a bunch of smaller issues.
2517 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2518 part of "Proposal 110: Avoiding infinite length circuits" by
2519 refusing all circuit-extend requests that do not use a relay_early
2520 cell. This change helps Tor resist a class of denial-of-service
2521 attacks by limiting the maximum circuit length.
2522 - Adjust the number of introduction points that a hidden service
2523 will try to maintain based on how long its introduction points
2524 remain in use and how many introductions they handle. Fixes
2526 - Try to use system facilities for enumerating local interface
2527 addresses, before falling back to our old approach (which was
2528 binding a UDP socket, and calling getsockname() on it). That
2529 approach was scaring OS X users whose draconian firewall
2530 software warned about binding to UDP sockets, regardless of
2531 whether packets were sent. Now we try to use getifaddrs(),
2532 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2533 system supports. Resolves ticket 1827.
2535 o Major security workaround:
2536 - When building or running with any version of OpenSSL earlier
2537 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2538 versions have a bug (CVE-2011-4576) in which their block cipher
2539 padding includes uninitialized data, potentially leaking sensitive
2540 information to any peer with whom they make a SSLv3 connection. Tor
2541 does not use SSL v3 by default, but a hostile client or server
2542 could force an SSLv3 connection in order to gain information that
2543 they shouldn't have been able to get. The best solution here is to
2544 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2545 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2546 to make sure that the bug can't happen.
2549 - Fix the SOCKET_OK test that we use to tell when socket
2550 creation fails so that it works on Win64. Fixes part of bug 4533;
2551 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2552 - Correct our replacements for the timeradd() and timersub() functions
2553 on platforms that lack them (for example, Windows). The timersub()
2554 function is used when expiring circuits, while timeradd() is
2555 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2556 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2557 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2558 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2559 bug at runtime, not compile time, because some distributions hack
2560 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2561 on 0.2.3.9-alpha. Found by Pascal.
2563 o Minor features (controller):
2564 - Use absolute path names when reporting the torrc filename in the
2565 control protocol, so a controller can more easily find the torrc
2566 file. Resolves bug 1101.
2567 - Extend the control protocol to report flags that control a circuit's
2568 path selection in CIRC events and in replies to 'GETINFO
2569 circuit-status'. Implements part of ticket 2411.
2570 - Extend the control protocol to report the hidden service address
2571 and current state of a hidden-service-related circuit in CIRC
2572 events and in replies to 'GETINFO circuit-status'. Implements part
2574 - When reporting the path to the cookie file to the controller,
2575 give an absolute path. Resolves ticket 4881.
2576 - Allow controllers to request an event notification whenever a
2577 circuit is cannibalized or its purpose is changed. Implements
2578 part of ticket 3457.
2579 - Include the creation time of a circuit in CIRC and CIRC2
2580 control-port events and the list produced by the 'GETINFO
2581 circuit-status' control-port command.
2583 o Minor features (directory authorities):
2584 - Directory authorities now reject versions of Tor older than
2585 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2586 inclusive. These versions accounted for only a small fraction of
2587 the Tor network, and have numerous known security issues. Resolves
2589 - Authority operators can now vote for all relays in a given
2590 set of countries to be BadDir/BadExit/Invalid/Rejected.
2591 - Provide two consensus parameters (FastFlagMinThreshold and
2592 FastFlagMaxThreshold) to control the range of allowable bandwidths
2593 for the Fast directory flag. These allow authorities to run
2594 experiments on appropriate requirements for being a "Fast" node.
2595 The AuthDirFastGuarantee config value still applies. Implements
2597 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2598 directory authority option (introduced in Tor 0.2.2.34).
2600 o Minor features (other):
2601 - Don't disable the DirPort when we cannot exceed our AccountingMax
2602 limit during this interval because the effective bandwidthrate is
2603 low enough. This is useful in a situation where AccountMax is only
2604 used as an additional safeguard or to provide statistics.
2605 - Prepend an informative header to generated dynamic_dh_params files.
2606 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2607 EntryNodes will have no effect. Resolves issue 2571.
2608 - Log more useful messages when we fail to disable debugger
2610 - Log which authority we're missing votes from when we go to fetch
2611 them from the other auths.
2612 - Log (at debug level) whenever a circuit's purpose is changed.
2613 - Add missing documentation for the MaxClientCircuitsPending,
2614 UseMicrodescriptors, UserspaceIOCPBuffers, and
2615 _UseFilteringSSLBufferevents options, all introduced during
2617 - Update to the January 3 2012 Maxmind GeoLite Country database.
2619 o Minor bugfixes (hidden services):
2620 - Don't close hidden service client circuits which have almost
2621 finished connecting to their destination when they reach
2622 the normal circuit-build timeout. Previously, we would close
2623 introduction circuits which are waiting for an acknowledgement
2624 from the introduction point, and rendezvous circuits which have
2625 been specified in an INTRODUCE1 cell sent to a hidden service,
2626 after the normal CBT. Now, we mark them as 'timed out', and launch
2627 another rendezvous attempt in parallel. This behavior change can
2628 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2629 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2630 - Don't close hidden-service-side rendezvous circuits when they
2631 reach the normal circuit-build timeout. This behaviour change can
2632 be disabled using the new
2633 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2634 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2635 - Make sure we never mark the wrong rendezvous circuit as having
2636 had its introduction cell acknowleged by the introduction-point
2637 relay. Previously, when we received an INTRODUCE_ACK cell on a
2638 client-side hidden-service introduction circuit, we might have
2639 marked a rendezvous circuit other than the one we specified in
2640 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2641 a warning message and interfered with the hidden service
2642 connection-establishment process. Fixes bug 4759; bugfix on
2643 0.2.3.3-alpha, when we added the stream-isolation feature which
2644 might cause Tor to open multiple rendezvous circuits for the same
2646 - Don't trigger an assertion failure when we mark a new client-side
2647 hidden-service introduction circuit for close during the process
2648 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2651 o Minor bugfixes (log messages):
2652 - Correctly spell "connect" in a log message on failure to create a
2653 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2655 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2656 Fixes bug 4856; bugfix on Tor 0.0.6.
2657 - Fix the log message describing how we work around discovering
2658 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2659 4837; bugfix on 0.2.2.9-alpha.
2660 - When logging about a disallowed .exit name, do not also call it
2661 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2663 o Minor bugfixes (build fixes):
2664 - During configure, detect when we're building with clang version
2665 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2666 CFLAGS. clang doesn't support them yet.
2667 - During configure, search for library containing cos function as
2668 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2669 against libm was hard-coded before. Fixes the first part of bug
2670 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2672 - Detect attempts to build Tor on (as yet hypothetical) versions
2673 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2674 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2675 - Preprocessor directives should not be put inside the arguments
2676 of a macro. This would break compilation with GCC releases prior
2677 to version 3.3. We would never recommend such an old GCC version,
2678 but it is apparently required for binary compatibility on some
2679 platforms (namely, certain builds of Haiku). Fixes the other part
2680 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2683 o Minor bugfixes (other):
2684 - Older Linux kernels erroneously respond to strange nmap behavior
2685 by having accept() return successfully with a zero-length
2686 socket. When this happens, just close the connection. Previously,
2687 we would try harder to learn the remote address: but there was
2688 no such remote address to learn, and our method for trying to
2689 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2690 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2691 - Fix null-pointer access that could occur if TLS allocation failed.
2692 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2693 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2694 accidentally been reverted.
2695 - Fix our implementation of crypto_random_hostname() so it can't
2696 overflow on ridiculously large inputs. (No Tor version has ever
2697 provided this kind of bad inputs, but let's be correct in depth.)
2698 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2699 - Find more places in the code that should have been testing for
2700 invalid sockets using the SOCKET_OK macro. Required for a fix
2701 for bug 4533. Bugfix on 0.2.2.28-beta.
2702 - Fix an assertion failure when, while running with bufferevents, a
2703 connection finishes connecting after it is marked for close, but
2704 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2705 - test_util_spawn_background_ok() hardcoded the expected value
2706 for ENOENT to 2. This isn't portable as error numbers are
2707 platform specific, and particularly the hurd has ENOENT at
2708 0x40000002. Construct expected string at runtime, using the correct
2709 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2710 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2711 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2712 - Use an appropriate-width type for sockets in tor-fw-helper on
2713 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2716 - When sending or relaying a RELAY_EARLY cell, we used to convert
2717 it to a RELAY cell if the connection was using the v1 link
2718 protocol. This was a workaround for older versions of Tor, which
2719 didn't handle RELAY_EARLY cells properly. Now that all supported
2720 versions can handle RELAY_EARLY cells, and now that we're enforcing
2721 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2722 remove this workaround. Addresses bug 4786.
2724 o Code simplifications and refactoring:
2725 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2726 own homebrewed ssl_state_to_string() replacement. Patch from
2727 Emile Snyder. Fixes bug 4653.
2728 - Use macros to indicate OpenSSL versions, so we don't need to worry
2729 about accidental hexadecimal bit shifts.
2730 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2732 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2733 - Use the smartlist_add_asprintf() alias more consistently.
2734 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2735 invalid value, rather than just -1.
2736 - Rename a handful of old identifiers, mostly related to crypto
2737 structures and crypto functions. By convention, our "create an
2738 object" functions are called "type_new()", our "free an object"
2739 functions are called "type_free()", and our types indicate that
2740 they are types only with a final "_t". But a handful of older
2741 types and functions broke these rules, with function names like
2742 "type_create" or "subsystem_op_type", or with type names like
2746 Changes in version 0.2.3.10-alpha - 2011-12-16
2747 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
2748 Tor's buffers code. Absolutely everybody should upgrade.
2750 The bug relied on an incorrect calculation when making data continuous
2751 in one of our IO buffers, if the first chunk of the buffer was
2752 misaligned by just the wrong amount. The miscalculation would allow an
2753 attacker to overflow a piece of heap-allocated memory. To mount this
2754 attack, the attacker would need to either open a SOCKS connection to
2755 Tor's SocksPort (usually restricted to localhost), or target a Tor
2756 instance configured to make its connections through a SOCKS proxy
2757 (which Tor does not do by default).
2759 Good security practice requires that all heap-overflow bugs should be
2760 presumed to be exploitable until proven otherwise, so we are treating
2761 this as a potential code execution attack. Please upgrade immediately!
2762 This bug does not affect bufferevents-based builds of Tor. Special
2763 thanks to "Vektor" for reporting this issue to us!
2765 This release also contains a few minor bugfixes for issues discovered
2769 - Fix a heap overflow bug that could occur when trying to pull
2770 data into the first chunk of a buffer, when that chunk had
2771 already had some data drained from it. Fixes CVE-2011-2778;
2772 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2775 - If we can't attach streams to a rendezvous circuit when we
2776 finish connecting to a hidden service, clear the rendezvous
2777 circuit's stream-isolation state and try to attach streams
2778 again. Previously, we cleared rendezvous circuits' isolation
2779 state either too early (if they were freshly built) or not at all
2780 (if they had been built earlier and were cannibalized). Bugfix on
2781 0.2.3.3-alpha; fixes bug 4655.
2782 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
2783 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
2784 - Fix an assertion failure when a relay with accounting enabled
2785 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
2788 - Update to the December 6 2011 Maxmind GeoLite Country database.
2791 Changes in version 0.2.2.35 - 2011-12-16
2792 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
2793 buffers code. Absolutely everybody should upgrade.
2795 The bug relied on an incorrect calculation when making data continuous
2796 in one of our IO buffers, if the first chunk of the buffer was
2797 misaligned by just the wrong amount. The miscalculation would allow an
2798 attacker to overflow a piece of heap-allocated memory. To mount this
2799 attack, the attacker would need to either open a SOCKS connection to
2800 Tor's SocksPort (usually restricted to localhost), or target a Tor
2801 instance configured to make its connections through a SOCKS proxy
2802 (which Tor does not do by default).
2804 Good security practice requires that all heap-overflow bugs should be
2805 presumed to be exploitable until proven otherwise, so we are treating
2806 this as a potential code execution attack. Please upgrade immediately!
2807 This bug does not affect bufferevents-based builds of Tor. Special
2808 thanks to "Vektor" for reporting this issue to us!
2810 Tor 0.2.2.35 also fixes several bugs in previous versions, including
2811 crash bugs for unusual configurations, and a long-term bug that
2812 would prevent Tor from starting on Windows machines with draconian
2815 With this release, we remind everyone that 0.2.0.x has reached its
2816 formal end-of-life. Those Tor versions have many known flaws, and
2817 nobody should be using them. You should upgrade -- ideally to the
2818 0.2.2.x series. If you're using a Linux or BSD and its packages are
2819 obsolete, stop using those packages and upgrade anyway.
2821 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
2822 longer receive support after some time in early 2012.
2825 - Fix a heap overflow bug that could occur when trying to pull
2826 data into the first chunk of a buffer, when that chunk had
2827 already had some data drained from it. Fixes CVE-2011-2778;
2828 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2829 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2830 that it doesn't attempt to allocate a socketpair. This could cause
2831 some problems on Windows systems with overzealous firewalls. Fix for
2832 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2834 - If we mark an OR connection for close based on a cell we process,
2835 don't process any further cells on it. We already avoid further
2836 reads on marked-for-close connections, but now we also discard the
2837 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2838 which was the first version where we might mark a connection for
2839 close based on processing a cell on it.
2840 - Correctly sanity-check that we don't underflow on a memory
2841 allocation (and then assert) for hidden service introduction
2842 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2843 bugfix on 0.2.1.5-alpha.
2844 - Fix a memory leak when we check whether a hidden service
2845 descriptor has any usable introduction points left. Fixes bug
2846 4424. Bugfix on 0.2.2.25-alpha.
2847 - Don't crash when we're running as a relay and don't have a GeoIP
2848 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
2849 we've had in the 0.2.3.x branch already.
2850 - When running as a client, do not print a misleading (and plain
2851 wrong) log message that we're collecting "directory request"
2852 statistics: clients don't collect statistics. Also don't create a
2853 useless (because empty) stats file in the stats/ directory. Fixes
2854 bug 4353; bugfix on 0.2.2.34.
2857 - Detect failure to initialize Libevent. This fix provides better
2858 detection for future instances of bug 4457.
2859 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2860 function. This was eating up hideously large amounts of time on some
2861 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2862 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2863 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2865 - Don't warn about unused log_mutex in log.c when building with
2866 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2867 0.1.0.6-rc which introduced --disable-threads.
2868 - When configuring, starting, or stopping an NT service, stop
2869 immediately after the service configuration attempt has succeeded
2870 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2871 - When sending a NETINFO cell, include the original address
2872 received for the other side, not its canonical address. Found
2873 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2874 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
2875 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2876 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2877 occurred when a client tried to fetch a descriptor for a bridge
2878 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2879 - Backport fixes for a pair of compilation warnings on Windows.
2880 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
2881 - If we had ever tried to call tor_addr_to_str on an address of
2882 unknown type, we would have done a strdup on an uninitialized
2883 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2884 Reported by "troll_un".
2885 - Correctly detect and handle transient lookup failures from
2886 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2887 Reported by "troll_un".
2888 - Fix null-pointer access that could occur if TLS allocation failed.
2889 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2890 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2891 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2894 - Add two new config options for directory authorities:
2895 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2896 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2897 that is always sufficient to satisfy the bandwidth requirement for
2898 the Guard flag. Now it will be easier for researchers to simulate
2899 Tor networks with different values. Resolves ticket 4484.
2900 - When Tor ignores a hidden service specified in its configuration,
2901 include the hidden service's directory in the warning message.
2902 Previously, we would only tell the user that some hidden service
2903 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2904 - Update to the December 6 2011 Maxmind GeoLite Country database.
2906 o Packaging changes:
2907 - Make it easier to automate expert package builds on Windows,
2908 by removing an absolute path from makensis.exe command.
2911 Changes in version 0.2.1.32 - 2011-12-16
2912 Tor 0.2.1.32 backports important security and privacy fixes for
2913 oldstable. This release is intended only for package maintainers and
2914 others who cannot use the 0.2.2 stable series. All others should be
2915 using Tor 0.2.2.x or newer.
2917 The Tor 0.2.1.x series will reach formal end-of-life some time in
2918 early 2012; we will stop releasing patches for it then.
2920 o Major bugfixes (also included in 0.2.2.x):
2921 - Correctly sanity-check that we don't underflow on a memory
2922 allocation (and then assert) for hidden service introduction
2923 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2924 bugfix on 0.2.1.5-alpha.
2925 - Fix a heap overflow bug that could occur when trying to pull
2926 data into the first chunk of a buffer, when that chunk had
2927 already had some data drained from it. Fixes CVE-2011-2778;
2928 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2931 - Update to the December 6 2011 Maxmind GeoLite Country database.
2934 Changes in version 0.2.3.9-alpha - 2011-12-08
2935 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
2936 a "DisableNetwork" security feature that bundles can use to avoid
2937 touching the network until bridges are configured, moves forward on
2938 the pluggable transport design, fixes a flaw in the hidden service
2939 design that unnecessarily prevented clients with wrong clocks from
2940 reaching hidden services, and fixes a wide variety of other issues.
2943 - Clients can now connect to private bridges over IPv6. Bridges
2944 still need at least one IPv4 address in order to connect to
2945 other relays. Note that we don't yet handle the case where the
2946 user has two bridge lines for the same bridge (one IPv4, one
2947 IPv6). Implements parts of proposal 186.
2948 - New "DisableNetwork" config option to prevent Tor from launching any
2949 connections or accepting any connections except on a control port.
2950 Bundles and controllers can set this option before letting Tor talk
2951 to the rest of the network, for example to prevent any connections
2952 to a non-bridge address. Packages like Orbot can also use this
2953 option to instruct Tor to save power when the network is off.
2954 - Clients and bridges can now be configured to use a separate
2955 "transport" proxy. This approach makes the censorship arms race
2956 easier by allowing bridges to use protocol obfuscation plugins. It
2957 implements the "managed proxy" part of proposal 180 (ticket 3472).
2958 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2959 implementation. It makes AES_CTR about 7% faster than our old one
2960 (which was about 10% faster than the one OpenSSL used to provide).
2961 Resolves ticket 4526.
2962 - Add a "tor2web mode" for clients that want to connect to hidden
2963 services non-anonymously (and possibly more quickly). As a safety
2964 measure to try to keep users from turning this on without knowing
2965 what they are doing, tor2web mode must be explicitly enabled at
2966 compile time, and a copy of Tor compiled to run in tor2web mode
2967 cannot be used as a normal Tor client. Implements feature 2553.
2968 - Add experimental support for running on Windows with IOCP and no
2969 kernel-space socket buffers. This feature is controlled by a new
2970 "UserspaceIOCPBuffers" config option (off by default), which has
2971 no effect unless Tor has been built with support for bufferevents,
2972 is running on Windows, and has enabled IOCP. This may, in the long
2973 run, help solve or mitigate bug 98.
2974 - Use a more secure consensus parameter voting algorithm. Now at
2975 least three directory authorities or a majority of them must
2976 vote on a given parameter before it will be included in the
2977 consensus. Implements proposal 178.
2980 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2981 They used to check that the timestamp was within 30 minutes
2982 of their system clock, so they could cap the size of their
2983 replay-detection cache, but that approach unnecessarily refused
2984 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2985 the v3 intro-point protocol (the first one which sent a timestamp
2986 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2987 - Only use the EVP interface when AES acceleration is enabled,
2988 to avoid a 5-7% performance regression. Resolves issue 4525;
2989 bugfix on 0.2.3.8-alpha.
2991 o Privacy/anonymity features (bridge detection):
2992 - Make bridge SSL certificates a bit more stealthy by using random
2993 serial numbers, in the same fashion as OpenSSL when generating
2994 self-signed certificates. Implements ticket 4584.
2995 - Introduce a new config option "DynamicDHGroups", enabled by
2996 default, which provides each bridge with a unique prime DH modulus
2997 to be used during SSL handshakes. This option attempts to help
2998 against censors who might use the Apache DH modulus as a static
2999 identifier for bridges. Addresses ticket 4548.
3001 o Minor features (new/different config options):
3002 - New configuration option "DisableDebuggerAttachment" (on by default)
3003 to prevent basic debugging attachment attempts by other processes.
3004 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3005 - Allow MapAddress directives to specify matches against super-domains,
3006 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3007 Implements issue 933.
3008 - Slightly change behavior of "list" options (that is, config
3009 options that can appear more than once) when they appear both in
3010 torrc and on the command line. Previously, the command-line options
3011 would be appended to the ones from torrc. Now, the command-line
3012 options override the torrc options entirely. This new behavior
3013 allows the user to override list options (like exit policies and
3014 ports to listen on) from the command line, rather than simply
3015 appending to the list.
3016 - You can get the old (appending) command-line behavior for "list"
3017 options by prefixing the option name with a "+".
3018 - You can remove all the values for a "list" option from the command
3019 line without adding any new ones by prefixing the option name
3021 - Add experimental support for a "defaults" torrc file to be parsed
3022 before the regular torrc. Torrc options override the defaults file's
3023 options in the same way that the command line overrides the torrc.
3024 The SAVECONF controller command saves only those options which
3025 differ between the current configuration and the defaults file. HUP
3026 reloads both files. (Note: This is an experimental feature; its
3027 behavior will probably be refined in future 0.2.3.x-alpha versions
3028 to better meet packagers' needs.) Implements task 4552.
3031 - Try to make the introductory warning message that Tor prints on
3032 startup more useful for actually finding help and information.
3033 Resolves ticket 2474.
3034 - Running "make version" now displays the version of Tor that
3035 we're about to build. Idea from katmagic; resolves issue 4400.
3036 - Expire old or over-used hidden service introduction points.
3037 Required by fix for bug 3460.
3038 - Move the replay-detection cache for the RSA-encrypted parts of
3039 INTRODUCE2 cells to the introduction point data structures.
3040 Previously, we would use one replay-detection cache per hidden
3041 service. Required by fix for bug 3460.
3042 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3043 public key replay-detection cache from 60 minutes to 5 minutes. This
3044 replay-detection cache is now used only to detect multiple
3045 INTRODUCE2 cells specifying the same rendezvous point, so we can
3046 avoid launching multiple simultaneous attempts to connect to it.
3048 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3049 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3050 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3052 - Fix a minor formatting issue in one of tor-gencert's error messages.
3054 - Prevent a false positive from the check-spaces script, by disabling
3055 the "whitespace between function name and (" check for functions
3057 - Fix a log message suggesting that people contact a non-existent
3058 email address. Fixes bug 3448.
3059 - Fix null-pointer access that could occur if TLS allocation failed.
3060 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3061 - Report a real bootstrap problem to the controller on router
3062 identity mismatch. Previously we just said "foo", which probably
3063 made a lot of sense at the time. Fixes bug 4169; bugfix on
3065 - If we had ever tried to call tor_addr_to_str() on an address of
3066 unknown type, we would have done a strdup() on an uninitialized
3067 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3068 Reported by "troll_un".
3069 - Correctly detect and handle transient lookup failures from
3070 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3071 Reported by "troll_un".
3072 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3073 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3074 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3075 bug 4532; found by "troll_un".
3077 o Minor bugfixes (on Tor 0.2.3.x):
3078 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3080 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3081 circuit for use as a hidden service client's rendezvous point.
3082 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3083 with help from wanoskarnet.
3084 - Restore behavior of overriding SocksPort, ORPort, and similar
3085 options from the command line. Bugfix on 0.2.3.3-alpha.
3088 - Properly handle the case where the build-tree is not the same
3089 as the source tree when generating src/common/common_sha1.i,
3090 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3091 bugfix on 0.2.0.1-alpha.
3093 o Code simplifications, cleanups, and refactorings:
3094 - Remove the pure attribute from all functions that used it
3095 previously. In many cases we assigned it incorrectly, because the
3096 functions might assert or call impure functions, and we don't have
3097 evidence that keeping the pure attribute is worthwhile. Implements
3098 changes suggested in ticket 4421.
3099 - Remove some dead code spotted by coverity. Fixes cid 432.
3100 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3103 Changes in version 0.2.3.8-alpha - 2011-11-22
3104 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3105 socketpair-related bug that has been bothering Windows users. It adds
3106 support to serve microdescriptors to controllers, so Vidalia's network
3107 map can resume listing relays (once Vidalia implements its side),
3108 and adds better support for hardware AES acceleration. Finally, it
3109 starts the process of adjusting the bandwidth cutoff for getting the
3110 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3111 that tiny relays harm performance more than they help network capacity.
3114 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3115 that it doesn't attempt to allocate a socketpair. This could cause
3116 some problems on Windows systems with overzealous firewalls. Fix for
3117 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3119 - Correctly sanity-check that we don't underflow on a memory
3120 allocation (and then assert) for hidden service introduction
3121 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3122 bugfix on 0.2.1.5-alpha.
3123 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3124 flag. In the past few years the average relay speed has picked
3125 up, and while the "top 7/8 of the network get the Fast flag" and
3126 "all relays with 20KB or more of capacity get the Fast flag" rules
3127 used to have the same result, now the top 7/8 of the network has
3128 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3129 - Fix a rare assertion failure when checking whether a v0 hidden
3130 service descriptor has any usable introduction points left, and
3131 we don't have enough information to build a circuit to the first
3132 intro point named in the descriptor. The HS client code in
3133 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3134 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3135 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3136 - Make bridge authorities not crash when they are asked for their own
3137 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3138 - When running as a client, do not print a misleading (and plain
3139 wrong) log message that we're collecting "directory request"
3140 statistics: clients don't collect statistics. Also don't create a
3141 useless (because empty) stats file in the stats/ directory. Fixes
3142 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3145 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3146 for a relay by identity digest or nickname. Previously,
3147 microdescriptors were only available by their own digests, so a
3148 controller would have to ask for and parse the whole microdescriptor
3149 consensus in order to look up a single relay's microdesc. Fixes
3150 bug 3832; bugfix on 0.2.3.1-alpha.
3151 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3152 operations can use hardware acceleration (if present). Resolves
3155 o Minor bugfixes (on 0.2.2.x and earlier):
3156 - Detect failure to initialize Libevent. This fix provides better
3157 detection for future instances of bug 4457.
3158 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3159 function. This was eating up hideously large amounts of time on some
3160 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3161 - Don't warn about unused log_mutex in log.c when building with
3162 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3163 0.1.0.6-rc which introduced --disable-threads.
3164 - Allow manual 'authenticate' commands to the controller interface
3165 from netcat (nc) as well as telnet. We were rejecting them because
3166 they didn't come with the expected whitespace at the end of the
3167 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3168 - Fix some (not actually triggerable) buffer size checks in usage of
3169 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3171 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3172 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3173 - When configuring, starting, or stopping an NT service, stop
3174 immediately after the service configuration attempt has succeeded
3175 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3176 - When sending a NETINFO cell, include the original address
3177 received for the other side, not its canonical address. Found
3178 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3179 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3180 can pick them up when the tests aren't disabled. Bugfix on
3181 0.2.2.4-alpha which introduced tinytest.
3182 - Fix a memory leak when we check whether a hidden service
3183 descriptor has any usable introduction points left. Fixes bug
3184 4424. Bugfix on 0.2.2.25-alpha.
3185 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3186 occurred when a client tried to fetch a descriptor for a bridge
3187 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3189 o Minor bugfixes (on 0.2.3.x):
3190 - Make util unit tests build correctly with MSVC. Bugfix on
3191 0.2.3.3-alpha. Patch by Gisle Vanem.
3192 - Successfully detect AUTH_CHALLENGE cells with no recognized
3193 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3195 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3196 it should still send a NETINFO cell to allow the connection to
3197 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3199 - Log less loudly when we get an invalid authentication certificate
3200 from a source other than a directory authority: it's not unusual
3201 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3203 - Tolerate servers with more clock skew in their authentication
3204 certificates than previously. Fixes bug 4371; bugfix on
3206 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3207 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3210 - Add two new config options for directory authorities:
3211 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3212 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3213 that is always sufficient to satisfy the bandwidth requirement for
3214 the Guard flag. Now it will be easier for researchers to simulate
3215 Tor networks with different values. Resolves ticket 4484.
3216 - When Tor ignores a hidden service specified in its configuration,
3217 include the hidden service's directory in the warning message.
3218 Previously, we would only tell the user that some hidden service
3219 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3220 - When we fail to initialize Libevent, retry with IOCP disabled so we
3221 don't need to turn on multi-threading support in Libevent, which in
3222 turn requires a working socketpair(). This is a workaround for bug
3223 4457, which affects Libevent versions from 2.0.1-alpha through
3225 - Detect when we try to build on a platform that doesn't define
3226 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3227 - Update to the November 1 2011 Maxmind GeoLite Country database.
3229 o Packaging changes:
3230 - Make it easier to automate expert package builds on Windows,
3231 by removing an absolute path from makensis.exe command.
3233 o Code simplifications and refactoring:
3234 - Remove some redundant #include directives throughout the code.
3235 Patch from Andrea Gelmini.
3236 - Unconditionally use OpenSSL's AES implementation instead of our
3237 old built-in one. OpenSSL's AES has been better for a while, and
3238 relatively few servers should still be on any version of OpenSSL
3239 that doesn't have good optimized assembly AES.
3240 - Use the name "CERTS" consistently to refer to the new cell type;
3241 we were calling it CERT in some places and CERTS in others.
3244 - Numerous new unit tests for functions in util.c and address.c by
3246 - The long-disabled benchmark tests are now split into their own
3247 ./src/test/bench binary.
3248 - The benchmark tests can now use more accurate timers than
3249 gettimeofday() when such timers are available.
3252 Changes in version 0.2.3.7-alpha - 2011-10-30
3253 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3254 the new v3 handshake. It also resolves yet another bridge address
3258 - If we mark an OR connection for close based on a cell we process,
3259 don't process any further cells on it. We already avoid further
3260 reads on marked-for-close connections, but now we also discard the
3261 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3262 which was the first version where we might mark a connection for
3263 close based on processing a cell on it.
3264 - Fix a double-free bug that would occur when we received an invalid
3265 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3266 bugfix on 0.2.3.6-alpha.
3267 - Bridges no longer include their address in NETINFO cells on outgoing
3268 OR connections, to allow them to blend in better with clients.
3269 Removes another avenue for enumerating bridges. Reported by
3270 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3271 cells were introduced.
3274 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3275 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3278 Changes in version 0.2.3.6-alpha - 2011-10-26
3279 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3280 anonymity vulnerability where an attacker can deanonymize Tor
3281 users. Everybody should upgrade.
3283 This release also features support for a new v3 connection handshake
3284 protocol, and fixes to make hidden service connections more robust.
3287 - Implement a new handshake protocol (v3) for authenticating Tors to
3288 each other over TLS. It should be more resistant to fingerprinting
3289 than previous protocols, and should require less TLS hacking for
3290 future Tor implementations. Implements proposal 176.
3291 - Allow variable-length padding cells to disguise the length of
3292 Tor's TLS records. Implements part of proposal 184.
3294 o Privacy/anonymity fixes (clients):
3295 - Clients and bridges no longer send TLS certificate chains on
3296 outgoing OR connections. Previously, each client or bridge would
3297 use the same cert chain for all outgoing OR connections until
3298 its IP address changes, which allowed any relay that the client
3299 or bridge contacted to determine which entry guards it is using.
3300 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3301 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3302 no longer considers that connection as suitable for satisfying a
3303 circuit EXTEND request. Now relays can protect clients from the
3304 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3305 - Directory authorities no longer assign the Guard flag to relays
3306 that haven't upgraded to the above "refuse EXTEND requests
3307 to client connections" fix. Now directory authorities can
3308 protect clients from the CVE-2011-2768 issue even if neither
3309 the clients nor the relays have upgraded yet. There's a new
3310 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3311 to let us transition smoothly, else tomorrow there would be no
3314 o Major bugfixes (hidden services):
3315 - Improve hidden service robustness: when an attempt to connect to
3316 a hidden service ends, be willing to refetch its hidden service
3317 descriptors from each of the HSDir relays responsible for them
3318 immediately. Previously, we would not consider refetching the
3319 service's descriptors from each HSDir for 15 minutes after the last
3320 fetch, which was inconvenient if the hidden service was not running
3321 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3322 - When one of a hidden service's introduction points appears to be
3323 unreachable, stop trying it. Previously, we would keep trying
3324 to build circuits to the introduction point until we lost the
3325 descriptor, usually because the user gave up and restarted Tor.
3326 Partly fixes bug 3825.
3327 - Don't launch a useless circuit after failing to use one of a
3328 hidden service's introduction points. Previously, we would
3329 launch a new introduction circuit, but not set the hidden service
3330 which that circuit was intended to connect to, so it would never
3331 actually be used. A different piece of code would then create a
3332 new introduction circuit correctly. Bug reported by katmagic and
3333 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3335 o Major bugfixes (other):
3336 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3337 that they initiated. Relays could distinguish incoming bridge
3338 connections from client connections, creating another avenue for
3339 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3340 Found by "frosty_un".
3341 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3342 tor gets started. This prevents a wrong average bandwidth
3343 estimate, which would cause relays to always start a new accounting
3344 interval at the earliest possible moment. Fixes bug 2003; bugfix
3345 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3346 immensely in tracking this bug down.
3347 - Fix a crash bug when changing node restrictions while a DNS lookup
3348 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3351 o Minor bugfixes (on 0.2.2.x and earlier):
3352 - When a hidden service turns an extra service-side introduction
3353 circuit into a general-purpose circuit, free the rend_data and
3354 intro_key fields first, so we won't leak memory if the circuit
3355 is cannibalized for use as another service-side introduction
3356 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3357 - Rephrase the log message emitted if the TestSocks check is
3358 successful. Patch from Fabian Keil; fixes bug 4094.
3359 - Bridges now skip DNS self-tests, to act a little more stealthily.
3360 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3361 bridges. Patch by "warms0x".
3362 - Remove a confusing dollar sign from the example fingerprint in the
3363 man page, and also make the example fingerprint a valid one. Fixes
3364 bug 4309; bugfix on 0.2.1.3-alpha.
3365 - Fix internal bug-checking logic that was supposed to catch
3366 failures in digest generation so that it will fail more robustly
3367 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3368 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3369 - Report any failure in init_keys() calls launched because our
3370 IP address has changed. Spotted by Coverity Scan. Bugfix on
3371 0.1.1.4-alpha; fixes CID 484.
3373 o Minor bugfixes (on 0.2.3.x):
3374 - Fix a bug in configure.in that kept it from building a configure
3375 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3376 bugfix on 0.2.3.1-alpha.
3377 - Don't warn users that they are exposing a client port to the
3378 Internet if they have specified an RFC1918 address. Previously,
3379 we would warn if the user had specified any non-loopback
3380 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3381 - Fix memory leaks in the failing cases of the new SocksPort and
3382 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3383 fixes coverity CIDs 485, 486, and 487.
3386 - When a hidden service's introduction point times out, consider
3387 trying it again during the next attempt to connect to the
3388 HS. Previously, we would not try it again unless a newly fetched
3389 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3390 - The next version of Windows will be called Windows 8, and it has
3391 a major version of 6, minor version of 2. Correctly identify that
3392 version instead of calling it "Very recent version". Resolves
3393 ticket 4153; reported by funkstar.
3394 - The Bridge Authority now writes statistics on how many bridge
3395 descriptors it gave out in total, and how many unique descriptors
3396 it gave out. It also lists how often the most and least commonly
3397 fetched descriptors were given out, as well as the median and
3398 25th/75th percentile. Implements tickets 4200 and 4294.
3399 - Update to the October 4 2011 Maxmind GeoLite Country database.
3401 o Code simplifications and refactoring:
3402 - Remove some old code to remember statistics about which descriptors
3403 we've served as a directory mirror. The feature wasn't used and
3404 is outdated now that microdescriptors are around.
3405 - Rename Tor functions that turn strings into addresses, so that
3406 "parse" indicates that no hostname resolution occurs, and
3407 "lookup" indicates that hostname resolution may occur. This
3408 should help prevent mistakes in the future. Fixes bug 3512.
3411 Changes in version 0.2.2.34 - 2011-10-26
3412 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3413 can deanonymize Tor users. Everybody should upgrade.
3415 The attack relies on four components: 1) Clients reuse their TLS cert
3416 when talking to different relays, so relays can recognize a user by
3417 the identity key in her cert. 2) An attacker who knows the client's
3418 identity key can probe each guard relay to see if that identity key
3419 is connected to that guard relay right now. 3) A variety of active
3420 attacks in the literature (starting from "Low-Cost Traffic Analysis
3421 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3422 discover the guard relays that a Tor user visiting the website is using.
3423 4) Clients typically pick three guards at random, so the set of guards
3424 for a given user could well be a unique fingerprint for her. This
3425 release fixes components #1 and #2, which is enough to block the attack;
3426 the other two remain as open research problems. Special thanks to
3427 "frosty_un" for reporting the issue to us!
3429 Clients should upgrade so they are no longer recognizable by the TLS
3430 certs they present. Relays should upgrade so they no longer allow a
3431 remote attacker to probe them to test whether unpatched clients are
3432 currently connected to them.
3434 This release also fixes several vulnerabilities that allow an attacker
3435 to enumerate bridge relays. Some bridge enumeration attacks still
3436 remain; see for example proposal 188.
3438 o Privacy/anonymity fixes (clients):
3439 - Clients and bridges no longer send TLS certificate chains on
3440 outgoing OR connections. Previously, each client or bridge would
3441 use the same cert chain for all outgoing OR connections until
3442 its IP address changes, which allowed any relay that the client
3443 or bridge contacted to determine which entry guards it is using.
3444 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3445 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3446 no longer considers that connection as suitable for satisfying a
3447 circuit EXTEND request. Now relays can protect clients from the
3448 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3449 - Directory authorities no longer assign the Guard flag to relays
3450 that haven't upgraded to the above "refuse EXTEND requests
3451 to client connections" fix. Now directory authorities can
3452 protect clients from the CVE-2011-2768 issue even if neither
3453 the clients nor the relays have upgraded yet. There's a new
3454 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3455 to let us transition smoothly, else tomorrow there would be no
3458 o Privacy/anonymity fixes (bridge enumeration):
3459 - Bridge relays now do their directory fetches inside Tor TLS
3460 connections, like all the other clients do, rather than connecting
3461 directly to the DirPort like public relays do. Removes another
3462 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3463 - Bridges relays now build circuits for themselves in a more similar
3464 way to how clients build them. Removes another avenue for
3465 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3466 when bridges were introduced.
3467 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3468 that they initiated. Relays could distinguish incoming bridge
3469 connections from client connections, creating another avenue for
3470 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3471 Found by "frosty_un".
3474 - Fix a crash bug when changing node restrictions while a DNS lookup
3475 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3477 - Don't launch a useless circuit after failing to use one of a
3478 hidden service's introduction points. Previously, we would
3479 launch a new introduction circuit, but not set the hidden service
3480 which that circuit was intended to connect to, so it would never
3481 actually be used. A different piece of code would then create a
3482 new introduction circuit correctly. Bug reported by katmagic and
3483 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3486 - Change an integer overflow check in the OpenBSD_Malloc code so
3487 that GCC is less likely to eliminate it as impossible. Patch
3488 from Mansour Moufid. Fixes bug 4059.
3489 - When a hidden service turns an extra service-side introduction
3490 circuit into a general-purpose circuit, free the rend_data and
3491 intro_key fields first, so we won't leak memory if the circuit
3492 is cannibalized for use as another service-side introduction
3493 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3494 - Bridges now skip DNS self-tests, to act a little more stealthily.
3495 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3496 bridges. Patch by "warms0x".
3497 - Fix internal bug-checking logic that was supposed to catch
3498 failures in digest generation so that it will fail more robustly
3499 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3500 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3501 - Report any failure in init_keys() calls launched because our
3502 IP address has changed. Spotted by Coverity Scan. Bugfix on
3503 0.1.1.4-alpha; fixes CID 484.
3505 o Minor bugfixes (log messages and documentation):
3506 - Remove a confusing dollar sign from the example fingerprint in the
3507 man page, and also make the example fingerprint a valid one. Fixes
3508 bug 4309; bugfix on 0.2.1.3-alpha.
3509 - The next version of Windows will be called Windows 8, and it has
3510 a major version of 6, minor version of 2. Correctly identify that
3511 version instead of calling it "Very recent version". Resolves
3512 ticket 4153; reported by funkstar.
3513 - Downgrade log messages about circuit timeout calibration from
3514 "notice" to "info": they don't require or suggest any human
3515 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3516 bugfix on 0.2.2.14-alpha.
3519 - Turn on directory request statistics by default and include them in
3520 extra-info descriptors. Don't break if we have no GeoIP database.
3521 Backported from 0.2.3.1-alpha; implements ticket 3951.
3522 - Update to the October 4 2011 Maxmind GeoLite Country database.
3525 Changes in version 0.2.1.31 - 2011-10-26
3526 Tor 0.2.1.31 backports important security and privacy fixes for
3527 oldstable. This release is intended only for package maintainers and
3528 others who cannot use the 0.2.2 stable series. All others should be
3529 using Tor 0.2.2.x or newer.
3531 o Security fixes (also included in 0.2.2.x):
3532 - Replace all potentially sensitive memory comparison operations
3533 with versions whose runtime does not depend on the data being
3534 compared. This will help resist a class of attacks where an
3535 adversary can use variations in timing information to learn
3536 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3537 implementation by Robert Ransom based partially on code by DJB.)
3538 - Fix an assert in parsing router descriptors containing IPv6
3539 addresses. This one took down the directory authorities when
3540 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3542 o Privacy/anonymity fixes (also included in 0.2.2.x):
3543 - Clients and bridges no longer send TLS certificate chains on
3544 outgoing OR connections. Previously, each client or bridge would
3545 use the same cert chain for all outgoing OR connections until
3546 its IP address changes, which allowed any relay that the client
3547 or bridge contacted to determine which entry guards it is using.
3548 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3549 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3550 no longer considers that connection as suitable for satisfying a
3551 circuit EXTEND request. Now relays can protect clients from the
3552 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3553 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3554 that they initiated. Relays could distinguish incoming bridge
3555 connections from client connections, creating another avenue for
3556 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3557 Found by "frosty_un".
3558 - When receiving a hidden service descriptor, check that it is for
3559 the hidden service we wanted. Previously, Tor would store any
3560 hidden service descriptors that a directory gave it, whether it
3561 wanted them or not. This wouldn't have let an attacker impersonate
3562 a hidden service, but it did let directories pre-seed a client
3563 with descriptors that it didn't want. Bugfix on 0.0.6.
3564 - Avoid linkability based on cached hidden service descriptors: forget
3565 all hidden service descriptors cached as a client when processing a
3566 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3567 - Make the bridge directory authority refuse to answer directory
3568 requests for "all" descriptors. It used to include bridge
3569 descriptors in its answer, which was a major information leak.
3570 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3571 - Don't attach new streams to old rendezvous circuits after SIGNAL
3572 NEWNYM. Previously, we would keep using an existing rendezvous
3573 circuit if it remained open (i.e. if it were kept open by a
3574 long-lived stream, or if a new stream were attached to it before
3575 Tor could notice that it was old and no longer in use). Bugfix on
3576 0.1.1.15-rc; fixes bug 3375.
3578 o Minor bugfixes (also included in 0.2.2.x):
3579 - When we restart our relay, we might get a successful connection
3580 from the outside before we've started our reachability tests,
3581 triggering a warning: "ORPort found reachable, but I have no
3582 routerinfo yet. Failing to inform controller of success." This
3583 bug was harmless unless Tor is running under a controller
3584 like Vidalia, in which case the controller would never get a
3585 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3587 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3588 enabled. Fixes bug 1526.
3589 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3590 anything since 0.2.1.16-rc.
3591 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3592 None of the cases where we did this before were wrong, but by making
3593 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3594 - Fix a rare crash bug that could occur when a client was configured
3595 with a large number of bridges. Fixes bug 2629; bugfix on
3596 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3597 - Correct the warning displayed when a rendezvous descriptor exceeds
3598 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3600 - Fix an uncommon assertion failure when running with DNSPort under
3601 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3602 - When warning about missing zlib development packages during compile,
3603 give the correct package names. Bugfix on 0.2.0.1-alpha.
3604 - Require that introduction point keys and onion keys have public
3605 exponent 65537. Bugfix on 0.2.0.10-alpha.
3606 - Do not crash when our configuration file becomes unreadable, for
3607 example due to a permissions change, between when we start up
3608 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3610 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3612 - Always NUL-terminate the sun_path field of a sockaddr_un before
3613 passing it to the kernel. (Not a security issue: kernels are
3614 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3615 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3616 - Don't stack-allocate the list of supplementary GIDs when we're
3617 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3618 could take up to 256K, which is way too much stack. Found by
3619 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3621 o Minor bugfixes (only in 0.2.1.x):
3622 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3623 rely on them. Bugfix on 0.2.1.30.
3624 - Use git revisions instead of svn revisions when generating our
3625 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3627 o Minor features (also included in 0.2.2.x):
3628 - Adjust the expiration time on our SSL session certificates to
3629 better match SSL certs seen in the wild. Resolves ticket 4014.
3630 - Allow nameservers with IPv6 address. Resolves bug 2574.
3631 - Update to the October 4 2011 Maxmind GeoLite Country database.
3634 Changes in version 0.2.3.5-alpha - 2011-09-28
3635 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3636 bridge relays; fixes an assertion error that many users started hitting
3637 today; and adds the ability to refill token buckets more often than
3638 once per second, allowing significant performance improvements.
3641 - Bridge relays now do their directory fetches inside Tor TLS
3642 connections, like all the other clients do, rather than connecting
3643 directly to the DirPort like public relays do. Removes another
3644 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3645 - Bridges relays now build circuits for themselves in a more similar
3646 way to how clients build them. Removes another avenue for
3647 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3648 when bridges were introduced.
3651 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3652 occur when the same microdescriptor was referenced by two node_t
3653 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3655 o Major features (networking):
3656 - Add a new TokenBucketRefillInterval option to refill token buckets
3657 more frequently than once per second. This should improve network
3658 performance, alleviate queueing problems, and make traffic less
3659 bursty. Implements proposal 183; closes ticket 3630. Design by
3660 Florian Tschorsch and Björn Scheuermann; implementation by
3664 - Change an integer overflow check in the OpenBSD_Malloc code so
3665 that GCC is less likely to eliminate it as impossible. Patch
3666 from Mansour Moufid. Fixes bug 4059.
3668 o Minor bugfixes (usability):
3669 - Downgrade log messages about circuit timeout calibration from
3670 "notice" to "info": they don't require or suggest any human
3671 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3672 bugfix on 0.2.2.14-alpha.
3674 o Minor features (diagnostics):
3675 - When the system call to create a listener socket fails, log the
3676 error message explaining why. This may help diagnose bug 4027.
3679 Changes in version 0.2.3.4-alpha - 2011-09-13
3680 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3681 tweak to Tor's TLS handshake that makes relays and bridges that run
3682 this new version reachable from Iran again. It also fixes a few new
3683 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3684 listed in the network consensus and republish.
3686 o Major bugfixes (also part of 0.2.2.33):
3687 - Avoid an assertion failure when reloading a configuration with
3688 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3689 3923; bugfix on 0.2.2.25-alpha.
3691 o Minor features (security, also part of 0.2.2.33):
3692 - Check for replays of the public-key encrypted portion of an
3693 INTRODUCE1 cell, in addition to the current check for replays of
3694 the g^x value. This prevents a possible class of active attacks
3695 by an attacker who controls both an introduction point and a
3696 rendezvous point, and who uses the malleability of AES-CTR to
3697 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3698 that these attacks is infeasible (requiring the attacker to send
3699 on the order of zettabytes of altered cells in a short interval),
3700 but we'd rather block them off in case there are any classes of
3701 this attack that we missed. Reported by Willem Pinckaers.
3703 o Minor features (also part of 0.2.2.33):
3704 - Adjust the expiration time on our SSL session certificates to
3705 better match SSL certs seen in the wild. Resolves ticket 4014.
3706 - Change the default required uptime for a relay to be accepted as
3707 a HSDir (hidden service directory) from 24 hours to 25 hours.
3708 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3709 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3710 authorities to abstain from voting on assignment of the HSDir
3711 consensus flag. Related to bug 2649.
3712 - Update to the September 6 2011 Maxmind GeoLite Country database.
3714 o Minor bugfixes (also part of 0.2.2.33):
3715 - Demote the 'replay detected' log message emitted when a hidden
3716 service receives the same Diffie-Hellman public key in two different
3717 INTRODUCE2 cells to info level. A normal Tor client can cause that
3718 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3719 fixes part of bug 2442.
3720 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3721 level. There is nothing that a hidden service's operator can do
3722 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3724 - Clarify a log message specifying the characters permitted in
3725 HiddenServiceAuthorizeClient client names. Previously, the log
3726 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3727 given the impression that every ASCII character between "+" and "_"
3728 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3730 o Build fixes (also part of 0.2.2.33):
3731 - Clean up some code issues that prevented Tor from building on older
3732 BSDs. Fixes bug 3894; reported by "grarpamp".
3733 - Search for a platform-specific version of "ar" when cross-compiling.
3734 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3737 - Fix a bug where the SocksPort option (for example) would get
3738 ignored and replaced by the default if a SocksListenAddress
3739 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3743 - Relays now try regenerating and uploading their descriptor more
3744 frequently if they are not listed in the consensus, or if the
3745 version of their descriptor listed in the consensus is too
3746 old. This fix should prevent situations where a server declines
3747 to re-publish itself because it has done so too recently, even
3748 though the authorities decided not to list its recent-enough
3749 descriptor. Fix for bug 3327.
3752 - Relays now include a reason for regenerating their descriptors
3753 in an HTTP header when uploading to the authorities. This will
3754 make it easier to debug descriptor-upload issues in the future.
3755 - When starting as root and then changing our UID via the User
3756 control option, and we have a ControlSocket configured, make sure
3757 that the ControlSocket is owned by the same account that Tor will
3758 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3761 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
3762 utility function used in the control-port code). This shouldn't
3763 ever happen unless Tor is completely out of memory, but if it did
3764 happen and Tor somehow recovered from it, Tor could have sent a log
3765 message to a control port in the middle of a reply to a controller
3766 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3767 - Make 'FetchUselessDescriptors' cause all descriptor types and
3768 all consensus types (including microdescriptors) to get fetched.
3769 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
3772 - Make a new "entry connection" struct as an internal subtype of "edge
3773 connection", to simplify the code and make exit connections smaller.
3776 Changes in version 0.2.2.33 - 2011-09-13
3777 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
3778 TLS handshake that makes relays and bridges that run this new version
3779 reachable from Iran again.
3782 - Avoid an assertion failure when reloading a configuration with
3783 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3784 3923; bugfix on 0.2.2.25-alpha.
3786 o Minor features (security):
3787 - Check for replays of the public-key encrypted portion of an
3788 INTRODUCE1 cell, in addition to the current check for replays of
3789 the g^x value. This prevents a possible class of active attacks
3790 by an attacker who controls both an introduction point and a
3791 rendezvous point, and who uses the malleability of AES-CTR to
3792 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3793 that these attacks are infeasible (requiring the attacker to send
3794 on the order of zettabytes of altered cells in a short interval),
3795 but we'd rather block them off in case there are any classes of
3796 this attack that we missed. Reported by Willem Pinckaers.
3799 - Adjust the expiration time on our SSL session certificates to
3800 better match SSL certs seen in the wild. Resolves ticket 4014.
3801 - Change the default required uptime for a relay to be accepted as
3802 a HSDir (hidden service directory) from 24 hours to 25 hours.
3803 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3804 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3805 authorities to abstain from voting on assignment of the HSDir
3806 consensus flag. Related to bug 2649.
3807 - Update to the September 6 2011 Maxmind GeoLite Country database.
3809 o Minor bugfixes (documentation and log messages):
3810 - Correct the man page to explain that HashedControlPassword and
3811 CookieAuthentication can both be set, in which case either method
3812 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3813 when we decided to allow these config options to both be set. Issue
3815 - Demote the 'replay detected' log message emitted when a hidden
3816 service receives the same Diffie-Hellman public key in two different
3817 INTRODUCE2 cells to info level. A normal Tor client can cause that
3818 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3819 fixes part of bug 2442.
3820 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3821 level. There is nothing that a hidden service's operator can do
3822 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3824 - Clarify a log message specifying the characters permitted in
3825 HiddenServiceAuthorizeClient client names. Previously, the log
3826 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3827 given the impression that every ASCII character between "+" and "_"
3828 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3831 - Provide a substitute implementation of lround() for MSVC, which
3832 apparently lacks it. Patch from Gisle Vanem.
3833 - Clean up some code issues that prevented Tor from building on older
3834 BSDs. Fixes bug 3894; reported by "grarpamp".
3835 - Search for a platform-specific version of "ar" when cross-compiling.
3836 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3839 Changes in version 0.2.3.3-alpha - 2011-09-01
3840 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
3841 security, and provides client-side support for the microdescriptor
3842 and optimistic data features introduced earlier in the 0.2.3.x
3843 series. It also includes numerous critical bugfixes in the (optional)
3844 bufferevent-based networking backend.
3846 o Major features (stream isolation):
3847 - You can now configure Tor so that streams from different
3848 applications are isolated on different circuits, to prevent an
3849 attacker who sees your streams as they leave an exit node from
3850 linking your sessions to one another. To do this, choose some way
3851 to distinguish the applications: have them connect to different
3852 SocksPorts, or have one of them use SOCKS4 while the other uses
3853 SOCKS5, or have them pass different authentication strings to the
3854 SOCKS proxy. Then, use the new SocksPort syntax to configure the
3855 degree of isolation you need. This implements Proposal 171.
3856 - There's a new syntax for specifying multiple client ports (such as
3857 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
3858 multiple *Port entries with full addr:port syntax on each.
3859 The old *ListenAddress format is still supported, but you can't
3860 mix it with the new *Port syntax.
3862 o Major features (other):
3863 - Enable microdescriptor fetching by default for clients. This allows
3864 clients to download a much smaller amount of directory information.
3865 To disable it (and go back to the old-style consensus and
3866 descriptors), set "UseMicrodescriptors 0" in your torrc file.
3867 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
3868 "PortForwarding" config option), now supports Windows.
3869 - When using an exit relay running 0.2.3.x, clients can now
3870 "optimistically" send data before the exit relay reports that
3871 the stream has opened. This saves a round trip when starting
3872 connections where the client speaks first (such as web browsing).
3873 This behavior is controlled by a consensus parameter (currently
3874 disabled). To turn it on or off manually, use the "OptimisticData"
3875 torrc option. Implements proposal 181; code by Ian Goldberg.
3877 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
3878 - When using IOCP on Windows, we need to enable Libevent windows
3880 - The IOCP backend now works even when the user has not specified
3881 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
3882 Fixes part of bug 3752.
3883 - Correctly record the bytes we've read and written when using
3884 bufferevents, so that we can include them in our bandwidth history
3885 and advertised bandwidth. Fixes bug 3803.
3886 - Apply rate-limiting only at the bottom of a chain of filtering
3887 bufferevents. This prevents us from filling up internal read
3888 buffers and violating rate-limits when filtering bufferevents
3889 are enabled. Fixes part of bug 3804.
3890 - Add high-watermarks to the output buffers for filtered
3891 bufferevents. This prevents us from filling up internal write
3892 buffers and wasting CPU cycles when filtering bufferevents are
3893 enabled. Fixes part of bug 3804.
3894 - Correctly notice when data has been written from a bufferevent
3895 without flushing it completely. Fixes bug 3805.
3896 - Fix a bug where server-side tunneled bufferevent-based directory
3897 streams would get closed prematurely. Fixes bug 3814.
3898 - Fix a use-after-free error with per-connection rate-limiting
3899 buckets. Fixes bug 3888.
3901 o Major bugfixes (also part of 0.2.2.31-rc):
3902 - If we're configured to write our ControlPorts to disk, only write
3903 them after switching UID and creating the data directory. This way,
3904 we don't fail when starting up with a nonexistent DataDirectory
3905 and a ControlPortWriteToFile setting based on that directory. Fixes
3906 bug 3747; bugfix on Tor 0.2.2.26-beta.
3909 - Added a new CONF_CHANGED event so that controllers can be notified
3910 of any configuration changes made by other controllers, or by the
3911 user. Implements ticket 1692.
3912 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
3913 leak when using bufferevents, and lets Libevent worry about how to
3914 best copy data out of a buffer.
3915 - Replace files in stats/ rather than appending to them. Now that we
3916 include statistics in extra-info descriptors, it makes no sense to
3917 keep old statistics forever. Implements ticket 2930.
3919 o Minor features (build compatibility):
3920 - Limited, experimental support for building with nmake and MSVC.
3921 - Provide a substitute implementation of lround() for MSVC, which
3922 apparently lacks it. Patch from Gisle Vanem.
3924 o Minor features (also part of 0.2.2.31-rc):
3925 - Update to the August 2 2011 Maxmind GeoLite Country database.
3927 o Minor bugfixes (on 0.2.3.x-alpha):
3928 - Fix a spurious warning when parsing SOCKS requests with
3929 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
3930 - Get rid of a harmless warning that could happen on relays running
3931 with bufferevents. The warning was caused by someone doing an http
3932 request to a relay's orport. Also don't warn for a few related
3933 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
3935 o Minor bugfixes (on 2.2.x and earlier):
3936 - Correct the man page to explain that HashedControlPassword and
3937 CookieAuthentication can both be set, in which case either method
3938 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3939 when we decided to allow these config options to both be set. Issue
3941 - The "--quiet" and "--hush" options now apply not only to Tor's
3942 behavior before logs are configured, but also to Tor's behavior in
3943 the absense of configured logs. Fixes bug 3550; bugfix on
3946 o Minor bugfixes (also part of 0.2.2.31-rc):
3947 - Write several files in text mode, on OSes that distinguish text
3948 mode from binary mode (namely, Windows). These files are:
3949 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3950 that collect those statistics; 'client_keys' and 'hostname' for
3951 hidden services that use authentication; and (in the tor-gencert
3952 utility) newly generated identity and signing keys. Previously,
3953 we wouldn't specify text mode or binary mode, leading to an
3954 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3955 the DirRecordUsageByCountry option which would have triggered
3956 the assertion failure was added), although this assertion failure
3957 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3958 - Selectively disable deprecation warnings on OS X because Lion
3959 started deprecating the shipped copy of openssl. Fixes bug 3643.
3960 - Remove an extra pair of quotation marks around the error
3961 message in control-port STATUS_GENERAL BUG events. Bugfix on
3962 0.1.2.6-alpha; fixes bug 3732.
3963 - When unable to format an address as a string, report its value
3964 as "???" rather than reusing the last formatted address. Bugfix
3967 o Code simplifications and refactoring:
3968 - Rewrite the listener-selection logic so that parsing which ports
3969 we want to listen on is now separate from binding to the ports
3973 - Building Tor with bufferevent support now requires Libevent
3974 2.0.13-stable or later. Previous versions of Libevent had bugs in
3975 SSL-related bufferevents and related issues that would make Tor
3976 work badly with bufferevents. Requiring 2.0.13-stable also allows
3977 Tor with bufferevents to take advantage of Libevent APIs
3978 introduced after 2.0.8-rc.
3981 Changes in version 0.2.2.32 - 2011-08-27
3982 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3983 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3984 a founder of the PETS community, a leader in our field, a mentor,
3985 and a friend. He left us with these words: "I had the possibility
3986 to contribute to this world that is not as it should be. I hope I
3987 could help in some areas to make the world a better place, and that
3988 I could also encourage other people to be engaged in improving the
3989 world. Please, stay engaged. This world needs you, your love, your
3990 initiative -- now I cannot be part of that anymore."
3992 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3993 ready. More than two years in the making, this release features improved
3994 client performance and hidden service reliability, better compatibility
3995 for Android, correct behavior for bridges that listen on more than
3996 one address, more extensible and flexible directory object handling,
3997 better reporting of network statistics, improved code security, and
3998 many many other features and bugfixes.
4001 Changes in version 0.2.2.31-rc - 2011-08-17
4002 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4003 for the Tor 0.2.2.x series.
4006 - Remove an extra pair of quotation marks around the error
4007 message in control-port STATUS_GENERAL BUG events. Bugfix on
4008 0.1.2.6-alpha; fixes bug 3732.
4009 - If we're configured to write our ControlPorts to disk, only write
4010 them after switching UID and creating the data directory. This way,
4011 we don't fail when starting up with a nonexistent DataDirectory
4012 and a ControlPortWriteToFile setting based on that directory. Fixes
4013 bug 3747; bugfix on Tor 0.2.2.26-beta.
4016 - Update to the August 2 2011 Maxmind GeoLite Country database.
4019 - Allow GETINFO fingerprint to return a fingerprint even when
4020 we have not yet built a router descriptor. Fixes bug 3577;
4021 bugfix on 0.2.0.1-alpha.
4022 - Write several files in text mode, on OSes that distinguish text
4023 mode from binary mode (namely, Windows). These files are:
4024 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4025 that collect those statistics; 'client_keys' and 'hostname' for
4026 hidden services that use authentication; and (in the tor-gencert
4027 utility) newly generated identity and signing keys. Previously,
4028 we wouldn't specify text mode or binary mode, leading to an
4029 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4030 the DirRecordUsageByCountry option which would have triggered
4031 the assertion failure was added), although this assertion failure
4032 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4033 - Selectively disable deprecation warnings on OS X because Lion
4034 started deprecating the shipped copy of openssl. Fixes bug 3643.
4035 - When unable to format an address as a string, report its value
4036 as "???" rather than reusing the last formatted address. Bugfix
4040 Changes in version 0.2.3.2-alpha - 2011-07-18
4041 Tor 0.2.3.2-alpha introduces two new experimental features:
4042 microdescriptors and pluggable transports. It also continues cleaning
4043 up a variety of recently introduced features.
4046 - Clients can now use microdescriptors instead of regular descriptors
4047 to build circuits. Microdescriptors are authority-generated
4048 summaries of regular descriptors' contents, designed to change
4049 very rarely (see proposal 158 for details). This feature is
4050 designed to save bandwidth, especially for clients on slow internet
4051 connections. It's off by default for now, since nearly no caches
4052 support it, but it will be on-by-default for clients in a future
4053 version. You can use the UseMicrodescriptors option to turn it on.
4054 - Tor clients using bridges can now be configured to use a separate
4055 'transport' proxy for each bridge. This approach helps to resist
4056 censorship by allowing bridges to use protocol obfuscation
4057 plugins. It implements part of proposal 180. Implements ticket 2841.
4058 - While we're trying to bootstrap, record how many TLS connections
4059 fail in each state, and report which states saw the most failures
4060 in response to any bootstrap failures. This feature may speed up
4061 diagnosis of censorship events. Implements ticket 3116.
4063 o Major bugfixes (on 0.2.3.1-alpha):
4064 - When configuring a large set of nodes in EntryNodes (as with
4065 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4066 random subset to be guards, and choose them in random
4067 order. Fixes bug 2798.
4068 - Tor could crash when remembering a consensus in a non-used consensus
4069 flavor without having a current consensus set. Fixes bug 3361.
4070 - Comparing an unknown address to a microdescriptor's shortened exit
4071 policy would always give a "rejected" result. Fixes bug 3599.
4072 - Using microdescriptors as a client no longer prevents Tor from
4073 uploading and downloading hidden service descriptors. Fixes
4077 - Allow nameservers with IPv6 address. Resolves bug 2574.
4078 - Accept attempts to include a password authenticator in the
4079 handshake, as supported by SOCKS5. This handles SOCKS clients that
4080 don't know how to omit a password when authenticating. Resolves
4082 - When configuring a large set of nodes in EntryNodes, and there are
4083 enough of them listed as Guard so that we don't need to consider
4084 the non-guard entries, prefer the ones listed with the Guard flag.
4085 - Check for and recover from inconsistency in the microdescriptor
4086 cache. This will make it harder for us to accidentally free a
4087 microdescriptor without removing it from the appropriate data
4088 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4089 - Log SSL state transitions at log level DEBUG, log domain
4090 HANDSHAKE. This can be useful for debugging censorship events.
4091 Implements ticket 3264.
4092 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4093 implements ticket 3439.
4095 o Minor bugfixes (on 0.2.3.1-alpha):
4096 - Do not free all general-purpose regular descriptors just
4097 because microdescriptor use is enabled. Fixes bug 3113.
4098 - Correctly link libevent_openssl when --enable-static-libevent
4099 is passed to configure. Fixes bug 3118.
4100 - Bridges should not complain during their heartbeat log messages that
4101 they are unlisted in the consensus: that's more or less the point
4102 of being a bridge. Fixes bug 3183.
4103 - Report a SIGNAL event to controllers when acting on a delayed
4104 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4105 event to the controller if we acted on a SIGNAL NEWNYM command
4106 immediately, and otherwise not report a SIGNAL event for the
4107 command at all. Fixes bug 3349.
4108 - Fix a crash when handling the SIGNAL controller command or
4109 reporting ERR-level status events with bufferevents enabled. Found
4110 by Robert Ransom. Fixes bug 3367.
4111 - Always ship the tor-fw-helper manpage in our release tarballs.
4112 Fixes bug 3389. Reported by Stephen Walker.
4113 - Fix a class of double-mark-for-close bugs when bufferevents
4114 are enabled. Fixes bug 3403.
4115 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4116 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4117 control-port command. Fixes part of bug 3465.
4118 - Prevent using negative indices during unit test runs when read_all()
4119 fails. Spotted by coverity.
4120 - Fix a rare memory leak when checking the nodelist without it being
4121 present. Found by coverity.
4122 - Only try to download a microdescriptor-flavored consensus from
4123 a directory cache that provides them.
4125 o Minor bugfixes (on 0.2.2.x and earlier):
4126 - Assert that hidden-service-related operations are not performed
4127 using single-hop circuits. Previously, Tor would assert that
4128 client-side streams are not attached to single-hop circuits,
4129 but not that other sensitive operations on the client and service
4130 side are not performed using single-hop circuits. Fixes bug 3332;
4132 - Don't publish a new relay descriptor when we reload our onion key,
4133 unless the onion key has actually changed. Fixes bug 3263 and
4134 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4135 - Allow GETINFO fingerprint to return a fingerprint even when
4136 we have not yet built a router descriptor. Fixes bug 3577;
4137 bugfix on 0.2.0.1-alpha.
4138 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4139 on 0.2.2.4-alpha; fixes bug 3427.
4141 o Code simplification and refactoring:
4142 - Use tor_sscanf() in place of scanf() in more places through the
4143 code. This makes us a little more locale-independent, and
4144 should help shut up code-analysis tools that can't tell
4145 a safe sscanf string from a dangerous one.
4146 - Use tt_assert(), not tor_assert(), for checking for test failures.
4147 This makes the unit tests more able to go on in the event that
4149 - Split connection_about_to_close() into separate functions for each
4153 - On Windows, we now define the _WIN32_WINNT macros only if they
4154 are not already defined. This lets the person building Tor decide,
4155 if they want, to require a later version of Windows.
4158 Changes in version 0.2.2.30-rc - 2011-07-07
4159 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4160 series. It fixes a few smaller bugs, but generally appears stable.
4161 Please test it and let us know whether it is!
4164 - Send a SUCCEEDED stream event to the controller when a reverse
4165 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4166 discovered by katmagic.
4167 - Always NUL-terminate the sun_path field of a sockaddr_un before
4168 passing it to the kernel. (Not a security issue: kernels are
4169 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4170 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4171 - Don't stack-allocate the list of supplementary GIDs when we're
4172 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4173 could take up to 256K, which is way too much stack. Found by
4174 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4175 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4176 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4177 fixes part of bug 3465.
4178 - Fix a memory leak when receiving a descriptor for a hidden
4179 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4183 - Update to the July 1 2011 Maxmind GeoLite Country database.
4186 Changes in version 0.2.2.29-beta - 2011-06-20
4187 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4188 have bridge lines in their torrc but don't want to use them; gets
4189 us closer to having the control socket feature working on Debian;
4190 and fixes a variety of smaller bugs.
4193 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4194 When we changed the default behavior to "use bridges if any
4195 are listed in the torrc", we surprised users who had bridges
4196 in their torrc files but who didn't actually want to use them.
4197 Partial resolution for bug 3354.
4200 - Don't attach new streams to old rendezvous circuits after SIGNAL
4201 NEWNYM. Previously, we would keep using an existing rendezvous
4202 circuit if it remained open (i.e. if it were kept open by a
4203 long-lived stream, or if a new stream were attached to it before
4204 Tor could notice that it was old and no longer in use). Bugfix on
4205 0.1.1.15-rc; fixes bug 3375.
4208 - Fix a bug when using ControlSocketsGroupWritable with User. The
4209 directory's group would be checked against the current group, not
4210 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4211 bugfix on 0.2.2.26-beta.
4212 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4213 expect it to emit a CRLF iff the format string ends with CRLF;
4214 it actually emitted a CRLF iff (a) the format string ended with
4215 CRLF or (b) the resulting string was over 1023 characters long or
4216 (c) the format string did not end with CRLF *and* the resulting
4217 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4218 fixes part of bug 3407.
4219 - Make send_control_event_impl()'s behaviour sane. Its callers
4220 expect it to always emit a CRLF at the end of the string; it
4221 might have emitted extra control characters as well. Bugfix on
4222 0.1.1.9-alpha; fixes another part of bug 3407.
4223 - Make crypto_rand_int() check the value of its input correctly.
4224 Previously, it accepted values up to UINT_MAX, but could return a
4225 negative number if given a value above INT_MAX+1. Found by George
4226 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4227 - Avoid a segfault when reading a malformed circuit build state
4228 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4230 - When asked about a DNS record type we don't support via a
4231 client DNSPort, reply with NOTIMPL rather than an empty
4232 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4233 - Fix a rare memory leak during stats writing. Found by coverity.
4236 - Update to the June 1 2011 Maxmind GeoLite Country database.
4238 o Code simplifications and refactoring:
4239 - Remove some dead code as indicated by coverity.
4240 - Remove a few dead assignments during router parsing. Found by
4242 - Add some forgotten return value checks during unit tests. Found
4244 - Don't use 1-bit wide signed bit fields. Found by coverity.
4247 Changes in version 0.2.2.28-beta - 2011-06-04
4248 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4249 fixed a big bug in whether relays stay in the consensus consistently,
4250 we moved closer to handling bridges and hidden services correctly,
4251 and we started the process of better handling the dreaded "my Vidalia
4252 died, and now my Tor demands a password when I try to reconnect to it"
4256 - Don't decide to make a new descriptor when receiving a HUP signal.
4257 This bug has caused a lot of 0.2.2.x relays to disappear from the
4258 consensus periodically. Fixes the most common case of triggering
4259 bug 1810; bugfix on 0.2.2.7-alpha.
4260 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4261 - Don't try to build descriptors if "ORPort auto" is set and we
4262 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4264 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4265 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4266 - Apply circuit timeouts to opened hidden-service-related circuits
4267 based on the correct start time. Previously, we would apply the
4268 circuit build timeout based on time since the circuit's creation;
4269 it was supposed to be applied based on time since the circuit
4270 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4271 - Use the same circuit timeout for client-side introduction
4272 circuits as for other four-hop circuits, rather than the timeout
4273 for single-hop directory-fetch circuits; the shorter timeout may
4274 have been appropriate with the static circuit build timeout in
4275 0.2.1.x and earlier, but caused many hidden service access attempts
4276 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4277 on 0.2.2.2-alpha; fixes another part of bug 1297.
4278 - In ticket 2511 we fixed a case where you could use an unconfigured
4279 bridge if you had configured it as a bridge the last time you ran
4280 Tor. Now fix another edge case: if you had configured it as a bridge
4281 but then switched to a different bridge via the controller, you
4282 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4286 - Add an __OwningControllerProcess configuration option and a
4287 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4288 that when it exits, Tor will shut down. Implements feature 3049.
4289 - If "UseBridges 1" is set and no bridges are configured, Tor will
4290 now refuse to build any circuits until some bridges are set.
4291 If "UseBridges auto" is set, Tor will use bridges if they are
4292 configured and we are not running as a server, but otherwise will
4293 make circuits as usual. The new default is "auto". Patch by anonym,
4294 so the Tails LiveCD can stop automatically revealing you as a Tor
4298 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4299 - Remove a trailing asterisk from "exit-policy/default" in the
4300 output of the control port command "GETINFO info/names". Bugfix
4302 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4304 - Warn when the user configures two HiddenServiceDir lines that point
4305 to the same directory. Bugfix on 0.0.6 (the version introducing
4306 HiddenServiceDir); fixes bug 3289.
4307 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4308 part of bug 2748; bugfix on 0.2.0.10-alpha.
4309 - Log malformed requests for rendezvous descriptors as protocol
4310 warnings, not warnings. Also, use a more informative log message
4311 in case someone sees it at log level warning without prior
4312 info-level messages. Fixes the other part of bug 2748; bugfix
4314 - Clear the table recording the time of the last request for each
4315 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4316 Previously, we would clear our HS descriptor cache on SIGNAL
4317 NEWNYM, but if we had previously retrieved a descriptor (or tried
4318 to) from every directory responsible for it, we would refuse to
4319 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4321 - Fix a log message that said "bits" while displaying a value in
4322 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4324 - When checking for 1024-bit keys, check for 1024 bits, not 128
4325 bytes. This allows Tor to correctly discard keys of length 1017
4326 through 1023. Bugfix on 0.0.9pre5.
4329 - Relays now log the reason for publishing a new relay descriptor,
4330 so we have a better chance of hunting down instances of bug 1810.
4331 Resolves ticket 3252.
4332 - Revise most log messages that refer to nodes by nickname to
4333 instead use the "$key=nickname at address" format. This should be
4334 more useful, especially since nicknames are less and less likely
4335 to be unique. Resolves ticket 3045.
4336 - Log (at info level) when purging pieces of hidden-service-client
4337 state because of SIGNAL NEWNYM.
4340 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4341 anything since 0.2.1.16-rc.
4344 Changes in version 0.2.2.27-beta - 2011-05-18
4345 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4346 release, and also adds a few more general bugfixes.
4349 - Fix a crash bug when changing bridges in a running Tor process.
4350 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4351 - When the controller configures a new bridge, don't wait 10 to 60
4352 seconds before trying to fetch its descriptor. Bugfix on
4353 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4356 - Require that onion keys have exponent 65537 in microdescriptors too.
4357 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4358 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4359 Changed the limit to 512 characters by removing base64 newlines.
4360 Fixes bug 2752. Fix by Michael Yakubovich.
4361 - When a client starts or stops using bridges, never use a circuit
4362 that was built before the configuration change. This behavior could
4363 put at risk a user who uses bridges to ensure that her traffic
4364 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4368 Changes in version 0.2.2.26-beta - 2011-05-17
4369 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4370 also introduces a new "socksport auto" approach that should make it
4371 easier to run multiple Tors on the same system, and does a lot of
4372 cleanup to get us closer to a release candidate.
4374 o Security/privacy fixes:
4375 - Replace all potentially sensitive memory comparison operations
4376 with versions whose runtime does not depend on the data being
4377 compared. This will help resist a class of attacks where an
4378 adversary can use variations in timing information to learn
4379 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4380 implementation by Robert Ransom based partially on code by DJB.)
4381 - When receiving a hidden service descriptor, check that it is for
4382 the hidden service we wanted. Previously, Tor would store any
4383 hidden service descriptors that a directory gave it, whether it
4384 wanted them or not. This wouldn't have let an attacker impersonate
4385 a hidden service, but it did let directories pre-seed a client
4386 with descriptors that it didn't want. Bugfix on 0.0.6.
4387 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4388 DNS cache entries, and virtual address mappings: that's what
4389 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4392 - The options SocksPort, ControlPort, and so on now all accept a
4393 value "auto" that opens a socket on an OS-selected port. A
4394 new ControlPortWriteToFile option tells Tor to write its
4395 actual control port or ports to a chosen file. If the option
4396 ControlPortFileGroupReadable is set, the file is created as
4397 group-readable. Now users can run two Tor clients on the same
4398 system without needing to manually mess with parameters. Resolves
4399 part of ticket 3076.
4400 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4401 help busy exit nodes avoid running out of useable ports just
4402 because all the ports have been used in the near past. Resolves
4406 - New "GETINFO net/listeners/(type)" controller command to return
4407 a list of addresses and ports that are bound for listeners for a
4408 given connection type. This is useful when the user has configured
4409 "SocksPort auto" and the controller needs to know which port got
4410 chosen. Resolves another part of ticket 3076.
4411 - Add a new ControlSocketsGroupWritable configuration option: when
4412 it is turned on, ControlSockets are group-writeable by the default
4413 group of the current user. Patch by Jérémy Bobbio; implements
4415 - Tor now refuses to create a ControlSocket in a directory that is
4416 world-readable (or group-readable if ControlSocketsGroupWritable
4417 is 0). This is necessary because some operating systems do not
4418 enforce permissions on an AF_UNIX sockets. Permissions on the
4419 directory holding the socket, however, seems to work everywhere.
4420 - Rate-limit a warning about failures to download v2 networkstatus
4421 documents. Resolves part of bug 1352.
4422 - Backport code from 0.2.3.x that allows directory authorities to
4423 clean their microdescriptor caches. Needed to resolve bug 2230.
4424 - When an HTTPS proxy reports "403 Forbidden", we now explain
4425 what it means rather than calling it an unexpected status code.
4426 Closes bug 2503. Patch from Michael Yakubovich.
4427 - Update to the May 1 2011 Maxmind GeoLite Country database.
4430 - Authorities now clean their microdesc cache periodically and when
4431 reading from disk initially, not only when adding new descriptors.
4432 This prevents a bug where we could lose microdescriptors. Bugfix
4433 on 0.2.2.6-alpha. Fixes bug 2230.
4434 - Do not crash when our configuration file becomes unreadable, for
4435 example due to a permissions change, between when we start up
4436 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4438 - Avoid a bug that would keep us from replacing a microdescriptor
4439 cache on Windows. (We would try to replace the file while still
4440 holding it open. That's fine on Unix, but Windows doesn't let us
4441 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4442 - Add missing explanations for the authority-related torrc options
4443 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4444 man page. Resolves issue 2379.
4445 - As an authority, do not upload our own vote or signature set to
4446 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4447 it would get flagged as a duplicate. Resolves bug 3026.
4448 - Accept hidden service descriptors if we think we might be a hidden
4449 service directory, regardless of what our consensus says. This
4450 helps robustness, since clients and hidden services can sometimes
4451 have a more up-to-date view of the network consensus than we do,
4452 and if they think that the directory authorities list us a HSDir,
4453 we might actually be one. Related to bug 2732; bugfix on
4455 - When a controller changes TrackHostExits, remove mappings for
4456 hosts that should no longer have their exits tracked. Bugfix on
4458 - When a controller changes VirtualAddrNetwork, remove any mappings
4459 for hosts that were automapped to the old network. Bugfix on
4461 - When a controller changes one of the AutomapHosts* options, remove
4462 any mappings for hosts that should no longer be automapped. Bugfix
4464 - Do not reset the bridge descriptor download status every time we
4465 re-parse our configuration or get a configuration change. Fixes
4466 bug 3019; bugfix on 0.2.0.3-alpha.
4468 o Minor bugfixes (code cleanup):
4469 - When loading the microdesc journal, remember its current size.
4470 In 0.2.2, this helps prevent the microdesc journal from growing
4471 without limit on authorities (who are the only ones to use it in
4472 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4473 Fix posted by "cypherpunks."
4474 - The microdesc journal is supposed to get rebuilt only if it is
4475 at least _half_ the length of the store, not _twice_ the length
4476 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4477 - Fix a potential null-pointer dereference while computing a
4478 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4480 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4481 cache without actually having any descriptors to cache. Bugfix on
4482 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4483 - If we fail to compute the identity digest of a v3 legacy keypair,
4484 warn, and don't use a buffer-full of junk instead. Bugfix on
4485 0.2.1.1-alpha; fixes bug 3106.
4486 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4487 where if the function had ever in the future been used to check
4488 for the presence of a too-large number, it would have given an
4489 incorrect result. (Fortunately, we only used it for 16-bit
4490 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4491 - Require that introduction point keys and onion handshake keys
4492 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4496 - Caches no longer download and serve v2 networkstatus documents
4497 unless FetchV2Networkstatus flag is set: these documents haven't
4498 haven't been used by clients or relays since 0.2.0.x. Resolves
4502 Changes in version 0.2.3.1-alpha - 2011-05-05
4503 Tor 0.2.3.1-alpha adds some new experimental features, including support
4504 for an improved network IO backend, IOCP networking on Windows,
4505 microdescriptor caching, "fast-start" support for streams, and automatic
4506 home router configuration. There are also numerous internal improvements
4507 to try to make the code easier for developers to work with.
4509 This is the first alpha release in a new series, so expect there to be
4510 bugs. Users who would rather test out a more stable branch should
4511 stay with 0.2.2.x for now.
4514 - Tor can now optionally build with the "bufferevents" buffered IO
4515 backend provided by Libevent 2. To use this feature, make sure you
4516 have the latest possible version of Libevent, and pass the
4517 --enable-bufferevents flag to configure when building Tor from
4518 source. This feature will make our networking code more flexible,
4519 let us stack layers on each other, and let us use more efficient
4520 zero-copy transports where available.
4521 - As an experimental feature, Tor can use IOCP for networking on Windows.
4522 Once this code is tuned and optimized, it promises much better
4523 performance than the select-based backend we've used in the past. To
4524 try this feature, you must build Tor with Libevent 2, configure Tor
4525 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4526 your torrc. There are known bugs here: only try this if you can help
4527 debug it as it breaks.
4528 - The EntryNodes option can now include country codes like {de} or IP
4529 addresses or network masks. Previously we had disallowed these options
4530 because we didn't have an efficient way to keep the list up to
4531 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4532 - Exit nodes now accept and queue data on not-yet-connected streams.
4533 Previously, the client wasn't allowed to send data until the stream was
4534 connected, which slowed down all connections. This change will enable
4535 clients to perform a "fast-start" on streams and send data without
4536 having to wait for a confirmation that the stream has opened. (Patch
4537 from Ian Goldberg; implements the server side of Proposal 174.)
4538 - Tor now has initial support for automatic port mapping on the many
4539 home routers that support NAT-PMP or UPnP. (Not yet supported on
4540 Windows). To build the support code, you'll need to have libnatpnp
4541 library and/or the libminiupnpc library, and you'll need to enable the
4542 feature specifically by passing "--enable-upnp" and/or
4543 "--enable-natpnp" to configure. To turn it on, use the new
4544 PortForwarding option.
4545 - Caches now download, cache, and serve multiple "flavors" of the
4546 consensus, including a flavor that describes microdescriptors.
4547 - Caches now download, cache, and serve microdescriptors -- small
4548 summaries of router descriptors that are authenticated by all of the
4549 directory authorities. Once enough caches are running this code,
4550 clients will be able to save significant amounts of directory bandwidth
4551 by downloading microdescriptors instead of router descriptors.
4554 - Make logging resolution configurable with a new LogTimeGranularity
4555 option, and change the default from 1 millisecond to 1 second.
4556 Implements enhancement 1668.
4557 - We log which torrc file we're using on startup. Implements ticket
4559 - Ordinarily, Tor does not count traffic from private addresses (like
4560 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4561 There is now a new option, CountPrivateBandwidth, to disable this
4562 behavior. Patch from Daniel Cagara.
4563 - New --enable-static-tor configure option for building Tor as
4564 statically as possible. Idea, general hackery and thoughts from
4565 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4567 - If you set the NumCPUs option to 0, Tor will now try to detect how
4568 many CPUs you have. This is the new default behavior.
4569 - Turn on directory request statistics by default and include them in
4570 extra-info descriptors. Don't break if we have no GeoIP database.
4571 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4572 bidirectional use of connections to disk every 24 hours.
4573 - Add a GeoIP file digest to the extra-info descriptor. Implements
4575 - The NodeFamily option -- which let you declare that you want to
4576 consider nodes to be part of a family whether they list themselves
4577 that way or not -- now allows IP address ranges and country codes.
4578 - Add a new 'Heartbeat' log message type to periodically log a message
4579 describing Tor's status at level Notice. This feature is meant for
4580 operators who log at notice, and want to make sure that their Tor
4581 server is still working. Implementation by George Kadianakis.
4583 o Minor bugfixes (on 0.2.2.25-alpha):
4584 - When loading the microdesc journal, remember its current size.
4585 In 0.2.2, this helps prevent the microdesc journal from growing
4586 without limit on authorities (who are the only ones to use it in
4587 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4588 Fix posted by "cypherpunks."
4589 - The microdesc journal is supposed to get rebuilt only if it is
4590 at least _half_ the length of the store, not _twice_ the length
4591 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4592 - If as an authority we fail to compute the identity digest of a v3
4593 legacy keypair, warn, and don't use a buffer-full of junk instead.
4594 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4595 - Authorities now clean their microdesc cache periodically and when
4596 reading from disk initially, not only when adding new descriptors.
4597 This prevents a bug where we could lose microdescriptors. Bugfix
4600 o Minor features (controller):
4601 - Add a new SIGNAL event to the controller interface so that
4602 controllers can be notified when Tor handles a signal. Resolves
4603 issue 1955. Patch by John Brooks.
4604 - Add a new GETINFO option to get total bytes read and written. Patch
4605 from pipe, revised by atagar. Resolves ticket 2345.
4606 - Implement some GETINFO controller fields to provide information about
4607 the Tor process's pid, euid, username, and resource limits.
4610 - Our build system requires automake 1.6 or later to create the
4611 Makefile.in files. Previously, you could have used 1.4.
4612 This only affects developers and people building Tor from git;
4613 people who build Tor from the source distribution without changing
4614 the Makefile.am files should be fine.
4615 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4616 so on. This is more robust against some of the failure modes
4617 associated with running the autotools pieces on their own.
4619 o Minor packaging issues:
4620 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4621 already created. Patch from Andreas Stieger. Fixes bug 2573.
4623 o Code simplifications and refactoring:
4624 - A major revision to our internal node-selecting and listing logic.
4625 Tor already had at least two major ways to look at the question of
4626 "which Tor servers do we know about": a list of router descriptors,
4627 and a list of entries in the current consensus. With
4628 microdescriptors, we're adding a third. Having so many systems
4629 without an abstraction layer over them was hurting the codebase.
4630 Now, we have a new "node_t" abstraction that presents a consistent
4631 interface to a client's view of a Tor node, and holds (nearly) all
4632 of the mutable state formerly in routerinfo_t and routerstatus_t.
4633 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4634 no longer link against Libevent: they never used it, but
4635 our library structure used to force them to link it.
4638 - Remove some old code to work around even older versions of Tor that
4639 used forked processes to handle DNS requests. Such versions of Tor
4640 are no longer in use as servers.
4642 o Documentation fixes:
4643 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4644 - Add missing documentation for the authority-related torrc options
4645 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4649 Changes in version 0.2.2.25-alpha - 2011-04-29
4650 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4651 robust, routers no longer overreport their bandwidth, Win7 should crash
4652 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4653 now prevents hidden service-related activity from being linkable. It
4654 provides more information to Vidalia so you can see if your bridge is
4655 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4656 StrictNodes configuration options to make them more reliable, more
4657 understandable, and more regularly applied. If you use those options,
4658 please see the revised documentation for them in the manual page.
4661 - Relays were publishing grossly inflated bandwidth values because
4662 they were writing their state files wrong--now they write the
4663 correct value. Also, resume reading bandwidth history from the
4664 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4665 - Improve hidden service robustness: When we find that we have
4666 extended a hidden service's introduction circuit to a relay not
4667 listed as an introduction point in the HS descriptor we currently
4668 have, retry with an introduction point from the current
4669 descriptor. Previously we would just give up. Fixes bugs 1024 and
4670 1930; bugfix on 0.2.0.10-alpha.
4671 - Clients now stop trying to use an exit node associated with a given
4672 destination by TrackHostExits if they fail to reach that exit node.
4673 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4674 - Fix crash bug on platforms where gmtime and localtime can return
4675 NULL. Windows 7 users were running into this one. Fixes part of bug
4676 2077. Bugfix on all versions of Tor. Found by boboper.
4678 o Security and stability fixes:
4679 - Don't double-free a parsable, but invalid, microdescriptor, even if
4680 it is followed in the blob we're parsing by an unparsable
4681 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4682 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4683 - If the Nickname configuration option isn't given, Tor would pick a
4684 nickname based on the local hostname as the nickname for a relay.
4685 Because nicknames are not very important in today's Tor and the
4686 "Unnamed" nickname has been implemented, this is now problematic
4687 behavior: It leaks information about the hostname without being
4688 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4689 introduced the Unnamed nickname. Reported by tagnaq.
4690 - Fix an uncommon assertion failure when running with DNSPort under
4691 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4692 - Avoid linkability based on cached hidden service descriptors: forget
4693 all hidden service descriptors cached as a client when processing a
4694 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4697 - Export GeoIP information on bridge usage to controllers even if we
4698 have not yet been running for 24 hours. Now Vidalia bridge operators
4699 can get more accurate and immediate feedback about their
4700 contributions to the network.
4702 o Major features and bugfixes (node selection):
4703 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4704 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4705 options. Previously, we had been ambiguous in describing what
4706 counted as an "exit" node, and what operations exactly "StrictNodes
4707 0" would permit. This created confusion when people saw nodes built
4708 through unexpected circuits, and made it hard to tell real bugs from
4709 surprises. Now the intended behavior is:
4710 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4711 a node that delivers user traffic outside the Tor network.
4712 . "Entry", in the context of EntryNodes, means a node used as the
4713 first hop of a multihop circuit. It doesn't include direct
4714 connections to directory servers.
4715 . "ExcludeNodes" applies to all nodes.
4716 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4717 StrictNodes is set, Tor should avoid all nodes listed in
4718 ExcludeNodes, even when it will make user requests fail. When
4719 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4720 whenever it can, except when it must use an excluded node to
4721 perform self-tests, connect to a hidden service, provide a
4722 hidden service, fulfill a .exit request, upload directory
4723 information, or fetch directory information.
4724 Collectively, the changes to implement the behavior fix bug 1090.
4725 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4726 a node is listed in both, it's treated as excluded.
4727 - ExcludeNodes now applies to directory nodes -- as a preference if
4728 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4729 Don't exclude all the directory authorities and set StrictNodes to 1
4730 unless you really want your Tor to break.
4731 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4732 - ExcludeExitNodes now overrides .exit requests.
4733 - We don't use bridges listed in ExcludeNodes.
4734 - When StrictNodes is 1:
4735 . We now apply ExcludeNodes to hidden service introduction points
4736 and to rendezvous points selected by hidden service users. This
4737 can make your hidden service less reliable: use it with caution!
4738 . If we have used ExcludeNodes on ourself, do not try relay
4739 reachability self-tests.
4740 . If we have excluded all the directory authorities, we will not
4741 even try to upload our descriptor if we're a relay.
4742 . Do not honor .exit requests to an excluded node.
4743 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4744 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4745 - When the set of permitted nodes changes, we now remove any mappings
4746 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4748 - We never cannibalize a circuit that had excluded nodes on it, even
4749 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4750 - Revert a change where we would be laxer about attaching streams to
4751 circuits than when building the circuits. This was meant to prevent
4752 a set of bugs where streams were never attachable, but our improved
4753 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
4754 - Keep track of how many times we launch a new circuit to handle a
4755 given stream. Too many launches could indicate an inconsistency
4756 between our "launch a circuit to handle this stream" logic and our
4757 "attach this stream to one of the available circuits" logic.
4758 - Improve log messages related to excluded nodes.
4761 - Fix a spurious warning when moving from a short month to a long
4762 month on relays with month-based BandwidthAccounting. Bugfix on
4763 0.2.2.17-alpha; fixes bug 3020.
4764 - When a client finds that an origin circuit has run out of 16-bit
4765 stream IDs, we now mark it as unusable for new streams. Previously,
4766 we would try to close the entire circuit. Bugfix on 0.0.6.
4767 - Add a forgotten cast that caused a compile warning on OS X 10.6.
4768 Bugfix on 0.2.2.24-alpha.
4769 - Be more careful about reporting the correct error from a failed
4770 connect() system call. Under some circumstances, it was possible to
4771 look at an incorrect value for errno when sending the end reason.
4772 Bugfix on 0.1.0.1-rc.
4773 - Correctly handle an "impossible" overflow cases in connection byte
4774 counting, where we write or read more than 4GB on an edge connection
4775 in a single second. Bugfix on 0.1.2.8-beta.
4776 - Correct the warning displayed when a rendezvous descriptor exceeds
4777 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4779 - Clients and hidden services now use HSDir-flagged relays for hidden
4780 service descriptor downloads and uploads even if the relays have no
4781 DirPort set and the client has disabled TunnelDirConns. This will
4782 eventually allow us to give the HSDir flag to relays with no
4783 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
4784 - Downgrade "no current certificates known for authority" message from
4785 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
4786 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
4787 2917. Bugfix on 0.1.1.1-alpha.
4788 - Only limit the lengths of single HS descriptors, even when multiple
4789 HS descriptors are published to an HSDir relay in a single POST
4790 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
4791 - Write the current time into the LastWritten line in our state file,
4792 rather than the time from the previous write attempt. Also, stop
4793 trying to use a time of -1 in our log statements. Fixes bug 3039;
4794 bugfix on 0.2.2.14-alpha.
4795 - Be more consistent in our treatment of file system paths. "~" should
4796 get expanded to the user's home directory in the Log config option.
4797 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
4798 feature for the -f and --DataDirectory options.
4801 - Make sure every relay writes a state file at least every 12 hours.
4802 Previously, a relay could go for weeks without writing its state
4803 file, and on a crash could lose its bandwidth history, capacity
4804 estimates, client country statistics, and so on. Addresses bug 3012.
4805 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
4806 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
4807 clients are already deprecated because of security bugs.
4808 - Don't allow v0 hidden service authorities to act as clients.
4809 Required by fix for bug 3000.
4810 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
4811 by fix for bug 3000.
4812 - Ensure that no empty [dirreq-](read|write)-history lines are added
4813 to an extrainfo document. Implements ticket 2497.
4815 o Code simplification and refactoring:
4816 - Remove workaround code to handle directory responses from servers
4817 that had bug 539 (they would send HTTP status 503 responses _and_
4818 send a body too). Since only server versions before
4819 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
4820 keep the workaround in place.
4821 - Remove the old 'fuzzy time' logic. It was supposed to be used for
4822 handling calculations where we have a known amount of clock skew and
4823 an allowed amount of unknown skew. But we only used it in three
4824 places, and we never adjusted the known/unknown skew values. This is
4825 still something we might want to do someday, but if we do, we'll
4826 want to do it differently.
4827 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4828 None of the cases where we did this before were wrong, but by making
4829 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4830 - Use GetTempDir to find the proper temporary directory location on
4831 Windows when generating temporary files for the unit tests. Patch by
4835 Changes in version 0.2.2.24-alpha - 2011-04-08
4836 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
4837 prevented Tor clients from effectively using "multihomed" bridges,
4838 that is, bridges that listen on multiple ports or IP addresses so users
4839 can continue to use some of their addresses even if others get blocked.
4842 - Fix a bug where bridge users who configure the non-canonical
4843 address of a bridge automatically switch to its canonical
4844 address. If a bridge listens at more than one address, it should be
4845 able to advertise those addresses independently and any non-blocked
4846 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
4848 - If you configured Tor to use bridge A, and then quit and
4849 configured Tor to use bridge B instead, it would happily continue
4850 to use bridge A if it's still reachable. While this behavior is
4851 a feature if your goal is connectivity, in some scenarios it's a
4852 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
4853 - Directory authorities now use data collected from their own
4854 uptime observations when choosing whether to assign the HSDir flag
4855 to relays, instead of trusting the uptime value the relay reports in
4856 its descriptor. This change helps prevent an attack where a small
4857 set of nodes with frequently-changing identity keys can blackhole
4858 a hidden service. (Only authorities need upgrade; others will be
4859 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
4862 - When we restart our relay, we might get a successful connection
4863 from the outside before we've started our reachability tests,
4864 triggering a warning: "ORPort found reachable, but I have no
4865 routerinfo yet. Failing to inform controller of success." This
4866 bug was harmless unless Tor is running under a controller
4867 like Vidalia, in which case the controller would never get a
4868 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4870 - Make directory authorities more accurate at recording when
4871 relays that have failed several reachability tests became
4872 unreachable, so we can provide more accuracy at assigning Stable,
4873 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
4874 - Fix an issue that prevented static linking of libevent on
4875 some platforms (notably Linux). Fixes bug 2698; bugfix on
4876 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
4877 the --with-static-libevent configure option).
4878 - We now ask the other side of a stream (the client or the exit)
4879 for more data on that stream when the amount of queued data on
4880 that stream dips low enough. Previously, we wouldn't ask the
4881 other side for more data until either it sent us more data (which
4882 it wasn't supposed to do if it had exhausted its window!) or we
4883 had completely flushed all our queued data. This flow control fix
4884 should improve throughput. Fixes bug 2756; bugfix on the earliest
4885 released versions of Tor (svn commit r152).
4886 - Avoid a double-mark-for-free warning when failing to attach a
4887 transparent proxy connection. (We thought we had fixed this in
4888 0.2.2.23-alpha, but it turns out our fix was checking the wrong
4889 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
4890 bug) and 0.2.2.23-alpha (the incorrect fix).
4891 - When warning about missing zlib development packages during compile,
4892 give the correct package names. Bugfix on 0.2.0.1-alpha.
4895 - Directory authorities now log the source of a rejected POSTed v3
4897 - Make compilation with clang possible when using
4898 --enable-gcc-warnings by removing two warning options that clang
4899 hasn't implemented yet and by fixing a few warnings. Implements
4901 - When expiring circuits, use microsecond timers rather than
4902 one-second timers. This can avoid an unpleasant situation where a
4903 circuit is launched near the end of one second and expired right
4904 near the beginning of the next, and prevent fluctuations in circuit
4906 - Use computed circuit-build timeouts to decide when to launch
4907 parallel introduction circuits for hidden services. (Previously,
4908 we would retry after 15 seconds.)
4909 - Update to the April 1 2011 Maxmind GeoLite Country database.
4912 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4913 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4915 o Documentation changes:
4916 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
4917 - Resolve all doxygen warnings except those for missing documentation.
4919 - Add doxygen documentation for more functions, fields, and types.
4922 Changes in version 0.2.2.23-alpha - 2011-03-08
4923 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
4924 they restart they don't lose their bandwidth capacity estimate. This
4925 release also fixes a diverse set of user-facing bugs, ranging from
4926 relays overrunning their rate limiting to clients falsely warning about
4927 clock skew to bridge descriptor leaks by our bridge directory authority.
4930 - Stop sending a CLOCK_SKEW controller status event whenever
4931 we fetch directory information from a relay that has a wrong clock.
4932 Instead, only inform the controller when it's a trusted authority
4933 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4934 the rest of bug 1074.
4935 - Fix an assert in parsing router descriptors containing IPv6
4936 addresses. This one took down the directory authorities when
4937 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4938 - Make the bridge directory authority refuse to answer directory
4939 requests for "all" descriptors. It used to include bridge
4940 descriptors in its answer, which was a major information leak.
4941 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4942 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4943 Tor would ignore their RelayBandwidthBurst setting,
4944 potentially using more bandwidth than expected. Bugfix on
4945 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4946 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4947 hidserv" in her torrc. The 'hidserv' argument never controlled
4948 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4951 - Relays now save observed peak bandwidth throughput rates to their
4952 state file (along with total usage, which was already saved)
4953 so that they can determine their correct estimated bandwidth on
4954 restart. Resolves bug 1863, where Tor relays would reset their
4955 estimated bandwidth to 0 after restarting.
4956 - Directory authorities now take changes in router IP address and
4957 ORPort into account when determining router stability. Previously,
4958 if a router changed its IP or ORPort, the authorities would not
4959 treat it as having any downtime for the purposes of stability
4960 calculation, whereas clients would experience downtime since the
4961 change could take a while to propagate to them. Resolves issue 1035.
4962 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4963 Prevention (DEP) by default on Windows to make it harder for
4964 attackers to exploit vulnerabilities. Patch from John Brooks.
4966 o Minor bugfixes (on 0.2.1.x and earlier):
4967 - Fix a rare crash bug that could occur when a client was configured
4968 with a large number of bridges. Fixes bug 2629; bugfix on
4969 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4970 - Avoid a double mark-for-free warning when failing to attach a
4971 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4973 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4974 found by "cypherpunks". This bug was introduced before the first
4975 Tor release, in svn commit r110.
4976 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
4977 don't mention them in the manpage. Fixes bug 2450; issue
4978 spotted by keb and G-Lo.
4979 - Fix a bug in bandwidth history state parsing that could have been
4980 triggered if a future version of Tor ever changed the timing
4981 granularity at which bandwidth history is measured. Bugfix on
4983 - When a relay decides that its DNS is too broken for it to serve
4984 as an exit server, it advertised itself as a non-exit, but
4985 continued to act as an exit. This could create accidental
4986 partitioning opportunities for users. Instead, if a relay is
4987 going to advertise reject *:* as its exit policy, it should
4988 really act with exit policy "reject *:*". Fixes bug 2366.
4989 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4990 - In the special case where you configure a public exit relay as your
4991 bridge, Tor would be willing to use that exit relay as the last
4992 hop in your circuit as well. Now we fail that circuit instead.
4993 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4994 - Fix a bug with our locking implementation on Windows that couldn't
4995 correctly detect when a file was already locked. Fixes bug 2504,
4996 bugfix on 0.2.1.6-alpha.
4997 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4998 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5000 - Set target port in get_interface_address6() correctly. Bugfix
5001 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5002 - Directory authorities are now more robust to hops back in time
5003 when calculating router stability. Previously, if a run of uptime
5004 or downtime appeared to be negative, the calculation could give
5005 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5007 - Fix an assert that got triggered when using the TestingTorNetwork
5008 configuration option and then issuing a GETINFO config-text control
5009 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5011 o Minor bugfixes (on 0.2.2.x):
5012 - Clients should not weight BadExit nodes as Exits in their node
5013 selection. Similarly, directory authorities should not count BadExit
5014 bandwidth as Exit bandwidth when computing bandwidth-weights.
5015 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5016 - Correctly clear our dir_read/dir_write history when there is an
5017 error parsing any bw history value from the state file. Bugfix on
5019 - Resolve a bug in verifying signatures of directory objects
5020 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5021 Fixes bug 2409. Found by "piebeer".
5022 - Bridge authorities no longer crash on SIGHUP when they try to
5023 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5027 - Log less aggressively about circuit timeout changes, and improve
5028 some other circuit timeout messages. Resolves bug 2004.
5029 - Log a little more clearly about the times at which we're no longer
5030 accepting new connections. Resolves bug 2181.
5031 - Reject attempts at the client side to open connections to private
5032 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5033 a randomly chosen exit node. Attempts to do so are always
5034 ill-defined, generally prevented by exit policies, and usually
5035 in error. This will also help to detect loops in transparent
5036 proxy configurations. You can disable this feature by setting
5037 "ClientRejectInternalAddresses 0" in your torrc.
5038 - Always treat failure to allocate an RSA key as an unrecoverable
5040 - Update to the March 1 2011 Maxmind GeoLite Country database.
5042 o Minor features (log subsystem):
5043 - Add documentation for configuring logging at different severities in
5044 different log domains. We've had this feature since 0.2.1.1-alpha,
5045 but for some reason it never made it into the manpage. Fixes
5047 - Make it simpler to specify "All log domains except for A and B".
5048 Previously you needed to say "[*,~A,~B]". Now you can just say
5050 - Add a "LogMessageDomains 1" option to include the domains of log
5051 messages along with the messages. Without this, there's no way
5052 to use log domains without reading the source or doing a lot
5055 o Packaging changes:
5056 - Stop shipping the Tor specs files and development proposal documents
5057 in the tarball. They are now in a separate git repository at
5058 git://git.torproject.org/torspec.git
5061 Changes in version 0.2.1.30 - 2011-02-23
5062 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5063 change is a slight tweak to Tor's TLS handshake that makes relays
5064 and bridges that run this new version reachable from Iran again.
5065 We don't expect this tweak will win the arms race long-term, but it
5066 buys us time until we roll out a better solution.
5069 - Stop sending a CLOCK_SKEW controller status event whenever
5070 we fetch directory information from a relay that has a wrong clock.
5071 Instead, only inform the controller when it's a trusted authority
5072 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5073 the rest of bug 1074.
5074 - Fix a bounds-checking error that could allow an attacker to
5075 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5077 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5078 Tor would ignore their RelayBandwidthBurst setting,
5079 potentially using more bandwidth than expected. Bugfix on
5080 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5081 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5082 hidserv" in her torrc. The 'hidserv' argument never controlled
5083 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5086 - Adjust our TLS Diffie-Hellman parameters to match those used by
5088 - Update to the February 1 2011 Maxmind GeoLite Country database.
5091 - Check for and reject overly long directory certificates and
5092 directory tokens before they have a chance to hit any assertions.
5093 Bugfix on 0.2.1.28. Found by "doorss".
5094 - Bring the logic that gathers routerinfos and assesses the
5095 acceptability of circuits into line. This prevents a Tor OP from
5096 getting locked in a cycle of choosing its local OR as an exit for a
5097 path (due to a .exit request) and then rejecting the circuit because
5098 its OR is not listed yet. It also prevents Tor clients from using an
5099 OR running in the same instance as an exit (due to a .exit request)
5100 if the OR does not meet the same requirements expected of an OR
5101 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5103 o Packaging changes:
5104 - Stop shipping the Tor specs files and development proposal documents
5105 in the tarball. They are now in a separate git repository at
5106 git://git.torproject.org/torspec.git
5107 - Do not include Git version tags as though they are SVN tags when
5108 generating a tarball from inside a repository that has switched
5109 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5112 Changes in version 0.2.2.22-alpha - 2011-01-25
5113 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5114 main other change is a slight tweak to Tor's TLS handshake that makes
5115 relays and bridges that run this new version reachable from Iran again.
5116 We don't expect this tweak will win the arms race long-term, but it
5117 will buy us a bit more time until we roll out a better solution.
5120 - Fix a bounds-checking error that could allow an attacker to
5121 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5123 - Don't assert when changing from bridge to relay or vice versa
5124 via the controller. The assert happened because we didn't properly
5125 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5126 bug 2433. Reported by bastik.
5129 - Adjust our TLS Diffie-Hellman parameters to match those used by
5131 - Provide a log message stating which geoip file we're parsing
5132 instead of just stating that we're parsing the geoip file.
5133 Implements ticket 2432.
5136 - Check for and reject overly long directory certificates and
5137 directory tokens before they have a chance to hit any assertions.
5138 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5141 Changes in version 0.2.2.21-alpha - 2011-01-15
5142 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5143 continues our recent code security audit work. The main fix resolves
5144 a remote heap overflow vulnerability that can allow remote code
5145 execution (CVE-2011-0427). Other fixes address a variety of assert
5146 and crash bugs, most of which we think are hard to exploit remotely.
5148 o Major bugfixes (security), also included in 0.2.1.29:
5149 - Fix a heap overflow bug where an adversary could cause heap
5150 corruption. This bug probably allows remote code execution
5151 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5153 - Prevent a denial-of-service attack by disallowing any
5154 zlib-compressed data whose compression factor is implausibly
5155 high. Fixes part of bug 2324; reported by "doorss".
5156 - Zero out a few more keys in memory before freeing them. Fixes
5157 bug 2384 and part of bug 2385. These key instances found by
5158 "cypherpunks", based on Andrew Case's report about being able
5159 to find sensitive data in Tor's memory space if you have enough
5160 permissions. Bugfix on 0.0.2pre9.
5162 o Major bugfixes (crashes), also included in 0.2.1.29:
5163 - Prevent calls to Libevent from inside Libevent log handlers.
5164 This had potential to cause a nasty set of crashes, especially
5165 if running Libevent with debug logging enabled, and running
5166 Tor with a controller watching for low-severity log messages.
5167 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5168 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5169 underflow errors there too. Fixes the other part of bug 2324.
5170 - Fix a bug where we would assert if we ever had a
5171 cached-descriptors.new file (or another file read directly into
5172 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5173 on 0.2.1.25. Found by doorss.
5174 - Fix some potential asserts and parsing issues with grossly
5175 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5178 o Minor bugfixes (other), also included in 0.2.1.29:
5179 - Fix a bug with handling misformed replies to reverse DNS lookup
5180 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5181 bug reported by doorss.
5182 - Fix compilation on mingw when a pthreads compatibility library
5183 has been installed. (We don't want to use it, so we shouldn't
5184 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5185 - Fix a bug where we would declare that we had run out of virtual
5186 addresses when the address space was only half-exhausted. Bugfix
5188 - Correctly handle the case where AutomapHostsOnResolve is set but
5189 no virtual addresses are available. Fixes bug 2328; bugfix on
5190 0.1.2.1-alpha. Bug found by doorss.
5191 - Correctly handle wrapping around when we run out of virtual
5192 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5194 o Minor features, also included in 0.2.1.29:
5195 - Update to the January 1 2011 Maxmind GeoLite Country database.
5196 - Introduce output size checks on all of our decryption functions.
5198 o Build changes, also included in 0.2.1.29:
5199 - Tor does not build packages correctly with Automake 1.6 and earlier;
5200 added a check to Makefile.am to make sure that we're building with
5201 Automake 1.7 or later.
5202 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5203 because we built it with a too-old version of automake. Thus that
5204 release broke ./configure --enable-openbsd-malloc, which is popular
5205 among really fast exit relays on Linux.
5207 o Major bugfixes, new in 0.2.2.21-alpha:
5208 - Prevent crash/heap corruption when the cbtnummodes consensus
5209 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5212 o Major features, new in 0.2.2.21-alpha:
5213 - Introduce minimum/maximum values that clients will believe
5214 from the consensus. Now we'll have a better chance to avoid crashes
5215 or worse when a consensus param has a weird value.
5217 o Minor features, new in 0.2.2.21-alpha:
5218 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5219 used on bridges, and it makes bridge scanning somewhat easier.
5220 - If writing the state file to disk fails, wait up to an hour before
5221 retrying again, rather than trying again each second. Fixes bug
5222 2346; bugfix on Tor 0.1.1.3-alpha.
5223 - Make Libevent log messages get delivered to controllers later,
5224 and not from inside the Libevent log handler. This prevents unsafe
5225 reentrant Libevent calls while still letting the log messages
5227 - Detect platforms that brokenly use a signed size_t, and refuse to
5228 build there. Found and analyzed by doorss and rransom.
5229 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5232 o Minor bugfixes, new in 0.2.2.21-alpha:
5233 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5234 than waiting forever for them to finish. Fixes bug 2330; bugfix
5235 on 0.2.0.16-alpha. Found by doorss.
5236 - Add assertions to check for overflow in arguments to
5237 base32_encode() and base32_decode(); fix a signed-unsigned
5238 comparison there too. These bugs are not actually reachable in Tor,
5239 but it's good to prevent future errors too. Found by doorss.
5240 - Correctly detect failures to create DNS requests when using Libevent
5241 versions before v2. (Before Libevent 2, we used our own evdns
5242 implementation. Its return values for Libevent's evdns_resolve_*()
5243 functions are not consistent with those from Libevent.) Fixes bug
5244 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5246 o Documentation, new in 0.2.2.21-alpha:
5247 - Document the default socks host and port (127.0.0.1:9050) for
5251 Changes in version 0.2.1.29 - 2011-01-15
5252 Tor 0.2.1.29 continues our recent code security audit work. The main
5253 fix resolves a remote heap overflow vulnerability that can allow remote
5254 code execution. Other fixes address a variety of assert and crash bugs,
5255 most of which we think are hard to exploit remotely.
5257 o Major bugfixes (security):
5258 - Fix a heap overflow bug where an adversary could cause heap
5259 corruption. This bug probably allows remote code execution
5260 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5262 - Prevent a denial-of-service attack by disallowing any
5263 zlib-compressed data whose compression factor is implausibly
5264 high. Fixes part of bug 2324; reported by "doorss".
5265 - Zero out a few more keys in memory before freeing them. Fixes
5266 bug 2384 and part of bug 2385. These key instances found by
5267 "cypherpunks", based on Andrew Case's report about being able
5268 to find sensitive data in Tor's memory space if you have enough
5269 permissions. Bugfix on 0.0.2pre9.
5271 o Major bugfixes (crashes):
5272 - Prevent calls to Libevent from inside Libevent log handlers.
5273 This had potential to cause a nasty set of crashes, especially
5274 if running Libevent with debug logging enabled, and running
5275 Tor with a controller watching for low-severity log messages.
5276 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5277 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5278 underflow errors there too. Fixes the other part of bug 2324.
5279 - Fix a bug where we would assert if we ever had a
5280 cached-descriptors.new file (or another file read directly into
5281 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5282 on 0.2.1.25. Found by doorss.
5283 - Fix some potential asserts and parsing issues with grossly
5284 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5287 o Minor bugfixes (other):
5288 - Fix a bug with handling misformed replies to reverse DNS lookup
5289 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5290 bug reported by doorss.
5291 - Fix compilation on mingw when a pthreads compatibility library
5292 has been installed. (We don't want to use it, so we shouldn't
5293 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5294 - Fix a bug where we would declare that we had run out of virtual
5295 addresses when the address space was only half-exhausted. Bugfix
5297 - Correctly handle the case where AutomapHostsOnResolve is set but
5298 no virtual addresses are available. Fixes bug 2328; bugfix on
5299 0.1.2.1-alpha. Bug found by doorss.
5300 - Correctly handle wrapping around to when we run out of virtual
5301 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5302 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5303 because we built it with a too-old version of automake. Thus that
5304 release broke ./configure --enable-openbsd-malloc, which is popular
5305 among really fast exit relays on Linux.
5308 - Update to the January 1 2011 Maxmind GeoLite Country database.
5309 - Introduce output size checks on all of our decryption functions.
5312 - Tor does not build packages correctly with Automake 1.6 and earlier;
5313 added a check to Makefile.am to make sure that we're building with
5314 Automake 1.7 or later.
5317 Changes in version 0.2.2.20-alpha - 2010-12-17
5318 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5319 exploitable bugs. We also fix a variety of other significant bugs,
5320 change the IP address for one of our directory authorities, and update
5321 the minimum version that Tor relays must run to join the network.
5324 - Fix a remotely exploitable bug that could be used to crash instances
5325 of Tor remotely by overflowing on the heap. Remote-code execution
5326 hasn't been confirmed, but can't be ruled out. Everyone should
5327 upgrade. Bugfix on the 0.1.1 series and later.
5328 - Fix a bug that could break accounting on 64-bit systems with large
5329 time_t values, making them hibernate for impossibly long intervals.
5330 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5331 - Fix a logic error in directory_fetches_from_authorities() that
5332 would cause all _non_-exits refusing single-hop-like circuits
5333 to fetch from authorities, when we wanted to have _exits_ fetch
5334 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5336 - Fix a stream fairness bug that would cause newer streams on a given
5337 circuit to get preference when reading bytes from the origin or
5338 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5339 introduced before the first Tor release, in svn revision r152.
5341 o Directory authority changes:
5342 - Change IP address and ports for gabelmoo (v3 directory authority).
5345 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5346 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5347 - Fix an off-by-one error in calculating some controller command
5348 argument lengths. Fortunately, this mistake is harmless since
5349 the controller code does redundant NUL termination too. Found by
5350 boboper. Bugfix on 0.1.1.1-alpha.
5351 - Do not dereference NULL if a bridge fails to build its
5352 extra-info descriptor. Found by an anonymous commenter on
5353 Trac. Bugfix on 0.2.2.19-alpha.
5356 - Update to the December 1 2010 Maxmind GeoLite Country database.
5357 - Directory authorities now reject relays running any versions of
5358 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5359 known bugs that keep RELAY_EARLY cells from working on rendezvous
5360 circuits. Followup to fix for bug 2081.
5361 - Directory authorities now reject relays running any version of Tor
5362 older than 0.2.0.26-rc. That version is the earliest that fetches
5363 current directory information correctly. Fixes bug 2156.
5364 - Report only the top 10 ports in exit-port stats in order not to
5365 exceed the maximum extra-info descriptor length of 50 KB. Implements
5369 Changes in version 0.2.1.28 - 2010-12-17
5370 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5371 exploitable bugs. We also took this opportunity to change the IP address
5372 for one of our directory authorities, and to update the geoip database
5376 - Fix a remotely exploitable bug that could be used to crash instances
5377 of Tor remotely by overflowing on the heap. Remote-code execution
5378 hasn't been confirmed, but can't be ruled out. Everyone should
5379 upgrade. Bugfix on the 0.1.1 series and later.
5381 o Directory authority changes:
5382 - Change IP address and ports for gabelmoo (v3 directory authority).
5385 - Update to the December 1 2010 Maxmind GeoLite Country database.
5388 Changes in version 0.2.1.27 - 2010-11-23
5389 Yet another OpenSSL security patch broke its compatibility with Tor:
5390 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5391 also took this opportunity to fix several crash bugs, integrate a new
5392 directory authority, and update the bundled GeoIP database.
5395 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5396 No longer set the tlsext_host_name extension on server SSL objects;
5397 but continue to set it on client SSL objects. Our goal in setting
5398 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5399 bugfix on 0.2.1.1-alpha.
5400 - Do not log messages to the controller while shrinking buffer
5401 freelists. Doing so would sometimes make the controller connection
5402 try to allocate a buffer chunk, which would mess up the internals
5403 of the freelist and cause an assertion failure. Fixes bug 1125;
5404 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5405 - Learn our external IP address when we're a relay or bridge, even if
5406 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5407 where we introduced bridge relays that don't need to publish to
5408 be useful. Fixes bug 2050.
5409 - Do even more to reject (and not just ignore) annotations on
5410 router descriptors received anywhere but from the cache. Previously
5411 we would ignore such annotations at first, but cache them to disk
5412 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5413 - When you're using bridges and your network goes away and your
5414 bridges get marked as down, recover when you attempt a new socks
5415 connection (if the network is back), rather than waiting up to an
5416 hour to try fetching new descriptors for your bridges. Bugfix on
5417 0.2.0.3-alpha; fixes bug 1981.
5420 - Move to the November 2010 Maxmind GeoLite country db (rather
5421 than the June 2009 ip-to-country GeoIP db) for our statistics that
5422 count how many users relays are seeing from each country. Now we'll
5423 have more accurate data, especially for many African countries.
5425 o New directory authorities:
5426 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5430 - Fix an assertion failure that could occur in directory caches or
5431 bridge users when using a very short voting interval on a testing
5432 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5434 - Enforce multiplicity rules when parsing annotations. Bugfix on
5435 0.2.0.8-alpha. Found by piebeer.
5436 - Allow handshaking OR connections to take a full KeepalivePeriod
5437 seconds to handshake. Previously, we would close them after
5438 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5439 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5441 - When building with --enable-gcc-warnings on OpenBSD, disable
5442 warnings in system headers. This makes --enable-gcc-warnings
5443 pass on OpenBSD 4.8.
5446 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5447 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5448 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5449 Servers can start sending this code when enough clients recognize
5450 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5451 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5452 Patch from mingw-san.
5455 - Remove the old debian/ directory from the main Tor distribution.
5456 The official Tor-for-debian git repository lives at the URL
5457 https://git.torproject.org/debian/tor.git
5458 - Stop shipping the old doc/website/ directory in the tarball. We
5459 changed the website format in late 2010, and what we shipped in
5460 0.2.1.26 really wasn't that useful anyway.
5463 Changes in version 0.2.2.19-alpha - 2010-11-22
5464 Yet another OpenSSL security patch broke its compatibility with Tor:
5465 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5468 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5469 No longer set the tlsext_host_name extension on server SSL objects;
5470 but continue to set it on client SSL objects. Our goal in setting
5471 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5472 bugfix on 0.2.1.1-alpha.
5475 - Try harder not to exceed the maximum length of 50 KB when writing
5476 statistics to extra-info descriptors. This bug was triggered by very
5477 fast relays reporting exit-port, entry, and dirreq statistics.
5478 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5479 - Publish a router descriptor even if generating an extra-info
5480 descriptor fails. Previously we would not publish a router
5481 descriptor without an extra-info descriptor; this can cause fast
5482 exit relays collecting exit-port statistics to drop from the
5483 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5486 Changes in version 0.2.2.18-alpha - 2010-11-16
5487 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5488 us lately, makes unpublished bridge relays able to detect their IP
5489 address, and fixes a wide variety of other bugs to get us much closer
5490 to a stable release.
5493 - Do even more to reject (and not just ignore) annotations on
5494 router descriptors received anywhere but from the cache. Previously
5495 we would ignore such annotations at first, but cache them to disk
5496 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5497 - Do not log messages to the controller while shrinking buffer
5498 freelists. Doing so would sometimes make the controller connection
5499 try to allocate a buffer chunk, which would mess up the internals
5500 of the freelist and cause an assertion failure. Fixes bug 1125;
5501 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5502 - Learn our external IP address when we're a relay or bridge, even if
5503 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5504 where we introduced bridge relays that don't need to publish to
5505 be useful. Fixes bug 2050.
5506 - Maintain separate TLS contexts and certificates for incoming and
5507 outgoing connections in bridge relays. Previously we would use the
5508 same TLS contexts and certs for incoming and outgoing connections.
5509 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5510 - Maintain separate identity keys for incoming and outgoing TLS
5511 contexts in bridge relays. Previously we would use the same
5512 identity keys for incoming and outgoing TLS contexts. Bugfix on
5513 0.2.0.3-alpha; addresses the other half of bug 988.
5514 - Avoid an assertion failure when we as an authority receive a
5515 duplicate upload of a router descriptor that we already have,
5516 but which we previously considered an obsolete descriptor.
5517 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5518 - Avoid a crash bug triggered by looking at a dangling pointer while
5519 setting the network status consensus. Found by Robert Ransom.
5520 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5521 - Fix a logic error where servers that _didn't_ act as exits would
5522 try to keep their server lists more aggressively up to date than
5523 exits, when it was supposed to be the other way around. Bugfix
5526 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5527 - When we're trying to guess whether we know our IP address as
5528 a relay, we would log various ways that we failed to guess
5529 our address, but never log that we ended up guessing it
5530 successfully. Now add a log line to help confused and anxious
5531 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5532 - Bring the logic that gathers routerinfos and assesses the
5533 acceptability of circuits into line. This prevents a Tor OP from
5534 getting locked in a cycle of choosing its local OR as an exit for a
5535 path (due to a .exit request) and then rejecting the circuit because
5536 its OR is not listed yet. It also prevents Tor clients from using an
5537 OR running in the same instance as an exit (due to a .exit request)
5538 if the OR does not meet the same requirements expected of an OR
5539 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5540 - Correctly describe errors that occur when generating a TLS object.
5541 Previously we would attribute them to a failure while generating a
5542 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5544 - Enforce multiplicity rules when parsing annotations. Bugfix on
5545 0.2.0.8-alpha. Found by piebeer.
5546 - Fix warnings that newer versions of autoconf produced during
5547 ./autogen.sh. These warnings appear to be harmless in our case,
5548 but they were extremely verbose. Fixes bug 2020.
5550 o Minor bugfixes (on Tor 0.2.2.x):
5551 - Enable protection of small arrays whenever we build with gcc
5552 hardening features, not only when also building with warnings
5553 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5556 - Make hidden services work better in private Tor networks by not
5557 requiring any uptime to join the hidden service descriptor
5558 DHT. Implements ticket 2088.
5559 - Rate-limit the "your application is giving Tor only an IP address"
5560 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5561 - When AllowSingleHopExits is set, print a warning to explain to the
5562 relay operator why most clients are avoiding her relay.
5563 - Update to the November 1 2010 Maxmind GeoLite Country database.
5565 o Code simplifications and refactoring:
5566 - When we fixed bug 1038 we had to put in a restriction not to send
5567 RELAY_EARLY cells on rend circuits. This was necessary as long
5568 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5569 active. Now remove this obsolete check. Resolves bug 2081.
5570 - Some options used different conventions for uppercasing of acronyms
5571 when comparing manpage and source. Fix those in favor of the
5572 manpage, as it makes sense to capitalize acronyms.
5573 - Remove the torrc.complete file. It hasn't been kept up to date
5574 and users will have better luck checking out the manpage.
5575 - Remove the obsolete "NoPublish" option; it has been flagged
5576 as obsolete and has produced a warning since 0.1.1.18-rc.
5577 - Remove everything related to building the expert bundle for OS X.
5578 It has confused many users, doesn't work right on OS X 10.6,
5579 and is hard to get rid of once installed. Resolves bug 1274.
5582 Changes in version 0.2.2.17-alpha - 2010-09-30
5583 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5584 to use one-hop circuits (which can put the exit relays at higher risk,
5585 plus unbalance the network); fixes a big bug in bandwidth accounting
5586 for relays that want to limit their monthly bandwidth use; fixes a
5587 big pile of bugs in how clients tolerate temporary network failure;
5588 and makes our adaptive circuit build timeout feature (which improves
5589 client performance if your network is fast while not breaking things
5590 if your network is slow) better handle bad networks.
5593 - Exit relays now try harder to block exit attempts from unknown
5594 relays, to make it harder for people to use them as one-hop proxies
5595 a la tortunnel. Controlled by the refuseunknownexits consensus
5596 parameter (currently enabled), or you can override it on your
5597 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5599 o Major bugfixes (0.2.1.x and earlier):
5600 - Fix a bug in bandwidth accounting that could make us use twice
5601 the intended bandwidth when our interval start changes due to
5602 daylight saving time. Now we tolerate skew in stored vs computed
5603 interval starts: if the start of the period changes by no more than
5604 50% of the period's duration, we remember bytes that we transferred
5605 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5606 - Always search the Windows system directory for system DLLs, and
5607 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5608 - When you're using bridges and your network goes away and your
5609 bridges get marked as down, recover when you attempt a new socks
5610 connection (if the network is back), rather than waiting up to an
5611 hour to try fetching new descriptors for your bridges. Bugfix on
5612 0.2.0.3-alpha; fixes bug 1981.
5614 o Major bugfixes (on 0.2.2.x):
5615 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5617 - Fix a segfault that could happen when operating a bridge relay with
5618 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5619 - The consensus bandwidth-weights (used by clients to choose fast
5620 relays) entered an unexpected edge case in September where
5621 Exits were much scarcer than Guards, resulting in bad weight
5622 recommendations. Now we compute them using new constraints that
5623 should succeed in all cases. Also alter directory authorities to
5624 not include the bandwidth-weights line if they fail to produce
5625 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5626 - When weighting bridges during path selection, we used to trust
5627 the bandwidths they provided in their descriptor, only capping them
5628 at 10MB/s. This turned out to be problematic for two reasons:
5629 Bridges could claim to handle a lot more traffic then they
5630 actually would, thus making more clients pick them and have a
5631 pretty effective DoS attack. The other issue is that new bridges
5632 that might not have a good estimate for their bw capacity yet
5633 would not get used at all unless no other bridges are available
5634 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5636 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5637 - Ignore cannibalized circuits when recording circuit build times.
5638 This should provide for a minor performance improvement for hidden
5639 service users using 0.2.2.14-alpha, and should remove two spurious
5640 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5641 - Simplify the logic that causes us to decide if the network is
5642 unavailable for purposes of recording circuit build times. If we
5643 receive no cells whatsoever for the entire duration of a circuit's
5644 full measured lifetime, the network is probably down. Also ignore
5645 one-hop directory fetching circuit timeouts when calculating our
5646 circuit build times. These changes should hopefully reduce the
5647 cases where we see ridiculous circuit build timeouts for people
5648 with spotty wireless connections. Fixes part of bug 1772; bugfix
5650 - Prevent the circuit build timeout from becoming larger than
5651 the maximum build time we have ever seen. Also, prevent the time
5652 period for measurement circuits from becoming larger than twice that
5653 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5656 - When we run out of directory information such that we can't build
5657 circuits, but then get enough that we can build circuits, log when
5658 we actually construct a circuit, so the user has a better chance of
5659 knowing what's going on. Fixes bug 1362.
5660 - Be more generous with how much bandwidth we'd use up (with
5661 accounting enabled) before entering "soft hibernation". Previously,
5662 we'd refuse new connections and circuits once we'd used up 95% of
5663 our allotment. Now, we use up 95% of our allotment, AND make sure
5664 that we have no more than 500MB (or 3 hours of expected traffic,
5665 whichever is lower) remaining before we enter soft hibernation.
5666 - If we've configured EntryNodes and our network goes away and/or all
5667 our entrynodes get marked down, optimistically retry them all when
5668 a new socks application request appears. Fixes bug 1882.
5669 - Add some more defensive programming for architectures that can't
5670 handle unaligned integer accesses. We don't know of any actual bugs
5671 right now, but that's the best time to fix them. Fixes bug 1943.
5672 - Support line continuations in the torrc config file. If a line
5673 ends with a single backslash character, the newline is ignored, and
5674 the configuration value is treated as continuing on the next line.
5677 o Minor bugfixes (on 0.2.1.x and earlier):
5678 - For bandwidth accounting, calculate our expected bandwidth rate
5679 based on the time during which we were active and not in
5680 soft-hibernation during the last interval. Previously, we were
5681 also considering the time spent in soft-hibernation. If this
5682 was a long time, we would wind up underestimating our bandwidth
5683 by a lot, and skewing our wakeup time towards the start of the
5684 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5686 o Minor bugfixes (on 0.2.2.x):
5687 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5688 which were disabled by the circuit build timeout changes in
5689 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5690 - Make sure we don't warn about missing bandwidth weights when
5691 choosing bridges or other relays not in the consensus. Bugfix on
5692 0.2.2.10-alpha; fixes bug 1805.
5693 - In our logs, do not double-report signatures from unrecognized
5694 authorities both as "from unknown authority" and "not
5695 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5698 Changes in version 0.2.2.16-alpha - 2010-09-17
5699 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5700 evident at exit relays), and also continues to resolve all the little
5701 bugs that have been filling up trac lately.
5703 o Major bugfixes (stream-level fairness):
5704 - When receiving a circuit-level SENDME for a blocked circuit, try
5705 to package cells fairly from all the streams that had previously
5706 been blocked on that circuit. Previously, we had started with the
5707 oldest stream, and allowed each stream to potentially exhaust
5708 the circuit's package window. This gave older streams on any
5709 given circuit priority over newer ones. Fixes bug 1937. Detected
5710 originally by Camilo Viecco. This bug was introduced before the
5711 first Tor release, in svn commit r152: it is the new winner of
5712 the longest-lived bug prize.
5713 - When the exit relay got a circuit-level sendme cell, it started
5714 reading on the exit streams, even if had 500 cells queued in the
5715 circuit queue already, so the circuit queue just grew and grew in
5716 some cases. We fix this by not re-enabling reading on receipt of a
5717 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5718 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5720 - Newly created streams were allowed to read cells onto circuits,
5721 even if the circuit's cell queue was blocked and waiting to drain.
5722 This created potential unfairness, as older streams would be
5723 blocked, but newer streams would gladly fill the queue completely.
5724 We add code to detect this situation and prevent any stream from
5725 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5729 - Update to the September 1 2010 Maxmind GeoLite Country database.
5730 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5731 not. This would lead to a cookie that is still not group readable.
5732 Closes bug 1843. Suggested by katmagic.
5733 - When logging a rate-limited warning, we now mention how many messages
5734 got suppressed since the last warning.
5735 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5736 do individual connection-level rate limiting of clients. The torrc
5737 config options with the same names trump the consensus params, if
5738 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5739 consensus params which were broken from 0.2.2.7-alpha through
5740 0.2.2.14-alpha. Closes bug 1947.
5741 - When a router changes IP address or port, authorities now launch
5742 a new reachability test for it. Implements ticket 1899.
5743 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5744 2 no signature, 4 required" messages about consensus signatures
5745 easier to read, and make sure they get logged at the same severity
5746 as the messages explaining which keys are which. Fixes bug 1290.
5747 - Don't warn when we have a consensus that we can't verify because
5748 of missing certificates, unless those certificates are ones
5749 that we have been trying and failing to download. Fixes bug 1145.
5750 - If you configure your bridge with a known identity fingerprint,
5751 and the bridge authority is unreachable (as it is in at least
5752 one country now), fall back to directly requesting the descriptor
5753 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5755 - When building with --enable-gcc-warnings on OpenBSD, disable
5756 warnings in system headers. This makes --enable-gcc-warnings
5757 pass on OpenBSD 4.8.
5759 o Minor bugfixes (on 0.2.1.x and earlier):
5760 - Authorities will now attempt to download consensuses if their
5761 own efforts to make a live consensus have failed. This change
5762 means authorities that restart will fetch a valid consensus, and
5763 it means authorities that didn't agree with the current consensus
5764 will still fetch and serve it if it has enough signatures. Bugfix
5765 on 0.2.0.9-alpha; fixes bug 1300.
5766 - Ensure DNS requests launched by "RESOLVE" commands from the
5767 controller respect the __LeaveStreamsUnattached setconf options. The
5768 same goes for requests launched via DNSPort or transparent
5769 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
5770 - Allow handshaking OR connections to take a full KeepalivePeriod
5771 seconds to handshake. Previously, we would close them after
5772 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5773 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5775 - Rate-limit "Failed to hand off onionskin" warnings.
5776 - Never relay a cell for a circuit we have already destroyed.
5777 Between marking a circuit as closeable and finally closing it,
5778 it may have been possible for a few queued cells to get relayed,
5779 even though they would have been immediately dropped by the next
5780 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
5781 - Never queue a cell for a circuit that's already been marked
5783 - Never vote for a server as "Running" if we have a descriptor for
5784 it claiming to be hibernating, and that descriptor was published
5785 more recently than our last contact with the server. Bugfix on
5786 0.2.0.3-alpha; fixes bug 911.
5787 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
5790 o Minor bugfixes (on 0.2.2.x):
5791 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
5792 down if a directory fetch fails and you've configured either
5793 bridges or EntryNodes. The intent was to mark the relay as down
5794 _unless_ you're using bridges or EntryNodes, since if you are
5795 then you could quickly run out of entry points.
5796 - Fix the Windows directory-listing code. A bug introduced in
5797 0.2.2.14-alpha could make Windows directory servers forget to load
5798 some of their cached v2 networkstatus files.
5799 - Really allow clients to use relays as bridges. Fixes bug 1776;
5800 bugfix on 0.2.2.15-alpha.
5801 - Demote a warn to info that happens when the CellStatistics option
5802 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
5803 Reported by Moritz Bartl.
5804 - On Windows, build correctly either with or without Unicode support.
5805 This is necessary so that Tor can support fringe platforms like
5806 Windows 98 (which has no Unicode), or Windows CE (which has no
5807 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
5810 - Add a unit test for cross-platform directory-listing code.
5813 Changes in version 0.2.2.15-alpha - 2010-08-18
5814 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
5815 fixes a variety of other bugs that were preventing performance
5816 experiments from moving forward, fixes several bothersome memory leaks,
5817 and generally closes a lot of smaller bugs that have been filling up
5821 - Stop assigning the HSDir flag to relays that disable their
5822 DirPort (and thus will refuse to answer directory requests). This
5823 fix should dramatically improve the reachability of hidden services:
5824 hidden services and hidden service clients pick six HSDir relays
5825 to store and retrieve the hidden service descriptor, and currently
5826 about half of the HSDir relays will refuse to work. Bugfix on
5827 0.2.0.10-alpha; fixes part of bug 1693.
5828 - The PerConnBWRate and Burst config options, along with the
5829 bwconnrate and bwconnburst consensus params, initialized each conn's
5830 token bucket values only when the connection is established. Now we
5831 update them if the config options change, and update them every time
5832 we get a new consensus. Otherwise we can encounter an ugly edge
5833 case where we initialize an OR conn to client-level bandwidth,
5834 but then later the relay joins the consensus and we leave it
5835 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
5836 - Fix a regression that caused Tor to rebind its ports if it receives
5837 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
5840 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
5841 should give us approximately 40-50% more Guard-flagged nodes,
5842 improving the anonymity the Tor network can provide and also
5843 decreasing the dropoff in throughput that relays experience when
5844 they first get the Guard flag.
5845 - Allow enabling or disabling the *Statistics config options while
5849 - Update to the August 1 2010 Maxmind GeoLite Country database.
5850 - Have the controller interface give a more useful message than
5851 "Internal Error" in response to failed GETINFO requests.
5852 - Warn when the same option is provided more than once in a torrc
5853 file, on the command line, or in a single SETCONF statement, and
5854 the option is one that only accepts a single line. Closes bug 1384.
5855 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5856 Patch from mingw-san.
5857 - Add support for the country code "{??}" in torrc options like
5858 ExcludeNodes, to indicate all routers of unknown country. Closes
5860 - Relays report the number of bytes spent on answering directory
5861 requests in extra-info descriptors similar to {read,write}-history.
5862 Implements enhancement 1790.
5864 o Minor bugfixes (on 0.2.1.x and earlier):
5865 - Complain if PublishServerDescriptor is given multiple arguments that
5866 include 0 or 1. This configuration will be rejected in the future.
5867 Bugfix on 0.2.0.1-alpha; closes bug 1107.
5868 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
5869 Bugfix on 0.2.0.13-alpha; closes bug 928.
5870 - Change "Application request when we're believed to be offline."
5871 notice to "Application request when we haven't used client
5872 functionality lately.", to clarify that it's not an error. Bugfix
5873 on 0.0.9.3; fixes bug 1222.
5874 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
5875 would return "551 Internal error" rather than "552 Unrecognized key
5876 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
5877 - Users can't configure a regular relay to be their bridge. It didn't
5878 work because when Tor fetched the bridge descriptor, it found
5879 that it already had it, and didn't realize that the purpose of the
5880 descriptor had changed. Now we replace routers with a purpose other
5881 than bridge with bridge descriptors when fetching them. Bugfix on
5882 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
5883 refetch the descriptor with router purpose 'general', disabling
5885 - Fix a rare bug in rend_fn unit tests: we would fail a test when
5886 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5887 on 0.2.0.10-alpha; fixes bug 1808.
5888 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5889 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5890 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5891 Servers can start sending this code when enough clients recognize
5892 it. Also update the spec to reflect this new reason. Bugfix on
5893 0.1.0.1-rc; fixes part of bug 1793.
5894 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
5895 when we switch from being a public relay to a bridge. Otherwise
5896 there will still be clients that see the relay in their consensus,
5897 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
5899 - Instead of giving an assertion failure on an internal mismatch
5900 on estimated freelist size, just log a BUG warning and try later.
5901 Mitigates but does not fix bug 1125.
5902 - Fix an assertion failure that could occur in caches or bridge users
5903 when using a very short voting interval on a testing network.
5904 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
5906 o Minor bugfixes (on 0.2.2.x):
5907 - Alter directory authorities to always consider Exit-flagged nodes
5908 as potential Guard nodes in their votes. The actual decision to
5909 use Exits as Guards is done in the consensus bandwidth weights.
5910 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
5911 - When the controller is reporting the purpose of circuits that
5912 didn't finish building before the circuit build timeout, it was
5913 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
5914 - Our libevent version parsing code couldn't handle versions like
5915 1.4.14b-stable and incorrectly warned the user about using an
5916 old and broken version of libevent. Treat 1.4.14b-stable like
5917 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
5919 - Don't use substitution references like $(VAR:MOD) when
5920 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
5921 '$(:x)' to 'x' rather than the empty string. This bites us in
5922 doc/ when configured with --disable-asciidoc. Bugfix on
5923 0.2.2.9-alpha; fixes bug 1773.
5924 - Remove a spurious hidden service server-side log notice about
5925 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
5927 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
5929 - Correctly report written bytes on linked connections. Found while
5930 implementing 1790. Bugfix on 0.2.2.4-alpha.
5931 - Fix three memory leaks: one in circuit_build_times_parse_state(),
5932 one in dirvote_add_signatures_to_pending_consensus(), and one every
5933 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
5934 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
5936 o Code simplifications and refactoring:
5937 - Take a first step towards making or.h smaller by splitting out
5938 function definitions for all source files in src/or/. Leave
5939 structures and defines in or.h for now.
5940 - Remove a bunch of unused function declarations as well as a block of
5941 #if 0'd code from the unit tests. Closes bug 1824.
5942 - New unit tests for exit-port history statistics; refactored exit
5943 statistics code to be more easily tested.
5944 - Remove the old debian/ directory from the main Tor distribution.
5945 The official Tor-for-debian git repository lives at the URL
5946 https://git.torproject.org/debian/tor.git
5949 Changes in version 0.2.2.14-alpha - 2010-07-12
5950 Tor 0.2.2.14-alpha greatly improves client-side handling of
5951 circuit build timeouts, which are used to estimate speed and improve
5952 performance. We also move to a much better GeoIP database, port Tor to
5953 Windows CE, introduce new compile flags that improve code security,
5954 add an eighth v3 directory authority, and address a lot of more
5958 - Tor directory authorities no longer crash when started with a
5959 cached-microdesc-consensus file in their data directory. Bugfix
5960 on 0.2.2.6-alpha; fixes bug 1532.
5961 - Treat an unset $HOME like an empty $HOME rather than triggering an
5962 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
5963 - Ignore negative and large circuit build timeout values that can
5964 happen during a suspend or hibernate. These values caused various
5965 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
5966 - Alter calculation of Pareto distribution parameter 'Xm' for
5967 Circuit Build Timeout learning to use the weighted average of the
5968 top N=3 modes (because we have three entry guards). Considering
5969 multiple modes should improve the timeout calculation in some cases,
5970 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
5972 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
5973 right censored distribution model. This approach improves over the
5974 synthetic timeout generation approach that was producing insanely
5975 high timeout values. Now we calculate build timeouts using truncated
5976 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
5977 - Do not close circuits that are under construction when they reach
5978 the circuit build timeout. Instead, leave them building (but do not
5979 use them) for up until the time corresponding to the 95th percentile
5980 on the Pareto CDF or 60 seconds, whichever is greater. This is done
5981 to provide better data for the new Pareto model. This percentile
5982 can be controlled by the consensus.
5985 - Move to the June 2010 Maxmind GeoLite country db (rather than the
5986 June 2009 ip-to-country GeoIP db) for our statistics that count
5987 how many users relays are seeing from each country. Now we have
5988 more accurate data for many African countries.
5989 - Port Tor to build and run correctly on Windows CE systems, using
5990 the wcecompat library. Contributed by Valerio Lupi.
5991 - New "--enable-gcc-hardening" ./configure flag (off by default)
5992 to turn on gcc compile time hardening options. It ensures
5993 that signed ints have defined behavior (-fwrapv), enables
5994 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
5995 with canaries (-fstack-protector-all), turns on ASLR protection if
5996 supported by the kernel (-fPIE, -pie), and adds additional security
5997 related warnings. Verified to work on Mac OS X and Debian Lenny.
5998 - New "--enable-linker-hardening" ./configure flag (off by default)
5999 to turn on ELF specific hardening features (relro, now). This does
6000 not work with Mac OS X or any other non-ELF binary format.
6002 o New directory authorities:
6003 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6007 - New config option "WarnUnsafeSocks 0" disables the warning that
6008 occurs whenever Tor receives a socks handshake using a version of
6009 the socks protocol that can only provide an IP address (rather
6010 than a hostname). Setups that do DNS locally over Tor are fine,
6011 and we shouldn't spam the logs in that case.
6012 - Convert the HACKING file to asciidoc, and add a few new sections
6013 to it, explaining how we use Git, how we make changelogs, and
6014 what should go in a patch.
6015 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6016 event, to give information on the current rate of circuit timeouts
6017 over our stored history.
6018 - Add ability to disable circuit build time learning via consensus
6019 parameter and via a LearnCircuitBuildTimeout config option. Also
6020 automatically disable circuit build time calculation if we are
6021 either a AuthoritativeDirectory, or if we fail to write our state
6022 file. Fixes bug 1296.
6023 - More gracefully handle corrupt state files, removing asserts
6024 in favor of saving a backup and resetting state.
6025 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6029 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6031 - When a2x fails, mention that the user could disable manpages instead
6032 of trying to fix their asciidoc installation.
6033 - Where available, use Libevent 2.0's periodic timers so that our
6034 once-per-second cleanup code gets called even more closely to
6035 once per second than it would otherwise. Fixes bug 943.
6036 - If you run a bridge that listens on multiple IP addresses, and
6037 some user configures a bridge address that uses a different IP
6038 address than your bridge writes in its router descriptor, and the
6039 user doesn't specify an identity key, their Tor would discard the
6040 descriptor because "it isn't one of our configured bridges", and
6041 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6042 Bugfix on 0.2.0.3-alpha.
6043 - If OpenSSL fails to make a duplicate of a private or public key, log
6044 an error message and try to exit cleanly. May help with debugging
6045 if bug 1209 ever remanifests.
6046 - Save a couple bytes in memory allocation every time we escape
6047 certain characters in a string. Patch from Florian Zumbiehl.
6048 - Make it explicit that we don't cannibalize one-hop circuits. This
6049 happens in the wild, but doesn't turn out to be a problem because
6050 we fortunately don't use those circuits. Many thanks to outofwords
6051 for the initial analysis and to swissknife who confirmed that
6052 two-hop circuits are actually created.
6053 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6054 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6055 - Eliminate a case where a circuit build time warning was displayed
6056 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6059 Changes in version 0.2.1.26 - 2010-05-02
6060 Tor 0.2.1.26 addresses the recent connection and memory overload
6061 problems we've been seeing on relays, especially relays with their
6062 DirPort open. If your relay has been crashing, or you turned it off
6063 because it used too many resources, give this release a try.
6065 This release also fixes yet another instance of broken OpenSSL libraries
6066 that was causing some relays to drop out of the consensus.
6069 - Teach relays to defend themselves from connection overload. Relays
6070 now close idle circuits early if it looks like they were intended
6071 for directory fetches. Relays are also more aggressive about closing
6072 TLS connections that have no circuits on them. Such circuits are
6073 unlikely to be re-used, and tens of thousands of them were piling
6074 up at the fast relays, causing the relays to run out of sockets
6075 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6076 their directory fetches over TLS).
6077 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6078 that claim to be earlier than 0.9.8m, but which have in reality
6079 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6080 behavior. Possible fix for some cases of bug 1346.
6081 - Directory mirrors were fetching relay descriptors only from v2
6082 directory authorities, rather than v3 authorities like they should.
6083 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6084 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6087 - Finally get rid of the deprecated and now harmful notion of "clique
6088 mode", where directory authorities maintain TLS connections to
6092 - In the util/threads test, no longer free the test_mutex before all
6093 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6094 - The master thread could starve the worker threads quite badly on
6095 certain systems, causing them to run only partially in the allowed
6096 window. This resulted in test failures. Now the master thread sleeps
6097 occasionally for a few microseconds while the two worker-threads
6098 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6101 Changes in version 0.2.2.13-alpha - 2010-04-24
6102 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6103 problems we've been seeing on relays, especially relays with their
6104 DirPort open. If your relay has been crashing, or you turned it off
6105 because it used too many resources, give this release a try.
6108 - Teach relays to defend themselves from connection overload. Relays
6109 now close idle circuits early if it looks like they were intended
6110 for directory fetches. Relays are also more aggressive about closing
6111 TLS connections that have no circuits on them. Such circuits are
6112 unlikely to be re-used, and tens of thousands of them were piling
6113 up at the fast relays, causing the relays to run out of sockets
6114 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6115 their directory fetches over TLS).
6118 - Finally get rid of the deprecated and now harmful notion of "clique
6119 mode", where directory authorities maintain TLS connections to
6121 - Directory authorities now do an immediate reachability check as soon
6122 as they hear about a new relay. This change should slightly reduce
6123 the time between setting up a relay and getting listed as running
6124 in the consensus. It should also improve the time between setting
6125 up a bridge and seeing use by bridge users.
6126 - Directory authorities no longer launch a TLS connection to every
6127 relay as they startup. Now that we have 2k+ descriptors cached,
6128 the resulting network hiccup is becoming a burden. Besides,
6129 authorities already avoid voting about Running for the first half
6130 hour of their uptime.
6133 Changes in version 0.2.2.12-alpha - 2010-04-20
6134 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6135 handle and vote on descriptors. It was causing relays to drop out of
6139 - Many relays have been falling out of the consensus lately because
6140 not enough authorities know about their descriptor for them to get
6141 a majority of votes. When we deprecated the v2 directory protocol,
6142 we got rid of the only way that v3 authorities can hear from each
6143 other about other descriptors. Now authorities examine every v3
6144 vote for new descriptors, and fetch them from that authority. Bugfix
6146 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6147 and a warning in or.h related to bandwidth_weight_rule_t that
6148 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6150 - Fix a segfault on relays when DirReqStatistics is enabled
6151 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6155 - Demote a confusing TLS warning that relay operators might get when
6156 someone tries to talk to their OrPort. It is neither the operator's
6157 fault nor can they do anything about it. Fixes bug 1364; bugfix
6161 Changes in version 0.2.2.11-alpha - 2010-04-15
6162 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6163 libraries that was causing some relays to drop out of the consensus.
6166 - Directory mirrors were fetching relay descriptors only from v2
6167 directory authorities, rather than v3 authorities like they should.
6168 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6169 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6170 - Fix a parsing error that made every possible value of
6171 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6172 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6173 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6174 about the option without breaking older ones.
6175 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6176 that claim to be earlier than 0.9.8m, but which have in reality
6177 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6178 behavior. Possible fix for some cases of bug 1346.
6181 - Experiment with a more aggressive approach to preventing clients
6182 from making one-hop exit streams. Exit relays who want to try it
6183 out can set "RefuseUnknownExits 1" in their torrc, and then look
6184 for "Attempt by %s to open a stream" log messages. Let us know
6186 - Add support for statically linking zlib by specifying
6187 --enable-static-zlib, to go with our support for statically linking
6188 openssl and libevent. Resolves bug 1358.
6191 - Fix a segfault that happens whenever a Tor client that is using
6192 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6194 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6195 out the first line. Fixes bug 1295.
6196 - When building the manpage from a tarball, we required asciidoc, but
6197 the asciidoc -> roff/html conversion was already done for the
6198 tarball. Make 'make' complain only when we need asciidoc (either
6199 because we're compiling directly from git, or because we altered
6200 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6201 - When none of the directory authorities vote on any params, Tor
6202 segfaulted when trying to make the consensus from the votes. We
6203 didn't trigger the bug in practice, because authorities do include
6204 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6207 - In the util/threads test, no longer free the test_mutex before all
6208 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6209 - The master thread could starve the worker threads quite badly on
6210 certain systems, causing them to run only partially in the allowed
6211 window. This resulted in test failures. Now the master thread sleeps
6212 occasionally for a few microseconds while the two worker-threads
6213 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6216 Changes in version 0.2.2.10-alpha - 2010-03-07
6217 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6218 could prevent relays from guessing their IP address correctly. It also
6219 starts the groundwork for another client-side performance boost, since
6220 currently we're not making efficient use of relays that have both the
6221 Guard flag and the Exit flag.
6224 - Fix a regression from our patch for bug 1244 that caused relays
6225 to guess their IP address incorrectly if they didn't set Address
6226 in their torrc and/or their address fails to resolve. Bugfix on
6227 0.2.2.9-alpha; fixes bug 1269.
6229 o Major features (performance):
6230 - Directory authorities now compute consensus weightings that instruct
6231 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6232 and no flag. Clients that use these weightings will distribute
6233 network load more evenly across these different relay types. The
6234 weightings are in the consensus so we can change them globally in
6235 the future. Extra thanks to "outofwords" for finding some nasty
6236 security bugs in the first implementation of this feature.
6238 o Minor features (performance):
6239 - Always perform router selections using weighted relay bandwidth,
6240 even if we don't need a high capacity circuit at the time. Non-fast
6241 circuits now only differ from fast ones in that they can use relays
6242 not marked with the Fast flag. This "feature" could turn out to
6243 be a horrible bug; we should investigate more before it goes into
6247 - Allow disabling building of the manpages. Skipping the manpage
6248 speeds up the build considerably.
6250 o Minor bugfixes (on 0.2.2.x):
6251 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6252 Bugfix on 0.2.2.9-alpha.
6253 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6254 config option. Bugfix on 0.2.2.7-alpha.
6255 - Ship the asciidoc-helper file in the tarball, so that people can
6256 build from source if they want to, and touching the .1.txt files
6257 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6259 o Minor bugfixes (on 0.2.1.x or earlier):
6260 - Fix a dereference-then-NULL-check sequence when publishing
6261 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6263 - Fix another dereference-then-NULL-check sequence. Bugfix on
6264 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6265 - Make sure we treat potentially not NUL-terminated strings correctly.
6266 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6268 o Code simplifications and refactoring:
6269 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6270 compliant. Based on a patch from Christian Kujau.
6271 - Don't use sed in asciidoc-helper anymore.
6272 - Make the build process fail if asciidoc cannot be found and
6273 building with asciidoc isn't disabled.
6276 Changes in version 0.2.2.9-alpha - 2010-02-22
6277 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6278 location of a directory authority, and cleans up a bunch of small bugs.
6280 o Directory authority changes:
6281 - Change IP address for dannenberg (v3 directory authority), and
6282 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6283 service directory authority) from the list.
6286 - Make Tor work again on the latest OS X: when deciding whether to
6287 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6288 version at run-time, not compile time. We need to do this because
6289 Apple doesn't update its dev-tools headers when it updates its
6290 libraries in a security patch.
6291 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6292 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6293 a memory leak when requesting a hidden service descriptor we've
6294 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6296 - Authorities could be tricked into giving out the Exit flag to relays
6297 that didn't allow exiting to any ports. This bug could screw
6298 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6299 1238. Bug discovered by Martin Kowalczyk.
6300 - When freeing a session key, zero it out completely. We only zeroed
6301 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6302 patched by ekir. Fixes bug 1254.
6305 - Fix static compilation by listing the openssl libraries in the right
6306 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6307 - Resume handling .exit hostnames in a special way: originally we
6308 stripped the .exit part and used the requested exit relay. In
6309 0.2.2.1-alpha we stopped treating them in any special way, meaning
6310 if you use a .exit address then Tor will pass it on to the exit
6311 relay. Now we reject the .exit stream outright, since that behavior
6312 might be more expected by the user. Found and diagnosed by Scott
6313 Bennett and Downie on or-talk.
6314 - Don't spam the controller with events when we have no file
6315 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6316 for log messages was already solved from bug 748.)
6317 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6319 - Make the DNSPort option work with libevent 2.x. Don't alter the
6320 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6321 - Emit a GUARD DROPPED controller event for a case we missed.
6322 - Make more fields in the controller protocol case-insensitive, since
6323 control-spec.txt said they were.
6324 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6325 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6326 - Fix a spec conformance issue: the network-status-version token
6327 must be the first token in a v3 consensus or vote. Discovered by
6328 parakeep. Bugfix on 0.2.0.3-alpha.
6330 o Code simplifications and refactoring:
6331 - Generate our manpage and HTML documentation using Asciidoc. This
6332 change should make it easier to maintain the documentation, and
6334 - Remove the --enable-iphone option. According to reports from Marco
6335 Bonetti, Tor builds fine without any special tweaking on recent
6336 iPhone SDK versions.
6337 - Removed some unnecessary files from the source distribution. The
6338 AUTHORS file has now been merged into the people page on the
6339 website. The roadmaps and design doc can now be found in the
6340 projects directory in svn.
6341 - Enabled various circuit build timeout constants to be controlled
6342 by consensus parameters. Also set better defaults for these
6343 parameters based on experimentation on broadband and simulated
6347 - The 'EXTENDCIRCUIT' control port command can now be used with
6348 a circ id of 0 and no path. This feature will cause Tor to build
6349 a new 'fast' general purpose circuit using its own path selection
6351 - Added a BUILDTIMEOUT_SET controller event to describe changes
6352 to the circuit build timeout.
6353 - Future-proof the controller protocol a bit by ignoring keyword
6354 arguments we do not recognize.
6355 - Expand homedirs passed to tor-checkkey. This should silence a
6356 coverity complaint about passing a user-supplied string into
6357 open() without checking it.
6360 Changes in version 0.2.1.25 - 2010-03-16
6361 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6362 prevent relays from guessing their IP address correctly. It also fixes
6363 several minor potential security bugs.
6366 - Fix a regression from our patch for bug 1244 that caused relays
6367 to guess their IP address incorrectly if they didn't set Address
6368 in their torrc and/or their address fails to resolve. Bugfix on
6369 0.2.1.23; fixes bug 1269.
6370 - When freeing a session key, zero it out completely. We only zeroed
6371 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6372 patched by ekir. Fixes bug 1254.
6375 - Fix a dereference-then-NULL-check sequence when publishing
6376 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6378 - Fix another dereference-then-NULL-check sequence. Bugfix on
6379 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6380 - Make sure we treat potentially not NUL-terminated strings correctly.
6381 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6385 Changes in version 0.2.1.24 - 2010-02-21
6386 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6390 - Work correctly out-of-the-box with even more vendor-patched versions
6391 of OpenSSL. In particular, make it so Debian and OS X don't need
6392 customized patches to run/build.
6395 Changes in version 0.2.1.23 - 2010-02-13
6396 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6397 again on the latest OS X, and updates the location of a directory
6400 o Major bugfixes (performance):
6401 - We were selecting our guards uniformly at random, and then weighting
6402 which of our guards we'd use uniformly at random. This imbalance
6403 meant that Tor clients were severely limited on throughput (and
6404 probably latency too) by the first hop in their circuit. Now we
6405 select guards weighted by currently advertised bandwidth. We also
6406 automatically discard guards picked using the old algorithm. Fixes
6407 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6410 - Make Tor work again on the latest OS X: when deciding whether to
6411 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6412 version at run-time, not compile time. We need to do this because
6413 Apple doesn't update its dev-tools headers when it updates its
6414 libraries in a security patch.
6415 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6416 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6417 a memory leak when requesting a hidden service descriptor we've
6418 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6421 o Directory authority changes:
6422 - Change IP address for dannenberg (v3 directory authority), and
6423 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6424 service directory authority) from the list.
6427 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6428 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6431 - Avoid a mad rush at the beginning of each month when each client
6432 rotates half of its guards. Instead we spread the rotation out
6433 throughout the month, but we still avoid leaving a precise timestamp
6434 in the state file about when we first picked the guard. Improves
6435 over the behavior introduced in 0.1.2.17.
6438 Changes in version 0.2.2.8-alpha - 2010-01-26
6439 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6440 causing bridge relays to disappear. If you're running a bridge,
6444 - Fix a memory corruption bug on bridges that occured during the
6445 inclusion of stats data in extra-info descriptors. Also fix the
6446 interface for geoip_get_bridge_stats* to prevent similar bugs in
6447 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6448 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6451 - Ignore OutboundBindAddress when connecting to localhost.
6452 Connections to localhost need to come _from_ localhost, or else
6453 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6457 Changes in version 0.2.2.7-alpha - 2010-01-19
6458 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6459 as laying the groundwork for further relay-side performance fixes. It
6460 also starts cleaning up client behavior with respect to the EntryNodes,
6461 ExitNodes, and StrictNodes config options.
6463 This release also rotates two directory authority keys, due to a
6464 security breach of some of the Torproject servers.
6466 o Directory authority changes:
6467 - Rotate keys (both v3 identity and relay identity) for moria1
6470 o Major features (performance):
6471 - We were selecting our guards uniformly at random, and then weighting
6472 which of our guards we'd use uniformly at random. This imbalance
6473 meant that Tor clients were severely limited on throughput (and
6474 probably latency too) by the first hop in their circuit. Now we
6475 select guards weighted by currently advertised bandwidth. We also
6476 automatically discard guards picked using the old algorithm. Fixes
6477 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6478 - When choosing which cells to relay first, relays can now favor
6479 circuits that have been quiet recently, to provide lower latency
6480 for low-volume circuits. By default, relays enable or disable this
6481 feature based on a setting in the consensus. You can override
6482 this default by using the new "CircuitPriorityHalflife" config
6483 option. Design and code by Ian Goldberg, Can Tang, and Chris
6485 - Add separate per-conn write limiting to go with the per-conn read
6486 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6487 but never per-conn write limits.
6488 - New consensus params "bwconnrate" and "bwconnburst" to let us
6489 rate-limit client connections as they enter the network. It's
6490 controlled in the consensus so we can turn it on and off for
6491 experiments. It's starting out off. Based on proposal 163.
6493 o Major features (relay selection options):
6494 - Switch to a StrictNodes config option, rather than the previous
6495 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6496 "StrictExcludeNodes" option.
6497 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6498 change during a config reload, mark and discard all our origin
6499 circuits. This fix should address edge cases where we change the
6500 config options and but then choose a circuit that we created before
6502 - If EntryNodes or ExitNodes are set, be more willing to use an
6503 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6505 - Make EntryNodes config option much more aggressive even when
6506 StrictNodes is not set. Before it would prepend your requested
6507 entrynodes to your list of guard nodes, but feel free to use others
6508 after that. Now it chooses only from your EntryNodes if any of
6509 those are available, and only falls back to others if a) they're
6510 all down and b) StrictNodes is not set.
6511 - Now we refresh your entry guards from EntryNodes at each consensus
6512 fetch -- rather than just at startup and then they slowly rot as
6513 the network changes.
6516 - Stop bridge directory authorities from answering dbg-stability.txt
6517 directory queries, which would let people fetch a list of all
6518 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6521 - Log a notice when we get a new control connection. Now it's easier
6522 for security-conscious users to recognize when a local application
6523 is knocking on their controller door. Suggested by bug 1196.
6524 - New config option "CircuitStreamTimeout" to override our internal
6525 timeout schedule for how many seconds until we detach a stream from
6526 a circuit and try a new circuit. If your network is particularly
6527 slow, you might want to set this to a number like 60.
6528 - New controller command "getinfo config-text". It returns the
6529 contents that Tor would write if you send it a SAVECONF command,
6530 so the controller can write the file to disk itself.
6531 - New options for SafeLogging to allow scrubbing only log messages
6532 generated while acting as a relay.
6533 - Ship the bridges spec file in the tarball too.
6534 - Avoid a mad rush at the beginning of each month when each client
6535 rotates half of its guards. Instead we spread the rotation out
6536 throughout the month, but we still avoid leaving a precise timestamp
6537 in the state file about when we first picked the guard. Improves
6538 over the behavior introduced in 0.1.2.17.
6540 o Minor bugfixes (compiling):
6541 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6542 hides it. Bugfix on 0.2.2.6-alpha.
6543 - Fix compilation on Solaris by removing support for the
6544 DisableAllSwap config option. Solaris doesn't have an rlimit for
6545 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6548 o Minor bugfixes (crashes):
6549 - Do not segfault when writing buffer stats when we haven't observed
6550 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6552 - If we're in the pathological case where there's no exit bandwidth
6553 but there is non-exit bandwidth, or no guard bandwidth but there
6554 is non-guard bandwidth, don't crash during path selection. Bugfix
6556 - Fix an impossible-to-actually-trigger buffer overflow in relay
6557 descriptor generation. Bugfix on 0.1.0.15.
6559 o Minor bugfixes (privacy):
6560 - Fix an instance where a Tor directory mirror might accidentally
6561 log the IP address of a misbehaving Tor client. Bugfix on
6563 - Don't list Windows capabilities in relay descriptors. We never made
6564 use of them, and maybe it's a bad idea to publish them. Bugfix
6567 o Minor bugfixes (other):
6568 - Resolve an edge case in path weighting that could make us misweight
6569 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6570 - Fix statistics on client numbers by country as seen by bridges that
6571 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6572 intervals instead of variable 12-to-48-hour intervals.
6573 - After we free an internal connection structure, overwrite it
6574 with a different memory value than we use for overwriting a freed
6575 internal circuit structure. Should help with debugging. Suggested
6577 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6581 - Remove the HSAuthorityRecordStats option that version 0 hidden
6582 service authorities could have used to track statistics of overall
6583 hidden service usage.
6586 Changes in version 0.2.1.22 - 2010-01-19
6587 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6588 authorities -- it would tell you its whole history of bridge descriptors
6589 if you make the right directory request. This stable update also
6590 rotates two of the seven v3 directory authority keys and locations.
6592 o Directory authority changes:
6593 - Rotate keys (both v3 identity and relay identity) for moria1
6597 - Stop bridge directory authorities from answering dbg-stability.txt
6598 directory queries, which would let people fetch a list of all
6599 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6602 Changes in version 0.2.1.21 - 2009-12-21
6603 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6604 library. If you use Tor on Linux / Unix and you're getting SSL
6605 renegotiation errors, upgrading should help. We also recommend an
6606 upgrade if you're an exit relay.
6609 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6610 handshake from working unless we explicitly tell OpenSSL that we
6611 are using SSL renegotiation safely. We are, of course, but OpenSSL
6612 0.9.8l won't work unless we say we are.
6613 - Avoid crashing if the client is trying to upload many bytes and the
6614 circuit gets torn down at the same time, or if the flip side
6615 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6618 - Do not refuse to learn about authority certs and v2 networkstatus
6619 documents that are older than the latest consensus. This bug might
6620 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6621 Spotted and fixed by xmux.
6622 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6623 trigger platform-specific option misparsing case found by Coverity
6625 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6626 trigger assert. Fixes bug 1173.
6629 Changes in version 0.2.2.6-alpha - 2009-11-19
6630 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6631 support for the new lower-footprint "microdescriptor" directory design,
6632 future-proofing our consensus format against new hash functions or
6633 other changes, and an Android port. It also makes Tor compatible with
6634 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6637 - Directory authorities can now create, vote on, and serve multiple
6638 parallel formats of directory data as part of their voting process.
6639 Partially implements Proposal 162: "Publish the consensus in
6641 - Directory authorities can now agree on and publish small summaries
6642 of router information that clients can use in place of regular
6643 server descriptors. This transition will eventually allow clients
6644 to use far less bandwidth for downloading information about the
6645 network. Begins the implementation of Proposal 158: "Clients
6646 download consensus + microdescriptors".
6647 - The directory voting system is now extensible to use multiple hash
6648 algorithms for signatures and resource selection. Newer formats
6649 are signed with SHA256, with a possibility for moving to a better
6650 hash algorithm in the future.
6651 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6652 current and future memory pages via mlockall(). On supported
6653 platforms (modern Linux and probably BSD but not Windows or OS X),
6654 this should effectively disable any and all attempts to page out
6655 memory. This option requires that you start your Tor as root --
6656 if you use DisableAllSwap, please consider using the User option
6657 to properly reduce the privileges of your Tor.
6658 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6659 to help Tor build correctly for Android phones.
6662 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6663 handshake from working unless we explicitly tell OpenSSL that we
6664 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6665 won't work unless we say we are.
6668 - Fix a crash bug when trying to initialize the evdns module in
6669 Libevent 2. Bugfix on 0.2.1.16-rc.
6670 - Stop logging at severity 'warn' when some other Tor client tries
6671 to establish a circuit with us using weak DH keys. It's a protocol
6672 violation, but that doesn't mean ordinary users need to hear about
6673 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6674 - Do not refuse to learn about authority certs and v2 networkstatus
6675 documents that are older than the latest consensus. This bug might
6676 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6677 Spotted and fixed by xmux.
6678 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6679 - If all authorities restart at once right before a consensus vote,
6680 nobody will vote about "Running", and clients will get a consensus
6681 with no usable relays. Instead, authorities refuse to build a
6682 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6683 - If your relay can't keep up with the number of incoming create
6684 cells, it would log one warning per failure into your logs. Limit
6685 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6686 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6687 on 0.2.0.3-alpha; fixes bug 1113.
6688 - Fix a memory leak on directory authorities during voting that was
6689 introduced in 0.2.2.1-alpha. Found via valgrind.
6692 Changes in version 0.2.1.20 - 2009-10-15
6693 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6694 services at once, prepares for more performance improvements, and
6695 fixes a bunch of smaller bugs.
6697 The Windows and OS X bundles also include a more recent Vidalia,
6698 and switch from Privoxy to Polipo.
6700 The OS X installers are now drag and drop. It's best to un-install
6701 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6702 you want to upgrade, you'll need to update the paths for Tor and Polipo
6703 in the Vidalia Settings window.
6706 - Send circuit or stream sendme cells when our window has decreased
6707 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6708 by Karsten when testing the "reduce circuit window" performance
6709 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6710 before the release of Tor 0.0.0. This is the new winner of the
6712 - Fix a remotely triggerable memory leak when a consensus document
6713 contains more than one signature from the same voter. Bugfix on
6715 - Avoid segfault in rare cases when finishing an introduction circuit
6716 as a client and finding out that we don't have an introduction key
6717 for it. Fixes bug 1073. Reported by Aaron Swartz.
6720 - Tor now reads the "circwindow" parameter out of the consensus,
6721 and uses that value for its circuit package window rather than the
6722 default of 1000 cells. Begins the implementation of proposal 168.
6724 o New directory authorities:
6725 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6727 - Move moria1 and tonga to alternate IP addresses.
6730 - Fix a signed/unsigned compile warning in 0.2.1.19.
6731 - Fix possible segmentation fault on directory authorities. Bugfix on
6733 - Fix an extremely rare infinite recursion bug that could occur if
6734 we tried to log a message after shutting down the log subsystem.
6735 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6736 - Fix an obscure bug where hidden services on 64-bit big-endian
6737 systems might mis-read the timestamp in v3 introduce cells, and
6738 refuse to connect back to the client. Discovered by "rotor".
6739 Bugfix on 0.2.1.6-alpha.
6740 - We were triggering a CLOCK_SKEW controller status event whenever
6741 we connect via the v2 connection protocol to any relay that has
6742 a wrong clock. Instead, we should only inform the controller when
6743 it's a trusted authority that claims our clock is wrong. Bugfix
6744 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6745 - We were telling the controller about CHECKING_REACHABILITY and
6746 REACHABILITY_FAILED status events whenever we launch a testing
6747 circuit or notice that one has failed. Instead, only tell the
6748 controller when we want to inform the user of overall success or
6749 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6751 - Don't warn when we're using a circuit that ends with a node
6752 excluded in ExcludeExitNodes, but the circuit is not used to access
6753 the outside world. This should help fix bug 1090. Bugfix on
6755 - Work around a small memory leak in some versions of OpenSSL that
6756 stopped the memory used by the hostname TLS extension from being
6760 - Add a "getinfo status/accepted-server-descriptor" controller
6761 command, which is the recommended way for controllers to learn
6762 whether our server descriptor has been successfully received by at
6763 least on directory authority. Un-recommend good-server-descriptor
6764 getinfo and status events until we have a better design for them.
6767 Changes in version 0.2.2.5-alpha - 2009-10-11
6768 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
6771 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
6773 o Directory authorities:
6774 - Temporarily (just for this release) move dizum to an alternate
6778 Changes in version 0.2.2.4-alpha - 2009-10-10
6779 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
6780 introduces a new unit test framework, shifts directry authority
6781 addresses around to reduce the impact from recent blocking events,
6782 and fixes a few smaller bugs.
6785 - Fix several more asserts in the circuit_build_times code, for
6786 example one that causes Tor to fail to start once we have
6787 accumulated 5000 build times in the state file. Bugfixes on
6788 0.2.2.2-alpha; fixes bug 1108.
6790 o New directory authorities:
6791 - Move moria1 and Tonga to alternate IP addresses.
6794 - Log SSL state transitions at debug level during handshake, and
6795 include SSL states in error messages. This may help debug future
6796 SSL handshake issues.
6797 - Add a new "Handshake" log domain for activities that happen
6798 during the TLS handshake.
6799 - Revert to the "June 3 2009" ip-to-country file. The September one
6800 seems to have removed most US IP addresses.
6801 - Directory authorities now reject Tor relays with versions less than
6802 0.1.2.14. This step cuts out four relays from the current network,
6803 none of which are very big.
6806 - Fix a couple of smaller issues with gathering statistics. Bugfixes
6808 - Fix two memory leaks in the error case of
6809 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
6810 - Don't count one-hop circuits when we're estimating how long it
6811 takes circuits to build on average. Otherwise we'll set our circuit
6812 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
6813 - Directory authorities no longer change their opinion of, or vote on,
6814 whether a router is Running, unless they have themselves been
6815 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
6818 o Code simplifications and refactoring:
6819 - Revise our unit tests to use the "tinytest" framework, so we
6820 can run tests in their own processes, have smarter setup/teardown
6821 code, and so on. The unit test code has moved to its own
6822 subdirectory, and has been split into multiple modules.
6825 Changes in version 0.2.2.3-alpha - 2009-09-23
6826 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
6829 - Fix an overzealous assert in our new circuit build timeout code.
6830 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
6833 - If the networkstatus consensus tells us that we should use a
6834 negative circuit package window, ignore it. Otherwise we'll
6835 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
6838 Changes in version 0.2.2.2-alpha - 2009-09-21
6839 Tor 0.2.2.2-alpha introduces our latest performance improvement for
6840 clients: Tor tracks the average time it takes to build a circuit, and
6841 avoids using circuits that take too long to build. For fast connections,
6842 this feature can cut your expected latency in half. For slow or flaky
6843 connections, it could ruin your Tor experience. Let us know if it does!
6846 - Tor now tracks how long it takes to build client-side circuits
6847 over time, and adapts its timeout to local network performance.
6848 Since a circuit that takes a long time to build will also provide
6849 bad performance, we get significant latency improvements by
6850 discarding the slowest 20% of circuits. Specifically, Tor creates
6851 circuits more aggressively than usual until it has enough data
6852 points for a good timeout estimate. Implements proposal 151.
6853 We are especially looking for reports (good and bad) from users with
6854 both EDGE and broadband connections that can move from broadband
6855 to EDGE and find out if the build-time data in the .tor/state gets
6856 reset without loss of Tor usability. You should also see a notice
6857 log message telling you that Tor has reset its timeout.
6858 - Directory authorities can now vote on arbitary integer values as
6859 part of the consensus process. This is designed to help set
6860 network-wide parameters. Implements proposal 167.
6861 - Tor now reads the "circwindow" parameter out of the consensus,
6862 and uses that value for its circuit package window rather than the
6863 default of 1000 cells. Begins the implementation of proposal 168.
6866 - Fix a remotely triggerable memory leak when a consensus document
6867 contains more than one signature from the same voter. Bugfix on
6871 - Fix an extremely rare infinite recursion bug that could occur if
6872 we tried to log a message after shutting down the log subsystem.
6873 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6874 - Fix parsing for memory or time units given without a space between
6875 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
6876 - A networkstatus vote must contain exactly one signature. Spec
6877 conformance issue. Bugfix on 0.2.0.3-alpha.
6878 - Fix an obscure bug where hidden services on 64-bit big-endian
6879 systems might mis-read the timestamp in v3 introduce cells, and
6880 refuse to connect back to the client. Discovered by "rotor".
6881 Bugfix on 0.2.1.6-alpha.
6882 - We were triggering a CLOCK_SKEW controller status event whenever
6883 we connect via the v2 connection protocol to any relay that has
6884 a wrong clock. Instead, we should only inform the controller when
6885 it's a trusted authority that claims our clock is wrong. Bugfix
6886 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6887 - We were telling the controller about CHECKING_REACHABILITY and
6888 REACHABILITY_FAILED status events whenever we launch a testing
6889 circuit or notice that one has failed. Instead, only tell the
6890 controller when we want to inform the user of overall success or
6891 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6893 - Don't warn when we're using a circuit that ends with a node
6894 excluded in ExcludeExitNodes, but the circuit is not used to access
6895 the outside world. This should help fix bug 1090, but more problems
6896 remain. Bugfix on 0.2.1.6-alpha.
6897 - Work around a small memory leak in some versions of OpenSSL that
6898 stopped the memory used by the hostname TLS extension from being
6900 - Make our 'torify' script more portable; if we have only one of
6901 'torsocks' or 'tsocks' installed, don't complain to the user;
6902 and explain our warning about tsocks better.
6905 - Add a "getinfo status/accepted-server-descriptor" controller
6906 command, which is the recommended way for controllers to learn
6907 whether our server descriptor has been successfully received by at
6908 least on directory authority. Un-recommend good-server-descriptor
6909 getinfo and status events until we have a better design for them.
6910 - Update to the "September 4 2009" ip-to-country file.
6913 Changes in version 0.2.2.1-alpha - 2009-08-26
6914 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
6915 Tor clients to bootstrap on networks where only port 80 is reachable,
6916 makes it more straightforward to support hardware crypto accelerators,
6917 and starts the groundwork for gathering stats safely at relays.
6920 - Start the process of disabling ".exit" address notation, since it
6921 can be used for a variety of esoteric application-level attacks
6922 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
6925 o New directory authorities:
6926 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6930 - New AccelName and AccelDir options add support for dynamic OpenSSL
6931 hardware crypto acceleration engines.
6932 - Tor now supports tunneling all of its outgoing connections over
6933 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
6934 configuration options. Code by Christopher Davis.
6937 - Send circuit or stream sendme cells when our window has decreased
6938 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6939 by Karsten when testing the "reduce circuit window" performance
6940 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6941 before the release of Tor 0.0.0. This is the new winner of the
6944 o New options for gathering stats safely:
6945 - Directory mirrors that set "DirReqStatistics 1" write statistics
6946 about directory requests to disk every 24 hours. As compared to the
6947 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
6948 1) stats are written to disk exactly every 24 hours; 2) estimated
6949 shares of v2 and v3 requests are determined as mean values, not at
6950 the end of a measurement period; 3) unresolved requests are listed
6951 with country code '??'; 4) directories also measure download times.
6952 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
6953 number of exit streams and transferred bytes per port to disk every
6955 - Relays that set "CellStatistics 1" write statistics on how long
6956 cells spend in their circuit queues to disk every 24 hours.
6957 - Entry nodes that set "EntryStatistics 1" write statistics on the
6958 rough number and origins of connecting clients to disk every 24
6960 - Relays that write any of the above statistics to disk and set
6961 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
6962 their extra-info documents.
6965 - New --digests command-line switch to output the digests of the
6966 source files Tor was built with.
6967 - The "torify" script now uses torsocks where available.
6968 - The memarea code now uses a sentinel value at the end of each area
6969 to make sure nothing writes beyond the end of an area. This might
6970 help debug some conceivable causes of bug 930.
6971 - Time and memory units in the configuration file can now be set to
6972 fractional units. For example, "2.5 GB" is now a valid value for
6974 - Certain Tor clients (such as those behind check.torproject.org) may
6975 want to fetch the consensus in an extra early manner. To enable this
6976 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
6977 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
6978 as only certain clients who must have this information sooner should
6980 - Instead of adding the svn revision to the Tor version string, report
6981 the git commit (when we're building from a git checkout).
6984 - If any of the v3 certs we download are unparseable, we should
6985 actually notice the failure so we don't retry indefinitely. Bugfix
6986 on 0.2.0.x; reported by "rotator".
6987 - If the cached cert file is unparseable, warn but don't exit.
6988 - Fix possible segmentation fault on directory authorities. Bugfix on
6990 - When Tor fails to parse a descriptor of any kind, dump it to disk.
6991 Might help diagnosing bug 1051.
6993 o Deprecated and removed features:
6994 - The controller no longer accepts the old obsolete "addr-mappings/"
6995 or "unregistered-servers-" GETINFO values.
6996 - Hidden services no longer publish version 0 descriptors, and clients
6997 do not request or use version 0 descriptors. However, the old hidden
6998 service authorities still accept and serve version 0 descriptors
6999 when contacted by older hidden services/clients.
7000 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7001 always on; using them is necessary for correct forward-compatible
7003 - Remove support for .noconnect style addresses. Nobody was using
7004 them, and they provided another avenue for detecting Tor users
7005 via application-level web tricks.
7007 o Packaging changes:
7008 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7009 installer bundles. See
7010 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7011 for details of what's new in Vidalia 0.2.3.
7012 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7013 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7014 configuration file, rather than the old Privoxy.
7015 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7016 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7017 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7018 better compatibility with OS X 10.6, aka Snow Leopard.
7019 - OS X Vidalia Bundle: The multi-package installer is now replaced
7020 by a simple drag and drop to the /Applications folder. This change
7021 occurred with the upgrade to Vidalia 0.2.3.
7024 Changes in version 0.2.1.19 - 2009-07-28
7025 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7026 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7029 - Make accessing hidden services on 0.2.1.x work right again.
7030 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7031 part of patch provided by "optimist".
7034 - When a relay/bridge is writing out its identity key fingerprint to
7035 the "fingerprint" file and to its logs, write it without spaces. Now
7036 it will look like the fingerprints in our bridges documentation,
7037 and confuse fewer users.
7040 - Relays no longer publish a new server descriptor if they change
7041 their MaxAdvertisedBandwidth config option but it doesn't end up
7042 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7043 fixes bug 1026. Patch from Sebastian.
7044 - Avoid leaking memory every time we get a create cell but we have
7045 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7046 fixes bug 1034. Reported by BarkerJr.
7049 Changes in version 0.2.1.18 - 2009-07-24
7050 Tor 0.2.1.18 lays the foundations for performance improvements,
7051 adds status events to help users diagnose bootstrap problems, adds
7052 optional authentication/authorization for hidden services, fixes a
7053 variety of potential anonymity problems, and includes a huge pile of
7054 other features and bug fixes.
7057 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7060 Changes in version 0.2.1.17-rc - 2009-07-07
7061 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7062 candidate for the 0.2.1.x series. It lays the groundwork for further
7063 client performance improvements, and also fixes a big bug with directory
7064 authorities that were causing them to assign Guard and Stable flags
7067 The Windows bundles also finally include the geoip database that we
7068 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7069 should actually install Torbutton rather than giving you a cryptic
7070 failure message (oops).
7073 - Clients now use the bandwidth values in the consensus, rather than
7074 the bandwidth values in each relay descriptor. This approach opens
7075 the door to more accurate bandwidth estimates once the directory
7076 authorities start doing active measurements. Implements more of
7080 - When Tor clients restart after 1-5 days, they discard all their
7081 cached descriptors as too old, but they still use the cached
7082 consensus document. This approach is good for robustness, but
7083 bad for performance: since they don't know any bandwidths, they
7084 end up choosing at random rather than weighting their choice by
7085 speed. Fixed by the above feature of putting bandwidths in the
7086 consensus. Bugfix on 0.2.0.x.
7087 - Directory authorities were neglecting to mark relays down in their
7088 internal histories if the relays fall off the routerlist without
7089 ever being found unreachable. So there were relays in the histories
7090 that haven't been seen for eight months, and are listed as being
7091 up for eight months. This wreaked havoc on the "median wfu"
7092 and "median mtbf" calculations, in turn making Guard and Stable
7093 flags very wrong, hurting network performance. Fixes bugs 696 and
7094 969. Bugfix on 0.2.0.6-alpha.
7097 - Serve the DirPortFrontPage page even when we have been approaching
7098 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7099 - The control port would close the connection before flushing long
7100 replies, such as the network consensus, if a QUIT command was issued
7101 before the reply had completed. Now, the control port flushes all
7102 pending replies before closing the connection. Also fixed a spurious
7103 warning when a QUIT command is issued after a malformed or rejected
7104 AUTHENTICATE command, but before the connection was closed. Patch
7105 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7106 - When we can't find an intro key for a v2 hidden service descriptor,
7107 fall back to the v0 hidden service descriptor and log a bug message.
7108 Workaround for bug 1024.
7109 - Fix a log message that did not respect the SafeLogging option.
7113 - If we're a relay and we change our IP address, be more verbose
7114 about the reason that made us change. Should help track down
7115 further bugs for relays on dynamic IP addresses.
7118 Changes in version 0.2.0.35 - 2009-06-24
7120 - Avoid crashing in the presence of certain malformed descriptors.
7121 Found by lark, and by automated fuzzing.
7122 - Fix an edge case where a malicious exit relay could convince a
7123 controller that the client's DNS question resolves to an internal IP
7124 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7127 - Finally fix the bug where dynamic-IP relays disappear when their
7128 IP address changes: directory mirrors were mistakenly telling
7129 them their old address if they asked via begin_dir, so they
7130 never got an accurate answer about their new address, so they
7131 just vanished after a day. For belt-and-suspenders, relays that
7132 don't set Address in their config now avoid using begin_dir for
7133 all direct connections. Should fix bugs 827, 883, and 900.
7134 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7135 that would occur on some exit nodes when DNS failures and timeouts
7136 occurred in certain patterns. Fix for bug 957.
7139 - When starting with a cache over a few days old, do not leak
7140 memory for the obsolete router descriptors in it. Bugfix on
7141 0.2.0.33; fixes bug 672.
7142 - Hidden service clients didn't use a cached service descriptor that
7143 was older than 15 minutes, but wouldn't fetch a new one either,
7144 because there was already one in the cache. Now, fetch a v2
7145 descriptor unless the same descriptor was added to the cache within
7146 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7149 Changes in version 0.2.1.16-rc - 2009-06-20
7150 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7151 a bunch of minor bugs.
7154 - Fix an edge case where a malicious exit relay could convince a
7155 controller that the client's DNS question resolves to an internal IP
7156 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7158 o Major performance improvements (on 0.2.0.x):
7159 - Disable and refactor some debugging checks that forced a linear scan
7160 over the whole server-side DNS cache. These accounted for over 50%
7161 of CPU time on a relatively busy exit node's gprof profile. Found
7163 - Disable some debugging checks that appeared in exit node profile
7167 - Update to the "June 3 2009" ip-to-country file.
7168 - Do not have tor-resolve automatically refuse all .onion addresses;
7169 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7171 o Minor bugfixes (on 0.2.0.x):
7172 - Log correct error messages for DNS-related network errors on
7174 - Fix a race condition that could cause crashes or memory corruption
7175 when running as a server with a controller listening for log
7177 - Avoid crashing when we have a policy specified in a DirPolicy or
7178 SocksPolicy or ReachableAddresses option with ports set on it,
7179 and we re-load the policy. May fix bug 996.
7180 - Hidden service clients didn't use a cached service descriptor that
7181 was older than 15 minutes, but wouldn't fetch a new one either,
7182 because there was already one in the cache. Now, fetch a v2
7183 descriptor unless the same descriptor was added to the cache within
7184 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7186 o Minor bugfixes (on 0.2.1.x):
7187 - Don't warn users about low port and hibernation mix when they
7188 provide a *ListenAddress directive to fix that. Bugfix on
7190 - When switching back and forth between bridge mode, do not start
7191 gathering GeoIP data until two hours have passed.
7192 - Do not complain that the user has requested an excluded node as
7193 an exit when the node is not really an exit. This could happen
7194 because the circuit was for testing, or an introduction point.
7198 Changes in version 0.2.1.15-rc - 2009-05-25
7199 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7200 series. It fixes a major bug on fast exit relays, as well as a variety
7203 o Major bugfixes (on 0.2.0.x):
7204 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7205 that would occur on some exit nodes when DNS failures and timeouts
7206 occurred in certain patterns. Fix for bug 957.
7208 o Minor bugfixes (on 0.2.0.x):
7209 - Actually return -1 in the error case for read_bandwidth_usage().
7210 Harmless bug, since we currently don't care about the return value
7211 anywhere. Bugfix on 0.2.0.9-alpha.
7212 - Provide a more useful log message if bug 977 (related to buffer
7213 freelists) ever reappears, and do not crash right away.
7214 - Fix an assertion failure on 64-bit platforms when we allocated
7215 memory right up to the end of a memarea, then realigned the memory
7216 one step beyond the end. Fixes a possible cause of bug 930.
7217 - Protect the count of open sockets with a mutex, so we can't
7218 corrupt it when two threads are closing or opening sockets at once.
7219 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7220 - Don't allow a bridge to publish its router descriptor to a
7221 non-bridge directory authority. Fixes part of bug 932.
7222 - When we change to or from being a bridge, reset our counts of
7223 client usage by country. Fixes bug 932.
7224 - Fix a bug that made stream bandwidth get misreported to the
7226 - Stop using malloc_usable_size() to use more area than we had
7227 actually allocated: it was safe, but made valgrind really unhappy.
7228 - Fix a memory leak when v3 directory authorities load their keys
7229 and cert from disk. Bugfix on 0.2.0.1-alpha.
7231 o Minor bugfixes (on 0.2.1.x):
7232 - Fix use of freed memory when deciding to mark a non-addable
7233 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7236 Changes in version 0.2.1.14-rc - 2009-04-12
7237 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7238 series. It begins fixing some major performance problems, and also
7239 finally addresses the bug that was causing relays on dynamic IP
7240 addresses to fall out of the directory.
7243 - Clients replace entry guards that were chosen more than a few months
7244 ago. This change should significantly improve client performance,
7245 especially once more people upgrade, since relays that have been
7246 a guard for a long time are currently overloaded.
7248 o Major bugfixes (on 0.2.0):
7249 - Finally fix the bug where dynamic-IP relays disappear when their
7250 IP address changes: directory mirrors were mistakenly telling
7251 them their old address if they asked via begin_dir, so they
7252 never got an accurate answer about their new address, so they
7253 just vanished after a day. For belt-and-suspenders, relays that
7254 don't set Address in their config now avoid using begin_dir for
7255 all direct connections. Should fix bugs 827, 883, and 900.
7256 - Relays were falling out of the networkstatus consensus for
7257 part of a day if they changed their local config but the
7258 authorities discarded their new descriptor as "not sufficiently
7259 different". Now directory authorities accept a descriptor as changed
7260 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7262 - Avoid crashing in the presence of certain malformed descriptors.
7263 Found by lark, and by automated fuzzing.
7266 - When generating circuit events with verbose nicknames for
7267 controllers, try harder to look up nicknames for routers on a
7268 circuit. (Previously, we would look in the router descriptors we had
7269 for nicknames, but not in the consensus.) Partial fix for bug 941.
7270 - If the bridge config line doesn't specify a port, assume 443.
7271 This makes bridge lines a bit smaller and easier for users to
7273 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7274 bytes (aka 20KB/s), to match our documentation. Also update
7275 directory authorities so they always assign the Fast flag to relays
7276 with 20KB/s of capacity. Now people running relays won't suddenly
7277 find themselves not seeing any use, if the network gets faster
7279 - Update to the "April 3 2009" ip-to-country file.
7282 - Avoid trying to print raw memory to the logs when we decide to
7283 give up on downloading a given relay descriptor. Bugfix on
7285 - In tor-resolve, when the Tor client to use is specified by
7286 <hostname>:<port>, actually use the specified port rather than
7287 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7288 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7289 - When starting with a cache over a few days old, do not leak
7290 memory for the obsolete router descriptors in it. Bugfix on
7292 - Avoid double-free on list of successfully uploaded hidden
7293 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7294 - Change memarea_strndup() implementation to work even when
7295 duplicating a string at the end of a page. This bug was
7296 harmless for now, but could have meant crashes later. Fix by
7297 lark. Bugfix on 0.2.1.1-alpha.
7298 - Limit uploaded directory documents to be 16M rather than 500K.
7299 The directory authorities were refusing v3 consensus votes from
7300 other authorities, since the votes are now 504K. Fixes bug 959;
7301 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7302 - Directory authorities should never send a 503 "busy" response to
7303 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7307 Changes in version 0.2.1.13-alpha - 2009-03-09
7308 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7309 cleanups. We're finally getting close to a release candidate.
7312 - Correctly update the list of which countries we exclude as
7313 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7314 lark. Bugfix on 0.2.1.6-alpha.
7316 o Minor bugfixes (on 0.2.0.x and earlier):
7317 - Automatically detect MacOSX versions earlier than 10.4.0, and
7318 disable kqueue from inside Tor when running with these versions.
7319 We previously did this from the startup script, but that was no
7320 help to people who didn't use the startup script. Resolves bug 863.
7321 - When we had picked an exit node for a connection, but marked it as
7322 "optional", and it turned out we had no onion key for the exit,
7323 stop wanting that exit and try again. This situation may not
7324 be possible now, but will probably become feasible with proposal
7325 158. Spotted by rovv. Fixes another case of bug 752.
7326 - Clients no longer cache certificates for authorities they do not
7327 recognize. Bugfix on 0.2.0.9-alpha.
7328 - When we can't transmit a DNS request due to a network error, retry
7329 it after a while, and eventually transmit a failing response to
7330 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7331 - If the controller claimed responsibility for a stream, but that
7332 stream never finished making its connection, it would live
7333 forever in circuit_wait state. Now we close it after SocksTimeout
7334 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7335 - Drop begin cells to a hidden service if they come from the middle
7336 of a circuit. Patch from lark.
7337 - When we erroneously receive two EXTEND cells for the same circuit
7338 ID on the same connection, drop the second. Patch from lark.
7339 - Fix a crash that occurs on exit nodes when a nameserver request
7340 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7341 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7343 - Do not assume that a stack-allocated character array will be
7344 64-bit aligned on platforms that demand that uint64_t access is
7345 aligned. Possible fix for bug 604.
7346 - Parse dates and IPv4 addresses in a locale- and libc-independent
7347 manner, to avoid platform-dependent behavior on malformed input.
7348 - Build correctly when configured to build outside the main source
7349 path. Patch from Michael Gold.
7350 - We were already rejecting relay begin cells with destination port
7351 of 0. Now also reject extend cells with destination port or address
7352 of 0. Suggested by lark.
7354 o Minor bugfixes (on 0.2.1.x):
7355 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7356 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7357 - If we're an exit node, scrub the IP address to which we are exiting
7358 in the logs. Bugfix on 0.2.1.8-alpha.
7361 - On Linux, use the prctl call to re-enable core dumps when the user
7363 - New controller event NEWCONSENSUS that lists the networkstatus
7364 lines for every recommended relay. Now controllers like Torflow
7365 can keep up-to-date on which relays they should be using.
7366 - Update to the "February 26 2009" ip-to-country file.
7369 Changes in version 0.2.0.34 - 2009-02-08
7370 Tor 0.2.0.34 features several more security-related fixes. You should
7371 upgrade, especially if you run an exit relay (remote crash) or a
7372 directory authority (remote infinite loop), or you're on an older
7373 (pre-XP) or not-recently-patched Windows (remote exploit).
7375 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7376 have many known flaws, and nobody should be using them. You should
7377 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7378 stop using those packages and upgrade anyway.
7381 - Fix an infinite-loop bug on handling corrupt votes under certain
7382 circumstances. Bugfix on 0.2.0.8-alpha.
7383 - Fix a temporary DoS vulnerability that could be performed by
7384 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7385 - Avoid a potential crash on exit nodes when processing malformed
7386 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7387 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7388 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7391 - Fix compilation on systems where time_t is a 64-bit integer.
7392 Patch from Matthias Drochner.
7393 - Don't consider expiring already-closed client connections. Fixes
7394 bug 893. Bugfix on 0.0.2pre20.
7397 Changes in version 0.2.1.12-alpha - 2009-02-08
7398 Tor 0.2.1.12-alpha features several more security-related fixes. You
7399 should upgrade, especially if you run an exit relay (remote crash) or
7400 a directory authority (remote infinite loop), or you're on an older
7401 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7402 includes a big pile of minor bugfixes and cleanups.
7405 - Fix an infinite-loop bug on handling corrupt votes under certain
7406 circumstances. Bugfix on 0.2.0.8-alpha.
7407 - Fix a temporary DoS vulnerability that could be performed by
7408 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7409 - Avoid a potential crash on exit nodes when processing malformed
7410 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7413 - Let controllers actually ask for the "clients_seen" event for
7414 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7415 reported by Matt Edman.
7416 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7418 - Fix a bug in address parsing that was preventing bridges or hidden
7419 service targets from being at IPv6 addresses.
7420 - Solve a bug that kept hardware crypto acceleration from getting
7421 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7423 - Remove a bash-ism from configure.in to build properly on non-Linux
7424 platforms. Bugfix on 0.2.1.1-alpha.
7425 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7426 headers. Bugfix on 0.2.0.10-alpha.
7427 - Don't consider expiring already-closed client connections. Fixes
7428 bug 893. Bugfix on 0.0.2pre20.
7429 - Fix another interesting corner-case of bug 891 spotted by rovv:
7430 Previously, if two hosts had different amounts of clock drift, and
7431 one of them created a new connection with just the wrong timing,
7432 the other might decide to deprecate the new connection erroneously.
7433 Bugfix on 0.1.1.13-alpha.
7434 - Resolve a very rare crash bug that could occur when the user forced
7435 a nameserver reconfiguration during the middle of a nameserver
7436 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7437 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7438 Bugfix on 0.2.1.7-alpha.
7439 - If we're using bridges and our network goes away, be more willing
7440 to forgive our bridges and try again when we get an application
7441 request. Bugfix on 0.2.0.x.
7444 - Support platforms where time_t is 64 bits long. (Congratulations,
7445 NetBSD!) Patch from Matthias Drochner.
7446 - Add a 'getinfo status/clients-seen' controller command, in case
7447 controllers want to hear clients_seen events but connect late.
7450 - Disable GCC's strict alias optimization by default, to avoid the
7451 likelihood of its introducing subtle bugs whenever our code violates
7452 the letter of C99's alias rules.
7455 Changes in version 0.2.0.33 - 2009-01-21
7456 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7457 useful to users. It also finally fixes a bug where a relay or client
7458 that's been off for many days would take a long time to bootstrap.
7460 This update also fixes an important security-related bug reported by
7461 Ilja van Sprundel. You should upgrade. (We'll send out more details
7462 about the bug once people have had some time to upgrade.)
7465 - Fix a heap-corruption bug that may be remotely triggerable on
7466 some platforms. Reported by Ilja van Sprundel.
7469 - When a stream at an exit relay is in state "resolving" or
7470 "connecting" and it receives an "end" relay cell, the exit relay
7471 would silently ignore the end cell and not close the stream. If
7472 the client never closes the circuit, then the exit relay never
7473 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7475 - When sending CREATED cells back for a given circuit, use a 64-bit
7476 connection ID to find the right connection, rather than an addr:port
7477 combination. Now that we can have multiple OR connections between
7478 the same ORs, it is no longer possible to use addr:port to uniquely
7479 identify a connection.
7480 - Bridge relays that had DirPort set to 0 would stop fetching
7481 descriptors shortly after startup, and then briefly resume
7482 after a new bandwidth test and/or after publishing a new bridge
7483 descriptor. Bridge users that try to bootstrap from them would
7484 get a recent networkstatus but would get descriptors from up to
7485 18 hours earlier, meaning most of the descriptors were obsolete
7486 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7487 - Prevent bridge relays from serving their 'extrainfo' document
7488 to anybody who asks, now that extrainfo docs include potentially
7489 sensitive aggregated client geoip summaries. Bugfix on
7491 - If the cached networkstatus consensus is more than five days old,
7492 discard it rather than trying to use it. In theory it could be
7493 useful because it lists alternate directory mirrors, but in practice
7494 it just means we spend many minutes trying directory mirrors that
7495 are long gone from the network. Also discard router descriptors as
7496 we load them if they are more than five days old, since the onion
7497 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7500 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7501 could make gcc generate non-functional binary search code. Bugfix
7503 - Build correctly on platforms without socklen_t.
7504 - Compile without warnings on solaris.
7505 - Avoid potential crash on internal error during signature collection.
7506 Fixes bug 864. Patch from rovv.
7507 - Correct handling of possible malformed authority signing key
7508 certificates with internal signature types. Fixes bug 880.
7509 Bugfix on 0.2.0.3-alpha.
7510 - Fix a hard-to-trigger resource leak when logging credential status.
7512 - When we can't initialize DNS because the network is down, do not
7513 automatically stop Tor from starting. Instead, we retry failed
7514 dns_init() every 10 minutes, and change the exit policy to reject
7515 *:* until one succeeds. Fixes bug 691.
7516 - Use 64 bits instead of 32 bits for connection identifiers used with
7517 the controller protocol, to greatly reduce risk of identifier reuse.
7518 - When we're choosing an exit node for a circuit, and we have
7519 no pending streams, choose a good general exit rather than one that
7520 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7521 - Fix another case of assuming, when a specific exit is requested,
7522 that we know more than the user about what hosts it allows.
7523 Fixes one case of bug 752. Patch from rovv.
7524 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7525 seconds. Warn the user if lower values are given in the
7526 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7527 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7528 user if lower values are given in the configuration. Bugfix on
7529 0.1.1.17-rc. Patch by Sebastian.
7530 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7531 the cache because we already had a v0 descriptor with the same ID.
7532 Bugfix on 0.2.0.18-alpha.
7533 - Fix a race condition when freeing keys shared between main thread
7534 and CPU workers that could result in a memory leak. Bugfix on
7535 0.1.0.1-rc. Fixes bug 889.
7536 - Send a valid END cell back when a client tries to connect to a
7537 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7538 840. Patch from rovv.
7539 - Check which hops rendezvous stream cells are associated with to
7540 prevent possible guess-the-streamid injection attacks from
7541 intermediate hops. Fixes another case of bug 446. Based on patch
7543 - If a broken client asks a non-exit router to connect somewhere,
7544 do not even do the DNS lookup before rejecting the connection.
7545 Fixes another case of bug 619. Patch from rovv.
7546 - When a relay gets a create cell it can't decrypt (e.g. because it's
7547 using the wrong onion key), we were dropping it and letting the
7548 client time out. Now actually answer with a destroy cell. Fixes
7549 bug 904. Bugfix on 0.0.2pre8.
7551 o Minor bugfixes (hidden services):
7552 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7553 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7556 - Report the case where all signatures in a detached set are rejected
7557 differently than the case where there is an error handling the
7559 - When we realize that another process has modified our cached
7560 descriptors, print out a more useful error message rather than
7561 triggering an assertion. Fixes bug 885. Patch from Karsten.
7562 - Implement the 0x20 hack to better resist DNS poisoning: set the
7563 case on outgoing DNS requests randomly, and reject responses that do
7564 not match the case correctly. This logic can be disabled with the
7565 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7566 of servers that do not reliably preserve case in replies. See
7567 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7569 - Check DNS replies for more matching fields to better resist DNS
7571 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7572 compress cells, which are basically all encrypted, compressed, or
7576 Changes in version 0.2.1.11-alpha - 2009-01-20
7577 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7578 week it will take a long time to bootstrap again" bug. It also fixes
7579 an important security-related bug reported by Ilja van Sprundel. You
7580 should upgrade. (We'll send out more details about the bug once people
7581 have had some time to upgrade.)
7584 - Fix a heap-corruption bug that may be remotely triggerable on
7585 some platforms. Reported by Ilja van Sprundel.
7588 - Discard router descriptors as we load them if they are more than
7589 five days old. Otherwise if Tor is off for a long time and then
7590 starts with cached descriptors, it will try to use the onion
7591 keys in those obsolete descriptors when building circuits. Bugfix
7592 on 0.2.0.x. Fixes bug 887.
7595 - Try to make sure that the version of Libevent we're running with
7596 is binary-compatible with the one we built with. May address bug
7598 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7599 for bug 905. Bugfix on 0.2.1.7-alpha.
7600 - Add a new --enable-local-appdata configuration switch to change
7601 the default location of the datadir on win32 from APPDATA to
7602 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7603 entirely. Patch from coderman.
7606 - Make outbound DNS packets respect the OutboundBindAddress setting.
7607 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7608 - When our circuit fails at the first hop (e.g. we get a destroy
7609 cell back), avoid using that OR connection anymore, and also
7610 tell all the one-hop directory requests waiting for it that they
7611 should fail. Bugfix on 0.2.1.3-alpha.
7612 - In the torify(1) manpage, mention that tsocks will leak your
7616 Changes in version 0.2.1.10-alpha - 2009-01-06
7617 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7618 would make the bridge relay not so useful if it had DirPort set to 0,
7619 and one that could let an attacker learn a little bit of information
7620 about the bridge's users), and a bug that would cause your Tor relay
7621 to ignore a circuit create request it can't decrypt (rather than reply
7622 with an error). It also fixes a wide variety of other bugs.
7625 - If the cached networkstatus consensus is more than five days old,
7626 discard it rather than trying to use it. In theory it could
7627 be useful because it lists alternate directory mirrors, but in
7628 practice it just means we spend many minutes trying directory
7629 mirrors that are long gone from the network. Helps bug 887 a bit;
7631 - Bridge relays that had DirPort set to 0 would stop fetching
7632 descriptors shortly after startup, and then briefly resume
7633 after a new bandwidth test and/or after publishing a new bridge
7634 descriptor. Bridge users that try to bootstrap from them would
7635 get a recent networkstatus but would get descriptors from up to
7636 18 hours earlier, meaning most of the descriptors were obsolete
7637 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7638 - Prevent bridge relays from serving their 'extrainfo' document
7639 to anybody who asks, now that extrainfo docs include potentially
7640 sensitive aggregated client geoip summaries. Bugfix on
7644 - New controller event "clients_seen" to report a geoip-based summary
7645 of which countries we've seen clients from recently. Now controllers
7646 like Vidalia can show bridge operators that they're actually making
7648 - Build correctly against versions of OpenSSL 0.9.8 or later built
7649 without support for deprecated functions.
7650 - Update to the "December 19 2008" ip-to-country file.
7652 o Minor bugfixes (on 0.2.0.x):
7653 - Authorities now vote for the Stable flag for any router whose
7654 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7655 - Do not remove routers as too old if we do not have any consensus
7656 document. Bugfix on 0.2.0.7-alpha.
7657 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7658 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7659 - When an exit relay resolves a stream address to a local IP address,
7660 do not just keep retrying that same exit relay over and
7661 over. Instead, just close the stream. Addresses bug 872. Bugfix
7662 on 0.2.0.32. Patch from rovv.
7663 - If a hidden service sends us an END cell, do not consider
7664 retrying the connection; just close it. Patch from rovv.
7665 - When we made bridge authorities stop serving bridge descriptors over
7666 unencrypted links, we also broke DirPort reachability testing for
7667 bridges. So bridges with a non-zero DirPort were printing spurious
7668 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7669 - When a relay gets a create cell it can't decrypt (e.g. because it's
7670 using the wrong onion key), we were dropping it and letting the
7671 client time out. Now actually answer with a destroy cell. Fixes
7672 bug 904. Bugfix on 0.0.2pre8.
7673 - Squeeze 2-5% out of client performance (according to oprofile) by
7674 improving the implementation of some policy-manipulation functions.
7676 o Minor bugfixes (on 0.2.1.x):
7677 - Make get_interface_address() function work properly again; stop
7678 guessing the wrong parts of our address as our address.
7679 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7680 send on that circuit. Otherwise we might violate the proposal-110
7681 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7683 - When we're sending non-EXTEND cells to the first hop in a circuit,
7684 for example to use an encrypted directory connection, we don't need
7685 to use RELAY_EARLY cells: the first hop knows what kind of cell
7686 it is, and nobody else can even see the cell type. Conserving
7687 RELAY_EARLY cells makes it easier to cannibalize circuits like
7689 - Stop logging nameserver addresses in reverse order.
7690 - If we are retrying a directory download slowly over and over, do
7691 not automatically give up after the 254th failure. Bugfix on
7693 - Resume reporting accurate "stream end" reasons to the local control
7694 port. They were lost in the changes for Proposal 148. Bugfix on
7697 o Deprecated and removed features:
7698 - The old "tor --version --version" command, which would print out
7699 the subversion "Id" of most of the source files, is now removed. It
7700 turned out to be less useful than we'd expected, and harder to
7703 o Code simplifications and refactoring:
7704 - Change our header file guard macros to be less likely to conflict
7705 with system headers. Adam Langley noticed that we were conflicting
7706 with log.h on Android.
7707 - Tool-assisted documentation cleanup. Nearly every function or
7708 static variable in Tor should have its own documentation now.
7711 Changes in version 0.2.1.9-alpha - 2008-12-25
7712 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7714 o New directory authorities:
7715 - gabelmoo (the authority run by Karsten Loesing) now has a new
7719 - Never use a connection with a mismatched address to extend a
7720 circuit, unless that connection is canonical. A canonical
7721 connection is one whose address is authenticated by the router's
7722 identity key, either in a NETINFO cell or in a router descriptor.
7723 - Avoid a possible memory corruption bug when receiving hidden service
7724 descriptors. Bugfix on 0.2.1.6-alpha.
7727 - Fix a logic error that would automatically reject all but the first
7728 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7729 part of bug 813/868. Bug spotted by coderman.
7730 - When a stream at an exit relay is in state "resolving" or
7731 "connecting" and it receives an "end" relay cell, the exit relay
7732 would silently ignore the end cell and not close the stream. If
7733 the client never closes the circuit, then the exit relay never
7734 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7736 - When we can't initialize DNS because the network is down, do not
7737 automatically stop Tor from starting. Instead, retry failed
7738 dns_init() every 10 minutes, and change the exit policy to reject
7739 *:* until one succeeds. Fixes bug 691.
7742 - Give a better error message when an overzealous init script says
7743 "sudo -u username tor --user username". Makes Bug 882 easier for
7745 - When a directory authority gives us a new guess for our IP address,
7746 log which authority we used. Hopefully this will help us debug
7747 the recent complaints about bad IP address guesses.
7748 - Detect svn revision properly when we're using git-svn.
7749 - Try not to open more than one descriptor-downloading connection
7750 to an authority at once. This should reduce load on directory
7751 authorities. Fixes bug 366.
7752 - Add cross-certification to newly generated certificates, so that
7753 a signing key is enough information to look up a certificate.
7754 Partial implementation of proposal 157.
7755 - Start serving certificates by <identity digest, signing key digest>
7756 pairs. Partial implementation of proposal 157.
7757 - Clients now never report any stream end reason except 'MISC'.
7758 Implements proposal 148.
7759 - On platforms with a maximum syslog string length, truncate syslog
7760 messages to that length ourselves, rather than relying on the
7761 system to do it for us.
7762 - Optimize out calls to time(NULL) that occur for every IO operation,
7763 or for every cell. On systems where time() is a slow syscall,
7764 this fix will be slightly helpful.
7765 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7766 - When we download a descriptor that we then immediately (as
7767 a directory authority) reject, do not retry downloading it right
7768 away. Should save some bandwidth on authorities. Fix for bug
7769 888. Patch by Sebastian Hahn.
7770 - When a download gets us zero good descriptors, do not notify
7771 Tor that new directory information has arrived.
7772 - Avoid some nasty corner cases in the logic for marking connections
7773 as too old or obsolete or noncanonical for circuits. Partial
7776 o Minor features (controller):
7777 - New CONSENSUS_ARRIVED event to note when a new consensus has
7778 been fetched and validated.
7779 - When we realize that another process has modified our cached
7780 descriptors file, print out a more useful error message rather
7781 than triggering an assertion. Fixes bug 885. Patch from Karsten.
7782 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
7783 controllers to prevent SIGHUP from reloading the
7784 configuration. Fixes bug 856.
7787 - Resume using the correct "REASON=" stream when telling the
7788 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
7789 - When a canonical connection appears later in our internal list
7790 than a noncanonical one for a given OR ID, always use the
7791 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
7793 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7794 seconds. Warn the user if lower values are given in the
7795 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7796 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7797 user if lower values are given in the configuration. Bugfix on
7798 0.1.1.17-rc. Patch by Sebastian.
7799 - Fix a race condition when freeing keys shared between main thread
7800 and CPU workers that could result in a memory leak. Bugfix on
7801 0.1.0.1-rc. Fixes bug 889.
7803 o Minor bugfixes (hidden services):
7804 - Do not throw away existing introduction points on SIGHUP (bugfix on
7805 0.0.6pre1); also, do not stall hidden services because we're
7806 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
7807 by John Brooks. Patch by Karsten. Fixes bug 874.
7808 - Fix a memory leak when we decline to add a v2 rendezvous
7809 descriptor to the cache because we already had a v0 descriptor
7810 with the same ID. Bugfix on 0.2.0.18-alpha.
7812 o Deprecated and removed features:
7813 - RedirectExits has been removed. It was deprecated since
7815 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
7816 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
7817 - Cell pools are now always enabled; --disable-cell-pools is ignored.
7819 o Code simplifications and refactoring:
7820 - Rename the confusing or_is_obsolete field to the more appropriate
7821 is_bad_for_new_circs, and move it to or_connection_t where it
7823 - Move edge-only flags from connection_t to edge_connection_t: not
7824 only is this better coding, but on machines of plausible alignment,
7825 it should save 4-8 bytes per connection_t. "Every little bit helps."
7826 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
7827 for consistency; keep old option working for backward compatibility.
7828 - Simplify the code for finding connections to use for a circuit.
7831 Changes in version 0.2.1.8-alpha - 2008-12-08
7832 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
7833 builds better on unusual platforms like Solaris and old OS X, and
7834 fixes a variety of other issues.
7837 - New DirPortFrontPage option that takes an html file and publishes
7838 it as "/" on the DirPort. Now relay operators can provide a
7839 disclaimer without needing to set up a separate webserver. There's
7840 a sample disclaimer in contrib/tor-exit-notice.html.
7843 - When the client is choosing entry guards, now it selects at most
7844 one guard from a given relay family. Otherwise we could end up with
7845 all of our entry points into the network run by the same operator.
7846 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
7849 - Fix a DOS opportunity during the voting signature collection process
7850 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7851 - Fix a possible segfault when establishing an exit connection. Bugfix
7855 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
7857 - Made Tor a little less aggressive about deleting expired
7858 certificates. Partial fix for bug 854.
7859 - Stop doing unaligned memory access that generated bus errors on
7860 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
7861 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
7862 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
7863 - Make USR2 log-level switch take effect immediately. Bugfix on
7865 - If one win32 nameserver fails to get added, continue adding the
7866 rest, and don't automatically fail.
7867 - Use fcntl() for locking when flock() is not available. Should fix
7868 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
7869 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7870 could make gcc generate non-functional binary search code. Bugfix
7872 - Build correctly on platforms without socklen_t.
7873 - Avoid potential crash on internal error during signature collection.
7874 Fixes bug 864. Patch from rovv.
7875 - Do not use C's stdio library for writing to log files. This will
7876 improve logging performance by a minute amount, and will stop
7877 leaking fds when our disk is full. Fixes bug 861.
7878 - Stop erroneous use of O_APPEND in cases where we did not in fact
7879 want to re-seek to the end of a file before every last write().
7880 - Correct handling of possible malformed authority signing key
7881 certificates with internal signature types. Fixes bug 880. Bugfix
7883 - Fix a hard-to-trigger resource leak when logging credential status.
7887 - Directory mirrors no longer fetch the v1 directory or
7888 running-routers files. They are obsolete, and nobody asks for them
7889 anymore. This is the first step to making v1 authorities obsolete.
7891 o Minor features (controller):
7892 - Return circuit purposes in response to GETINFO circuit-status. Fixes
7896 Changes in version 0.2.0.32 - 2008-11-20
7897 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
7898 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7899 a smaller security flaw that might allow an attacker to access local
7900 services, further improves hidden service performance, and fixes a
7901 variety of other issues.
7904 - The "User" and "Group" config options did not clear the
7905 supplementary group entries for the Tor process. The "User" option
7906 is now more robust, and we now set the groups to the specified
7907 user's primary group. The "Group" option is now ignored. For more
7908 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7909 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7910 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
7911 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7912 consistently obeyed: if an exit relay refuses a stream because its
7913 exit policy doesn't allow it, we would remember what IP address
7914 the relay said the destination address resolves to, even if it's
7915 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7918 - Fix a DOS opportunity during the voting signature collection process
7919 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7921 o Major bugfixes (hidden services):
7922 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7923 we were failing the whole hidden service request when the v0
7924 descriptor fetch fails, even if the v2 fetch is still pending and
7925 might succeed. Similarly, if the last v2 fetch fails, we were
7926 failing the whole hidden service request even if a v0 fetch is
7927 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7928 - When extending a circuit to a hidden service directory to upload a
7929 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7930 requests failed, because the router descriptor has not been
7931 downloaded yet. In these cases, do not attempt to upload the
7932 rendezvous descriptor, but wait until the router descriptor is
7933 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
7934 descriptor from a hidden service directory for which the router
7935 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
7939 - Fix several infrequent memory leaks spotted by Coverity.
7940 - When testing for libevent functions, set the LDFLAGS variable
7941 correctly. Found by Riastradh.
7942 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7943 bootstrapping with tunneled directory connections. Bugfix on
7944 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7945 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7946 and we know that server B rejects most-but-not all connections to
7947 port 80, we would previously reject the connection. Now, we assume
7948 the user knows what they were asking for. Fixes bug 752. Bugfix
7949 on 0.0.9rc5. Diagnosed by BarkerJr.
7950 - If we overrun our per-second write limits a little, count this as
7951 having used up our write allocation for the second, and choke
7952 outgoing directory writes. Previously, we had only counted this when
7953 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
7954 Bugfix on 0.2.0.x (??).
7955 - Remove the old v2 directory authority 'lefkada' from the default
7956 list. It has been gone for many months.
7957 - Stop doing unaligned memory access that generated bus errors on
7958 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
7959 - Make USR2 log-level switch take effect immediately. Bugfix on
7962 o Minor bugfixes (controller):
7963 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
7964 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
7967 Changes in version 0.2.1.7-alpha - 2008-11-08
7968 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
7969 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7970 a smaller security flaw that might allow an attacker to access local
7971 services, adds better defense against DNS poisoning attacks on exit
7972 relays, further improves hidden service performance, and fixes a
7973 variety of other issues.
7976 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7977 consistently obeyed: if an exit relay refuses a stream because its
7978 exit policy doesn't allow it, we would remember what IP address
7979 the relay said the destination address resolves to, even if it's
7980 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7981 - The "User" and "Group" config options did not clear the
7982 supplementary group entries for the Tor process. The "User" option
7983 is now more robust, and we now set the groups to the specified
7984 user's primary group. The "Group" option is now ignored. For more
7985 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7986 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7987 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
7988 - Do not use or believe expired v3 authority certificates. Patch
7989 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
7992 - Now NodeFamily and MyFamily config options allow spaces in
7993 identity fingerprints, so it's easier to paste them in.
7994 Suggested by Lucky Green.
7995 - Implement the 0x20 hack to better resist DNS poisoning: set the
7996 case on outgoing DNS requests randomly, and reject responses that do
7997 not match the case correctly. This logic can be disabled with the
7998 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
7999 of servers that do not reliably preserve case in replies. See
8000 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8002 - Preserve case in replies to DNSPort requests in order to support
8003 the 0x20 hack for resisting DNS poisoning attacks.
8005 o Hidden service performance improvements:
8006 - When the client launches an introduction circuit, retry with a
8007 new circuit after 30 seconds rather than 60 seconds.
8008 - Launch a second client-side introduction circuit in parallel
8009 after a delay of 15 seconds (based on work by Christian Wilms).
8010 - Hidden services start out building five intro circuits rather
8011 than three, and when the first three finish they publish a service
8012 descriptor using those. Now we publish our service descriptor much
8013 faster after restart.
8016 - Minor fix in the warning messages when you're having problems
8017 bootstrapping; also, be more forgiving of bootstrap problems when
8018 we're still making incremental progress on a given bootstrap phase.
8019 - When we're choosing an exit node for a circuit, and we have
8020 no pending streams, choose a good general exit rather than one that
8021 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8022 - Send a valid END cell back when a client tries to connect to a
8023 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8024 840. Patch from rovv.
8025 - If a broken client asks a non-exit router to connect somewhere,
8026 do not even do the DNS lookup before rejecting the connection.
8027 Fixes another case of bug 619. Patch from rovv.
8028 - Fix another case of assuming, when a specific exit is requested,
8029 that we know more than the user about what hosts it allows.
8030 Fixes another case of bug 752. Patch from rovv.
8031 - Check which hops rendezvous stream cells are associated with to
8032 prevent possible guess-the-streamid injection attacks from
8033 intermediate hops. Fixes another case of bug 446. Based on patch
8035 - Avoid using a negative right-shift when comparing 32-bit
8036 addresses. Possible fix for bug 845 and bug 811.
8037 - Make the assert_circuit_ok() function work correctly on circuits that
8038 have already been marked for close.
8039 - Fix read-off-the-end-of-string error in unit tests when decoding
8040 introduction points.
8041 - Fix uninitialized size field for memory area allocation: may improve
8042 memory performance during directory parsing.
8043 - Treat duplicate certificate fetches as failures, so that we do
8044 not try to re-fetch an expired certificate over and over and over.
8045 - Do not say we're fetching a certificate when we'll in fact skip it
8046 because of a pending download.
8049 Changes in version 0.2.1.6-alpha - 2008-09-30
8050 Tor 0.2.1.6-alpha further improves performance and robustness of
8051 hidden services, starts work on supporting per-country relay selection,
8052 and fixes a variety of smaller issues.
8055 - Implement proposal 121: make it possible to build hidden services
8056 that only certain clients are allowed to connect to. This is
8057 enforced at several points, so that unauthorized clients are unable
8058 to send INTRODUCE cells to the service, or even (depending on the
8059 type of authentication) to learn introduction points. This feature
8060 raises the bar for certain kinds of active attacks against hidden
8061 services. Code by Karsten Loesing.
8062 - Relays now store and serve v2 hidden service descriptors by default,
8063 i.e., the new default value for HidServDirectoryV2 is 1. This is
8064 the last step in proposal 114, which aims to make hidden service
8065 lookups more reliable.
8066 - Start work to allow node restrictions to include country codes. The
8067 syntax to exclude nodes in a country with country code XX is
8068 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8069 refinement to decide what config options should take priority if
8070 you ask to both use a particular node and exclude it.
8071 - Allow ExitNodes list to include IP ranges and country codes, just
8072 like the Exclude*Nodes lists. Patch from Robert Hogan.
8075 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8076 Tor to fail to start if you had it configured to use a bridge
8077 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8078 - When extending a circuit to a hidden service directory to upload a
8079 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8080 requests failed, because the router descriptor had not been
8081 downloaded yet. In these cases, we now wait until the router
8082 descriptor is downloaded, and then retry. Likewise, clients
8083 now skip over a hidden service directory if they don't yet have
8084 its router descriptor, rather than futilely requesting it and
8085 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8087 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8088 we were failing the whole hidden service request when the v0
8089 descriptor fetch fails, even if the v2 fetch is still pending and
8090 might succeed. Similarly, if the last v2 fetch fails, we were
8091 failing the whole hidden service request even if a v0 fetch is
8092 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8093 - DNS replies need to have names matching their requests, but
8094 these names should be in the questions section, not necessarily
8095 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8098 - Update to the "September 1 2008" ip-to-country file.
8099 - Allow ports 465 and 587 in the default exit policy again. We had
8100 rejected them in 0.1.0.15, because back in 2005 they were commonly
8101 misconfigured and ended up as spam targets. We hear they are better
8102 locked down these days.
8103 - Use a lockfile to make sure that two Tor processes are not
8104 simultaneously running with the same datadir.
8105 - Serve the latest v3 networkstatus consensus via the control
8106 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8107 - Better logging about stability/reliability calculations on directory
8109 - Drop the requirement to have an open dir port for storing and
8110 serving v2 hidden service descriptors.
8111 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8112 help debug WFU and MTBF calculations.
8113 - Implement most of Proposal 152: allow specialized servers to permit
8114 single-hop circuits, and clients to use those servers to build
8115 single-hop circuits when using a specialized controller. Patch
8116 from Josh Albrecht. Resolves feature request 768.
8117 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8118 people find host:port too confusing.
8119 - Make TrackHostExit mappings expire a while after their last use, not
8120 after their creation. Patch from Robert Hogan.
8121 - Provide circuit purposes along with circuit events to the controller.
8124 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8126 - Fixed some memory leaks -- some quite frequent, some almost
8127 impossible to trigger -- based on results from Coverity.
8128 - When testing for libevent functions, set the LDFLAGS variable
8129 correctly. Found by Riastradh.
8130 - Fix an assertion bug in parsing policy-related options; possible fix
8132 - Catch and report a few more bootstrapping failure cases when Tor
8133 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8134 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8135 bootstrapping with tunneled directory connections. Bugfix on
8136 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8137 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8138 and we know that server B rejects most-but-not all connections to
8139 port 80, we would previously reject the connection. Now, we assume
8140 the user knows what they were asking for. Fixes bug 752. Bugfix
8141 on 0.0.9rc5. Diagnosed by BarkerJr.
8142 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8143 service directories if they have no advertised dir port. Bugfix
8145 - If we overrun our per-second write limits a little, count this as
8146 having used up our write allocation for the second, and choke
8147 outgoing directory writes. Previously, we had only counted this when
8148 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8149 Bugfix on 0.2.0.x (??).
8150 - Avoid a "0 divided by 0" calculation when calculating router uptime
8151 at directory authorities. Bugfix on 0.2.0.8-alpha.
8152 - Make DNS resolved controller events into "CLOSED", not
8153 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8155 - Fix a bug where an unreachable relay would establish enough
8156 reachability testing circuits to do a bandwidth test -- if
8157 we already have a connection to the middle hop of the testing
8158 circuit, then it could establish the last hop by using the existing
8159 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8160 circuits no longer use entry guards in 0.2.1.3-alpha.
8161 - If we have correct permissions on $datadir, we complain to stdout
8162 and fail to start. But dangerous permissions on
8163 $datadir/cached-status/ would cause us to open a log and complain
8164 there. Now complain to stdout and fail to start in both cases. Fixes
8165 bug 820, reported by seeess.
8166 - Remove the old v2 directory authority 'lefkada' from the default
8167 list. It has been gone for many months.
8169 o Code simplifications and refactoring:
8170 - Revise the connection_new functions so that a more typesafe variant
8171 exists. This will work better with Coverity, and let us find any
8172 actual mistakes we're making here.
8173 - Refactor unit testing logic so that dmalloc can be used sensibly
8174 with unit tests to check for memory leaks.
8175 - Move all hidden-service related fields from connection and circuit
8176 structure to substructures: this way they won't eat so much memory.
8179 Changes in version 0.2.0.31 - 2008-09-03
8180 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8181 a big bug we're seeing where in rare cases traffic from one Tor stream
8182 gets mixed into another stream, and fixes a variety of smaller issues.
8185 - Make sure that two circuits can never exist on the same connection
8186 with the same circuit ID, even if one is marked for close. This
8187 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8188 - Relays now reject risky extend cells: if the extend cell includes
8189 a digest of all zeroes, or asks to extend back to the relay that
8190 sent the extend cell, tear down the circuit. Ideas suggested
8192 - If not enough of our entry guards are available so we add a new
8193 one, we might use the new one even if it overlapped with the
8194 current circuit's exit relay (or its family). Anonymity bugfix
8195 pointed out by rovv.
8198 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8199 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8200 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8201 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8202 - Pick size of default geoip filename string correctly on windows.
8203 Fixes bug 806. Bugfix on 0.2.0.30.
8204 - Make the autoconf script accept the obsolete --with-ssl-dir
8205 option as an alias for the actually-working --with-openssl-dir
8206 option. Fix the help documentation to recommend --with-openssl-dir.
8207 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8208 - When using the TransPort option on OpenBSD, and using the User
8209 option to change UID and drop privileges, make sure to open
8210 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8211 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8212 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8213 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8214 on the client side when connecting to a hidden service. Bugfix
8215 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8216 - When closing an application-side connection because its circuit is
8217 getting torn down, generate the stream event correctly. Bugfix on
8218 0.1.2.x. Anonymous patch.
8221 Changes in version 0.2.1.5-alpha - 2008-08-31
8222 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8223 in a lot of the infrastructure for adding authorization to hidden
8224 services, lays the groundwork for having clients read their load
8225 balancing information out of the networkstatus consensus rather than
8226 the individual router descriptors, addresses two potential anonymity
8227 issues, and fixes a variety of smaller issues.
8230 - Convert many internal address representations to optionally hold
8232 - Generate and accept IPv6 addresses in many protocol elements.
8233 - Make resolver code handle nameservers located at ipv6 addresses.
8234 - Begin implementation of proposal 121 ("Client authorization for
8235 hidden services"): configure hidden services with client
8236 authorization, publish descriptors for them, and configure
8237 authorization data for hidden services at clients. The next
8238 step is to actually access hidden services that perform client
8240 - More progress toward proposal 141: Network status consensus
8241 documents and votes now contain bandwidth information for each
8242 router and a summary of that router's exit policy. Eventually this
8243 will be used by clients so that they do not have to download every
8244 known descriptor before building circuits.
8246 o Major bugfixes (on 0.2.0.x and before):
8247 - When sending CREATED cells back for a given circuit, use a 64-bit
8248 connection ID to find the right connection, rather than an addr:port
8249 combination. Now that we can have multiple OR connections between
8250 the same ORs, it is no longer possible to use addr:port to uniquely
8251 identify a connection.
8252 - Relays now reject risky extend cells: if the extend cell includes
8253 a digest of all zeroes, or asks to extend back to the relay that
8254 sent the extend cell, tear down the circuit. Ideas suggested
8256 - If not enough of our entry guards are available so we add a new
8257 one, we might use the new one even if it overlapped with the
8258 current circuit's exit relay (or its family). Anonymity bugfix
8259 pointed out by rovv.
8262 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8263 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8264 - When using the TransPort option on OpenBSD, and using the User
8265 option to change UID and drop privileges, make sure to open /dev/pf
8266 before dropping privileges. Fixes bug 782. Patch from Christopher
8267 Davis. Bugfix on 0.1.2.1-alpha.
8268 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8269 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8270 - Add a missing safe_str() call for a debug log message.
8271 - Use 64 bits instead of 32 bits for connection identifiers used with
8272 the controller protocol, to greatly reduce risk of identifier reuse.
8273 - Make the autoconf script accept the obsolete --with-ssl-dir
8274 option as an alias for the actually-working --with-openssl-dir
8275 option. Fix the help documentation to recommend --with-openssl-dir.
8276 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8279 - Rate-limit too-many-sockets messages: when they happen, they happen
8280 a lot. Resolves bug 748.
8281 - Resist DNS poisoning a little better by making sure that names in
8282 answer sections match.
8283 - Print the SOCKS5 error message string as well as the error code
8284 when a tor-resolve request fails. Patch from Jacob.
8287 Changes in version 0.2.1.4-alpha - 2008-08-04
8288 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8291 - The address part of exit policies was not correctly written
8292 to router descriptors. This generated router descriptors that failed
8293 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8295 - Tor triggered a false assert when extending a circuit to a relay
8296 but we already have a connection open to that relay. Noticed by
8297 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8300 - Fix a hidden service logging bug: in some edge cases, the router
8301 descriptor of a previously picked introduction point becomes
8302 obsolete and we need to give up on it rather than continually
8303 complaining that it has become obsolete. Observed by xiando. Bugfix
8307 - Take out the TestVia config option, since it was a workaround for
8308 a bug that was fixed in Tor 0.1.1.21.
8311 Changes in version 0.2.1.3-alpha - 2008-08-03
8312 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8313 infinite-length circuit attacks (see proposal 110); fixes a bug that
8314 might cause exit relays to corrupt streams they send back; allows
8315 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8316 ExcludeExitNodes config options; and fixes a big pile of bugs.
8318 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8319 - Send a bootstrap problem "warn" event on the first problem if the
8320 reason is NO_ROUTE (that is, our network is down).
8323 - Implement most of proposal 110: The first K cells to be sent
8324 along a circuit are marked as special "early" cells; only K "early"
8325 cells will be allowed. Once this code is universal, we can block
8326 certain kinds of DOS attack by requiring that EXTEND commands must
8327 be sent using an "early" cell.
8330 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8331 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8332 on the client side when connecting to a hidden service. Bugfix
8333 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8334 - Ensure that two circuits can never exist on the same connection
8335 with the same circuit ID, even if one is marked for close. This
8336 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8339 - When relays do their initial bandwidth measurement, don't limit
8340 to just our entry guards for the test circuits. Otherwise we tend
8341 to have multiple test circuits going through a single entry guard,
8342 which makes our bandwidth test less accurate. Fixes part of bug 654;
8343 patch contributed by Josh Albrecht.
8344 - Add an ExcludeExitNodes option so users can list a set of nodes
8345 that should be be excluded from the exit node position, but
8346 allowed elsewhere. Implements proposal 151.
8347 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8348 ExcludeNodes and ExcludeExitNodes lists.
8349 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8350 be more efficient. Formerly it was quadratic in the number of
8351 servers; now it should be linear. Fixes bug 509.
8352 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8353 and n_conn_id_digest fields into a separate structure that's
8354 only needed when the circuit has not yet attached to an n_conn.
8357 - Change the contrib/tor.logrotate script so it makes the new
8358 logs as "_tor:_tor" rather than the default, which is generally
8359 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8360 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8361 warnings (occasionally), but it can also cause the compiler to
8362 eliminate error-checking code. Suggested by Peter Gutmann.
8363 - When a hidden service is giving up on an introduction point candidate
8364 that was not included in the last published rendezvous descriptor,
8365 don't reschedule publication of the next descriptor. Fixes bug 763.
8367 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8368 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8369 and nobody claims to be using them. Fixes bug 754. Bugfix on
8370 0.1.0.1-rc. Patch from Christian Wilms.
8371 - Fix a small alignment and memory-wasting bug on buffer chunks.
8374 o Minor bugfixes (controller):
8375 - When closing an application-side connection because its circuit
8376 is getting torn down, generate the stream event correctly.
8377 Bugfix on 0.1.2.x. Anonymous patch.
8380 - Remove all backward-compatibility code to support relays running
8381 versions of Tor so old that they no longer work at all on the
8385 Changes in version 0.2.0.30 - 2008-07-15
8387 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8388 warnings (occasionally), but it can also cause the compiler to
8389 eliminate error-checking code. Suggested by Peter Gutmann.
8392 Changes in version 0.2.0.29-rc - 2008-07-08
8393 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8394 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8397 - If you have more than one bridge but don't know their keys,
8398 you would only launch a request for the descriptor of the first one
8399 on your list. (Tor considered launching requests for the others, but
8400 found that it already had a connection on the way for $0000...0000
8401 so it didn't open another.) Bugfix on 0.2.0.x.
8402 - If you have more than one bridge but don't know their keys, and the
8403 connection to one of the bridges failed, you would cancel all
8404 pending bridge connections. (After all, they all have the same
8405 digest.) Bugfix on 0.2.0.x.
8406 - When a hidden service was trying to establish an introduction point,
8407 and Tor had built circuits preemptively for such purposes, we
8408 were ignoring all the preemptive circuits and launching a new one
8409 instead. Bugfix on 0.2.0.14-alpha.
8410 - When a hidden service was trying to establish an introduction point,
8411 and Tor *did* manage to reuse one of the preemptively built
8412 circuits, it didn't correctly remember which one it used,
8413 so it asked for another one soon after, until there were no
8414 more preemptive circuits, at which point it launched one from
8415 scratch. Bugfix on 0.0.9.x.
8416 - Make directory servers include the X-Your-Address-Is: http header in
8417 their responses even for begin_dir conns. Now clients who only
8418 ever use begin_dir connections still have a way to learn their IP
8419 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8422 - Fix a macro/CPP interaction that was confusing some compilers:
8423 some GCCs don't like #if/#endif pairs inside macro arguments.
8425 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8426 Fixes bug 704; fix from Steven Murdoch.
8427 - When opening /dev/null in finish_daemonize(), do not pass the
8428 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8429 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8430 - Correctly detect transparent proxy support on Linux hosts that
8431 require in.h to be included before netfilter_ipv4.h. Patch
8433 - Disallow session resumption attempts during the renegotiation
8434 stage of the v2 handshake protocol. Clients should never be trying
8435 session resumption at this point, but apparently some did, in
8436 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8437 found by Geoff Goodell.
8440 Changes in version 0.2.1.2-alpha - 2008-06-20
8441 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8442 make it easier to set up your own private Tor network; fixes several
8443 big bugs with using more than one bridge relay; fixes a big bug with
8444 offering hidden services quickly after Tor starts; and uses a better
8445 API for reporting potential bootstrapping problems to the controller.
8448 - New TestingTorNetwork config option to allow adjustment of
8449 previously constant values that, while reasonable, could slow
8450 bootstrapping. Implements proposal 135. Patch from Karsten.
8453 - If you have more than one bridge but don't know their digests,
8454 you would only learn a request for the descriptor of the first one
8455 on your list. (Tor considered launching requests for the others, but
8456 found that it already had a connection on the way for $0000...0000
8457 so it didn't open another.) Bugfix on 0.2.0.x.
8458 - If you have more than one bridge but don't know their digests,
8459 and the connection to one of the bridges failed, you would cancel
8460 all pending bridge connections. (After all, they all have the
8461 same digest.) Bugfix on 0.2.0.x.
8462 - When establishing a hidden service, introduction points that
8463 originate from cannibalized circuits are completely ignored and not
8464 included in rendezvous service descriptors. This might be another
8465 reason for delay in making a hidden service available. Bugfix
8466 from long ago (0.0.9.x?)
8469 - Allow OpenSSL to use dynamic locks if it wants.
8470 - When building a consensus, do not include routers that are down.
8471 This will cut down 30% to 40% on consensus size. Implements
8473 - In directory authorities' approved-routers files, allow
8474 fingerprints with or without space.
8475 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8476 controller can query our current bootstrap state in case it attaches
8477 partway through and wants to catch up.
8478 - Send an initial "Starting" bootstrap status event, so we have a
8479 state to start out in.
8482 - Asking for a conditional consensus at .../consensus/<fingerprints>
8483 would crash a dirserver if it did not already have a
8484 consensus. Bugfix on 0.2.1.1-alpha.
8485 - Clean up some macro/CPP interactions: some GCC versions don't like
8486 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8489 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8490 - Directory authorities shouldn't complain about bootstrapping
8491 problems just because they do a lot of reachability testing and
8492 some of the connection attempts fail.
8493 - Start sending "count" and "recommendation" key/value pairs in
8494 bootstrap problem status events, so the controller can hear about
8495 problems even before Tor decides they're worth reporting for sure.
8496 - If you're using bridges, generate "bootstrap problem" warnings
8497 as soon as you run out of working bridges, rather than waiting
8498 for ten failures -- which will never happen if you have less than
8500 - If we close our OR connection because there's been a circuit
8501 pending on it for too long, we were telling our bootstrap status
8502 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8505 Changes in version 0.2.1.1-alpha - 2008-06-13
8506 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8507 were making the Tor process bloat especially on Linux; makes our TLS
8508 handshake blend in better; sends "bootstrap phase" status events to
8509 the controller, so it can keep the user informed of progress (and
8510 problems) fetching directory information and establishing circuits;
8511 and adds a variety of smaller features.
8514 - More work on making our TLS handshake blend in: modify the list
8515 of ciphers advertised by OpenSSL in client mode to even more
8516 closely resemble a common web browser. We cheat a little so that
8517 we can advertise ciphers that the locally installed OpenSSL doesn't
8519 - Start sending "bootstrap phase" status events to the controller,
8520 so it can keep the user informed of progress fetching directory
8521 information and establishing circuits. Also inform the controller
8522 if we think we're stuck at a particular bootstrap phase. Implements
8524 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8525 cross-platform entropy collection again. We used to use it, then
8526 stopped using it because of a bug that could crash systems that
8527 called RAND_poll when they had a lot of fds open. It looks like the
8528 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8529 at startup, and to call RAND_poll() when we reseed later only if
8530 we have a non-buggy OpenSSL version.
8533 - When we choose to abandon a new entry guard because we think our
8534 older ones might be better, close any circuits pending on that
8535 new entry guard connection. This fix should make us recover much
8536 faster when our network is down and then comes back. Bugfix on
8537 0.1.2.8-beta; found by lodger.
8539 o Memory fixes and improvements:
8540 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8541 to avoid unused RAM in buffer chunks and memory pools.
8542 - Speed up parsing and cut down on memory fragmentation by using
8543 stack-style allocations for parsing directory objects. Previously,
8544 this accounted for over 40% of allocations from within Tor's code
8545 on a typical directory cache.
8546 - Use a Bloom filter rather than a digest-based set to track which
8547 descriptors we need to keep around when we're cleaning out old
8548 router descriptors. This speeds up the computation significantly,
8549 and may reduce fragmentation.
8550 - Reduce the default smartlist size from 32 to 16; it turns out that
8551 most smartlists hold around 8-12 elements tops.
8552 - Make dumpstats() log the fullness and size of openssl-internal
8554 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8555 patch to their OpenSSL, turn it on to save memory on servers. This
8556 patch will (with any luck) get included in a mainline distribution
8558 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8559 compress cells, which are basically all encrypted, compressed,
8563 - Stop reloading the router list from disk for no reason when we
8564 run out of reachable directory mirrors. Once upon a time reloading
8565 it would set the 'is_running' flag back to 1 for them. It hasn't
8566 done that for a long time.
8567 - In very rare situations new hidden service descriptors were
8568 published earlier than 30 seconds after the last change to the
8569 service. (We currently think that a hidden service descriptor
8570 that's been stable for 30 seconds is worth publishing.)
8573 - Allow separate log levels to be configured for different logging
8574 domains. For example, this allows one to log all notices, warnings,
8575 or errors, plus all memory management messages of level debug or
8576 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8577 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8578 and stop using a warning that had become unfixably verbose under
8580 - New --hush command-line option similar to --quiet. While --quiet
8581 disables all logging to the console on startup, --hush limits the
8582 output to messages of warning and error severity.
8583 - Servers support a new URL scheme for consensus downloads that
8584 allows the client to specify which authorities are trusted.
8585 The server then only sends the consensus if the client will trust
8586 it. Otherwise a 404 error is sent back. Clients use this
8587 new scheme when the server supports it (meaning it's running
8588 0.2.1.1-alpha or later). Implements proposal 134.
8589 - New configure/torrc options (--enable-geoip-stats,
8590 DirRecordUsageByCountry) to record how many IPs we've served
8591 directory info to in each country code, how many status documents
8592 total we've sent to each country code, and what share of the total
8593 directory requests we should expect to see.
8594 - Use the TLS1 hostname extension to more closely resemble browser
8596 - Lots of new unit tests.
8597 - Add a macro to implement the common pattern of iterating through
8598 two parallel lists in lockstep.
8601 Changes in version 0.2.0.28-rc - 2008-06-13
8602 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8603 performance bug, and fixes a bunch of smaller bugs.
8606 - Fix a bug where, when we were choosing the 'end stream reason' to
8607 put in our relay end cell that we send to the exit relay, Tor
8608 clients on Windows were sometimes sending the wrong 'reason'. The
8609 anonymity problem is that exit relays may be able to guess whether
8610 the client is running Windows, thus helping partition the anonymity
8611 set. Down the road we should stop sending reasons to exit relays,
8612 or otherwise prevent future versions of this bug.
8615 - While setting up a hidden service, some valid introduction circuits
8616 were overlooked and abandoned. This might be the reason for
8617 the long delay in making a hidden service available. Bugfix on
8621 - Update to the "June 9 2008" ip-to-country file.
8622 - Run 'make test' as part of 'make dist', so we stop releasing so
8623 many development snapshots that fail their unit tests.
8626 - When we're checking if we have enough dir info for each relay
8627 to begin establishing circuits, make sure that we actually have
8628 the descriptor listed in the consensus, not just any descriptor.
8630 - Bridge relays no longer print "xx=0" in their extrainfo document
8631 for every single country code in the geoip db. Bugfix on
8633 - Only warn when we fail to load the geoip file if we were planning to
8634 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8635 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8636 Tor won't realize it should publish a new relay descriptor. Fixes
8637 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8638 - When we haven't had any application requests lately, don't bother
8639 logging that we have expired a bunch of descriptors. Bugfix
8641 - Make relay cells written on a connection count as non-padding when
8642 tracking how long a connection has been in use. Bugfix on
8643 0.2.0.1-alpha. Spotted by lodger.
8644 - Fix unit tests in 0.2.0.27-rc.
8645 - Fix compile on Windows.
8648 Changes in version 0.2.0.27-rc - 2008-06-03
8649 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8650 release candidates. In particular, we now include an IP-to-country
8651 GeoIP database, so controllers can easily look up what country a
8652 given relay is in, and so bridge relays can give us some sanitized
8653 summaries about which countries are making use of bridges. (See proposal
8654 126-geoip-fetching.txt for details.)
8657 - Include an IP-to-country GeoIP file in the tarball, so bridge
8658 relays can report sanitized summaries of the usage they're seeing.
8661 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8662 Robert Hogan. Fixes the first part of bug 681.
8663 - Make bridge authorities never serve extrainfo docs.
8664 - Add support to detect Libevent versions in the 1.4.x series
8666 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8667 - Include a new contrib/tor-exit-notice.html file that exit relay
8668 operators can put on their website to help reduce abuse queries.
8671 - When tunneling an encrypted directory connection, and its first
8672 circuit fails, do not leave it unattached and ask the controller
8673 to deal. Fixes the second part of bug 681.
8674 - Make bridge authorities correctly expire old extrainfo documents
8678 Changes in version 0.2.0.26-rc - 2008-05-13
8679 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8680 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8681 should upgrade, whether they're running Debian or not.
8683 o Major security fixes:
8684 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8685 moria1 V3 directory authorities. The old keys were generated with
8686 a vulnerable version of Debian's OpenSSL package, and must be
8687 considered compromised. Other authorities' keys were not generated
8688 with an affected version of OpenSSL.
8691 - List authority signatures as "unrecognized" based on DirServer
8692 lines, not on cert cache. Bugfix on 0.2.0.x.
8695 - Add a new V3AuthUseLegacyKey option to make it easier for
8696 authorities to change their identity keys if they have to.
8699 Changes in version 0.2.0.25-rc - 2008-04-23
8700 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8703 - Remember to initialize threading before initializing logging.
8704 Otherwise, many BSD-family implementations will crash hard on
8705 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8708 - Authorities correctly free policies on bad servers on
8709 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8712 Changes in version 0.2.0.24-rc - 2008-04-22
8713 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8714 v3 directory authority, makes relays with dynamic IP addresses and no
8715 DirPort notice more quickly when their IP address changes, fixes a few
8716 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8718 o New directory authorities:
8719 - Take lefkada out of the list of v3 directory authorities, since
8720 it has been down for months.
8721 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8725 - Detect address changes more quickly on non-directory mirror
8726 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8728 o Minor features (security):
8729 - Reject requests for reverse-dns lookup of names that are in
8730 a private address space. Patch from lodger.
8731 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8734 o Minor bugfixes (crashes):
8735 - Avoid a rare assert that can trigger when Tor doesn't have much
8736 directory information yet and it tries to fetch a v2 hidden
8737 service descriptor. Fixes bug 651, reported by nwf.
8738 - Initialize log mutex before initializing dmalloc. Otherwise,
8739 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8740 - Use recursive pthread mutexes in order to avoid deadlock when
8741 logging debug-level messages to a controller. Bug spotted by nwf,
8742 bugfix on 0.2.0.16-alpha.
8744 o Minor bugfixes (resource management):
8745 - Keep address policies from leaking memory: start their refcount
8746 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8747 - Free authority certificates on exit, so they don't look like memory
8748 leaks. Bugfix on 0.2.0.19-alpha.
8749 - Free static hashtables for policy maps and for TLS connections on
8750 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
8751 - Avoid allocating extra space when computing consensuses on 64-bit
8752 platforms. Bug spotted by aakova.
8754 o Minor bugfixes (misc):
8755 - Do not read the configuration file when we've only been told to
8756 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8757 based on patch from Sebastian Hahn.
8758 - Exit relays that are used as a client can now reach themselves
8759 using the .exit notation, rather than just launching an infinite
8760 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8761 - When attempting to open a logfile fails, tell us why.
8762 - Fix a dumb bug that was preventing us from knowing that we should
8763 preemptively build circuits to handle expected directory requests.
8764 Fixes bug 660. Bugfix on 0.1.2.x.
8765 - Warn less verbosely about clock skew from netinfo cells from
8766 untrusted sources. Fixes bug 663.
8767 - Make controller stream events for DNS requests more consistent,
8768 by adding "new stream" events for DNS requests, and removing
8769 spurious "stream closed" events" for cached reverse resolves.
8770 Patch from mwenge. Fixes bug 646.
8771 - Correctly notify one-hop connections when a circuit build has
8772 failed. Possible fix for bug 669. Found by lodger.
8775 Changes in version 0.2.0.23-rc - 2008-03-24
8776 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
8777 makes bootstrapping faster if the first directory mirror you contact
8778 is down. The bundles also include the new Vidalia 0.1.2 release.
8781 - When a tunneled directory request is made to a directory server
8782 that's down, notice after 30 seconds rather than 120 seconds. Also,
8783 fail any begindir streams that are pending on it, so they can
8784 retry elsewhere. This was causing multi-minute delays on bootstrap.
8787 Changes in version 0.2.0.22-rc - 2008-03-18
8788 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
8789 enables encrypted directory connections by default for non-relays, fixes
8790 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
8791 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
8794 - Enable encrypted directory connections by default for non-relays,
8795 so censor tools that block Tor directory connections based on their
8796 plaintext patterns will no longer work. This means Tor works in
8797 certain censored countries by default again.
8800 - Make sure servers always request certificates from clients during
8801 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
8802 - Do not enter a CPU-eating loop when a connection is closed in
8803 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
8804 diagnosed by lodger; bugfix on 0.2.0.20-rc.
8805 - Fix assertion failure that could occur when a blocked circuit
8806 became unblocked, and it had pending client DNS requests. Bugfix
8807 on 0.2.0.1-alpha. Fixes bug 632.
8809 o Minor bugfixes (on 0.1.2.x):
8810 - Generate "STATUS_SERVER" events rather than misspelled
8811 "STATUS_SEVER" events. Caught by mwenge.
8812 - When counting the number of bytes written on a TLS connection,
8813 look at the BIO actually used for writing to the network, not
8814 at the BIO used (sometimes) to buffer data for the network.
8815 Looking at different BIOs could result in write counts on the
8816 order of ULONG_MAX. Fixes bug 614.
8817 - On Windows, correctly detect errors when listing the contents of
8818 a directory. Fix from lodger.
8820 o Minor bugfixes (on 0.2.0.x):
8821 - Downgrade "sslv3 alert handshake failure" message to INFO.
8822 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
8823 left BandwidthRate and BandwidthBurst at the default, we would be
8824 silently limited by those defaults. Now raise them to match the
8825 RelayBandwidth* values.
8826 - Fix the SVK version detection logic to work correctly on a branch.
8827 - Make --enable-openbsd-malloc work correctly on Linux with alpha
8828 CPUs. Fixes bug 625.
8829 - Logging functions now check that the passed severity is sane.
8830 - Use proper log levels in the testsuite call of
8831 get_interface_address6().
8832 - When using a nonstandard malloc, do not use the platform values for
8833 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
8834 - Make the openbsd malloc code use 8k pages on alpha CPUs and
8836 - Detect mismatched page sizes when using --enable-openbsd-malloc.
8837 - Avoid double-marked-for-close warning when certain kinds of invalid
8838 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
8839 for bug 617. Bugfix on 0.2.0.1-alpha.
8840 - Make sure that the "NULL-means-reject *:*" convention is followed by
8841 all the policy manipulation functions, avoiding some possible crash
8842 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
8843 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
8844 actually works, and doesn't warn about every single reverse lookup.
8845 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
8848 - Only log guard node status when guard node status has changed.
8849 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
8850 make "INFO" 75% less verbose.
8853 Changes in version 0.2.0.21-rc - 2008-03-02
8854 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
8855 makes Tor work well with Vidalia again, fixes a rare assert bug,
8856 and fixes a pair of more minor bugs. The bundles also include Vidalia
8857 0.1.0 and Torbutton 1.1.16.
8860 - The control port should declare that it requires password auth
8861 when HashedControlSessionPassword is set too. Patch from Matt Edman;
8862 bugfix on 0.2.0.20-rc. Fixes bug 615.
8863 - Downgrade assert in connection_buckets_decrement() to a log message.
8864 This may help us solve bug 614, and in any case will make its
8865 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
8866 - We were sometimes miscounting the number of bytes read from the
8867 network, causing our rate limiting to not be followed exactly.
8868 Bugfix on 0.2.0.16-alpha. Reported by lodger.
8871 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
8872 OpenSSL versions should have been working fine. Diagnosis and patch
8873 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
8874 Bugfix on 0.2.0.20-rc.
8877 Changes in version 0.2.0.20-rc - 2008-02-24
8878 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
8879 makes more progress towards normalizing Tor's TLS handshake, makes
8880 hidden services work better again, helps relays bootstrap if they don't
8881 know their IP address, adds optional support for linking in openbsd's
8882 allocator or tcmalloc, allows really fast relays to scale past 15000
8883 sockets, and fixes a bunch of minor bugs reported by Veracode.
8886 - Enable the revised TLS handshake based on the one designed by
8887 Steven Murdoch in proposal 124, as revised in proposal 130. It
8888 includes version negotiation for OR connections as described in
8889 proposal 105. The new handshake is meant to be harder for censors
8890 to fingerprint, and it adds the ability to detect certain kinds of
8891 man-in-the-middle traffic analysis attacks. The version negotiation
8892 feature will allow us to improve Tor's link protocol more safely
8894 - Choose which bridge to use proportional to its advertised bandwidth,
8895 rather than uniformly at random. This should speed up Tor for
8896 bridge users. Also do this for people who set StrictEntryNodes.
8897 - When a TrackHostExits-chosen exit fails too many times in a row,
8898 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
8901 - Resolved problems with (re-)fetching hidden service descriptors.
8902 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
8904 - If we only ever used Tor for hidden service lookups or posts, we
8905 would stop building circuits and start refusing connections after
8906 24 hours, since we falsely believed that Tor was dormant. Reported
8907 by nwf; bugfix on 0.1.2.x.
8908 - Servers that don't know their own IP address should go to the
8909 authorities for their first directory fetch, even if their DirPort
8910 is off or if they don't know they're reachable yet. This will help
8911 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
8912 - When counting the number of open sockets, count not only the number
8913 of sockets we have received from the socket() call, but also
8914 the number we've gotten from accept() and socketpair(). This bug
8915 made us fail to count all sockets that we were using for incoming
8916 connections. Bugfix on 0.2.0.x.
8917 - Fix code used to find strings within buffers, when those strings
8918 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
8919 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
8920 - Add a new __HashedControlSessionPassword option for controllers
8921 to use for one-off session password hashes that shouldn't get
8922 saved to disk by SAVECONF --- Vidalia users were accumulating a
8923 pile of HashedControlPassword lines in their torrc files, one for
8924 each time they had restarted Tor and then clicked Save. Make Tor
8925 automatically convert "HashedControlPassword" to this new option but
8926 only when it's given on the command line. Partial fix for bug 586.
8928 o Minor features (performance):
8929 - Tune parameters for cell pool allocation to minimize amount of
8931 - Add OpenBSD malloc code from phk as an optional malloc
8932 replacement on Linux: some glibc libraries do very poorly
8933 with Tor's memory allocation patterns. Pass
8934 --enable-openbsd-malloc to get the replacement malloc code.
8935 - Add a --with-tcmalloc option to the configure script to link
8936 against tcmalloc (if present). Does not yet search for
8937 non-system include paths.
8938 - Stop imposing an arbitrary maximum on the number of file descriptors
8939 used for busy servers. Bug reported by Olaf Selke; patch from
8942 o Minor features (other):
8943 - When SafeLogging is disabled, log addresses along with all TLS
8945 - When building with --enable-gcc-warnings, check for whether Apple's
8946 warning "-Wshorten-64-to-32" is available.
8947 - Add a --passphrase-fd argument to the tor-gencert command for
8950 o Minor bugfixes (memory leaks and code problems):
8951 - We were leaking a file descriptor if Tor started with a zero-length
8952 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
8953 - Detect size overflow in zlib code. Reported by Justin Ferguson and
8955 - We were comparing the raw BridgePassword entry with a base64'ed
8956 version of it, when handling a "/tor/networkstatus-bridges"
8957 directory request. Now compare correctly. Noticed by Veracode.
8958 - Recover from bad tracked-since value in MTBF-history file.
8960 - Alter the code that tries to recover from unhandled write
8961 errors, to not try to flush onto a socket that's given us
8962 unhandled errors. Bugfix on 0.1.2.x.
8963 - Make Unix controlsockets work correctly on OpenBSD. Patch from
8964 tup. Bugfix on 0.2.0.3-alpha.
8966 o Minor bugfixes (other):
8967 - If we have an extra-info document for our server, always make
8968 it available on the control port, even if we haven't gotten
8969 a copy of it from an authority yet. Patch from mwenge.
8970 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
8971 - Directory mirrors no longer include a guess at the client's IP
8972 address if the connection appears to be coming from the same /24
8973 network; it was producing too many wrong guesses.
8974 - Make the new hidden service code respect the SafeLogging setting.
8975 Bugfix on 0.2.0.x. Patch from Karsten.
8976 - When starting as an authority, do not overwrite all certificates
8977 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
8978 - If we're trying to flush the last bytes on a connection (for
8979 example, when answering a directory request), reset the
8980 time-to-give-up timeout every time we manage to write something
8981 on the socket. Bugfix on 0.1.2.x.
8982 - Change the behavior of "getinfo status/good-server-descriptor"
8983 so it doesn't return failure when any authority disappears.
8984 - Even though the man page said that "TrackHostExits ." should
8985 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
8986 - Report TLS "zero return" case as a "clean close" and "IO error"
8987 as a "close". Stop calling closes "unexpected closes": existing
8988 Tors don't use SSL_close(), so having a connection close without
8989 the TLS shutdown handshake is hardly unexpected.
8990 - Send NAMESERVER_STATUS messages for a single failed nameserver
8993 o Code simplifications and refactoring:
8994 - Remove the tor_strpartition function: its logic was confused,
8995 and it was only used for one thing that could be implemented far
8999 Changes in version 0.2.0.19-alpha - 2008-02-09
9000 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9001 handshake, makes path selection for relays more secure and IP address
9002 guessing more robust, and generally fixes a lot of bugs in preparation
9003 for calling the 0.2.0 branch stable.
9006 - Do not include recognizeable strings in the commonname part of
9007 Tor's x509 certificates.
9010 - If we're a relay, avoid picking ourselves as an introduction point,
9011 a rendezvous point, or as the final hop for internal circuits. Bug
9012 reported by taranis and lodger. Bugfix on 0.1.2.x.
9013 - Patch from "Andrew S. Lists" to catch when we contact a directory
9014 mirror at IP address X and he says we look like we're coming from
9015 IP address X. Bugfix on 0.1.2.x.
9017 o Minor features (security):
9018 - Be more paranoid about overwriting sensitive memory on free(),
9019 as a defensive programming tactic to ensure forward secrecy.
9021 o Minor features (directory authority):
9022 - Actually validate the options passed to AuthDirReject,
9023 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9024 - Reject router descriptors with out-of-range bandwidthcapacity or
9025 bandwidthburst values.
9027 o Minor features (controller):
9028 - Reject controller commands over 1MB in length. This keeps rogue
9029 processes from running us out of memory.
9031 o Minor features (misc):
9032 - Give more descriptive well-formedness errors for out-of-range
9033 hidden service descriptor/protocol versions.
9034 - Make memory debugging information describe more about history
9035 of cell allocation, so we can help reduce our memory use.
9037 o Deprecated features (controller):
9038 - The status/version/num-versioning and status/version/num-concurring
9039 GETINFO options are no longer useful in the v3 directory protocol:
9040 treat them as deprecated, and warn when they're used.
9043 - When our consensus networkstatus has been expired for a while, stop
9044 being willing to build circuits using it. Fixes bug 401. Bugfix
9046 - Directory caches now fetch certificates from all authorities
9047 listed in a networkstatus consensus, even when they do not
9048 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9049 - When connecting to a bridge without specifying its key, insert
9050 the connection into the identity-to-connection map as soon as
9051 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9052 - Detect versions of OS X where malloc_good_size() is present in the
9053 library but never actually declared. Resolves bug 587. Bugfix
9055 - Stop incorrectly truncating zlib responses to directory authority
9056 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9057 - Stop recommending that every server operator send mail to tor-ops.
9058 Resolves bug 597. Bugfix on 0.1.2.x.
9059 - Don't trigger an assert if we start a directory authority with a
9060 private IP address (like 127.0.0.1).
9061 - Avoid possible failures when generating a directory with routers
9062 with over-long versions strings, or too many flags set. Bugfix
9064 - If an attempt to launch a DNS resolve request over the control
9065 port fails because we have overrun the limit on the number of
9066 connections, tell the controller that the request has failed.
9067 - Avoid using too little bandwidth when our clock skips a few
9068 seconds. Bugfix on 0.1.2.x.
9069 - Fix shell error when warning about missing packages in configure
9070 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9071 - Do not become confused when receiving a spurious VERSIONS-like
9072 cell from a confused v1 client. Bugfix on 0.2.0.x.
9073 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9074 introduction points for a hidden service have failed. Patch from
9075 Karsten Loesing. Bugfix on 0.2.0.x.
9077 o Code simplifications and refactoring:
9078 - Remove some needless generality from cpuworker code, for improved
9080 - Stop overloading the circuit_t.onionskin field for both "onionskin
9081 from a CREATE cell that we are waiting for a cpuworker to be
9082 assigned" and "onionskin from an EXTEND cell that we are going to
9083 send to an OR as soon as we are connected". Might help with bug 600.
9084 - Add an in-place version of aes_crypt() so that we can avoid doing a
9085 needless memcpy() call on each cell payload.
9088 Changes in version 0.2.0.18-alpha - 2008-01-25
9089 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9090 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9091 that can warn or reject connections to ports generally associated with
9092 vulnerable-plaintext protocols.
9094 o New directory authorities:
9095 - Set up dannenberg (run by CCC) as the sixth v3 directory
9099 - Fix a major memory leak when attempting to use the v2 TLS
9100 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9101 - We accidentally enabled the under-development v2 TLS handshake
9102 code, which was causing log entries like "TLS error while
9103 renegotiating handshake". Disable it again. Resolves bug 590.
9104 - We were computing the wrong Content-Length: header for directory
9105 responses that need to be compressed on the fly, causing clients
9106 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9110 - Avoid going directly to the directory authorities even if you're a
9111 relay, if you haven't found yourself reachable yet or if you've
9112 decided not to advertise your dirport yet. Addresses bug 556.
9113 - If we've gone 12 hours since our last bandwidth check, and we
9114 estimate we have less than 50KB bandwidth capacity but we could
9115 handle more, do another bandwidth test.
9116 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9117 Tor can warn and/or refuse connections to ports commonly used with
9118 vulnerable-plaintext protocols. Currently we warn on ports 23,
9119 109, 110, and 143, but we don't reject any.
9122 - When we setconf ClientOnly to 1, close any current OR and Dir
9123 listeners. Reported by mwenge.
9124 - When we get a consensus that's been signed by more people than
9125 we expect, don't log about it; it's not a big deal. Reported
9129 - Don't answer "/tor/networkstatus-bridges" directory requests if
9130 the request isn't encrypted.
9131 - Make "ClientOnly 1" config option disable directory ports too.
9132 - Patches from Karsten Loesing to make v2 hidden services more
9133 robust: work even when there aren't enough HSDir relays available;
9134 retry when a v2 rend desc fetch fails; but don't retry if we
9135 already have a usable v0 rend desc.
9138 Changes in version 0.2.0.17-alpha - 2008-01-17
9139 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9142 - Make the tor-gencert man page get included correctly in the tarball.
9145 Changes in version 0.2.0.16-alpha - 2008-01-17
9146 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9147 Loesing, and generally cleans up a lot of features and minor bugs.
9149 o New directory authorities:
9150 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9153 o Major performance improvements:
9154 - Switch our old ring buffer implementation for one more like that
9155 used by free Unix kernels. The wasted space in a buffer with 1mb
9156 of data will now be more like 8k than 1mb. The new implementation
9157 also avoids realloc();realloc(); patterns that can contribute to
9158 memory fragmentation.
9161 - Configuration files now accept C-style strings as values. This
9162 helps encode characters not allowed in the current configuration
9163 file format, such as newline or #. Addresses bug 557.
9164 - Although we fixed bug 539 (where servers would send HTTP status 503
9165 responses _and_ send a body too), there are still servers out
9166 there that haven't upgraded. Therefore, make clients parse such
9167 bodies when they receive them.
9168 - When we're not serving v2 directory information, there is no reason
9169 to actually keep any around. Remove the obsolete files and directory
9170 on startup if they are very old and we aren't going to serve them.
9172 o Minor performance improvements:
9173 - Reference-count and share copies of address policy entries; only 5%
9174 of them were actually distinct.
9175 - Never walk through the list of logs if we know that no log is
9176 interested in a given message.
9179 - When an authority has not signed a consensus, do not try to
9180 download a nonexistent "certificate with key 00000000". Bugfix
9181 on 0.2.0.x. Fixes bug 569.
9182 - Fix a rare assert error when we're closing one of our threads:
9183 use a mutex to protect the list of logs, so we never write to the
9184 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9185 bug 575, which is kind of the revenge of bug 222.
9186 - Patch from Karsten Loesing to complain less at both the client
9187 and the relay when a relay used to have the HSDir flag but doesn't
9188 anymore, and we try to upload a hidden service descriptor.
9189 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9191 - Do not try to download missing certificates until we have tried
9192 to check our fallback consensus. Fixes bug 583.
9193 - Make bridges round reported GeoIP stats info up to the nearest
9194 estimate, not down. Now we can distinguish between "0 people from
9195 this country" and "1 person from this country".
9196 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9197 - Avoid possible segfault if key generation fails in
9198 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9199 - Avoid segfault in the case where a badly behaved v2 versioning
9200 directory sends a signed networkstatus with missing client-versions.
9202 - Avoid segfaults on certain complex invocations of
9203 router_get_by_hexdigest(). Bugfix on 0.1.2.
9204 - Correct bad index on array access in parse_http_time(). Bugfix
9206 - Fix possible bug in vote generation when server versions are present
9207 but client versions are not.
9208 - Fix rare bug on REDIRECTSTREAM control command when called with no
9209 port set: it could erroneously report an error when none had
9211 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9212 compressing large objects and find ourselves with more than 4k
9213 left over. Bugfix on 0.2.0.
9214 - Fix a small memory leak when setting up a hidden service.
9215 - Fix a few memory leaks that could in theory happen under bizarre
9217 - Fix an assert if we post a general-purpose descriptor via the
9218 control port but that descriptor isn't mentioned in our current
9219 network consensus. Bug reported by Jon McLachlan; bugfix on
9222 o Minor features (controller):
9223 - Get NS events working again. Patch from tup.
9224 - The GETCONF command now escapes and quotes configuration values
9225 that don't otherwise fit into the torrc file.
9226 - The SETCONF command now handles quoted values correctly.
9228 o Minor features (directory authorities):
9229 - New configuration options to override default maximum number of
9230 servers allowed on a single IP address. This is important for
9231 running a test network on a single host.
9232 - Actually implement the -s option to tor-gencert.
9233 - Add a manual page for tor-gencert.
9235 o Minor features (bridges):
9236 - Bridge authorities no longer serve bridge descriptors over
9237 unencrypted connections.
9239 o Minor features (other):
9240 - Add hidden services and DNSPorts to the list of things that make
9241 Tor accept that it has running ports. Change starting Tor with no
9242 ports from a fatal error to a warning; we might change it back if
9243 this turns out to confuse anybody. Fixes bug 579.
9246 Changes in version 0.1.2.19 - 2008-01-17
9247 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9248 exit policy a little bit more conservative so it's safer to run an
9249 exit relay on a home system, and fixes a variety of smaller issues.
9252 - Exit policies now reject connections that are addressed to a
9253 relay's public (external) IP address too, unless
9254 ExitPolicyRejectPrivate is turned off. We do this because too
9255 many relays are running nearby to services that trust them based
9259 - When the clock jumps forward a lot, do not allow the bandwidth
9260 buckets to become negative. Fixes bug 544.
9261 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9262 on every successful resolve. Reported by Mike Perry.
9263 - Purge old entries from the "rephist" database and the hidden
9264 service descriptor database even when DirPort is zero.
9265 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9266 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9267 crashing or mis-answering these requests.
9268 - When we decide to send a 503 response to a request for servers, do
9269 not then also send the server descriptors: this defeats the whole
9270 purpose. Fixes bug 539.
9273 - Changing the ExitPolicyRejectPrivate setting should cause us to
9274 rebuild our server descriptor.
9275 - Fix handling of hex nicknames when answering controller requests for
9276 networkstatus by name, or when deciding whether to warn about
9277 unknown routers in a config option. (Patch from mwenge.)
9278 - Fix a couple of hard-to-trigger autoconf problems that could result
9279 in really weird results on platforms whose sys/types.h files define
9280 nonstandard integer types.
9281 - Don't try to create the datadir when running --verify-config or
9282 --hash-password. Resolves bug 540.
9283 - If we were having problems getting a particular descriptor from the
9284 directory caches, and then we learned about a new descriptor for
9285 that router, we weren't resetting our failure count. Reported
9287 - Although we fixed bug 539 (where servers would send HTTP status 503
9288 responses _and_ send a body too), there are still servers out there
9289 that haven't upgraded. Therefore, make clients parse such bodies
9290 when they receive them.
9291 - Run correctly on systems where rlim_t is larger than unsigned long.
9292 This includes some 64-bit systems.
9293 - Run correctly on platforms (like some versions of OS X 10.5) where
9294 the real limit for number of open files is OPEN_FILES, not rlim_max
9295 from getrlimit(RLIMIT_NOFILES).
9296 - Avoid a spurious free on base64 failure.
9297 - Avoid segfaults on certain complex invocations of
9298 router_get_by_hexdigest().
9299 - Fix rare bug on REDIRECTSTREAM control command when called with no
9300 port set: it could erroneously report an error when none had
9304 Changes in version 0.2.0.15-alpha - 2007-12-25
9305 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9306 features added in 0.2.0.13-alpha.
9309 - Fix several remotely triggerable asserts based on DirPort requests
9310 for a v2 or v3 networkstatus object before we were prepared. This
9311 was particularly bad for 0.2.0.13 and later bridge relays, who
9312 would never have a v2 networkstatus and would thus always crash
9313 when used. Bugfixes on 0.2.0.x.
9314 - Estimate the v3 networkstatus size more accurately, rather than
9315 estimating it at zero bytes and giving it artificially high priority
9316 compared to other directory requests. Bugfix on 0.2.0.x.
9319 - Fix configure.in logic for cross-compilation.
9320 - When we load a bridge descriptor from the cache, and it was
9321 previously unreachable, mark it as retriable so we won't just
9322 ignore it. Also, try fetching a new copy immediately. Bugfixes
9324 - The bridge GeoIP stats were counting other relays, for example
9325 self-reachability and authority-reachability tests.
9328 - Support compilation to target iPhone; patch from cjacker huang.
9329 To build for iPhone, pass the --enable-iphone option to configure.
9332 Changes in version 0.2.0.14-alpha - 2007-12-23
9334 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9335 without a datadirectory from a previous Tor install. Reported
9337 - Fix a crash when we fetch a descriptor that turns out to be
9338 unexpected (it used to be in our networkstatus when we started
9339 fetching it, but it isn't in our current networkstatus), and we
9340 aren't using bridges. Bugfix on 0.2.0.x.
9341 - Fix a crash when accessing hidden services: it would work the first
9342 time you use a given introduction point for your service, but
9343 on subsequent requests we'd be using garbage memory. Fixed by
9344 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9345 - Fix a crash when we load a bridge descriptor from disk but we don't
9346 currently have a Bridge line for it in our torrc. Bugfix on
9350 - If bridge authorities set BridgePassword, they will serve a
9351 snapshot of known bridge routerstatuses from their DirPort to
9352 anybody who knows that password. Unset by default.
9355 - Make the unit tests build again.
9356 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9357 - Make PublishServerDescriptor default to 1, so the default doesn't
9358 have to change as we invent new directory protocol versions.
9359 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9360 be included unless sys/time.h is already included. Fixes
9361 bug 553. Bugfix on 0.2.0.x.
9362 - If we receive a general-purpose descriptor and then receive an
9363 identical bridge-purpose descriptor soon after, don't discard
9364 the next one as a duplicate.
9367 - If BridgeRelay is set to 1, then the default for
9368 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9369 - If the user sets RelayBandwidthRate but doesn't set
9370 RelayBandwidthBurst, then make them equal rather than erroring out.
9373 Changes in version 0.2.0.13-alpha - 2007-12-21
9374 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9375 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9378 o New directory authorities:
9379 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9383 - Only update guard status (usable / not usable) once we have
9384 enough directory information. This was causing us to always pick
9385 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9386 causing us to discard all our guards on startup if we hadn't been
9387 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9388 - Purge old entries from the "rephist" database and the hidden
9389 service descriptor databases even when DirPort is zero. Bugfix
9391 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9392 after opening a circuit -- even a relayed circuit. Bugfix on
9394 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9395 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9396 crashing or mis-answering these types of requests.
9397 - Relays were publishing their server descriptor to v1 and v2
9398 directory authorities, but they didn't try publishing to v3-only
9399 authorities. Fix this; and also stop publishing to v1 authorities.
9401 - When we were reading router descriptors from cache, we were ignoring
9402 the annotations -- so for example we were reading in bridge-purpose
9403 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9404 - When we decided to send a 503 response to a request for servers, we
9405 were then also sending the server descriptors: this defeats the
9406 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9409 - Bridge relays now behave like clients with respect to time
9410 intervals for downloading new consensus documents -- otherwise they
9411 stand out. Bridge users now wait until the end of the interval,
9412 so their bridge relay will be sure to have a new consensus document.
9413 - Three new config options (AlternateDirAuthority,
9414 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9415 user selectively replace the default directory authorities by type,
9416 rather than the all-or-nothing replacement that DirServer offers.
9417 - Tor can now be configured to read a GeoIP file from disk in one
9418 of two formats. This can be used by controllers to map IP addresses
9419 to countries. Eventually, it may support exit-by-country.
9420 - When possible, bridge relays remember which countries users
9421 are coming from, and report aggregate information in their
9422 extra-info documents, so that the bridge authorities can learn
9423 where Tor is blocked.
9424 - Bridge directory authorities now do reachability testing on the
9425 bridges they know. They provide router status summaries to the
9426 controller via "getinfo ns/purpose/bridge", and also dump summaries
9427 to a file periodically.
9428 - Stop fetching directory info so aggressively if your DirPort is
9429 on but your ORPort is off; stop fetching v2 dir info entirely.
9430 You can override these choices with the new FetchDirInfoEarly
9434 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9435 consensus documents when there are too many relays at a single
9436 IP address. Now clear it in v2 network status documents too, and
9437 also clear it in routerinfo_t when the relay is no longer listed
9438 in the relevant networkstatus document.
9439 - Don't crash if we get an unexpected value for the
9440 PublishServerDescriptor config option. Reported by Matt Edman;
9441 bugfix on 0.2.0.9-alpha.
9442 - Our new v2 hidden service descriptor format allows descriptors
9443 that have no introduction points. But Tor crashed when we tried
9444 to build a descriptor with no intro points (and it would have
9445 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9447 - Fix building with dmalloc 5.5.2 with glibc.
9448 - Reject uploaded descriptors and extrainfo documents if they're
9449 huge. Otherwise we'll cache them all over the network and it'll
9450 clog everything up. Reported by Aljosha Judmayer.
9451 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9452 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9453 - When the DANGEROUS_VERSION controller status event told us we're
9454 running an obsolete version, it used the string "OLD" to describe
9455 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9456 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9457 - If we can't expand our list of entry guards (e.g. because we're
9458 using bridges or we have StrictEntryNodes set), don't mark relays
9459 down when they fail a directory request. Otherwise we're too quick
9460 to mark all our entry points down. Bugfix on 0.1.2.x.
9461 - Fix handling of hex nicknames when answering controller requests for
9462 networkstatus by name, or when deciding whether to warn about unknown
9463 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9464 - Fix a couple of hard-to-trigger autoconf problems that could result
9465 in really weird results on platforms whose sys/types.h files define
9466 nonstandard integer types. Bugfix on 0.1.2.x.
9467 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9468 - Don't crash on name lookup when we have no current consensus. Fixes
9469 bug 538; bugfix on 0.2.0.x.
9470 - Only Tors that want to mirror the v2 directory info should
9471 create the "cached-status" directory in their datadir. (All Tors
9472 used to create it.) Bugfix on 0.2.0.9-alpha.
9473 - Directory authorities should only automatically download Extra Info
9474 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9477 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9478 consumers. (We already do this on HUP.)
9479 - Authorities and caches fetch the v2 networkstatus documents
9480 less often, now that v3 is encouraged.
9481 - Add a new config option BridgeRelay that specifies you want to
9482 be a bridge relay. Right now the only difference is that it makes
9483 you answer begin_dir requests, and it makes you cache dir info,
9484 even if your DirPort isn't on.
9485 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9486 ask about source, timestamp of arrival, purpose, etc. We need
9487 something like this to help Vidalia not do GeoIP lookups on bridge
9489 - Allow multiple HashedControlPassword config lines, to support
9490 multiple controller passwords.
9491 - Authorities now decide whether they're authoritative for a given
9492 router based on the router's purpose.
9493 - New config options AuthDirBadDir and AuthDirListBadDirs for
9494 authorities to mark certain relays as "bad directories" in the
9495 networkstatus documents. Also supports the "!baddir" directive in
9496 the approved-routers file.
9499 Changes in version 0.2.0.12-alpha - 2007-11-16
9500 This twelfth development snapshot fixes some more build problems as
9501 well as a few minor bugs.
9504 - Make it build on OpenBSD again. Patch from tup.
9505 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9506 package-building for Red Hat, OS X, etc.
9508 o Minor bugfixes (on 0.1.2.x):
9509 - Changing the ExitPolicyRejectPrivate setting should cause us to
9510 rebuild our server descriptor.
9512 o Minor bugfixes (on 0.2.0.x):
9513 - When we're lacking a consensus, don't try to perform rendezvous
9514 operations. Reported by Karsten Loesing.
9515 - Fix a small memory leak whenever we decide against using a
9516 newly picked entry guard. Reported by Mike Perry.
9517 - When authorities detected more than two relays running on the same
9518 IP address, they were clearing all the status flags but forgetting
9519 to clear the "hsdir" flag. So clients were being told that a
9520 given relay was the right choice for a v2 hsdir lookup, yet they
9521 never had its descriptor because it was marked as 'not running'
9523 - If we're trying to fetch a bridge descriptor and there's no way
9524 the bridge authority could help us (for example, we don't know
9525 a digest, or there is no bridge authority), don't be so eager to
9526 fall back to asking the bridge authority.
9527 - If we're using bridges or have strictentrynodes set, and our
9528 chosen exit is in the same family as all our bridges/entry guards,
9529 then be flexible about families.
9532 - When we negotiate a v2 link-layer connection (not yet implemented),
9533 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9534 negotiated a v1 connection for their next step. Initial code for
9538 Changes in version 0.2.0.11-alpha - 2007-11-12
9539 This eleventh development snapshot fixes some build problems with
9540 the previous snapshot. It also includes a more secure-by-default exit
9541 policy for relays, fixes an enormous memory leak for exit relays, and
9542 fixes another bug where servers were falling out of the directory list.
9545 - Exit policies now reject connections that are addressed to a
9546 relay's public (external) IP address too, unless
9547 ExitPolicyRejectPrivate is turned off. We do this because too
9548 many relays are running nearby to services that trust them based
9549 on network address. Bugfix on 0.1.2.x.
9552 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9553 on every successful resolve. Reported by Mike Perry; bugfix
9555 - On authorities, never downgrade to old router descriptors simply
9556 because they're listed in the consensus. This created a catch-22
9557 where we wouldn't list a new descriptor because there was an
9558 old one in the consensus, and we couldn't get the new one in the
9559 consensus because we wouldn't list it. Possible fix for bug 548.
9560 Also, this might cause bug 543 to appear on authorities; if so,
9561 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9563 o Packaging fixes on 0.2.0.10-alpha:
9564 - We were including instructions about what to do with the
9565 src/config/fallback-consensus file, but we weren't actually
9566 including it in the tarball. Disable all of that for now.
9569 - Allow people to say PreferTunnelledDirConns rather than
9570 PreferTunneledDirConns, for those alternate-spellers out there.
9573 - Don't reevaluate all the information from our consensus document
9574 just because we've downloaded a v2 networkstatus that we intend
9575 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9578 Changes in version 0.2.0.10-alpha - 2007-11-10
9579 This tenth development snapshot adds a third v3 directory authority
9580 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9581 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9582 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9583 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9584 addresses many more minor issues.
9586 o New directory authorities:
9587 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9590 - Allow tunnelled directory connections to ask for an encrypted
9591 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9592 connection independently. Now we can make anonymized begin_dir
9593 connections for (e.g.) more secure hidden service posting and
9595 - More progress on proposal 114: code from Karsten Loesing to
9596 implement new hidden service descriptor format.
9597 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9598 accommodate the growing number of servers that use the default
9599 and are reaching it.
9600 - Directory authorities use a new formula for selecting which nodes
9601 to advertise as Guards: they must be in the top 7/8 in terms of
9602 how long we have known about them, and above the median of those
9603 nodes in terms of weighted fractional uptime.
9604 - Make "not enough dir info yet" warnings describe *why* Tor feels
9605 it doesn't have enough directory info yet.
9608 - Stop servers from crashing if they set a Family option (or
9609 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9611 - Make bridge users work again -- the move to v3 directories in
9612 0.2.0.9-alpha had introduced a number of bugs that made bridges
9613 no longer work for clients.
9614 - When the clock jumps forward a lot, do not allow the bandwidth
9615 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9617 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9618 - When the consensus lists a router descriptor that we previously were
9619 mirroring, but that we considered non-canonical, reload the
9620 descriptor as canonical. This fixes bug 543 where Tor servers
9621 would start complaining after a few days that they don't have
9622 enough directory information to build a circuit.
9623 - Consider replacing the current consensus when certificates arrive
9624 that make the pending consensus valid. Previously, we were only
9625 considering replacement when the new certs _didn't_ help.
9626 - Fix an assert error on startup if we didn't already have the
9627 consensus and certs cached in our datadirectory: we were caching
9628 the consensus in consensus_waiting_for_certs but then free'ing it
9630 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9631 Request) if we need more v3 certs but we've already got pending
9632 requests for all of them.
9633 - Correctly back off from failing certificate downloads. Fixes
9635 - Authorities don't vote on the Running flag if they have been running
9636 for less than 30 minutes themselves. Fixes bug 547, where a newly
9637 started authority would vote that everyone was down.
9640 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9641 it, it had no AES, and it hasn't seen any security patches since
9645 - Clients now hold circuitless TLS connections open for 1.5 times
9646 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9647 rebuild a new circuit over them within that timeframe. Previously,
9648 they held them open only for KeepalivePeriod (5 minutes).
9649 - Use "If-Modified-Since" to avoid retrieving consensus
9650 networkstatuses that we already have.
9651 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9652 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9653 we start knowing some directory caches.
9654 - When we receive a consensus from the future, warn about skew.
9655 - Improve skew reporting: try to give the user a better log message
9656 about how skewed they are, and how much this matters.
9657 - When we have a certificate for an authority, believe that
9658 certificate's claims about the authority's IP address.
9659 - New --quiet command-line option to suppress the default console log.
9660 Good in combination with --hash-password.
9661 - Authorities send back an X-Descriptor-Not-New header in response to
9662 an accepted-but-discarded descriptor upload. Partially implements
9664 - Make the log message for "tls error. breaking." more useful.
9665 - Better log messages about certificate downloads, to attempt to
9666 track down the second incarnation of bug 546.
9668 o Minor features (bridges):
9669 - If bridge users set UpdateBridgesFromAuthority, but the digest
9670 they ask for is a 404 from the bridge authority, they now fall
9671 back to trying the bridge directly.
9672 - Bridges now use begin_dir to publish their server descriptor to
9673 the bridge authority, even when they haven't set TunnelDirConns.
9675 o Minor features (controller):
9676 - When reporting clock skew, and we know that the clock is _at least
9677 as skewed_ as some value, but we don't know the actual value,
9678 report the value as a "minimum skew."
9681 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9682 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9686 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9687 on 0.2.0.x, suggested by Matt Edman.
9688 - Don't stop fetching descriptors when FetchUselessDescriptors is
9689 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9690 reported by tup and ioerror.
9691 - Better log message on vote from unknown authority.
9692 - Don't log "Launching 0 request for 0 router" message.
9694 o Minor bugfixes (memory leaks):
9695 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9697 - Stop leaking memory every time we load a v3 certificate. Bugfix
9698 on 0.2.0.1-alpha. Fixes bug 536.
9699 - Stop leaking a cached networkstatus on exit. Bugfix on
9701 - Stop leaking voter information every time we free a consensus.
9702 Bugfix on 0.2.0.3-alpha.
9703 - Stop leaking signed data every time we check a voter signature.
9704 Bugfix on 0.2.0.3-alpha.
9705 - Stop leaking a signature every time we fail to parse a consensus or
9706 a vote. Bugfix on 0.2.0.3-alpha.
9707 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9709 - Stop leaking conn->nickname every time we make a connection to a
9710 Tor relay without knowing its expected identity digest (e.g. when
9711 using bridges). Bugfix on 0.2.0.3-alpha.
9713 - Minor bugfixes (portability):
9714 - Run correctly on platforms where rlim_t is larger than unsigned
9715 long, and/or where the real limit for number of open files is
9716 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9717 particular, these may be needed for OS X 10.5.
9720 Changes in version 0.1.2.18 - 2007-10-28
9721 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9722 hidden service introduction that were causing huge delays, and a big
9723 bug that was causing some servers to disappear from the network status
9724 lists for a few hours each day.
9726 o Major bugfixes (crashes):
9727 - If a connection is shut down abruptly because of something that
9728 happened inside connection_flushed_some(), do not call
9729 connection_finished_flushing(). Should fix bug 451:
9730 "connection_stop_writing: Assertion conn->write_event failed"
9731 Bugfix on 0.1.2.7-alpha.
9732 - Fix possible segfaults in functions called from
9733 rend_process_relay_cell().
9735 o Major bugfixes (hidden services):
9736 - Hidden services were choosing introduction points uniquely by
9737 hexdigest, but when constructing the hidden service descriptor
9738 they merely wrote the (potentially ambiguous) nickname.
9739 - Clients now use the v2 intro format for hidden service
9740 connections: they specify their chosen rendezvous point by identity
9741 digest rather than by (potentially ambiguous) nickname. These
9742 changes could speed up hidden service connections dramatically.
9744 o Major bugfixes (other):
9745 - Stop publishing a new server descriptor just because we get a
9746 HUP signal. This led (in a roundabout way) to some servers getting
9747 dropped from the networkstatus lists for a few hours each day.
9748 - When looking for a circuit to cannibalize, consider family as well
9749 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9750 circuit cannibalization).
9751 - When a router wasn't listed in a new networkstatus, we were leaving
9752 the flags for that router alone -- meaning it remained Named,
9753 Running, etc -- even though absence from the networkstatus means
9754 that it shouldn't be considered to exist at all anymore. Now we
9755 clear all the flags for routers that fall out of the networkstatus
9756 consensus. Fixes bug 529.
9759 - Don't try to access (or alter) the state file when running
9760 --list-fingerprint or --verify-config or --hash-password. Resolves
9762 - When generating information telling us how to extend to a given
9763 router, do not try to include the nickname if it is
9764 absent. Resolves bug 467.
9765 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9766 a way to trigger this remotely.)
9767 - When sending a status event to the controller telling it that an
9768 OR address is reachable, set the port correctly. (Previously we
9769 were reporting the dir port.)
9770 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9771 command. Bugfix on 0.1.2.17.
9772 - When loading bandwidth history, do not believe any information in
9773 the future. Fixes bug 434.
9774 - When loading entry guard information, do not believe any information
9776 - When we have our clock set far in the future and generate an
9777 onion key, then re-set our clock to be correct, we should not stop
9778 the onion key from getting rotated.
9779 - On some platforms, accept() can return a broken address. Detect
9780 this more quietly, and deal accordingly. Fixes bug 483.
9781 - It's not actually an error to find a non-pending entry in the DNS
9782 cache when canceling a pending resolve. Don't log unless stuff
9783 is fishy. Resolves bug 463.
9784 - Don't reset trusted dir server list when we set a configuration
9785 option. Patch from Robert Hogan.
9786 - Don't try to create the datadir when running --verify-config or
9787 --hash-password. Resolves bug 540.
9790 Changes in version 0.2.0.9-alpha - 2007-10-24
9791 This ninth development snapshot switches clients to the new v3 directory
9792 system; allows servers to be listed in the network status even when they
9793 have the same nickname as a registered server; and fixes many other
9794 bugs including a big one that was causing some servers to disappear
9795 from the network status lists for a few hours each day.
9797 o Major features (directory system):
9798 - Clients now download v3 consensus networkstatus documents instead
9799 of v2 networkstatus documents. Clients and caches now base their
9800 opinions about routers on these consensus documents. Clients only
9801 download router descriptors listed in the consensus.
9802 - Authorities now list servers who have the same nickname as
9803 a different named server, but list them with a new flag,
9804 "Unnamed". Now we can list servers that happen to pick the same
9805 nickname as a server that registered two years ago and then
9806 disappeared. Partially implements proposal 122.
9807 - If the consensus lists a router as "Unnamed", the name is assigned
9808 to a different router: do not identify the router by that name.
9809 Partially implements proposal 122.
9810 - Authorities can now come to a consensus on which method to use to
9811 compute the consensus. This gives us forward compatibility.
9814 - Stop publishing a new server descriptor just because we HUP or
9815 when we find our DirPort to be reachable but won't actually publish
9816 it. New descriptors without any real changes are dropped by the
9817 authorities, and can screw up our "publish every 18 hours" schedule.
9819 - When a router wasn't listed in a new networkstatus, we were leaving
9820 the flags for that router alone -- meaning it remained Named,
9821 Running, etc -- even though absence from the networkstatus means
9822 that it shouldn't be considered to exist at all anymore. Now we
9823 clear all the flags for routers that fall out of the networkstatus
9824 consensus. Fixes bug 529; bugfix on 0.1.2.x.
9825 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
9826 extrainfo documents and then discard them immediately for not
9827 matching the latest router. Bugfix on 0.2.0.1-alpha.
9829 o Minor features (v3 directory protocol):
9830 - Allow tor-gencert to generate a new certificate without replacing
9832 - Allow certificates to include an address.
9833 - When we change our directory-cache settings, reschedule all voting
9834 and download operations.
9835 - Reattempt certificate downloads immediately on failure, as long as
9836 we haven't failed a threshold number of times yet.
9837 - Delay retrying consensus downloads while we're downloading
9838 certificates to verify the one we just got. Also, count getting a
9839 consensus that we already have (or one that isn't valid) as a failure,
9840 and count failing to get the certificates after 20 minutes as a
9842 - Build circuits and download descriptors even if our consensus is a
9843 little expired. (This feature will go away once authorities are
9846 o Minor features (router descriptor cache):
9847 - If we find a cached-routers file that's been sitting around for more
9848 than 28 days unmodified, then most likely it's a leftover from
9849 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
9851 - When we (as a cache) download a descriptor because it was listed
9852 in a consensus, remember when the consensus was supposed to expire,
9853 and don't expire the descriptor until then.
9855 o Minor features (performance):
9856 - Call routerlist_remove_old_routers() much less often. This should
9857 speed startup, especially on directory caches.
9858 - Don't try to launch new descriptor downloads quite so often when we
9859 already have enough directory information to build circuits.
9860 - Base64 decoding was actually showing up on our profile when parsing
9861 the initial descriptor file; switch to an in-process all-at-once
9862 implementation that's about 3.5x times faster than calling out to
9865 o Minor features (compilation):
9866 - Detect non-ASCII platforms (if any still exist) and refuse to
9867 build there: some of our code assumes that 'A' is 65 and so on.
9869 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
9870 - Make the "next period" votes into "current period" votes immediately
9871 after publishing the consensus; avoid a heisenbug that made them
9872 stick around indefinitely.
9873 - When we discard a vote as a duplicate, do not report this as
9875 - Treat missing v3 keys or certificates as an error when running as a
9876 v3 directory authority.
9877 - When we're configured to be a v3 authority, but we're only listed
9878 as a non-v3 authority in our DirServer line for ourself, correct
9880 - If an authority doesn't have a qualified hostname, just put
9881 its address in the vote. This fixes the problem where we referred to
9882 "moria on moria:9031."
9883 - Distinguish between detached signatures for the wrong period, and
9884 detached signatures for a divergent vote.
9885 - Fix a small memory leak when computing a consensus.
9886 - When there's no concensus, we were forming a vote every 30
9887 minutes, but writing the "valid-after" line in our vote based
9888 on our configured V3AuthVotingInterval: so unless the intervals
9889 matched up, we immediately rejected our own vote because it didn't
9890 start at the voting interval that caused us to construct a vote.
9892 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
9893 - Delete unverified-consensus when the real consensus is set.
9894 - Consider retrying a consensus networkstatus fetch immediately
9895 after one fails: don't wait 60 seconds to notice.
9896 - When fetching a consensus as a cache, wait until a newer consensus
9897 should exist before trying to replace the current one.
9898 - Use a more forgiving schedule for retrying failed consensus
9899 downloads than for other types.
9901 o Minor bugfixes (other directory issues):
9902 - Correct the implementation of "download votes by digest." Bugfix on
9904 - Authorities no longer send back "400 you're unreachable please fix
9905 it" errors to Tor servers that aren't online all the time. We're
9906 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
9908 o Minor bugfixes (controller):
9909 - Don't reset trusted dir server list when we set a configuration
9910 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
9911 - Respond to INT and TERM SIGNAL commands before we execute the
9912 signal, in case the signal shuts us down. We had a patch in
9913 0.1.2.1-alpha that tried to do this by queueing the response on
9914 the connection's buffer before shutting down, but that really
9915 isn't the same thing at all. Bug located by Matt Edman.
9917 o Minor bugfixes (misc):
9918 - Correctly check for bad options to the "PublishServerDescriptor"
9919 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
9920 - Stop leaking memory on failing case of base32_decode, and make
9921 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
9922 - Don't try to download extrainfo documents when we're trying to
9923 fetch enough directory info to build a circuit: having enough
9924 info should get priority. Bugfix on 0.2.0.x.
9925 - Don't complain that "your server has not managed to confirm that its
9926 ports are reachable" if we haven't been able to build any circuits
9927 yet. Bug found by spending four hours without a v3 consensus. Bugfix
9929 - Detect the reason for failing to mmap a descriptor file we just
9930 wrote, and give a more useful log message. Fixes bug 533. Bugfix
9933 o Code simplifications and refactoring:
9934 - Remove support for the old bw_accounting file: we've been storing
9935 bandwidth accounting information in the state file since
9936 0.1.2.5-alpha. This may result in bandwidth accounting errors
9937 if you try to upgrade from 0.1.1.x or earlier, or if you try to
9938 downgrade to 0.1.1.x or earlier.
9939 - New convenience code to locate a file within the DataDirectory.
9940 - Move non-authority functionality out of dirvote.c.
9941 - Refactor the arguments for router_pick_{directory_|trusteddir}server
9942 so that they all take the same named flags.
9945 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
9946 Unix users an easy way to script their Tor process (e.g. by
9947 adjusting bandwidth based on the time of the day).
9950 Changes in version 0.2.0.8-alpha - 2007-10-12
9951 This eighth development snapshot fixes a crash bug that's been bothering
9952 us since February 2007, lets bridge authorities store a list of bridge
9953 descriptors they've seen, gets v3 directory voting closer to working,
9954 starts caching v3 directory consensus documents on directory mirrors,
9955 and fixes a variety of smaller issues including some minor memory leaks.
9957 o Major features (router descriptor cache):
9958 - Store routers in a file called cached-descriptors instead of in
9959 cached-routers. Initialize cached-descriptors from cached-routers
9960 if the old format is around. The new format allows us to store
9961 annotations along with descriptors.
9962 - Use annotations to record the time we received each descriptor, its
9963 source, and its purpose.
9964 - Disable the SETROUTERPURPOSE controller command: it is now
9966 - Controllers should now specify cache=no or cache=yes when using
9967 the +POSTDESCRIPTOR command.
9968 - Bridge authorities now write bridge descriptors to disk, meaning
9969 we can export them to other programs and begin distributing them
9972 o Major features (directory authorities):
9973 - When a v3 authority is missing votes or signatures, it now tries
9975 - Directory authorities track weighted fractional uptime as well as
9976 weighted mean-time-between failures. WFU is suitable for deciding
9977 whether a node is "usually up", while MTBF is suitable for deciding
9978 whether a node is "likely to stay up." We need both, because
9979 "usually up" is a good requirement for guards, while "likely to
9980 stay up" is a good requirement for long-lived connections.
9982 o Major features (v3 directory system):
9983 - Caches now download v3 network status documents as needed,
9984 and download the descriptors listed in them.
9985 - All hosts now attempt to download and keep fresh v3 authority
9986 certificates, and re-attempt after failures.
9987 - More internal-consistency checks for vote parsing.
9989 o Major bugfixes (crashes):
9990 - If a connection is shut down abruptly because of something that
9991 happened inside connection_flushed_some(), do not call
9992 connection_finished_flushing(). Should fix bug 451. Bugfix on
9995 o Major bugfixes (performance):
9996 - Fix really bad O(n^2) performance when parsing a long list of
9997 routers: Instead of searching the entire list for an "extra-info "
9998 string which usually wasn't there, once for every routerinfo
9999 we read, just scan lines forward until we find one we like.
10001 - When we add data to a write buffer in response to the data on that
10002 write buffer getting low because of a flush, do not consider the
10003 newly added data as a candidate for immediate flushing, but rather
10004 make it wait until the next round of writing. Otherwise, we flush
10005 and refill recursively, and a single greedy TLS connection can
10006 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10008 o Minor features (v3 authority system):
10009 - Add more ways for tools to download the votes that lead to the
10011 - Send a 503 when low on bandwidth and a vote, consensus, or
10012 certificate is requested.
10013 - If-modified-since is now implemented properly for all kinds of
10014 certificate requests.
10016 o Minor bugfixes (network statuses):
10017 - Tweak the implementation of proposal 109 slightly: allow at most
10018 two Tor servers on the same IP address, except if it's the location
10019 of a directory authority, in which case allow five. Bugfix on
10022 o Minor bugfixes (controller):
10023 - When sending a status event to the controller telling it that an
10024 OR address is reachable, set the port correctly. (Previously we
10025 were reporting the dir port.) Bugfix on 0.1.2.x.
10027 o Minor bugfixes (v3 directory system):
10028 - Fix logic to look up a cert by its signing key digest. Bugfix on
10030 - Only change the reply to a vote to "OK" if it's not already
10031 set. This gets rid of annoying "400 OK" log messages, which may
10032 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10033 - When we get a valid consensus, recompute the voting schedule.
10034 - Base the valid-after time of a vote on the consensus voting
10035 schedule, not on our preferred schedule.
10036 - Make the return values and messages from signature uploads and
10037 downloads more sensible.
10038 - Fix a memory leak when serving votes and consensus documents, and
10039 another when serving certificates.
10041 o Minor bugfixes (performance):
10042 - Use a slightly simpler string hashing algorithm (copying Python's
10043 instead of Java's) and optimize our digest hashing algorithm to take
10044 advantage of 64-bit platforms and to remove some possibly-costly
10046 - Fix a minor memory leak whenever we parse guards from our state
10047 file. Bugfix on 0.2.0.7-alpha.
10048 - Fix a minor memory leak whenever we write out a file. Bugfix on
10050 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10051 command. Bugfix on 0.2.0.5-alpha.
10053 o Minor bugfixes (portability):
10054 - On some platforms, accept() can return a broken address. Detect
10055 this more quietly, and deal accordingly. Fixes bug 483.
10056 - Stop calling tor_strlower() on uninitialized memory in some cases.
10057 Bugfix in 0.2.0.7-alpha.
10059 o Minor bugfixes (usability):
10060 - Treat some 403 responses from directory servers as INFO rather than
10061 WARN-severity events.
10062 - It's not actually an error to find a non-pending entry in the DNS
10063 cache when canceling a pending resolve. Don't log unless stuff is
10064 fishy. Resolves bug 463.
10066 o Minor bugfixes (anonymity):
10067 - Never report that we've used more bandwidth than we're willing to
10068 relay: it leaks how much non-relay traffic we're using. Resolves
10070 - When looking for a circuit to cannibalize, consider family as well
10071 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10072 circuit cannibalization).
10074 o Code simplifications and refactoring:
10075 - Make a bunch of functions static. Remove some dead code.
10076 - Pull out about a third of the really big routerlist.c; put it in a
10077 new module, networkstatus.c.
10078 - Merge the extra fields in local_routerstatus_t back into
10079 routerstatus_t: we used to need one routerstatus_t for each
10080 authority's opinion, plus a local_routerstatus_t for the locally
10081 computed consensus opinion. To save space, we put the locally
10082 modified fields into local_routerstatus_t, and only the common
10083 stuff into routerstatus_t. But once v3 directories are in use,
10084 clients and caches will no longer need to hold authority opinions;
10085 thus, the rationale for keeping the types separate is now gone.
10086 - Make the code used to reschedule and reattempt downloads more
10088 - Turn all 'Are we a directory server/mirror?' logic into a call to
10090 - Remove the code to generate the oldest (v1) directory format.
10091 The code has been disabled since 0.2.0.5-alpha.
10094 Changes in version 0.2.0.7-alpha - 2007-09-21
10095 This seventh development snapshot makes bridges work again, makes bridge
10096 authorities work for the first time, fixes two huge performance flaws
10097 in hidden services, and fixes a variety of minor issues.
10099 o New directory authorities:
10100 - Set up moria1 and tor26 as the first v3 directory authorities. See
10101 doc/spec/dir-spec.txt for details on the new directory design.
10103 o Major bugfixes (crashes):
10104 - Fix possible segfaults in functions called from
10105 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10107 o Major bugfixes (bridges):
10108 - Fix a bug that made servers send a "404 Not found" in response to
10109 attempts to fetch their server descriptor. This caused Tor servers
10110 to take many minutes to establish reachability for their DirPort,
10111 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10112 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10113 users configure that and specify a bridge with an identity
10114 fingerprint, now they will lookup the bridge descriptor at the
10115 default bridge authority via a one-hop tunnel, but once circuits
10116 are established they will switch to a three-hop tunnel for later
10117 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10119 o Major bugfixes (hidden services):
10120 - Hidden services were choosing introduction points uniquely by
10121 hexdigest, but when constructing the hidden service descriptor
10122 they merely wrote the (potentially ambiguous) nickname.
10123 - Clients now use the v2 intro format for hidden service
10124 connections: they specify their chosen rendezvous point by identity
10125 digest rather than by (potentially ambiguous) nickname. Both
10126 are bugfixes on 0.1.2.x, and they could speed up hidden service
10127 connections dramatically. Thanks to Karsten Loesing.
10129 o Minor features (security):
10130 - As a client, do not believe any server that tells us that an
10131 address maps to an internal address space.
10132 - Make it possible to enable HashedControlPassword and
10133 CookieAuthentication at the same time.
10135 o Minor features (guard nodes):
10136 - Tag every guard node in our state file with the version that
10137 we believe added it, or with our own version if we add it. This way,
10138 if a user temporarily runs an old version of Tor and then switches
10139 back to a new one, she doesn't automatically lose her guards.
10141 o Minor features (speed):
10142 - When implementing AES counter mode, update only the portions of the
10143 counter buffer that need to change, and don't keep separate
10144 network-order and host-order counters when they are the same (i.e.,
10145 on big-endian hosts.)
10147 o Minor features (controller):
10148 - Accept LF instead of CRLF on controller, since some software has a
10149 hard time generating real Internet newlines.
10150 - Add GETINFO values for the server status events
10151 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10154 o Removed features:
10155 - Routers no longer include bandwidth-history lines in their
10156 descriptors; this information is already available in extra-info
10157 documents, and including it in router descriptors took up 60%
10158 (!) of compressed router descriptor downloads. Completes
10159 implementation of proposal 104.
10160 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10161 and TorControl.py, as they use the old v0 controller protocol,
10162 and are obsoleted by TorFlow anyway.
10163 - Drop support for v1 rendezvous descriptors, since we never used
10164 them anyway, and the code has probably rotted by now. Based on
10165 patch from Karsten Loesing.
10166 - On OSX, stop warning the user that kqueue support in libevent is
10167 "experimental", since it seems to have worked fine for ages.
10170 - When generating information telling us how to extend to a given
10171 router, do not try to include the nickname if it is absent. Fixes
10172 bug 467. Bugfix on 0.2.0.3-alpha.
10173 - Fix a user-triggerable (but not remotely-triggerable) segfault
10174 in expand_filename(). Bugfix on 0.1.2.x.
10175 - Fix a memory leak when freeing incomplete requests from DNSPort.
10176 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10177 - Don't try to access (or alter) the state file when running
10178 --list-fingerprint or --verify-config or --hash-password. (Resolves
10179 bug 499.) Bugfix on 0.1.2.x.
10180 - Servers used to decline to publish their DirPort if their
10181 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10182 were below a threshold. Now they only look at BandwidthRate and
10183 RelayBandwidthRate. Bugfix on 0.1.2.x.
10184 - Remove an optimization in the AES counter-mode code that assumed
10185 that the counter never exceeded 2^68. When the counter can be set
10186 arbitrarily as an IV (as it is by Karsten's new hidden services
10187 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10188 - Resume listing "AUTHORITY" flag for authorities in network status.
10189 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10191 o Code simplifications and refactoring:
10192 - Revamp file-writing logic so we don't need to have the entire
10193 contents of a file in memory at once before we write to disk. Tor,
10195 - Turn "descriptor store" into a full-fledged type.
10196 - Move all NT services code into a separate source file.
10197 - Unify all code that computes medians, percentile elements, etc.
10198 - Get rid of a needless malloc when parsing address policies.
10201 Changes in version 0.1.2.17 - 2007-08-30
10202 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10203 X bundles. Vidalia 0.0.14 makes authentication required for the
10204 ControlPort in the default configuration, which addresses important
10205 security risks. Everybody who uses Vidalia (or another controller)
10208 In addition, this Tor update fixes major load balancing problems with
10209 path selection, which should speed things up a lot once many people
10212 o Major bugfixes (security):
10213 - We removed support for the old (v0) control protocol. It has been
10214 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10215 become more of a headache than it's worth.
10217 o Major bugfixes (load balancing):
10218 - When choosing nodes for non-guard positions, weight guards
10219 proportionally less, since they already have enough load. Patch
10221 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10222 will allow fast Tor servers to get more attention.
10223 - When we're upgrading from an old Tor version, forget our current
10224 guards and pick new ones according to the new weightings. These
10225 three load balancing patches could raise effective network capacity
10226 by a factor of four. Thanks to Mike Perry for measurements.
10228 o Major bugfixes (stream expiration):
10229 - Expire not-yet-successful application streams in all cases if
10230 they've been around longer than SocksTimeout. Right now there are
10231 some cases where the stream will live forever, demanding a new
10232 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10234 o Minor features (controller):
10235 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10236 is valid before any authentication has been received. It tells
10237 a controller what kind of authentication is expected, and what
10238 protocol is spoken. Implements proposal 119.
10240 o Minor bugfixes (performance):
10241 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10242 greatly speeding up loading cached-routers from disk on startup.
10243 - Disable sentinel-based debugging for buffer code: we squashed all
10244 the bugs that this was supposed to detect a long time ago, and now
10245 its only effect is to change our buffer sizes from nice powers of
10246 two (which platform mallocs tend to like) to values slightly over
10247 powers of two (which make some platform mallocs sad).
10249 o Minor bugfixes (misc):
10250 - If exit bandwidth ever exceeds one third of total bandwidth, then
10251 use the correct formula to weight exit nodes when choosing paths.
10252 Based on patch from Mike Perry.
10253 - Choose perfectly fairly among routers when choosing by bandwidth and
10254 weighting by fraction of bandwidth provided by exits. Previously, we
10255 would choose with only approximate fairness, and correct ourselves
10256 if we ran off the end of the list.
10257 - If we require CookieAuthentication but we fail to write the
10258 cookie file, we would warn but not exit, and end up in a state
10259 where no controller could authenticate. Now we exit.
10260 - If we require CookieAuthentication, stop generating a new cookie
10261 every time we change any piece of our config.
10262 - Refuse to start with certain directory authority keys, and
10263 encourage people using them to stop.
10264 - Terminate multi-line control events properly. Original patch
10266 - Fix a minor memory leak when we fail to find enough suitable
10267 servers to choose a circuit.
10268 - Stop leaking part of the descriptor when we run into a particularly
10269 unparseable piece of it.
10272 Changes in version 0.2.0.6-alpha - 2007-08-26
10273 This sixth development snapshot features a new Vidalia version in the
10274 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10275 the ControlPort in the default configuration, which addresses important
10278 In addition, this snapshot fixes major load balancing problems
10279 with path selection, which should speed things up a lot once many
10280 people have upgraded. The directory authorities also use a new
10281 mean-time-between-failure approach to tracking which servers are stable,
10282 rather than just looking at the most recent uptime.
10284 o New directory authorities:
10285 - Set up Tonga as the default bridge directory authority.
10288 - Directory authorities now track servers by weighted
10289 mean-times-between-failures. When we have 4 or more days of data,
10290 use measured MTBF rather than declared uptime to decide whether
10291 to call a router Stable. Implements proposal 108.
10293 o Major bugfixes (load balancing):
10294 - When choosing nodes for non-guard positions, weight guards
10295 proportionally less, since they already have enough load. Patch
10297 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10298 will allow fast Tor servers to get more attention.
10299 - When we're upgrading from an old Tor version, forget our current
10300 guards and pick new ones according to the new weightings. These
10301 three load balancing patches could raise effective network capacity
10302 by a factor of four. Thanks to Mike Perry for measurements.
10304 o Major bugfixes (descriptor parsing):
10305 - Handle unexpected whitespace better in malformed descriptors. Bug
10306 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10309 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10310 GETINFO for Torstat to use until it can switch to using extrainfos.
10311 - Optionally (if built with -DEXPORTMALLINFO) export the output
10312 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10316 - Do not intermix bridge routers with controller-added
10317 routers. (Bugfix on 0.2.0.x)
10318 - Do not fail with an assert when accept() returns an unexpected
10319 address family. Addresses but does not wholly fix bug 483. (Bugfix
10321 - Let directory authorities startup even when they can't generate
10322 a descriptor immediately, e.g. because they don't know their
10324 - Stop putting the authentication cookie in a file called "0"
10325 in your working directory if you don't specify anything for the
10326 new CookieAuthFile option. Reported by Matt Edman.
10327 - Make it possible to read the PROTOCOLINFO response in a way that
10328 conforms to our control-spec. Reported by Matt Edman.
10329 - Fix a minor memory leak when we fail to find enough suitable
10330 servers to choose a circuit. Bugfix on 0.1.2.x.
10331 - Stop leaking part of the descriptor when we run into a particularly
10332 unparseable piece of it. Bugfix on 0.1.2.x.
10333 - Unmap the extrainfo cache file on exit.
10336 Changes in version 0.2.0.5-alpha - 2007-08-19
10337 This fifth development snapshot fixes compilation on Windows again;
10338 fixes an obnoxious client-side bug that slowed things down and put
10339 extra load on the network; gets us closer to using the v3 directory
10340 voting scheme; makes it easier for Tor controllers to use cookie-based
10341 authentication; and fixes a variety of other bugs.
10343 o Removed features:
10344 - Version 1 directories are no longer generated in full. Instead,
10345 authorities generate and serve "stub" v1 directories that list
10346 no servers. This will stop Tor versions 0.1.0.x and earlier from
10347 working, but (for security reasons) nobody should be running those
10350 o Major bugfixes (compilation, 0.2.0.x):
10351 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10352 - Try to fix MSVC compilation: build correctly on platforms that do
10353 not define s6_addr16 or s6_addr32.
10354 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10357 o Major bugfixes (stream expiration):
10358 - Expire not-yet-successful application streams in all cases if
10359 they've been around longer than SocksTimeout. Right now there are
10360 some cases where the stream will live forever, demanding a new
10361 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10362 reported by lodger.
10364 o Minor features (directory servers):
10365 - When somebody requests a list of statuses or servers, and we have
10366 none of those, return a 404 rather than an empty 200.
10368 o Minor features (directory voting):
10369 - Store v3 consensus status consensuses on disk, and reload them
10372 o Minor features (security):
10373 - Warn about unsafe ControlPort configurations.
10374 - Refuse to start with certain directory authority keys, and
10375 encourage people using them to stop.
10377 o Minor features (controller):
10378 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10379 is valid before any authentication has been received. It tells
10380 a controller what kind of authentication is expected, and what
10381 protocol is spoken. Implements proposal 119.
10382 - New config option CookieAuthFile to choose a new location for the
10383 cookie authentication file, and config option
10384 CookieAuthFileGroupReadable to make it group-readable.
10386 o Minor features (unit testing):
10387 - Add command-line arguments to unit-test executable so that we can
10388 invoke any chosen test from the command line rather than having
10389 to run the whole test suite at once; and so that we can turn on
10390 logging for the unit tests.
10392 o Minor bugfixes (on 0.1.2.x):
10393 - If we require CookieAuthentication but we fail to write the
10394 cookie file, we would warn but not exit, and end up in a state
10395 where no controller could authenticate. Now we exit.
10396 - If we require CookieAuthentication, stop generating a new cookie
10397 every time we change any piece of our config.
10398 - When loading bandwidth history, do not believe any information in
10399 the future. Fixes bug 434.
10400 - When loading entry guard information, do not believe any information
10402 - When we have our clock set far in the future and generate an
10403 onion key, then re-set our clock to be correct, we should not stop
10404 the onion key from getting rotated.
10405 - Clean up torrc sample config file.
10406 - Do not automatically run configure from autogen.sh. This
10407 non-standard behavior tended to annoy people who have built other
10410 o Minor bugfixes (on 0.2.0.x):
10411 - Fix a bug with AutomapHostsOnResolve that would always cause
10412 the second request to fail. Bug reported by Kate. Bugfix on
10414 - Fix a bug in ADDRMAP controller replies that would sometimes
10415 try to print a NULL. Patch from tup.
10416 - Read v3 directory authority keys from the right location.
10417 - Numerous bugfixes to directory voting code.
10420 Changes in version 0.1.2.16 - 2007-08-01
10421 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10422 remote attacker in certain situations to rewrite the user's torrc
10423 configuration file. This can completely compromise anonymity of users
10424 in most configurations, including those running the Vidalia bundles,
10425 TorK, etc. Or worse.
10427 o Major security fixes:
10428 - Close immediately after missing authentication on control port;
10429 do not allow multiple authentication attempts.
10432 Changes in version 0.2.0.4-alpha - 2007-08-01
10433 This fourth development snapshot fixes a critical security vulnerability
10434 for most users, specifically those running Vidalia, TorK, etc. Everybody
10435 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10437 o Major security fixes:
10438 - Close immediately after missing authentication on control port;
10439 do not allow multiple authentication attempts.
10441 o Major bugfixes (compilation):
10442 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10445 o Minor features (performance):
10446 - Be even more aggressive about releasing RAM from small
10447 empty buffers. Thanks to our free-list code, this shouldn't be too
10448 performance-intensive.
10449 - Disable sentinel-based debugging for buffer code: we squashed all
10450 the bugs that this was supposed to detect a long time ago, and
10451 now its only effect is to change our buffer sizes from nice
10452 powers of two (which platform mallocs tend to like) to values
10453 slightly over powers of two (which make some platform mallocs sad).
10454 - Log malloc statistics from mallinfo() on platforms where it
10458 Changes in version 0.2.0.3-alpha - 2007-07-29
10459 This third development snapshot introduces new experimental
10460 blocking-resistance features and a preliminary version of the v3
10461 directory voting design, and includes many other smaller features
10465 - The first pieces of our "bridge" design for blocking-resistance
10466 are implemented. People can run bridge directory authorities;
10467 people can run bridges; and people can configure their Tor clients
10468 with a set of bridges to use as the first hop into the Tor network.
10469 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10471 - Create listener connections before we setuid to the configured
10472 User and Group. Now non-Windows users can choose port values
10473 under 1024, start Tor as root, and have Tor bind those ports
10474 before it changes to another UID. (Windows users could already
10476 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10477 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10478 on "vserver" accounts. (Patch from coderman.)
10479 - Be even more aggressive about separating local traffic from relayed
10480 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10482 o Major features (experimental):
10483 - First cut of code for "v3 dir voting": directory authorities will
10484 vote on a common network status document rather than each publishing
10485 their own opinion. This code needs more testing and more corner-case
10486 handling before it's ready for use.
10489 - Directory authorities now call routers Fast if their bandwidth is
10490 at least 100KB/s, and consider their bandwidth adequate to be a
10491 Guard if it is at least 250KB/s, no matter the medians. This fix
10492 complements proposal 107. [Bugfix on 0.1.2.x]
10493 - Directory authorities now never mark more than 3 servers per IP as
10494 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10496 - Minor change to organizationName and commonName generation
10497 procedures in TLS certificates during Tor handshakes, to invalidate
10498 some earlier censorware approaches. This is not a long-term
10499 solution, but applying it will give us a bit of time to look into
10500 the epidemiology of countermeasures as they spread.
10502 o Major bugfixes (directory):
10503 - Rewrite directory tokenization code to never run off the end of
10504 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10506 o Minor features (controller):
10507 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10508 match requests to applications. (Patch from Robert Hogan.)
10509 - Report address and port correctly on connections to DNSPort. (Patch
10510 from Robert Hogan.)
10511 - Add a RESOLVE command to launch hostname lookups. (Original patch
10512 from Robert Hogan.)
10513 - Add GETINFO status/enough-dir-info to let controllers tell whether
10514 Tor has downloaded sufficient directory information. (Patch
10516 - You can now use the ControlSocket option to tell Tor to listen for
10517 controller connections on Unix domain sockets on systems that
10518 support them. (Patch from Peter Palfrader.)
10519 - STREAM NEW events are generated for DNSPort requests and for
10520 tunneled directory connections. (Patch from Robert Hogan.)
10521 - New "GETINFO address-mappings/*" command to get address mappings
10522 with expiry information. "addr-mappings/*" is now deprecated.
10525 o Minor features (misc):
10526 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10528 - The tor-gencert tool for v3 directory authorities now creates all
10529 files as readable to the file creator only, and write-protects
10530 the authority identity key.
10531 - When dumping memory usage, list bytes used in buffer memory
10533 - When running with dmalloc, dump more stats on hup and on exit.
10534 - Directory authorities now fail quickly and (relatively) harmlessly
10535 if they generate a network status document that is somehow
10538 o Traffic load balancing improvements:
10539 - If exit bandwidth ever exceeds one third of total bandwidth, then
10540 use the correct formula to weight exit nodes when choosing paths.
10541 (Based on patch from Mike Perry.)
10542 - Choose perfectly fairly among routers when choosing by bandwidth and
10543 weighting by fraction of bandwidth provided by exits. Previously, we
10544 would choose with only approximate fairness, and correct ourselves
10545 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10547 o Performance improvements:
10548 - Be more aggressive with freeing buffer RAM or putting it on the
10550 - Use Critical Sections rather than Mutexes for synchronizing threads
10551 on win32; Mutexes are heavier-weight, and designed for synchronizing
10554 o Deprecated and removed features:
10555 - RedirectExits is now deprecated.
10556 - Stop allowing address masks that do not correspond to bit prefixes.
10557 We have warned about these for a really long time; now it's time
10558 to reject them. (Patch from croup.)
10560 o Minor bugfixes (directory):
10561 - Fix another crash bug related to extra-info caching. (Bug found by
10562 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10563 - Directories no longer return a "304 not modified" when they don't
10564 have the networkstatus the client asked for. Also fix a memory
10565 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10566 - We had accidentally labelled 0.1.2.x directory servers as not
10567 suitable for begin_dir requests, and had labelled no directory
10568 servers as suitable for uploading extra-info documents. [Bugfix
10571 o Minor bugfixes (dns):
10572 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10573 Hogan.) [Bugfix on 0.2.0.2-alpha]
10574 - Add DNSPort connections to the global connection list, so that we
10575 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10577 - Fix a dangling reference that could lead to a crash when DNSPort is
10578 changed or closed (Patch from Robert Hogan.) [Bugfix on
10581 o Minor bugfixes (controller):
10582 - Provide DNS expiry times in GMT, not in local time. For backward
10583 compatibility, ADDRMAP events only provide GMT expiry in an extended
10584 field. "GETINFO address-mappings" always does the right thing.
10585 - Use CRLF line endings properly in NS events.
10586 - Terminate multi-line control events properly. (Original patch
10587 from tup.) [Bugfix on 0.1.2.x-alpha]
10588 - Do not include spaces in SOURCE_ADDR fields in STREAM
10589 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10592 Changes in version 0.1.2.15 - 2007-07-17
10593 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10594 problems, fixes compilation on BSD, and fixes a variety of other
10595 bugs. Everybody should upgrade.
10597 o Major bugfixes (compilation):
10598 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10600 o Major bugfixes (crashes):
10601 - Try even harder not to dereference the first character after
10602 an mmap(). Reported by lodger.
10603 - Fix a crash bug in directory authorities when we re-number the
10604 routerlist while inserting a new router.
10605 - When the cached-routers file is an even multiple of the page size,
10606 don't run off the end and crash. (Fixes bug 455; based on idea
10608 - Fix eventdns.c behavior on Solaris: It is critical to include
10609 orconfig.h _before_ sys/types.h, so that we can get the expected
10610 definition of _FILE_OFFSET_BITS.
10612 o Major bugfixes (security):
10613 - Fix a possible buffer overrun when using BSD natd support. Bug
10615 - When sending destroy cells from a circuit's origin, don't include
10616 the reason for tearing down the circuit. The spec says we didn't,
10617 and now we actually don't. Reported by lodger.
10618 - Keep streamids from different exits on a circuit separate. This
10619 bug may have allowed other routers on a given circuit to inject
10620 cells into streams. Reported by lodger; fixes bug 446.
10621 - If there's a never-before-connected-to guard node in our list,
10622 never choose any guards past it. This way we don't expand our
10623 guard list unless we need to.
10625 o Minor bugfixes (guard nodes):
10626 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10627 don't get overused as guards.
10629 o Minor bugfixes (directory):
10630 - Correctly count the number of authorities that recommend each
10631 version. Previously, we were under-counting by 1.
10632 - Fix a potential crash bug when we load many server descriptors at
10633 once and some of them make others of them obsolete. Fixes bug 458.
10635 o Minor bugfixes (hidden services):
10636 - Stop tearing down the whole circuit when the user asks for a
10637 connection to a port that the hidden service didn't configure.
10640 o Minor bugfixes (misc):
10641 - On Windows, we were preventing other processes from reading
10642 cached-routers while Tor was running. Reported by janbar.
10643 - Fix a possible (but very unlikely) bug in picking routers by
10644 bandwidth. Add a log message to confirm that it is in fact
10645 unlikely. Patch from lodger.
10646 - Backport a couple of memory leak fixes.
10647 - Backport miscellaneous cosmetic bugfixes.
10650 Changes in version 0.2.0.2-alpha - 2007-06-02
10651 o Major bugfixes on 0.2.0.1-alpha:
10652 - Fix an assertion failure related to servers without extra-info digests.
10653 Resolves bugs 441 and 442.
10655 o Minor features (directory):
10656 - Support "If-Modified-Since" when answering HTTP requests for
10657 directories, running-routers documents, and network-status documents.
10658 (There's no need to support it for router descriptors, since those
10659 are downloaded by descriptor digest.)
10661 o Minor build issues:
10662 - Clear up some MIPSPro compiler warnings.
10663 - When building from a tarball on a machine that happens to have SVK
10664 installed, report the micro-revision as whatever version existed
10665 in the tarball, not as "x".
10668 Changes in version 0.2.0.1-alpha - 2007-06-01
10669 This early development snapshot provides new features for people running
10670 Tor as both a client and a server (check out the new RelayBandwidth
10671 config options); lets Tor run as a DNS proxy; and generally moves us
10672 forward on a lot of fronts.
10674 o Major features, server usability:
10675 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10676 a separate set of token buckets for relayed traffic. Right now
10677 relayed traffic is defined as answers to directory requests, and
10678 OR connections that don't have any local circuits on them.
10680 o Major features, client usability:
10681 - A client-side DNS proxy feature to replace the need for
10682 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10683 for DNS requests on port 9999, use the Tor network to resolve them
10684 anonymously, and send the reply back like a regular DNS server.
10685 The code still only implements a subset of DNS.
10686 - Make PreferTunneledDirConns and TunnelDirConns work even when
10687 we have no cached directory info. This means Tor clients can now
10688 do all of their connections protected by TLS.
10690 o Major features, performance and efficiency:
10691 - Directory authorities accept and serve "extra info" documents for
10692 routers. These documents contain fields from router descriptors
10693 that aren't usually needed, and that use a lot of excess
10694 bandwidth. Once these fields are removed from router descriptors,
10695 the bandwidth savings should be about 60%. [Partially implements
10697 - Servers upload extra-info documents to any authority that accepts
10698 them. Authorities (and caches that have been configured to download
10699 extra-info documents) download them as needed. [Partially implements
10701 - Change the way that Tor buffers data that it is waiting to write.
10702 Instead of queueing data cells in an enormous ring buffer for each
10703 client->OR or OR->OR connection, we now queue cells on a separate
10704 queue for each circuit. This lets us use less slack memory, and
10705 will eventually let us be smarter about prioritizing different kinds
10707 - Use memory pools to allocate cells with better speed and memory
10708 efficiency, especially on platforms where malloc() is inefficient.
10709 - Stop reading on edge connections when their corresponding circuit
10710 buffers are full; start again as the circuits empty out.
10712 o Major features, other:
10713 - Add an HSAuthorityRecordStats option that hidden service authorities
10714 can use to track statistics of overall hidden service usage without
10715 logging information that would be very useful to an attacker.
10716 - Start work implementing multi-level keys for directory authorities:
10717 Add a standalone tool to generate key certificates. (Proposal 103.)
10720 - Directory authorities now call routers Stable if they have an
10721 uptime of at least 30 days, even if that's not the median uptime
10722 in the network. Implements proposal 107, suggested by Kevin Bauer
10725 o Minor fixes (resource management):
10726 - Count the number of open sockets separately from the number
10727 of active connection_t objects. This will let us avoid underusing
10728 our allocated connection limit.
10729 - We no longer use socket pairs to link an edge connection to an
10730 anonymous directory connection or a DirPort test connection.
10731 Instead, we track the link internally and transfer the data
10732 in-process. This saves two sockets per "linked" connection (at the
10733 client and at the server), and avoids the nasty Windows socketpair()
10735 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10736 for every single inactive connection_t. Free items from the
10737 4k/16k-buffer free lists when they haven't been used for a while.
10739 o Minor features (build):
10740 - Make autoconf search for libevent, openssl, and zlib consistently.
10741 - Update deprecated macros in configure.in.
10742 - When warning about missing headers, tell the user to let us
10743 know if the compile succeeds anyway, so we can downgrade the
10745 - Include the current subversion revision as part of the version
10746 string: either fetch it directly if we're in an SVN checkout, do
10747 some magic to guess it if we're in an SVK checkout, or use
10748 the last-detected version if we're building from a .tar.gz.
10749 Use this version consistently in log messages.
10751 o Minor features (logging):
10752 - Always prepend "Bug: " to any log message about a bug.
10753 - Put a platform string (e.g. "Linux i686") in the startup log
10754 message, so when people paste just their logs, we know if it's
10755 OpenBSD or Windows or what.
10756 - When logging memory usage, break down memory used in buffers by
10759 o Minor features (directory system):
10760 - New config option V2AuthoritativeDirectory that all directory
10761 authorities should set. This will let future authorities choose
10762 not to serve V2 directory information.
10763 - Directory authorities allow multiple router descriptors and/or extra
10764 info documents to be uploaded in a single go. This will make
10765 implementing proposal 104 simpler.
10767 o Minor features (controller):
10768 - Add a new config option __DisablePredictedCircuits designed for
10769 use by the controller, when we don't want Tor to build any circuits
10771 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10772 so we can exit from the middle of the circuit.
10773 - Implement "getinfo status/circuit-established".
10774 - Implement "getinfo status/version/..." so a controller can tell
10775 whether the current version is recommended, and whether any versions
10776 are good, and how many authorities agree. (Patch from shibz.)
10778 o Minor features (hidden services):
10779 - Allow multiple HiddenServicePort directives with the same virtual
10780 port; when they occur, the user is sent round-robin to one
10781 of the target ports chosen at random. Partially fixes bug 393 by
10782 adding limited ad-hoc round-robining.
10784 o Minor features (other):
10786 - Add a new AutomapHostsOnResolve option: when it is enabled, any
10787 resolve request for hosts matching a given pattern causes Tor to
10788 generate an internal virtual address mapping for that host. This
10789 allows DNSPort to work sensibly with hidden service users. By
10790 default, .exit and .onion addresses are remapped; the list of
10791 patterns can be reconfigured with AutomapHostsSuffixes.
10792 - Add an "-F" option to tor-resolve to force a resolve for a .onion
10793 address. Thanks to the AutomapHostsOnResolve option, this is no
10794 longer a completely silly thing to do.
10795 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
10796 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
10797 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
10798 minus 1 byte: the actual maximum declared bandwidth.
10800 o Removed features:
10801 - Removed support for the old binary "version 0" controller protocol.
10802 This has been deprecated since 0.1.1, and warnings have been issued
10803 since 0.1.2. When we encounter a v0 control message, we now send
10804 back an error and close the connection.
10805 - Remove the old "dns worker" server DNS code: it hasn't been default
10806 since 0.1.2.2-alpha, and all the servers seem to be using the new
10809 o Minor bugfixes (portability):
10810 - Even though Windows is equally happy with / and \ as path separators,
10811 try to use \ consistently on Windows and / consistently on Unix: it
10812 makes the log messages nicer.
10813 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
10814 - Read resolv.conf files correctly on platforms where read() returns
10815 partial results on small file reads.
10817 o Minor bugfixes (directory):
10818 - Correctly enforce that elements of directory objects do not appear
10819 more often than they are allowed to appear.
10820 - When we are reporting the DirServer line we just parsed, we were
10821 logging the second stanza of the key fingerprint, not the first.
10823 o Minor bugfixes (logging):
10824 - When we hit an EOF on a log (probably because we're shutting down),
10825 don't try to remove the log from the list: just mark it as
10826 unusable. (Bulletproofs against bug 222.)
10828 o Minor bugfixes (other):
10829 - In the exitlist script, only consider the most recently published
10830 server descriptor for each server. Also, when the user requests
10831 a list of servers that _reject_ connections to a given address,
10832 explicitly exclude the IPs that also have servers that accept
10833 connections to that address. (Resolves bug 405.)
10834 - Stop allowing hibernating servers to be "stable" or "fast".
10835 - On Windows, we were preventing other processes from reading
10836 cached-routers while Tor was running. (Reported by janbar)
10837 - Make the NodeFamilies config option work. (Reported by
10838 lodger -- it has never actually worked, even though we added it
10840 - Check return values from pthread_mutex functions.
10841 - Don't save non-general-purpose router descriptors to the disk cache,
10842 because we have no way of remembering what their purpose was when
10844 - Add even more asserts to hunt down bug 417.
10845 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
10846 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
10847 Add a log message to confirm that it is in fact unlikely.
10849 o Minor bugfixes (controller):
10850 - Make 'getinfo fingerprint' return a 551 error if we're not a
10851 server, so we match what the control spec claims we do. Reported
10853 - Fix a typo in an error message when extendcircuit fails that
10854 caused us to not follow the \r\n-based delimiter protocol. Reported
10857 o Code simplifications and refactoring:
10858 - Stop passing around circuit_t and crypt_path_t pointers that are
10859 implicit in other procedure arguments.
10860 - Drop the old code to choke directory connections when the
10861 corresponding OR connections got full: thanks to the cell queue
10862 feature, OR conns don't get full any more.
10863 - Make dns_resolve() handle attaching connections to circuits
10864 properly, so the caller doesn't have to.
10865 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
10866 - Keep the connection array as a dynamic smartlist_t, rather than as
10867 a fixed-sized array. This is important, as the number of connections
10868 is becoming increasingly decoupled from the number of sockets.
10871 Changes in version 0.1.2.14 - 2007-05-25
10872 Tor 0.1.2.14 changes the addresses of two directory authorities (this
10873 change especially affects those who serve or use hidden services),
10874 and fixes several other crash- and security-related bugs.
10876 o Directory authority changes:
10877 - Two directory authorities (moria1 and moria2) just moved to new
10878 IP addresses. This change will particularly affect those who serve
10879 or use hidden services.
10881 o Major bugfixes (crashes):
10882 - If a directory server runs out of space in the connection table
10883 as it's processing a begin_dir request, it will free the exit stream
10884 but leave it attached to the circuit, leading to unpredictable
10885 behavior. (Reported by seeess, fixes bug 425.)
10886 - Fix a bug in dirserv_remove_invalid() that would cause authorities
10887 to corrupt memory under some really unlikely scenarios.
10888 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
10889 - Avoid segfaults when reading from mmaped descriptor file. (Reported
10892 o Major bugfixes (security):
10893 - When choosing an entry guard for a circuit, avoid using guards
10894 that are in the same family as the chosen exit -- not just guards
10895 that are exactly the chosen exit. (Reported by lodger.)
10897 o Major bugfixes (resource management):
10898 - If a directory authority is down, skip it when deciding where to get
10899 networkstatus objects or descriptors. Otherwise we keep asking
10900 every 10 seconds forever. Fixes bug 384.
10901 - Count it as a failure if we fetch a valid network-status but we
10902 don't want to keep it. Otherwise we'll keep fetching it and keep
10903 not wanting to keep it. Fixes part of bug 422.
10904 - If all of our dirservers have given us bad or no networkstatuses
10905 lately, then stop hammering them once per minute even when we
10906 think they're failed. Fixes another part of bug 422.
10909 - Actually set the purpose correctly for descriptors inserted with
10910 purpose=controller.
10911 - When we have k non-v2 authorities in our DirServer config,
10912 we ignored the last k authorities in the list when updating our
10914 - Correctly back-off from requesting router descriptors that we are
10915 having a hard time downloading.
10916 - Read resolv.conf files correctly on platforms where read() returns
10917 partial results on small file reads.
10918 - Don't rebuild the entire router store every time we get 32K of
10919 routers: rebuild it when the journal gets very large, or when
10920 the gaps in the store get very large.
10923 - When routers publish SVN revisions in their router descriptors,
10924 authorities now include those versions correctly in networkstatus
10926 - Warn when using a version of libevent before 1.3b to run a server on
10927 OSX or BSD: these versions interact badly with userspace threads.
10930 Changes in version 0.1.2.13 - 2007-04-24
10931 This release features some major anonymity fixes, such as safer path
10932 selection; better client performance; faster bootstrapping, better
10933 address detection, and better DNS support for servers; write limiting as
10934 well as read limiting to make servers easier to run; and a huge pile of
10935 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
10937 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
10938 of the Freenode IRC network, remembering his patience and vision for
10939 free speech on the Internet.
10942 - Fix a memory leak when we ask for "all" networkstatuses and we
10943 get one we don't recognize.
10944 - Add more asserts to hunt down bug 417.
10945 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
10948 Changes in version 0.1.2.12-rc - 2007-03-16
10950 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
10951 directory information requested inside Tor connections (i.e. via
10952 begin_dir cells). It only triggered when the same connection was
10953 serving other data at the same time. Reported by seeess.
10956 - When creating a circuit via the controller, send a 'launched'
10957 event when we're done, so we follow the spec better.
10960 Changes in version 0.1.2.11-rc - 2007-03-15
10961 o Minor bugfixes (controller), reported by daejees:
10962 - Correct the control spec to match how the code actually responds
10963 to 'getinfo addr-mappings/*'.
10964 - The control spec described a GUARDS event, but the code
10965 implemented a GUARD event. Standardize on GUARD, but let people
10966 ask for GUARDS too.
10969 Changes in version 0.1.2.10-rc - 2007-03-07
10970 o Major bugfixes (Windows):
10971 - Do not load the NT services library functions (which may not exist)
10972 just to detect if we're a service trying to shut down. Now we run
10973 on Win98 and friends again.
10975 o Minor bugfixes (other):
10976 - Clarify a couple of log messages.
10977 - Fix a misleading socks5 error number.
10980 Changes in version 0.1.2.9-rc - 2007-03-02
10981 o Major bugfixes (Windows):
10982 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
10983 of the usual GCC "%llu". This prevents a bug when saving 64-bit
10984 int configuration values: the high-order 32 bits would get
10985 truncated. In particular, we were being bitten by the default
10986 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
10987 and maybe also bug 397.)
10989 o Minor bugfixes (performance):
10990 - Use OpenSSL's AES implementation on platforms where it's faster.
10991 This could save us as much as 10% CPU usage.
10993 o Minor bugfixes (server):
10994 - Do not rotate onion key immediately after setting it for the first
10997 o Minor bugfixes (directory authorities):
10998 - Stop calling servers that have been hibernating for a long time
10999 "stable". Also, stop letting hibernating or obsolete servers affect
11000 uptime and bandwidth cutoffs.
11001 - Stop listing hibernating servers in the v1 directory.
11003 o Minor bugfixes (hidden services):
11004 - Upload hidden service descriptors slightly less often, to reduce
11005 load on authorities.
11007 o Minor bugfixes (other):
11008 - Fix an assert that could trigger if a controller quickly set then
11009 cleared EntryNodes. Bug found by Udo van den Heuvel.
11010 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11012 - Fix a potential race condition in the rpm installer. Found by
11014 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11015 of 2 as indicating that the server is completely bad; it sometimes
11016 means that the server is just bad for the request in question. (may fix
11017 the last of bug 326.)
11018 - Disable encrypted directory connections when we don't have a server
11019 descriptor for the destination. We'll get this working again in
11023 Changes in version 0.1.2.8-beta - 2007-02-26
11024 o Major bugfixes (crashes):
11025 - Stop crashing when the controller asks us to resetconf more than
11026 one config option at once. (Vidalia 0.0.11 does this.)
11027 - Fix a crash that happened on Win98 when we're given command-line
11028 arguments: don't try to load NT service functions from advapi32.dll
11029 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11031 - Fix a longstanding obscure crash bug that could occur when
11032 we run out of DNS worker processes. (Resolves bug 390.)
11034 o Major bugfixes (hidden services):
11035 - Correctly detect whether hidden service descriptor downloads are
11036 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11038 o Major bugfixes (accounting):
11039 - When we start during an accounting interval before it's time to wake
11040 up, remember to wake up at the correct time. (May fix bug 342.)
11042 o Minor bugfixes (controller):
11043 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11044 clear the corresponding on_circuit variable, and remember later
11045 that we don't need to send a redundant CLOSED event. Resolves part
11047 - Report events where a resolve succeeded or where we got a socks
11048 protocol error correctly, rather than calling both of them
11050 - Change reported stream target addresses to IP consistently when
11051 we finally get the IP from an exit node.
11052 - Send log messages to the controller even if they happen to be very
11055 o Minor bugfixes (other):
11056 - Display correct results when reporting which versions are
11057 recommended, and how recommended they are. (Resolves bug 383.)
11058 - Improve our estimates for directory bandwidth to be less random:
11059 guess that an unrecognized directory will have the average bandwidth
11060 from all known directories, not that it will have the average
11061 bandwidth from those directories earlier than it on the list.
11062 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11063 and hup, stop triggering an assert based on an empty onion_key.
11064 - On platforms with no working mmap() equivalent, don't warn the
11065 user when cached-routers doesn't exist.
11066 - Warn the user when mmap() [or its equivalent] fails for some reason
11067 other than file-not-found.
11068 - Don't warn the user when cached-routers.new doesn't exist: that's
11069 perfectly fine when starting up for the first time.
11070 - When EntryNodes are configured, rebuild the guard list to contain,
11071 in order: the EntryNodes that were guards before; the rest of the
11072 EntryNodes; the nodes that were guards before.
11073 - Mask out all signals in sub-threads; only the libevent signal
11074 handler should be processing them. This should prevent some crashes
11075 on some machines using pthreads. (Patch from coderman.)
11076 - Fix switched arguments on memset in the implementation of
11077 tor_munmap() for systems with no mmap() call.
11078 - When Tor receives a router descriptor that it asked for, but
11079 no longer wants (because it has received fresh networkstatuses
11080 in the meantime), do not warn the user. Cache the descriptor if
11081 we're a cache; drop it if we aren't.
11082 - Make earlier entry guards _really_ get retried when the network
11084 - On a malformed DNS reply, always give an error to the corresponding
11086 - Build with recent libevents on platforms that do not define the
11087 nonstandard types "u_int8_t" and friends.
11089 o Minor features (controller):
11090 - Warn the user when an application uses the obsolete binary v0
11091 control protocol. We're planning to remove support for it during
11092 the next development series, so it's good to give people some
11094 - Add STREAM_BW events to report per-entry-stream bandwidth
11095 use. (Patch from Robert Hogan.)
11096 - Rate-limit SIGNEWNYM signals in response to controllers that
11097 impolitely generate them for every single stream. (Patch from
11098 mwenge; closes bug 394.)
11099 - Make REMAP stream events have a SOURCE (cache or exit), and
11100 make them generated in every case where we get a successful
11101 connected or resolved cell.
11103 o Minor bugfixes (performance):
11104 - Call router_have_min_dir_info half as often. (This is showing up in
11105 some profiles, but not others.)
11106 - When using GCC, make log_debug never get called at all, and its
11107 arguments never get evaluated, when no debug logs are configured.
11108 (This is showing up in some profiles, but not others.)
11111 - Remove some never-implemented options. Mark PathlenCoinWeight as
11113 - Implement proposal 106: Stop requiring clients to have well-formed
11114 certificates; stop checking nicknames in certificates. (Clients
11115 have certificates so that they can look like Tor servers, but in
11116 the future we might want to allow them to look like regular TLS
11117 clients instead. Nicknames in certificates serve no purpose other
11118 than making our protocol easier to recognize on the wire.)
11119 - Revise messages on handshake failure again to be even more clear about
11120 which are incoming connections and which are outgoing.
11121 - Discard any v1 directory info that's over 1 month old (for
11122 directories) or over 1 week old (for running-routers lists).
11123 - Do not warn when individual nodes in the configuration's EntryNodes,
11124 ExitNodes, etc are down: warn only when all possible nodes
11125 are down. (Fixes bug 348.)
11126 - Always remove expired routers and networkstatus docs before checking
11127 whether we have enough information to build circuits. (Fixes
11129 - Put a lower-bound on MaxAdvertisedBandwidth.
11132 Changes in version 0.1.2.7-alpha - 2007-02-06
11133 o Major bugfixes (rate limiting):
11134 - Servers decline directory requests much more aggressively when
11135 they're low on bandwidth. Otherwise they end up queueing more and
11136 more directory responses, which can't be good for latency.
11137 - But never refuse directory requests from local addresses.
11138 - Fix a memory leak when sending a 503 response for a networkstatus
11140 - Be willing to read or write on local connections (e.g. controller
11141 connections) even when the global rate limiting buckets are empty.
11142 - If our system clock jumps back in time, don't publish a negative
11143 uptime in the descriptor. Also, don't let the global rate limiting
11144 buckets go absurdly negative.
11145 - Flush local controller connection buffers periodically as we're
11146 writing to them, so we avoid queueing 4+ megabytes of data before
11149 o Major bugfixes (NT services):
11150 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11151 command-line flag so that admins can override the default by saying
11152 "tor --service install --user "SomeUser"". This will not affect
11153 existing installed services. Also, warn the user that the service
11154 will look for its configuration file in the service user's
11155 %appdata% directory. (We can't do the 'hardwire the user's appdata
11156 directory' trick any more, since we may not have read access to that
11159 o Major bugfixes (other):
11160 - Previously, we would cache up to 16 old networkstatus documents
11161 indefinitely, if they came from nontrusted authorities. Now we
11162 discard them if they are more than 10 days old.
11163 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11165 - Detect and reject malformed DNS responses containing circular
11167 - If exits are rare enough that we're not marking exits as guards,
11168 ignore exit bandwidth when we're deciding the required bandwidth
11170 - When we're handling a directory connection tunneled over Tor,
11171 don't fill up internal memory buffers with all the data we want
11172 to tunnel; instead, only add it if the OR connection that will
11173 eventually receive it has some room for it. (This can lead to
11174 slowdowns in tunneled dir connections; a better solution will have
11175 to wait for 0.2.0.)
11177 o Minor bugfixes (dns):
11178 - Add some defensive programming to eventdns.c in an attempt to catch
11179 possible memory-stomping bugs.
11180 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11181 an incorrect number of bytes. (Previously, we would ignore the
11183 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11184 in the correct order, and doesn't crash.
11185 - Free memory held in recently-completed DNS lookup attempts on exit.
11186 This was not a memory leak, but may have been hiding memory leaks.
11187 - Handle TTL values correctly on reverse DNS lookups.
11188 - Treat failure to parse resolv.conf as an error.
11190 o Minor bugfixes (other):
11191 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11192 - When computing clock skew from directory HTTP headers, consider what
11193 time it was when we finished asking for the directory, not what
11195 - Expire socks connections if they spend too long waiting for the
11196 handshake to finish. Previously we would let them sit around for
11197 days, if the connecting application didn't close them either.
11198 - And if the socks handshake hasn't started, don't send a
11199 "DNS resolve socks failed" handshake reply; just close it.
11200 - Stop using C functions that OpenBSD's linker doesn't like.
11201 - Don't launch requests for descriptors unless we have networkstatuses
11202 from at least half of the authorities. This delays the first
11203 download slightly under pathological circumstances, but can prevent
11204 us from downloading a bunch of descriptors we don't need.
11205 - Do not log IPs with TLS failures for incoming TLS
11206 connections. (Fixes bug 382.)
11207 - If the user asks to use invalid exit nodes, be willing to use
11209 - Stop using the reserved ac_cv namespace in our configure script.
11210 - Call stat() slightly less often; use fstat() when possible.
11211 - Refactor the way we handle pending circuits when an OR connection
11212 completes or fails, in an attempt to fix a rare crash bug.
11213 - Only rewrite a conn's address based on X-Forwarded-For: headers
11214 if it's a parseable public IP address; and stop adding extra quotes
11215 to the resulting address.
11218 - Weight directory requests by advertised bandwidth. Now we can
11219 let servers enable write limiting but still allow most clients to
11220 succeed at their directory requests. (We still ignore weights when
11221 choosing a directory authority; I hope this is a feature.)
11224 - Create a new file ReleaseNotes which was the old ChangeLog. The
11225 new ChangeLog file now includes the summaries for all development
11227 - Check for addresses with invalid characters at the exit as well
11228 as at the client, and warn less verbosely when they fail. You can
11229 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11230 - Adapt a patch from goodell to let the contrib/exitlist script
11231 take arguments rather than require direct editing.
11232 - Inform the server operator when we decide not to advertise a
11233 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11234 was confusing Zax, so now we're hopefully more helpful.
11235 - Bring us one step closer to being able to establish an encrypted
11236 directory tunnel without knowing a descriptor first. Still not
11237 ready yet. As part of the change, now assume we can use a
11238 create_fast cell if we don't know anything about a router.
11239 - Allow exit nodes to use nameservers running on ports other than 53.
11240 - Servers now cache reverse DNS replies.
11241 - Add an --ignore-missing-torrc command-line option so that we can
11242 get the "use sensible defaults if the configuration file doesn't
11243 exist" behavior even when specifying a torrc location on the command
11246 o Minor features (controller):
11247 - Track reasons for OR connection failure; make these reasons
11248 available via the controller interface. (Patch from Mike Perry.)
11249 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11250 can learn when clients are sending malformed hostnames to Tor.
11251 - Clean up documentation for controller status events.
11252 - Add a REMAP status to stream events to note that a stream's
11253 address has changed because of a cached address or a MapAddress
11257 Changes in version 0.1.2.6-alpha - 2007-01-09
11259 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11260 connection handles more than 4 gigs in either direction, we crash.
11261 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11262 advertised exit node, somebody might try to exit from us when
11263 we're bootstrapping and before we've built our descriptor yet.
11264 Refuse the connection rather than crashing.
11267 - Warn if we (as a server) find that we've resolved an address that we
11268 weren't planning to resolve.
11269 - Warn that using select() on any libevent version before 1.1 will be
11270 unnecessarily slow (even for select()).
11271 - Flush ERR-level controller status events just like we currently
11272 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11273 the controller from learning about current events.
11275 o Minor features (more controller status events):
11276 - Implement EXTERNAL_ADDRESS server status event so controllers can
11277 learn when our address changes.
11278 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11279 can learn when directories reject our descriptor.
11280 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11281 can learn when a client application is speaking a non-socks protocol
11283 - Implement DANGEROUS_SOCKS client status event so controllers
11284 can learn when a client application is leaking DNS addresses.
11285 - Implement BUG general status event so controllers can learn when
11286 Tor is unhappy about its internal invariants.
11287 - Implement CLOCK_SKEW general status event so controllers can learn
11288 when Tor thinks the system clock is set incorrectly.
11289 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11290 server status events so controllers can learn when their descriptors
11291 are accepted by a directory.
11292 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11293 server status events so controllers can learn about Tor's progress in
11294 deciding whether it's reachable from the outside.
11295 - Implement BAD_LIBEVENT general status event so controllers can learn
11296 when we have a version/method combination in libevent that needs to
11298 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11299 and DNS_USELESS server status events so controllers can learn
11300 about changes to DNS server status.
11302 o Minor features (directory):
11303 - Authorities no longer recommend exits as guards if this would shift
11304 too much load to the exit nodes.
11307 Changes in version 0.1.2.5-alpha - 2007-01-06
11309 - Enable write limiting as well as read limiting. Now we sacrifice
11310 capacity if we're pushing out lots of directory traffic, rather
11311 than overrunning the user's intended bandwidth limits.
11312 - Include TLS overhead when counting bandwidth usage; previously, we
11313 would count only the bytes sent over TLS, but not the bytes used
11315 - Support running the Tor service with a torrc not in the same
11316 directory as tor.exe and default to using the torrc located in
11317 the %appdata%\Tor\ of the user who installed the service. Patch
11319 - Servers now check for the case when common DNS requests are going to
11320 wildcarded addresses (i.e. all getting the same answer), and change
11321 their exit policy to reject *:* if it's happening.
11322 - Implement BEGIN_DIR cells, so we can connect to the directory
11323 server via TLS to do encrypted directory requests rather than
11324 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11325 config options if you like.
11327 o Minor features (config and docs):
11328 - Start using the state file to store bandwidth accounting data:
11329 the bw_accounting file is now obsolete. We'll keep generating it
11330 for a while for people who are still using 0.1.2.4-alpha.
11331 - Try to batch changes to the state file so that we do as few
11332 disk writes as possible while still storing important things in
11334 - The state file and the bw_accounting file get saved less often when
11335 the AvoidDiskWrites config option is set.
11336 - Make PIDFile work on Windows (untested).
11337 - Add internal descriptions for a bunch of configuration options:
11338 accessible via controller interface and in comments in saved
11340 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11341 NNTP by default, so this seems like a sensible addition.
11342 - Clients now reject hostnames with invalid characters. This should
11343 avoid some inadvertent info leaks. Add an option
11344 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11345 is running a private network with hosts called @, !, and #.
11346 - Add a maintainer script to tell us which options are missing
11347 documentation: "make check-docs".
11348 - Add a new address-spec.txt document to describe our special-case
11349 addresses: .exit, .onion, and .noconnnect.
11351 o Minor features (DNS):
11352 - Ongoing work on eventdns infrastructure: now it has dns server
11353 and ipv6 support. One day Tor will make use of it.
11354 - Add client-side caching for reverse DNS lookups.
11355 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11356 - When we change nameservers or IP addresses, reset and re-launch
11357 our tests for DNS hijacking.
11359 o Minor features (directory):
11360 - Authorities now specify server versions in networkstatus. This adds
11361 about 2% to the size of compressed networkstatus docs, and allows
11362 clients to tell which servers support BEGIN_DIR and which don't.
11363 The implementation is forward-compatible with a proposed future
11364 protocol version scheme not tied to Tor versions.
11365 - DirServer configuration lines now have an orport= option so
11366 clients can open encrypted tunnels to the authorities without
11367 having downloaded their descriptors yet. Enabled for moria1,
11368 moria2, tor26, and lefkada now in the default configuration.
11369 - Directory servers are more willing to send a 503 "busy" if they
11370 are near their write limit, especially for v1 directory requests.
11371 Now they can use their limited bandwidth for actual Tor traffic.
11372 - Clients track responses with status 503 from dirservers. After a
11373 dirserver has given us a 503, we try not to use it until an hour has
11374 gone by, or until we have no dirservers that haven't given us a 503.
11375 - When we get a 503 from a directory, and we're not a server, we don't
11376 count the failure against the total number of failures allowed
11377 for the thing we're trying to download.
11378 - Report X-Your-Address-Is correctly from tunneled directory
11379 connections; don't report X-Your-Address-Is when it's an internal
11380 address; and never believe reported remote addresses when they're
11382 - Protect against an unlikely DoS attack on directory servers.
11383 - Add a BadDirectory flag to network status docs so that authorities
11384 can (eventually) tell clients about caches they believe to be
11387 o Minor features (controller):
11388 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11389 - Reimplement GETINFO so that info/names stays in sync with the
11391 - Implement "GETINFO fingerprint".
11392 - Implement "SETEVENTS GUARD" so controllers can get updates on
11393 entry guard status as it changes.
11395 o Minor features (clean up obsolete pieces):
11396 - Remove some options that have been deprecated since at least
11397 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11398 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11399 to set log options.
11400 - We no longer look for identity and onion keys in "identity.key" and
11401 "onion.key" -- these were replaced by secret_id_key and
11402 secret_onion_key in 0.0.8pre1.
11403 - We no longer require unrecognized directory entries to be
11406 o Major bugfixes (security):
11407 - Stop sending the HttpProxyAuthenticator string to directory
11408 servers when directory connections are tunnelled through Tor.
11409 - Clients no longer store bandwidth history in the state file.
11410 - Do not log introduction points for hidden services if SafeLogging
11412 - When generating bandwidth history, round down to the nearest
11413 1k. When storing accounting data, round up to the nearest 1k.
11414 - When we're running as a server, remember when we last rotated onion
11415 keys, so that we will rotate keys once they're a week old even if
11416 we never stay up for a week ourselves.
11418 o Major bugfixes (other):
11419 - Fix a longstanding bug in eventdns that prevented the count of
11420 timed-out resolves from ever being reset. This bug caused us to
11421 give up on a nameserver the third time it timed out, and try it
11422 10 seconds later... and to give up on it every time it timed out
11424 - Take out the '5 second' timeout from the connection retry
11425 schedule. Now the first connect attempt will wait a full 10
11426 seconds before switching to a new circuit. Perhaps this will help
11427 a lot. Based on observations from Mike Perry.
11428 - Fix a bug on the Windows implementation of tor_mmap_file() that
11429 would prevent the cached-routers file from ever loading. Reported
11433 - Fix an assert failure when a directory authority sets
11434 AuthDirRejectUnlisted and then receives a descriptor from an
11435 unlisted router. Reported by seeess.
11436 - Avoid a double-free when parsing malformed DirServer lines.
11437 - Fix a bug when a BSD-style PF socket is first used. Patch from
11439 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11440 to resolve an address at a given exit node even when they ask for
11442 - Servers no longer ever list themselves in their "family" line,
11443 even if configured to do so. This makes it easier to configure
11444 family lists conveniently.
11445 - When running as a server, don't fall back to 127.0.0.1 when no
11446 nameservers are configured in /etc/resolv.conf; instead, make the
11447 user fix resolv.conf or specify nameservers explicitly. (Resolves
11449 - Stop accepting certain malformed ports in configured exit policies.
11450 - Don't re-write the fingerprint file every restart, unless it has
11452 - Stop warning when a single nameserver fails: only warn when _all_ of
11453 our nameservers have failed. Also, when we only have one nameserver,
11454 raise the threshold for deciding that the nameserver is dead.
11455 - Directory authorities now only decide that routers are reachable
11456 if their identity keys are as expected.
11457 - When the user uses bad syntax in the Log config line, stop
11458 suggesting other bad syntax as a replacement.
11459 - Correctly detect ipv6 DNS capability on OpenBSD.
11461 o Minor bugfixes (controller):
11462 - Report the circuit number correctly in STREAM CLOSED events. Bug
11463 reported by Mike Perry.
11464 - Do not report bizarre values for results of accounting GETINFOs
11465 when the last second's write or read exceeds the allotted bandwidth.
11466 - Report "unrecognized key" rather than an empty string when the
11467 controller tries to fetch a networkstatus that doesn't exist.
11470 Changes in version 0.1.1.26 - 2006-12-14
11471 o Security bugfixes:
11472 - Stop sending the HttpProxyAuthenticator string to directory
11473 servers when directory connections are tunnelled through Tor.
11474 - Clients no longer store bandwidth history in the state file.
11475 - Do not log introduction points for hidden services if SafeLogging
11479 - Fix an assert failure when a directory authority sets
11480 AuthDirRejectUnlisted and then receives a descriptor from an
11481 unlisted router (reported by seeess).
11484 Changes in version 0.1.2.4-alpha - 2006-12-03
11486 - Add support for using natd; this allows FreeBSDs earlier than
11487 5.1.2 to have ipfw send connections through Tor without using
11488 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11491 - Make all connections to addresses of the form ".noconnect"
11492 immediately get closed. This lets application/controller combos
11493 successfully test whether they're talking to the same Tor by
11494 watching for STREAM events.
11495 - Make cross.sh cross-compilation script work even when autogen.sh
11496 hasn't been run. (Patch from Michael Mohr.)
11497 - Statistics dumped by -USR2 now include a breakdown of public key
11498 operations, for profiling.
11501 - Fix a major leak when directory authorities parse their
11502 approved-routers list, a minor memory leak when we fail to pick
11503 an exit node, and a few rare leaks on errors.
11504 - Handle TransPort connections even when the server sends data before
11505 the client sends data. Previously, the connection would just hang
11506 until the client sent data. (Patch from tup based on patch from
11508 - Avoid assert failure when our cached-routers file is empty on
11512 - Don't log spurious warnings when we see a circuit close reason we
11513 don't recognize; it's probably just from a newer version of Tor.
11514 - Have directory authorities allow larger amounts of drift in uptime
11515 without replacing the server descriptor: previously, a server that
11516 restarted every 30 minutes could have 48 "interesting" descriptors
11518 - Start linking to the Tor specification and Tor reference manual
11519 correctly in the Windows installer.
11520 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11521 Tor/Privoxy we also uninstall Vidalia.
11522 - Resume building on Irix64, and fix a lot of warnings from its
11523 MIPSpro C compiler.
11524 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11525 when we're running as a client.
11528 Changes in version 0.1.1.25 - 2006-11-04
11530 - When a client asks us to resolve (rather than connect to)
11531 an address, and we have a cached answer, give them the cached
11532 answer. Previously, we would give them no answer at all.
11533 - We were building exactly the wrong circuits when we predict
11534 hidden service requirements, meaning Tor would have to build all
11535 its circuits on demand.
11536 - If none of our live entry guards have a high uptime, but we
11537 require a guard with a high uptime, try adding a new guard before
11538 we give up on the requirement. This patch should make long-lived
11539 connections more stable on average.
11540 - When testing reachability of our DirPort, don't launch new
11541 tests when there's already one in progress -- unreachable
11542 servers were stacking up dozens of testing streams.
11544 o Security bugfixes:
11545 - When the user sends a NEWNYM signal, clear the client-side DNS
11546 cache too. Otherwise we continue to act on previous information.
11549 - Avoid a memory corruption bug when creating a hash table for
11551 - Avoid possibility of controller-triggered crash when misusing
11552 certain commands from a v0 controller on platforms that do not
11553 handle printf("%s",NULL) gracefully.
11554 - Avoid infinite loop on unexpected controller input.
11555 - Don't log spurious warnings when we see a circuit close reason we
11556 don't recognize; it's probably just from a newer version of Tor.
11557 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11558 Tor/Privoxy we also uninstall Vidalia.
11561 Changes in version 0.1.2.3-alpha - 2006-10-29
11563 - Prepare for servers to publish descriptors less often: never
11564 discard a descriptor simply for being too old until either it is
11565 recommended by no authorities, or until we get a better one for
11566 the same router. Make caches consider retaining old recommended
11567 routers for even longer.
11568 - If most authorities set a BadExit flag for a server, clients
11569 don't think of it as a general-purpose exit. Clients only consider
11570 authorities that advertise themselves as listing bad exits.
11571 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11572 headers for content, so that we can work better in the presence of
11573 caching HTTP proxies.
11574 - Allow authorities to list nodes as bad exits by fingerprint or by
11577 o Minor features, controller:
11578 - Add a REASON field to CIRC events; for backward compatibility, this
11579 field is sent only to controllers that have enabled the extended
11580 event format. Also, add additional reason codes to explain why
11581 a given circuit has been destroyed or truncated. (Patches from
11583 - Add a REMOTE_REASON field to extended CIRC events to tell the
11584 controller about why a remote OR told us to close a circuit.
11585 - Stream events also now have REASON and REMOTE_REASON fields,
11586 working much like those for circuit events.
11587 - There's now a GETINFO ns/... field so that controllers can ask Tor
11588 about the current status of a router.
11589 - A new event type "NS" to inform a controller when our opinion of
11590 a router's status has changed.
11591 - Add a GETINFO events/names and GETINFO features/names so controllers
11592 can tell which events and features are supported.
11593 - A new CLEARDNSCACHE signal to allow controllers to clear the
11594 client-side DNS cache without expiring circuits.
11596 o Security bugfixes:
11597 - When the user sends a NEWNYM signal, clear the client-side DNS
11598 cache too. Otherwise we continue to act on previous information.
11601 - Avoid sending junk to controllers or segfaulting when a controller
11602 uses EVENT_NEW_DESC with verbose nicknames.
11603 - Stop triggering asserts if the controller tries to extend hidden
11604 service circuits (reported by mwenge).
11605 - Avoid infinite loop on unexpected controller input.
11606 - When the controller does a "GETINFO network-status", tell it
11607 about even those routers whose descriptors are very old, and use
11608 long nicknames where appropriate.
11609 - Change NT service functions to be loaded on demand. This lets us
11610 build with MinGW without breaking Tor for Windows 98 users.
11611 - Do DirPort reachability tests less often, since a single test
11612 chews through many circuits before giving up.
11613 - In the hidden service example in torrc.sample, stop recommending
11614 esoteric and discouraged hidden service options.
11615 - When stopping an NT service, wait up to 10 sec for it to actually
11616 stop. Patch from Matt Edman; resolves bug 295.
11617 - Fix handling of verbose nicknames with ORCONN controller events:
11618 make them show up exactly when requested, rather than exactly when
11620 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11621 printing a duplicate "$" in the keys we send (reported by mwenge).
11622 - Correctly set maximum connection limit on Cygwin. (This time
11624 - Try to detect Windows correctly when cross-compiling.
11625 - Detect the size of the routers file correctly even if it is
11626 corrupted (on systems without mmap) or not page-aligned (on systems
11627 with mmap). This bug was harmless.
11628 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11629 to open a stream fails; now we do in more cases. This should
11630 make clients able to find a good exit faster in some cases, since
11631 unhandleable requests will now get an error rather than timing out.
11632 - Resolve two memory leaks when rebuilding the on-disk router cache
11633 (reported by fookoowa).
11634 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11635 and reported by some Centos users.
11636 - Controller signals now work on non-Unix platforms that don't define
11637 SIGUSR1 and SIGUSR2 the way we expect.
11638 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11639 values before failing, and always enables eventdns.
11640 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11641 Try to fix this in configure.in by checking for most functions
11642 before we check for libevent.
11645 Changes in version 0.1.2.2-alpha - 2006-10-07
11647 - Make our async eventdns library on-by-default for Tor servers,
11648 and plan to deprecate the separate dnsworker threads.
11649 - Add server-side support for "reverse" DNS lookups (using PTR
11650 records so clients can determine the canonical hostname for a given
11651 IPv4 address). Only supported by servers using eventdns; servers
11652 now announce in their descriptors whether they support eventdns.
11653 - Specify and implement client-side SOCKS5 interface for reverse DNS
11654 lookups (see doc/socks-extensions.txt).
11655 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11656 connect to directory servers through Tor. Previously, clients needed
11657 to find Tor exits to make private connections to directory servers.
11658 - Avoid choosing Exit nodes for entry or middle hops when the
11659 total bandwidth available from non-Exit nodes is much higher than
11660 the total bandwidth available from Exit nodes.
11661 - Workaround for name servers (like Earthlink's) that hijack failing
11662 DNS requests and replace the no-such-server answer with a "helpful"
11663 redirect to an advertising-driven search portal. Also work around
11664 DNS hijackers who "helpfully" decline to hijack known-invalid
11665 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11666 lets you turn it off.
11667 - Send out a burst of long-range padding cells once we've established
11668 that we're reachable. Spread them over 4 circuits, so hopefully
11669 a few will be fast. This exercises our bandwidth and bootstraps
11670 us into the directory more quickly.
11672 o New/improved config options:
11673 - Add new config option "ResolvConf" to let the server operator
11674 choose an alternate resolve.conf file when using eventdns.
11675 - Add an "EnforceDistinctSubnets" option to control our "exclude
11676 servers on the same /16" behavior. It's still on by default; this
11677 is mostly for people who want to operate private test networks with
11678 all the machines on the same subnet.
11679 - If one of our entry guards is on the ExcludeNodes list, or the
11680 directory authorities don't think it's a good guard, treat it as
11681 if it were unlisted: stop using it as a guard, and throw it off
11682 the guards list if it stays that way for a long time.
11683 - Allow directory authorities to be marked separately as authorities
11684 for the v1 directory protocol, the v2 directory protocol, and
11685 as hidden service directories, to make it easier to retire old
11686 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11687 to continue being hidden service authorities too.
11688 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11690 o Minor features, controller:
11691 - Fix CIRC controller events so that controllers can learn the
11692 identity digests of non-Named servers used in circuit paths.
11693 - Let controllers ask for more useful identifiers for servers. Instead
11694 of learning identity digests for un-Named servers and nicknames
11695 for Named servers, the new identifiers include digest, nickname,
11696 and indication of Named status. Off by default; see control-spec.txt
11697 for more information.
11698 - Add a "getinfo address" controller command so it can display Tor's
11699 best guess to the user.
11700 - New controller event to alert the controller when our server
11701 descriptor has changed.
11702 - Give more meaningful errors on controller authentication failure.
11704 o Minor features, other:
11705 - When asked to resolve a hostname, don't use non-exit servers unless
11706 requested to do so. This allows servers with broken DNS to be
11707 useful to the network.
11708 - Divide eventdns log messages into warn and info messages.
11709 - Reserve the nickname "Unnamed" for routers that can't pick
11710 a hostname: any router can call itself Unnamed; directory
11711 authorities will never allocate Unnamed to any particular router;
11712 clients won't believe that any router is the canonical Unnamed.
11713 - Only include function names in log messages for info/debug messages.
11714 For notice/warn/err, the content of the message should be clear on
11715 its own, and printing the function name only confuses users.
11716 - Avoid some false positives during reachability testing: don't try
11717 to test via a server that's on the same /24 as us.
11718 - If we fail to build a circuit to an intended enclave, and it's
11719 not mandatory that we use that enclave, stop wanting it.
11720 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11721 OpenBSD. (We had previously disabled threads on these platforms
11722 because they didn't have working thread-safe resolver functions.)
11724 o Major bugfixes, anonymity/security:
11725 - If a client asked for a server by name, and there's a named server
11726 in our network-status but we don't have its descriptor yet, we
11727 could return an unnamed server instead.
11728 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11729 to be sent to a server's DNS resolver. This only affects NetBSD
11730 and other platforms that do not bounds-check tolower().
11731 - Reject (most) attempts to use Tor circuits with length one. (If
11732 many people start using Tor as a one-hop proxy, exit nodes become
11733 a more attractive target for compromise.)
11734 - Just because your DirPort is open doesn't mean people should be
11735 able to remotely teach you about hidden service descriptors. Now
11736 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11738 o Major bugfixes, other:
11739 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11740 - When a client asks the server to resolve (not connect to)
11741 an address, and it has a cached answer, give them the cached answer.
11742 Previously, the server would give them no answer at all.
11743 - Allow really slow clients to not hang up five minutes into their
11744 directory downloads (suggested by Adam J. Richter).
11745 - We were building exactly the wrong circuits when we anticipated
11746 hidden service requirements, meaning Tor would have to build all
11747 its circuits on demand.
11748 - Avoid crashing when we mmap a router cache file of size 0.
11749 - When testing reachability of our DirPort, don't launch new
11750 tests when there's already one in progress -- unreachable
11751 servers were stacking up dozens of testing streams.
11753 o Minor bugfixes, correctness:
11754 - If we're a directory mirror and we ask for "all" network status
11755 documents, we would discard status documents from authorities
11756 we don't recognize.
11757 - Avoid a memory corruption bug when creating a hash table for
11759 - Avoid controller-triggered crash when misusing certain commands
11760 from a v0 controller on platforms that do not handle
11761 printf("%s",NULL) gracefully.
11762 - Don't crash when a controller sends a third argument to an
11763 "extendcircuit" request.
11764 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11765 response; fix error code when "getinfo dir/status/" fails.
11766 - Avoid crash when telling controller stream-status and a stream
11768 - Patch from Adam Langley to fix assert() in eventdns.c.
11769 - Fix a debug log message in eventdns to say "X resolved to Y"
11770 instead of "X resolved to X".
11771 - Make eventdns give strings for DNS errors, not just error numbers.
11772 - Track unreachable entry guards correctly: don't conflate
11773 'unreachable by us right now' with 'listed as down by the directory
11774 authorities'. With the old code, if a guard was unreachable by
11775 us but listed as running, it would clog our guard list forever.
11776 - Behave correctly in case we ever have a network with more than
11777 2GB/s total advertised capacity.
11778 - Make TrackExitHosts case-insensitive, and fix the behavior of
11779 ".suffix" TrackExitHosts items to avoid matching in the middle of
11781 - Finally fix the openssl warnings from newer gccs that believe that
11782 ignoring a return value is okay, but casting a return value and
11783 then ignoring it is a sign of madness.
11784 - Prevent the contrib/exitlist script from printing the same
11785 result more than once.
11786 - Patch from Steve Hildrey: Generate network status correctly on
11787 non-versioning dirservers.
11788 - Don't listen to the X-Your-Address-Is hint if you did the lookup
11789 via Tor; otherwise you'll think you're the exit node's IP address.
11791 o Minor bugfixes, performance:
11792 - Two small performance improvements on parsing descriptors.
11793 - Major performance improvement on inserting descriptors: change
11794 algorithm from O(n^2) to O(n).
11795 - Make the common memory allocation path faster on machines where
11796 malloc(0) returns a pointer.
11797 - Start remembering X-Your-Address-Is directory hints even if you're
11798 a client, so you can become a server more smoothly.
11799 - Avoid duplicate entries on MyFamily line in server descriptor.
11801 o Packaging, features:
11802 - Remove architecture from OS X builds. The official builds are
11803 now universal binaries.
11804 - The Debian package now uses --verify-config when (re)starting,
11805 to distinguish configuration errors from other errors.
11806 - Update RPMs to require libevent 1.1b.
11808 o Packaging, bugfixes:
11809 - Patches so Tor builds with MinGW on Windows.
11810 - Patches so Tor might run on Cygwin again.
11811 - Resume building on non-gcc compilers and ancient gcc. Resume
11812 building with the -O0 compile flag. Resume building cleanly on
11814 - Run correctly on OS X platforms with case-sensitive filesystems.
11815 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
11816 - Add autoconf checks so Tor can build on Solaris x86 again.
11819 - Documented (and renamed) ServerDNSSearchDomains and
11820 ServerDNSResolvConfFile options.
11821 - Be clearer that the *ListenAddress directives can be repeated
11825 Changes in version 0.1.1.24 - 2006-09-29
11827 - Allow really slow clients to not hang up five minutes into their
11828 directory downloads (suggested by Adam J. Richter).
11829 - Fix major performance regression from 0.1.0.x: instead of checking
11830 whether we have enough directory information every time we want to
11831 do something, only check when the directory information has changed.
11832 This should improve client CPU usage by 25-50%.
11833 - Don't crash if, after a server has been running for a while,
11834 it can't resolve its hostname.
11837 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11838 - Don't crash when the controller receives a third argument to an
11839 "extendcircuit" request.
11840 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11841 response; fix error code when "getinfo dir/status/" fails.
11842 - Fix configure.in to not produce broken configure files with
11843 more recent versions of autoconf. Thanks to Clint for his auto*
11845 - Fix security bug on NetBSD that could allow someone to force
11846 uninitialized RAM to be sent to a server's DNS resolver. This
11847 only affects NetBSD and other platforms that do not bounds-check
11849 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
11850 methods: these are known to be buggy.
11851 - If we're a directory mirror and we ask for "all" network status
11852 documents, we would discard status documents from authorities
11853 we don't recognize.
11856 Changes in version 0.1.2.1-alpha - 2006-08-27
11858 - Add "eventdns" async dns library from Adam Langley, tweaked to
11859 build on OSX and Windows. Only enabled if you pass the
11860 --enable-eventdns argument to configure.
11861 - Allow servers with no hostname or IP address to learn their
11862 IP address by asking the directory authorities. This code only
11863 kicks in when you would normally have exited with a "no address"
11864 error. Nothing's authenticated, so use with care.
11865 - Rather than waiting a fixed amount of time between retrying
11866 application connections, we wait only 5 seconds for the first,
11867 10 seconds for the second, and 15 seconds for each retry after
11868 that. Hopefully this will improve the expected user experience.
11869 - Patch from Tup to add support for transparent AP connections:
11870 this basically bundles the functionality of trans-proxy-tor
11871 into the Tor mainline. Now hosts with compliant pf/netfilter
11872 implementations can redirect TCP connections straight to Tor
11873 without diverting through SOCKS. Needs docs.
11874 - Busy directory servers save lots of memory by spooling server
11875 descriptors, v1 directories, and v2 networkstatus docs to buffers
11876 as needed rather than en masse. Also mmap the cached-routers
11877 files, so we don't need to keep the whole thing in memory too.
11878 - Automatically avoid picking more than one node from the same
11879 /16 network when constructing a circuit.
11880 - Revise and clean up the torrc.sample that we ship with; add
11881 a section for BandwidthRate and BandwidthBurst.
11884 - Split circuit_t into origin_circuit_t and or_circuit_t, and
11885 split connection_t into edge, or, dir, control, and base structs.
11886 These will save quite a bit of memory on busy servers, and they'll
11887 also help us track down bugs in the code and bugs in the spec.
11888 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
11889 or later. Log when we are doing this, so we can diagnose it when
11890 it fails. (Also, recommend libevent 1.1b for kqueue and
11891 win32 methods; deprecate libevent 1.0b harder; make libevent
11892 recommendation system saner.)
11893 - Start being able to build universal binaries on OS X (thanks
11895 - Export the default exit policy via the control port, so controllers
11896 don't need to guess what it is / will be later.
11897 - Add a man page entry for ProtocolWarnings.
11898 - Add TestVia config option to the man page.
11899 - Remove even more protocol-related warnings from Tor server logs,
11900 such as bad TLS handshakes and malformed begin cells.
11901 - Stop fetching descriptors if you're not a dir mirror and you
11902 haven't tried to establish any circuits lately. [This currently
11903 causes some dangerous behavior, because when you start up again
11904 you'll use your ancient server descriptors.]
11905 - New DirPort behavior: if you have your dirport set, you download
11906 descriptors aggressively like a directory mirror, whether or not
11907 your ORPort is set.
11908 - Get rid of the router_retry_connections notion. Now routers
11909 no longer try to rebuild long-term connections to directory
11910 authorities, and directory authorities no longer try to rebuild
11911 long-term connections to all servers. We still don't hang up
11912 connections in these two cases though -- we need to look at it
11913 more carefully to avoid flapping, and we likely need to wait til
11914 0.1.1.x is obsolete.
11915 - Drop compatibility with obsolete Tors that permit create cells
11916 to have the wrong circ_id_type.
11917 - Re-enable per-connection rate limiting. Get rid of the "OP
11918 bandwidth" concept. Lay groundwork for "bandwidth classes" --
11919 separate global buckets that apply depending on what sort of conn
11921 - Start publishing one minute or so after we find our ORPort
11922 to be reachable. This will help reduce the number of descriptors
11923 we have for ourselves floating around, since it's quite likely
11924 other things (e.g. DirPort) will change during that minute too.
11925 - Fork the v1 directory protocol into its own spec document,
11926 and mark dir-spec.txt as the currently correct (v2) spec.
11929 - When we find our DirPort to be reachable, publish a new descriptor
11930 so we'll tell the world (reported by pnx).
11931 - Publish a new descriptor after we hup/reload. This is important
11932 if our config has changed such that we'll want to start advertising
11933 our DirPort now, etc.
11934 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11935 - When we have a state file we cannot parse, tell the user and
11936 move it aside. Now we avoid situations where the user starts
11937 Tor in 1904, Tor writes a state file with that timestamp in it,
11938 the user fixes her clock, and Tor refuses to start.
11939 - Fix configure.in to not produce broken configure files with
11940 more recent versions of autoconf. Thanks to Clint for his auto*
11942 - "tor --verify-config" now exits with -1(255) or 0 depending on
11943 whether the config options are bad or good.
11944 - Resolve bug 321 when using dnsworkers: append a period to every
11945 address we resolve at the exit node, so that we do not accidentally
11946 pick up local addresses, and so that failing searches are retried
11947 in the resolver search domains. (This is already solved for
11948 eventdns.) (This breaks Blossom servers for now.)
11949 - If we are using an exit enclave and we can't connect, e.g. because
11950 its webserver is misconfigured to not listen on localhost, then
11951 back off and try connecting from somewhere else before we fail.
11954 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
11955 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
11956 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
11957 when the IP address is mapped through MapAddress to a hostname.
11958 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11959 useless IPv6 DNS resolves.
11960 - Patch suggested by Karsten Loesing: respond to SIGNAL command
11961 before we execute the signal, in case the signal shuts us down.
11962 - Clean up AllowInvalidNodes man page entry.
11963 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
11964 - Add more asserts to track down an assert error on a windows Tor
11965 server with connection_add being called with socket == -1.
11966 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
11967 - Fix misleading log messages: an entry guard that is "unlisted",
11968 as well as not known to be "down" (because we've never heard
11969 of it), is not therefore "up".
11970 - Remove code to special-case "-cvs" ending, since it has not
11971 actually mattered since 0.0.9.
11972 - Make our socks5 handling more robust to broken socks clients:
11973 throw out everything waiting on the buffer in between socks
11974 handshake phases, since they can't possibly (so the theory
11975 goes) have predicted what we plan to respond to them.
11978 Changes in version 0.1.1.23 - 2006-07-30
11980 - Fast Tor servers, especially exit nodes, were triggering asserts
11981 due to a bug in handling the list of pending DNS resolves. Some
11982 bugs still remain here; we're hunting them.
11983 - Entry guards could crash clients by sending unexpected input.
11984 - More fixes on reachability testing: if you find yourself reachable,
11985 then don't ever make any client requests (so you stop predicting
11986 circuits), then hup or have your clock jump, then later your IP
11987 changes, you won't think circuits are working, so you won't try to
11988 test reachability, so you won't publish.
11991 - Avoid a crash if the controller does a resetconf firewallports
11992 and then a setconf fascistfirewall=1.
11993 - Avoid an integer underflow when the dir authority decides whether
11994 a router is stable: we might wrongly label it stable, and compute
11995 a slightly wrong median stability, when a descriptor is published
11997 - Fix a place where we might trigger an assert if we can't build our
11998 own server descriptor yet.
12001 Changes in version 0.1.1.22 - 2006-07-05
12003 - Fix a big bug that was causing servers to not find themselves
12004 reachable if they changed IP addresses. Since only 0.1.1.22+
12005 servers can do reachability testing correctly, now we automatically
12006 make sure to test via one of these.
12007 - Fix to allow clients and mirrors to learn directory info from
12008 descriptor downloads that get cut off partway through.
12009 - Directory authorities had a bug in deciding if a newly published
12010 descriptor was novel enough to make everybody want a copy -- a few
12011 servers seem to be publishing new descriptors many times a minute.
12013 - Fix a rare bug that was causing some servers to complain about
12014 "closing wedged cpuworkers" and skip some circuit create requests.
12015 - Make the Exit flag in directory status documents actually work.
12018 Changes in version 0.1.1.21 - 2006-06-10
12019 o Crash and assert fixes from 0.1.1.20:
12020 - Fix a rare crash on Tor servers that have enabled hibernation.
12021 - Fix a seg fault on startup for Tor networks that use only one
12022 directory authority.
12023 - Fix an assert from a race condition that occurs on Tor servers
12024 while exiting, where various threads are trying to log that they're
12025 exiting, and delete the logs, at the same time.
12026 - Make our unit tests pass again on certain obscure platforms.
12029 - Add support for building SUSE RPM packages.
12030 - Speed up initial bootstrapping for clients: if we are making our
12031 first ever connection to any entry guard, then don't mark it down
12033 - When only one Tor server in the network is labelled as a guard,
12034 and we've already picked him, we would cycle endlessly picking him
12035 again, being unhappy about it, etc. Now we specifically exclude
12036 current guards when picking a new guard.
12037 - Servers send create cells more reliably after the TLS connection
12038 is established: we were sometimes forgetting to send half of them
12039 when we had more than one pending.
12040 - If we get a create cell that asks us to extend somewhere, but the
12041 Tor server there doesn't match the expected digest, we now send
12042 a destroy cell back, rather than silently doing nothing.
12043 - Make options->RedirectExit work again.
12044 - Make cookie authentication for the controller work again.
12045 - Stop being picky about unusual characters in the arguments to
12046 mapaddress. It's none of our business.
12047 - Add a new config option "TestVia" that lets you specify preferred
12048 middle hops to use for test circuits. Perhaps this will let me
12049 debug the reachability problems better.
12051 o Log / documentation fixes:
12052 - If we're a server and some peer has a broken TLS certificate, don't
12053 log about it unless ProtocolWarnings is set, i.e., we want to hear
12054 about protocol violations by others.
12055 - Fix spelling of VirtualAddrNetwork in man page.
12056 - Add a better explanation at the top of the autogenerated torrc file
12057 about what happened to our old torrc.
12060 Changes in version 0.1.1.20 - 2006-05-23
12062 - Downgrade a log severity where servers complain that they're
12064 - Avoid a compile warning on FreeBSD.
12065 - Remove string size limit on NEWDESC messages; solve bug 291.
12066 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12067 more thoroughly when we're running on windows.
12070 Changes in version 0.1.1.19-rc - 2006-05-03
12072 - Regenerate our local descriptor if it's dirty and we try to use
12073 it locally (e.g. if it changes during reachability detection).
12074 - If we setconf our ORPort to 0, we continued to listen on the
12075 old ORPort and receive connections.
12076 - Avoid a second warning about machine/limits.h on Debian
12078 - Be willing to add our own routerinfo into the routerlist.
12079 Now authorities will include themselves in their directories
12080 and network-statuses.
12081 - Stop trying to upload rendezvous descriptors to every
12082 directory authority: only try the v1 authorities.
12083 - Servers no longer complain when they think they're not
12084 registered with the directory authorities. There were too many
12086 - Backport dist-rpm changes so rpms can be built without errors.
12089 - Implement an option, VirtualAddrMask, to set which addresses
12090 get handed out in response to mapaddress requests. This works
12091 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12094 Changes in version 0.1.1.18-rc - 2006-04-10
12096 - Work harder to download live network-statuses from all the
12097 directory authorities we know about. Improve the threshold
12098 decision logic so we're more robust to edge cases.
12099 - When fetching rendezvous descriptors, we were willing to ask
12100 v2 authorities too, which would always return 404.
12103 - Stop listing down or invalid nodes in the v1 directory. This will
12104 reduce its bulk by about 1/3, and reduce load on directory
12106 - When deciding whether a router is Fast or Guard-worthy, consider
12107 his advertised BandwidthRate and not just the BandwidthCapacity.
12108 - No longer ship INSTALL and README files -- they are useless now.
12109 - Force rpmbuild to behave and honor target_cpu.
12110 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12111 - Start to include translated versions of the tor-doc-*.html
12112 files, along with the screenshots. Still needs more work.
12113 - Start sending back 512 and 451 errors if mapaddress fails,
12114 rather than not sending anything back at all.
12115 - When we fail to bind or listen on an incoming or outgoing
12116 socket, we should close it before failing. otherwise we just
12117 leak it. (thanks to weasel for finding.)
12118 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12119 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12120 - Make NoPublish (even though deprecated) work again.
12121 - Fix a minor security flaw where a versioning auth dirserver
12122 could list a recommended version many times in a row to make
12123 clients more convinced that it's recommended.
12124 - Fix crash bug if there are two unregistered servers running
12125 with the same nickname, one of them is down, and you ask for
12126 them by nickname in your EntryNodes or ExitNodes. Also, try
12127 to pick the one that's running rather than an arbitrary one.
12128 - Fix an infinite loop we could hit if we go offline for too long.
12129 - Complain when we hit WSAENOBUFS on recv() or write() too.
12130 Perhaps this will help us hunt the bug.
12131 - If you're not a versioning dirserver, don't put the string
12132 "client-versions \nserver-versions \n" in your network-status.
12133 - Lower the minimum required number of file descriptors to 1000,
12134 so we can have some overhead for Valgrind on Linux, where the
12135 default ulimit -n is 1024.
12138 - Add tor.dizum.com as the fifth authoritative directory server.
12139 - Add a new config option FetchUselessDescriptors, off by default,
12140 for when you plan to run "exitlist" on your client and you want
12141 to know about even the non-running descriptors.
12144 Changes in version 0.1.1.17-rc - 2006-03-28
12146 - Clients and servers since 0.1.1.10-alpha have been expiring
12147 connections whenever they are idle for 5 minutes and they *do*
12148 have circuits on them. Oops. With this new version, clients will
12149 discard their previous entry guard choices and avoid choosing
12150 entry guards running these flawed versions.
12151 - Fix memory leak when uncompressing concatenated zlib streams. This
12152 was causing substantial leaks over time on Tor servers.
12153 - The v1 directory was including servers as much as 48 hours old,
12154 because that's how the new routerlist->routers works. Now only
12155 include them if they're 20 hours old or less.
12158 - Resume building on irix64, netbsd 2.0, etc.
12159 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12161 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12162 and it is confusing some users.
12163 - Mirrors stop caching the v1 directory so often.
12164 - Make the max number of old descriptors that a cache will hold
12165 rise with the number of directory authorities, so we can scale.
12166 - Change our win32 uname() hack to be more forgiving about what
12167 win32 versions it thinks it's found.
12170 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12172 - When the controller's *setconf commands fail, collect an error
12173 message in a string and hand it back to the controller.
12174 - Make the v2 dir's "Fast" flag based on relative capacity, just
12175 like "Stable" is based on median uptime. Name everything in the
12176 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12177 - Log server fingerprint on startup, so new server operators don't
12178 have to go hunting around their filesystem for it.
12179 - Return a robots.txt on our dirport to discourage google indexing.
12180 - Let the controller ask for GETINFO dir/status/foo so it can ask
12181 directly rather than connecting to the dir port. Only works when
12182 dirport is set for now.
12184 o New config options rather than constants in the code:
12185 - SocksTimeout: How long do we let a socks connection wait
12186 unattached before we fail it?
12187 - CircuitBuildTimeout: Cull non-open circuits that were born
12188 at least this many seconds ago.
12189 - CircuitIdleTimeout: Cull open clean circuits that were born
12190 at least this many seconds ago.
12193 Changes in version 0.1.1.16-rc - 2006-03-18
12194 o Bugfixes on 0.1.1.15-rc:
12195 - Fix assert when the controller asks to attachstream a connect-wait
12196 or resolve-wait stream.
12197 - Now do address rewriting when the controller asks us to attach
12198 to a particular circuit too. This will let Blossom specify
12199 "moria2.exit" without having to learn what moria2's IP address is.
12200 - Make the "tor --verify-config" command-line work again, so people
12201 can automatically check if their torrc will parse.
12202 - Authoritative dirservers no longer require an open connection from
12203 a server to consider him "reachable". We need this change because
12204 when we add new auth dirservers, old servers won't know not to
12206 - Let Tor build on Sun CC again.
12207 - Fix an off-by-one buffer size in dirserv.c that magically never
12208 hit our three authorities but broke sjmurdoch's own tor network.
12209 - If we as a directory mirror don't know of any v1 directory
12210 authorities, then don't try to cache any v1 directories.
12211 - Stop warning about unknown servers in our family when they are
12212 given as hex digests.
12213 - Stop complaining as quickly to the server operator that he
12214 hasn't registered his nickname/key binding.
12215 - Various cleanups so we can add new V2 Auth Dirservers.
12216 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12217 reflect the updated flags in our v2 dir protocol.
12218 - Resume allowing non-printable characters for exit streams (both
12219 for connecting and for resolving). Now we tolerate applications
12220 that don't follow the RFCs. But continue to block malformed names
12223 o Bugfixes on 0.1.0.x:
12224 - Fix assert bug in close_logs(): when we close and delete logs,
12225 remove them all from the global "logfiles" list.
12226 - Fix minor integer overflow in calculating when we expect to use up
12227 our bandwidth allocation before hibernating.
12228 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12229 there are multiple SSLs installed with different versions.
12230 - When we try to be a server and Address is not explicitly set and
12231 our hostname resolves to a private IP address, try to use an
12232 interface address if it has a public address. Now Windows machines
12233 that think of themselves as localhost can work by default.
12236 - Let the controller ask for GETINFO dir/server/foo so it can ask
12237 directly rather than connecting to the dir port.
12238 - Let the controller tell us about certain router descriptors
12239 that it doesn't want Tor to use in circuits. Implement
12240 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12241 - New config option SafeSocks to reject all application connections
12242 using unsafe socks protocols. Defaults to off.
12245 Changes in version 0.1.1.15-rc - 2006-03-11
12246 o Bugfixes and cleanups:
12247 - When we're printing strings from the network, don't try to print
12248 non-printable characters. This protects us against shell escape
12249 sequence exploits, and also against attacks to fool humans into
12250 misreading their logs.
12251 - Fix a bug where Tor would fail to establish any connections if you
12252 left it off for 24 hours and then started it: we were happy with
12253 the obsolete network statuses, but they all referred to router
12254 descriptors that were too old to fetch, so we ended up with no
12255 valid router descriptors.
12256 - Fix a seg fault in the controller's "getinfo orconn-status"
12257 command while listing status on incoming handshaking connections.
12258 Introduce a status name "NEW" for these connections.
12259 - If we get a linelist or linelist_s config option from the torrc
12260 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12261 silently resetting it to its default.
12262 - Don't abandon entry guards until they've been down or gone for
12264 - Cleaner and quieter log messages.
12267 - New controller signal NEWNYM that makes new application requests
12268 use clean circuits.
12269 - Add a new circuit purpose 'controller' to let the controller ask
12270 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12271 controller command to let you specify the purpose if you're
12272 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12273 command to let you change a circuit's purpose after it's been
12275 - Accept "private:*" in routerdesc exit policies; not generated yet
12276 because older Tors do not understand it.
12277 - Add BSD-style contributed startup script "rc.subr" from Peter
12281 Changes in version 0.1.1.14-alpha - 2006-02-20
12282 o Bugfixes on 0.1.1.x:
12283 - Don't die if we ask for a stdout or stderr log (even implicitly)
12284 and we're set to RunAsDaemon -- just warn.
12285 - We still had a few bugs in the OR connection rotation code that
12286 caused directory servers to slowly aggregate connections to other
12287 fast Tor servers. This time for sure!
12288 - Make log entries on Win32 include the name of the function again.
12289 - We were treating a pair of exit policies if they were equal even
12290 if one said accept and the other said reject -- causing us to
12291 not always publish a new descriptor since we thought nothing
12293 - Retry pending server downloads as well as pending networkstatus
12294 downloads when we unexpectedly get a socks request.
12295 - We were ignoring the IS_FAST flag in the directory status,
12296 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12298 - If the controller's SAVECONF command fails (e.g. due to file
12299 permissions), let the controller know that it failed.
12302 - If we're trying to be a Tor server and running Windows 95/98/ME
12303 as a server, explain that we'll likely crash.
12304 - When we're a server, a client asks for an old-style directory,
12305 and our write bucket is empty, don't give it to him. This way
12306 small servers can continue to serve the directory *sometimes*,
12307 without getting overloaded.
12308 - Compress exit policies even more -- look for duplicate lines
12310 - Clients now honor the "guard" flag in the router status when
12311 picking entry guards, rather than looking at is_fast or is_stable.
12312 - Retain unrecognized lines in $DATADIR/state file, so that we can
12313 be forward-compatible.
12314 - Generate 18.0.0.0/8 address policy format in descs when we can;
12315 warn when the mask is not reducible to a bit-prefix.
12316 - Let the user set ControlListenAddress in the torrc. This can be
12317 dangerous, but there are some cases (like a secured LAN) where it
12319 - Split ReachableAddresses into ReachableDirAddresses and
12320 ReachableORAddresses, so we can restrict Dir conns to port 80
12321 and OR conns to port 443.
12322 - Now we can target arch and OS in rpm builds (contributed by
12323 Phobos). Also make the resulting dist-rpm filename match the
12325 - New config options to help controllers: FetchServerDescriptors
12326 and FetchHidServDescriptors for whether to fetch server
12327 info and hidserv info or let the controller do it, and
12328 PublishServerDescriptor and PublishHidServDescriptors.
12329 - Also let the controller set the __AllDirActionsPrivate config
12330 option if you want all directory fetches/publishes to happen via
12331 Tor (it assumes your controller bootstraps your circuits).
12334 Changes in version 0.1.0.17 - 2006-02-17
12335 o Crash bugfixes on 0.1.0.x:
12336 - When servers with a non-zero DirPort came out of hibernation,
12337 sometimes they would trigger an assert.
12339 o Other important bugfixes:
12340 - On platforms that don't have getrlimit (like Windows), we were
12341 artificially constraining ourselves to a max of 1024
12342 connections. Now just assume that we can handle as many as 15000
12343 connections. Hopefully this won't cause other problems.
12345 o Backported features:
12346 - When we're a server, a client asks for an old-style directory,
12347 and our write bucket is empty, don't give it to him. This way
12348 small servers can continue to serve the directory *sometimes*,
12349 without getting overloaded.
12350 - Whenever you get a 503 in response to a directory fetch, try
12351 once more. This will become important once servers start sending
12352 503's whenever they feel busy.
12353 - Fetch a new directory every 120 minutes, not every 40 minutes.
12354 Now that we have hundreds of thousands of users running the old
12355 directory algorithm, it's starting to hurt a lot.
12356 - Bump up the period for forcing a hidden service descriptor upload
12357 from 20 minutes to 1 hour.
12360 Changes in version 0.1.1.13-alpha - 2006-02-09
12361 o Crashes in 0.1.1.x:
12362 - When you tried to setconf ORPort via the controller, Tor would
12363 crash. So people using TorCP to become a server were sad.
12364 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12365 servers. The problem appears to be something do with OpenSSL's
12366 random number generation, or how we call it, or something. Let me
12367 know if the crashes continue.
12368 - Turn crypto hardware acceleration off by default, until we find
12369 somebody smart who can test it for us. (It appears to produce
12370 seg faults in at least some cases.)
12371 - Fix a rare assert error when we've tried all intro points for
12372 a hidden service and we try fetching the service descriptor again:
12373 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12376 - Fix a major load balance bug: we were round-robining in 16 KB
12377 chunks, and servers with bandwidthrate of 20 KB, while downloading
12378 a 600 KB directory, would starve their other connections. Now we
12379 try to be a bit more fair.
12380 - Dir authorities and mirrors were never expiring the newest
12381 descriptor for each server, causing memory and directory bloat.
12382 - Fix memory-bloating and connection-bloating bug on servers: We
12383 were never closing any connection that had ever had a circuit on
12384 it, because we were checking conn->n_circuits == 0, yet we had a
12385 bug that let it go negative.
12386 - Make Tor work using squid as your http proxy again -- squid
12387 returns an error if you ask for a URL that's too long, and it uses
12388 a really generic error message. Plus, many people are behind a
12389 transparent squid so they don't even realize it.
12390 - On platforms that don't have getrlimit (like Windows), we were
12391 artificially constraining ourselves to a max of 1024
12392 connections. Now just assume that we can handle as many as 15000
12393 connections. Hopefully this won't cause other problems.
12394 - Add a new config option ExitPolicyRejectPrivate which defaults to
12395 1. This means all exit policies will begin with rejecting private
12396 addresses, unless the server operator explicitly turns it off.
12399 - Clients no longer download descriptors for non-running
12401 - Before we add new directory authorities, we should make it
12402 clear that only v1 authorities should receive/publish hidden
12403 service descriptors.
12406 - As soon as we've fetched some more directory info, immediately
12407 try to download more server descriptors. This way we don't have
12408 a 10 second pause during initial bootstrapping.
12409 - Remove even more loud log messages that the server operator can't
12411 - When we're running an obsolete or un-recommended version, make
12412 the log message more clear about what the problem is and what
12413 versions *are* still recommended.
12414 - Provide a more useful warn message when our onion queue gets full:
12415 the CPU is too slow or the exit policy is too liberal.
12416 - Don't warn when we receive a 503 from a dirserver/cache -- this
12417 will pave the way for them being able to refuse if they're busy.
12418 - When we fail to bind a listener, try to provide a more useful
12419 log message: e.g., "Is Tor already running?"
12420 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12421 Goldberg can prove things about our handshake protocol more
12423 - MaxConn has been obsolete for a while now. Document the ConnLimit
12424 config option, which is a *minimum* number of file descriptors
12425 that must be available else Tor refuses to start.
12426 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12427 if you log to syslog and want something other than LOG_DAEMON.
12428 - Make dirservers generate a separate "guard" flag to mean,
12429 "would make a good entry guard". Make clients parse it and vote
12430 on it. Not used by clients yet.
12431 - Implement --with-libevent-dir option to ./configure. Also, improve
12432 search techniques to find libevent, and use those for openssl too.
12433 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12434 - Only start testing reachability once we've established a
12435 circuit. This will make startup on dirservers less noisy.
12436 - Don't try to upload hidden service descriptors until we have
12437 established a circuit.
12438 - Fix the controller's "attachstream 0" command to treat conn like
12439 it just connected, doing address remapping, handling .exit and
12440 .onion idioms, and so on. Now we're more uniform in making sure
12441 that the controller hears about new and closing connections.
12444 Changes in version 0.1.1.12-alpha - 2006-01-11
12445 o Bugfixes on 0.1.1.x:
12446 - The fix to close duplicate server connections was closing all
12447 Tor client connections if they didn't establish a circuit
12448 quickly enough. Oops.
12449 - Fix minor memory issue (double-free) that happened on exit.
12451 o Bugfixes on 0.1.0.x:
12452 - Tor didn't warn when it failed to open a log file.
12455 Changes in version 0.1.1.11-alpha - 2006-01-10
12456 o Crashes in 0.1.1.x:
12457 - Include all the assert/crash fixes from 0.1.0.16.
12458 - If you start Tor and then quit very quickly, there were some
12459 races that tried to free things that weren't allocated yet.
12460 - Fix a rare memory stomp if you're running hidden services.
12461 - Fix segfault when specifying DirServer in config without nickname.
12462 - Fix a seg fault when you finish connecting to a server but at
12463 that moment you dump his server descriptor.
12464 - Extendcircuit and Attachstream controller commands would
12465 assert/crash if you don't give them enough arguments.
12466 - Fix an assert error when we're out of space in the connection_list
12467 and we try to post a hidden service descriptor (reported by weasel).
12468 - If you specify a relative torrc path and you set RunAsDaemon in
12469 your torrc, then it chdir()'s to the new directory. If you HUP,
12470 it tries to load the new torrc location, fails, and exits.
12471 The fix: no longer allow a relative path to torrc using -f.
12474 - Implement "entry guards": automatically choose a handful of entry
12475 nodes and stick with them for all circuits. Only pick new guards
12476 when the ones you have are unsuitable, and if the old guards
12477 become suitable again, switch back. This will increase security
12478 dramatically against certain end-point attacks. The EntryNodes
12479 config option now provides some hints about which entry guards you
12480 want to use most; and StrictEntryNodes means to only use those.
12481 - New directory logic: download by descriptor digest, not by
12482 fingerprint. Caches try to download all listed digests from
12483 authorities; clients try to download "best" digests from caches.
12484 This avoids partitioning and isolating attacks better.
12485 - Make the "stable" router flag in network-status be the median of
12486 the uptimes of running valid servers, and make clients pay
12487 attention to the network-status flags. Thus the cutoff adapts
12488 to the stability of the network as a whole, making IRC, IM, etc
12489 connections more reliable.
12492 - Tor servers with dynamic IP addresses were needing to wait 18
12493 hours before they could start doing reachability testing using
12494 the new IP address and ports. This is because they were using
12495 the internal descriptor to learn what to test, yet they were only
12496 rebuilding the descriptor once they decided they were reachable.
12497 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12498 to download certain server descriptors, throw them away, and then
12499 fetch them again after 30 minutes. Now mirrors throw away these
12500 server descriptors so clients can't get them.
12501 - We were leaving duplicate connections to other ORs open for a week,
12502 rather than closing them once we detect a duplicate. This only
12503 really affected authdirservers, but it affected them a lot.
12504 - Spread the authdirservers' reachability testing over the entire
12505 testing interval, so we don't try to do 500 TLS's at once every
12509 - If the network is down, and we try to connect to a conn because
12510 we have a circuit in mind, and we timeout (30 seconds) because the
12511 network never answers, we were expiring the circuit, but we weren't
12512 obsoleting the connection or telling the entry_guards functions.
12513 - Some Tor servers process billions of cells per day. These statistics
12514 need to be uint64_t's.
12515 - Check for integer overflows in more places, when adding elements
12516 to smartlists. This could possibly prevent a buffer overflow
12517 on malicious huge inputs. I don't see any, but I haven't looked
12519 - ReachableAddresses kept growing new "reject *:*" lines on every
12521 - When you "setconf log" via the controller, it should remove all
12522 logs. We were automatically adding back in a "log notice stdout".
12523 - Newly bootstrapped Tor networks couldn't establish hidden service
12524 circuits until they had nodes with high uptime. Be more tolerant.
12525 - We were marking servers down when they could not answer every piece
12526 of the directory request we sent them. This was far too harsh.
12527 - Fix the torify (tsocks) config file to not use Tor for localhost
12529 - Directory authorities now go to the proper authority when asking for
12530 a networkstatus, even when they want a compressed one.
12531 - Fix a harmless bug that was causing Tor servers to log
12532 "Got an end because of misc error, but we're not an AP. Closing."
12533 - Authorities were treating their own descriptor changes as cosmetic,
12534 meaning the descriptor available in the network-status and the
12535 descriptor that clients downloaded were different.
12536 - The OS X installer was adding a symlink for tor_resolve but
12537 the binary was called tor-resolve (reported by Thomas Hardly).
12538 - Workaround a problem with some http proxies where they refuse GET
12539 requests that specify "Content-Length: 0" (reported by Adrian).
12540 - Fix wrong log message when you add a "HiddenServiceNodes" config
12541 line without any HiddenServiceDir line (reported by Chris Thomas).
12544 - Write the TorVersion into the state file so we have a prayer of
12545 keeping forward and backward compatibility.
12546 - Revive the FascistFirewall config option rather than eliminating it:
12547 now it's a synonym for ReachableAddresses *:80,*:443.
12548 - Clients choose directory servers from the network status lists,
12549 not from their internal list of router descriptors. Now they can
12550 go to caches directly rather than needing to go to authorities
12552 - Directory authorities ignore router descriptors that have only
12553 cosmetic differences: do this for 0.1.0.x servers now too.
12554 - Add a new flag to network-status indicating whether the server
12555 can answer v2 directory requests too.
12556 - Authdirs now stop whining so loudly about bad descriptors that
12557 they fetch from other dirservers. So when there's a log complaint,
12558 it's for sure from a freshly uploaded descriptor.
12559 - Reduce memory requirements in our structs by changing the order
12561 - There used to be two ways to specify your listening ports in a
12562 server descriptor: on the "router" line and with a separate "ports"
12563 line. Remove support for the "ports" line.
12564 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12565 a panic button: if we get flooded with unusable servers we can
12566 revert to only listing servers in the approved-routers file.
12567 - Auth dir servers can now mark a fingerprint as "!reject" or
12568 "!invalid" in the approved-routers file (as its nickname), to
12569 refuse descriptors outright or include them but marked as invalid.
12570 - Servers store bandwidth history across restarts/crashes.
12571 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12572 get a better idea of why their circuits failed. Not used yet.
12573 - Directory mirrors now cache up to 16 unrecognized network-status
12574 docs. Now we can add new authdirservers and they'll be cached too.
12575 - When picking a random directory, prefer non-authorities if any
12577 - New controller option "getinfo desc/all-recent" to fetch the
12578 latest server descriptor for every router that Tor knows about.
12581 Changes in version 0.1.0.16 - 2006-01-02
12582 o Crash bugfixes on 0.1.0.x:
12583 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12584 corrupting the heap, losing FDs, or crashing when we need to resize
12585 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12586 - It turns out sparc64 platforms crash on unaligned memory access
12587 too -- so detect and avoid this.
12588 - Handle truncated compressed data correctly (by detecting it and
12590 - Fix possible-but-unlikely free(NULL) in control.c.
12591 - When we were closing connections, there was a rare case that
12592 stomped on memory, triggering seg faults and asserts.
12593 - Avoid potential infinite recursion when building a descriptor. (We
12594 don't know that it ever happened, but better to fix it anyway.)
12595 - We were neglecting to unlink marked circuits from soon-to-close OR
12596 connections, which caused some rare scribbling on freed memory.
12597 - Fix a memory stomping race bug when closing the joining point of two
12598 rendezvous circuits.
12599 - Fix an assert in time parsing found by Steven Murdoch.
12601 o Other bugfixes on 0.1.0.x:
12602 - When we're doing reachability testing, provide more useful log
12603 messages so the operator knows what to expect.
12604 - Do not check whether DirPort is reachable when we are suppressing
12605 advertising it because of hibernation.
12606 - When building with -static or on Solaris, we sometimes needed -ldl.
12607 - When we're deciding whether a stream has enough circuits around
12608 that can handle it, count the freshly dirty ones and not the ones
12609 that are so dirty they won't be able to handle it.
12610 - When we're expiring old circuits, we had a logic error that caused
12611 us to close new rendezvous circuits rather than old ones.
12612 - Give a more helpful log message when you try to change ORPort via
12613 the controller: you should upgrade Tor if you want that to work.
12614 - We were failing to parse Tor versions that start with "Tor ".
12615 - Tolerate faulty streams better: when a stream fails for reason
12616 exitpolicy, stop assuming that the router is lying about his exit
12617 policy. When a stream fails for reason misc, allow it to retry just
12618 as if it was resolvefailed. When a stream has failed three times,
12619 reset its failure count so we can try again and get all three tries.
12622 Changes in version 0.1.1.10-alpha - 2005-12-11
12623 o Correctness bugfixes on 0.1.0.x:
12624 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12625 corrupting the heap, losing FDs, or crashing when we need to resize
12626 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12627 - Stop doing the complex voodoo overkill checking for insecure
12628 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12629 - When we were closing connections, there was a rare case that
12630 stomped on memory, triggering seg faults and asserts.
12631 - We were neglecting to unlink marked circuits from soon-to-close OR
12632 connections, which caused some rare scribbling on freed memory.
12633 - When we're deciding whether a stream has enough circuits around
12634 that can handle it, count the freshly dirty ones and not the ones
12635 that are so dirty they won't be able to handle it.
12636 - Recover better from TCP connections to Tor servers that are
12637 broken but don't tell you (it happens!); and rotate TLS
12638 connections once a week.
12639 - When we're expiring old circuits, we had a logic error that caused
12640 us to close new rendezvous circuits rather than old ones.
12641 - Fix a scary-looking but apparently harmless bug where circuits
12642 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12643 servers, and never switch to state CIRCUIT_STATE_OPEN.
12644 - When building with -static or on Solaris, we sometimes needed to
12646 - Give a useful message when people run Tor as the wrong user,
12647 rather than telling them to start chowning random directories.
12648 - We were failing to inform the controller about new .onion streams.
12650 o Security bugfixes on 0.1.0.x:
12651 - Refuse server descriptors if the fingerprint line doesn't match
12652 the included identity key. Tor doesn't care, but other apps (and
12653 humans) might actually be trusting the fingerprint line.
12654 - We used to kill the circuit when we receive a relay command we
12655 don't recognize. Now we just drop it.
12656 - Start obeying our firewall options more rigorously:
12657 . If we can't get to a dirserver directly, try going via Tor.
12658 . Don't ever try to connect (as a client) to a place our
12659 firewall options forbid.
12660 . If we specify a proxy and also firewall options, obey the
12661 firewall options even when we're using the proxy: some proxies
12662 can only proxy to certain destinations.
12663 - Fix a bug found by Lasse Overlier: when we were making internal
12664 circuits (intended to be cannibalized later for rendezvous and
12665 introduction circuits), we were picking them so that they had
12666 useful exit nodes. There was no need for this, and it actually
12667 aids some statistical attacks.
12668 - Start treating internal circuits and exit circuits separately.
12669 It's important to keep them separate because internal circuits
12670 have their last hops picked like middle hops, rather than like
12671 exit hops. So exiting on them will break the user's expectations.
12673 o Bugfixes on 0.1.1.x:
12674 - Take out the mis-feature where we tried to detect IP address
12675 flapping for people with DynDNS, and chose not to upload a new
12676 server descriptor sometimes.
12677 - Try to be compatible with OpenSSL 0.9.6 again.
12678 - Log fix: when the controller is logging about .onion addresses,
12679 sometimes it didn't include the ".onion" part of the address.
12680 - Don't try to modify options->DirServers internally -- if the
12681 user didn't specify any, just add the default ones directly to
12682 the trusted dirserver list. This fixes a bug where people running
12683 controllers would use SETCONF on some totally unrelated config
12684 option, and Tor would start yelling at them about changing their
12686 - Let the controller's redirectstream command specify a port, in
12687 case the controller wants to change that too.
12688 - When we requested a pile of server descriptors, we sometimes
12689 accidentally launched a duplicate request for the first one.
12690 - Bugfix for trackhostexits: write down the fingerprint of the
12691 chosen exit, not its nickname, because the chosen exit might not
12693 - When parsing foo.exit, if foo is unknown, and we are leaving
12694 circuits unattached, set the chosen_exit field and leave the
12695 address empty. This matters because controllers got confused
12697 - Directory authorities no longer try to download server
12698 descriptors that they know they will reject.
12700 o Features and updates:
12701 - Replace balanced trees with hash tables: this should make stuff
12702 significantly faster.
12703 - Resume using the AES counter-mode implementation that we ship,
12704 rather than OpenSSL's. Ours is significantly faster.
12705 - Many other CPU and memory improvements.
12706 - Add a new config option FastFirstHopPK (on by default) so clients
12707 do a trivial crypto handshake for their first hop, since TLS has
12708 already taken care of confidentiality and authentication.
12709 - Add a new config option TestSocks so people can see if their
12710 applications are using socks4, socks4a, socks5-with-ip, or
12711 socks5-with-hostname. This way they don't have to keep mucking
12712 with tcpdump and wondering if something got cached somewhere.
12713 - Warn when listening on a public address for socks. I suspect a
12714 lot of people are setting themselves up as open socks proxies,
12715 and they have no idea that jerks on the Internet are using them,
12716 since they simply proxy the traffic into the Tor network.
12717 - Add "private:*" as an alias in configuration for policies. Now
12718 you can simplify your exit policy rather than needing to list
12719 every single internal or nonroutable network space.
12720 - Add a new controller event type that allows controllers to get
12721 all server descriptors that were uploaded to a router in its role
12722 as authoritative dirserver.
12723 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12724 tor-doc-server.html, and stylesheet.css in the tarball.
12725 - Stop shipping tor-doc.html in the tarball.
12728 Changes in version 0.1.1.9-alpha - 2005-11-15
12729 o Usability improvements:
12730 - Start calling it FooListenAddress rather than FooBindAddress,
12731 since few of our users know what it means to bind an address
12733 - Reduce clutter in server logs. We're going to try to make
12734 them actually usable now. New config option ProtocolWarnings that
12735 lets you hear about how _other Tors_ are breaking the protocol. Off
12737 - Divide log messages into logging domains. Once we put some sort
12738 of interface on this, it will let people looking at more verbose
12739 log levels specify the topics they want to hear more about.
12740 - Make directory servers return better http 404 error messages
12741 instead of a generic "Servers unavailable".
12742 - Check for even more Windows version flags when writing the platform
12743 string in server descriptors, and note any we don't recognize.
12744 - Clean up more of the OpenSSL memory when exiting, so we can detect
12745 memory leaks better.
12746 - Make directory authorities be non-versioning, non-naming by
12747 default. Now we can add new directory servers without requiring
12748 their operators to pay close attention.
12749 - When logging via syslog, include the pid whenever we provide
12750 a log entry. Suggested by Todd Fries.
12752 o Performance improvements:
12753 - Directory servers now silently throw away new descriptors that
12754 haven't changed much if the timestamps are similar. We do this to
12755 tolerate older Tor servers that upload a new descriptor every 15
12756 minutes. (It seemed like a good idea at the time.)
12757 - Inline bottleneck smartlist functions; use fast versions by default.
12758 - Add a "Map from digest to void*" abstraction digestmap_t so we
12759 can do less hex encoding/decoding. Use it in router_get_by_digest()
12760 to resolve a performance bottleneck.
12761 - Allow tor_gzip_uncompress to extract as much as possible from
12762 truncated compressed data. Try to extract as many
12763 descriptors as possible from truncated http responses (when
12764 DIR_PURPOSE_FETCH_ROUTERDESC).
12765 - Make circ->onionskin a pointer, not a static array. moria2 was using
12766 125000 circuit_t's after it had been up for a few weeks, which
12767 translates to 20+ megs of wasted space.
12768 - The private half of our EDH handshake keys are now chosen out
12769 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12771 o Security improvements:
12772 - Start making directory caches retain old routerinfos, so soon
12773 clients can start asking by digest of descriptor rather than by
12774 fingerprint of server.
12775 - Add half our entropy from RAND_poll in OpenSSL. This knows how
12776 to use egd (if present), openbsd weirdness (if present), vms/os2
12777 weirdness (if we ever port there), and more in the future.
12779 o Bugfixes on 0.1.0.x:
12780 - Do round-robin writes of at most 16 kB per write. This might be
12781 more fair on loaded Tor servers, and it might resolve our Windows
12782 crash bug. It might also slow things down.
12783 - Our TLS handshakes were generating a single public/private
12784 keypair for the TLS context, rather than making a new one for
12785 each new connections. Oops. (But we were still rotating them
12786 periodically, so it's not so bad.)
12787 - When we were cannibalizing a circuit with a particular exit
12788 node in mind, we weren't checking to see if that exit node was
12789 already present earlier in the circuit. Oops.
12790 - When a Tor server's IP changes (e.g. from a dyndns address),
12791 upload a new descriptor so clients will learn too.
12792 - Really busy servers were keeping enough circuits open on stable
12793 connections that they were wrapping around the circuit_id
12794 space. (It's only two bytes.) This exposed a bug where we would
12795 feel free to reuse a circuit_id even if it still exists but has
12796 been marked for close. Try to fix this bug. Some bug remains.
12797 - If we would close a stream early (e.g. it asks for a .exit that
12798 we know would refuse it) but the LeaveStreamsUnattached config
12799 option is set by the controller, then don't close it.
12801 o Bugfixes on 0.1.1.8-alpha:
12802 - Fix a big pile of memory leaks, some of them serious.
12803 - Do not try to download a routerdesc if we would immediately reject
12805 - Resume inserting a newline between all router descriptors when
12806 generating (old style) signed directories, since our spec says
12808 - When providing content-type application/octet-stream for
12809 server descriptors using .z, we were leaving out the
12810 content-encoding header. Oops. (Everything tolerated this just
12811 fine, but that doesn't mean we need to be part of the problem.)
12812 - Fix a potential seg fault in getconf and getinfo using version 1
12813 of the controller protocol.
12814 - Avoid crash: do not check whether DirPort is reachable when we
12815 are suppressing it because of hibernation.
12816 - Make --hash-password not crash on exit.
12819 Changes in version 0.1.1.8-alpha - 2005-10-07
12820 o New features (major):
12821 - Clients don't download or use the directory anymore. Now they
12822 download and use network-statuses from the trusted dirservers,
12823 and fetch individual server descriptors as needed from mirrors.
12824 See dir-spec.txt for all the gory details.
12825 - Be more conservative about whether to advertise our DirPort.
12826 The main change is to not advertise if we're running at capacity
12827 and either a) we could hibernate or b) our capacity is low and
12828 we're using a default DirPort.
12829 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
12831 o New features (minor):
12832 - Try to be smart about when to retry network-status and
12833 server-descriptor fetches. Still needs some tuning.
12834 - Stop parsing, storing, or using running-routers output (but
12835 mirrors still cache and serve it).
12836 - Consider a threshold of versioning dirservers (dirservers who have
12837 an opinion about which Tor versions are still recommended) before
12838 deciding whether to warn the user that he's obsolete.
12839 - Dirservers can now reject/invalidate by key and IP, with the
12840 config options "AuthDirInvalid" and "AuthDirReject". This is
12841 useful since currently we automatically list servers as running
12842 and usable even if we know they're jerks.
12843 - Provide dire warnings to any users who set DirServer; move it out
12844 of torrc.sample and into torrc.complete.
12845 - Add MyFamily to torrc.sample in the server section.
12846 - Add nicknames to the DirServer line, so we can refer to them
12847 without requiring all our users to memorize their IP addresses.
12848 - When we get an EOF or a timeout on a directory connection, note
12849 how many bytes of serverdesc we are dropping. This will help
12850 us determine whether it is smart to parse incomplete serverdesc
12852 - Add a new function to "change pseudonyms" -- that is, to stop
12853 using any currently-dirty circuits for new streams, so we don't
12854 link new actions to old actions. Currently it's only called on
12855 HUP (or SIGNAL RELOAD).
12856 - On sighup, if UseHelperNodes changed to 1, use new circuits.
12857 - Start using RAND_bytes rather than RAND_pseudo_bytes from
12858 OpenSSL. Also, reseed our entropy every hour, not just at
12859 startup. And entropy in 512-bit chunks, not 160-bit chunks.
12861 o Fixes on 0.1.1.7-alpha:
12862 - Nobody ever implemented EVENT_ADDRMAP for control protocol
12863 version 0, so don't let version 0 controllers ask for it.
12864 - If you requested something with too many newlines via the
12865 v1 controller protocol, you could crash tor.
12866 - Fix a number of memory leaks, including some pretty serious ones.
12867 - Re-enable DirPort testing again, so Tor servers will be willing
12868 to advertise their DirPort if it's reachable.
12869 - On TLS handshake, only check the other router's nickname against
12870 its expected nickname if is_named is set.
12872 o Fixes forward-ported from 0.1.0.15:
12873 - Don't crash when we don't have any spare file descriptors and we
12874 try to spawn a dns or cpu worker.
12875 - Make the numbers in read-history and write-history into uint64s,
12876 so they don't overflow and publish negatives in the descriptor.
12878 o Fixes on 0.1.0.x:
12879 - For the OS X package's modified privoxy config file, comment
12880 out the "logfile" line so we don't log everything passed
12882 - We were whining about using socks4 or socks5-with-local-lookup
12883 even when it's an IP in the "virtual" range we designed exactly
12885 - We were leaking some memory every time the client changes IPs.
12886 - Never call free() on tor_malloc()d memory. This will help us
12887 use dmalloc to detect memory leaks.
12888 - Check for named servers when looking them up by nickname;
12889 warn when we'recalling a non-named server by its nickname;
12890 don't warn twice about the same name.
12891 - Try to list MyFamily elements by key, not by nickname, and warn
12892 if we've not heard of the server.
12893 - Make windows platform detection (uname equivalent) smarter.
12894 - It turns out sparc64 doesn't like unaligned access either.
12897 Changes in version 0.1.0.15 - 2005-09-23
12898 o Bugfixes on 0.1.0.x:
12899 - Reject ports 465 and 587 (spam targets) in default exit policy.
12900 - Don't crash when we don't have any spare file descriptors and we
12901 try to spawn a dns or cpu worker.
12902 - Get rid of IgnoreVersion undocumented config option, and make us
12903 only warn, never exit, when we're running an obsolete version.
12904 - Don't try to print a null string when your server finds itself to
12905 be unreachable and the Address config option is empty.
12906 - Make the numbers in read-history and write-history into uint64s,
12907 so they don't overflow and publish negatives in the descriptor.
12908 - Fix a minor memory leak in smartlist_string_remove().
12909 - We were only allowing ourselves to upload a server descriptor at
12910 most every 20 minutes, even if it changed earlier than that.
12911 - Clean up log entries that pointed to old URLs.
12914 Changes in version 0.1.1.7-alpha - 2005-09-14
12915 o Fixes on 0.1.1.6-alpha:
12916 - Exit servers were crashing when people asked them to make a
12917 connection to an address not in their exit policy.
12918 - Looking up a non-existent stream for a v1 control connection would
12920 - Fix a seg fault if we ask a dirserver for a descriptor by
12921 fingerprint but he doesn't know about him.
12922 - SETCONF was appending items to linelists, not clearing them.
12923 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
12924 out and refuse the setconf if it would fail.
12925 - Downgrade the dirserver log messages when whining about
12929 - Add Peter Palfrader's check-tor script to tor/contrib/
12930 It lets you easily check whether a given server (referenced by
12931 nickname) is reachable by you.
12932 - Numerous changes to move towards client-side v2 directories. Not
12935 o Fixes on 0.1.0.x:
12936 - If the user gave tor an odd number of command-line arguments,
12937 we were silently ignoring the last one. Now we complain and fail.
12938 [This wins the oldest-bug prize -- this bug has been present since
12939 November 2002, as released in Tor 0.0.0.]
12940 - Do not use unaligned memory access on alpha, mips, or mipsel.
12941 It *works*, but is very slow, so we treat them as if it doesn't.
12942 - Retry directory requests if we fail to get an answer we like
12943 from a given dirserver (we were retrying before, but only if
12944 we fail to connect).
12945 - When writing the RecommendedVersions line, sort them first.
12946 - When the client asked for a rendezvous port that the hidden
12947 service didn't want to provide, we were sending an IP address
12948 back along with the end cell. Fortunately, it was zero. But stop
12950 - Correct "your server is reachable" log entries to indicate that
12951 it was self-testing that told us so.
12954 Changes in version 0.1.1.6-alpha - 2005-09-09
12955 o Fixes on 0.1.1.5-alpha:
12956 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
12957 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
12958 - Fix bug with tor_memmem finding a match at the end of the string.
12959 - Make unit tests run without segfaulting.
12960 - Resolve some solaris x86 compile warnings.
12961 - Handle duplicate lines in approved-routers files without warning.
12962 - Fix bug where as soon as a server refused any requests due to his
12963 exit policy (e.g. when we ask for localhost and he tells us that's
12964 127.0.0.1 and he won't do it), we decided he wasn't obeying his
12965 exit policy using him for any exits.
12966 - Only do openssl hardware accelerator stuff if openssl version is
12969 o New controller features/fixes:
12970 - Add a "RESETCONF" command so you can set config options like
12971 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12972 a config option in the torrc with no value, then it clears it
12973 entirely (rather than setting it to its default).
12974 - Add a "GETINFO config-file" to tell us where torrc is.
12975 - Avoid sending blank lines when GETINFO replies should be empty.
12976 - Add a QUIT command for the controller (for using it manually).
12977 - Fix a bug in SAVECONF that was adding default dirservers and
12978 other redundant entries to the torrc file.
12980 o Start on the new directory design:
12981 - Generate, publish, cache, serve new network-status format.
12982 - Publish individual descriptors (by fingerprint, by "all", and by
12984 - Publish client and server recommended versions separately.
12985 - Allow tor_gzip_uncompress() to handle multiple concatenated
12986 compressed strings. Serve compressed groups of router
12987 descriptors. The compression logic here could be more
12989 - Distinguish v1 authorities (all currently trusted directories)
12990 from v2 authorities (all trusted directories).
12991 - Change DirServers config line to note which dirs are v1 authorities.
12992 - Add configuration option "V1AuthoritativeDirectory 1" which
12993 moria1, moria2, and tor26 should set.
12994 - Remove option when getting directory cache to see whether they
12995 support running-routers; they all do now. Replace it with one
12996 to see whether caches support v2 stuff.
12999 - Dirservers now do their own external reachability testing of each
13000 Tor server, and only list them as running if they've been found to
13001 be reachable. We also send back warnings to the server's logs if
13002 it uploads a descriptor that we already believe is unreachable.
13003 - Implement exit enclaves: if we know an IP address for the
13004 destination, and there's a running Tor server at that address
13005 which allows exit to the destination, then extend the circuit to
13006 that exit first. This provides end-to-end encryption and end-to-end
13007 authentication. Also, if the user wants a .exit address or enclave,
13008 use 4 hops rather than 3, and cannibalize a general circ for it
13010 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13011 controller. Also, rotate dns and cpu workers if the controller
13012 changes options that will affect them; and initialize the dns
13013 worker cache tree whether or not we start out as a server.
13014 - Only upload a new server descriptor when options change, 18
13015 hours have passed, uptime is reset, or bandwidth changes a lot.
13016 - Check [X-]Forwarded-For headers in HTTP requests when generating
13017 log messages. This lets people run dirservers (and caches) behind
13018 Apache but still know which IP addresses are causing warnings.
13020 o Config option changes:
13021 - Replace (Fascist)Firewall* config options with a new
13022 ReachableAddresses option that understands address policies.
13023 For example, "ReachableAddresses *:80,*:443"
13024 - Get rid of IgnoreVersion undocumented config option, and make us
13025 only warn, never exit, when we're running an obsolete version.
13026 - Make MonthlyAccountingStart config option truly obsolete now.
13028 o Fixes on 0.1.0.x:
13029 - Reject ports 465 and 587 in the default exit policy, since
13030 people have started using them for spam too.
13031 - It turns out we couldn't bootstrap a network since we added
13032 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13033 has never gone down. Add an AssumeReachable config option to let
13034 servers and dirservers bootstrap. When we're trying to build a
13035 high-uptime or high-bandwidth circuit but there aren't enough
13036 suitable servers, try being less picky rather than simply failing.
13037 - Our logic to decide if the OR we connected to was the right guy
13038 was brittle and maybe open to a mitm for unverified routers.
13039 - We weren't cannibalizing circuits correctly for
13040 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13041 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13042 build those from scratch. This should make hidden services faster.
13043 - Predict required circuits better, with an eye toward making hidden
13044 services faster on the service end.
13045 - Retry streams if the exit node sends back a 'misc' failure. This
13046 should result in fewer random failures. Also, after failing
13047 from resolve failed or misc, reset the num failures, so we give
13048 it a fair shake next time we try.
13049 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13050 - Reduce severity on logs about dns worker spawning and culling.
13051 - When we're shutting down and we do something like try to post a
13052 server descriptor or rendezvous descriptor, don't complain that
13053 we seem to be unreachable. Of course we are, we're shutting down.
13054 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13055 We don't use them yet, but maybe one day our DNS resolver will be
13056 able to discover them.
13057 - Make ContactInfo mandatory for authoritative directory servers.
13058 - Require server descriptors to list IPv4 addresses -- hostnames
13059 are no longer allowed. This also fixes some potential security
13060 problems with people providing hostnames as their address and then
13061 preferentially resolving them to partition users.
13062 - Change log line for unreachability to explicitly suggest /etc/hosts
13063 as the culprit. Also make it clearer what IP address and ports we're
13064 testing for reachability.
13065 - Put quotes around user-supplied strings when logging so users are
13066 more likely to realize if they add bad characters (like quotes)
13068 - Let auth dir servers start without specifying an Address config
13070 - Make unit tests (and other invocations that aren't the real Tor)
13071 run without launching listeners, creating subdirectories, and so on.
13074 Changes in version 0.1.1.5-alpha - 2005-08-08
13075 o Bugfixes included in 0.1.0.14.
13077 o Bugfixes on 0.1.0.x:
13078 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13079 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13080 it would silently using ignore the 6668.
13083 Changes in version 0.1.0.14 - 2005-08-08
13084 o Bugfixes on 0.1.0.x:
13085 - Fix the other half of the bug with crypto handshakes
13087 - Fix an assert trigger if you send a 'signal term' via the
13088 controller when it's listening for 'event info' messages.
13091 Changes in version 0.1.1.4-alpha - 2005-08-04
13092 o Bugfixes included in 0.1.0.13.
13095 - Improve tor_gettimeofday() granularity on windows.
13096 - Make clients regenerate their keys when their IP address changes.
13097 - Implement some more GETINFO goodness: expose helper nodes, config
13098 options, getinfo keys.
13101 Changes in version 0.1.0.13 - 2005-08-04
13102 o Bugfixes on 0.1.0.x:
13103 - Fix a critical bug in the security of our crypto handshakes.
13104 - Fix a size_t underflow in smartlist_join_strings2() that made
13105 it do bad things when you hand it an empty smartlist.
13106 - Fix Windows installer to ship Tor license (thanks to Aphex for
13107 pointing out this oversight) and put a link to the doc directory
13109 - Explicitly set no-unaligned-access for sparc: it turns out the
13110 new gcc's let you compile broken code, but that doesn't make it
13114 Changes in version 0.1.1.3-alpha - 2005-07-23
13115 o Bugfixes on 0.1.1.2-alpha:
13116 - Fix a bug in handling the controller's "post descriptor"
13118 - Fix several bugs in handling the controller's "extend circuit"
13120 - Fix a bug in handling the controller's "stream status" event.
13121 - Fix an assert failure if we have a controller listening for
13122 circuit events and we go offline.
13123 - Re-allow hidden service descriptors to publish 0 intro points.
13124 - Fix a crash when generating your hidden service descriptor if
13125 you don't have enough intro points already.
13127 o New features on 0.1.1.2-alpha:
13128 - New controller function "getinfo accounting", to ask how
13129 many bytes we've used in this time period.
13130 - Experimental support for helper nodes: a lot of the risk from
13131 a small static adversary comes because users pick new random
13132 nodes every time they rebuild a circuit. Now users will try to
13133 stick to the same small set of entry nodes if they can. Not
13134 enabled by default yet.
13136 o Bugfixes on 0.1.0.12:
13137 - If you're an auth dir server, always publish your dirport,
13138 even if you haven't yet found yourself to be reachable.
13139 - Fix a size_t underflow in smartlist_join_strings2() that made
13140 it do bad things when you hand it an empty smartlist.
13143 Changes in version 0.1.0.12 - 2005-07-18
13144 o New directory servers:
13145 - tor26 has changed IP address.
13147 o Bugfixes on 0.1.0.x:
13148 - Fix a possible double-free in tor_gzip_uncompress().
13149 - When --disable-threads is set, do not search for or link against
13150 pthreads libraries.
13151 - Don't trigger an assert if an authoritative directory server
13152 claims its dirport is 0.
13153 - Fix bug with removing Tor as an NT service: some people were
13154 getting "The service did not return an error." Thanks to Matt
13158 Changes in version 0.1.1.2-alpha - 2005-07-15
13159 o New directory servers:
13160 - tor26 has changed IP address.
13162 o Bugfixes on 0.1.0.x, crashes/leaks:
13163 - Port the servers-not-obeying-their-exit-policies fix from
13165 - Fix an fd leak in start_daemon().
13166 - On Windows, you can't always reopen a port right after you've
13167 closed it. So change retry_listeners() to only close and re-open
13168 ports that have changed.
13169 - Fix a possible double-free in tor_gzip_uncompress().
13171 o Bugfixes on 0.1.0.x, usability:
13172 - When tor_socketpair() fails in Windows, give a reasonable
13173 Windows-style errno back.
13174 - Let people type "tor --install" as well as "tor -install" when
13176 want to make it an NT service.
13177 - NT service patch from Matt Edman to improve error messages.
13178 - When the controller asks for a config option with an abbreviated
13179 name, give the full name in our response.
13180 - Correct the man page entry on TrackHostExitsExpire.
13181 - Looks like we were never delivering deflated (i.e. compressed)
13182 running-routers lists, even when asked. Oops.
13183 - When --disable-threads is set, do not search for or link against
13184 pthreads libraries.
13186 o Bugfixes on 0.1.1.x:
13187 - Fix a seg fault with autodetecting which controller version is
13191 - New hidden service descriptor format: put a version in it, and
13192 let people specify introduction/rendezvous points that aren't
13193 in "the directory" (which is subjective anyway).
13194 - Allow the DEBUG controller event to work again. Mark certain log
13195 entries as "don't tell this to controllers", so we avoid cycles.
13198 Changes in version 0.1.0.11 - 2005-06-30
13199 o Bugfixes on 0.1.0.x:
13200 - Fix major security bug: servers were disregarding their
13201 exit policies if clients behaved unexpectedly.
13202 - Make OS X init script check for missing argument, so we don't
13203 confuse users who invoke it incorrectly.
13204 - Fix a seg fault in "tor --hash-password foo".
13205 - The MAPADDRESS control command was broken.
13208 Changes in version 0.1.1.1-alpha - 2005-06-29
13210 - Make OS X init script check for missing argument, so we don't
13211 confuse users who invoke it incorrectly.
13212 - Fix a seg fault in "tor --hash-password foo".
13213 - Fix a possible way to DoS dirservers.
13214 - When we complain that your exit policy implicitly allows local or
13215 private address spaces, name them explicitly so operators can
13217 - Make the log message less scary when all the dirservers are
13218 temporarily unreachable.
13219 - We were printing the number of idle dns workers incorrectly when
13223 - Revised controller protocol (version 1) that uses ascii rather
13224 than binary. Add supporting libraries in python and java so you
13225 can use the controller from your applications without caring how
13226 our protocol works.
13227 - Spiffy new support for crypto hardware accelerators. Can somebody
13231 Changes in version 0.0.9.10 - 2005-06-16
13232 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13233 - Refuse relay cells that claim to have a length larger than the
13234 maximum allowed. This prevents a potential attack that could read
13235 arbitrary memory (e.g. keys) from an exit server's process
13239 Changes in version 0.1.0.10 - 2005-06-14
13240 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13241 libevent before 1.1a.
13244 Changes in version 0.1.0.9-rc - 2005-06-09
13246 - Reset buf->highwater every time buf_shrink() is called, not just on
13247 a successful shrink. This was causing significant memory bloat.
13248 - Fix buffer overflow when checking hashed passwords.
13249 - Security fix: if seeding the RNG on Win32 fails, quit.
13250 - Allow seeding the RNG on Win32 even when you're not running as
13252 - Disable threading on Solaris too. Something is wonky with it,
13253 cpuworkers, and reentrant libs.
13254 - Reenable the part of the code that tries to flush as soon as an
13255 OR outbuf has a full TLS record available. Perhaps this will make
13256 OR outbufs not grow as huge except in rare cases, thus saving lots
13257 of CPU time plus memory.
13258 - Reject malformed .onion addresses rather then passing them on as
13259 normal web requests.
13260 - Adapt patch from Adam Langley: fix possible memory leak in
13261 tor_lookup_hostname().
13262 - Initialize libevent later in the startup process, so the logs are
13263 already established by the time we start logging libevent warns.
13264 - Use correct errno on win32 if libevent fails.
13265 - Check and warn about known-bad/slow libevent versions.
13266 - Pay more attention to the ClientOnly config option.
13267 - Have torctl.in/tor.sh.in check for location of su binary (needed
13269 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13270 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13271 HttpProxyAuthenticator
13272 - Stop warning about sigpipes in the logs. We're going to
13273 pretend that getting these occassionally is normal and fine.
13274 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13276 installer screens; and don't put stuff into StartupItems unless
13277 the user asks you to.
13278 - Require servers that use the default dirservers to have public IP
13279 addresses. We have too many servers that are configured with private
13280 IPs and their admins never notice the log entries complaining that
13281 their descriptors are being rejected.
13282 - Add OSX uninstall instructions. An actual uninstall script will
13286 Changes in version 0.1.0.8-rc - 2005-05-23
13288 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13289 panics. Disable kqueue on all OS X Tors.
13290 - Fix RPM: remove duplicate line accidentally added to the rpm
13292 - Disable threads on openbsd too, since its gethostaddr is not
13294 - Tolerate libevent 0.8 since it still works, even though it's
13296 - Enable building on Red Hat 9.0 again.
13297 - Allow the middle hop of the testing circuit to be running any
13298 version, now that most of them have the bugfix to let them connect
13299 to unknown servers. This will allow reachability testing to work
13300 even when 0.0.9.7-0.0.9.9 become obsolete.
13301 - Handle relay cells with rh.length too large. This prevents
13302 a potential attack that could read arbitrary memory (maybe even
13303 keys) from the exit server's process.
13304 - We screwed up the dirport reachability testing when we don't yet
13305 have a cached version of the directory. Hopefully now fixed.
13306 - Clean up router_load_single_router() (used by the controller),
13307 so it doesn't seg fault on error.
13308 - Fix a minor memory leak when somebody establishes an introduction
13309 point at your Tor server.
13310 - If a socks connection ends because read fails, don't warn that
13311 you're not sending a socks reply back.
13314 - Add HttpProxyAuthenticator config option too, that works like
13315 the HttpsProxyAuthenticator config option.
13316 - Encode hashed controller passwords in hex instead of base64,
13317 to make it easier to write controllers.
13320 Changes in version 0.1.0.7-rc - 2005-05-17
13322 - Fix a bug in the OS X package installer that prevented it from
13323 installing on Tiger.
13324 - Fix a script bug in the OS X package installer that made it
13325 complain during installation.
13326 - Find libevent even if it's hiding in /usr/local/ and your
13327 CFLAGS and LDFLAGS don't tell you to look there.
13328 - Be able to link with libevent as a shared library (the default
13329 after 1.0d), even if it's hiding in /usr/local/lib and even
13330 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13331 assuming you're running gcc. Otherwise fail and give a useful
13333 - Fix a bug in the RPM packager: set home directory for _tor to
13334 something more reasonable when first installing.
13335 - Free a minor amount of memory that is still reachable on exit.
13338 Changes in version 0.1.0.6-rc - 2005-05-14
13340 - Implement --disable-threads configure option. Disable threads on
13341 netbsd by default, because it appears to have no reentrant resolver
13343 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13344 release (1.1) detects and disables kqueue if it's broken.
13345 - Append default exit policy before checking for implicit internal
13346 addresses. Now we don't log a bunch of complaints on startup
13347 when using the default exit policy.
13348 - Some people were putting "Address " in their torrc, and they had
13349 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13350 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13351 LOCALSTATEDIR/tor instead.
13352 - Fix fragmented-message bug in TorControl.py.
13353 - Resolve a minor bug which would prevent unreachable dirports
13354 from getting suppressed in the published descriptor.
13355 - When the controller gave us a new descriptor, we weren't resolving
13356 it immediately, so Tor would think its address was 0.0.0.0 until
13357 we fetched a new directory.
13358 - Fix an uppercase/lowercase case error in suppressing a bogus
13359 libevent warning on some Linuxes.
13362 - Begin scrubbing sensitive strings from logs by default. Turn off
13363 the config option SafeLogging if you need to do debugging.
13364 - Switch to a new buffer management algorithm, which tries to avoid
13365 reallocing and copying quite as much. In first tests it looks like
13366 it uses *more* memory on average, but less cpu.
13367 - First cut at support for "create-fast" cells. Clients can use
13368 these when extending to their first hop, since the TLS already
13369 provides forward secrecy and authentication. Not enabled on
13371 - When dirservers refuse a router descriptor, we now log its
13372 contactinfo, platform, and the poster's IP address.
13373 - Call tor_free_all instead of connections_free_all after forking, to
13374 save memory on systems that need to fork.
13375 - Whine at you if you're a server and you don't set your contactinfo.
13376 - Implement --verify-config command-line option to check if your torrc
13377 is valid without actually launching Tor.
13378 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13379 rather than just rejecting it.
13382 Changes in version 0.1.0.5-rc - 2005-04-27
13384 - Stop trying to print a null pointer if an OR conn fails because
13385 we didn't like its cert.
13387 - Switch our internal buffers implementation to use a ring buffer,
13388 to hopefully improve performance for fast servers a lot.
13389 - Add HttpsProxyAuthenticator support (basic auth only), based
13390 on patch from Adam Langley.
13391 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13392 the fast servers that have been joining lately.
13393 - Give hidden service accesses extra time on the first attempt,
13394 since 60 seconds is often only barely enough. This might improve
13396 - Improve performance for dirservers: stop re-parsing the whole
13397 directory every time you regenerate it.
13398 - Add more debugging info to help us find the weird dns freebsd
13399 pthreads bug; cleaner debug messages to help track future issues.
13402 Changes in version 0.0.9.9 - 2005-04-23
13403 o Bugfixes on 0.0.9.x:
13404 - If unofficial Tor clients connect and send weird TLS certs, our
13405 Tor server triggers an assert. This release contains a minimal
13406 backport from the broader fix that we put into 0.1.0.4-rc.
13409 Changes in version 0.1.0.4-rc - 2005-04-23
13411 - If unofficial Tor clients connect and send weird TLS certs, our
13412 Tor server triggers an assert. Stop asserting, and start handling
13413 TLS errors better in other situations too.
13414 - When the controller asks us to tell it about all the debug-level
13415 logs, it turns out we were generating debug-level logs while
13416 telling it about them, which turns into a bad loop. Now keep
13417 track of whether you're sending a debug log to the controller,
13418 and don't log when you are.
13419 - Fix the "postdescriptor" feature of the controller interface: on
13420 non-complete success, only say "done" once.
13422 - Clients are now willing to load balance over up to 2mB, not 1mB,
13423 of advertised bandwidth capacity.
13424 - Add a NoPublish config option, so you can be a server (e.g. for
13425 testing running Tor servers in other Tor networks) without
13426 publishing your descriptor to the primary dirservers.
13429 Changes in version 0.1.0.3-rc - 2005-04-08
13430 o Improvements on 0.1.0.2-rc:
13431 - Client now retries when streams end early for 'hibernating' or
13432 'resource limit' reasons, rather than failing them.
13433 - More automated handling for dirserver operators:
13434 - Automatically approve nodes running 0.1.0.2-rc or later,
13435 now that the the reachability detection stuff is working.
13436 - Now we allow two unverified servers with the same nickname
13437 but different keys. But if a nickname is verified, only that
13438 nickname+key are allowed.
13439 - If you're an authdirserver connecting to an address:port,
13440 and it's not the OR you were expecting, forget about that
13441 descriptor. If he *was* the one you were expecting, then forget
13442 about all other descriptors for that address:port.
13443 - Allow servers to publish descriptors from 12 hours in the future.
13444 Corollary: only whine about clock skew from the dirserver if
13445 he's a trusted dirserver (since now even verified servers could
13446 have quite wrong clocks).
13447 - Adjust maximum skew and age for rendezvous descriptors: let skew
13448 be 48 hours rather than 90 minutes.
13449 - Efficiency improvements:
13450 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13451 it much faster to look up a circuit for each relay cell.
13452 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13453 since they're eating our cpu on exit nodes.
13454 - Stop wasting time doing a case insensitive comparison for every
13455 dns name every time we do any lookup. Canonicalize the names to
13456 lowercase and be done with it.
13457 - Start sending 'truncated' cells back rather than destroy cells,
13458 if the circuit closes in front of you. This means we won't have
13459 to abandon partially built circuits.
13460 - Only warn once per nickname from add_nickname_list_to_smartlist
13461 per failure, so an entrynode or exitnode choice that's down won't
13463 - Put a note in the torrc about abuse potential with the default
13465 - Revise control spec and implementation to allow all log messages to
13466 be sent to controller with their severities intact (suggested by
13467 Matt Edman). Update TorControl to handle new log event types.
13468 - Provide better explanation messages when controller's POSTDESCRIPTOR
13470 - Stop putting nodename in the Platform string in server descriptors.
13471 It doesn't actually help, and it is confusing/upsetting some people.
13473 o Bugfixes on 0.1.0.2-rc:
13474 - We were printing the host mask wrong in exit policies in server
13475 descriptors. This isn't a critical bug though, since we were still
13476 obeying the exit policy internally.
13477 - Fix Tor when compiled with libevent but without pthreads: move
13478 connection_unregister() from _connection_free() to
13480 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13481 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13482 when we look through the connection array, we'll find any of the
13483 cpu/dnsworkers. This is no good.
13485 o Bugfixes on 0.0.9.8:
13486 - Fix possible bug on threading platforms (e.g. win32) which was
13487 leaking a file descriptor whenever a cpuworker or dnsworker died.
13488 - When using preferred entry or exit nodes, ignore whether the
13489 circuit wants uptime or capacity. They asked for the nodes, they
13491 - chdir() to your datadirectory at the *end* of the daemonize process,
13492 not the beginning. This was a problem because the first time you
13493 run tor, if your datadir isn't there, and you have runasdaemon set
13494 to 1, it will try to chdir to it before it tries to create it. Oops.
13495 - Handle changed router status correctly when dirserver reloads
13496 fingerprint file. We used to be dropping all unverified descriptors
13497 right then. The bug was hidden because we would immediately
13498 fetch a directory from another dirserver, which would include the
13499 descriptors we just dropped.
13500 - When we're connecting to an OR and he's got a different nickname/key
13501 than we were expecting, only complain loudly if we're an OP or a
13502 dirserver. Complaining loudly to the OR admins just confuses them.
13503 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13504 artificially capped at 500kB.
13507 Changes in version 0.0.9.8 - 2005-04-07
13508 o Bugfixes on 0.0.9.x:
13509 - We have a bug that I haven't found yet. Sometimes, very rarely,
13510 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13511 thinks of itself as idle. This meant that no new circuits ever got
13512 established. Here's a workaround to kill any cpuworker that's been
13513 busy for more than 100 seconds.
13516 Changes in version 0.1.0.2-rc - 2005-04-01
13517 o Bugfixes on 0.1.0.1-rc:
13518 - Fixes on reachability detection:
13519 - Don't check for reachability while hibernating.
13520 - If ORPort is reachable but DirPort isn't, still publish the
13521 descriptor, but zero out DirPort until it's found reachable.
13522 - When building testing circs for ORPort testing, use only
13523 high-bandwidth nodes, so fewer circuits fail.
13524 - Complain about unreachable ORPort separately from unreachable
13525 DirPort, so the user knows what's going on.
13526 - Make sure we only conclude ORPort reachability if we didn't
13527 initiate the conn. Otherwise we could falsely conclude that
13528 we're reachable just because we connected to the guy earlier
13529 and he used that same pipe to extend to us.
13530 - Authdirservers shouldn't do ORPort reachability detection,
13531 since they're in clique mode, so it will be rare to find a
13532 server not already connected to them.
13533 - When building testing circuits, always pick middle hops running
13534 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13535 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13537 - When we decide we're reachable, actually publish our descriptor
13539 - Fix bug in redirectstream in the controller.
13540 - Fix the state descriptor strings so logs don't claim edge streams
13541 are in a different state than they actually are.
13542 - Use recent libevent features when possible (this only really affects
13543 win32 and osx right now, because the new libevent with these
13544 features hasn't been released yet). Add code to suppress spurious
13546 - Prevent possible segfault in connection_close_unattached_ap().
13547 - Fix newlines on torrc in win32.
13548 - Improve error msgs when tor-resolve fails.
13550 o Improvements on 0.0.9.x:
13551 - New experimental script tor/contrib/ExerciseServer.py (needs more
13552 work) that uses the controller interface to build circuits and
13553 fetch pages over them. This will help us bootstrap servers that
13554 have lots of capacity but haven't noticed it yet.
13555 - New experimental script tor/contrib/PathDemo.py (needs more work)
13556 that uses the controller interface to let you choose whole paths
13558 "<hostname>.<path,separated by dots>.<length of path>.path"
13559 - When we've connected to an OR and handshaked but didn't like
13560 the result, we were closing the conn without sending destroy
13561 cells back for pending circuits. Now send those destroys.
13564 Changes in version 0.0.9.7 - 2005-04-01
13565 o Bugfixes on 0.0.9.x:
13566 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13567 - Compare identity to identity, not to nickname, when extending to
13568 a router not already in the directory. This was preventing us from
13569 extending to unknown routers. Oops.
13570 - Make sure to create OS X Tor user in <500 range, so we aren't
13571 creating actual system users.
13572 - Note where connection-that-hasn't-sent-end was marked, and fix
13573 a few really loud instances of this harmless bug (it's fixed more
13577 Changes in version 0.1.0.1-rc - 2005-03-28
13579 - Add reachability testing. Your Tor server will automatically try
13580 to see if its ORPort and DirPort are reachable from the outside,
13581 and it won't upload its descriptor until it decides they are.
13582 - Handle unavailable hidden services better. Handle slow or busy
13583 hidden services better.
13584 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13586 - New exit policy: accept most low-numbered ports, rather than
13587 rejecting most low-numbered ports.
13588 - More Tor controller support (still experimental). See
13589 http://tor.eff.org/doc/control-spec.txt for all the new features,
13590 including signals to emulate unix signals from any platform;
13591 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13592 closestream; closecircuit; etc.
13593 - Make nt services work and start on startup on win32 (based on
13594 patch by Matt Edman).
13595 - Add a new AddressMap config directive to rewrite incoming socks
13596 addresses. This lets you, for example, declare an implicit
13597 required exit node for certain sites.
13598 - Add a new TrackHostExits config directive to trigger addressmaps
13599 for certain incoming socks addresses -- for sites that break when
13600 your exit keeps changing (based on patch by Mike Perry).
13601 - Redo the client-side dns cache so it's just an addressmap too.
13602 - Notice when our IP changes, and reset stats/uptime/reachability.
13603 - When an application is using socks5, give him the whole variety of
13604 potential socks5 responses (connect refused, host unreachable, etc),
13605 rather than just "success" or "failure".
13606 - A more sane version numbering system. See
13607 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13608 - New contributed script "exitlist": a simple python script to
13609 parse directories and find Tor nodes that exit to listed
13611 - New contributed script "privoxy-tor-toggle" to toggle whether
13612 Privoxy uses Tor. Seems to be configured for Debian by default.
13613 - Report HTTP reasons to client when getting a response from directory
13614 servers -- so you can actually know what went wrong.
13615 - New config option MaxAdvertisedBandwidth which lets you advertise
13616 a low bandwidthrate (to not attract as many circuits) while still
13617 allowing a higher bandwidthrate in reality.
13619 o Robustness/stability fixes:
13620 - Make Tor use Niels Provos's libevent instead of its current
13621 poll-but-sometimes-select mess. This will let us use faster async
13622 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13624 - pthread support now too. This was forced because when we forked,
13625 we ended up wasting a lot of duplicate ram over time. Also switch
13626 to foo_r versions of some library calls to allow reentry and
13628 - Better handling for heterogeneous / unreliable nodes:
13629 - Annotate circuits w/ whether they aim to contain high uptime nodes
13630 and/or high capacity nodes. When building circuits, choose
13632 - This means that every single node in an intro rend circuit,
13633 not just the last one, will have a minimum uptime.
13634 - New config option LongLivedPorts to indicate application streams
13635 that will want high uptime circuits.
13636 - Servers reset uptime when a dir fetch entirely fails. This
13637 hopefully reflects stability of the server's network connectivity.
13638 - If somebody starts his tor server in Jan 2004 and then fixes his
13639 clock, don't make his published uptime be a year.
13640 - Reset published uptime when you wake up from hibernation.
13641 - Introduce a notion of 'internal' circs, which are chosen without
13642 regard to the exit policy of the last hop. Intro and rendezvous
13643 circs must be internal circs, to avoid leaking information. Resolve
13644 and connect streams can use internal circs if they want.
13645 - New circuit pooling algorithm: make sure to have enough circs around
13646 to satisfy any predicted ports, and also make sure to have 2 internal
13647 circs around if we've required internal circs lately (and with high
13648 uptime if we've seen that lately too).
13649 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13650 which describes how often we retry making new circuits if current
13651 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13652 how long we're willing to make use of an already-dirty circuit.
13653 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13654 circ as necessary, if there are any completed ones lying around
13655 when we try to launch one.
13656 - Make hidden services try to establish a rendezvous for 30 seconds,
13657 rather than for n (where n=3) attempts to build a circuit.
13658 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13659 "ShutdownWaitLength".
13660 - Try to be more zealous about calling connection_edge_end when
13661 things go bad with edge conns in connection.c.
13662 - Revise tor-spec to add more/better stream end reasons.
13663 - Revise all calls to connection_edge_end to avoid sending "misc",
13664 and to take errno into account where possible.
13667 - Fix a race condition that can trigger an assert, when we have a
13668 pending create cell and an OR connection fails right then.
13669 - Fix several double-mark-for-close bugs, e.g. where we were finding
13670 a conn for a cell even if that conn is already marked for close.
13671 - Make sequence of log messages when starting on win32 with no config
13672 file more reasonable.
13673 - When choosing an exit node for a new non-internal circ, don't take
13674 into account whether it'll be useful for any pending x.onion
13675 addresses -- it won't.
13676 - Turn addr_policy_compare from a tristate to a quadstate; this should
13677 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13678 for google.com" problem.
13679 - Make "platform" string in descriptor more accurate for Win32 servers,
13680 so it's not just "unknown platform".
13681 - Fix an edge case in parsing config options (thanks weasel).
13682 If they say "--" on the commandline, it's not an option.
13683 - Reject odd-looking addresses at the client (e.g. addresses that
13684 contain a colon), rather than having the server drop them because
13686 - tor-resolve requests were ignoring .exit if there was a working circuit
13687 they could use instead.
13688 - REUSEADDR on normal platforms means you can rebind to the port
13689 right after somebody else has let it go. But REUSEADDR on win32
13690 means to let you bind to the port _even when somebody else
13691 already has it bound_! So, don't do that on Win32.
13692 - Change version parsing logic: a version is "obsolete" if it is not
13693 recommended and (1) there is a newer recommended version in the
13694 same series, or (2) there are no recommended versions in the same
13695 series, but there are some recommended versions in a newer series.
13696 A version is "new" if it is newer than any recommended version in
13698 - Stop most cases of hanging up on a socks connection without sending
13702 - Require BandwidthRate to be at least 20kB/s for servers.
13703 - When a dirserver causes you to give a warn, mention which dirserver
13705 - New config option DirAllowPrivateAddresses for authdirservers.
13706 Now by default they refuse router descriptors that have non-IP or
13707 private-IP addresses.
13708 - Stop publishing socksport in the directory, since it's not
13709 actually meant to be public. For compatibility, publish a 0 there
13711 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13712 smart" value, that is low for servers and high for clients.
13713 - If our clock jumps forward by 100 seconds or more, assume something
13714 has gone wrong with our network and abandon all not-yet-used circs.
13715 - Warn when exit policy implicitly allows local addresses.
13716 - If we get an incredibly skewed timestamp from a dirserver mirror
13717 that isn't a verified OR, don't warn -- it's probably him that's
13719 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13720 cookies to disk and doesn't log each web request to disk. (Thanks
13721 to Brett Carrington for pointing this out.)
13722 - When a client asks us for a dir mirror and we don't have one,
13723 launch an attempt to get a fresh one.
13724 - If we're hibernating and we get a SIGINT, exit immediately.
13725 - Add --with-dmalloc ./configure option, to track memory leaks.
13726 - And try to free all memory on closing, so we can detect what
13728 - Cache local dns resolves correctly even when they're .exit
13730 - Give a better warning when some other server advertises an
13731 ORPort that is actually an apache running ssl.
13732 - Add "opt hibernating 1" to server descriptor to make it clearer
13733 whether the server is hibernating.
13736 Changes in version 0.0.9.6 - 2005-03-24
13737 o Bugfixes on 0.0.9.x (crashes and asserts):
13738 - Add new end stream reasons to maintainance branch. Fix bug where
13739 reason (8) could trigger an assert. Prevent bug from recurring.
13740 - Apparently win32 stat wants paths to not end with a slash.
13741 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13742 blowing away the circuit that conn->cpath_layer points to, then
13743 checking to see if the circ is well-formed. Backport check to make
13744 sure we dont use the cpath on a closed connection.
13745 - Prevent circuit_resume_edge_reading_helper() from trying to package
13746 inbufs for marked-for-close streams.
13747 - Don't crash on hup if your options->address has become unresolvable.
13748 - Some systems (like OS X) sometimes accept() a connection and tell
13749 you the remote host is 0.0.0.0:0. If this happens, due to some
13750 other mis-features, we get confused; so refuse the conn for now.
13752 o Bugfixes on 0.0.9.x (other):
13753 - Fix harmless but scary "Unrecognized content encoding" warn message.
13754 - Add new stream error reason: TORPROTOCOL reason means "you are not
13755 speaking a version of Tor I understand; say bye-bye to your stream."
13756 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13757 into the future, now that we are more tolerant of skew. This
13758 resolves a bug where a Tor server would refuse to cache a directory
13759 because all the directories it gets are too far in the future;
13760 yet the Tor server never logs any complaints about clock skew.
13761 - Mac packaging magic: make man pages useable, and do not overwrite
13762 existing torrc files.
13763 - Make OS X log happily to /var/log/tor/tor.log
13766 Changes in version 0.0.9.5 - 2005-02-22
13767 o Bugfixes on 0.0.9.x:
13768 - Fix an assert race at exit nodes when resolve requests fail.
13769 - Stop picking unverified dir mirrors--it only leads to misery.
13770 - Patch from Matt Edman to make NT services work better. Service
13771 support is still not compiled into the executable by default.
13772 - Patch from Dmitri Bely so the Tor service runs better under
13773 the win32 SYSTEM account.
13774 - Make tor-resolve actually work (?) on Win32.
13775 - Fix a sign bug when getrlimit claims to have 4+ billion
13776 file descriptors available.
13777 - Stop refusing to start when bandwidthburst == bandwidthrate.
13778 - When create cells have been on the onion queue more than five
13779 seconds, just send back a destroy and take them off the list.
13782 Changes in version 0.0.9.4 - 2005-02-03
13783 o Bugfixes on 0.0.9:
13784 - Fix an assert bug that took down most of our servers: when
13785 a server claims to have 1 GB of bandwidthburst, don't
13787 - Don't crash as badly if we have spawned the max allowed number
13788 of dnsworkers, or we're out of file descriptors.
13789 - Block more file-sharing ports in the default exit policy.
13790 - MaxConn is now automatically set to the hard limit of max
13791 file descriptors we're allowed (ulimit -n), minus a few for
13793 - Give a clearer message when servers need to raise their
13794 ulimit -n when they start running out of file descriptors.
13795 - SGI Compatibility patches from Jan Schaumann.
13796 - Tolerate a corrupt cached directory better.
13797 - When a dirserver hasn't approved your server, list which one.
13798 - Go into soft hibernation after 95% of the bandwidth is used,
13799 not 99%. This is especially important for daily hibernators who
13800 have a small accounting max. Hopefully it will result in fewer
13801 cut connections when the hard hibernation starts.
13802 - Load-balance better when using servers that claim more than
13803 800kB/s of capacity.
13804 - Make NT services work (experimental, only used if compiled in).
13807 Changes in version 0.0.9.3 - 2005-01-21
13808 o Bugfixes on 0.0.9:
13809 - Backport the cpu use fixes from main branch, so busy servers won't
13810 need as much processor time.
13811 - Work better when we go offline and then come back, or when we
13812 run Tor at boot before the network is up. We do this by
13813 optimistically trying to fetch a new directory whenever an
13814 application request comes in and we think we're offline -- the
13815 human is hopefully a good measure of when the network is back.
13816 - Backport some minimal hidserv bugfixes: keep rend circuits open as
13817 long as you keep using them; actually publish hidserv descriptors
13818 shortly after they change, rather than waiting 20-40 minutes.
13819 - Enable Mac startup script by default.
13820 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
13821 - When you update AllowUnverifiedNodes or FirewallPorts via the
13822 controller's setconf feature, we were always appending, never
13824 - When you update HiddenServiceDir via setconf, it was screwing up
13825 the order of reading the lines, making it fail.
13826 - Do not rewrite a cached directory back to the cache; otherwise we
13827 will think it is recent and not fetch a newer one on startup.
13828 - Workaround for webservers that lie about Content-Encoding: Tor
13829 now tries to autodetect compressed directories and compression
13830 itself. This lets us Proxypass dir fetches through apache.
13833 Changes in version 0.0.9.2 - 2005-01-04
13834 o Bugfixes on 0.0.9 (crashes and asserts):
13835 - Fix an assert on startup when the disk is full and you're logging
13837 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
13838 style address, then we'd crash.
13839 - Fix an assert trigger when the running-routers string we get from
13840 a dirserver is broken.
13841 - Make worker threads start and run on win32. Now win32 servers
13843 - Bandaid (not actually fix, but now it doesn't crash) an assert
13844 where the dns worker dies mysteriously and the main Tor process
13845 doesn't remember anything about the address it was resolving.
13847 o Bugfixes on 0.0.9 (Win32):
13848 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
13849 name out of the warning/assert messages.
13850 - Fix a superficial "unhandled error on read" bug on win32.
13851 - The win32 installer no longer requires a click-through for our
13852 license, since our Free Software license grants rights but does not
13854 - Win32: When connecting to a dirserver fails, try another one
13855 immediately. (This was already working for non-win32 Tors.)
13856 - Stop trying to parse $HOME on win32 when hunting for default
13858 - Make tor-resolve.c work on win32 by calling network_init().
13860 o Bugfixes on 0.0.9 (other):
13861 - Make 0.0.9.x build on Solaris again.
13862 - Due to a fencepost error, we were blowing away the \n when reporting
13863 confvalue items in the controller. So asking for multiple config
13864 values at once couldn't work.
13865 - When listing circuits that are pending on an opening OR connection,
13866 if we're an OR we were listing circuits that *end* at us as
13867 being pending on every listener, dns/cpu worker, etc. Stop that.
13868 - Dirservers were failing to create 'running-routers' or 'directory'
13869 strings if we had more than some threshold of routers. Fix them so
13870 they can handle any number of routers.
13871 - Fix a superficial "Duplicate mark for close" bug.
13872 - Stop checking for clock skew for OR connections, even for servers.
13873 - Fix a fencepost error that was chopping off the last letter of any
13874 nickname that is the maximum allowed nickname length.
13875 - Update URLs in log messages so they point to the new website.
13876 - Fix a potential problem in mangling server private keys while
13877 writing to disk (not triggered yet, as far as we know).
13878 - Include the licenses for other free software we include in Tor,
13879 now that we're shipping binary distributions more regularly.
13882 Changes in version 0.0.9.1 - 2004-12-15
13883 o Bugfixes on 0.0.9:
13884 - Make hibernation actually work.
13885 - Make HashedControlPassword config option work.
13886 - When we're reporting event circuit status to a controller,
13887 don't use the stream status code.
13890 Changes in version 0.0.9 - 2004-12-12
13892 - Clean up manpage and torrc.sample file.
13893 - Clean up severities and text of log warnings.
13895 - Make servers trigger an assert when they enter hibernation.
13898 Changes in version 0.0.9rc7 - 2004-12-08
13899 o Bugfixes on 0.0.9rc:
13900 - Fix a stack-trashing crash when an exit node begins hibernating.
13901 - Avoid looking at unallocated memory while considering which
13902 ports we need to build circuits to cover.
13903 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13904 we shouldn't hold-open-until-flush if the eof arrived first.
13905 - Fix a bug with init_cookie_authentication() in the controller.
13906 - When recommending new-format log lines, if the upper bound is
13907 LOG_ERR, leave it implicit.
13909 o Bugfixes on 0.0.8.1:
13910 - Fix a whole slew of memory leaks.
13911 - Fix isspace() and friends so they still make Solaris happy
13912 but also so they don't trigger asserts on win32.
13913 - Fix parse_iso_time on platforms without strptime (eg win32).
13914 - win32: tolerate extra "readable" events better.
13915 - win32: when being multithreaded, leave parent fdarray open.
13916 - Make unit tests work on win32.
13919 Changes in version 0.0.9rc6 - 2004-12-06
13920 o Bugfixes on 0.0.9pre:
13921 - Clean up some more integer underflow opportunities (not exploitable
13923 - While hibernating, hup should not regrow our listeners.
13924 - Send an end to the streams we close when we hibernate, rather
13925 than just chopping them off.
13926 - React to eof immediately on non-open edge connections.
13928 o Bugfixes on 0.0.8.1:
13929 - Calculate timeout for waiting for a connected cell from the time
13930 we sent the begin cell, not from the time the stream started. If
13931 it took a long time to establish the circuit, we would time out
13932 right after sending the begin cell.
13933 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13934 of * as always matching, so we were picking reject *:* nodes as
13935 exit nodes too. Oops.
13938 - New circuit building strategy: keep a list of ports that we've
13939 used in the past 6 hours, and always try to have 2 circuits open
13940 or on the way that will handle each such port. Seed us with port
13941 80 so web users won't complain that Tor is "slow to start up".
13942 - Make kill -USR1 dump more useful stats about circuits.
13943 - When warning about retrying or giving up, print the address, so
13944 the user knows which one it's talking about.
13945 - If you haven't used a clean circuit in an hour, throw it away,
13946 just to be on the safe side. (This means after 6 hours a totally
13947 unused Tor client will have no circuits open.)
13950 Changes in version 0.0.9rc5 - 2004-12-01
13951 o Bugfixes on 0.0.8.1:
13952 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13953 - Let resolve conns retry/expire also, rather than sticking around
13955 - If we are using select, make sure we stay within FD_SETSIZE.
13957 o Bugfixes on 0.0.9pre:
13958 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
13959 but doesn't seem to be currently; thanks to Ilja van Sprundel for
13961 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
13962 instead. Impose minima and maxima for all *Period options; impose
13963 even tighter maxima for fetching if we are a caching dirserver.
13964 Clip rather than rejecting.
13965 - Fetch cached running-routers from servers that serve it (that is,
13966 authdirservers and servers running 0.0.9rc5-cvs or later.)
13969 - Accept *:706 (silc) in default exit policy.
13970 - Implement new versioning format for post 0.1.
13971 - Support "foo.nickname.exit" addresses, to let Alice request the
13972 address "foo" as viewed by exit node "nickname". Based on a patch
13974 - Make tor --version --version dump the cvs Id of every file.
13977 Changes in version 0.0.9rc4 - 2004-11-28
13978 o Bugfixes on 0.0.8.1:
13979 - Make windows sockets actually non-blocking (oops), and handle
13980 win32 socket errors better.
13982 o Bugfixes on 0.0.9rc1:
13983 - Actually catch the -USR2 signal.
13986 Changes in version 0.0.9rc3 - 2004-11-25
13987 o Bugfixes on 0.0.8.1:
13988 - Flush the log file descriptor after we print "Tor opening log file",
13989 so we don't see those messages days later.
13991 o Bugfixes on 0.0.9rc1:
13992 - Make tor-resolve work again.
13993 - Avoid infinite loop in tor-resolve if tor hangs up on it.
13994 - Fix an assert trigger for clients/servers handling resolves.
13997 Changes in version 0.0.9rc2 - 2004-11-24
13998 o Bugfixes on 0.0.9rc1:
13999 - I broke socks5 support while fixing the eof bug.
14000 - Allow unitless bandwidths and intervals; they default to bytes
14002 - New servers don't start out hibernating; they are active until
14003 they run out of bytes, so they have a better estimate of how
14004 long it takes, and so their operators can know they're working.
14007 Changes in version 0.0.9rc1 - 2004-11-23
14008 o Bugfixes on 0.0.8.1:
14009 - Finally fix a bug that's been plaguing us for a year:
14010 With high load, circuit package window was reaching 0. Whenever
14011 we got a circuit-level sendme, we were reading a lot on each
14012 socket, but only writing out a bit. So we would eventually reach
14013 eof. This would be noticed and acted on even when there were still
14014 bytes sitting in the inbuf.
14015 - When poll() is interrupted, we shouldn't believe the revents values.
14017 o Bugfixes on 0.0.9pre6:
14018 - Fix hibernate bug that caused pre6 to be broken.
14019 - Don't keep rephist info for routers that haven't had activity for
14020 24 hours. (This matters now that clients have keys, since we track
14022 - Never call close_temp_logs while validating log options.
14023 - Fix backslash-escaping on tor.sh.in and torctl.in.
14026 - Implement weekly/monthly/daily accounting: now you specify your
14027 hibernation properties by
14028 AccountingMax N bytes|KB|MB|GB|TB
14029 AccountingStart day|week|month [day] HH:MM
14030 Defaults to "month 1 0:00".
14031 - Let bandwidth and interval config options be specified as 5 bytes,
14032 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14033 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14034 get back to normal.)
14035 - If your requested entry or exit node has advertised bandwidth 0,
14037 - Be more greedy about filling up relay cells -- we try reading again
14038 once we've processed the stuff we read, in case enough has arrived
14039 to fill the last cell completely.
14040 - Apply NT service patch from Osamu Fujino. Still needs more work.
14043 Changes in version 0.0.9pre6 - 2004-11-15
14044 o Bugfixes on 0.0.8.1:
14045 - Fix assert failure on malformed socks4a requests.
14046 - Use identity comparison, not nickname comparison, to choose which
14047 half of circuit-ID-space each side gets to use. This is needed
14048 because sometimes we think of a router as a nickname, and sometimes
14049 as a hex ID, and we can't predict what the other side will do.
14050 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14051 write() call will fail and we handle it there.
14052 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14053 and smartlist_len, which are two major profiling offenders.
14055 o Bugfixes on 0.0.9pre5:
14056 - Fix a bug in read_all that was corrupting config files on windows.
14057 - When we're raising the max number of open file descriptors to
14058 'unlimited', don't log that we just raised it to '-1'.
14059 - Include event code with events, as required by control-spec.txt.
14060 - Don't give a fingerprint when clients do --list-fingerprint:
14061 it's misleading, because it will never be the same again.
14062 - Stop using strlcpy in tor_strndup, since it was slowing us
14064 - Remove warn on startup about missing cached-directory file.
14065 - Make kill -USR1 work again.
14066 - Hibernate if we start tor during the "wait for wakeup-time" phase
14067 of an accounting interval. Log our hibernation plans better.
14068 - Authoritative dirservers now also cache their directory, so they
14069 have it on start-up.
14072 - Fetch running-routers; cache running-routers; compress
14073 running-routers; serve compressed running-routers.z
14074 - Add NSI installer script contributed by J Doe.
14075 - Commit VC6 and VC7 workspace/project files.
14076 - Commit a tor.spec for making RPM files, with help from jbash.
14077 - Add contrib/torctl.in contributed by Glenn Fink.
14078 - Implement the control-spec's SAVECONF command, to write your
14079 configuration to torrc.
14080 - Get cookie authentication for the controller closer to working.
14081 - Include control-spec.txt in the tarball.
14082 - When set_conf changes our server descriptor, upload a new copy.
14083 But don't upload it too often if there are frequent changes.
14084 - Document authentication config in man page, and document signals
14086 - Clean up confusing parts of man page and torrc.sample.
14087 - Make expand_filename handle ~ and ~username.
14088 - Use autoconf to enable largefile support where necessary. Use
14089 ftello where available, since ftell can fail at 2GB.
14090 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14091 log more informatively.
14092 - Give a slightly more useful output for "tor -h".
14093 - Refuse application socks connections to port 0.
14094 - Check clock skew for verified servers, but allow unverified
14095 servers and clients to have any clock skew.
14096 - Break DirFetchPostPeriod into:
14097 - DirFetchPeriod for fetching full directory,
14098 - StatusFetchPeriod for fetching running-routers,
14099 - DirPostPeriod for posting server descriptor,
14100 - RendPostPeriod for posting hidden service descriptors.
14101 - Make sure the hidden service descriptors are at a random offset
14102 from each other, to hinder linkability.
14105 Changes in version 0.0.9pre5 - 2004-11-09
14106 o Bugfixes on 0.0.9pre4:
14107 - Fix a seg fault in unit tests (doesn't affect main program).
14108 - Fix an assert bug where a hidden service provider would fail if
14109 the first hop of his rendezvous circuit was down.
14110 - Hidden service operators now correctly handle version 1 style
14111 INTRODUCE1 cells (nobody generates them still, so not a critical
14113 - If do_hup fails, actually notice.
14114 - Handle more errnos from accept() without closing the listener.
14115 Some OpenBSD machines were closing their listeners because
14116 they ran out of file descriptors.
14117 - Send resolve cells to exit routers that are running a new
14118 enough version of the resolve code to work right.
14119 - Better handling of winsock includes on non-MSV win32 compilers.
14120 - Some people had wrapped their tor client/server in a script
14121 that would restart it whenever it died. This did not play well
14122 with our "shut down if your version is obsolete" code. Now people
14123 don't fetch a new directory if their local cached version is
14125 - Make our autogen.sh work on ksh as well as bash.
14128 - Hibernation: New config option "AccountingMaxKB" lets you
14129 set how many KBytes per month you want to allow your server to
14130 consume. Rather than spreading those bytes out evenly over the
14131 month, we instead hibernate for some of the month and pop up
14132 at a deterministic time, work until the bytes are consumed, then
14133 hibernate again. Config option "MonthlyAccountingStart" lets you
14134 specify which day of the month your billing cycle starts on.
14135 - Control interface: a separate program can now talk to your
14136 client/server over a socket, and get/set config options, receive
14137 notifications of circuits and streams starting/finishing/dying,
14138 bandwidth used, etc. The next step is to get some GUIs working.
14139 Let us know if you want to help out. See doc/control-spec.txt .
14140 - Ship a contrib/tor-control.py as an example script to interact
14141 with the control port.
14142 - "tor --hash-password zzyxz" will output a salted password for
14143 use in authenticating to the control interface.
14144 - New log format in config:
14145 "Log minsev[-maxsev] stdout|stderr|syslog" or
14146 "Log minsev[-maxsev] file /var/foo"
14149 - DirPolicy config option, to let people reject incoming addresses
14150 from their dirserver.
14151 - "tor --list-fingerprint" will list your identity key fingerprint
14153 - Add "pass" target for RedirectExit, to make it easier to break
14154 out of a sequence of RedirectExit rules.
14155 - Clients now generate a TLS cert too, in preparation for having
14156 them act more like real nodes.
14157 - Ship src/win32/ in the tarball, so people can use it to build.
14158 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14160 - New "router-status" line in directory, to better bind each verified
14161 nickname to its identity key.
14162 - Deprecate unofficial config option abbreviations, and abbreviations
14163 not on the command line.
14164 - Add a pure-C tor-resolve implementation.
14165 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14166 1024) file descriptors.
14168 o Code security improvements, inspired by Ilja:
14169 - Replace sprintf with snprintf. (I think they were all safe, but
14171 - Replace strcpy/strncpy with strlcpy in more places.
14172 - Avoid strcat; use snprintf or strlcat instead.
14173 - snprintf wrapper with consistent (though not C99) overflow behavior.
14176 Changes in version 0.0.9pre4 - 2004-10-17
14177 o Bugfixes on 0.0.9pre3:
14178 - If the server doesn't specify an exit policy, use the real default
14179 exit policy, not reject *:*.
14180 - Ignore fascistfirewall when uploading/downloading hidden service
14181 descriptors, since we go through Tor for those; and when using
14182 an HttpProxy, since we assume it can reach them all.
14183 - When looking for an authoritative dirserver, use only the ones
14184 configured at boot. Don't bother looking in the directory.
14185 - The rest of the fix for get_default_conf_file() on older win32.
14186 - Make 'Routerfile' config option obsolete.
14189 - New 'MyFamily nick1,...' config option for a server to
14190 specify other servers that shouldn't be used in the same circuit
14191 with it. Only believed if nick1 also specifies us.
14192 - New 'NodeFamily nick1,nick2,...' config option for a client to
14193 specify nodes that it doesn't want to use in the same circuit.
14194 - New 'Redirectexit pattern address:port' config option for a
14195 server to redirect exit connections, e.g. to a local squid.
14198 Changes in version 0.0.9pre3 - 2004-10-13
14199 o Bugfixes on 0.0.8.1:
14200 - Better torrc example lines for dirbindaddress and orbindaddress.
14201 - Improved bounds checking on parsed ints (e.g. config options and
14202 the ones we find in directories.)
14203 - Better handling of size_t vs int, so we're more robust on 64
14205 - Fix the rest of the bug where a newly started OR would appear
14206 as unverified even after we've added his fingerprint and hupped
14208 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14209 close it without sending back an end. So 'connection refused'
14210 would simply be ignored and the user would get no response.
14212 o Bugfixes on 0.0.9pre2:
14213 - Serving the cached-on-disk directory to people is bad. We now
14214 provide no directory until we've fetched a fresh one.
14215 - Workaround for bug on windows where cached-directories get crlf
14217 - Make get_default_conf_file() work on older windows too.
14218 - If we write a *:* exit policy line in the descriptor, don't write
14219 any more exit policy lines.
14222 - Use only 0.0.9pre1 and later servers for resolve cells.
14223 - Make the dirservers file obsolete.
14224 - Include a dir-signing-key token in directories to tell the
14225 parsing entity which key is being used to sign.
14226 - Remove the built-in bulky default dirservers string.
14227 - New config option "Dirserver %s:%d [fingerprint]", which can be
14228 repeated as many times as needed. If no dirservers specified,
14229 default to moria1,moria2,tor26.
14230 - Make moria2 advertise a dirport of 80, so people behind firewalls
14231 will be able to get a directory.
14232 - Http proxy support
14233 - Dirservers translate requests for http://%s:%d/x to /x
14234 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14235 be routed through this host.
14236 - Clients ask for /tor/x rather than /x for new enough dirservers.
14237 This way we can one day coexist peacefully with apache.
14238 - Clients specify a "Host: %s%d" http header, to be compatible
14239 with more proxies, and so running squid on an exit node can work.
14242 Changes in version 0.0.8.1 - 2004-10-13
14244 - Fix a seg fault that can be triggered remotely for Tor
14245 clients/servers with an open dirport.
14246 - Fix a rare assert trigger, where routerinfos for entries in
14247 our cpath would expire while we're building the path.
14248 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14249 - Fix a rare seg fault for people running hidden services on
14250 intermittent connections.
14251 - Fix a bug in parsing opt keywords with objects.
14252 - Fix a stale pointer assert bug when a stream detaches and
14254 - Fix a string format vulnerability (probably not exploitable)
14255 in reporting stats locally.
14256 - Fix an assert trigger: sometimes launching circuits can fail
14257 immediately, e.g. because too many circuits have failed recently.
14258 - Fix a compile warning on 64 bit platforms.
14261 Changes in version 0.0.9pre2 - 2004-10-03
14263 - Make fetching a cached directory work for 64-bit platforms too.
14264 - Make zlib.h a required header, not an optional header.
14267 Changes in version 0.0.9pre1 - 2004-10-01
14269 - Stop using separate defaults for no-config-file and
14270 empty-config-file. Now you have to explicitly turn off SocksPort,
14271 if you don't want it open.
14272 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14273 - Improve man page to mention more of the 0.0.8 features.
14274 - Fix a rare seg fault for people running hidden services on
14275 intermittent connections.
14276 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14278 - Fix more dns related bugs: send back resolve_failed and end cells
14279 more reliably when the resolve fails, rather than closing the
14280 circuit and then trying to send the cell. Also attach dummy resolve
14281 connections to a circuit *before* calling dns_resolve(), to fix
14282 a bug where cached answers would never be sent in RESOLVED cells.
14283 - When we run out of disk space, or other log writing error, don't
14284 crash. Just stop logging to that log and continue.
14285 - We were starting to daemonize before we opened our logs, so if
14286 there were any problems opening logs, we would complain to stderr,
14287 which wouldn't work, and then mysteriously exit.
14288 - Fix a rare bug where sometimes a verified OR would connect to us
14289 before he'd uploaded his descriptor, which would cause us to
14290 assign conn->nickname as though he's unverified. Now we look through
14291 the fingerprint list to see if he's there.
14292 - Fix a rare assert trigger, where routerinfos for entries in
14293 our cpath would expire while we're building the path.
14296 - Clients can ask dirservers for /dir.z to get a compressed version
14297 of the directory. Only works for servers running 0.0.9, of course.
14298 - Make clients cache directories and use them to seed their router
14299 lists at startup. This means clients have a datadir again.
14300 - Configuration infrastructure support for warning on obsolete
14302 - Respond to content-encoding headers by trying to uncompress as
14304 - Reply with a deflated directory when a client asks for "dir.z".
14305 We could use allow-encodings instead, but allow-encodings isn't
14306 specified in HTTP 1.0.
14307 - Raise the max dns workers from 50 to 100.
14308 - Discourage people from setting their dirfetchpostperiod more often
14309 than once per minute.
14310 - Protect dirservers from overzealous descriptor uploading -- wait
14311 10 seconds after directory gets dirty, before regenerating.
14314 Changes in version 0.0.8 - 2004-08-25
14315 o Port it to SunOS 5.9 / Athena
14318 Changes in version 0.0.8rc2 - 2004-08-20
14319 o Make it compile on cygwin again.
14320 o When picking unverified routers, skip those with low uptime and/or
14321 low bandwidth, depending on what properties you care about.
14324 Changes in version 0.0.8rc1 - 2004-08-18
14325 o Changes from 0.0.7.3:
14327 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14328 don't put it into the client dns cache.
14329 - If a begin failed due to exit policy, but we believe the IP address
14330 should have been allowed, switch that router to exitpolicy reject *:*
14331 until we get our next directory.
14333 - Clients choose nodes proportional to advertised bandwidth.
14334 - Avoid using nodes with low uptime as introduction points.
14335 - Handle servers with dynamic IP addresses: don't replace
14336 options->Address with the resolved one at startup, and
14337 detect our address right before we make a routerinfo each time.
14338 - 'FascistFirewall' option to pick dirservers and ORs on specific
14339 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14340 which ports are open. (Defaults to 80,443)
14341 - Be more aggressive about trying to make circuits when the network
14342 has changed (e.g. when you unsuspend your laptop).
14343 - Check for time skew on http headers; report date in response to
14345 - If the entrynode config line has only one node, don't pick it as
14347 - Add strict{entry|exit}nodes config options. If set to 1, then
14348 we refuse to build circuits that don't include the specified entry
14350 - OutboundBindAddress config option, to bind to a specific
14351 IP address for outgoing connect()s.
14352 - End truncated log entries (e.g. directories) with "[truncated]".
14354 o Patches to 0.0.8preX:
14356 - Patches to compile and run on win32 again (maybe)?
14357 - Fix crash when looking for ~/.torrc with no $HOME set.
14358 - Fix a race bug in the unit tests.
14359 - Handle verified/unverified name collisions better when new
14360 routerinfo's arrive in a directory.
14361 - Sometimes routers were getting entered into the stats before
14362 we'd assigned their identity_digest. Oops.
14363 - Only pick and establish intro points after we've gotten a
14366 - AllowUnverifiedNodes config option to let circuits choose no-name
14367 routers in entry,middle,exit,introduction,rendezvous positions.
14368 Allow middle and rendezvous positions by default.
14369 - Add a man page for tor-resolve.
14372 Changes in version 0.0.7.3 - 2004-08-12
14373 o Stop dnsworkers from triggering an assert failure when you
14374 ask them to resolve the host "".
14377 Changes in version 0.0.8pre3 - 2004-08-09
14378 o Changes from 0.0.7.2:
14379 - Allow multiple ORs with same nickname in routerlist -- now when
14380 people give us one identity key for a nickname, then later
14381 another, we don't constantly complain until the first expires.
14382 - Remember used bandwidth (both in and out), and publish 15-minute
14383 snapshots for the past day into our descriptor.
14384 - You can now fetch $DIRURL/running-routers to get just the
14385 running-routers line, not the whole descriptor list. (But
14386 clients don't use this yet.)
14387 - When people mistakenly use Tor as an http proxy, point them
14388 at the tor-doc.html rather than the INSTALL.
14389 - Remove our mostly unused -- and broken -- hex_encode()
14390 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14391 for pointing out this bug.)
14392 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14393 fewer problems with people using the wrong key.
14394 - Change the default exit policy to reject the default edonkey,
14395 kazaa, gnutella ports.
14396 - Add replace_file() to util.[ch] to handle win32's rename().
14398 o Changes from 0.0.8preX:
14399 - Fix two bugs in saving onion keys to disk when rotating, so
14400 hopefully we'll get fewer people using old onion keys.
14401 - Fix an assert error that was making SocksPolicy not work.
14402 - Be willing to expire routers that have an open dirport -- it's
14403 just the authoritative dirservers we want to not forget.
14404 - Reject tor-resolve requests for .onion addresses early, so we
14405 don't build a whole rendezvous circuit and then fail.
14406 - When you're warning a server that he's unverified, don't cry
14407 wolf unpredictably.
14408 - Fix a race condition: don't try to extend onto a connection
14409 that's still handshaking.
14410 - For servers in clique mode, require the conn to be open before
14411 you'll choose it for your path.
14412 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14413 end relay cell, etc.
14414 - Measure bandwidth capacity over the last 24 hours, not just 12
14415 - Bugfix: authoritative dirservers were making and signing a new
14416 directory for each client, rather than reusing the cached one.
14419 Changes in version 0.0.8pre2 - 2004-08-04
14420 o Changes from 0.0.7.2:
14422 - Check directory signature _before_ you decide whether you're
14423 you're running an obsolete version and should exit.
14424 - Check directory signature _before_ you parse the running-routers
14425 list to decide who's running or verified.
14426 - Bugfixes and features:
14427 - Check return value of fclose while writing to disk, so we don't
14428 end up with broken files when servers run out of disk space.
14429 - Log a warning if the user uses an unsafe socks variant, so people
14430 are more likely to learn about privoxy or socat.
14431 - Dirservers now include RFC1123-style dates in the HTTP headers,
14432 which one day we will use to better detect clock skew.
14434 o Changes from 0.0.8pre1:
14435 - Make it compile without warnings again on win32.
14436 - Log a warning if you're running an unverified server, to let you
14437 know you might want to get it verified.
14438 - Only pick a default nickname if you plan to be a server.
14441 Changes in version 0.0.8pre1 - 2004-07-23
14443 - Made our unit tests compile again on OpenBSD 3.5, and tor
14444 itself compile again on OpenBSD on a sparc64.
14445 - We were neglecting milliseconds when logging on win32, so
14446 everything appeared to happen at the beginning of each second.
14448 o Protocol changes:
14449 - 'Extend' relay cell payloads now include the digest of the
14450 intended next hop's identity key. Now we can verify that we're
14451 extending to the right router, and also extend to routers we
14452 hadn't heard of before.
14455 - Tor nodes can now act as relays (with an advertised ORPort)
14456 without being manually verified by the dirserver operators.
14457 - Uploaded descriptors of unverified routers are now accepted
14458 by the dirservers, and included in the directory.
14459 - Verified routers are listed by nickname in the running-routers
14460 list; unverified routers are listed as "$<fingerprint>".
14461 - We now use hash-of-identity-key in most places rather than
14462 nickname or addr:port, for improved security/flexibility.
14463 - To avoid Sybil attacks, paths still use only verified servers.
14464 But now we have a chance to play around with hybrid approaches.
14465 - Nodes track bandwidth usage to estimate capacity (not used yet).
14466 - ClientOnly option for nodes that never want to become servers.
14467 - Directory caching.
14468 - "AuthoritativeDir 1" option for the official dirservers.
14469 - Now other nodes (clients and servers) will cache the latest
14470 directory they've pulled down.
14471 - They can enable their DirPort to serve it to others.
14472 - Clients will pull down a directory from any node with an open
14473 DirPort, and check the signature/timestamp correctly.
14474 - Authoritative dirservers now fetch directories from other
14475 authdirservers, to stay better synced.
14476 - Running-routers list tells who's down also, along with noting
14477 if they're verified (listed by nickname) or unverified (listed
14479 - Allow dirservers to serve running-router list separately.
14480 This isn't used yet.
14481 - ORs connect-on-demand to other ORs
14482 - If you get an extend cell to an OR you're not connected to,
14483 connect, handshake, and forward the create cell.
14484 - The authoritative dirservers stay connected to everybody,
14485 and everybody stays connected to 0.0.7 servers, but otherwise
14486 clients/servers expire unused connections after 5 minutes.
14487 - When servers get a sigint, they delay 30 seconds (refusing new
14488 connections) then exit. A second sigint causes immediate exit.
14489 - File and name management:
14490 - Look for .torrc if no CONFDIR "torrc" is found.
14491 - If no datadir is defined, then choose, make, and secure ~/.tor
14493 - If torrc not found, exitpolicy reject *:*.
14494 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14495 - If no nickname is defined, derive default from hostname.
14496 - Rename secret key files, e.g. identity.key -> secret_id_key,
14497 to discourage people from mailing their identity key to tor-ops.
14498 - Refuse to build a circuit before the directory has arrived --
14499 it won't work anyway, since you won't know the right onion keys
14501 - Try other dirservers immediately if the one you try is down. This
14502 should tolerate down dirservers better now.
14503 - Parse tor version numbers so we can do an is-newer-than check
14504 rather than an is-in-the-list check.
14505 - New socks command 'resolve', to let us shim gethostbyname()
14507 - A 'tor_resolve' script to access the socks resolve functionality.
14508 - A new socks-extensions.txt doc file to describe our
14509 interpretation and extensions to the socks protocols.
14510 - Add a ContactInfo option, which gets published in descriptor.
14511 - Publish OR uptime in descriptor (and thus in directory) too.
14512 - Write tor version at the top of each log file
14513 - New docs in the tarball:
14515 - Document that you should proxy your SSL traffic too.
14518 Changes in version 0.0.7.2 - 2004-07-07
14519 o A better fix for the 0.0.0.0 problem, that will hopefully
14520 eliminate the remaining related assertion failures.
14523 Changes in version 0.0.7.1 - 2004-07-04
14524 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14525 since internally we use 0.0.0.0 to signify "not yet resolved".
14528 Changes in version 0.0.7 - 2004-06-07
14529 o Updated the man page to reflect the new features.
14532 Changes in version 0.0.7rc2 - 2004-06-06
14533 o Changes from 0.0.7rc1:
14534 - Make it build on Win32 again.
14535 o Changes from 0.0.6.2:
14536 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14540 Changes in version 0.0.7rc1 - 2004-06-02
14542 - On sighup, we were adding another log without removing the first
14543 one. So log messages would get duplicated n times for n sighups.
14544 - Several cases of using a connection after we'd freed it. The
14545 problem was that connections that are pending resolve are in both
14546 the pending_resolve tree, and also the circuit's resolving_streams
14547 list. When you want to remove one, you must remove it from both.
14548 - Fix a double-mark-for-close where an end cell arrived for a
14549 resolving stream, and then the resolve failed.
14550 - Check directory signatures based on name of signer, not on whom
14551 we got the directory from. This will let us cache directories more
14554 - Crank up some of our constants to handle more users.
14557 Changes in version 0.0.7pre1 - 2004-06-02
14558 o Fixes for crashes and other obnoxious bugs:
14559 - Fix an epipe bug: sometimes when directory connections failed
14560 to connect, we would give them a chance to flush before closing
14562 - When we detached from a circuit because of resolvefailed, we
14563 would immediately try the same circuit twice more, and then
14564 give up on the resolve thinking we'd tried three different
14566 - Limit the number of intro circuits we'll attempt to build for a
14567 hidden service per 15-minute period.
14568 - Check recommended-software string *early*, before actually parsing
14569 the directory. Thus we can detect an obsolete version and exit,
14570 even if the new directory format doesn't parse.
14571 o Fixes for security bugs:
14572 - Remember which nodes are dirservers when you startup, and if a
14573 random OR enables his dirport, don't automatically assume he's
14574 a trusted dirserver.
14576 - Directory connections were asking the wrong poll socket to
14577 start writing, and not asking themselves to start writing.
14578 - When we detached from a circuit because we sent a begin but
14579 didn't get a connected, we would use it again the first time;
14580 but after that we would correctly switch to a different one.
14581 - Stop warning when the first onion decrypt attempt fails; they
14582 will sometimes legitimately fail now that we rotate keys.
14583 - Override unaligned-access-ok check when $host_cpu is ia64 or
14584 arm. Apparently they allow it but the kernel whines.
14585 - Dirservers try to reconnect periodically too, in case connections
14587 - Fix some memory leaks in directory servers.
14588 - Allow backslash in Win32 filenames.
14589 - Made Tor build complain-free on FreeBSD, hopefully without
14590 breaking other BSD builds. We'll see.
14592 - Doxygen markup on all functions and global variables.
14593 - Make directory functions update routerlist, not replace it. So
14594 now directory disagreements are not so critical a problem.
14595 - Remove the upper limit on number of descriptors in a dirserver's
14596 directory (not that we were anywhere close).
14597 - Allow multiple logfiles at different severity ranges.
14598 - Allow *BindAddress to specify ":port" rather than setting *Port
14599 separately. Allow multiple instances of each BindAddress config
14600 option, so you can bind to multiple interfaces if you want.
14601 - Allow multiple exit policy lines, which are processed in order.
14602 Now we don't need that huge line with all the commas in it.
14603 - Enable accept/reject policies on SOCKS connections, so you can bind
14604 to 0.0.0.0 but still control who can use your OP.
14607 Changes in version 0.0.6.2 - 2004-05-16
14608 o Our integrity-checking digest was checking only the most recent cell,
14609 not the previous cells like we'd thought.
14610 Thanks to Stefan Mark for finding the flaw!
14613 Changes in version 0.0.6.1 - 2004-05-06
14614 o Fix two bugs in our AES counter-mode implementation (this affected
14615 onion-level stream encryption, but not TLS-level). It turns
14616 out we were doing something much more akin to a 16-character
14617 polyalphabetic cipher. Oops.
14618 Thanks to Stefan Mark for finding the flaw!
14619 o Retire moria3 as a directory server, and add tor26 as a directory
14623 Changes in version 0.0.6 - 2004-05-02
14624 [version bump only]
14627 Changes in version 0.0.6rc4 - 2004-05-01
14628 o Update the built-in dirservers list to use the new directory format
14629 o Fix a rare seg fault: if a node offering a hidden service attempts
14630 to build a circuit to Alice's rendezvous point and fails before it
14631 reaches the last hop, it retries with a different circuit, but
14633 o Handle windows socket errors correctly.
14636 Changes in version 0.0.6rc3 - 2004-04-28
14637 o Don't expire non-general excess circuits (if we had enough
14638 circuits open, we were expiring rendezvous circuits -- even
14639 when they had a stream attached. oops.)
14640 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14641 o Better debugging for tls errors
14642 o Some versions of openssl have an SSL_pending function that erroneously
14643 returns bytes when there is a non-application record pending.
14644 o Set Content-Type on the directory and hidserv descriptor.
14645 o Remove IVs from cipher code, since AES-ctr has none.
14646 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14647 o We were using an array of length zero in a few places.
14648 o win32's gethostbyname can't resolve an IP to an IP.
14649 o win32's close can't close a socket.
14652 Changes in version 0.0.6rc2 - 2004-04-26
14653 o Fix a bug where we were closing tls connections intermittently.
14654 It turns out openssl keeps its errors around -- so if an error
14655 happens, and you don't ask about it, and then another openssl
14656 operation happens and succeeds, and you ask if there was an error,
14657 it tells you about the first error. Fun fun.
14658 o Fix a bug that's been lurking since 27 may 03 (!)
14659 When passing back a destroy cell, we would use the wrong circ id.
14660 'Mostly harmless', but still worth fixing.
14661 o Since we don't support truncateds much, don't bother sending them;
14662 just close the circ.
14663 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14664 o don't crash if a conn that sent a begin has suddenly lost its circuit
14665 (this was quite rare).
14668 Changes in version 0.0.6rc1 - 2004-04-25
14669 o We now rotate link (tls context) keys and onion keys.
14670 o CREATE cells now include oaep padding, so you can tell
14671 if you decrypted them correctly.
14672 o Add bandwidthburst to server descriptor.
14673 o Directories now say which dirserver signed them.
14674 o Use a tor_assert macro that logs failed assertions too.
14677 Changes in version 0.0.6pre5 - 2004-04-18
14678 o changes from 0.0.6pre4:
14679 - make tor build on broken freebsd 5.2 installs
14680 - fix a failed assert when you try an intro point, get a nack, and try
14681 a second one and it works.
14682 - when alice uses a port that the hidden service doesn't accept,
14683 it now sends back an end cell (denied by exit policy). otherwise
14684 alice would just have to wait to time out.
14685 - fix another rare bug: when we had tried all the intro
14686 points for a hidden service, we fetched the descriptor
14687 again, but we left our introcirc thinking it had already
14688 sent an intro, so it kept waiting for a response...
14689 - bugfix: when you sleep your hidden-service laptop, as soon
14690 as it wakes up it tries to upload a service descriptor, but
14691 socketpair fails for some reason (localhost not up yet?).
14692 now we simply give up on that upload, and we'll try again later.
14693 i'd still like to find the bug though.
14694 - if an intro circ waiting for an ack dies before getting one, then
14696 - we were reusing stale service descriptors and refetching usable
14700 Changes in version 0.0.6pre4 - 2004-04-14
14701 o changes from 0.0.6pre3:
14702 - when bob fails to connect to the rendezvous point, and his
14703 circ didn't fail because of the rendezvous point itself, then
14704 he retries a couple of times
14705 - we expire introduction and rendezvous circs more thoroughly
14706 (sometimes they were hanging around forever)
14707 - we expire unattached rendezvous streams that have been around
14708 too long (they were sticking around forever).
14709 - fix a measly fencepost error that was crashing everybody with
14713 Changes in version 0.0.6pre3 - 2004-04-14
14714 o changes from 0.0.6pre2:
14715 - make hup work again
14716 - fix some memory leaks for dirservers
14717 - allow more skew in rendezvous descriptor timestamps, to help
14718 handle people like blanu who don't know what time it is
14719 - normal circs are 3 hops, but some rend/intro circs are 4, if
14720 the initiator doesn't get to choose the last hop
14721 - send acks for introductions, so alice can know whether to try
14723 - bob publishes intro points more correctly
14724 o changes from 0.0.5:
14725 - fix an assert trigger that's been plaguing us since the days
14726 of 0.0.2prexx (thanks weasel!)
14727 - retry stream correctly when we fail to connect because of
14728 exit-policy-reject (should try another) or can't-resolve-address
14729 (also should try another, because dns on random internet servers
14731 - when we hup a dirserver and we've *removed* a server from the
14732 approved-routers list, now we remove that server from the
14733 in-memory directories too
14736 Changes in version 0.0.6pre2 - 2004-04-08
14737 o We fixed our base32 implementation. Now it works on all architectures.
14740 Changes in version 0.0.6pre1 - 2004-04-08
14742 - Hidden services and rendezvous points are implemented. Go to
14743 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14744 hidden services. (This only works via a socks4a proxy such as
14745 Privoxy, and currently it's quite slow.)
14748 Changes in version 0.0.5 - 2004-03-30
14749 [version bump only]
14752 Changes in version 0.0.5rc3 - 2004-03-29
14753 o Install torrc as torrc.sample -- we no longer clobber your
14755 o Re-enable recommendedversion checking (we broke it in rc2, oops)
14756 o Add in a 'notice' log level for things the operator should hear
14757 but that aren't warnings
14760 Changes in version 0.0.5rc2 - 2004-03-29
14761 o Hold socks connection open until reply is flushed (if possible)
14762 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14763 the dns farm to do it.
14764 o Fix c99 aliasing warnings in rephist.c
14765 o Don't include server descriptors that are older than 24 hours in the
14767 o Give socks 'reject' replies their whole 15s to attempt to flush,
14768 rather than seeing the 60s timeout and assuming the flush had failed.
14769 o Clean automake droppings from the cvs repository
14772 Changes in version 0.0.5rc1 - 2004-03-28
14773 o Fix mangled-state bug in directory fetching (was causing sigpipes).
14774 o Only build circuits after we've fetched the directory: clients were
14775 using only the directory servers before they'd fetched a directory.
14776 This also means longer startup time; so it goes.
14777 o Fix an assert trigger where an OP would fail to handshake, and we'd
14778 expect it to have a nickname.
14779 o Work around a tsocks bug: do a socks reject when AP connection dies
14780 early, else tsocks goes into an infinite loop.
14783 Changes in version 0.0.4 - 2004-03-26
14784 o When connecting to a dirserver or OR and the network is down,
14788 Changes in version 0.0.3 - 2004-03-26
14789 o Warn and fail if server chose a nickname with illegal characters
14790 o Port to Solaris and Sparc:
14791 - include missing header fcntl.h
14792 - have autoconf find -lsocket -lnsl automatically
14793 - deal with hardware word alignment
14794 - make uname() work (solaris has a different return convention)
14795 - switch from using signal() to sigaction()
14796 o Preliminary work on reputation system:
14797 - Keep statistics on success/fail of connect attempts; they're published
14798 by kill -USR1 currently.
14799 - Add a RunTesting option to try to learn link state by creating test
14800 circuits, even when SocksPort is off.
14801 - Remove unused open circuits when there are too many.
14804 Changes in version 0.0.2 - 2004-03-19
14805 - Include strlcpy and strlcat for safer string ops
14806 - define INADDR_NONE so we compile (but still not run) on solaris
14809 Changes in version 0.0.2pre27 - 2004-03-14
14811 - Allow internal tor networks (we were rejecting internal IPs,
14812 now we allow them if they're set explicitly).
14813 - And fix a few endian issues.
14816 Changes in version 0.0.2pre26 - 2004-03-14
14818 - If a stream times out after 15s without a connected cell, don't
14819 try that circuit again: try a new one.
14820 - Retry streams at most 4 times. Then give up.
14821 - When a dirserver gets a descriptor from an unknown router, it
14822 logs its fingerprint (so the dirserver operator can choose to
14823 accept it even without mail from the server operator).
14824 - Inform unapproved servers when we reject their descriptors.
14825 - Make tor build on Windows again. It works as a client, who knows
14827 - Clearer instructions in the torrc for how to set up a server.
14828 - Be more efficient about reading fd's when our global token bucket
14829 (used for rate limiting) becomes empty.
14831 - Stop asserting that computers always go forward in time. It's
14833 - When we sent a cell (e.g. destroy) and then marked an OR connection
14834 expired, we might close it before finishing a flush if the other
14835 side isn't reading right then.
14836 - Don't allow dirservers to start if they haven't defined
14837 RecommendedVersions
14838 - We were caching transient dns failures. Oops.
14839 - Prevent servers from publishing an internal IP as their address.
14840 - Address a strcat vulnerability in circuit.c
14843 Changes in version 0.0.2pre25 - 2004-03-04
14845 - Put the OR's IP in its router descriptor, not its fqdn. That way
14846 we'll stop being stalled by gethostbyname for nodes with flaky dns,
14849 - If the user typed in an address that didn't resolve, the server
14853 Changes in version 0.0.2pre24 - 2004-03-03
14855 - Fix an assertion failure in dns.c, where we were trying to dequeue
14856 a pending dns resolve even if it wasn't pending
14857 - Fix a spurious socks5 warning about still trying to write after the
14858 connection is finished.
14859 - Hold certain marked_for_close connections open until they're finished
14860 flushing, rather than losing bytes by closing them too early.
14861 - Correctly report the reason for ending a stream
14862 - Remove some duplicate calls to connection_mark_for_close
14863 - Put switch_id and start_daemon earlier in the boot sequence, so it
14864 will actually try to chdir() to options.DataDirectory
14865 - Make 'make test' exit(1) if a test fails; fix some unit tests
14866 - Make tor fail when you use a config option it doesn't know about,
14867 rather than warn and continue.
14868 - Make --version work
14869 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
14872 Changes in version 0.0.2pre23 - 2004-02-29
14874 - Print a statement when the first circ is finished, so the user
14875 knows it's working.
14876 - If a relay cell is unrecognized at the end of the circuit,
14877 send back a destroy. (So attacks to mutate cells are more
14879 - New config option 'excludenodes' to avoid certain nodes for circuits.
14880 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
14881 so you can collect coredumps there.
14883 - Fix a bug in tls flushing where sometimes data got wedged and
14884 didn't flush until more data got sent. Hopefully this bug was
14885 a big factor in the random delays we were seeing.
14886 - Make 'connected' cells include the resolved IP, so the client
14887 dns cache actually gets populated.
14888 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14889 - When we time-out on a stream and detach from the circuit, send an
14890 end cell down it first.
14891 - Only warn about an unknown router (in exitnodes, entrynodes,
14892 excludenodes) after we've fetched a directory.
14895 Changes in version 0.0.2pre22 - 2004-02-26
14897 - Servers publish less revealing uname information in descriptors.
14898 - More memory tracking and assertions, to crash more usefully when
14900 - If the default torrc isn't there, just use some default defaults.
14901 Plus provide an internal dirservers file if they don't have one.
14902 - When the user tries to use Tor as an http proxy, give them an http
14903 501 failure explaining that we're a socks proxy.
14904 - Dump a new router.desc on hup, to help confused people who change
14905 their exit policies and then wonder why router.desc doesn't reflect
14907 - Clean up the generic tor.sh init script that we ship with.
14909 - If the exit stream is pending on the resolve, and a destroy arrives,
14910 then the stream wasn't getting removed from the pending list. I
14911 think this was the one causing recent server crashes.
14912 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14913 - When it couldn't resolve any dirservers, it was useless from then on.
14914 Now it reloads the RouterFile (or default dirservers) if it has no
14916 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14917 many users don't even *have* a /usr/local/sbin/.
14920 Changes in version 0.0.2pre21 - 2004-02-18
14922 - There's a ChangeLog file that actually reflects the changelog.
14923 - There's a 'torify' wrapper script, with an accompanying
14924 tor-tsocks.conf, that simplifies the process of using tsocks for
14925 tor. It even has a man page.
14926 - The tor binary gets installed to sbin rather than bin now.
14927 - Retry streams where the connected cell hasn't arrived in 15 seconds
14928 - Clean up exit policy handling -- get the default out of the torrc,
14929 so we can update it without forcing each server operator to fix
14931 - Allow imaps and pop3s in default exit policy
14933 - Prevent picking middleman nodes as the last node in the circuit
14936 Changes in version 0.0.2pre20 - 2004-01-30
14938 - We now have a deb package, and it's in debian unstable. Go to
14939 it, apt-getters. :)
14940 - I've split the TotalBandwidth option into BandwidthRate (how many
14941 bytes per second you want to allow, long-term) and
14942 BandwidthBurst (how many bytes you will allow at once before the cap
14943 kicks in). This better token bucket approach lets you, say, set
14944 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14945 performance while not exceeding your monthly bandwidth quota.
14946 - Push out a tls record's worth of data once you've got it, rather
14947 than waiting until you've read everything waiting to be read. This
14948 may improve performance by pipelining better. We'll see.
14949 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14950 from failed circuits (if they haven't been connected yet) and attach
14952 - Expire old streams that haven't managed to connect. Some day we'll
14953 have them reattach to new circuits instead.
14956 - Fix several memory leaks that were causing servers to become bloated
14958 - Fix a few very rare assert triggers. A few more remain.
14959 - Setuid to User _before_ complaining about running as root.
14962 Changes in version 0.0.2pre19 - 2004-01-07
14964 - Fix deadlock condition in dns farm. We were telling a child to die by
14965 closing the parent's file descriptor to him. But newer children were
14966 inheriting the open file descriptor from the parent, and since they
14967 weren't closing it, the socket never closed, so the child never read
14968 eof, so he never knew to exit. Similarly, dns workers were holding
14969 open other sockets, leading to all sorts of chaos.
14970 - New cleaner daemon() code for forking and backgrounding.
14971 - If you log to a file, it now prints an entry at the top of the
14972 logfile so you know it's working.
14973 - The onionskin challenge length was 30 bytes longer than necessary.
14974 - Started to patch up the spec so it's not quite so out of date.
14977 Changes in version 0.0.2pre18 - 2004-01-02
14979 - Fix endian issues with the 'integrity' field in the relay header.
14980 - Fix a potential bug where connections in state
14981 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14984 Changes in version 0.0.2pre17 - 2003-12-30
14986 - Made --debuglogfile (or any second log file, actually) work.
14987 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14988 adversary could force us into an infinite loop.
14991 - Each onionskin handshake now includes a hash of the computed key,
14992 to prove the server's identity and help perfect forward secrecy.
14993 - Changed cell size from 256 to 512 bytes (working toward compatibility
14995 - Changed cell length to 2 bytes, and moved it to the relay header.
14996 - Implemented end-to-end integrity checking for the payloads of
14998 - Separated streamid from 'recognized' (otherwise circuits will get
14999 messed up when we try to have streams exit from the middle). We
15000 use the integrity-checking to confirm that a cell is addressed to
15002 - Randomize the initial circid and streamid values, so an adversary who
15003 breaks into a node can't learn how many circuits or streams have
15007 Changes in version 0.0.2pre16 - 2003-12-14
15009 - Fixed a bug that made HUP trigger an assert
15010 - Fixed a bug where a circuit that immediately failed wasn't being
15011 counted as a failed circuit in counting retries.
15014 - Now we close the circuit when we get a truncated cell: otherwise we're
15015 open to an anonymity attack where a bad node in the path truncates
15016 the circuit and then we open streams at him.
15017 - Add port ranges to exit policies
15018 - Add a conservative default exit policy
15019 - Warn if you're running tor as root
15020 - on HUP, retry OR connections and close/rebind listeners
15021 - options.EntryNodes: try these nodes first when picking the first node
15022 - options.ExitNodes: if your best choices happen to include any of
15023 your preferred exit nodes, you choose among just those preferred
15025 - options.ExcludedNodes: nodes that are never picked in path building
15028 Changes in version 0.0.2pre15 - 2003-12-03
15029 o Robustness and bugfixes:
15030 - Sometimes clients would cache incorrect DNS resolves, which would
15031 really screw things up.
15032 - An OP that goes offline would slowly leak all its sockets and stop
15034 - A wide variety of bugfixes in exit node selection, exit policy
15035 handling, and processing pending streams when a new circuit is
15037 - Pick nodes for a path only from those the directory says are up
15038 - Choose randomly from all running dirservers, not always the first one
15039 - Increase allowed http header size for directory fetch.
15040 - Stop writing to stderr (if we're daemonized it will be closed).
15041 - Enable -g always, so cores will be more useful to me.
15042 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15045 - Wrote a man page. It lists commonly used options.
15048 - Change default loglevel to warn.
15049 - Make PidFile default to null rather than littering in your CWD.
15050 - OnionRouter config option is now obsolete. Instead it just checks
15052 - Moved to a single unified torrc file for both clients and servers.
15055 Changes in version 0.0.2pre14 - 2003-11-29
15056 o Robustness and bugfixes:
15057 - Force the admin to make the DataDirectory himself
15058 - to get ownership/permissions right
15059 - so clients no longer make a DataDirectory and then never use it
15060 - fix bug where a client who was offline for 45 minutes would never
15061 pull down a directory again
15062 - fix (or at least hide really well) the dns assert bug that was
15063 causing server crashes
15064 - warnings and improved robustness wrt clockskew for certs
15065 - use the native daemon(3) to daemonize, when available
15066 - exit if bind() fails
15067 - exit if neither socksport nor orport is defined
15068 - include our own tor_timegm (Win32 doesn't have its own)
15069 - bugfix for win32 with lots of connections
15070 - fix minor bias in PRNG
15071 - make dirserver more robust to corrupt cached directory
15074 - Wrote the design document (woo)
15076 o Circuit building and exit policies:
15077 - Circuits no longer try to use nodes that the directory has told them
15079 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15080 bitcounts (18.0.0.0/8).
15081 - Make AP connections standby for a circuit if no suitable circuit
15082 exists, rather than failing
15083 - Circuits choose exit node based on addr/port, exit policies, and
15084 which AP connections are standing by
15085 - Bump min pathlen from 2 to 3
15086 - Relay end cells have a payload to describe why the stream ended.
15087 - If the stream failed because of exit policy, try again with a new
15089 - Clients have a dns cache to remember resolved addresses.
15090 - Notice more quickly when we have no working circuits
15093 - APPort is now called SocksPort
15094 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15096 - RecommendedVersions is now a config variable rather than
15097 hardcoded (for dirservers)
15098 - Reloads config on HUP
15099 - Usage info on -h or --help
15100 - If you set User and Group config vars, it'll setu/gid to them.
15103 Changes in version 0.0.2pre13 - 2003-10-19
15104 o General stability:
15105 - SSL_write no longer fails when it returns WANTWRITE and the number
15106 of bytes in the buf has changed by the next SSL_write call.
15107 - Fix segfault fetching directory when network is down
15108 - Fix a variety of minor memory leaks
15109 - Dirservers reload the fingerprints file on HUP, so I don't have
15110 to take down the network when I approve a new router
15111 - Default server config file has explicit Address line to specify fqdn
15114 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15115 - Make listener connections not ever alloc bufs
15117 o Autoconf improvements:
15118 - don't clobber an external CFLAGS in ./configure
15119 - Make install now works
15120 - create var/lib/tor on make install
15121 - autocreate a tor.sh initscript to help distribs
15122 - autocreate the torrc and sample-server-torrc with correct paths
15124 o Log files and Daemonizing now work:
15125 - If --DebugLogFile is specified, log to it at -l debug
15126 - If --LogFile is specified, use it instead of commandline
15127 - If --RunAsDaemon is set, tor forks and backgrounds on startup