1 Changes in version 0.2.4.17-rc - 2013-09-05
2 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
3 series. It adds an emergency step to help us tolerate the massive
4 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
5 circuit-level handshakes now effectively jump the queue compared to
6 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
7 big bug hindering bridge reachability tests.
10 - Relays now process the new "NTor" circuit-level handshake requests
11 with higher priority than the old "TAP" circuit-level handshake
12 requests. We still process some TAP requests to not totally starve
13 0.2.3 clients when NTor becomes popular. A new consensus parameter
14 "NumNTorsPerTAP" lets us tune the balance later if we need to.
15 Implements ticket 9574.
18 - If the circuit build timeout logic is disabled (via the consensus,
19 or because we are an authority), then don't build testing circuits.
20 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
21 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
22 previously they did not, which prevented them from receiving
23 successful connections from relays for self-test or bandwidth
24 testing. Also, when a relay is extending a circuit to a bridge,
25 it needs to send a NETINFO cell, even when the bridge hasn't sent
26 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
27 - If the time to download the next old-style networkstatus is in
28 the future, do not decline to consider whether to download the
29 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
33 - Avoid double-closing the listener socket in our socketpair()
34 replacement (used on Windows) in the case where the addresses on
35 our opened sockets don't match what we expected. Fixes bug 9400;
36 bugfix on 0.0.2pre7. Found by Coverity.
38 o Minor fixes (config options):
39 - Avoid overflows when the user sets MaxCircuitDirtiness to a
40 ridiculously high value, by imposing a (ridiculously high) 30-day
41 maximum on MaxCircuitDirtiness.
42 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
43 message is logged at notice, not at info.
44 - Warn and fail if a server is configured not to advertise any
45 ORPorts at all. (We need *something* to put in our descriptor,
46 or we just won't work.)
49 - Track how many "TAP" and "NTor" circuit handshake requests we get,
50 and how many we complete, and log it every hour to help relay
51 operators follow trends in network load. Addresses ticket 9658.
52 - Update to the August 7 2013 Maxmind GeoLite Country database.
55 Changes in version 0.2.4.16-rc - 2013-08-10
56 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
57 series. It fixes several crash bugs in the 0.2.4 branch.
60 - Fix a bug in the voting algorithm that could yield incorrect results
61 when a non-naming authority declared too many flags. Fixes bug 9200;
62 bugfix on 0.2.0.3-alpha.
63 - Fix an uninitialized read that could in some cases lead to a remote
64 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
65 Anybody running a hidden service on the experimental 0.2.4.x
66 branch should upgrade. (This is, so far as we know, unrelated to
68 - Avoid an assertion failure when processing DNS replies without the
69 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
70 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
71 0.2.4.15-rc. Found by stem integration tests.
74 - Fix an invalid memory read that occured when a pluggable
75 transport proxy failed its configuration protocol.
76 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
77 - When evaluating whether to use a connection that we haven't
78 decided is canonical using a recent link protocol version,
79 decide that it's canonical only if it used address _does_
80 match the desired address. Fixes bug 9309; bugfix on
81 0.2.4.4-alpha. Reported by skruffy.
82 - Make the default behavior of NumDirectoryGuards be to track
83 NumEntryGuards. Now a user who changes only NumEntryGuards will get
84 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
85 - Fix a spurious compilation warning with some older versions of
86 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
89 - Update to the July 3 2013 Maxmind GeoLite Country database.
92 Changes in version 0.2.4.15-rc - 2013-07-01
93 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
94 series. It fixes a few smaller bugs, but generally appears stable.
95 Please test it and let us know whether it is!
98 - When receiving a new configuration file via the control port's
99 LOADCONF command, do not treat the defaults file as absent.
100 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
103 - Issue a warning when running with the bufferevents backend enabled.
104 It's still not stable, and people should know that they're likely
105 to hit unexpected problems. Closes ticket 9147.
108 Changes in version 0.2.4.14-alpha - 2013-06-18
109 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
110 present in 0.2.4.13-alpha.
113 - When we have too much memory queued in circuits (according to a new
114 MaxMemInCellQueues option), close the circuits consuming the most
115 memory. This prevents us from running out of memory as a relay if
116 circuits fill up faster than they can be drained. Fixes bug 9063;
117 bugfix on the 54th commit of Tor. This bug is a further fix beyond
118 bug 6252, whose fix was merged into 0.2.3.21-rc.
120 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
121 where we tried to solve this issue simply by imposing an upper limit
122 on the number of queued cells for a single circuit. That approach
123 proved to be problematic, since there are ways to provoke clients to
124 send a number of cells in excess of any such reasonable limit. Fixes
125 bug 9072; bugfix on 0.2.4.13-alpha.
127 - Limit hidden service descriptors to at most ten introduction
128 points, to slow one kind of guard enumeration. Fixes bug 9002;
129 bugfix on 0.1.1.11-alpha.
132 Changes in version 0.2.4.13-alpha - 2013-06-14
133 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
134 vulnerabilities, makes socks5 username/password circuit isolation
135 actually actually work (this time for sure!), and cleans up a bunch
136 of other issues in preparation for a release candidate.
138 o Major bugfixes (robustness):
139 - Close any circuit that has too many cells queued on it. Fixes
140 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
141 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
142 - Prevent the get_freelists() function from running off the end of
143 the list of freelists if it somehow gets an unrecognized
144 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
146 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
147 when an exit connection with optimistic data succeeds immediately
148 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
150 - Fix a directory authority crash bug when building a consensus
151 using an older consensus as its basis. Fixes bug 8833. Bugfix
155 - Avoid a memory leak where we would leak a consensus body when we
156 find that a consensus which we couldn't previously verify due to
157 missing certificates is now verifiable. Fixes bug 8719; bugfix
159 - We used to always request authority certificates by identity digest,
160 meaning we'd get the newest one even when we wanted one with a
161 different signing key. Then we would complain about being given
162 a certificate we already had, and never get the one we really
163 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
164 resource to request the one we want. Fixes bug 5595; bugfix on
166 - Follow the socks5 protocol when offering username/password
167 authentication. The fix for bug 8117 exposed this bug, and it
168 turns out real-world applications like Pidgin do care. Bugfix on
169 0.2.3.2-alpha; fixes bug 8879.
170 - Prevent failures on Windows Vista and later when rebuilding the
171 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
172 bugfix on 0.2.4.12-alpha.
175 - Fix an impossible buffer overrun in the AES unit tests. Fixes
176 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
177 - If for some reason we fail to write a microdescriptor while
178 rebuilding the cache, do not let the annotations from that
179 microdescriptor linger in the cache file, and do not let the
180 microdescriptor stay recorded as present in its old location.
181 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
182 - Fix a memory leak that would occur whenever a configuration
183 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
184 - Paste the description for PathBias parameters from the man
185 page into or.h, so the code documents them too. Fixes bug 7982;
186 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
187 - Relays now treat a changed IPv6 ORPort as sufficient reason to
188 publish an updated descriptor. Fixes bug 6026; bugfix on
190 - When launching a resolve request on behalf of an AF_UNIX control
191 socket, omit the address field of the new entry connection, used in
192 subsequent controller events, rather than letting tor_dup_addr()
193 set it to "<unknown address type>". Fixes bug 8639; bugfix on
196 o Minor bugfixes (log messages):
197 - Fix a scaling issue in the path bias accounting code that
198 resulted in "Bug:" log messages from either
199 pathbias_scale_close_rates() or pathbias_count_build_success().
200 This represents a bugfix on a previous bugfix: the original fix
201 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
203 - Give a less useless error message when the user asks for an IPv4
204 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
208 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
209 to tolerate bug 8093 for now.
210 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
211 in directory authority votes to describe whether they have enough
212 measured bandwidths to ignore advertised (relay descriptor)
213 bandwidth claims. Resolves ticket 8711.
214 - Update to the June 5 2013 Maxmind GeoLite Country database.
216 o Removed documentation:
217 - Remove some of the older contents of doc/ as obsolete; move others
218 to torspec.git. Fixes bug 8965.
220 o Code simplification and refactoring:
221 - Avoid using character buffers when constructing most directory
222 objects: this approach was unwieldy and error-prone. Instead,
223 build smartlists of strings, and concatenate them when done.
226 Changes in version 0.2.4.12-alpha - 2013-04-18
227 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
228 process for lengthening the guard rotation period, makes directory
229 authority opinions in the consensus a bit less gameable, makes socks5
230 username/password circuit isolation actually work, and fixes a wide
231 variety of other issues.
234 - Raise the default time that a client keeps an entry guard from
235 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
236 2012 paper. (We would make it even longer, but we need better client
237 load balancing first.) Also, make the guard lifetime controllable
238 via a new GuardLifetime torrc option and a GuardLifetime consensus
239 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
240 - Directory authorities now prefer using measured bandwidths to
241 advertised ones when computing flags and thresholds. Resolves
243 - Directory authorities that have more than a threshold number
244 of relays with measured bandwidths now treat relays with unmeasured
245 bandwidths as having bandwidth 0. Resolves ticket 8435.
247 o Major bugfixes (assert / resource use):
248 - Avoid a bug where our response to TLS renegotiation under certain
249 network conditions could lead to a busy-loop, with 100% CPU
250 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
251 - Avoid an assertion when we discover that we'd like to write a cell
252 onto a closing connection: just discard the cell. Fixes another
253 case of bug 7350; bugfix on 0.2.4.4-alpha.
255 o Major bugfixes (client-side privacy):
256 - When we mark a circuit as unusable for new circuits, have it
257 continue to be unusable for new circuits even if MaxCircuitDirtiness
258 is increased too much at the wrong time, or the system clock jumps
259 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
260 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
261 which have resolved to internal addresses") is set, apply that
262 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
263 - When an exit relay rejects a stream with reason "exit policy", but
264 we only know an exit policy summary (e.g. from the microdesc
265 consensus) for it, do not mark the relay as useless for all exiting.
266 Instead, mark just the circuit as unsuitable for that particular
267 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
268 - Allow applications to get proper stream isolation with
269 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
270 username/password authentication also offer "no authentication". Tor
271 had previously preferred "no authentication", so the applications
272 never actually sent Tor their auth details. Now Tor selects
273 username/password authentication if it's offered. You can disable
274 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
275 bug 8117; bugfix on 0.2.3.3-alpha.
277 o Major bugfixes (other):
278 - When unable to find any working directory nodes to use as a
279 directory guard, give up rather than adding the same non-working
280 nodes to the directory guard list over and over. Fixes bug 8231;
281 bugfix on 0.2.4.8-alpha.
284 - Reject as invalid most directory objects containing a NUL.
285 Belt-and-suspender fix for bug 8037.
286 - In our testsuite, create temporary directories with a bit more
287 entropy in their name to make name collisions less likely. Fixes
289 - Add CACHED keyword to ADDRMAP events in the control protocol
290 to indicate whether a DNS result will be cached or not. Resolves
292 - Update to the April 3 2013 Maxmind GeoLite Country database.
294 o Minor features (build):
295 - Detect and reject attempts to build Tor with threading support
296 when OpenSSL has been compiled without threading support.
298 - Clarify that when autoconf is checking for nacl, it is checking
299 specifically for nacl with a fast curve25519 implementation.
301 - Warn if building on a platform with an unsigned time_t: there
302 are too many places where Tor currently assumes that time_t can
303 hold negative values. We'd like to fix them all, but probably
306 o Minor bugfixes (build):
307 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
308 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
309 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
310 - Add the old src/or/micro-revision.i filename to CLEANFILES.
311 On the off chance that somebody has one, it will go away as soon
312 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
313 - Build Tor correctly on 32-bit platforms where the compiler can build
314 but not run code using the "uint128_t" construction. Fixes bug 8587;
315 bugfix on 0.2.4.8-alpha.
316 - Fix compilation warning with some versions of clang that would
317 prefer the -Wswitch-enum compiler flag to warn about switch
318 statements with missing enum values, even if those switch
319 statements have a "default:" statement. Fixes bug 8598; bugfix
322 o Minor bugfixes (protocol):
323 - Fix the handling of a TRUNCATE cell when it arrives while the
324 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
325 - Fix a misframing issue when reading the version numbers in a
326 VERSIONS cell. Previously we would recognize [00 01 00 02] as
327 'version 1, version 2, and version 0x100', when it should have
328 only included versions 1 and 2. Fixes bug 8059; bugfix on
329 0.2.0.10-alpha. Reported pseudonymously.
330 - Make the format and order of STREAM events for DNS lookups
331 consistent among the various ways to launch DNS lookups. Fixes
332 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
333 - Correct our check for which versions of Tor support the EXTEND2
334 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
335 later, when support was really added in version 0.2.4.8-alpha.
336 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
338 o Minor bugfixes (other):
339 - Correctly store microdescriptors and extrainfo descriptors with
340 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
341 Bug reported by "cypherpunks".
342 - Increase the width of the field used to remember a connection's
343 link protocol version to two bytes. Harmless for now, since the
344 only currently recognized versions are one byte long. Reported
345 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
346 - If the state file's path bias counts are invalid (presumably from a
347 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
348 additional checks and log messages to the scaling of Path Bias
349 counts, in case there still are remaining issues with scaling.
350 Should help resolve bug 8235.
351 - Eliminate several instances where we use "Nickname=ID" to refer to
352 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
353 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
354 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
356 o Minor bugfixes (syscalls):
357 - Always check the return values of functions fcntl() and
358 setsockopt(). We don't believe these are ever actually failing in
359 practice, but better safe than sorry. Also, checking these return
360 values should please analysis tools like Coverity. Patch from
361 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
362 - Use direct writes rather than stdio when building microdescriptor
363 caches, in an attempt to mitigate bug 8031, or at least make it
366 o Minor bugfixes (config):
367 - When rejecting a configuration because we were unable to parse a
368 quoted string, log an actual error message. Fixes bug 7950; bugfix
370 - Behave correctly when the user disables LearnCircuitBuildTimeout
371 but doesn't tell us what they would like the timeout to be. Fixes
372 bug 6304; bugfix on 0.2.2.14-alpha.
373 - When autodetecting the number of CPUs, use the number of available
374 CPUs in preference to the number of configured CPUs. Inform the
375 user if this reduces the number of available CPUs. Fixes bug 8002;
376 bugfix on 0.2.3.1-alpha.
377 - Make it an error when you set EntryNodes but disable UseGuardNodes,
378 since it will (surprisingly to some users) ignore EntryNodes. Fixes
379 bug 8180; bugfix on 0.2.3.11-alpha.
380 - Allow TestingTorNetworks to override the 4096-byte minimum for
381 the Fast threshold. Otherwise they can't bootstrap until they've
382 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
383 - Fix some logic errors when the user manually overrides the
384 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
387 o Minor bugfixes (log messages to help diagnose bugs):
388 - If we fail to free a microdescriptor because of bug 7164, log
389 the filename and line number from which we tried to free it.
390 - Add another diagnostic to the heartbeat message: track and log
391 overhead that TLS is adding to the data we write. If this is
392 high, we are sending too little data to SSL_write at a time.
393 Diagnostic for bug 7707.
394 - Add more detail to a log message about relaxed timeouts, to help
396 - Warn more aggressively when flushing microdescriptors to a
397 microdescriptor cache fails, in an attempt to mitigate bug 8031,
398 or at least make it more diagnosable.
399 - Improve debugging output to help track down bug 8185 ("Bug:
400 outgoing relay cell has n_chan==NULL. Dropping.")
401 - Log the purpose of a path-bias testing circuit correctly.
402 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
404 o Minor bugfixes (0.2.4.x log messages that were too noisy):
405 - Don't attempt to relax the timeout of already opened 1-hop circuits.
406 They might never timeout. This should eliminate some/all cases of
407 the relaxed timeout log message.
408 - Use circuit creation time for network liveness evaluation. This
409 should eliminate warning log messages about liveness caused
410 by changes in timeout evaluation. Fixes bug 6572; bugfix on
412 - Reduce a path bias length check from notice to info. The message
413 is triggered when creating controller circuits. Fixes bug 8196;
414 bugfix on 0.2.4.8-alpha.
415 - Fix a path state issue that triggered a notice during relay startup.
416 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
417 - Reduce occurrences of warns about circuit purpose in
418 connection_ap_expire_building(). Fixes bug 8477; bugfix on
421 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
422 - If we encounter a write failure on a SOCKS connection before we
423 finish our SOCKS handshake, don't warn that we closed the
424 connection before we could send a SOCKS reply. Fixes bug 8427;
425 bugfix on 0.1.0.1-rc.
426 - Correctly recognize that [::1] is a loopback address. Fixes
427 bug 8377; bugfix on 0.2.1.3-alpha.
428 - Fix a directory authority warn caused when we have a large amount
429 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
430 - Don't log inappropriate heartbeat messages when hibernating: a
431 hibernating node is _expected_ to drop out of the consensus,
432 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
433 bugfix on 0.2.3.1-alpha.
434 - Don't complain about bootstrapping problems while hibernating.
435 These complaints reflect a general code problem, but not one
436 with any problematic effects (no connections are actually
437 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
439 o Documentation fixes:
440 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
441 names match. Fixes bug 7768.
442 - Make the torify manpage no longer refer to tsocks; torify hasn't
443 supported tsocks since 0.2.3.14-alpha.
444 - Make the tor manpage no longer reference tsocks.
445 - Fix the GeoIPExcludeUnknown documentation to refer to
446 ExcludeExitNodes rather than the currently nonexistent
447 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
450 - The tor-tsocks.conf is no longer distributed or installed. We
451 recommend that tsocks users use torsocks instead. Resolves
455 Changes in version 0.2.4.11-alpha - 2013-03-11
456 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
457 more robust, makes hidden service authentication work again, and
458 resolves a DPI fingerprint for Tor's SSL transport.
460 o Major features (directory authorities):
461 - Directory authorities now support a new consensus method (17)
462 where they cap the published bandwidth of servers for which
463 insufficient bandwidth measurements exist. Fixes part of bug 2286.
464 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
465 serve any v2 directory information. Now we can test disabling the
466 old deprecated v2 directory format, and see whether doing so has
467 any effect on network load. Begins to fix bug 6783.
468 - Directory authorities now include inside each vote a statement of
469 the performance thresholds they used when assigning flags.
470 Implements ticket 8151.
472 o Major bugfixes (directory authorities):
473 - Stop marking every relay as having been down for one hour every
474 time we restart a directory authority. These artificial downtimes
475 were messing with our Stable and Guard flag calculations. Fixes
476 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
478 o Major bugfixes (hidden services):
479 - Allow hidden service authentication to succeed again. When we
480 refactored the hidden service introduction code back
481 in 0.2.4.1-alpha, we didn't update the code that checks
482 whether authentication information is present, causing all
483 authentication checks to return "false". Fix for bug 8207; bugfix
484 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
486 o Minor features (relays, bridges):
487 - Make bridge relays check once a minute for whether their IP
488 address has changed, rather than only every 15 minutes. Resolves
490 - Refactor resolve_my_address() so it returns the method by which we
491 decided our public IP address (explicitly configured, resolved from
492 explicit hostname, guessed from interfaces, learned by gethostname).
493 Now we can provide more helpful log messages when a relay guesses
494 its IP address incorrectly (e.g. due to unexpected lines in
495 /etc/hosts). Resolves ticket 2267.
496 - Teach bridge-using clients to avoid 0.2.2 bridges when making
497 microdescriptor-related dir requests, and only fall back to normal
498 descriptors if none of their bridges can handle microdescriptors
499 (as opposed to the fix in ticket 4013, which caused them to fall
500 back to normal descriptors if *any* of their bridges preferred
501 them). Resolves ticket 4994.
502 - Randomize the lifetime of our SSL link certificate, so censors can't
503 use the static value for filtering Tor flows. Resolves ticket 8443;
504 related to ticket 4014 which was included in 0.2.2.33.
506 o Minor features (portability):
507 - Tweak the curve25519-donna*.c implementations to tolerate systems
508 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
509 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
510 the signs of types during autoconf. This is better than our old
511 approach, which didn't work when cross-compiling.
512 - Detect the sign of enum values, rather than assuming that MSC is the
513 only compiler where enum types are all signed. Fixes bug 7727;
514 bugfix on 0.2.4.10-alpha.
516 o Minor features (other):
517 - Say "KBytes" rather than "KB" in the man page (for various values
518 of K), to further reduce confusion about whether Tor counts in
519 units of memory or fractions of units of memory. Resolves ticket 7054.
520 - Clear the high bit on curve25519 public keys before passing them to
521 our backend, in case we ever wind up using a backend that doesn't do
522 so itself. If we used such a backend, and *didn't* clear the high bit,
523 we could wind up in a situation where users with such backends would
524 be distinguishable from users without. Fixes bug 8121; bugfix on
526 - Update to the March 6 2013 Maxmind GeoLite Country database.
528 o Minor bugfixes (clients):
529 - When we receive a RELAY_END cell with the reason DONE, or with no
530 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
531 status as "connection refused". Previously we reported these cases
532 as success but then immediately closed the connection. Fixes bug
533 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
534 - Downgrade an assertion in connection_ap_expire_beginning to an
535 LD_BUG message. The fix for bug 8024 should prevent this message
536 from displaying, but just in case, a warn that we can diagnose
537 is better than more assert crashes. Fixes bug 8065; bugfix on
539 - Lower path use bias thresholds to .80 for notice and .60 for warn.
540 Also make the rate limiting flags for the path use bias log messages
541 independent from the original path bias flags. Fixes bug 8161;
542 bugfix on 0.2.4.10-alpha.
544 o Minor bugfixes (relays):
545 - Stop trying to resolve our hostname so often (e.g. every time we
546 think about doing a directory fetch). Now we reuse the cached
547 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
548 and 2410 (bugfix on 0.1.2.2-alpha).
549 - Stop sending a stray "(null)" in some cases for the server status
550 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
552 - When choosing which stream on a formerly stalled circuit to wake
553 first, make better use of the platform's weak RNG. Previously,
554 we had been using the % ("modulo") operator to try to generate a
555 1/N chance of picking each stream, but this behaves badly with
556 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
558 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
559 Irix's random() only return 15 bits; Solaris's random() returns more
560 bits but its RAND_MAX says it only returns 15, and so on. Motivated
561 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
563 o Minor bugfixes (directory authorities):
564 - Directory authorities now use less space when formatting identical
565 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
568 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
569 - Avoid leaking memory if we fail to compute a consensus signature
570 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
571 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
573 - Fix a memory leak during safe-cookie controller authentication.
574 Bugfix on 0.2.3.13-alpha.
575 - Avoid memory leak of IPv6 policy content if we fail to format it into
576 a router descriptor. Bugfix on 0.2.4.7-alpha.
578 o Minor bugfixes (other code correctness issues):
579 - Avoid a crash if we fail to generate an extrainfo descriptor.
580 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
582 - When detecting the largest possible file descriptor (in order to
583 close all file descriptors when launching a new program), actually
584 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
585 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
587 - Fix a copy-and-paste error when adding a missing A1 to a routerset
588 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
589 Bugfix on 0.2.4.10-alpha.
590 - Fix an impossible-to-trigger integer overflow when estimating how
591 long our onionskin queue would take. (This overflow would require us
592 to accept 4 million onionskins before processing 100 of them.) Fixes
593 bug 8210; bugfix on 0.2.4.10-alpha.
595 o Code simplification and refactoring:
596 - Add a wrapper function for the common "log a message with a
600 Changes in version 0.2.4.10-alpha - 2013-02-04
601 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
602 certain attacks that flood the network with relays; changes the queue
603 for circuit create requests from a sized-based limit to a time-based
604 limit; resumes building with MSVC on Windows; and fixes a wide variety
607 o Major bugfixes (directory authority):
608 - When computing directory thresholds, ignore any rejected-as-sybil
609 nodes during the computation so that they can't influence Fast,
610 Guard, etc. (We should have done this for proposal 109.) Fixes
612 - When marking a node as a likely sybil, reset its uptime metrics
613 to zero, so that it cannot time towards getting marked as Guard,
614 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
618 - When a TLS write is partially successful but incomplete, remember
619 that the flushed part has been flushed, and notice that bytes were
620 actually written. Reported and fixed pseudonymously. Fixes bug
621 7708; bugfix on Tor 0.1.0.5-rc.
622 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
623 ID: these could be used to create unexpected streams and circuits
624 which would count as "present" to some parts of Tor but "absent"
625 to others, leading to zombie circuits and streams or to a bandwidth
626 denial-of-service. Fixes bug 7889; bugfix on every released version
627 of Tor. Reported by "oftc_must_be_destroyed".
628 - Rename all macros in our local copy of queue.h to begin with "TOR_".
629 This change seems the only good way to permanently prevent conflicts
630 with queue.h on various operating systems. Fixes bug 8107; bugfix
633 o Major features (relay):
634 - Instead of limiting the number of queued onionskins (aka circuit
635 create requests) to a fixed, hard-to-configure number, we limit
636 the size of the queue based on how many we expect to be able to
637 process in a given amount of time. We estimate the time it will
638 take to process an onionskin based on average processing time
639 of previous onionskins. Closes ticket 7291. You'll never have to
640 configure MaxOnionsPending again.
642 o Major features (portability):
643 - Resume building correctly with MSVC and Makefile.nmake. This patch
644 resolves numerous bugs and fixes reported by ultramage, including
645 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
646 - Make the ntor and curve25519 code build correctly with MSVC.
647 Fix on 0.2.4.8-alpha.
650 - When directory authorities are computing thresholds for flags,
651 never let the threshold for the Fast flag fall below 4096
652 bytes. Also, do not consider nodes with extremely low bandwidths
653 when deciding thresholds for various directory flags. This change
654 should raise our threshold for Fast relays, possibly in turn
655 improving overall network performance; see ticket 1854. Resolves
657 - The Tor client now ignores sub-domain components of a .onion
658 address. This change makes HTTP "virtual" hosting
659 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
660 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
661 hosted on the same hidden service. Implements proposal 204.
662 - We compute the overhead from passing onionskins back and forth to
663 cpuworkers, and report it when dumping statistics in response to
664 SIGUSR1. Supports ticket 7291.
666 o Minor features (path selection):
667 - When deciding whether we have enough descriptors to build circuits,
668 instead of looking at raw relay counts, look at which fraction
669 of (bandwidth-weighted) paths we're able to build. This approach
670 keeps clients from building circuits if their paths are likely to
671 stand out statistically. The default fraction of paths needed is
672 taken from the consensus directory; you can override it with the
673 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
674 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
675 and we have GeoIP information, also exclude all nodes with unknown
676 countries "??" and "A1". This behavior is controlled by the
677 new GeoIPExcludeUnknown option: you can make such nodes always
678 excluded with "GeoIPExcludeUnknown 1", and disable the feature
679 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
680 gets you the default behavior. Implements feature 7706.
681 - Path Use Bias: Perform separate accounting for successful circuit
682 use. Keep separate statistics on stream attempt rates versus stream
683 success rates for each guard. Provide configurable thresholds to
684 determine when to emit log messages or disable use of guards that
685 fail too many stream attempts. Resolves ticket 7802.
687 o Minor features (log messages):
688 - When learning a fingerprint for a bridge, log its corresponding
689 transport type. Implements ticket 7896.
690 - Improve the log message when "Bug/attack: unexpected sendme cell
691 from client" occurs, to help us track bug 8093.
694 - Remove a couple of extraneous semicolons that were upsetting the
695 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
696 bugfix on 0.2.2.1-alpha.
697 - Remove a source of rounding error during path bias count scaling;
698 don't count cannibalized circuits as used for path bias until we
699 actually try to use them; and fix a circuit_package_relay_cell()
700 warning message about n_chan==NULL. Fixes bug 7802.
701 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
702 actually link against nacl when we're configured to use it. Fixes
703 bug 7972; bugfix on 0.2.4.8-alpha.
704 - Compile correctly with the --disable-curve25519 option. Fixes
705 bug 8153; bugfix on 0.2.4.8-alpha.
707 o Build improvements:
708 - Do not report status verbosely from autogen.sh unless the -v flag
709 is specified. Fixes issue 4664. Patch from Onizuka.
710 - Replace all calls to snprintf() outside of src/ext with
711 tor_snprintf(). Also remove the #define to replace snprintf with
712 _snprintf on Windows; they have different semantics, and all of
713 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
714 - Try to detect if we are ever building on a platform where
715 memset(...,0,...) does not set the value of a double to 0.0. Such
716 platforms are permitted by the C standard, though in practice
717 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
718 currently support them, but it's better to detect them and fail
719 than to perform erroneously.
722 - Stop exporting estimates of v2 and v3 directory traffic shares
723 in extrainfo documents. They were unneeded and sometimes inaccurate.
724 Also stop exporting any v2 directory request statistics. Resolves
726 - Drop support for detecting and warning about versions of Libevent
727 before 1.3e. Nothing reasonable ships with them any longer;
728 warning the user about them shouldn't be needed. Resolves ticket
731 o Code simplifications and refactoring:
732 - Rename "isin" functions to "contains", for grammar. Resolves
734 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
735 with the natural logarithm function from the system libm. Resolves
739 Changes in version 0.2.4.9-alpha - 2013-01-15
740 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
744 - Fix backward compatibility logic when receiving an embedded ntor
745 handshake tunneled in a CREATE cell. This clears up the "Bug:
746 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
750 Changes in version 0.2.4.8-alpha - 2013-01-14
751 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
752 risks, adds a new stronger and faster circuit handshake, and offers
753 stronger and faster link encryption when both sides support it.
756 - Preliminary support for directory guards (proposal 207): when
757 possible, clients now use their entry guards for non-anonymous
758 directory requests. This can help prevent client enumeration. Note
759 that this behavior only works when we have a usable consensus
760 directory, and when options about what to download are more or less
761 standard. In the future we should re-bootstrap from our guards,
762 rather than re-bootstrapping from the preconfigured list of
763 directory sources that ships with Tor. Resolves ticket 6526.
764 - Tor relays and clients now support a better CREATE/EXTEND cell
765 format, allowing the sender to specify multiple address, identity,
766 and handshake types. Implements Robert Ransom's proposal 200;
769 o Major features (new circuit handshake):
770 - Tor now supports a new circuit extension handshake designed by Ian
771 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
772 circuit extension handshake, later called "TAP", was a bit slow
773 (especially on the relay side), had a fragile security proof, and
774 used weaker keys than we'd now prefer. The new circuit handshake
775 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
776 function, making it significantly more secure than the older
777 handshake, and significantly faster. Tor can use one of two built-in
778 pure-C curve25519-donna implementations by Adam Langley, or it
779 can link against the "nacl" library for a tuned version if present.
781 The built-in version is very fast for 64-bit systems when building
782 with GCC. The built-in 32-bit version is still faster than the
783 old TAP protocol, but using libnacl is better on most such hosts.
785 Clients don't currently use this protocol by default, since
786 comparatively few clients support it so far. To try it, set
787 UseNTorHandshake to 1.
789 Implements proposal 216; closes ticket 7202.
791 o Major features (better link encryption):
792 - Relays can now enable the ECDHE TLS ciphersuites when available
793 and appropriate. These ciphersuites let us negotiate forward-secure
794 TLS secret keys more safely and more efficiently than with our
795 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
796 public relays prefer the (faster) P224 group, and bridges prefer
797 the (more common) P256 group; you can override this with the
800 Enabling these ciphers was a little tricky, since for a long time,
801 clients had been claiming to support them without actually doing
802 so, in order to foil fingerprinting. But with the client-side
803 implementation of proposal 198 in 0.2.3.17-beta, clients can now
804 match the ciphers from recent Firefox versions *and* list the
805 ciphers they actually mean, so relays can believe such clients
806 when they advertise ECDHE support in their TLS ClientHello messages.
808 This feature requires clients running 0.2.3.17-beta or later,
809 and requires both sides to be running OpenSSL 1.0.0 or later
810 with ECC support. OpenSSL 1.0.1, with the compile-time option
811 "enable-ec_nistp_64_gcc_128", is highly recommended.
813 Implements the relay side of proposal 198; closes ticket 7200.
816 - Avoid crashing when, as a relay without IPv6-exit support, a
817 client insists on getting an IPv6 address or nothing. Fixes bug
818 7814; bugfix on 0.2.4.7-alpha.
821 - Improve circuit build timeout handling for hidden services.
822 In particular: adjust build timeouts more accurately depending
823 upon the number of hop-RTTs that a particular circuit type
824 undergoes. Additionally, launch intro circuits in parallel
825 if they timeout, and take the first one to reply as valid.
826 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
827 separate error codes; or at least, don't break for that reason.
828 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
829 - Update to the January 2 2013 Maxmind GeoLite Country database.
831 o Minor features (testing):
832 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
833 (P-256) Diffie-Hellman handshakes to src/or/bench.
834 - Add benchmark functions to test onion handshake performance.
836 o Minor features (path bias detection):
837 - Alter the Path Bias log messages to be more descriptive in terms
838 of reporting timeouts and other statistics.
839 - Create three levels of Path Bias log messages, as opposed to just
840 two. These are configurable via consensus as well as via the torrc
841 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
842 The default values are 0.70, 0.50, and 0.30 respectively.
843 - Separate the log message levels from the decision to drop guards,
844 which also is available via torrc option PathBiasDropGuards.
845 PathBiasDropGuards still defaults to 0 (off).
846 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
847 in combination with PathBiasExtremeRate.
848 - Increase the default values for PathBiasScaleThreshold and
849 PathBiasCircThreshold from (200, 20) to (300, 150).
850 - Add in circuit usage accounting to path bias. If we try to use a
851 built circuit but fail for any reason, it counts as path bias.
852 Certain classes of circuits where the adversary gets to pick your
853 destination node are exempt from this accounting. Usage accounting
854 can be specifically disabled via consensus parameter or torrc.
855 - Convert all internal path bias state to double-precision floating
856 point, to avoid roundoff error and other issues.
857 - Only record path bias information for circuits that have completed
858 *two* hops. Assuming end-to-end tagging is the attack vector, this
859 makes us more resilient to ambient circuit failure without any
860 detection capability loss.
862 o Minor bugfixes (log messages):
863 - Rate-limit the "No circuits are opened. Relaxed timeout for a
864 circuit with channel state open..." message to once per hour to
865 keep it from filling the notice logs. Mitigates bug 7799 but does
866 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
867 - Avoid spurious warnings when configuring multiple client ports of
868 which only some are nonlocal. Previously, we had claimed that some
869 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
872 o Code simplifications and refactoring:
873 - Get rid of a couple of harmless clang warnings, where we compared
874 enums to ints. These warnings are newly introduced in clang 3.2.
875 - Split the onion.c file into separate modules for the onion queue
876 and the different handshakes it supports.
877 - Remove the marshalling/unmarshalling code for sending requests to
878 cpuworkers over a socket, and instead just send structs. The
879 recipient will always be the same Tor binary as the sender, so
880 any encoding is overkill.
883 Changes in version 0.2.4.7-alpha - 2012-12-24
884 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
885 directory mirrors for more robust bootstrapping; fixes more issues where
886 clients with changing network conditions refuse to make any circuits;
887 adds initial support for exiting to IPv6 addresses; resumes being able
888 to update our GeoIP database, and includes the geoip6 file this time;
889 turns off the client-side DNS cache by default due to privacy risks;
890 and fixes a variety of other issues.
892 o Major features (client resilience):
893 - Add a new "FallbackDir" torrc option to use when we can't use
894 a directory mirror from the consensus (either because we lack a
895 consensus, or because they're all down). Currently, all authorities
896 are fallbacks by default, and there are no other default fallbacks,
897 but that will change. This option will allow us to give clients a
898 longer list of servers to try to get a consensus from when first
899 connecting to the Tor network, and thereby reduce load on the
900 directory authorities. Implements proposal 206, "Preconfigured
901 directory sources for bootstrapping". We also removed the old
902 "FallbackNetworkstatus" option, since we never got it working well
903 enough to use it. Closes bug 572.
904 - If we have no circuits open, use a relaxed timeout (the
905 95-percentile cutoff) until a circuit succeeds. This heuristic
906 should allow Tor to succeed at building circuits even when the
907 network connection drastically changes. Should help with bug 3443.
909 o Major features (IPv6):
910 - Tor now has (alpha) support for exiting to IPv6 addresses. To
911 enable it as an exit node, make sure that you have IPv6
912 connectivity, then set the IPv6Exit flag to 1. Also make sure your
913 exit policy reads as you would like: the address * applies to all
914 address families, whereas *4 is IPv4 address only, and *6 is IPv6
915 addresses only. On the client side, you'll need to wait until the
916 authorities have upgraded, wait for enough exits to support IPv6,
917 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
918 ticket 5547, implements proposal 117 as revised in proposal 208.
920 We DO NOT recommend that clients with actual anonymity needs start
921 using IPv6 over Tor yet, since not enough exits support it yet.
923 o Major features (geoip database):
924 - Maxmind began labelling Tor relays as being in country "A1",
925 which breaks by-country node selection inside Tor. Now we use a
926 script to replace "A1" ("Anonymous Proxy") entries in our geoip
927 file with real country codes. This script fixes about 90% of "A1"
928 entries automatically and uses manual country code assignments to
929 fix the remaining 10%. See src/config/README.geoip for details.
930 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
931 Country database, as modified above.
933 o Major bugfixes (client-side DNS):
934 - Turn off the client-side DNS cache by default. Updating and using
935 the DNS cache is now configurable on a per-client-port
936 level. SOCKSPort, DNSPort, etc lines may now contain
937 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
938 cache these types of DNS answers when we receive them from an
939 exit node in response to an application request on this port, and
940 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
941 cached DNS answers of these types, we shouldn't use them. It's
942 potentially risky to use cached DNS answers at the client, since
943 doing so can indicate to one exit what answers we've gotten
944 for DNS lookups in the past. With IPv6, this becomes especially
945 problematic. Using cached DNS answers for requests on the same
946 circuit would present less linkability risk, since all traffic
947 on a circuit is already linkable, but it would also provide
948 little performance benefit: the exit node caches DNS replies
949 too. Implements a simplified version of Proposal 205. Implements
952 o Major bugfixes (other):
953 - Alter circuit build timeout measurement to start at the point
954 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
955 initialization). This should make our timeout measurements more
956 uniform. Previously, we were sometimes including ORconn setup time
957 in our circuit build time measurements. Should resolve bug 3443.
958 - Fix an assertion that could trigger in hibernate_go_dormant() when
959 closing an or_connection_t: call channel_mark_for_close() rather
960 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
962 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
963 7655; bugfix on 0.2.4.6-alpha.
966 - Add a new torrc option "ServerTransportListenAddr" to let bridge
967 operators select the address where their pluggable transports will
968 listen for connections. Resolves ticket 7013.
969 - Allow an optional $ before the node identity digest in the
970 controller command GETINFO ns/id/<identity>, for consistency with
971 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
972 - Log packaged cell fullness as part of the heartbeat message.
973 Diagnosis to try to determine the extent of bug 7743.
975 o Minor features (IPv6):
976 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
977 prefer to hand out virtual IPv6 addresses, since there are more of
978 them and we can't run out. To override this behavior and make IPv4
979 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
980 or DNSPort you're using for resolving. Implements ticket 7571.
981 - AutomapHostsOnResolve responses are now randomized, to avoid
982 annoying situations where Tor is restarted and applications
983 connect to the wrong addresses.
984 - Never try more than 1000 times to pick a new virtual address when
985 AutomapHostsOnResolve is set. That's good enough so long as we
986 aren't close to handing out our entire virtual address space;
987 if you're getting there, it's best to switch to IPv6 virtual
991 - The ADDRMAP command can no longer generate an ill-formed error
992 code on a failed MAPADDRESS. It now says "internal" rather than
993 an English sentence fragment with spaces in the middle. Bugfix on
995 - Fix log messages and comments to avoid saying "GMT" when we mean
996 "UTC". Fixes bug 6113.
997 - Compile on win64 using mingw64. Fixes bug 7260; patches from
999 - Fix a crash when debugging unit tests on Windows: deallocate a
1000 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1001 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1004 - The DirServer option is now DirAuthority, for consistency with
1005 current naming patterns. You can still use the old DirServer form.
1007 o Code simplification and refactoring:
1008 - Move the client-side address-map/virtual-address/DNS-cache code
1009 out of connection_edge.c into a new addressmap.c module.
1010 - Remove unused code for parsing v1 directories and "running routers"
1011 documents. Fixes bug 6887.
1014 Changes in version 0.2.3.25 - 2012-11-19
1015 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1016 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1017 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1018 programmer, and friend. Unstinting in his dedication to the cause of
1019 freedom, he inspired and helped many of us as we began our work on
1020 anonymity, and inspires us still. Please honor his memory by writing
1021 software to protect people's freedoms, and by helping others to do so.
1023 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1024 significantly reduced directory overhead (via microdescriptors),
1025 enormous crypto performance improvements for fast relays on new
1026 enough hardware, a new v3 TLS handshake protocol that can better
1027 resist fingerprinting, support for protocol obfuscation plugins (aka
1028 pluggable transports), better scalability for hidden services, IPv6
1029 support for bridges, performance improvements like allowing clients
1030 to skip the first round-trip on the circuit ("optimistic data") and
1031 refilling token buckets more often, a new "stream isolation" design
1032 to isolate different applications on different circuits, and many
1033 stability, security, and privacy fixes.
1036 - Tor tries to wipe potentially sensitive data after using it, so
1037 that if some subsequent security failure exposes Tor's memory,
1038 the damage will be limited. But we had a bug where the compiler
1039 was eliminating these wipe operations when it decided that the
1040 memory was no longer visible to a (correctly running) program,
1041 hence defeating our attempt at defense in depth. We fix that
1042 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1043 is unlikely to optimize away. Future versions of Tor may use
1044 a less ridiculously heavy approach for this. Fixes bug 7352.
1045 Reported in an article by Andrey Karpov.
1048 - Fix a harmless bug when opting against publishing a relay descriptor
1049 because DisableNetwork is set. Fixes bug 7464; bugfix on
1053 Changes in version 0.2.4.6-alpha - 2012-11-13
1054 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1055 makes our defense-in-depth memory wiping more reliable, and begins to
1056 count IPv6 addresses in bridge statistics,
1059 - Fix an assertion failure that could occur when closing a connection
1060 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1062 - Tor tries to wipe potentially sensitive data after using it, so
1063 that if some subsequent security failure exposes Tor's memory,
1064 the damage will be limited. But we had a bug where the compiler
1065 was eliminating these wipe operations when it decided that the
1066 memory was no longer visible to a (correctly running) program,
1067 hence defeating our attempt at defense in depth. We fix that
1068 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1069 is unlikely to optimize away. Future versions of Tor may use
1070 a less ridiculously heavy approach for this. Fixes bug 7352.
1071 Reported in an article by Andrey Karpov.
1074 - Add GeoIP database for IPv6 addresses. The new config option
1076 - Bridge statistics now count bridge clients connecting over IPv6:
1077 bridge statistics files now list "bridge-ip-versions" and
1078 extra-info documents list "geoip6-db-digest". The control protocol
1079 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1080 implementation by "shkoo", addressing ticket 5055.
1083 - Warn when we are binding low ports when hibernation is enabled;
1084 previously we had warned when we were _advertising_ low ports with
1085 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1086 - Fix a harmless bug when opting against publishing a relay descriptor
1087 because DisableNetwork is set. Fixes bug 7464; bugfix on
1089 - Add warning message when a managed proxy dies during configuration.
1090 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1091 - Fix a linking error when building tor-fw-helper without miniupnp.
1092 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1093 - Check for closing an or_connection_t without going through correct
1094 channel functions; emit a warning and then call
1095 connection_or_close_for_error() so we don't assert as in bugs 7212
1097 - Compile correctly on compilers without C99 designated initializer
1098 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1099 - Avoid a possible assert that can occur when channel_send_destroy() is
1100 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1101 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1102 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1103 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1104 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1106 o Code simplification and refactoring:
1107 - Start using OpenBSD's implementation of queue.h, so that we don't
1108 need to hand-roll our own pointer and list structures whenever we
1109 need them. (We can't rely on a sys/queue.h, since some operating
1110 systems don't have them, and the ones that do have them don't all
1111 present the same extensions.)
1114 Changes in version 0.2.4.5-alpha - 2012-10-25
1115 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1116 two important security vulnerabilities that could lead to remotely
1117 triggerable relay crashes, fix a major bug that was preventing clients
1118 from choosing suitable exit nodes, and refactor some of our code.
1120 o Major bugfixes (security, also in 0.2.3.24-rc):
1121 - Fix a group of remotely triggerable assertion failures related to
1122 incorrect link protocol negotiation. Found, diagnosed, and fixed
1123 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1125 - Fix a denial of service attack by which any directory authority
1126 could crash all the others, or by which a single v2 directory
1127 authority could crash everybody downloading v2 directory
1128 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1130 o Major bugfixes (also in 0.2.3.24-rc):
1131 - When parsing exit policy summaries from microdescriptors, we had
1132 previously been ignoring the last character in each one, so that
1133 "accept 80,443,8080" would be treated by clients as indicating
1134 a node that allows access to ports 80, 443, and 808. That would
1135 lead to clients attempting connections that could never work,
1136 and ignoring exit nodes that would support their connections. Now
1137 clients parse these exit policy summaries correctly. Fixes bug 7192;
1138 bugfix on 0.2.3.1-alpha.
1140 o Minor bugfixes (also in 0.2.3.24-rc):
1141 - Clients now consider the ClientRejectInternalAddresses config option
1142 when using a microdescriptor consensus stanza to decide whether
1143 an exit relay would allow exiting to an internal address. Fixes
1144 bug 7190; bugfix on 0.2.3.1-alpha.
1147 - Only disable TLS session ticket support when running as a TLS
1148 server. Now clients will blend better with regular Firefox
1149 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1151 o Code simplification and refactoring:
1152 - Start using OpenBSD's implementation of queue.h (originally by
1154 - Move the entry node code from circuitbuild.c to its own file.
1155 - Move the circuit build timeout tracking code from circuitbuild.c
1159 Changes in version 0.2.3.24-rc - 2012-10-25
1160 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1161 could lead to remotely triggerable relay crashes, and fixes
1162 a major bug that was preventing clients from choosing suitable exit
1165 o Major bugfixes (security):
1166 - Fix a group of remotely triggerable assertion failures related to
1167 incorrect link protocol negotiation. Found, diagnosed, and fixed
1168 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1170 - Fix a denial of service attack by which any directory authority
1171 could crash all the others, or by which a single v2 directory
1172 authority could crash everybody downloading v2 directory
1173 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1176 - When parsing exit policy summaries from microdescriptors, we had
1177 previously been ignoring the last character in each one, so that
1178 "accept 80,443,8080" would be treated by clients as indicating
1179 a node that allows access to ports 80, 443, and 808. That would
1180 lead to clients attempting connections that could never work,
1181 and ignoring exit nodes that would support their connections. Now
1182 clients parse these exit policy summaries correctly. Fixes bug 7192;
1183 bugfix on 0.2.3.1-alpha.
1186 - Clients now consider the ClientRejectInternalAddresses config option
1187 when using a microdescriptor consensus stanza to decide whether
1188 an exit relay would allow exiting to an internal address. Fixes
1189 bug 7190; bugfix on 0.2.3.1-alpha.
1192 Changes in version 0.2.4.4-alpha - 2012-10-20
1193 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1194 vulnerability introduced by a change in OpenSSL, fixes a remotely
1195 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1196 that will make it easier to test new connection transport and cell
1197 scheduling algorithms.
1199 o New directory authorities (also in 0.2.3.23-rc):
1200 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1201 authority. Closes ticket 5749.
1203 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1204 - Disable TLS session tickets. OpenSSL's implementation was giving
1205 our TLS session keys the lifetime of our TLS context objects, when
1206 perfect forward secrecy would want us to discard anything that
1207 could decrypt a link connection as soon as the link connection
1208 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1209 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1210 - Discard extraneous renegotiation attempts once the V3 link
1211 protocol has been initiated. Failure to do so left us open to
1212 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1213 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1215 o Internal abstraction features:
1216 - Introduce new channel_t abstraction between circuits and
1217 or_connection_t to allow for implementing alternate OR-to-OR
1218 transports. A channel_t is an abstract object which can either be a
1219 cell-bearing channel, which is responsible for authenticating and
1220 handshaking with the remote OR and transmitting cells to and from
1221 it, or a listening channel, which spawns new cell-bearing channels
1222 at the request of remote ORs. Implements part of ticket 6465.
1223 - Also new is the channel_tls_t subclass of channel_t, adapting it
1224 to the existing or_connection_t code. The V2/V3 protocol handshaking
1225 code which formerly resided in command.c has been moved below the
1226 channel_t abstraction layer and may be found in channeltls.c now.
1227 Implements the rest of ticket 6465.
1228 - Introduce new circuitmux_t storing the queue of circuits for
1229 a channel; this encapsulates and abstracts the queue logic and
1230 circuit selection policy, and allows the latter to be overridden
1231 easily by switching out a policy object. The existing EWMA behavior
1232 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1234 o Required libraries:
1235 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1236 strongly recommended.
1239 - Warn users who run hidden services on a Tor client with
1240 UseEntryGuards disabled that their hidden services will be
1241 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1242 attack which motivated Tor to support entry guards in the first
1243 place). Resolves ticket 6889.
1244 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1245 dhill. Resolves ticket 6982.
1246 - Option OutboundBindAddress can be specified multiple times and
1247 accepts IPv6 addresses. Resolves ticket 6876.
1249 o Minor bugfixes (also in 0.2.3.23-rc):
1250 - Don't serve or accept v2 hidden service descriptors over a
1251 relay's DirPort. It's never correct to do so, and disabling it
1252 might make it more annoying to exploit any bugs that turn up in the
1253 descriptor-parsing code. Fixes bug 7149.
1254 - Fix two cases in src/or/transports.c where we were calling
1255 fmt_addr() twice in a parameter list. Bug found by David
1256 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1257 - Fix memory leaks whenever we logged any message about the "path
1258 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1259 - When relays refuse a "create" cell because their queue of pending
1260 create cells is too big (typically because their cpu can't keep up
1261 with the arrival rate), send back reason "resource limit" rather
1262 than reason "internal", so network measurement scripts can get a
1263 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1266 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1267 - Free some more still-in-use memory at exit, to make hunting for
1268 memory leaks easier. Resolves bug 7029.
1269 - When a Tor client gets a "truncated" relay cell, the first byte of
1270 its payload specifies why the circuit was truncated. We were
1271 ignoring this 'reason' byte when tearing down the circuit, resulting
1272 in the controller not being told why the circuit closed. Now we
1273 pass the reason from the truncated cell to the controller. Bugfix
1274 on 0.1.2.3-alpha; fixes bug 7039.
1275 - Downgrade "Failed to hand off onionskin" messages to "debug"
1276 severity, since they're typically redundant with the "Your computer
1277 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1278 - Make clients running with IPv6 bridges connect over IPv6 again,
1279 even without setting new config options ClientUseIPv6 and
1280 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1281 - Use square brackets around IPv6 addresses in numerous places
1282 that needed them, including log messages, HTTPS CONNECT proxy
1283 requests, TransportProxy statefile entries, and pluggable transport
1284 extra-info lines. Fixes bug 7011; patch by David Fifield.
1286 o Code refactoring and cleanup:
1287 - Source files taken from other packages now reside in src/ext;
1288 previously they were scattered around the rest of Tor.
1289 - Avoid use of reserved identifiers in our C code. The C standard
1290 doesn't like us declaring anything that starts with an
1291 underscore, so let's knock it off before we get in trouble. Fix
1292 for bug 1031; bugfix on the first Tor commit.
1295 Changes in version 0.2.3.23-rc - 2012-10-20
1296 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1297 vulnerability introduced by a change in OpenSSL, and fixes a variety
1298 of smaller bugs in preparation for the release.
1300 o New directory authorities:
1301 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1302 authority. Closes ticket 5749.
1304 o Major bugfixes (security/privacy):
1305 - Disable TLS session tickets. OpenSSL's implementation was giving
1306 our TLS session keys the lifetime of our TLS context objects, when
1307 perfect forward secrecy would want us to discard anything that
1308 could decrypt a link connection as soon as the link connection
1309 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1310 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1311 - Discard extraneous renegotiation attempts once the V3 link
1312 protocol has been initiated. Failure to do so left us open to
1313 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1314 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1317 - Fix a possible crash bug when checking for deactivated circuits
1318 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1319 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1321 o Minor bugfixes (on 0.2.3.x):
1322 - Fix two cases in src/or/transports.c where we were calling
1323 fmt_addr() twice in a parameter list. Bug found by David
1324 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1325 - Convert an assert in the pathbias code to a log message. The assert
1326 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1327 bugfix on 0.2.3.17-beta.
1328 - Fix memory leaks whenever we logged any message about the "path
1329 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1331 o Minor bugfixes (on 0.2.2.x and earlier):
1332 - Don't serve or accept v2 hidden service descriptors over a relay's
1333 DirPort. It's never correct to do so, and disabling it might
1334 make it more annoying to exploit any bugs that turn up in the
1335 descriptor-parsing code. Fixes bug 7149.
1336 - When relays refuse a "create" cell because their queue of pending
1337 create cells is too big (typically because their cpu can't keep up
1338 with the arrival rate), send back reason "resource limit" rather
1339 than reason "internal", so network measurement scripts can get a
1340 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1341 - Correct file sizes when reading binary files on Cygwin, to avoid
1342 a bug where Tor would fail to read its state file. Fixes bug 6844;
1343 bugfix on 0.1.2.7-alpha.
1344 - Avoid undefined behaviour when parsing the list of supported
1345 rendezvous/introduction protocols in a hidden service descriptor.
1346 Previously, Tor would have confused (as-yet-unused) protocol version
1347 numbers greater than 32 with lower ones on many platforms. Fixes
1348 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1350 o Documentation fixes:
1351 - Clarify that hidden services are TCP only. Fixes bug 6024.
1354 Changes in version 0.2.4.3-alpha - 2012-09-22
1355 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1356 assertion, resumes letting relays test reachability of their DirPort,
1357 and cleans up a bunch of smaller bugs.
1360 - Fix an assertion failure in tor_timegm() that could be triggered
1361 by a badly formatted directory object. Bug found by fuzzing with
1362 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1365 - Fix a possible crash bug when checking for deactivated circuits
1366 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1367 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1368 - Allow routers to detect that their own DirPorts are running. When
1369 we removed support for versions_supports_begindir, we also
1370 accidentally removed the mechanism we used to self-test our
1371 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1372 bugfix on 0.2.4.2-alpha.
1374 o Security features:
1375 - Switch to a completely time-invariant approach for picking nodes
1376 weighted by bandwidth. Our old approach would run through the
1377 part of the loop after it had made its choice slightly slower
1378 than it ran through the part of the loop before it had made its
1379 choice. Addresses ticket 6538.
1380 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1381 by tor2web clients allows hidden services to identity tor2web
1382 clients through their repeated selection of the same rendezvous
1383 and introduction point circuit endpoints (their guards). Resolves
1387 - Enable Tor to read configuration, state, and key information from
1388 a FIFO. Previously Tor would only read from files with a positive
1389 stat.st_size. Code from meejah; fixes bug 6044.
1392 - Correct file sizes when reading binary files on Cygwin, to avoid
1393 a bug where Tor would fail to read its state file. Fixes bug 6844;
1394 bugfix on 0.1.2.7-alpha.
1395 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1396 bugfix on 0.2.0.3-alpha.
1397 - When complaining about a client port on a public address, log
1398 which address we're complaining about. Fixes bug 4020; bugfix on
1399 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1400 - Convert an assert in the pathbias code to a log message. The assert
1401 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1402 bugfix on 0.2.3.17-beta.
1403 - Our new buildsystem was overzealous about rebuilding manpages: it
1404 would rebuild them all whenever any one of them changed. Now our
1405 dependency checking should be correct. Fixes bug 6843; bugfix on
1407 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1408 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1409 - Correct log printout about which address family is preferred
1410 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1411 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1413 o Minor bugfixes (code cleanliness):
1414 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1415 with large values. This situation was untriggered, but nevertheless
1416 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1417 - Reject consensus votes with more than 64 known-flags. We aren't even
1418 close to that limit yet, and our code doesn't handle it correctly.
1419 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1420 - Avoid undefined behaviour when parsing the list of supported
1421 rendezvous/introduction protocols in a hidden service descriptor.
1422 Previously, Tor would have confused (as-yet-unused) protocol version
1423 numbers greater than 32 with lower ones on many platforms. Fixes
1424 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1425 - Fix handling of rendezvous client authorization types over 8.
1426 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1427 - Fix building with older versions of GCC (2.95, for one) that don't
1428 like preprocessor directives inside macro arguments. Found by
1429 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1430 - Switch weighted node selection rule from using a list of doubles
1431 to using a list of int64_t. This change should make the process
1432 slightly easier to debug and maintain. Needed to finish ticket 6538.
1434 o Code simplification and refactoring:
1435 - Move the generic "config" code into a new file, and have "config.c"
1436 hold only torrc- and state-related code. Resolves ticket 6823.
1437 - Move the core of our "choose a weighted element at random" logic
1438 into its own function, and give it unit tests. Now the logic is
1439 testable, and a little less fragile too.
1440 - Removed the testing_since field of node_t, which hasn't been used
1441 for anything since 0.2.0.9-alpha.
1443 o Documentation fixes:
1444 - Clarify that hidden services are TCP only. Fixes bug 6024.
1445 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1449 Changes in version 0.2.3.22-rc - 2012-09-11
1450 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1454 - Fix an assertion failure in tor_timegm() that could be triggered
1455 by a badly formatted directory object. Bug found by fuzzing with
1456 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1459 - Avoid segfault when starting up having run with an extremely old
1460 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1464 Changes in version 0.2.2.39 - 2012-09-11
1465 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1469 - Fix an assertion failure in tor_timegm() that could be triggered
1470 by a badly formatted directory object. Bug found by fuzzing with
1471 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1472 - Do not crash when comparing an address with port value 0 to an
1473 address policy. This bug could have been used to cause a remote
1474 assertion failure by or against directory authorities, or to
1475 allow some applications to crash clients. Fixes bug 6690; bugfix
1479 Changes in version 0.2.4.2-alpha - 2012-09-10
1480 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1481 raises the default rate limiting even more, and makes the bootstrapping
1482 log messages less noisy.
1485 - Automatically forward the TCP ports of pluggable transport
1486 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1490 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1491 to 1GB/1GB. The previous defaults were intended to be "basically
1492 infinite", but it turns out they're now limiting our 100mbit+
1493 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1494 last time we raised it).
1497 - Detect when we're running with a version of OpenSSL other than the
1498 one we compiled with. This has occasionally given people hard-to-
1500 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1501 versions and capabilities when everything is going right. Resolves
1502 part of ticket 6736.
1503 - Directory authorities no long accept descriptors for any version of
1504 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1505 These versions are insecure, unsupported, or both. Implements
1509 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1510 to start with a triple-underscore so the controller won't touch it.
1511 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1512 - Avoid segfault when starting up having run with an extremely old
1513 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1515 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1516 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1517 - Don't follow the NULL pointer if microdescriptor generation fails.
1518 (This does not appear to be triggerable, but it's best to be safe.)
1519 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1520 - Fix mis-declared dependencies on src/common/crypto.c and
1521 src/or/tor_main.c that could break out-of-tree builds under some
1522 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1523 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1524 6778; bugfix on 0.2.4.1-alpha.
1525 - Fix a harmless (in this case) build warning for implicitly
1526 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1529 - Now that all versions before 0.2.2.x are disallowed, we no longer
1530 need to work around their missing features. Thus we can remove a
1531 bunch of compatibility code.
1534 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1535 TCP ports to forward. In the past it only accepted two ports:
1536 the ORPort and the DirPort.
1539 Changes in version 0.2.4.1-alpha - 2012-09-05
1540 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1541 bridgedb; lets relays use IPv6 addresses and directory authorities
1542 advertise them; and switches to a cleaner build interface.
1544 This is the first alpha release in a new series, so expect there to
1545 be bugs. Users who would rather test out a more stable branch should
1546 stay with 0.2.3.x for now.
1548 o Major features (bridges):
1549 - Bridges now report the pluggable transports they support to the
1550 bridge authority, so it can pass the supported transports on to
1551 bridgedb and/or eventually do reachability testing. Implements
1554 o Major features (IPv6):
1555 - Bridge authorities now accept IPv6 bridge addresses and include
1556 them in network status documents. Implements ticket 5534.
1557 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1558 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1559 to happen. Implements ticket 5535.
1560 - All kind of relays, not just bridges, can now advertise an IPv6
1561 OR port. Implements ticket 6362.
1562 - Directory authorities vote on IPv6 OR ports using the new consensus
1563 method 14. Implements ticket 6363.
1565 o Major features (build):
1566 - Switch to a nonrecursive Makefile structure. Now instead of each
1567 Makefile.am invoking other Makefile.am's, there is a master
1568 Makefile.am that includes the others. This change makes our build
1569 process slightly more maintainable, and improves parallelism for
1570 building with make -j. Original patch by Stewart Smith; various
1571 fixes by Jim Meyering.
1572 - Where available, we now use automake's "silent" make rules by
1573 default, so that warnings are easier to spot. You can get the old
1574 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1576 o Minor features (code security and spec conformance):
1577 - Clear keys and key-derived material left on the stack in
1578 rendservice.c and rendclient.c. Check return value of
1579 crypto_pk_write_private_key_to_string() in end_service_load_keys().
1580 These fixes should make us more forward-secure against cold-boot
1581 attacks and the like. Fixes bug 2385.
1582 - Reject EXTEND cells sent to nonexistent streams. According to the
1583 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1584 we were only checking for stream IDs that were currently in use.
1585 Found while hunting for more instances of bug 6271. Bugfix on
1586 0.0.2pre8, which introduced incremental circuit construction.
1588 o Minor features (streamlining);
1589 - No longer include the "opt" prefix when generating routerinfos
1590 or v2 directories: it has been needless since Tor 0.1.2. Closes
1592 - Remove some now-needless code that tried to aggressively flush
1593 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1594 cell queue logic has saved us from the failure mode that this code
1595 was supposed to prevent. Removing this code will limit the number
1596 of baroque control flow paths through Tor's network logic. Reported
1597 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1599 o Minor features (controller):
1600 - Add a "GETINFO signal/names" control port command. Implements
1602 - Provide default values for all options via "GETINFO config/defaults".
1603 Implements ticket 4971.
1605 o Minor features (IPv6):
1606 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1607 authorities should set if they have IPv6 connectivity and want to
1608 do reachability tests for IPv6 relays. Implements feature 5974.
1609 - A relay with an IPv6 OR port now sends that address in NETINFO
1610 cells (in addition to its other address). Implements ticket 6364.
1612 o Minor features (log messages):
1613 - Omit the first heartbeat log message, because it never has anything
1614 useful to say, and it clutters up the bootstrapping messages.
1615 Resolves ticket 6758.
1616 - Don't log about reloading the microdescriptor cache at startup. Our
1617 bootstrap warnings are supposed to tell the user when there's a
1618 problem, and our bootstrap notices say when there isn't. Resolves
1619 ticket 6759; bugfix on 0.2.2.6-alpha.
1620 - Don't log "I learned some more directory information" when we're
1621 reading cached directory information. Reserve it for when new
1622 directory information arrives in response to a fetch. Resolves
1624 - Prevent rounding error in path bias counts when scaling
1625 them down, and use the correct scale factor default. Also demote
1626 some path bias related log messages down a level and make others
1627 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1628 - We no longer warn so much when generating manpages from their
1631 o Code simplifications and refactoring:
1632 - Enhance our internal sscanf replacement so that we can eliminate
1633 the last remaining uses of the system sscanf. (Though those uses
1634 of sscanf were safe, sscanf itself is generally error prone, so
1635 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1637 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1638 - Move last_reachable and testing_since from routerinfo_t to node_t.
1639 Implements ticket 5529.
1640 - Add replaycache_t structure, functions and unit tests, then refactor
1641 rend_service_introduce() to be more clear to read, improve, debug,
1642 and test. Resolves bug 6177.
1643 - Finally remove support for malloc_good_size and malloc_usable_size.
1644 We had hoped that these functions would let us eke a little more
1645 memory out of our malloc implementation. Unfortunately, the only
1646 implementations that provided these functions are also ones that
1647 are already efficient about not overallocation: they never got us
1648 more than 7 or so bytes per allocation. Removing them saves us a
1649 little code complexity and a nontrivial amount of build complexity.
1652 - Tor maintainers now require Automake version 1.9 or later to build
1653 Tor from the Git repository. (Automake is not required when building
1654 from a source distribution.)
1657 Changes in version 0.2.3.21-rc - 2012-09-05
1658 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1659 series. It fixes a trio of potential security bugs, fixes a bug where
1660 we were leaving some of the fast relays out of the microdescriptor
1661 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1662 and cleans up other smaller issues.
1664 o Major bugfixes (security):
1665 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1666 could use this trick to make their circuits receive cells faster
1667 than our flow control would have allowed, or to gum up the network,
1668 or possibly to do targeted memory denial-of-service attacks on
1669 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1670 from July 2002, before the release of Tor 0.0.0. We had committed
1671 this patch previously, but we had to revert it because of bug 6271.
1672 Now that 6271 is fixed, this patch appears to work.
1673 - Reject any attempt to extend to an internal address. Without
1674 this fix, a router could be used to probe addresses on an internal
1675 network to see whether they were accepting connections. Fixes bug
1676 6710; bugfix on 0.0.8pre1.
1677 - Do not crash when comparing an address with port value 0 to an
1678 address policy. This bug could have been used to cause a remote
1679 assertion failure by or against directory authorities, or to
1680 allow some applications to crash clients. Fixes bug 6690; bugfix
1684 - Remove the upper bound on microdescriptor length. We were hitting
1685 the limit for routers with complex exit policies or family
1686 declarations, causing clients to not use them. Fixes the first
1687 piece of bug 6404; fix on 0.2.2.6-alpha.
1688 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1689 as a relay. Previously, some of our code would treat the presence
1690 of any ORPort line as meaning that we should act like a relay,
1691 even though our new listener code would correctly not open any
1692 ORPorts for ORPort 0. Similar bugs in other Port options are also
1693 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1696 - Avoid a pair of double-free and use-after-mark bugs that can
1697 occur with certain timings in canceled and re-received DNS
1698 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1699 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1700 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1701 - Allow one-hop directory fetching circuits the full "circuit build
1702 timeout" period, rather than just half of it, before failing them
1703 and marking the relay down. This fix should help reduce cases where
1704 clients declare relays (or worse, bridges) unreachable because
1705 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1706 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1708 - Authorities no longer include any router in their microdescriptor
1709 consensuses for which they couldn't generate or agree on a
1710 microdescriptor. Fixes the second piece of bug 6404; fix on
1712 - Detect and reject attempts to specify both "FooPort" and
1713 "FooPort 0" in the same configuration domain. (It's still okay
1714 to have a FooPort in your configuration file, and use "FooPort 0"
1715 on the command line to disable it.) Fixes the second half of bug
1716 6507; bugfix on 0.2.3.3-alpha.
1717 - Make wildcarded addresses (that is, ones beginning with "*.") work
1718 when provided via the controller's MapAddress command. Previously,
1719 they were accepted, but we never actually noticed that they were
1720 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1721 - Avoid crashing on a malformed state file where EntryGuardPathBias
1722 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1723 - Add a (probably redundant) memory clear between iterations of
1724 the router status voting loop, to prevent future coding errors
1725 where data might leak between iterations of the loop. Resolves
1728 o Minor bugfixes (log messages):
1729 - Downgrade "set buildtimeout to low value" messages to "info"
1730 severity; they were never an actual problem, there was never
1731 anything reasonable to do about them, and they tended to spam logs
1732 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1733 - Downgrade path-bias warning messages to "info". We'll try to get
1734 them working better in 0.2.4. Add internal circuit construction
1735 state to protect against the noisy warn message "Unexpectedly high
1736 circuit_successes". Also add some additional rate-limited notice
1737 messages to help determine the root cause of the warn. Fixes bug
1738 6475. Bugfix against 0.2.3.17-beta.
1739 - Move log message when unable to find a microdesc in a routerstatus
1740 entry to parse time. Previously we'd spam this warning every time
1741 we tried to figure out which microdescriptors to download. Fixes
1742 the third piece of bug 6404; fix on 0.2.3.18-rc.
1745 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1746 change when the authority is deciding whether to accept a newly
1747 uploaded descriptor. Implements ticket 6423.
1748 - Add missing documentation for consensus and microdesc files.
1749 Resolves ticket 6732.
1752 Changes in version 0.2.2.38 - 2012-08-12
1753 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1754 attack that could in theory leak path information.
1757 - Avoid an uninitialized memory read when reading a vote or consensus
1758 document that has an unrecognized flavor name. This read could
1759 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1760 - Try to leak less information about what relays a client is
1761 choosing to a side-channel attacker. Previously, a Tor client would
1762 stop iterating through the list of available relays as soon as it
1763 had chosen one, thus finishing a little earlier when it picked
1764 a router earlier in the list. If an attacker can recover this
1765 timing information (nontrivial but not proven to be impossible),
1766 they could learn some coarse-grained information about which relays
1767 a client was picking (middle nodes in particular are likelier to
1768 be affected than exits). The timing attack might be mitigated by
1769 other factors (see bug 6537 for some discussion), but it's best
1770 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1773 Changes in version 0.2.3.20-rc - 2012-08-05
1774 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1775 series. It fixes a pair of code security bugs and a potential anonymity
1776 issue, updates our RPM spec files, and cleans up other smaller issues.
1779 - Avoid read-from-freed-memory and double-free bugs that could occur
1780 when a DNS request fails while launching it. Fixes bug 6480;
1781 bugfix on 0.2.0.1-alpha.
1782 - Avoid an uninitialized memory read when reading a vote or consensus
1783 document that has an unrecognized flavor name. This read could
1784 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1785 - Try to leak less information about what relays a client is
1786 choosing to a side-channel attacker. Previously, a Tor client would
1787 stop iterating through the list of available relays as soon as it
1788 had chosen one, thus finishing a little earlier when it picked
1789 a router earlier in the list. If an attacker can recover this
1790 timing information (nontrivial but not proven to be impossible),
1791 they could learn some coarse-grained information about which relays
1792 a client was picking (middle nodes in particular are likelier to
1793 be affected than exits). The timing attack might be mitigated by
1794 other factors (see bug 6537 for some discussion), but it's best
1795 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1798 - Try to make the warning when giving an obsolete SOCKSListenAddress
1799 a little more useful.
1800 - Terminate active server managed proxies if Tor stops being a
1801 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
1802 - Provide a better error message about possible OSX Asciidoc failure
1803 reasons. Fixes bug 6436.
1804 - Warn when Tor is configured to use accounting in a way that can
1805 link a hidden service to some other hidden service or public
1806 address. Resolves ticket 6490.
1809 - Check return value of fputs() when writing authority certificate
1810 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
1811 - Ignore ServerTransportPlugin lines when Tor is not configured as
1812 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
1813 - When disabling guards for having too high a proportion of failed
1814 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
1818 - Update our default RPM spec files to work with mock and rpmbuild
1819 on RHEL/Fedora. They have an updated set of dependencies and
1820 conflicts, a fix for an ancient typo when creating the "_tor"
1821 user, and better instructions. Thanks to Ondrej Mikle for the
1822 patch series. Fixes bug 6043.
1825 - Make it possible to set the TestingTorNetwork configuration
1826 option using AlternateDirAuthority and AlternateBridgeAuthority
1827 as an alternative to setting DirServer. Addresses ticket 6377.
1830 - Clarify the documentation for the Alternate*Authority options.
1832 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
1834 o Code simplification and refactoring:
1835 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
1836 10 lines. Also, don't nest them. Doing so in the past has
1837 led to hard-to-debug code. The new style is to use the
1838 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
1841 Changes in version 0.2.3.19-rc - 2012-07-06
1842 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
1843 series. It fixes the compile on Windows, reverts to a GeoIP database
1844 that isn't as broken, and fixes a flow control bug that has been around
1845 since the beginning of Tor.
1848 - Fix a bug handling SENDME cells on nonexistent streams that could
1849 result in bizarre window values. Report and patch contributed
1850 pseudonymously. Fixes part of bug 6271. This bug was introduced
1851 before the first Tor release, in svn commit r152.
1852 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
1853 June 2012 database, Maxmind marked many Tor relays as country "A1",
1854 which will cause risky behavior for clients that set EntryNodes
1855 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
1856 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
1857 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
1860 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
1861 bugfix on 0.2.1.10-alpha.
1864 Changes in version 0.2.3.18-rc - 2012-06-28
1865 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
1866 series. It fixes a few smaller bugs, but generally appears stable.
1867 Please test it and let us know whether it is!
1870 - Allow wildcarded mapaddress targets to be specified on the
1871 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
1872 - Make our linker option detection code more robust against linkers
1873 such as on FreeBSD 8, where a bad combination of options completes
1874 successfully but makes an unrunnable binary. Fixes bug 6173;
1875 bugfix on 0.2.3.17-beta.
1877 o Minor bugfixes (on 0.2.2.x and earlier):
1878 - Avoid a false positive in the util/threads unit test by increasing
1879 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
1880 - Replace "Sending publish request" log messages with "Launching
1881 upload", so that they no longer confusingly imply that we're
1882 sending something to a directory we might not even be connected
1883 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
1884 - Make sure to set *socket_error in all error cases in
1885 connection_connect(), so it can't produce a warning about
1886 errno being zero from errno_to_orconn_end_reason(). Bugfix on
1887 0.2.1.1-alpha; resolves ticket 6028.
1888 - Downgrade "Got a certificate, but we already have it" log messages
1889 from warning to info, except when we're a dirauth. Fixes bug 5238;
1890 bugfix on 0.2.1.7-alpha.
1891 - When checking for requested signatures on the latest consensus
1892 before serving it to a client, make sure to check the right
1893 consensus flavor. Bugfix on 0.2.2.6-alpha.
1894 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
1895 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
1897 o Minor bugfixes (on 0.2.3.x):
1898 - Make format_helper_exit_status() avoid unnecessary space padding
1899 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
1901 - Downgrade a message about cleaning the microdescriptor cache to
1902 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
1903 - Log a BUG message at severity INFO if we have a networkstatus with
1904 a missing entry for some microdescriptor. Continues on a patch
1906 - Improve the log message when a managed proxy fails to launch. Fixes
1907 bug 5099; bugfix on 0.2.3.6-alpha.
1908 - Don't do DNS lookups when parsing corrupted managed proxy protocol
1909 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
1910 - When formatting wildcarded address mappings for the controller,
1911 be sure to include "*." as appropriate. Partially fixes bug 6244;
1912 bugfix on 0.2.3.9-alpha.
1913 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
1914 Bugfix on 0.2.3.13-alpha.
1915 - Stop logging messages about running with circuit timeout learning
1916 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
1917 - Disable a spurious warning about reading on a marked and flushing
1918 connection. We shouldn't be doing that, but apparently we
1919 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
1920 - Fix a bug that stopped AllowDotExit from working on addresses
1921 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
1924 o Code simplification, refactoring, unit tests:
1925 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
1926 Libevent's notion of cached time when possible.
1927 - Remove duplicate code for invoking getrlimit() from control.c.
1928 - Add a unit test for the environment_variable_names_equal function.
1931 - Document the --defaults-torrc option, and the new (in 0.2.3)
1932 semantics for overriding, extending, and clearing lists of
1933 options. Closes bug 4748.
1936 Changes in version 0.2.3.17-beta - 2012-06-15
1937 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
1938 gets our TLS handshake back on track for being able to blend in with
1939 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
1940 with Vidalia, and otherwise continues to get us closer to a release
1944 - Enable gcc and ld hardening by default. Resolves ticket 5210.
1945 - Update TLS cipher list to match Firefox 8 and later. Resolves
1947 - Implement the client side of proposal 198: remove support for
1948 clients falsely claiming to support standard ciphersuites that
1949 they can actually provide. As of modern OpenSSL versions, it's not
1950 necessary to fake any standard ciphersuite, and doing so prevents
1951 us from using better ciphersuites in the future, since servers
1952 can't know whether an advertised ciphersuite is really supported or
1953 not. Some hosts -- notably, ones with very old versions of OpenSSL
1954 or where OpenSSL has been built with ECC disabled -- will stand
1955 out because of this change; TBB users should not be affected.
1958 - Change the default value for DynamicDHGroups (introduced in
1959 0.2.3.9-alpha) to 0. This feature can make Tor relays less
1960 identifiable by their use of the mod_ssl DH group, but at
1961 the cost of some usability (#4721) and bridge tracing (#6087)
1962 regressions. Resolves ticket 5598.
1963 - Send a CRLF at the end of each STATUS_* control protocol event. This
1964 bug tickled a bug in Vidalia which would make it freeze. Fixes
1965 bug 6094; bugfix on 0.2.3.16-alpha.
1968 - Disable writing on marked-for-close connections when they are
1969 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
1970 bug 5263; bugfix on 0.0.2pre13, where we first added a special
1971 case for flushing marked connections.
1972 - Detect SSL handshake even when the initial attempt to write the
1973 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
1974 - Change the AllowDotExit rules so they should actually work.
1975 We now enforce AllowDotExit only immediately after receiving an
1976 address via SOCKS or DNSPort: other sources are free to provide
1977 .exit addresses after the resolution occurs. Fixes bug 3940;
1978 bugfix on 0.2.2.1-alpha.
1979 - Fix a (harmless) integer overflow in cell statistics reported by
1980 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
1981 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
1982 right places and never depends on the consensus parameters or
1983 computes adaptive timeouts when it is disabled. Fixes bug 5049;
1984 bugfix on 0.2.2.14-alpha.
1985 - When building Tor on Windows with -DUNICODE (not default), ensure
1986 that error messages, filenames, and DNS server names are always
1987 NUL-terminated when we convert them to a single-byte encoding.
1988 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
1989 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
1990 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
1991 - Fix an edge case where TestingTorNetwork is set but the authorities
1992 and relays all have an uptime of zero, where the private Tor network
1993 could briefly lack support for hidden services. Fixes bug 3886;
1994 bugfix on 0.2.2.18-alpha.
1995 - Correct the manpage's descriptions for the default values of
1996 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
1998 - Fix the documentation for the --hush and --quiet command line
1999 options, which changed their behavior back in 0.2.3.3-alpha.
2000 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2004 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2005 more information to it, so that we can track it down in case it
2006 returns again. Mitigates bug 5235.
2007 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2008 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2009 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2010 - Warn the user when HTTPProxy, but no other proxy type, is
2011 configured. This can cause surprising behavior: it doesn't send
2012 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2013 directory traffic only. Resolves ticket 4663.
2014 - Issue a notice if a guard completes less than 40% of your circuits.
2015 Threshold is configurable by torrc option PathBiasNoticeRate and
2016 consensus parameter pb_noticepct. There is additional, off-by-
2017 default code to disable guards which fail too many circuits.
2018 Addresses ticket 5458.
2019 - Update to the June 6 2012 Maxmind GeoLite Country database.
2021 o Code simplifications and refactoring:
2022 - Remove validate_pluggable_transports_config(): its warning
2023 message is now handled by connection_or_connect().
2026 Changes in version 0.2.2.37 - 2012-06-06
2027 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2028 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2032 - Work around a bug in OpenSSL that broke renegotiation with TLS
2033 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2034 the v2 Tor connection protocol when both sides were using OpenSSL
2035 1.0.1 would fail. Resolves ticket 6033.
2036 - When waiting for a client to renegotiate, don't allow it to add
2037 any bytes to the input buffer. This fixes a potential DoS issue.
2038 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2039 - Fix an edge case where if we fetch or publish a hidden service
2040 descriptor, we might build a 4-hop circuit and then use that circuit
2041 for exiting afterwards -- even if the new last hop doesn't obey our
2042 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2045 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2046 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2049 - Tell GCC and Clang to check for any errors in format strings passed
2050 to the tor_v*(print|scan)f functions.
2053 Changes in version 0.2.3.16-alpha - 2012-06-05
2054 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2055 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2056 currently). It also fixes a variety of smaller bugs and other cleanups
2057 that get us closer to a release candidate.
2059 o Major bugfixes (general):
2060 - Work around a bug in OpenSSL that broke renegotiation with TLS
2061 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2062 the v2 Tor connection protocol when both sides were using OpenSSL
2063 1.0.1 would fail. Resolves ticket 6033.
2064 - When waiting for a client to renegotiate, don't allow it to add
2065 any bytes to the input buffer. This fixes a potential DoS issue.
2066 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2067 - Pass correct OR address to managed proxies (like obfsproxy),
2068 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2070 - The advertised platform of a router now includes only its operating
2071 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2072 service pack level (for Windows) or its CPU architecture (for Unix).
2073 We also no longer include the "git-XYZ" tag in the version. Resolves
2076 o Major bugfixes (clients):
2077 - If we are unable to find any exit that supports our predicted ports,
2078 stop calling them predicted, so that we don't loop and build
2079 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2080 which introduced predicted ports.
2081 - Fix an edge case where if we fetch or publish a hidden service
2082 descriptor, we might build a 4-hop circuit and then use that circuit
2083 for exiting afterwards -- even if the new last hop doesn't obey our
2084 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2085 - Check at each new consensus whether our entry guards were picked
2086 long enough ago that we should rotate them. Previously, we only
2087 did this check at startup, which could lead to us holding a guard
2088 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2089 - When fetching a bridge descriptor from a bridge authority,
2090 always do so anonymously, whether we have been able to open
2091 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2092 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2093 but we'll need to wait for bug 6010 before it's actually usable.
2095 o Major bugfixes (directory authorities):
2096 - When computing weight parameters, behave more robustly in the
2097 presence of a bad bwweightscale value. Previously, the authorities
2098 would crash if they agreed on a sufficiently broken weight_scale
2099 value: now, they use a reasonable default and carry on. Partial
2100 fix for 5786; bugfix on 0.2.2.17-alpha.
2101 - Check more thoroughly to prevent a rogue authority from
2102 double-voting on any consensus directory parameter. Previously,
2103 authorities would crash in this case if the total number of
2104 votes for any parameter exceeded the number of active voters,
2105 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2109 - Rate-limit log messages when asked to connect anonymously to
2110 a private address. When these hit, they tended to hit fast and
2111 often. Also, don't bother trying to connect to addresses that we
2112 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2113 reply makes us think we have been lied to, even when the address the
2114 client tried to connect to was "localhost." Resolves ticket 2822.
2115 - Allow packagers to insert an extra string in server descriptor
2116 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2117 Resolves the rest of ticket 2988.
2118 - Raise the threshold of server descriptors needed (75%) and exit
2119 server descriptors needed (50%) before we will declare ourselves
2120 bootstrapped. This will make clients start building circuits a
2121 little later, but makes the initially constructed circuits less
2122 skewed and less in conflict with further directory fetches. Fixes
2124 - Close any connection that sends unrecognized junk before the
2125 handshake. Solves an issue noted in bug 4369.
2126 - Improve log messages about managed transports. Resolves ticket 5070.
2127 - Tag a bridge's descriptor as "never to be sent unencrypted".
2128 This shouldn't matter, since bridges don't open non-anonymous
2129 connections to the bridge authority and don't allow unencrypted
2130 directory connections from clients, but we might as well make
2131 sure. Closes bug 5139.
2132 - Expose our view of whether we have gone dormant to the controller,
2133 via a new "GETINFO dormant" value. Torbutton and other controllers
2134 can use this to avoid doing periodic requests through Tor while
2135 it's dormant (bug 4718). Fixes bug 5954.
2136 - Tell GCC and Clang to check for any errors in format strings passed
2137 to the tor_v*(print|scan)f functions.
2138 - Update to the May 1 2012 Maxmind GeoLite Country database.
2140 o Minor bugfixes (already included in 0.2.2.36):
2141 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2142 Fixes bug 5346; bugfix on 0.0.8pre3.
2143 - Correct parsing of certain date types in parse_http_time().
2144 Without this patch, If-Modified-Since would behave
2145 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2146 Esteban Manchado Velázques.
2147 - Make our number-parsing functions always treat too-large values
2148 as an error, even when those values exceed the width of the
2149 underlying type. Previously, if the caller provided these
2150 functions with minima or maxima set to the extreme values of the
2151 underlying integer type, these functions would return those
2152 values on overflow rather than treating overflow as an error.
2153 Fixes part of bug 5786; bugfix on 0.0.9.
2154 - If we hit the error case where routerlist_insert() replaces an
2155 existing (old) server descriptor, make sure to remove that
2156 server descriptor from the old_routers list. Fix related to bug
2157 1776. Bugfix on 0.2.2.18-alpha.
2158 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2159 circuits. Fixes issue 5259.
2161 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2162 - Prevent a null-pointer dereference when receiving a data cell
2163 for a nonexistent stream when the circuit in question has an
2164 empty deliver window. We don't believe this is triggerable,
2165 since we don't currently allow deliver windows to become empty,
2166 but the logic is tricky enough that it's better to make the code
2167 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2168 - Fix a memory leak when trying to launch a DNS request when the
2169 network is disabled or the nameservers are unconfigurable. Fixes
2170 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2171 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2172 - Don't hold a Windows file handle open for every file mapping;
2173 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2175 - Avoid O(n^2) performance characteristics when parsing a large
2176 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2177 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2178 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2180 - Make our replacement implementation of strtok_r() compatible with
2181 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2182 bugfix on 0.2.2.1-alpha.
2183 - Fix a NULL-pointer dereference on a badly formed
2184 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2185 bugfix on 0.2.2.9-alpha.
2186 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2187 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2188 - Defensively refactor rend_mid_rendezvous() so that protocol
2189 violations and length checks happen in the beginning. Fixes
2191 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2192 that IPv6 stuff will compile on MSVC, and compilation issues
2193 will be easier to track down. Fixes bug 5861.
2195 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2196 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2197 resource exhaustion, so that clients can adjust their load to
2198 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2199 started using END_STREAM_REASON_RESOURCELIMIT.
2200 - Don't check for whether the address we're using for outbound
2201 connections has changed until after the outbound connection has
2202 completed. On Windows, getsockname() doesn't succeed until the
2203 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2204 - If the configuration tries to set MyFamily on a bridge, refuse to
2205 do so, and warn about the security implications. Fixes bug 4657;
2206 bugfix on 0.2.0.3-alpha.
2207 - If the client fails to set a reasonable set of ciphersuites
2208 during its v2 handshake renegotiation, allow the renegotiation to
2209 continue nevertheless (i.e. send all the required certificates).
2210 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2211 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2212 option is set to 0 (which Vidalia version 0.2.16 now does when
2213 a SAVECONF attempt fails), perform other actions that SIGHUP
2214 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2216 - If we fail to write a microdescriptor to the disk cache, do not
2217 continue replacing the old microdescriptor file. Fixes bug 2954;
2218 bugfix on 0.2.2.6-alpha.
2219 - Exit nodes don't need to fetch certificates for authorities that
2220 they don't recognize; only directory authorities, bridges,
2221 and caches need to do that. Fixes part of bug 2297; bugfix on
2223 - Correctly handle checking the permissions on the parent
2224 directory of a control socket in the root directory. Bug found
2225 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2227 - When told to add a bridge with the same digest as a preexisting
2228 bridge but a different addr:port, change the addr:port as
2229 requested. Previously we would not notice the change. Fixes half
2230 of bug 5603; fix on 0.2.2.26-beta.
2231 - End AUTHCHALLENGE error messages (in the control protocol) with
2232 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2234 o Minor bugfixes (on 0.2.3.x):
2235 - Turn an assertion (that the number of handshakes received as a
2236 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2238 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2239 we had reversed them when the answer was cached.) Fixes bug
2240 5723; bugfix on 0.2.3.1-alpha.
2241 - Work correctly on Linux systems with accept4 support advertised in
2242 their headers, but without accept4 support in the kernel. Fix
2243 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2244 - When told to add a bridge with the same addr:port as a preexisting
2245 bridge but a different transport, change the transport as
2246 requested. Previously we would not notice the change. Fixes half
2247 of bug 5603; fix on 0.2.3.2-alpha.
2248 - Avoid a "double-reply" warning when replying to a SOCKS request
2249 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2250 bugfix on 0.2.3.4-alpha.
2251 - Fix a bug where a bridge authority crashes if it has seen no
2252 directory requests when it's time to write statistics to disk.
2253 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2255 - Don't try to open non-control listeners when DisableNetwork is set.
2256 Previously, we'd open all listeners, then immediately close them.
2257 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2258 - Don't abort the managed proxy protocol if the managed proxy
2259 sends us an unrecognized line; ignore it instead. Fixes bug
2260 5910; bugfix on 0.2.3.9-alpha.
2261 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2262 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2263 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2264 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2265 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2266 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2267 - Resolve numerous small warnings and build issues with MSVC. Resolves
2270 o Documentation fixes:
2271 - Improve the manual's documentation for the NT Service command-line
2272 options. Addresses ticket 3964.
2273 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2274 - Document the changes to the ORPort and DirPort options, and the
2275 fact that {OR/Dir}ListenAddress is now unnecessary (and
2276 therefore deprecated). Resolves ticket 5597.
2279 - Remove the torrc.bridge file: we don't use it for anything, and
2280 it had become badly desynchronized from torrc.sample. Resolves
2284 Changes in version 0.2.2.36 - 2012-05-24
2285 Tor 0.2.2.36 updates the addresses for two of the eight directory
2286 authorities, fixes some potential anonymity and security issues,
2287 and fixes several crash bugs.
2289 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2290 known flaws, and nobody should be using them. You should upgrade. If
2291 you're using a Linux or BSD and its packages are obsolete, stop using
2292 those packages and upgrade anyway.
2294 o Directory authority changes:
2295 - Change IP address for maatuska (v3 directory authority).
2296 - Change IP address for ides (v3 directory authority), and rename
2300 - When building or running with any version of OpenSSL earlier
2301 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2302 versions have a bug (CVE-2011-4576) in which their block cipher
2303 padding includes uninitialized data, potentially leaking sensitive
2304 information to any peer with whom they make a SSLv3 connection. Tor
2305 does not use SSL v3 by default, but a hostile client or server
2306 could force an SSLv3 connection in order to gain information that
2307 they shouldn't have been able to get. The best solution here is to
2308 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2309 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2310 to make sure that the bug can't happen.
2311 - Never use a bridge or a controller-supplied node as an exit, even
2312 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2313 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2314 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2315 - Only build circuits if we have a sufficient threshold of the total
2316 descriptors that are marked in the consensus with the "Exit"
2317 flag. This mitigates an attack proposed by wanoskarnet, in which
2318 all of a client's bridges collude to restrict the exit nodes that
2319 the client knows about. Fixes bug 5343.
2320 - Provide controllers with a safer way to implement the cookie
2321 authentication mechanism. With the old method, if another locally
2322 running program could convince a controller that it was the Tor
2323 process, then that program could trick the controller into telling
2324 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2325 authentication method uses a challenge-response approach to prevent
2326 this attack. Fixes bug 5185; implements proposal 193.
2329 - Avoid logging uninitialized data when unable to decode a hidden
2330 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2331 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2332 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2334 - Fix builds when the path to sed, openssl, or sha1sum contains
2335 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2337 - Correct our replacements for the timeradd() and timersub() functions
2338 on platforms that lack them (for example, Windows). The timersub()
2339 function is used when expiring circuits, while timeradd() is
2340 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2341 bugfix on 0.2.2.24-alpha.
2342 - Fix the SOCKET_OK test that we use to tell when socket
2343 creation fails so that it works on Win64. Fixes part of bug 4533;
2344 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2347 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2348 Fixes bug 5346; bugfix on 0.0.8pre3.
2349 - Make our number-parsing functions always treat too-large values
2350 as an error, even when those values exceed the width of the
2351 underlying type. Previously, if the caller provided these
2352 functions with minima or maxima set to the extreme values of the
2353 underlying integer type, these functions would return those
2354 values on overflow rather than treating overflow as an error.
2355 Fixes part of bug 5786; bugfix on 0.0.9.
2356 - Older Linux kernels erroneously respond to strange nmap behavior
2357 by having accept() return successfully with a zero-length
2358 socket. When this happens, just close the connection. Previously,
2359 we would try harder to learn the remote address: but there was
2360 no such remote address to learn, and our method for trying to
2361 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2362 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2363 - Correct parsing of certain date types in parse_http_time().
2364 Without this patch, If-Modified-Since would behave
2365 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2366 Esteban Manchado Velázques.
2367 - Change the BridgePassword feature (part of the "bridge community"
2368 design, which is not yet implemented) to use a time-independent
2369 comparison. The old behavior might have allowed an adversary
2370 to use timing to guess the BridgePassword value. Fixes bug 5543;
2371 bugfix on 0.2.0.14-alpha.
2372 - Detect and reject certain misformed escape sequences in
2373 configuration values. Previously, these values would cause us
2374 to crash if received in a torrc file or over an authenticated
2375 control port. Bug found by Esteban Manchado Velázquez, and
2376 independently by Robert Connolly from Matta Consulting who further
2377 noted that it allows a post-authentication heap overflow. Patch
2378 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2379 bugfix on 0.2.0.16-alpha.
2380 - Fix a compile warning when using the --enable-openbsd-malloc
2381 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2382 - During configure, detect when we're building with clang version
2383 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2384 CFLAGS. clang doesn't support them yet.
2385 - When sending an HTTP/1.1 proxy request, include a Host header.
2386 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2387 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2388 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2389 - If we hit the error case where routerlist_insert() replaces an
2390 existing (old) server descriptor, make sure to remove that
2391 server descriptor from the old_routers list. Fix related to bug
2392 1776. Bugfix on 0.2.2.18-alpha.
2394 o Minor bugfixes (documentation and log messages):
2395 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2396 Fixes bug 4856; bugfix on Tor 0.0.6.
2397 - Update "ClientOnly" man page entry to explain that there isn't
2398 really any point to messing with it. Resolves ticket 5005.
2399 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2400 directory authority option (introduced in Tor 0.2.2.34).
2401 - Downgrade the "We're missing a certificate" message from notice
2402 to info: people kept mistaking it for a real problem, whereas it
2403 is seldom the problem even when we are failing to bootstrap. Fixes
2404 bug 5067; bugfix on 0.2.0.10-alpha.
2405 - Correctly spell "connect" in a log message on failure to create a
2406 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2407 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2408 circuits. Fixes issue 5259.
2411 - Directory authorities now reject versions of Tor older than
2412 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2413 inclusive. These versions accounted for only a small fraction of
2414 the Tor network, and have numerous known security issues. Resolves
2416 - Update to the May 1 2012 Maxmind GeoLite Country database.
2419 - When sending or relaying a RELAY_EARLY cell, we used to convert
2420 it to a RELAY cell if the connection was using the v1 link
2421 protocol. This was a workaround for older versions of Tor, which
2422 didn't handle RELAY_EARLY cells properly. Now that all supported
2423 versions can handle RELAY_EARLY cells, and now that we're enforcing
2424 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2425 remove this workaround. Addresses bug 4786.
2428 Changes in version 0.2.3.15-alpha - 2012-04-30
2429 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2430 the development branch build on Windows again.
2432 o Minor bugfixes (on 0.2.2.x and earlier):
2433 - Make sure that there are no unhandled pending TLS errors before
2434 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2435 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2436 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2437 - Fix an assert that directory authorities could trigger on sighup
2438 during some configuration state transitions. We now don't treat
2439 it as a fatal error when the new descriptor we just generated in
2440 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2441 - After we pick a directory mirror, we would refuse to use it if
2442 it's in our ExcludeExitNodes list, resulting in mysterious failures
2443 to bootstrap for people who just wanted to avoid exiting from
2444 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2445 - When building with --enable-static-tor on OpenBSD, do not
2446 erroneously attempt to link -lrt. Fixes bug 5103.
2448 o Minor bugfixes (on 0.2.3.x):
2449 - When Tor is built with kernel headers from a recent (last few
2450 years) Linux kernel, do not fail to run on older (pre-2.6.28
2451 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2452 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2454 - Fix compilation with miniupnpc version 1.6; patch from
2455 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2456 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2457 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2458 - Fix compilation on platforms without unistd.h, or where environ
2459 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2462 - Directory authorities are now a little more lenient at accepting
2463 older router descriptors, or newer router descriptors that don't
2464 make big changes. This should help ameliorate past and future
2465 issues where routers think they have uploaded valid descriptors,
2466 but the authorities don't think so. Fix for ticket 2479.
2467 - Make the code that clients use to detect an address change be
2468 IPv6-aware, so that it won't fill clients' logs with error
2469 messages when trying to get the IPv4 address of an IPv6
2470 connection. Implements ticket 5537.
2473 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2474 authorities needed to use it for a while to keep the network working
2475 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2476 that was six months ago. As of now, it should no longer be needed
2480 Changes in version 0.2.3.14-alpha - 2012-04-23
2481 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2482 candidate. It also dramatically speeds up AES: fast relays should
2483 consider switching to the newer OpenSSL library.
2485 o Directory authority changes:
2486 - Change IP address for ides (v3 directory authority), and rename
2490 - Avoid logging uninitialized data when unable to decode a hidden
2491 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2492 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2493 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2495 - If authorities are unable to get a v2 consensus document from other
2496 directory authorities, they no longer fall back to fetching
2497 them from regular directory caches. Fixes bug 5635; bugfix on
2498 0.2.2.26-beta, where routers stopped downloading v2 consensus
2500 - When we start a Tor client with a normal consensus already cached,
2501 be willing to download a microdescriptor consensus. Fixes bug 4011;
2502 fix on 0.2.3.1-alpha.
2504 o Major features (performance):
2505 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2506 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2507 vectorized AES implementations as appropriate. These can be much,
2508 much faster than other AES implementations.
2510 o Minor bugfixes (0.2.2.x and earlier):
2511 - Don't launch more than 10 service-side introduction-point circuits
2512 for a hidden service in five minutes. Previously, we would consider
2513 launching more introduction-point circuits if at least one second
2514 had passed without any introduction-point circuits failing. Fixes
2515 bug 4607; bugfix on 0.0.7pre1.
2516 - Change the BridgePassword feature (part of the "bridge community"
2517 design, which is not yet implemented) to use a time-independent
2518 comparison. The old behavior might have allowed an adversary
2519 to use timing to guess the BridgePassword value. Fixes bug 5543;
2520 bugfix on 0.2.0.14-alpha.
2521 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2522 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2523 - When sending an HTTP/1.1 proxy request, include a Host header.
2524 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2525 - Don't log that we have "decided to publish new relay descriptor"
2526 unless we are actually publishing a descriptor. Fixes bug 3942;
2527 bugfix on 0.2.2.28-beta.
2529 o Minor bugfixes (0.2.3.x):
2530 - Fix a bug where a bridge authority crashes (on a failed assert)
2531 if it has seen no directory requests when it's time to write
2532 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2533 - Fix bug stomping on ORPort option NoListen and ignoring option
2534 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2535 - In the testsuite, provide a large enough buffer in the tor_sscanf
2536 unit test. Otherwise we'd overrun that buffer and crash during
2537 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2539 - Make sure we create the keys directory if it doesn't exist and we're
2540 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2541 5572; bugfix on 0.2.3.13-alpha.
2542 - Fix a small memory leak when trying to decode incorrect base16
2543 authenticator during SAFECOOKIE authentication. Found by
2544 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2547 - Add more information to a log statement that might help track down
2548 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2549 non-IP address" messages (or any Bug messages, for that matter!),
2550 please let us know about it.
2551 - Relays now understand an IPv6 address when they get one from a
2552 directory server. Resolves ticket 4875.
2553 - Resolve IPv6 addresses in bridge and entry statistics to country
2554 code "??" which means we at least count them. Resolves ticket 5053;
2555 improves on 0.2.3.9-alpha.
2556 - Update to the April 3 2012 Maxmind GeoLite Country database.
2557 - Begin a doc/state-contents.txt file to explain the contents of
2558 the Tor state file. Fixes bug 2987.
2560 o Default torrc changes:
2561 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2562 port on 9050 by default anyway, so this should not change anything
2564 - Stop mentioning the deprecated *ListenAddress options in
2565 torrc.sample. Fixes bug 5438.
2566 - Document unit of bandwidth related options in sample torrc.
2570 - The "torify" script no longer supports the "tsocks" socksifier
2571 tool, since tsocks doesn't support DNS and UDP right for Tor.
2572 Everyone should be using torsocks instead. Fixes bugs 3530 and
2573 5180. Based on a patch by "ugh".
2576 - Change the symmetric cipher interface so that creating and
2577 initializing a stream cipher are no longer separate functions.
2578 - Remove all internal support for unpadded RSA. We never used it, and
2579 it would be a bad idea to start.
2582 Changes in version 0.2.3.13-alpha - 2012-03-26
2583 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2584 in managed pluggable transports, as well as providing other cleanups
2585 that get us closer to a release candidate.
2587 o Directory authority changes:
2588 - Change IP address for maatuska (v3 directory authority).
2591 - Provide controllers with a safer way to implement the cookie
2592 authentication mechanism. With the old method, if another locally
2593 running program could convince a controller that it was the Tor
2594 process, then that program could trick the controller into telling
2595 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2596 authentication method uses a challenge-response approach to prevent
2597 this attack. Fixes bug 5185, implements proposal 193.
2598 - Never use a bridge or a controller-supplied node as an exit, even
2599 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2600 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2601 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2602 - Only build circuits if we have a sufficient threshold of the total
2603 descriptors that are marked in the consensus with the "Exit"
2604 flag. This mitigates an attack proposed by wanoskarnet, in which
2605 all of a client's bridges collude to restrict the exit nodes that
2606 the client knows about. Fixes bug 5343.
2608 o Major bugfixes (on Tor 0.2.3.x):
2609 - Avoid an assert when managed proxies like obfsproxy are configured,
2610 and we receive HUP signals or setconf attempts too rapidly. This
2611 situation happens most commonly when Vidalia tries to attach to
2612 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2613 bugfix on 0.2.3.6-alpha.
2614 - Fix a relay-side pluggable transports bug where managed proxies were
2615 unreachable from the Internet, because Tor asked them to bind on
2616 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2617 - Stop discarding command-line arguments when TestingTorNetwork
2618 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2619 0.2.3.9-alpha, where task 4552 added support for two layers of
2621 - Resume allowing the unit tests to run in gdb. This was accidentally
2622 made impossible when the DisableDebuggerAttachment option was
2623 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2624 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2625 0.2.3.11-alpha. Reported by Anthony G. Basile.
2627 o Minor bugfixes (on 0.2.2.x and earlier):
2628 - Ensure we don't cannibalize circuits that are longer than three hops
2629 already, so we don't end up making circuits with 5 or more
2630 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2631 0.1.0.1-rc which introduced cannibalization.
2632 - Detect and reject certain misformed escape sequences in
2633 configuration values. Previously, these values would cause us
2634 to crash if received in a torrc file or over an authenticated
2635 control port. Bug found by Esteban Manchado Velázquez, and
2636 independently by Robert Connolly from Matta Consulting who further
2637 noted that it allows a post-authentication heap overflow. Patch
2638 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2639 bugfix on 0.2.0.16-alpha.
2640 - Fix a compile warning when using the --enable-openbsd-malloc
2641 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2642 - Directory caches no longer refuse to clean out descriptors because
2643 of missing v2 networkstatus documents, unless they're configured
2644 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2645 0.2.2.26-beta. Patch by Daniel Bryg.
2646 - Update to the latest version of the tinytest unit testing framework.
2647 This includes a couple of bugfixes that can be relevant for
2648 running forked unit tests on Windows, and removes all reserved
2651 o Minor bugfixes (on 0.2.3.x):
2652 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2653 4296; bugfix on 0.2.3.1-alpha.
2654 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2655 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2656 on 0.2.3.6-alpha. Patch by "frosty".
2657 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2658 option, so that the IP stack doesn't decide to use it for IPv4
2659 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2660 - Ensure that variables set in Tor's environment cannot override
2661 environment variables that Tor passes to a managed
2662 pluggable-transport proxy. Previously, Tor would pass every
2663 variable in its environment to managed proxies along with the new
2664 ones, in such a way that on many operating systems, the inherited
2665 environment variables would override those which Tor tried to
2666 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2667 bugfix on 0.2.3.9-alpha for Windows.
2670 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2671 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2672 - Update to the March 6 2012 Maxmind GeoLite Country database.
2675 Changes in version 0.2.3.12-alpha - 2012-02-13
2676 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2677 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2678 when Tor is configured to use a pluggable transport like obfsproxy.
2681 - Fix builds when the path to sed, openssl, or sha1sum contains
2682 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2684 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2685 connections. This change should allow busy exit relays to stop
2686 running out of available sockets as quickly. Fixes bug 4950;
2687 bugfix on 0.2.2.26-beta.
2688 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2689 would ask the bridge for microdescriptors, which are only supported
2690 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2691 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2692 - Properly set up obfsproxy's environment when in managed mode. The
2693 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2694 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2695 5076 and 5082; bugfix on 0.2.3.6-alpha.
2698 - Use the dead_strip option when building Tor on OS X. This reduces
2699 binary size by almost 19% when linking openssl and libevent
2700 statically, which we do for Tor Browser Bundle.
2701 - Fix broken URLs in the sample torrc file, and tell readers about
2702 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2703 PublishServerDescriptor options. Addresses bug 4652.
2704 - Update to the February 7 2012 Maxmind GeoLite Country database.
2707 - Downgrade the "We're missing a certificate" message from notice
2708 to info: people kept mistaking it for a real problem, whereas it
2709 is seldom the problem even when we are failing to bootstrap. Fixes
2710 bug 5067; bugfix on 0.2.0.10-alpha.
2711 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2712 managed pluggable transport server proxy's environment.
2713 Previously, we would put it there, even though Tor doesn't
2714 implement an 'extended server port' yet, and even though Tor
2715 almost certainly isn't listening at that address. For now, we set
2716 it to an empty string to avoid crashing older obfsproxies. Bugfix
2718 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2719 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2720 0.2.3.1-alpha. Bug reported by Scott Bennett.
2721 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2722 bugfix on 0.2.3.11-alpha.
2723 - Update "ClientOnly" man page entry to explain that there isn't
2724 really any point to messing with it. Resolves ticket 5005.
2725 - Use the correct CVE number for CVE-2011-4576 in our comments and
2726 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2729 o Code simplifications and refactoring:
2730 - Use the _WIN32 macro throughout our code to detect Windows.
2731 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2735 Changes in version 0.2.3.11-alpha - 2012-01-22
2736 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2737 the last step of the plan to limit maximum circuit length, includes
2738 a wide variety of hidden service performance and correctness fixes,
2739 works around an OpenSSL security flaw if your distro is too stubborn
2740 to upgrade, and fixes a bunch of smaller issues.
2743 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2744 part of "Proposal 110: Avoiding infinite length circuits" by
2745 refusing all circuit-extend requests that do not use a relay_early
2746 cell. This change helps Tor resist a class of denial-of-service
2747 attacks by limiting the maximum circuit length.
2748 - Adjust the number of introduction points that a hidden service
2749 will try to maintain based on how long its introduction points
2750 remain in use and how many introductions they handle. Fixes
2752 - Try to use system facilities for enumerating local interface
2753 addresses, before falling back to our old approach (which was
2754 binding a UDP socket, and calling getsockname() on it). That
2755 approach was scaring OS X users whose draconian firewall
2756 software warned about binding to UDP sockets, regardless of
2757 whether packets were sent. Now we try to use getifaddrs(),
2758 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2759 system supports. Resolves ticket 1827.
2761 o Major security workaround:
2762 - When building or running with any version of OpenSSL earlier
2763 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2764 versions have a bug (CVE-2011-4576) in which their block cipher
2765 padding includes uninitialized data, potentially leaking sensitive
2766 information to any peer with whom they make a SSLv3 connection. Tor
2767 does not use SSL v3 by default, but a hostile client or server
2768 could force an SSLv3 connection in order to gain information that
2769 they shouldn't have been able to get. The best solution here is to
2770 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2771 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2772 to make sure that the bug can't happen.
2775 - Fix the SOCKET_OK test that we use to tell when socket
2776 creation fails so that it works on Win64. Fixes part of bug 4533;
2777 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2778 - Correct our replacements for the timeradd() and timersub() functions
2779 on platforms that lack them (for example, Windows). The timersub()
2780 function is used when expiring circuits, while timeradd() is
2781 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2782 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2783 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2784 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2785 bug at runtime, not compile time, because some distributions hack
2786 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
2787 on 0.2.3.9-alpha. Found by Pascal.
2789 o Minor features (controller):
2790 - Use absolute path names when reporting the torrc filename in the
2791 control protocol, so a controller can more easily find the torrc
2792 file. Resolves bug 1101.
2793 - Extend the control protocol to report flags that control a circuit's
2794 path selection in CIRC events and in replies to 'GETINFO
2795 circuit-status'. Implements part of ticket 2411.
2796 - Extend the control protocol to report the hidden service address
2797 and current state of a hidden-service-related circuit in CIRC
2798 events and in replies to 'GETINFO circuit-status'. Implements part
2800 - When reporting the path to the cookie file to the controller,
2801 give an absolute path. Resolves ticket 4881.
2802 - Allow controllers to request an event notification whenever a
2803 circuit is cannibalized or its purpose is changed. Implements
2804 part of ticket 3457.
2805 - Include the creation time of a circuit in CIRC and CIRC2
2806 control-port events and the list produced by the 'GETINFO
2807 circuit-status' control-port command.
2809 o Minor features (directory authorities):
2810 - Directory authorities now reject versions of Tor older than
2811 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2812 inclusive. These versions accounted for only a small fraction of
2813 the Tor network, and have numerous known security issues. Resolves
2815 - Authority operators can now vote for all relays in a given
2816 set of countries to be BadDir/BadExit/Invalid/Rejected.
2817 - Provide two consensus parameters (FastFlagMinThreshold and
2818 FastFlagMaxThreshold) to control the range of allowable bandwidths
2819 for the Fast directory flag. These allow authorities to run
2820 experiments on appropriate requirements for being a "Fast" node.
2821 The AuthDirFastGuarantee config value still applies. Implements
2823 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2824 directory authority option (introduced in Tor 0.2.2.34).
2826 o Minor features (other):
2827 - Don't disable the DirPort when we cannot exceed our AccountingMax
2828 limit during this interval because the effective bandwidthrate is
2829 low enough. This is useful in a situation where AccountMax is only
2830 used as an additional safeguard or to provide statistics.
2831 - Prepend an informative header to generated dynamic_dh_params files.
2832 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
2833 EntryNodes will have no effect. Resolves issue 2571.
2834 - Log more useful messages when we fail to disable debugger
2836 - Log which authority we're missing votes from when we go to fetch
2837 them from the other auths.
2838 - Log (at debug level) whenever a circuit's purpose is changed.
2839 - Add missing documentation for the MaxClientCircuitsPending,
2840 UseMicrodescriptors, UserspaceIOCPBuffers, and
2841 _UseFilteringSSLBufferevents options, all introduced during
2843 - Update to the January 3 2012 Maxmind GeoLite Country database.
2845 o Minor bugfixes (hidden services):
2846 - Don't close hidden service client circuits which have almost
2847 finished connecting to their destination when they reach
2848 the normal circuit-build timeout. Previously, we would close
2849 introduction circuits which are waiting for an acknowledgement
2850 from the introduction point, and rendezvous circuits which have
2851 been specified in an INTRODUCE1 cell sent to a hidden service,
2852 after the normal CBT. Now, we mark them as 'timed out', and launch
2853 another rendezvous attempt in parallel. This behavior change can
2854 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
2855 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
2856 - Don't close hidden-service-side rendezvous circuits when they
2857 reach the normal circuit-build timeout. This behaviour change can
2858 be disabled using the new
2859 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
2860 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
2861 - Make sure we never mark the wrong rendezvous circuit as having
2862 had its introduction cell acknowleged by the introduction-point
2863 relay. Previously, when we received an INTRODUCE_ACK cell on a
2864 client-side hidden-service introduction circuit, we might have
2865 marked a rendezvous circuit other than the one we specified in
2866 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
2867 a warning message and interfered with the hidden service
2868 connection-establishment process. Fixes bug 4759; bugfix on
2869 0.2.3.3-alpha, when we added the stream-isolation feature which
2870 might cause Tor to open multiple rendezvous circuits for the same
2872 - Don't trigger an assertion failure when we mark a new client-side
2873 hidden-service introduction circuit for close during the process
2874 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
2877 o Minor bugfixes (log messages):
2878 - Correctly spell "connect" in a log message on failure to create a
2879 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
2881 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2882 Fixes bug 4856; bugfix on Tor 0.0.6.
2883 - Fix the log message describing how we work around discovering
2884 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
2885 4837; bugfix on 0.2.2.9-alpha.
2886 - When logging about a disallowed .exit name, do not also call it
2887 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
2889 o Minor bugfixes (build fixes):
2890 - During configure, detect when we're building with clang version
2891 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2892 CFLAGS. clang doesn't support them yet.
2893 - During configure, search for library containing cos function as
2894 libm lives in libcore on some platforms (BeOS/Haiku). Linking
2895 against libm was hard-coded before. Fixes the first part of bug
2896 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
2898 - Detect attempts to build Tor on (as yet hypothetical) versions
2899 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
2900 fix for bug 4533. Bugfix on 0.2.2.28-beta.
2901 - Preprocessor directives should not be put inside the arguments
2902 of a macro. This would break compilation with GCC releases prior
2903 to version 3.3. We would never recommend such an old GCC version,
2904 but it is apparently required for binary compatibility on some
2905 platforms (namely, certain builds of Haiku). Fixes the other part
2906 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
2909 o Minor bugfixes (other):
2910 - Older Linux kernels erroneously respond to strange nmap behavior
2911 by having accept() return successfully with a zero-length
2912 socket. When this happens, just close the connection. Previously,
2913 we would try harder to learn the remote address: but there was
2914 no such remote address to learn, and our method for trying to
2915 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2916 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2917 - Fix null-pointer access that could occur if TLS allocation failed.
2918 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
2919 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
2920 accidentally been reverted.
2921 - Fix our implementation of crypto_random_hostname() so it can't
2922 overflow on ridiculously large inputs. (No Tor version has ever
2923 provided this kind of bad inputs, but let's be correct in depth.)
2924 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
2925 - Find more places in the code that should have been testing for
2926 invalid sockets using the SOCKET_OK macro. Required for a fix
2927 for bug 4533. Bugfix on 0.2.2.28-beta.
2928 - Fix an assertion failure when, while running with bufferevents, a
2929 connection finishes connecting after it is marked for close, but
2930 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
2931 - test_util_spawn_background_ok() hardcoded the expected value
2932 for ENOENT to 2. This isn't portable as error numbers are
2933 platform specific, and particularly the hurd has ENOENT at
2934 0x40000002. Construct expected string at runtime, using the correct
2935 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
2936 - Reject attempts to disable DisableDebuggerAttachment while Tor is
2937 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
2938 - Use an appropriate-width type for sockets in tor-fw-helper on
2939 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
2942 - When sending or relaying a RELAY_EARLY cell, we used to convert
2943 it to a RELAY cell if the connection was using the v1 link
2944 protocol. This was a workaround for older versions of Tor, which
2945 didn't handle RELAY_EARLY cells properly. Now that all supported
2946 versions can handle RELAY_EARLY cells, and now that we're enforcing
2947 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2948 remove this workaround. Addresses bug 4786.
2950 o Code simplifications and refactoring:
2951 - Use OpenSSL's built-in SSL_state_string_long() instead of our
2952 own homebrewed ssl_state_to_string() replacement. Patch from
2953 Emile Snyder. Fixes bug 4653.
2954 - Use macros to indicate OpenSSL versions, so we don't need to worry
2955 about accidental hexadecimal bit shifts.
2956 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
2958 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
2959 - Use the smartlist_add_asprintf() alias more consistently.
2960 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
2961 invalid value, rather than just -1.
2962 - Rename a handful of old identifiers, mostly related to crypto
2963 structures and crypto functions. By convention, our "create an
2964 object" functions are called "type_new()", our "free an object"
2965 functions are called "type_free()", and our types indicate that
2966 they are types only with a final "_t". But a handful of older
2967 types and functions broke these rules, with function names like
2968 "type_create" or "subsystem_op_type", or with type names like
2972 Changes in version 0.2.3.10-alpha - 2011-12-16
2973 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
2974 Tor's buffers code. Absolutely everybody should upgrade.
2976 The bug relied on an incorrect calculation when making data continuous
2977 in one of our IO buffers, if the first chunk of the buffer was
2978 misaligned by just the wrong amount. The miscalculation would allow an
2979 attacker to overflow a piece of heap-allocated memory. To mount this
2980 attack, the attacker would need to either open a SOCKS connection to
2981 Tor's SocksPort (usually restricted to localhost), or target a Tor
2982 instance configured to make its connections through a SOCKS proxy
2983 (which Tor does not do by default).
2985 Good security practice requires that all heap-overflow bugs should be
2986 presumed to be exploitable until proven otherwise, so we are treating
2987 this as a potential code execution attack. Please upgrade immediately!
2988 This bug does not affect bufferevents-based builds of Tor. Special
2989 thanks to "Vektor" for reporting this issue to us!
2991 This release also contains a few minor bugfixes for issues discovered
2995 - Fix a heap overflow bug that could occur when trying to pull
2996 data into the first chunk of a buffer, when that chunk had
2997 already had some data drained from it. Fixes CVE-2011-2778;
2998 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3001 - If we can't attach streams to a rendezvous circuit when we
3002 finish connecting to a hidden service, clear the rendezvous
3003 circuit's stream-isolation state and try to attach streams
3004 again. Previously, we cleared rendezvous circuits' isolation
3005 state either too early (if they were freshly built) or not at all
3006 (if they had been built earlier and were cannibalized). Bugfix on
3007 0.2.3.3-alpha; fixes bug 4655.
3008 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3009 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3010 - Fix an assertion failure when a relay with accounting enabled
3011 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3014 - Update to the December 6 2011 Maxmind GeoLite Country database.
3017 Changes in version 0.2.2.35 - 2011-12-16
3018 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3019 buffers code. Absolutely everybody should upgrade.
3021 The bug relied on an incorrect calculation when making data continuous
3022 in one of our IO buffers, if the first chunk of the buffer was
3023 misaligned by just the wrong amount. The miscalculation would allow an
3024 attacker to overflow a piece of heap-allocated memory. To mount this
3025 attack, the attacker would need to either open a SOCKS connection to
3026 Tor's SocksPort (usually restricted to localhost), or target a Tor
3027 instance configured to make its connections through a SOCKS proxy
3028 (which Tor does not do by default).
3030 Good security practice requires that all heap-overflow bugs should be
3031 presumed to be exploitable until proven otherwise, so we are treating
3032 this as a potential code execution attack. Please upgrade immediately!
3033 This bug does not affect bufferevents-based builds of Tor. Special
3034 thanks to "Vektor" for reporting this issue to us!
3036 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3037 crash bugs for unusual configurations, and a long-term bug that
3038 would prevent Tor from starting on Windows machines with draconian
3041 With this release, we remind everyone that 0.2.0.x has reached its
3042 formal end-of-life. Those Tor versions have many known flaws, and
3043 nobody should be using them. You should upgrade -- ideally to the
3044 0.2.2.x series. If you're using a Linux or BSD and its packages are
3045 obsolete, stop using those packages and upgrade anyway.
3047 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3048 longer receive support after some time in early 2012.
3051 - Fix a heap overflow bug that could occur when trying to pull
3052 data into the first chunk of a buffer, when that chunk had
3053 already had some data drained from it. Fixes CVE-2011-2778;
3054 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3055 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3056 that it doesn't attempt to allocate a socketpair. This could cause
3057 some problems on Windows systems with overzealous firewalls. Fix for
3058 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3060 - If we mark an OR connection for close based on a cell we process,
3061 don't process any further cells on it. We already avoid further
3062 reads on marked-for-close connections, but now we also discard the
3063 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3064 which was the first version where we might mark a connection for
3065 close based on processing a cell on it.
3066 - Correctly sanity-check that we don't underflow on a memory
3067 allocation (and then assert) for hidden service introduction
3068 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3069 bugfix on 0.2.1.5-alpha.
3070 - Fix a memory leak when we check whether a hidden service
3071 descriptor has any usable introduction points left. Fixes bug
3072 4424. Bugfix on 0.2.2.25-alpha.
3073 - Don't crash when we're running as a relay and don't have a GeoIP
3074 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3075 we've had in the 0.2.3.x branch already.
3076 - When running as a client, do not print a misleading (and plain
3077 wrong) log message that we're collecting "directory request"
3078 statistics: clients don't collect statistics. Also don't create a
3079 useless (because empty) stats file in the stats/ directory. Fixes
3080 bug 4353; bugfix on 0.2.2.34.
3083 - Detect failure to initialize Libevent. This fix provides better
3084 detection for future instances of bug 4457.
3085 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3086 function. This was eating up hideously large amounts of time on some
3087 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3088 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3089 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3091 - Don't warn about unused log_mutex in log.c when building with
3092 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3093 0.1.0.6-rc which introduced --disable-threads.
3094 - When configuring, starting, or stopping an NT service, stop
3095 immediately after the service configuration attempt has succeeded
3096 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3097 - When sending a NETINFO cell, include the original address
3098 received for the other side, not its canonical address. Found
3099 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3100 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3101 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3102 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3103 occurred when a client tried to fetch a descriptor for a bridge
3104 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3105 - Backport fixes for a pair of compilation warnings on Windows.
3106 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3107 - If we had ever tried to call tor_addr_to_str on an address of
3108 unknown type, we would have done a strdup on an uninitialized
3109 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3110 Reported by "troll_un".
3111 - Correctly detect and handle transient lookup failures from
3112 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3113 Reported by "troll_un".
3114 - Fix null-pointer access that could occur if TLS allocation failed.
3115 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3116 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3117 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3120 - Add two new config options for directory authorities:
3121 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3122 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3123 that is always sufficient to satisfy the bandwidth requirement for
3124 the Guard flag. Now it will be easier for researchers to simulate
3125 Tor networks with different values. Resolves ticket 4484.
3126 - When Tor ignores a hidden service specified in its configuration,
3127 include the hidden service's directory in the warning message.
3128 Previously, we would only tell the user that some hidden service
3129 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3130 - Update to the December 6 2011 Maxmind GeoLite Country database.
3132 o Packaging changes:
3133 - Make it easier to automate expert package builds on Windows,
3134 by removing an absolute path from makensis.exe command.
3137 Changes in version 0.2.1.32 - 2011-12-16
3138 Tor 0.2.1.32 backports important security and privacy fixes for
3139 oldstable. This release is intended only for package maintainers and
3140 others who cannot use the 0.2.2 stable series. All others should be
3141 using Tor 0.2.2.x or newer.
3143 The Tor 0.2.1.x series will reach formal end-of-life some time in
3144 early 2012; we will stop releasing patches for it then.
3146 o Major bugfixes (also included in 0.2.2.x):
3147 - Correctly sanity-check that we don't underflow on a memory
3148 allocation (and then assert) for hidden service introduction
3149 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3150 bugfix on 0.2.1.5-alpha.
3151 - Fix a heap overflow bug that could occur when trying to pull
3152 data into the first chunk of a buffer, when that chunk had
3153 already had some data drained from it. Fixes CVE-2011-2778;
3154 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3157 - Update to the December 6 2011 Maxmind GeoLite Country database.
3160 Changes in version 0.2.3.9-alpha - 2011-12-08
3161 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3162 a "DisableNetwork" security feature that bundles can use to avoid
3163 touching the network until bridges are configured, moves forward on
3164 the pluggable transport design, fixes a flaw in the hidden service
3165 design that unnecessarily prevented clients with wrong clocks from
3166 reaching hidden services, and fixes a wide variety of other issues.
3169 - Clients can now connect to private bridges over IPv6. Bridges
3170 still need at least one IPv4 address in order to connect to
3171 other relays. Note that we don't yet handle the case where the
3172 user has two bridge lines for the same bridge (one IPv4, one
3173 IPv6). Implements parts of proposal 186.
3174 - New "DisableNetwork" config option to prevent Tor from launching any
3175 connections or accepting any connections except on a control port.
3176 Bundles and controllers can set this option before letting Tor talk
3177 to the rest of the network, for example to prevent any connections
3178 to a non-bridge address. Packages like Orbot can also use this
3179 option to instruct Tor to save power when the network is off.
3180 - Clients and bridges can now be configured to use a separate
3181 "transport" proxy. This approach makes the censorship arms race
3182 easier by allowing bridges to use protocol obfuscation plugins. It
3183 implements the "managed proxy" part of proposal 180 (ticket 3472).
3184 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3185 implementation. It makes AES_CTR about 7% faster than our old one
3186 (which was about 10% faster than the one OpenSSL used to provide).
3187 Resolves ticket 4526.
3188 - Add a "tor2web mode" for clients that want to connect to hidden
3189 services non-anonymously (and possibly more quickly). As a safety
3190 measure to try to keep users from turning this on without knowing
3191 what they are doing, tor2web mode must be explicitly enabled at
3192 compile time, and a copy of Tor compiled to run in tor2web mode
3193 cannot be used as a normal Tor client. Implements feature 2553.
3194 - Add experimental support for running on Windows with IOCP and no
3195 kernel-space socket buffers. This feature is controlled by a new
3196 "UserspaceIOCPBuffers" config option (off by default), which has
3197 no effect unless Tor has been built with support for bufferevents,
3198 is running on Windows, and has enabled IOCP. This may, in the long
3199 run, help solve or mitigate bug 98.
3200 - Use a more secure consensus parameter voting algorithm. Now at
3201 least three directory authorities or a majority of them must
3202 vote on a given parameter before it will be included in the
3203 consensus. Implements proposal 178.
3206 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3207 They used to check that the timestamp was within 30 minutes
3208 of their system clock, so they could cap the size of their
3209 replay-detection cache, but that approach unnecessarily refused
3210 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3211 the v3 intro-point protocol (the first one which sent a timestamp
3212 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3213 - Only use the EVP interface when AES acceleration is enabled,
3214 to avoid a 5-7% performance regression. Resolves issue 4525;
3215 bugfix on 0.2.3.8-alpha.
3217 o Privacy/anonymity features (bridge detection):
3218 - Make bridge SSL certificates a bit more stealthy by using random
3219 serial numbers, in the same fashion as OpenSSL when generating
3220 self-signed certificates. Implements ticket 4584.
3221 - Introduce a new config option "DynamicDHGroups", enabled by
3222 default, which provides each bridge with a unique prime DH modulus
3223 to be used during SSL handshakes. This option attempts to help
3224 against censors who might use the Apache DH modulus as a static
3225 identifier for bridges. Addresses ticket 4548.
3227 o Minor features (new/different config options):
3228 - New configuration option "DisableDebuggerAttachment" (on by default)
3229 to prevent basic debugging attachment attempts by other processes.
3230 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3231 - Allow MapAddress directives to specify matches against super-domains,
3232 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3233 Implements issue 933.
3234 - Slightly change behavior of "list" options (that is, config
3235 options that can appear more than once) when they appear both in
3236 torrc and on the command line. Previously, the command-line options
3237 would be appended to the ones from torrc. Now, the command-line
3238 options override the torrc options entirely. This new behavior
3239 allows the user to override list options (like exit policies and
3240 ports to listen on) from the command line, rather than simply
3241 appending to the list.
3242 - You can get the old (appending) command-line behavior for "list"
3243 options by prefixing the option name with a "+".
3244 - You can remove all the values for a "list" option from the command
3245 line without adding any new ones by prefixing the option name
3247 - Add experimental support for a "defaults" torrc file to be parsed
3248 before the regular torrc. Torrc options override the defaults file's
3249 options in the same way that the command line overrides the torrc.
3250 The SAVECONF controller command saves only those options which
3251 differ between the current configuration and the defaults file. HUP
3252 reloads both files. (Note: This is an experimental feature; its
3253 behavior will probably be refined in future 0.2.3.x-alpha versions
3254 to better meet packagers' needs.) Implements task 4552.
3257 - Try to make the introductory warning message that Tor prints on
3258 startup more useful for actually finding help and information.
3259 Resolves ticket 2474.
3260 - Running "make version" now displays the version of Tor that
3261 we're about to build. Idea from katmagic; resolves issue 4400.
3262 - Expire old or over-used hidden service introduction points.
3263 Required by fix for bug 3460.
3264 - Move the replay-detection cache for the RSA-encrypted parts of
3265 INTRODUCE2 cells to the introduction point data structures.
3266 Previously, we would use one replay-detection cache per hidden
3267 service. Required by fix for bug 3460.
3268 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3269 public key replay-detection cache from 60 minutes to 5 minutes. This
3270 replay-detection cache is now used only to detect multiple
3271 INTRODUCE2 cells specifying the same rendezvous point, so we can
3272 avoid launching multiple simultaneous attempts to connect to it.
3274 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3275 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3276 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3278 - Fix a minor formatting issue in one of tor-gencert's error messages.
3280 - Prevent a false positive from the check-spaces script, by disabling
3281 the "whitespace between function name and (" check for functions
3283 - Fix a log message suggesting that people contact a non-existent
3284 email address. Fixes bug 3448.
3285 - Fix null-pointer access that could occur if TLS allocation failed.
3286 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3287 - Report a real bootstrap problem to the controller on router
3288 identity mismatch. Previously we just said "foo", which probably
3289 made a lot of sense at the time. Fixes bug 4169; bugfix on
3291 - If we had ever tried to call tor_addr_to_str() on an address of
3292 unknown type, we would have done a strdup() on an uninitialized
3293 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3294 Reported by "troll_un".
3295 - Correctly detect and handle transient lookup failures from
3296 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3297 Reported by "troll_un".
3298 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3299 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3300 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3301 bug 4532; found by "troll_un".
3303 o Minor bugfixes (on Tor 0.2.3.x):
3304 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3306 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3307 circuit for use as a hidden service client's rendezvous point.
3308 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3309 with help from wanoskarnet.
3310 - Restore behavior of overriding SocksPort, ORPort, and similar
3311 options from the command line. Bugfix on 0.2.3.3-alpha.
3314 - Properly handle the case where the build-tree is not the same
3315 as the source tree when generating src/common/common_sha1.i,
3316 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3317 bugfix on 0.2.0.1-alpha.
3319 o Code simplifications, cleanups, and refactorings:
3320 - Remove the pure attribute from all functions that used it
3321 previously. In many cases we assigned it incorrectly, because the
3322 functions might assert or call impure functions, and we don't have
3323 evidence that keeping the pure attribute is worthwhile. Implements
3324 changes suggested in ticket 4421.
3325 - Remove some dead code spotted by coverity. Fixes cid 432.
3326 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3329 Changes in version 0.2.3.8-alpha - 2011-11-22
3330 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3331 socketpair-related bug that has been bothering Windows users. It adds
3332 support to serve microdescriptors to controllers, so Vidalia's network
3333 map can resume listing relays (once Vidalia implements its side),
3334 and adds better support for hardware AES acceleration. Finally, it
3335 starts the process of adjusting the bandwidth cutoff for getting the
3336 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3337 that tiny relays harm performance more than they help network capacity.
3340 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3341 that it doesn't attempt to allocate a socketpair. This could cause
3342 some problems on Windows systems with overzealous firewalls. Fix for
3343 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3345 - Correctly sanity-check that we don't underflow on a memory
3346 allocation (and then assert) for hidden service introduction
3347 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3348 bugfix on 0.2.1.5-alpha.
3349 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3350 flag. In the past few years the average relay speed has picked
3351 up, and while the "top 7/8 of the network get the Fast flag" and
3352 "all relays with 20KB or more of capacity get the Fast flag" rules
3353 used to have the same result, now the top 7/8 of the network has
3354 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3355 - Fix a rare assertion failure when checking whether a v0 hidden
3356 service descriptor has any usable introduction points left, and
3357 we don't have enough information to build a circuit to the first
3358 intro point named in the descriptor. The HS client code in
3359 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3360 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3361 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3362 - Make bridge authorities not crash when they are asked for their own
3363 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3364 - When running as a client, do not print a misleading (and plain
3365 wrong) log message that we're collecting "directory request"
3366 statistics: clients don't collect statistics. Also don't create a
3367 useless (because empty) stats file in the stats/ directory. Fixes
3368 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3371 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3372 for a relay by identity digest or nickname. Previously,
3373 microdescriptors were only available by their own digests, so a
3374 controller would have to ask for and parse the whole microdescriptor
3375 consensus in order to look up a single relay's microdesc. Fixes
3376 bug 3832; bugfix on 0.2.3.1-alpha.
3377 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3378 operations can use hardware acceleration (if present). Resolves
3381 o Minor bugfixes (on 0.2.2.x and earlier):
3382 - Detect failure to initialize Libevent. This fix provides better
3383 detection for future instances of bug 4457.
3384 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3385 function. This was eating up hideously large amounts of time on some
3386 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3387 - Don't warn about unused log_mutex in log.c when building with
3388 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3389 0.1.0.6-rc which introduced --disable-threads.
3390 - Allow manual 'authenticate' commands to the controller interface
3391 from netcat (nc) as well as telnet. We were rejecting them because
3392 they didn't come with the expected whitespace at the end of the
3393 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3394 - Fix some (not actually triggerable) buffer size checks in usage of
3395 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3397 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3398 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3399 - When configuring, starting, or stopping an NT service, stop
3400 immediately after the service configuration attempt has succeeded
3401 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3402 - When sending a NETINFO cell, include the original address
3403 received for the other side, not its canonical address. Found
3404 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3405 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3406 can pick them up when the tests aren't disabled. Bugfix on
3407 0.2.2.4-alpha which introduced tinytest.
3408 - Fix a memory leak when we check whether a hidden service
3409 descriptor has any usable introduction points left. Fixes bug
3410 4424. Bugfix on 0.2.2.25-alpha.
3411 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3412 occurred when a client tried to fetch a descriptor for a bridge
3413 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3415 o Minor bugfixes (on 0.2.3.x):
3416 - Make util unit tests build correctly with MSVC. Bugfix on
3417 0.2.3.3-alpha. Patch by Gisle Vanem.
3418 - Successfully detect AUTH_CHALLENGE cells with no recognized
3419 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3421 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3422 it should still send a NETINFO cell to allow the connection to
3423 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3425 - Log less loudly when we get an invalid authentication certificate
3426 from a source other than a directory authority: it's not unusual
3427 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3429 - Tolerate servers with more clock skew in their authentication
3430 certificates than previously. Fixes bug 4371; bugfix on
3432 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3433 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3436 - Add two new config options for directory authorities:
3437 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3438 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3439 that is always sufficient to satisfy the bandwidth requirement for
3440 the Guard flag. Now it will be easier for researchers to simulate
3441 Tor networks with different values. Resolves ticket 4484.
3442 - When Tor ignores a hidden service specified in its configuration,
3443 include the hidden service's directory in the warning message.
3444 Previously, we would only tell the user that some hidden service
3445 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3446 - When we fail to initialize Libevent, retry with IOCP disabled so we
3447 don't need to turn on multi-threading support in Libevent, which in
3448 turn requires a working socketpair(). This is a workaround for bug
3449 4457, which affects Libevent versions from 2.0.1-alpha through
3451 - Detect when we try to build on a platform that doesn't define
3452 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3453 - Update to the November 1 2011 Maxmind GeoLite Country database.
3455 o Packaging changes:
3456 - Make it easier to automate expert package builds on Windows,
3457 by removing an absolute path from makensis.exe command.
3459 o Code simplifications and refactoring:
3460 - Remove some redundant #include directives throughout the code.
3461 Patch from Andrea Gelmini.
3462 - Unconditionally use OpenSSL's AES implementation instead of our
3463 old built-in one. OpenSSL's AES has been better for a while, and
3464 relatively few servers should still be on any version of OpenSSL
3465 that doesn't have good optimized assembly AES.
3466 - Use the name "CERTS" consistently to refer to the new cell type;
3467 we were calling it CERT in some places and CERTS in others.
3470 - Numerous new unit tests for functions in util.c and address.c by
3472 - The long-disabled benchmark tests are now split into their own
3473 ./src/test/bench binary.
3474 - The benchmark tests can now use more accurate timers than
3475 gettimeofday() when such timers are available.
3478 Changes in version 0.2.3.7-alpha - 2011-10-30
3479 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3480 the new v3 handshake. It also resolves yet another bridge address
3484 - If we mark an OR connection for close based on a cell we process,
3485 don't process any further cells on it. We already avoid further
3486 reads on marked-for-close connections, but now we also discard the
3487 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3488 which was the first version where we might mark a connection for
3489 close based on processing a cell on it.
3490 - Fix a double-free bug that would occur when we received an invalid
3491 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3492 bugfix on 0.2.3.6-alpha.
3493 - Bridges no longer include their address in NETINFO cells on outgoing
3494 OR connections, to allow them to blend in better with clients.
3495 Removes another avenue for enumerating bridges. Reported by
3496 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3497 cells were introduced.
3500 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3501 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3504 Changes in version 0.2.3.6-alpha - 2011-10-26
3505 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3506 anonymity vulnerability where an attacker can deanonymize Tor
3507 users. Everybody should upgrade.
3509 This release also features support for a new v3 connection handshake
3510 protocol, and fixes to make hidden service connections more robust.
3513 - Implement a new handshake protocol (v3) for authenticating Tors to
3514 each other over TLS. It should be more resistant to fingerprinting
3515 than previous protocols, and should require less TLS hacking for
3516 future Tor implementations. Implements proposal 176.
3517 - Allow variable-length padding cells to disguise the length of
3518 Tor's TLS records. Implements part of proposal 184.
3520 o Privacy/anonymity fixes (clients):
3521 - Clients and bridges no longer send TLS certificate chains on
3522 outgoing OR connections. Previously, each client or bridge would
3523 use the same cert chain for all outgoing OR connections until
3524 its IP address changes, which allowed any relay that the client
3525 or bridge contacted to determine which entry guards it is using.
3526 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3527 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3528 no longer considers that connection as suitable for satisfying a
3529 circuit EXTEND request. Now relays can protect clients from the
3530 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3531 - Directory authorities no longer assign the Guard flag to relays
3532 that haven't upgraded to the above "refuse EXTEND requests
3533 to client connections" fix. Now directory authorities can
3534 protect clients from the CVE-2011-2768 issue even if neither
3535 the clients nor the relays have upgraded yet. There's a new
3536 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3537 to let us transition smoothly, else tomorrow there would be no
3540 o Major bugfixes (hidden services):
3541 - Improve hidden service robustness: when an attempt to connect to
3542 a hidden service ends, be willing to refetch its hidden service
3543 descriptors from each of the HSDir relays responsible for them
3544 immediately. Previously, we would not consider refetching the
3545 service's descriptors from each HSDir for 15 minutes after the last
3546 fetch, which was inconvenient if the hidden service was not running
3547 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3548 - When one of a hidden service's introduction points appears to be
3549 unreachable, stop trying it. Previously, we would keep trying
3550 to build circuits to the introduction point until we lost the
3551 descriptor, usually because the user gave up and restarted Tor.
3552 Partly fixes bug 3825.
3553 - Don't launch a useless circuit after failing to use one of a
3554 hidden service's introduction points. Previously, we would
3555 launch a new introduction circuit, but not set the hidden service
3556 which that circuit was intended to connect to, so it would never
3557 actually be used. A different piece of code would then create a
3558 new introduction circuit correctly. Bug reported by katmagic and
3559 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3561 o Major bugfixes (other):
3562 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3563 that they initiated. Relays could distinguish incoming bridge
3564 connections from client connections, creating another avenue for
3565 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3566 Found by "frosty_un".
3567 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3568 tor gets started. This prevents a wrong average bandwidth
3569 estimate, which would cause relays to always start a new accounting
3570 interval at the earliest possible moment. Fixes bug 2003; bugfix
3571 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3572 immensely in tracking this bug down.
3573 - Fix a crash bug when changing node restrictions while a DNS lookup
3574 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3577 o Minor bugfixes (on 0.2.2.x and earlier):
3578 - When a hidden service turns an extra service-side introduction
3579 circuit into a general-purpose circuit, free the rend_data and
3580 intro_key fields first, so we won't leak memory if the circuit
3581 is cannibalized for use as another service-side introduction
3582 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3583 - Rephrase the log message emitted if the TestSocks check is
3584 successful. Patch from Fabian Keil; fixes bug 4094.
3585 - Bridges now skip DNS self-tests, to act a little more stealthily.
3586 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3587 bridges. Patch by "warms0x".
3588 - Remove a confusing dollar sign from the example fingerprint in the
3589 man page, and also make the example fingerprint a valid one. Fixes
3590 bug 4309; bugfix on 0.2.1.3-alpha.
3591 - Fix internal bug-checking logic that was supposed to catch
3592 failures in digest generation so that it will fail more robustly
3593 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3594 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3595 - Report any failure in init_keys() calls launched because our
3596 IP address has changed. Spotted by Coverity Scan. Bugfix on
3597 0.1.1.4-alpha; fixes CID 484.
3599 o Minor bugfixes (on 0.2.3.x):
3600 - Fix a bug in configure.in that kept it from building a configure
3601 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3602 bugfix on 0.2.3.1-alpha.
3603 - Don't warn users that they are exposing a client port to the
3604 Internet if they have specified an RFC1918 address. Previously,
3605 we would warn if the user had specified any non-loopback
3606 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3607 - Fix memory leaks in the failing cases of the new SocksPort and
3608 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3609 fixes coverity CIDs 485, 486, and 487.
3612 - When a hidden service's introduction point times out, consider
3613 trying it again during the next attempt to connect to the
3614 HS. Previously, we would not try it again unless a newly fetched
3615 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3616 - The next version of Windows will be called Windows 8, and it has
3617 a major version of 6, minor version of 2. Correctly identify that
3618 version instead of calling it "Very recent version". Resolves
3619 ticket 4153; reported by funkstar.
3620 - The Bridge Authority now writes statistics on how many bridge
3621 descriptors it gave out in total, and how many unique descriptors
3622 it gave out. It also lists how often the most and least commonly
3623 fetched descriptors were given out, as well as the median and
3624 25th/75th percentile. Implements tickets 4200 and 4294.
3625 - Update to the October 4 2011 Maxmind GeoLite Country database.
3627 o Code simplifications and refactoring:
3628 - Remove some old code to remember statistics about which descriptors
3629 we've served as a directory mirror. The feature wasn't used and
3630 is outdated now that microdescriptors are around.
3631 - Rename Tor functions that turn strings into addresses, so that
3632 "parse" indicates that no hostname resolution occurs, and
3633 "lookup" indicates that hostname resolution may occur. This
3634 should help prevent mistakes in the future. Fixes bug 3512.
3637 Changes in version 0.2.2.34 - 2011-10-26
3638 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3639 can deanonymize Tor users. Everybody should upgrade.
3641 The attack relies on four components: 1) Clients reuse their TLS cert
3642 when talking to different relays, so relays can recognize a user by
3643 the identity key in her cert. 2) An attacker who knows the client's
3644 identity key can probe each guard relay to see if that identity key
3645 is connected to that guard relay right now. 3) A variety of active
3646 attacks in the literature (starting from "Low-Cost Traffic Analysis
3647 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3648 discover the guard relays that a Tor user visiting the website is using.
3649 4) Clients typically pick three guards at random, so the set of guards
3650 for a given user could well be a unique fingerprint for her. This
3651 release fixes components #1 and #2, which is enough to block the attack;
3652 the other two remain as open research problems. Special thanks to
3653 "frosty_un" for reporting the issue to us!
3655 Clients should upgrade so they are no longer recognizable by the TLS
3656 certs they present. Relays should upgrade so they no longer allow a
3657 remote attacker to probe them to test whether unpatched clients are
3658 currently connected to them.
3660 This release also fixes several vulnerabilities that allow an attacker
3661 to enumerate bridge relays. Some bridge enumeration attacks still
3662 remain; see for example proposal 188.
3664 o Privacy/anonymity fixes (clients):
3665 - Clients and bridges no longer send TLS certificate chains on
3666 outgoing OR connections. Previously, each client or bridge would
3667 use the same cert chain for all outgoing OR connections until
3668 its IP address changes, which allowed any relay that the client
3669 or bridge contacted to determine which entry guards it is using.
3670 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3671 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3672 no longer considers that connection as suitable for satisfying a
3673 circuit EXTEND request. Now relays can protect clients from the
3674 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3675 - Directory authorities no longer assign the Guard flag to relays
3676 that haven't upgraded to the above "refuse EXTEND requests
3677 to client connections" fix. Now directory authorities can
3678 protect clients from the CVE-2011-2768 issue even if neither
3679 the clients nor the relays have upgraded yet. There's a new
3680 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3681 to let us transition smoothly, else tomorrow there would be no
3684 o Privacy/anonymity fixes (bridge enumeration):
3685 - Bridge relays now do their directory fetches inside Tor TLS
3686 connections, like all the other clients do, rather than connecting
3687 directly to the DirPort like public relays do. Removes another
3688 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3689 - Bridges relays now build circuits for themselves in a more similar
3690 way to how clients build them. Removes another avenue for
3691 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3692 when bridges were introduced.
3693 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3694 that they initiated. Relays could distinguish incoming bridge
3695 connections from client connections, creating another avenue for
3696 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3697 Found by "frosty_un".
3700 - Fix a crash bug when changing node restrictions while a DNS lookup
3701 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3703 - Don't launch a useless circuit after failing to use one of a
3704 hidden service's introduction points. Previously, we would
3705 launch a new introduction circuit, but not set the hidden service
3706 which that circuit was intended to connect to, so it would never
3707 actually be used. A different piece of code would then create a
3708 new introduction circuit correctly. Bug reported by katmagic and
3709 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3712 - Change an integer overflow check in the OpenBSD_Malloc code so
3713 that GCC is less likely to eliminate it as impossible. Patch
3714 from Mansour Moufid. Fixes bug 4059.
3715 - When a hidden service turns an extra service-side introduction
3716 circuit into a general-purpose circuit, free the rend_data and
3717 intro_key fields first, so we won't leak memory if the circuit
3718 is cannibalized for use as another service-side introduction
3719 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3720 - Bridges now skip DNS self-tests, to act a little more stealthily.
3721 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3722 bridges. Patch by "warms0x".
3723 - Fix internal bug-checking logic that was supposed to catch
3724 failures in digest generation so that it will fail more robustly
3725 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3726 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3727 - Report any failure in init_keys() calls launched because our
3728 IP address has changed. Spotted by Coverity Scan. Bugfix on
3729 0.1.1.4-alpha; fixes CID 484.
3731 o Minor bugfixes (log messages and documentation):
3732 - Remove a confusing dollar sign from the example fingerprint in the
3733 man page, and also make the example fingerprint a valid one. Fixes
3734 bug 4309; bugfix on 0.2.1.3-alpha.
3735 - The next version of Windows will be called Windows 8, and it has
3736 a major version of 6, minor version of 2. Correctly identify that
3737 version instead of calling it "Very recent version". Resolves
3738 ticket 4153; reported by funkstar.
3739 - Downgrade log messages about circuit timeout calibration from
3740 "notice" to "info": they don't require or suggest any human
3741 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3742 bugfix on 0.2.2.14-alpha.
3745 - Turn on directory request statistics by default and include them in
3746 extra-info descriptors. Don't break if we have no GeoIP database.
3747 Backported from 0.2.3.1-alpha; implements ticket 3951.
3748 - Update to the October 4 2011 Maxmind GeoLite Country database.
3751 Changes in version 0.2.1.31 - 2011-10-26
3752 Tor 0.2.1.31 backports important security and privacy fixes for
3753 oldstable. This release is intended only for package maintainers and
3754 others who cannot use the 0.2.2 stable series. All others should be
3755 using Tor 0.2.2.x or newer.
3757 o Security fixes (also included in 0.2.2.x):
3758 - Replace all potentially sensitive memory comparison operations
3759 with versions whose runtime does not depend on the data being
3760 compared. This will help resist a class of attacks where an
3761 adversary can use variations in timing information to learn
3762 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3763 implementation by Robert Ransom based partially on code by DJB.)
3764 - Fix an assert in parsing router descriptors containing IPv6
3765 addresses. This one took down the directory authorities when
3766 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3768 o Privacy/anonymity fixes (also included in 0.2.2.x):
3769 - Clients and bridges no longer send TLS certificate chains on
3770 outgoing OR connections. Previously, each client or bridge would
3771 use the same cert chain for all outgoing OR connections until
3772 its IP address changes, which allowed any relay that the client
3773 or bridge contacted to determine which entry guards it is using.
3774 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3775 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3776 no longer considers that connection as suitable for satisfying a
3777 circuit EXTEND request. Now relays can protect clients from the
3778 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3779 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3780 that they initiated. Relays could distinguish incoming bridge
3781 connections from client connections, creating another avenue for
3782 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3783 Found by "frosty_un".
3784 - When receiving a hidden service descriptor, check that it is for
3785 the hidden service we wanted. Previously, Tor would store any
3786 hidden service descriptors that a directory gave it, whether it
3787 wanted them or not. This wouldn't have let an attacker impersonate
3788 a hidden service, but it did let directories pre-seed a client
3789 with descriptors that it didn't want. Bugfix on 0.0.6.
3790 - Avoid linkability based on cached hidden service descriptors: forget
3791 all hidden service descriptors cached as a client when processing a
3792 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3793 - Make the bridge directory authority refuse to answer directory
3794 requests for "all" descriptors. It used to include bridge
3795 descriptors in its answer, which was a major information leak.
3796 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3797 - Don't attach new streams to old rendezvous circuits after SIGNAL
3798 NEWNYM. Previously, we would keep using an existing rendezvous
3799 circuit if it remained open (i.e. if it were kept open by a
3800 long-lived stream, or if a new stream were attached to it before
3801 Tor could notice that it was old and no longer in use). Bugfix on
3802 0.1.1.15-rc; fixes bug 3375.
3804 o Minor bugfixes (also included in 0.2.2.x):
3805 - When we restart our relay, we might get a successful connection
3806 from the outside before we've started our reachability tests,
3807 triggering a warning: "ORPort found reachable, but I have no
3808 routerinfo yet. Failing to inform controller of success." This
3809 bug was harmless unless Tor is running under a controller
3810 like Vidalia, in which case the controller would never get a
3811 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3813 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3814 enabled. Fixes bug 1526.
3815 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3816 anything since 0.2.1.16-rc.
3817 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3818 None of the cases where we did this before were wrong, but by making
3819 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3820 - Fix a rare crash bug that could occur when a client was configured
3821 with a large number of bridges. Fixes bug 2629; bugfix on
3822 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3823 - Correct the warning displayed when a rendezvous descriptor exceeds
3824 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3826 - Fix an uncommon assertion failure when running with DNSPort under
3827 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3828 - When warning about missing zlib development packages during compile,
3829 give the correct package names. Bugfix on 0.2.0.1-alpha.
3830 - Require that introduction point keys and onion keys have public
3831 exponent 65537. Bugfix on 0.2.0.10-alpha.
3832 - Do not crash when our configuration file becomes unreadable, for
3833 example due to a permissions change, between when we start up
3834 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3836 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3838 - Always NUL-terminate the sun_path field of a sockaddr_un before
3839 passing it to the kernel. (Not a security issue: kernels are
3840 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3841 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3842 - Don't stack-allocate the list of supplementary GIDs when we're
3843 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3844 could take up to 256K, which is way too much stack. Found by
3845 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3847 o Minor bugfixes (only in 0.2.1.x):
3848 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
3849 rely on them. Bugfix on 0.2.1.30.
3850 - Use git revisions instead of svn revisions when generating our
3851 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3853 o Minor features (also included in 0.2.2.x):
3854 - Adjust the expiration time on our SSL session certificates to
3855 better match SSL certs seen in the wild. Resolves ticket 4014.
3856 - Allow nameservers with IPv6 address. Resolves bug 2574.
3857 - Update to the October 4 2011 Maxmind GeoLite Country database.
3860 Changes in version 0.2.3.5-alpha - 2011-09-28
3861 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
3862 bridge relays; fixes an assertion error that many users started hitting
3863 today; and adds the ability to refill token buckets more often than
3864 once per second, allowing significant performance improvements.
3867 - Bridge relays now do their directory fetches inside Tor TLS
3868 connections, like all the other clients do, rather than connecting
3869 directly to the DirPort like public relays do. Removes another
3870 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3871 - Bridges relays now build circuits for themselves in a more similar
3872 way to how clients build them. Removes another avenue for
3873 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3874 when bridges were introduced.
3877 - Fix an "Assertion md->held_by_node == 1 failed" error that could
3878 occur when the same microdescriptor was referenced by two node_t
3879 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
3881 o Major features (networking):
3882 - Add a new TokenBucketRefillInterval option to refill token buckets
3883 more frequently than once per second. This should improve network
3884 performance, alleviate queueing problems, and make traffic less
3885 bursty. Implements proposal 183; closes ticket 3630. Design by
3886 Florian Tschorsch and Björn Scheuermann; implementation by
3890 - Change an integer overflow check in the OpenBSD_Malloc code so
3891 that GCC is less likely to eliminate it as impossible. Patch
3892 from Mansour Moufid. Fixes bug 4059.
3894 o Minor bugfixes (usability):
3895 - Downgrade log messages about circuit timeout calibration from
3896 "notice" to "info": they don't require or suggest any human
3897 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3898 bugfix on 0.2.2.14-alpha.
3900 o Minor features (diagnostics):
3901 - When the system call to create a listener socket fails, log the
3902 error message explaining why. This may help diagnose bug 4027.
3905 Changes in version 0.2.3.4-alpha - 2011-09-13
3906 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
3907 tweak to Tor's TLS handshake that makes relays and bridges that run
3908 this new version reachable from Iran again. It also fixes a few new
3909 bugs in 0.2.3.x, and teaches relays to recognize when they're not
3910 listed in the network consensus and republish.
3912 o Major bugfixes (also part of 0.2.2.33):
3913 - Avoid an assertion failure when reloading a configuration with
3914 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
3915 3923; bugfix on 0.2.2.25-alpha.
3917 o Minor features (security, also part of 0.2.2.33):
3918 - Check for replays of the public-key encrypted portion of an
3919 INTRODUCE1 cell, in addition to the current check for replays of
3920 the g^x value. This prevents a possible class of active attacks
3921 by an attacker who controls both an introduction point and a
3922 rendezvous point, and who uses the malleability of AES-CTR to
3923 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
3924 that these attacks are infeasible (requiring the attacker to send
3925 on the order of zettabytes of altered cells in a short interval),
3926 but we'd rather block them off in case there are any classes of
3927 this attack that we missed. Reported by Willem Pinckaers.
3929 o Minor features (also part of 0.2.2.33):
3930 - Adjust the expiration time on our SSL session certificates to
3931 better match SSL certs seen in the wild. Resolves ticket 4014.
3932 - Change the default required uptime for a relay to be accepted as
3933 a HSDir (hidden service directory) from 24 hours to 25 hours.
3934 Improves on 0.2.0.10-alpha; resolves ticket 2649.
3935 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
3936 authorities to abstain from voting on assignment of the HSDir
3937 consensus flag. Related to bug 2649.
3938 - Update to the September 6 2011 Maxmind GeoLite Country database.
3940 o Minor bugfixes (also part of 0.2.2.33):
3941 - Demote the 'replay detected' log message emitted when a hidden
3942 service receives the same Diffie-Hellman public key in two different
3943 INTRODUCE2 cells to info level. A normal Tor client can cause that
3944 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
3945 fixes part of bug 2442.
3946 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
3947 level. There is nothing that a hidden service's operator can do
3948 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
3950 - Clarify a log message specifying the characters permitted in
3951 HiddenServiceAuthorizeClient client names. Previously, the log
3952 message said that "[A-Za-z0-9+-_]" were permitted; that could have
3953 given the impression that every ASCII character between "+" and "_"
3954 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
3956 o Build fixes (also part of 0.2.2.33):
3957 - Clean up some code issues that prevented Tor from building on older
3958 BSDs. Fixes bug 3894; reported by "grarpamp".
3959 - Search for a platform-specific version of "ar" when cross-compiling.
3960 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
3963 - Fix a bug where the SocksPort option (for example) would get
3964 ignored and replaced by the default if a SocksListenAddress
3965 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
3969 - Relays now try regenerating and uploading their descriptor more
3970 frequently if they are not listed in the consensus, or if the
3971 version of their descriptor listed in the consensus is too
3972 old. This fix should prevent situations where a server declines
3973 to re-publish itself because it has done so too recently, even
3974 though the authorities decided not to list its recent-enough
3975 descriptor. Fix for bug 3327.
3978 - Relays now include a reason for regenerating their descriptors
3979 in an HTTP header when uploading to the authorities. This will
3980 make it easier to debug descriptor-upload issues in the future.
3981 - When starting as root and then changing our UID via the User
3982 control option, and we have a ControlSocket configured, make sure
3983 that the ControlSocket is owned by the same account that Tor will
3984 run under. Implements ticket 3421; fix by Jérémy Bobbio.
3987 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
3988 utility function used in the control-port code). This shouldn't
3989 ever happen unless Tor is completely out of memory, but if it did
3990 happen and Tor somehow recovered from it, Tor could have sent a log
3991 message to a control port in the middle of a reply to a controller
3992 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
3993 - Make 'FetchUselessDescriptors' cause all descriptor types and
3994 all consensus types (including microdescriptors) to get fetched.
3995 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
3998 - Make a new "entry connection" struct as an internal subtype of "edge
3999 connection", to simplify the code and make exit connections smaller.
4002 Changes in version 0.2.2.33 - 2011-09-13
4003 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4004 TLS handshake that makes relays and bridges that run this new version
4005 reachable from Iran again.
4008 - Avoid an assertion failure when reloading a configuration with
4009 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4010 3923; bugfix on 0.2.2.25-alpha.
4012 o Minor features (security):
4013 - Check for replays of the public-key encrypted portion of an
4014 INTRODUCE1 cell, in addition to the current check for replays of
4015 the g^x value. This prevents a possible class of active attacks
4016 by an attacker who controls both an introduction point and a
4017 rendezvous point, and who uses the malleability of AES-CTR to
4018 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4019 that these attacks are infeasible (requiring the attacker to send
4020 on the order of zettabytes of altered cells in a short interval),
4021 but we'd rather block them off in case there are any classes of
4022 this attack that we missed. Reported by Willem Pinckaers.
4025 - Adjust the expiration time on our SSL session certificates to
4026 better match SSL certs seen in the wild. Resolves ticket 4014.
4027 - Change the default required uptime for a relay to be accepted as
4028 a HSDir (hidden service directory) from 24 hours to 25 hours.
4029 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4030 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4031 authorities to abstain from voting on assignment of the HSDir
4032 consensus flag. Related to bug 2649.
4033 - Update to the September 6 2011 Maxmind GeoLite Country database.
4035 o Minor bugfixes (documentation and log messages):
4036 - Correct the man page to explain that HashedControlPassword and
4037 CookieAuthentication can both be set, in which case either method
4038 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4039 when we decided to allow these config options to both be set. Issue
4041 - Demote the 'replay detected' log message emitted when a hidden
4042 service receives the same Diffie-Hellman public key in two different
4043 INTRODUCE2 cells to info level. A normal Tor client can cause that
4044 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4045 fixes part of bug 2442.
4046 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4047 level. There is nothing that a hidden service's operator can do
4048 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4050 - Clarify a log message specifying the characters permitted in
4051 HiddenServiceAuthorizeClient client names. Previously, the log
4052 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4053 given the impression that every ASCII character between "+" and "_"
4054 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4057 - Provide a substitute implementation of lround() for MSVC, which
4058 apparently lacks it. Patch from Gisle Vanem.
4059 - Clean up some code issues that prevented Tor from building on older
4060 BSDs. Fixes bug 3894; reported by "grarpamp".
4061 - Search for a platform-specific version of "ar" when cross-compiling.
4062 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4065 Changes in version 0.2.3.3-alpha - 2011-09-01
4066 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4067 security, and provides client-side support for the microdescriptor
4068 and optimistic data features introduced earlier in the 0.2.3.x
4069 series. It also includes numerous critical bugfixes in the (optional)
4070 bufferevent-based networking backend.
4072 o Major features (stream isolation):
4073 - You can now configure Tor so that streams from different
4074 applications are isolated on different circuits, to prevent an
4075 attacker who sees your streams as they leave an exit node from
4076 linking your sessions to one another. To do this, choose some way
4077 to distinguish the applications: have them connect to different
4078 SocksPorts, or have one of them use SOCKS4 while the other uses
4079 SOCKS5, or have them pass different authentication strings to the
4080 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4081 degree of isolation you need. This implements Proposal 171.
4082 - There's a new syntax for specifying multiple client ports (such as
4083 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4084 multiple *Port entries with full addr:port syntax on each.
4085 The old *ListenAddress format is still supported, but you can't
4086 mix it with the new *Port syntax.
4088 o Major features (other):
4089 - Enable microdescriptor fetching by default for clients. This allows
4090 clients to download a much smaller amount of directory information.
4091 To disable it (and go back to the old-style consensus and
4092 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4093 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4094 "PortForwarding" config option), now supports Windows.
4095 - When using an exit relay running 0.2.3.x, clients can now
4096 "optimistically" send data before the exit relay reports that
4097 the stream has opened. This saves a round trip when starting
4098 connections where the client speaks first (such as web browsing).
4099 This behavior is controlled by a consensus parameter (currently
4100 disabled). To turn it on or off manually, use the "OptimisticData"
4101 torrc option. Implements proposal 181; code by Ian Goldberg.
4103 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4104 - When using IOCP on Windows, we need to enable Libevent windows
4106 - The IOCP backend now works even when the user has not specified
4107 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4108 Fixes part of bug 3752.
4109 - Correctly record the bytes we've read and written when using
4110 bufferevents, so that we can include them in our bandwidth history
4111 and advertised bandwidth. Fixes bug 3803.
4112 - Apply rate-limiting only at the bottom of a chain of filtering
4113 bufferevents. This prevents us from filling up internal read
4114 buffers and violating rate-limits when filtering bufferevents
4115 are enabled. Fixes part of bug 3804.
4116 - Add high-watermarks to the output buffers for filtered
4117 bufferevents. This prevents us from filling up internal write
4118 buffers and wasting CPU cycles when filtering bufferevents are
4119 enabled. Fixes part of bug 3804.
4120 - Correctly notice when data has been written from a bufferevent
4121 without flushing it completely. Fixes bug 3805.
4122 - Fix a bug where server-side tunneled bufferevent-based directory
4123 streams would get closed prematurely. Fixes bug 3814.
4124 - Fix a use-after-free error with per-connection rate-limiting
4125 buckets. Fixes bug 3888.
4127 o Major bugfixes (also part of 0.2.2.31-rc):
4128 - If we're configured to write our ControlPorts to disk, only write
4129 them after switching UID and creating the data directory. This way,
4130 we don't fail when starting up with a nonexistent DataDirectory
4131 and a ControlPortWriteToFile setting based on that directory. Fixes
4132 bug 3747; bugfix on Tor 0.2.2.26-beta.
4135 - Added a new CONF_CHANGED event so that controllers can be notified
4136 of any configuration changes made by other controllers, or by the
4137 user. Implements ticket 1692.
4138 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4139 leak when using bufferevents, and lets Libevent worry about how to
4140 best copy data out of a buffer.
4141 - Replace files in stats/ rather than appending to them. Now that we
4142 include statistics in extra-info descriptors, it makes no sense to
4143 keep old statistics forever. Implements ticket 2930.
4145 o Minor features (build compatibility):
4146 - Limited, experimental support for building with nmake and MSVC.
4147 - Provide a substitute implementation of lround() for MSVC, which
4148 apparently lacks it. Patch from Gisle Vanem.
4150 o Minor features (also part of 0.2.2.31-rc):
4151 - Update to the August 2 2011 Maxmind GeoLite Country database.
4153 o Minor bugfixes (on 0.2.3.x-alpha):
4154 - Fix a spurious warning when parsing SOCKS requests with
4155 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4156 - Get rid of a harmless warning that could happen on relays running
4157 with bufferevents. The warning was caused by someone doing an http
4158 request to a relay's orport. Also don't warn for a few related
4159 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4161 o Minor bugfixes (on 2.2.x and earlier):
4162 - Correct the man page to explain that HashedControlPassword and
4163 CookieAuthentication can both be set, in which case either method
4164 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4165 when we decided to allow these config options to both be set. Issue
4167 - The "--quiet" and "--hush" options now apply not only to Tor's
4168 behavior before logs are configured, but also to Tor's behavior in
4169 the absense of configured logs. Fixes bug 3550; bugfix on
4172 o Minor bugfixes (also part of 0.2.2.31-rc):
4173 - Write several files in text mode, on OSes that distinguish text
4174 mode from binary mode (namely, Windows). These files are:
4175 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4176 that collect those statistics; 'client_keys' and 'hostname' for
4177 hidden services that use authentication; and (in the tor-gencert
4178 utility) newly generated identity and signing keys. Previously,
4179 we wouldn't specify text mode or binary mode, leading to an
4180 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4181 the DirRecordUsageByCountry option which would have triggered
4182 the assertion failure was added), although this assertion failure
4183 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4184 - Selectively disable deprecation warnings on OS X because Lion
4185 started deprecating the shipped copy of openssl. Fixes bug 3643.
4186 - Remove an extra pair of quotation marks around the error
4187 message in control-port STATUS_GENERAL BUG events. Bugfix on
4188 0.1.2.6-alpha; fixes bug 3732.
4189 - When unable to format an address as a string, report its value
4190 as "???" rather than reusing the last formatted address. Bugfix
4193 o Code simplifications and refactoring:
4194 - Rewrite the listener-selection logic so that parsing which ports
4195 we want to listen on is now separate from binding to the ports
4199 - Building Tor with bufferevent support now requires Libevent
4200 2.0.13-stable or later. Previous versions of Libevent had bugs in
4201 SSL-related bufferevents and related issues that would make Tor
4202 work badly with bufferevents. Requiring 2.0.13-stable also allows
4203 Tor with bufferevents to take advantage of Libevent APIs
4204 introduced after 2.0.8-rc.
4207 Changes in version 0.2.2.32 - 2011-08-27
4208 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4209 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4210 a founder of the PETS community, a leader in our field, a mentor,
4211 and a friend. He left us with these words: "I had the possibility
4212 to contribute to this world that is not as it should be. I hope I
4213 could help in some areas to make the world a better place, and that
4214 I could also encourage other people to be engaged in improving the
4215 world. Please, stay engaged. This world needs you, your love, your
4216 initiative -- now I cannot be part of that anymore."
4218 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4219 ready. More than two years in the making, this release features improved
4220 client performance and hidden service reliability, better compatibility
4221 for Android, correct behavior for bridges that listen on more than
4222 one address, more extensible and flexible directory object handling,
4223 better reporting of network statistics, improved code security, and
4224 many many other features and bugfixes.
4227 Changes in version 0.2.2.31-rc - 2011-08-17
4228 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4229 for the Tor 0.2.2.x series.
4232 - Remove an extra pair of quotation marks around the error
4233 message in control-port STATUS_GENERAL BUG events. Bugfix on
4234 0.1.2.6-alpha; fixes bug 3732.
4235 - If we're configured to write our ControlPorts to disk, only write
4236 them after switching UID and creating the data directory. This way,
4237 we don't fail when starting up with a nonexistent DataDirectory
4238 and a ControlPortWriteToFile setting based on that directory. Fixes
4239 bug 3747; bugfix on Tor 0.2.2.26-beta.
4242 - Update to the August 2 2011 Maxmind GeoLite Country database.
4245 - Allow GETINFO fingerprint to return a fingerprint even when
4246 we have not yet built a router descriptor. Fixes bug 3577;
4247 bugfix on 0.2.0.1-alpha.
4248 - Write several files in text mode, on OSes that distinguish text
4249 mode from binary mode (namely, Windows). These files are:
4250 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4251 that collect those statistics; 'client_keys' and 'hostname' for
4252 hidden services that use authentication; and (in the tor-gencert
4253 utility) newly generated identity and signing keys. Previously,
4254 we wouldn't specify text mode or binary mode, leading to an
4255 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4256 the DirRecordUsageByCountry option which would have triggered
4257 the assertion failure was added), although this assertion failure
4258 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4259 - Selectively disable deprecation warnings on OS X because Lion
4260 started deprecating the shipped copy of openssl. Fixes bug 3643.
4261 - When unable to format an address as a string, report its value
4262 as "???" rather than reusing the last formatted address. Bugfix
4266 Changes in version 0.2.3.2-alpha - 2011-07-18
4267 Tor 0.2.3.2-alpha introduces two new experimental features:
4268 microdescriptors and pluggable transports. It also continues cleaning
4269 up a variety of recently introduced features.
4272 - Clients can now use microdescriptors instead of regular descriptors
4273 to build circuits. Microdescriptors are authority-generated
4274 summaries of regular descriptors' contents, designed to change
4275 very rarely (see proposal 158 for details). This feature is
4276 designed to save bandwidth, especially for clients on slow internet
4277 connections. It's off by default for now, since nearly no caches
4278 support it, but it will be on-by-default for clients in a future
4279 version. You can use the UseMicrodescriptors option to turn it on.
4280 - Tor clients using bridges can now be configured to use a separate
4281 'transport' proxy for each bridge. This approach helps to resist
4282 censorship by allowing bridges to use protocol obfuscation
4283 plugins. It implements part of proposal 180. Implements ticket 2841.
4284 - While we're trying to bootstrap, record how many TLS connections
4285 fail in each state, and report which states saw the most failures
4286 in response to any bootstrap failures. This feature may speed up
4287 diagnosis of censorship events. Implements ticket 3116.
4289 o Major bugfixes (on 0.2.3.1-alpha):
4290 - When configuring a large set of nodes in EntryNodes (as with
4291 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4292 random subset to be guards, and choose them in random
4293 order. Fixes bug 2798.
4294 - Tor could crash when remembering a consensus in a non-used consensus
4295 flavor without having a current consensus set. Fixes bug 3361.
4296 - Comparing an unknown address to a microdescriptor's shortened exit
4297 policy would always give a "rejected" result. Fixes bug 3599.
4298 - Using microdescriptors as a client no longer prevents Tor from
4299 uploading and downloading hidden service descriptors. Fixes
4303 - Allow nameservers with IPv6 address. Resolves bug 2574.
4304 - Accept attempts to include a password authenticator in the
4305 handshake, as supported by SOCKS5. This handles SOCKS clients that
4306 don't know how to omit a password when authenticating. Resolves
4308 - When configuring a large set of nodes in EntryNodes, and there are
4309 enough of them listed as Guard so that we don't need to consider
4310 the non-guard entries, prefer the ones listed with the Guard flag.
4311 - Check for and recover from inconsistency in the microdescriptor
4312 cache. This will make it harder for us to accidentally free a
4313 microdescriptor without removing it from the appropriate data
4314 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4315 - Log SSL state transitions at log level DEBUG, log domain
4316 HANDSHAKE. This can be useful for debugging censorship events.
4317 Implements ticket 3264.
4318 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4319 implements ticket 3439.
4321 o Minor bugfixes (on 0.2.3.1-alpha):
4322 - Do not free all general-purpose regular descriptors just
4323 because microdescriptor use is enabled. Fixes bug 3113.
4324 - Correctly link libevent_openssl when --enable-static-libevent
4325 is passed to configure. Fixes bug 3118.
4326 - Bridges should not complain during their heartbeat log messages that
4327 they are unlisted in the consensus: that's more or less the point
4328 of being a bridge. Fixes bug 3183.
4329 - Report a SIGNAL event to controllers when acting on a delayed
4330 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4331 event to the controller if we acted on a SIGNAL NEWNYM command
4332 immediately, and otherwise not report a SIGNAL event for the
4333 command at all. Fixes bug 3349.
4334 - Fix a crash when handling the SIGNAL controller command or
4335 reporting ERR-level status events with bufferevents enabled. Found
4336 by Robert Ransom. Fixes bug 3367.
4337 - Always ship the tor-fw-helper manpage in our release tarballs.
4338 Fixes bug 3389. Reported by Stephen Walker.
4339 - Fix a class of double-mark-for-close bugs when bufferevents
4340 are enabled. Fixes bug 3403.
4341 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4342 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4343 control-port command. Fixes part of bug 3465.
4344 - Prevent using negative indices during unit test runs when read_all()
4345 fails. Spotted by coverity.
4346 - Fix a rare memory leak when checking the nodelist without it being
4347 present. Found by coverity.
4348 - Only try to download a microdescriptor-flavored consensus from
4349 a directory cache that provides them.
4351 o Minor bugfixes (on 0.2.2.x and earlier):
4352 - Assert that hidden-service-related operations are not performed
4353 using single-hop circuits. Previously, Tor would assert that
4354 client-side streams are not attached to single-hop circuits,
4355 but not that other sensitive operations on the client and service
4356 side are not performed using single-hop circuits. Fixes bug 3332;
4358 - Don't publish a new relay descriptor when we reload our onion key,
4359 unless the onion key has actually changed. Fixes bug 3263 and
4360 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4361 - Allow GETINFO fingerprint to return a fingerprint even when
4362 we have not yet built a router descriptor. Fixes bug 3577;
4363 bugfix on 0.2.0.1-alpha.
4364 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4365 on 0.2.2.4-alpha; fixes bug 3427.
4367 o Code simplification and refactoring:
4368 - Use tor_sscanf() in place of scanf() in more places through the
4369 code. This makes us a little more locale-independent, and
4370 should help shut up code-analysis tools that can't tell
4371 a safe sscanf string from a dangerous one.
4372 - Use tt_assert(), not tor_assert(), for checking for test failures.
4373 This makes the unit tests more able to go on in the event that
4375 - Split connection_about_to_close() into separate functions for each
4379 - On Windows, we now define the _WIN32_WINNT macros only if they
4380 are not already defined. This lets the person building Tor decide,
4381 if they want, to require a later version of Windows.
4384 Changes in version 0.2.2.30-rc - 2011-07-07
4385 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4386 series. It fixes a few smaller bugs, but generally appears stable.
4387 Please test it and let us know whether it is!
4390 - Send a SUCCEEDED stream event to the controller when a reverse
4391 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4392 discovered by katmagic.
4393 - Always NUL-terminate the sun_path field of a sockaddr_un before
4394 passing it to the kernel. (Not a security issue: kernels are
4395 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4396 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4397 - Don't stack-allocate the list of supplementary GIDs when we're
4398 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4399 could take up to 256K, which is way too much stack. Found by
4400 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4401 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4402 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4403 fixes part of bug 3465.
4404 - Fix a memory leak when receiving a descriptor for a hidden
4405 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4409 - Update to the July 1 2011 Maxmind GeoLite Country database.
4412 Changes in version 0.2.2.29-beta - 2011-06-20
4413 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4414 have bridge lines in their torrc but don't want to use them; gets
4415 us closer to having the control socket feature working on Debian;
4416 and fixes a variety of smaller bugs.
4419 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4420 When we changed the default behavior to "use bridges if any
4421 are listed in the torrc", we surprised users who had bridges
4422 in their torrc files but who didn't actually want to use them.
4423 Partial resolution for bug 3354.
4426 - Don't attach new streams to old rendezvous circuits after SIGNAL
4427 NEWNYM. Previously, we would keep using an existing rendezvous
4428 circuit if it remained open (i.e. if it were kept open by a
4429 long-lived stream, or if a new stream were attached to it before
4430 Tor could notice that it was old and no longer in use). Bugfix on
4431 0.1.1.15-rc; fixes bug 3375.
4434 - Fix a bug when using ControlSocketsGroupWritable with User. The
4435 directory's group would be checked against the current group, not
4436 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4437 bugfix on 0.2.2.26-beta.
4438 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4439 expect it to emit a CRLF iff the format string ends with CRLF;
4440 it actually emitted a CRLF iff (a) the format string ended with
4441 CRLF or (b) the resulting string was over 1023 characters long or
4442 (c) the format string did not end with CRLF *and* the resulting
4443 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4444 fixes part of bug 3407.
4445 - Make send_control_event_impl()'s behaviour sane. Its callers
4446 expect it to always emit a CRLF at the end of the string; it
4447 might have emitted extra control characters as well. Bugfix on
4448 0.1.1.9-alpha; fixes another part of bug 3407.
4449 - Make crypto_rand_int() check the value of its input correctly.
4450 Previously, it accepted values up to UINT_MAX, but could return a
4451 negative number if given a value above INT_MAX+1. Found by George
4452 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4453 - Avoid a segfault when reading a malformed circuit build state
4454 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4456 - When asked about a DNS record type we don't support via a
4457 client DNSPort, reply with NOTIMPL rather than an empty
4458 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4459 - Fix a rare memory leak during stats writing. Found by coverity.
4462 - Update to the June 1 2011 Maxmind GeoLite Country database.
4464 o Code simplifications and refactoring:
4465 - Remove some dead code as indicated by coverity.
4466 - Remove a few dead assignments during router parsing. Found by
4468 - Add some forgotten return value checks during unit tests. Found
4470 - Don't use 1-bit wide signed bit fields. Found by coverity.
4473 Changes in version 0.2.2.28-beta - 2011-06-04
4474 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4475 fixed a big bug in whether relays stay in the consensus consistently,
4476 we moved closer to handling bridges and hidden services correctly,
4477 and we started the process of better handling the dreaded "my Vidalia
4478 died, and now my Tor demands a password when I try to reconnect to it"
4482 - Don't decide to make a new descriptor when receiving a HUP signal.
4483 This bug has caused a lot of 0.2.2.x relays to disappear from the
4484 consensus periodically. Fixes the most common case of triggering
4485 bug 1810; bugfix on 0.2.2.7-alpha.
4486 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4487 - Don't try to build descriptors if "ORPort auto" is set and we
4488 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4490 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4491 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4492 - Apply circuit timeouts to opened hidden-service-related circuits
4493 based on the correct start time. Previously, we would apply the
4494 circuit build timeout based on time since the circuit's creation;
4495 it was supposed to be applied based on time since the circuit
4496 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4497 - Use the same circuit timeout for client-side introduction
4498 circuits as for other four-hop circuits, rather than the timeout
4499 for single-hop directory-fetch circuits; the shorter timeout may
4500 have been appropriate with the static circuit build timeout in
4501 0.2.1.x and earlier, but caused many hidden service access attempts
4502 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4503 on 0.2.2.2-alpha; fixes another part of bug 1297.
4504 - In ticket 2511 we fixed a case where you could use an unconfigured
4505 bridge if you had configured it as a bridge the last time you ran
4506 Tor. Now fix another edge case: if you had configured it as a bridge
4507 but then switched to a different bridge via the controller, you
4508 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4512 - Add an __OwningControllerProcess configuration option and a
4513 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4514 that when it exits, Tor will shut down. Implements feature 3049.
4515 - If "UseBridges 1" is set and no bridges are configured, Tor will
4516 now refuse to build any circuits until some bridges are set.
4517 If "UseBridges auto" is set, Tor will use bridges if they are
4518 configured and we are not running as a server, but otherwise will
4519 make circuits as usual. The new default is "auto". Patch by anonym,
4520 so the Tails LiveCD can stop automatically revealing you as a Tor
4524 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4525 - Remove a trailing asterisk from "exit-policy/default" in the
4526 output of the control port command "GETINFO info/names". Bugfix
4528 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4530 - Warn when the user configures two HiddenServiceDir lines that point
4531 to the same directory. Bugfix on 0.0.6 (the version introducing
4532 HiddenServiceDir); fixes bug 3289.
4533 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4534 part of bug 2748; bugfix on 0.2.0.10-alpha.
4535 - Log malformed requests for rendezvous descriptors as protocol
4536 warnings, not warnings. Also, use a more informative log message
4537 in case someone sees it at log level warning without prior
4538 info-level messages. Fixes the other part of bug 2748; bugfix
4540 - Clear the table recording the time of the last request for each
4541 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4542 Previously, we would clear our HS descriptor cache on SIGNAL
4543 NEWNYM, but if we had previously retrieved a descriptor (or tried
4544 to) from every directory responsible for it, we would refuse to
4545 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4547 - Fix a log message that said "bits" while displaying a value in
4548 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4550 - When checking for 1024-bit keys, check for 1024 bits, not 128
4551 bytes. This allows Tor to correctly discard keys of length 1017
4552 through 1023. Bugfix on 0.0.9pre5.
4555 - Relays now log the reason for publishing a new relay descriptor,
4556 so we have a better chance of hunting down instances of bug 1810.
4557 Resolves ticket 3252.
4558 - Revise most log messages that refer to nodes by nickname to
4559 instead use the "$key=nickname at address" format. This should be
4560 more useful, especially since nicknames are less and less likely
4561 to be unique. Resolves ticket 3045.
4562 - Log (at info level) when purging pieces of hidden-service-client
4563 state because of SIGNAL NEWNYM.
4566 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4567 anything since 0.2.1.16-rc.
4570 Changes in version 0.2.2.27-beta - 2011-05-18
4571 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4572 release, and also adds a few more general bugfixes.
4575 - Fix a crash bug when changing bridges in a running Tor process.
4576 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4577 - When the controller configures a new bridge, don't wait 10 to 60
4578 seconds before trying to fetch its descriptor. Bugfix on
4579 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4582 - Require that onion keys have exponent 65537 in microdescriptors too.
4583 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4584 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4585 Changed the limit to 512 characters by removing base64 newlines.
4586 Fixes bug 2752. Fix by Michael Yakubovich.
4587 - When a client starts or stops using bridges, never use a circuit
4588 that was built before the configuration change. This behavior could
4589 put at risk a user who uses bridges to ensure that her traffic
4590 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4594 Changes in version 0.2.2.26-beta - 2011-05-17
4595 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4596 also introduces a new "socksport auto" approach that should make it
4597 easier to run multiple Tors on the same system, and does a lot of
4598 cleanup to get us closer to a release candidate.
4600 o Security/privacy fixes:
4601 - Replace all potentially sensitive memory comparison operations
4602 with versions whose runtime does not depend on the data being
4603 compared. This will help resist a class of attacks where an
4604 adversary can use variations in timing information to learn
4605 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4606 implementation by Robert Ransom based partially on code by DJB.)
4607 - When receiving a hidden service descriptor, check that it is for
4608 the hidden service we wanted. Previously, Tor would store any
4609 hidden service descriptors that a directory gave it, whether it
4610 wanted them or not. This wouldn't have let an attacker impersonate
4611 a hidden service, but it did let directories pre-seed a client
4612 with descriptors that it didn't want. Bugfix on 0.0.6.
4613 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4614 DNS cache entries, and virtual address mappings: that's what
4615 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4618 - The options SocksPort, ControlPort, and so on now all accept a
4619 value "auto" that opens a socket on an OS-selected port. A
4620 new ControlPortWriteToFile option tells Tor to write its
4621 actual control port or ports to a chosen file. If the option
4622 ControlPortFileGroupReadable is set, the file is created as
4623 group-readable. Now users can run two Tor clients on the same
4624 system without needing to manually mess with parameters. Resolves
4625 part of ticket 3076.
4626 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4627 help busy exit nodes avoid running out of useable ports just
4628 because all the ports have been used in the near past. Resolves
4632 - New "GETINFO net/listeners/(type)" controller command to return
4633 a list of addresses and ports that are bound for listeners for a
4634 given connection type. This is useful when the user has configured
4635 "SocksPort auto" and the controller needs to know which port got
4636 chosen. Resolves another part of ticket 3076.
4637 - Add a new ControlSocketsGroupWritable configuration option: when
4638 it is turned on, ControlSockets are group-writeable by the default
4639 group of the current user. Patch by Jérémy Bobbio; implements
4641 - Tor now refuses to create a ControlSocket in a directory that is
4642 world-readable (or group-readable if ControlSocketsGroupWritable
4643 is 0). This is necessary because some operating systems do not
4644 enforce permissions on an AF_UNIX sockets. Permissions on the
4645 directory holding the socket, however, seems to work everywhere.
4646 - Rate-limit a warning about failures to download v2 networkstatus
4647 documents. Resolves part of bug 1352.
4648 - Backport code from 0.2.3.x that allows directory authorities to
4649 clean their microdescriptor caches. Needed to resolve bug 2230.
4650 - When an HTTPS proxy reports "403 Forbidden", we now explain
4651 what it means rather than calling it an unexpected status code.
4652 Closes bug 2503. Patch from Michael Yakubovich.
4653 - Update to the May 1 2011 Maxmind GeoLite Country database.
4656 - Authorities now clean their microdesc cache periodically and when
4657 reading from disk initially, not only when adding new descriptors.
4658 This prevents a bug where we could lose microdescriptors. Bugfix
4659 on 0.2.2.6-alpha. Fixes bug 2230.
4660 - Do not crash when our configuration file becomes unreadable, for
4661 example due to a permissions change, between when we start up
4662 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4664 - Avoid a bug that would keep us from replacing a microdescriptor
4665 cache on Windows. (We would try to replace the file while still
4666 holding it open. That's fine on Unix, but Windows doesn't let us
4667 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4668 - Add missing explanations for the authority-related torrc options
4669 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4670 man page. Resolves issue 2379.
4671 - As an authority, do not upload our own vote or signature set to
4672 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4673 it would get flagged as a duplicate. Resolves bug 3026.
4674 - Accept hidden service descriptors if we think we might be a hidden
4675 service directory, regardless of what our consensus says. This
4676 helps robustness, since clients and hidden services can sometimes
4677 have a more up-to-date view of the network consensus than we do,
4678 and if they think that the directory authorities list us a HSDir,
4679 we might actually be one. Related to bug 2732; bugfix on
4681 - When a controller changes TrackHostExits, remove mappings for
4682 hosts that should no longer have their exits tracked. Bugfix on
4684 - When a controller changes VirtualAddrNetwork, remove any mappings
4685 for hosts that were automapped to the old network. Bugfix on
4687 - When a controller changes one of the AutomapHosts* options, remove
4688 any mappings for hosts that should no longer be automapped. Bugfix
4690 - Do not reset the bridge descriptor download status every time we
4691 re-parse our configuration or get a configuration change. Fixes
4692 bug 3019; bugfix on 0.2.0.3-alpha.
4694 o Minor bugfixes (code cleanup):
4695 - When loading the microdesc journal, remember its current size.
4696 In 0.2.2, this helps prevent the microdesc journal from growing
4697 without limit on authorities (who are the only ones to use it in
4698 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4699 Fix posted by "cypherpunks."
4700 - The microdesc journal is supposed to get rebuilt only if it is
4701 at least _half_ the length of the store, not _twice_ the length
4702 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4703 - Fix a potential null-pointer dereference while computing a
4704 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4706 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4707 cache without actually having any descriptors to cache. Bugfix on
4708 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4709 - If we fail to compute the identity digest of a v3 legacy keypair,
4710 warn, and don't use a buffer-full of junk instead. Bugfix on
4711 0.2.1.1-alpha; fixes bug 3106.
4712 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4713 where if the function had ever in the future been used to check
4714 for the presence of a too-large number, it would have given an
4715 incorrect result. (Fortunately, we only used it for 16-bit
4716 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4717 - Require that introduction point keys and onion handshake keys
4718 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4722 - Caches no longer download and serve v2 networkstatus documents
4723 unless FetchV2Networkstatus flag is set: these documents haven't
4724 haven't been used by clients or relays since 0.2.0.x. Resolves
4728 Changes in version 0.2.3.1-alpha - 2011-05-05
4729 Tor 0.2.3.1-alpha adds some new experimental features, including support
4730 for an improved network IO backend, IOCP networking on Windows,
4731 microdescriptor caching, "fast-start" support for streams, and automatic
4732 home router configuration. There are also numerous internal improvements
4733 to try to make the code easier for developers to work with.
4735 This is the first alpha release in a new series, so expect there to be
4736 bugs. Users who would rather test out a more stable branch should
4737 stay with 0.2.2.x for now.
4740 - Tor can now optionally build with the "bufferevents" buffered IO
4741 backend provided by Libevent 2. To use this feature, make sure you
4742 have the latest possible version of Libevent, and pass the
4743 --enable-bufferevents flag to configure when building Tor from
4744 source. This feature will make our networking code more flexible,
4745 let us stack layers on each other, and let us use more efficient
4746 zero-copy transports where available.
4747 - As an experimental feature, Tor can use IOCP for networking on Windows.
4748 Once this code is tuned and optimized, it promises much better
4749 performance than the select-based backend we've used in the past. To
4750 try this feature, you must build Tor with Libevent 2, configure Tor
4751 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4752 your torrc. There are known bugs here: only try this if you can help
4753 debug it as it breaks.
4754 - The EntryNodes option can now include country codes like {de} or IP
4755 addresses or network masks. Previously we had disallowed these options
4756 because we didn't have an efficient way to keep the list up to
4757 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4758 - Exit nodes now accept and queue data on not-yet-connected streams.
4759 Previously, the client wasn't allowed to send data until the stream was
4760 connected, which slowed down all connections. This change will enable
4761 clients to perform a "fast-start" on streams and send data without
4762 having to wait for a confirmation that the stream has opened. (Patch
4763 from Ian Goldberg; implements the server side of Proposal 174.)
4764 - Tor now has initial support for automatic port mapping on the many
4765 home routers that support NAT-PMP or UPnP. (Not yet supported on
4766 Windows). To build the support code, you'll need to have libnatpnp
4767 library and/or the libminiupnpc library, and you'll need to enable the
4768 feature specifically by passing "--enable-upnp" and/or
4769 "--enable-natpnp" to configure. To turn it on, use the new
4770 PortForwarding option.
4771 - Caches now download, cache, and serve multiple "flavors" of the
4772 consensus, including a flavor that describes microdescriptors.
4773 - Caches now download, cache, and serve microdescriptors -- small
4774 summaries of router descriptors that are authenticated by all of the
4775 directory authorities. Once enough caches are running this code,
4776 clients will be able to save significant amounts of directory bandwidth
4777 by downloading microdescriptors instead of router descriptors.
4780 - Make logging resolution configurable with a new LogTimeGranularity
4781 option, and change the default from 1 millisecond to 1 second.
4782 Implements enhancement 1668.
4783 - We log which torrc file we're using on startup. Implements ticket
4785 - Ordinarily, Tor does not count traffic from private addresses (like
4786 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
4787 There is now a new option, CountPrivateBandwidth, to disable this
4788 behavior. Patch from Daniel Cagara.
4789 - New --enable-static-tor configure option for building Tor as
4790 statically as possible. Idea, general hackery and thoughts from
4791 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
4793 - If you set the NumCPUs option to 0, Tor will now try to detect how
4794 many CPUs you have. This is the new default behavior.
4795 - Turn on directory request statistics by default and include them in
4796 extra-info descriptors. Don't break if we have no GeoIP database.
4797 - Relays that set "ConnDirectionStatistics 1" write statistics on the
4798 bidirectional use of connections to disk every 24 hours.
4799 - Add a GeoIP file digest to the extra-info descriptor. Implements
4801 - The NodeFamily option -- which let you declare that you want to
4802 consider nodes to be part of a family whether they list themselves
4803 that way or not -- now allows IP address ranges and country codes.
4804 - Add a new 'Heartbeat' log message type to periodically log a message
4805 describing Tor's status at level Notice. This feature is meant for
4806 operators who log at notice, and want to make sure that their Tor
4807 server is still working. Implementation by George Kadianakis.
4809 o Minor bugfixes (on 0.2.2.25-alpha):
4810 - When loading the microdesc journal, remember its current size.
4811 In 0.2.2, this helps prevent the microdesc journal from growing
4812 without limit on authorities (who are the only ones to use it in
4813 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4814 Fix posted by "cypherpunks."
4815 - The microdesc journal is supposed to get rebuilt only if it is
4816 at least _half_ the length of the store, not _twice_ the length
4817 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4818 - If as an authority we fail to compute the identity digest of a v3
4819 legacy keypair, warn, and don't use a buffer-full of junk instead.
4820 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
4821 - Authorities now clean their microdesc cache periodically and when
4822 reading from disk initially, not only when adding new descriptors.
4823 This prevents a bug where we could lose microdescriptors. Bugfix
4826 o Minor features (controller):
4827 - Add a new SIGNAL event to the controller interface so that
4828 controllers can be notified when Tor handles a signal. Resolves
4829 issue 1955. Patch by John Brooks.
4830 - Add a new GETINFO option to get total bytes read and written. Patch
4831 from pipe, revised by atagar. Resolves ticket 2345.
4832 - Implement some GETINFO controller fields to provide information about
4833 the Tor process's pid, euid, username, and resource limits.
4836 - Our build system requires automake 1.6 or later to create the
4837 Makefile.in files. Previously, you could have used 1.4.
4838 This only affects developers and people building Tor from git;
4839 people who build Tor from the source distribution without changing
4840 the Makefile.am files should be fine.
4841 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
4842 so on. This is more robust against some of the failure modes
4843 associated with running the autotools pieces on their own.
4845 o Minor packaging issues:
4846 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
4847 already created. Patch from Andreas Stieger. Fixes bug 2573.
4849 o Code simplifications and refactoring:
4850 - A major revision to our internal node-selecting and listing logic.
4851 Tor already had at least two major ways to look at the question of
4852 "which Tor servers do we know about": a list of router descriptors,
4853 and a list of entries in the current consensus. With
4854 microdescriptors, we're adding a third. Having so many systems
4855 without an abstraction layer over them was hurting the codebase.
4856 Now, we have a new "node_t" abstraction that presents a consistent
4857 interface to a client's view of a Tor node, and holds (nearly) all
4858 of the mutable state formerly in routerinfo_t and routerstatus_t.
4859 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
4860 no longer link against Libevent: they never used it, but
4861 our library structure used to force them to link it.
4864 - Remove some old code to work around even older versions of Tor that
4865 used forked processes to handle DNS requests. Such versions of Tor
4866 are no longer in use as servers.
4868 o Documentation fixes:
4869 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
4870 - Add missing documentation for the authority-related torrc options
4871 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
4875 Changes in version 0.2.2.25-alpha - 2011-04-29
4876 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
4877 robust, routers no longer overreport their bandwidth, Win7 should crash
4878 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
4879 now prevents hidden service-related activity from being linkable. It
4880 provides more information to Vidalia so you can see if your bridge is
4881 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
4882 StrictNodes configuration options to make them more reliable, more
4883 understandable, and more regularly applied. If you use those options,
4884 please see the revised documentation for them in the manual page.
4887 - Relays were publishing grossly inflated bandwidth values because
4888 they were writing their state files wrong--now they write the
4889 correct value. Also, resume reading bandwidth history from the
4890 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
4891 - Improve hidden service robustness: When we find that we have
4892 extended a hidden service's introduction circuit to a relay not
4893 listed as an introduction point in the HS descriptor we currently
4894 have, retry with an introduction point from the current
4895 descriptor. Previously we would just give up. Fixes bugs 1024 and
4896 1930; bugfix on 0.2.0.10-alpha.
4897 - Clients now stop trying to use an exit node associated with a given
4898 destination by TrackHostExits if they fail to reach that exit node.
4899 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
4900 - Fix crash bug on platforms where gmtime and localtime can return
4901 NULL. Windows 7 users were running into this one. Fixes part of bug
4902 2077. Bugfix on all versions of Tor. Found by boboper.
4904 o Security and stability fixes:
4905 - Don't double-free a parsable, but invalid, microdescriptor, even if
4906 it is followed in the blob we're parsing by an unparsable
4907 microdescriptor. Fixes an issue reported in a comment on bug 2954.
4908 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
4909 - If the Nickname configuration option isn't given, Tor would pick a
4910 nickname based on the local hostname as the nickname for a relay.
4911 Because nicknames are not very important in today's Tor and the
4912 "Unnamed" nickname has been implemented, this is now problematic
4913 behavior: It leaks information about the hostname without being
4914 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
4915 introduced the Unnamed nickname. Reported by tagnaq.
4916 - Fix an uncommon assertion failure when running with DNSPort under
4917 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4918 - Avoid linkability based on cached hidden service descriptors: forget
4919 all hidden service descriptors cached as a client when processing a
4920 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4923 - Export GeoIP information on bridge usage to controllers even if we
4924 have not yet been running for 24 hours. Now Vidalia bridge operators
4925 can get more accurate and immediate feedback about their
4926 contributions to the network.
4928 o Major features and bugfixes (node selection):
4929 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
4930 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
4931 options. Previously, we had been ambiguous in describing what
4932 counted as an "exit" node, and what operations exactly "StrictNodes
4933 0" would permit. This created confusion when people saw nodes built
4934 through unexpected circuits, and made it hard to tell real bugs from
4935 surprises. Now the intended behavior is:
4936 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
4937 a node that delivers user traffic outside the Tor network.
4938 . "Entry", in the context of EntryNodes, means a node used as the
4939 first hop of a multihop circuit. It doesn't include direct
4940 connections to directory servers.
4941 . "ExcludeNodes" applies to all nodes.
4942 . "StrictNodes" changes the behavior of ExcludeNodes only. When
4943 StrictNodes is set, Tor should avoid all nodes listed in
4944 ExcludeNodes, even when it will make user requests fail. When
4945 StrictNodes is *not* set, then Tor should follow ExcludeNodes
4946 whenever it can, except when it must use an excluded node to
4947 perform self-tests, connect to a hidden service, provide a
4948 hidden service, fulfill a .exit request, upload directory
4949 information, or fetch directory information.
4950 Collectively, the changes to implement the behavior fix bug 1090.
4951 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
4952 a node is listed in both, it's treated as excluded.
4953 - ExcludeNodes now applies to directory nodes -- as a preference if
4954 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
4955 Don't exclude all the directory authorities and set StrictNodes to 1
4956 unless you really want your Tor to break.
4957 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
4958 - ExcludeExitNodes now overrides .exit requests.
4959 - We don't use bridges listed in ExcludeNodes.
4960 - When StrictNodes is 1:
4961 . We now apply ExcludeNodes to hidden service introduction points
4962 and to rendezvous points selected by hidden service users. This
4963 can make your hidden service less reliable: use it with caution!
4964 . If we have used ExcludeNodes on ourself, do not try relay
4965 reachability self-tests.
4966 . If we have excluded all the directory authorities, we will not
4967 even try to upload our descriptor if we're a relay.
4968 . Do not honor .exit requests to an excluded node.
4969 - Remove a misfeature that caused us to ignore the Fast/Stable flags
4970 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
4971 - When the set of permitted nodes changes, we now remove any mappings
4972 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
4974 - We never cannibalize a circuit that had excluded nodes on it, even
4975 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
4976 - Revert a change where we would be laxer about attaching streams to
4977 circuits than when building the circuits. This was meant to prevent
4978 a set of bugs where streams were never attachable, but our improved
4979 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
4980 - Keep track of how many times we launch a new circuit to handle a
4981 given stream. Too many launches could indicate an inconsistency
4982 between our "launch a circuit to handle this stream" logic and our
4983 "attach this stream to one of the available circuits" logic.
4984 - Improve log messages related to excluded nodes.
4987 - Fix a spurious warning when moving from a short month to a long
4988 month on relays with month-based BandwidthAccounting. Bugfix on
4989 0.2.2.17-alpha; fixes bug 3020.
4990 - When a client finds that an origin circuit has run out of 16-bit
4991 stream IDs, we now mark it as unusable for new streams. Previously,
4992 we would try to close the entire circuit. Bugfix on 0.0.6.
4993 - Add a forgotten cast that caused a compile warning on OS X 10.6.
4994 Bugfix on 0.2.2.24-alpha.
4995 - Be more careful about reporting the correct error from a failed
4996 connect() system call. Under some circumstances, it was possible to
4997 look at an incorrect value for errno when sending the end reason.
4998 Bugfix on 0.1.0.1-rc.
4999 - Correctly handle an "impossible" overflow cases in connection byte
5000 counting, where we write or read more than 4GB on an edge connection
5001 in a single second. Bugfix on 0.1.2.8-beta.
5002 - Correct the warning displayed when a rendezvous descriptor exceeds
5003 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5005 - Clients and hidden services now use HSDir-flagged relays for hidden
5006 service descriptor downloads and uploads even if the relays have no
5007 DirPort set and the client has disabled TunnelDirConns. This will
5008 eventually allow us to give the HSDir flag to relays with no
5009 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5010 - Downgrade "no current certificates known for authority" message from
5011 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5012 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5013 2917. Bugfix on 0.1.1.1-alpha.
5014 - Only limit the lengths of single HS descriptors, even when multiple
5015 HS descriptors are published to an HSDir relay in a single POST
5016 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5017 - Write the current time into the LastWritten line in our state file,
5018 rather than the time from the previous write attempt. Also, stop
5019 trying to use a time of -1 in our log statements. Fixes bug 3039;
5020 bugfix on 0.2.2.14-alpha.
5021 - Be more consistent in our treatment of file system paths. "~" should
5022 get expanded to the user's home directory in the Log config option.
5023 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5024 feature for the -f and --DataDirectory options.
5027 - Make sure every relay writes a state file at least every 12 hours.
5028 Previously, a relay could go for weeks without writing its state
5029 file, and on a crash could lose its bandwidth history, capacity
5030 estimates, client country statistics, and so on. Addresses bug 3012.
5031 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5032 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5033 clients are already deprecated because of security bugs.
5034 - Don't allow v0 hidden service authorities to act as clients.
5035 Required by fix for bug 3000.
5036 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5037 by fix for bug 3000.
5038 - Ensure that no empty [dirreq-](read|write)-history lines are added
5039 to an extrainfo document. Implements ticket 2497.
5041 o Code simplification and refactoring:
5042 - Remove workaround code to handle directory responses from servers
5043 that had bug 539 (they would send HTTP status 503 responses _and_
5044 send a body too). Since only server versions before
5045 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5046 keep the workaround in place.
5047 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5048 handling calculations where we have a known amount of clock skew and
5049 an allowed amount of unknown skew. But we only used it in three
5050 places, and we never adjusted the known/unknown skew values. This is
5051 still something we might want to do someday, but if we do, we'll
5052 want to do it differently.
5053 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5054 None of the cases where we did this before were wrong, but by making
5055 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5056 - Use GetTempDir to find the proper temporary directory location on
5057 Windows when generating temporary files for the unit tests. Patch by
5061 Changes in version 0.2.2.24-alpha - 2011-04-08
5062 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5063 prevented Tor clients from effectively using "multihomed" bridges,
5064 that is, bridges that listen on multiple ports or IP addresses so users
5065 can continue to use some of their addresses even if others get blocked.
5068 - Fix a bug where bridge users who configure the non-canonical
5069 address of a bridge automatically switch to its canonical
5070 address. If a bridge listens at more than one address, it should be
5071 able to advertise those addresses independently and any non-blocked
5072 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5074 - If you configured Tor to use bridge A, and then quit and
5075 configured Tor to use bridge B instead, it would happily continue
5076 to use bridge A if it's still reachable. While this behavior is
5077 a feature if your goal is connectivity, in some scenarios it's a
5078 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5079 - Directory authorities now use data collected from their own
5080 uptime observations when choosing whether to assign the HSDir flag
5081 to relays, instead of trusting the uptime value the relay reports in
5082 its descriptor. This change helps prevent an attack where a small
5083 set of nodes with frequently-changing identity keys can blackhole
5084 a hidden service. (Only authorities need upgrade; others will be
5085 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5088 - When we restart our relay, we might get a successful connection
5089 from the outside before we've started our reachability tests,
5090 triggering a warning: "ORPort found reachable, but I have no
5091 routerinfo yet. Failing to inform controller of success." This
5092 bug was harmless unless Tor is running under a controller
5093 like Vidalia, in which case the controller would never get a
5094 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5096 - Make directory authorities more accurate at recording when
5097 relays that have failed several reachability tests became
5098 unreachable, so we can provide more accuracy at assigning Stable,
5099 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5100 - Fix an issue that prevented static linking of libevent on
5101 some platforms (notably Linux). Fixes bug 2698; bugfix on
5102 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5103 the --with-static-libevent configure option).
5104 - We now ask the other side of a stream (the client or the exit)
5105 for more data on that stream when the amount of queued data on
5106 that stream dips low enough. Previously, we wouldn't ask the
5107 other side for more data until either it sent us more data (which
5108 it wasn't supposed to do if it had exhausted its window!) or we
5109 had completely flushed all our queued data. This flow control fix
5110 should improve throughput. Fixes bug 2756; bugfix on the earliest
5111 released versions of Tor (svn commit r152).
5112 - Avoid a double-mark-for-free warning when failing to attach a
5113 transparent proxy connection. (We thought we had fixed this in
5114 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5115 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5116 bug) and 0.2.2.23-alpha (the incorrect fix).
5117 - When warning about missing zlib development packages during compile,
5118 give the correct package names. Bugfix on 0.2.0.1-alpha.
5121 - Directory authorities now log the source of a rejected POSTed v3
5123 - Make compilation with clang possible when using
5124 --enable-gcc-warnings by removing two warning options that clang
5125 hasn't implemented yet and by fixing a few warnings. Implements
5127 - When expiring circuits, use microsecond timers rather than
5128 one-second timers. This can avoid an unpleasant situation where a
5129 circuit is launched near the end of one second and expired right
5130 near the beginning of the next, and prevent fluctuations in circuit
5132 - Use computed circuit-build timeouts to decide when to launch
5133 parallel introduction circuits for hidden services. (Previously,
5134 we would retry after 15 seconds.)
5135 - Update to the April 1 2011 Maxmind GeoLite Country database.
5138 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5139 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5141 o Documentation changes:
5142 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5143 - Resolve all doxygen warnings except those for missing documentation.
5145 - Add doxygen documentation for more functions, fields, and types.
5148 Changes in version 0.2.2.23-alpha - 2011-03-08
5149 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5150 they restart they don't lose their bandwidth capacity estimate. This
5151 release also fixes a diverse set of user-facing bugs, ranging from
5152 relays overrunning their rate limiting to clients falsely warning about
5153 clock skew to bridge descriptor leaks by our bridge directory authority.
5156 - Stop sending a CLOCK_SKEW controller status event whenever
5157 we fetch directory information from a relay that has a wrong clock.
5158 Instead, only inform the controller when it's a trusted authority
5159 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5160 the rest of bug 1074.
5161 - Fix an assert in parsing router descriptors containing IPv6
5162 addresses. This one took down the directory authorities when
5163 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5164 - Make the bridge directory authority refuse to answer directory
5165 requests for "all" descriptors. It used to include bridge
5166 descriptors in its answer, which was a major information leak.
5167 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5168 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5169 Tor would ignore their RelayBandwidthBurst setting,
5170 potentially using more bandwidth than expected. Bugfix on
5171 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5172 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5173 hidserv" in her torrc. The 'hidserv' argument never controlled
5174 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5177 - Relays now save observed peak bandwidth throughput rates to their
5178 state file (along with total usage, which was already saved)
5179 so that they can determine their correct estimated bandwidth on
5180 restart. Resolves bug 1863, where Tor relays would reset their
5181 estimated bandwidth to 0 after restarting.
5182 - Directory authorities now take changes in router IP address and
5183 ORPort into account when determining router stability. Previously,
5184 if a router changed its IP or ORPort, the authorities would not
5185 treat it as having any downtime for the purposes of stability
5186 calculation, whereas clients would experience downtime since the
5187 change could take a while to propagate to them. Resolves issue 1035.
5188 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5189 Prevention (DEP) by default on Windows to make it harder for
5190 attackers to exploit vulnerabilities. Patch from John Brooks.
5192 o Minor bugfixes (on 0.2.1.x and earlier):
5193 - Fix a rare crash bug that could occur when a client was configured
5194 with a large number of bridges. Fixes bug 2629; bugfix on
5195 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5196 - Avoid a double mark-for-free warning when failing to attach a
5197 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5199 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5200 found by "cypherpunks". This bug was introduced before the first
5201 Tor release, in svn commit r110.
5202 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5203 don't mention them in the manpage. Fixes bug 2450; issue
5204 spotted by keb and G-Lo.
5205 - Fix a bug in bandwidth history state parsing that could have been
5206 triggered if a future version of Tor ever changed the timing
5207 granularity at which bandwidth history is measured. Bugfix on
5209 - When a relay decides that its DNS is too broken for it to serve
5210 as an exit server, it advertised itself as a non-exit, but
5211 continued to act as an exit. This could create accidental
5212 partitioning opportunities for users. Instead, if a relay is
5213 going to advertise reject *:* as its exit policy, it should
5214 really act with exit policy "reject *:*". Fixes bug 2366.
5215 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5216 - In the special case where you configure a public exit relay as your
5217 bridge, Tor would be willing to use that exit relay as the last
5218 hop in your circuit as well. Now we fail that circuit instead.
5219 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5220 - Fix a bug with our locking implementation on Windows that couldn't
5221 correctly detect when a file was already locked. Fixes bug 2504,
5222 bugfix on 0.2.1.6-alpha.
5223 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5224 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5226 - Set target port in get_interface_address6() correctly. Bugfix
5227 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5228 - Directory authorities are now more robust to hops back in time
5229 when calculating router stability. Previously, if a run of uptime
5230 or downtime appeared to be negative, the calculation could give
5231 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5233 - Fix an assert that got triggered when using the TestingTorNetwork
5234 configuration option and then issuing a GETINFO config-text control
5235 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5237 o Minor bugfixes (on 0.2.2.x):
5238 - Clients should not weight BadExit nodes as Exits in their node
5239 selection. Similarly, directory authorities should not count BadExit
5240 bandwidth as Exit bandwidth when computing bandwidth-weights.
5241 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5242 - Correctly clear our dir_read/dir_write history when there is an
5243 error parsing any bw history value from the state file. Bugfix on
5245 - Resolve a bug in verifying signatures of directory objects
5246 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5247 Fixes bug 2409. Found by "piebeer".
5248 - Bridge authorities no longer crash on SIGHUP when they try to
5249 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5253 - Log less aggressively about circuit timeout changes, and improve
5254 some other circuit timeout messages. Resolves bug 2004.
5255 - Log a little more clearly about the times at which we're no longer
5256 accepting new connections. Resolves bug 2181.
5257 - Reject attempts at the client side to open connections to private
5258 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5259 a randomly chosen exit node. Attempts to do so are always
5260 ill-defined, generally prevented by exit policies, and usually
5261 in error. This will also help to detect loops in transparent
5262 proxy configurations. You can disable this feature by setting
5263 "ClientRejectInternalAddresses 0" in your torrc.
5264 - Always treat failure to allocate an RSA key as an unrecoverable
5266 - Update to the March 1 2011 Maxmind GeoLite Country database.
5268 o Minor features (log subsystem):
5269 - Add documentation for configuring logging at different severities in
5270 different log domains. We've had this feature since 0.2.1.1-alpha,
5271 but for some reason it never made it into the manpage. Fixes
5273 - Make it simpler to specify "All log domains except for A and B".
5274 Previously you needed to say "[*,~A,~B]". Now you can just say
5276 - Add a "LogMessageDomains 1" option to include the domains of log
5277 messages along with the messages. Without this, there's no way
5278 to use log domains without reading the source or doing a lot
5281 o Packaging changes:
5282 - Stop shipping the Tor specs files and development proposal documents
5283 in the tarball. They are now in a separate git repository at
5284 git://git.torproject.org/torspec.git
5287 Changes in version 0.2.1.30 - 2011-02-23
5288 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5289 change is a slight tweak to Tor's TLS handshake that makes relays
5290 and bridges that run this new version reachable from Iran again.
5291 We don't expect this tweak will win the arms race long-term, but it
5292 buys us time until we roll out a better solution.
5295 - Stop sending a CLOCK_SKEW controller status event whenever
5296 we fetch directory information from a relay that has a wrong clock.
5297 Instead, only inform the controller when it's a trusted authority
5298 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5299 the rest of bug 1074.
5300 - Fix a bounds-checking error that could allow an attacker to
5301 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5303 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5304 Tor would ignore their RelayBandwidthBurst setting,
5305 potentially using more bandwidth than expected. Bugfix on
5306 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5307 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5308 hidserv" in her torrc. The 'hidserv' argument never controlled
5309 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5312 - Adjust our TLS Diffie-Hellman parameters to match those used by
5314 - Update to the February 1 2011 Maxmind GeoLite Country database.
5317 - Check for and reject overly long directory certificates and
5318 directory tokens before they have a chance to hit any assertions.
5319 Bugfix on 0.2.1.28. Found by "doorss".
5320 - Bring the logic that gathers routerinfos and assesses the
5321 acceptability of circuits into line. This prevents a Tor OP from
5322 getting locked in a cycle of choosing its local OR as an exit for a
5323 path (due to a .exit request) and then rejecting the circuit because
5324 its OR is not listed yet. It also prevents Tor clients from using an
5325 OR running in the same instance as an exit (due to a .exit request)
5326 if the OR does not meet the same requirements expected of an OR
5327 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5329 o Packaging changes:
5330 - Stop shipping the Tor specs files and development proposal documents
5331 in the tarball. They are now in a separate git repository at
5332 git://git.torproject.org/torspec.git
5333 - Do not include Git version tags as though they are SVN tags when
5334 generating a tarball from inside a repository that has switched
5335 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5338 Changes in version 0.2.2.22-alpha - 2011-01-25
5339 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5340 main other change is a slight tweak to Tor's TLS handshake that makes
5341 relays and bridges that run this new version reachable from Iran again.
5342 We don't expect this tweak will win the arms race long-term, but it
5343 will buy us a bit more time until we roll out a better solution.
5346 - Fix a bounds-checking error that could allow an attacker to
5347 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5349 - Don't assert when changing from bridge to relay or vice versa
5350 via the controller. The assert happened because we didn't properly
5351 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5352 bug 2433. Reported by bastik.
5355 - Adjust our TLS Diffie-Hellman parameters to match those used by
5357 - Provide a log message stating which geoip file we're parsing
5358 instead of just stating that we're parsing the geoip file.
5359 Implements ticket 2432.
5362 - Check for and reject overly long directory certificates and
5363 directory tokens before they have a chance to hit any assertions.
5364 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5367 Changes in version 0.2.2.21-alpha - 2011-01-15
5368 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5369 continues our recent code security audit work. The main fix resolves
5370 a remote heap overflow vulnerability that can allow remote code
5371 execution (CVE-2011-0427). Other fixes address a variety of assert
5372 and crash bugs, most of which we think are hard to exploit remotely.
5374 o Major bugfixes (security), also included in 0.2.1.29:
5375 - Fix a heap overflow bug where an adversary could cause heap
5376 corruption. This bug probably allows remote code execution
5377 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5379 - Prevent a denial-of-service attack by disallowing any
5380 zlib-compressed data whose compression factor is implausibly
5381 high. Fixes part of bug 2324; reported by "doorss".
5382 - Zero out a few more keys in memory before freeing them. Fixes
5383 bug 2384 and part of bug 2385. These key instances found by
5384 "cypherpunks", based on Andrew Case's report about being able
5385 to find sensitive data in Tor's memory space if you have enough
5386 permissions. Bugfix on 0.0.2pre9.
5388 o Major bugfixes (crashes), also included in 0.2.1.29:
5389 - Prevent calls to Libevent from inside Libevent log handlers.
5390 This had potential to cause a nasty set of crashes, especially
5391 if running Libevent with debug logging enabled, and running
5392 Tor with a controller watching for low-severity log messages.
5393 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5394 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5395 underflow errors there too. Fixes the other part of bug 2324.
5396 - Fix a bug where we would assert if we ever had a
5397 cached-descriptors.new file (or another file read directly into
5398 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5399 on 0.2.1.25. Found by doorss.
5400 - Fix some potential asserts and parsing issues with grossly
5401 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5404 o Minor bugfixes (other), also included in 0.2.1.29:
5405 - Fix a bug with handling misformed replies to reverse DNS lookup
5406 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5407 bug reported by doorss.
5408 - Fix compilation on mingw when a pthreads compatibility library
5409 has been installed. (We don't want to use it, so we shouldn't
5410 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5411 - Fix a bug where we would declare that we had run out of virtual
5412 addresses when the address space was only half-exhausted. Bugfix
5414 - Correctly handle the case where AutomapHostsOnResolve is set but
5415 no virtual addresses are available. Fixes bug 2328; bugfix on
5416 0.1.2.1-alpha. Bug found by doorss.
5417 - Correctly handle wrapping around when we run out of virtual
5418 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5420 o Minor features, also included in 0.2.1.29:
5421 - Update to the January 1 2011 Maxmind GeoLite Country database.
5422 - Introduce output size checks on all of our decryption functions.
5424 o Build changes, also included in 0.2.1.29:
5425 - Tor does not build packages correctly with Automake 1.6 and earlier;
5426 added a check to Makefile.am to make sure that we're building with
5427 Automake 1.7 or later.
5428 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5429 because we built it with a too-old version of automake. Thus that
5430 release broke ./configure --enable-openbsd-malloc, which is popular
5431 among really fast exit relays on Linux.
5433 o Major bugfixes, new in 0.2.2.21-alpha:
5434 - Prevent crash/heap corruption when the cbtnummodes consensus
5435 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5438 o Major features, new in 0.2.2.21-alpha:
5439 - Introduce minimum/maximum values that clients will believe
5440 from the consensus. Now we'll have a better chance to avoid crashes
5441 or worse when a consensus param has a weird value.
5443 o Minor features, new in 0.2.2.21-alpha:
5444 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5445 used on bridges, and it makes bridge scanning somewhat easier.
5446 - If writing the state file to disk fails, wait up to an hour before
5447 retrying again, rather than trying again each second. Fixes bug
5448 2346; bugfix on Tor 0.1.1.3-alpha.
5449 - Make Libevent log messages get delivered to controllers later,
5450 and not from inside the Libevent log handler. This prevents unsafe
5451 reentrant Libevent calls while still letting the log messages
5453 - Detect platforms that brokenly use a signed size_t, and refuse to
5454 build there. Found and analyzed by doorss and rransom.
5455 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5458 o Minor bugfixes, new in 0.2.2.21-alpha:
5459 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5460 than waiting forever for them to finish. Fixes bug 2330; bugfix
5461 on 0.2.0.16-alpha. Found by doorss.
5462 - Add assertions to check for overflow in arguments to
5463 base32_encode() and base32_decode(); fix a signed-unsigned
5464 comparison there too. These bugs are not actually reachable in Tor,
5465 but it's good to prevent future errors too. Found by doorss.
5466 - Correctly detect failures to create DNS requests when using Libevent
5467 versions before v2. (Before Libevent 2, we used our own evdns
5468 implementation. Its return values for Libevent's evdns_resolve_*()
5469 functions are not consistent with those from Libevent.) Fixes bug
5470 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5472 o Documentation, new in 0.2.2.21-alpha:
5473 - Document the default socks host and port (127.0.0.1:9050) for
5477 Changes in version 0.2.1.29 - 2011-01-15
5478 Tor 0.2.1.29 continues our recent code security audit work. The main
5479 fix resolves a remote heap overflow vulnerability that can allow remote
5480 code execution. Other fixes address a variety of assert and crash bugs,
5481 most of which we think are hard to exploit remotely.
5483 o Major bugfixes (security):
5484 - Fix a heap overflow bug where an adversary could cause heap
5485 corruption. This bug probably allows remote code execution
5486 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5488 - Prevent a denial-of-service attack by disallowing any
5489 zlib-compressed data whose compression factor is implausibly
5490 high. Fixes part of bug 2324; reported by "doorss".
5491 - Zero out a few more keys in memory before freeing them. Fixes
5492 bug 2384 and part of bug 2385. These key instances found by
5493 "cypherpunks", based on Andrew Case's report about being able
5494 to find sensitive data in Tor's memory space if you have enough
5495 permissions. Bugfix on 0.0.2pre9.
5497 o Major bugfixes (crashes):
5498 - Prevent calls to Libevent from inside Libevent log handlers.
5499 This had potential to cause a nasty set of crashes, especially
5500 if running Libevent with debug logging enabled, and running
5501 Tor with a controller watching for low-severity log messages.
5502 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5503 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5504 underflow errors there too. Fixes the other part of bug 2324.
5505 - Fix a bug where we would assert if we ever had a
5506 cached-descriptors.new file (or another file read directly into
5507 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5508 on 0.2.1.25. Found by doorss.
5509 - Fix some potential asserts and parsing issues with grossly
5510 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5513 o Minor bugfixes (other):
5514 - Fix a bug with handling misformed replies to reverse DNS lookup
5515 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5516 bug reported by doorss.
5517 - Fix compilation on mingw when a pthreads compatibility library
5518 has been installed. (We don't want to use it, so we shouldn't
5519 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5520 - Fix a bug where we would declare that we had run out of virtual
5521 addresses when the address space was only half-exhausted. Bugfix
5523 - Correctly handle the case where AutomapHostsOnResolve is set but
5524 no virtual addresses are available. Fixes bug 2328; bugfix on
5525 0.1.2.1-alpha. Bug found by doorss.
5526 - Correctly handle wrapping around to when we run out of virtual
5527 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5528 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5529 because we built it with a too-old version of automake. Thus that
5530 release broke ./configure --enable-openbsd-malloc, which is popular
5531 among really fast exit relays on Linux.
5534 - Update to the January 1 2011 Maxmind GeoLite Country database.
5535 - Introduce output size checks on all of our decryption functions.
5538 - Tor does not build packages correctly with Automake 1.6 and earlier;
5539 added a check to Makefile.am to make sure that we're building with
5540 Automake 1.7 or later.
5543 Changes in version 0.2.2.20-alpha - 2010-12-17
5544 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5545 exploitable bugs. We also fix a variety of other significant bugs,
5546 change the IP address for one of our directory authorities, and update
5547 the minimum version that Tor relays must run to join the network.
5550 - Fix a remotely exploitable bug that could be used to crash instances
5551 of Tor remotely by overflowing on the heap. Remote-code execution
5552 hasn't been confirmed, but can't be ruled out. Everyone should
5553 upgrade. Bugfix on the 0.1.1 series and later.
5554 - Fix a bug that could break accounting on 64-bit systems with large
5555 time_t values, making them hibernate for impossibly long intervals.
5556 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5557 - Fix a logic error in directory_fetches_from_authorities() that
5558 would cause all _non_-exits refusing single-hop-like circuits
5559 to fetch from authorities, when we wanted to have _exits_ fetch
5560 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5562 - Fix a stream fairness bug that would cause newer streams on a given
5563 circuit to get preference when reading bytes from the origin or
5564 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5565 introduced before the first Tor release, in svn revision r152.
5567 o Directory authority changes:
5568 - Change IP address and ports for gabelmoo (v3 directory authority).
5571 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5572 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5573 - Fix an off-by-one error in calculating some controller command
5574 argument lengths. Fortunately, this mistake is harmless since
5575 the controller code does redundant NUL termination too. Found by
5576 boboper. Bugfix on 0.1.1.1-alpha.
5577 - Do not dereference NULL if a bridge fails to build its
5578 extra-info descriptor. Found by an anonymous commenter on
5579 Trac. Bugfix on 0.2.2.19-alpha.
5582 - Update to the December 1 2010 Maxmind GeoLite Country database.
5583 - Directory authorities now reject relays running any versions of
5584 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5585 known bugs that keep RELAY_EARLY cells from working on rendezvous
5586 circuits. Followup to fix for bug 2081.
5587 - Directory authorities now reject relays running any version of Tor
5588 older than 0.2.0.26-rc. That version is the earliest that fetches
5589 current directory information correctly. Fixes bug 2156.
5590 - Report only the top 10 ports in exit-port stats in order not to
5591 exceed the maximum extra-info descriptor length of 50 KB. Implements
5595 Changes in version 0.2.1.28 - 2010-12-17
5596 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5597 exploitable bugs. We also took this opportunity to change the IP address
5598 for one of our directory authorities, and to update the geoip database
5602 - Fix a remotely exploitable bug that could be used to crash instances
5603 of Tor remotely by overflowing on the heap. Remote-code execution
5604 hasn't been confirmed, but can't be ruled out. Everyone should
5605 upgrade. Bugfix on the 0.1.1 series and later.
5607 o Directory authority changes:
5608 - Change IP address and ports for gabelmoo (v3 directory authority).
5611 - Update to the December 1 2010 Maxmind GeoLite Country database.
5614 Changes in version 0.2.1.27 - 2010-11-23
5615 Yet another OpenSSL security patch broke its compatibility with Tor:
5616 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5617 also took this opportunity to fix several crash bugs, integrate a new
5618 directory authority, and update the bundled GeoIP database.
5621 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5622 No longer set the tlsext_host_name extension on server SSL objects;
5623 but continue to set it on client SSL objects. Our goal in setting
5624 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5625 bugfix on 0.2.1.1-alpha.
5626 - Do not log messages to the controller while shrinking buffer
5627 freelists. Doing so would sometimes make the controller connection
5628 try to allocate a buffer chunk, which would mess up the internals
5629 of the freelist and cause an assertion failure. Fixes bug 1125;
5630 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5631 - Learn our external IP address when we're a relay or bridge, even if
5632 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5633 where we introduced bridge relays that don't need to publish to
5634 be useful. Fixes bug 2050.
5635 - Do even more to reject (and not just ignore) annotations on
5636 router descriptors received anywhere but from the cache. Previously
5637 we would ignore such annotations at first, but cache them to disk
5638 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5639 - When you're using bridges and your network goes away and your
5640 bridges get marked as down, recover when you attempt a new socks
5641 connection (if the network is back), rather than waiting up to an
5642 hour to try fetching new descriptors for your bridges. Bugfix on
5643 0.2.0.3-alpha; fixes bug 1981.
5646 - Move to the November 2010 Maxmind GeoLite country db (rather
5647 than the June 2009 ip-to-country GeoIP db) for our statistics that
5648 count how many users relays are seeing from each country. Now we'll
5649 have more accurate data, especially for many African countries.
5651 o New directory authorities:
5652 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5656 - Fix an assertion failure that could occur in directory caches or
5657 bridge users when using a very short voting interval on a testing
5658 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5660 - Enforce multiplicity rules when parsing annotations. Bugfix on
5661 0.2.0.8-alpha. Found by piebeer.
5662 - Allow handshaking OR connections to take a full KeepalivePeriod
5663 seconds to handshake. Previously, we would close them after
5664 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5665 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5667 - When building with --enable-gcc-warnings on OpenBSD, disable
5668 warnings in system headers. This makes --enable-gcc-warnings
5669 pass on OpenBSD 4.8.
5672 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5673 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5674 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5675 Servers can start sending this code when enough clients recognize
5676 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5677 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5678 Patch from mingw-san.
5681 - Remove the old debian/ directory from the main Tor distribution.
5682 The official Tor-for-debian git repository lives at the URL
5683 https://git.torproject.org/debian/tor.git
5684 - Stop shipping the old doc/website/ directory in the tarball. We
5685 changed the website format in late 2010, and what we shipped in
5686 0.2.1.26 really wasn't that useful anyway.
5689 Changes in version 0.2.2.19-alpha - 2010-11-22
5690 Yet another OpenSSL security patch broke its compatibility with Tor:
5691 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5694 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5695 No longer set the tlsext_host_name extension on server SSL objects;
5696 but continue to set it on client SSL objects. Our goal in setting
5697 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5698 bugfix on 0.2.1.1-alpha.
5701 - Try harder not to exceed the maximum length of 50 KB when writing
5702 statistics to extra-info descriptors. This bug was triggered by very
5703 fast relays reporting exit-port, entry, and dirreq statistics.
5704 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5705 - Publish a router descriptor even if generating an extra-info
5706 descriptor fails. Previously we would not publish a router
5707 descriptor without an extra-info descriptor; this can cause fast
5708 exit relays collecting exit-port statistics to drop from the
5709 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5712 Changes in version 0.2.2.18-alpha - 2010-11-16
5713 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5714 us lately, makes unpublished bridge relays able to detect their IP
5715 address, and fixes a wide variety of other bugs to get us much closer
5716 to a stable release.
5719 - Do even more to reject (and not just ignore) annotations on
5720 router descriptors received anywhere but from the cache. Previously
5721 we would ignore such annotations at first, but cache them to disk
5722 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5723 - Do not log messages to the controller while shrinking buffer
5724 freelists. Doing so would sometimes make the controller connection
5725 try to allocate a buffer chunk, which would mess up the internals
5726 of the freelist and cause an assertion failure. Fixes bug 1125;
5727 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5728 - Learn our external IP address when we're a relay or bridge, even if
5729 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5730 where we introduced bridge relays that don't need to publish to
5731 be useful. Fixes bug 2050.
5732 - Maintain separate TLS contexts and certificates for incoming and
5733 outgoing connections in bridge relays. Previously we would use the
5734 same TLS contexts and certs for incoming and outgoing connections.
5735 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5736 - Maintain separate identity keys for incoming and outgoing TLS
5737 contexts in bridge relays. Previously we would use the same
5738 identity keys for incoming and outgoing TLS contexts. Bugfix on
5739 0.2.0.3-alpha; addresses the other half of bug 988.
5740 - Avoid an assertion failure when we as an authority receive a
5741 duplicate upload of a router descriptor that we already have,
5742 but which we previously considered an obsolete descriptor.
5743 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5744 - Avoid a crash bug triggered by looking at a dangling pointer while
5745 setting the network status consensus. Found by Robert Ransom.
5746 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5747 - Fix a logic error where servers that _didn't_ act as exits would
5748 try to keep their server lists more aggressively up to date than
5749 exits, when it was supposed to be the other way around. Bugfix
5752 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5753 - When we're trying to guess whether we know our IP address as
5754 a relay, we would log various ways that we failed to guess
5755 our address, but never log that we ended up guessing it
5756 successfully. Now add a log line to help confused and anxious
5757 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5758 - Bring the logic that gathers routerinfos and assesses the
5759 acceptability of circuits into line. This prevents a Tor OP from
5760 getting locked in a cycle of choosing its local OR as an exit for a
5761 path (due to a .exit request) and then rejecting the circuit because
5762 its OR is not listed yet. It also prevents Tor clients from using an
5763 OR running in the same instance as an exit (due to a .exit request)
5764 if the OR does not meet the same requirements expected of an OR
5765 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5766 - Correctly describe errors that occur when generating a TLS object.
5767 Previously we would attribute them to a failure while generating a
5768 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5770 - Enforce multiplicity rules when parsing annotations. Bugfix on
5771 0.2.0.8-alpha. Found by piebeer.
5772 - Fix warnings that newer versions of autoconf produced during
5773 ./autogen.sh. These warnings appear to be harmless in our case,
5774 but they were extremely verbose. Fixes bug 2020.
5776 o Minor bugfixes (on Tor 0.2.2.x):
5777 - Enable protection of small arrays whenever we build with gcc
5778 hardening features, not only when also building with warnings
5779 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5782 - Make hidden services work better in private Tor networks by not
5783 requiring any uptime to join the hidden service descriptor
5784 DHT. Implements ticket 2088.
5785 - Rate-limit the "your application is giving Tor only an IP address"
5786 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
5787 - When AllowSingleHopExits is set, print a warning to explain to the
5788 relay operator why most clients are avoiding her relay.
5789 - Update to the November 1 2010 Maxmind GeoLite Country database.
5791 o Code simplifications and refactoring:
5792 - When we fixed bug 1038 we had to put in a restriction not to send
5793 RELAY_EARLY cells on rend circuits. This was necessary as long
5794 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
5795 active. Now remove this obsolete check. Resolves bug 2081.
5796 - Some options used different conventions for uppercasing of acronyms
5797 when comparing manpage and source. Fix those in favor of the
5798 manpage, as it makes sense to capitalize acronyms.
5799 - Remove the torrc.complete file. It hasn't been kept up to date
5800 and users will have better luck checking out the manpage.
5801 - Remove the obsolete "NoPublish" option; it has been flagged
5802 as obsolete and has produced a warning since 0.1.1.18-rc.
5803 - Remove everything related to building the expert bundle for OS X.
5804 It has confused many users, doesn't work right on OS X 10.6,
5805 and is hard to get rid of once installed. Resolves bug 1274.
5808 Changes in version 0.2.2.17-alpha - 2010-09-30
5809 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
5810 to use one-hop circuits (which can put the exit relays at higher risk,
5811 plus unbalance the network); fixes a big bug in bandwidth accounting
5812 for relays that want to limit their monthly bandwidth use; fixes a
5813 big pile of bugs in how clients tolerate temporary network failure;
5814 and makes our adaptive circuit build timeout feature (which improves
5815 client performance if your network is fast while not breaking things
5816 if your network is slow) better handle bad networks.
5819 - Exit relays now try harder to block exit attempts from unknown
5820 relays, to make it harder for people to use them as one-hop proxies
5821 a la tortunnel. Controlled by the refuseunknownexits consensus
5822 parameter (currently enabled), or you can override it on your
5823 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
5825 o Major bugfixes (0.2.1.x and earlier):
5826 - Fix a bug in bandwidth accounting that could make us use twice
5827 the intended bandwidth when our interval start changes due to
5828 daylight saving time. Now we tolerate skew in stored vs computed
5829 interval starts: if the start of the period changes by no more than
5830 50% of the period's duration, we remember bytes that we transferred
5831 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
5832 - Always search the Windows system directory for system DLLs, and
5833 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
5834 - When you're using bridges and your network goes away and your
5835 bridges get marked as down, recover when you attempt a new socks
5836 connection (if the network is back), rather than waiting up to an
5837 hour to try fetching new descriptors for your bridges. Bugfix on
5838 0.2.0.3-alpha; fixes bug 1981.
5840 o Major bugfixes (on 0.2.2.x):
5841 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
5843 - Fix a segfault that could happen when operating a bridge relay with
5844 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
5845 - The consensus bandwidth-weights (used by clients to choose fast
5846 relays) entered an unexpected edge case in September where
5847 Exits were much scarcer than Guards, resulting in bad weight
5848 recommendations. Now we compute them using new constraints that
5849 should succeed in all cases. Also alter directory authorities to
5850 not include the bandwidth-weights line if they fail to produce
5851 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
5852 - When weighting bridges during path selection, we used to trust
5853 the bandwidths they provided in their descriptor, only capping them
5854 at 10MB/s. This turned out to be problematic for two reasons:
5855 Bridges could claim to handle a lot more traffic then they
5856 actually would, thus making more clients pick them and have a
5857 pretty effective DoS attack. The other issue is that new bridges
5858 that might not have a good estimate for their bw capacity yet
5859 would not get used at all unless no other bridges are available
5860 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
5862 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
5863 - Ignore cannibalized circuits when recording circuit build times.
5864 This should provide for a minor performance improvement for hidden
5865 service users using 0.2.2.14-alpha, and should remove two spurious
5866 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
5867 - Simplify the logic that causes us to decide if the network is
5868 unavailable for purposes of recording circuit build times. If we
5869 receive no cells whatsoever for the entire duration of a circuit's
5870 full measured lifetime, the network is probably down. Also ignore
5871 one-hop directory fetching circuit timeouts when calculating our
5872 circuit build times. These changes should hopefully reduce the
5873 cases where we see ridiculous circuit build timeouts for people
5874 with spotty wireless connections. Fixes part of bug 1772; bugfix
5876 - Prevent the circuit build timeout from becoming larger than
5877 the maximum build time we have ever seen. Also, prevent the time
5878 period for measurement circuits from becoming larger than twice that
5879 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
5882 - When we run out of directory information such that we can't build
5883 circuits, but then get enough that we can build circuits, log when
5884 we actually construct a circuit, so the user has a better chance of
5885 knowing what's going on. Fixes bug 1362.
5886 - Be more generous with how much bandwidth we'd use up (with
5887 accounting enabled) before entering "soft hibernation". Previously,
5888 we'd refuse new connections and circuits once we'd used up 95% of
5889 our allotment. Now, we use up 95% of our allotment, AND make sure
5890 that we have no more than 500MB (or 3 hours of expected traffic,
5891 whichever is lower) remaining before we enter soft hibernation.
5892 - If we've configured EntryNodes and our network goes away and/or all
5893 our entrynodes get marked down, optimistically retry them all when
5894 a new socks application request appears. Fixes bug 1882.
5895 - Add some more defensive programming for architectures that can't
5896 handle unaligned integer accesses. We don't know of any actual bugs
5897 right now, but that's the best time to fix them. Fixes bug 1943.
5898 - Support line continuations in the torrc config file. If a line
5899 ends with a single backslash character, the newline is ignored, and
5900 the configuration value is treated as continuing on the next line.
5903 o Minor bugfixes (on 0.2.1.x and earlier):
5904 - For bandwidth accounting, calculate our expected bandwidth rate
5905 based on the time during which we were active and not in
5906 soft-hibernation during the last interval. Previously, we were
5907 also considering the time spent in soft-hibernation. If this
5908 was a long time, we would wind up underestimating our bandwidth
5909 by a lot, and skewing our wakeup time towards the start of the
5910 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
5912 o Minor bugfixes (on 0.2.2.x):
5913 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
5914 which were disabled by the circuit build timeout changes in
5915 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
5916 - Make sure we don't warn about missing bandwidth weights when
5917 choosing bridges or other relays not in the consensus. Bugfix on
5918 0.2.2.10-alpha; fixes bug 1805.
5919 - In our logs, do not double-report signatures from unrecognized
5920 authorities both as "from unknown authority" and "not
5921 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
5924 Changes in version 0.2.2.16-alpha - 2010-09-17
5925 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
5926 evident at exit relays), and also continues to resolve all the little
5927 bugs that have been filling up trac lately.
5929 o Major bugfixes (stream-level fairness):
5930 - When receiving a circuit-level SENDME for a blocked circuit, try
5931 to package cells fairly from all the streams that had previously
5932 been blocked on that circuit. Previously, we had started with the
5933 oldest stream, and allowed each stream to potentially exhaust
5934 the circuit's package window. This gave older streams on any
5935 given circuit priority over newer ones. Fixes bug 1937. Detected
5936 originally by Camilo Viecco. This bug was introduced before the
5937 first Tor release, in svn commit r152: it is the new winner of
5938 the longest-lived bug prize.
5939 - When the exit relay got a circuit-level sendme cell, it started
5940 reading on the exit streams, even if had 500 cells queued in the
5941 circuit queue already, so the circuit queue just grew and grew in
5942 some cases. We fix this by not re-enabling reading on receipt of a
5943 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
5944 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
5946 - Newly created streams were allowed to read cells onto circuits,
5947 even if the circuit's cell queue was blocked and waiting to drain.
5948 This created potential unfairness, as older streams would be
5949 blocked, but newer streams would gladly fill the queue completely.
5950 We add code to detect this situation and prevent any stream from
5951 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
5955 - Update to the September 1 2010 Maxmind GeoLite Country database.
5956 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
5957 not. This would lead to a cookie that is still not group readable.
5958 Closes bug 1843. Suggested by katmagic.
5959 - When logging a rate-limited warning, we now mention how many messages
5960 got suppressed since the last warning.
5961 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
5962 do individual connection-level rate limiting of clients. The torrc
5963 config options with the same names trump the consensus params, if
5964 both are present. Replaces the old "bwconnrate" and "bwconnburst"
5965 consensus params which were broken from 0.2.2.7-alpha through
5966 0.2.2.14-alpha. Closes bug 1947.
5967 - When a router changes IP address or port, authorities now launch
5968 a new reachability test for it. Implements ticket 1899.
5969 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
5970 2 no signature, 4 required" messages about consensus signatures
5971 easier to read, and make sure they get logged at the same severity
5972 as the messages explaining which keys are which. Fixes bug 1290.
5973 - Don't warn when we have a consensus that we can't verify because
5974 of missing certificates, unless those certificates are ones
5975 that we have been trying and failing to download. Fixes bug 1145.
5976 - If you configure your bridge with a known identity fingerprint,
5977 and the bridge authority is unreachable (as it is in at least
5978 one country now), fall back to directly requesting the descriptor
5979 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
5981 - When building with --enable-gcc-warnings on OpenBSD, disable
5982 warnings in system headers. This makes --enable-gcc-warnings
5983 pass on OpenBSD 4.8.
5985 o Minor bugfixes (on 0.2.1.x and earlier):
5986 - Authorities will now attempt to download consensuses if their
5987 own efforts to make a live consensus have failed. This change
5988 means authorities that restart will fetch a valid consensus, and
5989 it means authorities that didn't agree with the current consensus
5990 will still fetch and serve it if it has enough signatures. Bugfix
5991 on 0.2.0.9-alpha; fixes bug 1300.
5992 - Ensure DNS requests launched by "RESOLVE" commands from the
5993 controller respect the __LeaveStreamsUnattached setconf options. The
5994 same goes for requests launched via DNSPort or transparent
5995 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
5996 - Allow handshaking OR connections to take a full KeepalivePeriod
5997 seconds to handshake. Previously, we would close them after
5998 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5999 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6001 - Rate-limit "Failed to hand off onionskin" warnings.
6002 - Never relay a cell for a circuit we have already destroyed.
6003 Between marking a circuit as closeable and finally closing it,
6004 it may have been possible for a few queued cells to get relayed,
6005 even though they would have been immediately dropped by the next
6006 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6007 - Never queue a cell for a circuit that's already been marked
6009 - Never vote for a server as "Running" if we have a descriptor for
6010 it claiming to be hibernating, and that descriptor was published
6011 more recently than our last contact with the server. Bugfix on
6012 0.2.0.3-alpha; fixes bug 911.
6013 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6016 o Minor bugfixes (on 0.2.2.x):
6017 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6018 down if a directory fetch fails and you've configured either
6019 bridges or EntryNodes. The intent was to mark the relay as down
6020 _unless_ you're using bridges or EntryNodes, since if you are
6021 then you could quickly run out of entry points.
6022 - Fix the Windows directory-listing code. A bug introduced in
6023 0.2.2.14-alpha could make Windows directory servers forget to load
6024 some of their cached v2 networkstatus files.
6025 - Really allow clients to use relays as bridges. Fixes bug 1776;
6026 bugfix on 0.2.2.15-alpha.
6027 - Demote a warn to info that happens when the CellStatistics option
6028 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6029 Reported by Moritz Bartl.
6030 - On Windows, build correctly either with or without Unicode support.
6031 This is necessary so that Tor can support fringe platforms like
6032 Windows 98 (which has no Unicode), or Windows CE (which has no
6033 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6036 - Add a unit test for cross-platform directory-listing code.
6039 Changes in version 0.2.2.15-alpha - 2010-08-18
6040 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6041 fixes a variety of other bugs that were preventing performance
6042 experiments from moving forward, fixes several bothersome memory leaks,
6043 and generally closes a lot of smaller bugs that have been filling up
6047 - Stop assigning the HSDir flag to relays that disable their
6048 DirPort (and thus will refuse to answer directory requests). This
6049 fix should dramatically improve the reachability of hidden services:
6050 hidden services and hidden service clients pick six HSDir relays
6051 to store and retrieve the hidden service descriptor, and currently
6052 about half of the HSDir relays will refuse to work. Bugfix on
6053 0.2.0.10-alpha; fixes part of bug 1693.
6054 - The PerConnBWRate and Burst config options, along with the
6055 bwconnrate and bwconnburst consensus params, initialized each conn's
6056 token bucket values only when the connection is established. Now we
6057 update them if the config options change, and update them every time
6058 we get a new consensus. Otherwise we can encounter an ugly edge
6059 case where we initialize an OR conn to client-level bandwidth,
6060 but then later the relay joins the consensus and we leave it
6061 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6062 - Fix a regression that caused Tor to rebind its ports if it receives
6063 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6066 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6067 should give us approximately 40-50% more Guard-flagged nodes,
6068 improving the anonymity the Tor network can provide and also
6069 decreasing the dropoff in throughput that relays experience when
6070 they first get the Guard flag.
6071 - Allow enabling or disabling the *Statistics config options while
6075 - Update to the August 1 2010 Maxmind GeoLite Country database.
6076 - Have the controller interface give a more useful message than
6077 "Internal Error" in response to failed GETINFO requests.
6078 - Warn when the same option is provided more than once in a torrc
6079 file, on the command line, or in a single SETCONF statement, and
6080 the option is one that only accepts a single line. Closes bug 1384.
6081 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6082 Patch from mingw-san.
6083 - Add support for the country code "{??}" in torrc options like
6084 ExcludeNodes, to indicate all routers of unknown country. Closes
6086 - Relays report the number of bytes spent on answering directory
6087 requests in extra-info descriptors similar to {read,write}-history.
6088 Implements enhancement 1790.
6090 o Minor bugfixes (on 0.2.1.x and earlier):
6091 - Complain if PublishServerDescriptor is given multiple arguments that
6092 include 0 or 1. This configuration will be rejected in the future.
6093 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6094 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6095 Bugfix on 0.2.0.13-alpha; closes bug 928.
6096 - Change "Application request when we're believed to be offline."
6097 notice to "Application request when we haven't used client
6098 functionality lately.", to clarify that it's not an error. Bugfix
6099 on 0.0.9.3; fixes bug 1222.
6100 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6101 would return "551 Internal error" rather than "552 Unrecognized key
6102 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6103 - Users can't configure a regular relay to be their bridge. It didn't
6104 work because when Tor fetched the bridge descriptor, it found
6105 that it already had it, and didn't realize that the purpose of the
6106 descriptor had changed. Now we replace routers with a purpose other
6107 than bridge with bridge descriptors when fetching them. Bugfix on
6108 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6109 refetch the descriptor with router purpose 'general', disabling
6111 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6112 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6113 on 0.2.0.10-alpha; fixes bug 1808.
6114 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6115 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6116 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6117 Servers can start sending this code when enough clients recognize
6118 it. Also update the spec to reflect this new reason. Bugfix on
6119 0.1.0.1-rc; fixes part of bug 1793.
6120 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6121 when we switch from being a public relay to a bridge. Otherwise
6122 there will still be clients that see the relay in their consensus,
6123 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6125 - Instead of giving an assertion failure on an internal mismatch
6126 on estimated freelist size, just log a BUG warning and try later.
6127 Mitigates but does not fix bug 1125.
6128 - Fix an assertion failure that could occur in caches or bridge users
6129 when using a very short voting interval on a testing network.
6130 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6132 o Minor bugfixes (on 0.2.2.x):
6133 - Alter directory authorities to always consider Exit-flagged nodes
6134 as potential Guard nodes in their votes. The actual decision to
6135 use Exits as Guards is done in the consensus bandwidth weights.
6136 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6137 - When the controller is reporting the purpose of circuits that
6138 didn't finish building before the circuit build timeout, it was
6139 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6140 - Our libevent version parsing code couldn't handle versions like
6141 1.4.14b-stable and incorrectly warned the user about using an
6142 old and broken version of libevent. Treat 1.4.14b-stable like
6143 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6145 - Don't use substitution references like $(VAR:MOD) when
6146 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6147 '$(:x)' to 'x' rather than the empty string. This bites us in
6148 doc/ when configured with --disable-asciidoc. Bugfix on
6149 0.2.2.9-alpha; fixes bug 1773.
6150 - Remove a spurious hidden service server-side log notice about
6151 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6153 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6155 - Correctly report written bytes on linked connections. Found while
6156 implementing 1790. Bugfix on 0.2.2.4-alpha.
6157 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6158 one in dirvote_add_signatures_to_pending_consensus(), and one every
6159 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6160 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6162 o Code simplifications and refactoring:
6163 - Take a first step towards making or.h smaller by splitting out
6164 function definitions for all source files in src/or/. Leave
6165 structures and defines in or.h for now.
6166 - Remove a bunch of unused function declarations as well as a block of
6167 #if 0'd code from the unit tests. Closes bug 1824.
6168 - New unit tests for exit-port history statistics; refactored exit
6169 statistics code to be more easily tested.
6170 - Remove the old debian/ directory from the main Tor distribution.
6171 The official Tor-for-debian git repository lives at the URL
6172 https://git.torproject.org/debian/tor.git
6175 Changes in version 0.2.2.14-alpha - 2010-07-12
6176 Tor 0.2.2.14-alpha greatly improves client-side handling of
6177 circuit build timeouts, which are used to estimate speed and improve
6178 performance. We also move to a much better GeoIP database, port Tor to
6179 Windows CE, introduce new compile flags that improve code security,
6180 add an eighth v3 directory authority, and address a lot of more
6184 - Tor directory authorities no longer crash when started with a
6185 cached-microdesc-consensus file in their data directory. Bugfix
6186 on 0.2.2.6-alpha; fixes bug 1532.
6187 - Treat an unset $HOME like an empty $HOME rather than triggering an
6188 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6189 - Ignore negative and large circuit build timeout values that can
6190 happen during a suspend or hibernate. These values caused various
6191 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6192 - Alter calculation of Pareto distribution parameter 'Xm' for
6193 Circuit Build Timeout learning to use the weighted average of the
6194 top N=3 modes (because we have three entry guards). Considering
6195 multiple modes should improve the timeout calculation in some cases,
6196 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6198 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6199 right censored distribution model. This approach improves over the
6200 synthetic timeout generation approach that was producing insanely
6201 high timeout values. Now we calculate build timeouts using truncated
6202 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6203 - Do not close circuits that are under construction when they reach
6204 the circuit build timeout. Instead, leave them building (but do not
6205 use them) for up until the time corresponding to the 95th percentile
6206 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6207 to provide better data for the new Pareto model. This percentile
6208 can be controlled by the consensus.
6211 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6212 June 2009 ip-to-country GeoIP db) for our statistics that count
6213 how many users relays are seeing from each country. Now we have
6214 more accurate data for many African countries.
6215 - Port Tor to build and run correctly on Windows CE systems, using
6216 the wcecompat library. Contributed by Valerio Lupi.
6217 - New "--enable-gcc-hardening" ./configure flag (off by default)
6218 to turn on gcc compile time hardening options. It ensures
6219 that signed ints have defined behavior (-fwrapv), enables
6220 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6221 with canaries (-fstack-protector-all), turns on ASLR protection if
6222 supported by the kernel (-fPIE, -pie), and adds additional security
6223 related warnings. Verified to work on Mac OS X and Debian Lenny.
6224 - New "--enable-linker-hardening" ./configure flag (off by default)
6225 to turn on ELF specific hardening features (relro, now). This does
6226 not work with Mac OS X or any other non-ELF binary format.
6228 o New directory authorities:
6229 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6233 - New config option "WarnUnsafeSocks 0" disables the warning that
6234 occurs whenever Tor receives a socks handshake using a version of
6235 the socks protocol that can only provide an IP address (rather
6236 than a hostname). Setups that do DNS locally over Tor are fine,
6237 and we shouldn't spam the logs in that case.
6238 - Convert the HACKING file to asciidoc, and add a few new sections
6239 to it, explaining how we use Git, how we make changelogs, and
6240 what should go in a patch.
6241 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6242 event, to give information on the current rate of circuit timeouts
6243 over our stored history.
6244 - Add ability to disable circuit build time learning via consensus
6245 parameter and via a LearnCircuitBuildTimeout config option. Also
6246 automatically disable circuit build time calculation if we are
6247 either a AuthoritativeDirectory, or if we fail to write our state
6248 file. Fixes bug 1296.
6249 - More gracefully handle corrupt state files, removing asserts
6250 in favor of saving a backup and resetting state.
6251 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6255 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6257 - When a2x fails, mention that the user could disable manpages instead
6258 of trying to fix their asciidoc installation.
6259 - Where available, use Libevent 2.0's periodic timers so that our
6260 once-per-second cleanup code gets called even more closely to
6261 once per second than it would otherwise. Fixes bug 943.
6262 - If you run a bridge that listens on multiple IP addresses, and
6263 some user configures a bridge address that uses a different IP
6264 address than your bridge writes in its router descriptor, and the
6265 user doesn't specify an identity key, their Tor would discard the
6266 descriptor because "it isn't one of our configured bridges", and
6267 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6268 Bugfix on 0.2.0.3-alpha.
6269 - If OpenSSL fails to make a duplicate of a private or public key, log
6270 an error message and try to exit cleanly. May help with debugging
6271 if bug 1209 ever remanifests.
6272 - Save a couple bytes in memory allocation every time we escape
6273 certain characters in a string. Patch from Florian Zumbiehl.
6274 - Make it explicit that we don't cannibalize one-hop circuits. This
6275 happens in the wild, but doesn't turn out to be a problem because
6276 we fortunately don't use those circuits. Many thanks to outofwords
6277 for the initial analysis and to swissknife who confirmed that
6278 two-hop circuits are actually created.
6279 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6280 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6281 - Eliminate a case where a circuit build time warning was displayed
6282 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6285 Changes in version 0.2.1.26 - 2010-05-02
6286 Tor 0.2.1.26 addresses the recent connection and memory overload
6287 problems we've been seeing on relays, especially relays with their
6288 DirPort open. If your relay has been crashing, or you turned it off
6289 because it used too many resources, give this release a try.
6291 This release also fixes yet another instance of broken OpenSSL libraries
6292 that was causing some relays to drop out of the consensus.
6295 - Teach relays to defend themselves from connection overload. Relays
6296 now close idle circuits early if it looks like they were intended
6297 for directory fetches. Relays are also more aggressive about closing
6298 TLS connections that have no circuits on them. Such circuits are
6299 unlikely to be re-used, and tens of thousands of them were piling
6300 up at the fast relays, causing the relays to run out of sockets
6301 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6302 their directory fetches over TLS).
6303 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6304 that claim to be earlier than 0.9.8m, but which have in reality
6305 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6306 behavior. Possible fix for some cases of bug 1346.
6307 - Directory mirrors were fetching relay descriptors only from v2
6308 directory authorities, rather than v3 authorities like they should.
6309 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6310 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6313 - Finally get rid of the deprecated and now harmful notion of "clique
6314 mode", where directory authorities maintain TLS connections to
6318 - In the util/threads test, no longer free the test_mutex before all
6319 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6320 - The master thread could starve the worker threads quite badly on
6321 certain systems, causing them to run only partially in the allowed
6322 window. This resulted in test failures. Now the master thread sleeps
6323 occasionally for a few microseconds while the two worker-threads
6324 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6327 Changes in version 0.2.2.13-alpha - 2010-04-24
6328 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6329 problems we've been seeing on relays, especially relays with their
6330 DirPort open. If your relay has been crashing, or you turned it off
6331 because it used too many resources, give this release a try.
6334 - Teach relays to defend themselves from connection overload. Relays
6335 now close idle circuits early if it looks like they were intended
6336 for directory fetches. Relays are also more aggressive about closing
6337 TLS connections that have no circuits on them. Such circuits are
6338 unlikely to be re-used, and tens of thousands of them were piling
6339 up at the fast relays, causing the relays to run out of sockets
6340 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6341 their directory fetches over TLS).
6344 - Finally get rid of the deprecated and now harmful notion of "clique
6345 mode", where directory authorities maintain TLS connections to
6347 - Directory authorities now do an immediate reachability check as soon
6348 as they hear about a new relay. This change should slightly reduce
6349 the time between setting up a relay and getting listed as running
6350 in the consensus. It should also improve the time between setting
6351 up a bridge and seeing use by bridge users.
6352 - Directory authorities no longer launch a TLS connection to every
6353 relay as they startup. Now that we have 2k+ descriptors cached,
6354 the resulting network hiccup is becoming a burden. Besides,
6355 authorities already avoid voting about Running for the first half
6356 hour of their uptime.
6359 Changes in version 0.2.2.12-alpha - 2010-04-20
6360 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6361 handle and vote on descriptors. It was causing relays to drop out of
6365 - Many relays have been falling out of the consensus lately because
6366 not enough authorities know about their descriptor for them to get
6367 a majority of votes. When we deprecated the v2 directory protocol,
6368 we got rid of the only way that v3 authorities can hear from each
6369 other about other descriptors. Now authorities examine every v3
6370 vote for new descriptors, and fetch them from that authority. Bugfix
6372 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6373 and a warning in or.h related to bandwidth_weight_rule_t that
6374 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6376 - Fix a segfault on relays when DirReqStatistics is enabled
6377 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6381 - Demote a confusing TLS warning that relay operators might get when
6382 someone tries to talk to their OrPort. It is neither the operator's
6383 fault nor can they do anything about it. Fixes bug 1364; bugfix
6387 Changes in version 0.2.2.11-alpha - 2010-04-15
6388 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6389 libraries that was causing some relays to drop out of the consensus.
6392 - Directory mirrors were fetching relay descriptors only from v2
6393 directory authorities, rather than v3 authorities like they should.
6394 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6395 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6396 - Fix a parsing error that made every possible value of
6397 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6398 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6399 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6400 about the option without breaking older ones.
6401 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6402 that claim to be earlier than 0.9.8m, but which have in reality
6403 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6404 behavior. Possible fix for some cases of bug 1346.
6407 - Experiment with a more aggressive approach to preventing clients
6408 from making one-hop exit streams. Exit relays who want to try it
6409 out can set "RefuseUnknownExits 1" in their torrc, and then look
6410 for "Attempt by %s to open a stream" log messages. Let us know
6412 - Add support for statically linking zlib by specifying
6413 --enable-static-zlib, to go with our support for statically linking
6414 openssl and libevent. Resolves bug 1358.
6417 - Fix a segfault that happens whenever a Tor client that is using
6418 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6420 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6421 out the first line. Fixes bug 1295.
6422 - When building the manpage from a tarball, we required asciidoc, but
6423 the asciidoc -> roff/html conversion was already done for the
6424 tarball. Make 'make' complain only when we need asciidoc (either
6425 because we're compiling directly from git, or because we altered
6426 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6427 - When none of the directory authorities vote on any params, Tor
6428 segfaulted when trying to make the consensus from the votes. We
6429 didn't trigger the bug in practice, because authorities do include
6430 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6433 - In the util/threads test, no longer free the test_mutex before all
6434 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6435 - The master thread could starve the worker threads quite badly on
6436 certain systems, causing them to run only partially in the allowed
6437 window. This resulted in test failures. Now the master thread sleeps
6438 occasionally for a few microseconds while the two worker-threads
6439 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6442 Changes in version 0.2.2.10-alpha - 2010-03-07
6443 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6444 could prevent relays from guessing their IP address correctly. It also
6445 starts the groundwork for another client-side performance boost, since
6446 currently we're not making efficient use of relays that have both the
6447 Guard flag and the Exit flag.
6450 - Fix a regression from our patch for bug 1244 that caused relays
6451 to guess their IP address incorrectly if they didn't set Address
6452 in their torrc and/or their address fails to resolve. Bugfix on
6453 0.2.2.9-alpha; fixes bug 1269.
6455 o Major features (performance):
6456 - Directory authorities now compute consensus weightings that instruct
6457 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6458 and no flag. Clients that use these weightings will distribute
6459 network load more evenly across these different relay types. The
6460 weightings are in the consensus so we can change them globally in
6461 the future. Extra thanks to "outofwords" for finding some nasty
6462 security bugs in the first implementation of this feature.
6464 o Minor features (performance):
6465 - Always perform router selections using weighted relay bandwidth,
6466 even if we don't need a high capacity circuit at the time. Non-fast
6467 circuits now only differ from fast ones in that they can use relays
6468 not marked with the Fast flag. This "feature" could turn out to
6469 be a horrible bug; we should investigate more before it goes into
6473 - Allow disabling building of the manpages. Skipping the manpage
6474 speeds up the build considerably.
6476 o Minor bugfixes (on 0.2.2.x):
6477 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6478 Bugfix on 0.2.2.9-alpha.
6479 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6480 config option. Bugfix on 0.2.2.7-alpha.
6481 - Ship the asciidoc-helper file in the tarball, so that people can
6482 build from source if they want to, and touching the .1.txt files
6483 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6485 o Minor bugfixes (on 0.2.1.x or earlier):
6486 - Fix a dereference-then-NULL-check sequence when publishing
6487 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6489 - Fix another dereference-then-NULL-check sequence. Bugfix on
6490 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6491 - Make sure we treat potentially not NUL-terminated strings correctly.
6492 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6494 o Code simplifications and refactoring:
6495 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6496 compliant. Based on a patch from Christian Kujau.
6497 - Don't use sed in asciidoc-helper anymore.
6498 - Make the build process fail if asciidoc cannot be found and
6499 building with asciidoc isn't disabled.
6502 Changes in version 0.2.2.9-alpha - 2010-02-22
6503 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6504 location of a directory authority, and cleans up a bunch of small bugs.
6506 o Directory authority changes:
6507 - Change IP address for dannenberg (v3 directory authority), and
6508 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6509 service directory authority) from the list.
6512 - Make Tor work again on the latest OS X: when deciding whether to
6513 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6514 version at run-time, not compile time. We need to do this because
6515 Apple doesn't update its dev-tools headers when it updates its
6516 libraries in a security patch.
6517 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6518 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6519 a memory leak when requesting a hidden service descriptor we've
6520 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6522 - Authorities could be tricked into giving out the Exit flag to relays
6523 that didn't allow exiting to any ports. This bug could screw
6524 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6525 1238. Bug discovered by Martin Kowalczyk.
6526 - When freeing a session key, zero it out completely. We only zeroed
6527 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6528 patched by ekir. Fixes bug 1254.
6531 - Fix static compilation by listing the openssl libraries in the right
6532 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6533 - Resume handling .exit hostnames in a special way: originally we
6534 stripped the .exit part and used the requested exit relay. In
6535 0.2.2.1-alpha we stopped treating them in any special way, meaning
6536 if you use a .exit address then Tor will pass it on to the exit
6537 relay. Now we reject the .exit stream outright, since that behavior
6538 might be more expected by the user. Found and diagnosed by Scott
6539 Bennett and Downie on or-talk.
6540 - Don't spam the controller with events when we have no file
6541 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6542 for log messages was already solved from bug 748.)
6543 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6545 - Make the DNSPort option work with libevent 2.x. Don't alter the
6546 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6547 - Emit a GUARD DROPPED controller event for a case we missed.
6548 - Make more fields in the controller protocol case-insensitive, since
6549 control-spec.txt said they were.
6550 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6551 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6552 - Fix a spec conformance issue: the network-status-version token
6553 must be the first token in a v3 consensus or vote. Discovered by
6554 parakeep. Bugfix on 0.2.0.3-alpha.
6556 o Code simplifications and refactoring:
6557 - Generate our manpage and HTML documentation using Asciidoc. This
6558 change should make it easier to maintain the documentation, and
6560 - Remove the --enable-iphone option. According to reports from Marco
6561 Bonetti, Tor builds fine without any special tweaking on recent
6562 iPhone SDK versions.
6563 - Removed some unnecessary files from the source distribution. The
6564 AUTHORS file has now been merged into the people page on the
6565 website. The roadmaps and design doc can now be found in the
6566 projects directory in svn.
6567 - Enabled various circuit build timeout constants to be controlled
6568 by consensus parameters. Also set better defaults for these
6569 parameters based on experimentation on broadband and simulated
6573 - The 'EXTENDCIRCUIT' control port command can now be used with
6574 a circ id of 0 and no path. This feature will cause Tor to build
6575 a new 'fast' general purpose circuit using its own path selection
6577 - Added a BUILDTIMEOUT_SET controller event to describe changes
6578 to the circuit build timeout.
6579 - Future-proof the controller protocol a bit by ignoring keyword
6580 arguments we do not recognize.
6581 - Expand homedirs passed to tor-checkkey. This should silence a
6582 coverity complaint about passing a user-supplied string into
6583 open() without checking it.
6586 Changes in version 0.2.1.25 - 2010-03-16
6587 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6588 prevent relays from guessing their IP address correctly. It also fixes
6589 several minor potential security bugs.
6592 - Fix a regression from our patch for bug 1244 that caused relays
6593 to guess their IP address incorrectly if they didn't set Address
6594 in their torrc and/or their address fails to resolve. Bugfix on
6595 0.2.1.23; fixes bug 1269.
6596 - When freeing a session key, zero it out completely. We only zeroed
6597 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6598 patched by ekir. Fixes bug 1254.
6601 - Fix a dereference-then-NULL-check sequence when publishing
6602 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6604 - Fix another dereference-then-NULL-check sequence. Bugfix on
6605 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6606 - Make sure we treat potentially not NUL-terminated strings correctly.
6607 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6611 Changes in version 0.2.1.24 - 2010-02-21
6612 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6616 - Work correctly out-of-the-box with even more vendor-patched versions
6617 of OpenSSL. In particular, make it so Debian and OS X don't need
6618 customized patches to run/build.
6621 Changes in version 0.2.1.23 - 2010-02-13
6622 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6623 again on the latest OS X, and updates the location of a directory
6626 o Major bugfixes (performance):
6627 - We were selecting our guards uniformly at random, and then weighting
6628 which of our guards we'd use uniformly at random. This imbalance
6629 meant that Tor clients were severely limited on throughput (and
6630 probably latency too) by the first hop in their circuit. Now we
6631 select guards weighted by currently advertised bandwidth. We also
6632 automatically discard guards picked using the old algorithm. Fixes
6633 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6636 - Make Tor work again on the latest OS X: when deciding whether to
6637 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6638 version at run-time, not compile time. We need to do this because
6639 Apple doesn't update its dev-tools headers when it updates its
6640 libraries in a security patch.
6641 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6642 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6643 a memory leak when requesting a hidden service descriptor we've
6644 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6647 o Directory authority changes:
6648 - Change IP address for dannenberg (v3 directory authority), and
6649 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6650 service directory authority) from the list.
6653 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6654 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6657 - Avoid a mad rush at the beginning of each month when each client
6658 rotates half of its guards. Instead we spread the rotation out
6659 throughout the month, but we still avoid leaving a precise timestamp
6660 in the state file about when we first picked the guard. Improves
6661 over the behavior introduced in 0.1.2.17.
6664 Changes in version 0.2.2.8-alpha - 2010-01-26
6665 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6666 causing bridge relays to disappear. If you're running a bridge,
6670 - Fix a memory corruption bug on bridges that occured during the
6671 inclusion of stats data in extra-info descriptors. Also fix the
6672 interface for geoip_get_bridge_stats* to prevent similar bugs in
6673 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6674 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6677 - Ignore OutboundBindAddress when connecting to localhost.
6678 Connections to localhost need to come _from_ localhost, or else
6679 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6683 Changes in version 0.2.2.7-alpha - 2010-01-19
6684 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6685 as laying the groundwork for further relay-side performance fixes. It
6686 also starts cleaning up client behavior with respect to the EntryNodes,
6687 ExitNodes, and StrictNodes config options.
6689 This release also rotates two directory authority keys, due to a
6690 security breach of some of the Torproject servers.
6692 o Directory authority changes:
6693 - Rotate keys (both v3 identity and relay identity) for moria1
6696 o Major features (performance):
6697 - We were selecting our guards uniformly at random, and then weighting
6698 which of our guards we'd use uniformly at random. This imbalance
6699 meant that Tor clients were severely limited on throughput (and
6700 probably latency too) by the first hop in their circuit. Now we
6701 select guards weighted by currently advertised bandwidth. We also
6702 automatically discard guards picked using the old algorithm. Fixes
6703 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6704 - When choosing which cells to relay first, relays can now favor
6705 circuits that have been quiet recently, to provide lower latency
6706 for low-volume circuits. By default, relays enable or disable this
6707 feature based on a setting in the consensus. You can override
6708 this default by using the new "CircuitPriorityHalflife" config
6709 option. Design and code by Ian Goldberg, Can Tang, and Chris
6711 - Add separate per-conn write limiting to go with the per-conn read
6712 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6713 but never per-conn write limits.
6714 - New consensus params "bwconnrate" and "bwconnburst" to let us
6715 rate-limit client connections as they enter the network. It's
6716 controlled in the consensus so we can turn it on and off for
6717 experiments. It's starting out off. Based on proposal 163.
6719 o Major features (relay selection options):
6720 - Switch to a StrictNodes config option, rather than the previous
6721 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6722 "StrictExcludeNodes" option.
6723 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6724 change during a config reload, mark and discard all our origin
6725 circuits. This fix should address edge cases where we change the
6726 config options and but then choose a circuit that we created before
6728 - If EntryNodes or ExitNodes are set, be more willing to use an
6729 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6731 - Make EntryNodes config option much more aggressive even when
6732 StrictNodes is not set. Before it would prepend your requested
6733 entrynodes to your list of guard nodes, but feel free to use others
6734 after that. Now it chooses only from your EntryNodes if any of
6735 those are available, and only falls back to others if a) they're
6736 all down and b) StrictNodes is not set.
6737 - Now we refresh your entry guards from EntryNodes at each consensus
6738 fetch -- rather than just at startup and then they slowly rot as
6739 the network changes.
6742 - Stop bridge directory authorities from answering dbg-stability.txt
6743 directory queries, which would let people fetch a list of all
6744 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6747 - Log a notice when we get a new control connection. Now it's easier
6748 for security-conscious users to recognize when a local application
6749 is knocking on their controller door. Suggested by bug 1196.
6750 - New config option "CircuitStreamTimeout" to override our internal
6751 timeout schedule for how many seconds until we detach a stream from
6752 a circuit and try a new circuit. If your network is particularly
6753 slow, you might want to set this to a number like 60.
6754 - New controller command "getinfo config-text". It returns the
6755 contents that Tor would write if you send it a SAVECONF command,
6756 so the controller can write the file to disk itself.
6757 - New options for SafeLogging to allow scrubbing only log messages
6758 generated while acting as a relay.
6759 - Ship the bridges spec file in the tarball too.
6760 - Avoid a mad rush at the beginning of each month when each client
6761 rotates half of its guards. Instead we spread the rotation out
6762 throughout the month, but we still avoid leaving a precise timestamp
6763 in the state file about when we first picked the guard. Improves
6764 over the behavior introduced in 0.1.2.17.
6766 o Minor bugfixes (compiling):
6767 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6768 hides it. Bugfix on 0.2.2.6-alpha.
6769 - Fix compilation on Solaris by removing support for the
6770 DisableAllSwap config option. Solaris doesn't have an rlimit for
6771 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6774 o Minor bugfixes (crashes):
6775 - Do not segfault when writing buffer stats when we haven't observed
6776 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6778 - If we're in the pathological case where there's no exit bandwidth
6779 but there is non-exit bandwidth, or no guard bandwidth but there
6780 is non-guard bandwidth, don't crash during path selection. Bugfix
6782 - Fix an impossible-to-actually-trigger buffer overflow in relay
6783 descriptor generation. Bugfix on 0.1.0.15.
6785 o Minor bugfixes (privacy):
6786 - Fix an instance where a Tor directory mirror might accidentally
6787 log the IP address of a misbehaving Tor client. Bugfix on
6789 - Don't list Windows capabilities in relay descriptors. We never made
6790 use of them, and maybe it's a bad idea to publish them. Bugfix
6793 o Minor bugfixes (other):
6794 - Resolve an edge case in path weighting that could make us misweight
6795 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
6796 - Fix statistics on client numbers by country as seen by bridges that
6797 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
6798 intervals instead of variable 12-to-48-hour intervals.
6799 - After we free an internal connection structure, overwrite it
6800 with a different memory value than we use for overwriting a freed
6801 internal circuit structure. Should help with debugging. Suggested
6803 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
6807 - Remove the HSAuthorityRecordStats option that version 0 hidden
6808 service authorities could have used to track statistics of overall
6809 hidden service usage.
6812 Changes in version 0.2.1.22 - 2010-01-19
6813 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
6814 authorities -- it would tell you its whole history of bridge descriptors
6815 if you make the right directory request. This stable update also
6816 rotates two of the seven v3 directory authority keys and locations.
6818 o Directory authority changes:
6819 - Rotate keys (both v3 identity and relay identity) for moria1
6823 - Stop bridge directory authorities from answering dbg-stability.txt
6824 directory queries, which would let people fetch a list of all
6825 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6828 Changes in version 0.2.1.21 - 2009-12-21
6829 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
6830 library. If you use Tor on Linux / Unix and you're getting SSL
6831 renegotiation errors, upgrading should help. We also recommend an
6832 upgrade if you're an exit relay.
6835 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6836 handshake from working unless we explicitly tell OpenSSL that we
6837 are using SSL renegotiation safely. We are, of course, but OpenSSL
6838 0.9.8l won't work unless we say we are.
6839 - Avoid crashing if the client is trying to upload many bytes and the
6840 circuit gets torn down at the same time, or if the flip side
6841 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
6844 - Do not refuse to learn about authority certs and v2 networkstatus
6845 documents that are older than the latest consensus. This bug might
6846 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6847 Spotted and fixed by xmux.
6848 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
6849 trigger platform-specific option misparsing case found by Coverity
6851 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
6852 trigger assert. Fixes bug 1173.
6855 Changes in version 0.2.2.6-alpha - 2009-11-19
6856 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
6857 support for the new lower-footprint "microdescriptor" directory design,
6858 future-proofing our consensus format against new hash functions or
6859 other changes, and an Android port. It also makes Tor compatible with
6860 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
6863 - Directory authorities can now create, vote on, and serve multiple
6864 parallel formats of directory data as part of their voting process.
6865 Partially implements Proposal 162: "Publish the consensus in
6867 - Directory authorities can now agree on and publish small summaries
6868 of router information that clients can use in place of regular
6869 server descriptors. This transition will eventually allow clients
6870 to use far less bandwidth for downloading information about the
6871 network. Begins the implementation of Proposal 158: "Clients
6872 download consensus + microdescriptors".
6873 - The directory voting system is now extensible to use multiple hash
6874 algorithms for signatures and resource selection. Newer formats
6875 are signed with SHA256, with a possibility for moving to a better
6876 hash algorithm in the future.
6877 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
6878 current and future memory pages via mlockall(). On supported
6879 platforms (modern Linux and probably BSD but not Windows or OS X),
6880 this should effectively disable any and all attempts to page out
6881 memory. This option requires that you start your Tor as root --
6882 if you use DisableAllSwap, please consider using the User option
6883 to properly reduce the privileges of your Tor.
6884 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
6885 to help Tor build correctly for Android phones.
6888 - Work around a security feature in OpenSSL 0.9.8l that prevents our
6889 handshake from working unless we explicitly tell OpenSSL that we
6890 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
6891 won't work unless we say we are.
6894 - Fix a crash bug when trying to initialize the evdns module in
6895 Libevent 2. Bugfix on 0.2.1.16-rc.
6896 - Stop logging at severity 'warn' when some other Tor client tries
6897 to establish a circuit with us using weak DH keys. It's a protocol
6898 violation, but that doesn't mean ordinary users need to hear about
6899 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
6900 - Do not refuse to learn about authority certs and v2 networkstatus
6901 documents that are older than the latest consensus. This bug might
6902 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
6903 Spotted and fixed by xmux.
6904 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
6905 - If all authorities restart at once right before a consensus vote,
6906 nobody will vote about "Running", and clients will get a consensus
6907 with no usable relays. Instead, authorities refuse to build a
6908 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
6909 - If your relay can't keep up with the number of incoming create
6910 cells, it would log one warning per failure into your logs. Limit
6911 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
6912 - Bridges now use "reject *:*" as their default exit policy. Bugfix
6913 on 0.2.0.3-alpha; fixes bug 1113.
6914 - Fix a memory leak on directory authorities during voting that was
6915 introduced in 0.2.2.1-alpha. Found via valgrind.
6918 Changes in version 0.2.1.20 - 2009-10-15
6919 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
6920 services at once, prepares for more performance improvements, and
6921 fixes a bunch of smaller bugs.
6923 The Windows and OS X bundles also include a more recent Vidalia,
6924 and switch from Privoxy to Polipo.
6926 The OS X installers are now drag and drop. It's best to un-install
6927 Tor/Vidalia and then install this new bundle, rather than upgrade. If
6928 you want to upgrade, you'll need to update the paths for Tor and Polipo
6929 in the Vidalia Settings window.
6932 - Send circuit or stream sendme cells when our window has decreased
6933 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6934 by Karsten when testing the "reduce circuit window" performance
6935 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6936 before the release of Tor 0.0.0. This is the new winner of the
6938 - Fix a remotely triggerable memory leak when a consensus document
6939 contains more than one signature from the same voter. Bugfix on
6941 - Avoid segfault in rare cases when finishing an introduction circuit
6942 as a client and finding out that we don't have an introduction key
6943 for it. Fixes bug 1073. Reported by Aaron Swartz.
6946 - Tor now reads the "circwindow" parameter out of the consensus,
6947 and uses that value for its circuit package window rather than the
6948 default of 1000 cells. Begins the implementation of proposal 168.
6950 o New directory authorities:
6951 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6953 - Move moria1 and tonga to alternate IP addresses.
6956 - Fix a signed/unsigned compile warning in 0.2.1.19.
6957 - Fix possible segmentation fault on directory authorities. Bugfix on
6959 - Fix an extremely rare infinite recursion bug that could occur if
6960 we tried to log a message after shutting down the log subsystem.
6961 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
6962 - Fix an obscure bug where hidden services on 64-bit big-endian
6963 systems might mis-read the timestamp in v3 introduce cells, and
6964 refuse to connect back to the client. Discovered by "rotor".
6965 Bugfix on 0.2.1.6-alpha.
6966 - We were triggering a CLOCK_SKEW controller status event whenever
6967 we connect via the v2 connection protocol to any relay that has
6968 a wrong clock. Instead, we should only inform the controller when
6969 it's a trusted authority that claims our clock is wrong. Bugfix
6970 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6971 - We were telling the controller about CHECKING_REACHABILITY and
6972 REACHABILITY_FAILED status events whenever we launch a testing
6973 circuit or notice that one has failed. Instead, only tell the
6974 controller when we want to inform the user of overall success or
6975 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6977 - Don't warn when we're using a circuit that ends with a node
6978 excluded in ExcludeExitNodes, but the circuit is not used to access
6979 the outside world. This should help fix bug 1090. Bugfix on
6981 - Work around a small memory leak in some versions of OpenSSL that
6982 stopped the memory used by the hostname TLS extension from being
6986 - Add a "getinfo status/accepted-server-descriptor" controller
6987 command, which is the recommended way for controllers to learn
6988 whether our server descriptor has been successfully received by at
6989 least on directory authority. Un-recommend good-server-descriptor
6990 getinfo and status events until we have a better design for them.
6993 Changes in version 0.2.2.5-alpha - 2009-10-11
6994 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
6997 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
6999 o Directory authorities:
7000 - Temporarily (just for this release) move dizum to an alternate
7004 Changes in version 0.2.2.4-alpha - 2009-10-10
7005 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7006 introduces a new unit test framework, shifts directry authority
7007 addresses around to reduce the impact from recent blocking events,
7008 and fixes a few smaller bugs.
7011 - Fix several more asserts in the circuit_build_times code, for
7012 example one that causes Tor to fail to start once we have
7013 accumulated 5000 build times in the state file. Bugfixes on
7014 0.2.2.2-alpha; fixes bug 1108.
7016 o New directory authorities:
7017 - Move moria1 and Tonga to alternate IP addresses.
7020 - Log SSL state transitions at debug level during handshake, and
7021 include SSL states in error messages. This may help debug future
7022 SSL handshake issues.
7023 - Add a new "Handshake" log domain for activities that happen
7024 during the TLS handshake.
7025 - Revert to the "June 3 2009" ip-to-country file. The September one
7026 seems to have removed most US IP addresses.
7027 - Directory authorities now reject Tor relays with versions less than
7028 0.1.2.14. This step cuts out four relays from the current network,
7029 none of which are very big.
7032 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7034 - Fix two memory leaks in the error case of
7035 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7036 - Don't count one-hop circuits when we're estimating how long it
7037 takes circuits to build on average. Otherwise we'll set our circuit
7038 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7039 - Directory authorities no longer change their opinion of, or vote on,
7040 whether a router is Running, unless they have themselves been
7041 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7044 o Code simplifications and refactoring:
7045 - Revise our unit tests to use the "tinytest" framework, so we
7046 can run tests in their own processes, have smarter setup/teardown
7047 code, and so on. The unit test code has moved to its own
7048 subdirectory, and has been split into multiple modules.
7051 Changes in version 0.2.2.3-alpha - 2009-09-23
7052 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7055 - Fix an overzealous assert in our new circuit build timeout code.
7056 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7059 - If the networkstatus consensus tells us that we should use a
7060 negative circuit package window, ignore it. Otherwise we'll
7061 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7064 Changes in version 0.2.2.2-alpha - 2009-09-21
7065 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7066 clients: Tor tracks the average time it takes to build a circuit, and
7067 avoids using circuits that take too long to build. For fast connections,
7068 this feature can cut your expected latency in half. For slow or flaky
7069 connections, it could ruin your Tor experience. Let us know if it does!
7072 - Tor now tracks how long it takes to build client-side circuits
7073 over time, and adapts its timeout to local network performance.
7074 Since a circuit that takes a long time to build will also provide
7075 bad performance, we get significant latency improvements by
7076 discarding the slowest 20% of circuits. Specifically, Tor creates
7077 circuits more aggressively than usual until it has enough data
7078 points for a good timeout estimate. Implements proposal 151.
7079 We are especially looking for reports (good and bad) from users with
7080 both EDGE and broadband connections that can move from broadband
7081 to EDGE and find out if the build-time data in the .tor/state gets
7082 reset without loss of Tor usability. You should also see a notice
7083 log message telling you that Tor has reset its timeout.
7084 - Directory authorities can now vote on arbitary integer values as
7085 part of the consensus process. This is designed to help set
7086 network-wide parameters. Implements proposal 167.
7087 - Tor now reads the "circwindow" parameter out of the consensus,
7088 and uses that value for its circuit package window rather than the
7089 default of 1000 cells. Begins the implementation of proposal 168.
7092 - Fix a remotely triggerable memory leak when a consensus document
7093 contains more than one signature from the same voter. Bugfix on
7097 - Fix an extremely rare infinite recursion bug that could occur if
7098 we tried to log a message after shutting down the log subsystem.
7099 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7100 - Fix parsing for memory or time units given without a space between
7101 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7102 - A networkstatus vote must contain exactly one signature. Spec
7103 conformance issue. Bugfix on 0.2.0.3-alpha.
7104 - Fix an obscure bug where hidden services on 64-bit big-endian
7105 systems might mis-read the timestamp in v3 introduce cells, and
7106 refuse to connect back to the client. Discovered by "rotor".
7107 Bugfix on 0.2.1.6-alpha.
7108 - We were triggering a CLOCK_SKEW controller status event whenever
7109 we connect via the v2 connection protocol to any relay that has
7110 a wrong clock. Instead, we should only inform the controller when
7111 it's a trusted authority that claims our clock is wrong. Bugfix
7112 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7113 - We were telling the controller about CHECKING_REACHABILITY and
7114 REACHABILITY_FAILED status events whenever we launch a testing
7115 circuit or notice that one has failed. Instead, only tell the
7116 controller when we want to inform the user of overall success or
7117 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7119 - Don't warn when we're using a circuit that ends with a node
7120 excluded in ExcludeExitNodes, but the circuit is not used to access
7121 the outside world. This should help fix bug 1090, but more problems
7122 remain. Bugfix on 0.2.1.6-alpha.
7123 - Work around a small memory leak in some versions of OpenSSL that
7124 stopped the memory used by the hostname TLS extension from being
7126 - Make our 'torify' script more portable; if we have only one of
7127 'torsocks' or 'tsocks' installed, don't complain to the user;
7128 and explain our warning about tsocks better.
7131 - Add a "getinfo status/accepted-server-descriptor" controller
7132 command, which is the recommended way for controllers to learn
7133 whether our server descriptor has been successfully received by at
7134 least on directory authority. Un-recommend good-server-descriptor
7135 getinfo and status events until we have a better design for them.
7136 - Update to the "September 4 2009" ip-to-country file.
7139 Changes in version 0.2.2.1-alpha - 2009-08-26
7140 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7141 Tor clients to bootstrap on networks where only port 80 is reachable,
7142 makes it more straightforward to support hardware crypto accelerators,
7143 and starts the groundwork for gathering stats safely at relays.
7146 - Start the process of disabling ".exit" address notation, since it
7147 can be used for a variety of esoteric application-level attacks
7148 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7151 o New directory authorities:
7152 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7156 - New AccelName and AccelDir options add support for dynamic OpenSSL
7157 hardware crypto acceleration engines.
7158 - Tor now supports tunneling all of its outgoing connections over
7159 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7160 configuration options. Code by Christopher Davis.
7163 - Send circuit or stream sendme cells when our window has decreased
7164 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7165 by Karsten when testing the "reduce circuit window" performance
7166 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7167 before the release of Tor 0.0.0. This is the new winner of the
7170 o New options for gathering stats safely:
7171 - Directory mirrors that set "DirReqStatistics 1" write statistics
7172 about directory requests to disk every 24 hours. As compared to the
7173 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7174 1) stats are written to disk exactly every 24 hours; 2) estimated
7175 shares of v2 and v3 requests are determined as mean values, not at
7176 the end of a measurement period; 3) unresolved requests are listed
7177 with country code '??'; 4) directories also measure download times.
7178 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7179 number of exit streams and transferred bytes per port to disk every
7181 - Relays that set "CellStatistics 1" write statistics on how long
7182 cells spend in their circuit queues to disk every 24 hours.
7183 - Entry nodes that set "EntryStatistics 1" write statistics on the
7184 rough number and origins of connecting clients to disk every 24
7186 - Relays that write any of the above statistics to disk and set
7187 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7188 their extra-info documents.
7191 - New --digests command-line switch to output the digests of the
7192 source files Tor was built with.
7193 - The "torify" script now uses torsocks where available.
7194 - The memarea code now uses a sentinel value at the end of each area
7195 to make sure nothing writes beyond the end of an area. This might
7196 help debug some conceivable causes of bug 930.
7197 - Time and memory units in the configuration file can now be set to
7198 fractional units. For example, "2.5 GB" is now a valid value for
7200 - Certain Tor clients (such as those behind check.torproject.org) may
7201 want to fetch the consensus in an extra early manner. To enable this
7202 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7203 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7204 as only certain clients who must have this information sooner should
7206 - Instead of adding the svn revision to the Tor version string, report
7207 the git commit (when we're building from a git checkout).
7210 - If any of the v3 certs we download are unparseable, we should
7211 actually notice the failure so we don't retry indefinitely. Bugfix
7212 on 0.2.0.x; reported by "rotator".
7213 - If the cached cert file is unparseable, warn but don't exit.
7214 - Fix possible segmentation fault on directory authorities. Bugfix on
7216 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7217 Might help diagnosing bug 1051.
7219 o Deprecated and removed features:
7220 - The controller no longer accepts the old obsolete "addr-mappings/"
7221 or "unregistered-servers-" GETINFO values.
7222 - Hidden services no longer publish version 0 descriptors, and clients
7223 do not request or use version 0 descriptors. However, the old hidden
7224 service authorities still accept and serve version 0 descriptors
7225 when contacted by older hidden services/clients.
7226 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7227 always on; using them is necessary for correct forward-compatible
7229 - Remove support for .noconnect style addresses. Nobody was using
7230 them, and they provided another avenue for detecting Tor users
7231 via application-level web tricks.
7233 o Packaging changes:
7234 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7235 installer bundles. See
7236 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7237 for details of what's new in Vidalia 0.2.3.
7238 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7239 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7240 configuration file, rather than the old Privoxy.
7241 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7242 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7243 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7244 better compatibility with OS X 10.6, aka Snow Leopard.
7245 - OS X Vidalia Bundle: The multi-package installer is now replaced
7246 by a simple drag and drop to the /Applications folder. This change
7247 occurred with the upgrade to Vidalia 0.2.3.
7250 Changes in version 0.2.1.19 - 2009-07-28
7251 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7252 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7255 - Make accessing hidden services on 0.2.1.x work right again.
7256 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7257 part of patch provided by "optimist".
7260 - When a relay/bridge is writing out its identity key fingerprint to
7261 the "fingerprint" file and to its logs, write it without spaces. Now
7262 it will look like the fingerprints in our bridges documentation,
7263 and confuse fewer users.
7266 - Relays no longer publish a new server descriptor if they change
7267 their MaxAdvertisedBandwidth config option but it doesn't end up
7268 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7269 fixes bug 1026. Patch from Sebastian.
7270 - Avoid leaking memory every time we get a create cell but we have
7271 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7272 fixes bug 1034. Reported by BarkerJr.
7275 Changes in version 0.2.1.18 - 2009-07-24
7276 Tor 0.2.1.18 lays the foundations for performance improvements,
7277 adds status events to help users diagnose bootstrap problems, adds
7278 optional authentication/authorization for hidden services, fixes a
7279 variety of potential anonymity problems, and includes a huge pile of
7280 other features and bug fixes.
7283 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7286 Changes in version 0.2.1.17-rc - 2009-07-07
7287 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7288 candidate for the 0.2.1.x series. It lays the groundwork for further
7289 client performance improvements, and also fixes a big bug with directory
7290 authorities that were causing them to assign Guard and Stable flags
7293 The Windows bundles also finally include the geoip database that we
7294 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7295 should actually install Torbutton rather than giving you a cryptic
7296 failure message (oops).
7299 - Clients now use the bandwidth values in the consensus, rather than
7300 the bandwidth values in each relay descriptor. This approach opens
7301 the door to more accurate bandwidth estimates once the directory
7302 authorities start doing active measurements. Implements more of
7306 - When Tor clients restart after 1-5 days, they discard all their
7307 cached descriptors as too old, but they still use the cached
7308 consensus document. This approach is good for robustness, but
7309 bad for performance: since they don't know any bandwidths, they
7310 end up choosing at random rather than weighting their choice by
7311 speed. Fixed by the above feature of putting bandwidths in the
7312 consensus. Bugfix on 0.2.0.x.
7313 - Directory authorities were neglecting to mark relays down in their
7314 internal histories if the relays fall off the routerlist without
7315 ever being found unreachable. So there were relays in the histories
7316 that haven't been seen for eight months, and are listed as being
7317 up for eight months. This wreaked havoc on the "median wfu"
7318 and "median mtbf" calculations, in turn making Guard and Stable
7319 flags very wrong, hurting network performance. Fixes bugs 696 and
7320 969. Bugfix on 0.2.0.6-alpha.
7323 - Serve the DirPortFrontPage page even when we have been approaching
7324 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7325 - The control port would close the connection before flushing long
7326 replies, such as the network consensus, if a QUIT command was issued
7327 before the reply had completed. Now, the control port flushes all
7328 pending replies before closing the connection. Also fixed a spurious
7329 warning when a QUIT command is issued after a malformed or rejected
7330 AUTHENTICATE command, but before the connection was closed. Patch
7331 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7332 - When we can't find an intro key for a v2 hidden service descriptor,
7333 fall back to the v0 hidden service descriptor and log a bug message.
7334 Workaround for bug 1024.
7335 - Fix a log message that did not respect the SafeLogging option.
7339 - If we're a relay and we change our IP address, be more verbose
7340 about the reason that made us change. Should help track down
7341 further bugs for relays on dynamic IP addresses.
7344 Changes in version 0.2.0.35 - 2009-06-24
7346 - Avoid crashing in the presence of certain malformed descriptors.
7347 Found by lark, and by automated fuzzing.
7348 - Fix an edge case where a malicious exit relay could convince a
7349 controller that the client's DNS question resolves to an internal IP
7350 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7353 - Finally fix the bug where dynamic-IP relays disappear when their
7354 IP address changes: directory mirrors were mistakenly telling
7355 them their old address if they asked via begin_dir, so they
7356 never got an accurate answer about their new address, so they
7357 just vanished after a day. For belt-and-suspenders, relays that
7358 don't set Address in their config now avoid using begin_dir for
7359 all direct connections. Should fix bugs 827, 883, and 900.
7360 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7361 that would occur on some exit nodes when DNS failures and timeouts
7362 occurred in certain patterns. Fix for bug 957.
7365 - When starting with a cache over a few days old, do not leak
7366 memory for the obsolete router descriptors in it. Bugfix on
7367 0.2.0.33; fixes bug 672.
7368 - Hidden service clients didn't use a cached service descriptor that
7369 was older than 15 minutes, but wouldn't fetch a new one either,
7370 because there was already one in the cache. Now, fetch a v2
7371 descriptor unless the same descriptor was added to the cache within
7372 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7375 Changes in version 0.2.1.16-rc - 2009-06-20
7376 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7377 a bunch of minor bugs.
7380 - Fix an edge case where a malicious exit relay could convince a
7381 controller that the client's DNS question resolves to an internal IP
7382 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7384 o Major performance improvements (on 0.2.0.x):
7385 - Disable and refactor some debugging checks that forced a linear scan
7386 over the whole server-side DNS cache. These accounted for over 50%
7387 of CPU time on a relatively busy exit node's gprof profile. Found
7389 - Disable some debugging checks that appeared in exit node profile
7393 - Update to the "June 3 2009" ip-to-country file.
7394 - Do not have tor-resolve automatically refuse all .onion addresses;
7395 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7397 o Minor bugfixes (on 0.2.0.x):
7398 - Log correct error messages for DNS-related network errors on
7400 - Fix a race condition that could cause crashes or memory corruption
7401 when running as a server with a controller listening for log
7403 - Avoid crashing when we have a policy specified in a DirPolicy or
7404 SocksPolicy or ReachableAddresses option with ports set on it,
7405 and we re-load the policy. May fix bug 996.
7406 - Hidden service clients didn't use a cached service descriptor that
7407 was older than 15 minutes, but wouldn't fetch a new one either,
7408 because there was already one in the cache. Now, fetch a v2
7409 descriptor unless the same descriptor was added to the cache within
7410 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7412 o Minor bugfixes (on 0.2.1.x):
7413 - Don't warn users about low port and hibernation mix when they
7414 provide a *ListenAddress directive to fix that. Bugfix on
7416 - When switching back and forth between bridge mode, do not start
7417 gathering GeoIP data until two hours have passed.
7418 - Do not complain that the user has requested an excluded node as
7419 an exit when the node is not really an exit. This could happen
7420 because the circuit was for testing, or an introduction point.
7424 Changes in version 0.2.1.15-rc - 2009-05-25
7425 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7426 series. It fixes a major bug on fast exit relays, as well as a variety
7429 o Major bugfixes (on 0.2.0.x):
7430 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7431 that would occur on some exit nodes when DNS failures and timeouts
7432 occurred in certain patterns. Fix for bug 957.
7434 o Minor bugfixes (on 0.2.0.x):
7435 - Actually return -1 in the error case for read_bandwidth_usage().
7436 Harmless bug, since we currently don't care about the return value
7437 anywhere. Bugfix on 0.2.0.9-alpha.
7438 - Provide a more useful log message if bug 977 (related to buffer
7439 freelists) ever reappears, and do not crash right away.
7440 - Fix an assertion failure on 64-bit platforms when we allocated
7441 memory right up to the end of a memarea, then realigned the memory
7442 one step beyond the end. Fixes a possible cause of bug 930.
7443 - Protect the count of open sockets with a mutex, so we can't
7444 corrupt it when two threads are closing or opening sockets at once.
7445 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7446 - Don't allow a bridge to publish its router descriptor to a
7447 non-bridge directory authority. Fixes part of bug 932.
7448 - When we change to or from being a bridge, reset our counts of
7449 client usage by country. Fixes bug 932.
7450 - Fix a bug that made stream bandwidth get misreported to the
7452 - Stop using malloc_usable_size() to use more area than we had
7453 actually allocated: it was safe, but made valgrind really unhappy.
7454 - Fix a memory leak when v3 directory authorities load their keys
7455 and cert from disk. Bugfix on 0.2.0.1-alpha.
7457 o Minor bugfixes (on 0.2.1.x):
7458 - Fix use of freed memory when deciding to mark a non-addable
7459 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7462 Changes in version 0.2.1.14-rc - 2009-04-12
7463 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7464 series. It begins fixing some major performance problems, and also
7465 finally addresses the bug that was causing relays on dynamic IP
7466 addresses to fall out of the directory.
7469 - Clients replace entry guards that were chosen more than a few months
7470 ago. This change should significantly improve client performance,
7471 especially once more people upgrade, since relays that have been
7472 a guard for a long time are currently overloaded.
7474 o Major bugfixes (on 0.2.0):
7475 - Finally fix the bug where dynamic-IP relays disappear when their
7476 IP address changes: directory mirrors were mistakenly telling
7477 them their old address if they asked via begin_dir, so they
7478 never got an accurate answer about their new address, so they
7479 just vanished after a day. For belt-and-suspenders, relays that
7480 don't set Address in their config now avoid using begin_dir for
7481 all direct connections. Should fix bugs 827, 883, and 900.
7482 - Relays were falling out of the networkstatus consensus for
7483 part of a day if they changed their local config but the
7484 authorities discarded their new descriptor as "not sufficiently
7485 different". Now directory authorities accept a descriptor as changed
7486 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7488 - Avoid crashing in the presence of certain malformed descriptors.
7489 Found by lark, and by automated fuzzing.
7492 - When generating circuit events with verbose nicknames for
7493 controllers, try harder to look up nicknames for routers on a
7494 circuit. (Previously, we would look in the router descriptors we had
7495 for nicknames, but not in the consensus.) Partial fix for bug 941.
7496 - If the bridge config line doesn't specify a port, assume 443.
7497 This makes bridge lines a bit smaller and easier for users to
7499 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7500 bytes (aka 20KB/s), to match our documentation. Also update
7501 directory authorities so they always assign the Fast flag to relays
7502 with 20KB/s of capacity. Now people running relays won't suddenly
7503 find themselves not seeing any use, if the network gets faster
7505 - Update to the "April 3 2009" ip-to-country file.
7508 - Avoid trying to print raw memory to the logs when we decide to
7509 give up on downloading a given relay descriptor. Bugfix on
7511 - In tor-resolve, when the Tor client to use is specified by
7512 <hostname>:<port>, actually use the specified port rather than
7513 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7514 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7515 - When starting with a cache over a few days old, do not leak
7516 memory for the obsolete router descriptors in it. Bugfix on
7518 - Avoid double-free on list of successfully uploaded hidden
7519 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7520 - Change memarea_strndup() implementation to work even when
7521 duplicating a string at the end of a page. This bug was
7522 harmless for now, but could have meant crashes later. Fix by
7523 lark. Bugfix on 0.2.1.1-alpha.
7524 - Limit uploaded directory documents to be 16M rather than 500K.
7525 The directory authorities were refusing v3 consensus votes from
7526 other authorities, since the votes are now 504K. Fixes bug 959;
7527 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7528 - Directory authorities should never send a 503 "busy" response to
7529 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7533 Changes in version 0.2.1.13-alpha - 2009-03-09
7534 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7535 cleanups. We're finally getting close to a release candidate.
7538 - Correctly update the list of which countries we exclude as
7539 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7540 lark. Bugfix on 0.2.1.6-alpha.
7542 o Minor bugfixes (on 0.2.0.x and earlier):
7543 - Automatically detect MacOSX versions earlier than 10.4.0, and
7544 disable kqueue from inside Tor when running with these versions.
7545 We previously did this from the startup script, but that was no
7546 help to people who didn't use the startup script. Resolves bug 863.
7547 - When we had picked an exit node for a connection, but marked it as
7548 "optional", and it turned out we had no onion key for the exit,
7549 stop wanting that exit and try again. This situation may not
7550 be possible now, but will probably become feasible with proposal
7551 158. Spotted by rovv. Fixes another case of bug 752.
7552 - Clients no longer cache certificates for authorities they do not
7553 recognize. Bugfix on 0.2.0.9-alpha.
7554 - When we can't transmit a DNS request due to a network error, retry
7555 it after a while, and eventually transmit a failing response to
7556 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7557 - If the controller claimed responsibility for a stream, but that
7558 stream never finished making its connection, it would live
7559 forever in circuit_wait state. Now we close it after SocksTimeout
7560 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7561 - Drop begin cells to a hidden service if they come from the middle
7562 of a circuit. Patch from lark.
7563 - When we erroneously receive two EXTEND cells for the same circuit
7564 ID on the same connection, drop the second. Patch from lark.
7565 - Fix a crash that occurs on exit nodes when a nameserver request
7566 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7567 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7569 - Do not assume that a stack-allocated character array will be
7570 64-bit aligned on platforms that demand that uint64_t access is
7571 aligned. Possible fix for bug 604.
7572 - Parse dates and IPv4 addresses in a locale- and libc-independent
7573 manner, to avoid platform-dependent behavior on malformed input.
7574 - Build correctly when configured to build outside the main source
7575 path. Patch from Michael Gold.
7576 - We were already rejecting relay begin cells with destination port
7577 of 0. Now also reject extend cells with destination port or address
7578 of 0. Suggested by lark.
7580 o Minor bugfixes (on 0.2.1.x):
7581 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7582 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7583 - If we're an exit node, scrub the IP address to which we are exiting
7584 in the logs. Bugfix on 0.2.1.8-alpha.
7587 - On Linux, use the prctl call to re-enable core dumps when the user
7589 - New controller event NEWCONSENSUS that lists the networkstatus
7590 lines for every recommended relay. Now controllers like Torflow
7591 can keep up-to-date on which relays they should be using.
7592 - Update to the "February 26 2009" ip-to-country file.
7595 Changes in version 0.2.0.34 - 2009-02-08
7596 Tor 0.2.0.34 features several more security-related fixes. You should
7597 upgrade, especially if you run an exit relay (remote crash) or a
7598 directory authority (remote infinite loop), or you're on an older
7599 (pre-XP) or not-recently-patched Windows (remote exploit).
7601 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7602 have many known flaws, and nobody should be using them. You should
7603 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7604 stop using those packages and upgrade anyway.
7607 - Fix an infinite-loop bug on handling corrupt votes under certain
7608 circumstances. Bugfix on 0.2.0.8-alpha.
7609 - Fix a temporary DoS vulnerability that could be performed by
7610 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7611 - Avoid a potential crash on exit nodes when processing malformed
7612 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7613 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7614 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7617 - Fix compilation on systems where time_t is a 64-bit integer.
7618 Patch from Matthias Drochner.
7619 - Don't consider expiring already-closed client connections. Fixes
7620 bug 893. Bugfix on 0.0.2pre20.
7623 Changes in version 0.2.1.12-alpha - 2009-02-08
7624 Tor 0.2.1.12-alpha features several more security-related fixes. You
7625 should upgrade, especially if you run an exit relay (remote crash) or
7626 a directory authority (remote infinite loop), or you're on an older
7627 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7628 includes a big pile of minor bugfixes and cleanups.
7631 - Fix an infinite-loop bug on handling corrupt votes under certain
7632 circumstances. Bugfix on 0.2.0.8-alpha.
7633 - Fix a temporary DoS vulnerability that could be performed by
7634 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7635 - Avoid a potential crash on exit nodes when processing malformed
7636 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7639 - Let controllers actually ask for the "clients_seen" event for
7640 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7641 reported by Matt Edman.
7642 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7644 - Fix a bug in address parsing that was preventing bridges or hidden
7645 service targets from being at IPv6 addresses.
7646 - Solve a bug that kept hardware crypto acceleration from getting
7647 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7649 - Remove a bash-ism from configure.in to build properly on non-Linux
7650 platforms. Bugfix on 0.2.1.1-alpha.
7651 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7652 headers. Bugfix on 0.2.0.10-alpha.
7653 - Don't consider expiring already-closed client connections. Fixes
7654 bug 893. Bugfix on 0.0.2pre20.
7655 - Fix another interesting corner-case of bug 891 spotted by rovv:
7656 Previously, if two hosts had different amounts of clock drift, and
7657 one of them created a new connection with just the wrong timing,
7658 the other might decide to deprecate the new connection erroneously.
7659 Bugfix on 0.1.1.13-alpha.
7660 - Resolve a very rare crash bug that could occur when the user forced
7661 a nameserver reconfiguration during the middle of a nameserver
7662 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7663 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7664 Bugfix on 0.2.1.7-alpha.
7665 - If we're using bridges and our network goes away, be more willing
7666 to forgive our bridges and try again when we get an application
7667 request. Bugfix on 0.2.0.x.
7670 - Support platforms where time_t is 64 bits long. (Congratulations,
7671 NetBSD!) Patch from Matthias Drochner.
7672 - Add a 'getinfo status/clients-seen' controller command, in case
7673 controllers want to hear clients_seen events but connect late.
7676 - Disable GCC's strict alias optimization by default, to avoid the
7677 likelihood of its introducing subtle bugs whenever our code violates
7678 the letter of C99's alias rules.
7681 Changes in version 0.2.0.33 - 2009-01-21
7682 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7683 useful to users. It also finally fixes a bug where a relay or client
7684 that's been off for many days would take a long time to bootstrap.
7686 This update also fixes an important security-related bug reported by
7687 Ilja van Sprundel. You should upgrade. (We'll send out more details
7688 about the bug once people have had some time to upgrade.)
7691 - Fix a heap-corruption bug that may be remotely triggerable on
7692 some platforms. Reported by Ilja van Sprundel.
7695 - When a stream at an exit relay is in state "resolving" or
7696 "connecting" and it receives an "end" relay cell, the exit relay
7697 would silently ignore the end cell and not close the stream. If
7698 the client never closes the circuit, then the exit relay never
7699 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7701 - When sending CREATED cells back for a given circuit, use a 64-bit
7702 connection ID to find the right connection, rather than an addr:port
7703 combination. Now that we can have multiple OR connections between
7704 the same ORs, it is no longer possible to use addr:port to uniquely
7705 identify a connection.
7706 - Bridge relays that had DirPort set to 0 would stop fetching
7707 descriptors shortly after startup, and then briefly resume
7708 after a new bandwidth test and/or after publishing a new bridge
7709 descriptor. Bridge users that try to bootstrap from them would
7710 get a recent networkstatus but would get descriptors from up to
7711 18 hours earlier, meaning most of the descriptors were obsolete
7712 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7713 - Prevent bridge relays from serving their 'extrainfo' document
7714 to anybody who asks, now that extrainfo docs include potentially
7715 sensitive aggregated client geoip summaries. Bugfix on
7717 - If the cached networkstatus consensus is more than five days old,
7718 discard it rather than trying to use it. In theory it could be
7719 useful because it lists alternate directory mirrors, but in practice
7720 it just means we spend many minutes trying directory mirrors that
7721 are long gone from the network. Also discard router descriptors as
7722 we load them if they are more than five days old, since the onion
7723 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7726 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7727 could make gcc generate non-functional binary search code. Bugfix
7729 - Build correctly on platforms without socklen_t.
7730 - Compile without warnings on solaris.
7731 - Avoid potential crash on internal error during signature collection.
7732 Fixes bug 864. Patch from rovv.
7733 - Correct handling of possible malformed authority signing key
7734 certificates with internal signature types. Fixes bug 880.
7735 Bugfix on 0.2.0.3-alpha.
7736 - Fix a hard-to-trigger resource leak when logging credential status.
7738 - When we can't initialize DNS because the network is down, do not
7739 automatically stop Tor from starting. Instead, we retry failed
7740 dns_init() every 10 minutes, and change the exit policy to reject
7741 *:* until one succeeds. Fixes bug 691.
7742 - Use 64 bits instead of 32 bits for connection identifiers used with
7743 the controller protocol, to greatly reduce risk of identifier reuse.
7744 - When we're choosing an exit node for a circuit, and we have
7745 no pending streams, choose a good general exit rather than one that
7746 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7747 - Fix another case of assuming, when a specific exit is requested,
7748 that we know more than the user about what hosts it allows.
7749 Fixes one case of bug 752. Patch from rovv.
7750 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7751 seconds. Warn the user if lower values are given in the
7752 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7753 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7754 user if lower values are given in the configuration. Bugfix on
7755 0.1.1.17-rc. Patch by Sebastian.
7756 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7757 the cache because we already had a v0 descriptor with the same ID.
7758 Bugfix on 0.2.0.18-alpha.
7759 - Fix a race condition when freeing keys shared between main thread
7760 and CPU workers that could result in a memory leak. Bugfix on
7761 0.1.0.1-rc. Fixes bug 889.
7762 - Send a valid END cell back when a client tries to connect to a
7763 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7764 840. Patch from rovv.
7765 - Check which hops rendezvous stream cells are associated with to
7766 prevent possible guess-the-streamid injection attacks from
7767 intermediate hops. Fixes another case of bug 446. Based on patch
7769 - If a broken client asks a non-exit router to connect somewhere,
7770 do not even do the DNS lookup before rejecting the connection.
7771 Fixes another case of bug 619. Patch from rovv.
7772 - When a relay gets a create cell it can't decrypt (e.g. because it's
7773 using the wrong onion key), we were dropping it and letting the
7774 client time out. Now actually answer with a destroy cell. Fixes
7775 bug 904. Bugfix on 0.0.2pre8.
7777 o Minor bugfixes (hidden services):
7778 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7779 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7782 - Report the case where all signatures in a detached set are rejected
7783 differently than the case where there is an error handling the
7785 - When we realize that another process has modified our cached
7786 descriptors, print out a more useful error message rather than
7787 triggering an assertion. Fixes bug 885. Patch from Karsten.
7788 - Implement the 0x20 hack to better resist DNS poisoning: set the
7789 case on outgoing DNS requests randomly, and reject responses that do
7790 not match the case correctly. This logic can be disabled with the
7791 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
7792 of servers that do not reliably preserve case in replies. See
7793 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7795 - Check DNS replies for more matching fields to better resist DNS
7797 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7798 compress cells, which are basically all encrypted, compressed, or
7802 Changes in version 0.2.1.11-alpha - 2009-01-20
7803 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
7804 week it will take a long time to bootstrap again" bug. It also fixes
7805 an important security-related bug reported by Ilja van Sprundel. You
7806 should upgrade. (We'll send out more details about the bug once people
7807 have had some time to upgrade.)
7810 - Fix a heap-corruption bug that may be remotely triggerable on
7811 some platforms. Reported by Ilja van Sprundel.
7814 - Discard router descriptors as we load them if they are more than
7815 five days old. Otherwise if Tor is off for a long time and then
7816 starts with cached descriptors, it will try to use the onion
7817 keys in those obsolete descriptors when building circuits. Bugfix
7818 on 0.2.0.x. Fixes bug 887.
7821 - Try to make sure that the version of Libevent we're running with
7822 is binary-compatible with the one we built with. May address bug
7824 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
7825 for bug 905. Bugfix on 0.2.1.7-alpha.
7826 - Add a new --enable-local-appdata configuration switch to change
7827 the default location of the datadir on win32 from APPDATA to
7828 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
7829 entirely. Patch from coderman.
7832 - Make outbound DNS packets respect the OutboundBindAddress setting.
7833 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
7834 - When our circuit fails at the first hop (e.g. we get a destroy
7835 cell back), avoid using that OR connection anymore, and also
7836 tell all the one-hop directory requests waiting for it that they
7837 should fail. Bugfix on 0.2.1.3-alpha.
7838 - In the torify(1) manpage, mention that tsocks will leak your
7842 Changes in version 0.2.1.10-alpha - 2009-01-06
7843 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
7844 would make the bridge relay not so useful if it had DirPort set to 0,
7845 and one that could let an attacker learn a little bit of information
7846 about the bridge's users), and a bug that would cause your Tor relay
7847 to ignore a circuit create request it can't decrypt (rather than reply
7848 with an error). It also fixes a wide variety of other bugs.
7851 - If the cached networkstatus consensus is more than five days old,
7852 discard it rather than trying to use it. In theory it could
7853 be useful because it lists alternate directory mirrors, but in
7854 practice it just means we spend many minutes trying directory
7855 mirrors that are long gone from the network. Helps bug 887 a bit;
7857 - Bridge relays that had DirPort set to 0 would stop fetching
7858 descriptors shortly after startup, and then briefly resume
7859 after a new bandwidth test and/or after publishing a new bridge
7860 descriptor. Bridge users that try to bootstrap from them would
7861 get a recent networkstatus but would get descriptors from up to
7862 18 hours earlier, meaning most of the descriptors were obsolete
7863 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7864 - Prevent bridge relays from serving their 'extrainfo' document
7865 to anybody who asks, now that extrainfo docs include potentially
7866 sensitive aggregated client geoip summaries. Bugfix on
7870 - New controller event "clients_seen" to report a geoip-based summary
7871 of which countries we've seen clients from recently. Now controllers
7872 like Vidalia can show bridge operators that they're actually making
7874 - Build correctly against versions of OpenSSL 0.9.8 or later built
7875 without support for deprecated functions.
7876 - Update to the "December 19 2008" ip-to-country file.
7878 o Minor bugfixes (on 0.2.0.x):
7879 - Authorities now vote for the Stable flag for any router whose
7880 weighted MTBF is at least 5 days, regardless of the mean MTBF.
7881 - Do not remove routers as too old if we do not have any consensus
7882 document. Bugfix on 0.2.0.7-alpha.
7883 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7884 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7885 - When an exit relay resolves a stream address to a local IP address,
7886 do not just keep retrying that same exit relay over and
7887 over. Instead, just close the stream. Addresses bug 872. Bugfix
7888 on 0.2.0.32. Patch from rovv.
7889 - If a hidden service sends us an END cell, do not consider
7890 retrying the connection; just close it. Patch from rovv.
7891 - When we made bridge authorities stop serving bridge descriptors over
7892 unencrypted links, we also broke DirPort reachability testing for
7893 bridges. So bridges with a non-zero DirPort were printing spurious
7894 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
7895 - When a relay gets a create cell it can't decrypt (e.g. because it's
7896 using the wrong onion key), we were dropping it and letting the
7897 client time out. Now actually answer with a destroy cell. Fixes
7898 bug 904. Bugfix on 0.0.2pre8.
7899 - Squeeze 2-5% out of client performance (according to oprofile) by
7900 improving the implementation of some policy-manipulation functions.
7902 o Minor bugfixes (on 0.2.1.x):
7903 - Make get_interface_address() function work properly again; stop
7904 guessing the wrong parts of our address as our address.
7905 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
7906 send on that circuit. Otherwise we might violate the proposal-110
7907 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
7909 - When we're sending non-EXTEND cells to the first hop in a circuit,
7910 for example to use an encrypted directory connection, we don't need
7911 to use RELAY_EARLY cells: the first hop knows what kind of cell
7912 it is, and nobody else can even see the cell type. Conserving
7913 RELAY_EARLY cells makes it easier to cannibalize circuits like
7915 - Stop logging nameserver addresses in reverse order.
7916 - If we are retrying a directory download slowly over and over, do
7917 not automatically give up after the 254th failure. Bugfix on
7919 - Resume reporting accurate "stream end" reasons to the local control
7920 port. They were lost in the changes for Proposal 148. Bugfix on
7923 o Deprecated and removed features:
7924 - The old "tor --version --version" command, which would print out
7925 the subversion "Id" of most of the source files, is now removed. It
7926 turned out to be less useful than we'd expected, and harder to
7929 o Code simplifications and refactoring:
7930 - Change our header file guard macros to be less likely to conflict
7931 with system headers. Adam Langley noticed that we were conflicting
7932 with log.h on Android.
7933 - Tool-assisted documentation cleanup. Nearly every function or
7934 static variable in Tor should have its own documentation now.
7937 Changes in version 0.2.1.9-alpha - 2008-12-25
7938 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
7940 o New directory authorities:
7941 - gabelmoo (the authority run by Karsten Loesing) now has a new
7945 - Never use a connection with a mismatched address to extend a
7946 circuit, unless that connection is canonical. A canonical
7947 connection is one whose address is authenticated by the router's
7948 identity key, either in a NETINFO cell or in a router descriptor.
7949 - Avoid a possible memory corruption bug when receiving hidden service
7950 descriptors. Bugfix on 0.2.1.6-alpha.
7953 - Fix a logic error that would automatically reject all but the first
7954 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
7955 part of bug 813/868. Bug spotted by coderman.
7956 - When a stream at an exit relay is in state "resolving" or
7957 "connecting" and it receives an "end" relay cell, the exit relay
7958 would silently ignore the end cell and not close the stream. If
7959 the client never closes the circuit, then the exit relay never
7960 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
7962 - When we can't initialize DNS because the network is down, do not
7963 automatically stop Tor from starting. Instead, retry failed
7964 dns_init() every 10 minutes, and change the exit policy to reject
7965 *:* until one succeeds. Fixes bug 691.
7968 - Give a better error message when an overzealous init script says
7969 "sudo -u username tor --user username". Makes Bug 882 easier for
7971 - When a directory authority gives us a new guess for our IP address,
7972 log which authority we used. Hopefully this will help us debug
7973 the recent complaints about bad IP address guesses.
7974 - Detect svn revision properly when we're using git-svn.
7975 - Try not to open more than one descriptor-downloading connection
7976 to an authority at once. This should reduce load on directory
7977 authorities. Fixes bug 366.
7978 - Add cross-certification to newly generated certificates, so that
7979 a signing key is enough information to look up a certificate.
7980 Partial implementation of proposal 157.
7981 - Start serving certificates by <identity digest, signing key digest>
7982 pairs. Partial implementation of proposal 157.
7983 - Clients now never report any stream end reason except 'MISC'.
7984 Implements proposal 148.
7985 - On platforms with a maximum syslog string length, truncate syslog
7986 messages to that length ourselves, rather than relying on the
7987 system to do it for us.
7988 - Optimize out calls to time(NULL) that occur for every IO operation,
7989 or for every cell. On systems where time() is a slow syscall,
7990 this fix will be slightly helpful.
7991 - Exit servers can now answer resolve requests for ip6.arpa addresses.
7992 - When we download a descriptor that we then immediately (as
7993 a directory authority) reject, do not retry downloading it right
7994 away. Should save some bandwidth on authorities. Fix for bug
7995 888. Patch by Sebastian Hahn.
7996 - When a download gets us zero good descriptors, do not notify
7997 Tor that new directory information has arrived.
7998 - Avoid some nasty corner cases in the logic for marking connections
7999 as too old or obsolete or noncanonical for circuits. Partial
8002 o Minor features (controller):
8003 - New CONSENSUS_ARRIVED event to note when a new consensus has
8004 been fetched and validated.
8005 - When we realize that another process has modified our cached
8006 descriptors file, print out a more useful error message rather
8007 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8008 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8009 controllers to prevent SIGHUP from reloading the
8010 configuration. Fixes bug 856.
8013 - Resume using the correct "REASON=" stream when telling the
8014 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8015 - When a canonical connection appears later in our internal list
8016 than a noncanonical one for a given OR ID, always use the
8017 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8019 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8020 seconds. Warn the user if lower values are given in the
8021 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8022 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8023 user if lower values are given in the configuration. Bugfix on
8024 0.1.1.17-rc. Patch by Sebastian.
8025 - Fix a race condition when freeing keys shared between main thread
8026 and CPU workers that could result in a memory leak. Bugfix on
8027 0.1.0.1-rc. Fixes bug 889.
8029 o Minor bugfixes (hidden services):
8030 - Do not throw away existing introduction points on SIGHUP (bugfix on
8031 0.0.6pre1); also, do not stall hidden services because we're
8032 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8033 by John Brooks. Patch by Karsten. Fixes bug 874.
8034 - Fix a memory leak when we decline to add a v2 rendezvous
8035 descriptor to the cache because we already had a v0 descriptor
8036 with the same ID. Bugfix on 0.2.0.18-alpha.
8038 o Deprecated and removed features:
8039 - RedirectExits has been removed. It was deprecated since
8041 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8042 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8043 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8045 o Code simplifications and refactoring:
8046 - Rename the confusing or_is_obsolete field to the more appropriate
8047 is_bad_for_new_circs, and move it to or_connection_t where it
8049 - Move edge-only flags from connection_t to edge_connection_t: not
8050 only is this better coding, but on machines of plausible alignment,
8051 it should save 4-8 bytes per connection_t. "Every little bit helps."
8052 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8053 for consistency; keep old option working for backward compatibility.
8054 - Simplify the code for finding connections to use for a circuit.
8057 Changes in version 0.2.1.8-alpha - 2008-12-08
8058 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8059 builds better on unusual platforms like Solaris and old OS X, and
8060 fixes a variety of other issues.
8063 - New DirPortFrontPage option that takes an html file and publishes
8064 it as "/" on the DirPort. Now relay operators can provide a
8065 disclaimer without needing to set up a separate webserver. There's
8066 a sample disclaimer in contrib/tor-exit-notice.html.
8069 - When the client is choosing entry guards, now it selects at most
8070 one guard from a given relay family. Otherwise we could end up with
8071 all of our entry points into the network run by the same operator.
8072 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8075 - Fix a DOS opportunity during the voting signature collection process
8076 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8077 - Fix a possible segfault when establishing an exit connection. Bugfix
8081 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8083 - Made Tor a little less aggressive about deleting expired
8084 certificates. Partial fix for bug 854.
8085 - Stop doing unaligned memory access that generated bus errors on
8086 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8087 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8088 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8089 - Make USR2 log-level switch take effect immediately. Bugfix on
8091 - If one win32 nameserver fails to get added, continue adding the
8092 rest, and don't automatically fail.
8093 - Use fcntl() for locking when flock() is not available. Should fix
8094 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8095 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8096 could make gcc generate non-functional binary search code. Bugfix
8098 - Build correctly on platforms without socklen_t.
8099 - Avoid potential crash on internal error during signature collection.
8100 Fixes bug 864. Patch from rovv.
8101 - Do not use C's stdio library for writing to log files. This will
8102 improve logging performance by a minute amount, and will stop
8103 leaking fds when our disk is full. Fixes bug 861.
8104 - Stop erroneous use of O_APPEND in cases where we did not in fact
8105 want to re-seek to the end of a file before every last write().
8106 - Correct handling of possible malformed authority signing key
8107 certificates with internal signature types. Fixes bug 880. Bugfix
8109 - Fix a hard-to-trigger resource leak when logging credential status.
8113 - Directory mirrors no longer fetch the v1 directory or
8114 running-routers files. They are obsolete, and nobody asks for them
8115 anymore. This is the first step to making v1 authorities obsolete.
8117 o Minor features (controller):
8118 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8122 Changes in version 0.2.0.32 - 2008-11-20
8123 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8124 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8125 a smaller security flaw that might allow an attacker to access local
8126 services, further improves hidden service performance, and fixes a
8127 variety of other issues.
8130 - The "User" and "Group" config options did not clear the
8131 supplementary group entries for the Tor process. The "User" option
8132 is now more robust, and we now set the groups to the specified
8133 user's primary group. The "Group" option is now ignored. For more
8134 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8135 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8136 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8137 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8138 consistently obeyed: if an exit relay refuses a stream because its
8139 exit policy doesn't allow it, we would remember what IP address
8140 the relay said the destination address resolves to, even if it's
8141 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8144 - Fix a DOS opportunity during the voting signature collection process
8145 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8147 o Major bugfixes (hidden services):
8148 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8149 we were failing the whole hidden service request when the v0
8150 descriptor fetch fails, even if the v2 fetch is still pending and
8151 might succeed. Similarly, if the last v2 fetch fails, we were
8152 failing the whole hidden service request even if a v0 fetch is
8153 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8154 - When extending a circuit to a hidden service directory to upload a
8155 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8156 requests failed, because the router descriptor has not been
8157 downloaded yet. In these cases, do not attempt to upload the
8158 rendezvous descriptor, but wait until the router descriptor is
8159 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8160 descriptor from a hidden service directory for which the router
8161 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8165 - Fix several infrequent memory leaks spotted by Coverity.
8166 - When testing for libevent functions, set the LDFLAGS variable
8167 correctly. Found by Riastradh.
8168 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8169 bootstrapping with tunneled directory connections. Bugfix on
8170 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8171 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8172 and we know that server B rejects most-but-not all connections to
8173 port 80, we would previously reject the connection. Now, we assume
8174 the user knows what they were asking for. Fixes bug 752. Bugfix
8175 on 0.0.9rc5. Diagnosed by BarkerJr.
8176 - If we overrun our per-second write limits a little, count this as
8177 having used up our write allocation for the second, and choke
8178 outgoing directory writes. Previously, we had only counted this when
8179 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8180 Bugfix on 0.2.0.x (??).
8181 - Remove the old v2 directory authority 'lefkada' from the default
8182 list. It has been gone for many months.
8183 - Stop doing unaligned memory access that generated bus errors on
8184 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8185 - Make USR2 log-level switch take effect immediately. Bugfix on
8188 o Minor bugfixes (controller):
8189 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8190 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8193 Changes in version 0.2.1.7-alpha - 2008-11-08
8194 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8195 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8196 a smaller security flaw that might allow an attacker to access local
8197 services, adds better defense against DNS poisoning attacks on exit
8198 relays, further improves hidden service performance, and fixes a
8199 variety of other issues.
8202 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8203 consistently obeyed: if an exit relay refuses a stream because its
8204 exit policy doesn't allow it, we would remember what IP address
8205 the relay said the destination address resolves to, even if it's
8206 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8207 - The "User" and "Group" config options did not clear the
8208 supplementary group entries for the Tor process. The "User" option
8209 is now more robust, and we now set the groups to the specified
8210 user's primary group. The "Group" option is now ignored. For more
8211 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8212 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8213 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8214 - Do not use or believe expired v3 authority certificates. Patch
8215 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8218 - Now NodeFamily and MyFamily config options allow spaces in
8219 identity fingerprints, so it's easier to paste them in.
8220 Suggested by Lucky Green.
8221 - Implement the 0x20 hack to better resist DNS poisoning: set the
8222 case on outgoing DNS requests randomly, and reject responses that do
8223 not match the case correctly. This logic can be disabled with the
8224 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8225 of servers that do not reliably preserve case in replies. See
8226 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8228 - Preserve case in replies to DNSPort requests in order to support
8229 the 0x20 hack for resisting DNS poisoning attacks.
8231 o Hidden service performance improvements:
8232 - When the client launches an introduction circuit, retry with a
8233 new circuit after 30 seconds rather than 60 seconds.
8234 - Launch a second client-side introduction circuit in parallel
8235 after a delay of 15 seconds (based on work by Christian Wilms).
8236 - Hidden services start out building five intro circuits rather
8237 than three, and when the first three finish they publish a service
8238 descriptor using those. Now we publish our service descriptor much
8239 faster after restart.
8242 - Minor fix in the warning messages when you're having problems
8243 bootstrapping; also, be more forgiving of bootstrap problems when
8244 we're still making incremental progress on a given bootstrap phase.
8245 - When we're choosing an exit node for a circuit, and we have
8246 no pending streams, choose a good general exit rather than one that
8247 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8248 - Send a valid END cell back when a client tries to connect to a
8249 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8250 840. Patch from rovv.
8251 - If a broken client asks a non-exit router to connect somewhere,
8252 do not even do the DNS lookup before rejecting the connection.
8253 Fixes another case of bug 619. Patch from rovv.
8254 - Fix another case of assuming, when a specific exit is requested,
8255 that we know more than the user about what hosts it allows.
8256 Fixes another case of bug 752. Patch from rovv.
8257 - Check which hops rendezvous stream cells are associated with to
8258 prevent possible guess-the-streamid injection attacks from
8259 intermediate hops. Fixes another case of bug 446. Based on patch
8261 - Avoid using a negative right-shift when comparing 32-bit
8262 addresses. Possible fix for bug 845 and bug 811.
8263 - Make the assert_circuit_ok() function work correctly on circuits that
8264 have already been marked for close.
8265 - Fix read-off-the-end-of-string error in unit tests when decoding
8266 introduction points.
8267 - Fix uninitialized size field for memory area allocation: may improve
8268 memory performance during directory parsing.
8269 - Treat duplicate certificate fetches as failures, so that we do
8270 not try to re-fetch an expired certificate over and over and over.
8271 - Do not say we're fetching a certificate when we'll in fact skip it
8272 because of a pending download.
8275 Changes in version 0.2.1.6-alpha - 2008-09-30
8276 Tor 0.2.1.6-alpha further improves performance and robustness of
8277 hidden services, starts work on supporting per-country relay selection,
8278 and fixes a variety of smaller issues.
8281 - Implement proposal 121: make it possible to build hidden services
8282 that only certain clients are allowed to connect to. This is
8283 enforced at several points, so that unauthorized clients are unable
8284 to send INTRODUCE cells to the service, or even (depending on the
8285 type of authentication) to learn introduction points. This feature
8286 raises the bar for certain kinds of active attacks against hidden
8287 services. Code by Karsten Loesing.
8288 - Relays now store and serve v2 hidden service descriptors by default,
8289 i.e., the new default value for HidServDirectoryV2 is 1. This is
8290 the last step in proposal 114, which aims to make hidden service
8291 lookups more reliable.
8292 - Start work to allow node restrictions to include country codes. The
8293 syntax to exclude nodes in a country with country code XX is
8294 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8295 refinement to decide what config options should take priority if
8296 you ask to both use a particular node and exclude it.
8297 - Allow ExitNodes list to include IP ranges and country codes, just
8298 like the Exclude*Nodes lists. Patch from Robert Hogan.
8301 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8302 Tor to fail to start if you had it configured to use a bridge
8303 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8304 - When extending a circuit to a hidden service directory to upload a
8305 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8306 requests failed, because the router descriptor had not been
8307 downloaded yet. In these cases, we now wait until the router
8308 descriptor is downloaded, and then retry. Likewise, clients
8309 now skip over a hidden service directory if they don't yet have
8310 its router descriptor, rather than futilely requesting it and
8311 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8313 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8314 we were failing the whole hidden service request when the v0
8315 descriptor fetch fails, even if the v2 fetch is still pending and
8316 might succeed. Similarly, if the last v2 fetch fails, we were
8317 failing the whole hidden service request even if a v0 fetch is
8318 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8319 - DNS replies need to have names matching their requests, but
8320 these names should be in the questions section, not necessarily
8321 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8324 - Update to the "September 1 2008" ip-to-country file.
8325 - Allow ports 465 and 587 in the default exit policy again. We had
8326 rejected them in 0.1.0.15, because back in 2005 they were commonly
8327 misconfigured and ended up as spam targets. We hear they are better
8328 locked down these days.
8329 - Use a lockfile to make sure that two Tor processes are not
8330 simultaneously running with the same datadir.
8331 - Serve the latest v3 networkstatus consensus via the control
8332 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8333 - Better logging about stability/reliability calculations on directory
8335 - Drop the requirement to have an open dir port for storing and
8336 serving v2 hidden service descriptors.
8337 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8338 help debug WFU and MTBF calculations.
8339 - Implement most of Proposal 152: allow specialized servers to permit
8340 single-hop circuits, and clients to use those servers to build
8341 single-hop circuits when using a specialized controller. Patch
8342 from Josh Albrecht. Resolves feature request 768.
8343 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8344 people find host:port too confusing.
8345 - Make TrackHostExit mappings expire a while after their last use, not
8346 after their creation. Patch from Robert Hogan.
8347 - Provide circuit purposes along with circuit events to the controller.
8350 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8352 - Fixed some memory leaks -- some quite frequent, some almost
8353 impossible to trigger -- based on results from Coverity.
8354 - When testing for libevent functions, set the LDFLAGS variable
8355 correctly. Found by Riastradh.
8356 - Fix an assertion bug in parsing policy-related options; possible fix
8358 - Catch and report a few more bootstrapping failure cases when Tor
8359 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8360 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8361 bootstrapping with tunneled directory connections. Bugfix on
8362 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8363 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8364 and we know that server B rejects most-but-not all connections to
8365 port 80, we would previously reject the connection. Now, we assume
8366 the user knows what they were asking for. Fixes bug 752. Bugfix
8367 on 0.0.9rc5. Diagnosed by BarkerJr.
8368 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8369 service directories if they have no advertised dir port. Bugfix
8371 - If we overrun our per-second write limits a little, count this as
8372 having used up our write allocation for the second, and choke
8373 outgoing directory writes. Previously, we had only counted this when
8374 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8375 Bugfix on 0.2.0.x (??).
8376 - Avoid a "0 divided by 0" calculation when calculating router uptime
8377 at directory authorities. Bugfix on 0.2.0.8-alpha.
8378 - Make DNS resolved controller events into "CLOSED", not
8379 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8381 - Fix a bug where an unreachable relay would establish enough
8382 reachability testing circuits to do a bandwidth test -- if
8383 we already have a connection to the middle hop of the testing
8384 circuit, then it could establish the last hop by using the existing
8385 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8386 circuits no longer use entry guards in 0.2.1.3-alpha.
8387 - If we have correct permissions on $datadir, we complain to stdout
8388 and fail to start. But dangerous permissions on
8389 $datadir/cached-status/ would cause us to open a log and complain
8390 there. Now complain to stdout and fail to start in both cases. Fixes
8391 bug 820, reported by seeess.
8392 - Remove the old v2 directory authority 'lefkada' from the default
8393 list. It has been gone for many months.
8395 o Code simplifications and refactoring:
8396 - Revise the connection_new functions so that a more typesafe variant
8397 exists. This will work better with Coverity, and let us find any
8398 actual mistakes we're making here.
8399 - Refactor unit testing logic so that dmalloc can be used sensibly
8400 with unit tests to check for memory leaks.
8401 - Move all hidden-service related fields from connection and circuit
8402 structure to substructures: this way they won't eat so much memory.
8405 Changes in version 0.2.0.31 - 2008-09-03
8406 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8407 a big bug we're seeing where in rare cases traffic from one Tor stream
8408 gets mixed into another stream, and fixes a variety of smaller issues.
8411 - Make sure that two circuits can never exist on the same connection
8412 with the same circuit ID, even if one is marked for close. This
8413 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8414 - Relays now reject risky extend cells: if the extend cell includes
8415 a digest of all zeroes, or asks to extend back to the relay that
8416 sent the extend cell, tear down the circuit. Ideas suggested
8418 - If not enough of our entry guards are available so we add a new
8419 one, we might use the new one even if it overlapped with the
8420 current circuit's exit relay (or its family). Anonymity bugfix
8421 pointed out by rovv.
8424 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8425 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8426 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8427 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8428 - Pick size of default geoip filename string correctly on windows.
8429 Fixes bug 806. Bugfix on 0.2.0.30.
8430 - Make the autoconf script accept the obsolete --with-ssl-dir
8431 option as an alias for the actually-working --with-openssl-dir
8432 option. Fix the help documentation to recommend --with-openssl-dir.
8433 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8434 - When using the TransPort option on OpenBSD, and using the User
8435 option to change UID and drop privileges, make sure to open
8436 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8437 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8438 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8439 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8440 on the client side when connecting to a hidden service. Bugfix
8441 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8442 - When closing an application-side connection because its circuit is
8443 getting torn down, generate the stream event correctly. Bugfix on
8444 0.1.2.x. Anonymous patch.
8447 Changes in version 0.2.1.5-alpha - 2008-08-31
8448 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8449 in a lot of the infrastructure for adding authorization to hidden
8450 services, lays the groundwork for having clients read their load
8451 balancing information out of the networkstatus consensus rather than
8452 the individual router descriptors, addresses two potential anonymity
8453 issues, and fixes a variety of smaller issues.
8456 - Convert many internal address representations to optionally hold
8458 - Generate and accept IPv6 addresses in many protocol elements.
8459 - Make resolver code handle nameservers located at ipv6 addresses.
8460 - Begin implementation of proposal 121 ("Client authorization for
8461 hidden services"): configure hidden services with client
8462 authorization, publish descriptors for them, and configure
8463 authorization data for hidden services at clients. The next
8464 step is to actually access hidden services that perform client
8466 - More progress toward proposal 141: Network status consensus
8467 documents and votes now contain bandwidth information for each
8468 router and a summary of that router's exit policy. Eventually this
8469 will be used by clients so that they do not have to download every
8470 known descriptor before building circuits.
8472 o Major bugfixes (on 0.2.0.x and before):
8473 - When sending CREATED cells back for a given circuit, use a 64-bit
8474 connection ID to find the right connection, rather than an addr:port
8475 combination. Now that we can have multiple OR connections between
8476 the same ORs, it is no longer possible to use addr:port to uniquely
8477 identify a connection.
8478 - Relays now reject risky extend cells: if the extend cell includes
8479 a digest of all zeroes, or asks to extend back to the relay that
8480 sent the extend cell, tear down the circuit. Ideas suggested
8482 - If not enough of our entry guards are available so we add a new
8483 one, we might use the new one even if it overlapped with the
8484 current circuit's exit relay (or its family). Anonymity bugfix
8485 pointed out by rovv.
8488 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8489 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8490 - When using the TransPort option on OpenBSD, and using the User
8491 option to change UID and drop privileges, make sure to open /dev/pf
8492 before dropping privileges. Fixes bug 782. Patch from Christopher
8493 Davis. Bugfix on 0.1.2.1-alpha.
8494 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8495 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8496 - Add a missing safe_str() call for a debug log message.
8497 - Use 64 bits instead of 32 bits for connection identifiers used with
8498 the controller protocol, to greatly reduce risk of identifier reuse.
8499 - Make the autoconf script accept the obsolete --with-ssl-dir
8500 option as an alias for the actually-working --with-openssl-dir
8501 option. Fix the help documentation to recommend --with-openssl-dir.
8502 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8505 - Rate-limit too-many-sockets messages: when they happen, they happen
8506 a lot. Resolves bug 748.
8507 - Resist DNS poisoning a little better by making sure that names in
8508 answer sections match.
8509 - Print the SOCKS5 error message string as well as the error code
8510 when a tor-resolve request fails. Patch from Jacob.
8513 Changes in version 0.2.1.4-alpha - 2008-08-04
8514 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8517 - The address part of exit policies was not correctly written
8518 to router descriptors. This generated router descriptors that failed
8519 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8521 - Tor triggered a false assert when extending a circuit to a relay
8522 but we already have a connection open to that relay. Noticed by
8523 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8526 - Fix a hidden service logging bug: in some edge cases, the router
8527 descriptor of a previously picked introduction point becomes
8528 obsolete and we need to give up on it rather than continually
8529 complaining that it has become obsolete. Observed by xiando. Bugfix
8533 - Take out the TestVia config option, since it was a workaround for
8534 a bug that was fixed in Tor 0.1.1.21.
8537 Changes in version 0.2.1.3-alpha - 2008-08-03
8538 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8539 infinite-length circuit attacks (see proposal 110); fixes a bug that
8540 might cause exit relays to corrupt streams they send back; allows
8541 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8542 ExcludeExitNodes config options; and fixes a big pile of bugs.
8544 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8545 - Send a bootstrap problem "warn" event on the first problem if the
8546 reason is NO_ROUTE (that is, our network is down).
8549 - Implement most of proposal 110: The first K cells to be sent
8550 along a circuit are marked as special "early" cells; only K "early"
8551 cells will be allowed. Once this code is universal, we can block
8552 certain kinds of DOS attack by requiring that EXTEND commands must
8553 be sent using an "early" cell.
8556 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8557 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8558 on the client side when connecting to a hidden service. Bugfix
8559 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8560 - Ensure that two circuits can never exist on the same connection
8561 with the same circuit ID, even if one is marked for close. This
8562 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8565 - When relays do their initial bandwidth measurement, don't limit
8566 to just our entry guards for the test circuits. Otherwise we tend
8567 to have multiple test circuits going through a single entry guard,
8568 which makes our bandwidth test less accurate. Fixes part of bug 654;
8569 patch contributed by Josh Albrecht.
8570 - Add an ExcludeExitNodes option so users can list a set of nodes
8571 that should be be excluded from the exit node position, but
8572 allowed elsewhere. Implements proposal 151.
8573 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8574 ExcludeNodes and ExcludeExitNodes lists.
8575 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8576 be more efficient. Formerly it was quadratic in the number of
8577 servers; now it should be linear. Fixes bug 509.
8578 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8579 and n_conn_id_digest fields into a separate structure that's
8580 only needed when the circuit has not yet attached to an n_conn.
8583 - Change the contrib/tor.logrotate script so it makes the new
8584 logs as "_tor:_tor" rather than the default, which is generally
8585 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8586 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8587 warnings (occasionally), but it can also cause the compiler to
8588 eliminate error-checking code. Suggested by Peter Gutmann.
8589 - When a hidden service is giving up on an introduction point candidate
8590 that was not included in the last published rendezvous descriptor,
8591 don't reschedule publication of the next descriptor. Fixes bug 763.
8593 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8594 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8595 and nobody claims to be using them. Fixes bug 754. Bugfix on
8596 0.1.0.1-rc. Patch from Christian Wilms.
8597 - Fix a small alignment and memory-wasting bug on buffer chunks.
8600 o Minor bugfixes (controller):
8601 - When closing an application-side connection because its circuit
8602 is getting torn down, generate the stream event correctly.
8603 Bugfix on 0.1.2.x. Anonymous patch.
8606 - Remove all backward-compatibility code to support relays running
8607 versions of Tor so old that they no longer work at all on the
8611 Changes in version 0.2.0.30 - 2008-07-15
8613 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8614 warnings (occasionally), but it can also cause the compiler to
8615 eliminate error-checking code. Suggested by Peter Gutmann.
8618 Changes in version 0.2.0.29-rc - 2008-07-08
8619 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8620 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8623 - If you have more than one bridge but don't know their keys,
8624 you would only launch a request for the descriptor of the first one
8625 on your list. (Tor considered launching requests for the others, but
8626 found that it already had a connection on the way for $0000...0000
8627 so it didn't open another.) Bugfix on 0.2.0.x.
8628 - If you have more than one bridge but don't know their keys, and the
8629 connection to one of the bridges failed, you would cancel all
8630 pending bridge connections. (After all, they all have the same
8631 digest.) Bugfix on 0.2.0.x.
8632 - When a hidden service was trying to establish an introduction point,
8633 and Tor had built circuits preemptively for such purposes, we
8634 were ignoring all the preemptive circuits and launching a new one
8635 instead. Bugfix on 0.2.0.14-alpha.
8636 - When a hidden service was trying to establish an introduction point,
8637 and Tor *did* manage to reuse one of the preemptively built
8638 circuits, it didn't correctly remember which one it used,
8639 so it asked for another one soon after, until there were no
8640 more preemptive circuits, at which point it launched one from
8641 scratch. Bugfix on 0.0.9.x.
8642 - Make directory servers include the X-Your-Address-Is: http header in
8643 their responses even for begin_dir conns. Now clients who only
8644 ever use begin_dir connections still have a way to learn their IP
8645 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8648 - Fix a macro/CPP interaction that was confusing some compilers:
8649 some GCCs don't like #if/#endif pairs inside macro arguments.
8651 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8652 Fixes bug 704; fix from Steven Murdoch.
8653 - When opening /dev/null in finish_daemonize(), do not pass the
8654 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8655 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8656 - Correctly detect transparent proxy support on Linux hosts that
8657 require in.h to be included before netfilter_ipv4.h. Patch
8659 - Disallow session resumption attempts during the renegotiation
8660 stage of the v2 handshake protocol. Clients should never be trying
8661 session resumption at this point, but apparently some did, in
8662 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8663 found by Geoff Goodell.
8666 Changes in version 0.2.1.2-alpha - 2008-06-20
8667 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8668 make it easier to set up your own private Tor network; fixes several
8669 big bugs with using more than one bridge relay; fixes a big bug with
8670 offering hidden services quickly after Tor starts; and uses a better
8671 API for reporting potential bootstrapping problems to the controller.
8674 - New TestingTorNetwork config option to allow adjustment of
8675 previously constant values that, while reasonable, could slow
8676 bootstrapping. Implements proposal 135. Patch from Karsten.
8679 - If you have more than one bridge but don't know their digests,
8680 you would only learn a request for the descriptor of the first one
8681 on your list. (Tor considered launching requests for the others, but
8682 found that it already had a connection on the way for $0000...0000
8683 so it didn't open another.) Bugfix on 0.2.0.x.
8684 - If you have more than one bridge but don't know their digests,
8685 and the connection to one of the bridges failed, you would cancel
8686 all pending bridge connections. (After all, they all have the
8687 same digest.) Bugfix on 0.2.0.x.
8688 - When establishing a hidden service, introduction points that
8689 originate from cannibalized circuits are completely ignored and not
8690 included in rendezvous service descriptors. This might be another
8691 reason for delay in making a hidden service available. Bugfix
8692 from long ago (0.0.9.x?)
8695 - Allow OpenSSL to use dynamic locks if it wants.
8696 - When building a consensus, do not include routers that are down.
8697 This will cut down 30% to 40% on consensus size. Implements
8699 - In directory authorities' approved-routers files, allow
8700 fingerprints with or without space.
8701 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8702 controller can query our current bootstrap state in case it attaches
8703 partway through and wants to catch up.
8704 - Send an initial "Starting" bootstrap status event, so we have a
8705 state to start out in.
8708 - Asking for a conditional consensus at .../consensus/<fingerprints>
8709 would crash a dirserver if it did not already have a
8710 consensus. Bugfix on 0.2.1.1-alpha.
8711 - Clean up some macro/CPP interactions: some GCC versions don't like
8712 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8715 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8716 - Directory authorities shouldn't complain about bootstrapping
8717 problems just because they do a lot of reachability testing and
8718 some of the connection attempts fail.
8719 - Start sending "count" and "recommendation" key/value pairs in
8720 bootstrap problem status events, so the controller can hear about
8721 problems even before Tor decides they're worth reporting for sure.
8722 - If you're using bridges, generate "bootstrap problem" warnings
8723 as soon as you run out of working bridges, rather than waiting
8724 for ten failures -- which will never happen if you have less than
8726 - If we close our OR connection because there's been a circuit
8727 pending on it for too long, we were telling our bootstrap status
8728 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8731 Changes in version 0.2.1.1-alpha - 2008-06-13
8732 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8733 were making the Tor process bloat especially on Linux; makes our TLS
8734 handshake blend in better; sends "bootstrap phase" status events to
8735 the controller, so it can keep the user informed of progress (and
8736 problems) fetching directory information and establishing circuits;
8737 and adds a variety of smaller features.
8740 - More work on making our TLS handshake blend in: modify the list
8741 of ciphers advertised by OpenSSL in client mode to even more
8742 closely resemble a common web browser. We cheat a little so that
8743 we can advertise ciphers that the locally installed OpenSSL doesn't
8745 - Start sending "bootstrap phase" status events to the controller,
8746 so it can keep the user informed of progress fetching directory
8747 information and establishing circuits. Also inform the controller
8748 if we think we're stuck at a particular bootstrap phase. Implements
8750 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8751 cross-platform entropy collection again. We used to use it, then
8752 stopped using it because of a bug that could crash systems that
8753 called RAND_poll when they had a lot of fds open. It looks like the
8754 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8755 at startup, and to call RAND_poll() when we reseed later only if
8756 we have a non-buggy OpenSSL version.
8759 - When we choose to abandon a new entry guard because we think our
8760 older ones might be better, close any circuits pending on that
8761 new entry guard connection. This fix should make us recover much
8762 faster when our network is down and then comes back. Bugfix on
8763 0.1.2.8-beta; found by lodger.
8765 o Memory fixes and improvements:
8766 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8767 to avoid unused RAM in buffer chunks and memory pools.
8768 - Speed up parsing and cut down on memory fragmentation by using
8769 stack-style allocations for parsing directory objects. Previously,
8770 this accounted for over 40% of allocations from within Tor's code
8771 on a typical directory cache.
8772 - Use a Bloom filter rather than a digest-based set to track which
8773 descriptors we need to keep around when we're cleaning out old
8774 router descriptors. This speeds up the computation significantly,
8775 and may reduce fragmentation.
8776 - Reduce the default smartlist size from 32 to 16; it turns out that
8777 most smartlists hold around 8-12 elements tops.
8778 - Make dumpstats() log the fullness and size of openssl-internal
8780 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8781 patch to their OpenSSL, turn it on to save memory on servers. This
8782 patch will (with any luck) get included in a mainline distribution
8784 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8785 compress cells, which are basically all encrypted, compressed,
8789 - Stop reloading the router list from disk for no reason when we
8790 run out of reachable directory mirrors. Once upon a time reloading
8791 it would set the 'is_running' flag back to 1 for them. It hasn't
8792 done that for a long time.
8793 - In very rare situations new hidden service descriptors were
8794 published earlier than 30 seconds after the last change to the
8795 service. (We currently think that a hidden service descriptor
8796 that's been stable for 30 seconds is worth publishing.)
8799 - Allow separate log levels to be configured for different logging
8800 domains. For example, this allows one to log all notices, warnings,
8801 or errors, plus all memory management messages of level debug or
8802 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
8803 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
8804 and stop using a warning that had become unfixably verbose under
8806 - New --hush command-line option similar to --quiet. While --quiet
8807 disables all logging to the console on startup, --hush limits the
8808 output to messages of warning and error severity.
8809 - Servers support a new URL scheme for consensus downloads that
8810 allows the client to specify which authorities are trusted.
8811 The server then only sends the consensus if the client will trust
8812 it. Otherwise a 404 error is sent back. Clients use this
8813 new scheme when the server supports it (meaning it's running
8814 0.2.1.1-alpha or later). Implements proposal 134.
8815 - New configure/torrc options (--enable-geoip-stats,
8816 DirRecordUsageByCountry) to record how many IPs we've served
8817 directory info to in each country code, how many status documents
8818 total we've sent to each country code, and what share of the total
8819 directory requests we should expect to see.
8820 - Use the TLS1 hostname extension to more closely resemble browser
8822 - Lots of new unit tests.
8823 - Add a macro to implement the common pattern of iterating through
8824 two parallel lists in lockstep.
8827 Changes in version 0.2.0.28-rc - 2008-06-13
8828 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
8829 performance bug, and fixes a bunch of smaller bugs.
8832 - Fix a bug where, when we were choosing the 'end stream reason' to
8833 put in our relay end cell that we send to the exit relay, Tor
8834 clients on Windows were sometimes sending the wrong 'reason'. The
8835 anonymity problem is that exit relays may be able to guess whether
8836 the client is running Windows, thus helping partition the anonymity
8837 set. Down the road we should stop sending reasons to exit relays,
8838 or otherwise prevent future versions of this bug.
8841 - While setting up a hidden service, some valid introduction circuits
8842 were overlooked and abandoned. This might be the reason for
8843 the long delay in making a hidden service available. Bugfix on
8847 - Update to the "June 9 2008" ip-to-country file.
8848 - Run 'make test' as part of 'make dist', so we stop releasing so
8849 many development snapshots that fail their unit tests.
8852 - When we're checking if we have enough dir info for each relay
8853 to begin establishing circuits, make sure that we actually have
8854 the descriptor listed in the consensus, not just any descriptor.
8856 - Bridge relays no longer print "xx=0" in their extrainfo document
8857 for every single country code in the geoip db. Bugfix on
8859 - Only warn when we fail to load the geoip file if we were planning to
8860 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
8861 - If we change our MaxAdvertisedBandwidth and then reload torrc,
8862 Tor won't realize it should publish a new relay descriptor. Fixes
8863 bug 688, reported by mfr. Bugfix on 0.1.2.x.
8864 - When we haven't had any application requests lately, don't bother
8865 logging that we have expired a bunch of descriptors. Bugfix
8867 - Make relay cells written on a connection count as non-padding when
8868 tracking how long a connection has been in use. Bugfix on
8869 0.2.0.1-alpha. Spotted by lodger.
8870 - Fix unit tests in 0.2.0.27-rc.
8871 - Fix compile on Windows.
8874 Changes in version 0.2.0.27-rc - 2008-06-03
8875 Tor 0.2.0.27-rc adds a few features we left out of the earlier
8876 release candidates. In particular, we now include an IP-to-country
8877 GeoIP database, so controllers can easily look up what country a
8878 given relay is in, and so bridge relays can give us some sanitized
8879 summaries about which countries are making use of bridges. (See proposal
8880 126-geoip-fetching.txt for details.)
8883 - Include an IP-to-country GeoIP file in the tarball, so bridge
8884 relays can report sanitized summaries of the usage they're seeing.
8887 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
8888 Robert Hogan. Fixes the first part of bug 681.
8889 - Make bridge authorities never serve extrainfo docs.
8890 - Add support to detect Libevent versions in the 1.4.x series
8892 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
8893 - Include a new contrib/tor-exit-notice.html file that exit relay
8894 operators can put on their website to help reduce abuse queries.
8897 - When tunneling an encrypted directory connection, and its first
8898 circuit fails, do not leave it unattached and ask the controller
8899 to deal. Fixes the second part of bug 681.
8900 - Make bridge authorities correctly expire old extrainfo documents
8904 Changes in version 0.2.0.26-rc - 2008-05-13
8905 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
8906 in Debian's OpenSSL packages. All users running any 0.2.0.x version
8907 should upgrade, whether they're running Debian or not.
8909 o Major security fixes:
8910 - Use new V3 directory authority keys on the tor26, gabelmoo, and
8911 moria1 V3 directory authorities. The old keys were generated with
8912 a vulnerable version of Debian's OpenSSL package, and must be
8913 considered compromised. Other authorities' keys were not generated
8914 with an affected version of OpenSSL.
8917 - List authority signatures as "unrecognized" based on DirServer
8918 lines, not on cert cache. Bugfix on 0.2.0.x.
8921 - Add a new V3AuthUseLegacyKey option to make it easier for
8922 authorities to change their identity keys if they have to.
8925 Changes in version 0.2.0.25-rc - 2008-04-23
8926 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
8929 - Remember to initialize threading before initializing logging.
8930 Otherwise, many BSD-family implementations will crash hard on
8931 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
8934 - Authorities correctly free policies on bad servers on
8935 exit. Fixes bug 672. Bugfix on 0.2.0.x.
8938 Changes in version 0.2.0.24-rc - 2008-04-22
8939 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
8940 v3 directory authority, makes relays with dynamic IP addresses and no
8941 DirPort notice more quickly when their IP address changes, fixes a few
8942 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
8944 o New directory authorities:
8945 - Take lefkada out of the list of v3 directory authorities, since
8946 it has been down for months.
8947 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
8951 - Detect address changes more quickly on non-directory mirror
8952 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
8954 o Minor features (security):
8955 - Reject requests for reverse-dns lookup of names that are in
8956 a private address space. Patch from lodger.
8957 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
8960 o Minor bugfixes (crashes):
8961 - Avoid a rare assert that can trigger when Tor doesn't have much
8962 directory information yet and it tries to fetch a v2 hidden
8963 service descriptor. Fixes bug 651, reported by nwf.
8964 - Initialize log mutex before initializing dmalloc. Otherwise,
8965 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
8966 - Use recursive pthread mutexes in order to avoid deadlock when
8967 logging debug-level messages to a controller. Bug spotted by nwf,
8968 bugfix on 0.2.0.16-alpha.
8970 o Minor bugfixes (resource management):
8971 - Keep address policies from leaking memory: start their refcount
8972 at 1, not 2. Bugfix on 0.2.0.16-alpha.
8973 - Free authority certificates on exit, so they don't look like memory
8974 leaks. Bugfix on 0.2.0.19-alpha.
8975 - Free static hashtables for policy maps and for TLS connections on
8976 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
8977 - Avoid allocating extra space when computing consensuses on 64-bit
8978 platforms. Bug spotted by aakova.
8980 o Minor bugfixes (misc):
8981 - Do not read the configuration file when we've only been told to
8982 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
8983 based on patch from Sebastian Hahn.
8984 - Exit relays that are used as a client can now reach themselves
8985 using the .exit notation, rather than just launching an infinite
8986 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
8987 - When attempting to open a logfile fails, tell us why.
8988 - Fix a dumb bug that was preventing us from knowing that we should
8989 preemptively build circuits to handle expected directory requests.
8990 Fixes bug 660. Bugfix on 0.1.2.x.
8991 - Warn less verbosely about clock skew from netinfo cells from
8992 untrusted sources. Fixes bug 663.
8993 - Make controller stream events for DNS requests more consistent,
8994 by adding "new stream" events for DNS requests, and removing
8995 spurious "stream closed" events" for cached reverse resolves.
8996 Patch from mwenge. Fixes bug 646.
8997 - Correctly notify one-hop connections when a circuit build has
8998 failed. Possible fix for bug 669. Found by lodger.
9001 Changes in version 0.2.0.23-rc - 2008-03-24
9002 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9003 makes bootstrapping faster if the first directory mirror you contact
9004 is down. The bundles also include the new Vidalia 0.1.2 release.
9007 - When a tunneled directory request is made to a directory server
9008 that's down, notice after 30 seconds rather than 120 seconds. Also,
9009 fail any begindir streams that are pending on it, so they can
9010 retry elsewhere. This was causing multi-minute delays on bootstrap.
9013 Changes in version 0.2.0.22-rc - 2008-03-18
9014 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9015 enables encrypted directory connections by default for non-relays, fixes
9016 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9017 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9020 - Enable encrypted directory connections by default for non-relays,
9021 so censor tools that block Tor directory connections based on their
9022 plaintext patterns will no longer work. This means Tor works in
9023 certain censored countries by default again.
9026 - Make sure servers always request certificates from clients during
9027 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9028 - Do not enter a CPU-eating loop when a connection is closed in
9029 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9030 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9031 - Fix assertion failure that could occur when a blocked circuit
9032 became unblocked, and it had pending client DNS requests. Bugfix
9033 on 0.2.0.1-alpha. Fixes bug 632.
9035 o Minor bugfixes (on 0.1.2.x):
9036 - Generate "STATUS_SERVER" events rather than misspelled
9037 "STATUS_SEVER" events. Caught by mwenge.
9038 - When counting the number of bytes written on a TLS connection,
9039 look at the BIO actually used for writing to the network, not
9040 at the BIO used (sometimes) to buffer data for the network.
9041 Looking at different BIOs could result in write counts on the
9042 order of ULONG_MAX. Fixes bug 614.
9043 - On Windows, correctly detect errors when listing the contents of
9044 a directory. Fix from lodger.
9046 o Minor bugfixes (on 0.2.0.x):
9047 - Downgrade "sslv3 alert handshake failure" message to INFO.
9048 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9049 left BandwidthRate and BandwidthBurst at the default, we would be
9050 silently limited by those defaults. Now raise them to match the
9051 RelayBandwidth* values.
9052 - Fix the SVK version detection logic to work correctly on a branch.
9053 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9054 CPUs. Fixes bug 625.
9055 - Logging functions now check that the passed severity is sane.
9056 - Use proper log levels in the testsuite call of
9057 get_interface_address6().
9058 - When using a nonstandard malloc, do not use the platform values for
9059 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9060 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9062 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9063 - Avoid double-marked-for-close warning when certain kinds of invalid
9064 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9065 for bug 617. Bugfix on 0.2.0.1-alpha.
9066 - Make sure that the "NULL-means-reject *:*" convention is followed by
9067 all the policy manipulation functions, avoiding some possible crash
9068 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9069 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9070 actually works, and doesn't warn about every single reverse lookup.
9071 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9074 - Only log guard node status when guard node status has changed.
9075 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9076 make "INFO" 75% less verbose.
9079 Changes in version 0.2.0.21-rc - 2008-03-02
9080 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9081 makes Tor work well with Vidalia again, fixes a rare assert bug,
9082 and fixes a pair of more minor bugs. The bundles also include Vidalia
9083 0.1.0 and Torbutton 1.1.16.
9086 - The control port should declare that it requires password auth
9087 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9088 bugfix on 0.2.0.20-rc. Fixes bug 615.
9089 - Downgrade assert in connection_buckets_decrement() to a log message.
9090 This may help us solve bug 614, and in any case will make its
9091 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9092 - We were sometimes miscounting the number of bytes read from the
9093 network, causing our rate limiting to not be followed exactly.
9094 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9097 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9098 OpenSSL versions should have been working fine. Diagnosis and patch
9099 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9100 Bugfix on 0.2.0.20-rc.
9103 Changes in version 0.2.0.20-rc - 2008-02-24
9104 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9105 makes more progress towards normalizing Tor's TLS handshake, makes
9106 hidden services work better again, helps relays bootstrap if they don't
9107 know their IP address, adds optional support for linking in openbsd's
9108 allocator or tcmalloc, allows really fast relays to scale past 15000
9109 sockets, and fixes a bunch of minor bugs reported by Veracode.
9112 - Enable the revised TLS handshake based on the one designed by
9113 Steven Murdoch in proposal 124, as revised in proposal 130. It
9114 includes version negotiation for OR connections as described in
9115 proposal 105. The new handshake is meant to be harder for censors
9116 to fingerprint, and it adds the ability to detect certain kinds of
9117 man-in-the-middle traffic analysis attacks. The version negotiation
9118 feature will allow us to improve Tor's link protocol more safely
9120 - Choose which bridge to use proportional to its advertised bandwidth,
9121 rather than uniformly at random. This should speed up Tor for
9122 bridge users. Also do this for people who set StrictEntryNodes.
9123 - When a TrackHostExits-chosen exit fails too many times in a row,
9124 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9127 - Resolved problems with (re-)fetching hidden service descriptors.
9128 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9130 - If we only ever used Tor for hidden service lookups or posts, we
9131 would stop building circuits and start refusing connections after
9132 24 hours, since we falsely believed that Tor was dormant. Reported
9133 by nwf; bugfix on 0.1.2.x.
9134 - Servers that don't know their own IP address should go to the
9135 authorities for their first directory fetch, even if their DirPort
9136 is off or if they don't know they're reachable yet. This will help
9137 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9138 - When counting the number of open sockets, count not only the number
9139 of sockets we have received from the socket() call, but also
9140 the number we've gotten from accept() and socketpair(). This bug
9141 made us fail to count all sockets that we were using for incoming
9142 connections. Bugfix on 0.2.0.x.
9143 - Fix code used to find strings within buffers, when those strings
9144 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9145 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9146 - Add a new __HashedControlSessionPassword option for controllers
9147 to use for one-off session password hashes that shouldn't get
9148 saved to disk by SAVECONF --- Vidalia users were accumulating a
9149 pile of HashedControlPassword lines in their torrc files, one for
9150 each time they had restarted Tor and then clicked Save. Make Tor
9151 automatically convert "HashedControlPassword" to this new option but
9152 only when it's given on the command line. Partial fix for bug 586.
9154 o Minor features (performance):
9155 - Tune parameters for cell pool allocation to minimize amount of
9157 - Add OpenBSD malloc code from phk as an optional malloc
9158 replacement on Linux: some glibc libraries do very poorly
9159 with Tor's memory allocation patterns. Pass
9160 --enable-openbsd-malloc to get the replacement malloc code.
9161 - Add a --with-tcmalloc option to the configure script to link
9162 against tcmalloc (if present). Does not yet search for
9163 non-system include paths.
9164 - Stop imposing an arbitrary maximum on the number of file descriptors
9165 used for busy servers. Bug reported by Olaf Selke; patch from
9168 o Minor features (other):
9169 - When SafeLogging is disabled, log addresses along with all TLS
9171 - When building with --enable-gcc-warnings, check for whether Apple's
9172 warning "-Wshorten-64-to-32" is available.
9173 - Add a --passphrase-fd argument to the tor-gencert command for
9176 o Minor bugfixes (memory leaks and code problems):
9177 - We were leaking a file descriptor if Tor started with a zero-length
9178 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9179 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9181 - We were comparing the raw BridgePassword entry with a base64'ed
9182 version of it, when handling a "/tor/networkstatus-bridges"
9183 directory request. Now compare correctly. Noticed by Veracode.
9184 - Recover from bad tracked-since value in MTBF-history file.
9186 - Alter the code that tries to recover from unhandled write
9187 errors, to not try to flush onto a socket that's given us
9188 unhandled errors. Bugfix on 0.1.2.x.
9189 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9190 tup. Bugfix on 0.2.0.3-alpha.
9192 o Minor bugfixes (other):
9193 - If we have an extra-info document for our server, always make
9194 it available on the control port, even if we haven't gotten
9195 a copy of it from an authority yet. Patch from mwenge.
9196 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9197 - Directory mirrors no longer include a guess at the client's IP
9198 address if the connection appears to be coming from the same /24
9199 network; it was producing too many wrong guesses.
9200 - Make the new hidden service code respect the SafeLogging setting.
9201 Bugfix on 0.2.0.x. Patch from Karsten.
9202 - When starting as an authority, do not overwrite all certificates
9203 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9204 - If we're trying to flush the last bytes on a connection (for
9205 example, when answering a directory request), reset the
9206 time-to-give-up timeout every time we manage to write something
9207 on the socket. Bugfix on 0.1.2.x.
9208 - Change the behavior of "getinfo status/good-server-descriptor"
9209 so it doesn't return failure when any authority disappears.
9210 - Even though the man page said that "TrackHostExits ." should
9211 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9212 - Report TLS "zero return" case as a "clean close" and "IO error"
9213 as a "close". Stop calling closes "unexpected closes": existing
9214 Tors don't use SSL_close(), so having a connection close without
9215 the TLS shutdown handshake is hardly unexpected.
9216 - Send NAMESERVER_STATUS messages for a single failed nameserver
9219 o Code simplifications and refactoring:
9220 - Remove the tor_strpartition function: its logic was confused,
9221 and it was only used for one thing that could be implemented far
9225 Changes in version 0.2.0.19-alpha - 2008-02-09
9226 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9227 handshake, makes path selection for relays more secure and IP address
9228 guessing more robust, and generally fixes a lot of bugs in preparation
9229 for calling the 0.2.0 branch stable.
9232 - Do not include recognizeable strings in the commonname part of
9233 Tor's x509 certificates.
9236 - If we're a relay, avoid picking ourselves as an introduction point,
9237 a rendezvous point, or as the final hop for internal circuits. Bug
9238 reported by taranis and lodger. Bugfix on 0.1.2.x.
9239 - Patch from "Andrew S. Lists" to catch when we contact a directory
9240 mirror at IP address X and he says we look like we're coming from
9241 IP address X. Bugfix on 0.1.2.x.
9243 o Minor features (security):
9244 - Be more paranoid about overwriting sensitive memory on free(),
9245 as a defensive programming tactic to ensure forward secrecy.
9247 o Minor features (directory authority):
9248 - Actually validate the options passed to AuthDirReject,
9249 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9250 - Reject router descriptors with out-of-range bandwidthcapacity or
9251 bandwidthburst values.
9253 o Minor features (controller):
9254 - Reject controller commands over 1MB in length. This keeps rogue
9255 processes from running us out of memory.
9257 o Minor features (misc):
9258 - Give more descriptive well-formedness errors for out-of-range
9259 hidden service descriptor/protocol versions.
9260 - Make memory debugging information describe more about history
9261 of cell allocation, so we can help reduce our memory use.
9263 o Deprecated features (controller):
9264 - The status/version/num-versioning and status/version/num-concurring
9265 GETINFO options are no longer useful in the v3 directory protocol:
9266 treat them as deprecated, and warn when they're used.
9269 - When our consensus networkstatus has been expired for a while, stop
9270 being willing to build circuits using it. Fixes bug 401. Bugfix
9272 - Directory caches now fetch certificates from all authorities
9273 listed in a networkstatus consensus, even when they do not
9274 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9275 - When connecting to a bridge without specifying its key, insert
9276 the connection into the identity-to-connection map as soon as
9277 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9278 - Detect versions of OS X where malloc_good_size() is present in the
9279 library but never actually declared. Resolves bug 587. Bugfix
9281 - Stop incorrectly truncating zlib responses to directory authority
9282 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9283 - Stop recommending that every server operator send mail to tor-ops.
9284 Resolves bug 597. Bugfix on 0.1.2.x.
9285 - Don't trigger an assert if we start a directory authority with a
9286 private IP address (like 127.0.0.1).
9287 - Avoid possible failures when generating a directory with routers
9288 with over-long versions strings, or too many flags set. Bugfix
9290 - If an attempt to launch a DNS resolve request over the control
9291 port fails because we have overrun the limit on the number of
9292 connections, tell the controller that the request has failed.
9293 - Avoid using too little bandwidth when our clock skips a few
9294 seconds. Bugfix on 0.1.2.x.
9295 - Fix shell error when warning about missing packages in configure
9296 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9297 - Do not become confused when receiving a spurious VERSIONS-like
9298 cell from a confused v1 client. Bugfix on 0.2.0.x.
9299 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9300 introduction points for a hidden service have failed. Patch from
9301 Karsten Loesing. Bugfix on 0.2.0.x.
9303 o Code simplifications and refactoring:
9304 - Remove some needless generality from cpuworker code, for improved
9306 - Stop overloading the circuit_t.onionskin field for both "onionskin
9307 from a CREATE cell that we are waiting for a cpuworker to be
9308 assigned" and "onionskin from an EXTEND cell that we are going to
9309 send to an OR as soon as we are connected". Might help with bug 600.
9310 - Add an in-place version of aes_crypt() so that we can avoid doing a
9311 needless memcpy() call on each cell payload.
9314 Changes in version 0.2.0.18-alpha - 2008-01-25
9315 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9316 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9317 that can warn or reject connections to ports generally associated with
9318 vulnerable-plaintext protocols.
9320 o New directory authorities:
9321 - Set up dannenberg (run by CCC) as the sixth v3 directory
9325 - Fix a major memory leak when attempting to use the v2 TLS
9326 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9327 - We accidentally enabled the under-development v2 TLS handshake
9328 code, which was causing log entries like "TLS error while
9329 renegotiating handshake". Disable it again. Resolves bug 590.
9330 - We were computing the wrong Content-Length: header for directory
9331 responses that need to be compressed on the fly, causing clients
9332 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9336 - Avoid going directly to the directory authorities even if you're a
9337 relay, if you haven't found yourself reachable yet or if you've
9338 decided not to advertise your dirport yet. Addresses bug 556.
9339 - If we've gone 12 hours since our last bandwidth check, and we
9340 estimate we have less than 50KB bandwidth capacity but we could
9341 handle more, do another bandwidth test.
9342 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9343 Tor can warn and/or refuse connections to ports commonly used with
9344 vulnerable-plaintext protocols. Currently we warn on ports 23,
9345 109, 110, and 143, but we don't reject any.
9348 - When we setconf ClientOnly to 1, close any current OR and Dir
9349 listeners. Reported by mwenge.
9350 - When we get a consensus that's been signed by more people than
9351 we expect, don't log about it; it's not a big deal. Reported
9355 - Don't answer "/tor/networkstatus-bridges" directory requests if
9356 the request isn't encrypted.
9357 - Make "ClientOnly 1" config option disable directory ports too.
9358 - Patches from Karsten Loesing to make v2 hidden services more
9359 robust: work even when there aren't enough HSDir relays available;
9360 retry when a v2 rend desc fetch fails; but don't retry if we
9361 already have a usable v0 rend desc.
9364 Changes in version 0.2.0.17-alpha - 2008-01-17
9365 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9368 - Make the tor-gencert man page get included correctly in the tarball.
9371 Changes in version 0.2.0.16-alpha - 2008-01-17
9372 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9373 Loesing, and generally cleans up a lot of features and minor bugs.
9375 o New directory authorities:
9376 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9379 o Major performance improvements:
9380 - Switch our old ring buffer implementation for one more like that
9381 used by free Unix kernels. The wasted space in a buffer with 1mb
9382 of data will now be more like 8k than 1mb. The new implementation
9383 also avoids realloc();realloc(); patterns that can contribute to
9384 memory fragmentation.
9387 - Configuration files now accept C-style strings as values. This
9388 helps encode characters not allowed in the current configuration
9389 file format, such as newline or #. Addresses bug 557.
9390 - Although we fixed bug 539 (where servers would send HTTP status 503
9391 responses _and_ send a body too), there are still servers out
9392 there that haven't upgraded. Therefore, make clients parse such
9393 bodies when they receive them.
9394 - When we're not serving v2 directory information, there is no reason
9395 to actually keep any around. Remove the obsolete files and directory
9396 on startup if they are very old and we aren't going to serve them.
9398 o Minor performance improvements:
9399 - Reference-count and share copies of address policy entries; only 5%
9400 of them were actually distinct.
9401 - Never walk through the list of logs if we know that no log is
9402 interested in a given message.
9405 - When an authority has not signed a consensus, do not try to
9406 download a nonexistent "certificate with key 00000000". Bugfix
9407 on 0.2.0.x. Fixes bug 569.
9408 - Fix a rare assert error when we're closing one of our threads:
9409 use a mutex to protect the list of logs, so we never write to the
9410 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9411 bug 575, which is kind of the revenge of bug 222.
9412 - Patch from Karsten Loesing to complain less at both the client
9413 and the relay when a relay used to have the HSDir flag but doesn't
9414 anymore, and we try to upload a hidden service descriptor.
9415 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9417 - Do not try to download missing certificates until we have tried
9418 to check our fallback consensus. Fixes bug 583.
9419 - Make bridges round reported GeoIP stats info up to the nearest
9420 estimate, not down. Now we can distinguish between "0 people from
9421 this country" and "1 person from this country".
9422 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9423 - Avoid possible segfault if key generation fails in
9424 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9425 - Avoid segfault in the case where a badly behaved v2 versioning
9426 directory sends a signed networkstatus with missing client-versions.
9428 - Avoid segfaults on certain complex invocations of
9429 router_get_by_hexdigest(). Bugfix on 0.1.2.
9430 - Correct bad index on array access in parse_http_time(). Bugfix
9432 - Fix possible bug in vote generation when server versions are present
9433 but client versions are not.
9434 - Fix rare bug on REDIRECTSTREAM control command when called with no
9435 port set: it could erroneously report an error when none had
9437 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9438 compressing large objects and find ourselves with more than 4k
9439 left over. Bugfix on 0.2.0.
9440 - Fix a small memory leak when setting up a hidden service.
9441 - Fix a few memory leaks that could in theory happen under bizarre
9443 - Fix an assert if we post a general-purpose descriptor via the
9444 control port but that descriptor isn't mentioned in our current
9445 network consensus. Bug reported by Jon McLachlan; bugfix on
9448 o Minor features (controller):
9449 - Get NS events working again. Patch from tup.
9450 - The GETCONF command now escapes and quotes configuration values
9451 that don't otherwise fit into the torrc file.
9452 - The SETCONF command now handles quoted values correctly.
9454 o Minor features (directory authorities):
9455 - New configuration options to override default maximum number of
9456 servers allowed on a single IP address. This is important for
9457 running a test network on a single host.
9458 - Actually implement the -s option to tor-gencert.
9459 - Add a manual page for tor-gencert.
9461 o Minor features (bridges):
9462 - Bridge authorities no longer serve bridge descriptors over
9463 unencrypted connections.
9465 o Minor features (other):
9466 - Add hidden services and DNSPorts to the list of things that make
9467 Tor accept that it has running ports. Change starting Tor with no
9468 ports from a fatal error to a warning; we might change it back if
9469 this turns out to confuse anybody. Fixes bug 579.
9472 Changes in version 0.1.2.19 - 2008-01-17
9473 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9474 exit policy a little bit more conservative so it's safer to run an
9475 exit relay on a home system, and fixes a variety of smaller issues.
9478 - Exit policies now reject connections that are addressed to a
9479 relay's public (external) IP address too, unless
9480 ExitPolicyRejectPrivate is turned off. We do this because too
9481 many relays are running nearby to services that trust them based
9485 - When the clock jumps forward a lot, do not allow the bandwidth
9486 buckets to become negative. Fixes bug 544.
9487 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9488 on every successful resolve. Reported by Mike Perry.
9489 - Purge old entries from the "rephist" database and the hidden
9490 service descriptor database even when DirPort is zero.
9491 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9492 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9493 crashing or mis-answering these requests.
9494 - When we decide to send a 503 response to a request for servers, do
9495 not then also send the server descriptors: this defeats the whole
9496 purpose. Fixes bug 539.
9499 - Changing the ExitPolicyRejectPrivate setting should cause us to
9500 rebuild our server descriptor.
9501 - Fix handling of hex nicknames when answering controller requests for
9502 networkstatus by name, or when deciding whether to warn about
9503 unknown routers in a config option. (Patch from mwenge.)
9504 - Fix a couple of hard-to-trigger autoconf problems that could result
9505 in really weird results on platforms whose sys/types.h files define
9506 nonstandard integer types.
9507 - Don't try to create the datadir when running --verify-config or
9508 --hash-password. Resolves bug 540.
9509 - If we were having problems getting a particular descriptor from the
9510 directory caches, and then we learned about a new descriptor for
9511 that router, we weren't resetting our failure count. Reported
9513 - Although we fixed bug 539 (where servers would send HTTP status 503
9514 responses _and_ send a body too), there are still servers out there
9515 that haven't upgraded. Therefore, make clients parse such bodies
9516 when they receive them.
9517 - Run correctly on systems where rlim_t is larger than unsigned long.
9518 This includes some 64-bit systems.
9519 - Run correctly on platforms (like some versions of OS X 10.5) where
9520 the real limit for number of open files is OPEN_FILES, not rlim_max
9521 from getrlimit(RLIMIT_NOFILES).
9522 - Avoid a spurious free on base64 failure.
9523 - Avoid segfaults on certain complex invocations of
9524 router_get_by_hexdigest().
9525 - Fix rare bug on REDIRECTSTREAM control command when called with no
9526 port set: it could erroneously report an error when none had
9530 Changes in version 0.2.0.15-alpha - 2007-12-25
9531 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9532 features added in 0.2.0.13-alpha.
9535 - Fix several remotely triggerable asserts based on DirPort requests
9536 for a v2 or v3 networkstatus object before we were prepared. This
9537 was particularly bad for 0.2.0.13 and later bridge relays, who
9538 would never have a v2 networkstatus and would thus always crash
9539 when used. Bugfixes on 0.2.0.x.
9540 - Estimate the v3 networkstatus size more accurately, rather than
9541 estimating it at zero bytes and giving it artificially high priority
9542 compared to other directory requests. Bugfix on 0.2.0.x.
9545 - Fix configure.in logic for cross-compilation.
9546 - When we load a bridge descriptor from the cache, and it was
9547 previously unreachable, mark it as retriable so we won't just
9548 ignore it. Also, try fetching a new copy immediately. Bugfixes
9550 - The bridge GeoIP stats were counting other relays, for example
9551 self-reachability and authority-reachability tests.
9554 - Support compilation to target iPhone; patch from cjacker huang.
9555 To build for iPhone, pass the --enable-iphone option to configure.
9558 Changes in version 0.2.0.14-alpha - 2007-12-23
9560 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9561 without a datadirectory from a previous Tor install. Reported
9563 - Fix a crash when we fetch a descriptor that turns out to be
9564 unexpected (it used to be in our networkstatus when we started
9565 fetching it, but it isn't in our current networkstatus), and we
9566 aren't using bridges. Bugfix on 0.2.0.x.
9567 - Fix a crash when accessing hidden services: it would work the first
9568 time you use a given introduction point for your service, but
9569 on subsequent requests we'd be using garbage memory. Fixed by
9570 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9571 - Fix a crash when we load a bridge descriptor from disk but we don't
9572 currently have a Bridge line for it in our torrc. Bugfix on
9576 - If bridge authorities set BridgePassword, they will serve a
9577 snapshot of known bridge routerstatuses from their DirPort to
9578 anybody who knows that password. Unset by default.
9581 - Make the unit tests build again.
9582 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9583 - Make PublishServerDescriptor default to 1, so the default doesn't
9584 have to change as we invent new directory protocol versions.
9585 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9586 be included unless sys/time.h is already included. Fixes
9587 bug 553. Bugfix on 0.2.0.x.
9588 - If we receive a general-purpose descriptor and then receive an
9589 identical bridge-purpose descriptor soon after, don't discard
9590 the next one as a duplicate.
9593 - If BridgeRelay is set to 1, then the default for
9594 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9595 - If the user sets RelayBandwidthRate but doesn't set
9596 RelayBandwidthBurst, then make them equal rather than erroring out.
9599 Changes in version 0.2.0.13-alpha - 2007-12-21
9600 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9601 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9604 o New directory authorities:
9605 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9609 - Only update guard status (usable / not usable) once we have
9610 enough directory information. This was causing us to always pick
9611 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9612 causing us to discard all our guards on startup if we hadn't been
9613 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9614 - Purge old entries from the "rephist" database and the hidden
9615 service descriptor databases even when DirPort is zero. Bugfix
9617 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9618 after opening a circuit -- even a relayed circuit. Bugfix on
9620 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9621 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9622 crashing or mis-answering these types of requests.
9623 - Relays were publishing their server descriptor to v1 and v2
9624 directory authorities, but they didn't try publishing to v3-only
9625 authorities. Fix this; and also stop publishing to v1 authorities.
9627 - When we were reading router descriptors from cache, we were ignoring
9628 the annotations -- so for example we were reading in bridge-purpose
9629 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9630 - When we decided to send a 503 response to a request for servers, we
9631 were then also sending the server descriptors: this defeats the
9632 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9635 - Bridge relays now behave like clients with respect to time
9636 intervals for downloading new consensus documents -- otherwise they
9637 stand out. Bridge users now wait until the end of the interval,
9638 so their bridge relay will be sure to have a new consensus document.
9639 - Three new config options (AlternateDirAuthority,
9640 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9641 user selectively replace the default directory authorities by type,
9642 rather than the all-or-nothing replacement that DirServer offers.
9643 - Tor can now be configured to read a GeoIP file from disk in one
9644 of two formats. This can be used by controllers to map IP addresses
9645 to countries. Eventually, it may support exit-by-country.
9646 - When possible, bridge relays remember which countries users
9647 are coming from, and report aggregate information in their
9648 extra-info documents, so that the bridge authorities can learn
9649 where Tor is blocked.
9650 - Bridge directory authorities now do reachability testing on the
9651 bridges they know. They provide router status summaries to the
9652 controller via "getinfo ns/purpose/bridge", and also dump summaries
9653 to a file periodically.
9654 - Stop fetching directory info so aggressively if your DirPort is
9655 on but your ORPort is off; stop fetching v2 dir info entirely.
9656 You can override these choices with the new FetchDirInfoEarly
9660 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9661 consensus documents when there are too many relays at a single
9662 IP address. Now clear it in v2 network status documents too, and
9663 also clear it in routerinfo_t when the relay is no longer listed
9664 in the relevant networkstatus document.
9665 - Don't crash if we get an unexpected value for the
9666 PublishServerDescriptor config option. Reported by Matt Edman;
9667 bugfix on 0.2.0.9-alpha.
9668 - Our new v2 hidden service descriptor format allows descriptors
9669 that have no introduction points. But Tor crashed when we tried
9670 to build a descriptor with no intro points (and it would have
9671 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9673 - Fix building with dmalloc 5.5.2 with glibc.
9674 - Reject uploaded descriptors and extrainfo documents if they're
9675 huge. Otherwise we'll cache them all over the network and it'll
9676 clog everything up. Reported by Aljosha Judmayer.
9677 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9678 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9679 - When the DANGEROUS_VERSION controller status event told us we're
9680 running an obsolete version, it used the string "OLD" to describe
9681 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9682 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9683 - If we can't expand our list of entry guards (e.g. because we're
9684 using bridges or we have StrictEntryNodes set), don't mark relays
9685 down when they fail a directory request. Otherwise we're too quick
9686 to mark all our entry points down. Bugfix on 0.1.2.x.
9687 - Fix handling of hex nicknames when answering controller requests for
9688 networkstatus by name, or when deciding whether to warn about unknown
9689 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9690 - Fix a couple of hard-to-trigger autoconf problems that could result
9691 in really weird results on platforms whose sys/types.h files define
9692 nonstandard integer types. Bugfix on 0.1.2.x.
9693 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9694 - Don't crash on name lookup when we have no current consensus. Fixes
9695 bug 538; bugfix on 0.2.0.x.
9696 - Only Tors that want to mirror the v2 directory info should
9697 create the "cached-status" directory in their datadir. (All Tors
9698 used to create it.) Bugfix on 0.2.0.9-alpha.
9699 - Directory authorities should only automatically download Extra Info
9700 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9703 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9704 consumers. (We already do this on HUP.)
9705 - Authorities and caches fetch the v2 networkstatus documents
9706 less often, now that v3 is encouraged.
9707 - Add a new config option BridgeRelay that specifies you want to
9708 be a bridge relay. Right now the only difference is that it makes
9709 you answer begin_dir requests, and it makes you cache dir info,
9710 even if your DirPort isn't on.
9711 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9712 ask about source, timestamp of arrival, purpose, etc. We need
9713 something like this to help Vidalia not do GeoIP lookups on bridge
9715 - Allow multiple HashedControlPassword config lines, to support
9716 multiple controller passwords.
9717 - Authorities now decide whether they're authoritative for a given
9718 router based on the router's purpose.
9719 - New config options AuthDirBadDir and AuthDirListBadDirs for
9720 authorities to mark certain relays as "bad directories" in the
9721 networkstatus documents. Also supports the "!baddir" directive in
9722 the approved-routers file.
9725 Changes in version 0.2.0.12-alpha - 2007-11-16
9726 This twelfth development snapshot fixes some more build problems as
9727 well as a few minor bugs.
9730 - Make it build on OpenBSD again. Patch from tup.
9731 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9732 package-building for Red Hat, OS X, etc.
9734 o Minor bugfixes (on 0.1.2.x):
9735 - Changing the ExitPolicyRejectPrivate setting should cause us to
9736 rebuild our server descriptor.
9738 o Minor bugfixes (on 0.2.0.x):
9739 - When we're lacking a consensus, don't try to perform rendezvous
9740 operations. Reported by Karsten Loesing.
9741 - Fix a small memory leak whenever we decide against using a
9742 newly picked entry guard. Reported by Mike Perry.
9743 - When authorities detected more than two relays running on the same
9744 IP address, they were clearing all the status flags but forgetting
9745 to clear the "hsdir" flag. So clients were being told that a
9746 given relay was the right choice for a v2 hsdir lookup, yet they
9747 never had its descriptor because it was marked as 'not running'
9749 - If we're trying to fetch a bridge descriptor and there's no way
9750 the bridge authority could help us (for example, we don't know
9751 a digest, or there is no bridge authority), don't be so eager to
9752 fall back to asking the bridge authority.
9753 - If we're using bridges or have strictentrynodes set, and our
9754 chosen exit is in the same family as all our bridges/entry guards,
9755 then be flexible about families.
9758 - When we negotiate a v2 link-layer connection (not yet implemented),
9759 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9760 negotiated a v1 connection for their next step. Initial code for
9764 Changes in version 0.2.0.11-alpha - 2007-11-12
9765 This eleventh development snapshot fixes some build problems with
9766 the previous snapshot. It also includes a more secure-by-default exit
9767 policy for relays, fixes an enormous memory leak for exit relays, and
9768 fixes another bug where servers were falling out of the directory list.
9771 - Exit policies now reject connections that are addressed to a
9772 relay's public (external) IP address too, unless
9773 ExitPolicyRejectPrivate is turned off. We do this because too
9774 many relays are running nearby to services that trust them based
9775 on network address. Bugfix on 0.1.2.x.
9778 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9779 on every successful resolve. Reported by Mike Perry; bugfix
9781 - On authorities, never downgrade to old router descriptors simply
9782 because they're listed in the consensus. This created a catch-22
9783 where we wouldn't list a new descriptor because there was an
9784 old one in the consensus, and we couldn't get the new one in the
9785 consensus because we wouldn't list it. Possible fix for bug 548.
9786 Also, this might cause bug 543 to appear on authorities; if so,
9787 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
9789 o Packaging fixes on 0.2.0.10-alpha:
9790 - We were including instructions about what to do with the
9791 src/config/fallback-consensus file, but we weren't actually
9792 including it in the tarball. Disable all of that for now.
9795 - Allow people to say PreferTunnelledDirConns rather than
9796 PreferTunneledDirConns, for those alternate-spellers out there.
9799 - Don't reevaluate all the information from our consensus document
9800 just because we've downloaded a v2 networkstatus that we intend
9801 to cache. Fixes bug 545; bugfix on 0.2.0.x.
9804 Changes in version 0.2.0.10-alpha - 2007-11-10
9805 This tenth development snapshot adds a third v3 directory authority
9806 run by Mike Perry, adds most of Karsten Loesing's new hidden service
9807 descriptor format, fixes a bad crash bug and new bridge bugs introduced
9808 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
9809 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
9810 addresses many more minor issues.
9812 o New directory authorities:
9813 - Set up ides (run by Mike Perry) as the third v3 directory authority.
9816 - Allow tunnelled directory connections to ask for an encrypted
9817 "begin_dir" connection or an anonymized "uses a full Tor circuit"
9818 connection independently. Now we can make anonymized begin_dir
9819 connections for (e.g.) more secure hidden service posting and
9821 - More progress on proposal 114: code from Karsten Loesing to
9822 implement new hidden service descriptor format.
9823 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
9824 accommodate the growing number of servers that use the default
9825 and are reaching it.
9826 - Directory authorities use a new formula for selecting which nodes
9827 to advertise as Guards: they must be in the top 7/8 in terms of
9828 how long we have known about them, and above the median of those
9829 nodes in terms of weighted fractional uptime.
9830 - Make "not enough dir info yet" warnings describe *why* Tor feels
9831 it doesn't have enough directory info yet.
9834 - Stop servers from crashing if they set a Family option (or
9835 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
9837 - Make bridge users work again -- the move to v3 directories in
9838 0.2.0.9-alpha had introduced a number of bugs that made bridges
9839 no longer work for clients.
9840 - When the clock jumps forward a lot, do not allow the bandwidth
9841 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
9843 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
9844 - When the consensus lists a router descriptor that we previously were
9845 mirroring, but that we considered non-canonical, reload the
9846 descriptor as canonical. This fixes bug 543 where Tor servers
9847 would start complaining after a few days that they don't have
9848 enough directory information to build a circuit.
9849 - Consider replacing the current consensus when certificates arrive
9850 that make the pending consensus valid. Previously, we were only
9851 considering replacement when the new certs _didn't_ help.
9852 - Fix an assert error on startup if we didn't already have the
9853 consensus and certs cached in our datadirectory: we were caching
9854 the consensus in consensus_waiting_for_certs but then free'ing it
9856 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
9857 Request) if we need more v3 certs but we've already got pending
9858 requests for all of them.
9859 - Correctly back off from failing certificate downloads. Fixes
9861 - Authorities don't vote on the Running flag if they have been running
9862 for less than 30 minutes themselves. Fixes bug 547, where a newly
9863 started authority would vote that everyone was down.
9866 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
9867 it, it had no AES, and it hasn't seen any security patches since
9871 - Clients now hold circuitless TLS connections open for 1.5 times
9872 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
9873 rebuild a new circuit over them within that timeframe. Previously,
9874 they held them open only for KeepalivePeriod (5 minutes).
9875 - Use "If-Modified-Since" to avoid retrieving consensus
9876 networkstatuses that we already have.
9877 - When we have no consensus, check FallbackNetworkstatusFile (defaults
9878 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
9879 we start knowing some directory caches.
9880 - When we receive a consensus from the future, warn about skew.
9881 - Improve skew reporting: try to give the user a better log message
9882 about how skewed they are, and how much this matters.
9883 - When we have a certificate for an authority, believe that
9884 certificate's claims about the authority's IP address.
9885 - New --quiet command-line option to suppress the default console log.
9886 Good in combination with --hash-password.
9887 - Authorities send back an X-Descriptor-Not-New header in response to
9888 an accepted-but-discarded descriptor upload. Partially implements
9890 - Make the log message for "tls error. breaking." more useful.
9891 - Better log messages about certificate downloads, to attempt to
9892 track down the second incarnation of bug 546.
9894 o Minor features (bridges):
9895 - If bridge users set UpdateBridgesFromAuthority, but the digest
9896 they ask for is a 404 from the bridge authority, they now fall
9897 back to trying the bridge directly.
9898 - Bridges now use begin_dir to publish their server descriptor to
9899 the bridge authority, even when they haven't set TunnelDirConns.
9901 o Minor features (controller):
9902 - When reporting clock skew, and we know that the clock is _at least
9903 as skewed_ as some value, but we don't know the actual value,
9904 report the value as a "minimum skew."
9907 - Update linux-tor-prio.sh script to allow QoS based on the uid of
9908 the Tor process. Patch from Marco Bonetti with tweaks from Mike
9912 - Refuse to start if both ORPort and UseBridges are set. Bugfix
9913 on 0.2.0.x, suggested by Matt Edman.
9914 - Don't stop fetching descriptors when FetchUselessDescriptors is
9915 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
9916 reported by tup and ioerror.
9917 - Better log message on vote from unknown authority.
9918 - Don't log "Launching 0 request for 0 router" message.
9920 o Minor bugfixes (memory leaks):
9921 - Stop leaking memory every time we parse a v3 certificate. Bugfix
9923 - Stop leaking memory every time we load a v3 certificate. Bugfix
9924 on 0.2.0.1-alpha. Fixes bug 536.
9925 - Stop leaking a cached networkstatus on exit. Bugfix on
9927 - Stop leaking voter information every time we free a consensus.
9928 Bugfix on 0.2.0.3-alpha.
9929 - Stop leaking signed data every time we check a voter signature.
9930 Bugfix on 0.2.0.3-alpha.
9931 - Stop leaking a signature every time we fail to parse a consensus or
9932 a vote. Bugfix on 0.2.0.3-alpha.
9933 - Stop leaking v2_download_status_map on shutdown. Bugfix on
9935 - Stop leaking conn->nickname every time we make a connection to a
9936 Tor relay without knowing its expected identity digest (e.g. when
9937 using bridges). Bugfix on 0.2.0.3-alpha.
9939 - Minor bugfixes (portability):
9940 - Run correctly on platforms where rlim_t is larger than unsigned
9941 long, and/or where the real limit for number of open files is
9942 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
9943 particular, these may be needed for OS X 10.5.
9946 Changes in version 0.1.2.18 - 2007-10-28
9947 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
9948 hidden service introduction that were causing huge delays, and a big
9949 bug that was causing some servers to disappear from the network status
9950 lists for a few hours each day.
9952 o Major bugfixes (crashes):
9953 - If a connection is shut down abruptly because of something that
9954 happened inside connection_flushed_some(), do not call
9955 connection_finished_flushing(). Should fix bug 451:
9956 "connection_stop_writing: Assertion conn->write_event failed"
9957 Bugfix on 0.1.2.7-alpha.
9958 - Fix possible segfaults in functions called from
9959 rend_process_relay_cell().
9961 o Major bugfixes (hidden services):
9962 - Hidden services were choosing introduction points uniquely by
9963 hexdigest, but when constructing the hidden service descriptor
9964 they merely wrote the (potentially ambiguous) nickname.
9965 - Clients now use the v2 intro format for hidden service
9966 connections: they specify their chosen rendezvous point by identity
9967 digest rather than by (potentially ambiguous) nickname. These
9968 changes could speed up hidden service connections dramatically.
9970 o Major bugfixes (other):
9971 - Stop publishing a new server descriptor just because we get a
9972 HUP signal. This led (in a roundabout way) to some servers getting
9973 dropped from the networkstatus lists for a few hours each day.
9974 - When looking for a circuit to cannibalize, consider family as well
9975 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9976 circuit cannibalization).
9977 - When a router wasn't listed in a new networkstatus, we were leaving
9978 the flags for that router alone -- meaning it remained Named,
9979 Running, etc -- even though absence from the networkstatus means
9980 that it shouldn't be considered to exist at all anymore. Now we
9981 clear all the flags for routers that fall out of the networkstatus
9982 consensus. Fixes bug 529.
9985 - Don't try to access (or alter) the state file when running
9986 --list-fingerprint or --verify-config or --hash-password. Resolves
9988 - When generating information telling us how to extend to a given
9989 router, do not try to include the nickname if it is
9990 absent. Resolves bug 467.
9991 - Fix a user-triggerable segfault in expand_filename(). (There isn't
9992 a way to trigger this remotely.)
9993 - When sending a status event to the controller telling it that an
9994 OR address is reachable, set the port correctly. (Previously we
9995 were reporting the dir port.)
9996 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9997 command. Bugfix on 0.1.2.17.
9998 - When loading bandwidth history, do not believe any information in
9999 the future. Fixes bug 434.
10000 - When loading entry guard information, do not believe any information
10002 - When we have our clock set far in the future and generate an
10003 onion key, then re-set our clock to be correct, we should not stop
10004 the onion key from getting rotated.
10005 - On some platforms, accept() can return a broken address. Detect
10006 this more quietly, and deal accordingly. Fixes bug 483.
10007 - It's not actually an error to find a non-pending entry in the DNS
10008 cache when canceling a pending resolve. Don't log unless stuff
10009 is fishy. Resolves bug 463.
10010 - Don't reset trusted dir server list when we set a configuration
10011 option. Patch from Robert Hogan.
10012 - Don't try to create the datadir when running --verify-config or
10013 --hash-password. Resolves bug 540.
10016 Changes in version 0.2.0.9-alpha - 2007-10-24
10017 This ninth development snapshot switches clients to the new v3 directory
10018 system; allows servers to be listed in the network status even when they
10019 have the same nickname as a registered server; and fixes many other
10020 bugs including a big one that was causing some servers to disappear
10021 from the network status lists for a few hours each day.
10023 o Major features (directory system):
10024 - Clients now download v3 consensus networkstatus documents instead
10025 of v2 networkstatus documents. Clients and caches now base their
10026 opinions about routers on these consensus documents. Clients only
10027 download router descriptors listed in the consensus.
10028 - Authorities now list servers who have the same nickname as
10029 a different named server, but list them with a new flag,
10030 "Unnamed". Now we can list servers that happen to pick the same
10031 nickname as a server that registered two years ago and then
10032 disappeared. Partially implements proposal 122.
10033 - If the consensus lists a router as "Unnamed", the name is assigned
10034 to a different router: do not identify the router by that name.
10035 Partially implements proposal 122.
10036 - Authorities can now come to a consensus on which method to use to
10037 compute the consensus. This gives us forward compatibility.
10040 - Stop publishing a new server descriptor just because we HUP or
10041 when we find our DirPort to be reachable but won't actually publish
10042 it. New descriptors without any real changes are dropped by the
10043 authorities, and can screw up our "publish every 18 hours" schedule.
10045 - When a router wasn't listed in a new networkstatus, we were leaving
10046 the flags for that router alone -- meaning it remained Named,
10047 Running, etc -- even though absence from the networkstatus means
10048 that it shouldn't be considered to exist at all anymore. Now we
10049 clear all the flags for routers that fall out of the networkstatus
10050 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10051 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10052 extrainfo documents and then discard them immediately for not
10053 matching the latest router. Bugfix on 0.2.0.1-alpha.
10055 o Minor features (v3 directory protocol):
10056 - Allow tor-gencert to generate a new certificate without replacing
10058 - Allow certificates to include an address.
10059 - When we change our directory-cache settings, reschedule all voting
10060 and download operations.
10061 - Reattempt certificate downloads immediately on failure, as long as
10062 we haven't failed a threshold number of times yet.
10063 - Delay retrying consensus downloads while we're downloading
10064 certificates to verify the one we just got. Also, count getting a
10065 consensus that we already have (or one that isn't valid) as a failure,
10066 and count failing to get the certificates after 20 minutes as a
10068 - Build circuits and download descriptors even if our consensus is a
10069 little expired. (This feature will go away once authorities are
10072 o Minor features (router descriptor cache):
10073 - If we find a cached-routers file that's been sitting around for more
10074 than 28 days unmodified, then most likely it's a leftover from
10075 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10077 - When we (as a cache) download a descriptor because it was listed
10078 in a consensus, remember when the consensus was supposed to expire,
10079 and don't expire the descriptor until then.
10081 o Minor features (performance):
10082 - Call routerlist_remove_old_routers() much less often. This should
10083 speed startup, especially on directory caches.
10084 - Don't try to launch new descriptor downloads quite so often when we
10085 already have enough directory information to build circuits.
10086 - Base64 decoding was actually showing up on our profile when parsing
10087 the initial descriptor file; switch to an in-process all-at-once
10088 implementation that's about 3.5x times faster than calling out to
10091 o Minor features (compilation):
10092 - Detect non-ASCII platforms (if any still exist) and refuse to
10093 build there: some of our code assumes that 'A' is 65 and so on.
10095 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10096 - Make the "next period" votes into "current period" votes immediately
10097 after publishing the consensus; avoid a heisenbug that made them
10098 stick around indefinitely.
10099 - When we discard a vote as a duplicate, do not report this as
10101 - Treat missing v3 keys or certificates as an error when running as a
10102 v3 directory authority.
10103 - When we're configured to be a v3 authority, but we're only listed
10104 as a non-v3 authority in our DirServer line for ourself, correct
10106 - If an authority doesn't have a qualified hostname, just put
10107 its address in the vote. This fixes the problem where we referred to
10108 "moria on moria:9031."
10109 - Distinguish between detached signatures for the wrong period, and
10110 detached signatures for a divergent vote.
10111 - Fix a small memory leak when computing a consensus.
10112 - When there's no concensus, we were forming a vote every 30
10113 minutes, but writing the "valid-after" line in our vote based
10114 on our configured V3AuthVotingInterval: so unless the intervals
10115 matched up, we immediately rejected our own vote because it didn't
10116 start at the voting interval that caused us to construct a vote.
10118 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10119 - Delete unverified-consensus when the real consensus is set.
10120 - Consider retrying a consensus networkstatus fetch immediately
10121 after one fails: don't wait 60 seconds to notice.
10122 - When fetching a consensus as a cache, wait until a newer consensus
10123 should exist before trying to replace the current one.
10124 - Use a more forgiving schedule for retrying failed consensus
10125 downloads than for other types.
10127 o Minor bugfixes (other directory issues):
10128 - Correct the implementation of "download votes by digest." Bugfix on
10130 - Authorities no longer send back "400 you're unreachable please fix
10131 it" errors to Tor servers that aren't online all the time. We're
10132 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10134 o Minor bugfixes (controller):
10135 - Don't reset trusted dir server list when we set a configuration
10136 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10137 - Respond to INT and TERM SIGNAL commands before we execute the
10138 signal, in case the signal shuts us down. We had a patch in
10139 0.1.2.1-alpha that tried to do this by queueing the response on
10140 the connection's buffer before shutting down, but that really
10141 isn't the same thing at all. Bug located by Matt Edman.
10143 o Minor bugfixes (misc):
10144 - Correctly check for bad options to the "PublishServerDescriptor"
10145 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10146 - Stop leaking memory on failing case of base32_decode, and make
10147 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10148 - Don't try to download extrainfo documents when we're trying to
10149 fetch enough directory info to build a circuit: having enough
10150 info should get priority. Bugfix on 0.2.0.x.
10151 - Don't complain that "your server has not managed to confirm that its
10152 ports are reachable" if we haven't been able to build any circuits
10153 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10155 - Detect the reason for failing to mmap a descriptor file we just
10156 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10159 o Code simplifications and refactoring:
10160 - Remove support for the old bw_accounting file: we've been storing
10161 bandwidth accounting information in the state file since
10162 0.1.2.5-alpha. This may result in bandwidth accounting errors
10163 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10164 downgrade to 0.1.1.x or earlier.
10165 - New convenience code to locate a file within the DataDirectory.
10166 - Move non-authority functionality out of dirvote.c.
10167 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10168 so that they all take the same named flags.
10171 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10172 Unix users an easy way to script their Tor process (e.g. by
10173 adjusting bandwidth based on the time of the day).
10176 Changes in version 0.2.0.8-alpha - 2007-10-12
10177 This eighth development snapshot fixes a crash bug that's been bothering
10178 us since February 2007, lets bridge authorities store a list of bridge
10179 descriptors they've seen, gets v3 directory voting closer to working,
10180 starts caching v3 directory consensus documents on directory mirrors,
10181 and fixes a variety of smaller issues including some minor memory leaks.
10183 o Major features (router descriptor cache):
10184 - Store routers in a file called cached-descriptors instead of in
10185 cached-routers. Initialize cached-descriptors from cached-routers
10186 if the old format is around. The new format allows us to store
10187 annotations along with descriptors.
10188 - Use annotations to record the time we received each descriptor, its
10189 source, and its purpose.
10190 - Disable the SETROUTERPURPOSE controller command: it is now
10192 - Controllers should now specify cache=no or cache=yes when using
10193 the +POSTDESCRIPTOR command.
10194 - Bridge authorities now write bridge descriptors to disk, meaning
10195 we can export them to other programs and begin distributing them
10198 o Major features (directory authorities):
10199 - When a v3 authority is missing votes or signatures, it now tries
10201 - Directory authorities track weighted fractional uptime as well as
10202 weighted mean-time-between failures. WFU is suitable for deciding
10203 whether a node is "usually up", while MTBF is suitable for deciding
10204 whether a node is "likely to stay up." We need both, because
10205 "usually up" is a good requirement for guards, while "likely to
10206 stay up" is a good requirement for long-lived connections.
10208 o Major features (v3 directory system):
10209 - Caches now download v3 network status documents as needed,
10210 and download the descriptors listed in them.
10211 - All hosts now attempt to download and keep fresh v3 authority
10212 certificates, and re-attempt after failures.
10213 - More internal-consistency checks for vote parsing.
10215 o Major bugfixes (crashes):
10216 - If a connection is shut down abruptly because of something that
10217 happened inside connection_flushed_some(), do not call
10218 connection_finished_flushing(). Should fix bug 451. Bugfix on
10221 o Major bugfixes (performance):
10222 - Fix really bad O(n^2) performance when parsing a long list of
10223 routers: Instead of searching the entire list for an "extra-info "
10224 string which usually wasn't there, once for every routerinfo
10225 we read, just scan lines forward until we find one we like.
10227 - When we add data to a write buffer in response to the data on that
10228 write buffer getting low because of a flush, do not consider the
10229 newly added data as a candidate for immediate flushing, but rather
10230 make it wait until the next round of writing. Otherwise, we flush
10231 and refill recursively, and a single greedy TLS connection can
10232 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10234 o Minor features (v3 authority system):
10235 - Add more ways for tools to download the votes that lead to the
10237 - Send a 503 when low on bandwidth and a vote, consensus, or
10238 certificate is requested.
10239 - If-modified-since is now implemented properly for all kinds of
10240 certificate requests.
10242 o Minor bugfixes (network statuses):
10243 - Tweak the implementation of proposal 109 slightly: allow at most
10244 two Tor servers on the same IP address, except if it's the location
10245 of a directory authority, in which case allow five. Bugfix on
10248 o Minor bugfixes (controller):
10249 - When sending a status event to the controller telling it that an
10250 OR address is reachable, set the port correctly. (Previously we
10251 were reporting the dir port.) Bugfix on 0.1.2.x.
10253 o Minor bugfixes (v3 directory system):
10254 - Fix logic to look up a cert by its signing key digest. Bugfix on
10256 - Only change the reply to a vote to "OK" if it's not already
10257 set. This gets rid of annoying "400 OK" log messages, which may
10258 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10259 - When we get a valid consensus, recompute the voting schedule.
10260 - Base the valid-after time of a vote on the consensus voting
10261 schedule, not on our preferred schedule.
10262 - Make the return values and messages from signature uploads and
10263 downloads more sensible.
10264 - Fix a memory leak when serving votes and consensus documents, and
10265 another when serving certificates.
10267 o Minor bugfixes (performance):
10268 - Use a slightly simpler string hashing algorithm (copying Python's
10269 instead of Java's) and optimize our digest hashing algorithm to take
10270 advantage of 64-bit platforms and to remove some possibly-costly
10272 - Fix a minor memory leak whenever we parse guards from our state
10273 file. Bugfix on 0.2.0.7-alpha.
10274 - Fix a minor memory leak whenever we write out a file. Bugfix on
10276 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10277 command. Bugfix on 0.2.0.5-alpha.
10279 o Minor bugfixes (portability):
10280 - On some platforms, accept() can return a broken address. Detect
10281 this more quietly, and deal accordingly. Fixes bug 483.
10282 - Stop calling tor_strlower() on uninitialized memory in some cases.
10283 Bugfix in 0.2.0.7-alpha.
10285 o Minor bugfixes (usability):
10286 - Treat some 403 responses from directory servers as INFO rather than
10287 WARN-severity events.
10288 - It's not actually an error to find a non-pending entry in the DNS
10289 cache when canceling a pending resolve. Don't log unless stuff is
10290 fishy. Resolves bug 463.
10292 o Minor bugfixes (anonymity):
10293 - Never report that we've used more bandwidth than we're willing to
10294 relay: it leaks how much non-relay traffic we're using. Resolves
10296 - When looking for a circuit to cannibalize, consider family as well
10297 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10298 circuit cannibalization).
10300 o Code simplifications and refactoring:
10301 - Make a bunch of functions static. Remove some dead code.
10302 - Pull out about a third of the really big routerlist.c; put it in a
10303 new module, networkstatus.c.
10304 - Merge the extra fields in local_routerstatus_t back into
10305 routerstatus_t: we used to need one routerstatus_t for each
10306 authority's opinion, plus a local_routerstatus_t for the locally
10307 computed consensus opinion. To save space, we put the locally
10308 modified fields into local_routerstatus_t, and only the common
10309 stuff into routerstatus_t. But once v3 directories are in use,
10310 clients and caches will no longer need to hold authority opinions;
10311 thus, the rationale for keeping the types separate is now gone.
10312 - Make the code used to reschedule and reattempt downloads more
10314 - Turn all 'Are we a directory server/mirror?' logic into a call to
10316 - Remove the code to generate the oldest (v1) directory format.
10317 The code has been disabled since 0.2.0.5-alpha.
10320 Changes in version 0.2.0.7-alpha - 2007-09-21
10321 This seventh development snapshot makes bridges work again, makes bridge
10322 authorities work for the first time, fixes two huge performance flaws
10323 in hidden services, and fixes a variety of minor issues.
10325 o New directory authorities:
10326 - Set up moria1 and tor26 as the first v3 directory authorities. See
10327 doc/spec/dir-spec.txt for details on the new directory design.
10329 o Major bugfixes (crashes):
10330 - Fix possible segfaults in functions called from
10331 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10333 o Major bugfixes (bridges):
10334 - Fix a bug that made servers send a "404 Not found" in response to
10335 attempts to fetch their server descriptor. This caused Tor servers
10336 to take many minutes to establish reachability for their DirPort,
10337 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10338 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10339 users configure that and specify a bridge with an identity
10340 fingerprint, now they will lookup the bridge descriptor at the
10341 default bridge authority via a one-hop tunnel, but once circuits
10342 are established they will switch to a three-hop tunnel for later
10343 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10345 o Major bugfixes (hidden services):
10346 - Hidden services were choosing introduction points uniquely by
10347 hexdigest, but when constructing the hidden service descriptor
10348 they merely wrote the (potentially ambiguous) nickname.
10349 - Clients now use the v2 intro format for hidden service
10350 connections: they specify their chosen rendezvous point by identity
10351 digest rather than by (potentially ambiguous) nickname. Both
10352 are bugfixes on 0.1.2.x, and they could speed up hidden service
10353 connections dramatically. Thanks to Karsten Loesing.
10355 o Minor features (security):
10356 - As a client, do not believe any server that tells us that an
10357 address maps to an internal address space.
10358 - Make it possible to enable HashedControlPassword and
10359 CookieAuthentication at the same time.
10361 o Minor features (guard nodes):
10362 - Tag every guard node in our state file with the version that
10363 we believe added it, or with our own version if we add it. This way,
10364 if a user temporarily runs an old version of Tor and then switches
10365 back to a new one, she doesn't automatically lose her guards.
10367 o Minor features (speed):
10368 - When implementing AES counter mode, update only the portions of the
10369 counter buffer that need to change, and don't keep separate
10370 network-order and host-order counters when they are the same (i.e.,
10371 on big-endian hosts.)
10373 o Minor features (controller):
10374 - Accept LF instead of CRLF on controller, since some software has a
10375 hard time generating real Internet newlines.
10376 - Add GETINFO values for the server status events
10377 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10380 o Removed features:
10381 - Routers no longer include bandwidth-history lines in their
10382 descriptors; this information is already available in extra-info
10383 documents, and including it in router descriptors took up 60%
10384 (!) of compressed router descriptor downloads. Completes
10385 implementation of proposal 104.
10386 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10387 and TorControl.py, as they use the old v0 controller protocol,
10388 and are obsoleted by TorFlow anyway.
10389 - Drop support for v1 rendezvous descriptors, since we never used
10390 them anyway, and the code has probably rotted by now. Based on
10391 patch from Karsten Loesing.
10392 - On OSX, stop warning the user that kqueue support in libevent is
10393 "experimental", since it seems to have worked fine for ages.
10396 - When generating information telling us how to extend to a given
10397 router, do not try to include the nickname if it is absent. Fixes
10398 bug 467. Bugfix on 0.2.0.3-alpha.
10399 - Fix a user-triggerable (but not remotely-triggerable) segfault
10400 in expand_filename(). Bugfix on 0.1.2.x.
10401 - Fix a memory leak when freeing incomplete requests from DNSPort.
10402 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10403 - Don't try to access (or alter) the state file when running
10404 --list-fingerprint or --verify-config or --hash-password. (Resolves
10405 bug 499.) Bugfix on 0.1.2.x.
10406 - Servers used to decline to publish their DirPort if their
10407 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10408 were below a threshold. Now they only look at BandwidthRate and
10409 RelayBandwidthRate. Bugfix on 0.1.2.x.
10410 - Remove an optimization in the AES counter-mode code that assumed
10411 that the counter never exceeded 2^68. When the counter can be set
10412 arbitrarily as an IV (as it is by Karsten's new hidden services
10413 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10414 - Resume listing "AUTHORITY" flag for authorities in network status.
10415 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10417 o Code simplifications and refactoring:
10418 - Revamp file-writing logic so we don't need to have the entire
10419 contents of a file in memory at once before we write to disk. Tor,
10421 - Turn "descriptor store" into a full-fledged type.
10422 - Move all NT services code into a separate source file.
10423 - Unify all code that computes medians, percentile elements, etc.
10424 - Get rid of a needless malloc when parsing address policies.
10427 Changes in version 0.1.2.17 - 2007-08-30
10428 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10429 X bundles. Vidalia 0.0.14 makes authentication required for the
10430 ControlPort in the default configuration, which addresses important
10431 security risks. Everybody who uses Vidalia (or another controller)
10434 In addition, this Tor update fixes major load balancing problems with
10435 path selection, which should speed things up a lot once many people
10438 o Major bugfixes (security):
10439 - We removed support for the old (v0) control protocol. It has been
10440 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10441 become more of a headache than it's worth.
10443 o Major bugfixes (load balancing):
10444 - When choosing nodes for non-guard positions, weight guards
10445 proportionally less, since they already have enough load. Patch
10447 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10448 will allow fast Tor servers to get more attention.
10449 - When we're upgrading from an old Tor version, forget our current
10450 guards and pick new ones according to the new weightings. These
10451 three load balancing patches could raise effective network capacity
10452 by a factor of four. Thanks to Mike Perry for measurements.
10454 o Major bugfixes (stream expiration):
10455 - Expire not-yet-successful application streams in all cases if
10456 they've been around longer than SocksTimeout. Right now there are
10457 some cases where the stream will live forever, demanding a new
10458 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10460 o Minor features (controller):
10461 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10462 is valid before any authentication has been received. It tells
10463 a controller what kind of authentication is expected, and what
10464 protocol is spoken. Implements proposal 119.
10466 o Minor bugfixes (performance):
10467 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10468 greatly speeding up loading cached-routers from disk on startup.
10469 - Disable sentinel-based debugging for buffer code: we squashed all
10470 the bugs that this was supposed to detect a long time ago, and now
10471 its only effect is to change our buffer sizes from nice powers of
10472 two (which platform mallocs tend to like) to values slightly over
10473 powers of two (which make some platform mallocs sad).
10475 o Minor bugfixes (misc):
10476 - If exit bandwidth ever exceeds one third of total bandwidth, then
10477 use the correct formula to weight exit nodes when choosing paths.
10478 Based on patch from Mike Perry.
10479 - Choose perfectly fairly among routers when choosing by bandwidth and
10480 weighting by fraction of bandwidth provided by exits. Previously, we
10481 would choose with only approximate fairness, and correct ourselves
10482 if we ran off the end of the list.
10483 - If we require CookieAuthentication but we fail to write the
10484 cookie file, we would warn but not exit, and end up in a state
10485 where no controller could authenticate. Now we exit.
10486 - If we require CookieAuthentication, stop generating a new cookie
10487 every time we change any piece of our config.
10488 - Refuse to start with certain directory authority keys, and
10489 encourage people using them to stop.
10490 - Terminate multi-line control events properly. Original patch
10492 - Fix a minor memory leak when we fail to find enough suitable
10493 servers to choose a circuit.
10494 - Stop leaking part of the descriptor when we run into a particularly
10495 unparseable piece of it.
10498 Changes in version 0.2.0.6-alpha - 2007-08-26
10499 This sixth development snapshot features a new Vidalia version in the
10500 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10501 the ControlPort in the default configuration, which addresses important
10504 In addition, this snapshot fixes major load balancing problems
10505 with path selection, which should speed things up a lot once many
10506 people have upgraded. The directory authorities also use a new
10507 mean-time-between-failure approach to tracking which servers are stable,
10508 rather than just looking at the most recent uptime.
10510 o New directory authorities:
10511 - Set up Tonga as the default bridge directory authority.
10514 - Directory authorities now track servers by weighted
10515 mean-times-between-failures. When we have 4 or more days of data,
10516 use measured MTBF rather than declared uptime to decide whether
10517 to call a router Stable. Implements proposal 108.
10519 o Major bugfixes (load balancing):
10520 - When choosing nodes for non-guard positions, weight guards
10521 proportionally less, since they already have enough load. Patch
10523 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10524 will allow fast Tor servers to get more attention.
10525 - When we're upgrading from an old Tor version, forget our current
10526 guards and pick new ones according to the new weightings. These
10527 three load balancing patches could raise effective network capacity
10528 by a factor of four. Thanks to Mike Perry for measurements.
10530 o Major bugfixes (descriptor parsing):
10531 - Handle unexpected whitespace better in malformed descriptors. Bug
10532 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10535 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10536 GETINFO for Torstat to use until it can switch to using extrainfos.
10537 - Optionally (if built with -DEXPORTMALLINFO) export the output
10538 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10542 - Do not intermix bridge routers with controller-added
10543 routers. (Bugfix on 0.2.0.x)
10544 - Do not fail with an assert when accept() returns an unexpected
10545 address family. Addresses but does not wholly fix bug 483. (Bugfix
10547 - Let directory authorities startup even when they can't generate
10548 a descriptor immediately, e.g. because they don't know their
10550 - Stop putting the authentication cookie in a file called "0"
10551 in your working directory if you don't specify anything for the
10552 new CookieAuthFile option. Reported by Matt Edman.
10553 - Make it possible to read the PROTOCOLINFO response in a way that
10554 conforms to our control-spec. Reported by Matt Edman.
10555 - Fix a minor memory leak when we fail to find enough suitable
10556 servers to choose a circuit. Bugfix on 0.1.2.x.
10557 - Stop leaking part of the descriptor when we run into a particularly
10558 unparseable piece of it. Bugfix on 0.1.2.x.
10559 - Unmap the extrainfo cache file on exit.
10562 Changes in version 0.2.0.5-alpha - 2007-08-19
10563 This fifth development snapshot fixes compilation on Windows again;
10564 fixes an obnoxious client-side bug that slowed things down and put
10565 extra load on the network; gets us closer to using the v3 directory
10566 voting scheme; makes it easier for Tor controllers to use cookie-based
10567 authentication; and fixes a variety of other bugs.
10569 o Removed features:
10570 - Version 1 directories are no longer generated in full. Instead,
10571 authorities generate and serve "stub" v1 directories that list
10572 no servers. This will stop Tor versions 0.1.0.x and earlier from
10573 working, but (for security reasons) nobody should be running those
10576 o Major bugfixes (compilation, 0.2.0.x):
10577 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10578 - Try to fix MSVC compilation: build correctly on platforms that do
10579 not define s6_addr16 or s6_addr32.
10580 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10583 o Major bugfixes (stream expiration):
10584 - Expire not-yet-successful application streams in all cases if
10585 they've been around longer than SocksTimeout. Right now there are
10586 some cases where the stream will live forever, demanding a new
10587 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10588 reported by lodger.
10590 o Minor features (directory servers):
10591 - When somebody requests a list of statuses or servers, and we have
10592 none of those, return a 404 rather than an empty 200.
10594 o Minor features (directory voting):
10595 - Store v3 consensus status consensuses on disk, and reload them
10598 o Minor features (security):
10599 - Warn about unsafe ControlPort configurations.
10600 - Refuse to start with certain directory authority keys, and
10601 encourage people using them to stop.
10603 o Minor features (controller):
10604 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10605 is valid before any authentication has been received. It tells
10606 a controller what kind of authentication is expected, and what
10607 protocol is spoken. Implements proposal 119.
10608 - New config option CookieAuthFile to choose a new location for the
10609 cookie authentication file, and config option
10610 CookieAuthFileGroupReadable to make it group-readable.
10612 o Minor features (unit testing):
10613 - Add command-line arguments to unit-test executable so that we can
10614 invoke any chosen test from the command line rather than having
10615 to run the whole test suite at once; and so that we can turn on
10616 logging for the unit tests.
10618 o Minor bugfixes (on 0.1.2.x):
10619 - If we require CookieAuthentication but we fail to write the
10620 cookie file, we would warn but not exit, and end up in a state
10621 where no controller could authenticate. Now we exit.
10622 - If we require CookieAuthentication, stop generating a new cookie
10623 every time we change any piece of our config.
10624 - When loading bandwidth history, do not believe any information in
10625 the future. Fixes bug 434.
10626 - When loading entry guard information, do not believe any information
10628 - When we have our clock set far in the future and generate an
10629 onion key, then re-set our clock to be correct, we should not stop
10630 the onion key from getting rotated.
10631 - Clean up torrc sample config file.
10632 - Do not automatically run configure from autogen.sh. This
10633 non-standard behavior tended to annoy people who have built other
10636 o Minor bugfixes (on 0.2.0.x):
10637 - Fix a bug with AutomapHostsOnResolve that would always cause
10638 the second request to fail. Bug reported by Kate. Bugfix on
10640 - Fix a bug in ADDRMAP controller replies that would sometimes
10641 try to print a NULL. Patch from tup.
10642 - Read v3 directory authority keys from the right location.
10643 - Numerous bugfixes to directory voting code.
10646 Changes in version 0.1.2.16 - 2007-08-01
10647 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10648 remote attacker in certain situations to rewrite the user's torrc
10649 configuration file. This can completely compromise anonymity of users
10650 in most configurations, including those running the Vidalia bundles,
10651 TorK, etc. Or worse.
10653 o Major security fixes:
10654 - Close immediately after missing authentication on control port;
10655 do not allow multiple authentication attempts.
10658 Changes in version 0.2.0.4-alpha - 2007-08-01
10659 This fourth development snapshot fixes a critical security vulnerability
10660 for most users, specifically those running Vidalia, TorK, etc. Everybody
10661 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10663 o Major security fixes:
10664 - Close immediately after missing authentication on control port;
10665 do not allow multiple authentication attempts.
10667 o Major bugfixes (compilation):
10668 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10671 o Minor features (performance):
10672 - Be even more aggressive about releasing RAM from small
10673 empty buffers. Thanks to our free-list code, this shouldn't be too
10674 performance-intensive.
10675 - Disable sentinel-based debugging for buffer code: we squashed all
10676 the bugs that this was supposed to detect a long time ago, and
10677 now its only effect is to change our buffer sizes from nice
10678 powers of two (which platform mallocs tend to like) to values
10679 slightly over powers of two (which make some platform mallocs sad).
10680 - Log malloc statistics from mallinfo() on platforms where it
10684 Changes in version 0.2.0.3-alpha - 2007-07-29
10685 This third development snapshot introduces new experimental
10686 blocking-resistance features and a preliminary version of the v3
10687 directory voting design, and includes many other smaller features
10691 - The first pieces of our "bridge" design for blocking-resistance
10692 are implemented. People can run bridge directory authorities;
10693 people can run bridges; and people can configure their Tor clients
10694 with a set of bridges to use as the first hop into the Tor network.
10695 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10697 - Create listener connections before we setuid to the configured
10698 User and Group. Now non-Windows users can choose port values
10699 under 1024, start Tor as root, and have Tor bind those ports
10700 before it changes to another UID. (Windows users could already
10702 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10703 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10704 on "vserver" accounts. (Patch from coderman.)
10705 - Be even more aggressive about separating local traffic from relayed
10706 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10708 o Major features (experimental):
10709 - First cut of code for "v3 dir voting": directory authorities will
10710 vote on a common network status document rather than each publishing
10711 their own opinion. This code needs more testing and more corner-case
10712 handling before it's ready for use.
10715 - Directory authorities now call routers Fast if their bandwidth is
10716 at least 100KB/s, and consider their bandwidth adequate to be a
10717 Guard if it is at least 250KB/s, no matter the medians. This fix
10718 complements proposal 107. [Bugfix on 0.1.2.x]
10719 - Directory authorities now never mark more than 3 servers per IP as
10720 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10722 - Minor change to organizationName and commonName generation
10723 procedures in TLS certificates during Tor handshakes, to invalidate
10724 some earlier censorware approaches. This is not a long-term
10725 solution, but applying it will give us a bit of time to look into
10726 the epidemiology of countermeasures as they spread.
10728 o Major bugfixes (directory):
10729 - Rewrite directory tokenization code to never run off the end of
10730 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10732 o Minor features (controller):
10733 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10734 match requests to applications. (Patch from Robert Hogan.)
10735 - Report address and port correctly on connections to DNSPort. (Patch
10736 from Robert Hogan.)
10737 - Add a RESOLVE command to launch hostname lookups. (Original patch
10738 from Robert Hogan.)
10739 - Add GETINFO status/enough-dir-info to let controllers tell whether
10740 Tor has downloaded sufficient directory information. (Patch
10742 - You can now use the ControlSocket option to tell Tor to listen for
10743 controller connections on Unix domain sockets on systems that
10744 support them. (Patch from Peter Palfrader.)
10745 - STREAM NEW events are generated for DNSPort requests and for
10746 tunneled directory connections. (Patch from Robert Hogan.)
10747 - New "GETINFO address-mappings/*" command to get address mappings
10748 with expiry information. "addr-mappings/*" is now deprecated.
10751 o Minor features (misc):
10752 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10754 - The tor-gencert tool for v3 directory authorities now creates all
10755 files as readable to the file creator only, and write-protects
10756 the authority identity key.
10757 - When dumping memory usage, list bytes used in buffer memory
10759 - When running with dmalloc, dump more stats on hup and on exit.
10760 - Directory authorities now fail quickly and (relatively) harmlessly
10761 if they generate a network status document that is somehow
10764 o Traffic load balancing improvements:
10765 - If exit bandwidth ever exceeds one third of total bandwidth, then
10766 use the correct formula to weight exit nodes when choosing paths.
10767 (Based on patch from Mike Perry.)
10768 - Choose perfectly fairly among routers when choosing by bandwidth and
10769 weighting by fraction of bandwidth provided by exits. Previously, we
10770 would choose with only approximate fairness, and correct ourselves
10771 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10773 o Performance improvements:
10774 - Be more aggressive with freeing buffer RAM or putting it on the
10776 - Use Critical Sections rather than Mutexes for synchronizing threads
10777 on win32; Mutexes are heavier-weight, and designed for synchronizing
10780 o Deprecated and removed features:
10781 - RedirectExits is now deprecated.
10782 - Stop allowing address masks that do not correspond to bit prefixes.
10783 We have warned about these for a really long time; now it's time
10784 to reject them. (Patch from croup.)
10786 o Minor bugfixes (directory):
10787 - Fix another crash bug related to extra-info caching. (Bug found by
10788 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
10789 - Directories no longer return a "304 not modified" when they don't
10790 have the networkstatus the client asked for. Also fix a memory
10791 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
10792 - We had accidentally labelled 0.1.2.x directory servers as not
10793 suitable for begin_dir requests, and had labelled no directory
10794 servers as suitable for uploading extra-info documents. [Bugfix
10797 o Minor bugfixes (dns):
10798 - Fix a crash when DNSPort is set more than once. (Patch from Robert
10799 Hogan.) [Bugfix on 0.2.0.2-alpha]
10800 - Add DNSPort connections to the global connection list, so that we
10801 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
10803 - Fix a dangling reference that could lead to a crash when DNSPort is
10804 changed or closed (Patch from Robert Hogan.) [Bugfix on
10807 o Minor bugfixes (controller):
10808 - Provide DNS expiry times in GMT, not in local time. For backward
10809 compatibility, ADDRMAP events only provide GMT expiry in an extended
10810 field. "GETINFO address-mappings" always does the right thing.
10811 - Use CRLF line endings properly in NS events.
10812 - Terminate multi-line control events properly. (Original patch
10813 from tup.) [Bugfix on 0.1.2.x-alpha]
10814 - Do not include spaces in SOURCE_ADDR fields in STREAM
10815 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
10818 Changes in version 0.1.2.15 - 2007-07-17
10819 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
10820 problems, fixes compilation on BSD, and fixes a variety of other
10821 bugs. Everybody should upgrade.
10823 o Major bugfixes (compilation):
10824 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
10826 o Major bugfixes (crashes):
10827 - Try even harder not to dereference the first character after
10828 an mmap(). Reported by lodger.
10829 - Fix a crash bug in directory authorities when we re-number the
10830 routerlist while inserting a new router.
10831 - When the cached-routers file is an even multiple of the page size,
10832 don't run off the end and crash. (Fixes bug 455; based on idea
10834 - Fix eventdns.c behavior on Solaris: It is critical to include
10835 orconfig.h _before_ sys/types.h, so that we can get the expected
10836 definition of _FILE_OFFSET_BITS.
10838 o Major bugfixes (security):
10839 - Fix a possible buffer overrun when using BSD natd support. Bug
10841 - When sending destroy cells from a circuit's origin, don't include
10842 the reason for tearing down the circuit. The spec says we didn't,
10843 and now we actually don't. Reported by lodger.
10844 - Keep streamids from different exits on a circuit separate. This
10845 bug may have allowed other routers on a given circuit to inject
10846 cells into streams. Reported by lodger; fixes bug 446.
10847 - If there's a never-before-connected-to guard node in our list,
10848 never choose any guards past it. This way we don't expand our
10849 guard list unless we need to.
10851 o Minor bugfixes (guard nodes):
10852 - Weight guard selection by bandwidth, so that low-bandwidth nodes
10853 don't get overused as guards.
10855 o Minor bugfixes (directory):
10856 - Correctly count the number of authorities that recommend each
10857 version. Previously, we were under-counting by 1.
10858 - Fix a potential crash bug when we load many server descriptors at
10859 once and some of them make others of them obsolete. Fixes bug 458.
10861 o Minor bugfixes (hidden services):
10862 - Stop tearing down the whole circuit when the user asks for a
10863 connection to a port that the hidden service didn't configure.
10866 o Minor bugfixes (misc):
10867 - On Windows, we were preventing other processes from reading
10868 cached-routers while Tor was running. Reported by janbar.
10869 - Fix a possible (but very unlikely) bug in picking routers by
10870 bandwidth. Add a log message to confirm that it is in fact
10871 unlikely. Patch from lodger.
10872 - Backport a couple of memory leak fixes.
10873 - Backport miscellaneous cosmetic bugfixes.
10876 Changes in version 0.2.0.2-alpha - 2007-06-02
10877 o Major bugfixes on 0.2.0.1-alpha:
10878 - Fix an assertion failure related to servers without extra-info digests.
10879 Resolves bugs 441 and 442.
10881 o Minor features (directory):
10882 - Support "If-Modified-Since" when answering HTTP requests for
10883 directories, running-routers documents, and network-status documents.
10884 (There's no need to support it for router descriptors, since those
10885 are downloaded by descriptor digest.)
10887 o Minor build issues:
10888 - Clear up some MIPSPro compiler warnings.
10889 - When building from a tarball on a machine that happens to have SVK
10890 installed, report the micro-revision as whatever version existed
10891 in the tarball, not as "x".
10894 Changes in version 0.2.0.1-alpha - 2007-06-01
10895 This early development snapshot provides new features for people running
10896 Tor as both a client and a server (check out the new RelayBandwidth
10897 config options); lets Tor run as a DNS proxy; and generally moves us
10898 forward on a lot of fronts.
10900 o Major features, server usability:
10901 - New config options RelayBandwidthRate and RelayBandwidthBurst:
10902 a separate set of token buckets for relayed traffic. Right now
10903 relayed traffic is defined as answers to directory requests, and
10904 OR connections that don't have any local circuits on them.
10906 o Major features, client usability:
10907 - A client-side DNS proxy feature to replace the need for
10908 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
10909 for DNS requests on port 9999, use the Tor network to resolve them
10910 anonymously, and send the reply back like a regular DNS server.
10911 The code still only implements a subset of DNS.
10912 - Make PreferTunneledDirConns and TunnelDirConns work even when
10913 we have no cached directory info. This means Tor clients can now
10914 do all of their connections protected by TLS.
10916 o Major features, performance and efficiency:
10917 - Directory authorities accept and serve "extra info" documents for
10918 routers. These documents contain fields from router descriptors
10919 that aren't usually needed, and that use a lot of excess
10920 bandwidth. Once these fields are removed from router descriptors,
10921 the bandwidth savings should be about 60%. [Partially implements
10923 - Servers upload extra-info documents to any authority that accepts
10924 them. Authorities (and caches that have been configured to download
10925 extra-info documents) download them as needed. [Partially implements
10927 - Change the way that Tor buffers data that it is waiting to write.
10928 Instead of queueing data cells in an enormous ring buffer for each
10929 client->OR or OR->OR connection, we now queue cells on a separate
10930 queue for each circuit. This lets us use less slack memory, and
10931 will eventually let us be smarter about prioritizing different kinds
10933 - Use memory pools to allocate cells with better speed and memory
10934 efficiency, especially on platforms where malloc() is inefficient.
10935 - Stop reading on edge connections when their corresponding circuit
10936 buffers are full; start again as the circuits empty out.
10938 o Major features, other:
10939 - Add an HSAuthorityRecordStats option that hidden service authorities
10940 can use to track statistics of overall hidden service usage without
10941 logging information that would be very useful to an attacker.
10942 - Start work implementing multi-level keys for directory authorities:
10943 Add a standalone tool to generate key certificates. (Proposal 103.)
10946 - Directory authorities now call routers Stable if they have an
10947 uptime of at least 30 days, even if that's not the median uptime
10948 in the network. Implements proposal 107, suggested by Kevin Bauer
10951 o Minor fixes (resource management):
10952 - Count the number of open sockets separately from the number
10953 of active connection_t objects. This will let us avoid underusing
10954 our allocated connection limit.
10955 - We no longer use socket pairs to link an edge connection to an
10956 anonymous directory connection or a DirPort test connection.
10957 Instead, we track the link internally and transfer the data
10958 in-process. This saves two sockets per "linked" connection (at the
10959 client and at the server), and avoids the nasty Windows socketpair()
10961 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
10962 for every single inactive connection_t. Free items from the
10963 4k/16k-buffer free lists when they haven't been used for a while.
10965 o Minor features (build):
10966 - Make autoconf search for libevent, openssl, and zlib consistently.
10967 - Update deprecated macros in configure.in.
10968 - When warning about missing headers, tell the user to let us
10969 know if the compile succeeds anyway, so we can downgrade the
10971 - Include the current subversion revision as part of the version
10972 string: either fetch it directly if we're in an SVN checkout, do
10973 some magic to guess it if we're in an SVK checkout, or use
10974 the last-detected version if we're building from a .tar.gz.
10975 Use this version consistently in log messages.
10977 o Minor features (logging):
10978 - Always prepend "Bug: " to any log message about a bug.
10979 - Put a platform string (e.g. "Linux i686") in the startup log
10980 message, so when people paste just their logs, we know if it's
10981 OpenBSD or Windows or what.
10982 - When logging memory usage, break down memory used in buffers by
10985 o Minor features (directory system):
10986 - New config option V2AuthoritativeDirectory that all directory
10987 authorities should set. This will let future authorities choose
10988 not to serve V2 directory information.
10989 - Directory authorities allow multiple router descriptors and/or extra
10990 info documents to be uploaded in a single go. This will make
10991 implementing proposal 104 simpler.
10993 o Minor features (controller):
10994 - Add a new config option __DisablePredictedCircuits designed for
10995 use by the controller, when we don't want Tor to build any circuits
10997 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
10998 so we can exit from the middle of the circuit.
10999 - Implement "getinfo status/circuit-established".
11000 - Implement "getinfo status/version/..." so a controller can tell
11001 whether the current version is recommended, and whether any versions
11002 are good, and how many authorities agree. (Patch from shibz.)
11004 o Minor features (hidden services):
11005 - Allow multiple HiddenServicePort directives with the same virtual
11006 port; when they occur, the user is sent round-robin to one
11007 of the target ports chosen at random. Partially fixes bug 393 by
11008 adding limited ad-hoc round-robining.
11010 o Minor features (other):
11012 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11013 resolve request for hosts matching a given pattern causes Tor to
11014 generate an internal virtual address mapping for that host. This
11015 allows DNSPort to work sensibly with hidden service users. By
11016 default, .exit and .onion addresses are remapped; the list of
11017 patterns can be reconfigured with AutomapHostsSuffixes.
11018 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11019 address. Thanks to the AutomapHostsOnResolve option, this is no
11020 longer a completely silly thing to do.
11021 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11022 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11023 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11024 minus 1 byte: the actual maximum declared bandwidth.
11026 o Removed features:
11027 - Removed support for the old binary "version 0" controller protocol.
11028 This has been deprecated since 0.1.1, and warnings have been issued
11029 since 0.1.2. When we encounter a v0 control message, we now send
11030 back an error and close the connection.
11031 - Remove the old "dns worker" server DNS code: it hasn't been default
11032 since 0.1.2.2-alpha, and all the servers seem to be using the new
11035 o Minor bugfixes (portability):
11036 - Even though Windows is equally happy with / and \ as path separators,
11037 try to use \ consistently on Windows and / consistently on Unix: it
11038 makes the log messages nicer.
11039 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11040 - Read resolv.conf files correctly on platforms where read() returns
11041 partial results on small file reads.
11043 o Minor bugfixes (directory):
11044 - Correctly enforce that elements of directory objects do not appear
11045 more often than they are allowed to appear.
11046 - When we are reporting the DirServer line we just parsed, we were
11047 logging the second stanza of the key fingerprint, not the first.
11049 o Minor bugfixes (logging):
11050 - When we hit an EOF on a log (probably because we're shutting down),
11051 don't try to remove the log from the list: just mark it as
11052 unusable. (Bulletproofs against bug 222.)
11054 o Minor bugfixes (other):
11055 - In the exitlist script, only consider the most recently published
11056 server descriptor for each server. Also, when the user requests
11057 a list of servers that _reject_ connections to a given address,
11058 explicitly exclude the IPs that also have servers that accept
11059 connections to that address. (Resolves bug 405.)
11060 - Stop allowing hibernating servers to be "stable" or "fast".
11061 - On Windows, we were preventing other processes from reading
11062 cached-routers while Tor was running. (Reported by janbar)
11063 - Make the NodeFamilies config option work. (Reported by
11064 lodger -- it has never actually worked, even though we added it
11066 - Check return values from pthread_mutex functions.
11067 - Don't save non-general-purpose router descriptors to the disk cache,
11068 because we have no way of remembering what their purpose was when
11070 - Add even more asserts to hunt down bug 417.
11071 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11072 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11073 Add a log message to confirm that it is in fact unlikely.
11075 o Minor bugfixes (controller):
11076 - Make 'getinfo fingerprint' return a 551 error if we're not a
11077 server, so we match what the control spec claims we do. Reported
11079 - Fix a typo in an error message when extendcircuit fails that
11080 caused us to not follow the \r\n-based delimiter protocol. Reported
11083 o Code simplifications and refactoring:
11084 - Stop passing around circuit_t and crypt_path_t pointers that are
11085 implicit in other procedure arguments.
11086 - Drop the old code to choke directory connections when the
11087 corresponding OR connections got full: thanks to the cell queue
11088 feature, OR conns don't get full any more.
11089 - Make dns_resolve() handle attaching connections to circuits
11090 properly, so the caller doesn't have to.
11091 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11092 - Keep the connection array as a dynamic smartlist_t, rather than as
11093 a fixed-sized array. This is important, as the number of connections
11094 is becoming increasingly decoupled from the number of sockets.
11097 Changes in version 0.1.2.14 - 2007-05-25
11098 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11099 change especially affects those who serve or use hidden services),
11100 and fixes several other crash- and security-related bugs.
11102 o Directory authority changes:
11103 - Two directory authorities (moria1 and moria2) just moved to new
11104 IP addresses. This change will particularly affect those who serve
11105 or use hidden services.
11107 o Major bugfixes (crashes):
11108 - If a directory server runs out of space in the connection table
11109 as it's processing a begin_dir request, it will free the exit stream
11110 but leave it attached to the circuit, leading to unpredictable
11111 behavior. (Reported by seeess, fixes bug 425.)
11112 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11113 to corrupt memory under some really unlikely scenarios.
11114 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11115 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11118 o Major bugfixes (security):
11119 - When choosing an entry guard for a circuit, avoid using guards
11120 that are in the same family as the chosen exit -- not just guards
11121 that are exactly the chosen exit. (Reported by lodger.)
11123 o Major bugfixes (resource management):
11124 - If a directory authority is down, skip it when deciding where to get
11125 networkstatus objects or descriptors. Otherwise we keep asking
11126 every 10 seconds forever. Fixes bug 384.
11127 - Count it as a failure if we fetch a valid network-status but we
11128 don't want to keep it. Otherwise we'll keep fetching it and keep
11129 not wanting to keep it. Fixes part of bug 422.
11130 - If all of our dirservers have given us bad or no networkstatuses
11131 lately, then stop hammering them once per minute even when we
11132 think they're failed. Fixes another part of bug 422.
11135 - Actually set the purpose correctly for descriptors inserted with
11136 purpose=controller.
11137 - When we have k non-v2 authorities in our DirServer config,
11138 we ignored the last k authorities in the list when updating our
11140 - Correctly back-off from requesting router descriptors that we are
11141 having a hard time downloading.
11142 - Read resolv.conf files correctly on platforms where read() returns
11143 partial results on small file reads.
11144 - Don't rebuild the entire router store every time we get 32K of
11145 routers: rebuild it when the journal gets very large, or when
11146 the gaps in the store get very large.
11149 - When routers publish SVN revisions in their router descriptors,
11150 authorities now include those versions correctly in networkstatus
11152 - Warn when using a version of libevent before 1.3b to run a server on
11153 OSX or BSD: these versions interact badly with userspace threads.
11156 Changes in version 0.1.2.13 - 2007-04-24
11157 This release features some major anonymity fixes, such as safer path
11158 selection; better client performance; faster bootstrapping, better
11159 address detection, and better DNS support for servers; write limiting as
11160 well as read limiting to make servers easier to run; and a huge pile of
11161 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11163 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11164 of the Freenode IRC network, remembering his patience and vision for
11165 free speech on the Internet.
11168 - Fix a memory leak when we ask for "all" networkstatuses and we
11169 get one we don't recognize.
11170 - Add more asserts to hunt down bug 417.
11171 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11174 Changes in version 0.1.2.12-rc - 2007-03-16
11176 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11177 directory information requested inside Tor connections (i.e. via
11178 begin_dir cells). It only triggered when the same connection was
11179 serving other data at the same time. Reported by seeess.
11182 - When creating a circuit via the controller, send a 'launched'
11183 event when we're done, so we follow the spec better.
11186 Changes in version 0.1.2.11-rc - 2007-03-15
11187 o Minor bugfixes (controller), reported by daejees:
11188 - Correct the control spec to match how the code actually responds
11189 to 'getinfo addr-mappings/*'.
11190 - The control spec described a GUARDS event, but the code
11191 implemented a GUARD event. Standardize on GUARD, but let people
11192 ask for GUARDS too.
11195 Changes in version 0.1.2.10-rc - 2007-03-07
11196 o Major bugfixes (Windows):
11197 - Do not load the NT services library functions (which may not exist)
11198 just to detect if we're a service trying to shut down. Now we run
11199 on Win98 and friends again.
11201 o Minor bugfixes (other):
11202 - Clarify a couple of log messages.
11203 - Fix a misleading socks5 error number.
11206 Changes in version 0.1.2.9-rc - 2007-03-02
11207 o Major bugfixes (Windows):
11208 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11209 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11210 int configuration values: the high-order 32 bits would get
11211 truncated. In particular, we were being bitten by the default
11212 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11213 and maybe also bug 397.)
11215 o Minor bugfixes (performance):
11216 - Use OpenSSL's AES implementation on platforms where it's faster.
11217 This could save us as much as 10% CPU usage.
11219 o Minor bugfixes (server):
11220 - Do not rotate onion key immediately after setting it for the first
11223 o Minor bugfixes (directory authorities):
11224 - Stop calling servers that have been hibernating for a long time
11225 "stable". Also, stop letting hibernating or obsolete servers affect
11226 uptime and bandwidth cutoffs.
11227 - Stop listing hibernating servers in the v1 directory.
11229 o Minor bugfixes (hidden services):
11230 - Upload hidden service descriptors slightly less often, to reduce
11231 load on authorities.
11233 o Minor bugfixes (other):
11234 - Fix an assert that could trigger if a controller quickly set then
11235 cleared EntryNodes. Bug found by Udo van den Heuvel.
11236 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11238 - Fix a potential race condition in the rpm installer. Found by
11240 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11241 of 2 as indicating that the server is completely bad; it sometimes
11242 means that the server is just bad for the request in question. (may fix
11243 the last of bug 326.)
11244 - Disable encrypted directory connections when we don't have a server
11245 descriptor for the destination. We'll get this working again in
11249 Changes in version 0.1.2.8-beta - 2007-02-26
11250 o Major bugfixes (crashes):
11251 - Stop crashing when the controller asks us to resetconf more than
11252 one config option at once. (Vidalia 0.0.11 does this.)
11253 - Fix a crash that happened on Win98 when we're given command-line
11254 arguments: don't try to load NT service functions from advapi32.dll
11255 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11257 - Fix a longstanding obscure crash bug that could occur when
11258 we run out of DNS worker processes. (Resolves bug 390.)
11260 o Major bugfixes (hidden services):
11261 - Correctly detect whether hidden service descriptor downloads are
11262 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11264 o Major bugfixes (accounting):
11265 - When we start during an accounting interval before it's time to wake
11266 up, remember to wake up at the correct time. (May fix bug 342.)
11268 o Minor bugfixes (controller):
11269 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11270 clear the corresponding on_circuit variable, and remember later
11271 that we don't need to send a redundant CLOSED event. Resolves part
11273 - Report events where a resolve succeeded or where we got a socks
11274 protocol error correctly, rather than calling both of them
11276 - Change reported stream target addresses to IP consistently when
11277 we finally get the IP from an exit node.
11278 - Send log messages to the controller even if they happen to be very
11281 o Minor bugfixes (other):
11282 - Display correct results when reporting which versions are
11283 recommended, and how recommended they are. (Resolves bug 383.)
11284 - Improve our estimates for directory bandwidth to be less random:
11285 guess that an unrecognized directory will have the average bandwidth
11286 from all known directories, not that it will have the average
11287 bandwidth from those directories earlier than it on the list.
11288 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11289 and hup, stop triggering an assert based on an empty onion_key.
11290 - On platforms with no working mmap() equivalent, don't warn the
11291 user when cached-routers doesn't exist.
11292 - Warn the user when mmap() [or its equivalent] fails for some reason
11293 other than file-not-found.
11294 - Don't warn the user when cached-routers.new doesn't exist: that's
11295 perfectly fine when starting up for the first time.
11296 - When EntryNodes are configured, rebuild the guard list to contain,
11297 in order: the EntryNodes that were guards before; the rest of the
11298 EntryNodes; the nodes that were guards before.
11299 - Mask out all signals in sub-threads; only the libevent signal
11300 handler should be processing them. This should prevent some crashes
11301 on some machines using pthreads. (Patch from coderman.)
11302 - Fix switched arguments on memset in the implementation of
11303 tor_munmap() for systems with no mmap() call.
11304 - When Tor receives a router descriptor that it asked for, but
11305 no longer wants (because it has received fresh networkstatuses
11306 in the meantime), do not warn the user. Cache the descriptor if
11307 we're a cache; drop it if we aren't.
11308 - Make earlier entry guards _really_ get retried when the network
11310 - On a malformed DNS reply, always give an error to the corresponding
11312 - Build with recent libevents on platforms that do not define the
11313 nonstandard types "u_int8_t" and friends.
11315 o Minor features (controller):
11316 - Warn the user when an application uses the obsolete binary v0
11317 control protocol. We're planning to remove support for it during
11318 the next development series, so it's good to give people some
11320 - Add STREAM_BW events to report per-entry-stream bandwidth
11321 use. (Patch from Robert Hogan.)
11322 - Rate-limit SIGNEWNYM signals in response to controllers that
11323 impolitely generate them for every single stream. (Patch from
11324 mwenge; closes bug 394.)
11325 - Make REMAP stream events have a SOURCE (cache or exit), and
11326 make them generated in every case where we get a successful
11327 connected or resolved cell.
11329 o Minor bugfixes (performance):
11330 - Call router_have_min_dir_info half as often. (This is showing up in
11331 some profiles, but not others.)
11332 - When using GCC, make log_debug never get called at all, and its
11333 arguments never get evaluated, when no debug logs are configured.
11334 (This is showing up in some profiles, but not others.)
11337 - Remove some never-implemented options. Mark PathlenCoinWeight as
11339 - Implement proposal 106: Stop requiring clients to have well-formed
11340 certificates; stop checking nicknames in certificates. (Clients
11341 have certificates so that they can look like Tor servers, but in
11342 the future we might want to allow them to look like regular TLS
11343 clients instead. Nicknames in certificates serve no purpose other
11344 than making our protocol easier to recognize on the wire.)
11345 - Revise messages on handshake failure again to be even more clear about
11346 which are incoming connections and which are outgoing.
11347 - Discard any v1 directory info that's over 1 month old (for
11348 directories) or over 1 week old (for running-routers lists).
11349 - Do not warn when individual nodes in the configuration's EntryNodes,
11350 ExitNodes, etc are down: warn only when all possible nodes
11351 are down. (Fixes bug 348.)
11352 - Always remove expired routers and networkstatus docs before checking
11353 whether we have enough information to build circuits. (Fixes
11355 - Put a lower-bound on MaxAdvertisedBandwidth.
11358 Changes in version 0.1.2.7-alpha - 2007-02-06
11359 o Major bugfixes (rate limiting):
11360 - Servers decline directory requests much more aggressively when
11361 they're low on bandwidth. Otherwise they end up queueing more and
11362 more directory responses, which can't be good for latency.
11363 - But never refuse directory requests from local addresses.
11364 - Fix a memory leak when sending a 503 response for a networkstatus
11366 - Be willing to read or write on local connections (e.g. controller
11367 connections) even when the global rate limiting buckets are empty.
11368 - If our system clock jumps back in time, don't publish a negative
11369 uptime in the descriptor. Also, don't let the global rate limiting
11370 buckets go absurdly negative.
11371 - Flush local controller connection buffers periodically as we're
11372 writing to them, so we avoid queueing 4+ megabytes of data before
11375 o Major bugfixes (NT services):
11376 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11377 command-line flag so that admins can override the default by saying
11378 "tor --service install --user "SomeUser"". This will not affect
11379 existing installed services. Also, warn the user that the service
11380 will look for its configuration file in the service user's
11381 %appdata% directory. (We can't do the 'hardwire the user's appdata
11382 directory' trick any more, since we may not have read access to that
11385 o Major bugfixes (other):
11386 - Previously, we would cache up to 16 old networkstatus documents
11387 indefinitely, if they came from nontrusted authorities. Now we
11388 discard them if they are more than 10 days old.
11389 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11391 - Detect and reject malformed DNS responses containing circular
11393 - If exits are rare enough that we're not marking exits as guards,
11394 ignore exit bandwidth when we're deciding the required bandwidth
11396 - When we're handling a directory connection tunneled over Tor,
11397 don't fill up internal memory buffers with all the data we want
11398 to tunnel; instead, only add it if the OR connection that will
11399 eventually receive it has some room for it. (This can lead to
11400 slowdowns in tunneled dir connections; a better solution will have
11401 to wait for 0.2.0.)
11403 o Minor bugfixes (dns):
11404 - Add some defensive programming to eventdns.c in an attempt to catch
11405 possible memory-stomping bugs.
11406 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11407 an incorrect number of bytes. (Previously, we would ignore the
11409 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11410 in the correct order, and doesn't crash.
11411 - Free memory held in recently-completed DNS lookup attempts on exit.
11412 This was not a memory leak, but may have been hiding memory leaks.
11413 - Handle TTL values correctly on reverse DNS lookups.
11414 - Treat failure to parse resolv.conf as an error.
11416 o Minor bugfixes (other):
11417 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11418 - When computing clock skew from directory HTTP headers, consider what
11419 time it was when we finished asking for the directory, not what
11421 - Expire socks connections if they spend too long waiting for the
11422 handshake to finish. Previously we would let them sit around for
11423 days, if the connecting application didn't close them either.
11424 - And if the socks handshake hasn't started, don't send a
11425 "DNS resolve socks failed" handshake reply; just close it.
11426 - Stop using C functions that OpenBSD's linker doesn't like.
11427 - Don't launch requests for descriptors unless we have networkstatuses
11428 from at least half of the authorities. This delays the first
11429 download slightly under pathological circumstances, but can prevent
11430 us from downloading a bunch of descriptors we don't need.
11431 - Do not log IPs with TLS failures for incoming TLS
11432 connections. (Fixes bug 382.)
11433 - If the user asks to use invalid exit nodes, be willing to use
11435 - Stop using the reserved ac_cv namespace in our configure script.
11436 - Call stat() slightly less often; use fstat() when possible.
11437 - Refactor the way we handle pending circuits when an OR connection
11438 completes or fails, in an attempt to fix a rare crash bug.
11439 - Only rewrite a conn's address based on X-Forwarded-For: headers
11440 if it's a parseable public IP address; and stop adding extra quotes
11441 to the resulting address.
11444 - Weight directory requests by advertised bandwidth. Now we can
11445 let servers enable write limiting but still allow most clients to
11446 succeed at their directory requests. (We still ignore weights when
11447 choosing a directory authority; I hope this is a feature.)
11450 - Create a new file ReleaseNotes which was the old ChangeLog. The
11451 new ChangeLog file now includes the summaries for all development
11453 - Check for addresses with invalid characters at the exit as well
11454 as at the client, and warn less verbosely when they fail. You can
11455 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11456 - Adapt a patch from goodell to let the contrib/exitlist script
11457 take arguments rather than require direct editing.
11458 - Inform the server operator when we decide not to advertise a
11459 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11460 was confusing Zax, so now we're hopefully more helpful.
11461 - Bring us one step closer to being able to establish an encrypted
11462 directory tunnel without knowing a descriptor first. Still not
11463 ready yet. As part of the change, now assume we can use a
11464 create_fast cell if we don't know anything about a router.
11465 - Allow exit nodes to use nameservers running on ports other than 53.
11466 - Servers now cache reverse DNS replies.
11467 - Add an --ignore-missing-torrc command-line option so that we can
11468 get the "use sensible defaults if the configuration file doesn't
11469 exist" behavior even when specifying a torrc location on the command
11472 o Minor features (controller):
11473 - Track reasons for OR connection failure; make these reasons
11474 available via the controller interface. (Patch from Mike Perry.)
11475 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11476 can learn when clients are sending malformed hostnames to Tor.
11477 - Clean up documentation for controller status events.
11478 - Add a REMAP status to stream events to note that a stream's
11479 address has changed because of a cached address or a MapAddress
11483 Changes in version 0.1.2.6-alpha - 2007-01-09
11485 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11486 connection handles more than 4 gigs in either direction, we crash.
11487 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11488 advertised exit node, somebody might try to exit from us when
11489 we're bootstrapping and before we've built our descriptor yet.
11490 Refuse the connection rather than crashing.
11493 - Warn if we (as a server) find that we've resolved an address that we
11494 weren't planning to resolve.
11495 - Warn that using select() on any libevent version before 1.1 will be
11496 unnecessarily slow (even for select()).
11497 - Flush ERR-level controller status events just like we currently
11498 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11499 the controller from learning about current events.
11501 o Minor features (more controller status events):
11502 - Implement EXTERNAL_ADDRESS server status event so controllers can
11503 learn when our address changes.
11504 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11505 can learn when directories reject our descriptor.
11506 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11507 can learn when a client application is speaking a non-socks protocol
11509 - Implement DANGEROUS_SOCKS client status event so controllers
11510 can learn when a client application is leaking DNS addresses.
11511 - Implement BUG general status event so controllers can learn when
11512 Tor is unhappy about its internal invariants.
11513 - Implement CLOCK_SKEW general status event so controllers can learn
11514 when Tor thinks the system clock is set incorrectly.
11515 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11516 server status events so controllers can learn when their descriptors
11517 are accepted by a directory.
11518 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11519 server status events so controllers can learn about Tor's progress in
11520 deciding whether it's reachable from the outside.
11521 - Implement BAD_LIBEVENT general status event so controllers can learn
11522 when we have a version/method combination in libevent that needs to
11524 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11525 and DNS_USELESS server status events so controllers can learn
11526 about changes to DNS server status.
11528 o Minor features (directory):
11529 - Authorities no longer recommend exits as guards if this would shift
11530 too much load to the exit nodes.
11533 Changes in version 0.1.2.5-alpha - 2007-01-06
11535 - Enable write limiting as well as read limiting. Now we sacrifice
11536 capacity if we're pushing out lots of directory traffic, rather
11537 than overrunning the user's intended bandwidth limits.
11538 - Include TLS overhead when counting bandwidth usage; previously, we
11539 would count only the bytes sent over TLS, but not the bytes used
11541 - Support running the Tor service with a torrc not in the same
11542 directory as tor.exe and default to using the torrc located in
11543 the %appdata%\Tor\ of the user who installed the service. Patch
11545 - Servers now check for the case when common DNS requests are going to
11546 wildcarded addresses (i.e. all getting the same answer), and change
11547 their exit policy to reject *:* if it's happening.
11548 - Implement BEGIN_DIR cells, so we can connect to the directory
11549 server via TLS to do encrypted directory requests rather than
11550 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11551 config options if you like.
11553 o Minor features (config and docs):
11554 - Start using the state file to store bandwidth accounting data:
11555 the bw_accounting file is now obsolete. We'll keep generating it
11556 for a while for people who are still using 0.1.2.4-alpha.
11557 - Try to batch changes to the state file so that we do as few
11558 disk writes as possible while still storing important things in
11560 - The state file and the bw_accounting file get saved less often when
11561 the AvoidDiskWrites config option is set.
11562 - Make PIDFile work on Windows (untested).
11563 - Add internal descriptions for a bunch of configuration options:
11564 accessible via controller interface and in comments in saved
11566 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11567 NNTP by default, so this seems like a sensible addition.
11568 - Clients now reject hostnames with invalid characters. This should
11569 avoid some inadvertent info leaks. Add an option
11570 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11571 is running a private network with hosts called @, !, and #.
11572 - Add a maintainer script to tell us which options are missing
11573 documentation: "make check-docs".
11574 - Add a new address-spec.txt document to describe our special-case
11575 addresses: .exit, .onion, and .noconnnect.
11577 o Minor features (DNS):
11578 - Ongoing work on eventdns infrastructure: now it has dns server
11579 and ipv6 support. One day Tor will make use of it.
11580 - Add client-side caching for reverse DNS lookups.
11581 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11582 - When we change nameservers or IP addresses, reset and re-launch
11583 our tests for DNS hijacking.
11585 o Minor features (directory):
11586 - Authorities now specify server versions in networkstatus. This adds
11587 about 2% to the size of compressed networkstatus docs, and allows
11588 clients to tell which servers support BEGIN_DIR and which don't.
11589 The implementation is forward-compatible with a proposed future
11590 protocol version scheme not tied to Tor versions.
11591 - DirServer configuration lines now have an orport= option so
11592 clients can open encrypted tunnels to the authorities without
11593 having downloaded their descriptors yet. Enabled for moria1,
11594 moria2, tor26, and lefkada now in the default configuration.
11595 - Directory servers are more willing to send a 503 "busy" if they
11596 are near their write limit, especially for v1 directory requests.
11597 Now they can use their limited bandwidth for actual Tor traffic.
11598 - Clients track responses with status 503 from dirservers. After a
11599 dirserver has given us a 503, we try not to use it until an hour has
11600 gone by, or until we have no dirservers that haven't given us a 503.
11601 - When we get a 503 from a directory, and we're not a server, we don't
11602 count the failure against the total number of failures allowed
11603 for the thing we're trying to download.
11604 - Report X-Your-Address-Is correctly from tunneled directory
11605 connections; don't report X-Your-Address-Is when it's an internal
11606 address; and never believe reported remote addresses when they're
11608 - Protect against an unlikely DoS attack on directory servers.
11609 - Add a BadDirectory flag to network status docs so that authorities
11610 can (eventually) tell clients about caches they believe to be
11613 o Minor features (controller):
11614 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11615 - Reimplement GETINFO so that info/names stays in sync with the
11617 - Implement "GETINFO fingerprint".
11618 - Implement "SETEVENTS GUARD" so controllers can get updates on
11619 entry guard status as it changes.
11621 o Minor features (clean up obsolete pieces):
11622 - Remove some options that have been deprecated since at least
11623 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11624 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11625 to set log options.
11626 - We no longer look for identity and onion keys in "identity.key" and
11627 "onion.key" -- these were replaced by secret_id_key and
11628 secret_onion_key in 0.0.8pre1.
11629 - We no longer require unrecognized directory entries to be
11632 o Major bugfixes (security):
11633 - Stop sending the HttpProxyAuthenticator string to directory
11634 servers when directory connections are tunnelled through Tor.
11635 - Clients no longer store bandwidth history in the state file.
11636 - Do not log introduction points for hidden services if SafeLogging
11638 - When generating bandwidth history, round down to the nearest
11639 1k. When storing accounting data, round up to the nearest 1k.
11640 - When we're running as a server, remember when we last rotated onion
11641 keys, so that we will rotate keys once they're a week old even if
11642 we never stay up for a week ourselves.
11644 o Major bugfixes (other):
11645 - Fix a longstanding bug in eventdns that prevented the count of
11646 timed-out resolves from ever being reset. This bug caused us to
11647 give up on a nameserver the third time it timed out, and try it
11648 10 seconds later... and to give up on it every time it timed out
11650 - Take out the '5 second' timeout from the connection retry
11651 schedule. Now the first connect attempt will wait a full 10
11652 seconds before switching to a new circuit. Perhaps this will help
11653 a lot. Based on observations from Mike Perry.
11654 - Fix a bug on the Windows implementation of tor_mmap_file() that
11655 would prevent the cached-routers file from ever loading. Reported
11659 - Fix an assert failure when a directory authority sets
11660 AuthDirRejectUnlisted and then receives a descriptor from an
11661 unlisted router. Reported by seeess.
11662 - Avoid a double-free when parsing malformed DirServer lines.
11663 - Fix a bug when a BSD-style PF socket is first used. Patch from
11665 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11666 to resolve an address at a given exit node even when they ask for
11668 - Servers no longer ever list themselves in their "family" line,
11669 even if configured to do so. This makes it easier to configure
11670 family lists conveniently.
11671 - When running as a server, don't fall back to 127.0.0.1 when no
11672 nameservers are configured in /etc/resolv.conf; instead, make the
11673 user fix resolv.conf or specify nameservers explicitly. (Resolves
11675 - Stop accepting certain malformed ports in configured exit policies.
11676 - Don't re-write the fingerprint file every restart, unless it has
11678 - Stop warning when a single nameserver fails: only warn when _all_ of
11679 our nameservers have failed. Also, when we only have one nameserver,
11680 raise the threshold for deciding that the nameserver is dead.
11681 - Directory authorities now only decide that routers are reachable
11682 if their identity keys are as expected.
11683 - When the user uses bad syntax in the Log config line, stop
11684 suggesting other bad syntax as a replacement.
11685 - Correctly detect ipv6 DNS capability on OpenBSD.
11687 o Minor bugfixes (controller):
11688 - Report the circuit number correctly in STREAM CLOSED events. Bug
11689 reported by Mike Perry.
11690 - Do not report bizarre values for results of accounting GETINFOs
11691 when the last second's write or read exceeds the allotted bandwidth.
11692 - Report "unrecognized key" rather than an empty string when the
11693 controller tries to fetch a networkstatus that doesn't exist.
11696 Changes in version 0.1.1.26 - 2006-12-14
11697 o Security bugfixes:
11698 - Stop sending the HttpProxyAuthenticator string to directory
11699 servers when directory connections are tunnelled through Tor.
11700 - Clients no longer store bandwidth history in the state file.
11701 - Do not log introduction points for hidden services if SafeLogging
11705 - Fix an assert failure when a directory authority sets
11706 AuthDirRejectUnlisted and then receives a descriptor from an
11707 unlisted router (reported by seeess).
11710 Changes in version 0.1.2.4-alpha - 2006-12-03
11712 - Add support for using natd; this allows FreeBSDs earlier than
11713 5.1.2 to have ipfw send connections through Tor without using
11714 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11717 - Make all connections to addresses of the form ".noconnect"
11718 immediately get closed. This lets application/controller combos
11719 successfully test whether they're talking to the same Tor by
11720 watching for STREAM events.
11721 - Make cross.sh cross-compilation script work even when autogen.sh
11722 hasn't been run. (Patch from Michael Mohr.)
11723 - Statistics dumped by -USR2 now include a breakdown of public key
11724 operations, for profiling.
11727 - Fix a major leak when directory authorities parse their
11728 approved-routers list, a minor memory leak when we fail to pick
11729 an exit node, and a few rare leaks on errors.
11730 - Handle TransPort connections even when the server sends data before
11731 the client sends data. Previously, the connection would just hang
11732 until the client sent data. (Patch from tup based on patch from
11734 - Avoid assert failure when our cached-routers file is empty on
11738 - Don't log spurious warnings when we see a circuit close reason we
11739 don't recognize; it's probably just from a newer version of Tor.
11740 - Have directory authorities allow larger amounts of drift in uptime
11741 without replacing the server descriptor: previously, a server that
11742 restarted every 30 minutes could have 48 "interesting" descriptors
11744 - Start linking to the Tor specification and Tor reference manual
11745 correctly in the Windows installer.
11746 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11747 Tor/Privoxy we also uninstall Vidalia.
11748 - Resume building on Irix64, and fix a lot of warnings from its
11749 MIPSpro C compiler.
11750 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11751 when we're running as a client.
11754 Changes in version 0.1.1.25 - 2006-11-04
11756 - When a client asks us to resolve (rather than connect to)
11757 an address, and we have a cached answer, give them the cached
11758 answer. Previously, we would give them no answer at all.
11759 - We were building exactly the wrong circuits when we predict
11760 hidden service requirements, meaning Tor would have to build all
11761 its circuits on demand.
11762 - If none of our live entry guards have a high uptime, but we
11763 require a guard with a high uptime, try adding a new guard before
11764 we give up on the requirement. This patch should make long-lived
11765 connections more stable on average.
11766 - When testing reachability of our DirPort, don't launch new
11767 tests when there's already one in progress -- unreachable
11768 servers were stacking up dozens of testing streams.
11770 o Security bugfixes:
11771 - When the user sends a NEWNYM signal, clear the client-side DNS
11772 cache too. Otherwise we continue to act on previous information.
11775 - Avoid a memory corruption bug when creating a hash table for
11777 - Avoid possibility of controller-triggered crash when misusing
11778 certain commands from a v0 controller on platforms that do not
11779 handle printf("%s",NULL) gracefully.
11780 - Avoid infinite loop on unexpected controller input.
11781 - Don't log spurious warnings when we see a circuit close reason we
11782 don't recognize; it's probably just from a newer version of Tor.
11783 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11784 Tor/Privoxy we also uninstall Vidalia.
11787 Changes in version 0.1.2.3-alpha - 2006-10-29
11789 - Prepare for servers to publish descriptors less often: never
11790 discard a descriptor simply for being too old until either it is
11791 recommended by no authorities, or until we get a better one for
11792 the same router. Make caches consider retaining old recommended
11793 routers for even longer.
11794 - If most authorities set a BadExit flag for a server, clients
11795 don't think of it as a general-purpose exit. Clients only consider
11796 authorities that advertise themselves as listing bad exits.
11797 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
11798 headers for content, so that we can work better in the presence of
11799 caching HTTP proxies.
11800 - Allow authorities to list nodes as bad exits by fingerprint or by
11803 o Minor features, controller:
11804 - Add a REASON field to CIRC events; for backward compatibility, this
11805 field is sent only to controllers that have enabled the extended
11806 event format. Also, add additional reason codes to explain why
11807 a given circuit has been destroyed or truncated. (Patches from
11809 - Add a REMOTE_REASON field to extended CIRC events to tell the
11810 controller about why a remote OR told us to close a circuit.
11811 - Stream events also now have REASON and REMOTE_REASON fields,
11812 working much like those for circuit events.
11813 - There's now a GETINFO ns/... field so that controllers can ask Tor
11814 about the current status of a router.
11815 - A new event type "NS" to inform a controller when our opinion of
11816 a router's status has changed.
11817 - Add a GETINFO events/names and GETINFO features/names so controllers
11818 can tell which events and features are supported.
11819 - A new CLEARDNSCACHE signal to allow controllers to clear the
11820 client-side DNS cache without expiring circuits.
11822 o Security bugfixes:
11823 - When the user sends a NEWNYM signal, clear the client-side DNS
11824 cache too. Otherwise we continue to act on previous information.
11827 - Avoid sending junk to controllers or segfaulting when a controller
11828 uses EVENT_NEW_DESC with verbose nicknames.
11829 - Stop triggering asserts if the controller tries to extend hidden
11830 service circuits (reported by mwenge).
11831 - Avoid infinite loop on unexpected controller input.
11832 - When the controller does a "GETINFO network-status", tell it
11833 about even those routers whose descriptors are very old, and use
11834 long nicknames where appropriate.
11835 - Change NT service functions to be loaded on demand. This lets us
11836 build with MinGW without breaking Tor for Windows 98 users.
11837 - Do DirPort reachability tests less often, since a single test
11838 chews through many circuits before giving up.
11839 - In the hidden service example in torrc.sample, stop recommending
11840 esoteric and discouraged hidden service options.
11841 - When stopping an NT service, wait up to 10 sec for it to actually
11842 stop. Patch from Matt Edman; resolves bug 295.
11843 - Fix handling of verbose nicknames with ORCONN controller events:
11844 make them show up exactly when requested, rather than exactly when
11846 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
11847 printing a duplicate "$" in the keys we send (reported by mwenge).
11848 - Correctly set maximum connection limit on Cygwin. (This time
11850 - Try to detect Windows correctly when cross-compiling.
11851 - Detect the size of the routers file correctly even if it is
11852 corrupted (on systems without mmap) or not page-aligned (on systems
11853 with mmap). This bug was harmless.
11854 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
11855 to open a stream fails; now we do in more cases. This should
11856 make clients able to find a good exit faster in some cases, since
11857 unhandleable requests will now get an error rather than timing out.
11858 - Resolve two memory leaks when rebuilding the on-disk router cache
11859 (reported by fookoowa).
11860 - Clean up minor code warnings suggested by the MIPSpro C compiler,
11861 and reported by some Centos users.
11862 - Controller signals now work on non-Unix platforms that don't define
11863 SIGUSR1 and SIGUSR2 the way we expect.
11864 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
11865 values before failing, and always enables eventdns.
11866 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
11867 Try to fix this in configure.in by checking for most functions
11868 before we check for libevent.
11871 Changes in version 0.1.2.2-alpha - 2006-10-07
11873 - Make our async eventdns library on-by-default for Tor servers,
11874 and plan to deprecate the separate dnsworker threads.
11875 - Add server-side support for "reverse" DNS lookups (using PTR
11876 records so clients can determine the canonical hostname for a given
11877 IPv4 address). Only supported by servers using eventdns; servers
11878 now announce in their descriptors whether they support eventdns.
11879 - Specify and implement client-side SOCKS5 interface for reverse DNS
11880 lookups (see doc/socks-extensions.txt).
11881 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
11882 connect to directory servers through Tor. Previously, clients needed
11883 to find Tor exits to make private connections to directory servers.
11884 - Avoid choosing Exit nodes for entry or middle hops when the
11885 total bandwidth available from non-Exit nodes is much higher than
11886 the total bandwidth available from Exit nodes.
11887 - Workaround for name servers (like Earthlink's) that hijack failing
11888 DNS requests and replace the no-such-server answer with a "helpful"
11889 redirect to an advertising-driven search portal. Also work around
11890 DNS hijackers who "helpfully" decline to hijack known-invalid
11891 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
11892 lets you turn it off.
11893 - Send out a burst of long-range padding cells once we've established
11894 that we're reachable. Spread them over 4 circuits, so hopefully
11895 a few will be fast. This exercises our bandwidth and bootstraps
11896 us into the directory more quickly.
11898 o New/improved config options:
11899 - Add new config option "ResolvConf" to let the server operator
11900 choose an alternate resolve.conf file when using eventdns.
11901 - Add an "EnforceDistinctSubnets" option to control our "exclude
11902 servers on the same /16" behavior. It's still on by default; this
11903 is mostly for people who want to operate private test networks with
11904 all the machines on the same subnet.
11905 - If one of our entry guards is on the ExcludeNodes list, or the
11906 directory authorities don't think it's a good guard, treat it as
11907 if it were unlisted: stop using it as a guard, and throw it off
11908 the guards list if it stays that way for a long time.
11909 - Allow directory authorities to be marked separately as authorities
11910 for the v1 directory protocol, the v2 directory protocol, and
11911 as hidden service directories, to make it easier to retire old
11912 authorities. V1 authorities should set "HSAuthoritativeDir 1"
11913 to continue being hidden service authorities too.
11914 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
11916 o Minor features, controller:
11917 - Fix CIRC controller events so that controllers can learn the
11918 identity digests of non-Named servers used in circuit paths.
11919 - Let controllers ask for more useful identifiers for servers. Instead
11920 of learning identity digests for un-Named servers and nicknames
11921 for Named servers, the new identifiers include digest, nickname,
11922 and indication of Named status. Off by default; see control-spec.txt
11923 for more information.
11924 - Add a "getinfo address" controller command so it can display Tor's
11925 best guess to the user.
11926 - New controller event to alert the controller when our server
11927 descriptor has changed.
11928 - Give more meaningful errors on controller authentication failure.
11930 o Minor features, other:
11931 - When asked to resolve a hostname, don't use non-exit servers unless
11932 requested to do so. This allows servers with broken DNS to be
11933 useful to the network.
11934 - Divide eventdns log messages into warn and info messages.
11935 - Reserve the nickname "Unnamed" for routers that can't pick
11936 a hostname: any router can call itself Unnamed; directory
11937 authorities will never allocate Unnamed to any particular router;
11938 clients won't believe that any router is the canonical Unnamed.
11939 - Only include function names in log messages for info/debug messages.
11940 For notice/warn/err, the content of the message should be clear on
11941 its own, and printing the function name only confuses users.
11942 - Avoid some false positives during reachability testing: don't try
11943 to test via a server that's on the same /24 as us.
11944 - If we fail to build a circuit to an intended enclave, and it's
11945 not mandatory that we use that enclave, stop wanting it.
11946 - When eventdns is enabled, allow multithreaded builds on NetBSD and
11947 OpenBSD. (We had previously disabled threads on these platforms
11948 because they didn't have working thread-safe resolver functions.)
11950 o Major bugfixes, anonymity/security:
11951 - If a client asked for a server by name, and there's a named server
11952 in our network-status but we don't have its descriptor yet, we
11953 could return an unnamed server instead.
11954 - Fix NetBSD bug that could allow someone to force uninitialized RAM
11955 to be sent to a server's DNS resolver. This only affects NetBSD
11956 and other platforms that do not bounds-check tolower().
11957 - Reject (most) attempts to use Tor circuits with length one. (If
11958 many people start using Tor as a one-hop proxy, exit nodes become
11959 a more attractive target for compromise.)
11960 - Just because your DirPort is open doesn't mean people should be
11961 able to remotely teach you about hidden service descriptors. Now
11962 only accept rendezvous posts if you've got HSAuthoritativeDir set.
11964 o Major bugfixes, other:
11965 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
11966 - When a client asks the server to resolve (not connect to)
11967 an address, and it has a cached answer, give them the cached answer.
11968 Previously, the server would give them no answer at all.
11969 - Allow really slow clients to not hang up five minutes into their
11970 directory downloads (suggested by Adam J. Richter).
11971 - We were building exactly the wrong circuits when we anticipated
11972 hidden service requirements, meaning Tor would have to build all
11973 its circuits on demand.
11974 - Avoid crashing when we mmap a router cache file of size 0.
11975 - When testing reachability of our DirPort, don't launch new
11976 tests when there's already one in progress -- unreachable
11977 servers were stacking up dozens of testing streams.
11979 o Minor bugfixes, correctness:
11980 - If we're a directory mirror and we ask for "all" network status
11981 documents, we would discard status documents from authorities
11982 we don't recognize.
11983 - Avoid a memory corruption bug when creating a hash table for
11985 - Avoid controller-triggered crash when misusing certain commands
11986 from a v0 controller on platforms that do not handle
11987 printf("%s",NULL) gracefully.
11988 - Don't crash when a controller sends a third argument to an
11989 "extendcircuit" request.
11990 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
11991 response; fix error code when "getinfo dir/status/" fails.
11992 - Avoid crash when telling controller stream-status and a stream
11994 - Patch from Adam Langley to fix assert() in eventdns.c.
11995 - Fix a debug log message in eventdns to say "X resolved to Y"
11996 instead of "X resolved to X".
11997 - Make eventdns give strings for DNS errors, not just error numbers.
11998 - Track unreachable entry guards correctly: don't conflate
11999 'unreachable by us right now' with 'listed as down by the directory
12000 authorities'. With the old code, if a guard was unreachable by
12001 us but listed as running, it would clog our guard list forever.
12002 - Behave correctly in case we ever have a network with more than
12003 2GB/s total advertised capacity.
12004 - Make TrackExitHosts case-insensitive, and fix the behavior of
12005 ".suffix" TrackExitHosts items to avoid matching in the middle of
12007 - Finally fix the openssl warnings from newer gccs that believe that
12008 ignoring a return value is okay, but casting a return value and
12009 then ignoring it is a sign of madness.
12010 - Prevent the contrib/exitlist script from printing the same
12011 result more than once.
12012 - Patch from Steve Hildrey: Generate network status correctly on
12013 non-versioning dirservers.
12014 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12015 via Tor; otherwise you'll think you're the exit node's IP address.
12017 o Minor bugfixes, performance:
12018 - Two small performance improvements on parsing descriptors.
12019 - Major performance improvement on inserting descriptors: change
12020 algorithm from O(n^2) to O(n).
12021 - Make the common memory allocation path faster on machines where
12022 malloc(0) returns a pointer.
12023 - Start remembering X-Your-Address-Is directory hints even if you're
12024 a client, so you can become a server more smoothly.
12025 - Avoid duplicate entries on MyFamily line in server descriptor.
12027 o Packaging, features:
12028 - Remove architecture from OS X builds. The official builds are
12029 now universal binaries.
12030 - The Debian package now uses --verify-config when (re)starting,
12031 to distinguish configuration errors from other errors.
12032 - Update RPMs to require libevent 1.1b.
12034 o Packaging, bugfixes:
12035 - Patches so Tor builds with MinGW on Windows.
12036 - Patches so Tor might run on Cygwin again.
12037 - Resume building on non-gcc compilers and ancient gcc. Resume
12038 building with the -O0 compile flag. Resume building cleanly on
12040 - Run correctly on OS X platforms with case-sensitive filesystems.
12041 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12042 - Add autoconf checks so Tor can build on Solaris x86 again.
12045 - Documented (and renamed) ServerDNSSearchDomains and
12046 ServerDNSResolvConfFile options.
12047 - Be clearer that the *ListenAddress directives can be repeated
12051 Changes in version 0.1.1.24 - 2006-09-29
12053 - Allow really slow clients to not hang up five minutes into their
12054 directory downloads (suggested by Adam J. Richter).
12055 - Fix major performance regression from 0.1.0.x: instead of checking
12056 whether we have enough directory information every time we want to
12057 do something, only check when the directory information has changed.
12058 This should improve client CPU usage by 25-50%.
12059 - Don't crash if, after a server has been running for a while,
12060 it can't resolve its hostname.
12063 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12064 - Don't crash when the controller receives a third argument to an
12065 "extendcircuit" request.
12066 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12067 response; fix error code when "getinfo dir/status/" fails.
12068 - Fix configure.in to not produce broken configure files with
12069 more recent versions of autoconf. Thanks to Clint for his auto*
12071 - Fix security bug on NetBSD that could allow someone to force
12072 uninitialized RAM to be sent to a server's DNS resolver. This
12073 only affects NetBSD and other platforms that do not bounds-check
12075 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12076 methods: these are known to be buggy.
12077 - If we're a directory mirror and we ask for "all" network status
12078 documents, we would discard status documents from authorities
12079 we don't recognize.
12082 Changes in version 0.1.2.1-alpha - 2006-08-27
12084 - Add "eventdns" async dns library from Adam Langley, tweaked to
12085 build on OSX and Windows. Only enabled if you pass the
12086 --enable-eventdns argument to configure.
12087 - Allow servers with no hostname or IP address to learn their
12088 IP address by asking the directory authorities. This code only
12089 kicks in when you would normally have exited with a "no address"
12090 error. Nothing's authenticated, so use with care.
12091 - Rather than waiting a fixed amount of time between retrying
12092 application connections, we wait only 5 seconds for the first,
12093 10 seconds for the second, and 15 seconds for each retry after
12094 that. Hopefully this will improve the expected user experience.
12095 - Patch from Tup to add support for transparent AP connections:
12096 this basically bundles the functionality of trans-proxy-tor
12097 into the Tor mainline. Now hosts with compliant pf/netfilter
12098 implementations can redirect TCP connections straight to Tor
12099 without diverting through SOCKS. Needs docs.
12100 - Busy directory servers save lots of memory by spooling server
12101 descriptors, v1 directories, and v2 networkstatus docs to buffers
12102 as needed rather than en masse. Also mmap the cached-routers
12103 files, so we don't need to keep the whole thing in memory too.
12104 - Automatically avoid picking more than one node from the same
12105 /16 network when constructing a circuit.
12106 - Revise and clean up the torrc.sample that we ship with; add
12107 a section for BandwidthRate and BandwidthBurst.
12110 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12111 split connection_t into edge, or, dir, control, and base structs.
12112 These will save quite a bit of memory on busy servers, and they'll
12113 also help us track down bugs in the code and bugs in the spec.
12114 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12115 or later. Log when we are doing this, so we can diagnose it when
12116 it fails. (Also, recommend libevent 1.1b for kqueue and
12117 win32 methods; deprecate libevent 1.0b harder; make libevent
12118 recommendation system saner.)
12119 - Start being able to build universal binaries on OS X (thanks
12121 - Export the default exit policy via the control port, so controllers
12122 don't need to guess what it is / will be later.
12123 - Add a man page entry for ProtocolWarnings.
12124 - Add TestVia config option to the man page.
12125 - Remove even more protocol-related warnings from Tor server logs,
12126 such as bad TLS handshakes and malformed begin cells.
12127 - Stop fetching descriptors if you're not a dir mirror and you
12128 haven't tried to establish any circuits lately. [This currently
12129 causes some dangerous behavior, because when you start up again
12130 you'll use your ancient server descriptors.]
12131 - New DirPort behavior: if you have your dirport set, you download
12132 descriptors aggressively like a directory mirror, whether or not
12133 your ORPort is set.
12134 - Get rid of the router_retry_connections notion. Now routers
12135 no longer try to rebuild long-term connections to directory
12136 authorities, and directory authorities no longer try to rebuild
12137 long-term connections to all servers. We still don't hang up
12138 connections in these two cases though -- we need to look at it
12139 more carefully to avoid flapping, and we likely need to wait til
12140 0.1.1.x is obsolete.
12141 - Drop compatibility with obsolete Tors that permit create cells
12142 to have the wrong circ_id_type.
12143 - Re-enable per-connection rate limiting. Get rid of the "OP
12144 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12145 separate global buckets that apply depending on what sort of conn
12147 - Start publishing one minute or so after we find our ORPort
12148 to be reachable. This will help reduce the number of descriptors
12149 we have for ourselves floating around, since it's quite likely
12150 other things (e.g. DirPort) will change during that minute too.
12151 - Fork the v1 directory protocol into its own spec document,
12152 and mark dir-spec.txt as the currently correct (v2) spec.
12155 - When we find our DirPort to be reachable, publish a new descriptor
12156 so we'll tell the world (reported by pnx).
12157 - Publish a new descriptor after we hup/reload. This is important
12158 if our config has changed such that we'll want to start advertising
12159 our DirPort now, etc.
12160 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12161 - When we have a state file we cannot parse, tell the user and
12162 move it aside. Now we avoid situations where the user starts
12163 Tor in 1904, Tor writes a state file with that timestamp in it,
12164 the user fixes her clock, and Tor refuses to start.
12165 - Fix configure.in to not produce broken configure files with
12166 more recent versions of autoconf. Thanks to Clint for his auto*
12168 - "tor --verify-config" now exits with -1(255) or 0 depending on
12169 whether the config options are bad or good.
12170 - Resolve bug 321 when using dnsworkers: append a period to every
12171 address we resolve at the exit node, so that we do not accidentally
12172 pick up local addresses, and so that failing searches are retried
12173 in the resolver search domains. (This is already solved for
12174 eventdns.) (This breaks Blossom servers for now.)
12175 - If we are using an exit enclave and we can't connect, e.g. because
12176 its webserver is misconfigured to not listen on localhost, then
12177 back off and try connecting from somewhere else before we fail.
12180 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12181 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12182 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12183 when the IP address is mapped through MapAddress to a hostname.
12184 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12185 useless IPv6 DNS resolves.
12186 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12187 before we execute the signal, in case the signal shuts us down.
12188 - Clean up AllowInvalidNodes man page entry.
12189 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12190 - Add more asserts to track down an assert error on a windows Tor
12191 server with connection_add being called with socket == -1.
12192 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12193 - Fix misleading log messages: an entry guard that is "unlisted",
12194 as well as not known to be "down" (because we've never heard
12195 of it), is not therefore "up".
12196 - Remove code to special-case "-cvs" ending, since it has not
12197 actually mattered since 0.0.9.
12198 - Make our socks5 handling more robust to broken socks clients:
12199 throw out everything waiting on the buffer in between socks
12200 handshake phases, since they can't possibly (so the theory
12201 goes) have predicted what we plan to respond to them.
12204 Changes in version 0.1.1.23 - 2006-07-30
12206 - Fast Tor servers, especially exit nodes, were triggering asserts
12207 due to a bug in handling the list of pending DNS resolves. Some
12208 bugs still remain here; we're hunting them.
12209 - Entry guards could crash clients by sending unexpected input.
12210 - More fixes on reachability testing: if you find yourself reachable,
12211 then don't ever make any client requests (so you stop predicting
12212 circuits), then hup or have your clock jump, then later your IP
12213 changes, you won't think circuits are working, so you won't try to
12214 test reachability, so you won't publish.
12217 - Avoid a crash if the controller does a resetconf firewallports
12218 and then a setconf fascistfirewall=1.
12219 - Avoid an integer underflow when the dir authority decides whether
12220 a router is stable: we might wrongly label it stable, and compute
12221 a slightly wrong median stability, when a descriptor is published
12223 - Fix a place where we might trigger an assert if we can't build our
12224 own server descriptor yet.
12227 Changes in version 0.1.1.22 - 2006-07-05
12229 - Fix a big bug that was causing servers to not find themselves
12230 reachable if they changed IP addresses. Since only 0.1.1.22+
12231 servers can do reachability testing correctly, now we automatically
12232 make sure to test via one of these.
12233 - Fix to allow clients and mirrors to learn directory info from
12234 descriptor downloads that get cut off partway through.
12235 - Directory authorities had a bug in deciding if a newly published
12236 descriptor was novel enough to make everybody want a copy -- a few
12237 servers seem to be publishing new descriptors many times a minute.
12239 - Fix a rare bug that was causing some servers to complain about
12240 "closing wedged cpuworkers" and skip some circuit create requests.
12241 - Make the Exit flag in directory status documents actually work.
12244 Changes in version 0.1.1.21 - 2006-06-10
12245 o Crash and assert fixes from 0.1.1.20:
12246 - Fix a rare crash on Tor servers that have enabled hibernation.
12247 - Fix a seg fault on startup for Tor networks that use only one
12248 directory authority.
12249 - Fix an assert from a race condition that occurs on Tor servers
12250 while exiting, where various threads are trying to log that they're
12251 exiting, and delete the logs, at the same time.
12252 - Make our unit tests pass again on certain obscure platforms.
12255 - Add support for building SUSE RPM packages.
12256 - Speed up initial bootstrapping for clients: if we are making our
12257 first ever connection to any entry guard, then don't mark it down
12259 - When only one Tor server in the network is labelled as a guard,
12260 and we've already picked him, we would cycle endlessly picking him
12261 again, being unhappy about it, etc. Now we specifically exclude
12262 current guards when picking a new guard.
12263 - Servers send create cells more reliably after the TLS connection
12264 is established: we were sometimes forgetting to send half of them
12265 when we had more than one pending.
12266 - If we get a create cell that asks us to extend somewhere, but the
12267 Tor server there doesn't match the expected digest, we now send
12268 a destroy cell back, rather than silently doing nothing.
12269 - Make options->RedirectExit work again.
12270 - Make cookie authentication for the controller work again.
12271 - Stop being picky about unusual characters in the arguments to
12272 mapaddress. It's none of our business.
12273 - Add a new config option "TestVia" that lets you specify preferred
12274 middle hops to use for test circuits. Perhaps this will let me
12275 debug the reachability problems better.
12277 o Log / documentation fixes:
12278 - If we're a server and some peer has a broken TLS certificate, don't
12279 log about it unless ProtocolWarnings is set, i.e., we want to hear
12280 about protocol violations by others.
12281 - Fix spelling of VirtualAddrNetwork in man page.
12282 - Add a better explanation at the top of the autogenerated torrc file
12283 about what happened to our old torrc.
12286 Changes in version 0.1.1.20 - 2006-05-23
12288 - Downgrade a log severity where servers complain that they're
12290 - Avoid a compile warning on FreeBSD.
12291 - Remove string size limit on NEWDESC messages; solve bug 291.
12292 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12293 more thoroughly when we're running on windows.
12296 Changes in version 0.1.1.19-rc - 2006-05-03
12298 - Regenerate our local descriptor if it's dirty and we try to use
12299 it locally (e.g. if it changes during reachability detection).
12300 - If we setconf our ORPort to 0, we continued to listen on the
12301 old ORPort and receive connections.
12302 - Avoid a second warning about machine/limits.h on Debian
12304 - Be willing to add our own routerinfo into the routerlist.
12305 Now authorities will include themselves in their directories
12306 and network-statuses.
12307 - Stop trying to upload rendezvous descriptors to every
12308 directory authority: only try the v1 authorities.
12309 - Servers no longer complain when they think they're not
12310 registered with the directory authorities. There were too many
12312 - Backport dist-rpm changes so rpms can be built without errors.
12315 - Implement an option, VirtualAddrMask, to set which addresses
12316 get handed out in response to mapaddress requests. This works
12317 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12320 Changes in version 0.1.1.18-rc - 2006-04-10
12322 - Work harder to download live network-statuses from all the
12323 directory authorities we know about. Improve the threshold
12324 decision logic so we're more robust to edge cases.
12325 - When fetching rendezvous descriptors, we were willing to ask
12326 v2 authorities too, which would always return 404.
12329 - Stop listing down or invalid nodes in the v1 directory. This will
12330 reduce its bulk by about 1/3, and reduce load on directory
12332 - When deciding whether a router is Fast or Guard-worthy, consider
12333 his advertised BandwidthRate and not just the BandwidthCapacity.
12334 - No longer ship INSTALL and README files -- they are useless now.
12335 - Force rpmbuild to behave and honor target_cpu.
12336 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12337 - Start to include translated versions of the tor-doc-*.html
12338 files, along with the screenshots. Still needs more work.
12339 - Start sending back 512 and 451 errors if mapaddress fails,
12340 rather than not sending anything back at all.
12341 - When we fail to bind or listen on an incoming or outgoing
12342 socket, we should close it before failing. otherwise we just
12343 leak it. (thanks to weasel for finding.)
12344 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12345 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12346 - Make NoPublish (even though deprecated) work again.
12347 - Fix a minor security flaw where a versioning auth dirserver
12348 could list a recommended version many times in a row to make
12349 clients more convinced that it's recommended.
12350 - Fix crash bug if there are two unregistered servers running
12351 with the same nickname, one of them is down, and you ask for
12352 them by nickname in your EntryNodes or ExitNodes. Also, try
12353 to pick the one that's running rather than an arbitrary one.
12354 - Fix an infinite loop we could hit if we go offline for too long.
12355 - Complain when we hit WSAENOBUFS on recv() or write() too.
12356 Perhaps this will help us hunt the bug.
12357 - If you're not a versioning dirserver, don't put the string
12358 "client-versions \nserver-versions \n" in your network-status.
12359 - Lower the minimum required number of file descriptors to 1000,
12360 so we can have some overhead for Valgrind on Linux, where the
12361 default ulimit -n is 1024.
12364 - Add tor.dizum.com as the fifth authoritative directory server.
12365 - Add a new config option FetchUselessDescriptors, off by default,
12366 for when you plan to run "exitlist" on your client and you want
12367 to know about even the non-running descriptors.
12370 Changes in version 0.1.1.17-rc - 2006-03-28
12372 - Clients and servers since 0.1.1.10-alpha have been expiring
12373 connections whenever they are idle for 5 minutes and they *do*
12374 have circuits on them. Oops. With this new version, clients will
12375 discard their previous entry guard choices and avoid choosing
12376 entry guards running these flawed versions.
12377 - Fix memory leak when uncompressing concatenated zlib streams. This
12378 was causing substantial leaks over time on Tor servers.
12379 - The v1 directory was including servers as much as 48 hours old,
12380 because that's how the new routerlist->routers works. Now only
12381 include them if they're 20 hours old or less.
12384 - Resume building on irix64, netbsd 2.0, etc.
12385 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12387 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12388 and it is confusing some users.
12389 - Mirrors stop caching the v1 directory so often.
12390 - Make the max number of old descriptors that a cache will hold
12391 rise with the number of directory authorities, so we can scale.
12392 - Change our win32 uname() hack to be more forgiving about what
12393 win32 versions it thinks it's found.
12396 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12398 - When the controller's *setconf commands fail, collect an error
12399 message in a string and hand it back to the controller.
12400 - Make the v2 dir's "Fast" flag based on relative capacity, just
12401 like "Stable" is based on median uptime. Name everything in the
12402 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12403 - Log server fingerprint on startup, so new server operators don't
12404 have to go hunting around their filesystem for it.
12405 - Return a robots.txt on our dirport to discourage google indexing.
12406 - Let the controller ask for GETINFO dir/status/foo so it can ask
12407 directly rather than connecting to the dir port. Only works when
12408 dirport is set for now.
12410 o New config options rather than constants in the code:
12411 - SocksTimeout: How long do we let a socks connection wait
12412 unattached before we fail it?
12413 - CircuitBuildTimeout: Cull non-open circuits that were born
12414 at least this many seconds ago.
12415 - CircuitIdleTimeout: Cull open clean circuits that were born
12416 at least this many seconds ago.
12419 Changes in version 0.1.1.16-rc - 2006-03-18
12420 o Bugfixes on 0.1.1.15-rc:
12421 - Fix assert when the controller asks to attachstream a connect-wait
12422 or resolve-wait stream.
12423 - Now do address rewriting when the controller asks us to attach
12424 to a particular circuit too. This will let Blossom specify
12425 "moria2.exit" without having to learn what moria2's IP address is.
12426 - Make the "tor --verify-config" command-line work again, so people
12427 can automatically check if their torrc will parse.
12428 - Authoritative dirservers no longer require an open connection from
12429 a server to consider him "reachable". We need this change because
12430 when we add new auth dirservers, old servers won't know not to
12432 - Let Tor build on Sun CC again.
12433 - Fix an off-by-one buffer size in dirserv.c that magically never
12434 hit our three authorities but broke sjmurdoch's own tor network.
12435 - If we as a directory mirror don't know of any v1 directory
12436 authorities, then don't try to cache any v1 directories.
12437 - Stop warning about unknown servers in our family when they are
12438 given as hex digests.
12439 - Stop complaining as quickly to the server operator that he
12440 hasn't registered his nickname/key binding.
12441 - Various cleanups so we can add new V2 Auth Dirservers.
12442 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12443 reflect the updated flags in our v2 dir protocol.
12444 - Resume allowing non-printable characters for exit streams (both
12445 for connecting and for resolving). Now we tolerate applications
12446 that don't follow the RFCs. But continue to block malformed names
12449 o Bugfixes on 0.1.0.x:
12450 - Fix assert bug in close_logs(): when we close and delete logs,
12451 remove them all from the global "logfiles" list.
12452 - Fix minor integer overflow in calculating when we expect to use up
12453 our bandwidth allocation before hibernating.
12454 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12455 there are multiple SSLs installed with different versions.
12456 - When we try to be a server and Address is not explicitly set and
12457 our hostname resolves to a private IP address, try to use an
12458 interface address if it has a public address. Now Windows machines
12459 that think of themselves as localhost can work by default.
12462 - Let the controller ask for GETINFO dir/server/foo so it can ask
12463 directly rather than connecting to the dir port.
12464 - Let the controller tell us about certain router descriptors
12465 that it doesn't want Tor to use in circuits. Implement
12466 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12467 - New config option SafeSocks to reject all application connections
12468 using unsafe socks protocols. Defaults to off.
12471 Changes in version 0.1.1.15-rc - 2006-03-11
12472 o Bugfixes and cleanups:
12473 - When we're printing strings from the network, don't try to print
12474 non-printable characters. This protects us against shell escape
12475 sequence exploits, and also against attacks to fool humans into
12476 misreading their logs.
12477 - Fix a bug where Tor would fail to establish any connections if you
12478 left it off for 24 hours and then started it: we were happy with
12479 the obsolete network statuses, but they all referred to router
12480 descriptors that were too old to fetch, so we ended up with no
12481 valid router descriptors.
12482 - Fix a seg fault in the controller's "getinfo orconn-status"
12483 command while listing status on incoming handshaking connections.
12484 Introduce a status name "NEW" for these connections.
12485 - If we get a linelist or linelist_s config option from the torrc
12486 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12487 silently resetting it to its default.
12488 - Don't abandon entry guards until they've been down or gone for
12490 - Cleaner and quieter log messages.
12493 - New controller signal NEWNYM that makes new application requests
12494 use clean circuits.
12495 - Add a new circuit purpose 'controller' to let the controller ask
12496 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12497 controller command to let you specify the purpose if you're
12498 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12499 command to let you change a circuit's purpose after it's been
12501 - Accept "private:*" in routerdesc exit policies; not generated yet
12502 because older Tors do not understand it.
12503 - Add BSD-style contributed startup script "rc.subr" from Peter
12507 Changes in version 0.1.1.14-alpha - 2006-02-20
12508 o Bugfixes on 0.1.1.x:
12509 - Don't die if we ask for a stdout or stderr log (even implicitly)
12510 and we're set to RunAsDaemon -- just warn.
12511 - We still had a few bugs in the OR connection rotation code that
12512 caused directory servers to slowly aggregate connections to other
12513 fast Tor servers. This time for sure!
12514 - Make log entries on Win32 include the name of the function again.
12515 - We were treating a pair of exit policies if they were equal even
12516 if one said accept and the other said reject -- causing us to
12517 not always publish a new descriptor since we thought nothing
12519 - Retry pending server downloads as well as pending networkstatus
12520 downloads when we unexpectedly get a socks request.
12521 - We were ignoring the IS_FAST flag in the directory status,
12522 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12524 - If the controller's SAVECONF command fails (e.g. due to file
12525 permissions), let the controller know that it failed.
12528 - If we're trying to be a Tor server and running Windows 95/98/ME
12529 as a server, explain that we'll likely crash.
12530 - When we're a server, a client asks for an old-style directory,
12531 and our write bucket is empty, don't give it to him. This way
12532 small servers can continue to serve the directory *sometimes*,
12533 without getting overloaded.
12534 - Compress exit policies even more -- look for duplicate lines
12536 - Clients now honor the "guard" flag in the router status when
12537 picking entry guards, rather than looking at is_fast or is_stable.
12538 - Retain unrecognized lines in $DATADIR/state file, so that we can
12539 be forward-compatible.
12540 - Generate 18.0.0.0/8 address policy format in descs when we can;
12541 warn when the mask is not reducible to a bit-prefix.
12542 - Let the user set ControlListenAddress in the torrc. This can be
12543 dangerous, but there are some cases (like a secured LAN) where it
12545 - Split ReachableAddresses into ReachableDirAddresses and
12546 ReachableORAddresses, so we can restrict Dir conns to port 80
12547 and OR conns to port 443.
12548 - Now we can target arch and OS in rpm builds (contributed by
12549 Phobos). Also make the resulting dist-rpm filename match the
12551 - New config options to help controllers: FetchServerDescriptors
12552 and FetchHidServDescriptors for whether to fetch server
12553 info and hidserv info or let the controller do it, and
12554 PublishServerDescriptor and PublishHidServDescriptors.
12555 - Also let the controller set the __AllDirActionsPrivate config
12556 option if you want all directory fetches/publishes to happen via
12557 Tor (it assumes your controller bootstraps your circuits).
12560 Changes in version 0.1.0.17 - 2006-02-17
12561 o Crash bugfixes on 0.1.0.x:
12562 - When servers with a non-zero DirPort came out of hibernation,
12563 sometimes they would trigger an assert.
12565 o Other important bugfixes:
12566 - On platforms that don't have getrlimit (like Windows), we were
12567 artificially constraining ourselves to a max of 1024
12568 connections. Now just assume that we can handle as many as 15000
12569 connections. Hopefully this won't cause other problems.
12571 o Backported features:
12572 - When we're a server, a client asks for an old-style directory,
12573 and our write bucket is empty, don't give it to him. This way
12574 small servers can continue to serve the directory *sometimes*,
12575 without getting overloaded.
12576 - Whenever you get a 503 in response to a directory fetch, try
12577 once more. This will become important once servers start sending
12578 503's whenever they feel busy.
12579 - Fetch a new directory every 120 minutes, not every 40 minutes.
12580 Now that we have hundreds of thousands of users running the old
12581 directory algorithm, it's starting to hurt a lot.
12582 - Bump up the period for forcing a hidden service descriptor upload
12583 from 20 minutes to 1 hour.
12586 Changes in version 0.1.1.13-alpha - 2006-02-09
12587 o Crashes in 0.1.1.x:
12588 - When you tried to setconf ORPort via the controller, Tor would
12589 crash. So people using TorCP to become a server were sad.
12590 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12591 servers. The problem appears to be something do with OpenSSL's
12592 random number generation, or how we call it, or something. Let me
12593 know if the crashes continue.
12594 - Turn crypto hardware acceleration off by default, until we find
12595 somebody smart who can test it for us. (It appears to produce
12596 seg faults in at least some cases.)
12597 - Fix a rare assert error when we've tried all intro points for
12598 a hidden service and we try fetching the service descriptor again:
12599 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12602 - Fix a major load balance bug: we were round-robining in 16 KB
12603 chunks, and servers with bandwidthrate of 20 KB, while downloading
12604 a 600 KB directory, would starve their other connections. Now we
12605 try to be a bit more fair.
12606 - Dir authorities and mirrors were never expiring the newest
12607 descriptor for each server, causing memory and directory bloat.
12608 - Fix memory-bloating and connection-bloating bug on servers: We
12609 were never closing any connection that had ever had a circuit on
12610 it, because we were checking conn->n_circuits == 0, yet we had a
12611 bug that let it go negative.
12612 - Make Tor work using squid as your http proxy again -- squid
12613 returns an error if you ask for a URL that's too long, and it uses
12614 a really generic error message. Plus, many people are behind a
12615 transparent squid so they don't even realize it.
12616 - On platforms that don't have getrlimit (like Windows), we were
12617 artificially constraining ourselves to a max of 1024
12618 connections. Now just assume that we can handle as many as 15000
12619 connections. Hopefully this won't cause other problems.
12620 - Add a new config option ExitPolicyRejectPrivate which defaults to
12621 1. This means all exit policies will begin with rejecting private
12622 addresses, unless the server operator explicitly turns it off.
12625 - Clients no longer download descriptors for non-running
12627 - Before we add new directory authorities, we should make it
12628 clear that only v1 authorities should receive/publish hidden
12629 service descriptors.
12632 - As soon as we've fetched some more directory info, immediately
12633 try to download more server descriptors. This way we don't have
12634 a 10 second pause during initial bootstrapping.
12635 - Remove even more loud log messages that the server operator can't
12637 - When we're running an obsolete or un-recommended version, make
12638 the log message more clear about what the problem is and what
12639 versions *are* still recommended.
12640 - Provide a more useful warn message when our onion queue gets full:
12641 the CPU is too slow or the exit policy is too liberal.
12642 - Don't warn when we receive a 503 from a dirserver/cache -- this
12643 will pave the way for them being able to refuse if they're busy.
12644 - When we fail to bind a listener, try to provide a more useful
12645 log message: e.g., "Is Tor already running?"
12646 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12647 Goldberg can prove things about our handshake protocol more
12649 - MaxConn has been obsolete for a while now. Document the ConnLimit
12650 config option, which is a *minimum* number of file descriptors
12651 that must be available else Tor refuses to start.
12652 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12653 if you log to syslog and want something other than LOG_DAEMON.
12654 - Make dirservers generate a separate "guard" flag to mean,
12655 "would make a good entry guard". Make clients parse it and vote
12656 on it. Not used by clients yet.
12657 - Implement --with-libevent-dir option to ./configure. Also, improve
12658 search techniques to find libevent, and use those for openssl too.
12659 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12660 - Only start testing reachability once we've established a
12661 circuit. This will make startup on dirservers less noisy.
12662 - Don't try to upload hidden service descriptors until we have
12663 established a circuit.
12664 - Fix the controller's "attachstream 0" command to treat conn like
12665 it just connected, doing address remapping, handling .exit and
12666 .onion idioms, and so on. Now we're more uniform in making sure
12667 that the controller hears about new and closing connections.
12670 Changes in version 0.1.1.12-alpha - 2006-01-11
12671 o Bugfixes on 0.1.1.x:
12672 - The fix to close duplicate server connections was closing all
12673 Tor client connections if they didn't establish a circuit
12674 quickly enough. Oops.
12675 - Fix minor memory issue (double-free) that happened on exit.
12677 o Bugfixes on 0.1.0.x:
12678 - Tor didn't warn when it failed to open a log file.
12681 Changes in version 0.1.1.11-alpha - 2006-01-10
12682 o Crashes in 0.1.1.x:
12683 - Include all the assert/crash fixes from 0.1.0.16.
12684 - If you start Tor and then quit very quickly, there were some
12685 races that tried to free things that weren't allocated yet.
12686 - Fix a rare memory stomp if you're running hidden services.
12687 - Fix segfault when specifying DirServer in config without nickname.
12688 - Fix a seg fault when you finish connecting to a server but at
12689 that moment you dump his server descriptor.
12690 - Extendcircuit and Attachstream controller commands would
12691 assert/crash if you don't give them enough arguments.
12692 - Fix an assert error when we're out of space in the connection_list
12693 and we try to post a hidden service descriptor (reported by weasel).
12694 - If you specify a relative torrc path and you set RunAsDaemon in
12695 your torrc, then it chdir()'s to the new directory. If you HUP,
12696 it tries to load the new torrc location, fails, and exits.
12697 The fix: no longer allow a relative path to torrc using -f.
12700 - Implement "entry guards": automatically choose a handful of entry
12701 nodes and stick with them for all circuits. Only pick new guards
12702 when the ones you have are unsuitable, and if the old guards
12703 become suitable again, switch back. This will increase security
12704 dramatically against certain end-point attacks. The EntryNodes
12705 config option now provides some hints about which entry guards you
12706 want to use most; and StrictEntryNodes means to only use those.
12707 - New directory logic: download by descriptor digest, not by
12708 fingerprint. Caches try to download all listed digests from
12709 authorities; clients try to download "best" digests from caches.
12710 This avoids partitioning and isolating attacks better.
12711 - Make the "stable" router flag in network-status be the median of
12712 the uptimes of running valid servers, and make clients pay
12713 attention to the network-status flags. Thus the cutoff adapts
12714 to the stability of the network as a whole, making IRC, IM, etc
12715 connections more reliable.
12718 - Tor servers with dynamic IP addresses were needing to wait 18
12719 hours before they could start doing reachability testing using
12720 the new IP address and ports. This is because they were using
12721 the internal descriptor to learn what to test, yet they were only
12722 rebuilding the descriptor once they decided they were reachable.
12723 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12724 to download certain server descriptors, throw them away, and then
12725 fetch them again after 30 minutes. Now mirrors throw away these
12726 server descriptors so clients can't get them.
12727 - We were leaving duplicate connections to other ORs open for a week,
12728 rather than closing them once we detect a duplicate. This only
12729 really affected authdirservers, but it affected them a lot.
12730 - Spread the authdirservers' reachability testing over the entire
12731 testing interval, so we don't try to do 500 TLS's at once every
12735 - If the network is down, and we try to connect to a conn because
12736 we have a circuit in mind, and we timeout (30 seconds) because the
12737 network never answers, we were expiring the circuit, but we weren't
12738 obsoleting the connection or telling the entry_guards functions.
12739 - Some Tor servers process billions of cells per day. These statistics
12740 need to be uint64_t's.
12741 - Check for integer overflows in more places, when adding elements
12742 to smartlists. This could possibly prevent a buffer overflow
12743 on malicious huge inputs. I don't see any, but I haven't looked
12745 - ReachableAddresses kept growing new "reject *:*" lines on every
12747 - When you "setconf log" via the controller, it should remove all
12748 logs. We were automatically adding back in a "log notice stdout".
12749 - Newly bootstrapped Tor networks couldn't establish hidden service
12750 circuits until they had nodes with high uptime. Be more tolerant.
12751 - We were marking servers down when they could not answer every piece
12752 of the directory request we sent them. This was far too harsh.
12753 - Fix the torify (tsocks) config file to not use Tor for localhost
12755 - Directory authorities now go to the proper authority when asking for
12756 a networkstatus, even when they want a compressed one.
12757 - Fix a harmless bug that was causing Tor servers to log
12758 "Got an end because of misc error, but we're not an AP. Closing."
12759 - Authorities were treating their own descriptor changes as cosmetic,
12760 meaning the descriptor available in the network-status and the
12761 descriptor that clients downloaded were different.
12762 - The OS X installer was adding a symlink for tor_resolve but
12763 the binary was called tor-resolve (reported by Thomas Hardly).
12764 - Workaround a problem with some http proxies where they refuse GET
12765 requests that specify "Content-Length: 0" (reported by Adrian).
12766 - Fix wrong log message when you add a "HiddenServiceNodes" config
12767 line without any HiddenServiceDir line (reported by Chris Thomas).
12770 - Write the TorVersion into the state file so we have a prayer of
12771 keeping forward and backward compatibility.
12772 - Revive the FascistFirewall config option rather than eliminating it:
12773 now it's a synonym for ReachableAddresses *:80,*:443.
12774 - Clients choose directory servers from the network status lists,
12775 not from their internal list of router descriptors. Now they can
12776 go to caches directly rather than needing to go to authorities
12778 - Directory authorities ignore router descriptors that have only
12779 cosmetic differences: do this for 0.1.0.x servers now too.
12780 - Add a new flag to network-status indicating whether the server
12781 can answer v2 directory requests too.
12782 - Authdirs now stop whining so loudly about bad descriptors that
12783 they fetch from other dirservers. So when there's a log complaint,
12784 it's for sure from a freshly uploaded descriptor.
12785 - Reduce memory requirements in our structs by changing the order
12787 - There used to be two ways to specify your listening ports in a
12788 server descriptor: on the "router" line and with a separate "ports"
12789 line. Remove support for the "ports" line.
12790 - New config option "AuthDirRejectUnlisted" for auth dirservers as
12791 a panic button: if we get flooded with unusable servers we can
12792 revert to only listing servers in the approved-routers file.
12793 - Auth dir servers can now mark a fingerprint as "!reject" or
12794 "!invalid" in the approved-routers file (as its nickname), to
12795 refuse descriptors outright or include them but marked as invalid.
12796 - Servers store bandwidth history across restarts/crashes.
12797 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
12798 get a better idea of why their circuits failed. Not used yet.
12799 - Directory mirrors now cache up to 16 unrecognized network-status
12800 docs. Now we can add new authdirservers and they'll be cached too.
12801 - When picking a random directory, prefer non-authorities if any
12803 - New controller option "getinfo desc/all-recent" to fetch the
12804 latest server descriptor for every router that Tor knows about.
12807 Changes in version 0.1.0.16 - 2006-01-02
12808 o Crash bugfixes on 0.1.0.x:
12809 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12810 corrupting the heap, losing FDs, or crashing when we need to resize
12811 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12812 - It turns out sparc64 platforms crash on unaligned memory access
12813 too -- so detect and avoid this.
12814 - Handle truncated compressed data correctly (by detecting it and
12816 - Fix possible-but-unlikely free(NULL) in control.c.
12817 - When we were closing connections, there was a rare case that
12818 stomped on memory, triggering seg faults and asserts.
12819 - Avoid potential infinite recursion when building a descriptor. (We
12820 don't know that it ever happened, but better to fix it anyway.)
12821 - We were neglecting to unlink marked circuits from soon-to-close OR
12822 connections, which caused some rare scribbling on freed memory.
12823 - Fix a memory stomping race bug when closing the joining point of two
12824 rendezvous circuits.
12825 - Fix an assert in time parsing found by Steven Murdoch.
12827 o Other bugfixes on 0.1.0.x:
12828 - When we're doing reachability testing, provide more useful log
12829 messages so the operator knows what to expect.
12830 - Do not check whether DirPort is reachable when we are suppressing
12831 advertising it because of hibernation.
12832 - When building with -static or on Solaris, we sometimes needed -ldl.
12833 - When we're deciding whether a stream has enough circuits around
12834 that can handle it, count the freshly dirty ones and not the ones
12835 that are so dirty they won't be able to handle it.
12836 - When we're expiring old circuits, we had a logic error that caused
12837 us to close new rendezvous circuits rather than old ones.
12838 - Give a more helpful log message when you try to change ORPort via
12839 the controller: you should upgrade Tor if you want that to work.
12840 - We were failing to parse Tor versions that start with "Tor ".
12841 - Tolerate faulty streams better: when a stream fails for reason
12842 exitpolicy, stop assuming that the router is lying about his exit
12843 policy. When a stream fails for reason misc, allow it to retry just
12844 as if it was resolvefailed. When a stream has failed three times,
12845 reset its failure count so we can try again and get all three tries.
12848 Changes in version 0.1.1.10-alpha - 2005-12-11
12849 o Correctness bugfixes on 0.1.0.x:
12850 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
12851 corrupting the heap, losing FDs, or crashing when we need to resize
12852 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
12853 - Stop doing the complex voodoo overkill checking for insecure
12854 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
12855 - When we were closing connections, there was a rare case that
12856 stomped on memory, triggering seg faults and asserts.
12857 - We were neglecting to unlink marked circuits from soon-to-close OR
12858 connections, which caused some rare scribbling on freed memory.
12859 - When we're deciding whether a stream has enough circuits around
12860 that can handle it, count the freshly dirty ones and not the ones
12861 that are so dirty they won't be able to handle it.
12862 - Recover better from TCP connections to Tor servers that are
12863 broken but don't tell you (it happens!); and rotate TLS
12864 connections once a week.
12865 - When we're expiring old circuits, we had a logic error that caused
12866 us to close new rendezvous circuits rather than old ones.
12867 - Fix a scary-looking but apparently harmless bug where circuits
12868 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
12869 servers, and never switch to state CIRCUIT_STATE_OPEN.
12870 - When building with -static or on Solaris, we sometimes needed to
12872 - Give a useful message when people run Tor as the wrong user,
12873 rather than telling them to start chowning random directories.
12874 - We were failing to inform the controller about new .onion streams.
12876 o Security bugfixes on 0.1.0.x:
12877 - Refuse server descriptors if the fingerprint line doesn't match
12878 the included identity key. Tor doesn't care, but other apps (and
12879 humans) might actually be trusting the fingerprint line.
12880 - We used to kill the circuit when we receive a relay command we
12881 don't recognize. Now we just drop it.
12882 - Start obeying our firewall options more rigorously:
12883 . If we can't get to a dirserver directly, try going via Tor.
12884 . Don't ever try to connect (as a client) to a place our
12885 firewall options forbid.
12886 . If we specify a proxy and also firewall options, obey the
12887 firewall options even when we're using the proxy: some proxies
12888 can only proxy to certain destinations.
12889 - Fix a bug found by Lasse Overlier: when we were making internal
12890 circuits (intended to be cannibalized later for rendezvous and
12891 introduction circuits), we were picking them so that they had
12892 useful exit nodes. There was no need for this, and it actually
12893 aids some statistical attacks.
12894 - Start treating internal circuits and exit circuits separately.
12895 It's important to keep them separate because internal circuits
12896 have their last hops picked like middle hops, rather than like
12897 exit hops. So exiting on them will break the user's expectations.
12899 o Bugfixes on 0.1.1.x:
12900 - Take out the mis-feature where we tried to detect IP address
12901 flapping for people with DynDNS, and chose not to upload a new
12902 server descriptor sometimes.
12903 - Try to be compatible with OpenSSL 0.9.6 again.
12904 - Log fix: when the controller is logging about .onion addresses,
12905 sometimes it didn't include the ".onion" part of the address.
12906 - Don't try to modify options->DirServers internally -- if the
12907 user didn't specify any, just add the default ones directly to
12908 the trusted dirserver list. This fixes a bug where people running
12909 controllers would use SETCONF on some totally unrelated config
12910 option, and Tor would start yelling at them about changing their
12912 - Let the controller's redirectstream command specify a port, in
12913 case the controller wants to change that too.
12914 - When we requested a pile of server descriptors, we sometimes
12915 accidentally launched a duplicate request for the first one.
12916 - Bugfix for trackhostexits: write down the fingerprint of the
12917 chosen exit, not its nickname, because the chosen exit might not
12919 - When parsing foo.exit, if foo is unknown, and we are leaving
12920 circuits unattached, set the chosen_exit field and leave the
12921 address empty. This matters because controllers got confused
12923 - Directory authorities no longer try to download server
12924 descriptors that they know they will reject.
12926 o Features and updates:
12927 - Replace balanced trees with hash tables: this should make stuff
12928 significantly faster.
12929 - Resume using the AES counter-mode implementation that we ship,
12930 rather than OpenSSL's. Ours is significantly faster.
12931 - Many other CPU and memory improvements.
12932 - Add a new config option FastFirstHopPK (on by default) so clients
12933 do a trivial crypto handshake for their first hop, since TLS has
12934 already taken care of confidentiality and authentication.
12935 - Add a new config option TestSocks so people can see if their
12936 applications are using socks4, socks4a, socks5-with-ip, or
12937 socks5-with-hostname. This way they don't have to keep mucking
12938 with tcpdump and wondering if something got cached somewhere.
12939 - Warn when listening on a public address for socks. I suspect a
12940 lot of people are setting themselves up as open socks proxies,
12941 and they have no idea that jerks on the Internet are using them,
12942 since they simply proxy the traffic into the Tor network.
12943 - Add "private:*" as an alias in configuration for policies. Now
12944 you can simplify your exit policy rather than needing to list
12945 every single internal or nonroutable network space.
12946 - Add a new controller event type that allows controllers to get
12947 all server descriptors that were uploaded to a router in its role
12948 as authoritative dirserver.
12949 - Start shipping socks-extensions.txt, tor-doc-unix.html,
12950 tor-doc-server.html, and stylesheet.css in the tarball.
12951 - Stop shipping tor-doc.html in the tarball.
12954 Changes in version 0.1.1.9-alpha - 2005-11-15
12955 o Usability improvements:
12956 - Start calling it FooListenAddress rather than FooBindAddress,
12957 since few of our users know what it means to bind an address
12959 - Reduce clutter in server logs. We're going to try to make
12960 them actually usable now. New config option ProtocolWarnings that
12961 lets you hear about how _other Tors_ are breaking the protocol. Off
12963 - Divide log messages into logging domains. Once we put some sort
12964 of interface on this, it will let people looking at more verbose
12965 log levels specify the topics they want to hear more about.
12966 - Make directory servers return better http 404 error messages
12967 instead of a generic "Servers unavailable".
12968 - Check for even more Windows version flags when writing the platform
12969 string in server descriptors, and note any we don't recognize.
12970 - Clean up more of the OpenSSL memory when exiting, so we can detect
12971 memory leaks better.
12972 - Make directory authorities be non-versioning, non-naming by
12973 default. Now we can add new directory servers without requiring
12974 their operators to pay close attention.
12975 - When logging via syslog, include the pid whenever we provide
12976 a log entry. Suggested by Todd Fries.
12978 o Performance improvements:
12979 - Directory servers now silently throw away new descriptors that
12980 haven't changed much if the timestamps are similar. We do this to
12981 tolerate older Tor servers that upload a new descriptor every 15
12982 minutes. (It seemed like a good idea at the time.)
12983 - Inline bottleneck smartlist functions; use fast versions by default.
12984 - Add a "Map from digest to void*" abstraction digestmap_t so we
12985 can do less hex encoding/decoding. Use it in router_get_by_digest()
12986 to resolve a performance bottleneck.
12987 - Allow tor_gzip_uncompress to extract as much as possible from
12988 truncated compressed data. Try to extract as many
12989 descriptors as possible from truncated http responses (when
12990 DIR_PURPOSE_FETCH_ROUTERDESC).
12991 - Make circ->onionskin a pointer, not a static array. moria2 was using
12992 125000 circuit_t's after it had been up for a few weeks, which
12993 translates to 20+ megs of wasted space.
12994 - The private half of our EDH handshake keys are now chosen out
12995 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
12997 o Security improvements:
12998 - Start making directory caches retain old routerinfos, so soon
12999 clients can start asking by digest of descriptor rather than by
13000 fingerprint of server.
13001 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13002 to use egd (if present), openbsd weirdness (if present), vms/os2
13003 weirdness (if we ever port there), and more in the future.
13005 o Bugfixes on 0.1.0.x:
13006 - Do round-robin writes of at most 16 kB per write. This might be
13007 more fair on loaded Tor servers, and it might resolve our Windows
13008 crash bug. It might also slow things down.
13009 - Our TLS handshakes were generating a single public/private
13010 keypair for the TLS context, rather than making a new one for
13011 each new connections. Oops. (But we were still rotating them
13012 periodically, so it's not so bad.)
13013 - When we were cannibalizing a circuit with a particular exit
13014 node in mind, we weren't checking to see if that exit node was
13015 already present earlier in the circuit. Oops.
13016 - When a Tor server's IP changes (e.g. from a dyndns address),
13017 upload a new descriptor so clients will learn too.
13018 - Really busy servers were keeping enough circuits open on stable
13019 connections that they were wrapping around the circuit_id
13020 space. (It's only two bytes.) This exposed a bug where we would
13021 feel free to reuse a circuit_id even if it still exists but has
13022 been marked for close. Try to fix this bug. Some bug remains.
13023 - If we would close a stream early (e.g. it asks for a .exit that
13024 we know would refuse it) but the LeaveStreamsUnattached config
13025 option is set by the controller, then don't close it.
13027 o Bugfixes on 0.1.1.8-alpha:
13028 - Fix a big pile of memory leaks, some of them serious.
13029 - Do not try to download a routerdesc if we would immediately reject
13031 - Resume inserting a newline between all router descriptors when
13032 generating (old style) signed directories, since our spec says
13034 - When providing content-type application/octet-stream for
13035 server descriptors using .z, we were leaving out the
13036 content-encoding header. Oops. (Everything tolerated this just
13037 fine, but that doesn't mean we need to be part of the problem.)
13038 - Fix a potential seg fault in getconf and getinfo using version 1
13039 of the controller protocol.
13040 - Avoid crash: do not check whether DirPort is reachable when we
13041 are suppressing it because of hibernation.
13042 - Make --hash-password not crash on exit.
13045 Changes in version 0.1.1.8-alpha - 2005-10-07
13046 o New features (major):
13047 - Clients don't download or use the directory anymore. Now they
13048 download and use network-statuses from the trusted dirservers,
13049 and fetch individual server descriptors as needed from mirrors.
13050 See dir-spec.txt for all the gory details.
13051 - Be more conservative about whether to advertise our DirPort.
13052 The main change is to not advertise if we're running at capacity
13053 and either a) we could hibernate or b) our capacity is low and
13054 we're using a default DirPort.
13055 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13057 o New features (minor):
13058 - Try to be smart about when to retry network-status and
13059 server-descriptor fetches. Still needs some tuning.
13060 - Stop parsing, storing, or using running-routers output (but
13061 mirrors still cache and serve it).
13062 - Consider a threshold of versioning dirservers (dirservers who have
13063 an opinion about which Tor versions are still recommended) before
13064 deciding whether to warn the user that he's obsolete.
13065 - Dirservers can now reject/invalidate by key and IP, with the
13066 config options "AuthDirInvalid" and "AuthDirReject". This is
13067 useful since currently we automatically list servers as running
13068 and usable even if we know they're jerks.
13069 - Provide dire warnings to any users who set DirServer; move it out
13070 of torrc.sample and into torrc.complete.
13071 - Add MyFamily to torrc.sample in the server section.
13072 - Add nicknames to the DirServer line, so we can refer to them
13073 without requiring all our users to memorize their IP addresses.
13074 - When we get an EOF or a timeout on a directory connection, note
13075 how many bytes of serverdesc we are dropping. This will help
13076 us determine whether it is smart to parse incomplete serverdesc
13078 - Add a new function to "change pseudonyms" -- that is, to stop
13079 using any currently-dirty circuits for new streams, so we don't
13080 link new actions to old actions. Currently it's only called on
13081 HUP (or SIGNAL RELOAD).
13082 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13083 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13084 OpenSSL. Also, reseed our entropy every hour, not just at
13085 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13087 o Fixes on 0.1.1.7-alpha:
13088 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13089 version 0, so don't let version 0 controllers ask for it.
13090 - If you requested something with too many newlines via the
13091 v1 controller protocol, you could crash tor.
13092 - Fix a number of memory leaks, including some pretty serious ones.
13093 - Re-enable DirPort testing again, so Tor servers will be willing
13094 to advertise their DirPort if it's reachable.
13095 - On TLS handshake, only check the other router's nickname against
13096 its expected nickname if is_named is set.
13098 o Fixes forward-ported from 0.1.0.15:
13099 - Don't crash when we don't have any spare file descriptors and we
13100 try to spawn a dns or cpu worker.
13101 - Make the numbers in read-history and write-history into uint64s,
13102 so they don't overflow and publish negatives in the descriptor.
13104 o Fixes on 0.1.0.x:
13105 - For the OS X package's modified privoxy config file, comment
13106 out the "logfile" line so we don't log everything passed
13108 - We were whining about using socks4 or socks5-with-local-lookup
13109 even when it's an IP in the "virtual" range we designed exactly
13111 - We were leaking some memory every time the client changes IPs.
13112 - Never call free() on tor_malloc()d memory. This will help us
13113 use dmalloc to detect memory leaks.
13114 - Check for named servers when looking them up by nickname;
13115 warn when we'recalling a non-named server by its nickname;
13116 don't warn twice about the same name.
13117 - Try to list MyFamily elements by key, not by nickname, and warn
13118 if we've not heard of the server.
13119 - Make windows platform detection (uname equivalent) smarter.
13120 - It turns out sparc64 doesn't like unaligned access either.
13123 Changes in version 0.1.0.15 - 2005-09-23
13124 o Bugfixes on 0.1.0.x:
13125 - Reject ports 465 and 587 (spam targets) in default exit policy.
13126 - Don't crash when we don't have any spare file descriptors and we
13127 try to spawn a dns or cpu worker.
13128 - Get rid of IgnoreVersion undocumented config option, and make us
13129 only warn, never exit, when we're running an obsolete version.
13130 - Don't try to print a null string when your server finds itself to
13131 be unreachable and the Address config option is empty.
13132 - Make the numbers in read-history and write-history into uint64s,
13133 so they don't overflow and publish negatives in the descriptor.
13134 - Fix a minor memory leak in smartlist_string_remove().
13135 - We were only allowing ourselves to upload a server descriptor at
13136 most every 20 minutes, even if it changed earlier than that.
13137 - Clean up log entries that pointed to old URLs.
13140 Changes in version 0.1.1.7-alpha - 2005-09-14
13141 o Fixes on 0.1.1.6-alpha:
13142 - Exit servers were crashing when people asked them to make a
13143 connection to an address not in their exit policy.
13144 - Looking up a non-existent stream for a v1 control connection would
13146 - Fix a seg fault if we ask a dirserver for a descriptor by
13147 fingerprint but he doesn't know about him.
13148 - SETCONF was appending items to linelists, not clearing them.
13149 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13150 out and refuse the setconf if it would fail.
13151 - Downgrade the dirserver log messages when whining about
13155 - Add Peter Palfrader's check-tor script to tor/contrib/
13156 It lets you easily check whether a given server (referenced by
13157 nickname) is reachable by you.
13158 - Numerous changes to move towards client-side v2 directories. Not
13161 o Fixes on 0.1.0.x:
13162 - If the user gave tor an odd number of command-line arguments,
13163 we were silently ignoring the last one. Now we complain and fail.
13164 [This wins the oldest-bug prize -- this bug has been present since
13165 November 2002, as released in Tor 0.0.0.]
13166 - Do not use unaligned memory access on alpha, mips, or mipsel.
13167 It *works*, but is very slow, so we treat them as if it doesn't.
13168 - Retry directory requests if we fail to get an answer we like
13169 from a given dirserver (we were retrying before, but only if
13170 we fail to connect).
13171 - When writing the RecommendedVersions line, sort them first.
13172 - When the client asked for a rendezvous port that the hidden
13173 service didn't want to provide, we were sending an IP address
13174 back along with the end cell. Fortunately, it was zero. But stop
13176 - Correct "your server is reachable" log entries to indicate that
13177 it was self-testing that told us so.
13180 Changes in version 0.1.1.6-alpha - 2005-09-09
13181 o Fixes on 0.1.1.5-alpha:
13182 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13183 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13184 - Fix bug with tor_memmem finding a match at the end of the string.
13185 - Make unit tests run without segfaulting.
13186 - Resolve some solaris x86 compile warnings.
13187 - Handle duplicate lines in approved-routers files without warning.
13188 - Fix bug where as soon as a server refused any requests due to his
13189 exit policy (e.g. when we ask for localhost and he tells us that's
13190 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13191 exit policy using him for any exits.
13192 - Only do openssl hardware accelerator stuff if openssl version is
13195 o New controller features/fixes:
13196 - Add a "RESETCONF" command so you can set config options like
13197 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13198 a config option in the torrc with no value, then it clears it
13199 entirely (rather than setting it to its default).
13200 - Add a "GETINFO config-file" to tell us where torrc is.
13201 - Avoid sending blank lines when GETINFO replies should be empty.
13202 - Add a QUIT command for the controller (for using it manually).
13203 - Fix a bug in SAVECONF that was adding default dirservers and
13204 other redundant entries to the torrc file.
13206 o Start on the new directory design:
13207 - Generate, publish, cache, serve new network-status format.
13208 - Publish individual descriptors (by fingerprint, by "all", and by
13210 - Publish client and server recommended versions separately.
13211 - Allow tor_gzip_uncompress() to handle multiple concatenated
13212 compressed strings. Serve compressed groups of router
13213 descriptors. The compression logic here could be more
13215 - Distinguish v1 authorities (all currently trusted directories)
13216 from v2 authorities (all trusted directories).
13217 - Change DirServers config line to note which dirs are v1 authorities.
13218 - Add configuration option "V1AuthoritativeDirectory 1" which
13219 moria1, moria2, and tor26 should set.
13220 - Remove option when getting directory cache to see whether they
13221 support running-routers; they all do now. Replace it with one
13222 to see whether caches support v2 stuff.
13225 - Dirservers now do their own external reachability testing of each
13226 Tor server, and only list them as running if they've been found to
13227 be reachable. We also send back warnings to the server's logs if
13228 it uploads a descriptor that we already believe is unreachable.
13229 - Implement exit enclaves: if we know an IP address for the
13230 destination, and there's a running Tor server at that address
13231 which allows exit to the destination, then extend the circuit to
13232 that exit first. This provides end-to-end encryption and end-to-end
13233 authentication. Also, if the user wants a .exit address or enclave,
13234 use 4 hops rather than 3, and cannibalize a general circ for it
13236 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13237 controller. Also, rotate dns and cpu workers if the controller
13238 changes options that will affect them; and initialize the dns
13239 worker cache tree whether or not we start out as a server.
13240 - Only upload a new server descriptor when options change, 18
13241 hours have passed, uptime is reset, or bandwidth changes a lot.
13242 - Check [X-]Forwarded-For headers in HTTP requests when generating
13243 log messages. This lets people run dirservers (and caches) behind
13244 Apache but still know which IP addresses are causing warnings.
13246 o Config option changes:
13247 - Replace (Fascist)Firewall* config options with a new
13248 ReachableAddresses option that understands address policies.
13249 For example, "ReachableAddresses *:80,*:443"
13250 - Get rid of IgnoreVersion undocumented config option, and make us
13251 only warn, never exit, when we're running an obsolete version.
13252 - Make MonthlyAccountingStart config option truly obsolete now.
13254 o Fixes on 0.1.0.x:
13255 - Reject ports 465 and 587 in the default exit policy, since
13256 people have started using them for spam too.
13257 - It turns out we couldn't bootstrap a network since we added
13258 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13259 has never gone down. Add an AssumeReachable config option to let
13260 servers and dirservers bootstrap. When we're trying to build a
13261 high-uptime or high-bandwidth circuit but there aren't enough
13262 suitable servers, try being less picky rather than simply failing.
13263 - Our logic to decide if the OR we connected to was the right guy
13264 was brittle and maybe open to a mitm for unverified routers.
13265 - We weren't cannibalizing circuits correctly for
13266 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13267 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13268 build those from scratch. This should make hidden services faster.
13269 - Predict required circuits better, with an eye toward making hidden
13270 services faster on the service end.
13271 - Retry streams if the exit node sends back a 'misc' failure. This
13272 should result in fewer random failures. Also, after failing
13273 from resolve failed or misc, reset the num failures, so we give
13274 it a fair shake next time we try.
13275 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13276 - Reduce severity on logs about dns worker spawning and culling.
13277 - When we're shutting down and we do something like try to post a
13278 server descriptor or rendezvous descriptor, don't complain that
13279 we seem to be unreachable. Of course we are, we're shutting down.
13280 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13281 We don't use them yet, but maybe one day our DNS resolver will be
13282 able to discover them.
13283 - Make ContactInfo mandatory for authoritative directory servers.
13284 - Require server descriptors to list IPv4 addresses -- hostnames
13285 are no longer allowed. This also fixes some potential security
13286 problems with people providing hostnames as their address and then
13287 preferentially resolving them to partition users.
13288 - Change log line for unreachability to explicitly suggest /etc/hosts
13289 as the culprit. Also make it clearer what IP address and ports we're
13290 testing for reachability.
13291 - Put quotes around user-supplied strings when logging so users are
13292 more likely to realize if they add bad characters (like quotes)
13294 - Let auth dir servers start without specifying an Address config
13296 - Make unit tests (and other invocations that aren't the real Tor)
13297 run without launching listeners, creating subdirectories, and so on.
13300 Changes in version 0.1.1.5-alpha - 2005-08-08
13301 o Bugfixes included in 0.1.0.14.
13303 o Bugfixes on 0.1.0.x:
13304 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13305 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13306 it would silently using ignore the 6668.
13309 Changes in version 0.1.0.14 - 2005-08-08
13310 o Bugfixes on 0.1.0.x:
13311 - Fix the other half of the bug with crypto handshakes
13313 - Fix an assert trigger if you send a 'signal term' via the
13314 controller when it's listening for 'event info' messages.
13317 Changes in version 0.1.1.4-alpha - 2005-08-04
13318 o Bugfixes included in 0.1.0.13.
13321 - Improve tor_gettimeofday() granularity on windows.
13322 - Make clients regenerate their keys when their IP address changes.
13323 - Implement some more GETINFO goodness: expose helper nodes, config
13324 options, getinfo keys.
13327 Changes in version 0.1.0.13 - 2005-08-04
13328 o Bugfixes on 0.1.0.x:
13329 - Fix a critical bug in the security of our crypto handshakes.
13330 - Fix a size_t underflow in smartlist_join_strings2() that made
13331 it do bad things when you hand it an empty smartlist.
13332 - Fix Windows installer to ship Tor license (thanks to Aphex for
13333 pointing out this oversight) and put a link to the doc directory
13335 - Explicitly set no-unaligned-access for sparc: it turns out the
13336 new gcc's let you compile broken code, but that doesn't make it
13340 Changes in version 0.1.1.3-alpha - 2005-07-23
13341 o Bugfixes on 0.1.1.2-alpha:
13342 - Fix a bug in handling the controller's "post descriptor"
13344 - Fix several bugs in handling the controller's "extend circuit"
13346 - Fix a bug in handling the controller's "stream status" event.
13347 - Fix an assert failure if we have a controller listening for
13348 circuit events and we go offline.
13349 - Re-allow hidden service descriptors to publish 0 intro points.
13350 - Fix a crash when generating your hidden service descriptor if
13351 you don't have enough intro points already.
13353 o New features on 0.1.1.2-alpha:
13354 - New controller function "getinfo accounting", to ask how
13355 many bytes we've used in this time period.
13356 - Experimental support for helper nodes: a lot of the risk from
13357 a small static adversary comes because users pick new random
13358 nodes every time they rebuild a circuit. Now users will try to
13359 stick to the same small set of entry nodes if they can. Not
13360 enabled by default yet.
13362 o Bugfixes on 0.1.0.12:
13363 - If you're an auth dir server, always publish your dirport,
13364 even if you haven't yet found yourself to be reachable.
13365 - Fix a size_t underflow in smartlist_join_strings2() that made
13366 it do bad things when you hand it an empty smartlist.
13369 Changes in version 0.1.0.12 - 2005-07-18
13370 o New directory servers:
13371 - tor26 has changed IP address.
13373 o Bugfixes on 0.1.0.x:
13374 - Fix a possible double-free in tor_gzip_uncompress().
13375 - When --disable-threads is set, do not search for or link against
13376 pthreads libraries.
13377 - Don't trigger an assert if an authoritative directory server
13378 claims its dirport is 0.
13379 - Fix bug with removing Tor as an NT service: some people were
13380 getting "The service did not return an error." Thanks to Matt
13384 Changes in version 0.1.1.2-alpha - 2005-07-15
13385 o New directory servers:
13386 - tor26 has changed IP address.
13388 o Bugfixes on 0.1.0.x, crashes/leaks:
13389 - Port the servers-not-obeying-their-exit-policies fix from
13391 - Fix an fd leak in start_daemon().
13392 - On Windows, you can't always reopen a port right after you've
13393 closed it. So change retry_listeners() to only close and re-open
13394 ports that have changed.
13395 - Fix a possible double-free in tor_gzip_uncompress().
13397 o Bugfixes on 0.1.0.x, usability:
13398 - When tor_socketpair() fails in Windows, give a reasonable
13399 Windows-style errno back.
13400 - Let people type "tor --install" as well as "tor -install" when
13402 want to make it an NT service.
13403 - NT service patch from Matt Edman to improve error messages.
13404 - When the controller asks for a config option with an abbreviated
13405 name, give the full name in our response.
13406 - Correct the man page entry on TrackHostExitsExpire.
13407 - Looks like we were never delivering deflated (i.e. compressed)
13408 running-routers lists, even when asked. Oops.
13409 - When --disable-threads is set, do not search for or link against
13410 pthreads libraries.
13412 o Bugfixes on 0.1.1.x:
13413 - Fix a seg fault with autodetecting which controller version is
13417 - New hidden service descriptor format: put a version in it, and
13418 let people specify introduction/rendezvous points that aren't
13419 in "the directory" (which is subjective anyway).
13420 - Allow the DEBUG controller event to work again. Mark certain log
13421 entries as "don't tell this to controllers", so we avoid cycles.
13424 Changes in version 0.1.0.11 - 2005-06-30
13425 o Bugfixes on 0.1.0.x:
13426 - Fix major security bug: servers were disregarding their
13427 exit policies if clients behaved unexpectedly.
13428 - Make OS X init script check for missing argument, so we don't
13429 confuse users who invoke it incorrectly.
13430 - Fix a seg fault in "tor --hash-password foo".
13431 - The MAPADDRESS control command was broken.
13434 Changes in version 0.1.1.1-alpha - 2005-06-29
13436 - Make OS X init script check for missing argument, so we don't
13437 confuse users who invoke it incorrectly.
13438 - Fix a seg fault in "tor --hash-password foo".
13439 - Fix a possible way to DoS dirservers.
13440 - When we complain that your exit policy implicitly allows local or
13441 private address spaces, name them explicitly so operators can
13443 - Make the log message less scary when all the dirservers are
13444 temporarily unreachable.
13445 - We were printing the number of idle dns workers incorrectly when
13449 - Revised controller protocol (version 1) that uses ascii rather
13450 than binary. Add supporting libraries in python and java so you
13451 can use the controller from your applications without caring how
13452 our protocol works.
13453 - Spiffy new support for crypto hardware accelerators. Can somebody
13457 Changes in version 0.0.9.10 - 2005-06-16
13458 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13459 - Refuse relay cells that claim to have a length larger than the
13460 maximum allowed. This prevents a potential attack that could read
13461 arbitrary memory (e.g. keys) from an exit server's process
13465 Changes in version 0.1.0.10 - 2005-06-14
13466 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13467 libevent before 1.1a.
13470 Changes in version 0.1.0.9-rc - 2005-06-09
13472 - Reset buf->highwater every time buf_shrink() is called, not just on
13473 a successful shrink. This was causing significant memory bloat.
13474 - Fix buffer overflow when checking hashed passwords.
13475 - Security fix: if seeding the RNG on Win32 fails, quit.
13476 - Allow seeding the RNG on Win32 even when you're not running as
13478 - Disable threading on Solaris too. Something is wonky with it,
13479 cpuworkers, and reentrant libs.
13480 - Reenable the part of the code that tries to flush as soon as an
13481 OR outbuf has a full TLS record available. Perhaps this will make
13482 OR outbufs not grow as huge except in rare cases, thus saving lots
13483 of CPU time plus memory.
13484 - Reject malformed .onion addresses rather then passing them on as
13485 normal web requests.
13486 - Adapt patch from Adam Langley: fix possible memory leak in
13487 tor_lookup_hostname().
13488 - Initialize libevent later in the startup process, so the logs are
13489 already established by the time we start logging libevent warns.
13490 - Use correct errno on win32 if libevent fails.
13491 - Check and warn about known-bad/slow libevent versions.
13492 - Pay more attention to the ClientOnly config option.
13493 - Have torctl.in/tor.sh.in check for location of su binary (needed
13495 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13496 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13497 HttpProxyAuthenticator
13498 - Stop warning about sigpipes in the logs. We're going to
13499 pretend that getting these occassionally is normal and fine.
13500 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13502 installer screens; and don't put stuff into StartupItems unless
13503 the user asks you to.
13504 - Require servers that use the default dirservers to have public IP
13505 addresses. We have too many servers that are configured with private
13506 IPs and their admins never notice the log entries complaining that
13507 their descriptors are being rejected.
13508 - Add OSX uninstall instructions. An actual uninstall script will
13512 Changes in version 0.1.0.8-rc - 2005-05-23
13514 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13515 panics. Disable kqueue on all OS X Tors.
13516 - Fix RPM: remove duplicate line accidentally added to the rpm
13518 - Disable threads on openbsd too, since its gethostaddr is not
13520 - Tolerate libevent 0.8 since it still works, even though it's
13522 - Enable building on Red Hat 9.0 again.
13523 - Allow the middle hop of the testing circuit to be running any
13524 version, now that most of them have the bugfix to let them connect
13525 to unknown servers. This will allow reachability testing to work
13526 even when 0.0.9.7-0.0.9.9 become obsolete.
13527 - Handle relay cells with rh.length too large. This prevents
13528 a potential attack that could read arbitrary memory (maybe even
13529 keys) from the exit server's process.
13530 - We screwed up the dirport reachability testing when we don't yet
13531 have a cached version of the directory. Hopefully now fixed.
13532 - Clean up router_load_single_router() (used by the controller),
13533 so it doesn't seg fault on error.
13534 - Fix a minor memory leak when somebody establishes an introduction
13535 point at your Tor server.
13536 - If a socks connection ends because read fails, don't warn that
13537 you're not sending a socks reply back.
13540 - Add HttpProxyAuthenticator config option too, that works like
13541 the HttpsProxyAuthenticator config option.
13542 - Encode hashed controller passwords in hex instead of base64,
13543 to make it easier to write controllers.
13546 Changes in version 0.1.0.7-rc - 2005-05-17
13548 - Fix a bug in the OS X package installer that prevented it from
13549 installing on Tiger.
13550 - Fix a script bug in the OS X package installer that made it
13551 complain during installation.
13552 - Find libevent even if it's hiding in /usr/local/ and your
13553 CFLAGS and LDFLAGS don't tell you to look there.
13554 - Be able to link with libevent as a shared library (the default
13555 after 1.0d), even if it's hiding in /usr/local/lib and even
13556 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13557 assuming you're running gcc. Otherwise fail and give a useful
13559 - Fix a bug in the RPM packager: set home directory for _tor to
13560 something more reasonable when first installing.
13561 - Free a minor amount of memory that is still reachable on exit.
13564 Changes in version 0.1.0.6-rc - 2005-05-14
13566 - Implement --disable-threads configure option. Disable threads on
13567 netbsd by default, because it appears to have no reentrant resolver
13569 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13570 release (1.1) detects and disables kqueue if it's broken.
13571 - Append default exit policy before checking for implicit internal
13572 addresses. Now we don't log a bunch of complaints on startup
13573 when using the default exit policy.
13574 - Some people were putting "Address " in their torrc, and they had
13575 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13576 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13577 LOCALSTATEDIR/tor instead.
13578 - Fix fragmented-message bug in TorControl.py.
13579 - Resolve a minor bug which would prevent unreachable dirports
13580 from getting suppressed in the published descriptor.
13581 - When the controller gave us a new descriptor, we weren't resolving
13582 it immediately, so Tor would think its address was 0.0.0.0 until
13583 we fetched a new directory.
13584 - Fix an uppercase/lowercase case error in suppressing a bogus
13585 libevent warning on some Linuxes.
13588 - Begin scrubbing sensitive strings from logs by default. Turn off
13589 the config option SafeLogging if you need to do debugging.
13590 - Switch to a new buffer management algorithm, which tries to avoid
13591 reallocing and copying quite as much. In first tests it looks like
13592 it uses *more* memory on average, but less cpu.
13593 - First cut at support for "create-fast" cells. Clients can use
13594 these when extending to their first hop, since the TLS already
13595 provides forward secrecy and authentication. Not enabled on
13597 - When dirservers refuse a router descriptor, we now log its
13598 contactinfo, platform, and the poster's IP address.
13599 - Call tor_free_all instead of connections_free_all after forking, to
13600 save memory on systems that need to fork.
13601 - Whine at you if you're a server and you don't set your contactinfo.
13602 - Implement --verify-config command-line option to check if your torrc
13603 is valid without actually launching Tor.
13604 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13605 rather than just rejecting it.
13608 Changes in version 0.1.0.5-rc - 2005-04-27
13610 - Stop trying to print a null pointer if an OR conn fails because
13611 we didn't like its cert.
13613 - Switch our internal buffers implementation to use a ring buffer,
13614 to hopefully improve performance for fast servers a lot.
13615 - Add HttpsProxyAuthenticator support (basic auth only), based
13616 on patch from Adam Langley.
13617 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13618 the fast servers that have been joining lately.
13619 - Give hidden service accesses extra time on the first attempt,
13620 since 60 seconds is often only barely enough. This might improve
13622 - Improve performance for dirservers: stop re-parsing the whole
13623 directory every time you regenerate it.
13624 - Add more debugging info to help us find the weird dns freebsd
13625 pthreads bug; cleaner debug messages to help track future issues.
13628 Changes in version 0.0.9.9 - 2005-04-23
13629 o Bugfixes on 0.0.9.x:
13630 - If unofficial Tor clients connect and send weird TLS certs, our
13631 Tor server triggers an assert. This release contains a minimal
13632 backport from the broader fix that we put into 0.1.0.4-rc.
13635 Changes in version 0.1.0.4-rc - 2005-04-23
13637 - If unofficial Tor clients connect and send weird TLS certs, our
13638 Tor server triggers an assert. Stop asserting, and start handling
13639 TLS errors better in other situations too.
13640 - When the controller asks us to tell it about all the debug-level
13641 logs, it turns out we were generating debug-level logs while
13642 telling it about them, which turns into a bad loop. Now keep
13643 track of whether you're sending a debug log to the controller,
13644 and don't log when you are.
13645 - Fix the "postdescriptor" feature of the controller interface: on
13646 non-complete success, only say "done" once.
13648 - Clients are now willing to load balance over up to 2mB, not 1mB,
13649 of advertised bandwidth capacity.
13650 - Add a NoPublish config option, so you can be a server (e.g. for
13651 testing running Tor servers in other Tor networks) without
13652 publishing your descriptor to the primary dirservers.
13655 Changes in version 0.1.0.3-rc - 2005-04-08
13656 o Improvements on 0.1.0.2-rc:
13657 - Client now retries when streams end early for 'hibernating' or
13658 'resource limit' reasons, rather than failing them.
13659 - More automated handling for dirserver operators:
13660 - Automatically approve nodes running 0.1.0.2-rc or later,
13661 now that the the reachability detection stuff is working.
13662 - Now we allow two unverified servers with the same nickname
13663 but different keys. But if a nickname is verified, only that
13664 nickname+key are allowed.
13665 - If you're an authdirserver connecting to an address:port,
13666 and it's not the OR you were expecting, forget about that
13667 descriptor. If he *was* the one you were expecting, then forget
13668 about all other descriptors for that address:port.
13669 - Allow servers to publish descriptors from 12 hours in the future.
13670 Corollary: only whine about clock skew from the dirserver if
13671 he's a trusted dirserver (since now even verified servers could
13672 have quite wrong clocks).
13673 - Adjust maximum skew and age for rendezvous descriptors: let skew
13674 be 48 hours rather than 90 minutes.
13675 - Efficiency improvements:
13676 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13677 it much faster to look up a circuit for each relay cell.
13678 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13679 since they're eating our cpu on exit nodes.
13680 - Stop wasting time doing a case insensitive comparison for every
13681 dns name every time we do any lookup. Canonicalize the names to
13682 lowercase and be done with it.
13683 - Start sending 'truncated' cells back rather than destroy cells,
13684 if the circuit closes in front of you. This means we won't have
13685 to abandon partially built circuits.
13686 - Only warn once per nickname from add_nickname_list_to_smartlist
13687 per failure, so an entrynode or exitnode choice that's down won't
13689 - Put a note in the torrc about abuse potential with the default
13691 - Revise control spec and implementation to allow all log messages to
13692 be sent to controller with their severities intact (suggested by
13693 Matt Edman). Update TorControl to handle new log event types.
13694 - Provide better explanation messages when controller's POSTDESCRIPTOR
13696 - Stop putting nodename in the Platform string in server descriptors.
13697 It doesn't actually help, and it is confusing/upsetting some people.
13699 o Bugfixes on 0.1.0.2-rc:
13700 - We were printing the host mask wrong in exit policies in server
13701 descriptors. This isn't a critical bug though, since we were still
13702 obeying the exit policy internally.
13703 - Fix Tor when compiled with libevent but without pthreads: move
13704 connection_unregister() from _connection_free() to
13706 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13707 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13708 when we look through the connection array, we'll find any of the
13709 cpu/dnsworkers. This is no good.
13711 o Bugfixes on 0.0.9.8:
13712 - Fix possible bug on threading platforms (e.g. win32) which was
13713 leaking a file descriptor whenever a cpuworker or dnsworker died.
13714 - When using preferred entry or exit nodes, ignore whether the
13715 circuit wants uptime or capacity. They asked for the nodes, they
13717 - chdir() to your datadirectory at the *end* of the daemonize process,
13718 not the beginning. This was a problem because the first time you
13719 run tor, if your datadir isn't there, and you have runasdaemon set
13720 to 1, it will try to chdir to it before it tries to create it. Oops.
13721 - Handle changed router status correctly when dirserver reloads
13722 fingerprint file. We used to be dropping all unverified descriptors
13723 right then. The bug was hidden because we would immediately
13724 fetch a directory from another dirserver, which would include the
13725 descriptors we just dropped.
13726 - When we're connecting to an OR and he's got a different nickname/key
13727 than we were expecting, only complain loudly if we're an OP or a
13728 dirserver. Complaining loudly to the OR admins just confuses them.
13729 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13730 artificially capped at 500kB.
13733 Changes in version 0.0.9.8 - 2005-04-07
13734 o Bugfixes on 0.0.9.x:
13735 - We have a bug that I haven't found yet. Sometimes, very rarely,
13736 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13737 thinks of itself as idle. This meant that no new circuits ever got
13738 established. Here's a workaround to kill any cpuworker that's been
13739 busy for more than 100 seconds.
13742 Changes in version 0.1.0.2-rc - 2005-04-01
13743 o Bugfixes on 0.1.0.1-rc:
13744 - Fixes on reachability detection:
13745 - Don't check for reachability while hibernating.
13746 - If ORPort is reachable but DirPort isn't, still publish the
13747 descriptor, but zero out DirPort until it's found reachable.
13748 - When building testing circs for ORPort testing, use only
13749 high-bandwidth nodes, so fewer circuits fail.
13750 - Complain about unreachable ORPort separately from unreachable
13751 DirPort, so the user knows what's going on.
13752 - Make sure we only conclude ORPort reachability if we didn't
13753 initiate the conn. Otherwise we could falsely conclude that
13754 we're reachable just because we connected to the guy earlier
13755 and he used that same pipe to extend to us.
13756 - Authdirservers shouldn't do ORPort reachability detection,
13757 since they're in clique mode, so it will be rare to find a
13758 server not already connected to them.
13759 - When building testing circuits, always pick middle hops running
13760 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13761 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13763 - When we decide we're reachable, actually publish our descriptor
13765 - Fix bug in redirectstream in the controller.
13766 - Fix the state descriptor strings so logs don't claim edge streams
13767 are in a different state than they actually are.
13768 - Use recent libevent features when possible (this only really affects
13769 win32 and osx right now, because the new libevent with these
13770 features hasn't been released yet). Add code to suppress spurious
13772 - Prevent possible segfault in connection_close_unattached_ap().
13773 - Fix newlines on torrc in win32.
13774 - Improve error msgs when tor-resolve fails.
13776 o Improvements on 0.0.9.x:
13777 - New experimental script tor/contrib/ExerciseServer.py (needs more
13778 work) that uses the controller interface to build circuits and
13779 fetch pages over them. This will help us bootstrap servers that
13780 have lots of capacity but haven't noticed it yet.
13781 - New experimental script tor/contrib/PathDemo.py (needs more work)
13782 that uses the controller interface to let you choose whole paths
13784 "<hostname>.<path,separated by dots>.<length of path>.path"
13785 - When we've connected to an OR and handshaked but didn't like
13786 the result, we were closing the conn without sending destroy
13787 cells back for pending circuits. Now send those destroys.
13790 Changes in version 0.0.9.7 - 2005-04-01
13791 o Bugfixes on 0.0.9.x:
13792 - Fix another race crash bug (thanks to Glenn Fink for reporting).
13793 - Compare identity to identity, not to nickname, when extending to
13794 a router not already in the directory. This was preventing us from
13795 extending to unknown routers. Oops.
13796 - Make sure to create OS X Tor user in <500 range, so we aren't
13797 creating actual system users.
13798 - Note where connection-that-hasn't-sent-end was marked, and fix
13799 a few really loud instances of this harmless bug (it's fixed more
13803 Changes in version 0.1.0.1-rc - 2005-03-28
13805 - Add reachability testing. Your Tor server will automatically try
13806 to see if its ORPort and DirPort are reachable from the outside,
13807 and it won't upload its descriptor until it decides they are.
13808 - Handle unavailable hidden services better. Handle slow or busy
13809 hidden services better.
13810 - Add support for CONNECTing through https proxies, with "HttpsProxy"
13812 - New exit policy: accept most low-numbered ports, rather than
13813 rejecting most low-numbered ports.
13814 - More Tor controller support (still experimental). See
13815 http://tor.eff.org/doc/control-spec.txt for all the new features,
13816 including signals to emulate unix signals from any platform;
13817 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
13818 closestream; closecircuit; etc.
13819 - Make nt services work and start on startup on win32 (based on
13820 patch by Matt Edman).
13821 - Add a new AddressMap config directive to rewrite incoming socks
13822 addresses. This lets you, for example, declare an implicit
13823 required exit node for certain sites.
13824 - Add a new TrackHostExits config directive to trigger addressmaps
13825 for certain incoming socks addresses -- for sites that break when
13826 your exit keeps changing (based on patch by Mike Perry).
13827 - Redo the client-side dns cache so it's just an addressmap too.
13828 - Notice when our IP changes, and reset stats/uptime/reachability.
13829 - When an application is using socks5, give him the whole variety of
13830 potential socks5 responses (connect refused, host unreachable, etc),
13831 rather than just "success" or "failure".
13832 - A more sane version numbering system. See
13833 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
13834 - New contributed script "exitlist": a simple python script to
13835 parse directories and find Tor nodes that exit to listed
13837 - New contributed script "privoxy-tor-toggle" to toggle whether
13838 Privoxy uses Tor. Seems to be configured for Debian by default.
13839 - Report HTTP reasons to client when getting a response from directory
13840 servers -- so you can actually know what went wrong.
13841 - New config option MaxAdvertisedBandwidth which lets you advertise
13842 a low bandwidthrate (to not attract as many circuits) while still
13843 allowing a higher bandwidthrate in reality.
13845 o Robustness/stability fixes:
13846 - Make Tor use Niels Provos's libevent instead of its current
13847 poll-but-sometimes-select mess. This will let us use faster async
13848 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
13850 - pthread support now too. This was forced because when we forked,
13851 we ended up wasting a lot of duplicate ram over time. Also switch
13852 to foo_r versions of some library calls to allow reentry and
13854 - Better handling for heterogeneous / unreliable nodes:
13855 - Annotate circuits w/ whether they aim to contain high uptime nodes
13856 and/or high capacity nodes. When building circuits, choose
13858 - This means that every single node in an intro rend circuit,
13859 not just the last one, will have a minimum uptime.
13860 - New config option LongLivedPorts to indicate application streams
13861 that will want high uptime circuits.
13862 - Servers reset uptime when a dir fetch entirely fails. This
13863 hopefully reflects stability of the server's network connectivity.
13864 - If somebody starts his tor server in Jan 2004 and then fixes his
13865 clock, don't make his published uptime be a year.
13866 - Reset published uptime when you wake up from hibernation.
13867 - Introduce a notion of 'internal' circs, which are chosen without
13868 regard to the exit policy of the last hop. Intro and rendezvous
13869 circs must be internal circs, to avoid leaking information. Resolve
13870 and connect streams can use internal circs if they want.
13871 - New circuit pooling algorithm: make sure to have enough circs around
13872 to satisfy any predicted ports, and also make sure to have 2 internal
13873 circs around if we've required internal circs lately (and with high
13874 uptime if we've seen that lately too).
13875 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
13876 which describes how often we retry making new circuits if current
13877 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
13878 how long we're willing to make use of an already-dirty circuit.
13879 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
13880 circ as necessary, if there are any completed ones lying around
13881 when we try to launch one.
13882 - Make hidden services try to establish a rendezvous for 30 seconds,
13883 rather than for n (where n=3) attempts to build a circuit.
13884 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
13885 "ShutdownWaitLength".
13886 - Try to be more zealous about calling connection_edge_end when
13887 things go bad with edge conns in connection.c.
13888 - Revise tor-spec to add more/better stream end reasons.
13889 - Revise all calls to connection_edge_end to avoid sending "misc",
13890 and to take errno into account where possible.
13893 - Fix a race condition that can trigger an assert, when we have a
13894 pending create cell and an OR connection fails right then.
13895 - Fix several double-mark-for-close bugs, e.g. where we were finding
13896 a conn for a cell even if that conn is already marked for close.
13897 - Make sequence of log messages when starting on win32 with no config
13898 file more reasonable.
13899 - When choosing an exit node for a new non-internal circ, don't take
13900 into account whether it'll be useful for any pending x.onion
13901 addresses -- it won't.
13902 - Turn addr_policy_compare from a tristate to a quadstate; this should
13903 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
13904 for google.com" problem.
13905 - Make "platform" string in descriptor more accurate for Win32 servers,
13906 so it's not just "unknown platform".
13907 - Fix an edge case in parsing config options (thanks weasel).
13908 If they say "--" on the commandline, it's not an option.
13909 - Reject odd-looking addresses at the client (e.g. addresses that
13910 contain a colon), rather than having the server drop them because
13912 - tor-resolve requests were ignoring .exit if there was a working circuit
13913 they could use instead.
13914 - REUSEADDR on normal platforms means you can rebind to the port
13915 right after somebody else has let it go. But REUSEADDR on win32
13916 means to let you bind to the port _even when somebody else
13917 already has it bound_! So, don't do that on Win32.
13918 - Change version parsing logic: a version is "obsolete" if it is not
13919 recommended and (1) there is a newer recommended version in the
13920 same series, or (2) there are no recommended versions in the same
13921 series, but there are some recommended versions in a newer series.
13922 A version is "new" if it is newer than any recommended version in
13924 - Stop most cases of hanging up on a socks connection without sending
13928 - Require BandwidthRate to be at least 20kB/s for servers.
13929 - When a dirserver causes you to give a warn, mention which dirserver
13931 - New config option DirAllowPrivateAddresses for authdirservers.
13932 Now by default they refuse router descriptors that have non-IP or
13933 private-IP addresses.
13934 - Stop publishing socksport in the directory, since it's not
13935 actually meant to be public. For compatibility, publish a 0 there
13937 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
13938 smart" value, that is low for servers and high for clients.
13939 - If our clock jumps forward by 100 seconds or more, assume something
13940 has gone wrong with our network and abandon all not-yet-used circs.
13941 - Warn when exit policy implicitly allows local addresses.
13942 - If we get an incredibly skewed timestamp from a dirserver mirror
13943 that isn't a verified OR, don't warn -- it's probably him that's
13945 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
13946 cookies to disk and doesn't log each web request to disk. (Thanks
13947 to Brett Carrington for pointing this out.)
13948 - When a client asks us for a dir mirror and we don't have one,
13949 launch an attempt to get a fresh one.
13950 - If we're hibernating and we get a SIGINT, exit immediately.
13951 - Add --with-dmalloc ./configure option, to track memory leaks.
13952 - And try to free all memory on closing, so we can detect what
13954 - Cache local dns resolves correctly even when they're .exit
13956 - Give a better warning when some other server advertises an
13957 ORPort that is actually an apache running ssl.
13958 - Add "opt hibernating 1" to server descriptor to make it clearer
13959 whether the server is hibernating.
13962 Changes in version 0.0.9.6 - 2005-03-24
13963 o Bugfixes on 0.0.9.x (crashes and asserts):
13964 - Add new end stream reasons to maintainance branch. Fix bug where
13965 reason (8) could trigger an assert. Prevent bug from recurring.
13966 - Apparently win32 stat wants paths to not end with a slash.
13967 - Fix assert triggers in assert_cpath_layer_ok(), where we were
13968 blowing away the circuit that conn->cpath_layer points to, then
13969 checking to see if the circ is well-formed. Backport check to make
13970 sure we dont use the cpath on a closed connection.
13971 - Prevent circuit_resume_edge_reading_helper() from trying to package
13972 inbufs for marked-for-close streams.
13973 - Don't crash on hup if your options->address has become unresolvable.
13974 - Some systems (like OS X) sometimes accept() a connection and tell
13975 you the remote host is 0.0.0.0:0. If this happens, due to some
13976 other mis-features, we get confused; so refuse the conn for now.
13978 o Bugfixes on 0.0.9.x (other):
13979 - Fix harmless but scary "Unrecognized content encoding" warn message.
13980 - Add new stream error reason: TORPROTOCOL reason means "you are not
13981 speaking a version of Tor I understand; say bye-bye to your stream."
13982 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
13983 into the future, now that we are more tolerant of skew. This
13984 resolves a bug where a Tor server would refuse to cache a directory
13985 because all the directories it gets are too far in the future;
13986 yet the Tor server never logs any complaints about clock skew.
13987 - Mac packaging magic: make man pages useable, and do not overwrite
13988 existing torrc files.
13989 - Make OS X log happily to /var/log/tor/tor.log
13992 Changes in version 0.0.9.5 - 2005-02-22
13993 o Bugfixes on 0.0.9.x:
13994 - Fix an assert race at exit nodes when resolve requests fail.
13995 - Stop picking unverified dir mirrors--it only leads to misery.
13996 - Patch from Matt Edman to make NT services work better. Service
13997 support is still not compiled into the executable by default.
13998 - Patch from Dmitri Bely so the Tor service runs better under
13999 the win32 SYSTEM account.
14000 - Make tor-resolve actually work (?) on Win32.
14001 - Fix a sign bug when getrlimit claims to have 4+ billion
14002 file descriptors available.
14003 - Stop refusing to start when bandwidthburst == bandwidthrate.
14004 - When create cells have been on the onion queue more than five
14005 seconds, just send back a destroy and take them off the list.
14008 Changes in version 0.0.9.4 - 2005-02-03
14009 o Bugfixes on 0.0.9:
14010 - Fix an assert bug that took down most of our servers: when
14011 a server claims to have 1 GB of bandwidthburst, don't
14013 - Don't crash as badly if we have spawned the max allowed number
14014 of dnsworkers, or we're out of file descriptors.
14015 - Block more file-sharing ports in the default exit policy.
14016 - MaxConn is now automatically set to the hard limit of max
14017 file descriptors we're allowed (ulimit -n), minus a few for
14019 - Give a clearer message when servers need to raise their
14020 ulimit -n when they start running out of file descriptors.
14021 - SGI Compatibility patches from Jan Schaumann.
14022 - Tolerate a corrupt cached directory better.
14023 - When a dirserver hasn't approved your server, list which one.
14024 - Go into soft hibernation after 95% of the bandwidth is used,
14025 not 99%. This is especially important for daily hibernators who
14026 have a small accounting max. Hopefully it will result in fewer
14027 cut connections when the hard hibernation starts.
14028 - Load-balance better when using servers that claim more than
14029 800kB/s of capacity.
14030 - Make NT services work (experimental, only used if compiled in).
14033 Changes in version 0.0.9.3 - 2005-01-21
14034 o Bugfixes on 0.0.9:
14035 - Backport the cpu use fixes from main branch, so busy servers won't
14036 need as much processor time.
14037 - Work better when we go offline and then come back, or when we
14038 run Tor at boot before the network is up. We do this by
14039 optimistically trying to fetch a new directory whenever an
14040 application request comes in and we think we're offline -- the
14041 human is hopefully a good measure of when the network is back.
14042 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14043 long as you keep using them; actually publish hidserv descriptors
14044 shortly after they change, rather than waiting 20-40 minutes.
14045 - Enable Mac startup script by default.
14046 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14047 - When you update AllowUnverifiedNodes or FirewallPorts via the
14048 controller's setconf feature, we were always appending, never
14050 - When you update HiddenServiceDir via setconf, it was screwing up
14051 the order of reading the lines, making it fail.
14052 - Do not rewrite a cached directory back to the cache; otherwise we
14053 will think it is recent and not fetch a newer one on startup.
14054 - Workaround for webservers that lie about Content-Encoding: Tor
14055 now tries to autodetect compressed directories and compression
14056 itself. This lets us Proxypass dir fetches through apache.
14059 Changes in version 0.0.9.2 - 2005-01-04
14060 o Bugfixes on 0.0.9 (crashes and asserts):
14061 - Fix an assert on startup when the disk is full and you're logging
14063 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14064 style address, then we'd crash.
14065 - Fix an assert trigger when the running-routers string we get from
14066 a dirserver is broken.
14067 - Make worker threads start and run on win32. Now win32 servers
14069 - Bandaid (not actually fix, but now it doesn't crash) an assert
14070 where the dns worker dies mysteriously and the main Tor process
14071 doesn't remember anything about the address it was resolving.
14073 o Bugfixes on 0.0.9 (Win32):
14074 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14075 name out of the warning/assert messages.
14076 - Fix a superficial "unhandled error on read" bug on win32.
14077 - The win32 installer no longer requires a click-through for our
14078 license, since our Free Software license grants rights but does not
14080 - Win32: When connecting to a dirserver fails, try another one
14081 immediately. (This was already working for non-win32 Tors.)
14082 - Stop trying to parse $HOME on win32 when hunting for default
14084 - Make tor-resolve.c work on win32 by calling network_init().
14086 o Bugfixes on 0.0.9 (other):
14087 - Make 0.0.9.x build on Solaris again.
14088 - Due to a fencepost error, we were blowing away the \n when reporting
14089 confvalue items in the controller. So asking for multiple config
14090 values at once couldn't work.
14091 - When listing circuits that are pending on an opening OR connection,
14092 if we're an OR we were listing circuits that *end* at us as
14093 being pending on every listener, dns/cpu worker, etc. Stop that.
14094 - Dirservers were failing to create 'running-routers' or 'directory'
14095 strings if we had more than some threshold of routers. Fix them so
14096 they can handle any number of routers.
14097 - Fix a superficial "Duplicate mark for close" bug.
14098 - Stop checking for clock skew for OR connections, even for servers.
14099 - Fix a fencepost error that was chopping off the last letter of any
14100 nickname that is the maximum allowed nickname length.
14101 - Update URLs in log messages so they point to the new website.
14102 - Fix a potential problem in mangling server private keys while
14103 writing to disk (not triggered yet, as far as we know).
14104 - Include the licenses for other free software we include in Tor,
14105 now that we're shipping binary distributions more regularly.
14108 Changes in version 0.0.9.1 - 2004-12-15
14109 o Bugfixes on 0.0.9:
14110 - Make hibernation actually work.
14111 - Make HashedControlPassword config option work.
14112 - When we're reporting event circuit status to a controller,
14113 don't use the stream status code.
14116 Changes in version 0.0.9 - 2004-12-12
14118 - Clean up manpage and torrc.sample file.
14119 - Clean up severities and text of log warnings.
14121 - Make servers trigger an assert when they enter hibernation.
14124 Changes in version 0.0.9rc7 - 2004-12-08
14125 o Bugfixes on 0.0.9rc:
14126 - Fix a stack-trashing crash when an exit node begins hibernating.
14127 - Avoid looking at unallocated memory while considering which
14128 ports we need to build circuits to cover.
14129 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14130 we shouldn't hold-open-until-flush if the eof arrived first.
14131 - Fix a bug with init_cookie_authentication() in the controller.
14132 - When recommending new-format log lines, if the upper bound is
14133 LOG_ERR, leave it implicit.
14135 o Bugfixes on 0.0.8.1:
14136 - Fix a whole slew of memory leaks.
14137 - Fix isspace() and friends so they still make Solaris happy
14138 but also so they don't trigger asserts on win32.
14139 - Fix parse_iso_time on platforms without strptime (eg win32).
14140 - win32: tolerate extra "readable" events better.
14141 - win32: when being multithreaded, leave parent fdarray open.
14142 - Make unit tests work on win32.
14145 Changes in version 0.0.9rc6 - 2004-12-06
14146 o Bugfixes on 0.0.9pre:
14147 - Clean up some more integer underflow opportunities (not exploitable
14149 - While hibernating, hup should not regrow our listeners.
14150 - Send an end to the streams we close when we hibernate, rather
14151 than just chopping them off.
14152 - React to eof immediately on non-open edge connections.
14154 o Bugfixes on 0.0.8.1:
14155 - Calculate timeout for waiting for a connected cell from the time
14156 we sent the begin cell, not from the time the stream started. If
14157 it took a long time to establish the circuit, we would time out
14158 right after sending the begin cell.
14159 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14160 of * as always matching, so we were picking reject *:* nodes as
14161 exit nodes too. Oops.
14164 - New circuit building strategy: keep a list of ports that we've
14165 used in the past 6 hours, and always try to have 2 circuits open
14166 or on the way that will handle each such port. Seed us with port
14167 80 so web users won't complain that Tor is "slow to start up".
14168 - Make kill -USR1 dump more useful stats about circuits.
14169 - When warning about retrying or giving up, print the address, so
14170 the user knows which one it's talking about.
14171 - If you haven't used a clean circuit in an hour, throw it away,
14172 just to be on the safe side. (This means after 6 hours a totally
14173 unused Tor client will have no circuits open.)
14176 Changes in version 0.0.9rc5 - 2004-12-01
14177 o Bugfixes on 0.0.8.1:
14178 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14179 - Let resolve conns retry/expire also, rather than sticking around
14181 - If we are using select, make sure we stay within FD_SETSIZE.
14183 o Bugfixes on 0.0.9pre:
14184 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14185 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14187 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14188 instead. Impose minima and maxima for all *Period options; impose
14189 even tighter maxima for fetching if we are a caching dirserver.
14190 Clip rather than rejecting.
14191 - Fetch cached running-routers from servers that serve it (that is,
14192 authdirservers and servers running 0.0.9rc5-cvs or later.)
14195 - Accept *:706 (silc) in default exit policy.
14196 - Implement new versioning format for post 0.1.
14197 - Support "foo.nickname.exit" addresses, to let Alice request the
14198 address "foo" as viewed by exit node "nickname". Based on a patch
14200 - Make tor --version --version dump the cvs Id of every file.
14203 Changes in version 0.0.9rc4 - 2004-11-28
14204 o Bugfixes on 0.0.8.1:
14205 - Make windows sockets actually non-blocking (oops), and handle
14206 win32 socket errors better.
14208 o Bugfixes on 0.0.9rc1:
14209 - Actually catch the -USR2 signal.
14212 Changes in version 0.0.9rc3 - 2004-11-25
14213 o Bugfixes on 0.0.8.1:
14214 - Flush the log file descriptor after we print "Tor opening log file",
14215 so we don't see those messages days later.
14217 o Bugfixes on 0.0.9rc1:
14218 - Make tor-resolve work again.
14219 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14220 - Fix an assert trigger for clients/servers handling resolves.
14223 Changes in version 0.0.9rc2 - 2004-11-24
14224 o Bugfixes on 0.0.9rc1:
14225 - I broke socks5 support while fixing the eof bug.
14226 - Allow unitless bandwidths and intervals; they default to bytes
14228 - New servers don't start out hibernating; they are active until
14229 they run out of bytes, so they have a better estimate of how
14230 long it takes, and so their operators can know they're working.
14233 Changes in version 0.0.9rc1 - 2004-11-23
14234 o Bugfixes on 0.0.8.1:
14235 - Finally fix a bug that's been plaguing us for a year:
14236 With high load, circuit package window was reaching 0. Whenever
14237 we got a circuit-level sendme, we were reading a lot on each
14238 socket, but only writing out a bit. So we would eventually reach
14239 eof. This would be noticed and acted on even when there were still
14240 bytes sitting in the inbuf.
14241 - When poll() is interrupted, we shouldn't believe the revents values.
14243 o Bugfixes on 0.0.9pre6:
14244 - Fix hibernate bug that caused pre6 to be broken.
14245 - Don't keep rephist info for routers that haven't had activity for
14246 24 hours. (This matters now that clients have keys, since we track
14248 - Never call close_temp_logs while validating log options.
14249 - Fix backslash-escaping on tor.sh.in and torctl.in.
14252 - Implement weekly/monthly/daily accounting: now you specify your
14253 hibernation properties by
14254 AccountingMax N bytes|KB|MB|GB|TB
14255 AccountingStart day|week|month [day] HH:MM
14256 Defaults to "month 1 0:00".
14257 - Let bandwidth and interval config options be specified as 5 bytes,
14258 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14259 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14260 get back to normal.)
14261 - If your requested entry or exit node has advertised bandwidth 0,
14263 - Be more greedy about filling up relay cells -- we try reading again
14264 once we've processed the stuff we read, in case enough has arrived
14265 to fill the last cell completely.
14266 - Apply NT service patch from Osamu Fujino. Still needs more work.
14269 Changes in version 0.0.9pre6 - 2004-11-15
14270 o Bugfixes on 0.0.8.1:
14271 - Fix assert failure on malformed socks4a requests.
14272 - Use identity comparison, not nickname comparison, to choose which
14273 half of circuit-ID-space each side gets to use. This is needed
14274 because sometimes we think of a router as a nickname, and sometimes
14275 as a hex ID, and we can't predict what the other side will do.
14276 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14277 write() call will fail and we handle it there.
14278 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14279 and smartlist_len, which are two major profiling offenders.
14281 o Bugfixes on 0.0.9pre5:
14282 - Fix a bug in read_all that was corrupting config files on windows.
14283 - When we're raising the max number of open file descriptors to
14284 'unlimited', don't log that we just raised it to '-1'.
14285 - Include event code with events, as required by control-spec.txt.
14286 - Don't give a fingerprint when clients do --list-fingerprint:
14287 it's misleading, because it will never be the same again.
14288 - Stop using strlcpy in tor_strndup, since it was slowing us
14290 - Remove warn on startup about missing cached-directory file.
14291 - Make kill -USR1 work again.
14292 - Hibernate if we start tor during the "wait for wakeup-time" phase
14293 of an accounting interval. Log our hibernation plans better.
14294 - Authoritative dirservers now also cache their directory, so they
14295 have it on start-up.
14298 - Fetch running-routers; cache running-routers; compress
14299 running-routers; serve compressed running-routers.z
14300 - Add NSI installer script contributed by J Doe.
14301 - Commit VC6 and VC7 workspace/project files.
14302 - Commit a tor.spec for making RPM files, with help from jbash.
14303 - Add contrib/torctl.in contributed by Glenn Fink.
14304 - Implement the control-spec's SAVECONF command, to write your
14305 configuration to torrc.
14306 - Get cookie authentication for the controller closer to working.
14307 - Include control-spec.txt in the tarball.
14308 - When set_conf changes our server descriptor, upload a new copy.
14309 But don't upload it too often if there are frequent changes.
14310 - Document authentication config in man page, and document signals
14312 - Clean up confusing parts of man page and torrc.sample.
14313 - Make expand_filename handle ~ and ~username.
14314 - Use autoconf to enable largefile support where necessary. Use
14315 ftello where available, since ftell can fail at 2GB.
14316 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14317 log more informatively.
14318 - Give a slightly more useful output for "tor -h".
14319 - Refuse application socks connections to port 0.
14320 - Check clock skew for verified servers, but allow unverified
14321 servers and clients to have any clock skew.
14322 - Break DirFetchPostPeriod into:
14323 - DirFetchPeriod for fetching full directory,
14324 - StatusFetchPeriod for fetching running-routers,
14325 - DirPostPeriod for posting server descriptor,
14326 - RendPostPeriod for posting hidden service descriptors.
14327 - Make sure the hidden service descriptors are at a random offset
14328 from each other, to hinder linkability.
14331 Changes in version 0.0.9pre5 - 2004-11-09
14332 o Bugfixes on 0.0.9pre4:
14333 - Fix a seg fault in unit tests (doesn't affect main program).
14334 - Fix an assert bug where a hidden service provider would fail if
14335 the first hop of his rendezvous circuit was down.
14336 - Hidden service operators now correctly handle version 1 style
14337 INTRODUCE1 cells (nobody generates them still, so not a critical
14339 - If do_hup fails, actually notice.
14340 - Handle more errnos from accept() without closing the listener.
14341 Some OpenBSD machines were closing their listeners because
14342 they ran out of file descriptors.
14343 - Send resolve cells to exit routers that are running a new
14344 enough version of the resolve code to work right.
14345 - Better handling of winsock includes on non-MSV win32 compilers.
14346 - Some people had wrapped their tor client/server in a script
14347 that would restart it whenever it died. This did not play well
14348 with our "shut down if your version is obsolete" code. Now people
14349 don't fetch a new directory if their local cached version is
14351 - Make our autogen.sh work on ksh as well as bash.
14354 - Hibernation: New config option "AccountingMaxKB" lets you
14355 set how many KBytes per month you want to allow your server to
14356 consume. Rather than spreading those bytes out evenly over the
14357 month, we instead hibernate for some of the month and pop up
14358 at a deterministic time, work until the bytes are consumed, then
14359 hibernate again. Config option "MonthlyAccountingStart" lets you
14360 specify which day of the month your billing cycle starts on.
14361 - Control interface: a separate program can now talk to your
14362 client/server over a socket, and get/set config options, receive
14363 notifications of circuits and streams starting/finishing/dying,
14364 bandwidth used, etc. The next step is to get some GUIs working.
14365 Let us know if you want to help out. See doc/control-spec.txt .
14366 - Ship a contrib/tor-control.py as an example script to interact
14367 with the control port.
14368 - "tor --hash-password zzyxz" will output a salted password for
14369 use in authenticating to the control interface.
14370 - New log format in config:
14371 "Log minsev[-maxsev] stdout|stderr|syslog" or
14372 "Log minsev[-maxsev] file /var/foo"
14375 - DirPolicy config option, to let people reject incoming addresses
14376 from their dirserver.
14377 - "tor --list-fingerprint" will list your identity key fingerprint
14379 - Add "pass" target for RedirectExit, to make it easier to break
14380 out of a sequence of RedirectExit rules.
14381 - Clients now generate a TLS cert too, in preparation for having
14382 them act more like real nodes.
14383 - Ship src/win32/ in the tarball, so people can use it to build.
14384 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14386 - New "router-status" line in directory, to better bind each verified
14387 nickname to its identity key.
14388 - Deprecate unofficial config option abbreviations, and abbreviations
14389 not on the command line.
14390 - Add a pure-C tor-resolve implementation.
14391 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14392 1024) file descriptors.
14394 o Code security improvements, inspired by Ilja:
14395 - Replace sprintf with snprintf. (I think they were all safe, but
14397 - Replace strcpy/strncpy with strlcpy in more places.
14398 - Avoid strcat; use snprintf or strlcat instead.
14399 - snprintf wrapper with consistent (though not C99) overflow behavior.
14402 Changes in version 0.0.9pre4 - 2004-10-17
14403 o Bugfixes on 0.0.9pre3:
14404 - If the server doesn't specify an exit policy, use the real default
14405 exit policy, not reject *:*.
14406 - Ignore fascistfirewall when uploading/downloading hidden service
14407 descriptors, since we go through Tor for those; and when using
14408 an HttpProxy, since we assume it can reach them all.
14409 - When looking for an authoritative dirserver, use only the ones
14410 configured at boot. Don't bother looking in the directory.
14411 - The rest of the fix for get_default_conf_file() on older win32.
14412 - Make 'Routerfile' config option obsolete.
14415 - New 'MyFamily nick1,...' config option for a server to
14416 specify other servers that shouldn't be used in the same circuit
14417 with it. Only believed if nick1 also specifies us.
14418 - New 'NodeFamily nick1,nick2,...' config option for a client to
14419 specify nodes that it doesn't want to use in the same circuit.
14420 - New 'Redirectexit pattern address:port' config option for a
14421 server to redirect exit connections, e.g. to a local squid.
14424 Changes in version 0.0.9pre3 - 2004-10-13
14425 o Bugfixes on 0.0.8.1:
14426 - Better torrc example lines for dirbindaddress and orbindaddress.
14427 - Improved bounds checking on parsed ints (e.g. config options and
14428 the ones we find in directories.)
14429 - Better handling of size_t vs int, so we're more robust on 64
14431 - Fix the rest of the bug where a newly started OR would appear
14432 as unverified even after we've added his fingerprint and hupped
14434 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14435 close it without sending back an end. So 'connection refused'
14436 would simply be ignored and the user would get no response.
14438 o Bugfixes on 0.0.9pre2:
14439 - Serving the cached-on-disk directory to people is bad. We now
14440 provide no directory until we've fetched a fresh one.
14441 - Workaround for bug on windows where cached-directories get crlf
14443 - Make get_default_conf_file() work on older windows too.
14444 - If we write a *:* exit policy line in the descriptor, don't write
14445 any more exit policy lines.
14448 - Use only 0.0.9pre1 and later servers for resolve cells.
14449 - Make the dirservers file obsolete.
14450 - Include a dir-signing-key token in directories to tell the
14451 parsing entity which key is being used to sign.
14452 - Remove the built-in bulky default dirservers string.
14453 - New config option "Dirserver %s:%d [fingerprint]", which can be
14454 repeated as many times as needed. If no dirservers specified,
14455 default to moria1,moria2,tor26.
14456 - Make moria2 advertise a dirport of 80, so people behind firewalls
14457 will be able to get a directory.
14458 - Http proxy support
14459 - Dirservers translate requests for http://%s:%d/x to /x
14460 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14461 be routed through this host.
14462 - Clients ask for /tor/x rather than /x for new enough dirservers.
14463 This way we can one day coexist peacefully with apache.
14464 - Clients specify a "Host: %s%d" http header, to be compatible
14465 with more proxies, and so running squid on an exit node can work.
14468 Changes in version 0.0.8.1 - 2004-10-13
14470 - Fix a seg fault that can be triggered remotely for Tor
14471 clients/servers with an open dirport.
14472 - Fix a rare assert trigger, where routerinfos for entries in
14473 our cpath would expire while we're building the path.
14474 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14475 - Fix a rare seg fault for people running hidden services on
14476 intermittent connections.
14477 - Fix a bug in parsing opt keywords with objects.
14478 - Fix a stale pointer assert bug when a stream detaches and
14480 - Fix a string format vulnerability (probably not exploitable)
14481 in reporting stats locally.
14482 - Fix an assert trigger: sometimes launching circuits can fail
14483 immediately, e.g. because too many circuits have failed recently.
14484 - Fix a compile warning on 64 bit platforms.
14487 Changes in version 0.0.9pre2 - 2004-10-03
14489 - Make fetching a cached directory work for 64-bit platforms too.
14490 - Make zlib.h a required header, not an optional header.
14493 Changes in version 0.0.9pre1 - 2004-10-01
14495 - Stop using separate defaults for no-config-file and
14496 empty-config-file. Now you have to explicitly turn off SocksPort,
14497 if you don't want it open.
14498 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14499 - Improve man page to mention more of the 0.0.8 features.
14500 - Fix a rare seg fault for people running hidden services on
14501 intermittent connections.
14502 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14504 - Fix more dns related bugs: send back resolve_failed and end cells
14505 more reliably when the resolve fails, rather than closing the
14506 circuit and then trying to send the cell. Also attach dummy resolve
14507 connections to a circuit *before* calling dns_resolve(), to fix
14508 a bug where cached answers would never be sent in RESOLVED cells.
14509 - When we run out of disk space, or other log writing error, don't
14510 crash. Just stop logging to that log and continue.
14511 - We were starting to daemonize before we opened our logs, so if
14512 there were any problems opening logs, we would complain to stderr,
14513 which wouldn't work, and then mysteriously exit.
14514 - Fix a rare bug where sometimes a verified OR would connect to us
14515 before he'd uploaded his descriptor, which would cause us to
14516 assign conn->nickname as though he's unverified. Now we look through
14517 the fingerprint list to see if he's there.
14518 - Fix a rare assert trigger, where routerinfos for entries in
14519 our cpath would expire while we're building the path.
14522 - Clients can ask dirservers for /dir.z to get a compressed version
14523 of the directory. Only works for servers running 0.0.9, of course.
14524 - Make clients cache directories and use them to seed their router
14525 lists at startup. This means clients have a datadir again.
14526 - Configuration infrastructure support for warning on obsolete
14528 - Respond to content-encoding headers by trying to uncompress as
14530 - Reply with a deflated directory when a client asks for "dir.z".
14531 We could use allow-encodings instead, but allow-encodings isn't
14532 specified in HTTP 1.0.
14533 - Raise the max dns workers from 50 to 100.
14534 - Discourage people from setting their dirfetchpostperiod more often
14535 than once per minute.
14536 - Protect dirservers from overzealous descriptor uploading -- wait
14537 10 seconds after directory gets dirty, before regenerating.
14540 Changes in version 0.0.8 - 2004-08-25
14541 o Port it to SunOS 5.9 / Athena
14544 Changes in version 0.0.8rc2 - 2004-08-20
14545 o Make it compile on cygwin again.
14546 o When picking unverified routers, skip those with low uptime and/or
14547 low bandwidth, depending on what properties you care about.
14550 Changes in version 0.0.8rc1 - 2004-08-18
14551 o Changes from 0.0.7.3:
14553 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14554 don't put it into the client dns cache.
14555 - If a begin failed due to exit policy, but we believe the IP address
14556 should have been allowed, switch that router to exitpolicy reject *:*
14557 until we get our next directory.
14559 - Clients choose nodes proportional to advertised bandwidth.
14560 - Avoid using nodes with low uptime as introduction points.
14561 - Handle servers with dynamic IP addresses: don't replace
14562 options->Address with the resolved one at startup, and
14563 detect our address right before we make a routerinfo each time.
14564 - 'FascistFirewall' option to pick dirservers and ORs on specific
14565 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14566 which ports are open. (Defaults to 80,443)
14567 - Be more aggressive about trying to make circuits when the network
14568 has changed (e.g. when you unsuspend your laptop).
14569 - Check for time skew on http headers; report date in response to
14571 - If the entrynode config line has only one node, don't pick it as
14573 - Add strict{entry|exit}nodes config options. If set to 1, then
14574 we refuse to build circuits that don't include the specified entry
14576 - OutboundBindAddress config option, to bind to a specific
14577 IP address for outgoing connect()s.
14578 - End truncated log entries (e.g. directories) with "[truncated]".
14580 o Patches to 0.0.8preX:
14582 - Patches to compile and run on win32 again (maybe)?
14583 - Fix crash when looking for ~/.torrc with no $HOME set.
14584 - Fix a race bug in the unit tests.
14585 - Handle verified/unverified name collisions better when new
14586 routerinfo's arrive in a directory.
14587 - Sometimes routers were getting entered into the stats before
14588 we'd assigned their identity_digest. Oops.
14589 - Only pick and establish intro points after we've gotten a
14592 - AllowUnverifiedNodes config option to let circuits choose no-name
14593 routers in entry,middle,exit,introduction,rendezvous positions.
14594 Allow middle and rendezvous positions by default.
14595 - Add a man page for tor-resolve.
14598 Changes in version 0.0.7.3 - 2004-08-12
14599 o Stop dnsworkers from triggering an assert failure when you
14600 ask them to resolve the host "".
14603 Changes in version 0.0.8pre3 - 2004-08-09
14604 o Changes from 0.0.7.2:
14605 - Allow multiple ORs with same nickname in routerlist -- now when
14606 people give us one identity key for a nickname, then later
14607 another, we don't constantly complain until the first expires.
14608 - Remember used bandwidth (both in and out), and publish 15-minute
14609 snapshots for the past day into our descriptor.
14610 - You can now fetch $DIRURL/running-routers to get just the
14611 running-routers line, not the whole descriptor list. (But
14612 clients don't use this yet.)
14613 - When people mistakenly use Tor as an http proxy, point them
14614 at the tor-doc.html rather than the INSTALL.
14615 - Remove our mostly unused -- and broken -- hex_encode()
14616 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14617 for pointing out this bug.)
14618 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14619 fewer problems with people using the wrong key.
14620 - Change the default exit policy to reject the default edonkey,
14621 kazaa, gnutella ports.
14622 - Add replace_file() to util.[ch] to handle win32's rename().
14624 o Changes from 0.0.8preX:
14625 - Fix two bugs in saving onion keys to disk when rotating, so
14626 hopefully we'll get fewer people using old onion keys.
14627 - Fix an assert error that was making SocksPolicy not work.
14628 - Be willing to expire routers that have an open dirport -- it's
14629 just the authoritative dirservers we want to not forget.
14630 - Reject tor-resolve requests for .onion addresses early, so we
14631 don't build a whole rendezvous circuit and then fail.
14632 - When you're warning a server that he's unverified, don't cry
14633 wolf unpredictably.
14634 - Fix a race condition: don't try to extend onto a connection
14635 that's still handshaking.
14636 - For servers in clique mode, require the conn to be open before
14637 you'll choose it for your path.
14638 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14639 end relay cell, etc.
14640 - Measure bandwidth capacity over the last 24 hours, not just 12
14641 - Bugfix: authoritative dirservers were making and signing a new
14642 directory for each client, rather than reusing the cached one.
14645 Changes in version 0.0.8pre2 - 2004-08-04
14646 o Changes from 0.0.7.2:
14648 - Check directory signature _before_ you decide whether you're
14649 you're running an obsolete version and should exit.
14650 - Check directory signature _before_ you parse the running-routers
14651 list to decide who's running or verified.
14652 - Bugfixes and features:
14653 - Check return value of fclose while writing to disk, so we don't
14654 end up with broken files when servers run out of disk space.
14655 - Log a warning if the user uses an unsafe socks variant, so people
14656 are more likely to learn about privoxy or socat.
14657 - Dirservers now include RFC1123-style dates in the HTTP headers,
14658 which one day we will use to better detect clock skew.
14660 o Changes from 0.0.8pre1:
14661 - Make it compile without warnings again on win32.
14662 - Log a warning if you're running an unverified server, to let you
14663 know you might want to get it verified.
14664 - Only pick a default nickname if you plan to be a server.
14667 Changes in version 0.0.8pre1 - 2004-07-23
14669 - Made our unit tests compile again on OpenBSD 3.5, and tor
14670 itself compile again on OpenBSD on a sparc64.
14671 - We were neglecting milliseconds when logging on win32, so
14672 everything appeared to happen at the beginning of each second.
14674 o Protocol changes:
14675 - 'Extend' relay cell payloads now include the digest of the
14676 intended next hop's identity key. Now we can verify that we're
14677 extending to the right router, and also extend to routers we
14678 hadn't heard of before.
14681 - Tor nodes can now act as relays (with an advertised ORPort)
14682 without being manually verified by the dirserver operators.
14683 - Uploaded descriptors of unverified routers are now accepted
14684 by the dirservers, and included in the directory.
14685 - Verified routers are listed by nickname in the running-routers
14686 list; unverified routers are listed as "$<fingerprint>".
14687 - We now use hash-of-identity-key in most places rather than
14688 nickname or addr:port, for improved security/flexibility.
14689 - To avoid Sybil attacks, paths still use only verified servers.
14690 But now we have a chance to play around with hybrid approaches.
14691 - Nodes track bandwidth usage to estimate capacity (not used yet).
14692 - ClientOnly option for nodes that never want to become servers.
14693 - Directory caching.
14694 - "AuthoritativeDir 1" option for the official dirservers.
14695 - Now other nodes (clients and servers) will cache the latest
14696 directory they've pulled down.
14697 - They can enable their DirPort to serve it to others.
14698 - Clients will pull down a directory from any node with an open
14699 DirPort, and check the signature/timestamp correctly.
14700 - Authoritative dirservers now fetch directories from other
14701 authdirservers, to stay better synced.
14702 - Running-routers list tells who's down also, along with noting
14703 if they're verified (listed by nickname) or unverified (listed
14705 - Allow dirservers to serve running-router list separately.
14706 This isn't used yet.
14707 - ORs connect-on-demand to other ORs
14708 - If you get an extend cell to an OR you're not connected to,
14709 connect, handshake, and forward the create cell.
14710 - The authoritative dirservers stay connected to everybody,
14711 and everybody stays connected to 0.0.7 servers, but otherwise
14712 clients/servers expire unused connections after 5 minutes.
14713 - When servers get a sigint, they delay 30 seconds (refusing new
14714 connections) then exit. A second sigint causes immediate exit.
14715 - File and name management:
14716 - Look for .torrc if no CONFDIR "torrc" is found.
14717 - If no datadir is defined, then choose, make, and secure ~/.tor
14719 - If torrc not found, exitpolicy reject *:*.
14720 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14721 - If no nickname is defined, derive default from hostname.
14722 - Rename secret key files, e.g. identity.key -> secret_id_key,
14723 to discourage people from mailing their identity key to tor-ops.
14724 - Refuse to build a circuit before the directory has arrived --
14725 it won't work anyway, since you won't know the right onion keys
14727 - Try other dirservers immediately if the one you try is down. This
14728 should tolerate down dirservers better now.
14729 - Parse tor version numbers so we can do an is-newer-than check
14730 rather than an is-in-the-list check.
14731 - New socks command 'resolve', to let us shim gethostbyname()
14733 - A 'tor_resolve' script to access the socks resolve functionality.
14734 - A new socks-extensions.txt doc file to describe our
14735 interpretation and extensions to the socks protocols.
14736 - Add a ContactInfo option, which gets published in descriptor.
14737 - Publish OR uptime in descriptor (and thus in directory) too.
14738 - Write tor version at the top of each log file
14739 - New docs in the tarball:
14741 - Document that you should proxy your SSL traffic too.
14744 Changes in version 0.0.7.2 - 2004-07-07
14745 o A better fix for the 0.0.0.0 problem, that will hopefully
14746 eliminate the remaining related assertion failures.
14749 Changes in version 0.0.7.1 - 2004-07-04
14750 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14751 since internally we use 0.0.0.0 to signify "not yet resolved".
14754 Changes in version 0.0.7 - 2004-06-07
14755 o Updated the man page to reflect the new features.
14758 Changes in version 0.0.7rc2 - 2004-06-06
14759 o Changes from 0.0.7rc1:
14760 - Make it build on Win32 again.
14761 o Changes from 0.0.6.2:
14762 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14766 Changes in version 0.0.7rc1 - 2004-06-02
14768 - On sighup, we were adding another log without removing the first
14769 one. So log messages would get duplicated n times for n sighups.
14770 - Several cases of using a connection after we'd freed it. The
14771 problem was that connections that are pending resolve are in both
14772 the pending_resolve tree, and also the circuit's resolving_streams
14773 list. When you want to remove one, you must remove it from both.
14774 - Fix a double-mark-for-close where an end cell arrived for a
14775 resolving stream, and then the resolve failed.
14776 - Check directory signatures based on name of signer, not on whom
14777 we got the directory from. This will let us cache directories more
14780 - Crank up some of our constants to handle more users.
14783 Changes in version 0.0.7pre1 - 2004-06-02
14784 o Fixes for crashes and other obnoxious bugs:
14785 - Fix an epipe bug: sometimes when directory connections failed
14786 to connect, we would give them a chance to flush before closing
14788 - When we detached from a circuit because of resolvefailed, we
14789 would immediately try the same circuit twice more, and then
14790 give up on the resolve thinking we'd tried three different
14792 - Limit the number of intro circuits we'll attempt to build for a
14793 hidden service per 15-minute period.
14794 - Check recommended-software string *early*, before actually parsing
14795 the directory. Thus we can detect an obsolete version and exit,
14796 even if the new directory format doesn't parse.
14797 o Fixes for security bugs:
14798 - Remember which nodes are dirservers when you startup, and if a
14799 random OR enables his dirport, don't automatically assume he's
14800 a trusted dirserver.
14802 - Directory connections were asking the wrong poll socket to
14803 start writing, and not asking themselves to start writing.
14804 - When we detached from a circuit because we sent a begin but
14805 didn't get a connected, we would use it again the first time;
14806 but after that we would correctly switch to a different one.
14807 - Stop warning when the first onion decrypt attempt fails; they
14808 will sometimes legitimately fail now that we rotate keys.
14809 - Override unaligned-access-ok check when $host_cpu is ia64 or
14810 arm. Apparently they allow it but the kernel whines.
14811 - Dirservers try to reconnect periodically too, in case connections
14813 - Fix some memory leaks in directory servers.
14814 - Allow backslash in Win32 filenames.
14815 - Made Tor build complain-free on FreeBSD, hopefully without
14816 breaking other BSD builds. We'll see.
14818 - Doxygen markup on all functions and global variables.
14819 - Make directory functions update routerlist, not replace it. So
14820 now directory disagreements are not so critical a problem.
14821 - Remove the upper limit on number of descriptors in a dirserver's
14822 directory (not that we were anywhere close).
14823 - Allow multiple logfiles at different severity ranges.
14824 - Allow *BindAddress to specify ":port" rather than setting *Port
14825 separately. Allow multiple instances of each BindAddress config
14826 option, so you can bind to multiple interfaces if you want.
14827 - Allow multiple exit policy lines, which are processed in order.
14828 Now we don't need that huge line with all the commas in it.
14829 - Enable accept/reject policies on SOCKS connections, so you can bind
14830 to 0.0.0.0 but still control who can use your OP.
14833 Changes in version 0.0.6.2 - 2004-05-16
14834 o Our integrity-checking digest was checking only the most recent cell,
14835 not the previous cells like we'd thought.
14836 Thanks to Stefan Mark for finding the flaw!
14839 Changes in version 0.0.6.1 - 2004-05-06
14840 o Fix two bugs in our AES counter-mode implementation (this affected
14841 onion-level stream encryption, but not TLS-level). It turns
14842 out we were doing something much more akin to a 16-character
14843 polyalphabetic cipher. Oops.
14844 Thanks to Stefan Mark for finding the flaw!
14845 o Retire moria3 as a directory server, and add tor26 as a directory
14849 Changes in version 0.0.6 - 2004-05-02
14850 [version bump only]
14853 Changes in version 0.0.6rc4 - 2004-05-01
14854 o Update the built-in dirservers list to use the new directory format
14855 o Fix a rare seg fault: if a node offering a hidden service attempts
14856 to build a circuit to Alice's rendezvous point and fails before it
14857 reaches the last hop, it retries with a different circuit, but
14859 o Handle windows socket errors correctly.
14862 Changes in version 0.0.6rc3 - 2004-04-28
14863 o Don't expire non-general excess circuits (if we had enough
14864 circuits open, we were expiring rendezvous circuits -- even
14865 when they had a stream attached. oops.)
14866 o Fetch randomness from /dev/urandom better (not via fopen/fread)
14867 o Better debugging for tls errors
14868 o Some versions of openssl have an SSL_pending function that erroneously
14869 returns bytes when there is a non-application record pending.
14870 o Set Content-Type on the directory and hidserv descriptor.
14871 o Remove IVs from cipher code, since AES-ctr has none.
14872 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
14873 o We were using an array of length zero in a few places.
14874 o win32's gethostbyname can't resolve an IP to an IP.
14875 o win32's close can't close a socket.
14878 Changes in version 0.0.6rc2 - 2004-04-26
14879 o Fix a bug where we were closing tls connections intermittently.
14880 It turns out openssl keeps its errors around -- so if an error
14881 happens, and you don't ask about it, and then another openssl
14882 operation happens and succeeds, and you ask if there was an error,
14883 it tells you about the first error. Fun fun.
14884 o Fix a bug that's been lurking since 27 may 03 (!)
14885 When passing back a destroy cell, we would use the wrong circ id.
14886 'Mostly harmless', but still worth fixing.
14887 o Since we don't support truncateds much, don't bother sending them;
14888 just close the circ.
14889 o check for <machine/limits.h> so we build on NetBSD again (I hope).
14890 o don't crash if a conn that sent a begin has suddenly lost its circuit
14891 (this was quite rare).
14894 Changes in version 0.0.6rc1 - 2004-04-25
14895 o We now rotate link (tls context) keys and onion keys.
14896 o CREATE cells now include oaep padding, so you can tell
14897 if you decrypted them correctly.
14898 o Add bandwidthburst to server descriptor.
14899 o Directories now say which dirserver signed them.
14900 o Use a tor_assert macro that logs failed assertions too.
14903 Changes in version 0.0.6pre5 - 2004-04-18
14904 o changes from 0.0.6pre4:
14905 - make tor build on broken freebsd 5.2 installs
14906 - fix a failed assert when you try an intro point, get a nack, and try
14907 a second one and it works.
14908 - when alice uses a port that the hidden service doesn't accept,
14909 it now sends back an end cell (denied by exit policy). otherwise
14910 alice would just have to wait to time out.
14911 - fix another rare bug: when we had tried all the intro
14912 points for a hidden service, we fetched the descriptor
14913 again, but we left our introcirc thinking it had already
14914 sent an intro, so it kept waiting for a response...
14915 - bugfix: when you sleep your hidden-service laptop, as soon
14916 as it wakes up it tries to upload a service descriptor, but
14917 socketpair fails for some reason (localhost not up yet?).
14918 now we simply give up on that upload, and we'll try again later.
14919 i'd still like to find the bug though.
14920 - if an intro circ waiting for an ack dies before getting one, then
14922 - we were reusing stale service descriptors and refetching usable
14926 Changes in version 0.0.6pre4 - 2004-04-14
14927 o changes from 0.0.6pre3:
14928 - when bob fails to connect to the rendezvous point, and his
14929 circ didn't fail because of the rendezvous point itself, then
14930 he retries a couple of times
14931 - we expire introduction and rendezvous circs more thoroughly
14932 (sometimes they were hanging around forever)
14933 - we expire unattached rendezvous streams that have been around
14934 too long (they were sticking around forever).
14935 - fix a measly fencepost error that was crashing everybody with
14939 Changes in version 0.0.6pre3 - 2004-04-14
14940 o changes from 0.0.6pre2:
14941 - make hup work again
14942 - fix some memory leaks for dirservers
14943 - allow more skew in rendezvous descriptor timestamps, to help
14944 handle people like blanu who don't know what time it is
14945 - normal circs are 3 hops, but some rend/intro circs are 4, if
14946 the initiator doesn't get to choose the last hop
14947 - send acks for introductions, so alice can know whether to try
14949 - bob publishes intro points more correctly
14950 o changes from 0.0.5:
14951 - fix an assert trigger that's been plaguing us since the days
14952 of 0.0.2prexx (thanks weasel!)
14953 - retry stream correctly when we fail to connect because of
14954 exit-policy-reject (should try another) or can't-resolve-address
14955 (also should try another, because dns on random internet servers
14957 - when we hup a dirserver and we've *removed* a server from the
14958 approved-routers list, now we remove that server from the
14959 in-memory directories too
14962 Changes in version 0.0.6pre2 - 2004-04-08
14963 o We fixed our base32 implementation. Now it works on all architectures.
14966 Changes in version 0.0.6pre1 - 2004-04-08
14968 - Hidden services and rendezvous points are implemented. Go to
14969 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
14970 hidden services. (This only works via a socks4a proxy such as
14971 Privoxy, and currently it's quite slow.)
14974 Changes in version 0.0.5 - 2004-03-30
14975 [version bump only]
14978 Changes in version 0.0.5rc3 - 2004-03-29
14979 o Install torrc as torrc.sample -- we no longer clobber your
14981 o Re-enable recommendedversion checking (we broke it in rc2, oops)
14982 o Add in a 'notice' log level for things the operator should hear
14983 but that aren't warnings
14986 Changes in version 0.0.5rc2 - 2004-03-29
14987 o Hold socks connection open until reply is flushed (if possible)
14988 o Make exit nodes resolve IPs to IPs immediately, rather than asking
14989 the dns farm to do it.
14990 o Fix c99 aliasing warnings in rephist.c
14991 o Don't include server descriptors that are older than 24 hours in the
14993 o Give socks 'reject' replies their whole 15s to attempt to flush,
14994 rather than seeing the 60s timeout and assuming the flush had failed.
14995 o Clean automake droppings from the cvs repository
14998 Changes in version 0.0.5rc1 - 2004-03-28
14999 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15000 o Only build circuits after we've fetched the directory: clients were
15001 using only the directory servers before they'd fetched a directory.
15002 This also means longer startup time; so it goes.
15003 o Fix an assert trigger where an OP would fail to handshake, and we'd
15004 expect it to have a nickname.
15005 o Work around a tsocks bug: do a socks reject when AP connection dies
15006 early, else tsocks goes into an infinite loop.
15009 Changes in version 0.0.4 - 2004-03-26
15010 o When connecting to a dirserver or OR and the network is down,
15014 Changes in version 0.0.3 - 2004-03-26
15015 o Warn and fail if server chose a nickname with illegal characters
15016 o Port to Solaris and Sparc:
15017 - include missing header fcntl.h
15018 - have autoconf find -lsocket -lnsl automatically
15019 - deal with hardware word alignment
15020 - make uname() work (solaris has a different return convention)
15021 - switch from using signal() to sigaction()
15022 o Preliminary work on reputation system:
15023 - Keep statistics on success/fail of connect attempts; they're published
15024 by kill -USR1 currently.
15025 - Add a RunTesting option to try to learn link state by creating test
15026 circuits, even when SocksPort is off.
15027 - Remove unused open circuits when there are too many.
15030 Changes in version 0.0.2 - 2004-03-19
15031 - Include strlcpy and strlcat for safer string ops
15032 - define INADDR_NONE so we compile (but still not run) on solaris
15035 Changes in version 0.0.2pre27 - 2004-03-14
15037 - Allow internal tor networks (we were rejecting internal IPs,
15038 now we allow them if they're set explicitly).
15039 - And fix a few endian issues.
15042 Changes in version 0.0.2pre26 - 2004-03-14
15044 - If a stream times out after 15s without a connected cell, don't
15045 try that circuit again: try a new one.
15046 - Retry streams at most 4 times. Then give up.
15047 - When a dirserver gets a descriptor from an unknown router, it
15048 logs its fingerprint (so the dirserver operator can choose to
15049 accept it even without mail from the server operator).
15050 - Inform unapproved servers when we reject their descriptors.
15051 - Make tor build on Windows again. It works as a client, who knows
15053 - Clearer instructions in the torrc for how to set up a server.
15054 - Be more efficient about reading fd's when our global token bucket
15055 (used for rate limiting) becomes empty.
15057 - Stop asserting that computers always go forward in time. It's
15059 - When we sent a cell (e.g. destroy) and then marked an OR connection
15060 expired, we might close it before finishing a flush if the other
15061 side isn't reading right then.
15062 - Don't allow dirservers to start if they haven't defined
15063 RecommendedVersions
15064 - We were caching transient dns failures. Oops.
15065 - Prevent servers from publishing an internal IP as their address.
15066 - Address a strcat vulnerability in circuit.c
15069 Changes in version 0.0.2pre25 - 2004-03-04
15071 - Put the OR's IP in its router descriptor, not its fqdn. That way
15072 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15075 - If the user typed in an address that didn't resolve, the server
15079 Changes in version 0.0.2pre24 - 2004-03-03
15081 - Fix an assertion failure in dns.c, where we were trying to dequeue
15082 a pending dns resolve even if it wasn't pending
15083 - Fix a spurious socks5 warning about still trying to write after the
15084 connection is finished.
15085 - Hold certain marked_for_close connections open until they're finished
15086 flushing, rather than losing bytes by closing them too early.
15087 - Correctly report the reason for ending a stream
15088 - Remove some duplicate calls to connection_mark_for_close
15089 - Put switch_id and start_daemon earlier in the boot sequence, so it
15090 will actually try to chdir() to options.DataDirectory
15091 - Make 'make test' exit(1) if a test fails; fix some unit tests
15092 - Make tor fail when you use a config option it doesn't know about,
15093 rather than warn and continue.
15094 - Make --version work
15095 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15098 Changes in version 0.0.2pre23 - 2004-02-29
15100 - Print a statement when the first circ is finished, so the user
15101 knows it's working.
15102 - If a relay cell is unrecognized at the end of the circuit,
15103 send back a destroy. (So attacks to mutate cells are more
15105 - New config option 'excludenodes' to avoid certain nodes for circuits.
15106 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15107 so you can collect coredumps there.
15109 - Fix a bug in tls flushing where sometimes data got wedged and
15110 didn't flush until more data got sent. Hopefully this bug was
15111 a big factor in the random delays we were seeing.
15112 - Make 'connected' cells include the resolved IP, so the client
15113 dns cache actually gets populated.
15114 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15115 - When we time-out on a stream and detach from the circuit, send an
15116 end cell down it first.
15117 - Only warn about an unknown router (in exitnodes, entrynodes,
15118 excludenodes) after we've fetched a directory.
15121 Changes in version 0.0.2pre22 - 2004-02-26
15123 - Servers publish less revealing uname information in descriptors.
15124 - More memory tracking and assertions, to crash more usefully when
15126 - If the default torrc isn't there, just use some default defaults.
15127 Plus provide an internal dirservers file if they don't have one.
15128 - When the user tries to use Tor as an http proxy, give them an http
15129 501 failure explaining that we're a socks proxy.
15130 - Dump a new router.desc on hup, to help confused people who change
15131 their exit policies and then wonder why router.desc doesn't reflect
15133 - Clean up the generic tor.sh init script that we ship with.
15135 - If the exit stream is pending on the resolve, and a destroy arrives,
15136 then the stream wasn't getting removed from the pending list. I
15137 think this was the one causing recent server crashes.
15138 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15139 - When it couldn't resolve any dirservers, it was useless from then on.
15140 Now it reloads the RouterFile (or default dirservers) if it has no
15142 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15143 many users don't even *have* a /usr/local/sbin/.
15146 Changes in version 0.0.2pre21 - 2004-02-18
15148 - There's a ChangeLog file that actually reflects the changelog.
15149 - There's a 'torify' wrapper script, with an accompanying
15150 tor-tsocks.conf, that simplifies the process of using tsocks for
15151 tor. It even has a man page.
15152 - The tor binary gets installed to sbin rather than bin now.
15153 - Retry streams where the connected cell hasn't arrived in 15 seconds
15154 - Clean up exit policy handling -- get the default out of the torrc,
15155 so we can update it without forcing each server operator to fix
15157 - Allow imaps and pop3s in default exit policy
15159 - Prevent picking middleman nodes as the last node in the circuit
15162 Changes in version 0.0.2pre20 - 2004-01-30
15164 - We now have a deb package, and it's in debian unstable. Go to
15165 it, apt-getters. :)
15166 - I've split the TotalBandwidth option into BandwidthRate (how many
15167 bytes per second you want to allow, long-term) and
15168 BandwidthBurst (how many bytes you will allow at once before the cap
15169 kicks in). This better token bucket approach lets you, say, set
15170 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15171 performance while not exceeding your monthly bandwidth quota.
15172 - Push out a tls record's worth of data once you've got it, rather
15173 than waiting until you've read everything waiting to be read. This
15174 may improve performance by pipelining better. We'll see.
15175 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15176 from failed circuits (if they haven't been connected yet) and attach
15178 - Expire old streams that haven't managed to connect. Some day we'll
15179 have them reattach to new circuits instead.
15182 - Fix several memory leaks that were causing servers to become bloated
15184 - Fix a few very rare assert triggers. A few more remain.
15185 - Setuid to User _before_ complaining about running as root.
15188 Changes in version 0.0.2pre19 - 2004-01-07
15190 - Fix deadlock condition in dns farm. We were telling a child to die by
15191 closing the parent's file descriptor to him. But newer children were
15192 inheriting the open file descriptor from the parent, and since they
15193 weren't closing it, the socket never closed, so the child never read
15194 eof, so he never knew to exit. Similarly, dns workers were holding
15195 open other sockets, leading to all sorts of chaos.
15196 - New cleaner daemon() code for forking and backgrounding.
15197 - If you log to a file, it now prints an entry at the top of the
15198 logfile so you know it's working.
15199 - The onionskin challenge length was 30 bytes longer than necessary.
15200 - Started to patch up the spec so it's not quite so out of date.
15203 Changes in version 0.0.2pre18 - 2004-01-02
15205 - Fix endian issues with the 'integrity' field in the relay header.
15206 - Fix a potential bug where connections in state
15207 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15210 Changes in version 0.0.2pre17 - 2003-12-30
15212 - Made --debuglogfile (or any second log file, actually) work.
15213 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15214 adversary could force us into an infinite loop.
15217 - Each onionskin handshake now includes a hash of the computed key,
15218 to prove the server's identity and help perfect forward secrecy.
15219 - Changed cell size from 256 to 512 bytes (working toward compatibility
15221 - Changed cell length to 2 bytes, and moved it to the relay header.
15222 - Implemented end-to-end integrity checking for the payloads of
15224 - Separated streamid from 'recognized' (otherwise circuits will get
15225 messed up when we try to have streams exit from the middle). We
15226 use the integrity-checking to confirm that a cell is addressed to
15228 - Randomize the initial circid and streamid values, so an adversary who
15229 breaks into a node can't learn how many circuits or streams have
15233 Changes in version 0.0.2pre16 - 2003-12-14
15235 - Fixed a bug that made HUP trigger an assert
15236 - Fixed a bug where a circuit that immediately failed wasn't being
15237 counted as a failed circuit in counting retries.
15240 - Now we close the circuit when we get a truncated cell: otherwise we're
15241 open to an anonymity attack where a bad node in the path truncates
15242 the circuit and then we open streams at him.
15243 - Add port ranges to exit policies
15244 - Add a conservative default exit policy
15245 - Warn if you're running tor as root
15246 - on HUP, retry OR connections and close/rebind listeners
15247 - options.EntryNodes: try these nodes first when picking the first node
15248 - options.ExitNodes: if your best choices happen to include any of
15249 your preferred exit nodes, you choose among just those preferred
15251 - options.ExcludedNodes: nodes that are never picked in path building
15254 Changes in version 0.0.2pre15 - 2003-12-03
15255 o Robustness and bugfixes:
15256 - Sometimes clients would cache incorrect DNS resolves, which would
15257 really screw things up.
15258 - An OP that goes offline would slowly leak all its sockets and stop
15260 - A wide variety of bugfixes in exit node selection, exit policy
15261 handling, and processing pending streams when a new circuit is
15263 - Pick nodes for a path only from those the directory says are up
15264 - Choose randomly from all running dirservers, not always the first one
15265 - Increase allowed http header size for directory fetch.
15266 - Stop writing to stderr (if we're daemonized it will be closed).
15267 - Enable -g always, so cores will be more useful to me.
15268 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15271 - Wrote a man page. It lists commonly used options.
15274 - Change default loglevel to warn.
15275 - Make PidFile default to null rather than littering in your CWD.
15276 - OnionRouter config option is now obsolete. Instead it just checks
15278 - Moved to a single unified torrc file for both clients and servers.
15281 Changes in version 0.0.2pre14 - 2003-11-29
15282 o Robustness and bugfixes:
15283 - Force the admin to make the DataDirectory himself
15284 - to get ownership/permissions right
15285 - so clients no longer make a DataDirectory and then never use it
15286 - fix bug where a client who was offline for 45 minutes would never
15287 pull down a directory again
15288 - fix (or at least hide really well) the dns assert bug that was
15289 causing server crashes
15290 - warnings and improved robustness wrt clockskew for certs
15291 - use the native daemon(3) to daemonize, when available
15292 - exit if bind() fails
15293 - exit if neither socksport nor orport is defined
15294 - include our own tor_timegm (Win32 doesn't have its own)
15295 - bugfix for win32 with lots of connections
15296 - fix minor bias in PRNG
15297 - make dirserver more robust to corrupt cached directory
15300 - Wrote the design document (woo)
15302 o Circuit building and exit policies:
15303 - Circuits no longer try to use nodes that the directory has told them
15305 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15306 bitcounts (18.0.0.0/8).
15307 - Make AP connections standby for a circuit if no suitable circuit
15308 exists, rather than failing
15309 - Circuits choose exit node based on addr/port, exit policies, and
15310 which AP connections are standing by
15311 - Bump min pathlen from 2 to 3
15312 - Relay end cells have a payload to describe why the stream ended.
15313 - If the stream failed because of exit policy, try again with a new
15315 - Clients have a dns cache to remember resolved addresses.
15316 - Notice more quickly when we have no working circuits
15319 - APPort is now called SocksPort
15320 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15322 - RecommendedVersions is now a config variable rather than
15323 hardcoded (for dirservers)
15324 - Reloads config on HUP
15325 - Usage info on -h or --help
15326 - If you set User and Group config vars, it'll setu/gid to them.
15329 Changes in version 0.0.2pre13 - 2003-10-19
15330 o General stability:
15331 - SSL_write no longer fails when it returns WANTWRITE and the number
15332 of bytes in the buf has changed by the next SSL_write call.
15333 - Fix segfault fetching directory when network is down
15334 - Fix a variety of minor memory leaks
15335 - Dirservers reload the fingerprints file on HUP, so I don't have
15336 to take down the network when I approve a new router
15337 - Default server config file has explicit Address line to specify fqdn
15340 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15341 - Make listener connections not ever alloc bufs
15343 o Autoconf improvements:
15344 - don't clobber an external CFLAGS in ./configure
15345 - Make install now works
15346 - create var/lib/tor on make install
15347 - autocreate a tor.sh initscript to help distribs
15348 - autocreate the torrc and sample-server-torrc with correct paths
15350 o Log files and Daemonizing now work:
15351 - If --DebugLogFile is specified, log to it at -l debug
15352 - If --LogFile is specified, use it instead of commandline
15353 - If --RunAsDaemon is set, tor forks and backgrounds on startup